* [Bug 1001881] New: Allow FIS cmd to handle multiple flash devices with different block alignments
@ 2013-07-17 20:12 bugzilla-daemon
0 siblings, 0 replies; only message in thread
From: bugzilla-daemon @ 2013-07-17 20:12 UTC (permalink / raw)
To: ecos-patches
Please do not reply to this email, use the link below.
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001881
Bug ID: 1001881
Summary: Allow FIS cmd to handle multiple flash devices with
different block alignments
Product: eCos
Version: unknown
Target: All
Architecture/Host Other
OS:
Status: UNCONFIRMED
Severity: enhancement
Priority: low
Component: Patches and contributions
Assignee: unassigned@bugs.ecos.sourceware.org
Reporter: sarcastic.mannequin@gmail.com
CC: ecos-patches@ecos.sourceware.org
Created attachment 2336
--> http://bugs.ecos.sourceware.org/attachment.cgi?id=2336&action=edit
Allow FIS cmd to handle multiple flash devices with different block alignments
This patch allows Redboot FIS command to manage multiple flash devices even
when the flash devices have different block sizes/alignments.
Note this is not about different block sizes in a single flash device, this is
about different block sizes in multiple flash devices.
Noticed this problem with Redboot on a board that has embedded flash in SoC and
also a SPI dataflash device. Most FIS operations were failing because it was
using alignment from embedded flash even on dataflash device.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2013-07-17 20:12 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-07-17 20:12 [Bug 1001881] New: Allow FIS cmd to handle multiple flash devices with different block alignments bugzilla-daemon
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).