public inbox for ecos-patches@sourceware.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1000819] Add support for Atmel AT91SAM9263
Date: Wed, 16 Mar 2011 16:54:00 -0000	[thread overview]
Message-ID: <20110316165405.540E72F7800B@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 #13 from Jonathan Larmour <jifl@ecoscentric.com> 2011-03-16 16:54:03 GMT ---
(In reply to comment #11)
> Let's try to push through with review and get it checked in. I've invited all
> interested parties to add themselves to the CC list and add their own comment
> where necessary/appropriate.
> 
> Evgeniy, the use of multiple patches is a great help - thank you!
> 
> Let's start with the ARM7/ARM9 abstraction work (patch 1). This looks to be a
> case of moving the existing HAL cache macros (which are not appropriate for
> AT91SAM9) from the AT91 variant package to a new ARM7 package. I assume that
> there is nothing AT91-specific in the new package so it could be used by any
> other ARM7 ports in the future. Please confirm.

No ARM7 has cache, so it's safe IMO.

> As it stands, this patch should only affect AT91 targets. The risk of breaking
> other AT91 target support is small since there does not appear to be any
> changes to the macros themselves. There is a risk of breaking compatibility
> with non-contributed ports to AT91SAM7 hardware but the effort in fixing such
> breakage should be limited to adding the new ARM7 package to the target
> description in ecos.db. I don't have a problem with this.

Particularly since it's obvious due to the change in the AT91 HAL for the ARM7
HAL to be its parent (which implies active_if).

> Is there any other code in the existing AT91 variant HAL which might not be
> appropriate for AT91SAM9?

That is in fact a very important issue, and one of the harder ones with this
patch. The AT91 HAL already has lots of ifdefs, making it harder to parse and
see what's going on. I think I already mentioned (way, way back) the SH HAL
having a more tractable approach by splitting out CPUs into their own files,
and that's what patch 3 appears to be about, but whether it's sufficient to
limit that to just PIO definitions I'm distinctly unsure. Maybe we'll leave
that to discussing Patch 3 in depth.

-- 
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.

  parent reply	other threads:[~2011-03-16 16:54 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 [this message]
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=20110316165405.540E72F7800B@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).