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 17:57:41 +0100 [thread overview]
Message-ID: <201201081757.42171.marek.vasut@gmail.com> (raw)
In-Reply-To: <CAFEAcA9EofGSbmjdeqjEBFZK9UtQbR0CcVNscvaU5c9XDV9E7A@mail.gmail.com>
> On 8 January 2012 16:02, Marek Vasut <marek.vasut@gmail.com> wrote:
> >> Can you point me to some documentation? I looked at
> >> http://cache.freescale.com/files/dsp/doc/ref_manual/MCIMX28RM.pdf?fsrch=
> >> 1&s r=7 (i.MX28 Applications Processor Reference Manual) and although it
> >> has a number of UARTs none of them looked obviously like PL011s.
> >
> > That's it, look at DUART section and Memory map section.
>
> That doesn't document that it implements the ID registers at all :-)
Well ... can't be helped.
> 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 ................
>
> Anyway, the right approach to this is going to be to have either
> (a) a qdev device with a different name [this is how we handle
> the pl061 variant in the Stellaris Luminary, for instance]
> (b) qdev properties
> so you can get the mx28 right.
This seems more correct/extensible approach.
M
>
> -- PMM
next prev parent reply other threads:[~2012-01-08 16:57 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 [this message]
2012-01-08 17:10 ` Peter Maydell
2012-01-08 19:44 ` Marek Vasut
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=201201081757.42171.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.