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: Thu, 19 May 2011 13:32:00 -0000	[thread overview]
Message-ID: <20110519133140.12DD615197C8@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 #32 from Ilija Kocho <ilijak@siva.com.mk> 2011-05-19 14:31:37 BST ---
(In reply to comment #31)
> (In reply to comment #30)
> 
> > However if larger re-organization of AT91 port is considered, I
> > would propose moving AT91 peripherals out of ARM devs subdirectories
> > (except for peripherals based on ARM IP, if any). Something like
> > this:
> > 
> > packages-+
> >          +-devs+
> >                +-serial+
> >                        +-AT91-+
> >                               +-current-+...
> 
> That's what makes the most sense to me, and it's the way all the other
> processor families are supported -- isn't it?

I couldn't tell. In general devs looks pretty much scattered to me. For example
there are many directories related to Freescale's controllers, I can imagine
some of them contain same devices. On the other hand are ARM directories that
contain devices that are not related to ARM (architecture or company) merely to
chips with ARM cores.

-- 
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-05-19 13:32 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 [this message]
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=20110519133140.12DD615197C8@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).