| Message ID | 1356484120-15740-1-git-send-email-marex@denx.de |
|---|---|
| State | Awaiting Upstream |
| Delegated to: | Stefano Babic |
| Headers | show |
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? -- Otavio Salvador O.S. Systems E-mail: otavio@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
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). Best regards, Marek Vasut
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? -- Otavio Salvador O.S. Systems E-mail: otavio@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
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? -Scott
On Thu, Jan 3, 2013 at 9:42 PM, Scott Wood <scottwood@freescale.com> wrote: > 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 have nothing against initramfs or any other name, I just think 'ramdisk' is confusing (but it might be just my impression) that's why I commented in the patch so others can comment on it too. -- Otavio Salvador O.S. Systems E-mail: otavio@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
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. Best regards, Marek Vasut
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
On 01/03/2013 06:49:05 PM, Otavio Salvador wrote: > On Thu, Jan 3, 2013 at 9:42 PM, Scott Wood <scottwood@freescale.com> > wrote: > > 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 have nothing against initramfs or any other name, I just think > 'ramdisk' is confusing (but it might be just my impression) that's why > I commented in the patch so others can comment on it too. How is an abbreviation for "initial ramdisk" less confusing than "ramdisk"? -Scott
Dear Scott Wood, > 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. True, so what is the discussion here about anyway? I fail to see the point -- is there a problem with the patch or not? If not, please apply for .01 release. Best regards, Marek Vasut
On 01/04/2013 09:58:28 AM, Marek Vasut wrote: > Dear Scott Wood, > > > 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. > > True, so what is the discussion here about anyway? I fail to see the > point -- is > there a problem with the patch or not? If not, please apply for .01 > release. I have no problem with it. My point was that "ramdisk" is a better name than "initrd". -Scott
Dear Scott Wood, > On 01/04/2013 09:58:28 AM, Marek Vasut wrote: > > Dear Scott Wood, > > > > > 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. > > > > True, so what is the discussion here about anyway? I fail to see the > > point -- is > > there a problem with the patch or not? If not, please apply for .01 > > release. > > I have no problem with it. My point was that "ramdisk" is a better > name than "initrd". The patch contains "ramdisk" ... go look at the patch please. Best regards, Marek Vasut
On 01/04/2013 10:04:06 AM, Marek Vasut wrote: > Dear Scott Wood, > > > On 01/04/2013 09:58:28 AM, Marek Vasut wrote: > > > Dear Scott Wood, > > > > > > > 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. > > > > > > True, so what is the discussion here about anyway? I fail to see > the > > > point -- is > > > there a problem with the patch or not? If not, please apply for > .01 > > > release. > > > > I have no problem with it. My point was that "ramdisk" is a better > > name than "initrd". > > The patch contains "ramdisk" ... go look at the patch please. Sigh... I said I have no problem with the patch. I was responding to Otavio's suggestion to change it to initrd. -Scott
Dear Scott Wood, > On 01/04/2013 10:04:06 AM, Marek Vasut wrote: > > Dear Scott Wood, > > > > > On 01/04/2013 09:58:28 AM, Marek Vasut wrote: > > > > Dear Scott Wood, > > > > > > > > > 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. > > > > > > > > True, so what is the discussion here about anyway? I fail to see > > > > the > > > > > > point -- is > > > > there a problem with the patch or not? If not, please apply for > > > > .01 > > > > > > release. > > > > > > I have no problem with it. My point was that "ramdisk" is a better > > > name than "initrd". > > > > The patch contains "ramdisk" ... go look at the patch please. > > Sigh... I said I have no problem with the patch. I was responding to > Otavio's suggestion to change it to initrd. Sigh ... I got lost in this (pointless) discussion, sorry. Best regards, Marek Vasut
On 26/12/2012 02:08, Marek Vasut 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> > Cc: Detlev Zundel <dzu@denx.de> > Cc: Stefano Babic <sbabic@denx.de> > Cc: Wolfgang Denk <wd@denx.de> > --- > include/configs/m28evk.h | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/include/configs/m28evk.h b/include/configs/m28evk.h > index b49ec8c..36ce672 100644 > --- a/include/configs/m28evk.h > +++ b/include/configs/m28evk.h > @@ -178,6 +178,8 @@ > "512k(environment)," \ > "512k(redundant-environment)," \ > "4m(kernel)," \ > + "128k(fdt)," \ > + "8m(ramdisk)," \ > "-(filesystem)" > #else > #define CONFIG_ENV_IS_NOWHERE > Discussion in the thread was quite off-topic - but at the end, there is nothing for not applying it. Applied to u-boot-imx, thanks. Best regards, Stefano Babic
Dear Stefano Babic, > On 26/12/2012 02:08, Marek Vasut 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> > > Cc: Detlev Zundel <dzu@denx.de> > > Cc: Stefano Babic <sbabic@denx.de> > > Cc: Wolfgang Denk <wd@denx.de> > > --- > > > > include/configs/m28evk.h | 2 ++ > > 1 file changed, 2 insertions(+) > > > > diff --git a/include/configs/m28evk.h b/include/configs/m28evk.h > > index b49ec8c..36ce672 100644 > > --- a/include/configs/m28evk.h > > +++ b/include/configs/m28evk.h > > @@ -178,6 +178,8 @@ > > > > "512k(environment)," \ > > "512k(redundant-environment)," \ > > "4m(kernel)," \ > > > > + "128k(fdt)," \ > > + "8m(ramdisk)," \ > > > > "-(filesystem)" > > > > #else > > #define CONFIG_ENV_IS_NOWHERE > > Discussion in the thread was quite off-topic - but at the end, there is > nothing for not applying it. > > Applied to u-boot-imx, thanks. Thanks, will this make it for 2013.01 please ? > Best regards, > Stefano Babic Best regards, Marek Vasut
On 05/01/2013 18:10, Marek Vasut wrote: > Dear Stefano Babic, > >> On 26/12/2012 02:08, Marek Vasut 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> >>> Cc: Detlev Zundel <dzu@denx.de> >>> Cc: Stefano Babic <sbabic@denx.de> >>> Cc: Wolfgang Denk <wd@denx.de> >>> --- >>> >>> include/configs/m28evk.h | 2 ++ >>> 1 file changed, 2 insertions(+) >>> >>> diff --git a/include/configs/m28evk.h b/include/configs/m28evk.h >>> index b49ec8c..36ce672 100644 >>> --- a/include/configs/m28evk.h >>> +++ b/include/configs/m28evk.h >>> @@ -178,6 +178,8 @@ >>> >>> "512k(environment)," \ >>> "512k(redundant-environment)," \ >>> "4m(kernel)," \ >>> >>> + "128k(fdt)," \ >>> + "8m(ramdisk)," \ >>> >>> "-(filesystem)" >>> >>> #else >>> #define CONFIG_ENV_IS_NOWHERE >> >> Discussion in the thread was quite off-topic - but at the end, there is >> nothing for not applying it. >> >> Applied to u-boot-imx, thanks. > > Thanks, will this make it for 2013.01 please ? Of course, it is part of my next pull request. Best regards, Stefano Babic
Dear Stefano Babic, > On 05/01/2013 18:10, Marek Vasut wrote: > > Dear Stefano Babic, > > > >> On 26/12/2012 02:08, Marek Vasut 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> > >>> Cc: Detlev Zundel <dzu@denx.de> > >>> Cc: Stefano Babic <sbabic@denx.de> > >>> Cc: Wolfgang Denk <wd@denx.de> > >>> --- > >>> > >>> include/configs/m28evk.h | 2 ++ > >>> 1 file changed, 2 insertions(+) > >>> > >>> diff --git a/include/configs/m28evk.h b/include/configs/m28evk.h > >>> index b49ec8c..36ce672 100644 > >>> --- a/include/configs/m28evk.h > >>> +++ b/include/configs/m28evk.h > >>> @@ -178,6 +178,8 @@ > >>> > >>> "512k(environment)," \ > >>> "512k(redundant-environment)," \ > >>> "4m(kernel)," \ > >>> > >>> + "128k(fdt)," \ > >>> + "8m(ramdisk)," \ > >>> > >>> "-(filesystem)" > >>> > >>> #else > >>> #define CONFIG_ENV_IS_NOWHERE > >> > >> Discussion in the thread was quite off-topic - but at the end, there is > >> nothing for not applying it. > >> > >> Applied to u-boot-imx, thanks. > > > > Thanks, will this make it for 2013.01 please ? > > Of course, it is part of my next pull request. Thanks! Best regards, Marek Vasut
diff --git a/include/configs/m28evk.h b/include/configs/m28evk.h index b49ec8c..36ce672 100644 --- a/include/configs/m28evk.h +++ b/include/configs/m28evk.h @@ -178,6 +178,8 @@ "512k(environment)," \ "512k(redundant-environment)," \ "4m(kernel)," \ + "128k(fdt)," \ + "8m(ramdisk)," \ "-(filesystem)" #else #define CONFIG_ENV_IS_NOWHERE
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> Cc: Detlev Zundel <dzu@denx.de> Cc: Stefano Babic <sbabic@denx.de> Cc: Wolfgang Denk <wd@denx.de> --- include/configs/m28evk.h | 2 ++ 1 file changed, 2 insertions(+)