Skip to content

ARM: omap3: beagle, evm: synchronize common setup

Tom Rini u-boot 3 versions New

Get series with b4
b4 am 20180224200221.GP4311@bill-the-cat

Versions newest first · linked by author and title

  1. v2 Latest posting 3/30 of 3 patches 0 repliesNew
  2. v2 posting 2/30 of 3 patches 0 repliesSuperseded
  3. v2 posting 1/30 of 3 patches 0 repliesSuperseded

Patches in v2 posting 3/3 No applies recorded yet

None of the 3 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.

Read the v2 thread

Cover letter [U-Boot] [PATCH v2 0/3] ARM: omap3: beagle, evm: synchronize common setup
Quoted 40 lines · Derald Woods
Quoted 28 lines · Tom Rini
Quoted 20 lines · Derald D. Woods
Quoted 14 lines · Tom Rini
Quoted 11 lines · Derald D. Woods

This short series is an attempt to make this set of boards use the same default configuration items where possible. This was prompted by an investigation into enabling SERIAL_SEARCH_ALL on omap3_evm. This feature now works for omap3_evm after this series.

The series changes the default NAND layout of MTDPARTS_DEFAULT and uses ENV_IS_IN_FAT. More detail is provided with the patches. As most things are configurable now, this should not be an issue. I am trying to get simple defaults that just boot and expose the common core features. This will make future testing and maintenance a bit more predictable, as there will be a very similar comparable set of boards.

Quoted 4 lines

I was thinking, wouldn't we want to update the beagle code now to do env in NAND on beagleboard and env on FAT on xM? We could provide a new env_get_location() to return the right location based on board. Thanks!

Quoted 6 lines

I thought of that too. xM can never use NAND. So FAT is always right for it. Regular BeagleBoard(3530) can have the environment in either location. Configuration can simply handle the user preference. I did not see a reason to add any more logic into an already heavy board file. The Overo boards are equally heavy with board type logic. For now, my thinking was to allow configuration do the work.

Quoted 7 lines

OK, but on the other hand, xM must have an SD card inserted and vanilla does not require an SD card. So now those users need to put in an SD card. Now, I honestly don't know how big a deal that is really, so I won't nak the patches. But I do think it would be the best user experience to have classic continue to work as-is and xM to finally get functional env.

I will try to add the 'env_get_location'. So let's hold until I can push a 'v3' of the series.

Quoted 8 lines

The possible env locations:

ENVL_FAT
ENVL_MMC
ENVL_NAND
ENVL_UBI

If those make sense, 'env_get_location' priority will select one of them.

Sounds good, thanks!

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180224/0f25b6e9/attachment.sig>