From: Evgeniy Dushistov <dushistov@mail.ru>
To: ecos-discuss@sourceware.org, ecos-patches@ecos.sourceware.org
Subject: Re: [Bug 1000819] New: Add support for Atmel AT91SAM9263
Date: Sun, 06 Sep 2009 17:59:00 -0000 [thread overview]
Message-ID: <20090906180053.GA18355@rain> (raw)
In-Reply-To: <bug-1000819-104@http.bugs.ecos.sourceware.org/>
On Sun, Sep 06, 2009 at 06:42:24PM +0100, bugzilla-daemon@ecoscentric.com wrote:
> http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000819
>
> Summary: Add support for Atmel AT91SAM9263
> Product: eCos
> Version: CVS
> Platform: Other (please specify)
> OS/Version: Other
> Status: UNCONFIRMED
> Severity: normal
> Priority: normal
> Component: Patches and contributions
> AssignedTo: jifl@ecoscentric.com
> ReportedBy: dushistov@mail.ru
> QAContact: ecos-patches@ecos.sourceware.org
> CC: ecos-patches@ecos.sourceware.org
> Class: ---
>
>
> Here is patchset that introduces support for at91sam9263 cpu,
> it splited to logic steps:
>
> 1)introduce arm7 package
> 2)fix hal_diag to handle 115200 baudrate
> 3)separate board's pio layout
> 4)move common for arm9 code for work with mmu into common header
> 5)hal packages for at91sam9263ek and at91sam9
> 6)implement support pio interrupts in the way as ordinal interrupt
> 7)support of norflash for at91sam9263
> 8)can support for at91sam9263ek
>
Finally I got reply from fsf:
>Your ECOS assignment/disclaimer process with the FSF is currently
>complete
so I ready to start discuss technical problems for merging support
for at91sam9263 into CVS.
--
/Evgeniy
next prev parent reply other threads:[~2009-09-06 17:59 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-06 17:42 bugzilla-daemon
2009-09-06 17:46 ` [Bug 1000819] " bugzilla-daemon
2009-09-06 17:47 ` bugzilla-daemon
2009-09-06 17:48 ` bugzilla-daemon
2009-09-06 17:48 ` bugzilla-daemon
2009-09-06 17:49 ` bugzilla-daemon
2009-09-06 17:50 ` bugzilla-daemon
2009-09-06 17:51 ` bugzilla-daemon
2009-09-06 17:51 ` bugzilla-daemon
2009-09-06 17:52 ` bugzilla-daemon
2009-09-06 17:59 ` Evgeniy Dushistov [this message]
2009-09-14 7:25 ` [Bug 1000819] New: " John Dallaway
2010-02-24 11:54 ` [Bug 1000819] " bugzilla-daemon
2011-03-16 12:06 ` bugzilla-daemon
2011-03-16 16:44 ` bugzilla-daemon
2011-03-16 16:54 ` bugzilla-daemon
2011-03-16 16:59 ` bugzilla-daemon
2011-03-16 17:04 ` bugzilla-daemon
2011-03-16 17:20 ` bugzilla-daemon
2011-03-16 17:34 ` bugzilla-daemon
2011-03-16 18:34 ` bugzilla-daemon
2011-03-16 19:06 ` bugzilla-daemon
2011-03-22 13:23 ` bugzilla-daemon
2011-03-22 14:05 ` bugzilla-daemon
2011-03-22 14:06 ` bugzilla-daemon
2011-03-22 14:07 ` bugzilla-daemon
2011-03-22 14:07 ` bugzilla-daemon
2011-03-22 14:14 ` bugzilla-daemon
2011-03-22 15:09 ` bugzilla-daemon
2011-03-22 15:09 ` bugzilla-daemon
2011-05-17 22:44 ` bugzilla-daemon
2011-05-17 23:11 ` bugzilla-daemon
2011-05-18 17:20 ` bugzilla-daemon
2011-05-18 19:00 ` Grant Edwards
2011-05-18 21:15 ` bugzilla-daemon
2011-05-19 12:48 ` bugzilla-daemon
2011-05-19 12:53 ` bugzilla-daemon
2011-05-19 13:32 ` bugzilla-daemon
2011-05-24 18:28 ` 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=20090906180053.GA18355@rain \
--to=dushistov@mail.ru \
--cc=ecos-discuss@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).