From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot: target/devicetarget/device/x86/i386 too etc...
Date: Wed, 11 Apr 2007 17:01:44 +0200 [thread overview]
Message-ID: <01ce01c77c4b$27966e70$254565d5@atmel.com> (raw)
In-Reply-To: 20070411082200.973434808C@busybox.net
While it is nice to have these things, I propose that we put the
linux stuff in a subdirectory of its own.
I.E: targets/linux
which should include a "Config.in" and a "Makefile.in"
Also I think you do not want to store the LINUX26_KCONFIG in just
any place in your file system.
Is it not better to have the configurable, but normally in the board directory?
A more flexible way would be to have the default value to be
$(BR2_BOARD_PATH)/.config
I.E:
config BR2_PACKAGE_LINUX_KCONFIG
string ".config file"
depends on BR2_PACKAGE_LINUX
default "$(BR2_BOARD_PATH)/linux26.config"
help
kernel's .config to use
We should also consider running
"make <board>_defconfig"
on the kernel as an option to providing the kconfig file.
Will send a patch which will do just this, (but not your latest patch)
Best Regards
Ulf Samuelsson
prev parent reply other threads:[~2007-04-11 15:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 8:22 [Buildroot] svn commit: trunk/buildroot: target/device target/device/x86/i386 too etc aldot at uclibc.org
2007-04-11 15:01 ` Ulf Samuelsson [this message]
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='01ce01c77c4b$27966e70$254565d5@atmel.com' \
--to=ulf@atmel.com \
--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