LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Michael E Brown <Michael_E_Brown@dell.com>
Cc: Markus Rechberger <markus.rechberger@amd.com>,
	Matt_Domsch@dell.com,
	Jos?? Luis Tall??n <jltallon@adv-solutions.net>,
	Douglas_Warzecha@dell.com, Abhay_Salunke@dell.com,
	linux-kernel@vger.kernel.org, Greg KH <gregkh@suse.de>
Subject: Re: 2.6.24 breaks BIOS updates on all Dell machines
Date: Tue, 5 Feb 2008 17:25:11 +0100	[thread overview]
Message-ID: <20080205172511.68116747@hyperion.delvare> (raw)
In-Reply-To: <20080204155834.GA32437@humbolt.us.dell.com>

On Mon, 4 Feb 2008 09:58:35 -0600, Michael E Brown wrote:
> On Sun, Feb 03, 2008 at 03:02:38PM +0100, Jean Delvare wrote:
> > Hi Michael,
> > 
> > On Tue, 29 Jan 2008 13:09:25 -0600, Michael E Brown wrote:
> > > On Tue, Jan 29, 2008 at 08:04:17PM +0100, Sytse Wielinga wrote:
> > > > I've created the simple patch below. I have no idea if it actually works,
> > > > though, as I don't appear to have any hardware for which a linux driver
> > > > supports firmware loading. Please comment.
> > > 
> > > You can test this rather easily. Simply modprobe the "dell_rbu" driver.
> > > You dont need any special hardware, it should load on any machine. After
> > > you have loaded it, check the sysfs path to see if it has the correct
> > > path (or some symlink thereof):
> > > 
> > > GOOD: /sys/class/firmware/dell_rbu/   
> > > BAD : /sys/class/firmware/firmware-dell_rbu/loading
> > 
> > This doesn't actually work for me. Loading the dell_rbu driver on a
> > non-Dell system doesn't create anything under /sys/class/firmware.
> 
> You have to initialize the driver first before that file appears.
> 
> [root@localhost ~]# modprobe dell_rbu
> [root@localhost ~]# cd /sys/devices/platform/dell_rbu/
> [root@localhost dell_rbu]# ll /sys/class/firmware/dell_rbu/loading 
> ls: cannot access /sys/class/firmware/dell_rbu/loading: No such file or
> directory
> [root@localhost dell_rbu]# echo -n -e 'init\0' > image_type 
> [root@localhost dell_rbu]# ll /sys/class/firmware/dell_rbu/loading 
> -rw-r--r-- 1 root root 4096 2008-02-04 09:57
> /sys/class/firmware/dell_rbu/loading

Ah, OK, thanks for the hint, it works now.

-- 
Jean Delvare

  parent reply	other threads:[~2008-02-05 16:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E9909A75A543064DB66E55B8E3BE41EC5FD218@ausx3mps307.aus.amer.dell.com>
2008-01-29 14:59 ` FW: " Markus Rechberger
2008-01-29 18:41   ` Greg KH
2008-01-29 22:15     ` Jean Delvare
2008-02-05  6:45       ` Greg KH
2008-02-05 20:16         ` Jean Delvare
2008-02-05 23:44           ` Greg KH
2008-02-06 13:20             ` Jean Delvare
2008-01-29 19:04   ` FW: " Sytse Wielinga
     [not found]     ` <20080129190924.GB8786@humbolt.us.dell.com>
2008-02-03 14:02       ` Jean Delvare
     [not found]         ` <20080204155834.GA32437@humbolt.us.dell.com>
2008-02-05 16:25           ` Jean Delvare [this message]
     [not found] <20080129063244.GA19076@humbolt.us.dell.com>
2008-01-29  6:44 ` Greg KH

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=20080205172511.68116747@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=Abhay_Salunke@dell.com \
    --cc=Douglas_Warzecha@dell.com \
    --cc=Matt_Domsch@dell.com \
    --cc=Michael_E_Brown@dell.com \
    --cc=gregkh@suse.de \
    --cc=jltallon@adv-solutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus.rechberger@amd.com \
    --subject='Re: 2.6.24 breaks BIOS updates on all Dell machines' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).