qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Juergen Lock <qemu-l@jelal.kn-bremen.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFT] qemu 0.13.0-rc3
Date: Tue, 12 Oct 2010 17:00:34 -0500	[thread overview]
Message-ID: <4CB4DA82.3080805@codemonkey.ws> (raw)
In-Reply-To: <201010122134.o9CLYoxu005707@triton8.kn-bremen.de>

On 10/12/2010 04:34 PM, Juergen Lock wrote:
> In article<4CB38C82.1090403@linux.vnet.ibm.com>  you write:
>    
>> After suffering from a prolonged maintainer softlockup, I'm attempting
>> to get 0.13.0 release process back on track.
>>
>> I've tagged qemu-0.13.0-rc3 in git which only carries a few changes
>> since 0.13.0-rc1.  Most notably, a series of updates from Kevin Wolf and
>> Cam Macdonell's ivshmem device.
>>
>> I think we're pretty good testing wise for the final release but I
>> wanted to offer a 24-hour window for last minute fixes.  I'm only
>> interested in the following:
>>
>> 1) Patches that are *tested* against the stable-0.13 branch that are
>> already committed in master.  Please tell me explicitly that you've
>> tested the patch and how you've tested it.
>>
>> [...]
>>      
> First tests:
>
> - vmmouse seems broken (or disabled?  I don't see it in `info qdm'...)
>    

I don't think vmmouse is part of qdev yet.

> - to test arm emulation I tried booting my old zaurus images (-M terrier)
>    which failed (q&d fix below), and in the process also tested -M n800
>    w/o an image which failed with:
>
> 	qemu-system-arm: Duplicate ID 'null' for chardev
> 	Can't create serial device, empty char device
>
>    and that I got fixed by cherry-picking this commit from master:
>
> 	6a8aabd3c132188ee8e0e82ef4aba09f782cbe96
>
> 	From: Stefan Weil<weil@mail.berlios.de>
> 	Date: Sun, 8 Aug 2010 14:09:26 +0200
> 	Subject: [PATCH] hw/omap: Fix default setup for OMAP UART devices
>    

Sorry, is the patch below an additional fix?  If so, please submit 
against master.

Regards,

Anthony Liguori

> ==========
>
> And the zaurus patch, problem was the 2nd scoop's base address
> (0x08800040) gets rounded down to start of page which causes its
> io read/write callbacks to be passed addresses 0x40 higher than
> the code expects:  (as witnessed by "Bad register offset" messages
> and failure to attach the internal CF disk aka microdrive at least.)
>
> Signed-off-by: Juergen Lock<nox@jelal.kn-bremen.de>
>
> --- a/hw/zaurus.c
> +++ b/hw/zaurus.c
> @@ -70,6 +70,10 @@ static uint32_t scoop_readb(void *opaque
>   {
>       ScoopInfo *s = (ScoopInfo *) opaque;
>
> +    // XXX Workaround for base address (0x08800040 in this case)
> +    //     rounded down to start of page
> +    addr&= 0x3f;
> +
>       switch (addr) {
>       case SCOOP_MCR:
>           return s->mcr;
> @@ -104,6 +108,10 @@ static void scoop_writeb(void *opaque, t
>       ScoopInfo *s = (ScoopInfo *) opaque;
>       value&= 0xffff;
>
> +    // XXX Workaround for base address (0x08800040 in this case)
> +    //     rounded down to start of page
> +    addr&= 0x3f;
> +
>       switch (addr) {
>       case SCOOP_MCR:
>           s->mcr = value;
>
>    

  reply	other threads:[~2010-10-12 22:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-11 22:15 [Qemu-devel] [RFT] qemu 0.13.0-rc3 Anthony Liguori
2010-10-11 23:45 ` [Qemu-devel] " Luiz Capitulino
2010-10-12  0:02   ` Anthony Liguori
2010-10-12 15:43 ` [Qemu-devel] " Rick Vernam
2010-10-12 16:27 ` Stefan Weil
2010-10-12 21:34 ` Juergen Lock
2010-10-12 22:00   ` Anthony Liguori [this message]
2010-10-13  3:28     ` Juergen Lock
2010-10-13 19:12       ` [Qemu-devel] [PATCH] (master, stable-0.13) zaurus: workaround for io base address rounded down Juergen Lock
2010-10-13 19:45         ` Blue Swirl
2010-10-13 21:30           ` Juergen Lock
2010-10-13 19:24       ` [Qemu-devel] [RFT] qemu 0.13.0-rc3 Juergen Lock
2010-10-13  9:41 ` Amit Shah

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=4CB4DA82.3080805@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-l@jelal.kn-bremen.de \
    /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).