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 1001070] BSP for Olimex LPC-L2294-8M
Date: Thu, 16 Dec 2010 12:29:00 -0000	[thread overview]
Message-ID: <20101216122848.F05F62F78007@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001070-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=1001070

Sergei Gavrikov <sergei.gavrikov@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Attachment #1010|0                           |1
        is obsolete|                            |
   Attachment #1011|0                           |1
        is obsolete|                            |
   Attachment #1025|0                           |1
        is obsolete|                            |
   Attachment #1029|0                           |1
        is obsolete|                            |
   Attachment #1057|0                           |1
        is obsolete|                            |

--- Comment #14 from Sergei Gavrikov <sergei.gavrikov@gmail.com> 2010-12-16 12:28:43 GMT ---
Created an attachment (id=1060)
 --> (http://bugs.ecos.sourceware.org/attachment.cgi?id=1060)
olpcl2294_20101216-cvs.patch

I could reproduce the issue using arm-elf-gcc 3.2.1 toolchain. Thanks for
report. Unfortunately, your "workaround" deprives flash support for other
targets from Olimex (non-olpcl2294). On my look there should be if/then/else
macro as only LPC-L2294-1M have 28F160 parts. New patch is attached (generated
against CVS).

-- 
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:[~2010-12-16 12:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-08 15:36 [Bug 1001070] New: " bugzilla-daemon
2010-11-09  9:53 ` [Bug 1001070] " bugzilla-daemon
2010-11-09 11:34 ` bugzilla-daemon
2010-11-09 11:43 ` bugzilla-daemon
2010-11-09 12:31 ` bugzilla-daemon
2010-11-22  9:02 ` bugzilla-daemon
2010-11-22  9:43 ` bugzilla-daemon
2010-11-22  9:46 ` bugzilla-daemon
2010-11-22 11:12 ` bugzilla-daemon
2010-11-22 11:33 ` bugzilla-daemon
2010-11-25 13:34 ` bugzilla-daemon
2010-11-25 13:38 ` bugzilla-daemon
2010-12-15  4:41 ` bugzilla-daemon
2010-12-15  6:43 ` bugzilla-daemon
2010-12-16 12:29 ` bugzilla-daemon [this message]
2010-12-16 12:34 ` bugzilla-daemon
2011-03-14 19:46 ` bugzilla-daemon
2011-11-08  1:15 ` bugzilla-daemon
2011-11-08  1:17 ` bugzilla-daemon
2011-11-08  1:17 ` bugzilla-daemon
2011-11-08 10:41 ` bugzilla-daemon
2011-11-08 17:08 ` 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=20101216122848.F05F62F78007@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).