From: Adrian Cox <apc@agelectronics.co.uk>
To: "David S. Miller" <davem@redhat.com>
Cc: groudier@club-internet.fr, mj@suse.cz,
lk@tantalophile.demon.co.uk, davej@suse.de,
linux-kernel@vger.kernel.org
Subject: Re: pdev_enable_device no longer used ?
Date: Tue, 12 Dec 2000 12:21:19 +0000 [thread overview]
Message-ID: <3A36183F.1EBD9368@agelectronics.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.10.10012112207400.2144-100000@linux.local> <200012112221.OAA01081@pizda.ninka.net>
"David S. Miller" wrote:
> Interpreting physical BAR values is another issue altogether. Kernel
> wide interfaces for this may be easily added to include/asm/pci.h
> infrastructure, please just choose some sane name for it and I will
> compose a patch ok? :-)
There's a semi-respectable use for BAR values: peer-to-peer mastering.
A new kernel interface could actually make that portable, eg:
int pci_peer_master_address(struct pci_dev *master,
struct pci_dev *target, int resource, unsigned long offset,
unsigned long *address);
Return values PCI_PEER_OK, PCI_PEER_NOWAY, PCI_PEER_FXBUG,
PCI_PEER_YOURE_JOKING_RIGHT, ... Bus address usable by master placed in
address.
Implementing something like this with a single hostbridge is simple.
It's harder on boards like my Intel 840 motherboard here, where the
33MHz and 66MHz buses don't talk to each other. It could eventually grow
into a big list of platform specific workarounds, but at least they'd
all be in one place where we could see them.
- Adrian Cox, AG Electronics
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-12 12:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-09 11:30 pdev_enable_device no longer used ? davej
2000-12-09 11:38 ` Russell King
2000-12-09 12:15 ` Ivan Kokshaysky
2000-12-09 12:36 ` davej
2000-12-09 12:53 ` Alan Cox
2000-12-09 13:08 ` davej
2000-12-09 13:44 ` Ivan Kokshaysky
2000-12-09 14:26 ` Gérard Roudier
2000-12-09 17:48 ` Russell King
2000-12-09 20:57 ` Alan Cox
2000-12-09 15:04 ` Martin Mares
2000-12-09 18:11 ` davej
2000-12-10 23:28 ` Jamie Lokier
2000-12-11 0:34 ` davej
2000-12-11 19:40 ` Gérard Roudier
2000-12-12 2:43 ` Jes Sorensen
2000-12-11 19:20 ` Gérard Roudier
2000-12-11 20:55 ` Martin Mares
2000-12-11 20:49 ` Gérard Roudier
2000-12-11 21:48 ` David S. Miller
2000-12-11 21:30 ` Gérard Roudier
2000-12-11 22:21 ` David S. Miller
2000-12-11 22:07 ` Gérard Roudier
2000-12-11 23:03 ` David S. Miller
2000-12-12 19:17 ` Gérard Roudier
2000-12-12 20:14 ` David S. Miller
2000-12-12 20:28 ` Gérard Roudier
2000-12-12 22:39 ` David S. Miller
2000-12-11 23:16 ` Martin Mares
2000-12-12 18:56 ` Gérard Roudier
2000-12-12 12:21 ` Adrian Cox [this message]
2000-12-12 2:39 ` Jes Sorensen
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=3A36183F.1EBD9368@agelectronics.co.uk \
--to=apc@agelectronics.co.uk \
--cc=davej@suse.de \
--cc=davem@redhat.com \
--cc=groudier@club-internet.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=lk@tantalophile.demon.co.uk \
--cc=mj@suse.cz \
/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