+boot-architecture list On Mon, Mar 25, 2024 at 03:38:19PM +0000, Daniel Golle wrote: > On Mon, Mar 25, 2024 at 10:10:46AM -0500, Rob Herring wrote: > > On Thu, Mar 21, 2024 at 07:31:48PM +0000, Daniel Golle wrote: > > > On embedded devices using an eMMC it is common that one or more (hw/sw) > > > partitions on the eMMC are used to store MAC addresses and Wi-Fi > > > calibration EEPROM data. > > > > > > Implement an NVMEM provider backed by a block device as typically the > > > NVMEM framework is used to have kernel drivers read and use binary data > > > from EEPROMs, efuses, flash memory (MTD), ... > > > > > > In order to be able to reference hardware partitions on an eMMC, add code > > > to bind each hardware partition to a specific firmware subnode. > > > > > > Overall, this enables uniform handling across practially all flash > > > storage types used for this purpose (MTD, UBI, and now also MMC). > > > > > > As part of this series it was necessary to define a device tree schema > > > for block devices and partitions on them, which (similar to how it now > > > works also for UBI volumes) can be matched by one or more properties. > > > > > > --- > > > This series has previously been submitted as RFC on July 19th 2023[1] > > > and most of the basic idea did not change since. Another round of RFC > > > was submitted on March 5th 2024[2] which has received overall positive > > > feedback and only minor corrections have been done since (see > > > changelog below). > > > > I don't recall giving positive feedback. > > > > I still think this should use offsets rather than partition specific > > information. Not wanting to have to update the offsets if they change is > > not reason enough to not use them. > > Using raw offsets on the block device (rather than the partition) > won't work for most existing devices and boot firmware out there. They > always reference the partition, usually by the name of a GPT > partition (but sometimes also PARTUUID or even PARTNO) which is then > used in the exact same way as an MTD partition or UBI volume would be > on devices with NOR or NAND flash. MTD normally uses offsets hence why I'd like some alignment. UBI is special because raw NAND is, well, special. > Just on eMMC we usually use a GPT > or MBR partition table rather than defining partitions in DT or cmdline, > which is rather rare (for historic reasons, I suppose, but it is what it > is now). Yes, I understand how eMMC works. I don't understand why if you have part #, uuid, or name you can't get to the offset or vice-versa. You need only 1 piece of identification to map partition table entries to DT nodes. Sure, offsets can change, but surely the firmware can handle adjusting the DT? An offset would also work for the case of random firmware data on the disk that may or may not have a partition associated with it. There are certainly cases of that. I don't think we have much of a solution for that other than trying to educate vendors to not do that or OS installers only supporting installing to something other than eMMC. This is something EBBR[1] is trying to address. > Depending on the eMMC chip used, that partition may not even be at the > same offset for different batches of the same device and hence I'd > like to just do it in the same way vendor firmware does it as well. Often vendor firmware is not a model to follow... > Chad of Adtran has previously confirmed that [1], which was the > positive feedback I was refering to. Other vendors like GL-iNet or > Netgear are doing the exact same thing. > > As of now, we support this in OpenWrt by adding a lot of > board-specific knowledge to userland, which is ugly and also prevents > using things like PXE-initiated nfsroot on those devices. > > The purpose of this series is to be able to properly support such devices > (ie. practially all consumer-grade routers out there using an eMMC for > storing firmware). > > Also, those devices have enough resources to run a general purpose > distribution like Debian instead of OpenWrt, and all the userland > hacks to set MAC addresses and extract WiFi-EEPROM-data in a > board-specific ways will most certainly never find their way into > Debian. It's just not how embedded Linux works, unless you are looking > only at the RaspberryPi which got that data stored in a textfile > which is shipped by the distribution -- something very weird and very > different from literally all of-the-shelf routers, access-points or > switches I have ever seen (and I've seen many). Maybe Felix who has > seen even more of them can tell us more about that. General purpose distros want to partition the disk themselves. Adding anything to the DT for disk partitions would require the installer to be aware of it. There's various distro folks on the boot-arch list, so maybe one of them can comment. Rob [1] https://arm-software.github.io/ebbr/index.html#document-chapter4-firmware-media
