qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Alexey Kardashevskiy <aik@ozlabs.ru>, qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org,
	Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH qemu] pseries: Update SLOF firmware image to qemu-slof-20150313
Date: Mon, 16 Mar 2015 12:45:48 -0400	[thread overview]
Message-ID: <550708BC.5070808@suse.de> (raw)
In-Reply-To: <55065525.5060307@ozlabs.ru>



On 15.03.15 23:59, Alexey Kardashevskiy wrote:
> On 03/13/2015 10:45 PM, Alexey Kardashevskiy wrote:
>> The changelog is:
>>    > virtio: Fix vring allocation
>>    > helpers: Fix SLOF_alloc_mem_aligned to meet callers expectation
>>    > Set default palette according to "16-color Text Extension" document
>>    > Fix rectangle drawing functions to work also with higher bit depths
>>    > Fix the x86emu patch file
>>    > Silence compiler warning when building the biosemu
>>    > Use device-type Forth word to set up the corresponding property
>>    > Improve /openprom node
>>    > pci-properties: Remove redundant call to device-type
>>    > cas: reconfigure memory nodes
>>    > pci: use 64bit bar ranges
> 
> 
> It would be really nice to have in 2.3 (I saw "hardfreeze" mail), or the
> whole pseries-2.3 machine thing won't make sense. Sorry, I missed this
> earlier, I honestly thought 64bit BARs are in upstream QEMU for a long
> time already.

Thanks, applied to ppc-next (for 2.3). I want to make sure it
successfully goes through autotest first though before passing it into
the upstream tree.


Alex

      reply	other threads:[~2015-03-16 16:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13 11:45 [Qemu-devel] [PATCH qemu] pseries: Update SLOF firmware image to qemu-slof-20150313 Alexey Kardashevskiy
2015-03-16  3:59 ` Alexey Kardashevskiy
2015-03-16 16:45   ` Alexander Graf [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=550708BC.5070808@suse.de \
    --to=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=david@gibson.dropbear.id.au \
    --cc=nikunj@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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 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).