Thanks Pete. On Fri, 18 Jul 2014 11:37:54 +0200 Hans-Peter Jansen <h...@urpla.net> wrote:
> On Donnerstag, 17. Juli 2014 20:41:09 James B wrote: > > On Thu, 17 Jul 2014 13:36:47 +0700 > > > > For the receiving part, you can use a usb serial converter just fine! Actually for i4p all I need is a USB cable since the it includes FTDI converter already, inside the box. The only thing is that I need to setup a laptop sitting next to it so I can connect the cable and then log the output ... The i2u on the other hand doesn't have this (and it doesn't have any thing to connect an external serial probe unless I disassemble the casing, which I'm currently reluctant to do), so it's rather useless for debugging kernel issues. Update on the issue: I've decided to try another path - Russel King the ARM kernel maintainer has updated his cubox-i patches to work with 3.16-rc kernel (so now the cubox-i can run mainline kernel + his 40-odd patches). I have tried building 3.16-rc5 kernel with his patches (using "aufs3.15" branch, since aufs3.x-rcN doesn't work for me) and I still got the same issue so far. If it is a kernel bug when it would be a very subtle one to survive from 3.10.30 to 3.16-rc5, and build a very different configuration. If it is the cubox-i issue (e.g. DMA overwriting part of aufs variables) then I'm really really out of luck here :( But we won't know that until I can get the logging output intact, and I'm still working on it. cheers! -- James B <jamesbond3...@gmail.com> ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds
