Wifi on Samsung NC110 -- How to include a new driver and compile ?

[Troll]

Hi everyone,

I just tried many different ROMS of the Androix x86 project and almost
everything is working well... except the Wifi, which is, well, the
most important for a Netbook.

I have seen that we could compile Android x86 ourself using the
sources to "add a new target" to the list of the supported targets. As
I am using Linux, I know that there is a driver (a proprietary one,
and a free one) for Linux for my WiFi card (Atheros) so the thing I
was wondering is : Could someone explain me the steps to include a new
WiFi driver and compile Android x86 from the sources in order to get
it running with WiFi on my Samsung ?


Thanks in advance.

Troll

[Dan]

Building in the correct driver is pretty straigtforward after you
figured out how to build for a new target. there is a step by step
tutorial on the website for building a new target. The steps for
building are pretty simple - there's like three commands, but you have
to get your build environment setup correctly. Depending on what
linux your building on - that could take some time.

get it to build from source using one of the existing targets like
eeepc:
http://www.android-x86.org/getsourcecode

Then make your own target, and modify the kernel and build scripts to
include wifi.
http://www.android-x86.org/documents/how-to-add-new-x86-platforms

Dan

[Troll]

Hello Dan and thank you for answering. I have already visited that
page before, but I don't understand exactly where you are supposed to
include your drivers and when.

The script whose seems the page to talk about is to add a "New
Target", ok, great, but it only talks about makefiles. How are we
supposed to include the driver files themselves ? Directly in the
device/XXX/ directory ? How will the system know that it's for wifi
and not for USB or even to add a device to go into hyperspace... !?

Troll

On 8 oct, 23:58, Dan <daniel.naugh...@gmail.com> wrote:
> Building in the correct driver is pretty straigtforward after you
> figured out how to build for a new target.  there is a step by step
> tutorial on the website for building a new target.  The steps for
> building are pretty simple - there's like three commands, but you have
> to get your build environment setup correctly.  Depending on what
> linux your building on - that could take some time.
>
> get it to build from source using one of the existing targets like
> eeepc:http://www.android-x86.org/getsourcecode
>
> Then make your own target, and modify the kernel and build scripts to

> include wifi.http://www.android-x86.org/documents/how-to-add-new-x86-platforms

[Troll]

Would anyone be so kind to help us two guysa bit with this thread ? :)

Troll

On 10/12/2011 09:37 AM, abhi wrote:
> Hi ALL,
>
> Android build consist of thousands of folders and files....
> if we want to add new drivers ex Ethernet ...touch screen...wi-fi..
> 3G..Blue tooth etc which folder we have to consider to do modification
> to add driver..i am totally confused to select the required folders
> and files from thousands of folders and files...!?!
>
> can anybody please guide me the folders path and files to consider for
> implementing above features...?!?
>
>
> regards
> Abhilash

[Yi Sun]

One way is to put u driver into the kernel dir just like any other drivers and have your target config file to enable it

> --
> You received this message because you are subscribed to the Google Groups "Android-x86" group.
> To post to this group, send email to andro...@googlegroups.com.
> To unsubscribe from this group, send email to android-x86...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.
>

[Troll]

Thank you for anwsering.

With the small skills I have about all that, if I understand well, the
driver will be included as a kernel module. Then the target config file
is responsible for loading the kernel module ?

Troll

[Yi Sun]

Most correct, but the config file does not load module but just includes the module in the image. To load module, you will need to rely on the auto install scripts in the boot directory. You can look at these scripts to find detail