From: Dirk Behme <dirk.behme@gmail.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Fabio Estevam <festevam@gmail.com>,
linux-mmc@vger.kernel.org,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Sascha Hauer <kernel@pengutronix.de>
Subject: Re: Adding aliases to mmc
Date: Fri, 20 Sep 2013 18:37:24 +0200 [thread overview]
Message-ID: <523C79C4.1070308@gmail.com> (raw)
In-Reply-To: <523C7231.7040701@wwwdotorg.org>
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?
To my understanding, the UUID is different for each SD card/eMMC, correct?
Best regards
Dirk
next prev parent reply other threads:[~2013-09-20 16:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 18:04 Adding aliases to mmc Fabio Estevam
[not found] ` <CAOMZO5CJ36JHJMaiG3QVdtpBoWd_ZyHQuRTrKHz4bLP39gpJtQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-09-18 0:06 ` Fabio Estevam
[not found] ` <CAOMZO5AT3bduZ0=EtWHuHVg6tSWrdr_ZjX5PLu815o0qgkeSig-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-09-22 6:48 ` Dirk Behme
2013-09-22 15:24 ` Fabio Estevam
[not found] ` <CAOMZO5CVTRvC1z_xzco1A9FE+GALEHAZe8WNU20sNy+oZdNe+A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-09-23 2:17 ` Fabio Estevam
2013-09-18 5:47 ` Dirk Behme
2013-09-18 15:17 ` Stephen Warren
[not found] ` <5239C40C.9030503-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-09-18 17:01 ` Dirk Behme
[not found] ` <5239DC65.3080803-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-09-18 17:13 ` Stephen Warren
[not found] ` <5239DF55.8010308-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-09-19 5:22 ` Dirk Behme
2013-09-20 16:05 ` Stephen Warren
2013-09-20 16:37 ` Dirk Behme [this message]
[not found] ` <523C79C4.1070308-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-09-20 17:03 ` Stephen Warren
2013-09-21 5:23 ` Dirk Behme
2013-09-21 7:42 ` Sascha Hauer
[not found] ` <20130921074238.GI30088-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2013-09-21 12:30 ` Michael Olbrich
2013-09-21 13:52 ` Sascha Hauer
2013-09-20 6:30 ` Chaiken, Alison
[not found] ` <60BA5429A0E1584BA3633194F6F993B50E7CE937-0dz9ie/QGrnnlEkxMdpx1dQH9K4/4qFeAL8bYrjMMd8@public.gmane.org>
2013-09-20 16:10 ` Stephen Warren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=523C79C4.1070308@gmail.com \
--to=dirk.behme@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-mmc@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).