From: Wolfgang Denk <wd@denx.de>
To: Dan Malek <dan@embeddededge.com>
Cc: "barry.fisher" <barry.fisher@seranoa.com>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: Need SPI support
Date: Mon, 11 Mar 2002 22:03:14 +0100 [thread overview]
Message-ID: <20020311210319.B28C310BF2@denx.denx.de> (raw)
In-Reply-To: Your message of "Mon, 11 Mar 2002 13:56:13 EST." <3C8CFDCD.6080600@embeddededge.com>
In message <3C8CFDCD.6080600@embeddededge.com> you wrote:
>
> > Does anyone know where I might get some code to support Motorola 8260
> > Serial Peripheral Interface (SPI) for Linux.
...
> The controller set up is trivial, just copy the guts of managing BDs
> from something else, like I2C. The SPI implementations typically have
> board specific methods for device selection and devices that may be
> sensitive to whether the clock keeps running. A generic driver is
... and devices that need frame sync signals, etc.
SPI looks fine as long as you just look at the specification, but you
soon discover the ugly side when you have to use it.
> challenging due to these board variations, but a skeleton driver
> would be useful.
>
> Wolfgang, do you have something that isn't checked into BK sources :-)?
Nothing for the 8260.
In PPCBoot there is a polled mode driver (cpu/mpc8xx/spi.c) which
could easily be adapted.
The Linux stuff we have on 8xx is (1) not really ready yet and (2)
extremely special (building a multiprocessor system from a 823 and
two DSP's).
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
There are two ways to write error-free programs. Only the third one
works.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-03-11 21:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-11 16:49 Need SPI support barry.fisher
2002-03-11 18:56 ` Dan Malek
2002-03-11 21:03 ` Wolfgang Denk [this message]
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=20020311210319.B28C310BF2@denx.denx.de \
--to=wd@denx.de \
--cc=barry.fisher@seranoa.com \
--cc=dan@embeddededge.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).