All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Schwingen <rincewind@discworld.dascon.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot/IXP
Date: Mon, 05 Mar 2012 20:34:02 +0100	[thread overview]
Message-ID: <4F55152A.8080003@discworld.dascon.de> (raw)
In-Reply-To: <201203051254.17795.marex@denx.de>

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?

cu
Michael

  reply	other threads:[~2012-03-05 19:34 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 [this message]
2012-03-05 20:15       ` Marek Vasut
2012-03-05 22:00         ` Bryan Hundven
2012-03-05 22:09           ` Marek Vasut
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=4F55152A.8080003@discworld.dascon.de \
    --to=rincewind@discworld.dascon.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.