2013-10-13 00:13 cmbrgo has quit [Changing host]
2013-10-13 00:13 cmbrgo has joined #qi-hardware
2013-10-13 00:47 <kristianpaul> freertos? :o
2013-10-13 00:49 pcercuei has quit [Quit: dodo]
2013-10-13 01:19 dos1 has quit [Ping timeout: 240 seconds]
2013-10-13 01:29 wej has quit [Ping timeout: 264 seconds]
2013-10-13 02:40 <DocScrutinizer05> o.O
2013-10-13 02:41 <DocScrutinizer05> rogue site?
2013-10-13 03:03 xiangfu has quit [Ping timeout: 272 seconds]
2013-10-13 03:23 wolfspraul has joined #qi-hardware
2013-10-13 03:43 wolfspraul has quit [Read error: Connection reset by peer]
2013-10-13 04:02 xiangfu has joined #qi-hardware
2013-10-13 04:15 xiangfu has quit [Ping timeout: 245 seconds]
2013-10-13 04:27 xiangfu has joined #qi-hardware
2013-10-13 04:42 xiangfu has quit [Ping timeout: 245 seconds]
2013-10-13 04:49 xiangfu has joined #qi-hardware
2013-10-13 04:52 viric has quit [Ping timeout: 240 seconds]
2013-10-13 04:53 viric has joined #qi-hardware
2013-10-13 06:50 xiangfu has quit [Remote host closed the connection]
2013-10-13 08:13 kilae has joined #qi-hardware
2013-10-13 08:20 wej has joined #qi-hardware
2013-10-13 09:48 xiangfu has joined #qi-hardware
2013-10-13 12:09 dos1 has joined #qi-hardware
2013-10-13 12:37 pcercuei has joined #qi-hardware
2013-10-13 14:13 rz2k has joined #qi-hardware
2013-10-13 14:29 Jurting_pc2 has joined #qi-hardware
2013-10-13 15:21 mth has joined #qi-hardware
2013-10-13 15:57 paul_boddie has joined #qi-hardware
2013-10-13 16:48 cmbrgo has quit [Ping timeout: 246 seconds]
2013-10-13 16:52 xiangfu has quit [Remote host closed the connection]
2013-10-13 17:37 <apelete> ahah, just built jz-3.11 vanilla (without my musb hacks), and the pagealloc memory corruption appears in it too: http://paste.debian.net/57073/
2013-10-13 17:38 <larsc> now that is unexpected
2013-10-13 17:38 <apelete> tried to debug the thing this whole afternoon, and after reading backtraces in gdb I suspected that the problem was not in musb and I was right
2013-10-13 17:40 <apelete> I don't know where it's coming from exactly though, cause gdb won't let me break on the exact function that produce the memory corruption error :-(
2013-10-13 17:40 <larsc> you should build your kernel with KALLSYMS
2013-10-13 17:40 <larsc> then we'll see where it is triggered
2013-10-13 17:42 <apelete> yeah, forgot to build jz-3.11 with KALLSYMS, but I think I recorded a boot session with more information a few days ago
2013-10-13 17:43 <apelete> larsc: there you have it, recorded on october 10 -> http://paste.debian.net/57081/
2013-10-13 17:45 <larsc> hm, maybe your memory is bad
2013-10-13 17:45 <larsc> so it should all be 0xaa
2013-10-13 17:45 <larsc> but you got some 0xae
2013-10-13 17:45 <larsc> in there
2013-10-13 17:46 <apelete> larsc: what do you mean by "memory is bad" ?
2013-10-13 17:47 <apelete> you mean my nanonote may be faulty ?
2013-10-13 17:47 <apelete> the memory corruption only shows up if DEBUG_PAGEALLOC is enabled by the way
2013-10-13 17:47 <larsc> yes
2013-10-13 17:47 <larsc> it will only be detected if DEBUG_PAGEALLOC is enabled
2013-10-13 17:47 <larsc> cause there is a function checking if it is 0xaa
2013-10-13 17:50 <apelete> larsc: hmm, since I'm booting from sdcard, maybe it's the card that's faulty, what do you think ?
2013-10-13 17:50 <larsc> no
2013-10-13 17:50 <apelete> ah no, it must be the nanonote memory
2013-10-13 17:51 <apelete> pagealloc is done on memory, didn't think before asking :)
2013-10-13 17:51 <larsc> yep, there is one function that sets the memory to all 0xaa
2013-10-13 17:52 <larsc> when the memory is freed
2013-10-13 17:52 <larsc> once it is allocated again it checks whether it is still all 0xaa
2013-10-13 17:53 <apelete> yes, I think it's check_poison_mem() from debug-pagealloc.c you're talking about
2013-10-13 17:54 <apelete> still, that's bad. I hope the device won't be damaged though
2013-10-13 17:54 <apelete> I need it to continue hacking on musb :-(
2013-10-13 17:55 <larsc> it could also be a user after free somewhere
2013-10-13 17:58 <apelete> will ignore that problem for now, and focus on getting the glue layer init function right
2013-10-13 18:00 <apelete> larsc: this is what I'm trying to do currently:
2013-10-13 18:00 <apelete> /* The musb_platform_init() call:
2013-10-13 18:00 <apelete>  *   - sets the musb->isr
2013-10-13 18:00 <apelete>  *   - adjusts musb->mregs
2013-10-13 18:00 <larsc> ok
2013-10-13 18:00 <apelete> larsc: any advice on how to proceed here ?
2013-10-13 18:01 <larsc> So mregs should probably come out of the mmio platform_resource
2013-10-13 18:01 <larsc> same for the interrupt number (platform_get_irq())
2013-10-13 18:02 <larsc> not sure about what the isr is supposed to do exactly
2013-10-13 18:02 <larsc> or if there is some kind of musb default isr
2013-10-13 18:03 <apelete> <larsc> So mregs should probably come out of the mmio platform_resource
2013-10-13 18:03 <apelete> I don't get it, could you be more specific please ?
2013-10-13 18:07 <larsc> I think you are supposed to call musb_init_controller
2013-10-13 18:07 <larsc> hm, no actually
2013-10-13 18:07 <larsc> I think you don't need to do anything for mregs
2013-10-13 18:07 <larsc> as it should already be correct
2013-10-13 18:08 <apelete> so that leaves musb->isr to take care of
2013-10-13 18:09 <larsc> As far as I can see none of the existing drivers implement the init callback
2013-10-13 18:09 <larsc> ah, no they do
2013-10-13 18:10 <larsc> so some init functions add a offset to mregs
2013-10-13 18:10 <larsc> but I don't think we need to do this
2013-10-13 18:11 <larsc>  about what the isr is supposed to do exactly
2013-10-13 18:11 <larsc> 20:02 < larsc> or if there is some kind of musb default isr
2013-10-13 18:11 <larsc> ups
2013-10-13 18:12 <larsc> ux500_musb_interrupt seems to be a good example
2013-10-13 18:14 <apelete> will try that
2013-10-13 18:17 <apelete> larsc: ok, will try to get the interrupt settings right, then we'll see. thanks for the advices
2013-10-13 19:20 paul_boddie has left #qi-hardware ["Konversation terminated!"]
2013-10-13 20:41 <wpwrak> DocScrutinizer05: btw, some more EE design verification: http://lists.en.qi-hardware.com/pipermail/discussion/2013-October/010329.html
2013-10-13 20:54 kilae has quit [Quit: ChatZilla 0.9.90.1 [Firefox 24.0/20130910160258]]
2013-10-13 21:23 rz2k has quit []
2013-10-13 21:56 pcercuei has quit [Read error: Connection reset by peer]
2013-10-13 21:57 pcercuei has joined #qi-hardware
2013-10-13 22:21 zear has quit [Ping timeout: 260 seconds]
2013-10-13 22:28 zear has joined #qi-hardware
2013-10-13 22:48 <apelete> larsc mth: just added interruot regs initialisation in musb init function -> http://seketeli.fr/git/~apelete/qi-kernel.git/commit/?h=jz4740-musb&id=6de03fc47ef850a34b4bcdf1d63f7b9fb015b94a
2013-10-13 22:49 <apelete> but something's amiss -> http://paste.debian.net/57163/:
2013-10-13 22:49 <apelete> [    1.320000] musb-hdrc musb-hdrc.0.auto: can't request region for resource [mem 0x13040000-0x1304ffff]
2013-10-13 22:49 <apelete> [    1.330000] musb-hdrc: probe of musb-hdrc.0.auto failed with error -16
2013-10-13 22:50 <apelete> enabled a few printk to get a clearer picture -> http://paste.debian.net/57164/:
2013-10-13 22:50 <apelete> [    1.560000] bus: 'platform': really_probe: probing driver musb-hdrc with device musb-hdrc.0.auto
2013-10-13 22:50 <apelete> [    1.570000] musb-hdrc musb-hdrc.0.auto: can't request region for resource [mem 0x13040000-0x1304ffff]
2013-10-13 22:50 <apelete> [    1.580000] musb-hdrc: probe of musb-hdrc.0.auto failed with error -16
2013-10-13 22:52 <apelete> seems like there is still something wrong with platform data...
2013-10-13 22:56 <apelete> anyway, need some sleep right now, maybe we can discuss it in a few hours
2013-10-13 22:58 <pcercuei> this memory area has probably already been requested elsewhere
2013-10-13 23:13 Yogi_Bear has joined #qi-hardware
2013-10-13 23:14 <Yogi_Bear> invitation http://www.tatuuu.com.br ONLY QI-HARDWARE
2013-10-13 23:14 Yogi_Bear has quit [Client Quit]
2013-10-13 23:37 <DocScrutinizer05> wpwrak: sorry, just wake up
2013-10-13 23:38 <DocScrutinizer05> woke
2013-10-13 23:38 <DocScrutinizer05> ugh a wall of text
2013-10-13 23:47 pcercuei_ has joined #qi-hardware
2013-10-13 23:47 pcercuei has quit [Read error: Connection reset by peer]
2013-10-13 23:50 Jurting_pc2 has quit [Read error: Connection reset by peer]
2013-10-13 23:53 <DocScrutinizer05> wpwrak: sorry, takes a while to what that NCIS in TV and then wait til the coffeee kicks in
2013-10-13 23:53 <DocScrutinizer05> to watch*
2013-10-13 23:59 pcercuei_ has quit [Ping timeout: 240 seconds]