public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Dittmer <jdi@l4x.org>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: bryan.wu@analog.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Blackfin arch fixes (try #2)
Date: Wed, 04 Jul 2007 22:38:21 +0200	[thread overview]
Message-ID: <468C053D.9050302@l4x.org> (raw)
In-Reply-To: <8bd0f97a0707031055h7b97c0cerbd2314a2836f7798@mail.gmail.com>

Mike Frysinger wrote:
> On 7/3/07, Jan Dittmer <jdi@l4x.org> wrote:
>> Bryan Wu wrote:
>>> Jie's patch is required because we will release our new Blackfin toolchain.
>> So, what is the new toolchain version?
>> gcc 4.1.1 (adi 07r1) / binutils 2.17 doesn't seem to work anymore:
> 
> we'll post new toolchain binaries in a bit

Hrm, somehow I don't understand it. On [1] you're
talking about gcc 4.1.2 and binutils 2.17 supporting
the -mcpu switch. But if you download the 2007R1 RC9
toolchain from the Files section of the site (tar.gz)
you actually get 4.1.1 without mcpu support. But the
version string from gcc indicates 07r1.
Care to explain?

Thanks,

Jan

ps: All in all it is a bit unfortunate to put features
    in the upstream kernel for a toolchain version just
    available from svn.


[1]
http://docs.blackfin.uclinux.org/doku.php?id=toolchain_release_notes_2007r1


  reply	other threads:[~2007-07-04 20:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-03  0:37 [GIT PULL] Blackfin arch fixes (try #2) Bryan Wu
2007-07-03 13:58 ` Jan Dittmer
2007-07-03 17:55   ` Mike Frysinger
2007-07-04 20:38     ` Jan Dittmer [this message]
2007-07-06  7:22       ` Mike Frysinger
2007-07-06  7:51         ` Jan Dittmer
2007-07-12 21:02           ` Mike Frysinger
2007-07-10 18:44         ` Jan Dittmer
2007-07-10 21:42           ` Robin Getz
2007-07-11  2:09           ` Bryan Wu

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=468C053D.9050302@l4x.org \
    --to=jdi@l4x.org \
    --cc=bryan.wu@analog.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vapier.adi@gmail.com \
    /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