瀏覽代碼

Stop referencing the crazy target/device stuff

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.).

However, a placeholder such as target/device will be kept in order to
host things such as kernel configuration files or various
board-specific patches.

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
Thomas Petazzoni 14 年之前
父節點
當前提交
1a5f2d6d7a
共有 2 個文件被更改,包括 0 次插入4 次删除
  1. 0 1
      Config.in
  2. 0 3
      target/Makefile.in

+ 0 - 1
Config.in

@@ -11,7 +11,6 @@ config BR2_VERSION
 	option env="BR2_VERSION_FULL"
 
 source "target/Config.in.arch"
-source "target/device/Config.in"
 
 menu "Build options"
 

+ 0 - 3
target/Makefile.in

@@ -1,6 +1,3 @@
 # make sure to put everything that is board-specific before the tarroot targets
 include target/generic/Makefile.in
 
-# this eventually adds the kernel target to TARGETS:
-include target/device/Makefile.in
-include target/xtensa/Makefile.in