From: Markus Heidelberg <markus.heidelberg@web.de>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot maintainer and stable releases
Date: Wed, 7 Jan 2009 13:19:00 +0100 [thread overview]
Message-ID: <200901071319.00644.markus.heidelberg@web.de> (raw)
In-Reply-To: <87y6xnldvt.fsf@macbook.be.48ers.dk>
Peter Korsgaard, 07.01.2009:
> >>>>> "Markus" == Markus Heidelberg <markus.heidelberg@web.de> writes:
>
> (resend with trimmed Cc line to please mailman)
What was the problem with the former mail?
In my sent mail you, Ulf and HCE were on Cc, but when receiving my mail
from the list, only Ulf was on Cc, you and HCE were gone. Is this a
related problem? How to fix it?
> I don't know anything about this Atmel fork (where is it?), but as
> avr32 is maturing, long term I don't see why we cannot support it in
> uclibc buildroot.
You can find references to it on the AVR32 Linux site avr32linux.org
under "DevelopemtTools", there is also a link to
http://www.atmel.no/buildroot/
They also keep several packages on
http://www.atmel.no/buildroot/source/mirror/
It used to be just the packages missing on the upstream mirror but just
looking at it, it seems to be much more packages now, if not all
packages activated by default.
I don't remember where to find the git URL, but I did it somehow once:
git://www.atmel.no/~hcegtvedt/buildroot/avr32.git
> Right now things are kind of a mess as avr32 is lacking from most
> upstream projects, so there's lots of big patches involved. As things
> are now, I don't see missing avr32 as a showstopper for a first
> release.
Absolutely agreed. Especially given that there is this well-supported
AVR32 fork (which isn't really a fork I think, it rather sits on top of
uclibc-buildroot).
> Markus> Yes, mplayer for example is more than 2 years old and includes a huge
> Markus> avr32 patch.
>
> Exactly. Who will redo this patch if I bump the mplayer version?
I tried it some weeks ago. I think it should have worked, but I got
a compile error that wasn't related to the patch as far as I remember
and judge. I had some time consuming toolchain rebuilds and then I
noticed that the new version wasn't really necessary, so I stopped
investigating further and stayed with the current version.
And even if it worked, this is not a solution. Someone should make it
ready and submit it upstream and it's definetly not me, I haven't
written the patch and cannot say anything about it's maturity.
If nobody involved in this patch has the time to do it, it should best
be thrown out of uclibc-buildroot and just be kept in HCE's repo.
Markus
next prev parent reply other threads:[~2009-01-07 12:19 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 21:18 [Buildroot] Buildroot maintainer and stable releases Peter Korsgaard
2009-01-06 12:02 ` Ulf Samuelsson
2009-01-06 12:39 ` Ulf Samuelsson
2009-01-06 12:55 ` Peter Korsgaard
2009-01-06 15:32 ` Ulf Samuelsson
2009-01-06 12:44 ` Peter Korsgaard
2009-01-07 3:09 ` Markus Heidelberg
2009-01-07 8:08 ` Peter Korsgaard
2009-01-07 8:27 ` Peter Korsgaard
2009-01-07 8:31 ` Nigel Kukard
2009-01-07 12:19 ` Markus Heidelberg [this message]
2009-01-07 13:02 ` Peter Korsgaard
2009-01-07 14:01 ` Thiago A. Corrêa
2009-01-08 17:50 ` Markus Heidelberg
2009-01-08 18:29 ` Ulf Samuelsson
2009-01-08 20:28 ` Markus Heidelberg
2009-01-08 21:05 ` Ulf Samuelsson
2009-01-08 22:06 ` Markus Heidelberg
2009-01-08 22:33 ` Ulf Samuelsson
2009-01-08 23:13 ` Markus Heidelberg
2009-01-09 9:15 ` Peter Korsgaard
2009-01-09 9:12 ` Peter Korsgaard
2009-01-07 11:13 ` Ulf Samuelsson
2009-01-07 11:28 ` Peter Korsgaard
2009-01-07 12:10 ` Ulf Samuelsson
2009-01-07 12:24 ` Nigel Kukard
2009-01-07 12:57 ` Peter Korsgaard
2009-01-07 18:13 ` Thomas Lundquist
2009-01-07 19:16 ` Ulf Samuelsson
2009-01-07 19:39 ` Peter Korsgaard
2009-01-08 8:25 ` Thomas Lundquist
2009-01-08 9:10 ` Peter Korsgaard
2009-01-07 11:50 ` Markus Heidelberg
2009-01-07 11:54 ` Peter Korsgaard
2009-01-07 12:55 ` Ulf Samuelsson
2009-01-06 14:01 ` Thomas Lundquist
2009-01-06 15:08 ` Peter Korsgaard
2009-01-06 18:32 ` Thomas Lundquist
2009-01-06 18:52 ` Peter Korsgaard
2009-01-06 19:09 ` Ulf Samuelsson
2009-01-06 19:23 ` Peter Korsgaard
2009-01-07 18:43 ` Thomas Lundquist
2009-01-07 19:26 ` Ulf Samuelsson
2009-01-07 20:22 ` Thomas Lundquist
2009-01-07 20:31 ` Peter Korsgaard
2009-01-08 8:27 ` Thomas Lundquist
2009-01-08 9:12 ` Peter Korsgaard
2009-01-08 10:02 ` Thomas Lundquist
2009-01-07 23:42 ` Ulf Samuelsson
2009-01-08 9:00 ` Peter Korsgaard
2009-01-06 14:52 ` Nigel Kukard
2009-01-06 15:01 ` Peter Korsgaard
2009-01-08 21:00 ` Markus Heidelberg
2009-01-06 18:22 ` Thiago A. Corrêa
2009-01-06 18:33 ` Peter Korsgaard
2009-01-06 18:53 ` Thiago A. Corrêa
2009-01-06 18:55 ` Ulf Samuelsson
2009-01-06 19:19 ` Peter Korsgaard
2009-01-06 19:02 ` Ulf Samuelsson
2009-01-06 19:16 ` Peter Korsgaard
2009-01-06 20:49 ` Ulf Samuelsson
2009-01-07 11:29 ` Peter Korsgaard
2009-01-07 12:34 ` Ulf Samuelsson
2009-01-07 13:15 ` Peter Korsgaard
2009-01-07 18:02 ` Thomas Lundquist
2009-01-07 19:13 ` Ulf Samuelsson
2009-01-07 19:36 ` Peter Korsgaard
2009-01-07 20:36 ` Joe George
2009-01-07 20:47 ` Peter Korsgaard
2009-01-07 23:28 ` Ulf Samuelsson
2009-01-08 8:07 ` Thomas Lundquist
2009-01-08 19:22 ` Steve Calfee
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=200901071319.00644.markus.heidelberg@web.de \
--to=markus.heidelberg@web.de \
--cc=buildroot@busybox.net \
/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