From: Tom Rini <trini@kernel.crashing.org>
To: Michel Lanners <mlan@cpu.lu>
Cc: chas@cmf.nrl.navy.mil, linuxppc-dev@lists.linuxppc.org
Subject: Re: nvram access in 2.3.48?
Date: Tue, 7 Mar 2000 16:08:35 -0700 [thread overview]
Message-ID: <20000307160835.H399@opus.bloom.county> (raw)
In-Reply-To: <200003072211.XAA00471@piglet.grunz.lu>; from mlan@cpu.lu on Tue, Mar 07, 2000 at 11:11:14PM +0100
On Tue, Mar 07, 2000 at 11:11:14PM +0100, Michel Lanners wrote:
> On 7 Mar, this message from Chas Williams echoed through cyberspace:
> >> Another weiredity I've come across in my 2.3 crusade: /dev/nvram
> >> doesn't seem to work anymore.
> >
> > this problem arises from a different source. the nvram driver in
> > drivers/macintosh needs to be converted to use the new driver initalization
> > scheme (like the driver in drivers/char/nvram.c)
> >
> > there were some posts about this about a month or so ago.
>
> Here is the essence:
>
> http://lists.linuxppc.org/listarcs/linuxppc-dev/200002/msg00079.html
>
> And to say I do read every message on this list...
Yeah, that did it (it forgot to change the CONFIG_MAC version). I'll pass
it along to BK.
I still think it would be a good idea to try and merge the two macintosh nvram
drivers into one tho.
---
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-03-07 23:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-07 21:29 nvram access in 2.3.48? Michel Lanners
2000-03-07 21:48 ` Tom Rini
2000-03-07 21:52 ` Michel Lanners
2000-03-07 22:15 ` Tom Rini
2000-03-07 21:53 ` Tom Rini
2000-03-07 21:57 ` Chas Williams
2000-03-07 22:11 ` Michel Lanners
2000-03-07 23:08 ` Tom Rini [this message]
2000-03-08 6:39 ` Michel Lanners
2000-03-08 7:08 ` Tony Mantler
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=20000307160835.H399@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=chas@cmf.nrl.navy.mil \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mlan@cpu.lu \
/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).