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] New: eCos support for MPC5xxx MCUs Date: Mon, 11 May 2009 17:06:00 -0000 [thread overview] Message-ID: <bug-1000761-13@http.bugzilla.ecoscentric.com/> (raw) http://bugzilla.ecoscentric.com/show_bug.cgi?id=1000761 Summary: eCos support for MPC5xxx MCUs Product: eCos Version: 3.0 Platform: Other (please specify) OS/Version: PowerPC Status: UNCONFIRMED Severity: enhancement Priority: normal Component: HAL AssignedTo: jifl@ecoscentric.com ReportedBy: Stefan.Singer@freescale.com QAContact: ecos-bugs@ecos.sourceware.org Class: --- Created an attachment (id=715) --> (http://bugzilla.ecoscentric.com/attachment.cgi?id=715) Patches for eCos support for MPC5xxx MCUs Hi eCos maintainers, here in Freescale we have developed a port of eCos for many of our MPC5xxx MCUs. We did this originally for eCos 2.0 and checked it recently against the new eCos 3.0 release. We have also signed the Assignment form of the Free Software Foundation (please see below the email from the copyright clerk). We made the port in a way to minimize changes to the existing sources: Those packages are new and did not exist previously: packages\devs\can\powerpc\mpc55xx packages\devs\eth\powerpc\mpc5xxx packages\devs\spi\powerpc\mpc551x packages\devs\spi\freescale\mc33905 packages\devs\eth\phytec packages\devs\serial\powerpc\mpc55xx packages\hal\powerpc\e200 packages\hal\powerpc\mpc551x packages\hal\powerpc\mpc5517 packages\hal\powerpc\mpc5517_MOST packages\hal\powerpc\mpc5553 packages\hal\powerpc\mpc5554 packages\hal\powerpc\mpc5566 packages\hal\powerpc\mpc5567 packages\hal\powerpc\mpc5567demo packages\hal\powerpc\mpc5567_ZGW packages\hal\powerpc\mpc5668 packages\hal\powerpc\mpc5668_var packages\hal\powerpc\mpc55xx packages\hal\powerpc\mpc5517_kanis packages\hal\powerpc\mpc5567pcm028 This package was modified to fix some issues regarding endianess: packages\devs\eth\smsc\lan91cxx And obviously we updated the database: packages\ecos.db How can we handle over the files now ? Is there an email adress to send them to or a webinterface ? The FAQ says, that externals can not write directly to the CVS. Best regards, Stefan Singer EMEA FAE Manager Automotive -- Configure bugmail: http://bugzilla.ecoscentric.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
next reply other threads:[~2009-05-11 17:06 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-05-11 17:06 bugzilla-daemon [this message] 2009-05-11 17:11 ` [Issue 1000761] " bugzilla-daemon 2009-05-11 18:01 ` bugzilla-daemon 2009-06-02 9:56 ` [Bug " bugzilla-daemon 2009-08-05 9:54 ` [Issue " bugzilla-daemon 2009-08-06 14:30 ` [Bug " bugzilla-daemon 2009-08-06 15:05 ` [Issue " bugzilla-daemon 2009-08-06 18:44 ` [Bug " bugzilla-daemon 2009-08-06 18:49 ` bugzilla-daemon 2009-08-07 9:23 ` [Issue " bugzilla-daemon 2009-08-21 13:57 ` [Bug " 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=bug-1000761-13@http.bugzilla.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).