public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] implement HAVE_PCI_LEGACY for ia64
Date: Mon, 10 Jan 2005 21:29:40 +0000	[thread overview]
Message-ID: <200501101329.40773.jbarnes@engr.sgi.com> (raw)

Tony, the generic part of this patch just got applied to Linus' tree.  Can you 
please include the ia64 part in the tree you have Linus pull from next?

Thanks,
Jesse

On Thursday, December 23, 2004 7:57 am, Jesse Barnes wrote:
> This patch implements the features required for the HAVE_PCI_LEGACY code in
> sysfs.  It allows userspace applications to access legacy I/O ports an
> memory space using files in sysfs on a per-bus basis.  Tested on sn2, but
> it *should* work on other ia64 platforms as well (though zx1 will probably
> need machine vectors to do routing of non-base busses).
>
>  arch/ia64/pci/pci.c             |  114
> +++++++++++++++++++++++++++++++++++++- arch/ia64/sn/pci/pci_dma.c      |  
> 64 ++++++++++++++++++++++
>  include/asm-ia64/machvec.h      |   24 ++++++++
>  include/asm-ia64/machvec_init.h |    3 +
>  include/asm-ia64/machvec_sn2.h  |    6 ++
>  include/asm-ia64/pci.h          |   14 ++++
>  include/asm-ia64/sn/sn_sal.h    |   46 ++++++++++++++++
>  7 files changed, 270 insertions(+), 1 deletion(-)
>
> Signed-off-by: Jesse Barnes <jbarnes@sgi.com>
>
> Thanks,
> Jesse

             reply	other threads:[~2005-01-10 21:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-10 21:29 Jesse Barnes [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-12-23 15:57 [PATCH] implement HAVE_PCI_LEGACY for ia64 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=200501101329.40773.jbarnes@engr.sgi.com \
    --to=jbarnes@engr.sgi.com \
    --cc=linux-ia64@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