is there a thing such as static compilation of drivers ? android uses BlueZ for bluetooth and for WLAN has very well defined integration sort of layer which your driver has to provide. bluetooth/bluez drivers are already present in the linux kernel and a whole bunch of wlan drivers are also present in the linux kernel.
although specifically in bluetooth they have kind of concentrated on uart transport BT chips, wlan integration (+ supplicant interface) is of more generic. regards, Pavan On Mon, Sep 14, 2009 at 12:34 PM, Abhinayak Mishra <abhina...@gmail.com> wrote: > My guess is static compilation comes into play because of absence of the > standard functions support in the form of a shared library. As to why some > drivers could be directly ported over is probably because they never assumed > presence of any of the "standard" functions. :) > > > > On Sun, Sep 13, 2009 at 10:42 PM, Rajesh N <rajesh.andr...@gmail.com> wrote: >> >> Hi, >> I was working on Freescale iMX31 board, I ported android and it was >> working fine , but when it came to integration of WiFi & Bluetooth, android >> forum recommended me to do static compilation for porting over android ! >> Can I know why some drivers have to be statically compiled before it is >> ported over android? >> It was not the case with other drivers which when integrated with >> android, they worked perfectly well like serial port, usb etc.. >> >> Any info on this would be appreciated. >> >> -- >> Best Regards, >> Rajesh N >> >> -- >> Best Regards, >> Rajesh N >> >> > > > > > -- --Pavan Savoy --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
