[U-Boot-Users] [PATCH] 85xx: add ability to upload QE firmware
Wolfgang Denk
wd at denx.de
Tue Dec 18 02:05:29 CET 2007
In message <4766D29F.7090707 at freescale.com> you 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
It's just another type of payload to wrap and to recognize.
> new format is still a long way from being implemented, I don't see why it should
> delay adding support for QE firmware.
Oh, that's not a long way. Probaly counted in weeks rather than
months.
> The "qe fw" command requires an address, and it takes care of the rest. As long
Yes, but how do you get this address from a multi-file image format?
> 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.
I see.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
The software required `Windows 95 or better', so I installed Linux.
More information about the U-Boot
mailing list