From: "Jeremy Rosen" <Jeremy.Rosen@au.thalesgroup.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: SPI driver for m8xx
Date: Tue, 12 Mar 2002 15:03:17 +1100 [thread overview]
Message-ID: <sc8e18c0.080@gw_tms_syd2.pty.tms.thomson-csf.com> (raw)
Hello everybody
a quick question while the subject of SPI driver is in the air
I am trying to reimplement the driver for the SPI based on the driver
from David Boppuri and Prashant Patel,
and their is a thing I don't understand...
for the TX and RX buffer, they use memory they get for
m8xx_cpm_hostalloc... why ?
Does it have something to do with the MMU ?
I would like to avoid doing that, is their a way to use normal ( kernel
space) memory ?
Thanks
Jeremy
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-03-12 4:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-12 4:03 Jeremy Rosen [this message]
2002-03-12 9:28 ` SPI driver for m8xx Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2002-03-12 15:54 Navin Boppuri
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=sc8e18c0.080@gw_tms_syd2.pty.tms.thomson-csf.com \
--to=jeremy.rosen@au.thalesgroup.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).