On Mon, Feb 16, 2009 at 12:22 PM, Gary C Martin g...@garycmartin.com wrote:
On 16 Feb 2009, at 05:32, Chris Ball wrote:
Hi,
Last I checked, it was either the firmware or the kernel changes
that did it. I posted my findings to the mailing list in the past
two weeks.
I think your findings
I find 767, with either q2e18 or q2e24, connecting to a WPA AP
succeeds 100% of the time for me using a Linksys WRT54g L.
With OFW q2e32 I have seen the network connection die. Seems like
the stack is dead. I assume it is the marvell driver that is
delivered with q2e32. My other XO
The OS is supposed to reload the wireless firmware so the firmware that
is in OFW shouldn't affect the OS behavior.
rihowa...@gmail.com wrote:
I find 767, with either q2e18 or q2e24, connecting to a WPA AP
succeeds 100% of the time for me using a Linksys WRT54g L.
With OFW q2e32 I have
On Mon, Feb 16, 2009 at 11:21:34AM -1000, Mitch Bradley wrote:
The OS is supposed to reload the wireless firmware so the firmware that
is in OFW shouldn't affect the OS behavior.
Agreed. It shouldn't. I wonder if it does, through some mechanism we
don't know yet. Has anyone else got the
James Cameron wrote:
On Mon, Feb 16, 2009 at 11:21:34AM -1000, Mitch Bradley wrote:
The OS is supposed to reload the wireless firmware so the firmware that
is in OFW shouldn't affect the OS behavior.
Agreed. It shouldn't. I wonder if it does, through some mechanism we
don't
