From: Wolfgang Denk <wd@denx.de>
To: "Nicholas Hickman" <nhickman@dtechlabs.com>
Cc: Hesam.Kohanteb@Sun.COM, linuxppc-embedded@ozlabs.org
Subject: Re: SPI driver?
Date: Tue, 11 Sep 2007 22:19:26 +0200 [thread overview]
Message-ID: <20070911201926.2B0EA247CE@gemini.denx.de> (raw)
In-Reply-To: Your message of "Tue, 11 Sep 2007 11:50:56 EDT." <8140AAF341CC904BA92C3D6A5A1909782F0D4F@ditech-1.ditechllc.com>
In message <8140AAF341CC904BA92C3D6A5A1909782F0D4F@ditech-1.ditechllc.com> you wrote:
> I am also in search of this, or some information about one. Please let
> me know if you find anything.
>
> I ran across an existing platform that used an mpc8270. During boot up
> it displayed:
> [ 17.828513] SPIDriver: module license 'Proprietary' taints kernel.
> [ 17.865052] CPM SPI Driver: $Revision: 1.0 $ wd@denx.de
>
> I have been all over denx and have not been able to find it. This
> particular system used the SPI for a DSP chip.
Probably somebody copied and modified a driver they found in our
trees. We release all such code under GPL...
You can find SPI driver code in our old linuxppc_2_4_devel tree, but
this does not include support for MPC82xx; and then there is an
ancient (5+ years) 82xx SPI driver in our linux-2.4 (2.4.4) kernel
tree.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Thought for the day: What if there were no hypothetical situations?
next prev parent reply other threads:[~2007-09-11 20:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-10 16:16 SPI driver? Hesam Kohanteb
2007-09-11 15:50 ` Nicholas Hickman
2007-09-11 20:19 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-18 0:58 Rod Boyce
2001-12-18 1:38 ` Kevin Fry
2001-12-18 0:48 Kevin Fry
2001-12-18 9:50 ` Alex Zeffertt
2001-12-18 10:54 ` Alex Zeffertt
2000-11-08 21:18 Dan Winkler
2000-11-08 18:12 clark
2000-11-08 18:37 ` Tobias Otto-Adamczak
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=20070911201926.2B0EA247CE@gemini.denx.de \
--to=wd@denx.de \
--cc=Hesam.Kohanteb@Sun.COM \
--cc=linuxppc-embedded@ozlabs.org \
--cc=nhickman@dtechlabs.com \
/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).