> For any major feature that you're targeting to the next release, you should:
>
> # Make sure that you've posted a patch series to qemu-devel
> # Write a Feature page on the qemu.org wiki describing the feature and the
> motivation
> # On the release planning wiki page, link to your feature wiki p
On 09/30/2011 08:59 AM, Anthony Liguori wrote:
On 09/29/2011 10:21 PM, Stefan Berger wrote:
On 09/21/2011 08:34 PM, Anthony Liguori wrote:
For any major feature that you're targeting to the next release, you
should:
# Make sure that you've posted a patch series to qemu-devel
# Write a Feat
On 09/29/2011 10:21 PM, Stefan Berger wrote:
On 09/21/2011 08:34 PM, Anthony Liguori wrote:
For any major feature that you're targeting to the next release, you should:
# Make sure that you've posted a patch series to qemu-devel
# Write a Feature page on the qemu.org wiki describing the featu
On 09/21/2011 08:34 PM, Anthony Liguori wrote:
For any major feature that you're targeting to the next release, you
should:
# Make sure that you've posted a patch series to qemu-devel
# Write a Feature page on the qemu.org wiki describing the feature and
the motivation
# On the release pla
Am 29.09.2011 um 21:28 schrieb Blue Swirl :
> On Wed, Sep 28, 2011 at 9:21 PM, Alexander Graf wrote:
>>
>> On 27.09.2011, at 21:19, Blue Swirl wrote:
>>
>> On Tue, Sep 27, 2011 at 4:44 PM, Avi Kivity wrote:
>>
>> On 09/27/2011 07:39 PM, Blue Swirl wrote:
>>
>>
>> Well, it's not that easy.
On Wed, Sep 28, 2011 at 9:21 PM, Alexander Graf wrote:
>
> On 27.09.2011, at 21:19, Blue Swirl wrote:
>
> On Tue, Sep 27, 2011 at 4:44 PM, Avi Kivity wrote:
>
> On 09/27/2011 07:39 PM, Blue Swirl wrote:
>
>
> Well, it's not that easy. As the other mapping is part of an ordinary
>
> BAR,
>
> yo
On 27.09.2011, at 21:19, Blue Swirl wrote:
> On Tue, Sep 27, 2011 at 4:44 PM, Avi Kivity wrote:
>> On 09/27/2011 07:39 PM, Blue Swirl wrote:
>>>
Well, it's not that easy. As the other mapping is part of an ordinary
BAR,
you need to setup the device (at least PCI_COMMAND
On Tue, Sep 27, 2011 at 4:44 PM, Avi Kivity wrote:
> On 09/27/2011 07:39 PM, Blue Swirl wrote:
>>
>> >
>> > Well, it's not that easy. As the other mapping is part of an ordinary
>> > BAR,
>> > you need to setup the device (at least PCI_COMMAND and
>> > PCI_BASE_ADDRESS_0)
>> > so it responds t
On 09/27/2011 07:39 PM, Blue Swirl wrote:
>
> Well, it's not that easy. As the other mapping is part of an ordinary BAR,
> you need to setup the device (at least PCI_COMMAND and PCI_BASE_ADDRESS_0)
> so it responds to memory requests, and also enable the bridge.
>
> We could hack it by havin
On Tue, Sep 27, 2011 at 8:57 AM, Avi Kivity wrote:
> On 09/27/2011 11:33 AM, Avi Kivity wrote:
>>
>> On 09/26/2011 09:07 PM, Blue Swirl wrote:
>>>
>>> >> The default address is used for early serial printk in OpenBIOS, so
>>> >> it
>>> >> should still work.
>>> >
>>> > Ok, so drop the extra map
On 09/27/2011 11:33 AM, Avi Kivity wrote:
On 09/26/2011 09:07 PM, Blue Swirl wrote:
>> The default address is used for early serial printk in OpenBIOS,
so it
>> should still work.
>
> Ok, so drop the extra mapping, but init the dynamic mapping to
0x80013000.
That should work.
It's alrea
On 09/26/2011 09:07 PM, Blue Swirl wrote:
>> The default address is used for early serial printk in OpenBIOS, so it
>> should still work.
>
> Ok, so drop the extra mapping, but init the dynamic mapping to 0x80013000.
That should work.
It's already there (macio.c):
if (macio_state->escc
On Mon, Sep 26, 2011 at 5:24 PM, Avi Kivity wrote:
> On 09/26/2011 08:20 PM, Blue Swirl wrote:
>>
>> On Mon, Sep 26, 2011 at 5:18 PM, Avi Kivity wrote:
>> > On 09/26/2011 08:15 PM, Blue Swirl wrote:
>> >>
>> >> On Mon, Sep 26, 2011 at 10:08 AM, Avi Kivity wrote:
>> >> > On 09/25/2011 08:
On 09/26/2011 08:20 PM, Blue Swirl wrote:
On Mon, Sep 26, 2011 at 5:18 PM, Avi Kivity wrote:
> On 09/26/2011 08:15 PM, Blue Swirl wrote:
>>
>> On Mon, Sep 26, 2011 at 10:08 AM, Avi Kivitywrote:
>> >On 09/25/2011 08:31 PM, Blue Swirl wrote:
>> >>
>> >>>
>> >>> Please po
On Mon, Sep 26, 2011 at 5:18 PM, Avi Kivity wrote:
> On 09/26/2011 08:15 PM, Blue Swirl wrote:
>>
>> On Mon, Sep 26, 2011 at 10:08 AM, Avi Kivity wrote:
>> > On 09/25/2011 08:31 PM, Blue Swirl wrote:
>> >>
>> >> >
>> >> > Please point out a test case and I'll try to fix it.
>> >>
>> >> Run
On 09/26/2011 08:15 PM, Blue Swirl wrote:
On Mon, Sep 26, 2011 at 10:08 AM, Avi Kivity wrote:
> On 09/25/2011 08:31 PM, Blue Swirl wrote:
>>
>> >
>> >Please point out a test case and I'll try to fix it.
>>
>> Run qemu-system-ppc without any arguments. There is a black bar
>> (because of
On Mon, Sep 26, 2011 at 10:08 AM, Avi Kivity wrote:
> On 09/25/2011 08:31 PM, Blue Swirl wrote:
>>
>> >
>> > Please point out a test case and I'll try to fix it.
>>
>> Run qemu-system-ppc without any arguments. There is a black bar
>> (because of vga.chain4), it shouldn't be there.
>
> With your
On 09/26/2011 01:08 PM, Avi Kivity wrote:
On 09/25/2011 08:31 PM, Blue Swirl wrote:
>
> Please point out a test case and I'll try to fix it.
Run qemu-system-ppc without any arguments. There is a black bar
(because of vga.chain4), it shouldn't be there.
With your pci hole patch, it's fixed, e
On 09/25/2011 08:31 PM, Blue Swirl wrote:
>
> Please point out a test case and I'll try to fix it.
Run qemu-system-ppc without any arguments. There is a black bar
(because of vga.chain4), it shouldn't be there.
With your pci hole patch, it's fixed, except for:
escc_mem = escc_init(0x8001
On 09/25/2011 09:10 AM, Avi Kivity wrote:
On 09/24/2011 11:05 AM, Blue Swirl wrote:
On Thu, Sep 22, 2011 at 12:34 AM, Anthony Liguori wrote:
> Consider this a friendly reminder that we're only three weeks away from the
> soft feature freeze for 1.0. I've written a wiki page about my expectations
On Sun, Sep 25, 2011 at 4:48 PM, Avi Kivity wrote:
> On 09/25/2011 07:36 PM, Blue Swirl wrote:
>>
>> On Sun, Sep 25, 2011 at 2:10 PM, Avi Kivity wrote:
>> > On 09/24/2011 11:05 AM, Blue Swirl wrote:
>> >>
>> >> On Thu, Sep 22, 2011 at 12:34 AM, Anthony
>> >> Liguori
>> >> wrote:
>> >> >
On 09/25/2011 07:36 PM, Blue Swirl wrote:
On Sun, Sep 25, 2011 at 2:10 PM, Avi Kivity wrote:
> On 09/24/2011 11:05 AM, Blue Swirl wrote:
>>
>> On Thu, Sep 22, 2011 at 12:34 AM, Anthony Liguori
>>wrote:
>> >Consider this a friendly reminder that we're only three weeks away from
>> >
On Sun, Sep 25, 2011 at 2:10 PM, Avi Kivity wrote:
> On 09/24/2011 11:05 AM, Blue Swirl wrote:
>>
>> On Thu, Sep 22, 2011 at 12:34 AM, Anthony Liguori
>> wrote:
>> > Consider this a friendly reminder that we're only three weeks away from
>> > the
>> > soft feature freeze for 1.0. I've written
On Sat, Sep 24, 2011 at 9:56 PM, Anthony Liguori wrote:
>
> On Sep 24, 2011 3:05 AM, "Blue Swirl" wrote:
>>
>> On Thu, Sep 22, 2011 at 12:34 AM, Anthony Liguori
>> wrote:
>> > Consider this a friendly reminder that we're only three weeks away from
>> > the
>> > soft feature freeze for 1.0. I've
On 09/24/2011 11:05 AM, Blue Swirl wrote:
On Thu, Sep 22, 2011 at 12:34 AM, Anthony Liguori wrote:
> Consider this a friendly reminder that we're only three weeks away from the
> soft feature freeze for 1.0. I've written a wiki page about my expectations
> for the soft feature freeze. It's
On Sep 24, 2011 3:05 AM, "Blue Swirl" wrote:
>
> On Thu, Sep 22, 2011 at 12:34 AM, Anthony Liguori
wrote:
> > Consider this a friendly reminder that we're only three weeks away from
the
> > soft feature freeze for 1.0. I've written a wiki page about my
expectations
> > for the soft feature freez
On Thu, Sep 22, 2011 at 12:34 AM, Anthony Liguori wrote:
> Consider this a friendly reminder that we're only three weeks away from the
> soft feature freeze for 1.0. I've written a wiki page about my expectations
> for the soft feature freeze. It's inlined here for easier commenting.
I think th
Consider this a friendly reminder that we're only three weeks away from the soft
feature freeze for 1.0. I've written a wiki page about my expectations for the
soft feature freeze. It's inlined here for easier commenting.
== What is the soft feature freeze? ==
The soft feature freeze is the
28 matches
Mail list logo
