Hi Sascha,
Hi Stefan,
On Wed, Jul 10, 2019 at 01:17:28PM +0200, Stefan Riedmueller wrote:
PHYTEC_ENTRY(start_phytec_phycore_imx6dl_som_nand_256mb, imx6dl_phytec_phycore_som_nand, SZ_256M, true);
+PHYTEC_ENTRY(start_phytec_phycore_imx6dl_som_lc_nand_256mb, imx6dl_phytec_phycore_som_lc_nand, SZ_256M, true);
PHYTEC_ENTRY(start_phytec_phycore_imx6dl_som_nand_1gib, imx6dl_phytec_phycore_som_nand, SZ_1G, true);
PHYTEC_ENTRY(start_phytec_phycore_imx6dl_som_emmc_1gib, imx6dl_phytec_phycore_som_emmc, SZ_1G, true);
+PHYTEC_ENTRY(start_phytec_phycore_imx6dl_som_lc_emmc_1gib, imx6dl_phytec_phycore_som_lc_emmc, SZ_1G, true);
PHYTEC_ENTRY(start_phytec_phycore_imx6q_som_nand_1gib, imx6q_phytec_phycore_som_nand, SZ_1G, true);
PHYTEC_ENTRY(start_phytec_phycore_imx6qp_som_nand_1gib, imx6qp_phytec_phycore_som_nand, SZ_1G, true);
PHYTEC_ENTRY(start_phytec_phycore_imx6q_som_emmc_1gib, imx6q_phytec_phycore_som_emmc, SZ_1G, true);
I am a bit worried that with this series the combinatoric explosion of
the Phytec boards goes into another round. For some reason the lowcost
NAND version has 256MiB SDRAM and the eMMC version has 1GiB SDRAM. I
guess different combinations are not supported because you haven't
produced them yet, but they might appear sooner or later. Even now it is
really hard to pick a board from the shelf and find the right barebox
binary for it. Do you have any ideas/plans to improve this?
I agree and I don't like the amount of images much either. We already had
some discussions here about this but did not find a satisfying solution yet.
It seems all boards have EEPROMs. Wouldn't it be an option to store some
information there?
The problem here is that the EEPROM is an option and there are SOMs out
there which do not have it (people try to save money where ever they can).
There are plans to make use of the EEPROM but they probably won't affect the
i.MX 6 for reasons I just mentioned.
Another point is: Do we really need image variants for eMMC and NAND? In
the end the drivers detect automatically if one or the other is equipped
on the board.
There is also a problem here as both options share some pins. So pinmuxing
would still be something to take care of.
Let's go crazy now. How about a QR code on the board with a link that
describes which hardware (SoC variant, amount of memory, NAND/eMMC) I
am looking at?
That would be very convenient and I will gladly pass this idea to the
product management.
Anyway, applied, thanks. It would just be nice to see some improvements
here.
Thanks
Stefan
Sascha
_______________________________________________
barebox mailing list
barebox@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/barebox
