[RFC] Online firmware upgrade in non-embedded systems
Carl-Daniel Hailfinger
c-d.hailfinger.devel.2006 at gmx.net
Wed Sep 29 09:43:58 EDT 2010
On 29.09.2010 15:10, Ben Hutchings wrote:
> On Wed, 2010-09-29 at 14:45 +0200, Carl-Daniel Hailfinger wrote:
>
>> On 29.09.2010 14:35, Ben Hutchings wrote:
>>
>>> On Wed, 2010-09-29 at 00:41 +0200, Carl-Daniel Hailfinger wrote:
>>>
>>>
>>>> [adding flashrom at flashrom.org to CC, senders will be whitelisted after a
>>>> short delay]
>>>>
>>>> On 28.09.2010 19:59, Ben Hutchings wrote:
>>>>
>>>>
>>>>> Network and disk controllers normally have at least some firmware in
>>>>> flash to support their use as boot devices. [...]
>>>>>
>>>>>
>>>>>
>>>> Given that the flashrom utility <http://www.flashrom.org/> (GPLv2)
>>>> supports flashing many network cards, SATA/PATA controllers, graphics
>>>> cards, and of course the main system firmware/BIOS/EFI, and it does that
>>>> from userspace without any kernel support,
>>>>
>>>>
>>> [...]
>>>
>>> I'm looking for a clean solution, not a hack.
>>>
>>>
>> What would qualify as a clean solution?
>>
>
> One where hardware access is mediated by the kernel, and doesn't involve
> unloading or potentially conflicting with the driver for that hardware.
>
flashrom can ask the kernel driver to "please stop accessing flash". No
unloading needed, no conflict in place.
>> And is cross-platform code one of your goals?
>>
>
> Not at this level. At the application level, yes, but we already have a
> working application so I'm not interested in using flashrom for that.
>
I see. Just because I'm interested in how other flashing applications
solve this: Does that application work on *BSD as well? And could you
tell me the name of the app so I can take a look at it? Thanks.
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
More information about the linux-mtd
mailing list