nvram access in 2.3.48?

nvram access in 2.3.48?

[Michel Lanners]

Hi list,

Another weiredity I've come across in my 2.3 crusade: /dev/nvram
doesn't seem to work anymore.

I've enabled nvram support under the char devices, but the device
doesn't seem to get included in the kernel image: kmod tries to load a
module for char-major-10-144 upon access, but it's not built as a
module...

Anybody experienced this, and wants to spare me a few hours chasing
that problem?

Thanks

Michel

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

Re: nvram access in 2.3.48?

[Tom Rini]

On Tue, Mar 07, 2000 at 10:29:45PM +0100, Michel Lanners wrote:

> Another weiredity I've come across in my 2.3 crusade: /dev/nvram
> doesn't seem to work anymore.

Near as I can tell (and I'm about to try this and then see if bk will pass
it along happily) is that all the calls to nvram_init have been changed to
pmac_nvram_init.

---
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

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

Re: nvram access in 2.3.48?

[Michel Lanners]

On   7 Mar, this message from Tom Rini echoed through cyberspace:
> On Tue, Mar 07, 2000 at 10:29:45PM +0100, Michel Lanners wrote:
>
>> Another weiredity I've come across in my 2.3 crusade: /dev/nvram
>> doesn't seem to work anymore.
>
> Near as I can tell (and I'm about to try this and then see if bk will pass
> it along happily) is that all the calls to nvram_init have been changed to
> pmac_nvram_init.

I've just done a quick grep through kernel code, and found lots of
nvram code in at least three files, and decided it was too late to
follow all of them ;-)

That was in a drivers/char file, under drivers/macintosh, and under
arch/ppc, if I rember right....

Michel

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

Re: nvram access in 2.3.48?

[Tom Rini]

On Tue, Mar 07, 2000 at 02:48:23PM -0700, Tom Rini wrote:

> On Tue, Mar 07, 2000 at 10:29:45PM +0100, Michel Lanners wrote:
>
> > Another weiredity I've come across in my 2.3 crusade: /dev/nvram
> > doesn't seem to work anymore.
>
> Near as I can tell (and I'm about to try this and then see if bk will pass
> it along happily) is that all the calls to nvram_init have been changed to
> pmac_nvram_init.

On further inspection, it's not.   Eugg.  It looks like the functionality of
drivers/macintosh/nvram.c needs to be added to arch/ppc/kernel/pmac_nvram.c
(Some other drivers depend on the drivers version functionality, which is
working I _think_..

---
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

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

Re: nvram access in 2.3.48?

[Chas Williams]

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

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

Re: nvram access in 2.3.48?

[Michel Lanners]

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/

Re: nvram access in 2.3.48?

[Tom Rini]

On Tue, Mar 07, 2000 at 10:52:09PM +0100, Michel Lanners wrote:

> That was in a drivers/char file, under drivers/macintosh, and under
> arch/ppc, if I rember right....

Right.  drivers/char/nvram.c is the PC-style NVRAM driver.  CHRP and PReP(?)
can use it.  drivers/macintosh/nvram.c is the PMac-style (Basically pre-new
world rom).  arch/ppc/kernel/pmac_nvram is for anything newer then that, it
seems.  Somehow, all three need to co-exist happily.  What _should_ be the
"easy" way is to merge the drivers/macintosh and arch/ppc/kernel ones together.

---
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

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

Re: nvram access in 2.3.48?

[Tom Rini]

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/

Re: nvram access in 2.3.48?

[Michel Lanners]

On   7 Mar, this message from Tom Rini echoed through cyberspace:
[about NVRAM]
>> > 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.

Be careful; isn't the one in drivers/macintosh needed by the M68K port?

Of course, there could be one general drivers/char/nvram.c file with
all the high-level stuff, and platform-specific files only implementing
the low-level access routines. But then, there is an API to be defined
between the two.....

Michel

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

Re: nvram access in 2.3.48?

[Tony Mantler]

At 12:39 AM -0600 3/8/2000, Michel Lanners wrote:
>On   7 Mar, this message from Tom Rini echoed through cyberspace:
>[about NVRAM]
>>> > 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.
>
>Be careful; isn't the one in drivers/macintosh needed by the M68K port?

Don't think so. Unless nvram is just a curiously renamed and retasked pram,
which I seem to recall it isn't, then 68k macs don't even have it.

The pram/rtc, by the way, is accessed on 68k macs by either some VIA
register twiddling, or by IIsi, PMU or CUDA style adb, so if you see any
refrences to that code anywhere, don't break it. :)


By the way, if you get rid of the nvram.c in drivers/macintosh, then it
would probably be fruitful to entirely disband the directory. I don't have
a 2.3 source tree handy, but I seem to recall that the 68k serial driver
was merged with the PPC serial driver a little bit back, and belongs most
sensibly in drivers/char anyways, adb probably belongs in a drivers/adb
directory so the NeXT port people need not associate with those icky macs
;), and after all that's gone there's not much of anything left in
drivers/macintosh that can't be moved elsewhere.


Cheers - Tony :)


--
Tony Mantler         Renaissance Nerd Extraordinaire         eek@escape.ca
Winnipeg, Manitoba, Canada                       http://www.escape.ca/~eek


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