Previous day | Jump to hour: 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 | Next day

Seconds: Show Hide | Joins: Show Hide | View raw
Font: Serif Sans-Serif Monospace | Size: Small Medium Large

Click in the nick column to highlight everything a person has said.
The Logo icon identifies that the person is a core developer (has commit access).

Notice: Only Gecko based browsers prior to FF4 support the multipart/mixed "server push" method used by this log reader to auto-update. Since you do not appear to use such a browser, this page will simply show the current log, and not automatically update.

#rockbox log for 2016-02-06

00:24:29***Saving seen data "./dancer.seen"
00:24:34 Quit krnlyng (Ping timeout: 240 seconds)
00:29:50 Join krnlyng [0] (
00:46:22 Quit lebellium (Quit: ChatZilla 0.9.92 [Firefox 45.0/20160201143558])
00:47:05 Quit petur (Quit: Leaving)
01:28:59 Quit krnlyng (Ping timeout: 272 seconds)
01:39:39 Quit pamaury (Ping timeout: 245 seconds)
02:21:49 Quit krabador (Read error: Connection reset by peer)
02:24:33***Saving seen data "./dancer.seen"
02:29:18 Join krnlyng [0] (
02:29:58 Quit ZincAlloy (Quit: Leaving.)
02:40:20jtdesigns01Mr. Somebody needs to implement material UI in rockbox.
02:42:26[Saint]If only we had a full theme engine...
03:05:45 Quit foolsh_ (Ping timeout: 250 seconds)
03:31:31 Quit Link7 (Remote host closed the connection)
04:19:13 Quit krnlyng (Ping timeout: 276 seconds)
04:24:36***Saving seen data "./dancer.seen"
04:29:59 Join krnlyng [0] (
05:32:05 Quit krnlyng (Ping timeout: 240 seconds)
05:36:34 Quit TheSeven (Ping timeout: 240 seconds)
05:38:14 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven)
05:38:33 Quit Rower (Ping timeout: 240 seconds)
05:47:25 Join Rower [0] (
06:12:00 Quit sparetire (Quit: sparetire)
06:24:40***Saving seen data "./dancer.seen"
06:30:28 Join krnlyng [0] (
06:51:45 Quit PurlingNayuki (Read error: Connection reset by peer)
06:53:06 Join PurlingNayuki [0] (~Thunderbi@
07:20:05 Join feoafka [0] (
07:20:57 Quit athidhep (Ping timeout: 250 seconds)
07:45:27 Join JdGordon [0] (
07:45:27 Quit JdGordon (Changing host)
07:45:27 Join JdGordon [0] (~jonno@rockbox/developer/JdGordon)
07:45:55 Quit krnlyng (Ping timeout: 248 seconds)
07:47:14 Quit JdGordon_ (Ping timeout: 240 seconds)
08:24:41***Saving seen data "./dancer.seen"
08:31:05 Join krnlyng [0] (
09:12:33 Join bertrik [0] (~quassel@rockbox/developer/bertrik)
09:51:04 Quit krnlyng (Ping timeout: 240 seconds)
09:52:51 Quit Rower (Ping timeout: 248 seconds)
09:58:20 Quit bertrik (Remote host closed the connection)
10:13:34 Join Rower [0] (
10:19:31 Join ender` [0] (
10:22:30 Join krabador [0] (~krabador@unaffiliated/krabador)
10:24:42***Saving seen data "./dancer.seen"
10:31:38 Join krnlyng [0] (
10:47:43 Quit bluebrother (Disconnected by services)
10:47:48 Join bluebrother [0] (~dom@rockbox/developer/bluebrother)
10:48:42 Join fs-bluebot [0] (
10:50:41 Quit fs-bluebot_ (Ping timeout: 250 seconds)
11:14:24 Join petur [0] (~petur@rockbox/developer/petur)
11:19:48 Join lebellium [0] (
11:47:10 Join djukon [0] (~djukon@gateway/shell/insomnia247/x-gtypbvsqtvcqkijb)
11:50:43 Quit krnlyng (Ping timeout: 248 seconds)
12:20:55 Quit djukon (Ping timeout: 240 seconds)
12:21:16 Join wodz [0] (
12:24:44***Saving seen data "./dancer.seen"
12:25:14 Quit JanC (Ping timeout: 240 seconds)
12:28:30 Join djukon [0] (
12:31:59 Join krnlyng [0] (~liar@
12:39:38 Join JanC [0] (~janc@lugwv/member/JanC)
13:20:06 Join pamaury [0] (~quassel@rockbox/developer/pamaury)
13:22:22wodzpamaury: ping
13:23:25pamaurywodz: pong
13:23:37orpheu apple:
13:23:49pamauryjust saw your message
13:23:55wodzpamaury: I dropped you email. Hope you will have some brilliant idea
13:24:13orpheuimagine if this was the case with the ipods!
13:24:22wodzpamaury: I have literally no idea
13:24:29pamaurycouple of ideas: check that all the constants in the code are correct (ie are you writing the proper value ?), is the register address correct ? is register size correct ?
13:25:00pamaurywhat do switch with the command ?
13:25:32pamaury*do you
13:27:21wodzsdlib_send_cmd(IF_MD(drive,) SDLIB_SWITCH_FUNC, 0x80fffff1, &rspdat, 64);
13:27:31wodzso switching to HS timing
13:28:18pamaurydo you change the communication frequency too or does is freeze even with the original one ?
13:28:28wodzwith original
13:29:17wodzit freezes when you write to register which starts the transfer to the card
13:30:04pamaurydid you switch to 4-bit bus size before ? did you correctly disconnected the pull-up on cd/dat3 ?
13:31:04wodzI tried also to insert delay before this command and removed the card. The transfer then moves on but fails of course but this allows me to double check which values were written to registers
13:31:29pamauryare you sure that the clock and power setting are the same with lua and C code ?
13:32:19wodzpamaury: I think I checked that before
13:34:42pamauryit is unfortunate that you don't have anything to sniff the sd traffic, see what is happenning
13:35:35wodzThats the sequence. It goes well till this SWITCH_FUNC
13:36:00pamaurydoes it use dma ?
13:37:26wodzpamaury: this is lua part
13:38:07wodzpamaury: I which sense? You can grab data with general purpose dma engine.
13:38:30pamaurymaybe there is a problem with memory alignement ? or other constraints ?
13:39:11pamauryout of curiosity, how do you encode the fact that commands need to first send SD_APP_CMD ? Is that included in SDLIB_* ?
13:39:25wodzpamaury: yes
13:40:26pamaurydid you try to dump the response of the card after each command to see if the error is before and the card somehow enters an error state ?
13:40:41wodzpamaury: hmm, good idea
13:40:56pamaurythe looks really ok, that's frustrating !
13:42:46pamaurywodz: I'm slightly concerned about the way you get the RCA
13:43:06wodzThe things which I really can't understand is HOW this manifests. To send command to the card you basically write SD_ARG with argument, SD_CMD with command code and then SD_CMDRSP with response type expected and bit to kick it in. Now with this command the very next instruction after writing SD_CMDRSP is never executed
13:43:31pamauryah no sorry, forgot that lua indices start at one !
13:49:09wodzah, I also tried various compiler flags to rule out some optimization problem.
13:49:14pamaurywodz: you can even go further: dump everything you write to sd registers in lua and C and compare
13:50:35wodzpamaury: I kinda did. I print from inside send_cmd() just after sanity checks.
13:53:37wodzthe sd clock dumped from registers is 281250Hz so well below the limit
13:55:04wodzit the same in lua and C
13:56:51pamauryif everything is the same, it must an another factor, something related to gpio, clock or power (or dma ?)
13:58:33wodzwhat can cause write to register hang?
13:59:13wodzI'd expect the write to succeed but maybe give erroneous effect but not hang.
13:59:58pamaurya typical hang would that sd tries to communicate with a hardware block which is powered down or gated
14:00:17pamaurydid you ungate dma properly ?
14:01:18wodzWhat if I do not consume this 64bytes of data? Could it hang the thing?
14:01:34pamauryprobably not
14:01:53pamaurybut you don't even reach this point right ?
14:02:14wodzyes it hangs earlier
14:02:44pamauryI mean if don't get all the data the sd card is sending, the next command will probably fail but that's all
14:03:19wodzThats I understand this as well and hence it doesn't fit to what I see here
14:03:21pamaurycan you post the code of the sdlib_* and sdc_* functions ?
14:03:50wodzpamaury: 1 sec
14:04:39pamauryI'll be back in 10/15 mon
14:09:26wodz - sdlib.h; - sdlib.c; - sd-drv-atj213x.c
14:15:30 Join bertrik [0] (~quassel@rockbox/developer/bertrik)
14:24:46***Saving seen data "./dancer.seen"
14:24:53 Quit [Saint] (Remote host closed the connection)
14:25:13pamaurywodz: did you see g#1246 ?
14:25:14fs-bluebot3Gerrit review #1246 at : 3configure: allow for compiler toolchain override (with warnings) by Amaury Pouly
14:25:50 Join [Saint] [0] (~hayden@rockbox/staff/saint)
14:29:49wodzpamaury: yes I saw that
14:32:33pamaurywodz: I might be missing something but why do you call sdc_dma_wr uncondtionnally ? shouldn't it be sdc_dma_rd in the case of the switch command for example ?
14:35:04wodzpamaury: where exactly? I see if (rspdat->data && datlen > 0 && !rspdat->rd) condition for calling sdc_dma_wr
14:35:48pamauryok but 1) also sdc_dma_wr() is a stub ? 2) why isn't there another another test for sdc_dma_rd() ?
14:36:23pamaurymaybe the sd block doesn't like the fact that you don't setup dma ?
14:38:37wodzpamaury: I experimented with this in lua. The next command fails if you do not consume data but thats it
14:39:25wodzand btw there is such test near the end of sdc_send_cmd()
14:40:16pamauryoh I see sorry, I thought would setup the dma transfer before sending the command
14:41:06wodzI can't remember why I did it this way actually
14:42:15pamauryI'm running out ideas...
14:44:53wodzso am I ...
14:49:49pamauryis there a difference in the running environement between C and lua ?
14:50:07pamauryany thought on g#1246 ? I'd like to commit it
14:50:08fs-bluebot3Gerrit review #1246 at : 3configure: allow for compiler toolchain override (with warnings) by Amaury Pouly
14:52:15wodzpamaury: for me it ok, commit
14:52:43wodzpamaury: I can't think of anything relevant
14:52:45pamauryhow do load the C code ? through hwstub ?
14:53:08wodzpamaury: no, directly by adfuload
14:53:24 Quit bertrik (Remote host closed the connection)
14:53:58pamaurycould it be that something in the hwstub init code makes a difference ?
14:56:12wodzcrt0.S is almost verbatim copy between the two.
15:01:32pamaurythen I would go for full dump of what you read/write in every register, you say you kinda of did already but why only "kinda" ?
15:01:58pamaurythere must be something if it manages to hang the whole thing
15:04:34fs-bluebotBuild Server message: 3New build round started. Revision 16c915e, 255 builds, 26 clients.
15:06:10pamauryI also would like to commit g#1131 soon, I can probably split it into several commits if necessary. The only, possibly annoying, big change is that qeditor cannot only read v2 file after this, but of course there is the convert program for v1 -> v2
15:06:27fs-bluebot3Gerrit review #1131 at : 3regtoosl/qeditor: port to the new description format (WIP) by Amaury Pouly
15:08:32pamauryhum, is it me or gerrit is dying ?
15:08:48 Join sparetire [0] (~sparetire@unaffiliated/sparetire)
15:09:11pamauryah finally back.
15:09:43pamaurywodz: also I tried to rewrite the imx233 code using the new headergen_v2 (basically removing the BF_SET macro so that it can be repurposed) and here is the result: g#1245
15:09:44fs-bluebot3Gerrit review #1245 at : 3imx233: generate register headers using headergen_v2 by Amaury Pouly
15:12:28fs-bluebotBuild Server message: 3Build round completed after 473 seconds.
15:12:29fs-bluebotBuild Server message: 3Revision 16c915e result: 23 errors 151 warnings
15:12:29wodzpamaury: I'd very appreciate commiting v2 stuff. I have various temp in either v1 format or v2 and holding two sets of tools and two sets of reg description is annoying
15:13:54pamauryok. I need to go through the code one last time to make sure I didn't left anything over. The only partially incomplete tool is headergen_v2 but that can be tweaked later
15:14:08 Quit [Saint] (Remote host closed the connection)
15:20:20 Join [Saint] [0] (~hayden@rockbox/staff/saint)
15:27:29 Join ZincAlloy [0] (
15:38:13 Quit [Saint] (Read error: Connection reset by peer)
15:43:04 Join [Saint] [0] (~hayden@rockbox/staff/saint)
16:10:54 Quit krabador (Ping timeout: 240 seconds)
16:11:19 Quit Rower (Ping timeout: 245 seconds)
16:11:45 Join krabador [0] (~krabador@unaffiliated/krabador)
16:22:24pamaurywodz: I've split the commit into two: g#1247 and g#1131
16:22:26fs-bluebot3Gerrit review #1247 at : 3regtools: update v2 specification, library and tools by Amaury Pouly
16:22:26fs-bluebot3Gerrit review #1131 at : 3regtoosl/qeditor: port to the new description format by Amaury Pouly
16:22:30pamauryFor me it's ready to push
16:23:16wodzpamaury: I am using some quite recent version of this here without problems so for me - go ahead and commit
16:24:48***Saving seen data "./dancer.seen"
16:25:20pamauryok cool
16:25:30fs-bluebotBuild Server message: 3New build round started. Revision 0f701a6, 255 builds, 26 clients.
16:25:39 Join rela_ [0] (
16:29:04 Quit rela (Ping timeout: 240 seconds)
16:30:19fs-bluebotBuild Server message: 3Build round completed after 290 seconds.
16:30:20fs-bluebotBuild Server message: 3Revision 0f701a6 result: 1 errors 25 warnings
16:30:21fs-bluebotBuild Server message: 3New build round started. Revision 6b9610f, 255 builds, 26 clients.
16:34:44fs-bluebotBuild Server message: 3Build round completed after 264 seconds.
16:34:45fs-bluebotBuild Server message: 3Revision 6b9610f result: 0 errors 33 warnings
16:41:24fs-bluebotBuild Server message: 3New build round started. Revision 6e54f72, 255 builds, 26 clients.
16:46:38fs-bluebotBuild Server message: 3Build round completed after 314 seconds.
16:46:39fs-bluebotBuild Server message: 3Revision 6e54f72 result: 0 errors 24 warnings
16:46:40fs-bluebotBuild Server message: 3New build round started. Revision 7d87ebb, 255 builds, 22 clients.
16:51:48fs-bluebotBuild Server message: 3Build round completed after 310 seconds.
16:51:49fs-bluebotBuild Server message: 3Revision 7d87ebb result: 0 errors 121 warnings
16:52:17 Join Rower [0] (
16:53:12wodzpamaury: I compared clocks and this are the same in hwstub and in C. I checked also command responses and they are the same in lua and C.
16:55:54 Quit Jack87 (Read error: Connection reset by peer)
16:57:23pamauryare you absolutely sure you write the same registers in the same order with the same values in C and lua ? how could it be possible ?!
16:57:39 Join Jack87 [0] (~Jack87@nasadmin/admin/jack87)
17:02:02wodznow I checked if running from uncached address makes a difference but it doesn't
17:04:32wodzthe only difference is more repetitions of acmd41 when running with cache which is obvious
17:09:39wodzpamaury: I checked once again the order in which registers are written is the same: ARG, CMD, CMDRSP
17:10:02wodzconstants used for CMDRSP are the same
17:12:56wodzThere is one big difference however. C code uses lcd to output debug info. The problem is that sd lines and lcd lines are multiplexed. But if this is the cause why on earth i triggers only this command.
17:15:15pamaurymaybe because you don't get the data ?
17:16:42pamaurylike you lock the pins for sd, do things, unlock the pins, but the sd block is still doing things on the pins so when the lcd acquire then, something bad happens ?
17:17:42wodzbut it hangs before I unlock so I can't see how this could happen
17:18:25wodzbtw. who on earth had an idea to multiplex sd and lcd in DAP!
17:18:31pamauryis it possible that in the lock/unlock scheme you forgot some pins ?
17:18:40pamauryyeah that looks like a bad idea in the first place
17:18:57pamaurybecause this command is probably the first one to use DAT1,2,3
17:19:10pamauryfor example forgot a pullup/down
17:19:24wodzI use the same constants as in lua
17:19:49wodzI mean to drive multiplexer
17:21:02pamaurybut lua doesn't use the lcd
17:22:38wodzthats true. But I just added some flipping of the muliplexer in lua to somewhat simulate this and card initialization still works.
17:22:58wodzso pure switching of multiplexer is correct
17:23:18pamauryI was more thinking about a problem that the switching forget something, and this something doesn't interfere as long as the lcd is not in use
17:23:40pamauryi don't know if it's even possible
17:23:56wodzswitching code is taken from disassembly of sd driver in OF
17:23:57pamauryfor example try to gate the lcd when doing sd operations to see
17:24:22wodzhmm, interesting idea, lets try
17:30:13wodzhmm, maybe the whole problem is not in sd but in lcd? Maybe for some reason displaying gets broken
17:31:04pamaurywodz: can you copy the switching code and lcd code so I can have a look at the datasheet ?
17:33:21wodzpamaury: switching code wodz/rockbox-atj213x/blob/master/firmware/target/mips/atj213x/gpio-atj213x.c"> lcd code
17:34:05wodzin local tree I have random delays spread in switching code but I don't see any difference actually
17:36:50 Nick kugel__ is now known as kugel (~kugel@rockbox/developer/kugel)
17:38:02wodzpamaury: yep. it is lcd which is screwed up. I inserted backlight_hw_off() and this gets executed.
17:40:58wodzso this command somehow kills lcd transfers (data transfer?)
17:42:35pamaurybut how ? it doesn't call the lcd ?
17:43:38 Join ender [0] (
17:44:24 Quit Smx- (Excess Flood)
17:44:47wodzno it sets pwm fill factor
17:44:54 Quit ender` (Ping timeout: 240 seconds)
17:46:57pamaurybut you are saying that backlight_hw_off() kills the lcd transfer ?
17:48:59 Join Smx [0] (Elite8556@gateway/shell/elitebnc/x-rftkxxuqndboaypj)
17:49:00wodzno, no
17:49:17wodzcmd6 kills all subseqent lcd transfers
17:49:28 Join Mihail [0] (252d7c79@gateway/web/freenode/ip.
17:51:33wodzthis should be possible to simulate in lua as well.
17:51:59pamaurycould it have something to do with the SD pullup ?
17:54:23Mihailwodz: I have some experience with direct use of sd cards on uC (AVR). Possible I can try help. Are you sure that initialization of sd card is successful?
17:56:03wodzMihail: On AVR you are using SPI mode which is a bit different. The problem seems to be in ackward multiplexing of sd and lcd lines in this particular case
17:56:30pamaurywodz: SD_CTL_RESE enables pullups, so when you switch the bus to 4-bit, I assume it also enables pullups on the data lines. If somehow those pullups are still on after the gpio function change, that will probably kill the lcd tranfers
17:56:53pamaury(assuming the chip doesn't multiplex the pullup which could be possible)
17:57:24wodzpamaury: ACMD42 disconnect the pull-up resistor on CD/DAT3 - at least thats how I read this command
17:57:34pamauryyeah but on the host side
17:57:42wodzpamaury: ah, I see what you mean
17:59:18wodzpamaury: hmm, SD_CTL_RESE is set indeed in initialization
17:59:44pamaurylet me check the SD spec, I don't remember all the details of the on-wire format
18:01:24wodzhmm, OF writes 0 to SD_CTL after sd transfers
18:02:59pamaurythe sd bus needs pullups to operate, the question is whether those are external or internal, I guess RESE is meant to be used when there are no external pullups
18:03:23pamauryso it probably needs to be set before the transfer, but after it you might want to disable them
18:03:38wodzthe interesting thing is that gating clock to SD block doesn't block access to sd registers. I am curious what clock gate means in this case
18:03:52pamauryprobably card clock gating
18:04:04pamauryyou don't want the scaclock to be on when sending
18:04:13pamaury*card clock to be on when sending lcd data
18:04:58wodzup to cmd6 it doesn't matter but who knows
18:05:32pamaurywhat does the OF do ?
18:06:19pamauryup to CMD6 you don't use the data lines. I assume the SD CMD and CLK lines are not shared ?
18:06:30Mihailwodz: you right, but initial stage mostly same. From my experience ACMD41 should by send with one second delay between attempts. Some cards don't response correct on ACMD41, but still can be used after 5 attempts.
18:07:12wodzMihail: I have the problem further in the line of initialization. ACMD41 works just fine
18:07:26pamauryomg, they even multiplex SD CLK and lcd CE :-o
18:07:44pamaurythat's kind of clever actually
18:08:04wodzpamaury: OF uses quite complicated sequence actually
18:10:43wodzpamaury: oh, and OF sets unknown register in GPIO block - 0xb01c0088
18:10:58pamaurythat might be important
18:11:24pamauryit's PAD_DRV
18:11:45wodzpamaury: I checked that there is also 0xb01c0084 and 0xb01c008c which sticks value written into
18:12:00pamauryprobably related to drive strength and pullups, might be exactly what we need
18:12:38wodzpamaury: where do you see it?
18:13:25wodzah, I see it. How could I overlook it
18:14:07wodzOF ORs 0x23 with this register
18:15:40pamaurythat P_D[0:3], P_D[4:7] and PA[5:0]
18:15:48pamauryis there a pin map ?
18:16:48pamauryMFCTL0 refers to A[2:0] for SD_CMD and D[7:0] for data
18:17:30wodzI think pinmap is in Datasheet (as opposed to programming guide)
18:18:32wodzhmm, I see this bits only set. I can't spot anything clearing it.
18:19:33wodzThe set part is in function which prepares sd block to be operational
18:20:12wodzit sets interface width, clk freq, multiplexing and this PAD_DRV
18:21:13wodzThe counter function which deactivates block doesn't touch PAD_DRV
18:22:37pamaurythat's worth a try I would say
18:22:50pamaurysince we don't really know what it does anyway
18:23:41wodzI'd love to reproduce this on hwstub as there is much easier to sniff around
18:24:49***Saving seen data "./dancer.seen"
18:27:35pamaurythe datasheet doesn't say much about pad driver
18:28:17pamauryand there is no schematic of the gpio structure
18:29:16pamaurybut my guess is that it controls drive strength, since if you have a pullup on the bus, you might need a high drive strength to achieve good rise/fall times
18:29:46pamauryespecially if you drive it above 10 or 20MHz
18:30:01pamaurylike the lcd probably does
18:31:00 Quit PurlingNayuki (Quit: PurlingNayuki)
18:32:12pamaurywodz: I need to leave, but i'll read the log and might be online later
18:32:31wodzok, thanks for support
18:36:33 Quit pamaury (Ping timeout: 250 seconds)
18:44:00 Quit orpheu (Quit: Page closed)
18:46:46 Quit Mihail (Quit: Page closed)
19:12:03 Join orpheu [0] (0252b710@gateway/web/freenode/ip.
19:14:44wodzpamaury: (log) Setting PAD_DRV helps indeed.
19:15:54wodzpamaury: (log) I don't know yet if it solves everything but cmd6 doesn't screw up panicf() at least
19:22:22 Quit shamus (Read error: Connection reset by peer)
19:42:58 Join HazWard [0] (~HazWard@
19:45:08HazWardThe android port of Rockbox is written in what language
19:47:57 Quit krnlyng (Quit: huiiiiii)
19:48:24 Join krnlyng [0] (
19:54:03rela_java i presume
20:14:04wodzjava is only thiny wrapper around native .so library
20:14:28wodzRockbox is C + small portion of asm
20:14:36 Join krnlyng_ [0] (~liar@
20:14:53wodzHazWard, rela: ^
20:16:29wodzHazWard: Why are you asking?
20:17:45HazWardI was thinking about learning a language to maybe modernize rockbox but I don't know C and Assembly
20:18:12 Quit krnlyng (Ping timeout: 272 seconds)
20:19:23wodzHazWard: Modernize in which sense?
20:20:10 Quit rela_ (Quit: Leaving)
20:20:25 Join rela [0] (~x@pdpc/supporter/active/rela)
20:21:07HazWardOn android, the UI feels clunky, the core of Rockbox is amazing but the UI isn't on par with what the software can deliver
20:22:30wodzHazWard: You would need to drastically change the way rockbox on android port is done. This HUGE task.
20:23:24wodzHazWard: Kugel started work in this direction but lost interest/had no time to finish. Nobody picked that up till now.
20:24:53***Saving seen data "./dancer.seen"
20:25:01wodzHazWard: Basically you would need to rip core part of rockbox and turn it into lib with established API. Then write UI part in java and call rockbox code from there.
20:25:39 Nick krnlyng_ is now known as krnlyng (~liar@
20:26:05wodzHazWard: Not speaking about solving threading to not interfere with android runtime.
20:28:26wodzHazWard: And honestly now it is easier to build app around ffmpeg or something then diving into 10+ years of history
20:30:07 Join saratoga [0] (ac3ad93e@gateway/web/freenode/ip.
20:30:32saratogai think you could write a new UI and just use the rockbox codec lib as well, although that would be far from a rockbox port
20:30:55saratogabut really if knowing c is a problem, i think this is probably too ambitious a project
20:31:18HazWardok thanks a lot for the tips wodz, and is there anything new going on with the "traditional" builds (running on DAP)
20:32:04wodzHazWard: from time to time, yes
20:32:58HazWardsaratoga: learning c isn't a problem at all, I'm currently learning c# and trying things with unity3d so a new language is not a problem
21:01:03 Quit saratoga (Quit: Page closed)
21:28:29 Quit alexweissman ()
21:30:03 Quit krabador (Read error: Connection reset by peer)
21:32:07 Join krabador [0] (~krabador@unaffiliated/krabador)
21:51:56 Join nlogex [0] (
22:13:12 Join webguest69 [0] (
22:13:16 Quit webguest69 (Client Quit)
22:14:33 Quit djukon (Ping timeout: 240 seconds)
22:16:39HazWardI've installed Rockbox on an iPhone 3G (4.2.1) with OpeniBoot (iDroid)
22:16:40 Join djukon [0] (
22:21:13 Quit mwfc (Ping timeout: 240 seconds)
22:22:31 Join mwfc [0] (
22:24:54***Saving seen data "./dancer.seen"
22:49:24 Quit wodz (Ping timeout: 240 seconds)
23:08:54 Quit rela (Ping timeout: 240 seconds)
23:15:59[Saint]HazWard: Oh wow /reaaaaally/ hate yourself don't you, lol.
23:24:29HazWard[Saint]: Do you still have you theme for touch devices?
23:30:02[Saint]I might, somewhere, on some backup snapshot - the current 320x480 cabbiev2 does indeed support touchscreen, though.
23:30:42[Saint]So if touch isn;t working out of the box it is probable that it's a result of some fuckery in the nature of how you got this frankendroidiOS kludge running.
23:31:51[Saint]I'm looking at cabbiev2.320x480x16.wps right now and it pretty clearly supports touchscreen devices.
23:36:29 Join shamus [0] (
23:37:34[Saint]What I am basically saying is that if touch isn't working for you right now, no theme that myself or anyone could supply you will make that not be the case, and you would need to debug the interaction between the iOS and Android layers and how that relates to the touchscreen.
23:39:23HazWardtouch is perfectly working
23:39:24 Quit Rower (Ping timeout: 250 seconds)
23:39:50[Saint]Oh. Then what was the intention?
23:39:56jtdesigns01how do we even deal with touch in RB?
23:40:04HazWardchanging the theme
23:40:38[Saint]If you dislike cabbiev2, then you don't want anything that I could supply you.
23:41:10HazWardhaha well ok
23:41:30HazWardand can rockbox run as a linux application (no simulator)?
23:42:53[Saint]Our configure script presents an SDL target device.
23:43:06HazWardwhere could I find a build (or do I have to build it myself)
23:43:21[Saint]The latter.
23:45:32Petri152I love you all
23:46:57jtdesigns01I`ll take that as a compliment
23:55:10*[Saint] has some fun with the forum quote syntax

Previous day | Next day