linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@netx4.com>
To: Ralf HECKHAUSEN <RHeckhau@frequentis.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Device driver for SPI
Date: Mon, 24 Jan 2000 15:43:22 -0500	[thread overview]
Message-ID: <388CB96A.6EC5D7A6@netx4.com> (raw)
In-Reply-To: s88c20b1.048@mail.frequentis.com


Ralf HECKHAUSEN wrote:
>
> Did anyone implement a device driver for SPI which we could use as a starting point?

I have one, but the trouble is most 8xx processors need the
microcode patches to relocate the SPI away from things like
Ethernet.  I don't have that working correctly yet, as it also
requires the SPI driver to know about the relocation.

The other question is the application interface to the SPI.
Most SPI implementations have multiple selects based upon some
general purpose register, how do you manage the full duplex
nature of the interface and so on....


	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2000-01-24 20:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-24  8:51 Device driver for SPI Ralf HECKHAUSEN
2000-01-24 20:43 ` Dan Malek [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=388CB96A.6EC5D7A6@netx4.com \
    --to=dan@netx4.com \
    --cc=RHeckhau@frequentis.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).