From: Matt Domsch <Matt_Domsch@dell.com>
To: Abhay Salunke <Abhay_Salunke@dell.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [patch 2.6.12-rc3] dell_rbu: New Dell BIOS update driver
Date: Wed, 11 May 2005 17:05:07 -0500 [thread overview]
Message-ID: <20050511220507.GA11723@lists.us.dell.com> (raw)
In-Reply-To: <20050510220520.GA30741@littleblue.us.dell.com>
On Tue, May 10, 2005 at 05:05:20PM -0500, Abhay Salunke wrote:
> The dell_rbu driver is required for updating BIOS on DELL servers and client
> systems. The driver lets a user application download the BIOS image in to
> contiguous physical memory pages; the driver exposes the memory via sysfs
> filesystem. The update mechanism basically has two approcahes; one by
> allocating contiguous physical memory and the second approach is by allocating
> small chunks of contiguous physical memory.
[snip]
> diff -uprN linux-2.6.11.8.ORIG/drivers/firmware/Kconfig linux-2.6.11.8/drivers/firmware/Kconfig
> --- linux-2.6.11.8.ORIG/drivers/firmware/Kconfig 2005-05-09 15:13:06.257801832 -0500
> +++ linux-2.6.11.8/drivers/firmware/Kconfig 2005-05-09 16:30:47.746147888 -0500
> @@ -58,4 +58,16 @@ config EFI_PCDP
>
> See <http://www.dig64.org/specifications/DIG64_HCDPv20_042804.pdf>
>
> +config DELL_RBU
> + bool "BIOS update support for DELL systems via sysfs"
Trivial: needs to be tristate, not bool, to make a module. Change
help text then accordingly.
Thanks,
Matt
--
Matt Domsch
Software Architect
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
next prev parent reply other threads:[~2005-05-11 22:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-10 22:05 Abhay Salunke
2005-05-10 23:59 ` Andrew Morton
2005-05-11 8:35 ` Arjan van de Ven
2005-05-11 7:19 ` Greg KH
2005-05-11 8:49 ` Arjan van de Ven
2005-05-11 9:57 ` Xavier Bestel
2005-05-11 22:05 ` Matt Domsch [this message]
2005-05-11 15:25 Abhay_Salunke
2005-05-11 18:21 Abhay_Salunke
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=20050511220507.GA11723@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=Abhay_Salunke@dell.com \
--cc=akpm@osdl.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®