LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Mark Bishop <mark@bish.net>
Cc: linuxppc-dev <Linuxppc-dev@ozlabs.org>
Subject: Re: Freescale MPC8313 & SPI
Date: Wed, 25 Feb 2009 08:22:37 -0600	[thread overview]
Message-ID: <19A971C7-A024-4315-993E-3253BDE7094A@kernel.crashing.org> (raw)
In-Reply-To: <20090224201936.jlryqrul6owwc0sg@www.bish.net>


On Feb 24, 2009, at 7:19 PM, Mark Bishop wrote:

> I am trying to understand more about how to talk to different spi  
> chips using the MPC8313.  The documentation that comes with the  
> development board is really lacking and I am relying on the /usr/src/ 
> linux/Documentaion/spi.  However, I still can't seem to answer my  
> questions.
>
> 1) Which device do I open up to talk to the bus.  I would use  
> something like /dev/ttyS0 for a serial port, and I assume it would  
> be /dev/spidev.0 and I would have to make it manually using mknod -  
> but what ties the /dev/spidev.0 to the actual chip driver?  Is there  
> something I have to do in addition to mknod?
>
> 2) I would be looking for a few examples on how to talk to a SPI bus  
> as well.  I've looked at spidev_test.c and I would like to see  
> another example or two.

This question might be better asked on the spi-devel list.

https://lists.sourceforge.net/lists/listinfo/spi-devel-general

- k

      reply	other threads:[~2009-02-25 14:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-25  1:19 Freescale MPC8313 & SPI Mark Bishop
2009-02-25 14:22 ` Kumar Gala [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=19A971C7-A024-4315-993E-3253BDE7094A@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=Linuxppc-dev@ozlabs.org \
    --cc=mark@bish.net \
    /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