From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] 85xx: add ability to upload QE firmware
Date: Mon, 17 Dec 2007 13:48:47 -0600 [thread overview]
Message-ID: <4766D29F.7090707@freescale.com> (raw)
In-Reply-To: <20071217193755.71F45248AC@gemini.denx.de>
Wolfgang Denk wrote:
> Think about the situation that someone whats to use DHCP to boot his
> board, which will usually result in the TFTP download of exactly
> *one* image from a TFTP server. That image should then contain the
> Linux kernel, the dtb, the QE firmware image, eventually a ramdisk,
> and maybe even more... That's what the new image format is about.
Ok, I can appreciate that, but how is my QE firmware blob any different from any
other generic binary that this new image format must support? And since this
new format is still a long way from being implemented, I don't see why it should
delay adding support for QE firmware.
The "qe fw" command requires an address, and it takes care of the rest. As long
as this new image format can identify the QE firmware within it and pass the
address of the blob to the "qe fw" command, I don't really care about the rest.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2007-12-17 19:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 22:39 [U-Boot-Users] [PATCH] 85xx: add ability to upload QE firmware Timur Tabi
2007-12-16 20:20 ` Wolfgang Denk
2007-12-17 15:33 ` Timur Tabi
2007-12-17 19:37 ` Wolfgang Denk
2007-12-17 19:48 ` Timur Tabi [this message]
2007-12-18 1:05 ` Wolfgang Denk
2007-12-18 15:12 ` Timur Tabi
2007-12-18 16:06 ` Wolfgang Denk
2007-12-17 15:42 ` 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=4766D29F.7090707@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