[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <458C5389.70704@s5r6.in-berlin.de>
Date: Fri, 22 Dec 2006 22:52:09 +0100
From: Stefan Richter <stefanr@...6.in-berlin.de>
To: Grant Grundler <grundler@...isc-linux.org>
CC: Randy Dunlap <randy.dunlap@...cle.com>, Greg KH <greg@...ah.com>,
Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>,
Linux Kernel list <linux-kernel@...r.kernel.org>,
linux-pci@...ey.karlin.mff.cuni.cz, Andrew Morton <akpm@...l.org>,
e1000-devel@...ts.sourceforge.net, linux-scsi@...r.kernel.org,
Kenji Kaneshige <kaneshige.kenji@...fujitsu.com>
Subject: Re: [PATCH 1/5] Update Documentation/pci.txt
> On Mon, 18 Dec 2006 00:11:33 -0700 Grant Grundler wrote:
...
>> +4.1 Stop IRQs on the device
>> +~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> +How to do this is chip/device specific. If it's not done, it opens
>> +the possibility of a "screaming interrupt" if (and only if)
>> +the IRQ is shared with another device.
>> +
>> +When the shared IRQ handler is "unhoooked", the remaining devices
^^^
-> unhooked
...
>> +11. MMIO Space and "Write Posting"
>> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> +Converting a driver from using I/O Port space to using MMIO space
>> +often requires some additional changes. Specifically, "write posting"
>> +needs to be handled. Many drivers (e.g. tg3, acenic, sym53c8xx_2)
>> +already do. I/O Port space guarantees write transactions reach the PCI
>
> already do this.
>
>> +device before the CPU can continue. Writes to MMIO space allow to CPU
^^
>> +continue before the transaction reaches the PCI device. HW weenies
^
-> allow the CPU to continue
--
Stefan Richter
-=====-=-==- ==-- =-==-
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists