From: "David S. Miller" <davem@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] PCI 64-bit API up for testing
Date: Tue, 21 Aug 2001 08:09:53 -0700 (PDT) [thread overview]
Message-ID: <20010821.080953.66175161.davem@redhat.com> (raw)
As discussed much of last week between Jens and myself,
we need a PCI 64-bit API to make progress in certain
areas. It is needed for other reasons, but what Jens
is trying to solve exacerbates this need.
Jens's current highmem no-bounce patches include this
stuff, but we feel it is useful to distribute just these
changes independantly. Especially for review and to acquire
help from port maintainers.
I held off until today because I wanted to convert a few
drivers first for two reasons:
1) To provide useful 64-bit driver examples.
2) To make sure the API worked and was usable. A lot
of details were not fleshed out until I actually tried
to use the API I had initially created :-)
So this patch serves two purposes. First, it's for review
and to get feedback from other hackers and driver authors.
Second, it is for platform authors so that they can send me
the updates for their port.
Most platforms which are simple and never have more than 4GB
ram will simply define the pci_*() routines to pci64_*(), make
pci_dac_cycles_ok() always return '0' and define dma64_addr_t
to be typedef'd to "u32".
If platform maintainers could do this and send me an incremental
diff, I would appreciate it.
Currently it is "ported" and tested on ix86 and Sparc64.
Get the latest at:
ftp://ftp.kernel.org/pub/linux/kernel/people/davem/PCI64/
I've moved the older zerocopy stuff, which used to be at
the top level under davem/, to:
ftp://ftp.kernel.org/pub/linux/kernel/people/davem/ZEROCOPY/
Later,
David S. Miller
davem@redhat.com
next reply other threads:[~2001-08-21 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-21 15:09 David S. Miller [this message]
2001-08-26 20:20 ` [PATCH] PCI 64-bit API up for testing Richard Henderson
2001-08-27 22:48 ` David S. Miller
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=20010821.080953.66175161.davem@redhat.com \
--to=davem@redhat.com \
--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