All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RESENT PATCH v3] rockchip: update emmc/sd index for distro boot order
Date: Thu, 29 Nov 2018 22:44:58 +0100	[thread overview]
Message-ID: <EBE5067A-EBFF-4D13-874E-859620DB5B11@theobroma-systems.com> (raw)
In-Reply-To: <DA484925-8B24-4BA4-8F30-4180ED28C98A@theobroma-systems.com>



>> With this patch, people can use firmware in SD card if they want;
>> Without this patch, people never able to use firmware in SD card if eMMC
>> firmware exist (even if it's broken).
> 
> Most boards I know have the ability to bypass the internal eMMC.

One last thing: I know a number of projects developing devices using our
modules that have a SD card slot for data exchange (e.g. config data, log
files, data acquisition and export) but that don’t want endusers to boot the
device from the SD card (possibly using unauthorized firmware).

For factory use, there’s a signal on the mainboard to disable (until turned
back on by software) the on-module eMMC and (if available) SPI to allow
booting from the external SD card.  For field use, this signal is unaccessible
and can not be asserted…

Hope this provides one example to how different use cases can play out...

Thanks,
Philipp.

  reply	other threads:[~2018-11-29 21:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-28  2:06 [U-Boot] [RESENT PATCH v3] rockchip: update emmc/sd index for distro boot order Kever Yang
2018-11-28  9:15 ` Philipp Tomsich
2018-11-29  1:48   ` Kever Yang
2018-11-29  9:54     ` Wadim Egorov
2018-11-29 21:04       ` Philipp Tomsich
2018-11-30  1:27       ` Kever Yang
2018-11-30 10:26         ` Wadim Egorov
2018-11-29 21:31     ` Philipp Tomsich
2018-11-29 21:44       ` Philipp Tomsich [this message]
2018-11-29 22:01         ` Klaus Goger
2018-11-29 22:14           ` Klaus Goger
2018-11-30  2:08         ` Kever Yang
2019-01-23  2:14 ` Kever Yang
2019-01-23 11:00   ` Philipp Tomsich
2019-01-24  8:21     ` Kever Yang

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=EBE5067A-EBFF-4D13-874E-859620DB5B11@theobroma-systems.com \
    --to=philipp.tomsich@theobroma-systems.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.