--- Log for 10.11.113 Server: sendak.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 3 days and 18 hours ago 00.04.53 Quit Guest17648 (Ping timeout: 272 seconds) 00.05.34 Join Guest17648 [0] (~husvagn@94.234.170.11) 00.13.54 Quit kugel (Ping timeout: 245 seconds) 00.15.42 Quit y4n (Quit: AMIGAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAHAHAHAHAAAAAAAAAAAAHAHAAA) 00.22.16 Quit n1s (Quit: Ex-Chat) 01.01.25 Quit Zagor (Quit: Clint excited) 01.03.47 Quit pamaury (Ping timeout: 272 seconds) 01.08.33 Quit Narod () 01.10.45 Join treaki__ [0] (c791bd9c79@p4FF4ADB5.dip0.t-ipconnect.de) 01.14.33 Quit treaki_ (Ping timeout: 245 seconds) 01.29.09 Nick SuperBrainAk is now known as DormantBrain (~andy@2001:470:8:a61::5f92:59a1) 01.31.51 *** Saving seen data "./dancer.seen" 01.36.24 Quit bertrik (Remote host closed the connection) 01.37.18 Quit ender` (Quit: Cigarettes are like squirrels. They're perfectly harmless until you put one in your mouth and light it on fire.) 01.42.04 Quit dfkt (Remote host closed the connection) 01.53.26 # <[Saint]> [08:11:13] The iPod Classic devices are as big as the iPod Video, right? 01.53.26 # <[Saint]> [08:12:44] thinner 01.53.55 # <[Saint]> ...only some. 01.55.06 # <[Saint]> The 160GB CE-ATA Classic is massive. 02.01.30 Nick DormantBrain is now known as SuperBrainAk (~andy@2001:470:8:a61::5f92:59a1) 02.12.03 Quit mc2739 (Ping timeout: 248 seconds) 02.14.03 Join mc2739 [0] (~mc2739@rockbox/developer/mc2739) 02.38.43 Quit Guest17648 (Ping timeout: 245 seconds) 02.39.00 Join Guest17648 [0] (~husvagn@90-230-140-28-no41.tbcn.telia.com) 02.44.34 Quit Guest17648 (Quit: Hmmm...) 02.47.18 Join Guest17648 [0] (~husvagn@90-230-140-28-no41.tbcn.telia.com) 02.48.23 Quit Guest17648 (Client Quit) 03.03.12 Quit krabador (Quit: Leaving) 03.22.17 Quit lebellium (Quit: ChatZilla 0.9.90.1 [Firefox 26.0/20131107161719]) 03.31.53 *** Saving seen data "./dancer.seen" 04.50.59 Quit amiconn (Disconnected by services) 04.50.59 Join amiconn_ [0] (amiconn@rockbox/developer/amiconn) 04.51.03 Nick amiconn_ is now known as amiconn (amiconn@rockbox/developer/amiconn) 04.51.18 Quit pixelma (Read error: Operation timed out) 04.51.39 Join pixelma [0] (pixelma@rockbox/staff/pixelma) 05.31.55 *** Saving seen data "./dancer.seen" 05.32.16 Quit [7] (Disconnected by services) 05.32.29 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven) 05.47.31 Nick SuperBrainAk is now known as DormantBrain (~andy@2001:470:8:a61::5f92:59a1) 06.14.48 Nick DormantBrain is now known as SuperBrainAk (~andy@2001:470:8:a61::5f92:59a1) 07.15.40 Quit rdn (Remote host closed the connection) 07.30.16 Join kevku [0] (~kevku@2001:470:27:773:0:feed:c0f:fee) 07.31.56 *** Saving seen data "./dancer.seen" 07.47.34 Join foolsh [0] (~foolsh@c-24-14-134-34.hsd1.in.comcast.net) 08.16.09 Quit [Saint] (Remote host closed the connection) 08.18.16 Join [Saint] [0] (~saint@rockbox/user/saint) 08.52.18 Quit nosa-j (Ping timeout: 260 seconds) 08.54.16 Join nosa-j [0] (~m00k@66.233.224.206) 09.04.11 Nick SuperBrainAk is now known as DormantBrain (~andy@2001:470:8:a61::5f92:59a1) 09.08.32 Join rela [0] (~x@pdpc/supporter/active/rela) 09.24.40 Join y4n [0] (~y4n@unaffiliated/y4ndexx) 09.30.19 Join ender` [0] (krneki@foo.eternallybored.org) 09.32.00 *** Saving seen data "./dancer.seen" 09.50.55 Join lorenzo92 [0] (~chatzilla@host158-109-dynamic.6-79-r.retail.telecomitalia.it) 09.52.06 Join bertrik [0] (~quassel@rockbox/developer/bertrik) 09.53.45 Quit lorenzo92 (Remote host closed the connection) 09.55.40 Join mortalis [0] (~mortalis@77.108.98.176) 10.07.06 Join eyfour [0] (~eyfour@13.90-149-56.nextgentel.com) 10.14.03 Join n1s [0] (~n1s@rockbox/developer/n1s) 10.31.41 Quit nosa-j (Ping timeout: 265 seconds) 10.33.55 Join nosa-j [0] (~m00k@66.233.224.206) 10.34.49 Quit nosa-j (Excess Flood) 10.35.53 Join nosa-j [0] (~m00k@66.233.224.206) 10.42.48 Join Narod [0] (Narod@p5DDDAAB7.dip0.t-ipconnect.de) 10.56.49 Quit nosa-j (Ping timeout: 265 seconds) 11.01.43 Join nosa-j [0] (~m00k@66.233.224.206) 11.31.11 Quit rela (Read error: Connection reset by peer) 11.32.04 *** Saving seen data "./dancer.seen" 12.08.17 Join lebellium [0] (~chatzilla@lns-c10k-ld-02-m-212-194-176-149.dsl.sta.abo.bbox.fr) 12.38.14 Join sisyphe [0] (revolver14@183.4.92.135) 12.39.01 # Build Server message: 3New build round started. Revision 500b137, 240 builds, 37 clients. 12.43.24 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 12.50.37 # Build Server message: 3Build round completed after 696 seconds. 13.07.26 Join Guest17648 [0] (~husvagn@90-230-140-28-no41.tbcn.telia.com) 13.15.17 Quit Guest17648 (Quit: Hmmm...) 13.23.06 Join Guest17648 [0] (~husvagn@90-230-140-28-no41.tbcn.telia.com) 13.32.06 *** Saving seen data "./dancer.seen" 13.33.44 Quit thegeek (Ping timeout: 245 seconds) 13.43.29 # Hello im looking 4 a rockbox for android 800x480x86 13.44.33 # here http://rasher.dk/rockbox/android/ 13.47.47 # Yes, I tried this.They are built from an unmodified source tree and not so user-friendly on android, any other builds? 13.48.15 # why would there be other builds? 13.48.17 Join rela [0] (~x@pdpc/supporter/active/rela) 13.48.49 # That's how Rockbox is on Android 13.48.53 # there is no other version 13.50.31 # but Fonts issue... 13.50.47 # you can download the font pack 13.50.57 # I don't really know how to use it... 13.52.17 # how to use what? 13.52.18 # just upack at the right place... 13.52.28 # s/upack/unpack/ 14.20.40 # I think the Android port is listed as "unusable" for a reason. ;) 14.21.02 # It works, but it's far from being done. 14.23.44 # Yeah hope the per-day builds goes on 14.23.54 Quit sisyphe (Quit: ChatZilla 0.9.90.1 [Firefox 24.1.0/20131021230807]) 14.36.19 # I think rockbox needs pretty much an entirely different UI for Android. Since we don't have buttons or a separate touchpad, having a classic scroll&select interface is not exactly the best idea. 14.36.46 # Maybe I'll do that as a project for college if my professor allows it. (in a year or two, that is.) 14.50.46 Join kugel [0] (~kugel@rockbox/developer/kugel) 15.12.13 # hum, there is something strange with the mmu setup of the NWZ-E380, it is not as usual 15.12.32 # I might need to reverse the full mmu setup finally 15.24.42 Quit bertrik (Remote host closed the connection) 15.32.10 *** Saving seen data "./dancer.seen" 15.34.34 Quit kugel (Ping timeout: 252 seconds) 15.35.38 Quit n1s (Quit: Ex-Chat) 15.54.41 Join SATAN_SATAN_ [0] (~smuxi@c-67-174-206-250.hsd1.ca.comcast.net) 15.55.45 Join krabador [0] (~krabador_@unaffiliated/krabador) 15.58.22 Join rdn [0] (~oop@cpe-69-204-124-212.buffalo.res.rr.com) 16.12.55 Join einhirn [0] (~Miranda@p4FC76CAF.dip0.t-ipconnect.de) 16.17.56 Quit einhirn (Ping timeout: 248 seconds) 16.21.36 Quit SATAN_SATAN_ (Ping timeout: 265 seconds) 16.31.17 Join bertrik [0] (~bertrik@rockbox/developer/bertrik) 16.39.26 Quit pamaury (Ping timeout: 244 seconds) 16.52.18 Join dfkt [0] (dfkt@unaffiliated/dfkt) 16.54.30 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 16.57.27 Quit liar (Ping timeout: 264 seconds) 17.10.07 Quit GodEater (Read error: Connection reset by peer) 17.11.25 Join GodEater [0] (~whoknows@cl-711.lon-02.gb.sixxs.net) 17.11.25 Quit GodEater (Changing host) 17.11.25 Join GodEater [0] (~whoknows@rockbox/staff/GodEater) 17.20.29 Part foolsh 17.23.22 Quit eyfour (Quit: WeeChat 0.3.7) 17.32.14 *** Saving seen data "./dancer.seen" 17.49.07 Join SATAN_SATAN_ [0] (~smuxi@c-67-174-206-250.hsd1.ca.comcast.net) 18.02.40 Quit SATAN_SATAN_ (Read error: Connection reset by peer) 18.12.25 Quit pamaury (Quit: No Ping reply in 180 seconds.) 18.13.14 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 18.25.24 Quit bertrik (Ping timeout: 248 seconds) 18.26.28 Quit krabador (Quit: Sto andando via) 18.33.47 Quit mc2739 (Quit: leaving) 18.35.58 Join mc2739 [0] (~mc2739@rockbox/developer/mc2739) 18.41.25 # Build Server message: 3New build round started. Revision b170c73, 240 builds, 38 clients. 18.46.48 Quit Scall (Ping timeout: 272 seconds) 18.52.10 Join Scall [0] (~chat@unaffiliated/scall) 18.53.30 # Build Server message: 3Build round completed after 725 seconds. 18.54.30 Quit GeekShadow (Remote host closed the connection) 18.55.23 Join kugel [0] (~kugel@p5DC53EB2.dip0.t-ipconnect.de) 18.55.33 Quit kugel (Changing host) 18.55.33 Join kugel [0] (~kugel@rockbox/developer/kugel) 18.57.49 Quit Scall (Ping timeout: 264 seconds) 19.01.30 Join GeekShadow [0] (~antoine@reactos/tester/GeekShadow) 19.05.09 Join Scall [0] (~chat@unaffiliated/scall) 19.10.52 Join liar [0] (~liar@83.175.90.24) 19.24.58 Quit mortalis (Quit: KVIrc 4.3.1 Aria http://www.kvirc.net/) 19.32.17 *** Saving seen data "./dancer.seen" 19.35.21 Nick DormantBrain is now known as SuperBrainAk (~andy@2001:470:8:a61::5f92:59a1) 19.36.12 Quit Poodlemastah (Read error: Connection reset by peer) 19.38.18 Quit pamaury (Quit: No Ping reply in 180 seconds.) 19.39.02 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 19.41.13 Join Poodlemastah [0] (~Poodlemas@109-124-181-96.customer.t3.se) 19.57.31 Join Zagor [242] (~bjst@rockbox/developer/Zagor) 20.05.31 Join n1s [0] (~n1s@nl118-168-30.student.uu.se) 20.05.33 Quit n1s (Changing host) 20.05.33 Join n1s [0] (~n1s@rockbox/developer/n1s) 20.28.21 Quit n1s (Quit: Ex-Chat) 20.29.28 # TheSeven: ping 20.29.35 # pong 20.29.49 # flyspray is now back up. a little thorny, but up. 20.31.12 # TheSeven: I am facing something really weird where disassembling some firmware for the imx233, maybe you'll have an idea 20.31.34 Quit rela (Read error: Connection reset by peer) 20.32.30 # The firmware is a bit like elf: there are chunks of code which are loaded at different location in memory. On top of this, the firmware comes with a big data block which is actually code to put at a virtual location (to handle swapping). Some the firmware setup virtual memory and loads this block of code. Noting too fancy BUT 20.32.51 # s/Some/Later 20.33.19 # the firmware code mostly lies in two blocks: [0,0x8000[ and [0x40000000,0x40900000[ 20.33.35 # but virtual block of code lies in [0x100000,0x300000[ 20.33.57 # and now for the weirdness: in the virtual code, I found occurences of calls to some non-existing code 20.34.33 # for example, some (obviously interworking stuff) code calls code at 0x40A3891D, so non-mapped location 20.35.01 # what is funny is that for some reason, I know what the piece of code called, and I know its actual address is 0x4086C92C 20.35.39 # you couldn't tell anything from one example, right ? But I have a second occurrence of the problem: code calls 0x40A37F7D and I know the actual code is at 0x4086BF8C 20.35.59 # now there is some strange coincidence: in both cases, the offset is 0x1CBFF1 20.36.36 # any idea on how this could work and why it is done this way ? 20.38.53 # some kind of runtime relocation going on? 20.39.04 # do you have a memory dump of how all of this looks like once it's loaded? 20.39.31 # no 20.39.39 # I don't even have the device ^^ 20.40.12 # hm... 20.40.31 # yeah I thought about relocation but why would you do that when you know in advance the location of this block of code ? 20.40.41 # the offset +1 part suggests thumb is involved here, but no idea where that ~190KB offset comes from 20.40.49 # do they really know that at compile time? 20.41.11 # the offset seems a bit too small to make sense for runtime relocation 20.41.15 # yeah the target is thumb code 20.41.24 # you'd usually use virtual address 0 or something as the base for that 20.43.13 # yeah they know, I have disassemble enough of the mmu setup to know that, they *always* load the code block at 0x100000 20.43.35 # and on the other devices of the same line, the same virtual block of code existed and didn't have these strange addresses 20.43.51 # yes exactly, that's rather strange for a relocation 20.44.28 # the offset is not a multiple of something useful... 20.48.53 # omg 20.48.56 # I found out 20.49.04 # suicide suddently became an option 20.49.13 # as well 20.54.40 # sorry for loosing your time 21.03.52 Quit Jinx (Quit: reboot) 21.09.25 # pamaury: now I'm curious :) 21.13.08 # since: in ida I loaded the code as an additional file and since I do that in a virtual machine using shared folders which are very slow, I don't have the patience to go into the folders so I just type the uri directly 21.13.27 # so I put \\VBOXSHARED\\blabla\nwz-e360\fw_1.0.0\pvmi.bin 21.13.38 # instead of \\VBOXSHARED\\blabla\nwz-e380\fw_1.0.0\pvmi.bin 21.13.39 Join bertrik [0] (~quassel@rockbox/developer/bertrik) 21.13.52 # :) 21.14.05 # and since my reverse engineering folders are *very* well organised with standard naming for some, that was an actual file 21.14.35 # and since it was a very close target, it wasn't obvious that there was a mismatch, because some addresses were actually correct (!) 21.15.03 Quit y4n (Quit: only amiga makes it possible) 21.15.05 # I feel quite stupid now :) 21.32.21 *** Saving seen data "./dancer.seen" 21.44.32 Quit pamaury (Quit: No Ping reply in 180 seconds.) 21.45.53 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 21.56.28 Quit bluebrother (Read error: Connection reset by peer) 21.56.28 Quit fs-bluebot (Read error: Connection reset by peer) 21.56.41 Join bluebrother [0] (~dom@rockbox/developer/bluebrother) 22.00.12 Join fs-bluebot [0] (~fs-bluebo@f053154126.adsl.alicedsl.de) 22.12.10 # hum, the lcd of the e380 is the exact same (very bad) lcd as the e370 22.12.22 # Sony must be kidding, the E380 is just another E370 22.37.58 Nick SuperBrainAk is now known as DormantBrain (~andy@2001:470:8:a61::5f92:59a1) 22.49.45 # gevaerts: I'm wondering, isn't there an inherent race condition in the current code with the current implementation of card_get_info_target and sd_get_info() ? 22.50.01 # I mean, most sd drivers are lazy: they init the storage only on the first read/write 22.50.10 # Uhmmm 22.50.15 # I have *no* idea 22.50.23 # so if for some reason the get_info() is called before read_sectors() or write_sectors(), you're dead 22.51.53 # that might explain some weirdness with sd, doesn't it ? 22.51.57 # * gevaerts hasn't ever looked at sd drivers 22.52.24 # can you add a panic to the current source code and see if users report it? 22.52.30 # But yes, from what you describe, that could cause issues 22.52.51 # saratoga: that's what I going to do on my device to see 22.53.23 # which device is this? 22.55.41 # I'll tes on my fuze+ and on the ZEN 22.56.07 # fuze+ for microsd sd and ZEN because it's internal sotrage is sd and some users have reported funny things 22.56.39 # in general i like to put debug messages for as many possible error conditions as possible 22.56.55 # since we have all these random users saying they have a panic doing X 22.58.47 # yeah I agree, but like most race condition you first need to be aware that it can happen before you do something about it :) 22.58.57 # can burn-in occur on the display of an iPod Classic? 23.00.00 # probably not 23.00.07 # i don't think modern LCDs get that anymroe do they? 23.01.48 # I know it happened on the OLED display of my FiiO E7 23.04.12 # only OLED do that 23.04.23 # and all OLED do it ;) 23.04.41 # so LCD's fine? 23.04.45 # yeah OLED is a bunch of carbon, sooner or later it burns up if you put enough power into it 23.05.06 # LCDs are a lot more stable in general 23.06.14 Quit kevku (Ping timeout: 260 seconds) 23.08.10 # ok, thanks 23.24.49 Quit Guest17648 (Ping timeout: 264 seconds) 23.26.03 Nick rasher is now known as rasher_test (~rasher@rockbox/developer/rasher) 23.26.21 Nick rasher_test is now known as rasher (~rasher@rockbox/developer/rasher) 23.29.47 Quit dfkt (Disconnected by services) 23.29.49 Join dfkt_ [0] (OxO29A@unaffiliated/dfkt) 23.31.09 Quit Zagor (Quit: Clint excited) 23.32.23 *** Saving seen data "./dancer.seen" 23.42.23 # pamaury: I don't remember the details at all, but things start in usb.c with handling SYS_HOTSWAP_EXTRACTED and SYS_HOTSWAP_INSERTED, which trickles down to usb_storage.c where it mainly sets the ejected[] stuff, which is converted to lun_present in handle_scsi(), which is used to decide on what to return to SCSI_TEST_UNIT_READY 23.43.35 # yeah I saw that, so either we are doing it wrong or imx233 is broken wrt to this or the kernel doesn't correctly interpret our sense status 23.49.09 # pamaury: there is no difference between E370 and E380?! That's pure rebranding? 23.50.27 # lebellium: I'm not exactly sure how different but lcd is exactly the same, interesting pins so far too, not sure for the tuner but they are strong signs toward it 23.50.34 # so yeah, that's clearly possible at this point 23.50.46 # only the firmware is different, perhaps it handles more format 23.50.56 # hum 23.51.02 # I'll compare the user manual 23.51.29 # I don't understand why they use the same the lcd as the E370, it's soooo bad 23.51.33 # I hate when Sony tries to fool the consumer 23.51.33 # the E360 is much better 23.51.50 # yeah, worse screen for the same size 23.52.02 # same price* 23.52.50 # hey that's sony, they have been rebranding mp3 players for years now 23.52.58 # they basically only have two of them