--- Log for 18.03.113 Server: sendak.freenode.net Channel: #rockbox --- Nick: Guest7860 Version: Dancer V4.16 Started: 10 days and 19 hours ago 00.05.22 Quit Guest23610 (Read error: Connection reset by peer) 00.05.31 Quit lebellium (Quit: ChatZilla 0.9.90 [Firefox 20.0/20130313170052]) 00.08.41 Join onyxice [0] (~Onyx@nat.mtp.cmsinter.net) 00.09.34 Quit Zinc_Alloy (Quit: CGI:IRC (Ping timeout)) 00.21.23 Join Zinc_Alloy [0] (~d9ee9ab9@www.haxx.se) 00.26.43 Quit ender` (Quit: If the experiment works, you must be using the wrong equipment. -- Patrick's Theorem) 00.27.36 Join digbaddy [0] (~benrobert@dslg221.ody.ca) 00.45.54 *** Saving seen data "./dancer.seen" 00.46.49 Quit bertrik (Ping timeout: 252 seconds) 00.56.57 Quit Zinc_Alloy (Quit: CGI:IRC) 01.20.31 Quit prof_wolfff (Ping timeout: 245 seconds) 01.27.18 Quit pamaury (Ping timeout: 256 seconds) 01.34.03 Join prof_wolfff [0] (~prof_wolf@62.83.50.196.dyn.user.ono.com) 02.45.55 *** Saving seen data "./dancer.seen" 03.16.51 Quit onyxice (Quit: There's no place like 127.0.0.1) 03.28.47 Quit krabador (Quit: Sto andando via) 03.51.00 Join onyxice [0] (~Onyx@nat.mtp.cmsinter.net) 03.55.20 Join jhMikeS [0] (~jethead71@50.4.240.19) 03.55.20 Quit jhMikeS (Changing host) 03.55.20 Join jhMikeS [0] (~jethead71@rockbox/developer/jhMikeS) 04.05.20 Quit Rower (Quit: Hmmm...) 04.08.03 # going to see about updating the forums...putting them into maintenance mode now... 04.17.37 Quit amiconn (Disconnected by services) 04.17.37 Quit pixelma (Disconnected by services) 04.17.38 Join pixelma_ [0] (pixelma@rockbox/staff/pixelma) 04.17.38 Join amiconn_ [0] (amiconn@rockbox/developer/amiconn) 04.17.40 Nick pixelma_ is now known as pixelma (pixelma@rockbox/staff/pixelma) 04.17.42 Nick amiconn_ is now known as amiconn (amiconn@rockbox/developer/amiconn) 04.32.53 Quit froggyman (Ping timeout: 252 seconds) 04.45.59 *** Saving seen data "./dancer.seen" 04.46.18 Join guset [0] (~4352b552@www.haxx.se) 04.49.37 Quit guset (Client Quit) 04.49.48 Join guset [0] (~4352b552@www.haxx.se) 04.55.12 Quit guset (Quit: CGI:IRC (Ping timeout)) 05.00.23 Join webguest012 [0] (~7d1@www.haxx.se) 05.05.52 Quit webguest012 (Quit: CGI:IRC) 05.10.56 # alright - should be good 05.14.59 Join TheSphinX^ [0] (~briehl@pD9FBB212.dip.t-dialin.net) 05.18.17 Quit TheSphinX_ (Ping timeout: 252 seconds) 05.34.43 Quit TheSeven (Read error: Operation timed out) 05.35.22 Quit [Saint] (Remote host closed the connection) 05.36.14 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven) 05.37.20 Join [Saint] [0] (~saint@rockbox/user/saint) 05.38.08 Join zamboni [0] (~bottledwa@unaffiliated/zamboni) 05.54.36 Quit bluebrother (Disconnected by services) 05.54.41 Join bluebrother^ [0] (~dom@rockbox/developer/bluebrother) 05.57.13 Quit fs-bluebot (Ping timeout: 245 seconds) 05.58.29 Join Provel [0] (~Provel@75-132-18-44.dhcp.stls.mo.charter.com) 05.58.31 Join fs-bluebot [0] (~fs-bluebo@g224239007.adsl.alicedsl.de) 06.01.08 Quit Provel_ (Ping timeout: 248 seconds) 06.02.05 Quit dfkt (Disconnected by services) 06.02.07 Join dfkt_ [0] (OxO29A@unaffiliated/dfkt) 06.08.42 Join kevku [0] (~kevku@2001:470:27:773:0:feed:c0f:fee) 06.11.00 Quit zamboni () 06.14.58 Join akaWolf [0] (~akaWolf@unaffiliated/akawolf) 06.31.03 Quit prof_wolfff (Ping timeout: 258 seconds) 06.46.01 *** Saving seen data "./dancer.seen" 07.25.47 Quit SuperBrainAK (Quit: pbly going to sleep /_\) 07.32.12 Join davo [0] (~davo@cpe-76-168-205-170.socal.res.rr.com) 07.34.26 Quit davo (Client Quit) 07.46.51 Join melmothX [0] (~melmoth@unaffiliated/melmothx) 08.06.48 Quit kevku (Ping timeout: 264 seconds) 08.13.17 Join ender` [0] (~ender@foo.eternallybored.org) 08.18.44 Join LinusN [0] (~linus@giant.haxx.se) 08.34.32 Join Zagor [242] (~bjst@rockbox/developer/Zagor) 08.42.07 # pamaury (for the logs): the OTG that you just found is probably the same one that the nano2g, ipod classic and some sansas use 08.42.29 # given how much trouble we're having with this driver, it might indeed be worth redoing from scratch 08.43.09 # I do however have a driver for that STM32F[24] series of chips that seems to work flawlessly, but has a slightly different interface towards the USB core 08.43.25 # if anyone is interested in that, I can pastebin it somewhere 08.46.05 *** Saving seen data "./dancer.seen" 08.46.47 Join mortalis [0] (~kvirc@213.33.220.118) 08.52.11 Join bertrik [0] (~quassel@rockbox/developer/bertrik) 09.03.09 Join lebellium [0] (~chatzilla@lns-c10k-ld-02-m-212-194-176-149.dsl.sta.abo.bbox.fr) 09.05.25 # seems to be some spam here http://forums.rockbox.org/index.php/topic,42709.msg218096.html?PHPSESSID=b248i2bjb3cm4ce2j8il919o34#new 09.06.15 Join kevku [0] (~kevku@2a01:d0:ffff:34a::8:3) 09.29.02 Quit bertrik (Ping timeout: 256 seconds) 09.34.39 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 09.40.23 Join petur [0] (~petur@rockbox/developer/petur) 09.42.11 Join einhirn [0] (~Miranda@bsod.rz.tu-clausthal.de) 10.02.38 Quit lebellium (Quit: ChatZilla 0.9.90 [Firefox 20.0/20130313170052]) 10.06.38 # TheSeven: is that an chipidea core? 10.07.18 # no idea, I just know that it's apparently from synopsys (or from someone that they bought), and that there's also a linux driver for it 10.08.03 # TheSeven: there are IIRC at least 3 driver for it as it was only noticed recently that it is build-in in sooo many SoCs. 10.08.51 # and yes, that's probably the same one. A colleague is currently fighting with it. 10.10.38 # drivers that i'm aware of: my old one (the old nano2g driver), our sansa driver (IIRC written by funman?), funman's new driver (merge of those two drivers), the linux driver, the STM32 reference driver, and my own STM32 driver 10.14.54 Quit jhMikeS (Ping timeout: 258 seconds) 10.17.26 # my own STM32 driver implementation for that core: 10.17.27 # USB core header: http://pastie.org/6600590 10.17.27 # USB core code: http://pastie.org/6600592 10.17.27 DBUG Enqueued KICK TheSeven 10.17.27 # Synopsys-specific header: http://pastie.org/6600594 10.17.27 # Synopsys-specific code: http://pastie.org/6600601 10.17.28 *** Alert Mode level 1 10.17.28 # STM32-specific code: http://pastie.org/6600604 10.17.49 # feel free to use that (or parts of it) wherever you need them 10.18.17 # pamaury: you as well :) 10.19.05 # TheSeven: great to know that :) 10.19.20 # In Linux it's at least: ci13xxx, drivers/usb/gadget/fsl_udc_core.c 10.19.50 # the linux driver doesn't use DMA because of some hardware bug IIRC 10.19.53 # I'm still light years from knowing enough of the rknano-b anyway, I just figured out from the disassembly that it is using this core 10.20.13 # this core is very similar to the one in amsv2 right ? 10.20.23 # probably the very same core 10.20.44 # that might be way dma on those is buggy ^^ 10.20.46 # *why 10.20.49 # (possibly with a different feature set, that can be adapted during synthesis) 10.20.54 # s/dma/driver using dma 10.21.17 # I've observed some weird things with DMA on the ipod classic as well 10.21.36 # the core locking up in certain situations when there's traffic on multiple endpoints at the same time 10.21.41 Ctcp Ignored 1 channel CTCP requests in 0 seconds at the last flood 10.21.41 # * pamaury will be back in hour one for this usb thing 10.22.12 # we currently see a stall and think it's related to an errata published by Freescale 10.22.20 # http://patchwork.ozlabs.org/patch/160326/ 10.22.34 # my driver supports both DMA and PIO mode, and DMA seems to work perfectly fine for my current use case (that just uses EP0 and one data endpoint) 10.22.51 # so mv_udc_core is a third instance of a driver for that core. 10.24.22 # ukleinek: seems like that errata is only important for host mode 10.25.03 # TheSeven: you're talking about the link in the commit log? 10.26.14 Quit pamaury (Ping timeout: 256 seconds) 10.26.50 # TheSeven: I think that is wrong, because drivers/usb/gadget is about usb device drivers 10.27.22 # I don't think this core uses memory mapped TDs in device mode at all (and I haven't dealt with host mode yet) 10.27.29 *** Alert Mode OFF 10.28.12 # * ukleinek looks for his colleague and asks him to come here as he doesn't know the glory details. 10.28.30 # so if this is referring to device mode, then that driver is for a different core 10.33.05 Quit melmothX (Ping timeout: 264 seconds) 10.34.23 Join melmothX [0] (~melmoth@unaffiliated/melmothx) 10.46.06 *** Saving seen data "./dancer.seen" 10.46.13 Quit kiwicam (Remote host closed the connection) 10.54.03 Join dot [0] (~mgr@port-212-202-120-50.static.qsc.de) 10.54.05 # hi 10.54.38 # i hear someone is fighting with an chipidea udc 10.57.20 # dot: you have the logs, right? 10.57.31 # (logs == channel logs) 10.58.30 Join bebna [0] (~a.fasold@94.101.33.114) 10.58.54 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 10.59.07 # the synopsys core doesn't use memory mapped TDs in device mode 11.00.02 # the usb core in freescale chips is usually the one we refer to as usb ARC, which uses memory mapped TDs 11.02.15 Quit kaputnik_ (Read error: Operation timed out) 11.02.31 # synosys has another core, which is not based on memorymapped tds, i think its name is dwc2 11.02.54 # pamaury: and which is the Linux kernel driver for the core you talked about? 11.03.38 # s/pamaury/TheSeven/ 11.03.44 # did I talk about a linux driver ? 11.03.47 # ah no 11.04.48 # you could look into drivers/usb/gadget/s3c-hsudc.c in the kernel, IMHO its an dwc2 implementation 11.07.19 # hsotg.c you mean, Im not sure hsudc.c is the same, but yeah it is, last time I checked it was fifo only iirc 11.08.35 # and that driver is unbearably complicated also, though far less than the original code from synopsis I got 11.09.13 # what is the difference between dwc and dwc2 ? 11.10.42 Quit copper (Quit: ZNC - http://znc.in) 11.11.01 # agree, i think currently i did not see any driver implementing dwc2 with dma mainline 11.11.34 # i think its the common name for the ehci-variant, as currently the dwc3 is being mainlined 11.11.59 # dwc3 == xhci 11.12.59 # I must say I was surprised to see a synopsis core in a rockchip soc 11.14.51 # hum, audio broken on the fuze+ but there was no recent change on the imx233 :( I'll need to bisect that 11.15.58 # dot, ukleinek, pamaury: yes, IIRC the synopsys one that we're using on STM32, AMSv2 and nano2g/classic is the dwc/dwc2 one 11.16.24 # you might be lucky, dwc2 is currently discussed on linux-usb 11.16.36 # <[Saint]> Maybe re-writing the driver will get us USB back on N2G ;) 11.16.40 # it's a shame we still haven't a working implementation, nano2g is broken and amsv2 is unstable 11.16.43 Join copper [0] (~copper@unaffiliated/copper) 11.16.54 # <[Saint]> heh - snap. 11.17.05 Join kaputnik_ [0] (~kaputnik@port-92-206-142-153.dynamic.qsc.de) 11.17.13 # http://www.spinics.net/lists/linux-usb/msg81662.html 11.17.34 # [Saint]: someone might want to port over my new dwc2 device mode driver for STM32 11.17.41 # (which I linked above) 11.18.08 # * [Saint] has no time to be someone lately 11.18.25 # <[Saint]> I've had to abandone pretty much all of my Rb projects 11.18.42 # dot: if you're curious, I have written this driver for an STM32 chip (it appears to use a dwc2 core) to get rid of STM's bloaty reference implementation 11.18.56 # TheSeven: I don't have the time for it right now but that sounds interesting 11.18.57 # it supports PIO and DMA, but only device mode so far, and uses a completely redesigned API 11.20.13 # oh, very interesting to hear that this is the core that's used in the raspberry pi, which has awfully buggy USB 11.20.34 # maybe that core is just bad :D 11.20.38 # <[Saint]> Oy - yes. 11.20.48 # <[Saint]> USB on the raspi is unbearably shite. 11.21.13 # device or host ? 11.21.16 # host 11.21.20 # <[Saint]> host 11.21.24 # <[Saint]> device is fine. 11.21.36 # that core is very popular and doesn't appear to be that bad, I suspect the driver is more of a problem :) 11.23.06 # dot: so what are you doing with that core? host or device mode? 11.23.13 # and what kind of problems are you observing? 11.23.35 # or are you dealing with the udc one? 11.26.04 # * [Saint] also thinks that this may be responsible for this issue with some wireless keyboards giving repeat keypresses on the raspi 11.26.21 # i've had that with non-wireless ones as well 11.26.33 # <[Saint]> I trialled an updated driver not so long ago that made things a /lot/ better. 11.26.36 # and keypresses being ignored during network traffic spikes (which is connected through USB as well) 11.27.13 # dot: if you're curious, here's my dwc2 device mode driver code: 11.27.14 # USB core header: http://pastie.org/6600590 11.27.14 # USB core code: http://pastie.org/6600592 11.27.14 # Synopsys-specific header: http://pastie.org/6600594 11.27.15 # Synopsys-specific code: http://pastie.org/6600601 11.27.17 # STM32-specific code: http://pastie.org/6600604 11.27.34 # * TheSeven heads to work, but will be online on his phone 11.27.41 # <[Saint]> actually, I think that might be 2.94a - which I think is in the debian image presently - but the version I was using had additional patches I think aren't currently in the raspbian images. 11.28.15 # * pamaury goes for lunch 11.28.26 # TheSeven: we're interested in imx23/28 host and device 11.30.22 # TheSeven: sorry, but we are not working with dwc2, we use the memorymapped td variant, known as chipidea 13xxx 11.52.13 # <[Saint]> Is there anything in particular keeping g#393 from being committed? 11.52.17 # 3Gerrit review #393 at http://gerrit.rockbox.org/r/393 : Implement "reverse stereo" channel configuration to reverse left and right audio... by Bertrik Sikken (changes/93/393/2) 11.52.32 # <[Saint]> 'tis a useful, and oft requested feature. 11.53.22 # <[Saint]> Aha - HWcodec. 11.54.55 # * [Saint] wonders where he put his volume cap patch 11.56.26 Join Lynx_ [0] (~bayer@109.171.130.211) 12.10.07 Join Ward [0] (~Mirandaha@bpb01-1-88-162-4-186.fbx.proxad.net) 12.10.30 Nick Ward is now known as Guest51073 (~Mirandaha@bpb01-1-88-162-4-186.fbx.proxad.net) 12.24.37 # ukleinek: usb devuce mx23 is usb arc, we have a driver for it, it's pretty common 12.26.00 Quit melmothX (Ping timeout: 258 seconds) 12.46.10 *** Saving seen data "./dancer.seen" 12.46.22 # JdGordon: ping FS#12639 12.46.24 # http://www.rockbox.org/tracker/task/12639 3Certain themes cause the WPS to not load properly and USB to not work (bugs, unconfirmed) 12.46.48 Join prof_wolfff [0] (~prof_wolf@62.83.50.196.dyn.user.ono.com) 12.52.41 # Hi, is there a way to read smart data from a ipod classic? It seems that my second hand bought one, has a problem with his disk and rockbox never stops to scan the disk on boot 12.53.32 # bebna: not easily, no. 12.53.44 # bebna: if database is enabled it could be a bug in metadata reading, choking on one of your files 12.53.48 # bebna: i was working on it for aw hile but it's really fiddly. 12.53.48 # dot: seen pamaury's statement? 12.54.15 # i can try to delete the db by the bootloader 12.55.00 # but there isn't propably a way to get rockbox working with a disk with faulty sectors 12.55.04 # right? 12.55.50 # well you have to replace the disk 12.57.29 # the thing is, the disk seems to work fine until i tried to delete the old ipod data dir from it 12.57.49 # so I assumed that only a small part of disk is damaged 12.58.44 # bebna: if the disk has a few bad sectors and it's not getting worse, then rockbox can work just fine; have chkdsk mark those sectors as bad and we won't use them 12.58.44 # the bootloader and rockbox itself seems to reading the .rockbox dir just fine from the disk for example 12.58.48 # however, that's unlikely to be the case 12.58.58 # hard disks with bad sectors are basically always dying 12.59.00 # and will get worse 12.59.08 # so, if you really do have bad sectors i'd replace the disk 12.59.36 # anyway. rockbox doesn't support reading the SMART data at present; i was writing a patch for it but it doesn't work yet 12.59.45 # and you can't read the smart data via usb either 12.59.59 # Torne: I know 13.00.01 # on the older ipods the builtin ROM diagnostic mode could display some of the smart data 13.00.09 # i don't know if the classic has anything like that 13.00.30 # but these disks don't have sata/ide right? 13.00.55 # most of them are just ATA disks 13.01.23 # iirc there's one model of classic that has a weird ce-ata interface 13.01.45 Quit dot (Quit: leaving) 13.01.50 # hmm 13.02.22 # it should be one of the latest 120gb models i think 13.03.18 Join dot [0] (~mgr@port-212-202-120-50.static.qsc.de) 13.04.30 # anyway thanks for the chkdsk idea, I will see what I can do. If that doesn't help, It was my fault to buy a faulty ipod 13.04.53 # the later ones are normal ata disks, to my understanding 13.05.01 # you can';t pluyg them directly into a pc because they use a weird connector 13.05.04 # but there are adapters :) 13.05.13 Quit mortalis (Read error: Connection reset by peer) 13.05.29 # oh 13.05.31 Join mortalis [0] (~kvirc@213.33.220.118) 13.05.34 # hmm 13.06.31 Quit petur (Quit: *plop*) 13.06.32 # Why there aren't 2.5" hdd players! 13.06.53 # because nobody wants them 13.07.07 # in fact barely anyone wants hdd playuers at all :) 13.07.16 # it's almost surprising anyone still bothers making them 13.08.07 # the thing is i like variaty 13.08.21 # well, unfortunately markets don't 13.09.40 # I mean with my music. My last Sandisk Clip had a 32GB card and only with opus ~96kbps, I was able to put a small part of my collection on it 13.10.19 # right, but the people who sell millions of mp3 players don't care how much music *you* have :) 13.10.53 # Yeah no wonder, everyone uses a streaming service nowadays 13.11.58 # Is there a player who can hold multiple storage cards? 13.13.50 Join Rower [0] (husvagn@v-413-alfarv-177.bitnet.nu) 13.19.57 # bebna: the iRiver AK100 13.20.05 # has two microsd slots 13.23.40 # thanks copper, but it doesn't look in the first check that it can use only 2x32GB cards and not 64gb ones to reach > 120GB, and the price isn't nice either 13.24.43 # bebna: "Can I use a 64GB micro SD card with the Astell & Kern AK100?" 13.24.55 # "Yes!" 13.24.59 # format as FAT32 13.25.05 # http://www.aloaudio.com/ak100 13.25.23 # it has a high output impedance though, 22Ω 13.28.27 # i can gat a 256gb zif ssd for my wrongly bought ipod for a third of this price and my mobile earplugs don't resolve more than roughly 256kbps mp3 13.28.52 # but how i said thanks 13.38.52 Quit Guest51073 (Read error: Connection reset by peer) 13.43.04 Quit Raptors (Read error: Connection reset by peer) 13.44.03 # <[Saint]> I think that manufactures don't actually expect you to take your *entire* audio collection with you. 13.44.15 # Apple does. 13.44.21 # <[Saint]> For many people, this would be impossible, even with 250GB+ drives. 13.44.36 # <[Saint]> I would need 8 iPods to do that. 13.45.00 # I'd like to know just how many people have lossy libraries that amount to 250 GB. 13.45.18 # <[Saint]> I think that it is expected that you'll take your favorite audio with you and freshen it as needed. 13.46.03 # <[Saint]> copper: my lossy stuff amounts to about 800GB 13.46.25 # 250 GB @ 256kbps is ~2300 hour long albums 13.46.44 # [Saint]: you're in a tiny, tiny minority 13.47.54 # I don't think so, my mixed mostly lossy collection is also around 750GB at the moment 13.48.08 # yes, that's a tiny, tiny minority 13.48.12 # :) 13.48.40 Join amayer [0] (~amayer@mail.weberadvertising.com) 13.49.45 # For the sake of this minority, even my mother would crack 500gb if she would digitilize her LPs, tapes and CDs 13.55.57 # <[Saint]> bebna: can you compile your own builds? 13.56.14 # <[Saint]> re: S.M.A.R.T data - you might want to look at http://gerrit.rockbox.org/r/#/c/385/ 13.56.35 # <[Saint]> description: g#385 13.56.37 # 3Gerrit review #385 at http://gerrit.rockbox.org/r/385 : iPod Classic/6G: reads HDD S.M.A.R.T. data by Cástor Muñoz (changes/85/385/1) 13.57.02 # would'nt help me, can't access debug menu anymore 13.57.25 # <[Saint]> huh?...why not? 13.57.33 # i cant get further than the bootlogo 13.57.52 # <[Saint]> not even with the fallback image? 13.58.09 # <[Saint]> emCORE Menu - Tools - Boot Rockbox Fallback image 13.58.18 # no, it only shows me in the debug image that it scans the disk 13.59.08 # <[Saint]> sounds like you might want to format the disk. 13.59.19 # <[Saint]> emCORE can do this also. 13.59.59 # emCore only shows a bar, which needs a hour to finish and after that it seems that the .rockbox folder is present afterwards 14.00.07 # even if it should'nt 14.02.30 # hmm 14.02.42 # doesn't have the iriver h10 also a zip hdd 14.02.52 # i got one of those somewhere 14.08.44 # [15:00:04] emCore only shows a bar, which needs a hour to finish and after that it seems that the .rockbox folder is present afterwards << you might want to ask TheSeven at #freemyipod-support about his hddscan2 emcore app, which can mark bad secotrs better than chkdsk 14.09.51 # <[Saint]> (but may take several days to complete) 14.10.48 # hmm, how do i get this on the ipod if i can't access it without rockbox? 14.11.35 # bebna: it's an emcore app - as long as emcore boots, it can be run 14.12.09 # emcore does boot, but did'nt i need to run rockbox for usb access? 14.12.36 # no, emcore also has an usb driver, but it does not use mass storage protocol, it uses its own one 14.12.38 # <[Saint]> not necessarily, no. 14.12.51 # and there are pc-side tools, that can upload code and run it on the ipod 14.13.14 # oh 14.13.17 # thankyou 14.15.58 # I just found a log from 2011-11.21, with a conversation of this hddscan2 app and a download link who works 14.16.38 # will check it out tonight, at the moment I'm at work and can't access my ipod from here -,-* 14.16.42 # there's a similar log here: http://logs.freemyipod.org/%23freemyipod/2011-04/2011-04-01-%23freemyipod.log 14.17.00 # i got this one http://logs.freemyipod.org/%23freemyipod-support/2011-11/2011-11-21-%23freemyipod-support.log 14.17.24 # please be warned that running hddscan2 will completely trash all your ipod's hdd contents 14.17.26 # I also looked in the freemyipod.org wiki but it doesn't seem to got a page 14.17.45 # user890104: I never got to uploading any music to it 14.18.24 # no, there's no page yet, and the sourcecode isn't yet uploaded to the official svn repo (but it's available if someone wants to take a look) 14.18.34 # <[Saint]> user890104: I know we can't dual-boot, but, could we jump into diagmode? 14.18.46 # ok, then you can just go ahead and run it, but keep the ipod connected to power 14.18.50 # < [7]> you basically have three options: 1. toss it into the trash can, 2. replace the hdd, 3. use only emcore and rockbox, try hddscan2 and pray :) 14.19.01 # ^ that line hits me hard 14.19.10 # [Saint]: disk mode does not work for sure, haven't tried diagmode yet 14.19.33 # <[Saint]> I just thought that if we could jump into diagmode, SMART data would be accessible 14.19.42 # bebna: these are basicly the options you have now 14.20.08 # hddscan2 creates a file with bad blocks, which only emcore and rockbox can read 14.20.37 # once you restore to apple's os, this file would be lost, and even if you backup it, their os can't make use of it 14.21.51 # I only want to use rockbox with it, apple's os doesn't support opus 14.22.54 # <[Saint]> fwiw, Rockbox's opus support is only very basic - but the classic has enough guts to do the job. 14.23.20 # <[Saint]> there's a lot of room for optimization. 14.23.42 # The Sandisk Clip+ doesn't got a problem with it either, until it got stolen -.-* 14.24.08 # <[Saint]> The Clip didn't choke on higher bitrates? 14.25.51 # I tested it up too 256kbps i think, WPS was laggy with 256 yes, but sound was fine 14.25.51 # <[Saint]> Hum, interesting, it has progressed further than I thought. 14.25.51 # But I couldn't hear a difference >96kbps 14.26.08 # Try it out, but check your battery lifetime, it drains faster than with simpler codecs. 14.26.37 # <[Saint]> Oh, I'm aware of this. Which is why I'm not using it presently. 14.27.23 # <[Saint]> ...though batter life isn't really an issue on the CE-ATA CLassic, 850mA means roughly 50 hours playback. 14.27.27 # <[Saint]> *battery 14.27.41 # <[Saint]> (mp3@320CBR) 14.28.22 # o.0 pidgin thinks mp3@320CBR is a vaild email address 14.28.33 # not quite ;) 14.28.45 # it doesn't have a dot in it ;) 14.29.05 # <[Saint]> (mp3@320.CBR) 14.29.10 # <[Saint]> fixed! :) 14.29.42 # the thing is 14.30.21 # I couldn't differentiate between 96kbps and 128kbps opus, but i could differentiate 128kbps mp3 and 96kbps and opus 14.30.37 # with opus sounding better and wider 14.32.00 # And the author of opus says, V1.1 sounds better than V1.0, which I believe Rockbox has 14.32.48 # even if it is encoded with 1.1 and decoded with 1.0? 14.33.21 # don't know, doesn't used v1.1 yet 14.34.44 # the sound was played on the clip+ and with denon ah-c360 plugs 14.36.11 # i can recheck against some some neutral speakers 14.36.15 # if you like 14.37.01 Join Raptors [0] (~whoneedsa@216-58-33-203.cpe.distributel.net) 14.37.27 Join guset [0] (~4352b552@www.haxx.se) 14.37.27 Quit guset (Client Quit) 14.37.55 Join webguest31 [0] (~4352b552@www.haxx.se) 14.38.51 # Hi Torne, Thanks for rockbox support. Quick question regarding Big Disk support 14.39.52 # I have Gigabeat S and 240gb HD... 14.40.22 # Tried few times your instructions from thread: http://forums.rockbox.org/index.php?topic=28554.0 14.42.17 # with no luck... not in rockbox file explorer... but avalable partitions in rockbox debug info show correct number and sizes 14.42.40 # Any idea to enable 14.43.29 # * [Saint] assumes you've recompiled with multivolume support enabled? 14.43.40 # <[Saint]> I _think_ this is still required. 14.45.40 # Thansk... yes I updated system-target.h file as recommended and removed #define USBSTOR_READ_SECTORS_FILTER() ... block.. 14.46.12 *** Saving seen data "./dancer.seen" 14.46.39 # is the other partition actually formatted correctly? 14.46.39 Quit shamus (Read error: Connection reset by peer) 14.46.47 # can you access it and write to it via USB? 14.46.49 Join shamus [0] (~shmaus@ip-206-192-195-49.marylandheights.ip.cablemo.net) 14.47.32 # Linux sucessefully recognised all partitions and allow format empty space with fat32... Yes I also can write correctly... new partition is type ff... 14.48.06 # did you also apply the patch to rockbox to allow it to mount partitions of type ff? 14.48.19 # the patch linked in that thread isn't there any more 14.48.23 # so, i'm guessing you didn't ;) 14.48.32 # (the link to paste.debian.net) 14.48.33 # ups.. i guess no... 14.49.08 # you need to modify the code that reads the partition table in rockbox to think that 0xff is a valid FAT partition type 14.49.10 # the link seems dead http://paste.debian.net/125614/ 14.49.12 # yes 14.49.14 # that's what i just said :) 14.49.19 # that's why i guessed you hadn't applied it 14.49.54 # thanks... will try to searh the patch... 14.50.03 # it's a one line change 14.50.14 # you won't find tha tpatch anywhere i expect 14.50.21 # it wasn't by us, it was the author of that forum post 14.50.52 # <[Saint]> does multivolume "just work" now? Or does the target's config need HAVE_MULTIVOLUME added to it? 14.51.31 # webguest31: you need to add 0xff to the array fat_partition_types in firmware/common/disk.c 14.51.38 # around line 50 14.51.48 # as far as i remember that was all that was in that patch. 14.52.04 # got it... Much thanks!!! let me try.. 14.52.35 # we tried to make this unnecessary by having it probe all partitions regardless of type 14.52.49 # but unfortunately our FAT code is not careful enough about validating whether partitions are really FAT partitions or not 14.52.58 # and it resulted in some devices misdetecting their partition layout and becoming unusable :) 14.53.06 # we need to make fat_mount() more cautious ;) 14.53.49 # Git it! This is great job with rockbox as it is!! Much Thanks for support 14.54.43 # no problem. it would be nice if we got this to work "properly" at some point (i.e. without hacks0 14.55.07 # my idea was to write a plugin that creates the extra partition on the device for you 14.55.16 # such that you don't need the weird usb patches to make it from the host 14.56.01 # Perfect! Thanks 14.56.21 # well, i haven't gotten around to doing it however many years later 14.56.24 # so don't say thanks ;) 14.58.34 # <[Saint]> webguest31: you might want to check if you defined HAVE_MULTIVOLUME in your devices config .h file, I don't recall seeing that stated in the forum link above and as far as I'm aware this is necessary. 14.59.05 # <[Saint]> as far as I'm aware, without doing so, it still won't work even if you do the changes Torne listed 14.59.34 # [Saint]: we at least *discussed* turning multivolume on universally 14.59.38 # i'm not sure if we actually did 14.59.49 # <[Saint]> AHa...hum. 15.00.01 # there may have been some reason not to 15.00.07 # or maybe we didn't get around to it ;) 15.03.55 # #ifdef HAVE_MULTIVOLUME 15.03.55 # #define NUM_VOLUMES_PER_DRIVE 4 15.03.59 # Saint... thanks for headsup.. i checked config.h and it seems that 15.04.20 # HAVE_MULTIVOLUME is there with above clouse.. 15.05.44 # <[Saint]> ok, then just add "#define HAVE_MULTIVOLUME" in there. 15.05.56 # <[Saint]> but, I'm sure you're aware of this if you've gotten this far. 15.10.18 # Thanks Saint... It seems below clouse there.. hope it will work: 15.10.20 # #if defined(HAVE_MULTIDRIVE) && !defined(HAVE_MULTIVOLUME) 15.10.20 # #define HAVE_MULTIVOLUME 15.10.20 # #endif 15.12.28 # <[Saint]> that seems like an odd way to do it... 15.12.51 # webguest31: no, that's not relevant 15.12.58 # that says that things which are multidrive must also be multivolume 15.13.24 # you need to add #define HAVE_MULTIVOLUME to the gigabeat S's config file 15.14.15 # <[Saint]> firmware/export/config/your_device.h 15.15.36 # got it... checking... 15.18.29 # Great... updated gigabeats.h with #define MULTIVOLUME... will try new buld... Much Thanks... 15.19.08 # <[Saint]> Hum - we could /probably/ make a plugin that did all this for you I think. 15.19.15 Quit fs-bluebot (Ping timeout: 258 seconds) 15.19.16 # <[Saint]> But, meh...it smacks of effort. 15.19.33 # [Saint]: the partitioning can be done by a plugin, which avoids the need to patch the USB code 15.19.41 # and we could enable multivolume on the Beast by default 15.19.44 # or on all targets maybe 15.19.45 # * [Saint] nods 15.19.51 # you';d still need a host to actually format the second partition 15.19.59 # <[Saint]> Aha - good point. 15.20.11 # as i doubt we want to get into writing mkdosfs 15.20.13 # because yuck 15.20.28 # but that's fine, formatting a volume is easy for users 15.20.37 # the only remaining thing would be allowing partition type ff as a valid type 15.20.49 # which we could do, again, but because fat_mount is a bit wonky that might cause weird effects on some people's players 15.21.05 # making fat_mount more careful to verify that the filesystem is actually plausible before mounting it would be nice :) 15.22.07 # <[Saint]> Hum - did I break something, or has the USB screen never actually notified the user when it is safe to disconnect? 15.22.19 # <[Saint]> My recollection is failing me. 15.22.26 # our handling of eject is really wonky and "broke" a while back 15.22.27 # for some value of broke 15.22.36 # there's more than one way that the host can signal to the device that it's no longer in use 15.22.45 # depending if the host thinks the device is removable or not 15.22.48 # and on what OS you use 15.22.53 # and rockbox doesn't treat them all equally 15.22.55 # <[Saint]> Aha - so it *did* make some form of notification, or am I imagining this? 15.23.05 # for me it used to just exit usb mode 15.23.06 # no notification 15.23.12 # it would just go back to the main menu, still charging 15.23.17 # when i ejected it in windows. 15.23.17 # <[Saint]> Aha, right. 15.23.23 Join fs-bluebot [0] (~fs-bluebo@g224239007.adsl.alicedsl.de) 15.23.30 # but at some point either rockbox changed or i switched to a different version of windows and then it stopped :) 15.23.39 # <[Saint]> Now it just sticks in the USB screen. 15.23.46 # from talking to people about this before it's nontrivial to work out 15.24.24 # <[Saint]> That's fine, I was more concerned with whether or not I was imagining different behavior or not. 15.24.46 # <[Saint]> errr...but worded more goodlier. 15.25.20 # this was, like, years ago though :) 15.30.51 # hmm, did I checked it just wrong, or isn't there anywhere in the metadata fields the possibility to set tags? 15.35.44 Quit Mathnerd314 (Read error: Connection reset by peer) 15.36.32 # * [Saint] is unsure of the question but takes a guess. 15.36.44 # <[Saint]> "No, you cannot edit metadata from within Rockbox at all" 15.37.20 # no no no 15.37.28 # i mean tags like categories 15.37.36 # huh? 15.38.24 Join Mathnerd314 [0] (~quassel@palevsky-223-221.rh.uchicago.edu) 15.38.37 # * [Saint] is lost 15.39.15 # i hate english 15.39.24 # bebna: we only parse the traditional id3 tags from the metadata, like genre 15.39.29 # and we dont' support multivalue fields 15.39.38 # the database doesn't support arbitrary columns 15.40.00 # OSS, one can change that ;-) 15.40.07 # so, unless you modify the database code there's no way for it to index anything other than artist/album/track/genre 15.40.07 # the thing is 15.40.25 # the thing is the database code is horrible and nobody understands it and most of the developers don't use it anyway 15.40.30 # i thought about sorting my music with tags 15.40.32 # so nobody has made the database smarter for a long time :) 15.40.44 # tags like "electro, happy, fast" 15.41.08 # right. so yeah, you can't do that. the only relevant field we support is genre and we treat it as a single string 15.41.10 # <[Saint]> use the "comment" field. 15.41.16 # oh, hm 15.41.20 # yeah, we do index comment actually 15.41.26 # <[Saint]> that's as good as you'll get. 15.41.26 # but it's not very useful 15.41.35 # you can do substring seraches on it by making a custom tag index thingy 15.41.43 # but you can't really just browse it by tag if they have multiple values 15.41.46 # yeah, but other apps don't seem to use it either, because it isn't in the standards 15.42.03 # bebna: the id3v2 standard does actually have fields for these things, and does specify how to encode multiple values 15.42.06 # :) 15.42.15 # virtually all music playing programs get it wrong or ignore it 15.42.18 # how did i miss it? 15.42.59 # i tested this a while ago when retagging all my music and while Picard can *write* multivalue tags in multiple stnadard or nonstandard formats virtually nothing reads them correctly/at all 15.43.18 # so it's probably hopeless :) 15.43.25 # even if you fixed rockbox to support it, nothing else will be compatible :) 15.43.51 # there isn't a proper music manager anyways 15.44.18 # rockbox needs it's own itunes! *ambitions* 15.44.24 # <[Saint]> Picard is probably the least broken of a large bunch. 15.44.40 # <[Saint]> "its own iTunes" is the last thing Rockbox needs :) 15.45.13 # <[Saint]> The fact that you specifically don't need any management software is one of the huge benefits of Rockbox. 15.45.28 # y7eah, i "Manage" my music with rsync 15.45.31 # :) 15.46.21 # but yeah, all text frames in id3 are allowed to contain multiple strings, which are stored as a null separated list (i.e. a byte that's just zero, in most encodings) 15.46.39 # i have yet to find a single program other than picard that understands the null separated format 15.46.46 # some programs support semicolon-separated lists, which is wrong 15.46.58 # or comma-separated, which is also wrong (and conflicts with existing usage of commas for otehr purposes) 15.47.32 # most programs will either just use the first value and truncate it after the null because they are using C string functions that think that's the end of the string, or end up concatenating them all togetherwith garbage characters or question marks or something in the place of the nulls 15.47.36 # <[Saint]> Indeedy. 15.47.37 # whcih si even less useful ;) 15.47.45 # null seperated values often crash with null terminated strings, ... 15.47.53 # no 15.47.57 # <[Saint]> I should be able to do "Cure, The" etc. without things thinking it is two seperate tags. 15.47.58 # crashing is not involved. 15.48.10 # [Saint]: yah, well, programs tend to apply this logic selectively to certain fields 15.48.19 # which is also wrong, as the spec says it applies to *all* text frames 15.48.36 # e.g. you could have a multivalue artist tag ;) 15.48.45 # so yeah 15.48.48 # this shit doesn't work 15.49.10 # at all, unless you always use the same program to access your music, and that program happens to impelemnt it in a certain way that you can use. 15.49.14 # it's just notn portable 15.49.16 # i gave up :) 15.49.30 # i would be interested in adding support to rockbox *if* it actually worked in other things 15.49.34 # but, it doesn't, so fuck it 15.49.43 # <[Saint]> Fair enough. :) 15.49.50 # so symlinks for the rescue? 15.49.56 # you can't symlink files on FAT 15.50.04 # <[Saint]> errr...FAT 15.50.05 # and rockbox only supports FAT 15.50.07 # <[Saint]> no symlinks 15.50.08 # so, no. 15.50.09 # ... i forgot 15.50.55 # i just the checked id3v2.4.0 frames, there is nothing for tags to be found 15.51.46 # that's because it doesn't have one called "tags" 15.51.52 # it has, instead, like, 20 different more specific text fields 15.51.56 # like mood and so on :) 15.53.05 # the plugin i use for picard to populate this data sets grouping, genre, mood, decade, occasion, category, and some others too :) 15.53.09 # i didn't check for mood, i searched for everything that would resamble some user defined identifiers 15.53.22 # Right, there are literally dozens of fields for user defined identifiers 15.53.30 # for different purposes 15.53.34 # and also several generic ones as well :) 15.54.06 Quit Zagor (Quit: Clint excited) 15.54.37 # also, there are others not actually in the spec that are still de facto stadnards like occasion :) 15.54.57 # again, programs use this stuff all completely weirdly and inconsistently 15.55.15 # so, unless you intend to use it with one specific piece of software (in which case you just do whatever it supports) you are basically screwed 15.58.15 # hmm, vorbis allows using a tag like genre multiple types 15.58.19 # Torne / Saint ... as follow up on Big Disk for gigabeat S... All is working great after rebuld with recomended changes! Much Thanks!! 15.58.24 # Can I access ff partition in Win7 it seems that only main 128GB is visable... Linux mounts all partitions well 15.58.46 # webguest31: windows shouldn't care waht the partition type is either 15.58.50 # well, hm 15.58.54 # it might not like ff, though 15.59.16 # there was originally another suggestion (which i don't recall if anyone actually implemented) to patch the partition table on read over USB to say it was the normal type 15.59.33 # windows doesn't mind if the partition type is wrong, but 0xff is supposed to mean "empty" so it may well ignore it 15.59.37 # :) 15.59.49 # bebna: indeed, but again, programs don't handelt his consistenlty 15.59.55 # webguest31: can you see the the partition in "disk managment"? 16.00.09 # bebna: also, as a bonus, some programs seemt o handle repeated vorbis comments by letting them overwrite each other such that the value you see is the *last8 one, not the first one 16.00.12 Quit kevku (Ping timeout: 264 seconds) 16.00.14 # which is even less useful 16.00.19 # yes it is in manager... but not allow leter change... 16.00.36 # webguest31: you probably need to have rockbox patch the MBR when it's read over USB, then 16.00.43 # ^ 16.00.52 # no idea if the previous guy did that or not 16.00.54 # maybe he didn't care ;) 16.01.06 # Got it! Much Thanks!! 16.01.46 # the usb_fix_mbr code already fakes the mbr, but those instructions disbled that (necessary to allow modifying the patition table over usb) 16.02.07 # if you put the USB code back to the original state where it doesn't allow writing to the MBR and patches it, you can extend usb_fix_mbr to also do this rewriting 16.02.19 # you don't need those usb patches now you partitioned it once :) 16.02.33 Quit mortalis (Quit: KVIrc 4.1.3 Equilibrium http://www.kvirc.net/) 16.03.26 # I envy you webguest31, your disk is working! hf 16.03.36 Join pretty_function [0] (~sigBART@123.252.212.194) 16.28.13 # Torne, I put USB code in original state and now trying to extend usb_fix_mbr. In my case it is usb-gigabeat-s.c. I wonder if extend usb_fix_mbr meens to swap first and 3rd partitions 16.28.17 # /* Swap second and third partitions */ 16.28.17 # memcpy(tmp, &p[0x10], 16); 16.28.17 # memcpy(&p[0x10], &p[0x20], 16); 16.28.17 DBUG Enqueued KICK webguest31 16.28.17 # memcpy(&p[0x20], tmp, 16); 16.28.37 # i forget :) 16.35.18 # Thanks ;) I winder if below from usb-gigabeat-s.c describes Win limitation... or I can force to mount 2 partitions 16.35.20 # Windows ignores the partition flags and mounts the first partition it 16.35.20 # sees when the device reports itself as removable 16.35.29 Quit pamaury (Ping timeout: 264 seconds) 16.37.42 # Oh, right, yes 16.37.44 # that :) 16.37.48 # Yeah, you are probably running into that ;) 16.37.57 # so the partition type is prbably not the problem 16.39.35 # Much Thanks! 16.39.49 Quit webguest31 (Quit: CGI:IRC) 16.40.28 Join froggyman [0] (~me@dhcp-155-92-103-232.nebula.msoe.edu) 16.40.28 Quit froggyman (Changing host) 16.40.28 Join froggyman [0] (~me@unaffiliated/froggyman) 16.46.15 *** Saving seen data "./dancer.seen" 16.52.33 Join n1s [0] (~n1s@rockbox/developer/n1s) 17.02.08 Join kevku [0] (~kevku@2001:470:27:773:0:feed:c0f:fee) 17.07.13 Part LinusN 17.08.54 Join krabador [0] (~krabador@host206-183-dynamic.19-79-r.retail.telecomitalia.it) 17.09.55 Quit digbaddy (Quit: digbaddy) 17.13.31 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 17.14.16 Nick GeekShad1w is now known as GeekShadow (~antoine@nzf.turmel.info) 17.14.28 Quit GeekShadow (Changing host) 17.14.28 Join GeekShadow [0] (~antoine@reactos/tester/GeekShadow) 17.19.28 Quit pretty_function (Remote host closed the connection) 17.35.28 Join djp_ [0] (~user@fsf/member/djp-) 17.53.33 Quit froggyman (Ping timeout: 246 seconds) 17.57.50 Join froggyman [0] (~me@msoe-00033403.nebula.msoe.edu) 17.57.51 Quit froggyman (Changing host) 17.57.51 Join froggyman [0] (~me@unaffiliated/froggyman) 17.59.35 Quit froggyman (Read error: Connection reset by peer) 18.06.46 Join bertrik [0] (~quassel@rockbox/developer/bertrik) 18.07.36 Join lebellium [0] (~chatzilla@lns-c10k-ld-02-m-212-194-176-149.dsl.sta.abo.bbox.fr) 18.07.55 Join mortalis [0] (~mortalis@77.108.98.176) 18.30.48 Quit einhirn (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 18.31.50 Quit kevku (Quit: KVIrc 4.3.1 Aria http://www.kvirc.net/) 18.35.21 Join Strife89 [0] (~Strife89@2602:306:250d:8809:225:d3ff:fed6:15a) 18.35.49 Join pretty_function [0] (~sigBART@123.252.212.194) 18.38.41 Join kevku [0] (~kevku@2001:470:27:773:0:feed:c0f:fee) 18.46.17 *** Saving seen data "./dancer.seen" 18.47.22 Join Ward [0] (~Mirandaha@bpb01-1-88-162-4-186.fbx.proxad.net) 18.47.46 Nick Ward is now known as Guest37545 (~Mirandaha@bpb01-1-88-162-4-186.fbx.proxad.net) 18.50.37 Quit Mathnerd314 (Read error: Connection reset by peer) 18.51.35 Join Mathnerd314 [0] (~quassel@palevsky-223-221.rh.uchicago.edu) 19.08.37 Join jhMikeS [0] (~jethead71@50.4.240.19) 19.08.37 Quit jhMikeS (Changing host) 19.08.37 Join jhMikeS [0] (~jethead71@rockbox/developer/jhMikeS) 19.17.50 Quit dfkt_ (Quit: -= SysReset 2.55=- Sic gorgiamus allos subjectatos nunc.) 19.20.10 Join melmothX [0] (~melmoth@unaffiliated/melmothx) 19.35.09 Quit bebna (Quit: Leaving.) 19.43.29 Quit mortalis (Quit: KVIrc 4.3.1 Aria http://www.kvirc.net/) 19.48.13 Join robin0800 [0] (~robin0800@cpc1-brig15-2-0-cust755.3-3.cable.virginmedia.com) 19.58.37 Quit robin0800 (Remote host closed the connection) 19.59.03 Join robin0800 [0] (~robin0800@cpc1-brig15-2-0-cust755.3-3.cable.virginmedia.com) 20.00.12 Join dfkt [0] (dfkt@unaffiliated/dfkt) 20.02.54 Quit onyxice (Ping timeout: 258 seconds) 20.11.30 Quit Strife89 (Quit: Vamoose.) 20.14.08 Join froggyman [0] (~me@dhcp-155-92-103-232.nebula.msoe.edu) 20.14.08 Quit froggyman (Changing host) 20.14.08 Join froggyman [0] (~me@unaffiliated/froggyman) 20.30.34 Join crose [0] (~John@116-66-190-109.dsl.ovh.fr) 20.37.07 Quit pretty_function (Remote host closed the connection) 20.39.12 Quit melmothX (Quit: bau) 20.46.21 *** Saving seen data "./dancer.seen" 20.51.41 Quit froggyman (Ping timeout: 264 seconds) 20.55.46 Join froggyman [0] (~me@msoe-00033403.nebula.msoe.edu) 20.55.46 Quit froggyman (Changing host) 20.55.46 Join froggyman [0] (~me@unaffiliated/froggyman) 21.05.43 Quit froggyman (Ping timeout: 272 seconds) 21.18.46 Quit akaWolf (Ping timeout: 256 seconds) 21.18.47 Quit kevku (Ping timeout: 264 seconds) 21.25.28 Quit DexterLB (Read error: Connection reset by peer) 21.30.44 Quit Guest37545 (Ping timeout: 276 seconds) 21.30.45 Join froggyman [0] (~me@unaffiliated/froggyman) 21.30.48 Join DexterLB [0] (~dex@95.43.105.211) 21.38.51 Quit [Saint] (Remote host closed the connection) 21.40.08 Join [Saint] [0] (~saint@rockbox/user/saint) 21.54.52 Quit froggyman (Ping timeout: 252 seconds) 22.21.59 Join randomdent [0] (~b891f8d3@www.haxx.se) 22.21.59 # Hello? 22.23.29 # <[Saint]> Yes? 22.23.42 # <[Saint]> No need to ask to ask, just ask your question. 22.24.03 # haha great thanks. my device is an iRiver E300 22.24.40 # <[Saint]> I suppose this is a "does Rockbox run on my...XXXXXXXXX?" question? 22.24.56 Quit dv_ (Read error: Connection reset by peer) 22.25.07 # more like what i have to do to make any kind of rockbox work? 22.25.44 # <[Saint]> https://www.google.co.nz/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&ved=0CDAQFjAA&url=http%3A%2F%2Fwww.rockbox.org%2Fwiki%2FNewPort&ei=S4ZHUYD7FYfsiAf9uYG4Cw&usg=AFQjCNHRBxqFZOb66Jp_1MhOVTiiD3h49w&bvm=bv.43828540,d.aGc 22.25.47 # because at the moment rockbox is not fitted for my player 22.25.49 # <[Saint]> blargh! 22.25.54 # <[Saint]> silly Google... 22.26.03 # <[Saint]> http://www.rockbox.org/wiki/NewPort 22.26.17 # i got the page, thanks 22.28.02 # ok, so i got to this page 22.28.03 # http://www.rockbox.org/wiki/IriverEseries 22.28.10 # what do i do with the code? 22.28.26 Join dv_ [0] (~quassel@chello080108009040.14.11.vie.surfer.at) 22.29.20 # <[Saint]> At this stage - nothing at all. 22.29.47 Quit kadoban (Read error: Operation timed out) 22.31.56 # oh, ok. is it worth trying to install the rockbox firmware that is intended for a different device? 22.32.21 # <[Saint]> No - don't ever do that. 22.32.39 # is that risky? That just won't work, will it? :) 22.32.59 # <[Saint]> Potentially both, definitely the latter. 22.33.42 # ahh man. and i dont know how to code.. i'll have to keep an eye on it if someone gets up to it 22.33.49 # <[Saint]> The small saving grace for you in that the SoC is known, and the supported E series targets use it - but you'll still need to find out about any additional HW that may be shared or has changed. 22.34.32 # <[Saint]> Following the steps listed in the newports wiki page linked above is generally considered a bare minimum effort. 22.34.35 # well if you can't code at all, don't expect anything unless there is a dev with this device willing to port RB to it 22.35.23 # <[Saint]> It pays to assume that the only person interested in said new port, is you, and that no one will help you - and be pleasantly surprised if/when other developers/users step in. 22.35.55 # nope, cant code at all. i'd be willing to do something though if theres anything i can do 22.35.56 # <[Saint]> The newports page is blunt, and it seems harsh - but its true. 22.36.16 # <[Saint]> a new port can potentially be many hundreds of man hours. 22.37.33 # wow.. i'll have to stick with custom then 22.37.41 # <[Saint]> start a new device page, get scans, identify components...just, follow the steps listed in newports. 22.37.50 Quit jhMikeS (Ping timeout: 240 seconds) 22.37.53 # <[Saint]> every bit helps. 22.38.11 # if the soc is unsuppported, yeah it can be hundreds of man hours (mind the s after hundred), but ifwe already have support for the soc, it might be far less 22.38.16 # <[Saint]> Even if someone picks up on your work years from now, every bit helps. 22.38.41 # can i break the player if i open it? 22.38.44 Ctcp Ignored 1 channel CTCP requests in 0 seconds at the last flood 22.38.44 # * [Saint] is willing to bet that there's at least some hardware reused in addition to the SoC 22.38.53 # <[Saint]> randomdent: Oh, yes, certainly. 22.39.18 # [Saint]: It's hard to convince a new user that working for people in several years or never is not a waste of time :) 22.39.27 # what is the soc in iriver e300 ? 22.39.38 # http://www.rockbox.org/wiki/IriverEseries 22.39.48 # <[Saint]> ATJ213x 22.39.52 # <[Saint]> iirc 22.39.56 # <[Saint]> Aha, yep. 22.40.04 # well i'd rather not break it to be honest, i have nothing to replace it at all.. and i need my music :D 22.40.22 # wodz is working on the atj soc currently 22.40.44 # <[Saint]> You probably won't. But you asked if you could, and that is certainly possible. 22.40.59 # <[Saint]> just don't go poking at the sparkly bits with pointy things :) 22.41.37 # that seems logical 22.41.39 # when wodz is online, you should ask him, he knows thingds about this soc, he can better evaluate the work 22.42.26 Quit amayer (Ping timeout: 260 seconds) 22.43.30 # <[Saint]> the construction seems very similar to the E100/150 22.44.03 # <[Saint]> in which case the required tool for opening said device is a spudger/guitar pick and a phillipshead 00 22.44.26 Quit n1s (Quit: Ex-Chat) 22.44.57 Join wodz [0] (~wodz@ayq146.neoplus.adsl.tpnet.pl) 22.45.08 # <[Saint]> good timing, sir. 22.45.09 Join kadoban [0] (~kadoban@ip98-165-177-158.ph.ph.cox.net) 22.45.14 # e100/e200/e300 are very similar 22.46.01 # I tend to think it is pure marketing voodoo and players are actually the same (minus aestetic minor differences) 22.46.22 *** Saving seen data "./dancer.seen" 22.46.33 # e200 is a bit more different due to different controls but for sure is based on the same reference design 22.46.52 # sounds great 22.47.12 # <[Saint]> the 200 had diagonals on the dpad, no? 22.47.24 # * [Saint] used to own one, many moons ago. 22.47.26 # i'd open my e300 if theres someone that can help me from there.. or at least someone that continues the project. that i dont risk it for nothing :) 22.47.31 # <[Saint]> ...not that long ago really. :) 22.48.14 # well I have e150 only, pictures of e300 internals could be usefull 22.48.34 # <[Saint]> randomdent: that's the thing, for instance, a developer could pick it up - and then get hit by a bus. You never know. 22.48.36 # wodz: i've made some progress on the rknano :) 22.48.50 # BUT it is really hard to open if you don't know how to start 22.48.53 # and nothing happens with it when i scan it? 22.48.54 # <[Saint]> The information is always useful, but there can't ever be any guarantees on whether or not it will be used. 22.49.05 # pamaury: yeah, saw in logs 22.49.09 # well i'd unscrew the two little screws and use a thin pick 22.49.35 # <[Saint]> No, a scanner can't harm the device. 22.49.46 # <[Saint]> A nice digital camera can do the trick also. 22.50.07 # pamaury: the lack of upload limit is most probably due to bigger iram 22.50.25 # pamaury: maybe this rknano has iram only 22.50.35 # probably 22.50.56 # alright, ill see when i get to it, and ill come back then :) 22.52.21 Quit kadoban (Read error: Connection reset by peer) 22.52.38 Join kadoban [0] (~kadoban@ip98-165-177-158.ph.ph.cox.net) 23.07.52 # "hard" adfu mode of atj213x doesn't seem to accept 'read memory' command. It accepts something which I think is 'write memory' and 'execute'. I need to craft some smart code to proof this. 23.09.42 Join morksoldat [0] (~morksolda@pc-172-210-86-200.cm.vtr.net) 23.10.58 Join stripwax [0] (~Miranda@rockbox/developer/stripwax) 23.20.35 # wodz: I still suspect the AMS "bricked" mode to do something similar 23.21.06 # bertrik: there's no DFU usb device though, only UMS? 23.21.58 # wait, we're gonna support both sansa e200 and iriver e200 at some point? 23.22.08 # funman: yes, could it be that writing to the USB device actually writes to RAM? but I don't know of any "execute" command 23.22.39 # bertrik: a block device mapped to RAM would be weird (but well we've seen weird things anyway) 23.22.54 # the UMS device data did seem to be persistent, but not across shutdowns 23.23.23 # bertrik: get some liquid nitrogen and try cold boot attack :) 23.24.14 # JdGordon: ping FS#12639 23.24.16 # http://www.rockbox.org/tracker/task/12639 3Certain themes cause the WPS to not load properly and USB to not work (bugs, unconfirmed) 23.25.21 # funman: I've seen recognisable greyscale images from DRAM that wasn't refreshed for a minute or so 23.26.48 Quit randomdent (Quit: CGI:IRC) 23.32.03 # funman: maybe in far future we will support both sansa e200 and iriver e200 - this will be support nightmare 23.32.11 Quit ender| (Ping timeout: 256 seconds) 23.34.26 # funman: maybe ums with vendor scsi or buggy ums (i've sen this) ? 23.34.48 # or onlyworks in full-speed mode ? 23.34.53 Join ender| [0] (whatever@2a01:260:4094:1:42:42:42:42) 23.38.48 Quit wodz (Quit: Leaving) 23.41.15 Quit crose (Quit: Leaving) 23.41.43 Join ikeboy [0] (~435622d3@www.haxx.se) 23.42.55 Join jhMikeS [0] (~jethead71@50.4.240.19) 23.42.55 Quit jhMikeS (Changing host) 23.42.55 Join jhMikeS [0] (~jethead71@rockbox/developer/jhMikeS) 23.43.23 # What rockbox supported model is the fastest? 23.43.54 # fastest in what? they all play music the same :) 23.44.27 # http://www.rockbox.org/wiki/CodecPerformanceComparison might be helpful 23.45.15 # lebellium: that's a bit confusing. Yes, they all play a 10 minute track in 10 minutes, but no, they can't all decode the more CPU-intensive codecs 23.46.41 # except for the newly supported Opus codec, are there differences for the user between the various targets ? 23.47.12 # Sure. See http://www.rockbox.org/wiki/SoundCodecMonkeysAudio for an extreme case 23.48.49 # funman: hehe, keep trying :) 23.49.03 # JdGordon: i'll have no rest :) 23.49.36 # funman: I'm with you. 23.50.10 # I have 10 or more rockboxed devices and USB doesn't work on any of them with my theme... pfiouu :'( 23.50.52 # gevaerts: thank you, I did not know about that 23.51.23 # which have the most RAM and CPU speed? 23.52.21 # I have the sansa fuze plus but wanted to know if there were other models that rockbox will work with that are faster 23.53.05 # ikeboy: the toshiba gigabeat S is the fastest "traditional" (i.e. not android or something like that) target 23.53.14 # YP-R0 has a IMX37 532Mhz too 23.53.26 # but it's RaaA 23.53.28 # That one might be close to the gigabeat then 23.53.54 # The gigabeat S is unfortunately not easy to install 23.54.17 # lebellium: ping Jd until he takes a look at this valgrind trace! 23.54.43 # I don't want him to hate me :D 23.55.39 # I think the gigabeat is not in production anymore 23.55.54 # It isn't, YP-R0 either 23.56.02 # neither* 23.56.17 # you did not mention it has to be in production 23.56.21 # Why do you care about CPU speed and RAM? 23.57.41 Join amayer [0] (~amayer@72.25.61.20) 23.58.10 Quit amayer (Client Quit) 23.58.19 Join amayer [0] (~amayer@72.25.61.20)