https://redmine.graphics-muse.org/https://redmine.graphics-muse.org/favicon.ico?16278048512013-03-23T22:46:50ZGraphics Muse Issue TrackerPiBox - Action Item #176: PiBox component rev: kernelhttps://redmine.graphics-muse.org/issues/176?journal_id=5612013-03-23T22:46:50ZHammelmjhammel@graphics-muse.org
<ul><li><strong>Tracker</strong> changed from <i>Bug</i> to <i>Action Item</i></li></ul><p>Initial tests with a build on 64-bit failed. The kernel couldn't find init. I'm using the same cmdline.txt that was used for the 3.2.27 branch. The root file systems is an ext3 partition and the cmdline.txt references it correctly. Not sure why the newer kernel doesn't work.</p> PiBox - Action Item #176: PiBox component rev: kernelhttps://redmine.graphics-muse.org/issues/176?journal_id=5622013-03-23T22:48:16ZHammelmjhammel@graphics-muse.org
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>10</i></li></ul> PiBox - Action Item #176: PiBox component rev: kernelhttps://redmine.graphics-muse.org/issues/176?journal_id=5682013-03-29T01:09:01ZHammelmjhammel@graphics-muse.org
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Low</i></li><li><strong>% Done</strong> changed from <i>10</i> to <i>20</i></li><li><strong>Severity</strong> changed from <i>03 - Medium</i> to <i>04 - Low</i></li></ul><p>The 3.6.y kernel builds fine and boots, but it doesn't support my wireless keyboard. It also seems to mix the init processing with some usb probing, which causes some things not to happen, like the USB wifi not to get loaded because the USB has not enumerated the dongle when mdev is starting up.</p>
<p>The latter issue might be an "early init" configuration item. I seem to have a vague recollection about hearing about such a feature in the kernel. The former I don't know what the problem is. I ran meld on the two kernel configs (3.6.y and 3.2.27) and dont' see anything missing from the new kernels config that was in the old kernel config. But there are lots of changes so maybe I missed something.</p>
<p>For now, I'm falling back to 3.2.27 until I get a public release of PiBox out the door.</p> PiBox - Action Item #176: PiBox component rev: kernelhttps://redmine.graphics-muse.org/issues/176?journal_id=9282014-01-18T22:22:53ZHammelmjhammel@graphics-muse.org
<ul><li><strong>% Done</strong> changed from <i>20</i> to <i>50</i></li></ul><p>Ran a test today with the kernel from the Raspberry Pi kernel repo on github using GIT id rpi-3.10.y. This was built using the current PiBox xcc, based on Crosstool-NG 1.15.2. The rootfs is the same with only a minor change to cleaning up the lib/modules/.../ symlinks to support kernel versions that don't match the kernel release names.</p>
<p>The system boots just fine. In fact, it seems to boot rather fast in comparison to the 3.2.27 tree. Also, the keyboard is available on boot (at least with the initial test). Not sure if that was a fluke or they fixed something with the USB handling.</p>
<p>I will checkin the changes to buildroot.mk and the new kernel configuration file for rpi-3.10.y. I'll also add commented out configuration support for the new kernel, but won't make it the default yet. I need to verify that all required components (re: opkgs) are working with the new kernel first.</p> PiBox - Action Item #176: PiBox component rev: kernelhttps://redmine.graphics-muse.org/issues/176?journal_id=9292014-01-18T23:06:12ZHammelmjhammel@graphics-muse.org
<ul></ul><p>A quick check shows that the mdev handler (usbhandler.conf/usbhandler.sh) is not getting called, so the network driver (which <strong>is</strong> compiled and available) is not getting loaded.</p> PiBox - Action Item #176: PiBox component rev: kernelhttps://redmine.graphics-muse.org/issues/176?journal_id=9352014-01-19T21:20:51ZHammelmjhammel@graphics-muse.org
<ul></ul>Stuff to review for mdev:
<ol>
<li><a class="external" href="http://git.busybox.net/busybox/plain/docs/mdev.txt">http://git.busybox.net/busybox/plain/docs/mdev.txt</a></li>
<li><a class="external" href="https://wiki.gentoo.org/wiki/Mdev">https://wiki.gentoo.org/wiki/Mdev</a></li>
<li><a class="external" href="http://free-electrons.com/doc/mdev-lab.pdf">http://free-electrons.com/doc/mdev-lab.pdf</a></li>
<li><a class="external" href="http://www.linuxfromscratch.org/clfs/view/clfs-3.0/mips/bootscripts/mdev.html">http://www.linuxfromscratch.org/clfs/view/clfs-3.0/mips/bootscripts/mdev.html</a></li>
</ol>
<p>Also, add usr/bin/mdevdebug.sh (from my sandbox) and add it to /etc/mdev.conf as the first command that executes and falls through to the other commands. This should really be an opkg that patches mdev.conf on install and unpatches on uninstall.</p> PiBox - Action Item #176: PiBox component rev: kernelhttps://redmine.graphics-muse.org/issues/176?journal_id=9452014-01-22T04:04:48ZHammelmjhammel@graphics-muse.org
<ul></ul><p>Inittab tries to mount /proc/bus/usb as usbfs. This directory doesn't exist with this kernel using the default RPi kernel config (not my config, the default one).</p>
<p>The reason no mdev-based driver loading occurs is because the usbfs isn't mounted. It's deprecated after kernel 3.5. See this discussion:<br /><a class="external" href="http://askubuntu.com/questions/326597/enabling-usbfs-in-ubuntu">http://askubuntu.com/questions/326597/enabling-usbfs-in-ubuntu</a></p>
<p>One solution that seems to also be deprecated was CONFIG_USB_DEVICE_CLASS (it's not in the 3.10.25 configuration). See <a class="external" href="http://www.libusb.org/ticket/119">http://www.libusb.org/ticket/119</a></p>
<p>I might get more info from <a class="external" href="https://wiki.gentoo.org/wiki/Mdev/Automount_USB">https://wiki.gentoo.org/wiki/Mdev/Automount_USB</a></p> PiBox - Action Item #176: PiBox component rev: kernelhttps://redmine.graphics-muse.org/issues/176?journal_id=9472014-01-24T03:24:56ZHammelmjhammel@graphics-muse.org
<ul></ul>Possible alternatives to mdev (that can call mdev):
<ul>
<li><a class="external" href="http://www.skarnet.org/software/s6-linux-utils/s6-devd.html">http://www.skarnet.org/software/s6-linux-utils/s6-devd.html</a></li>
<li><a class="external" href="http://git.r-36.net/nldev/">http://git.r-36.net/nldev/</a><br />Both listen to the netlink socket for events and pass them to mdev.</li>
</ul> PiBox - Action Item #176: PiBox component rev: kernelhttps://redmine.graphics-muse.org/issues/176?journal_id=9802014-02-09T22:51:03ZHammelmjhammel@graphics-muse.org
<ul><li><strong>Priority</strong> changed from <i>Low</i> to <i>Immediate</i></li><li><strong>Severity</strong> changed from <i>04 - Low</i> to <i>03 - Medium</i></li></ul> PiBox - Action Item #176: PiBox component rev: kernelhttps://redmine.graphics-muse.org/issues/176?journal_id=9952014-02-22T16:19:49ZHammelmjhammel@graphics-muse.org
<ul><li><strong>Target version</strong> changed from <i>1.0 - Atreides</i> to <i>0.8.0</i></li></ul><p>Getting close to making this work so retarget for 0.8.0.</p> PiBox - Action Item #176: PiBox component rev: kernelhttps://redmine.graphics-muse.org/issues/176?journal_id=10002014-02-27T04:22:53ZHammelmjhammel@graphics-muse.org
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Closed</i></li><li><strong>% Done</strong> changed from <i>50</i> to <i>100</i></li></ul><p>After finding a working branch from the RPi kernel repo, which is not the latest but is merge with kernel.org's 3.10.31, and updating the rootfs to properly load usb drivers using lsusb as a front end in an init script, PiBox is now rev'd to a 3.10.x kernel.</p>
<p>This means we can integrate with the mainline fbtft drivers for the touchscreen display and can properly support BLE.</p>
<p>This issue can be closed.</p>