From: Grant Grundler <grundler@cup.hp.com>
To: Philipp Rumpf <prumpf@mandrakesoft.mandrakesoft.com>
Cc: Jeff Garzik <jgarzik@mandrakesoft.mandrakesoft.com>,
Tim Waugh <twaugh@redhat.com>, Andrew Morton <andrewm@uow.edu.au>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] 2.4.2-pre3: parport_pc init_module bug
Date: Wed, 14 Feb 2001 09:25:20 -0800 [thread overview]
Message-ID: <200102141725.JAA11515@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Wed, 14 Feb 2001 05:40:03 PST." <Pine.LNX.3.96.1010214053241.12746C-100000@mandrakesoft.mandrakesoft.com>
Philipp Rumpf wrote:
> Jeff Garzik wrote:
> > Looks ok, but I wonder if we should include this list in the docs.
> > These is stuff defined by the PCI spec, and this list could potentially
> > get longer... (opinions either way wanted...)
Having people look things up in the spec isn't very user friendly.
Finding a copy of the PCI 2.1 or 2.2 spec I could pass on to others
(outside of HP) was a problem last year. The best I could do then
(legally) was point them to "PCI Systems Architecture" published
by MindShare.
> I'm not sure whether the
> plan is to have drivers handle MSIs or do it in the generic PCI code.
> Grant ?
Generic PCI code can d very little by itself with MSI since not all
platforms provide support for it - even within the same arch.
Support for MSI is very platform specific.
Eg for parisc: I expect everything but V-class to support MSI.
There are some subtle differences between transaction based
interrupts used by parisc CPU and MSI. But I don't recall what
they are at the moment - I'd have to look it up again.
I thought any x86 with SAPIC (not sure about APIC) could support
MSI as well. But I don't know the x86 arch nearly as well.
It's also possible for the driver to just ignore MSI and not use it.
ie use regular PCI IRQ lines for interrupts.
grant
Grant Grundler
parisc-linux {PCI|IOMMU|SMP} hacker
+1.408.447.7253
next prev parent reply other threads:[~2001-02-14 17:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-13 23:43 Tim Waugh
2001-02-14 8:03 ` Jeff Garzik
2001-02-14 8:53 ` James Sutherland
2001-02-14 10:53 ` Tim Waugh
2001-02-14 11:14 ` Jeff Garzik
2001-02-14 11:18 ` Tim Waugh
2001-02-14 11:21 ` Andrew Morton
2001-02-14 11:17 ` Tim Waugh
2001-02-14 11:24 ` Jeff Garzik
2001-02-14 11:40 ` Philipp Rumpf
2001-02-14 17:25 ` Grant Grundler [this message]
2001-02-14 21:12 ` Philipp Rumpf
2001-02-15 2:26 ` Grant Grundler
2001-02-18 15:05 ` Jeff Garzik
2001-02-14 11:31 ` Philipp Rumpf
2001-02-14 11:17 ` Jeff Garzik
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=200102141725.JAA11515@milano.cup.hp.com \
--to=grundler@cup.hp.com \
--cc=andrewm@uow.edu.au \
--cc=jgarzik@mandrakesoft.mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=prumpf@mandrakesoft.mandrakesoft.com \
--cc=twaugh@redhat.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: link
Be 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
all inboxes | Powered by JetHome®