Hi Sascha, > > the patchstack first refactors the phyCARD-i.MX6 and phyFLEX-i.MX6 to a common > > phytec-som-imx6. Then some phyFLEX-i.MX6 variants and the new phyCORE-i.MX6 are > > added plus some environment updates and one image rename patch. > > > > The Phytec i.MX6 boards all have an EEPROM, right? No, it's possible to get a board without an EEPROM and we have some of them lying around here. > Does it have the memory setup encoded somewhere? So no, the memory is not encoded anywhere on the module. > It gets increasingly hard picking the right image for the Phytec boards. Yeah. We are discussing some solutions for that like GPIOs, EEPROM or EFuses, but nothing has emerged from that and they are only viable for new products. One simple thing would be to encode the memory configuration into the barebox image filename. So a user can look at the module, count the memory chips and banks, and pick the correct image for that. Mit freundlichen Grüßen / Kind regards, Stefan Christ On Mon, Nov 09, 2015 at 07:49:24AM +0100, Sascha Hauer wrote: > Hi Stefan, > > On Fri, Nov 06, 2015 at 11:21:48AM +0100, Stefan Christ wrote: > > Hi, > > > > the patchstack first refactors the phyCARD-i.MX6 and phyFLEX-i.MX6 to a common > > phytec-som-imx6. Then some phyFLEX-i.MX6 variants and the new phyCORE-i.MX6 are > > added plus some environment updates and one image rename patch. > > > > The Phytec i.MX6 boards all have an EEPROM, right? Does it have the > memory setup encoded somewhere? It gets increasingly hard picking the > right image for the Phytec boards. > > Sascha > > -- > Pengutronix e.K. | | > Industrial Linux Solutions | http://www.pengutronix.de/ | > Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | > Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
