public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: unassigned@bugs.ecos.sourceware.org
Subject: [Bug 1001864] Data not relocated to RAM during ROMINT startup
Date: Wed, 12 Jun 2013 22:47:00 -0000	[thread overview]
Message-ID: <bug-1001864-777-IsLznwSuE8@http.bugs.ecos.sourceware.org/> (raw)
In-Reply-To: <bug-1001864-777@http.bugs.ecos.sourceware.org/>

Please do not reply to this email, use the link below.

http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001864

Ilija Kocho <ilijak@siva.com.mk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ilijak@siva.com.mk

--- Comment #1 from Ilija Kocho <ilijak@siva.com.mk> ---
Probably it would be enough to provide CYG_HAL_STARTUP_ROM macro:

 cdl_option CYGFOO {
    .....
    active_if { CYG_HAL_STARTUP == "ROMINT }
    define -file system.h CYG_HAL_STARTUP_ROM
    ....
  }

At least it works for bug Bug 1001623 (Attachment 1877)
I hope this helps

Ilija

-- 
You are receiving this mail because:
You are the assignee for the bug.


  reply	other threads:[~2013-06-12 22:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-12 20:12 [Bug 1001864] New: " bugzilla-daemon
2013-06-12 22:47 ` bugzilla-daemon [this message]
2014-10-03 15:03 ` [Bug 1001864] " bugzilla-daemon
2014-10-04 12:52 ` bugzilla-daemon
2014-10-05 10:20 ` bugzilla-daemon
2014-10-07 13:44 ` bugzilla-daemon
2014-10-07 16:54 ` bugzilla-daemon
  -- strict thread matches above, loose matches on Subject: below --
2013-06-12 20:12 [Bug 1001864] New: " bugzilla-daemon
2013-06-12 22:47 ` [Bug 1001864] " bugzilla-daemon
2014-10-03 15:03 ` bugzilla-daemon
2014-10-04 12:52 ` bugzilla-daemon
2014-10-07 13:44 ` bugzilla-daemon
2014-10-07 19:39 ` 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=bug-1001864-777-IsLznwSuE8@http.bugs.ecos.sourceware.org/ \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=unassigned@bugs.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).