linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michel Lanners <mlan@cpu.lu>
To: chas@cmf.nrl.navy.mil
Cc: trini@kernel.crashing.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: nvram access in 2.3.48?
Date: Tue, 7 Mar 2000 23:11:14 +0100 (CET)	[thread overview]
Message-ID: <200003072211.XAA00471@piglet.grunz.lu> (raw)
In-Reply-To: <200003072157.QAA95728@borg.cmf.nrl.navy.mil>


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...

Thanks

Michel

PS I've not tried this patch yet, if anyone wants to go ahead...

-------------------------------------------------------------------------
Michel Lanners                 |  " Read Philosophy.  Study Art.
23, Rue Paul Henkes            |    Ask Questions.  Make Mistakes.
L-1710 Luxembourg              |
email   mlan@cpu.lu            |
http://www.cpu.lu/~mlan        |                     Learn Always. "


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-03-07 22:11 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 [this message]
2000-03-07 23:08       ` Tom Rini
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=200003072211.XAA00471@piglet.grunz.lu \
    --to=mlan@cpu.lu \
    --cc=chas@cmf.nrl.navy.mil \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=trini@kernel.crashing.org \
    /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).