Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Dooks <ben@fluff.org>
To: buildroot@busybox.net
Subject: [Buildroot] ARM EABI builds
Date: Fri, 29 Jun 2007 10:31:51 +0100	[thread overview]
Message-ID: <20070629093151.GC3856@trinity.fluff.org> (raw)
In-Reply-To: <468459AE.40807@gmail.com>

On Thu, Jun 28, 2007 at 06:00:30PM -0700, Tom wrote:
> 
> 
> 
> Bernhard Fischer wrote:
> > On Thu, Jun 28, 2007 at 03:54:22PM -0400, Stuart Wood wrote:
> >> Just a note on what Tom said about user land application. I've already 
> > 
> > Just as a note on what everybody seems to say about configuring GCC:
> > It is very amusing that you guys seem to be excited about _not_ setting
> > a config option -- CONFIG_BR2_EXTRA_TARGET_GCC_CONFIG_OPTIONS -- which
> > is specifically exported to you, to spell out specific requirements put
> > upon gcc (other toolchain parts of course also provide said means for
> > hand-crafted  options, mind you).
> 
> Speaking for myself, I am not excited about any particular option. Also 
> I don't need a doctor for this anymore, as for my part it works. Now.
> 
> However, as the combination EABI and ARM9 seems to be popular, I thought 
> it would be nice to save others some of this trouble that they are bound 
> to run into (*), either by just mentioning the option or by setting it 
> automatically in buildroot. If you are saying that 
> CONFIG_BR2_EXTRA_TARGET_GCC_CONFIG_OPTIONS is better suited for the 
> required target CPU option than BR2_EXTRA_GCC_CONFIG_OPTIONS, that could 
> very well be.
> 
> (*) This is the error I got after kernel boot on ARM920T/EABI default 
> config, w/o the required CPU option:
> init (1): undefined instruction: pc=00008c60

That is interesting, because I haven't been getting that when my
system fails. I'll check the setup of /dev/console and the /dev
entries for the serial ports. This would have been very helpful in
pointing out the problem. 

As an aside, it would be possible to fix the instruction in the
kernel's undefined instruction trap (as is done to emulate the
old hardware floating point instructions on newer processors) but
I personally feel that this is something the kernel should not
have to be doing.

[snip]

-- 
Ben

Q:      What's a light-year?
A:      One-third less calories than a regular year.

  reply	other threads:[~2007-06-29  9:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-28 19:54 [Buildroot] ARM EABI builds Stuart Wood
2007-06-28 23:01 ` Bernhard Fischer
2007-06-29  1:00   ` Tom
2007-06-29  9:31     ` Ben Dooks [this message]
2007-06-29  1:42   ` Alex Stewart
2007-06-29  7:16     ` Bernhard Fischer
2007-06-29  9:26   ` Ben Dooks
  -- strict thread matches above, loose matches on Subject: below --
2007-06-26 13:33 Ben Dooks
2007-06-26 21:19 ` Tom
2007-06-26 22:25   ` Ben Dooks
2007-06-27  8:19     ` Ben Dooks
2007-06-27  9:03       ` Konstantin Kletschke
2007-06-27 15:25         ` Ben Dooks
2007-06-27 17:44       ` Tom
2007-06-28 10:34         ` Ben Dooks
2007-06-28 19:13           ` Tom
2007-06-29 13:52             ` Ben Dooks
2007-06-28 22:50           ` Ulf Samuelsson
2007-06-28 23:57             ` Tom
2007-06-29 13:53               ` Ben Dooks

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=20070629093151.GC3856@trinity.fluff.org \
    --to=ben@fluff.org \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox