android-x86 project for all brand or everyone to create own android-x86 image?

[ady2k10]

I have read many posting in this forum. I didn't know this project
created for few brands or for all brands.
Everyone joined it and tried to create own android-x86 image.
Maybe apple users also created own android-x86 image for apple Intel
notebook.
Any comment about this ?

[slajeune]

Since the X86 hardware is VERY vast, there will be one common android
x86 source tree but MANY /device trees (as we are seeing with viewpad,
asus, etc..). And in the end, that will mean a lot of different
images. This is sadly the reality of the X86 architecture.

Cheers,
Stephane.

Post by ady2k10
I have read many posting in this forum. I didn't know this project
created for few brands or for all brands.
Everyone joined it and tried to create own android-x86 image.
Maybe apple users also created own android-x86 image for apple Intel
notebook.
Any comment about this ?

[ady2k10]

Android-x86 can install on HardDisk. I don't think have any problem to
create generic android-x86 image for all brand.
At the end, this project spent a lot time just to solved a problem for
few brnads.

Post by slajeune
Since the X86 hardware is VERY vast, there will be one common android
x86 source tree but MANY /device trees (as we are seeing with viewpad,
asus, etc..).  And in the end, that will mean a lot of different
images.  This is sadly the reality of the X86 architecture.
Cheers,
Stephane.

Post by ady2k10
I have read many posting in this forum. I didn't know this project
created for few brands or for all brands.
Everyone joined it and tried to create own android-x86 image.
Maybe apple users also created own android-x86 image for apple Intel
notebook.
Any comment about this ?

[Shawn Winnie]

We need a generic install that allows you add your own drivers at
install time, perhaps those that use readily available Linux drivers,
even if for older machines, thus far all I've seen or been able to find
is information on platform-specific builds and nobody's sharing their
ISO's. :/

Post by ady2k10
Android-x86 can install on HardDisk. I don't think have any problem to
create generic android-x86 image for all brand.
At the end, this project spent a lot time just to solved a problem for
few brnads.

Post by slajeune
Since the X86 hardware is VERY vast, there will be one common android
x86 source tree but MANY /device trees (as we are seeing with viewpad,
asus, etc..). And in the end, that will mean a lot of different
images. This is sadly the reality of the X86 architecture.
Cheers,
Stephane.

Post by ady2k10
I have read many posting in this forum. I didn't know this project
created for few brands or for all brands.
Everyone joined it and tried to create own android-x86 image.
Maybe apple users also created own android-x86 image for apple Intel
notebook.
Any comment about this ?

[ady2k10]

That will be great idea, if users can install own drivers on Android-
x86.
Or create new generic Android-x86 image every 3 months or 6 months.
So can add new driver on Android-x86.

Post by Shawn Winnie
We need a generic install that allows you add your own drivers at
install time, perhaps those that use readily available Linux drivers,
even if for older machines, thus far all I've seen or been able to find
is information on platform-specific builds and nobody's sharing their
ISO's. :/

Post by ady2k10
Android-x86 can install on HardDisk. I don't think have any problem to
create generic android-x86 image for all brand.
At the end, this project spent a lot time just to solved a problem for
few brnads.

Post by slajeune
Since the X86 hardware is VERY vast, there will be one common android
x86 source tree but MANY /device trees (as we are seeing with viewpad,
asus, etc..).  And in the end, that will mean a lot of different
images.  This is sadly the reality of the X86 architecture.
Cheers,
Stephane.

Post by ady2k10
I have read many posting in this forum. I didn't know this project
created for few brands or for all brands.
Everyone joined it and tried to create own android-x86 image.
Maybe apple users also created own android-x86 image for apple Intel
notebook.
Any comment about this ?

[Doug Schaefer]

If Linux distros can do it, it should be possible with Android-x86.
It's what the Linux kernel module structure was intended for. And if
you have good init scripts that can detect the underlying hardware you
have good support for user space dynamics as well.

I think it would attract a lot more people to the project if you had
an image that can run on many machines. It would at least give people
an opportunity to try it out with some confidence it would work on
their hardware.

Just my 2 cents.

Post by ady2k10
That will be great idea, if users can install own drivers on Android-
x86.
Or create new generic Android-x86 image every 3 months or 6 months.
So can add new driver on Android-x86.

Post by Shawn Winnie
We need a generic install that allows you add your own drivers at
install time, perhaps those that use readily available Linux drivers,
even if for older machines, thus far all I've seen or been able to find
is information on platform-specific builds and nobody's sharing their
ISO's. :/

Post by ady2k10
Android-x86 can install on HardDisk. I don't think have any problem to
create generic android-x86 image for all brand.
At the end, this project spent a lot time just to solved a problem for
few brnads.

