From: Nathan French <nathan.french@onrampwireless.com>
To: Stefan Roese <sr@denx.de>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Lorenz Kolb <lorenz.kolb.newsgroups.nospam@lkmail.de>
Subject: Re: need help getting SPI controller working on 405EX
Date: Tue, 11 Aug 2009 08:59:26 -0700 [thread overview]
Message-ID: <1250006366.3747.8595.camel@localhost.localdomain> (raw)
In-Reply-To: <200908110744.52394.sr@denx.de>
This is good news. Can you point me towards the patch for that?
Nathan
On Tue, 2009-08-11 at 01:44 -0400, Stefan Roese wrote:
> On Monday 10 August 2009 18:07:15 Nathan French wrote:
> > > At least something similar worked for me some months ago (before we
> > > switched to a "real" driver for some custom peripheral).
> >
> > Did this work on a 4xx PowerPC platform? Or something else? I've been
> > told that there is no SPI driver for 4xx. If you have done this on 4xx
> > then I'm very interested.
>
> The 4xx SPI driver is (finally) queued for 2.6.32. So you either need to
> manually apply it now or wait a while.
>
> Best regards,
> Stefan
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
next prev parent reply other threads:[~2009-08-11 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1249574886.3747.2650.camel__48649.694157257$1249575290$gmane$org@localhost.localdomain>
2009-08-09 13:38 ` need help getting SPI controller working on 405EX Lorenz Kolb
2009-08-10 16:07 ` Nathan French
2009-08-11 5:44 ` Stefan Roese
2009-08-11 15:59 ` Nathan French [this message]
2009-08-11 16:11 ` Stefan Roese
2009-08-06 16:08 Nathan French
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=1250006366.3747.8595.camel@localhost.localdomain \
--to=nathan.french@onrampwireless.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=lorenz.kolb.newsgroups.nospam@lkmail.de \
--cc=sr@denx.de \
/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).