From: Jesse Barnes <jbarnes@engr.sgi.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
linux-ia64@vger.kernel.org,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] add legacy I/O and memory access routines to /proc/bus/pci API
Date: Thu, 16 Dec 2004 16:26:31 +0000 [thread overview]
Message-ID: <200412160826.32315.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <1103208922.25262.10.camel@gaston>
On Thursday, December 16, 2004 6:55 am, Benjamin Herrenschmidt wrote:
> On Wed, 2004-12-15 at 09:00 -0800, Jesse Barnes wrote:
> > Good, because that's exactly what it does. The arch is responsible for
> > returning the legacy I/O port or legacy ISA memory base address given a
> > pci_dev, which is used as a base for the page offset passed into mmap.
> > So e.g. mmap(..., 0xa0000) after doing ioctl(fd,
> > PCIIOC_MMAP_IS_LEGACY_MEM, ...) would get you the VGA framebuffer for the
> > device corresponding to 'fd'.
>
> Sounds good... The only thing is a pci_dev may not be available if you
> have a PCI->ISA bridge, tho you may just use the pci_dev of the
> bridge...
Well, you'll have to have a fake one at least. Remember the fds used in the
above example come from fd = open("/proc/bus/pci/BB/SS.F", O_RDWR)...
Jesse
next prev parent reply other threads:[~2004-12-16 16:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-14 17:41 [PATCH] add legacy I/O and memory access routines to /proc/bus/pci API Jesse Barnes
2004-12-14 23:55 ` Bjorn Helgaas
2004-12-15 0:11 ` Jesse Barnes
2004-12-15 3:06 ` Jesse Barnes
2004-12-15 8:57 ` [PATCH] add legacy I/O and memory access routines to Benjamin Herrenschmidt
2004-12-15 17:00 ` [PATCH] add legacy I/O and memory access routines to /proc/bus/pci API Jesse Barnes
2004-12-16 14:55 ` [PATCH] add legacy I/O and memory access routines to Benjamin Herrenschmidt
2004-12-16 16:26 ` Jesse Barnes [this message]
2004-12-15 17:27 ` [PATCH] add legacy I/O and memory access routines to /proc/bus/pci API Jesse Barnes
2004-12-15 21:03 ` Andreas Dilger
2004-12-15 23:15 ` Jesse Barnes
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=200412160826.32315.jbarnes@engr.sgi.com \
--to=jbarnes@engr.sgi.com \
--cc=benh@kernel.crashing.org \
--cc=bjorn.helgaas@hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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