Hi Simon,
On Sun, Mar 21, 2021 at 11:51 AM Simon Glass sjg@chromium.org wrote:
Hi Bin,
On Mon, 15 Mar 2021 at 18:30, Simon Glass sjg@chromium.org wrote:
Hi Bin,
On Tue, 9 Mar 2021 at 15:34, Bin Meng bmeng.cn@gmail.com wrote:
Hi Simon,
On Sun, Feb 7, 2021 at 12:13 AM Simon Glass sjg@chromium.org wrote:
Provide the model information through sysinfo so that it shows up on boot. For memconfig 4 pins are provided, for 16 combinations. For SKU ID there are two options:
- two pins provided in a ternary arrangement, for 9 combinations.
- reading from the EC
Add a binding doc and drop the unused #defines as well.
Example:
U-Boot 2021.01-rc5
CPU: Intel(R) Celeron(R) CPU N3450 @ 1.10GHz DRAM: 3.9 GiB MMC: sdmmc@1b,0: 1, emmc@1c,0: 2 Video: 1024x768x32 @ b0000000 Model: Google Coral (memconfig 5, SKU 3)
This depends on the GPIO series:
http://patchwork.ozlabs.org/project/uboot/list/?series=228126
It looks this series is applied as patchwork returns nothing?
But the CI still fails https://source.denx.de/u-boot/custodians/u-boot-x86/-/jobs/235619
Can you apply it to u-boot-x86/next perhaps? The GPIO series was applied to -next, not -master.
I've sent a new version, v5, which should apply on the U-Boot -next branch. Are you keeping a -next for x86? If not I am happy to apply it via dm.
No, I did not track u-boot/next in the x86 repo. Feel free to apply this series via dm.
Regards, Bin