Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Nikita V. Youshchenko" <yoush@cs.msu.su>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: support for bit-reversed CFI cmd/query
Date: Tue, 22 Apr 2008 23:08:32 +0400	[thread overview]
Message-ID: <200804222308.39071@blacky.localdomain> (raw)
In-Reply-To: <1208890591.9212.654.camel@pmac.infradead.org>

[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]

> On Wed, 2008-02-27 at 23:48 +0300, Nikita V. Youshchenko wrote:
> >     mtd: support for bit-reversed CFI cmd/query
> >
> >     Some embedded boards have flash chips connected with reversed bit
> > order. Example for 16-bit width:
> >      chip D0 is bus D15
> >      chip D1 is bus D14
> >      ...
> >      chip D15 is bus D0
> >     It works perfectly for data access, however probing and issuing
> > CFI commands for such chips require bit reversing. This patch adds
> > support for this.
> >
> >     Signed-off-by: Nikita Youshchenko <yoush@cs.msu.su>
>
> Am I missing something, or did you only reverse the bits on 16-bit and
> 64-bit access, and not 8-bit or 32-bit?

Hmm... Looks so :(.
The board I work with has 16-bit flash, so I could not test others.

Btw, the vendor of the board confirmed that such a strange flash chip 
connection is 'an old hardware bug', however they decided to keep it in 
current and future revisions of the board 'for backward compatibility'.

Is it a good idea to support such strange cases in the official kernel?
If yes, I may send an updated patch.

Nikita

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-04-22 19:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-27 20:48 [PATCH] mtd: support for bit-reversed CFI cmd/query Nikita V. Youshchenko
2008-04-22 18:56 ` David Woodhouse
2008-04-22 19:08   ` Nikita V. Youshchenko [this message]
2008-04-22 19:23     ` David Woodhouse

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=200804222308.39071@blacky.localdomain \
    --to=yoush@cs.msu.su \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.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