Post by slajeune
Since the X86 hardware is VERY vast, there will be one common android
x86 source tree but MANY /device trees (as we are seeing with viewpad,
asus, etc..).  And in the end, that will mean a lot of different
images.  This is sadly the reality of the X86 architecture.
Cheers,
Stephane.

Post by ady2k10
I have read many posting in this forum. I didn't know this project
created for few brands or for all brands.
Everyone joined it and tried to create own android-x86 image.
Maybe apple users also created own android-x86 image for apple Intel
notebook.
Any comment about this ?

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[Alexandru Stoian]

I share the same feelings about this. Would love to see a generic_x86
or atleast a generic atom build similar to what meego has.

[Yi Sun]

This is our goal too. The issue is still resource and time. It is very hard for us to test different platforms to make sure that we have enough good modules for different platforms.
The better approach (only my point of view) is if you find a missing driver for a platform, try to find a good driver and then you can either make a patch or send email to let us know so that from time to time we can make things better and better.
Yi

Post by Alexandru Stoian
I share the same feelings about this. Would love to see a generic_x86
or atleast a generic atom build similar to what meego has.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[Alexandru Stoian]

Wouldn't a start point be building for the general intel atom platform
rather then only for the eee. The netbooks and mini itx atom boards
all share pretty much the same hardware and there are quite a few
optimisations for the linux kernel running ontop of atom.

[Doug Schaefer]

Post by Alexandru Stoian
Wouldn't a start point be building for the general intel atom platform
rather then only for the eee. The netbooks and mini itx atom boards
all share pretty much the same hardware and there are quite a few
optimisations for the linux kernel running ontop of atom.

If someone had a .config file that covered that, would that be enough?
Or are special drivers required that aren't in the kernel tree
already?

Post by Alexandru Stoian
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[Yi Sun]

Post by Doug Schaefer

Post by Alexandru Stoian
Wouldn't a start point be building for the general intel atom platform
rather then only for the eee. The netbooks and mini itx atom boards
all share pretty much the same hardware and there are quite a few
optimisations for the linux kernel running ontop of atom.

If someone had a .config file that covered that, would that be enough?
Or are special drivers required that aren't in the kernel tree
already?

It is really case by case, some time a config update is good enough
but sometime it is not. As I said, WIFI driver is a big problem. Also,
the hw opengl support is another issue that needs not only kernel
support both also some framework changes.

Post by Doug Schaefer

Post by Alexandru Stoian
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[Yi Sun]

If you are looking at the issue we have today, the majority of them
comes from three parts: wifi, touch and graphic. When we pick up eee
901/701/1000 to work on, we thought that they are generic enough (no
touch, i916, at5k). But, it seems that even the same device with the
same driver may not work on the netbooks from different vendors.
Also, even for the vanilla Linux, some driver may not work out of box
(wifi is the biggest issue) not mention the opengl support. So what is
a generic atom platform that you are talking about?

Post by Alexandru Stoian
Wouldn't a start point be building for the general intel atom platform
rather then only for the eee. The netbooks and mini itx atom boards
all share pretty much the same hardware and there are quite a few
optimisations for the linux kernel running ontop of atom.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[Chih-Wei Huang]

Hey, we already have a generic_x86 target
that supposes to work on all x86 platforms ideally.
Of course it's not so perfect.
If you found it doesn't work on your device,
it is considered a bug.
Feel free to fix it and send us a patch.

On the other hand, we have several targets
for some particular x86 platforms.
Why we need such targets if generic_x86
also works on the particular platforms?
The reasons are (at least):

* For optimizations. The kernel can be stripped
by removed hundreds of unused drivers.
The libraries can also be optimized for the
target cpu.
* For customizations. The target maintainers
may add some unique features that
only available for their targets.
(e.g., hw accel, gps, 3G, backlight, ...)

Post by Alexandru Stoian
I share the same feelings about this. Would love to see a generic_x86
or atleast a generic atom build similar to what meego has.

[Abhay kumar]

That's true i had tested this tree on some diffrent maufacture x86 it just
work out of the box.
May be it is not supporting your hardware.
You can get logcat results and share it with us.

cheers

Post by Chih-Wei Huang
Hey, we already have a generic_x86 target
that supposes to work on all x86 platforms ideally.
Of course it's not so perfect.
If you found it doesn't work on your device,
it is considered a bug.
Feel free to fix it and send us a patch.
On the other hand, we have several targets
for some particular x86 platforms.
Why we need such targets if generic_x86
also works on the particular platforms?
* For optimizations. The kernel can be stripped
by removed hundreds of unused drivers.
The libraries can also be optimized for the
target cpu.
* For customizations. The target maintainers
may add some unique features that
only available for their targets.
(e.g., hw accel, gps, 3G, backlight, ...)

