All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Blue Swirl <blauwirbel@gmail.com>, Bob Breuer <breuerr@mc.net>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Artyom Tarasenko <atar4qemu@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] sun4m: Add FCode ROM for TCX framebuffer
Date: Wed, 21 Aug 2013 17:29:51 +0100	[thread overview]
Message-ID: <5214EAFF.3030306@ilande.co.uk> (raw)
In-Reply-To: <CAFEAcA-viZo+G+_vz32RZCOGe0vCFW-XnYx5xHS31t3-Ex2cMg@mail.gmail.com>

On 21/08/13 16:34, Peter Maydell wrote:

>> Unfortunately the OpenBIOS repository is still based in SVN :(  There is a
>> git-svn mirror on git.qemu.org, but currently it needs to be manually
>> updated and so is generally not particularly helpful. For the 1.6 release I
>> got Anthony to manually update the repository on git.qemu.org so that the
>> git submodule reference was updated as part of the pull request.
>>
>> The main reason for not updating the git submodule in this particular commit
>> is because this is actually a precursor to another larger sun4m framebuffer
>> patch, and once both these patches are hopefully accepted then my plan is to
>> send a single pull request to update all 3 of the OpenBIOS images at the
>> same time rather than to split architectures across different OpenBIOS
>> versions.
>
> In that case we should defer adding this fcode rom blob until then.
> I really don't like the idea of having random binary blobs in our git
> repo (and thus in our release tarballs) which aren't tied exactly to
> the sources you need to rebuild them.
>
> (It's the pain of managing this which is why I don't like binary blobs
> at all, in fact. But they're a fact of life given that mostly we don't have
> easy cross-compilation setups  :-( )

Okay so in that case what is the best way to manage to process? If both 
this and the follow-up patchset are committed first without the 
associated FCode ROM images then qemu-system-sparc will be broken until 
the main OpenBIOS images are updated because (quite rightly) the TCX 
driver will attempt to load the ROM at startup and fail because they 
aren't present...?

Is the best way to send a pull request for the update OpenBIOS images 
plus associated FCode ROMs first and then work on getting the QEMU 
patches applied? This isn't strictly correct, but the display code 
currently has a "panic" fallback in place where it should try and load 
an inbuilt TCX driver if it doesn't find a valid display ROM during probe.


ATB,

Mark.

  reply	other threads:[~2013-08-21 16:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-20 22:25 [Qemu-devel] [PATCH] sun4m: Add FCode ROM for TCX framebuffer Mark Cave-Ayland
2013-08-20 22:41 ` Peter Maydell
2013-08-21 14:44   ` Mark Cave-Ayland
2013-08-21 15:34     ` Peter Maydell
2013-08-21 16:29       ` Mark Cave-Ayland [this message]
2013-08-21 17:06         ` Peter Maydell
2013-08-24 13:05           ` Mark Cave-Ayland
2013-08-21 17:54   ` Andreas Färber
2013-08-21 18:52     ` Mark Cave-Ayland
2013-08-24 17:46       ` Andreas Färber
2013-08-26 21:35         ` Mark Cave-Ayland

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=5214EAFF.3030306@ilande.co.uk \
    --to=mark.cave-ayland@ilande.co.uk \
    --cc=atar4qemu@gmail.com \
    --cc=blauwirbel@gmail.com \
    --cc=breuerr@mc.net \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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.