linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Timur Tabi <timur@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v2] qe: add ability to upload QE firmware
Date: Thu, 6 Dec 2007 16:31:18 +0100	[thread overview]
Message-ID: <200712061631.19485.arnd@arndb.de> (raw)
In-Reply-To: <47580F43.7020404@freescale.com>

On Thursday 06 December 2007, Timur Tabi wrote:
> > I'm not trying to convince you of this if it's completely pointless for
> > all your systems, just want to make sure you're aware of this option,
> > because spending a few extra code lines on it now may save you some tro=
uble
> > if you need this later.
>=20
> Um, I think I'm a little confused as to what your point is. =A0My code is=
 just a=20
> generic QE firmware uploader.

My point is that you could have some extra code that calls your
qe_upload_firmware() when the device tree contains the blob but the boot
loader did not already load it. This helps e.g. for the case where you
want to be able to install a generic Linux distribution that is not
able to ship with your firmware blob in the kernel or the root file system.
Putting the blob in the device tree makes it easier to get to a running
system then.

You can argue that the boot loader can always load the firmware in the
first place, but then you wouldn't need an implementation of
qe_upload_firmware in the kernel any more.

	Arnd <><

  reply	other threads:[~2007-12-06 15:31 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
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 [this message]
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=200712061631.19485.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=timur@freescale.com \
    /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;
as well as URLs for NNTP newsgroup(s).