<html>
<head>
</head>
<body class='hmmessage'><div dir='ltr'>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr">> Date: Sat, 24 Jan 2015 12:25:41 +0100<br><div>> From: daniel@makrotopia.org<br>> To: openwrt-devel@lists.openwrt.org<br>> Subject: Re: [OpenWrt-Devel] [PATCH] kirkwood: include kernel images and DTB in rootfs<br>> <br>> Hi Nathan,<br>> <br>> I don't believe that files inside UBIFS rootfs is the right approach for<br>> kernel and dtb. Given that the bootloader already supports UBI, why not<br>> use use a UBI volume instead?<br>> While U-Boot does support reading files from UBIFS, squashfs inside UBI<br>> volumes are not supported (squashfs inside read-only UBI volume is<br>> desirable if you like having the features depending on ROM+overlay such as<br>> failsafe and factory restore similar to other hardware targets).<br>> <br>> The Kirkwood target is part of OpenWrt for a long while already, longer<br>> than proper UBI support is around and long before wasting any thoughts<br>> about rootfs_overlay on NAND.<br>> Our current "state of the art" is to have squashfs read-only rootfs, just<br>> like on NOR devices, using UBIFS as rootfs_overlay (instead of JFFS2 on<br>> NOR). For bootloaders supporting UBI it makes sense to store kernel (and<br>> DTB) in a UBI volume and load them from there.<br>> Take a look at SysupgradeNAND and UbinizeImage targets in image.mk for<br>> examples.<br>> <br>> <br>> Cheers<br>> <br>> <br>> Daniel<br>> <br>> <br>Hi Daniel,<br><br>What I've been working on lately is to get OpenWrt running on a GuruPlug Server Plus I have <br>that has been mostly gathering dust up until now. I've updated to the latest uboot, patched for<br>Guruplug in a similar fashion to the Dockstar/IConnect/PogoPlug patches that can be found in<br>"package/boot/uboot-kirkwood/patches" (but w/o "second_stage_uboot"). All of those devices<br>have been patched to load the kernel image and DTB from the rootfs (based on the default<br>environment variables set up in the OpenWrt uboot), and I basically followed that model. What<br>I don't understand is how any of those would work out of the box unless you were to specify to<br>include the kernal image and DTB in the rootfs (which none of them do). I'm obviously missing<br>something. Any ideas?<br><br>The change you are suggesting would probably best be addressed by the target maintainer;<br>but I may experiment with it a bit too.<br><br>Thanks for the pointers!<br><br>Nathan<br><br>> <br>> On Fri, Jan 23, 2015 at 08:57:57PM -0800, Nathan Hintz wrote:<br>> > For SheevaPlug and GuruPlug devices.<br>> > <br>> > Signed-off-by: Nathan Hintz <nlhintz@hotmail.com><br>> > ---<br>> > target/linux/kirkwood/profiles/120-plug.mk | 3 +++<br>> > 1 file changed, 3 insertions(+)<br>> > <br>> > diff --git a/target/linux/kirkwood/profiles/120-plug.mk b/target/linux/kirkwood/profiles/120-plug.mk<br>> > index dcbda71..473955d 100644<br>> > --- a/target/linux/kirkwood/profiles/120-plug.mk<br>> > +++ b/target/linux/kirkwood/profiles/120-plug.mk<br>> > @@ -7,6 +7,7 @@<br>> > <br>> > define Profile/SHEEVAPLUG<br>> > NAME:=Globalscale Technologies SheevaPlug<br>> > + DEPENDS:=+@TARGET_ROOTFS_INCLUDE_KERNEL +@TARGET_ROOTFS_INCLUDE_ZIMAGE +@TARGET_ROOTFS_INCLUDE_DTB<br>> > PACKAGES:= \<br>> > kmod-mmc kmod-mvsdio kmod-usb2 kmod-usb-storage \<br>> > kmod-of-i2c kmod-i2c-core kmod-i2c-mv64xxx \<br>> > @@ -24,6 +25,7 @@ $(eval $(call Profile,SHEEVAPLUG))<br>> > <br>> > define Profile/SHEEVAPLUGSATA<br>> > NAME:=Globalscale Technologies eSATA SheevaPlug<br>> > + DEPENDS:=+@TARGET_ROOTFS_INCLUDE_KERNEL +@TARGET_ROOTFS_INCLUDE_ZIMAGE +@TARGET_ROOTFS_INCLUDE_DTB<br>> > PACKAGES:= \<br>> > kmod-mmc kmod-mvsdio kmod-usb2 kmod-usb-storage \<br>> > kmod-of-i2c kmod-i2c-core kmod-i2c-mv64xxx \<br>> > @@ -42,6 +44,7 @@ $(eval $(call Profile,SHEEVAPLUGSATA))<br>> > <br>> > define Profile/Guruplug-Server-Plus<br>> > NAME:=Globalscale Technologies Guruplug Server Plus<br>> > + DEPENDS:=+@TARGET_ROOTFS_INCLUDE_KERNEL +@TARGET_ROOTFS_INCLUDE_ZIMAGE +@TARGET_ROOTFS_INCLUDE_DTB<br>> > PACKAGES:= \<br>> > kmod-mmc kmod-mvsdio kmod-usb2 kmod-usb-storage \<br>> > kmod-of-i2c kmod-i2c-core kmod-i2c-mv64xxx \<br>> > -- <br>> > 1.9.3<br>> > _______________________________________________<br>> > openwrt-devel mailing list<br>> > openwrt-devel@lists.openwrt.org<br>> > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel<br>> _______________________________________________<br>> openwrt-devel mailing list<br>> openwrt-devel@lists.openwrt.org<br>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel<br></div></div>
</div></body>
</html>