All of lore.kernel.org
 help / color / mirror / Atom feed
From: jgd@neon-john.com (NeonJohn)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Intro and some questions
Date: Wed, 20 Feb 2013 02:31:33 -0500	[thread overview]
Message-ID: <51247BD5.4040406@neon-john.com> (raw)

Greetings,

I just discovered this list while beating my head against the wall
(kernel noobs do that a lot, I hear).  I thought I'd introduce myself.

I'm mainly an EE but with fairly extensive Unix and Linux user space
coding and with embedded system programming.  I'm a newborn infant when
it comes to the kernel.

I'm working with the BeagleBone and Robert Nelson's Angstrom derivative

https://github.com/RobertCNelson/stable-kernel

I intend to embed the BB in our new product if I can solve a small
problem.  The BB has 2 SPI ports, 1 with 1 chip select and the other
with 2.  Only one port is supported in the standard kernel.  I found
some info that guided me into activating the new port and having all
three devices enumerated in /dev.

What I have not yet been able to do is figure out how to enable that
second chip select line.  So my first question is, where do I start
looking for the existing code?  I'm hoping that I'll be lucky enough to
reuse that code, changing a bit or two in the CPU register.

Thanks,
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

             reply	other threads:[~2013-02-20  7:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-20  7:31 NeonJohn [this message]
2013-02-21  2:51 ` Intro and some questions anish singh
2013-02-23 16:38   ` NeonJohn
2013-02-24  3:38     ` NeonJohn

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=51247BD5.4040406@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.