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: Tue, 22 Mar 2011 14:14:00 -0000	[thread overview]
Message-ID: <20110322141355.653CC2F78008@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 #22 from John Dallaway <john@dallaway.org.uk> 2011-03-22 14:13:53 GMT ---
Patch 3 is separating the PIO layout definitions for various AT91 family
processors into separate header files. Historically, these definitions have all
been placed in var_io.h within various preprocessor blocks under the control
of:

  CYGHWR_HAL_ARM_AT91_M55800A
  CYGHWR_HAL_ARM_AT91SAM7
  CYGHWR_HAL_ARM_AT91SAM7S
  CYGHWR_HAL_ARM_AT91SAM7S_at91sam7s32
  CYGHWR_HAL_ARM_AT91SAM7X
  CYGHWR_HAL_ARM_AT91SAM7SE

Patch 3 separates these out into separate header files for M55800A, SAM7S,
SAM7SE, SAM7X and other ("default") processors, all within the AT91 variant
HAL. The relevant header file is specified by CYGBLD_HAL_AT91_PIO_LAYOUT_H.

Patch 3 paves the way for the introduction of further PIO layout header files
for the AT91SAM9 processors. Evgeniy's port to AT91SAM9263 includes a PIO
layout header file dedicated to this processor (AT91SAM9263) and this is also
located within the AT91 variant HAL.

I don't think there can be any argument that the historical approach of adding
more and more preprocessor blocks to the AT91 var_io.h is not scalable. So the
issues are:

a) Is the separation of PIO layout definitions into separate header files
implemented at the correct level in this case (processor level)?

b) Does it make sense to separate the PIO layout definitions from other I/O
definitions (if any) in this way?

c) For the existing ports, would it be preferable to place the PIO layout
definitions in the processor HAL rather than in the AT91 variant HAL? This
would avoid the need to give each PIO layout header file a unique name. We need
to weigh up the risk of breaking platform ports we cannot readily test.

d) For new ports (including AT91SAM9 family), would it be preferable to place
the PIO layout definitions in the processor HAL rather than in the AT91 variant
HAL? I definitely think so.

Comments?

Any other issues relating specifically to patch 3?

-- 
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-22 14:14 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 [this message]
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=20110322141355.653CC2F78008@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).