From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] dfu: fix some issues with reads/uploads
Date: Thu, 12 Jun 2014 09:25:12 -0600 [thread overview]
Message-ID: <5399C658.8060901@wwwdotorg.org> (raw)
In-Reply-To: <20140612091700.3122fdb3@amdc2363>
On 06/12/2014 01:17 AM, Lukasz Majewski wrote:
> Stephen Warren wrote:
...
>> Here's how I'd love to see the dfu command work. It would take a bit
>> of refactoring of the code, and a change to the format of the
>> dfu_alt_info variable and "dfu" command parameters. Perhaps we could
>> have an option to the "dfu" command saying which cmdline style the
>> user is using?
>>
>> dfu_alt_info = setting [; setting]*
>>
>> setting = mmc_format | nand_format | ram_format | fs_format
>>
>> mmc_format = "mmc" device_id hwpart_num start_sector sector_count
>>
>> nand_format = "nand" device_id start_sector sector_count
>>
>> ram_format = "ram" start_address byte_count
>>
>> fs_format = "fs" fs_device_type fs_device_id filename
>
> I think that the fs also need fs_device_id and fs_partition.
I would expect fs_device_id to include the partition information. Shell
commands such as ls and load use the following format for the device ID:
controller_id[.hw_partition][:sw_partition]
(with support for the .hw_partition field being part of a patch I sent
to get_device_and_partition() within the last few weeks). Hence, we
don't need separate fields for this. This proposal would unify the way
ls/load/dfu specified devices.
next prev parent reply other threads:[~2014-06-12 15:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 23:59 [U-Boot] [PATCH] dfu: fix some issues with reads/uploads Stephen Warren
2014-05-22 10:20 ` Lukasz Majewski
2014-05-22 17:06 ` Stephen Warren
2014-05-30 8:28 ` Lukasz Majewski
2014-05-30 20:59 ` Stephen Warren
2014-06-02 6:14 ` Lukasz Majewski
2014-06-02 15:52 ` Stephen Warren
2014-06-03 7:51 ` Lukasz Majewski
2014-06-10 17:53 ` Stephen Warren
2014-06-12 7:17 ` Lukasz Majewski
2014-06-12 15:25 ` Stephen Warren [this message]
2014-06-20 15:16 ` Lukasz Majewski
-- strict thread matches above, loose matches on Subject: below --
2014-06-10 21:25 Stephen Warren
2014-06-10 21:27 ` 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=5399C658.8060901@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox