From: Joseph Garcia <jpgarcia@execpc.com>
To: Vladimir Simonov <sv@asplinux.ru>
Cc: "linuxppc-dev@lists.linuxppc.org" <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Can't find nvtool?
Date: Thu, 17 Aug 2000 14:13:50 -0500 [thread overview]
Message-ID: <399C396E.C72DFCA4@execpc.com> (raw)
In-Reply-To: NEBBKFDEKEFCPABJIFOMKEEFDEAA.sv@sw.mipt.ru
Vladimir Simonov wrote:
> Reference
> poof-19991029.tar.gz on http://www.ping.de/sites/zagadka/poof/
> is broken.
> Can somebody help me to find poof sources?
> Thanks in advance
> Vladimir Simonov
If i recall correctly, the reason that nvsetenv didnt work on newworld boxen was
because the partitions in nvram are mapped to different offsets than oldworld.
like the xpram and OF partitions. BenH's kernel recognizes where they are
mapped, and i think there is even a way to find out where in userspace.
'pmac_xpram_read/write' maybe?
The kernel used to report where they were mapped (dmesg), but doesn't seem to
anymore.
Basically, I'm saying that nvsetenv could/should be modified to recognize which
kind of system its on, and act accordingly. If nobody wants to do it, I suppose
I could.
i wonder if using devfs we could have an nvram directory with devs pertaining to
each nvram partition. or is that done already?
--
Joseph P. Garcia jpgarcia@execpc.com jpgarcia@lidar.ssec.wisc.edu
CS Undergraduate Student Employee - Systems Programmer
University of Wisconsin - Madison UW Lidar Group
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-08-17 19:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-17 17:57 FW: Can't find nvtool? RE: setpramboot problems Vladimir Simonov
2000-08-17 19:13 ` Joseph Garcia [this message]
2000-08-17 19:23 ` Can't find nvtool? Joseph Garcia
2000-08-17 19:46 ` nvsetenv on NW (was Can't find nvtool?) Hollis R Blanchard
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=399C396E.C72DFCA4@execpc.com \
--to=jpgarcia@execpc.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=sv@asplinux.ru \
/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).