public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt_Domsch@Dell.com
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] [PATCH] /proc access to EFI variables v0.02
Date: Mon, 12 Mar 2001 22:29:07 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005275@msgid-missing> (raw)

I've created a kernel patch which makes all the EFI variables available
under /proc/efi.  Support for reading, writing, creating, and destroying
variables is present.

I've incorporated feedback from Stephane Eranian (thanks!).
This patch is at version 0.02.  I've tested it myself, and believe it ready
for inclusion in David's tree.

Other changes include:
- exporting struct efi in kernel/ia64_ksyms.c so efivars can be a module
- setting the high bit on EFI error status codes in include/asm-ia64/efi.h
(per spec) (There's probably a cleaner way to do this.)


The patch is available at
http://domsch.com/linux/ia64/linux-2.4.1-010131-efivars-010312.patch, and is
also attached.

Reads to /proc/efi/varname return an efi_variable_t structure.
Writes to /proc/efi/varname must be an efi_variable_t structure.
Writes with DataSize = 0 or Attributes = 0 deletes the variable named in the
structure.  You should write to a different variable name file than the one
you are deleting (i.e., to delete Boot0000*, write to Boot0001*, with a name
of Boot0000 in the name field of the structure).  This avoids the problem of
deleting a /proc file while you are holding an open file handle to it.
Writes to any file with a new value in VariableName+VendorGuid creates a new
variable.

I haven't written a user-space app for manipulating the variables, but
that's necessary.  Or, you can cat one of the variables to a file, and use a
hex editor to change it, then cat it back.  That works well.

As always, your feedback is appreciated.

Thanks,
Matt

--
Matt Domsch
Dell Linux Systems Group
Linux OS Development
www.dell.com/linux


                 reply	other threads:[~2001-03-12 22:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=marc-linux-ia64-105590693005275@msgid-missing \
    --to=matt_domsch@dell.com \
    --cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox