From: "David S. Miller" <davem@redhat.com>
To: Jes.Sorensen@cern.ch
Cc: rmk@arm.linux.org.uk, linux-kernel@vger.rutgers.edu
Subject: Re: DMA changes in 2.3.41 - how the f* do I get this working on ARM?
Date: Mon, 31 Jan 2000 02:09:37 -0800 [thread overview]
Message-ID: <200001311009.CAA06036@pizda.ninka.net> (raw)
In-Reply-To: <d3oga2r22z.fsf@lxplus011.cern.ch> (message from Jes Sorensen on 31 Jan 2000 11:02:28 +0100)
From: Jes Sorensen <Jes.Sorensen@cern.ch>
Date: 31 Jan 2000 11:02:28 +0100
The place where this is a real problem is in drivers where data is
shared between the adapter and the host CPU, for instance the
53c7xx driver. On the m68k we currently use a
kernel_set_cachemode() function to change the caching of the page
allocated for the shared structures, but thats a pretty non
portable way of doing it. I would like to see something a
get_free_cachecoherent_page() interface instead, what do you think
of that?
Sounds like pci_alloc_consistent()
Go read the document and check out the interfaces, I believe
you'll be pleasantly surprised :-)
Later,
David S. Miller
davem@redhat.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-01-31 7:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-30 0:06 Russell King
2000-01-30 5:52 ` Andre Hedrick
2000-01-30 6:01 ` Jakub Jelinek
2000-01-30 9:48 ` Russell King
2000-01-30 22:11 ` David S. Miller
2000-01-30 23:49 ` Russell King
2000-01-31 0:24 ` David S. Miller
2000-01-31 4:27 ` Andre Hedrick
2000-01-31 4:27 ` David S. Miller
2000-01-31 10:02 ` Jes Sorensen
2000-01-31 10:09 ` David S. Miller [this message]
2000-01-31 11:45 ` Jakub Jelinek
2000-01-31 12:48 ` Jes Sorensen
2000-01-31 18:00 ` Jeff Garzik
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=200001311009.CAA06036@pizda.ninka.net \
--to=davem@redhat.com \
--cc=Jes.Sorensen@cern.ch \
--cc=linux-kernel@vger.rutgers.edu \
--cc=rmk@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®