From: "Tolentino, Matthew E" <matthew.e.tolentino@intel.com>
To: "Matt Domsch" <Matt_Domsch@dell.com>,
"Bjorn Helgaas" <bjorn.helgaas@hp.com>
Cc: <linux-ia64@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] add some EFI device smarts
Date: Wed, 21 Apr 2004 00:05:33 -0700 [thread overview]
Message-ID: <D36CE1FCEFD3524B81CA12C6FE5BCAB002FFEA99@fmsmsx406.fm.intel.com> (raw)
> On Tue, Apr 20, 2004 at 04:00:26PM -0600, Bjorn Helgaas wrote:
> > (Like much of the EFI stuff, this really isn't ia64-specific. Maybe
> > it's time to move some of it under drivers/efi? If there's
> interest,
> > I can look at doing that.)
>
> Matt T. had done the work to move it under drivers/efi, though now
> that there's a drivers/firmware, that's more appropraite. It also
> converted it to use sysfs instead of proc. There was a bug in
> efivars_exit() where it was removing stuff (which could sleep) while
> holding a spinlock which wasn't good, but that was about the only
> issue anyone had with it.
Indeed. I fixed that and one other small issue Greg pointed out
a while ago. I'll resend updated efivars driver patches in a separate
mail shortly.
> +int
> +efi_get_variable(char *name, efi_variable_t *guid, unsigned
> char *data, unsigned long *size)
>
> and do a guidcmp() on them as well as the strcmp() on the name.
>
> > +int __init
> > +efi_uart_console_only(void)
>
> So to be useful, efivars can't be build modular anymore, right? Then
> Kconfig needs to change as well. It's module_init(), is that early
> enough to be used? Where is efi_uart_console_only() called from?
> It's not in this patch.
This part isn't clear to me. It looks like you are including a
duplicate efi_get_variable function in efi.c in order to have
access to EFI variable services (and perform the checks) very early
before console initialization and/or efivars is available ... is
that correct?
thanks,
matt
next reply other threads:[~2004-04-21 7:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 7:05 Tolentino, Matthew E [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-20 22:00 Bjorn Helgaas
2004-04-20 23:50 ` Matt Domsch
2004-04-21 12:59 ` Bjorn Helgaas
2004-04-21 14:22 ` Matthew Wilcox
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=D36CE1FCEFD3524B81CA12C6FE5BCAB002FFEA99@fmsmsx406.fm.intel.com \
--to=matthew.e.tolentino@intel.com \
--cc=Matt_Domsch@dell.com \
--cc=bjorn.helgaas@hp.com \
--cc=linux-ia64@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®