From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001649] AT91 hal extension
Date: Mon, 11 Mar 2013 15:19:00 -0000 [thread overview]
Message-ID: <bug-1001649-104-Sqf5NEI3Jg@http.bugs.ecos.sourceware.org/> (raw)
In-Reply-To: <bug-1001649-104@http.bugs.ecos.sourceware.org/>
Please do not reply to this email, use the link below.
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001649
--- Comment #16 from Bernd Edlinger <bernd.edlinger@hotmail.de> ---
(In reply to comment #14)
> Since John Dallaway is involved in bug 1000819 that may be or become related
> to this bug, I'm putting him on CC list.
Hello Ilija,
I am aware of this patch, but IMHO that work was concentrating
too much on re-structuring other ports, while it never made any
progress on the processor support.
It should be fairly simple to add ports for AT91SAM9263 or AT91SAM9X25
to this code base, if some one would like to do that.
Bernd.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-03-11 15:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 16:30 [Bug 1001649] New: " bugzilla-daemon
2012-08-10 16:31 ` [Bug 1001649] " bugzilla-daemon
2012-08-10 16:33 ` bugzilla-daemon
2012-08-10 16:34 ` bugzilla-daemon
2012-08-10 16:38 ` bugzilla-daemon
2012-08-10 16:40 ` bugzilla-daemon
2012-08-10 16:43 ` bugzilla-daemon
2012-08-14 7:45 ` bugzilla-daemon
2012-08-20 7:41 ` bugzilla-daemon
2012-08-20 7:51 ` bugzilla-daemon
2012-08-20 8:13 ` bugzilla-daemon
2012-09-13 11:09 ` bugzilla-daemon
2012-09-13 11:15 ` bugzilla-daemon
2012-09-13 11:16 ` bugzilla-daemon
2012-09-13 11:28 ` bugzilla-daemon
2013-03-10 16:56 ` bugzilla-daemon
2013-03-10 17:10 ` bugzilla-daemon
2013-03-11 14:05 ` bugzilla-daemon
2013-03-11 15:19 ` bugzilla-daemon [this message]
2013-03-15 1:29 ` 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-1001649-104-Sqf5NEI3Jg@http.bugs.ecos.sourceware.org/ \
--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).