[02:03:23] *** Joins: clustur (~logger@c-68-53-250-91.hsd1.tn.comcast.net) [02:03:23] *** Quits: clustur (~logger@c-68-53-250-91.hsd1.tn.comcast.net) (Remote host closed the connection) [03:27:37] *** Quits: n1s (~n1s@rockbox/developer/n1s) (Quit: Ex-Chat) [06:39:18] *** Quits: TheSeven (~quassel@rockbox/developer/TheSeven) (Disconnected by services) [06:39:27] *** Joins: [7] (~quassel@rockbox/developer/TheSeven) [06:44:03] *** Quits: [Saint] (~saint@rockbox/user/saint) (Quit: No Ping reply in 180 seconds.) [06:44:32] *** Joins: [Saint] (~saint@rockbox/user/saint) [07:42:03] *** Quits: [7] (~quassel@rockbox/developer/TheSeven) (Disconnected by services) [07:42:15] *** Joins: TheSeven (~quassel@rockbox/developer/TheSeven) [08:03:24] *** Joins: clustur (~logger@c-68-53-250-91.hsd1.tn.comcast.net) [08:03:24] *** Quits: clustur (~logger@c-68-53-250-91.hsd1.tn.comcast.net) (Remote host closed the connection) [12:45:06] *** Joins: n1s (~n1s@nl118-168-30.student.uu.se) [12:45:06] *** Quits: n1s (~n1s@nl118-168-30.student.uu.se) (Changing host) [12:45:06] *** Joins: n1s (~n1s@rockbox/developer/n1s) [13:37:24] [Saint]: how many n4gs do you have, and did you have time to try out umsboot 0.2 for n4g? [13:39:22] TheSeven: how do i check the LCD type of n4g? i remember there's something in diagmode, but i can't find it [13:41:22] user890104: i can test that bootstrapper thing tomorrow [13:41:44] n1s: ok, great [13:46:38] user890104: no idea, look at the bootstub... [13:48:38] looks like the nano4g is the first device that actually inquires the LCD about what it is instead of just using some GPIO pins [13:48:51] it sends a cmd 0x04 to the lcd, then reads back 3 bytes [13:49:13] the last byte determines the LCD type [13:49:27] there are 4 models: 0xb3, 0xc4, 0xd5 and 0xe6 [13:49:43] *** Quits: n1s (~n1s@rockbox/developer/n1s) (Quit: Ex-Chat) [13:49:59] all four of them seem to be implemented in the boot stub, but apparently some don't work [13:53:10] unlike on the older models, all seem to share the same command set after initialization though [13:55:49] user890104: if you want to fix your type, feel free to compare with the disassembly [13:57:49] http://codepad.org/CUJiDnOs [13:59:13] the first byte is the number of following bytes (the first one of those is a command, the others are data). if the length is >0x80, it is treated as a sleep (length & 0x7f milliseconds). 0x80 terminates the init sequence. [14:03:22] *** Joins: clustur (~logger@c-68-53-250-91.hsd1.tn.comcast.net) [14:03:22] *** Quits: clustur (~logger@c-68-53-250-91.hsd1.tn.comcast.net) (Remote host closed the connection) [14:08:22] *** Quits: [Saint] (~saint@rockbox/user/saint) (Remote host closed the connection) [14:09:28] *** Joins: [Saint] (~saint@rockbox/user/saint) [16:38:06] TheSeven: i'm going to write an app, that queries the lcd about its type, and prints it via usb for example (unless you have a similar tool) [16:38:28] so i know which type's init code is wrong [16:38:42] hm... are there direct LCD access APIs? [16:39:34] might be easiest to just directly mess with the LCD controller registers via USB while nothing is running that touches the LCD [20:03:24] *** Joins: clustur (~logger@c-68-53-250-91.hsd1.tn.comcast.net) [20:03:24] *** Quits: clustur (~logger@c-68-53-250-91.hsd1.tn.comcast.net) (Remote host closed the connection)