On Tue, 2008-06-03 at 11:34 -0300, Ricardo Carrano wrote: > On Tue, Jun 3, 2008 at 11:12 AM, Dan Williams <[EMAIL PROTECTED]> wrote: > > On Mon, 2008-06-02 at 17:12 -0700, Brian Cavagnolo wrote: > >> To update boot2, copy the boot2 and firmware images to /lib/firmware and: > >> > >> echo <boot2_image_name> > /sys/class/net/eth2/lbs_boot2 > >> echo <firmware_image_name> > /sys/class/net/eth2/lbs_fw > > > > So why are we doing this with the driver, and not the userspace update > > tool? Marvell keeps wanting to do firmware update in the driver, and we > > (David and I at least) keep saying no. If there are issues that prevent > > the userspace firmware update tool from working, then we need to fix > > those issues. Firmware updates from the driver were a disaster the > > first time around, and I don't quite see how that may have changed this > > time? > > A necessary rectification: > Firmware updates from the driver are the only method that works > currently. If we want to name one method a "disaster", we would have > to choose the userspace tool, since it will brick many of your active > antennae.
It worked up until boot2 3109; and then apparently nobody at OLPC cared enough to fix the tool after that, and nobody at Marvell cared enough to tell anyone what changed so that somebody _could_ fix the tool. Dan _______________________________________________ Devel mailing list [email protected] http://lists.laptop.org/listinfo/devel
