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 1001429] LPC1766-STK "address 0x10008d9c of */redboot.elf section .bss is not within region ram"
Date: Wed, 21 Dec 2011 16:10:00 -0000	[thread overview]
Message-ID: <20111221161010.5DB392F78005@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001429-777@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=1001429

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

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

--- Comment #1 from Ilija Kocho <ilijak@siva.com.mk> 2011-12-21 16:10:07 GMT ---
LPC 1766 has small RAM resources. In addition, RAM being fragmented in two
blocks makes it even more difficult. You could try to decrease some memory
demand (buffers, etc) but I'm afraid that RAM is too low to run Redboot with
networking.

I hope this helps.
Ilija

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


  reply	other threads:[~2011-12-21 16:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-21 13:45 [Bug 1001429] New: " bugzilla-daemon
2011-12-21 16:10 ` bugzilla-daemon [this message]
2011-12-22  6:02 ` [Bug 1001429] " bugzilla-daemon
2011-12-22  7:45 ` bugzilla-daemon
  -- strict thread matches above, loose matches on Subject: below --
2011-12-21 13:45 [Bug 1001429] New: " bugzilla-daemon
2011-12-21 16:10 ` [Bug 1001429] " bugzilla-daemon
2011-12-22  6:02 ` bugzilla-daemon
2011-12-22  7:45 ` 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=20111221161010.5DB392F78005@mail.ecoscentric.com \
    --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).