public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@ecoscentric.com To: ecos-bugs@ecos.sourceware.org Subject: [Bug 1000761] eCos support for MPC5xxx MCUs Date: Thu, 21 May 2009 14:25:00 -0000 [thread overview] Message-ID: <20090521142449.527E33B4005C@mail.ecoscentric.com> (raw) In-Reply-To: <bug-1000761-13@http.bugs.ecos.sourceware.org/> http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000761 John Dallaway <john@dallaway.org.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nickg@ecoscentric.com --- Comment #7 from John Dallaway <john@dallaway.org.uk> 2009-05-21 15:24:46 --- Stefan, apologies for the delay in getting back to you on this matter. Firstly, I must thank you and Jochen for your substantial contribution to the eCos project which is much appreciated. We do have some issues to work through with you: The eCos maintainers are in agreement that your implementation of support for e200 cores in the form of a new eCos architectural HAL is not really in keeping with the intended layering of eCos hardware support. Your e200 HAL package necessarily includes a lot of code copied from the standard PowerPC architectural HAL and we would wish to see any architecture-level support for e200 integrated into the standard PowerPC architectural HAL directly to avoid code duplication. In order to provide the right foundation for future PowerPC variant support, eCosCentric will be contributing a patch for the standard eCos PowerPC architectural HAL which adds architecture-level support for Book-E processors in general (including e200). I would expect this contribution to be checked-in to our public CVS repository in the next few days. Would you be able to migrate your MPC5xxx contribution to use the updated PowerPC architectural HAL? I am advised that the changes required to your own contribution should be minor and the resulting contribution would then be much more beneficial for the future of eCos on PowerPC. Of course, you may wish to wait for, and review, the updated PowerPC architectural HAL before responding to this question. Thanks, again, for supporting eCos. -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
next prev parent reply other threads:[~2009-05-21 14:25 UTC|newest] Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-1000761-13@http.bugs.ecos.sourceware.org/> 2009-05-12 16:28 ` bugzilla-daemon 2009-05-12 22:11 ` bugzilla-daemon 2009-05-14 8:17 ` bugzilla-daemon 2009-05-21 12:31 ` bugzilla-daemon 2009-05-21 14:25 ` bugzilla-daemon [this message] 2009-05-22 12:29 ` bugzilla-daemon 2009-06-02 9:55 ` bugzilla-daemon 2009-06-08 15:46 ` [Issue " bugzilla-daemon 2009-06-08 19:10 ` [Bug " bugzilla-daemon 2009-07-06 20:52 ` bugzilla-daemon 2009-07-07 6:47 ` bugzilla-daemon 2009-07-20 20:17 ` bugzilla-daemon 2009-07-20 20:47 ` bugzilla-daemon 2009-07-22 14:13 ` bugzilla-daemon 2010-09-14 15:39 ` bugzilla-daemon 2010-09-26 12:02 ` bugzilla-daemon 2010-09-28 17:14 ` bugzilla-daemon 2012-05-30 13:52 ` bugzilla-daemon 2012-05-31 12:55 ` bugzilla-daemon 2012-05-31 13:54 ` bugzilla-daemon 2012-05-31 13:55 ` bugzilla-daemon 2012-05-31 13:56 ` bugzilla-daemon 2012-06-04 9:53 ` bugzilla-daemon 2012-06-04 19:15 ` bugzilla-daemon 2012-06-05 7:57 ` bugzilla-daemon 2012-07-05 9:40 ` bugzilla-daemon 2012-07-05 9:41 ` bugzilla-daemon 2012-07-08 16:02 ` bugzilla-daemon 2012-07-08 17:27 ` bugzilla-daemon 2012-08-01 16:36 ` bugzilla-daemon 2012-08-01 16:37 ` bugzilla-daemon 2012-08-01 16:38 ` bugzilla-daemon 2012-08-01 16:39 ` bugzilla-daemon 2012-08-06 8:49 ` bugzilla-daemon 2012-08-06 8:55 ` bugzilla-daemon 2012-08-06 9:01 ` bugzilla-daemon 2012-08-06 9:37 ` bugzilla-daemon 2012-08-06 15:30 ` bugzilla-daemon 2012-08-06 15:31 ` bugzilla-daemon 2012-08-06 15:33 ` bugzilla-daemon 2012-08-06 15:42 ` bugzilla-daemon 2012-08-08 7:52 ` bugzilla-daemon 2012-08-13 7:18 ` bugzilla-daemon 2012-08-13 21:12 ` bugzilla-daemon 2012-09-30 15:38 ` bugzilla-daemon 2012-09-30 15:41 ` bugzilla-daemon 2012-09-30 19:17 ` bugzilla-daemon 2012-10-01 9:58 ` bugzilla-daemon 2012-10-05 13:06 ` bugzilla-daemon 2012-10-14 15:23 ` bugzilla-daemon 2012-10-29 9:50 ` bugzilla-daemon 2012-10-29 10:05 ` bugzilla-daemon 2012-10-29 16:58 ` bugzilla-daemon 2012-10-29 18:09 ` bugzilla-daemon 2012-10-30 13:26 ` bugzilla-daemon 2013-02-04 16:59 ` bugzilla-daemon 2013-02-04 17:01 ` bugzilla-daemon [not found] <bug-1000761-776@http.bugs.ecos.sourceware.org/> 2010-09-14 15:39 ` bugzilla-daemon 2010-09-26 12:02 ` bugzilla-daemon 2010-09-28 17:14 ` bugzilla-daemon 2012-05-30 13:52 ` bugzilla-daemon 2012-05-31 12:55 ` bugzilla-daemon 2009-05-11 17:06 [Bug 1000761] New: " bugzilla-daemon 2009-06-02 9:56 ` [Bug 1000761] " bugzilla-daemon 2009-08-06 14:30 ` bugzilla-daemon 2009-08-06 18:44 ` bugzilla-daemon 2009-08-06 18:49 ` bugzilla-daemon 2009-08-21 13:57 ` bugzilla-daemon 2009-08-21 14:04 ` 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=20090521142449.527E33B4005C@mail.ecoscentric.com \ --to=bugzilla-daemon@ecoscentric.com \ --cc=ecos-bugs@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: linkBe 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).