All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicola Ranaldo <ranaldo@unina.it>
To: Paul Sokolovsky <pmiscml@gmail.com>, openembedded-devel@openembedded.org
Subject: Re: Angstrom and h2200
Date: Mon, 26 Feb 2007 11:44:48 +0100	[thread overview]
Message-ID: <200702261144.48348.ranaldo@unina.it> (raw)
In-Reply-To: <7010259346.20070225203430@gmail.com>

On Sunday 25 February 2007 19:34:30 Paul Sokolovsky wrote:

Hello Paul!

[...]
> Friday, February 23, 2007, 2:26:36 PM, you wrote:
> > Hoping i'm not boring you
>
>   No, but this is OpenEmbedded list. Your report would give more use
> if posted to the proper list - angstrom-distro-users (where I route
> this reply).

Ok!, i will redirect angstrom related questions there.

> > 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.
>
>   Well, this is one boring problem which is very hard to solve,
> because it is rooted in machine idiosyncrasies. You fix it for one
> machine, and it pops up with another, etc., until it goes thru the
> full circle, something changes outside, and the first machine breaks
> again.
>
>   Someone indeed should break this vicious cycle and make a solution
> which either cuts down mentioned idiosyncrasies or flies above them.

Are there so many differences between machines? i thinked the only difference 
was in the kernel and input devices configuration files.

>   There's an RFC to have consistent (feature-wise) defconfigs for all
> machines. h3900 & h4000 already joined the party. You're welcome to
> work towards h2200 support, please start here:
> http://defconfigman.sourceforge.net/
>
> > And now some other issues about gpe-image:
> > * the usb0-eth device is not present, is it normal?
>
>   No, it is not. See about defconfig consistency above.

I will take a look at it, howewer to customize my kernel configuration is 
there a tool, bitbake config, etc, to submit a .config or to run make 
menuconfig before building the kernel?

[...]
> > * 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
>
>   There's some incompatibility with freetype's configure and your
> gentoo gcc.

Other peoples seems to have the same problem,  with patch in #1906 it seems to 
be fixed, if some one may review the proposed patch and commit to the 
tree.

> > * the last, may i use some kind of emulator before deploying the fs image
> > to the ipaq?
>
>   Yes, QEMU.

fork in a new thread !

Thanks Paul!

	Nicola Ranaldo



  parent reply	other threads:[~2007-02-26 10:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-23 12:26 Angstrom and h2200 Nicola Ranaldo
     [not found] ` <7010259346.20070225203430@gmail.com>
2007-02-26 10:44   ` Nicola Ranaldo [this message]
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=200702261144.48348.ranaldo@unina.it \
    --to=ranaldo@unina.it \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.org \
    --cc=pmiscml@gmail.com \
    /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.