Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "William J. Earl" <wje@fir.engr.sgi.com>
To: Alex deVries <adevries@engsoc.carleton.ca>
Cc: SGI Linux <linux@cthulhu.engr.sgi.com>
Subject: Re: Boot flags in the kernel.
Date: Mon, 26 Jan 1998 09:36:43 -0800	[thread overview]
Message-ID: <199801261736.JAA08190@fir.engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.3.95.980126004413.18537A-100000@lager.engsoc.carleton.ca>

Alex deVries writes:
 > 
 > I'm not sure if what I'm trying to do is possible. I'm trying to implement
 > the same rootflags that are passwd within the kernel image in i386 into
 > the MIPS kernel. 
 > 
 > In i386 there's a portion of the boot image reserved for these flags;
 > they're things like console type, initial filesystem, initial ramdisk
 > location, etc.  
 > 
 > It's traditionally been more important to have this feature in i386
 > because there wasn't anything nice like the PROMs on MIPS or Sparcs.
 > 
 > But, there _is a good reason to have it; for install or rescue images it's
 > nice to be able to boot with compressed initial ramdisk within the same
 > boot image without having to pass the ramdisk offset on command line
 > manually.
 > 
 > Where in the kernel would we put this data?

       I am sure where you should put it, but bear in mind that the
command line options and environment are passed to the kernel much as
if it were a user main program (as argc, argv, and envp, in $a0, $a1,
and $a2), by sash or the PROM.  You can get things like the console
variable that way (console=g means textport and console=d means
serial console). 

  reply	other threads:[~1998-01-26 17:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-01-26  6:05 Boot flags in the kernel Alex deVries
1998-01-26 17:36 ` William J. Earl [this message]
1998-01-26 22:47 ` ralf
1998-01-26 23:49   ` Alex deVries
1998-01-27  0:08     ` ralf

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=199801261736.JAA08190@fir.engr.sgi.com \
    --to=wje@fir.engr.sgi.com \
    --cc=adevries@engsoc.carleton.ca \
    --cc=linux@cthulhu.engr.sgi.com \
    /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