From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] What's up with the kernel names? (Again)
Date: Tue, 10 Feb 2009 10:28:35 +0100 [thread overview]
Message-ID: <87zlgu63p8.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <013101c98b56$14a0a350$f53018ac@Glamdring> (Ulf Samuelsson's message of "Tue\, 10 Feb 2009 09\:02\:44 +0100")
>>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:
Hi,
Ulf> I don't see anywhere where the kernel name is referenced in u-boot
Ulf> except for the generation of the script, which I fixed. Looks like
Ulf> Peter is also unable to guess what you are talking about. Perhaps you
Ulf> might care to enlighten us.
Ulf> ==> Look at the u.-boot patches in device/Atmel/arch-arm/
Ulf, see again why hiding that kind of "magic" under target/device is
bad? If things break for specific platforms because they have feature
patches hidden away under target/device then I think it's pretty
unrealistic for other developers to fix it.
Ulf> ==> I designed the advanced linux configuration to tightly fit
Ulf> together with u-boot
Ulf> to mimize the hassle of getting the board up and running.
Ulf> You can always build the classic linux configuration
Ulf> target/linux/Makefile.in",
Ulf> so unless you are prepared to go the whole way, why meddle?
So maybe the problems we're seing is in that design? I don't use the
linux-advanced stuff, but my feeling is that there's too much "magic"
going around here, and that things are too specialized.
But that's a discussion for another day.
Ulf> Peter has said on other occasions: "fix the problem you
Ulf> created, or revert the patch".
And I agree with that, but it's ofcourse not black/white. What I mean
is that if you make changes, then you need to work with the other
developers to help fix up stuff and/or change it so stuff doesn't
break.
In other words, try to think bigger than just your specific platform.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-02-10 9:28 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 1:49 [Buildroot] What's up with the kernel names? (Again) Thiago A. Corrêa
2009-02-04 7:39 ` Peter Korsgaard
2009-02-04 12:29 ` Peter Korsgaard
2009-02-05 2:33 ` Thiago A. Corrêa
2009-02-05 13:23 ` Peter Korsgaard
2009-02-05 20:37 ` Ulf Samuelsson
2009-02-06 2:28 ` Thiago A. Corrêa
2009-02-06 6:16 ` Ulf Samuelsson
2009-02-06 8:49 ` Peter Korsgaard
2009-02-06 9:06 ` Ulf Samuelsson
2009-02-06 12:30 ` Peter Korsgaard
2009-02-06 8:45 ` Peter Korsgaard
2009-02-06 8:58 ` Ulf Samuelsson
2009-02-06 8:44 ` Peter Korsgaard
2009-02-05 20:23 ` Ulf Samuelsson
2009-02-06 8:41 ` Peter Korsgaard
2009-02-06 8:56 ` Ulf Samuelsson
2009-02-06 12:27 ` Peter Korsgaard
2009-02-06 14:31 ` Thiago A. Corrêa
2009-02-06 15:18 ` Thiago A. Corrêa
2009-02-09 17:24 ` Ulf Samuelsson
2009-02-09 19:34 ` Peter Korsgaard
2009-02-09 22:52 ` Ulf Samuelsson
2009-02-10 1:25 ` Thiago A. Corrêa
2009-02-10 8:02 ` Ulf Samuelsson
2009-02-10 9:28 ` Peter Korsgaard [this message]
2009-02-10 10:32 ` Ulf Samuelsson
2009-02-10 9:17 ` Peter Korsgaard
2009-02-10 10:16 ` Ulf Samuelsson
2009-02-10 12:51 ` Peter Korsgaard
2009-02-10 13:50 ` Ulf Samuelsson
2009-02-10 16:34 ` Thiago A. Corrêa
2009-02-10 17:17 ` Thiago A. Corrêa
2009-02-10 17:42 ` Ulf Samuelsson
2009-02-10 18:48 ` Thiago A. Corrêa
2009-02-11 20:03 ` Ulf Samuelsson
2009-02-11 20:15 ` Peter Korsgaard
2009-02-12 18:16 ` Ulf Samuelsson
2009-02-16 22:21 ` Thiago A. Corrêa
2009-02-17 11:26 ` Peter Korsgaard
2009-02-10 18:26 ` Ulf Samuelsson
2009-02-10 18:50 ` Ulf Samuelsson
2009-02-10 20:06 ` Thiago A. Corrêa
2009-02-10 18:59 ` Ulf Samuelsson
2009-02-10 19:49 ` Ulf Samuelsson
2009-02-10 20:06 ` Peter Korsgaard
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=87zlgu63p8.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.