|
From: | Anthony Liguori |
Subject: | Re: [Qemu-devel] [RFC][PATCH 0/21] QEMU Object Model |
Date: | Wed, 27 Jul 2011 15:01:41 -0500 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110516 Lightning/1.0b2 Thunderbird/3.1.10 |
On 07/27/2011 01:51 PM, Paolo Bonzini wrote:
On 07/27/2011 06:28 PM, Anthony Liguori wrote:On 07/27/2011 10:33 AM, Paolo Bonzini wrote:On 07/27/2011 02:48 PM, Anthony Liguori wrote:So the idea here is that the PIC will multiplex a bunch of interrupts into a single line?Yes, but the device needs to know the interrupt number so it can expose it through the enumerator interface. So the configuration cannot be simply pic->irq[n] = tty->irq; Logically, it's more similar to the ISA case, but I doubt the PIC distributes all interrupts to everyone in real hardware.Is the enumerator something that has an interface to devices where the devices hold this info? Or is the enumerator just a bank of flash that's preprogrammed with fixed info?The former, at least in theory. Not sure if it also works that way in real hardware, but that's the model it exposes and the way the Android guys implemented it.I can't really find what you're describing. I think all the specs are on http://www.milkymist.org/mmsoc.htmlThat's milkymist, not GoldFish.
Oh, Goldfish is fake. It's not real hardware.The enumerator device is not a real device. It's weird because it's imaginary and was designed specifically within QEMU.
It's not a good example for discussing modelling. Regards, Anthony Liguori
You can see the code at https://github.com/patricksjackson/qemu/blob/android/hw/goldfish_device.c (see also https://github.com/patricksjackson/qemu/blob/android/hw/goldfish_device.h for the structs composing the list). Paolo
[Prev in Thread] | Current Thread | [Next in Thread] |