linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Arvanitis <tharvan@inaccessnetworks.com>
To: linuxppc-embedded@ozlabs.org
Subject: spi on mpc82xx
Date: Tue, 29 Nov 2005 13:14:42 +0200	[thread overview]
Message-ID: <20051129111442.GB27630@inaccessnetworks.com> (raw)

Hi,

I was wondering what is the status for supporting spi devices with 2.6
on an mpc82xx device (I use an mpc8275). I checked and the kernel from
kernel.org does not include anything. Is there an spi bus
infrastructure (like i2c) coming any time soon, where one can add
support for specific chips, and then write a driver on top of that?
Or a plan for these things?

I found a patch for something like that, by Grant Likely, but I don't
know whether I should go that way.

I want to write a driver for controlling the micrel ks8995 ethernet
switch through spi. Should I just go for a self contained driver?

Thanks for you help,
-Thomas.

             reply	other threads:[~2005-11-29 11:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-29 11:14 Thomas Arvanitis [this message]
2005-11-30  5:49 ` spi on mpc82xx Kumar Gala

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=20051129111442.GB27630@inaccessnetworks.com \
    --to=tharvan@inaccessnetworks.com \
    --cc=linuxppc-embedded@ozlabs.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).