From: Dan Malek <dmalek@jlc.net>
To: Gary Thomas <gdt@linuxppc.org>
Cc: Michael Meissner <meissner@cygnus.com>,
linuxppc-dev@lists.linuxppc.org,
Alois Fertl <alois_fertl@mucmot.muenchen.europe.mcd.mot.com>,
Johnnie Peters <jpeters@phx.mcd.mot.com>,
Cort Dougan <cort@persephone.cs.nmt.edu>
Subject: Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)
Date: Tue, 19 Jan 1999 13:54:06 -0500 [thread overview]
Message-ID: <36A4D4CE.9D957BA0@jlc.net> (raw)
In-Reply-To: XFMail.990119132838.gdt@linuxppc.org
Gary Thomas wrote:
> I like this idea. I'll see what I can do with it tonight.
Just copy the stuff I did for the 8xx/MBX ports in misc.c.
Add a #define string to the config process and pass it into
misc.c during compilation.
When a system has some type of environment strings you
could rummage around in there to find the default information.
An example can be found in the embedded 2.1.127 kernel tarball.
There are modifications in there that I have not yet added to
the real kernel. It reads serial EEPROM or other NVRAM storage
commonly found on the 8xx cards. Using any type of environment
string would allow system changes without recompiling.
Have fun :-).
-- Dan
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next prev parent reply other threads:[~1999-01-19 18:54 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-12 22:43 Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200) Michael Meissner
1999-01-13 20:10 ` Cort Dougan
1999-01-15 15:28 ` Alois Fertl
1999-01-15 20:10 ` Cort Dougan
1999-01-15 21:58 ` Michael Meissner
1999-01-15 22:04 ` Cort Dougan
1999-01-15 23:33 ` Michael Meissner
1999-01-18 8:51 ` Alois Fertl
1999-01-16 1:49 ` Johnnie Peters
1999-01-16 18:54 ` Dan Malek
1999-01-17 18:58 ` Cort Dougan
1999-01-18 9:21 ` Gabriel Paubert
1999-01-18 13:01 ` Gary Thomas
1999-01-18 16:54 ` Cort Dougan
1999-01-18 17:58 ` Michael Meissner
1999-01-19 22:43 ` Michael Meissner
1999-01-20 0:18 ` Johnnie Peters
1999-01-20 3:53 ` 3-button mouse Brent H Mundy
1999-01-20 22:20 ` Benjamin Herrenschmidt
1999-01-21 9:34 ` pre8(vger) kills button 3 on 1-button mouse Martin Costabel
1999-01-21 10:05 ` 3-button mouse fritzwe.linux
1999-01-20 15:21 ` Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200) Gary Thomas
1999-01-20 15:31 ` Johnnie Peters
1999-01-21 23:46 ` Johnnie Peters
1999-01-22 1:52 ` Michael Meissner
1999-01-22 2:04 ` Cort Dougan
1999-01-22 7:54 ` Gary Thomas
1999-01-22 8:19 ` Cort Dougan
1999-01-22 11:07 ` Gary Thomas
1999-01-22 15:17 ` Johnnie Peters
1999-02-01 15:58 ` Michael Meissner
1999-02-01 16:18 ` Gary Thomas
1999-02-04 19:09 ` Michael Meissner
1999-02-04 19:21 ` Gary Thomas
1999-02-04 20:23 ` Michael Meissner
[not found] ` <XFMail.990119102730.gdt@linuxppc.org>
1999-01-19 13:13 ` Michael Meissner
1999-01-19 13:28 ` Gary Thomas
1999-01-19 18:54 ` Dan Malek [this message]
1999-01-20 13:56 ` Loic Prylli
1999-01-18 18:11 ` Dan Malek
-- strict thread matches above, loose matches on Subject: below --
1999-01-16 2:23 Johnnie Peters
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=36A4D4CE.9D957BA0@jlc.net \
--to=dmalek@jlc.net \
--cc=alois_fertl@mucmot.muenchen.europe.mcd.mot.com \
--cc=cort@persephone.cs.nmt.edu \
--cc=gdt@linuxppc.org \
--cc=jpeters@phx.mcd.mot.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=meissner@cygnus.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;
as well as URLs for NNTP newsgroup(s).