public inbox for ecos-patches@sourceware.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001550] STM32 F2 and STM3220G-EVAL / STM3240G-EVAL contribution from eCosCentric
Date: Mon, 02 Apr 2012 15:56:00 -0000	[thread overview]
Message-ID: <20120402155537.ABE2E2F78003@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001550-104@http.bugs.ecos.sourceware.org/>

Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001550

--- Comment #13 from Jonathan Larmour <jifl@ecoscentric.com> 2012-04-02 16:55:32 BST ---
(In reply to comment #10)
> Hi Jifl, can you integrate this contribution with the existing STM32
> contribution in bug #1001219 ? It seems that the Jerzy's contribution should
> really have been checked in first to avoid conflicts.

As far as I knew, that change was still work in progress, whereas this
contribution was complete and finished. Were it otherwise, then I would expect
Jerzy's contribution to have been committed, and at that point yes merging may
have had to be considered for some portions. However looking at Jerzy's
contribution, the STM32 variant changes in the eCosCentric contribution
completely subsume and obsolete what Jerzy did, given this needs to provide
both connectivity line *and* F2/F4 processor support, which changes clocking
and pin mapping properties significantly, so the result would still have been
something that looks identical or near-identical to this contribution.

As for the Ethernet, it's up to Jerzy if he wants to use the definitions
provided, or provide his own alternative in var_io_eth.h - at least a separate
file keeps it all self-contained (var_io.h was getting too big to be
navigable). All I would say is that eCosCentric's driver has undergone
extensive testing using these definitions, so they are "known good", and has
been used on multiple boards, and include necessary changed definitions for the
F2/F4 which Jerzy's obviously wouldn't. And he will probably find the majority
correspond exactly to what he's already got anyway since both the names and
values essentially come from ST anyway.

But yes, since an ethernet driver is not included in this contribution, Jerzy
is free to use or ignore these definitions. They're there to be helpful, not to
be an obstacle.

Jifl

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

  parent reply	other threads:[~2012-04-02 15:56 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-01  1:45 [Bug 1001550] New: " bugzilla-daemon
2012-04-01  1:45 ` [Bug 1001550] " bugzilla-daemon
2012-04-01  1:46 ` bugzilla-daemon
2012-04-01  1:47 ` bugzilla-daemon
2012-04-01  1:48 ` bugzilla-daemon
2012-04-01  1:49 ` bugzilla-daemon
2012-04-01  1:49 ` bugzilla-daemon
2012-04-01  1:50 ` bugzilla-daemon
2012-04-01  1:51 ` bugzilla-daemon
2012-04-01  1:51 ` bugzilla-daemon
2012-04-01 19:41 ` bugzilla-daemon
2012-04-02  7:22 ` bugzilla-daemon
2012-04-02 11:43 ` bugzilla-daemon
2012-04-02 15:08 ` bugzilla-daemon
2012-04-02 15:56 ` bugzilla-daemon [this message]
2012-04-03 11:45 ` bugzilla-daemon
2012-04-03 12:54 ` bugzilla-daemon
2012-04-03 13:32 ` bugzilla-daemon
2012-04-03 17:17 ` bugzilla-daemon
2012-04-03 18:07 ` bugzilla-daemon
2012-04-03 18:46 ` bugzilla-daemon
2012-04-03 18:59   ` Christophe Coutand
2012-04-05  8:36 ` bugzilla-daemon
2012-04-05 15:42 ` bugzilla-daemon
2012-04-13 17:50 ` bugzilla-daemon
2012-04-13 17:51 ` bugzilla-daemon
2012-04-13 17:51 ` bugzilla-daemon
2012-04-13 17:57 ` bugzilla-daemon
2012-04-13 17:57 ` bugzilla-daemon
2012-04-13 17:58 ` bugzilla-daemon
2012-04-13 17:58 ` bugzilla-daemon
2012-04-13 18:01 ` bugzilla-daemon
2012-04-15 19:27 ` bugzilla-daemon
2012-04-16 14:28 ` bugzilla-daemon
2012-04-16 14:42 ` bugzilla-daemon

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=20120402155537.ABE2E2F78003@mail.ecoscentric.com \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=ecos-patches@ecos.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).