public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org, jay.estabrook@compaq.com
Subject: Re: [PATCH] PCI 64-bit API up for testing
Date: Sun, 26 Aug 2001 13:20:53 -0700	[thread overview]
Message-ID: <20010826132053.A8001@twiddle.net> (raw)
In-Reply-To: <20010821.080953.66175161.davem@redhat.com>
In-Reply-To: <20010821.080953.66175161.davem@redhat.com>; from davem@redhat.com on Tue, Aug 21, 2001 at 08:09:53AM -0700

[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]

On Tue, Aug 21, 2001 at 08:09:53AM -0700, David S. Miller wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/davem/PCI64/

Here's bits for Alpha vs 2.4.9 + pci64 patch 3.  It's not been
tested seriously, since I have no 64-bit capable devices.  But it
looks mostly ok, and continues to boot on a number of machines.

Something that should be mentioned in the documentation for someone
implementing these functions is that drivers will call the pci64
interfaces *even if* pci_dac_cycles_ok returns false, which means
that one has to remember what decisions were made in that function.

I'm undecided on whether we should consider such nonsense illegal.

On the one hand, it clutters up the pci mapping functions, and it
is easy to forget all the proper checks.  The sparc64 version, for
instance, will do the wrong thing if PCI_DMA_FLAG_HUGE_MAPS is set
and the device supports less than 64 bits of addressing.

On the other hand, I can also see that requiring that the driver
call the correct sets of functions based on what mode it's in will
clutter up driver source.  Given that there are more drivers than
architectures, it makes sense to keep them as clean as may be.


r~

[-- Attachment #2: d-pci64.gz --]
[-- Type: application/x-gzip, Size: 14125 bytes --]

  reply	other threads:[~2001-08-26 20:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-21 15:09 [PATCH] PCI 64-bit API up for testing David S. Miller
2001-08-26 20:20 ` Richard Henderson [this message]
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=20010826132053.A8001@twiddle.net \
    --to=rth@twiddle.net \
    --cc=davem@redhat.com \
    --cc=jay.estabrook@compaq.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