From: Timur Tabi <timur@freescale.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v2] qe: add ability to upload QE firmware
Date: Wed, 05 Dec 2007 17:37:19 -0600 [thread overview]
Message-ID: <4757362F.7040404@freescale.com> (raw)
In-Reply-To: <200712060031.43171.arnd@arndb.de>
Arnd Bergmann wrote:
> Of course, that approach does not help you if the blob is not GPL compatible
> and you are relying on the dts file to be linked into the kernel,
Well, the blobs will never be GPL compatible, which is why I created the
firmware binary format. Previously, the firmware was shipped as header files
with code like this:
#define MPC8323_R1_0_UC_PATCH \
{ \
0xb3ff0006 \
, 0xffffffff \
, 0xb3ff0009 \
, 0xffffffff \
, 0xb3ff000c \
, 0xffffffff \
and so on.
To address the issue of loading the firmware before the kernel boots, I have
ported qe_upload_firmware() to U-Boot, and provided a command-line command for
uploading a firmware at an address in flash. The blob can be placed in flash,
and then a boot script will load it. The U-Boot version of qe_upload_firmware()
will also create the 'firmware' node in the device tree.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2007-12-05 23:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 22:41 [PATCH v2] qe: add ability to upload QE firmware Timur Tabi
2007-12-05 23:31 ` Arnd Bergmann
2007-12-05 23:37 ` Timur Tabi [this message]
2007-12-05 23:56 ` Arnd Bergmann
2007-12-06 0:05 ` Timur Tabi
2007-12-06 0:17 ` Arnd Bergmann
2007-12-06 15:03 ` Timur Tabi
2007-12-06 15:31 ` Arnd Bergmann
2007-12-06 15:46 ` Timur Tabi
2007-12-06 15:58 ` Arnd Bergmann
2007-12-06 15:59 ` Timur Tabi
2007-12-06 16:02 ` Kumar Gala
2007-12-06 16:12 ` Timur Tabi
2007-12-06 17:25 ` 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=4757362F.7040404@freescale.com \
--to=timur@freescale.com \
--cc=arnd@arndb.de \
--cc=linuxppc-dev@ozlabs.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.