From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jesse Barnes <jbarnes@engr.sgi.com>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
linux-pci@atrey.karlin.mff.cu, 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
Date: Thu, 16 Dec 2004 14:55:22 +0000 [thread overview]
Message-ID: <1103208922.25262.10.camel@gaston> (raw)
In-Reply-To: <200412150900.18890.jbarnes@engr.sgi.com>
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...
> > There is some work done by Jon Smirl in this area (a VGA access
> > arbitration driver).
>
> I think Dave Airlie did a version of the vga class driver, and the backend
> used for /proc/bus/pci could be used for both drivers. I'm
> using /proc/bus/pci because it's available now and nearly good enough (i.e.
> this patch was all I needed to get going).
>
> Anyway, I'll post another version with Bjorn's suggestion about the ioctl for
> choosing config or legacy I/O port read/writes, since it looks like the rest
> of your concerns are dealt with.
>
> Thanks,
> Jesse
--
Benjamin Herrenschmidt <benh@kernel.crashing.org>
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jesse Barnes <jbarnes@engr.sgi.com>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
linux-pci@atrey.karlin.mff.cu, 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 15:55:22 +0100 [thread overview]
Message-ID: <1103208922.25262.10.camel@gaston> (raw)
In-Reply-To: <200412150900.18890.jbarnes@engr.sgi.com>
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...
> > There is some work done by Jon Smirl in this area (a VGA access
> > arbitration driver).
>
> I think Dave Airlie did a version of the vga class driver, and the backend
> used for /proc/bus/pci could be used for both drivers. I'm
> using /proc/bus/pci because it's available now and nearly good enough (i.e.
> this patch was all I needed to get going).
>
> Anyway, I'll post another version with Bjorn's suggestion about the ioctl for
> choosing config or legacy I/O port read/writes, since it looks like the rest
> of your concerns are dealt with.
>
> Thanks,
> Jesse
--
Benjamin Herrenschmidt <benh@kernel.crashing.org>
next prev parent reply other threads:[~2004-12-16 14:55 UTC|newest]
Thread overview: 22+ 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 17:41 ` Jesse Barnes
2004-12-14 23:55 ` Bjorn Helgaas
2004-12-14 23:55 ` Bjorn Helgaas
2004-12-15 0:11 ` Jesse Barnes
2004-12-15 0:11 ` Jesse Barnes
2004-12-15 3:06 ` 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 8:57 ` [PATCH] add legacy I/O and memory access routines to /proc/bus/pci API Benjamin Herrenschmidt
2004-12-15 17:00 ` Jesse Barnes
2004-12-15 17:00 ` Jesse Barnes
2004-12-16 14:55 ` Benjamin Herrenschmidt [this message]
2004-12-16 14:55 ` Benjamin Herrenschmidt
2004-12-16 16:26 ` Jesse Barnes
2004-12-16 16:26 ` Jesse Barnes
2004-12-15 17:27 ` Jesse Barnes
2004-12-15 17:27 ` Jesse Barnes
2004-12-15 21:03 ` Andreas Dilger
2004-12-15 21:03 ` Andreas Dilger
2004-12-15 23:15 ` Jesse Barnes
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=1103208922.25262.10.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=bjorn.helgaas@hp.com \
--cc=jbarnes@engr.sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.