Post by Alexandru Stoian
I share the same feelings about this. Would love to see a generic_x86
or atleast a generic atom build similar to what meego has.

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

[supriady]

I don't think have a big problem if android-x86 kernel was too big.
Because android-x86 cam install on Netbook/Laptop even PC with harddisk/USB
Flashdisk 4 GB.
I have tried to install Ubuntu Netbook Edition 10.10 and others on USB
Flashdisk 4 GB and was running fine.
And I have tested many Linux Distros on USB Flashdisk 4 GB.
Do not have any problem.
Android-x86 had few default applications if compared to standard linux
distros (OpenOffice, Gimp, mplayer,..etc).

Post by Abhay kumar
That's true i had tested this tree on some diffrent maufacture x86 it just
work out of the box.
May be it is not supporting your hardware.
You can get logcat results and share it with us.
cheers

Post by Chih-Wei Huang
Hey, we already have a generic_x86 target
that supposes to work on all x86 platforms ideally.
Of course it's not so perfect.
If you found it doesn't work on your device,
it is considered a bug.
Feel free to fix it and send us a patch.
On the other hand, we have several targets
for some particular x86 platforms.
Why we need such targets if generic_x86
also works on the particular platforms?
* For optimizations. The kernel can be stripped
by removed hundreds of unused drivers.
The libraries can also be optimized for the
target cpu.
* For customizations. The target maintainers
may add some unique features that
only available for their targets.
(e.g., hw accel, gps, 3G, backlight, ...)

Post by Alexandru Stoian
I share the same feelings about this. Would love to see a generic_x86
or atleast a generic atom build similar to what meego has.

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

--
Abhay kumar
([phone]
--
You received this message because you are subscribed to the Google Groups
"Android-x86" group.
To unsubscribe from this group, send email to
.
For more options, visit this group at
http://groups.google.com/group/android-x86?hl=en.

[ady2k10]

Sure, many android smartphone and Android tablet customized their own
android kernel.
Because they didn't connect to another devices (hardware limited and
Used ARM Processor)
Android kernel for smartphone and Tablet became very slim.
I dont' think It should make android-x86 kernel likes Android
Smartphone or Android Tablet.

Post by supriady
I don't think have a big problem if android-x86 kernel was too big.
Because android-x86 cam install on Netbook/Laptop even PC with harddisk/USB
Flashdisk 4 GB.
I have tried to install Ubuntu Netbook Edition 10.10 and others on USB
Flashdisk 4 GB and was running fine.
And I have tested many Linux Distros on USB Flashdisk 4 GB.
Do not have any problem.
Android-x86 had few default applications if compared to standard linux
distros (OpenOffice, Gimp, mplayer,..etc).

Post by Abhay kumar
That's true i had tested this tree on some diffrent maufacture x86 it just
work out of the box.
May be it is not supporting your hardware.
You can get logcat results and share it with us.
cheers

Post by Chih-Wei Huang
Hey, we already have a generic_x86 target
that supposes to work on all x86 platforms ideally.
Of course it's not so perfect.
If you found it doesn't work on your device,
it is considered a bug.
Feel free to fix it and send us a patch.
On the other hand, we have several targets
for some particular x86 platforms.
Why we need such targets if generic_x86
also works on the particular platforms?
* For optimizations. The kernel can be stripped
 by removed hundreds of unused drivers.
 The libraries can also be optimized for the
 target cpu.
* For customizations. The target maintainers
 may add some unique features that
 only available for their targets.
 (e.g., hw accel, gps, 3G, backlight, ...)

Post by Alexandru Stoian
I share the same feelings about this. Would love to see a generic_x86
or atleast a generic atom build similar to what meego has.

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

--
Abhay kumar
([phone]
 --
You received this message because you are subscribed to the Google Groups
"Android-x86" group.
To unsubscribe from this group, send email to
.
For more options, visit this group at
http://groups.google.com/group/android-x86?hl=en.

[fishman]

Personally I don't see why not have different kernel configs for the
different hardware. If someone wants to add a kernel for various via
hardware that would work better / faster than the generic kernel would
that be so bad?

J

Post by ady2k10
Sure, many android smartphone and Android tablet customized their own
android kernel.
Because they didn't connect to another devices (hardware limited and
Used ARM Processor)
Android kernel for smartphone and Tablet became very slim.
I dont' think It should make android-x86 kernel likes Android
Smartphone or Android Tablet.

Post by supriady
I don't think have a big problem if android-x86 kernel was too big.
Because android-x86 cam install on Netbook/Laptop even PC with harddisk/USB
Flashdisk 4 GB.
I have tried to install Ubuntu Netbook Edition 10.10 and others on USB
Flashdisk 4 GB and was running fine.
And I have tested many Linux Distros on USB Flashdisk 4 GB.
Do not have any problem.
Android-x86 had few default applications if compared to standard linux
distros (OpenOffice, Gimp, mplayer,..etc).

