Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Thiemo Seufer <ths@networkno.de>
To: Franck Bui-Huu <vagabon.xyz@gmail.com>
Cc: linux-mips@linux-mips.org, anemo@mba.ocn.ne.jp,
	ralf@linux-mips.org, yoichi_yuasa@tripeaks.co.jp
Subject: Re: [PATCH 6/6] setup.c: use early_param() for early command line parsing
Date: Tue, 8 Aug 2006 16:14:09 +0100	[thread overview]
Message-ID: <20060808151409.GA1177@networkno.de> (raw)
In-Reply-To: <44D898FE.7080006@innova-card.com>

Franck Bui-Huu wrote:
> Thiemo Seufer wrote:
> > Franck Bui-Huu wrote:
> >> There's no point to rewrite some logic to parse command line
> >> to pass initrd parameters or to declare a user memory area.
> >> We could use instead parse_early_param() that does the same
> >> thing.
> >>
> >> NOTE ! This patch also changes the initrd semantic. Old code
> >> was expecting "rd_start=xxx rd_size=xxx" which uses two
> >> parameters. Now the code expects "initrd=xxx@yyy" which is
> >> really simpler to parse and to use. No default config files
> >> use these parameters anyways but not sure for bootloader's
> >> users...
> > 
> > This code is there precisely because most mips bootloaders use
> > rd_start/rd_size.
> 
> OK, I guess we have to stick with this weird semantic...
> 
> > It also is IMHO a bad idea to overload the
> > semantics of initrd= with both file names and memory locations.
> 
> I wasn't aware of any file name usages. Can you give a pointer ?

Documentation/initrd.txt
Documentation/filesystems/ramfs-rootfs-initramfs.txt


Thiemo

  reply	other threads:[~2006-08-08 15:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-08 12:48 [patch 0/6] cleanup setup.c Franck Bui-Huu
2006-08-08 12:48 ` [PATCH 1/6] setup.c: cleanup bootmem_init() Franck Bui-Huu
2006-08-08 12:48 ` [PATCH 2/6] setup.c: move initrd code inside dedicated functions Franck Bui-Huu
2006-08-08 12:48 ` [PATCH 3/6] setup.c: remove useless includes Franck Bui-Huu
2006-08-08 12:48 ` [PATCH 4/6] setup.c: do not inline functions Franck Bui-Huu
2006-08-08 12:48 ` [PATCH 5/6] setup.c: remove MAXMEM macro Franck Bui-Huu
2006-08-08 12:48 ` [PATCH 6/6] setup.c: use early_param() for early command line parsing Franck Bui-Huu
2006-08-08 12:56   ` Thiemo Seufer
2006-08-08 14:00     ` Franck Bui-Huu
2006-08-08 15:14       ` Thiemo Seufer [this message]
2006-08-09  8:15         ` Franck Bui-Huu
2006-08-09 11:12           ` Thiemo Seufer
2006-08-08 16:05       ` Atsushi Nemoto
2006-08-09  8:21         ` Franck Bui-Huu
2006-08-09 14:25           ` Atsushi Nemoto
2006-08-11  7:36             ` Franck Bui-Huu
2006-08-11 14:36               ` Atsushi Nemoto
  -- strict thread matches above, loose matches on Subject: below --
2006-08-09 14:52 [patch 0/6] cleanup setup.c (take #2) Franck Bui-Huu
2006-08-09 14:52 ` [PATCH 6/6] setup.c: use early_param() for early command line parsing Franck Bui-Huu
2006-08-11 11:55   ` Franck Bui-Huu
2006-08-11 15:51 cleanup setup.c (take #3) Franck Bui-Huu
2006-08-11 15:51 ` [PATCH 6/6] setup.c: use early_param() for early command line parsing Franck Bui-Huu

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=20060808151409.GA1177@networkno.de \
    --to=ths@networkno.de \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=vagabon.xyz@gmail.com \
    --cc=yoichi_yuasa@tripeaks.co.jp \
    /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