--- Log for 29.12.114 Server: tepper.freenode.net Channel: #rockbox --- Nick: logbot- Version: Dancer V4.16 Started: 8 days and 11 hours ago 00.14.31 Quit cmhobbs (Remote host closed the connection) 00.16.22 Quit ZincAlloy (Quit: Leaving.) 00.30.57 Quit lorenzo92 (Ping timeout: 258 seconds) 00.34.23 Quit ender` (Quit: If man could be crossed with the cat it would improve man, but it would deteriorate the cat. -- Mark Twain) 00.35.25 Join JdGordon_ [0] (~jonno@rockbox/developer/JdGordon) 00.36.28 Quit JdGordon (Ping timeout: 245 seconds) 00.36.52 Quit lebellium (Quit: ChatZilla 0.9.91.1 [Firefox 35.0/20141218174327]) 00.46.12 *** Saving seen data "./dancer.seen" 00.54.52 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 01.23.34 Quit [Franklin] (Remote host closed the connection) 01.23.52 Join [Franklin] [0] (~franklin@cpe-071-071-039-006.triad.res.rr.com) 01.34.04 Join Strife89 [0] (~Strife89@adsl-98-80-221-247.mcn.bellsouth.net) 01.49.23 Quit bertrik (Ping timeout: 245 seconds) 02.18.17 Quit pamaury (Ping timeout: 258 seconds) 02.30.34 Join Strife1989 [0] (~Strife89@adsl-98-80-221-247.mcn.bellsouth.net) 02.31.04 Quit Strife89 (Quit: Vamoose.) 02.37.55 Quit derf (Ping timeout: 240 seconds) 02.40.03 Join derf [0] (~derf@static-108-18-126-14.washdc.fios.verizon.net) 02.46.14 *** Saving seen data "./dancer.seen" 02.57.44 Join Riviera [0] (Riviera@2a03:b0c0:1:d0::10:b001) 03.22.44 Quit RiD (Quit: A good plan today is better than a perfect plan tomorrow.) 03.28.09 Quit krabador (Quit: Take the time.) 03.40.42 Quit kugel_ (Ping timeout: 244 seconds) 03.41.22 Join kugel [0] (~kugel@ip5b42e323.dynamic.kabel-deutschland.de) 03.41.23 Quit kugel (Changing host) 03.41.23 Join kugel [0] (~kugel@rockbox/developer/kugel) 04.25.04 Join ungali [0] (~ungali@unaffiliated/ungali) 04.36.52 Quit [Franklin] (Ping timeout: 240 seconds) 04.46.16 *** Saving seen data "./dancer.seen" 05.47.20 Join bp0 [0] (~bp@unaffiliated/bp0) 05.59.24 Quit bp0 (Quit: Leaving) 06.15.44 Join rela [0] (~x@pdpc/supporter/active/rela) 06.20.28 Quit rela (Ping timeout: 265 seconds) 06.32.17 Join rela [0] (~x@pdpc/supporter/active/rela) 06.32.52 Quit Strife1989 (Ping timeout: 240 seconds) 06.36.54 Quit rela (Ping timeout: 265 seconds) 06.46.17 *** Saving seen data "./dancer.seen" 06.48.19 Join rela [0] (~x@pdpc/supporter/active/rela) 06.53.20 Quit rela (Ping timeout: 265 seconds) 07.20.46 Join rela [0] (~x@pdpc/supporter/active/rela) 07.25.43 Quit rela (Ping timeout: 265 seconds) 07.37.01 Join rela [0] (~x@pdpc/supporter/active/rela) 07.41.40 Quit rela (Ping timeout: 265 seconds) 07.53.11 Join rela [0] (~x@pdpc/supporter/active/rela) 07.56.28 Quit Provel (Read error: Connection reset by peer) 07.57.30 Quit rela (Ping timeout: 244 seconds) 07.57.49 Join ploco [0] (dce9b7f9@gateway/web/freenode/ip.220.233.183.249) 08.25.35 Join rela [0] (~x@pdpc/supporter/active/rela) 08.30.48 Quit rela (Ping timeout: 272 seconds) 08.40.36 Join ender` [0] (krneki@foo.eternallybored.org) 08.41.45 Quit ungali (Quit: ungali) 08.41.48 Join rela [0] (~x@pdpc/supporter/active/rela) 08.46.04 Quit rela (Ping timeout: 244 seconds) 08.46.21 *** Saving seen data "./dancer.seen" 08.57.52 Join bzed_ [0] (~bzed@devel.recluse.de) 09.00.16 Quit Galois (Ping timeout: 252 seconds) 09.00.16 Quit __jae__ (Ping timeout: 252 seconds) 09.00.16 Quit Scall (Ping timeout: 252 seconds) 09.00.16 Quit krnlyng_ (Ping timeout: 252 seconds) 09.00.17 Quit bzed (Ping timeout: 252 seconds) 09.00.17 Quit the-kyle (Ping timeout: 252 seconds) 09.00.17 Quit n17ikh_ (Ping timeout: 252 seconds) 09.00.20 Nick bzed_ is now known as bzed (~bzed@devel.recluse.de) 09.00.29 Join __jae__ [0] (~jae@dedicated.jaerhard.com) 09.00.48 Join n17ikh [0] (~n17ikh@unaffiliated/n17ikh) 09.01.22 Quit zu (Ping timeout: 252 seconds) 09.01.44 Quit maraz (Ping timeout: 252 seconds) 09.01.51 Join maraz [0] (maraz@kapsi.fi) 09.01.57 Join mikroflops_ [0] (~yogurt@178.174.137.62) 09.02.55 Quit mikroflops (Read error: Connection reset by peer) 09.02.58 Join zu [0] (~zu@ks387228.kimsufi.com) 09.03.53 Join krnlyng_ [0] (~liar@83.175.90.24) 09.05.02 Join the-kyle [0] (~kyle@kyle.tk) 09.10.40 Join Scall [0] (~chat@unaffiliated/scall) 09.14.15 Join rela [0] (~x@p2003006684120F002808C2AC227127CA.dip0.t-ipconnect.de) 09.14.27 Quit rela (Changing host) 09.14.27 Join rela [0] (~x@pdpc/supporter/active/rela) 09.18.37 Quit rela (Ping timeout: 244 seconds) 09.19.42 Quit mikroflops_ (Ping timeout: 252 seconds) 09.21.30 Join mikroflops [0] (~yogurt@178.174.137.62) 09.25.48 Join thomasjfox [0] (~tomj@rockbox/developer/thomasjfox) 09.30.27 Join rela [0] (~x@pdpc/supporter/active/rela) 09.34.00 Quit dfkt (Read error: Connection reset by peer) 09.34.33 Join dfkt [0] (dfkt@unaffiliated/dfkt) 09.35.24 Quit rela (Ping timeout: 272 seconds) 09.43.28 Quit dfkt (Ping timeout: 256 seconds) 10.26.03 Quit thomasjfox () 10.29.54 Join bertrik [0] (~quassel@rockbox/developer/bertrik) 10.42.22 Join thomasjfox [0] (~tomj@rockbox/developer/thomasjfox) 10.46.25 *** Saving seen data "./dancer.seen" 10.55.29 Quit syon__ (Ping timeout: 265 seconds) 11.17.23 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 11.25.23 Join Misanthropos [0] (~Misanthro@frnk-5f743194.pool.mediaWays.net) 11.29.34 Join einhirn [0] (~Miranda@p4FC122C5.dip0.t-ipconnect.de) 11.30.33 Join lebellium [0] (~chatzilla@i16-les01-ntr-212-194-176-149.sfr.lns.abo.bbox.fr) 11.33.35 Quit einhirn (Ping timeout: 240 seconds) 11.38.30 Quit Misanthropos (Ping timeout: 256 seconds) 11.42.27 Join lorenzo92 [0] (~chatzilla@host24-106-dynamic.117-80-r.retail.telecomitalia.it) 11.46.09 Join einhirn [0] (~Miranda@bsod.rz.tu-clausthal.de) 11.48.18 Join syon__ [0] (~quassel@cpc23-cmbg15-2-0-cust12.5-4.cable.virginm.net) 11.56.50 Join Misanthropos [0] (~Misanthro@frnk-5f743194.pool.mediaWays.net) 12.02.36 Quit ploco (Quit: Page closed) 12.09.26 Join rela [0] (~x@p2003006684120F002808C2AC227127CA.dip0.t-ipconnect.de) 12.09.33 Quit rela (Changing host) 12.09.33 Join rela [0] (~x@pdpc/supporter/active/rela) 12.10.36 Quit Misanthropos (Remote host closed the connection) 12.14.09 Join Misanthropos [0] (~Misanthro@frnk-5f743194.pool.mediaWays.net) 12.31.39 Quit lorenzo92 (Ping timeout: 265 seconds) 12.43.53 Quit einhirn (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 12.46.29 *** Saving seen data "./dancer.seen" 12.49.54 Quit Misanthropos (Read error: Connection reset by peer) 12.50.25 Quit byteframe (Ping timeout: 258 seconds) 13.11.11 Join Misanthropos [0] (~Misanthro@frnk-4d013b78.pool.mediaWays.net) 13.20.18 Join ZincAlloy [0] (~Adium@pD9EEBD24.dip0.t-ipconnect.de) 14.04.17 Join lorenzo92 [0] (~chatzilla@host24-106-dynamic.117-80-r.retail.telecomitalia.it) 14.42.06 # large album art is working again on android ports o_O 14.46.33 *** Saving seen data "./dancer.seen" 14.49.47 Join RiD [0] (~RiD@bl22-61-11.dsl.telepac.pt) 15.12.34 Join amayer [0] (~amayer@mail.weberadvertising.com) 15.18.24 Join maruk [0] (~papier@titanium.v6.sdv.fr) 15.49.35 Quit krnlyng_ (Ping timeout: 240 seconds) 15.53.55 Join krnlyng_ [0] (~liar@83.175.90.24) 16.05.35 Quit krnlyng_ (Ping timeout: 240 seconds) 16.07.42 Join krnlyng_ [0] (~liar@83.175.90.24) 16.09.21 Quit JdGordon_ (Ping timeout: 244 seconds) 16.22.14 Join JdGordon [0] (~jonno@ppp118-209-154-15.lns20.mel8.internode.on.net) 16.22.14 Quit JdGordon (Changing host) 16.22.14 Join JdGordon [0] (~jonno@rockbox/developer/JdGordon) 16.46.37 *** Saving seen data "./dancer.seen" 16.59.49 Join Galois [0] (djao@efnet.math.uwaterloo.ca) 17.08.47 Join dfkt [0] (dfkt@unaffiliated/dfkt) 17.14.32 Quit bertrik (Ping timeout: 256 seconds) 17.17.59 Join Meezy [0] (492e5938@gateway/web/freenode/ip.73.46.89.56) 17.19.18 # hello, I need someone to help me with the component specs of the Sansa Fuze+ 17.21.22 # please? 17.22.18 # just ask your question and if someone knows the answer he will reply 17.23.28 # ok, the flex cable that connects to the navigation sensor 17.24.55 Quit Scall (Ping timeout: 240 seconds) 17.27.40 Join Scall [0] (~chat@unaffiliated/scall) 17.35.03 Join Zambezi__ [0] (Zulu@bnc.from.dotbnc.com) 17.35.34 # Meezy: what do you want to know about it ? 17.36.09 Quit Zambezi_ (Ping timeout: 244 seconds) 17.38.17 Join V4A-Pro [0] (~V4A-User@modemcable066.201-175-137.mc.videotron.ca) 17.39.32 Quit V4A-Pro (Client Quit) 17.39.40 Join V4A-Pro [0] (~V4A-User@modemcable066.201-175-137.mc.videotron.ca) 17.43.42 Quit V4A-Pro (Read error: Connection reset by peer) 17.48.33 # it says Eclipser - 512- 01.01 17.49.20 # on the other side in capital letters is AKM 17.49.36 # then in digital numbers is 1039 17.50.21 # theres also J1 17.52.25 # I don't get what is your question 17.52.40 # the flex cable by itself it quite irrelevant, it's just a flex cable 17.54.09 # do you know the part number? 17.54.23 # so that i can search online and buy it? 17.54.30 # no, did you damage it ? 17.54.37 # yes 17.54.39 # it snapped 17.56.32 # how did you achieve that ? you are not supposed to disassemble you device... 17.56.32 # anyway it looks like a standard flex cable, 6 wires, payt attention to which sides are conductive. Maybe someone here may help you, based on the photos of http://www.rockbox.org/wiki/SansaFuzePlus 18.01.24 Join [Franklin] [0] (~franklin@unaffiliated/franklin) 18.01.52 Join V4A-Pro [0] (~V4A-User@modemcable066.201-175-137.mc.videotron.ca) 18.03.03 Quit Meezy (Ping timeout: 246 seconds) 18.06.06 Quit V4A-Pro (Read error: Connection reset by peer) 18.24.05 Join V4A-Pro [0] (~V4A-User@modemcable066.201-175-137.mc.videotron.ca) 18.24.47 Quit thomasjfox () 18.28.24 Part maruk 18.31.03 Quit V4A-Pro (Read error: Connection reset by peer) 18.46.39 *** Saving seen data "./dancer.seen" 18.46.56 Nick [Franklin] is now known as worm (~franklin@unaffiliated/franklin) 18.47.07 Nick worm is now known as [Frankliny] (~franklin@unaffiliated/franklin) 18.47.21 Nick [Frankliny] is now known as [Franklin] (~franklin@unaffiliated/franklin) 18.49.15 Join bertrik [0] (~quassel@92.69.242.73) 18.49.27 Quit bertrik (Changing host) 18.49.27 Join bertrik [0] (~quassel@rockbox/developer/bertrik) 18.51.47 Quit Misanthropos (Quit: Ex-Chat) 18.55.15 Join Misanthropos [0] (~Misanthro@frnk-4d013b78.pool.mediaways.net) 19.03.54 Join bertrik_ [0] (~quassel@rockbox/developer/bertrik) 19.04.15 Quit bertrik (Ping timeout: 264 seconds) 19.13.51 Quit [Franklin] (Ping timeout: 240 seconds) 19.15.04 Join [Franklin] [0] (~franklin@cpe-071-071-039-006.triad.res.rr.com) 19.16.30 Join JdGordon_ [0] (~jonno@rockbox/developer/JdGordon) 19.24.43 Join Misanthropos_ [0] (~Misanthro@frnk-4d013b78.pool.mediaWays.net) 19.27.12 Quit Misanthropos (*.net *.split) 19.27.12 Quit JdGordon (*.net *.split) 19.30.14 Quit Scall (Ping timeout: 255 seconds) 19.34.46 Quit Misanthropos_ (Ping timeout: 250 seconds) 19.36.41 Join Scall [0] (~chat@unaffiliated/scall) 19.43.02 Join dowdle [0] (~dowdle@scott.coe.montana.edu) 19.44.09 # Argh, my Sandisk Sansa Clip Zip's screen broke. It seems that the Clip Sport is now the current model. Information about the Clip Sport on the Rockbox website is elluding me. Will Rockbox work on the SanDisk Sansa Clip Sport? 19.45.00 # No 19.46.38 # gevaerts: Is that "No" addressed to my question? 19.46.45 # Yes 19.46.56 # gevaerts: Ok. Darn the luck. Thanks for the info. 19.47.42 # Based on available information, it looks like the clip sport doesn't have powerful enough hardware to ever run rockbox 19.51.38 # <[Franklin]> does Rockbox have support for the long double type? 19.53.19 Join Misanthropos [0] (~Misanthro@frnk-4d01be07.pool.mediaWays.net) 20.00.35 # gevaerts: The Sport looks like a slightly redesigned Clip with the same playback (including radio) functionality... so I would hope it would have the same or slightly higher specs... but if you say it has less... what do I know? :) 20.02.00 Quit Misanthropos (Remote host closed the connection) 20.02.15 # <[Franklin]> always trust gevaerts ;) 20.02.27 # it uses a completely different processor, about which we know next to nothing, and the little we know tends to indicate that porting Rockbox would be if not possible, extremely hard 20.10.15 Join thomasjfox [0] (~thomasjfo@rockbox/developer/thomasjfox) 20.16.21 # pamaury: Well, Sandisk does appear to still make the Clip+ and Clip Zip... and there are plenty in the retail pipeline... so I guess my answer is clear. 20.16.35 Nick bertrik_ is now known as bertrik (~quassel@rockbox/developer/bertrik) 20.17.08 # Although I'd be open to another device if anyone has one they'd like to recommend. Would prefer it include radio functionality. 20.19.47 # depends on what you are looking for, there is the fuze+ but it has a touchpad and a completely different form factor. 20.22.12 Join Misanthropos [0] (~Misanthro@frnk-4d01be07.pool.mediaWays.net) 20.27.55 Quit Misanthropos (Ping timeout: 240 seconds) 20.46.41 *** Saving seen data "./dancer.seen" 20.48.47 Join krabador [0] (~krabador_@unaffiliated/krabador) 21.41.41 # <[Franklin]> foolsh: check out unitconv now! 21.43.23 # <[Franklin]> I think it's time to add semi-useful embellishments now :) 21.43.37 Quit JanC (Ping timeout: 265 seconds) 21.43.52 # <[Franklin]> [Saint]: you mentioned that there was a way to customize the virtual keyboard. Is there a way to do that from a plugin? 21.45.31 Part dowdle ("Konversation terminated!") 21.51.40 Join byteframe [0] (~byteframe@unaffiliated/byteframe) 21.55.59 Join JanC [0] (~janc@lugwv/member/JanC) 21.57.05 Quit sakax (Remote host closed the connection) 22.04.55 Join Misanthropos [0] (~Misanthro@frnk-5f7407e0.pool.mediaWays.net) 22.16.58 # kugel: hey there :) do you know of your mind why buflib handle 0 is invalid? is it because handle_alloc() is an unsigned (pointer) and therefore NULL is used to return an "invalid handle"? 22.17.01 Quit Misanthropos (Remote host closed the connection) 22.17.56 Quit [Franklin] (Ping timeout: 272 seconds) 22.18.55 Join Misanthropos [0] (~Misanthro@frnk-5f7407e0.pool.mediaWays.net) 22.23.27 Quit Misanthropos (Ping timeout: 264 seconds) 22.26.53 # * thomasjfox thinks that "val" is not the best name for the buffer length indicator in buflib 22.27.49 Join [Franklin] [0] (~franklin@cpe-071-071-039-006.triad.res.rr.com) 22.38.07 Join Misanthropos [0] (~Misanthro@frnk-5f7407e0.pool.mediaWays.net) 22.41.03 Quit Misanthropos (Remote host closed the connection) 22.42.47 Join Misanthropos [0] (~Misanthro@frnk-5f7407e0.pool.mediaWays.net) 22.46.16 # <[Saint]> [Franklin]: No, there is not. 22.46.27 # <[Saint]> [Franklin]: and, it'd be a somewhat silly idea. 22.46.44 *** Saving seen data "./dancer.seen" 22.47.03 # <[Saint]> You'd have to use the virtual keyboard to customize the...virtual keyboard. 22.47.27 Quit Misanthropos (Ping timeout: 264 seconds) 22.47.53 # <[Saint]> thomasjfox: sounds roughly similar to the variables in some of my themes. 22.48.19 # :o) 22.48.23 # <[Saint]> They have such excellent descriptive names like "variable_1" and "variable_2" 22.48.42 # it could have just been called "length", but that would be kind of boring... 22.52.35 # also, to make it even more fun, the documentation of the buflib datastructure does not correspond to the current implementation 22.52.46 # I'll verify that tomorrow in detail 22.53.06 # ...and it all started because I wanted to know why zero is an invalid buflib handle :D 22.53.57 # <[Saint]> thomasjfox: I've asked myself a few questions about buflib and ended up running away screaming, and cowering in fear. 22.54.00 # <[Saint]> Good luck. 22.54.32 # <[Saint]> Also, yeah, a fair few of the comments in there don't seem to apply anymore. 22.54.34 # thanks. I'll start by adding documentation to buflib.h and probably will rewrite the documentation a bit the next days ;) 22.55.06 # in-tree unit test would also be nice... 22.55.39 # <[Saint]> I know you can piss around to a very limited extent in the debug menu for buflib and allocate and drop a test buffer, so this could quite probably be expanded upon to provide meaningful tests and data. 22.56.06 # I was wondering in general why rockbox doesn't have anything like cunit or so 22.56.15 # <[Saint]> but I may have lost track of your interim or end goals. 22.56.21 # <[Saint]> aha, right. I see. 22.57.27 # instead of wishing death to your worst enemies, you could also wish them to write unit tests for tagcache :p 22.58.06 # <[Saint]> Ohhhhhhh piss off. 22.58.08 # <[Saint]> :p 22.58.27 # <[Saint]> tagcache is one of the core assets in Rockbox that _EVERYONE_ fears. 22.58.40 # <[Saint]> If you look at the git history, its hilarious. 22.58.41 # in java, I do a lot of unit testing, don't really know how to do that in C 22.58.43 # it's also funny that the buflib documentation starts to mention "cookie" in two places without even explaining it 22.58.45 # <[Saint]> It basically never gets touched. 22.58.55 # * [Saint] nods 22.59.06 # <[Saint]> I've noticed that too but I assumed it was a Gerglish-ism. 22.59.25 # we should change that in the long run, tagcache is such a cool feature. In fact the tag database is the feature I remember most vividly from my empeg / Rio Karma 22.59.37 # <[Saint]> Very few of the core developers use it. 22.59.46 # <[Saint]> I can't think of anyone offhand. 23.00.00 # in doubt: gevaerts does! 23.00.02 # * bertrik raises hand timidly 23.00.21 # * [Saint] bets gevaerts most certainly does not use tagcache 23.00.33 # <[Saint]> I'd almost be willing to put money on it. 23.00.51 # you should bet pineapple on it... 23.01.00 # <[Saint]> Its a combination of two factors, really. 23.01.10 # <[Saint]> 1: Very little core devs actually use tagcache 23.01.17 # <[Saint]> 2: its foolishly fucking complex. 23.01.32 # <[Saint]> both of those add up to the current situation. 23.02.02 # 3: no unit tests. If you touch one of the dark corners of it, you don't know if you break something by accident 23.02.10 # <[Saint]> oh - I guess there's also 3: it "Just Works" and has done for years and years and years. 23.02.27 # <[Saint]> If it fell over at any point, maybe things would be quite different. 23.02.41 # <[Saint]> but its been remarkably solid. 23.03.03 # I remember I had to reset it a few times on RaaA 23.03.15 Quit rela (Quit: Leaving) 23.03.23 # it just choked on the 300.000+ files on the N900 I guess 23.04.47 # <[Saint]> it shouldn't. 23.04.55 Quit mwcampbell (Ping timeout: 240 seconds) 23.05.20 # <[Saint]> I have mine reading from a mounted network share and it has to deal with a LOT more than 300k files. 23.05.52 # hehe :) 23.05.59 # <[Saint]> perhaps its something specific to the N900, I dunno. But I haven't had any issue with reading very learge quantities of files on hosted platforms. 23.06.09 # <[Saint]> *large 23.08.21 # it just happened two times. Currently it's running fine 23.11.35 Join bluebrother [0] (~dom@rockbox/developer/bluebrother) 23.13.55 Quit fs-bluebot (Ping timeout: 240 seconds) 23.14.21 Quit bluebrother^ (Ping timeout: 240 seconds) 23.14.52 Join fs-bluebot [0] (~fs-bluebo@g226070022.adsl.alicedsl.de) 23.32.22 Quit lorenzo92 (Ping timeout: 265 seconds) 23.34.08 # does anyone have experience with those dual sd-to-cf adapters? i assume/hope they merge both sd cards into one, like raid0? 23.34.15 # something like this - http://www.ebay.com/itm/Dual-2-TF-Slot-Micro-SD-SDHC-SDXC-To-CF-Card-Adapter-Compact-Flash-Converter-/181558099084?pt=US_Memory_Card_Readers_Adapters&hash=item2a45b4bc8c 23.35.23 # any speed increase for my h300 would be nice, considering its true IDE interface is way faster than newer mp3 players anyways 23.36.18 # <[Saint]> I have a few uSD RAID adapter cards, and in every single instance they make IO drastically worse. 23.36.40 # they do? ouch. 23.36.52 # <[Saint]> Instead of the terrible random read/write of a single SD card, you're now adding another to it. 23.37.10 # <[Saint]> It merely magnifies the shitty things about SD. 23.37.14 # hm. so a single sd-to-cf would be better? 23.37.20 # <[Saint]> Much. 23.37.52 # good to know. i guess they don't have much of a controller in there, that actually manages the two cards 23.38.00 # <[Saint]> Its quite possible that there exists adapters of this type that aren't terrible, but I haven't found any. 23.38.09 # they're all from china, that i found 23.38.14 # so... yeah :) 23.38.37 Quit amayer (Quit: Leaving) 23.38.43 # ok, single adapter and single (non-micro) 128gb sd it is 23.39.38 # <[Saint]> sdcards these days, especially the large capacity ones, seem to (rightly so, given their intended use case) prioritize large contiguous writes. 23.39.51 # <[Saint]> something that's going to happen quite rarely in the desired application. 23.40.32 # yeah, shouldn't matter much with rockbox accessing the card, i was just thinking about pc-to-player transfer 23.40.33 # <[Saint]> when you start to chuck in small random reads and writes things can fall over hilariously. 23.40.40 # <[Saint]> aha, right. 23.41.06 Quit syon__ (Ping timeout: 245 seconds) 23.41.22 # <[Saint]> I'm sure its possible to create such adapters that /don't/ suck, but I haven't found any personally. 23.41.35 # <[Saint]> The ones I own to seem to be largely for the sake of novelty. 23.41.48 # i'd like to cut out the whole sd shtick anyways, but cf prices are still much higher 23.42.03 # <[Saint]> Yeah, indeed. 23.42.08 # yours are the typical ebay/dx specimens as well? 23.42.17 # <[Saint]> Correct. 23.42.21 # :) 23.43.22 # <[Saint]> I have a 2 card SD -> USB adapter, and a 4 card uSD -> sd adapter. 23.43.41 # <[Saint]> very weird shit. 23.44.06 # just slow, or prone to mess up the data as well? 23.44.26 # <[Saint]> Just dog slow. 23.44.44 # guess game from buflib_alloc_ex(): "size += name_len; size = (size + sizeof(union buflib_data) - 1) / sizeof(union buflib_data)" 23.44.52 # <[Saint]> and the latter isn't particularly practical as it has a hilariously flimsy ribbon cable. 23.44.58 # what's the "xxx -1" in there (I know the answer) 23.45.39 # * thomasjfox loves magic numbers in the code 23.46.13 # <[Saint]> I...wha? Hmmm. 23.46.13 # in my x5 i have a fancy full-enclosure cf-to-ide with a lexar 400x cf... it gives about 20mb/s for both, read and write 23.46.22 # * [Saint] needs some context. 23.46.38 # hope i get something close with a sd-to-cf-to-ide in my h300 23.46.39 # look at buflib.c:buflib_alloc_ex() 23.52.42 # <[Saint]> maybe my sources are old, or is that psuedo-code? 23.53.02 # <[Saint]> I can find vaguely similar strings, but nothing to that exact effect. 23.53.55 # ah, sorry, I squeezed it into one line. Search for "sizeof(union buflib_data) - 1)" 23.54.18 # I still bet you won't figure it out instantly. It took me ages until it occured to me 23.57.18 # need a hint? 23.57.28 # <[Saint]> Please. 23.57.29 # <[Saint]> o_o 23.57.34 # look at the line before that given line 23.58.18 # still no clue?