From: Jean Delvare <khali@linux-fr.org>
To: Matt Domsch <Matt_Domsch@dell.com>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
Michael E Brown <Michael_E_Brown@dell.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: Class device namespaces
Date: Mon, 27 Apr 2009 17:30:05 +0200 [thread overview]
Message-ID: <20090427173005.3ff1100b@hyperion.delvare> (raw)
In-Reply-To: <20090426130122.GB12455@auslistsprd01.us.dell.com>
On Sun, 26 Apr 2009 08:01:22 -0500, Matt Domsch wrote:
> On Sun, Apr 26, 2009 at 07:44:43AM -0500, Matt Domsch wrote:
> > On Sun, Apr 26, 2009 at 08:54:01AM +0200, Jean Delvare wrote:
> > > Matt, maybe you can help? Could you please point us to the source code
> > > of the dell firmware tool which relies on the dell_rbu driver?
> >
> > There's a git tree at:
> > http://linux.dell.com/git/?p=libsmbios.git
> >
> > which you can get via rsync at:
> > rsync -va rsync://linux.dell.com/git/libsmbios.git/
> >
> > the application is dellBiosUpdate, and the source is at this point in
> > the tree:
> >
> > http://linux.dell.com/git/?p=libsmbios.git;a=blob;f=src/bin/dellBiosUpdate.cpp;h=b32e157b7ceb0be0d53eed4a4d171d24fe6456a7;hb=HEAD
OK, thanks for the pointers.
> I'll note there is a second implementation that uses dell_rbu, and
> that is included in each and every "Dell Update Package" (aka DUP)
> BIOS update posted on support.dell.com for every Dell PowerEdge server
> for the past several years. Because the updater and they BIOS payload
> are packaged in the same package, a change which would require
> changing that updater will result in requiring Dell to spin and
> re-release hundreds of DUPs, which would not go over well... Thank
> you for being careful not to change the interface capriciously - it
> could have a huge impact on us.
I'll be careful, but you have to admit that duplicating utility code
like this is poor engineering from Dell :( I don't want to think of the
mess it will be if you ever have to fix a critical bug in that code.
--
Jean Delvare
next prev parent reply other threads:[~2009-04-27 15:30 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-29 15:48 Class device namespaces Jean Delvare
2009-03-29 16:36 ` Kay Sievers
2009-03-30 8:49 ` Jean Delvare
2009-03-30 11:24 ` Kay Sievers
2009-04-26 6:54 ` Jean Delvare
2009-04-26 12:44 ` Matt Domsch
2009-04-26 13:01 ` Matt Domsch
2009-04-27 15:30 ` Jean Delvare [this message]
2009-04-27 17:30 ` Matt Domsch
2009-04-26 13:42 ` Kay Sievers
2009-04-27 16:00 ` Jean Delvare
2009-04-27 21:57 ` Kay Sievers
2009-04-28 8:08 ` Jean Delvare
2009-04-28 12:36 ` Kay Sievers
2009-04-29 12:19 ` Jean Delvare
2009-04-27 13:20 ` Michael E Brown
2009-04-27 15:27 ` Jean Delvare
2009-04-27 17:23 ` Michael Brown
2009-04-28 8:10 ` Jean Delvare
2009-04-28 17:39 ` Doug Warzecha
2009-04-28 17:46 ` Kay Sievers
2009-04-28 21:58 ` Doug Warzecha
2009-04-29 1:42 ` Kay Sievers
2009-04-29 3:19 ` Michael Brown
2009-04-29 10:30 ` Kay Sievers
2009-04-29 17:00 ` Michael Brown
2009-04-29 19:10 ` Kay Sievers
2009-04-29 21:28 ` Michael Brown
2009-04-29 21:53 ` Kay Sievers
2009-04-30 15:18 ` David Dillow
2009-04-30 16:34 ` Kay Sievers
2009-04-28 19:06 ` Jean Delvare
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=20090427173005.3ff1100b@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=Matt_Domsch@dell.com \
--cc=Michael_E_Brown@dell.com \
--cc=gregkh@suse.de \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.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