public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Erdfelt <johannes@erdfelt.com>
To: "David S. Miller" <davem@redhat.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: struct page to 36 (or 64) bit bus address?
Date: Thu, 9 Aug 2001 16:35:32 -0400	[thread overview]
Message-ID: <20010809163531.D1575@sventech.com> (raw)
In-Reply-To: <20010809151022.C1575@sventech.com> <E15UvLO-0007tH-00@the-village.bc.nu> <15218.61869.424038.30544@pizda.ninka.net>
In-Reply-To: <15218.61869.424038.30544@pizda.ninka.net>; from davem@redhat.com on Thu, Aug 09, 2001 at 01:25:17PM -0700

On Thu, Aug 09, 2001, David S. Miller <davem@redhat.com> wrote:
> 
> Alan Cox writes:
>  > > Obviously the more portable way across architectures is using the PCI
>  > > DMA API but when will the implementation be fixed so I can use it to
>  > > exploit the full potential of this device?
>  > 
>  > 2.5 I believe, ping the peacefrog and ask <DaveM@redhat.com>
> 
> That's the current plan.  There may be a 2.4.x backport, but no
> promises.  It all depends upon how straightforward the changes
> are.

It's not a big deal. It's just less efficient which isn't the end of the
world.

> Note, if you use the "bttv method" (ie. virt_to_bus) your driver will
> then fail to compile on several platforms.

So noted. I already have a PCI DMA API version, but I wanted to code up
a "i have an i386 and gigs of memory" version as well.

JE


  reply	other threads:[~2001-08-09 20:38 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-09 18:40 struct page to 36 (or 64) bit bus address? Johannes Erdfelt
2001-08-09 19:09 ` Alan Cox
2001-08-09 19:10   ` Johannes Erdfelt
2001-08-09 19:19     ` Alan Cox
2001-08-09 20:25       ` David S. Miller
2001-08-09 20:35         ` Johannes Erdfelt [this message]
2001-08-10  7:00           ` Gerd Knorr
2001-08-10  7:56             ` Johannes Erdfelt
2001-08-10 21:58             ` David S. Miller
2001-08-11  7:09               ` Gerd Knorr
2001-08-12 10:49                 ` Write Combining (Write Coalescing) on memory mapped I/O on IA64 Steffen Persvold
2001-08-11 15:32               ` struct page to 36 (or 64) bit bus address? Jens Axboe
2001-08-11 15:56           ` Andrea Arcangeli
2001-08-11 16:13             ` Sandy Harris
2001-08-12  8:00               ` David S. Miller
     [not found] <no.id>
2001-08-12 11:49 ` Alan Cox
2001-08-13 13:51   ` David S. Miller
2001-08-13 14:09 ` Alan Cox
2001-08-13 14:21   ` David S. Miller
2001-08-13 19:07     ` Gérard Roudier
2001-08-13 19:42       ` David S. Miller
2001-08-13 15:10 ` Alan Cox

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=20010809163531.D1575@sventech.com \
    --to=johannes@erdfelt.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=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