From: "Richard Hendricks" <ra6353@email.sps.mot.com>
To: "linuxppc-embedded@lists.linuxppc.org"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: USB driver for MPC850/823
Date: Thu, 09 Mar 2000 09:34:02 -0600 [thread overview]
Message-ID: <38C7C46A.D995D187@email.sps.mot.com> (raw)
In-Reply-To: 38C7368A.7B28E61E@netx4.com
Dan Malek wrote:
>
> Just make sure kmalloc() gives you something that is properly
> aligned, as some CPM functions have rather large alignment boundaries.
> When allocated in this way, you have to chase down the pte's and modify
> the cache attributes yourself if desired.
The most famous case of this is the IDMA buffer descriptors. Unlike
everything elses buffer descriptors, the IDMA buffer descriptors must be
16 byte aligned, not 8.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-03-09 15:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-08 9:35 USB driver for MPC850/823 Bjvrn Lundberg
2000-03-08 23:53 ` Steve Calfee
2000-03-09 5:28 ` Dan Malek
2000-03-09 12:30 ` Björn Lundberg
2000-03-09 15:34 ` Richard Hendricks [this message]
2000-03-09 16:30 ` Dan Malek
2000-03-09 17:14 ` Richard Hendricks
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=38C7C46A.D995D187@email.sps.mot.com \
--to=ra6353@email.sps.mot.com \
--cc=linuxppc-embedded@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).