From: Kevin Fry <kevin@carts.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: SPI driver?
Date: Mon, 17 Dec 2001 16:48:40 -0800 [thread overview]
Message-ID: <3C1E9268.13D0EE46@carts.com> (raw)
Is there an MPC8260 SPI driver out there for Linux? It wouldn't be
terribly hard to write one on my own, but why re-invent the wheel?
A link to an 8xx driver would be almost as good. The only one I've found
so far has been SPI over a PC's parallel port. heh
Thanks
Kevin Fry
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-12-18 0:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-18 0:48 Kevin Fry [this message]
2001-12-18 9:50 ` SPI driver? Alex Zeffertt
2001-12-18 10:54 ` Alex Zeffertt
-- strict thread matches above, loose matches on Subject: below --
2007-09-10 16:16 Hesam Kohanteb
2007-09-11 15:50 ` Nicholas Hickman
2007-09-11 20:19 ` Wolfgang Denk
2001-12-18 0:58 Rod Boyce
2001-12-18 1:38 ` Kevin Fry
2000-11-08 21:18 Dan Winkler
2000-11-08 18:12 clark
2000-11-08 18:37 ` Tobias Otto-Adamczak
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=3C1E9268.13D0EE46@carts.com \
--to=kevin@carts.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).