From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Bjorn Helgaas <bjorn.helgaas@hp.com>,
tony.luck@intel.com, linux-pci@vger.kernel.org
Subject: Re: [RFC/PATCH 1/2] pci: Add ability to mmap legacy_io on some platforms
Date: Fri, 3 Oct 2008 08:53:29 -0700 [thread overview]
Message-ID: <200810030853.30340.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <20081003094951.10B3FDE183@ozlabs.org>
On Friday, October 3, 2008 2:49 am Benjamin Herrenschmidt wrote:
> This adds the ability to mmap legacy IO space to the legacy_io files
> in sysfs on platforms that support it. This will allow to clean up
> X to use this instead of /dev/mem for legacy IO accesses such as
> those performed by Int10.
>
> While at it I moved pci_create/remove_legacy_files() to pci-sysfs.c
> where I think they belong, thus making more things statis in there
> and cleaned up some spurrious prototypes in the ia64 pci.h file
>
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> ---
>
> I didn't have a chance to test that I didn't break ia64, so I would
> be if somebody could give it a spin there ! Thanks !
>
> arch/ia64/include/asm/pci.h | 12 -----
> arch/ia64/pci/pci.c | 7 ++-
> drivers/pci/pci-sysfs.c | 93
> +++++++++++++++++++++++++++++++++++++++++--- drivers/pci/pci.h |
> 6 ++
> drivers/pci/probe.c | 66 -------------------------------
> 5 files changed, 102 insertions(+), 82 deletions(-)
Heh, is it obvious that this code originated on ia64 and no one ever ported it
to another platform until now? :)
Tony and/or Bjorn, do you want to take a look and make sure this is ok? If so
I can take the whole thing into the PCI tree.
Thanks,
Jesse
next prev parent reply other threads:[~2008-10-03 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 9:49 [RFC/PATCH 1/2] pci: Add ability to mmap legacy_io on some platforms Benjamin Herrenschmidt
2008-10-03 15:53 ` Jesse Barnes [this message]
2008-10-07 0:18 ` Benjamin Herrenschmidt
2008-10-03 17:55 ` Luck, Tony
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=200810030853.30340.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=benh@kernel.crashing.org \
--cc=bjorn.helgaas@hp.com \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=tony.luck@intel.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;
as well as URLs for NNTP newsgroup(s).