From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] initramfs support through the initrd mechanism of u-boot
Date: Thu, 14 Jul 2011 16:40:31 +0200 [thread overview]
Message-ID: <4E1EFFDF.9090805@aribaud.net> (raw)
In-Reply-To: <C12A6026D660AE43A63DC2270B27335475BBA43B7B@GVW1154EXB.americas.hpqcorp.net>
Hi Thomas,
Le 14/07/2011 16:17, Cao, Da-Shi (EB-Presales-ZTE/HW-GZ) a ?crit :
> Currently the support of Linux initial file system by u-boot is a file system image through "initrd". I tweaked a little of both the "lib_arm/armlinux.c" and the initramfs of Linux (a gziped cpio) so that the initramfs file could be passed to the kernel.
Not sure why you need this. Can you not simply make a uImage of the
initrd and leave bootm untouched?
> For example: bootm c0008000 c1008000 will pass c1008000 to kernel as the start address of a initramfs.
That's already what's being done except for the format of the initramfs
IIUC, see <http://www.denx.de/wiki/view/DULG/LinuxRamdiskRoot> for instance.
> However in the Linux kernel it seems that it expects a physical address of initrd start, but u-boot passes a virtual address if MMU is enable.
> So a "virt_to_phy" should be used on the address before it is passed to the kernel.
Hmm... This should be a problem anyway, whether you pass a gzipped CPIO
or an U-Boot initrd image I guess. How do you get to this diagnostic?
> I'm currently using a Mini6410 (with Samsung S3C6410 CPU), an ARM board from China.
>
> Thanks,
> Thomas
Amicalement,
--
Albert.
next prev parent reply other threads:[~2011-07-14 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-14 14:17 [U-Boot] initramfs support through the initrd mechanism of u-boot Cao, Da-Shi
2011-07-14 14:40 ` Albert ARIBAUD [this message]
[not found] ` <C12A6026D660AE43A63DC2270B27335475BBA43F25@GVW1154EXB.americas.hpqcorp.net>
2011-07-16 9:25 ` Albert ARIBAUD
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E1EFFDF.9090805@aribaud.net \
--to=albert.u.boot@aribaud.net \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox