Chih-Wei,
IRT the ipw2200, I got it working by:
1) Hacking the kernel source
(kernel/drivers/net/wireless/ipw2x00/ipw2200.c and adding the following at
line 11737, in the ipw_pci_probe() function:
strcpy(net_dev->name, "wlan%d");
2) Re-enabling WEXT in wpa_supplicant
(external/wpa_supplicant_8/wpa_supplicant/android.config), which took
several other changes in that area; including pulling wireless_copy.h from
the ics tree; and adding the following to
(external/wpa_supplicant_8/private_lib/driver_cmd_wext.h). Apparently it's
been awhile since anyone used WEXT with this tree :)
#define WPA_EVENT_DRIVER_STATE
"CTRL-EVENT-DRIVER-STATE "
3) Again Hacking the kernel source to enable
LIB80211_CRYPT_TKIP, LIB80211_CRYPT_CCMP, LIB80211_CRYPT_WEP - for some
reason, in (kernel/net/wireless/Kconfig) the configuration for these 3 does
not have a description, so their only ever compiled as modules; and wext
does not load them by default like nl80211 does. Could have been
easier-solved by just adding a modprobe line to the init.sh.
IRT liblights; I have got most working; but in some special
situations (resuming from any time the screen gets shut off) the brightness
is not set properly; I'm assuming that it's being set to a static number
somewhere; but can't find where.
IRT The battery; it just says 100%, 0s on battery; on the battery
page... regardless if it is running on batteries or AC adapter; I'd rather
have some real info here; but now with ACPI off; I need to write kernel
drivers for the battery/ac adapter/power button/thermal zone; that pulls the
info from EC0. (BACKGROUND: the Motion Computing LE1600's ACPI is broken in
linux)
IOT get Android 4.3 x86 to compile for non-sse3 cpu's; you need to
change line #118 of (build/core/combo/TARGET_linux-x86.mk) to:
TARGET_GLOBAL_CFLAGS += -march=pentium-m -mstackrealign
-mmmx -msse -msse2 -mno-sse3 -mfpmath=sse -m32
If you don't remove -msse3 from that; SSE3 is used regardless if you
set -mno-sse3 later; I would suggest this be moved to the device-specific
folder; rather than the global build directory.
Additionally, What needs to be fed to a uinput device to get a
pointer to display on the screen? And is there any reason why right-clicks
and middle-clicks crash the settings app and browser? I've already disabled
them in my "driver" for the digitizer; but found it strange that native apps
would not have some form of error handling for these events.
After I get the last bit of cosmetic stuff fixed (WiFi Signal Level,
Battery Status, visible cursor, screen rotation, brightness control) fixed;
I'll release a binary image for the LE1600; but considering the amount of
changes that need to be made in the core files, I can't really submit a
proper device folder for it :/
V/r,
Mike
--
You received this message because you are subscribed to a topic in the
Google Groups "Android-x86" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/android-x86/iLVz2hcqcFk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to