From: Dan Malek <dan@embeddededge.com>
To: Dan Malek <dan@netx4.com>
Cc: Eric.Oosterhof@radisys.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: I2C module problem on 8260
Date: Tue, 12 Feb 2002 18:21:05 -0500 [thread overview]
Message-ID: <3C69A361.2070103@embeddededge.com> (raw)
In-Reply-To: 3C69A0EC.2090400@embeddededge.com
Dan Malek wrote:
> One of the programming techniques for modules is you must explicitly
> allocate
> all objects subject to DMA such that they are known to be physically
> contiguous
> if necessary.
I should have also mentioned that using these functions also returns
both physical and virtual addresses that you should keep within your
driver so you can avoid calling any function/macro that converts
between physical and virtual addresses.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-02-12 23:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-12 22:49 I2C module problem on 8260 Eric.Oosterhof
2002-02-12 23:10 ` Dan Malek
2002-02-12 23:18 ` Wolfgang Denk
2002-02-13 6:43 ` Murray Jensen
2002-02-12 23:21 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-20 19:26 Eric.Oosterhof
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=3C69A361.2070103@embeddededge.com \
--to=dan@embeddededge.com \
--cc=Eric.Oosterhof@radisys.com \
--cc=dan@netx4.com \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).