From: Grant Likely <glikely@gmail.com>
To: bennett78@digis.net, linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: SPI bus master driver for the Freescale MPC52xx
Date: Fri, 23 Sep 2005 10:54:40 -0600 [thread overview]
Message-ID: <528646bc05092309543d4e2c2f@mail.gmail.com> (raw)
In-Reply-To: <528646bc0509230933251d6600@mail.gmail.com>
Bah! Your reply-to: address is broken. Check your email client.
let me try that again...
On 9/23/05, Grant Likely <glikely@gmail.com> wrote:
> Hi.
>
> First off, I've included the linuxppc-embedded mailing list in my
> reply. It's better to mail the list and CC: me rather than just
> mailing me. There are many others far brighter than me on the list
> who can provide far more help.
>
> On 9/22/05, Frank Bennett <bennett78@digis.net> wrote:
> > Gary:
> My name is Grant
>
> >
> > I saw your patch on http://patchwork.ozlabs.org/linuxppc
> > I'm developing a SPI driver for the Lite5200.
> Are you using a PSC or the SPI peripheral? The driver I've written is fo=
r a PSC
> >
> > What distribution of Linux is this for?
> Any distro you want. It should apply cleanly against any recent 2.6.x ke=
rnel
>
> > What is this patch registry all about?
> Are you refering to the bit about device drivers registering to the
> SPI subsystem? If so, the first patch provides the generic SPI
> infrastructure. Device drivers for SPI masters and SPI slaves
> register to the SPI subsystem. That way SPI master device drivers are
> decoupled from SPI slave device drivers. It follows the new device
> model in the 2.6.x kernels. (See "Linux Device Drivers" book from
> O'reilly for details.
>
> > Can I get a snapshot of the mpc52xx driver stuff?
> I've made no changes since posting the patch.
>
> Eventually I'll have a public git tree with all my changes posted in
> it; but not yet.
>
> > How can I contribute to this effort?
> Write code, write documentation and post patches. Also, look in the
> LKML archives. There are two other competing SPI implementations that
> are being developed. I've been pulled off onto other work so I've not
> done any additional work. The other code looks more promising.
>
> That being said, my code works for me so it may be usable for you as-is.
>
> cheers,
> g.
>
prev parent reply other threads:[~2005-09-23 16:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43335991.1040004@digis.net>
2005-09-23 16:33 ` SPI bus master driver for the Freescale MPC52xx Grant Likely
2005-09-23 16:54 ` Grant Likely [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=528646bc05092309543d4e2c2f@mail.gmail.com \
--to=glikely@gmail.com \
--cc=bennett78@digis.net \
--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).