From: "Asier Llano Palacios" <a.llano@usyscom.com>
To: "John Rigby" <jcrigby@gmail.com>
Cc: Txema Lopez <tlopez@aotek.es>, linuxppc-embedded@ozlabs.org
Subject: Re: mpc5200 and spi bus
Date: Thu, 03 May 2007 12:22:57 +0200 [thread overview]
Message-ID: <1178187777.25579.23.camel@a.llano.llano> (raw)
In-Reply-To: <4b73d43f0705021319y116aa62axe0d1ce868d4d7ad1@mail.gmail.com>
Thank you very much for the patch. I will tell you how it worked.
Currently I need the SPI mode PSC driver (this one), but the other one
may be quite interesting also.
Thank you,
Asier
El mi=E9, 02-05-2007 a las 14:19 -0600, John Rigby escribi=F3:
> This will take you to a page where the download attachment link will
> actually work:
>=20
> =
http://sourceforge.net/mailarchive/attachment.php?list_name=3Dspi-devel-g=
eneral&message_id=3D45DEDC70.7010301@toptica.com&counter=3D1
>=20
> On 5/2/07, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> > Hi,
> >
> > On Wed, May 02, 2007 at 10:02:44AM +0200, Asier Llano Palacios =
wrote:
> > > >
> > >
> > > I'll have a look. If don't see anything the code from 2.4.x is =
good
> > > starting point to port it.
> >
> > There was a patch for the PSC in SPI mode for 2.6 posted here:
> >
> > =
http://sourceforge.net/mailarchive/forum.php?thread_name=3D45DD9ABF.90100=
09%40toptica.com&forum_name=3Dspi-devel-general
> >
> > I can forward you the patch if you like, because the sourceforge =
server
> > only replies with "Insufficient parameters" when I click on the =
patch
> > link :(
> >
> > I myself wrote a driver for the dedicated SPI port which I can post =
on
> > spi-devel-general tomorrow (after I looked over it again).
> >
> > Best regards,
> > Sascha
> >
> > _______________________________________________
> > Linuxppc-embedded mailing list
> > Linuxppc-embedded@ozlabs.org
> > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> >=20
=20
----------------------------------------- PLEASE NOTE =
-------------------------------------------
This message, along with any attachments, may be confidential or legally =
privileged.=20
It is intended only for the named person(s), who is/are the only =
authorized recipients.
If this message has reached you in error, kindly destroy it without =
review and notify the sender immediately.
Thank you for your help.
=B5SysCom uses virus scanning software but excludes any liability for =
viruses contained in any attachment.
=20
------------------------------------ ROGAMOS LEA ESTE TEXTO =
-------------------------------
Este mensaje y sus anexos pueden contener informaci=F3n confidencial y/o =
con derecho legal.=20
Est=E1 dirigido =FAnicamente a la/s persona/s o entidad/es rese=F1adas =
como =FAnico destinatario autorizado.
Si este mensaje le hubiera llegado por error, por favor elim=EDnelo sin =
revisarlo ni reenviarlo y notif=EDquelo inmediatamente al remitente. =
Gracias por su colaboraci=F3n. =20
=B5SysCom utiliza software antivirus, pero no se hace responsable de los =
virus contenidos en los ficheros anexos.
prev parent reply other threads:[~2007-05-03 10:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 13:50 mpc5200 and spi bus Asier Llano Palacios
2007-04-26 14:49 ` Txema Lopez
2007-04-27 10:36 ` Asier Llano Palacios
2007-04-27 12:41 ` Txema Lopez
2007-05-02 8:02 ` Asier Llano Palacios
2007-05-02 17:36 ` Sascha Hauer
2007-05-02 20:19 ` John Rigby
2007-05-03 10:22 ` Asier Llano Palacios [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=1178187777.25579.23.camel@a.llano.llano \
--to=a.llano@usyscom.com \
--cc=jcrigby@gmail.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=tlopez@aotek.es \
/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).