Re: Mount SD card partition as rootfs

"Sartakov A. Vasily" <[email protected]>
Newsgroups gmane.comp.micro-kernel.l4.devel
Message-ID <[email protected]>
Hi. 
If you didn't change anything in source of L4Linux, you can't use MMC. The l4linux contain small amount of arm board support code (arch/arm/omap2/), so initial code which add mmc and other devices doesn't exist. 

04.07.2012, в 18:21, Pierre Larus <[email protected]>:

> Hi,
> 
> I am currently trying to mount a SD card partition as L4Linux rootfs.
> I am using a beagleboard. The first flash card partition (fat32) is mounted by U-boot and contains the L4Linux kernel . The second partition (ext3) contains the rootfs.
> I have compiled L4Linux to support SD card et Ext3 filesystem and configured L4 to give to L4Linux access to the MMC device through a virtual bus.
> But the SD card partitions are not available in L4Linux. Do I forget something ?
> Regards,
> 
> Pierre Larus
> 
> -------------------------------------------------------------------
> entry l4LinuxUcos
>       kernel    fiasco -serial_esc
>       roottask    moe rom/l4lx.cfg
>       module    l4re
>       module    ned
>       module    io
>       module    l4lx.cfg
>       module    vmlinuz.arm
>       module    beagle.devs
>       module    beagle.io
> -------------------------------------------------------------------
> hw-root
> {
>     # MultiMediaCard 1 2 3
>     mmc => new Device()
>     {
>         .hid = "OMAP_HSMMC";
>         new-res Mmio(0x4809c000 .. 0x4809dfff);
>         new-res Mmio(0x480b4000 .. 0x480b5fff);
>         new-res Mmio(0x480ad000 .. 0x480aefff);
>     }
> }
> 
> mmiodev => new System_bus()
> {
>     mmc => wrap(hw-root.mmc);
> }
> -------------------------------------------------------------------
> local lxname = "vmlinuz.arm";
> local DeviceFile = "beagle.devs"
> local IOFile = "beagle.io"
> local loader = L4.default_loader;
> 
> local io_bus = loader:new_channel();
> 
> loader:start({
>         caps = {
>              mmiodev = io_bus:svr(),
>              icu = L4.Env.icu,
>              sigma0 = L4.cast(L4.Proto.Factory, L4.Env.sigma0):create(L4.Proto.Sigma0),
> },
>               },
>          "rom/io -vv rom/" .. DeviceFile .. " rom/" .. IOFile);
> 
> loader:start(
>   { caps = {
>       vbus = io_bus,
>       icu = L4.Env.icu,
>       log = L4.Env.log:m("rws"),
>     },
>     l4re_dbg = L4.Dbg.Warn,
>     log = { "l4linux", "yellow" },
>   },
>     "rom/" .. lxname .. " root=/dev/mmcblk0p2 rw rootfstype=ext3 init=/sbin/init console=ttyLv0");
> ---------------------------------------------------------------------------------------
> ...
> L4 serial driver
> ttyLv0 at MMIO 0x1 (irq = 210) is a L4
> L4 shared mem serial driver
> l4cdds: No name given, not starting.
> brd: module loaded
> l4bdds: No name given, not starting.
> mousedev: PS/2 mouse device common for all mice
> sdhci: Secure Digital Host Controller Interface driver
> sdhci: Copyright(c) Pierre Ossman
> TCP cubic registered
> NET: Registered protocol family 17
> VFS: Cannot open root device "mmcblk0p2" or unknown-block(0,0)
> Please append a correct "root=" boot option; here are the available partitions:
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
> [<00129d68>] (unwind_backtrace+0x0/0xf0) from [<00335858>] (panic+0x58/0x178)
> [<00335858>] (panic+0x58/0x178) from [<00100aa0>] (mount_block_root+0x1d4/0x294)
> [<00100aa0>] (mount_block_root+0x1d4/0x294) from [<00100e24>] (prepare_namespace
> +0x164/0x1bc)
> [<00100e24>] (prepare_namespace+0x164/0x1bc) from [<00100794>] (kernel_init+0xe4
> /0x118)
> [<00100794>] (kernel_init+0xe4/0x118) from [<00122410>] (kernel_thread_exit+0x0/
> 0x8)
> panic: going to sleep forever, bye
> l4linux | panic: going to sleep forever, bye
> _______________________________________________
> l4-hackers mailing list
> [email protected]
> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

_______________________________________________
l4-hackers mailing list
[email protected]
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.