LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Haavard Skinnemoen <hskinnemoen@atmel.com>
Cc: Matthew Wilcox <matthew@wil.cx>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Greg KH <greg@kroah.com>, Mark Fasheh <mark.fasheh@oracle.com>
Subject: Re: linux-next: semaphore update merge conflicts
Date: Fri, 29 Feb 2008 23:30:19 +1100	[thread overview]
Message-ID: <20080229233019.780abba7.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20080229132514.00d5087e@hskinnemoen.norway.atmel.com>

[-- Attachment #1: Type: text/plain, Size: 915 bytes --]

On Fri, 29 Feb 2008 13:25:14 +0100 Haavard Skinnemoen <hskinnemoen@atmel.com> wrote:
>
> On Fri, 29 Feb 2008 23:17:04 +1100
> Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> > By the way, is there some place I can get a cross compiler to build avr32
> > kernels (or better yet a recipe for crosstool to make one)?
> 
> You can get the official toolchain from this page:
> 
> http://www.atmel.com/dyn/products/tools_card.asp?tool_id=4118
> 
> I'm not sure about crosstool, but you can get a patched version of
> buildroot from this page:
> 
> http://www.atmel.no/buildroot/
> 
> Maybe you can just grab the patches from buildroot and use them with
> crosstool? Or I can send them to you if you don't want to download the
> whole thing.

I'll have a look and let you know.  Thanks.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2008-02-29 12:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-29  4:39 Stephen Rothwell
2008-02-29 10:17 ` Haavard Skinnemoen
2008-02-29 12:17   ` Stephen Rothwell
2008-02-29 12:25     ` Haavard Skinnemoen
2008-02-29 12:30       ` Stephen Rothwell [this message]

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=20080229233019.780abba7.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=greg@kroah.com \
    --cc=hskinnemoen@atmel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mark.fasheh@oracle.com \
    --cc=matthew@wil.cx \
    --subject='Re: linux-next: semaphore update merge conflicts' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).