From: Fabien Chouteau <chouteau@adacore.com>
To: "Jiri Gaisler" <jiri@gaisler.se>,
"Andreas Färber" <afaerber@suse.de>,
qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, mark.cave-ayland@ilande.co.uk
Subject: Re: [Qemu-devel] [PATCH][SPARC] LEON3: Add emulation of AMBA plug&play
Date: Thu, 09 Oct 2014 11:21:14 +0200 [thread overview]
Message-ID: <5436538A.8030801@adacore.com> (raw)
In-Reply-To: <543593E5.5060503@gaisler.se>
On 10/08/2014 09:43 PM, Jiri Gaisler wrote:
> On 10/08/2014 05:38 PM, Andreas Färber wrote:
>> Hi,
>>
>> Am 08.10.2014 um 16:19 schrieb Fabien Chouteau:
>>> From: Jiri Gaisler <jiri@gaisler.se>
>>>
>>> AMBA plug&play is used by kernels to probe available devices (Timers,
>>> UART, etc...). This is a static declaration of devices implemented in
>>> QEMU. In the future, a more advanced version could compute those
>>> information directly from the device tree.
>>
>> Interesting. There's quite some magic numbers in the read functions; I
>> wonder if you could read them via QOM if you actually give the devices a
>> canonical path or search by type? You may want to peek at ACPI code.
>
>
> The plug&play area is similar in function to the PCI configuration
> space, indicating vendor/device ID's, address range, interrupt number
> etc. of on-chip IP cores. The 'magic' numbers could be generated by
> generic functions taking these parameters as inputs. This would
> certainly make the code more readable, and easily extended in the
> future. Would such a solution be acceptable?
>
>
That would be a great improvement, then we could try to plug it with the
QOM API to generate automatically the data.
next prev parent reply other threads:[~2014-10-09 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 14:19 [Qemu-devel] [PATCH][SPARC] LEON3: Add emulation of AMBA plug&play Fabien Chouteau
2014-10-08 15:38 ` Andreas Färber
2014-10-08 19:43 ` Jiri Gaisler
2014-10-09 9:21 ` Fabien Chouteau [this message]
2014-10-09 8:43 ` Fabien Chouteau
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=5436538A.8030801@adacore.com \
--to=chouteau@adacore.com \
--cc=afaerber@suse.de \
--cc=jiri@gaisler.se \
--cc=mark.cave-ayland@ilande.co.uk \
--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.