I case a static build of busybox is good enough for you, you can
follow this tutorial:
http://wiki.androidx86.org/index.php?title=Installing_BusyBox
With the tool chain questions I can't help you...
Dani
On Mar 14, 7:11 pm, neilnguyen_2...@yahoo.com
neilnguyen_2...@yahoo.com wrote:
Dear all:
driver. But when I put a
printk(Test IRQ\n); in the file at the interrupt handler and then
touch the screen, it's not printing anything... Still finding out how
it works. When I call geteevent, it does react on touchscreen input.
On 11 mrt, 08:05, squix dani.eichh...@squix.ch wrote:
Hi
My
: KEY=3 0 0 0 0 0 0 0 0
B: ABS=3
B: MSC=10
On 11 mrt, 10:40, squix dani.eichh...@squix.ch wrote:
I don't really understand that much of linux drivers. I thought that
at least for the serial module a parameter for the kernel would be
needed. My controller is attached directly
Did you get busybox to run on x86? If yes, how did your build commands
look like, how your Android.mk?
Dani
On Feb 4, 7:36 pm, AndyM andrewdm...@gmail.com wrote:
when you build busy box there is an option to build statically. That
may be your best bet to get it running on x86.
On Feb 4,
with Android. You
just need to configure busybox by: make menuconfig
Hope it helps.
--
Chen
On Tue, Mar 10, 2009 at 8:18 PM, squix dani.eichh...@squix.ch wrote:
Did you get busybox to run on x86? If yes, how did your build commands
look like, how your Android.mk?
Dani
On Feb 4, 7:36 pm
The mainboard that I'm trying to run android on can't boot from a usb
pendrive but is able to boot from external USB HDD. How do I have to
modify Chris make-live script to be able to run the live image from my
USB harddisk? The BIOS seems also to limit the boot partition to be
within the first
)http://pastebin.com/f26fe5376
4) No sound yet.
SVGA (vga=788) works but on wrong aspect ratio because LCD panel
is 1024x600
On Jan 28, 3:44 am, squix dani.eichh...@squix.ch wrote:
Hi list
I'm trying to put together an overview for the current state of
supported x86 hardware running
Hi list
I'm trying to put together an overview for the current state of
supported x86 hardware running android. Since my own targeted hardware
(PPC-1210/ Geode GX1/ Wafer Board 5822) isn't running yet I could use
your input about your hardware. You'll find the wiki page at
Hi Jeroen
I just saw that someone added a tutorial about how to build the kernel
for Geode LX to the Wiki, I guess that was you? Thanks!
I pimped it a little bit, I hope you don't mind...
--Dani
On Jan 20, 7:48 am, squix dani.eichh...@squix.ch wrote:
That sounds great! When I had my own
and increasing the root delay a bit,
android seems to boot, but I am currently stuck with framebuffer
issues. I have a blank screen with Geode framebuffer and a kernel
panic with vesafb, but I'm investigating that as I have more time.
Jeroen
On Jan 18, 8:53 pm, squix dani.eichh...@squix.ch
Hi everybody
I got tired of pull together all the little bits and pieces from the
many x86 related threads in this forum and I setup a website for this
purpose: http://www.androidx86.org
Don't get me wrong, I think this list is great, but the information I
need is scattered all over the place
plans. (Also a Geode GX with touchscreen
for home automation.)
Regards
Jeroen
On Jan 18, 1:04 pm, squix dani.eichh...@squix.ch wrote:
Hi everybody
I got tired of pull together all the little bits and pieces from the
many x86 related threads in this forum and I setup a website
Thanks for your answer. When I try to compile the kernel with the
config file from the eee project I get the following error and I have
no clue how to solve it:
CC=gcc-4.2 CXX=g++-4.2 make ARCH=x86 CROSS-COMPILE=
CHK include/linux/version.h
CHK include/linux/utsrelease.h
CALL
Sorry for such a stupid question, but is the kernel provided in anyway
patched for the use with android or is it basically a standard x86
kernel? What do I have to do to build a kernel for an older target
like a Geode GX1?
Dani
On Dec 23, 2:43 am, Dima Zavin d...@android.com wrote:
Although
believe it should already be built as 32-bit. In case of doubt, check
build/core/combo/linux-x86.mk which contains all compiler/link flags
definitions for linux x86 (also used on x86_64 machines)
On Sat, Dec 20, 2008 at 11:07 AM, squix dani.eichh...@squix.ch wrote:
How can I make sure
I had the same problem. It has to to with the gcc version your using
and the header refactoring that they did for that version. You can fix
errors like that by simply adding the right includes in the file
complaining.
In 90% I had to add one of these
#include cstdlib
#include cstring
but there
16 matches
Mail list logo
