From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1000819] Add support for Atmel AT91SAM9263
Date: Tue, 24 May 2011 18:28:00 -0000 [thread overview]
Message-ID: <20110524182816.6E5D02F78006@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1000819-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=1000819
--- Comment #33 from Daniel Helgason <dhelgason@shaw.ca> 2011-05-24 19:28:12 BST ---
(In reply to comment #29)
> Hi,
>
> ...As such the AT91SAM9
> series should be implemented as 4 separate platforms under this structure,
> although they probably be using common peripheral devices which may also be
> shared with the rest of the AT91 family...
That's the way I see it, too.
> ...The
> question I see is do we need to introduce a new set of devices for the AT91SAM9
> series, only if there are significant enhancements or interoperability issues
> would be my humble opinion....
I don't understand. Do you mean all AT91SAM9 SoC in one AT91SAM9 package? Or
additional AT91 peripherals?
> ...The problem I see with supporting the SAM3 from the
> same IO package is that the peripheral bus structure usually implemented on
> cortex devices is not the same as the earlier models. Perhaps the IO package
> should be divided by peripheral bus structure AHB,AMBA etc. Okay that's enough
> from me.
About the only problem I had with using existing AT91 drivers with the SAM3 is
that, under Cortex arch, the interrupt number is no longer the same as the AT91
peripheral ID. Also, I had to duplicate all the AT91 peripheral definitions
into the SAM3 port. Way too much duplication. That's why I think having the
AT91 package just be a I/O support package would be a good thing.
Dan H.
--
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.
prev parent reply other threads:[~2011-05-24 18:28 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-06 17:42 [Bug 1000819] New: " 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 ` [Bug 1000819] New: " Evgeniy Dushistov
2009-09-14 7:25 ` 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 [this message]
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=20110524182816.6E5D02F78006@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).