[U-Boot] [PATCH v4 0/2] Refactoring of boards.cfg
Changes in v4: - Rebase on the current u-boot/master
Changes in v3: - Rebase on the current u-boot/master - Fix a typo in commit log
Changes in v2: - Do not delete Lite5200*
Masahiro Yamada (2): boards.cfg: Place "-" in the 8th field if it is the same as 7th boards.cfg: Delete the equivalent entries
boards.cfg | 85 +++++++++++++++++++++++++++++--------------------------------- 1 file changed, 40 insertions(+), 45 deletions(-)
The 8th field of boards.cfg takes the form: <board config name>[:comma separated config options]
We should describe explicitely the 8th field only when it is necessary to do so. Specify "-" in the 8th field if it is the same as 7th field.
Signed-off-by: Masahiro Yamada yamada.m@jp.panasonic.com Acked-by: Otavio Salvador otavio@ossystems.com.br ---
Changes in v4: - Rebase on the current u-boot/master
Changes in v3: - Rebase on the current u-boot/master
Changes in v2: None
boards.cfg | 80 +++++++++++++++++++++++++++++++------------------------------- 1 file changed, 40 insertions(+), 40 deletions(-)
diff --git a/boards.cfg b/boards.cfg index 07ae05b..ee2f53e 100644 --- a/boards.cfg +++ b/boards.cfg @@ -59,11 +59,11 @@ Active arm arm720t - armltd integrator Active arm arm920t - armltd integrator integratorap_cm920t integratorap:CM920T Linus Walleij linus.walleij@linaro.org Active arm arm920t - armltd integrator integratorcp_cm920t integratorcp:CM920T Linus Walleij linus.walleij@linaro.org Active arm arm920t a320 faraday - a320evb - Po-Yu Chuang ratbert@faraday-tech.com -Active arm arm920t at91 atmel at91rm9200ek at91rm9200ek at91rm9200ek Andreas Bießmann andreas.devel@gmail.com +Active arm arm920t at91 atmel at91rm9200ek at91rm9200ek - Andreas Bießmann andreas.devel@gmail.com Active arm arm920t at91 atmel at91rm9200ek at91rm9200ek_ram at91rm9200ek:RAMBOOT Andreas Bießmann andreas.devel@gmail.com -Active arm arm920t at91 BuS eb_cpux9k2 eb_cpux9k2 eb_cpux9k2 Jens Scharsig esw@bus-elektronik.de +Active arm arm920t at91 BuS eb_cpux9k2 eb_cpux9k2 - Jens Scharsig esw@bus-elektronik.de Active arm arm920t at91 BuS eb_cpux9k2 eb_cpux9k2_ram eb_cpux9k2:RAMBOOT Jens Scharsig esw@bus-elektronik.de -Active arm arm920t at91 eukrea cpuat91 cpuat91 cpuat91 Eric Benard eric@eukrea.com +Active arm arm920t at91 eukrea cpuat91 cpuat91 - Eric Benard eric@eukrea.com Active arm arm920t at91 eukrea cpuat91 cpuat91_ram cpuat91:RAMBOOT Eric Benard eric@eukrea.com Active arm arm920t imx - - scb9328 - Torsten Koschorrek koschorrek@synertronixx.de Active arm arm920t ks8695 - - cm4008 - Greg Ungerer greg.ungerer@opengear.com @@ -141,7 +141,7 @@ Active arm arm926ejs at91 taskit stamp9g20 Active arm arm926ejs at91 siemens taurus axm taurus:AT91SAM9G20,MACH_TYPE=2068,BOARD_AXM Heiko Schocher hs@denx.de Active arm arm926ejs at91 siemens corvus corvus corvus:AT91SAM9M10G45,SYS_USE_NANDFLASH Heiko Schocher hs@denx.de Active arm arm926ejs at91 siemens taurus taurus taurus:AT91SAM9G20,MACH_TYPE=2067,BOARD_TAURUS Heiko Schocher hs@denx.de -Active arm arm926ejs davinci ait cam_enc_4xx cam_enc_4xx cam_enc_4xx Heiko Schocher hs@denx.de +Active arm arm926ejs davinci ait cam_enc_4xx cam_enc_4xx - Heiko Schocher hs@denx.de Active arm arm926ejs davinci Barix ipam390 ipam390 - Heiko Schocher hs@denx.de Active arm arm926ejs davinci davinci da8xxevm da830evm - Nick Thompson nick.thompson@gefanuc.com Active arm arm926ejs davinci davinci da8xxevm da850_am18xxevm da850evm:DA850_AM18X_EVM,MAC_ADDR_IN_EEPROM,SYS_I2C_EEPROM_ADDR_LEN=2,SYS_I2C_EEPROM_ADDR=0x50 Sudhakar Rajashekhara sudhakar.raj@ti.com @@ -202,15 +202,15 @@ Active arm arm926ejs mx25 syteco zmx25 Active arm arm926ejs mx27 armadeus apf27 apf27 - Philippe Reynes tremyfr@yahoo.fr:Eric Jarrige eric.jarrige@armadeus.org Active arm arm926ejs mx27 logicpd imx27lite imx27lite - Wolfgang Denk wd@denx.de Active arm arm926ejs mx27 logicpd imx27lite magnesium - Heiko Schocher hs@denx.de -Active arm arm926ejs mxs bluegiga apx4devkit apx4devkit apx4devkit Lauri Hintsala lauri.hintsala@bluegiga.com +Active arm arm926ejs mxs bluegiga apx4devkit apx4devkit - Lauri Hintsala lauri.hintsala@bluegiga.com Active arm arm926ejs mxs creative xfi3 xfi3 - Marek Vasut marek.vasut@gmail.com -Active arm arm926ejs mxs denx m28evk m28evk m28evk Marek Vasut marek.vasut@gmail.com -Active arm arm926ejs mxs freescale mx23evk mx23evk mx23evk Otavio Salvador otavio@ossystems.com.br +Active arm arm926ejs mxs denx m28evk m28evk - Marek Vasut marek.vasut@gmail.com +Active arm arm926ejs mxs freescale mx23evk mx23evk - Otavio Salvador otavio@ossystems.com.br Active arm arm926ejs mxs freescale mx28evk mx28evk mx28evk:ENV_IS_IN_MMC Fabio Estevam fabio.estevam@freescale.com Active arm arm926ejs mxs freescale mx28evk mx28evk_auart_console mx28evk:MXS_AUART,MXS_AUART_BASE=MXS_UARTAPP3_BASE,ENV_IS_IN_MMC Fabio Estevam fabio.estevam@freescale.com Active arm arm926ejs mxs freescale mx28evk mx28evk_nand mx28evk:ENV_IS_IN_NAND Fabio Estevam fabio.estevam@freescale.com -Active arm arm926ejs mxs olimex mx23_olinuxino mx23_olinuxino mx23_olinuxino Marek Vasut marek.vasut@gmail.com -Active arm arm926ejs mxs ppcag bg0900 bg0900 bg0900 Marek Vasut marex@denx.de +Active arm arm926ejs mxs olimex mx23_olinuxino mx23_olinuxino - Marek Vasut marek.vasut@gmail.com +Active arm arm926ejs mxs ppcag bg0900 bg0900 - Marek Vasut marex@denx.de Active arm arm926ejs mxs sandisk sansa_fuze_plus sansa_fuze_plus - Marek Vasut marek.vasut@gmail.com Active arm arm926ejs mxs schulercontrol sc_sps_1 sc_sps_1 - Marek Vasut marek.vasut@gmail.com Active arm arm926ejs nomadik st nhk8815 nhk8815 - Nomadik Linux Team STN_WMM_nomadik_linux@list.st.com:Alessandro Rubini rubini@unipv.it @@ -218,7 +218,7 @@ Active arm arm926ejs nomadik st nhk8815 Active arm arm926ejs omap ti - omap5912osk - Rishi Bhattacharya rishi@ti.com Active arm arm926ejs orion5x LaCie - edminiv2 - Albert ARIBAUD albert.u.boot@aribaud.net Active arm arm926ejs pantheon Marvell - dkb - Lei Wen leiwen@marvell.com -Active arm arm926ejs spear spear - x600 x600 Stefan Roese sr@denx.de +Active arm arm926ejs spear spear - x600 - Stefan Roese sr@denx.de Active arm arm926ejs spear spear spear300 spear300 spear3xx_evb:spear300 Vipin Kumar vipin.kumar@st.com Active arm arm926ejs spear spear spear300 spear300_nand spear3xx_evb:spear300,nand - Active arm arm926ejs spear spear spear300 spear300_usbtty spear3xx_evb:spear300,usbtty - @@ -247,7 +247,7 @@ Active arm arm946es - armltd integrator Active arm armv7 - armltd vexpress vexpress_ca15_tc2 - - Active arm armv7 - armltd vexpress vexpress_ca5x2 - Matt Waddel matt.waddel@linaro.org Active arm armv7 - armltd vexpress vexpress_ca9x4 - Matt Waddel matt.waddel@linaro.org -Active arm armv7 am33xx compulab cm_t335 cm_t335 cm_t335 Igor Grinberg grinberg@compulab.co.il +Active arm armv7 am33xx compulab cm_t335 cm_t335 - Igor Grinberg grinberg@compulab.co.il Active arm armv7 am33xx isee igep0033 am335x_igep0033 - Enric Balletbo i Serra eballetbo@iseebcn.com Active arm armv7 am33xx phytec pcm051 pcm051_rev1 pcm051:REV1 Lars Poeschel poeschel@lemonage.de Active arm armv7 am33xx phytec pcm051 pcm051_rev3 pcm051:REV3 Lars Poeschel poeschel@lemonage.de @@ -576,7 +576,7 @@ Active powerpc mpc5xxx - - icecube Active powerpc mpc5xxx - - icecube lite5200b IceCube:MPC5200_DDR,LITE5200B - Active powerpc mpc5xxx - - icecube lite5200b_LOWBOOT IceCube:MPC5200_DDR,LITE5200B,SYS_TEXT_BASE=0xFF000000 - Active powerpc mpc5xxx - - icecube lite5200b_PM IceCube:MPC5200_DDR,LITE5200B,LITE5200B_PM - -Active powerpc mpc5xxx - - mcc200 mcc200 mcc200 - +Active powerpc mpc5xxx - - mcc200 mcc200 - - Active powerpc mpc5xxx - - mcc200 mcc200_COM12 mcc200:CONSOLE_COM12 - Active powerpc mpc5xxx - - mcc200 mcc200_COM12_highboot mcc200:CONSOLE_COM12,SYS_TEXT_BASE=0xFFF00000 - Active powerpc mpc5xxx - - mcc200 mcc200_COM12_highboot_SDRAM mcc200:CONSOLE_COM12,SYS_TEXT_BASE=0xFFF00000,MCC200_SDRAM - @@ -621,17 +621,17 @@ Active powerpc mpc5xxx - manroland - Active powerpc mpc5xxx - manroland - uc101 - Heiko Schocher hs@denx.de Active powerpc mpc5xxx - matrix_vision mvbc_p MVBC_P MVBC_P:MVBC_P Andre Schwarz andre.schwarz@matrix-vision.de Active powerpc mpc5xxx - matrix_vision mvsmr MVSMR - Andre Schwarz andre.schwarz@matrix-vision.de -Active powerpc mpc5xxx - phytec pcm030 pcm030 pcm030 Jon Smirl jonsmirl@gmail.com +Active powerpc mpc5xxx - phytec pcm030 pcm030 - Jon Smirl jonsmirl@gmail.com Active powerpc mpc5xxx - phytec pcm030 pcm030_LOWBOOT pcm030:SYS_TEXT_BASE=0xFF000000 Jon Smirl jonsmirl@gmail.com Active powerpc mpc5xxx - tqc tqm5200 aev - - Active powerpc mpc5xxx - tqc tqm5200 cam5200 TQM5200:CAM5200,TQM5200S,TQM5200_B - Active powerpc mpc5xxx - tqc tqm5200 cam5200_niosflash TQM5200:CAM5200,TQM5200S,TQM5200_B,CAM5200_NIOSFLASH - -Active powerpc mpc5xxx - tqc tqm5200 charon charon Heiko Schocher hs@denx.de +Active powerpc mpc5xxx - tqc tqm5200 charon - Heiko Schocher hs@denx.de Active powerpc mpc5xxx - tqc tqm5200 fo300 TQM5200:FO300 - Active powerpc mpc5xxx - tqc tqm5200 MiniFAP TQM5200:MINIFAP - Active powerpc mpc5xxx - tqc tqm5200 TB5200 - - Active powerpc mpc5xxx - tqc tqm5200 TB5200_B TB5200:TQM5200_B - -Active powerpc mpc5xxx - tqc tqm5200 TQM5200 TQM5200: - +Active powerpc mpc5xxx - tqc tqm5200 TQM5200 - - Active powerpc mpc5xxx - tqc tqm5200 TQM5200_B TQM5200:TQM5200_B - Active powerpc mpc5xxx - tqc tqm5200 TQM5200_B_HIGHBOOT TQM5200:TQM5200_B,SYS_TEXT_BASE=0xFFF00000 - Active powerpc mpc5xxx - tqc tqm5200 TQM5200_STK100 TQM5200:STK52XX_REV100 - @@ -639,7 +639,7 @@ Active powerpc mpc5xxx - tqc tqm5200 Active powerpc mpc5xxx - tqc tqm5200 TQM5200S_HIGHBOOT TQM5200:TQM5200_B,TQM5200S,SYS_TEXT_BASE=0xFFF00000 - Active powerpc mpc824x - - - utx8245 - Greg Allen gallen@arlut.utexas.edu Active powerpc mpc824x - - a3000 A3000 - - -Active powerpc mpc824x - - cpc45 CPC45 CPC45 Josef Wagner Wagner@Microsys.de +Active powerpc mpc824x - - cpc45 CPC45 - Josef Wagner Wagner@Microsys.de Active powerpc mpc824x - - cpc45 CPC45_ROMBOOT CPC45:BOOT_ROM Josef Wagner Wagner@Microsys.de Active powerpc mpc824x - - cu824 CU824 - Wolfgang Denk wd@denx.de Active powerpc mpc824x - - eXalion eXalion - Torsten Demke torsten.demke@fci.com @@ -658,9 +658,9 @@ Active powerpc mpc8260 - - - Active powerpc mpc8260 - - - ppmc8260 - Brad Kemp Brad.Kemp@seranoa.com Active powerpc mpc8260 - - - sacsng - Jerry Van Baren gerald.vanbaren@smiths-aerospace.com Active powerpc mpc8260 - - cogent cogent_mpc8260 - Murray Jensen Murray.Jensen@csiro.au -Active powerpc mpc8260 - - cpu86 CPU86 CPU86 Wolfgang Denk wd@denx.de +Active powerpc mpc8260 - - cpu86 CPU86 - Wolfgang Denk wd@denx.de Active powerpc mpc8260 - - cpu86 CPU86_ROMBOOT CPU86:BOOT_ROM Wolfgang Denk wd@denx.de -Active powerpc mpc8260 - - cpu87 CPU87 CPU87 - +Active powerpc mpc8260 - - cpu87 CPU87 - - Active powerpc mpc8260 - - cpu87 CPU87_ROMBOOT CPU87:BOOT_ROM - Active powerpc mpc8260 - - ep8248 ep8248 - Yuli Barcohen yuli@arabellasw.com Active powerpc mpc8260 - - ep8248 ep8248E ep8248 Yuli Barcohen yuli@arabellasw.com @@ -678,11 +678,11 @@ Active powerpc mpc8260 - - pm826 Active powerpc mpc8260 - - pm826 PM826_BIGFLASH PM826:FLASH_32MB,SYS_TEXT_BASE=0x40000000 Wolfgang Denk wd@denx.de Active powerpc mpc8260 - - pm826 PM826_ROMBOOT PM826:BOOT_ROM,SYS_TEXT_BASE=0xFF800000 Wolfgang Denk wd@denx.de Active powerpc mpc8260 - - pm826 PM826_ROMBOOT_BIGFLASH PM826:BOOT_ROM,FLASH_32MB,SYS_TEXT_BASE=0xFF800000 Wolfgang Denk wd@denx.de -Active powerpc mpc8260 - - pm828 PM828 PM828 - +Active powerpc mpc8260 - - pm828 PM828 - - Active powerpc mpc8260 - - pm828 PM828_PCI PM828:PCI - Active powerpc mpc8260 - - pm828 PM828_ROMBOOT PM828:BOOT_ROM,SYS_TEXT_BASE=0xFF800000 - Active powerpc mpc8260 - - pm828 PM828_ROMBOOT_PCI PM828:PCI,BOOT_ROM,SYS_TEXT_BASE=0xFF800000 - -Active powerpc mpc8260 - - rattler Rattler Rattler Yuli Barcohen yuli@arabellasw.com +Active powerpc mpc8260 - - rattler Rattler - Yuli Barcohen yuli@arabellasw.com Active powerpc mpc8260 - - rattler Rattler8248 Rattler:MPC8248 Yuli Barcohen yuli@arabellasw.com Active powerpc mpc8260 - - zpc1900 ZPC1900 - Yuli Barcohen yuli@arabellasw.com Active powerpc mpc8260 - freescale mpc8260ads MPC8260ADS MPC8260ADS:ADSTYPE=CONFIG_SYS_8260ADS Yuli Barcohen yuli@arabellasw.com @@ -718,21 +718,21 @@ Active powerpc mpc8260 - tqc tqm8260 Active powerpc mpc8260 - tqc tqm8260 TQM8265_AA TQM8260:MPC8265,300MHz,BUSMODE_60x Wolfgang Denk wd@denx.de Active powerpc mpc8260 - tqc tqm8272 TQM8272 - - Active powerpc mpc83xx - - - mpc8308_p1m - Ilya Yanok yanok@emcraft.com -Active powerpc mpc83xx - - sbc8349 sbc8349 sbc8349 Paul Gortmaker paul.gortmaker@windriver.com +Active powerpc mpc83xx - - sbc8349 sbc8349 - Paul Gortmaker paul.gortmaker@windriver.com Active powerpc mpc83xx - - sbc8349 sbc8349_PCI_33 sbc8349:PCI,PCI_33M Paul Gortmaker paul.gortmaker@windriver.com Active powerpc mpc83xx - - sbc8349 sbc8349_PCI_66 sbc8349:PCI,PCI_66M Paul Gortmaker paul.gortmaker@windriver.com Active powerpc mpc83xx - - ve8313 ve8313 - Heiko Schocher hs@denx.de Active powerpc mpc83xx - esd vme8349 caddy2 vme8349:CADDY2 Reinhard Arlt reinhard.arlt@esd-electronics.com -Active powerpc mpc83xx - esd vme8349 vme8349 vme8349 Reinhard Arlt reinhard.arlt@esd-electronics.com +Active powerpc mpc83xx - esd vme8349 vme8349 - Reinhard Arlt reinhard.arlt@esd-electronics.com Active powerpc mpc83xx - freescale mpc8308rdb MPC8308RDB - Ilya Yanok yanok@emcraft.com Active powerpc mpc83xx - freescale mpc8313erdb MPC8313ERDB_33 MPC8313ERDB:SYS_33MHZ - Active powerpc mpc83xx - freescale mpc8313erdb MPC8313ERDB_66 MPC8313ERDB:SYS_66MHZ - Active powerpc mpc83xx - freescale mpc8313erdb MPC8313ERDB_NAND_33 MPC8313ERDB:SYS_33MHZ,NAND - Active powerpc mpc83xx - freescale mpc8313erdb MPC8313ERDB_NAND_66 MPC8313ERDB:SYS_66MHZ,NAND - -Active powerpc mpc83xx - freescale mpc8315erdb MPC8315ERDB MPC8315ERDB Dave Liu daveliu@freescale.com +Active powerpc mpc83xx - freescale mpc8315erdb MPC8315ERDB - Dave Liu daveliu@freescale.com Active powerpc mpc83xx - freescale mpc8315erdb MPC8315ERDB_NAND MPC8315ERDB:NAND_U_BOOT Dave Liu daveliu@freescale.com Active powerpc mpc83xx - freescale mpc8323erdb MPC8323ERDB - Michael Barkowski michael.barkowski@freescale.com -Active powerpc mpc83xx - freescale mpc832xemds MPC832XEMDS MPC832XEMDS: Dave Liu daveliu@freescale.com +Active powerpc mpc83xx - freescale mpc832xemds MPC832XEMDS - Dave Liu daveliu@freescale.com Active powerpc mpc83xx - freescale mpc832xemds MPC832XEMDS_ATM MPC832XEMDS:PQ_MDS_PIB=1,PQ_MDS_PIB_ATM=1 Dave Liu daveliu@freescale.com Active powerpc mpc83xx - freescale mpc832xemds MPC832XEMDS_HOST_33 MPC832XEMDS:PCI,PCI_33M,PQ_MDS_PIB=1 Dave Liu daveliu@freescale.com Active powerpc mpc83xx - freescale mpc832xemds MPC832XEMDS_HOST_66 MPC832XEMDS:PCI,PCI_66M,PQ_MDS_PIB=1 Dave Liu daveliu@freescale.com @@ -751,10 +751,10 @@ Active powerpc mpc83xx - freescale mpc8360emds Active powerpc mpc83xx - freescale mpc8360emds MPC8360EMDS_66_HOST_33 MPC8360EMDS:CLKIN_66MHZ,PCI,PCI_33M,PQ_MDS_PIB=1 Dave Liu daveliu@freescale.com Active powerpc mpc83xx - freescale mpc8360emds MPC8360EMDS_66_HOST_66 MPC8360EMDS:CLKIN_66MHZ,PCI,PCI_66M,PQ_MDS_PIB=1 Dave Liu daveliu@freescale.com Active powerpc mpc83xx - freescale mpc8360emds MPC8360EMDS_66_SLAVE MPC8360EMDS:CLKIN_66MHZ,PCI,PCISLAVE Dave Liu daveliu@freescale.com -Active powerpc mpc83xx - freescale mpc8360erdk MPC8360ERDK MPC8360ERDK Anton Vorontsov avorontsov@ru.mvista.com +Active powerpc mpc83xx - freescale mpc8360erdk MPC8360ERDK - Anton Vorontsov avorontsov@ru.mvista.com Active powerpc mpc83xx - freescale mpc8360erdk MPC8360ERDK_33 MPC8360ERDK:CLKIN_33MHZ Anton Vorontsov avorontsov@ru.mvista.com Active powerpc mpc83xx - freescale mpc8360erdk MPC8360ERDK_66 MPC8360ERDK Anton Vorontsov avorontsov@ru.mvista.com -Active powerpc mpc83xx - freescale mpc837xemds MPC837XEMDS MPC837XEMDS Dave Liu daveliu@freescale.com +Active powerpc mpc83xx - freescale mpc837xemds MPC837XEMDS - Dave Liu daveliu@freescale.com Active powerpc mpc83xx - freescale mpc837xemds MPC837XEMDS_HOST MPC837XEMDS:PCI Dave Liu daveliu@freescale.com Active powerpc mpc83xx - freescale mpc837xerdb MPC837XERDB - Joe D'Abbraccio ljd015@freescale.com Active powerpc mpc83xx - keymile km83xx kmcoge5ne km8360:KMCOGE5NE Holger Brunck holger.brunck@keymile.com @@ -770,7 +770,7 @@ Active powerpc mpc83xx - matrix_vision mvblm7 Active powerpc mpc83xx - sheldon simpc8313 SIMPC8313_LP SIMPC8313:NAND_LP Ron Madrid info@sheldoninst.com Active powerpc mpc83xx - sheldon simpc8313 SIMPC8313_SP SIMPC8313:NAND_SP Ron Madrid info@sheldoninst.com Active powerpc mpc83xx - tqc tqm834x TQM834x - - -Active powerpc mpc85xx - - sbc8548 sbc8548 sbc8548 Paul Gortmaker paul.gortmaker@windriver.com +Active powerpc mpc85xx - - sbc8548 sbc8548 - Paul Gortmaker paul.gortmaker@windriver.com Active powerpc mpc85xx - - sbc8548 sbc8548_PCI_33 sbc8548:PCI,33 Paul Gortmaker paul.gortmaker@windriver.com Active powerpc mpc85xx - - sbc8548 sbc8548_PCI_33_PCIE sbc8548:PCI,33,PCIE Paul Gortmaker paul.gortmaker@windriver.com Active powerpc mpc85xx - - sbc8548 sbc8548_PCI_66 sbc8548:PCI,66 Paul Gortmaker paul.gortmaker@windriver.com @@ -820,26 +820,26 @@ Active powerpc mpc85xx - freescale corenet_ds Active powerpc mpc85xx - freescale corenet_ds P5040DS_NAND P5040DS:RAMBOOT_PBL,NAND,SYS_TEXT_BASE=0xFFF40000 - Active powerpc mpc85xx - freescale corenet_ds P5040DS_SDCARD P5040DS:RAMBOOT_PBL,SDCARD,SYS_TEXT_BASE=0xFFF40000 - Active powerpc mpc85xx - freescale corenet_ds P5040DS_SPIFLASH P5040DS:RAMBOOT_PBL,SPIFLASH,SYS_TEXT_BASE=0xFFF40000 - -Active powerpc mpc85xx - freescale mpc8536ds MPC8536DS MPC8536DS - +Active powerpc mpc85xx - freescale mpc8536ds MPC8536DS - - Active powerpc mpc85xx - freescale mpc8536ds MPC8536DS_36BIT MPC8536DS:36BIT - Active powerpc mpc85xx - freescale mpc8536ds MPC8536DS_NAND MPC8536DS:NAND - Active powerpc mpc85xx - freescale mpc8536ds MPC8536DS_SDCARD MPC8536DS:SDCARD - Active powerpc mpc85xx - freescale mpc8536ds MPC8536DS_SPIFLASH MPC8536DS:SPIFLASH - Active powerpc mpc85xx - freescale mpc8540ads MPC8540ADS - Kumar Gala kumar.gala@freescale.com -Active powerpc mpc85xx - freescale mpc8541cds MPC8541CDS MPC8541CDS Kumar Gala kumar.gala@freescale.com +Active powerpc mpc85xx - freescale mpc8541cds MPC8541CDS - Kumar Gala kumar.gala@freescale.com Active powerpc mpc85xx - freescale mpc8541cds MPC8541CDS_legacy MPC8541CDS:LEGACY Kumar Gala kumar.gala@freescale.com Active powerpc mpc85xx - freescale mpc8544ds MPC8544DS - - -Active powerpc mpc85xx - freescale mpc8548cds MPC8548CDS MPC8548CDS - +Active powerpc mpc85xx - freescale mpc8548cds MPC8548CDS - - Active powerpc mpc85xx - freescale mpc8548cds MPC8548CDS_36BIT MPC8548CDS:36BIT - Active powerpc mpc85xx - freescale mpc8548cds MPC8548CDS_legacy MPC8548CDS:LEGACY - -Active powerpc mpc85xx - freescale mpc8555cds MPC8555CDS MPC8555CDS Kumar Gala kumar.gala@freescale.com +Active powerpc mpc85xx - freescale mpc8555cds MPC8555CDS - Kumar Gala kumar.gala@freescale.com Active powerpc mpc85xx - freescale mpc8555cds MPC8555CDS_legacy MPC8555CDS:LEGACY Kumar Gala kumar.gala@freescale.com Active powerpc mpc85xx - freescale mpc8560ads MPC8560ADS - Kumar Gala kumar.gala@freescale.com Active powerpc mpc85xx - freescale mpc8568mds MPC8568MDS - - -Active powerpc mpc85xx - freescale mpc8569mds MPC8569MDS MPC8569MDS - +Active powerpc mpc85xx - freescale mpc8569mds MPC8569MDS - - Active powerpc mpc85xx - freescale mpc8569mds MPC8569MDS_ATM MPC8569MDS:ATM - Active powerpc mpc85xx - freescale mpc8569mds MPC8569MDS_NAND MPC8569MDS:NAND - -Active powerpc mpc85xx - freescale mpc8572ds MPC8572DS MPC8572DS - +Active powerpc mpc85xx - freescale mpc8572ds MPC8572DS - - Active powerpc mpc85xx - freescale mpc8572ds MPC8572DS_36BIT MPC8572DS:36BIT - Active powerpc mpc85xx - freescale mpc8572ds MPC8572DS_NAND MPC8572DS:NAND - Active powerpc mpc85xx - freescale p1010rdb P1010RDB-PA_36BIT_NAND P1010RDB:P1010RDB_PA,36BIT,NAND - @@ -878,8 +878,8 @@ Active powerpc mpc85xx - freescale p1022ds Active powerpc mpc85xx - freescale p1022ds P1022DS_NAND P1022DS:NAND Timur Tabi timur@freescale.com Active powerpc mpc85xx - freescale p1022ds P1022DS_SDCARD P1022DS:SDCARD Timur Tabi timur@freescale.com Active powerpc mpc85xx - freescale p1022ds P1022DS_SPIFLASH P1022DS:SPIFLASH Timur Tabi timur@freescale.com -Active powerpc mpc85xx - freescale p1023rdb P1023RDB P1023RDB - -Active powerpc mpc85xx - freescale p1023rds P1023RDS P1023RDS Roy Zang tie-fei.zang@freescale.com +Active powerpc mpc85xx - freescale p1023rdb P1023RDB - - +Active powerpc mpc85xx - freescale p1023rds P1023RDS - Roy Zang tie-fei.zang@freescale.com Active powerpc mpc85xx - freescale p1023rds P1023RDS_NAND P1023RDS:NAND Roy Zang tie-fei.zang@freescale.com Active powerpc mpc85xx - freescale p1_p2_rdb P1011RDB P1_P2_RDB:P1011RDB - Active powerpc mpc85xx - freescale p1_p2_rdb P1011RDB_36BIT P1_P2_RDB:P1011RDB,36BIT - @@ -992,14 +992,14 @@ Active powerpc mpc85xx - gdsys p1022 Active powerpc mpc85xx - gdsys p1022 controlcenterd_TRAILBLAZER_DEVELOP controlcenterd:TRAILBLAZER,SPIFLASH,DEVELOP Dirk Eibach eibach@gdsys.de Active powerpc mpc85xx - keymile kmp204x kmlion1 kmp204x:KMLION1 Valentin Longchamp valentin.longchamp@keymile.com Active powerpc mpc85xx - stx stxgp3 stxgp3 - Dan Malek dan@embeddedalley.com -Active powerpc mpc85xx - stx stxssa stxssa stxssa Dan Malek dan@embeddedalley.com +Active powerpc mpc85xx - stx stxssa stxssa - Dan Malek dan@embeddedalley.com Active powerpc mpc85xx - stx stxssa stxssa_4M stxssa:STXSSA_4M Dan Malek dan@embeddedalley.com Active powerpc mpc85xx - xes - xpedite520x - - Active powerpc mpc85xx - xes - xpedite537x - - Active powerpc mpc85xx - xes - xpedite550x - - Active powerpc mpc86xx - - - sbc8641d - Paul Gortmaker paul.gortmaker@windriver.com Active powerpc mpc86xx - freescale mpc8610hpcd MPC8610HPCD - - -Active powerpc mpc86xx - freescale mpc8641hpcn MPC8641HPCN MPC8641HPCN Kumar Gala kumar.gala@freescale.com +Active powerpc mpc86xx - freescale mpc8641hpcn MPC8641HPCN - Kumar Gala kumar.gala@freescale.com Active powerpc mpc86xx - freescale mpc8641hpcn MPC8641HPCN_36BIT MPC8641HPCN:PHYS_64BIT Kumar Gala kumar.gala@freescale.com Active powerpc mpc86xx - xes - xpedite517x - - Active powerpc mpc8xx - - - hermes - Wolfgang Denk wd@denx.de @@ -1031,7 +1031,7 @@ Active powerpc mpc8xx - - ivm Active powerpc mpc8xx - - ivm IVMS8_256 IVMS8:IVMS8_64M Wolfgang Denk wd@denx.de Active powerpc mpc8xx - - netphone NETPHONE NETPHONE:NETPHONE_VERSION=1 - Active powerpc mpc8xx - - netphone NETPHONE_V2 NETPHONE:NETPHONE_VERSION=2 - -Active powerpc mpc8xx - - netta NETTA NETTA - +Active powerpc mpc8xx - - netta NETTA - - Active powerpc mpc8xx - - netta NETTA_6412 NETTA:NETTA_6412=1 - Active powerpc mpc8xx - - netta NETTA_6412_SWAPHOOK NETTA:NETTA_6412=1,NETTA_SWAPHOOK=1 - Active powerpc mpc8xx - - netta NETTA_ISDN NETTA:NETTA_ISDN=1 - @@ -1045,7 +1045,7 @@ Active powerpc mpc8xx - - netvia Active powerpc mpc8xx - - netvia NETVIA_V2 NETVIA:NETVIA_VERSION=2 Pantelis Antoniou panto@intracom.gr Active powerpc mpc8xx - - r360mpi R360MPI - Wolfgang Denk wd@denx.de Active powerpc mpc8xx - - rbc823 RBC823 - - -Active powerpc mpc8xx - - RPXlite_dw RPXlite_DW RPXlite_DW - +Active powerpc mpc8xx - - RPXlite_dw RPXlite_DW - - Active powerpc mpc8xx - - RPXlite_dw RPXlite_DW_64 RPXlite_DW:RPXlite_64MHz - Active powerpc mpc8xx - - RPXlite_dw RPXlite_DW_64_LCD RPXlite_DW:RPXlite_64MHz,LCD,NEC_NL6448BC20 - Active powerpc mpc8xx - - RPXlite_dw RPXlite_DW_LCD RPXlite_DW:LCD,NEC_NL6448BC20 - @@ -1232,7 +1232,7 @@ Active x86 x86 coreboot chromebook-x86 coreboot Orphan arm arm1136 mx31 - imx31_phycore imx31_phycore_eet imx31_phycore:IMX31_PHYCORE_EET (resigned) Guennadi Liakhovetski g.liakhovetski@gmx.de Orphan arm arm1136 mx31 freescale - mx31ads - (resigned) Guennadi Liakhovetski g.liakhovetski@gmx.de Orphan arm pxa - - - lubbock - (dead address) Kyle Harris kharris@nexus-tech.net -Orphan powerpc 74xx_7xx - - evb64260 EVB64260 EVB64260 - +Orphan powerpc 74xx_7xx - - evb64260 EVB64260 - - Orphan powerpc 74xx_7xx - - evb64260 EVB64260_750CX EVB64260 Eran Man eran@nbase.co.il Orphan powerpc mpc824x - - mousse MOUSSE - - Orphan powerpc mpc8260 - - - rsdproto - -
On Thu, Jan 23, 2014 at 08:09:28PM +0900, Masahiro Yamada wrote:
The 8th field of boards.cfg takes the form: <board config name>[:comma separated config options]
We should describe explicitely the 8th field only when it is necessary to do so. Specify "-" in the 8th field if it is the same as 7th field.
Signed-off-by: Masahiro Yamada yamada.m@jp.panasonic.com Acked-by: Otavio Salvador otavio@ossystems.com.br
Applied to u-boot/master, thanks!
There are some entries which produce the same binaries: - ep8248E is equivalent to ep8248 - MPC8360ERDK_66 is equivalent to MPC8360ERDK - Adder87x/AdderUSB is equivalent to Adder - EVB64260_750CX is equivalent to EVB64260
I also notice - Lite5200 is equivalent to icecube_5200 - Lite5200_LOWBOOT is equivalent to icecube_5200_LOWBOOT - Lite5200_LOWBOOT08 is equivalent to icecube_5200_LOWBOOT08 But I am keeping them. (Wolfgang suggested to do so because Lite5200* are referenced in misc documents.)
Signed-off-by: Masahiro Yamada yamada.m@jp.panasonic.com ---
Changes in v4: None Changes in v3: - Fix a typo in commit log
Changes in v2: - Do not delete Lite5200*
boards.cfg | 5 ----- 1 file changed, 5 deletions(-)
diff --git a/boards.cfg b/boards.cfg index ee2f53e..0bbb0ec 100644 --- a/boards.cfg +++ b/boards.cfg @@ -663,7 +663,6 @@ Active powerpc mpc8260 - - cpu86 Active powerpc mpc8260 - - cpu87 CPU87 - - Active powerpc mpc8260 - - cpu87 CPU87_ROMBOOT CPU87:BOOT_ROM - Active powerpc mpc8260 - - ep8248 ep8248 - Yuli Barcohen yuli@arabellasw.com -Active powerpc mpc8260 - - ep8248 ep8248E ep8248 Yuli Barcohen yuli@arabellasw.com Active powerpc mpc8260 - - ids8247 IDS8247 - Heiko Schocher hs@denx.de Active powerpc mpc8260 - - iphase4539 IPHASE4539 - Wolfgang Grandegger wg@denx.de Active powerpc mpc8260 - - ispan ISPAN - Yuli Barcohen yuli@arabellasw.com @@ -753,7 +752,6 @@ Active powerpc mpc83xx - freescale mpc8360emds Active powerpc mpc83xx - freescale mpc8360emds MPC8360EMDS_66_SLAVE MPC8360EMDS:CLKIN_66MHZ,PCI,PCISLAVE Dave Liu daveliu@freescale.com Active powerpc mpc83xx - freescale mpc8360erdk MPC8360ERDK - Anton Vorontsov avorontsov@ru.mvista.com Active powerpc mpc83xx - freescale mpc8360erdk MPC8360ERDK_33 MPC8360ERDK:CLKIN_33MHZ Anton Vorontsov avorontsov@ru.mvista.com -Active powerpc mpc83xx - freescale mpc8360erdk MPC8360ERDK_66 MPC8360ERDK Anton Vorontsov avorontsov@ru.mvista.com Active powerpc mpc83xx - freescale mpc837xemds MPC837XEMDS - Dave Liu daveliu@freescale.com Active powerpc mpc83xx - freescale mpc837xemds MPC837XEMDS_HOST MPC837XEMDS:PCI Dave Liu daveliu@freescale.com Active powerpc mpc83xx - freescale mpc837xerdb MPC837XERDB - Joe D'Abbraccio ljd015@freescale.com @@ -1010,9 +1008,7 @@ Active powerpc mpc8xx - - - Active powerpc mpc8xx - - - svm_sc8xx - John Zhan zhanz@sinovee.com Active powerpc mpc8xx - - - v37 - - Active powerpc mpc8xx - - adder Adder - Yuli Barcohen yuli@arabellasw.com -Active powerpc mpc8xx - - adder Adder87x Adder Yuli Barcohen yuli@arabellasw.com Active powerpc mpc8xx - - adder AdderII Adder:MPC852T Yuli Barcohen yuli@arabellasw.com -Active powerpc mpc8xx - - adder AdderUSB Adder Yuli Barcohen yuli@arabellasw.com Active powerpc mpc8xx - - cogent cogent_mpc8xx - Murray Jensen Murray.Jensen@csiro.au Active powerpc mpc8xx - - esteem192e ESTEEM192E - Conn Clark clark@esteem.com Active powerpc mpc8xx - - fads MPC86xADS - - @@ -1233,7 +1229,6 @@ Orphan arm arm1136 mx31 - imx31_phycore Orphan arm arm1136 mx31 freescale - mx31ads - (resigned) Guennadi Liakhovetski g.liakhovetski@gmx.de Orphan arm pxa - - - lubbock - (dead address) Kyle Harris kharris@nexus-tech.net Orphan powerpc 74xx_7xx - - evb64260 EVB64260 - - -Orphan powerpc 74xx_7xx - - evb64260 EVB64260_750CX EVB64260 Eran Man eran@nbase.co.il Orphan powerpc mpc824x - - mousse MOUSSE - - Orphan powerpc mpc8260 - - - rsdproto - - Orphan powerpc mpc8260 - - rpxsuper RPXsuper - -
Hi Masahiro,
On Thu, 23 Jan 2014 20:09:29 +0900, Masahiro Yamada yamada.m@jp.panasonic.com wrote:
There are some entries which produce the same binaries:
- ep8248E is equivalent to ep8248
- MPC8360ERDK_66 is equivalent to MPC8360ERDK
- Adder87x/AdderUSB is equivalent to Adder
- EVB64260_750CX is equivalent to EVB64260
I also notice
- Lite5200 is equivalent to icecube_5200
- Lite5200_LOWBOOT is equivalent to icecube_5200_LOWBOOT
- Lite5200_LOWBOOT08 is equivalent to icecube_5200_LOWBOOT08
But I am keeping them. (Wolfgang suggested to do so because Lite5200* are referenced in misc documents.)
Signed-off-by: Masahiro Yamada yamada.m@jp.panasonic.com
I wonder (i.e., this is an open question) whether we should delete entries for different hardware just because they happen produce identical binaries.
Amicalement,
Hello Albert,
There are some entries which produce the same binaries:
- ep8248E is equivalent to ep8248
- MPC8360ERDK_66 is equivalent to MPC8360ERDK
- Adder87x/AdderUSB is equivalent to Adder
- EVB64260_750CX is equivalent to EVB64260
I also notice
- Lite5200 is equivalent to icecube_5200
- Lite5200_LOWBOOT is equivalent to icecube_5200_LOWBOOT
- Lite5200_LOWBOOT08 is equivalent to icecube_5200_LOWBOOT08
But I am keeping them. (Wolfgang suggested to do so because Lite5200* are referenced in misc documents.)
Signed-off-by: Masahiro Yamada yamada.m@jp.panasonic.com
I wonder (i.e., this is an open question) whether we should delete entries for different hardware just because they happen produce identical binaries.
In my option, we should not create multiple entries pointing to the same config header.
We are already using single entry for different boards. (In such a case, a wildcard character "x" is often used but it is not must.) For example, the entry "zynq_zc70x" is used for both "Zynq ZC702" and "Zynq ZC706" board. They are definitely different boards but the difference is quite small. So we can use the same configuration for the two.
In the case of this patch, (I am not familiar with "ep8248" board, but I guess) ep8248 and ep8248E are different, but probably similar board.
So we can use the common entry "ep8248" for them. And "ep8248" means "ep8248 boards family", not "exactly ep8248 board".
Best Regards Masahiro Yamada
Hi Masahiro,
On Thu, 13 Feb 2014 14:32:12 +0900, Masahiro Yamada yamada.m@jp.panasonic.com wrote:
Hello Albert,
There are some entries which produce the same binaries:
- ep8248E is equivalent to ep8248
- MPC8360ERDK_66 is equivalent to MPC8360ERDK
- Adder87x/AdderUSB is equivalent to Adder
- EVB64260_750CX is equivalent to EVB64260
I also notice
- Lite5200 is equivalent to icecube_5200
- Lite5200_LOWBOOT is equivalent to icecube_5200_LOWBOOT
- Lite5200_LOWBOOT08 is equivalent to icecube_5200_LOWBOOT08
But I am keeping them. (Wolfgang suggested to do so because Lite5200* are referenced in misc documents.)
Signed-off-by: Masahiro Yamada yamada.m@jp.panasonic.com
I wonder (i.e., this is an open question) whether we should delete entries for different hardware just because they happen produce identical binaries.
In my option, we should not create multiple entries pointing to the same config header.
We are already using single entry for different boards. (In such a case, a wildcard character "x" is often used but it is not must.) For example, the entry "zynq_zc70x" is used for both "Zynq ZC702" and "Zynq ZC706" board. They are definitely different boards but the difference is quite small. So we can use the same configuration for the two.
In the case of this patch, (I am not familiar with "ep8248" board, but I guess) ep8248 and ep8248E are different, but probably similar board.
So we can use the common entry "ep8248" for them. And "ep8248" means "ep8248 boards family", not "exactly ep8248 board".
I agreed then boards.cfg ntries which point to the same config header *and* have the same config options in boards.cfg could be merged.
However, as you point out, and I agree, that some boards are *probably* similar enough to be merged, this "probably" shows that we do not know for sure the intent of the board maintainer.
Besides, we do not know which build procedure or script is out there which expects one board name or the other; merging entries would disrupt those procedures, so I want to be sure we are doing the right thing there.
Therefore, I would defer the decision of merging similar entries to the board maintainer(s), who is/are supposed to know best about this; at least, I would suggest to CC: them so that they can either Ack or Nak as they see fit.
Best Regards Masahiro Yamada
Amicalement,
Hello Albert,
There are some entries which produce the same binaries:
- ep8248E is equivalent to ep8248
- MPC8360ERDK_66 is equivalent to MPC8360ERDK
- Adder87x/AdderUSB is equivalent to Adder
- EVB64260_750CX is equivalent to EVB64260
I also notice
- Lite5200 is equivalent to icecube_5200
- Lite5200_LOWBOOT is equivalent to icecube_5200_LOWBOOT
- Lite5200_LOWBOOT08 is equivalent to icecube_5200_LOWBOOT08
But I am keeping them. (Wolfgang suggested to do so because Lite5200* are referenced in misc documents.)
Signed-off-by: Masahiro Yamada yamada.m@jp.panasonic.com
I wonder (i.e., this is an open question) whether we should delete entries for different hardware just because they happen produce identical binaries.
In my option, we should not create multiple entries pointing to the same config header.
We are already using single entry for different boards. (In such a case, a wildcard character "x" is often used but it is not must.) For example, the entry "zynq_zc70x" is used for both "Zynq ZC702" and "Zynq ZC706" board. They are definitely different boards but the difference is quite small. So we can use the same configuration for the two.
In the case of this patch, (I am not familiar with "ep8248" board, but I guess) ep8248 and ep8248E are different, but probably similar board.
So we can use the common entry "ep8248" for them. And "ep8248" means "ep8248 boards family", not "exactly ep8248 board".
I agreed then boards.cfg ntries which point to the same config header *and* have the same config options in boards.cfg could be merged.
However, as you point out, and I agree, that some boards are *probably* similar enough to be merged, this "probably" shows that we do not know for sure the intent of the board maintainer.
Besides, we do not know which build procedure or script is out there which expects one board name or the other; merging entries would disrupt those procedures, so I want to be sure we are doing the right thing there.
Therefore, I would defer the decision of merging similar entries to the board maintainer(s), who is/are supposed to know best about this; at least, I would suggest to CC: them so that they can either Ack or Nak as they see fit.
I had already done this.
Please read this thread: http://patchwork.ozlabs.org/patch/307941/
All boards I am touching in this patch are surely unmaintained. (So we cannot ask the reason why they added multiple entries.)
I tried to contact to their maintainers but all mails have been bouncing.
So I dropped Cc: tag when I posted v4. Otherwise, I would get delivery failure notification mails from STMP again and again.
Best Regards Masahiro Yamada
Hi Masahiro,
On Thu, 13 Feb 2014 15:46:41 +0900, Masahiro Yamada yamada.m@jp.panasonic.com wrote:
Hello Albert,
There are some entries which produce the same binaries:
- ep8248E is equivalent to ep8248
- MPC8360ERDK_66 is equivalent to MPC8360ERDK
- Adder87x/AdderUSB is equivalent to Adder
- EVB64260_750CX is equivalent to EVB64260
I also notice
- Lite5200 is equivalent to icecube_5200
- Lite5200_LOWBOOT is equivalent to icecube_5200_LOWBOOT
- Lite5200_LOWBOOT08 is equivalent to icecube_5200_LOWBOOT08
But I am keeping them. (Wolfgang suggested to do so because Lite5200* are referenced in misc documents.)
Signed-off-by: Masahiro Yamada yamada.m@jp.panasonic.com
I wonder (i.e., this is an open question) whether we should delete entries for different hardware just because they happen produce identical binaries.
In my option, we should not create multiple entries pointing to the same config header.
We are already using single entry for different boards. (In such a case, a wildcard character "x" is often used but it is not must.) For example, the entry "zynq_zc70x" is used for both "Zynq ZC702" and "Zynq ZC706" board. They are definitely different boards but the difference is quite small. So we can use the same configuration for the two.
In the case of this patch, (I am not familiar with "ep8248" board, but I guess) ep8248 and ep8248E are different, but probably similar board.
So we can use the common entry "ep8248" for them. And "ep8248" means "ep8248 boards family", not "exactly ep8248 board".
I agreed then boards.cfg ntries which point to the same config header *and* have the same config options in boards.cfg could be merged.
However, as you point out, and I agree, that some boards are *probably* similar enough to be merged, this "probably" shows that we do not know for sure the intent of the board maintainer.
Besides, we do not know which build procedure or script is out there which expects one board name or the other; merging entries would disrupt those procedures, so I want to be sure we are doing the right thing there.
Therefore, I would defer the decision of merging similar entries to the board maintainer(s), who is/are supposed to know best about this; at least, I would suggest to CC: them so that they can either Ack or Nak as they see fit.
I had already done this.
Please read this thread: http://patchwork.ozlabs.org/patch/307941/
All boards I am touching in this patch are surely unmaintained. (So we cannot ask the reason why they added multiple entries.)
I tried to contact to their maintainers but all mails have been bouncing.
So I dropped Cc: tag when I posted v4. Otherwise, I would get delivery failure notification mails from STMP again and again.
Sorry for missing the maintainers point -- as I had to catch up, I had not read the whole patch series ML history.
Still, this leaves the fact of possibly breaking scripts out there by removing an existing boards.cfg entry.
Also, Wolfgang's comment on the fact we're talking about configuration makes me realize that even binary-identical builds might behave differently on different hardware even though the software is configured identically.
In the end, I tend to think that the only drawback of having similar entries is to U-Boot architecture custodians and (some) developers, when we do a 'MAKEALL -a' or similar command, as it possibly builds a few more boards than we might need.
For ARM, the cost of the 4 entries in boards.cfg which could perhaps be removed is about 1% of the total 360 which I build routinely; as far as absolute time is concerned, that's less than 30 seconds.
I think this small benefit is not worth it. Either we remove the orphan boards entirely since we know they have no maintainer, or we keep them in all their variants.
Best Regards Masahiro Yamada
Amicalement,
Dear Masahiro Yamada,
In message 20140213143212.97DA.AA925319@jp.panasonic.com you wrote:
In the case of this patch, (I am not familiar with "ep8248" board, but I guess) ep8248 and ep8248E are different, but probably similar board.
So we can use the common entry "ep8248" for them. And "ep8248" means "ep8248 boards family", not "exactly ep8248 board".
The make target name (and as such the entry in boards.cfg) selects a specific board _configuration_, not a board family or such. We need a convenient way for the user to selct any of the supported configurations, and we also need a convenient way to actually list all supported configurations (for example, to be able to build them all in the autobuilder).
As such, combining different configurations under a common name is not possible. We do need separate entries for each and every configuration (unless someone changes the implementation such that we have another way fulfill the aforementioned requirements).
Best regards,
Wolfgang Denk
Hello Wolfgang, Albert,
Dear Masahiro Yamada,
In message 20140213143212.97DA.AA925319@jp.panasonic.com you wrote:
In the case of this patch, (I am not familiar with "ep8248" board, but I guess) ep8248 and ep8248E are different, but probably similar board.
So we can use the common entry "ep8248" for them. And "ep8248" means "ep8248 boards family", not "exactly ep8248 board".
The make target name (and as such the entry in boards.cfg) selects a specific board _configuration_, not a board family or such. We need a convenient way for the user to selct any of the supported configurations, and we also need a convenient way to actually list all supported configurations (for example, to be able to build them all in the autobuilder).
As such, combining different configurations under a common name is not possible. We do need separate entries for each and every configuration (unless someone changes the implementation such that we have another way fulfill the aforementioned requirements).
The motivation for this patch is that I want to consolidate equivalent entries before Kconfig. (I do not want to generate and maintain the same copies, configs/ep8248_defconfig and configs/ep8248E_defconfig. Or create a symbolic link from one to the other?)
If you do not like this patch, you can dismiss it for now. But can I put this discussion to the table again along with Kconfig series?
Anyway, Kconfig patches are not posted yet (please give me a little more time) so I think it is too early for our final decision.
Best Regards Masahiro Yamada
On Thu, Feb 13, 2014 at 08:24:06AM +0100, Wolfgang Denk wrote:
Dear Masahiro Yamada,
In message 20140213143212.97DA.AA925319@jp.panasonic.com you wrote:
In the case of this patch, (I am not familiar with "ep8248" board, but I guess) ep8248 and ep8248E are different, but probably similar board.
So we can use the common entry "ep8248" for them. And "ep8248" means "ep8248 boards family", not "exactly ep8248 board".
The make target name (and as such the entry in boards.cfg) selects a specific board _configuration_, not a board family or such. We need a convenient way for the user to selct any of the supported configurations, and we also need a convenient way to actually list all supported configurations (for example, to be able to build them all in the autobuilder).
As such, combining different configurations under a common name is not possible. We do need separate entries for each and every configuration (unless someone changes the implementation such that we have another way fulfill the aforementioned requirements).
OK, but we were generating the same exact code into the same binary, with just another name, and that's not useful. Or did we both miss something here?
On Thu, Jan 23, 2014 at 08:09:29PM +0900, Masahiro Yamada wrote:
There are some entries which produce the same binaries:
- ep8248E is equivalent to ep8248
- MPC8360ERDK_66 is equivalent to MPC8360ERDK
- Adder87x/AdderUSB is equivalent to Adder
- EVB64260_750CX is equivalent to EVB64260
I also notice
- Lite5200 is equivalent to icecube_5200
- Lite5200_LOWBOOT is equivalent to icecube_5200_LOWBOOT
- Lite5200_LOWBOOT08 is equivalent to icecube_5200_LOWBOOT08
But I am keeping them. (Wolfgang suggested to do so because Lite5200* are referenced in misc documents.)
Signed-off-by: Masahiro Yamada yamada.m@jp.panasonic.com
Applied to u-boot/master, thanks!
participants (4)
-
Albert ARIBAUD -
Masahiro Yamada -
Tom Rini -
Wolfgang Denk