From: Gary Thomas <gary@mlbassoc.com>
To: Will Wagner <will_wagner@carallon.com>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] I2C and SPI porting help
Date: Fri, 28 Oct 2005 14:27:00 -0000 [thread overview]
Message-ID: <1130509581.5754.122.camel@hermes> (raw)
In-Reply-To: <436233D2.7030105@carallon.com>
On Fri, 2005-10-28 at 15:21 +0100, Will Wagner wrote:
> Carlos Sobrinho wrote:
> > Hello there.
> >
> > I'm working with a AEB-1 board and I implemented the SPI and I2C buses with
> > bit bang but now I would like to migrate my code to use the cyg_i2c_* and
> > cyg_spi_* infrastructure.
> >
> > I read the hardware porting guide but I still need some more info.
> > Can anyone point me in the right direction? Maybe give a example?
> > I read that I only need some basic io in some functions and I need to pass the
> > function pointer to the I2C/SPI struct.
> >
> > Do I need to add something in the packages/dev/spi... or can I use it in my
> > own application?
> >
> > Any information would be gladly appreciated
>
> I can send you my implementation of SPI using an MPC866P if you want an
> example.
>
Could you post it here (so we may all benefit)?
Does it use the cyg_XXX infrastructure?
Thanks
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2005-10-28 14:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 14:12 Carlos Sobrinho
2005-10-28 14:20 ` Will Wagner
2005-10-28 14:22 ` Carlos Sobrinho
2005-10-28 14:27 ` Gary Thomas [this message]
2005-10-28 14:37 ` Will Wagner
2005-10-28 14:51 ` Gary Thomas
2005-10-28 14:39 ` Carlos Sobrinho
2005-10-28 14:51 ` Gary Thomas
2005-10-28 15:04 ` Carlos Sobrinho
2005-10-28 15:09 ` Gary Thomas
2005-10-28 15:13 ` Andrew Lunn
2005-10-28 15:27 ` Carlos Sobrinho
2005-10-28 15:22 ` Carlos Sobrinho
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=1130509581.5754.122.camel@hermes \
--to=gary@mlbassoc.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=will_wagner@carallon.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 read-only IMAP folder(s) and NNTP newsgroup(s).