From: "Vincent Stehlé" <vincent.stehle@stepmind.com>
To: linux-mips@linux-mips.org
Subject: Re: PROM variables
Date: Thu, 13 Mar 2003 17:08:00 +0100 [thread overview]
Message-ID: <3E70ACE0.5010306@stepmind.com> (raw)
In-Reply-To: <20030313102601.GD24866@bogon.ms20.nix>
Guido Guenther wrote:
[..]
> When doing this I'd write into the NVRAM
> directly instead of using the Arcs functions, I think the necessary info
> is in the IRIX headers.
I had a look at the ARC spec. (ARC/riscspec.pdf), and I am affraid the
only (documented) way to access PROM env. variables are the two get/set
functions.
In that case, the /proc approach makes sense IMHO.
Looking at hpc3 spec. and ip22-sc.c, I understand that PROM data are
stored in the EEPROM behind the hpc3.
Maybe a reasonable approach is:
o write a new char device driver (as pc's /dev/nvram for example)
o move eeprom read/write routines from ip22-sc.c somewhere else,
and use those routines both in ip22-sc.c and the char driver
o guess the format/offsets of the info. stored in nvram
o then write some user space app. to do the env. variable
specific part.
In that latter case, the /proc approach makes less sense IMHO.
What do you think ? Am I missing some documentation ? Is there more in
the IRIX headers ? (can't check right now, but I have them at home)
Regards,
--
Vincent Stehlé
next prev parent reply other threads:[~2003-03-13 16:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 10:04 PROM variables Vincent Stehlé
2003-03-13 10:17 ` Juan Quintela
2003-03-13 10:26 ` Guido Guenther
2003-03-13 11:33 ` Ladislav Michl
2003-03-13 11:42 ` Juan Quintela
2003-03-13 11:42 ` Juan Quintela
2003-03-13 16:08 ` Vincent Stehlé [this message]
2003-03-13 10:27 ` Ladislav Michl
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=3E70ACE0.5010306@stepmind.com \
--to=vincent.stehle@stepmind.com \
--cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.