From: jgd@neon-john.com (NeonJohn)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Intro and some questions
Date: Sat, 23 Feb 2013 22:38:47 -0500 [thread overview]
Message-ID: <51298B47.5080309@neon-john.com> (raw)
In-Reply-To: <5128F06E.3060704@neon-john.com>
On 02/23/2013 11:38 AM, NeonJohn wrote:
> No, it's still just a pencil sketch. But I don't need a completed
> schematic to know that I need 3 SPI channels and the Bone only has one
> enabled by default. I've enabled the other port. Now I need to figure
> out how to enable that port's second chip select line. That was my
> question. Any suggestions?
Update: I got 'er dun today :-) I now have 3 nice SPI ports operating
on the BeagleBone.
John
--
John DeArmond
Tellico Plains, Occupied TN
http://www.fluxeon.com <-- THE source for induction heaters
http://www.neon-john.com <-- email from here
http://www.johndearmond.com <-- Best damned Blog on the net
PGP key: wwwkeys.pgp.net: BCB68D77
prev parent reply other threads:[~2013-02-24 3:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 7:31 Intro and some questions NeonJohn
2013-02-21 2:51 ` anish singh
2013-02-23 16:38 ` NeonJohn
2013-02-24 3:38 ` NeonJohn [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=51298B47.5080309@neon-john.com \
--to=jgd@neon-john.com \
--cc=kernelnewbies@lists.kernelnewbies.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).