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 1001839] New: Fix for wrong setup of flash memory parts for different Olimex LPC-2294 boards Date: Mon, 06 May 2013 05:14:00 -0000 [thread overview] Message-ID: <bug-1001839-777@http.bugs.ecos.sourceware.org/> (raw) Please do not reply to this email, use the link below. http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001839 Bug ID: 1001839 Summary: Fix for wrong setup of flash memory parts for different Olimex LPC-2294 boards Product: eCos Version: CVS Target: Other (please specify) Architecture/Host HostOS: Win XP/7 OS: Status: UNCONFIRMED Severity: major Priority: low Component: Patches and contributions Assignee: unassigned@bugs.ecos.sourceware.org Reporter: uwe_kindler@web.de CC: ecos-patches@ecos.sourceware.org Created attachment 2228 --> http://bugs.ecos.sourceware.org/attachment.cgi?id=2228&action=edit Patch for Olimex LPC-2294 boards that fixes flash configuration In the current flash driver for Olimex LPC-2294 boards, the wrong flash memory type was selected for certain boards (i.e. for Olimex LPC-E2294-1MB). The Olimex boards can have two flash configurations: TE28F160C3BD70 C3 INTEL FLASH or TE28F320C3BD70 C3 INTEL FLASH Only two boards (LPC-L2294-8MB and LPC-H2294) have the 4MB Intel 28F320C3 parts. This was wrong in the old implementation (I stumbeld across this issue wehn building Redboot for LPC-E2294-1MB). The attached patch fixes this issue and adds a table in the documentation, that shows the configurations more clearly. -- You are receiving this mail because: You are the assignee for the bug.
next reply other threads:[~2013-05-06 5:14 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-05-06 5:14 bugzilla-daemon [this message] 2013-05-06 20:08 ` [Bug 1001839] " 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-1001839-777@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).