Re: [Qemu-devel] [PATCH] Register usb-uhci reset function.

[Gleb Natapov <gleb@redhat.com>]

On Tue, Jun 16, 2009 at 08:38:24PM +0100, Paul Brook wrote:
> >What about the mantra that we should be as close to HW as possible?
> >Reseting state only on a bus level will not work for hot-unplug anyway
> 
> Real hardware consists of electrical signals. Qemu emulates the logical 
> effects of a device/subsystem, often at a much higher level. Thus "close to HW 
> as possible" is no longer a straightforward concept.
> 
You keep changing the story to suit your agenda. When I proposed a patch
to change qemu_irq() to propagate status of irq delivery back to the
caller you were against it because "this is not how real HW work" and no
amount of "Real hardware consists of electrical signals. Qemu emulates
the logical effects of a device/subsystem, often at a much higher
level." from other people haven't convince you a bit. But now, when it
comes from your mouth it is a gospel.

> Apart from anything else, I'm pretty sure than on all real hotplug PCI systems 
> each socket is on its own PCI bus to allow electrical isolation of the device 
> before physical hotplug occurs.
> 
> > > However having the device explicit set its IRQ line during a full system
> > > reset is a different matter. This is probably harmless most of the time,
> > > and may paper over other bugs (e.g. the PCI bus not being reset
> > > properly). However I do not believe it is the correct justification for
> > > these changes.
> >
> > The IRQ state inside piix3 code is QEMU implementation detail. There is
> > now such thing on real HW.
> 
> Yes there is. It's a long strip of copper wire with a pullup resistor on the 
> end.
> 
And guess who drives this long strip of copper wire?

a. Device.
b. Pci bridge
c. Lightning stroke

And BTW "pullup resistor" is there just in case no device is present.

--
			Gleb.