From: Robert Schwebel <r.schwebel@pengutronix.de>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: Adrian Bunk <bunk@kernel.org>,
hskinnemoen@atmel.com, linux-kernel@vger.kernel.org
Subject: Re: Working upstream toolchain for avr32?
Date: Fri, 14 Dec 2007 21:55:42 +0100 [thread overview]
Message-ID: <20071214205542.GO3851@pengutronix.de> (raw)
In-Reply-To: <8bd0f97a0712141235h48c3062cl139e4c2883a815a9@mail.gmail.com>
On Fri, Dec 14, 2007 at 03:35:36PM -0500, Mike Frysinger wrote:
> > Upstream plus a well defined patch stack with well documented patches
> > would definitely be preferred here.
Well, tell me that it is wrong, but isn't it common community
methodology to have rebasable things like patch stacks or git trees
against mainline instead of disconnected vendor trees?
> as you've been told in the past, the things are documented. go read
> the ChangeLog.bfin file.
You didn't explain how for example your trunk [1] is related to mainline
[2].
> > Ah, that sounds pretty good! At the moment we still need three different
> > toolchains to build u-boot, the kernel
>
> maybe, if you're using different version of u-boot and the kernel.
> but that isnt a good idea anyways.
We use mainline linux and u-boot-v2, which is surely not what ADI
supplies officially to their random commercial customers. Nevertheless,
it is the way community technology works elsewhere.
> > and the icebear tools, which is not very satisfying.
>
> there's nothing we can do about this and you're complaining to the
> wrong people. icebear is a third party binary-only tool.
Hmm, the sources are here: http://www.section5.ch/dsp/icebear/bfloader-1.2.tgz
Do you have a good hint for a better low level debug tool? For all other
processors like ARM, PowerPC and ColdFire we use a BDI2000, but it seems
not to be available for blackfin.
> if you dont like the way the third party does things, complain to
> the third party. or dont buy their product.
Thanks for the constructive comments.
> we are upstream and we've given you blessed toolchains.
"Trust us, we are $BIG_VENDOR" is not the way these things are usually
done. Sorry, I don't buy this. Chip vendors just too often lose interest
in supporting their users once they have moved to the next generations
of chips or whatever.
Can you explain why bfin should not have gcc.gnu.org as it's upstream?
Robert
[1] http://blackfin.uclinux.org/gf/project/toolchain/scmsvn/?action=browse&path=%2Ftrunk%2F
[2] http://gcc.gnu.org/viewcvs/trunk/
--
Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
Pengutronix - Linux Solutions for Science and Industry
Handelsregister: Amtsgericht Hildesheim, HRA 2686
Hannoversche Str. 2, 31134 Hildesheim, Germany
Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9
next prev parent reply other threads:[~2007-12-14 20:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 19:56 Adrian Bunk
2007-12-14 9:41 ` Haavard Skinnemoen
2007-12-28 8:52 ` Adrian Bunk
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 [this message]
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=20071214205542.GO3851@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--cc=bunk@kernel.org \
--cc=hskinnemoen@atmel.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
Powered by JetHome