[Bug 3161] h5000: WiFi doesn't work

[bugzilla-daemon at treke.net]

http://bugs.openembedded.net/show_bug.cgi?id=3161





--- Comment #8 from Milan Plzik <milan.plzik at gmail.com>  2008-02-25 09:29:41 ---
(In reply to comment #7)
> (In reply to comment #6)

First of all, in my previous comment, anyone who tries to use it, substitute
'gpiodev' with 'devmem2' :)

> Hi Milan!
> 
> >   The bits are not (unfortunately) in the driver. You need to enable power to
> > wifi before using it and that is something what at76c503 driver doesn't do
> > right now.
> 
> Which driver - the h5400_wifi or at76c503 ? 

  h5400_wifi is (more or less) obsolete driver, whose purpose was to register
new ohci interface and enable wifi. Registering OHCI interface is now being
done by samcop's driver, setting these bits _could_ be done by h5400_wifi
driver, but I guess it's not the right way to use modprobe/rmmod to
enable/disable wifi :)

> 
> >   If you want to do it manually, you will need devmem2 package, and to this:
> 
> How can I do it not manually ? 

  Up to now I thoughy there is no other way, but after re-reading h5400_wifi,
you can toggle those bits also by (un-)loading this driver.

> What do all these memory bits do ? What are they responsible for ? 

  One bit enables the atmel chip (so it appears on the USB bus), other one
enables power to transceiver.

> How (by which driver) was it handled in 2.4 kernel ? 

  In 2.4, the at76c503 driver enabled wifi as soon as it was loaded, and
disabled it when removing. There were also power management issues with wifi
not being disabled when ipaq entered sleep mode. I would not like to go this
way and rather somehow (correctly) modify at76_usb driver to power up wifi when
ifconfig wlan0 up is called, etc.


-- 
Configure bugmail: http://bugs.openembedded.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.