All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Haavard Skinnemoen <hskinnemoen@atmel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Working upstream toolchain for avr32?
Date: Fri, 28 Dec 2007 10:52:59 +0200	[thread overview]
Message-ID: <20071228085259.GE8911@does.not.exist> (raw)
In-Reply-To: <20071214104158.6d256b7b@dhcp-252-066.norway.atmel.com>

On Fri, Dec 14, 2007 at 10:41:58AM +0100, Haavard Skinnemoen wrote:
> On Thu, 13 Dec 2007 20:56:17 +0100
> Adrian Bunk <bunk@kernel.org> wrote:
> 
> > AFAIK the latest available AVR32 toolchains are some patched gcc 4.0 and 
> > some patched binutils 2.17, and avr32 is currently the only architecture 
> > in the kernel where upstream of both of them is not capable of building 
> > a kernel for the architecture.
> 
> gcc 4.2 is available from www.atmel.com. But I agree that it's
> unfortunate that avr32 support isn't available upstream.
> 
> > ALthough not technically a requirement, it would be nice if all Linux 
> > kernel archs could be compiled with plain upstream toolchains.
> 
> We're working on it. I believe the legal issues around copyright
> assignment, etc. are mostly sorted out now, so I'm hoping we'll start
> pushing things upstream early next year.

First of all sorry for my late answer.

What you are saying is more or less what I was hoping to hear.  :)

> > Even more since at some point in the future [1] current toolchains might 
> > no longer be able to compile the then current kernels.
> 
> I'm not sure if I understood that, but I guess it's always good to have
> older versions of the toolchain around.

My point was that if there was _only_ support in some older toolchain,
a few years from now there might no longer be a toolchain capable of 
compiling the then-current kernel.

> Haavard

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2007-12-28  8:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-13 19:56 Working upstream toolchain for avr32? Adrian Bunk
2007-12-14  9:41 ` Haavard Skinnemoen
2007-12-28  8:52   ` Adrian Bunk [this message]
2007-12-14 20:03 ` Robert Schwebel
2007-12-14 20:21   ` Mike Frysinger
2007-12-14 20:28     ` Robert Schwebel
2007-12-14 20:35       ` Mike Frysinger
2007-12-14 20:55         ` Robert Schwebel
2007-12-14 21:23           ` Mike Frysinger
2007-12-14 21:59             ` Robert Schwebel

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=20071228085259.GE8911@does.not.exist \
    --to=bunk@kernel.org \
    --cc=hskinnemoen@atmel.com \
    --cc=linux-kernel@vger.kernel.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.