dm: Complete CONFIG_BLK migration
Get series with b4
b4 am 20180629015549.GA18978@hopeVersions newest first
- v1 Latest0 of 2 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 2 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [U-Boot] [PATCH 0/2] dm: Complete CONFIG_BLK migration
Quoted 65 lines · Tom Rini
Quoted 55 lines · Simon Glass
The time has come to migrate all boards to use
CONFIG_BLK. This series is just a test to see what boards would have to be removed if we requiredCONFIG_BLK, as we plan to after the next release.This should help maintainers see what is impacted.
Hopefully maintainers will be able to convert their boards over in the next month so we we can avoid having to remove any boards.
The goal is to have all boards use driver model. But so far, we do allow
CONFIG_DMto not be defined.For 'Force BLK', here is the buildman output showing failed boards and the relatively small number of command errors:
03: Force BLK
mips: + pic32mzdask arm: + mixtile_loftq colibri_imx6_nospl sniper omap3_zoom1 tbs2910 Mele_A1000G_quad
am335x_igep003xmx6ul_14x14_evkmk802_a10sam43xx_hs_evmdevkit3250pcm051_rev3am57xx_hs_evmEmpire_electronix_m712Auxtek-T003 pcm058 zc5202am335x_shcam335x_shc_ictHummingbird_A31vining_2000am335x_evm_usbsplot1200_spligep00x0Mele_I7Wobo_i5r7-tv-dongle liteboardomap3_overoam335x_boneblackevb-ast2500 warp7gwventana_gw5904cairo A13-OLinuXinoMmccmon6_sdapalis_imx6_nospl_itwandboardbirdland_bav335acolibri_imx7colibri_imx6inet_q972xpress_splstm32f429-evaluationudoo_neoigep0032Mele_M9A13-OLinuXinoinet98v_rev2A10s-OLinuXino-M riotboard snapper9260am43xx_evmpfla02 mx6qsabreliteapalis_imx6_nospl_coms5p_gonicolibri_pxa270snapper9g20Yones_Toptech_BS1078_V2am335x_shc_sdboot_promptk2g_hs_evmcl-som-imx7am335x_shc_sdbootvf610twr_nandstm32f469-discoveryam335x_evm_normx53cx9020Empire_electronix_d709vf610twrcm_t43pengwyn stm32f746-discoSinovoip_BPI_M2Sinovoip_BPI_M3Sinlinx_SinA31spico-imx7dam43xx_evm_rtconlyLicheePi_Zeropcm051_rev1mccmon6_normx6sabreautodisplay5_factoryam335x_shc_promptgwventana_nandBananapi_M2_UltraAuxtek-T004tbs_a711cm_t335h8_homlet_v2Colombusam43xx_evm_usbhost_bootchiliboardam335x_baltoscolibri_vfmx6ul_9x9_evkkp_imx6q_tpcbk4r1 udoodifrnce_dit4350am335x_evm_norbootUTOO_P66iNet_86VSmarsboardMSI_Primo81apalis_imx6bananapi_m2_berryxilinx_zynqmp_r5birdland_bav335bam43xx_evm_qspibootCSQ_CS908Ampe_A76kp_imx53am335x_evm_spibootCubietruck_plusk2g_evmmx6sabresdomap3_logicpeppercolorfly_e708_q1pcm052gwventana_emmcam335x_boneblack_vbootam335x_shc_netbootxpress ot1200 cgtqmx6eval zc5601 devkit8000dh_imx6mx6cuboxiam57xx_evmam335x_sl50q8_a13_tabletsksimx6microblaze: + microblaze-generic powerpc: + P1010RDB-PA_36BIT_NOR_SECBOOT BSC9132QDS_SDCARD_DDRCLK100_SECUREP1010RDB-PB_SPIFLASH_SECBOOT
T1024QDS_DDR4_SECURE_BOOTcontrolcenterd_36BIT_SDCARDBSC9132QDS_SDCARD_DDRCLK133_SECUREP1010RDB-PA_SPIFLASH_SECBOOTBSC9132QDS_NAND_DDRCLK133_SECUREP1010RDB-PA_36BIT_SPIFLASH_SECBOOTP2041RDB_SECURE_BOOTP5020DS_NAND_SECURE_BOOTP1010RDB-PB_36BIT_NOR_SECBOOTBSC9132QDS_NOR_DDRCLK100_SECUREP3041DS_SECURE_BOOTT1042D4RDB_SECURE_BOOTT1042RDB_SECURE_BOOTT4240QDS_SECURE_BOOTP1010RDB-PB_36BIT_SPIFLASH_SECBOOT P1010RDB-PB_NAND_SECBOOTBSC9132QDS_SPIFLASH_DDRCLK100_SECUREP3041DS_NAND_SECURE_BOOTT4160QDS_SECURE_BOOTT2080RDB_SECURE_BOOTB4860QDS_SECURE_BOOTP4080DS_SECURE_BOOTT2080QDS_SECURE_BOOTP5040DS_SECURE_BOOTQuoted 8 lines
P1010RDB-PB_36BIT_NAND_SECBOOT
controlcenterd_36BIT_SDCARD_DEVELOPP1010RDB-PA_NAND_SECBOOTBSC9132QDS_SPIFLASH_DDRCLK133_SECUREP1010RDB-PA_NOR_SECBOOTcontrolcenterd_TRAILBLAZER_DEVELOPP5020DS_SECURE_BOOTT1024QDS_SECURE_BOOTT1040QDS_SECURE_BOOTBSC9132QDS_NOR_DDRCLK133_SECURET1024RDB_SECURE_BOOTP5040DS_NAND_SECURE_BOOTP1010RDB-PA_36BIT_NAND_SECBOOTT1042RDB_PI_NAND_SECURE_BOOTT1040RDB_SECURE_BOOTT1040D4RDB_SECURE_BOOTBSC9132QDS_NAND_DDRCLK100_SECUREP1010RDB-PB_NOR_SECBOOTT1023RDB_SECURE_BOOTcontrolcenterd_TRAILBLAZER
Quoted 4 lines
So, how are the maintainers CC'd on this feeling about the deadline? It was supposed to be 2018.05, but it's looking like we would enforce it for 2018.09 at this point in time.
So. What is the right model for this to work? Some boards may build cleanly, but may not actually boot. One can make something build by trimming things out of the config and get the board off the 'reap' list. But that is not quite the point of all this. Right. A failed build may mean you have been adding things as you can. Now your stuck trying to keep up with a moving target.
Is there a bootable reference board for each architecture variant?
I will help with the conversion work. Some good references will speed up the process. For me, at least. Just being honest.
Derald
Quoted 4 lines
_______________________________________________
U-Boot mailing list
U-Boot at lists.denx.de
https://lists.denx.de/listinfo/u-boot