public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-bugs@ecos.sourceware.org
Subject: [Bug 1001078] New: STM32 flash driver support for non-aligned source buffers.
Date: Sun, 21 Nov 2010 16:53:00 -0000 [thread overview]
Message-ID: <bug-1001078-13@http.bugs.ecos.sourceware.org/> (raw)
Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001078
Summary: STM32 flash driver support for non-aligned source
buffers.
Product: eCos
Version: CVS
Platform: stm32e_eval (ST STM3210E EVAL board)
OS/Version: Cortex-M
Status: UNCONFIRMED
Severity: enhancement
Priority: low
Component: Flash
AssignedTo: unassigned@bugs.ecos.sourceware.org
ReportedBy: chris@zynaptic.com
CC: ecos-bugs@ecos.sourceware.org
Class: Advice Request
Created an attachment (id=1024)
--> (http://bugs.ecos.sourceware.org/attachment.cgi?id=1024)
Patch to support non-aligned source buffers for STM32 flash.
The current CVS version of the STM32 flash driver requires the source buffer to
be 16-bit aligned for writes. This causes problems when attempting to program
the flash from data held in non-aligned buffers. I am currently using the
attached patch to work around this.
In addition the patched version checks that the length of the write data is an
integer number of flash words, rather than silently discarding the last byte
when an odd number of bytes is written.
--
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.
next reply other threads:[~2010-11-21 16:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-21 16:53 bugzilla-daemon [this message]
2010-11-21 21:50 ` [Bug 1001078] " bugzilla-daemon
2010-11-22 9:02 ` bugzilla-daemon
2010-11-23 10:33 ` bugzilla-daemon
2010-11-21 21:50 [Bug 1001078] New: " 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-1001078-13@http.bugs.ecos.sourceware.org/ \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=ecos-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).