On Tue, Jun 3, 2008 at 12:08 PM, David Woodhouse [EMAIL PROTECTED] wrote:
On Tue, 2008-06-03 at 11:03 -0400, John Watlington wrote:
My bad. This is now Trac #7170
http://dev.laptop.org/ticket/7170
All of the information in this ticket comes from email exchanged with
dcbw and dwmw2 when I
On Jun 3, 2008, at 11:08 AM, David Woodhouse wrote:
On Tue, 2008-06-03 at 11:03 -0400, John Watlington wrote:
My bad. This is now Trac #7170
http://dev.laptop.org/ticket/7170
All of the information in this ticket comes from email exchanged with
dcbw and dwmw2 when I first discovered it.
[EMAIL PROTECTED] wrote on 06/03/2008 11:20:51 AM:
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
On Tue, 2008-06-03 at 10:37 -0400, Michail Bletsas wrote:
[EMAIL PROTECTED] wrote on 06/03/2008 10:12:31 AM:
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
On Tue, 2008-06-03 at 11:18 -0400, John Watlington wrote:
On Jun 3, 2008, at 11:08 AM, David Woodhouse wrote:
On Tue, 2008-06-03 at 11:03 -0400, John Watlington wrote:
My bad. This is now Trac #7170
http://dev.laptop.org/ticket/7170
All of the information in this ticket comes from
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
On Tue, 2008-06-03 at 10:37 -0400, Michail Bletsas wrote:
The userspace tool is extremely awkward to use (since it requires the
driver modules to be unloaded which in turn makes the identification
of devices on the XO even more difficult)
I believe there's a way for libusb to unbind the
On Tue, 2008-06-03 at 10:12 -0400, Dan Williams wrote:
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
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
On Tue, 2008-06-03 at 11:34 -0300, Ricardo Carrano wrote:
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
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
On Tue, 2008-06-03 at 11:44 -0300, Ricardo Carrano wrote:
Please check comment on:
http://wiki.laptop.org/go/Active_Antenna_Reprogramming#User_Space_Method
Where am I looking? The 'has failed twice' claim? That's hardly a decent
bug report. Put a coherent report in trac, and we'll look at it.
On Tue, Jun 3, 2008 at 11:49 AM, David Woodhouse [EMAIL PROTECTED] wrote:
On Tue, 2008-06-03 at 11:44 -0300, Ricardo Carrano wrote:
Please check comment on:
http://wiki.laptop.org/go/Active_Antenna_Reprogramming#User_Space_Method
Where am I looking? The 'has failed twice' claim? That's hardly
On Tue, Jun 3, 2008 at 11:35 AM, David Woodhouse [EMAIL PROTECTED] wrote:
On Tue, 2008-06-03 at 11:34 -0300, Ricardo Carrano wrote:
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
[EMAIL PROTECTED] wrote on 06/03/2008 10:12:31 AM:
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
On Tue, Jun 3, 2008 at 11:35 AM, David Woodhouse [EMAIL PROTECTED] wrote:
On Tue, 2008-06-03 at 11:34 -0300, Ricardo Carrano wrote:
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
My bad. This is now Trac #7170
http://dev.laptop.org/ticket/7170
All of the information in this ticket comes from email exchanged with
dcbw and dwmw2 when I first discovered it.
wad
On Jun 3, 2008, at 10:49 AM, David Woodhouse wrote:
On Tue, 2008-06-03 at 11:44 -0300, Ricardo Carrano
On Tue, 2008-06-03 at 11:03 -0400, John Watlington wrote:
My bad. This is now Trac #7170
http://dev.laptop.org/ticket/7170
All of the information in this ticket comes from email exchanged with
dcbw and dwmw2 when I first discovered it.
Didn't we fix that months ago by increasing the
On Tue, 2008-06-03 at 11:26 -0400, Dan Williams wrote:
On Tue, 2008-06-03 at 10:37 -0400, Michail Bletsas wrote:
[EMAIL PROTECTED] wrote on 06/03/2008 10:12:31 AM:
On Mon, 2008-06-02 at 17:12 -0700, Brian Cavagnolo wrote:
To update boot2, copy the boot2 and firmware images to
On Tue, 2008-06-03 at 11:30 -0400, Michail Bletsas wrote:
[EMAIL PROTECTED] wrote on 06/03/2008 11:20:51 AM:
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
Dan Williams [EMAIL PROTECTED] wrote on 06/03/2008 12:09:11 PM:
On Tue, 2008-06-03 at 11:30 -0400, Michail Bletsas wrote:
[EMAIL PROTECTED] wrote on 06/03/2008 11:20:51
AM:
A necessary rectification:
Firmware updates from the driver are the only method that works
Dan Williams [EMAIL PROTECTED] 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
of
How does it make the ID more difficult?
On Tue, 2008-06-03 at 13:49 -0400, Michail Bletsas wrote:
Dan Williams [EMAIL PROTECTED] wrote on 06/03/2008 01:20:11 PM:
On Tue, 2008-06-03 at 13:03 -0400, Michail Bletsas wrote:
Dan Williams [EMAIL PROTECTED] wrote on 06/03/2008 11:26:21 AM:
It is not a matter of
On Tue, 2008-06-03 at 13:03 -0400, Michail Bletsas wrote:
Dan Williams [EMAIL PROTECTED] 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
Dan Williams [EMAIL PROTECTED] wrote on 06/03/2008 01:20:11 PM:
On Tue, 2008-06-03 at 13:03 -0400, Michail Bletsas wrote:
Dan Williams [EMAIL PROTECTED] 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
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 by this point the driver has already sent
On Tue, 2008-06-03 at 13:09 -0400, Michail Bletsas wrote:
Dan Williams [EMAIL PROTECTED] wrote on 06/03/2008 12:09:11 PM:
On Tue, 2008-06-03 at 11:30 -0400, Michail Bletsas wrote:
[EMAIL PROTECTED] wrote on 06/03/2008 11:20:51
AM:
A necessary rectification:
Dan Williams [EMAIL PROTECTED] wrote on 06/03/2008 01:50:59 PM:
That's a good suggestion.
From a practical perspective though, in XOs, the onboard interface is
always eth0 these days.
Yes, but I thought the discussion was more about active antenna updates,
where you may have more
Dan Williams wrote:
that wasn't intended for my part. I'm happy to test this out and try to
get the userspace tool working again if given:
1) one or more active antenna modules to potentially brick
If you have a unit that you brick we can program a new chip and swap it
at 1cc. Assuming
On Tue, 2008-06-03 at 11:28 -0400, Dan Williams wrote:
I'm happy to test this out and try to
get the userspace tool working again if given:
Last time I knew, the userspace tool _was_ working.
Although we'd stripped out the support from the kernel driver ages ago
and wrote libertas-flash.py,
On Tue, 2008-06-03 at 22:08 +0100, David Woodhouse wrote:
On Tue, 2008-06-03 at 11:28 -0400, Dan Williams wrote:
I'm happy to test this out and try to
get the userspace tool working again if given:
Last time I knew, the userspace tool _was_ working.
Although we'd stripped out the
Hello,
On Tue, Jun 3, 2008 at 11:38 AM, Dan Williams [EMAIL PROTECTED] wrote:
Am I correct in assuming that the runtime firmware implements _all_ the
same boot commands that the boot2 firmware does, including UPDATE_BOOT2
(flash new boot2 to EEPROM), FW_BY_USB (execute uploaded firmware but do
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
Signed-off-by: Brian Cavagnolo [EMAIL PROTECTED]
---
drivers/net/wireless/libertas/if_usb.c | 65
33 matches
Mail list logo