Post by Abhay kumar
That's true i had tested this tree on some diffrent maufacture x86 it just
work out of the box.
May be it is not supporting your hardware.
You can get logcat results and share it with us.
cheers

Post by Chih-Wei Huang
Hey, we already have a generic_x86 target
that supposes to work on all x86 platforms ideally.
Of course it's not so perfect.
If you found it doesn't work on your device,
it is considered a bug.
Feel free to fix it and send us a patch.
On the other hand, we have several targets
for some particular x86 platforms.
Why we need such targets if generic_x86
also works on the particular platforms?
* For optimizations. The kernel can be stripped
 by removed hundreds of unused drivers.
 The libraries can also be optimized for the
 target cpu.
* For customizations. The target maintainers
 may add some unique features that
 only available for their targets.
 (e.g., hw accel, gps, 3G, backlight, ...)

Post by Alexandru Stoian
I share the same feelings about this. Would love to see a generic_x86
or atleast a generic atom build similar to what meego has.

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

--
Abhay kumar
([phone]
 --
You received this message because you are subscribed to the Google Groups
"Android-x86" group.
To unsubscribe from this group, send email to
.
For more options, visit this group at
http://groups.google.com/group/android-x86?hl=en.

[supriady]

Hi fishman,

One brand likes ASUS had many different devices for different EEEPC.Are you
sure One Android EEEPC image can work for All EEEPC (9",10",12") ?
Is Android-x86 project running on android smartphone and Android Tablet?
Do you know Netbook/EEEPC can run Win 7 ?
If you complained slow to run generic android on Netbook.
Maybe you will not install win7 on Netbook.
Thanks

Post by fishman
Personally I don't see why not have different kernel configs for the
different hardware. If someone wants to add a kernel for various via
hardware that would work better / faster than the generic kernel would
that be so bad?
J

Post by ady2k10
Sure, many android smartphone and Android tablet customized their own
android kernel.
Because they didn't connect to another devices (hardware limited and
Used ARM Processor)
Android kernel for smartphone and Tablet became very slim.
I dont' think It should make android-x86 kernel likes Android
Smartphone or Android Tablet.

Post by supriady
I don't think have a big problem if android-x86 kernel was too big.
Because android-x86 cam install on Netbook/Laptop even PC with

harddisk/USB

Post by ady2k10

Post by supriady
Flashdisk 4 GB.
I have tried to install Ubuntu Netbook Edition 10.10 and others on USB
Flashdisk 4 GB and was running fine.
And I have tested many Linux Distros on USB Flashdisk 4 GB.
Do not have any problem.
Android-x86 had few default applications if compared to standard linux
distros (OpenOffice, Gimp, mplayer,..etc).

Post by Abhay kumar
That's true i had tested this tree on some diffrent maufacture x86 it

just

Post by ady2k10

Post by supriady

Post by Abhay kumar
work out of the box.
May be it is not supporting your hardware.
You can get logcat results and share it with us.
cheers
On Mon, Nov 29, 2010 at 7:30 AM, Chih-Wei Huang <

Post by Chih-Wei Huang
Hey, we already have a generic_x86 target
that supposes to work on all x86 platforms ideally.
Of course it's not so perfect.
If you found it doesn't work on your device,
it is considered a bug.
Feel free to fix it and send us a patch.
On the other hand, we have several targets
for some particular x86 platforms.
Why we need such targets if generic_x86
also works on the particular platforms?
* For optimizations. The kernel can be stripped
by removed hundreds of unused drivers.
The libraries can also be optimized for the
target cpu.
* For customizations. The target maintainers
may add some unique features that
only available for their targets.
(e.g., hw accel, gps, 3G, backlight, ...)

Post by Alexandru Stoian
I share the same feelings about this. Would love to see a

generic_x86

Post by ady2k10

Post by supriady

Post by Abhay kumar

Post by Chih-Wei Huang

Post by Alexandru Stoian
or atleast a generic atom build similar to what meego has.

--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
You received this message because you are subscribed to the Google

Groups

Post by ady2k10

Post by supriady

Post by Abhay kumar

Post by Chih-Wei Huang
"Android-x86" group.
To unsubscribe from this group, send email to
.
For more options, visit this group at
http://groups.google.com/group/android-x86?hl=en.

--
Abhay kumar
([phone]
--
You received this message because you are subscribed to the Google

Groups

Post by ady2k10

Post by supriady

Post by Abhay kumar
"Android-x86" group.
To unsubscribe from this group, send email to
.
For more options, visit this group at
http://groups.google.com/group/android-x86?hl=en.

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