public inbox for ecos-patches@sourceware.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001881] New: Allow FIS cmd to handle multiple flash devices with different block alignments
Date: Wed, 17 Jul 2013 20:12:00 -0000	[thread overview]
Message-ID: <bug-1001881-104@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=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.

                 reply	other threads:[~2013-07-17 20:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-1001881-104@http.bugs.ecos.sourceware.org/ \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=ecos-patches@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).