[PATCH] libertas: add sysfs hooks to update boot2 and persistent firmware

Michail Bletsas mbletsas at laptop.org
Tue Jun 3 13:03:40 EDT 2008

Dan Williams <dcbw at redhat.com> wrote on 06/03/2008 11:26:21 AM:

> > > 
> > It is not a matter of Python vs C.
> > The userspace tool is extremely awkward to use (since it requires the 
> > driver modules to be unloaded which in turn makes the identification 
> How does it make the ID more difficult?  What do we need besides the
> bcdDevice ID that tells us what boot2 version the device has?  Is there
> something more needed to find out if the device has larger EEPROM for
> active antenna support perhaps?

It makes it more difficult because instead of network interfaces (eth0, 
eth1 etc), one ends up having to deal with USB ids.
In devices with multiple intefaces (an XO with an active antenna for 
example), that is very confusing.

> > devices on the XO even more difficult) and it bricks wireless modules 
> > while the driver method doesn't. So the statement that "firmware 
> > from the driver were a disaster" is simply not true.
> It bricks the modules because the only people with the access to the
> docs and firmware (Marvell) didn't try to debug the issue, or correct
> the tool.  There's only so much _I_ can do without access to the
> firmware source itself if other people who have the info aren't really
> jumping on these problems, when I don't have the info.

Marvell already has a working method. Are you suggesting that they are 
obliged to support yours on top of theirs?


More information about the libertas-dev mailing list