On Thu, Aug 24, 2006 at 02:31:23PM -0400, Jim Gettys wrote: > Interesting. I'm glad we now know what was going on. > > In theory, I would think the device driver should have responsibility > for enabling the power on devices; in Linux has knowledge of the bus > topology.
Not really - in this case its responsability of the BIOS to power up the device. Richard, Ronald, please fixup LinuxBIOS to enable the WLAN_EC pin. Thanks > Regards, > - Jim > > > On Thu, 2006-08-24 at 13:27 -0500, Richard Smith wrote: > > > > No, but the libertas driver doesn't seem to send anything to dmesg under > > > > Insyde either, so that doesn't help. The device is missing from lsusb > > > > and /proc/bus/usb/devices; it's "Bus 001 Device 004: ID 1286:2001" when > > > > booted in Insyde, and that line doesn't appear inside LB. I've checked > > > > that ehci/uhci are both loaded. > > > > > > > > - Chris. > > > I wonder if this is some magic being done by our friend the VSA ... > > > > Nope looks to me to be a simple enable pin. The EC has a singnal > > marked WLAN_EN that appears to control the 3.3V to the marvel chip. > > > > Its hooked up to GPIO18 on the EC. So enable that output and wireless > > should come back. > > > > Should linuxbios do this or leave it up to a userspace program? > > > -- > Jim Gettys > One Laptop Per Child > > > _______________________________________________ > Devel mailing list > [email protected] > http://mailman.laptop.org/mailman/listinfo/devel _______________________________________________ Devel mailing list [email protected] http://mailman.laptop.org/mailman/listinfo/devel
