From: Sven Luther <sven.luther@wanadoo.fr>
To: Mark Guertin <mguertin@macdiscussion.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Would setting the CONFIG_RTC option break the powerpc kernel on your machine ?
Date: Mon, 22 Dec 2003 18:27:36 +0100 [thread overview]
Message-ID: <20031222172736.GA9999@iliana> (raw)
In-Reply-To: <A8565590-34A0-11D8-A35A-000A95DC1AB2@macdiscussion.com>
On Mon, Dec 22, 2003 at 12:02:43PM -0500, Mark Guertin wrote:
>
> On 22-Dec-03, at 11:48 AM, Sven Luther wrote:
>
> >>Does it really have OpenFirmware?
> >
> >Yeah, and i even have the source of it (not free software though). OF
> >coding is a nightmare though.
>
> It's not really OpenFirmware ... it's SmartFirmware is it not? it's
Yes, it is based on SmartFirmware.
> Slightly OT, but Sven, is there access to /dev/nvram available yet on
No, there is no /dev/nvram, i don't believe there ever will be, not
sure. I think there is no physical nvram for such a device in the
hardware.
> pegasos? I've still got a forth bootloader menu somewhere here that I
> made for the pegasos, which I've never been able to load (without
> massive typing at SF prompt)...but my pegasos is non functional so I
> may find it this week and email the file to you to fight with :)
Well, my own solution to this, is to implement the boot loader thingy
directly in the OS/SF/whatever. My plan is to have a function to read a
file on disk, which would contain a grub like format (i like it more
than yaboot/lilo like format) and construct a boot-loader menu from
this.
Friendly,
Sven Luther
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-12-22 17:27 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031216105656.GA5291@iliana>
[not found] ` <1071642293.753.414.camel@gaston>
[not found] ` <200312170717.36564.jel@ntlworld.com>
[not found] ` <1071646057.6370.482.camel@gaston>
2003-12-17 9:51 ` Would setting the CONFIG_RTC option break the powerpc kernel on your machine ? Sven Luther
2003-12-17 10:27 ` Geert Uytterhoeven
2003-12-17 15:45 ` Segher Boessenkool
2003-12-17 16:18 ` Geert Uytterhoeven
2003-12-17 17:16 ` Segher Boessenkool
2003-12-17 16:47 ` Tom Rini
2003-12-17 16:56 ` Sven Luther
2003-12-17 17:06 ` Tom Rini
2003-12-17 17:10 ` Sven Luther
2003-12-17 17:24 ` Tom Rini
2003-12-19 11:40 ` Sven Luther
2003-12-19 16:28 ` Tom Rini
2003-12-22 13:45 ` Sven Luther
2003-12-22 16:10 ` Tom Rini
2003-12-22 16:26 ` Sven Luther
2003-12-22 16:33 ` Tom Rini
2003-12-22 16:48 ` Sven Luther
2003-12-22 16:59 ` Tom Rini
2003-12-22 17:02 ` Mark Guertin
2003-12-22 17:27 ` Sven Luther [this message]
2004-01-07 6:54 ` Sven Luther
2004-01-07 7:22 ` Benjamin Herrenschmidt
2004-01-07 7:43 ` Sven Luther
2004-01-07 7:47 ` Sven Luther
2004-01-07 8:30 ` Benjamin Herrenschmidt
2004-01-07 9:53 ` Sven Luther
2004-01-07 10:44 ` Benjamin Herrenschmidt
2004-01-07 10:54 ` Sven Luther
2004-01-07 11:47 ` Benjamin Herrenschmidt
2004-01-07 11:53 ` Sven Luther
2004-01-07 18:34 ` Tom Rini
2004-01-07 7:51 ` Ethan Benson
2004-01-07 11:27 ` Volunteer needed : " Sven Luther
2004-01-07 12:28 ` Ethan Benson
2004-01-07 14:47 ` Sven Luther
2004-01-08 7:27 ` Ethan Benson
2004-01-08 15:53 ` Tom Rini
2004-01-08 17:47 ` Sven Luther
2004-01-08 21:53 ` Benjamin Herrenschmidt
2004-01-08 21:57 ` Sven Luther
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=20031222172736.GA9999@iliana \
--to=sven.luther@wanadoo.fr \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mguertin@macdiscussion.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).