Re: Adding aliases to mmc

[Dirk Behme <dirk.behme@gmail.com>]

Am 20.09.2013 19:03, schrieb Stephen Warren:
> On 09/20/2013 10:37 AM, Dirk Behme wrote:
>> Am 20.09.2013 18:05, schrieb Stephen Warren:
>>> On 09/18/2013 11:22 PM, Dirk Behme wrote:
>>> ...
>>>> If you have an embedded system were you just care a little about boot
>>>> time you don't want to do anything like U-Boot's "part uuid" every time
>>>> you boot. Or even worse, you just have a minimalistic boot loader (e.g.
>>>> U-Boot's SPL) which doesn't know anything about UUIDs and file systems.
>>>>
>>>> As mentioned above, no I don't think UUIDs work for production embedded
>>>> systems.
>>>
>>> As I said above, whatever generates the filesystem image can easily
>>> embed the appropriate UUID in the system's boot scripts or bootloader
>>> environment. There's no need to run the "part" command at run-time if
>>> there's a more appropriate flow for your situation.
>>
>> Using a simple boot loader as an example, there are no boot scripts or
>> boot loader environment. The only thing the boot loader does is loading
>> the device tree and the kernel into RAM. Where do you want to embed an
>> UUID in such a product?
>
> I think the initrd would be typical.

An embedded system typically doesn't have an initrd. The kernel boots 
directly into the rootfs on SD/eMMC.

>> To my understanding, the UUID is different for each SD card/eMMC, correct?
>
> Yes by default.
>
> Although for an embedded product with a fixed eMMC, there's no reason
> you couldn't make every device have the same UUID for the fixed device.

How do you make the eMMC on 1000 boards have the same UUID?

How do you ensure that this eMMC is enumerated as mmcblk0, always? 
Independent if there is a SD card in the second/removable slot at boot 
time or not?

Best regards

Dirk