From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] qe: add ability to upload QE firmware
Date: Fri, 30 Nov 2007 16:34:10 -0600 [thread overview]
Message-ID: <47508FE2.5020903@freescale.com> (raw)
In-Reply-To: <93E5AFB9-9143-4B73-B357-C30BB5C840D7@kernel.crashing.org>
Kumar Gala wrote:
>> +U_BOOT_CMD(
>> + qe, 4, 0, qe_cmd,
>> + "qe - QUICC Engine commands\n",
>> + "fw <addr> [<length>] - Upload firmware at address <addr>,\n"
>
> I'm at a loss, why have length at all? You seem to always take it from
> firmware->header.length.
It's optional. If you specify the length, it will validate that against
header.length. That's so that you can do this:
tftp $loadaddr $firmware
qe fw $loadaddr $filesize
If the length doesn't match, then it doesn't bother trying to parse the rest of
the image.
The Linux version of this code does the same thing, but it's probably more
useful since drivers will use request_firmware() which returns a length.
Granted, the CRC check is more bullet-proof.
> Also can we be more explicit in the help with 'Upload firmware'.. to
> 'Upload microcode firmware to QE' or something like that.
Sure. New patch coming.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2007-11-30 22:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 21:20 [U-Boot-Users] qe: add ability to upload QE firmware Timur Tabi
2007-11-30 22:28 ` Kumar Gala
2007-11-30 22:34 ` Timur Tabi [this message]
2007-11-30 22:49 ` Kumar Gala
2007-11-30 22:50 ` Timur Tabi
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=47508FE2.5020903@freescale.com \
--to=timur@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox