From: Matt Domsch <Matt_Domsch@dell.com>
To: Matt Tolentino <metolent@snoqualmie.dp.intel.com>
Cc: akpm@osdl.org, bjorn.helgaas@hp.com, linux-ia64@vger.kernel.org,
linux-kernel@vger.kernel.org, matthew.e.tolentino@intel.com
Subject: Re: [patch 1/3] efivars driver update and move
Date: Fri, 23 Apr 2004 17:29:45 -0500 [thread overview]
Message-ID: <20040423222945.GA9594@lists.us.dell.com> (raw)
In-Reply-To: <200404221732.i3MHWJcc023373@snoqualmie.dp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]
On Thu, Apr 22, 2004 at 10:32:19AM -0700, Matt Tolentino wrote:
> Andrew,
>
> I broke up the efivars driver update patch I had sent out
> quite a while ago into several smaller patches. This
> includes several fixes and suggestions that were pointed
> out. The patches are broken down as follows:
>
> 2 - add new sysfs based efivars driver into
> drivers/firmware with accompanying Kconfig/Makefile
> changes to make it fully functional for ia64 again.
Trying these against 2.6.5 + ia64 patch, with efibootmgr-0.5.2-test2.
Works: reading, deleting values.
Doesn't work: creating and editing values
I note that efibootmgr prints out a warning when it can't read
nonexistant variables, like BootNext. I'll remove that warning.
It's likely a bug in efibootmgr, as this is the first time I've tried
the sysfs side of things. If you're in a position to help debug, I'd
appreciate it.
Thanks,
Matt
--
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-04-23 22:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 17:32 [patch 1/3] efivars driver update and move Matt Tolentino
2004-04-22 16:46 ` Bjorn Helgaas
2004-04-23 22:29 ` Matt Domsch [this message]
2004-04-24 3:41 ` Matt Domsch
2004-04-26 18:57 ` Matt Domsch
-- strict thread matches above, loose matches on Subject: below --
2004-04-30 1:55 Matt Tolentino
2004-04-26 21:15 Matt Tolentino
2004-04-22 17:14 Tolentino, Matthew E
2004-04-22 17:20 ` Bjorn Helgaas
2004-04-29 19:50 ` Alex Williamson
2004-04-29 21:19 ` Matt Domsch
2004-04-29 22:08 ` Alex Williamson
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=20040423222945.GA9594@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=akpm@osdl.org \
--cc=bjorn.helgaas@hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.e.tolentino@intel.com \
--cc=metolent@snoqualmie.dp.intel.com \
/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