From: Nicola Ranaldo <ranaldo@unina.it>
To: openembedded-devel@openembedded.org
Subject: Angstrom and h2200
Date: Fri, 23 Feb 2007 13:26:36 +0100 [thread overview]
Message-ID: <200702231326.37015.ranaldo@unina.it> (raw)
New test images boots over my ipaq h2200, and bug #1677 is now closed, howewer
i had to disable the S10checkroot.sh startup as it wanted to run fsck over a
readwrite mounted filesystem, claiming it's very dangerous and asking the
user for a confirmation. This should be patched in some manner. I tried to
change the fs to reiserfs, rebuilding the kernel, but i was not lucky. To
disable the bootsplash i readed the S00psplash script and patched startup.txt
of haret, but to have a console over the frame buffer i ran make menuconfig
on the kernel dir, changed the config and after that removed the kernel
compile stamp, and runned again bitbake amstrong-gpe-image again.
Wath's the official/legacy method to give a different configuration to the
kernel?
And now some other issues about gpe-image:
* the usb0-eth device is not present, is it normal?
* keyboard, fonts are bigger then rects and sometimes i have to hold down the
pen to use it, if not the keyboard acts as i pressed the key and a backspace
* i was not able to compile a custom gpe-image (i used the prereleased for
tests), the build failed on package freetype with:
./configure: line 2943: i686-pc-linux-gnu: command not found
configure: error: native C compiler is not working
* the last, may i use some kind of emulator before deploying the fs image to
the ipaq?
Hoping i'm not boring you
Best Regards
Nicola Ranaldo
next reply other threads:[~2007-02-23 12:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-23 12:26 Nicola Ranaldo [this message]
[not found] ` <7010259346.20070225203430@gmail.com>
2007-02-26 10:44 ` Angstrom and h2200 Nicola Ranaldo
2007-02-26 11:15 ` testing with qemu, was " Nicola Ranaldo
2007-02-26 12:03 ` Patrick Fischer
2007-02-26 21:05 ` Richard Purdie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200702231326.37015.ranaldo@unina.it \
--to=ranaldo@unina.it \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.