LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de> To: Grant Grundler <grundler@parisc-linux.org> Cc: Randy Dunlap <randy.dunlap@oracle.com>, Greg KH <greg@kroah.com>, Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>, Linux Kernel list <linux-kernel@vger.kernel.org>, linux-pci@atrey.karlin.mff.cuni.cz, Andrew Morton <akpm@osdl.org>, e1000-devel@lists.sourceforge.net, linux-scsi@vger.kernel.org, Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com> Subject: Re: [PATCH 1/5] Update Documentation/pci.txt Date: Fri, 22 Dec 2006 22:52:09 +0100 [thread overview] Message-ID: <458C5389.70704@s5r6.in-berlin.de> (raw) In-Reply-To: <20061222114658.01da661b.randy.dunlap@oracle.com> > 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/
next prev parent reply other threads:[~2006-12-22 21:53 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-11-22 8:05 [PATCH 1/5] Update Documentation/pci.txt Hidetoshi Seto 2006-11-22 8:54 ` Arjan van de Ven 2006-11-22 18:28 ` Grant Grundler 2006-11-24 0:38 ` Hidetoshi Seto 2006-11-24 5:12 ` Grant Grundler 2006-11-24 6:05 ` Hidetoshi Seto 2006-12-06 7:26 ` Greg KH 2006-12-07 3:55 ` Grant Grundler 2006-12-10 7:25 ` Grant Grundler 2006-12-15 17:02 ` Greg KH 2006-12-18 7:11 ` Grant Grundler 2006-12-22 19:46 ` Randy Dunlap 2006-12-22 21:52 ` Stefan Richter [this message] 2006-12-24 6:11 ` Grant Grundler 2006-12-24 6:07 ` [PATCH] Update Documentation/pci.txt v7 Grant Grundler 2006-12-24 19:16 ` Randy Dunlap 2006-12-25 7:59 ` Grant Grundler 2006-12-25 8:06 ` Grant Grundler 2006-12-25 8:08 ` Grant Grundler 2007-01-02 21:45 ` Greg KH 2007-01-03 7:15 ` Grant Grundler 2006-12-25 9:04 ` Kenji Kaneshige 2007-01-16 22:26 ` patch pci-rework-documentation-pci.txt.patch added to gregkh-2.6 tree gregkh 2007-01-17 9:10 ` Jiri Slaby 2007-01-17 19:21 ` Greg KH
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=458C5389.70704@s5r6.in-berlin.de \ --to=stefanr@s5r6.in-berlin.de \ --cc=akpm@osdl.org \ --cc=e1000-devel@lists.sourceforge.net \ --cc=greg@kroah.com \ --cc=grundler@parisc-linux.org \ --cc=kaneshige.kenji@jp.fujitsu.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pci@atrey.karlin.mff.cuni.cz \ --cc=linux-scsi@vger.kernel.org \ --cc=randy.dunlap@oracle.com \ --cc=seto.hidetoshi@jp.fujitsu.com \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).