From: Wolfgang Denk <wd@denx.de>
To: "dibacco\@inwind\.it" <dibacco@inwind.it>
Cc: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: SPI support for MPC8xx in ELDK 3.1.1?
Date: Sat, 11 Feb 2006 00:26:14 +0100 [thread overview]
Message-ID: <20060210232615.0EC073525CC@atlas.denx.de> (raw)
In-Reply-To: Your message of "Sat, 11 Feb 2006 00:04:09 +0100." <IUHUQX$E3BAE7D116850E80B61395D5308F6B3C@libero.it>
In message <IUHUQX$E3BAE7D116850E80B61395D5308F6B3C@libero.it> you wrote:
>
> the support for SPI device for MPC8xx (MPC880) is present in the ELDK 3.1.1 ?
Yes, if you use the ELDK in combination with a kernel tree that
supports SPI on your board.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
When some people discover the truth, they just can't understand why
everybody isn't eager to hear it.
prev parent reply other threads:[~2006-02-10 23:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-10 23:04 SPI support for MPC8xx in ELDK 3.1.1? dibacco
2006-02-10 23:26 ` Wolfgang Denk [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=20060210232615.0EC073525CC@atlas.denx.de \
--to=wd@denx.de \
--cc=dibacco@inwind.it \
--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).