From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] target/device/Atmel kernel patches
Date: Thu, 29 Jan 2009 17:54:46 +0100 [thread overview]
Message-ID: <87skn2qch5.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <69C4B5A4F9B74F77AE1E58B4F020A786@aeglos> (Ulf Samuelsson's message of "Thu\, 29 Jan 2009 17\:28\:12 +0100")
>>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:
Ulf> As I see it, you get the base kernel from www.kernel.org
Yes, more or less directly, and that's fine for evaluation boards -
But for real development on specialized hardware that's rarely enough,
hence the need for either:
- Provide a way to add project specific patches on top
OR
- Take the kernel from somewhere else (some other
cvs/svn/git/whatever repo).
I suspect we need to support both.
Ulf> and if you dont want to host kernel patches for AT91, then
Ulf> it will be no problem to download them from $(ATMEL_MIRROR).
Ulf> I just think there are other things in higher need of attention
Ulf> than removing these patches RIGHT NOW.
Ulf> I see that moving these patches from svn to a mirror should
Ulf> be done before the next release of buildroot.
No, but we're doing a bunch of cleanups now - And as I mentioned before,
the arch-arm directory seems a bit extreme as it is.
I don't think adding a bunch of special case handling to buildroot to
download AT91 patches from somewhere is a better solution. We should
rather generalize the setup so you can handle it outside BR and just
point BR to a repo or a directory full of patches.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-01-29 16:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 21:03 [Buildroot] target/device/Atmel kernel patches Peter Korsgaard
2009-01-26 21:29 ` Ulf Samuelsson
2009-01-26 21:37 ` Peter Korsgaard
2009-01-26 22:19 ` Ulf Samuelsson
2009-01-27 9:25 ` Peter Korsgaard
2009-01-29 14:33 ` Ulf Samuelsson
2009-01-29 14:57 ` Peter Korsgaard
2009-01-29 15:27 ` Ulf Samuelsson
2009-01-29 16:03 ` Peter Korsgaard
2009-01-29 16:28 ` Ulf Samuelsson
2009-01-29 16:54 ` Peter Korsgaard [this message]
2009-01-29 18:31 ` Ulf Samuelsson
2009-01-29 19:04 ` Peter Korsgaard
2009-01-29 22:04 ` Ulf Samuelsson
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=87skn2qch5.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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