qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
	BALATON Zoltan <balaton@eik.bme.hu>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	"Emilio G. Cota" <cota@braap.org>,
	qemu-ppc@nongnu.org, Francois Revol <revol@free.fr>,
	David Gibson <dgibson@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 0/2] Firmware blob and git submodule for Sam460ex
Date: Thu, 22 Feb 2018 08:27:36 +0100	[thread overview]
Message-ID: <e300f9da-8a47-7c0f-71db-2e5227c0c275@redhat.com> (raw)
In-Reply-To: <CAFEAcA-UaWGqLHfN_Z7h+C-k=1A5ic_REaWUu0-w19ALcNJy_A@mail.gmail.com>

On 21.02.2018 19:33, Peter Maydell wrote:
> On 21 February 2018 at 17:06, BALATON Zoltan <balaton@eik.bme.hu> wrote:
>> It's not that upstream u-boot has abandoned board support (it only removed
>> support for the PPC440 CPU it once had). The board itself never had support
>> in upstream u-boot, it only exists in vendor's fork which is the reason we
>> need a separate source and cannot use upstream u-boot source we already
>> have.
>>
>> In my opinion we don't aim to take on support for this board in u-boot, we
>> only need to include the firmware binary for the emulation to be useful
>> which then requires us to also include the source for the GPL it's licensed
>> under. I've also found a few bugs in the firmware which I've fixed but apart
>> from such occasional bug fixes when needed I don't expect to take over
>> support for the board from the hardware vendor so this source is only so we
>> can include the firmware binary which is needed for the board emulation.
>> Does this answer your concerns?
> 
> We have lots of boards we don't ship firmware blobs for and
> which we expect the users to provide the guest code for
> if they're going to use them.

... which is also somewhat unfortunate. Have you ever tried to run one
of those boards to see whether you've broken something with your code
changes or not? Hunting the firmware for such a board can be quite
challenging. I'm not saying that we should now try to include way more
firmware blobs in our repository (its size would explode, I guess), but
maybe we should at least start a Wiki page with links to the various
firmware images or so?

 Thomas

      parent reply	other threads:[~2018-02-22  7:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-20 18:10 [Qemu-devel] [PATCH 0/2] Firmware blob and git submodule for Sam460ex BALATON Zoltan
2018-02-20 17:55 ` [Qemu-devel] [PATCH 1/2] roms: Added git submodule for u-boot-sam460 (firmware for sam460ex) BALATON Zoltan
2018-02-20 17:57 ` [Qemu-devel] [PATCH 2/2] pc-bios: Added u-boot-sam460 firmware binary BALATON Zoltan
2018-02-20 18:30   ` Daniel P. Berrangé
2018-02-20 21:55     ` BALATON Zoltan
2018-02-20 18:31 ` [Qemu-devel] [PATCH 0/2] Firmware blob and git submodule for Sam460ex Peter Maydell
2018-02-20 20:44   ` Emilio G. Cota
2018-02-21 13:43     ` Peter Maydell
2018-02-21 17:06       ` BALATON Zoltan
2018-02-21 18:33         ` Peter Maydell
2018-02-22  2:11           ` David Gibson
2018-02-22  7:27           ` Thomas Huth [this message]

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=e300f9da-8a47-7c0f-71db-2e5227c0c275@redhat.com \
    --to=thuth@redhat.com \
    --cc=balaton@eik.bme.hu \
    --cc=cota@braap.org \
    --cc=dgibson@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=revol@free.fr \
    /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).