All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] PL011: Fix ID reporting
Date: Sun, 8 Jan 2012 20:44:46 +0100	[thread overview]
Message-ID: <201201082044.46412.marek.vasut@gmail.com> (raw)
In-Reply-To: <CAFEAcA82GOciRko2s3S+oTuoYv9JCB8yk1P80RG3wuvX9dBKLg@mail.gmail.com>

> On 8 January 2012 16:57, Marek Vasut <marek.vasut@gmail.com> wrote:
> >Peter Maydell wrote:
> >> Does the hardware give the ID registers the same values as stock
> >> PL011 or are the part number/designer/etc fields different?
> > 
> > Slightly different, but compatible with Linux:
> > 
> > 80075fe0: 00000011 00000010 00000024 00000000    ........$.......
> > 80075ff0: 0000000d 000000f0 00000005 000000b1    ................
> 
> OK, that's just the patchlevel -- QEMU currently reports
> itself as r1p1 (0x14 in UARTPeriphID2), and mx28 is r1p3
> or r1p4 (0x24). The manual describes no functional differences
> between r1p0 up to r1p4 (r1p5 has a different fifo size) so
> I'd be inclined not to worry about the ID registers here.

It's just their position that's different indeed. And even this can be tuned via 
props. I'll update the patch once I get FEC operational.

M
> 
> -- PMM

  reply	other threads:[~2012-01-08 19:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-07 20:11 [Qemu-devel] [PATCH] PL011: Fix ID reporting Marek Vasut
2012-01-07 20:38 ` Peter Maydell
2012-01-07 20:56   ` Marek Vasut
2012-01-08 14:36     ` Peter Maydell
2012-01-08 16:02       ` Marek Vasut
2012-01-08 16:21         ` Peter Maydell
2012-01-08 16:57           ` Marek Vasut
2012-01-08 17:10             ` Peter Maydell
2012-01-08 19:44               ` Marek Vasut [this message]
2012-01-08 21:36                 ` Peter Maydell
2012-01-08 23:59                   ` Marek Vasut

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=201201082044.46412.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.com \
    --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.