All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot/IXP
Date: Mon, 5 Mar 2012 23:09:04 +0100	[thread overview]
Message-ID: <201203052309.04883.marex@denx.de> (raw)
In-Reply-To: <CAJ+oik0_5ybzjrm4YjsKMpZ5YyExkf0+kJfj2Fhe=ewUrV+9KQ@mail.gmail.com>

Dear Bryan Hundven,

> On Mon, Mar 5, 2012 at 12:15 PM, Marek Vasut <marex@denx.de> wrote:
> > Dear Michael Schwingen,
> > 
> >> Am 03/05/2012 12:54 PM, schrieb Marek Vasut:
> >> > Dear Michael Schwingen,
> >> > 
> >> >> On Mon, Mar 05, 2012 at 02:14:56AM +0100, Marek Vasut wrote:
> >> >>> Dear Michael Schwingen,
> >> >>> 
> >> >>> do you still intend to maintain IXP support in uboot or can all
> >> >>> those IXP boards be removed? I'd be great if you helped bringing
> >> >>> them back in-line!
> >> >> 
> >> >> I still use them and would want to keep these boards (and maintain
> >> >> them).
> >> >> 
> >> >> I only glimpse at the mailing list from time to time - are there any
> >> >> open problems with these boards that need to be addressed?
> >> > 
> >> > No, I just cannot compile it with usual arm-linux-gnueabi- toolchain
> >> > and that puts a bleep on my bug-radar. Is that normal? Do I need a
> >> > special toolchain?
> >> 
> >> I am using an old, locally built toolchain that identifies itself as
> >> gcc version 4.3.4 (crosstool-NG-hg_default at 1471_4a88cb9bfe8f)
> >> 
> >> I can take a look at this using a newer toolchain - however, I am in the
> >> process of moving, so this will probably take some weeks.
> >> 
> >> What prebuilt toolchain should I try?
> > 
> > I was more curious if it's possible for me myself to build these. And if
> > so, can that be done with usual arm-linux-gnueabi- toolchain? Or do I
> > need special armeb toolchain compiled in some special way?
> 
> I've built a new armeb xscale toolchain available here if you want to try
> it.
> https://sourceforge.net/projects/bhundven.u/files/armeb-unknown-linux-gnue
> abi.tar.bz2/download
> 
> I built it on x86_64. I can build it on 32-bit intel if you don't have
> an x86_64 build box. Let me know.
> 
> $ ct-ng show-armeb-unknown-linux-gnueabi
> armeb-unknown-linux-gnueabi  [L X]
>     OS             : linux-3.2.8
>     Companion libs : gmp-5.0.2 mpfr-3.1.0 ppl-0.11.2 cloog-ppl-0.15.11
> mpc-0.9 libelf-0.8.13
>     binutils       : binutils-2.22
>     C compiler     : gcc-4.6.3
> (C,C++,Fortran,Java,Objective-C,Objective-C++) C library      :
> eglibc-2_15
>     Tools          : dmalloc-5.5.2 duma-2_5_15 gdb-7.3a ltrace-0.5.3
> strace-4.6
> 
Ok, that's good. But can someone please answer my question (now there are two)?

1) Does usual arm-linux-gnueabi- toolchain work? (possibly if I use some switch 
to toggle arm core endianness)
2) Do I need any special options to build the toolchain?

Best regards,
Marek Vasut

  reply	other threads:[~2012-03-05 22:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-05  1:14 [U-Boot] U-Boot/IXP Marek Vasut
2012-03-05  7:34 ` Michael Schwingen
2012-03-05 11:54   ` Marek Vasut
2012-03-05 19:34     ` Michael Schwingen
2012-03-05 20:15       ` Marek Vasut
2012-03-05 22:00         ` Bryan Hundven
2012-03-05 22:09           ` Marek Vasut [this message]
2012-03-05 22:14             ` Bryan Hundven
2012-03-05 22:22               ` Marek Vasut
2012-03-05 22:31                 ` Bryan Hundven
2012-03-05 23:00                   ` Marek Vasut
2012-03-05 22:51               ` Michael Schwingen

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=201203052309.04883.marex@denx.de \
    --to=marex@denx.de \
    --cc=u-boot@lists.denx.de \
    /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.