On Wed, Sep 16, 2009 at 1:54 AM, Rajesh N <[email protected]> wrote:
> Pavan, > > We r using CSR based WiFi and BT , where WiFi is interfaced through SDIO > and BT through UART. > > Thanks for the info on BT , I am not sure if it is a OpenBT stack BlueZ > stack , One more question do linux kernel downloaded from www.kernel.orgcomes > with OpenBT or Bluez? > > From ur below words , u said with minor modifications with WiFi code u > were able to achive porting of WiFi on Android , Can I know which particular > area of concern u had to change to make u r WiFi work? > > You can take a look at the code in android-x86.org. With it, as long as you driver is install correctly during the boot up, you wifi should work (assuming you are using wext). > Best Regards, > Rajesh > > > On Wed, Sep 16, 2009 at 2:14 PM, pavan savoy <[email protected]>wrote: > >> >> Hi, >> >> I can comment on the BT part and a bit about Wifi part. >> For BT - You should have a BlueZ driver for your BT device, be it usb >> or uart transport, it should work with BlueZ in general first. If that >> is taken care, then android UI will work out of the box without >> any[minimal] issues. >> >> Please specify whether what android release you are using, what's the >> BT chip ? what transport ? and the exact problems that you face. >> >> On WLAN, >> The chip which I've worked with had WEXT support in its driver and the >> supplicant/wifi.c integration code worked with the chip after few >> minor modifications. >> Here the key point is supplicant, if you can make your chip work on >> normal linux via the supplicant, you should also be able to use >> android UI. >> >> regards, >> Pavan >> >> >> >> >> On Wed, Sep 16, 2009 at 2:07 PM, Rajesh N <[email protected]> >> wrote: >> > Pavan, >> > >> > Yes, I agree with your statement. >> > But I don't see any WiFi or BT doesn't work with android ! , The same >> > driver works with linux based UI not with android UI ! >> > >> > Can u name few issues which comes when integrating Android UI with >> linux >> > device drivers? >> > >> > Best Regards, >> > Rajesh >> > >> > On Wed, Sep 16, 2009 at 1:56 PM, pavan savoy <[email protected]> >> wrote: >> >> >> >> Rajesh, >> >> >> >> Isn't BT driver eventually a USB/serial driver ? and Wifi eventually a >> >> SPI/mmc driver ? >> >> So all that logic of power management still applies, However there >> >> would be some specific chip specific power management options, which >> >> is very specific to the BT/Wifi chip you use and modify your drivers >> >> accordingly. >> >> >> >> >> >> regards, >> >> Pavan >> >> >> >> On Wed, Sep 16, 2009 at 12:59 PM, Rajesh N <[email protected]> >> >> wrote: >> >> > Hi All, >> >> > >> >> > I have seen most of WiFi and BT drivers are not directly portable >> on >> >> > android platform, Is it due to the fact android platform restricts >> the >> >> > way >> >> > of communication mechanism? I went through a video presentation from >> >> > google >> >> > android in youtube.com which was on power management on android , >> where >> >> > the >> >> > presenter emphasis on the fact how the software has to be written for >> >> > better >> >> > power management! >> >> > >> >> > But I don't see any problem with rest of the device drivers which >> are >> >> > present on android , like serial port , SPI, I2C etc, does it mean >> such >> >> > modification for drivers are necessary for WiFI and BT drivers of >> >> > devices? >> >> > >> >> > -- >> >> > Best Regards, >> >> > Rajesh N >> >> > >> >> > > >> >> > >> >> >> >> >> >> >> >> -- >> >> --Pavan Savoy >> >> >> >> >> > >> > >> > >> > -- >> > Best Regards, >> > Rajesh N >> > >> > > >> > >> >> >> >> -- >> --Pavan Savoy >> >> >> > > > -- > Best Regards, > Rajesh N > > > > > -- Android-x86 http://www.android-x86.org --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
