[Buildroot] [PATCH 09/55] Stop referencing the crazy target/device stuff

[Thomas De Schampheleire]

Hi,

On Sun, Dec 5, 2010 at 9:52 PM, Thomas Petazzoni
<thomas.petazzoni at free-electrons.com> wrote:
> We don't need Config.in and Makefile in target/device: defconfig files
> are sufficient to describe the specificities of a board (architecture,
> compilation flags, bootloader and kernel details, etc.).

How then would you add board-specific configuration options?
Suppose that for a certain board you can enable or disable a certain
feature. Previously, you'd add such an option in the board-specific
Config.in file, which was included via the manufacturer-specific
Config.in file, which was included from target/device/Config.in.
Now that all these are being removed, what's the strategy?

Related to this: previously some target/device/*/Config.in files added
configuration options called BR2_BOARD_NAME and BR2_BOARD_PATH. These
could be referenced from other configuration options, for example in
target/linux/Config.in.advanced, as the default Linux configuration
file. Is this mechanism still supported, or is there an alternative?

Thanks,
Thomas