From: Nick Garnett <nickg@ecoscentric.com>
To: Chris Holgate <chris@zynaptic.com>
Cc: ecos-patches@sourceware.org
Subject: Re: STM32 SPI bus 3 pin contention patch.
Date: Tue, 10 Feb 2009 16:28:00 -0000 [thread overview]
Message-ID: <m3ab8utfxv.fsf@xl5.calivar.com> (raw)
In-Reply-To: <4991606D.3070400@zynaptic.com>
Chris Holgate <chris@zynaptic.com> writes:
> The attached patch adds some additional comments to CDL file regarding
> the JTAG/SPI3 pin contention discussed here:
>
> http://ecos.sourceware.org/ml/ecos-discuss/2009-02/msg00050.html
>
> It also provides a new CDL option to automatically disable the JTAG port
> when SPI bus 3 is initialised. Tested using the simple SPI loopback test.
Thanks, checked in.
--
Nick Garnett eCos Kernel Architect
eCosCentric Limited http://www.eCosCentric.com The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No: 4422071
Besuchen Sie uns vom 3.-5.03.09 auf der Embedded World 2009, Stand 11-300
Visit us at Embedded World 2009, Nürnberg, Germany, 3-5 Mar, Stand 11-300
prev parent reply other threads:[~2009-02-10 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 11:09 Chris Holgate
2009-02-10 16:28 ` Nick Garnett [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=m3ab8utfxv.fsf@xl5.calivar.com \
--to=nickg@ecoscentric.com \
--cc=chris@zynaptic.com \
--cc=ecos-patches@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).