On Mon, Nov 19, 2018 at 10:54 AM Simon Glass <s...@chromium.org> wrote: > > All boards should now be migrated to use CONFIG_BLK. This series removes > those with build problems using this option. > > If maintainers want to keep these boards in they should send a patch in > the next week or two. Otherwise the board will be removed in the next > release, and will need to be added and re-reviewed later. > > The goal is to have all boards use driver model. But so far, we do allow > CONFIG_DM to not be defined. > > PLEASE NOTE: This is not an easy process. It is possible that your board > does work, or works with only minor changes. Please try to understand that > the removal of a board is not done because people don't like your board. > In fact the board might have been the first one I used when trying out > U-Boot! It's just that we expect maintainers to keep up with the migration > to driver model which has been running now for 4 years. It just isn't > possible for a few people to migrate and test hundreds of boards. > > So, send a patch!
OK, so with the intention of "need to light a fire", consider the fire lit! But, I think v2 of this series needs to: - Address the bug that's been noted of you checking on "DM_BLK" when it's really just "BLK". - Do a test build with BLK just being unconditional now. For example, you're deleting the am335x_evm family but it builds fine with BLK being enabled now. I even gave it a run time test via test.py and we're fine. So, I think a new run where you see what fails to build with BLK enabled by default now is in order to come up with a new delete list. Thanks! -- Tom _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot