From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mxs: Add NAND fdt and ramdisk partition to m28evk
Date: Fri, 4 Jan 2013 09:53:10 -0600 [thread overview]
Message-ID: <1357314790.666.0@snotra> (raw)
In-Reply-To: <201301040619.35821.marex@denx.de> (from marex@denx.de on Thu Jan 3 23:19:35 2013)
On 01/03/2013 11:19:35 PM, Marek Vasut wrote:
> Dear Scott Wood,
>
> > On 12/26/2012 12:26:13 PM, Otavio Salvador wrote:
> > > On Wed, Dec 26, 2012 at 1:13 AM, Marek Vasut <marex@denx.de>
> wrote:
> > > > Dear Otavio Salvador,
> > > >
> > > >> On Tue, Dec 25, 2012 at 11:08 PM, Marek Vasut <marex@denx.de>
> > >
> > > wrote:
> > > >> > Adjust the NAND partitioning layout so that there is a
> separate
> > >
> > > partition
> > >
> > > >> > for the ramdisk and fdt blob on the NAND.
> > > >> >
> > > >> > Signed-off-by: Marek Vasut <marex@denx.de>
> > > >>
> > > >> A partition for a ramdisk? maybe initramfs or initrd might be
> > >
> > > better?
> > >
> > > > Separate ramdisk (initrd).
> > >
> > > So maybe name it 'initrd' in the partition table?
> >
> > Why bias users against using initramfs instead?
>
> I'm not biasing users against initramfs, but some users simply want
> separate
> ramdisk outside of the kernel.
initramfs and initrd are different ways of formatting a ramdisk. It's
orthogonal to whether it's separate from the kernel image.
-Scott
next prev parent reply other threads:[~2013-01-04 15:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-26 1:08 [U-Boot] [PATCH] mxs: Add NAND fdt and ramdisk partition to m28evk Marek Vasut
2012-12-26 2:37 ` Otavio Salvador
2012-12-26 3:13 ` Marek Vasut
2012-12-26 18:26 ` Otavio Salvador
2013-01-03 23:42 ` Scott Wood
2013-01-04 0:49 ` Otavio Salvador
2013-01-04 15:53 ` Scott Wood
2013-01-04 5:19 ` Marek Vasut
2013-01-04 15:53 ` Scott Wood [this message]
2013-01-04 15:58 ` Marek Vasut
2013-01-04 16:01 ` Scott Wood
2013-01-04 16:04 ` Marek Vasut
2013-01-04 16:10 ` Scott Wood
2013-01-04 16:12 ` Marek Vasut
2013-01-05 16:42 ` Stefano Babic
2013-01-05 17:10 ` Marek Vasut
2013-01-05 17:18 ` Stefano Babic
2013-01-05 18:29 ` Marek Vasut
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=1357314790.666.0@snotra \
--to=scottwood@freescale.com \
--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