Luca:
I thought I posted this yesterday, but looks like I sent it as a
Author only reply. I thought I would put this here for everyone's
benefit.
In the changes we both initially did in the wifi.c, the path to the
module needs to be /lib/modules/ath5k.ko and not /system/lib/modules/
ath5k.ko. If you change that, the Module gets loaded properly. Not
that the WLAN works, but you dont go into the Airplane Mode.
The next thing I did was to comment out the line set_prop
("ctrl.status", WLAN_LOADER); since the logs showed that it was trying
to load the firmware - ATH5K driver does not need any firmware as far
as I know. The error related to this goes away, but I am no closer to
getting the driver to work.
Gani
On Apr 21, 9:41 pm, Luca Belluccini <
lucabellucc...@gmail.com> wrote:
> It is not working for me. I did the same changes onwifi.c as you
> pasted here.
> In Android GUI, I can press Enablewifiand I get:
> -module insmodded
> -GUI locked for some seconds
> -reboot
> -Android in airplane mode
> I'm running on a real eeepc701.
> It seems the hot code causing error is:
> wifi_load_driver inwifi.c
>
> By the way I think we need wpa_supplicant (or it will be launched by
> Android?).
> The property wlan.driver.status must be set. But I don't know which
> value must be set.
>
> On 21 Apr, 19:40, Gani Bhagavathula <
gani.bhagavath...@gmail.com>
> wrote:
>
> > Luca:
>
> > If I dont use WPA (and have no wpa_supplicant) is it OK just to change
> > thewifi.c like this, and compile the module and make sure it is in
> > the init.rc? Will it connect to a WEP protected network at that
> > point?
>
> > static const char IFACE_DIR[] = "/data/system/
> > wpa_supplicant";
> > static const char DRIVER_MODULE_NAME[] = "ath5k";
> > static const char DRIVER_MODULE_TAG[] = "ath5k ";
> > static const char DRIVER_MODULE_PATH[] = "/system/lib/modules/
> > ath5k.ko";
> > static const char FIRMWARE_LOADER[] = "wlan_loader";
> > static const char DRIVER_PROP_NAME[] = "wlan.driver.status";
>
> > Regards,
> > Gani
>
> > On Apr 21, 3:54 pm, Luca Belluccini <
lucabellucc...@gmail.com> wrote:
>
> > > I'm with the same module. I set it NOT built-in.
> > > You are planning to makewifiinteract with Android GUI?
> > > I modifiedwifi.c specifying the right path to module to be insmodded.