From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Date: Fri, 03 Aug 2012 09:32:57 -0600 Subject: [U-Boot] [PATCH v3 5/7] dfu:cmd: Support for DFU u-boot command In-Reply-To: <20120803081357.159053ec@amdc308.digital.local> References: <1341308291-14663-1-git-send-email-l.majewski@samsung.com> <1343716623-8943-1-git-send-email-l.majewski@samsung.com> <1343716623-8943-6-git-send-email-l.majewski@samsung.com> <50181267.7000005@wwwdotorg.org> <20120801091647.6a8ba9d5@amdc308.digital.local> <501963AA.90102@wwwdotorg.org> <20120802103146.5b70f39f@amdc308.digital.local> <501AA254.5070407@wwwdotorg.org> <20120803081357.159053ec@amdc308.digital.local> Message-ID: <501BEF29.2030002@wwwdotorg.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 08/03/2012 12:13 AM, Lukasz Majewski wrote: > Dear Stephen Warren, > >> Again, this is confusing two different kinds of partitions. >> >> There are HW-level partitions/regions/areas within the eMMC HW itself. >> You need to send commands to the eMMC device to select whether >> read/write commands act on the boot0/boot1/general*/user HW partition. > > This will be done via "mmc boot [dev] [HW partition (boot0/1/user]" > command (from u-boot prompt). Hmm. I still fail to see how this is any different to the existing "mmc dev" command. Are the following two commands not exactly identical: mmc dev $dev $part # already exists today mmc boot $dev $part # new command you're proposing ? > This command is not yet implemented at u-boot (at least for Trats > development board). > After its implementation it will be used as a helper function for dfu.