All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Subject: [RFC] Generic access to firmware environment variables
Date: Wed, 10 Apr 2002 20:42:31 +0200	[thread overview]
Message-ID: <20020410184231.GC8136@lug-owl.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1226 bytes --]

Hi!

I've developed a driver to access environment variables on Alpha
computers from userspace through procfs some time ago. These
days, I updated the driver. While doing this, I also looked
at other architectures; some of them also do have some kind
of environment variables in firmware:

	Alphas			-	SRM firmware
	SGI Workstations	-	ARCS firmware
	MIPS/ITE-Boards		-	PMON
	m68k/MAC		-	?? (info is placed into a
					"bootinfo" struct)
	IA64			-	(_seems_ to know about
					environment...)

They all access environment variables either by name, or by an
internally handles number. For Alpha, I've (now) implemented both,
access by name (if variable name is known/described) and access by
generic number.

I think it would be useful to have something like this for other
architectures as well. So I'm currently thinking about implementing a
base driver (like parport does) and additional modules to implement
machine/architecture specific access methode (like parport_pc).

It's easy to code, so what do you think of this?

MfG, JBG

-- 
Jan-Benedict Glaw   .   jbglaw@lug-owl.de   .   +49-172-7608481
	 -- New APT-Proxy written in shell script --
	   http://lug-owl.de/~jbglaw/software/ap2/

[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]

             reply	other threads:[~2002-04-10 18:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-10 18:42 Jan-Benedict Glaw [this message]
2002-04-10 19:00 ` [RFC] Generic access to firmware environment variables David Mosberger

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=20020410184231.GC8136@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=linux-kernel@vger.kernel.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.