From 222af308ba200c645b888b8788f2d4f964b5aa5b Mon Sep 17 00:00:00 2001 From: Max Krummenacher Date: Mon, 2 Dec 2013 19:38:12 +0100 Subject: rootfs: don't populate /dev/ with static device files The Colibri VFxx console gobbles most output and sometimes provokes a kernel oops during boot, if a valid /dev/null is already part of the rootfs before mounting devtmpfs. The dynamically populated dev with devtmpfs / udev is enough. --- conf/machine/colibri-vf.conf | 9 ++++++++- recipes/images/files/colibri-vf/burnflash.tar.bz2 | Bin 5449 -> 5409 bytes 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/conf/machine/colibri-vf.conf b/conf/machine/colibri-vf.conf index d3fee40..aef2abe 100644 --- a/conf/machine/colibri-vf.conf +++ b/conf/machine/colibri-vf.conf @@ -23,4 +23,11 @@ IMAGE_FSTYPES ?= "tar.bz2 ext3 sdcard" SERIAL_CONSOLE = "115200 ttymxc0" MACHINE_FEATURES = "apm usbgadget usbhost vfat ext2 alsa touchscreen ethernet wifi bluetooth 3g" -EXTRA_IMAGEDEPENDS += "u-boot" \ No newline at end of file +EXTRA_IMAGEDEPENDS += "u-boot" + +#Workaround +#if there is /dev/null with correct major and minor number, the userspace RS232 +#console gobbles most of the output. Sometimes there is a kernel oops during +#init. So don't provide any device files during in the rootfs and let the +#tempdevfs do the work +USE_DEVFS = "1" diff --git a/recipes/images/files/colibri-vf/burnflash.tar.bz2 b/recipes/images/files/colibri-vf/burnflash.tar.bz2 index 5d0c554..5622a23 100644 Binary files a/recipes/images/files/colibri-vf/burnflash.tar.bz2 and b/recipes/images/files/colibri-vf/burnflash.tar.bz2 differ -- cgit v1.2.3