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: Tue, 07 Oct 2014 13:44:00 -0000 [thread overview] Message-ID: <bug-1001864-777-WJNMxNY9yJ@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 Jonathan Larmour <jifl@ecoscentric.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jifl@ecoscentric.com --- Comment #5 from Jonathan Larmour <jifl@ecoscentric.com> --- Hi Ilija, The specific proposal in comment #1 to use CYG_HAL_STARTUP_ROM doesn't feel quite right to me: a) it would probably be better for this property to be accessible via CDL, not just source. A CDL interface presumably. b) It might make the code appear confusing in the case where you do need to distinguish "real" ROM startup from ROMINT/FLASH/whatever. But this is easily dealt with just by using a different name for the abstract startup type. It could be CYGINT_HAL_STARTUP_ROM or CYGINT_HAL_ROM_STARTUP, but perhaps it might better express what we're after here if we called it CYGINT_HAL_STANDALONE_STARTUP. But i've no strong preferences. Jifl -- You are receiving this mail because: You are the assignee for the bug.
next prev parent reply other threads:[~2014-10-07 13:44 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 ` [Bug 1001864] " bugzilla-daemon 2014-10-03 15:03 ` bugzilla-daemon 2014-10-04 12:52 ` bugzilla-daemon 2014-10-05 10:20 ` bugzilla-daemon 2014-10-07 13:44 ` bugzilla-daemon [this message] 2014-10-07 16:54 ` bugzilla-daemon 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-WJNMxNY9yJ@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: linkBe 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).