public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: ebiederman@lnxi.com (Eric W. Biederman)
To: Joshua Wise <joshua@joshuawise.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JEDEC probing redux
Date: 15 Nov 2003 01:08:24 -0700	[thread overview]
Message-ID: <m3ptfuoxzb.fsf@maxwell.lnxi.com> (raw)
In-Reply-To: <200311150109.39539.joshua@joshuawise.com>

Joshua Wise <joshua@joshuawise.com> writes:

> I'm thinking two things here: 1) I'm assuming that the unlock address verify 
> is just paranoia. Can I nuke that? (Will it break anyone's board?)

It will break things.  Some flash chips will ID but nothing else with
the wrong unlock address.  So without the test some boards will not
work.

> and 2) Is 
> there a better way to say that we should be left-shifting all the unlock 
> addresses over?

I am wondering if your map driver could handle that.  Either or
a solution like LART endian might be appropriate.

Handling flash chips that are connected up peculiarly seems to be
a recurring theme.  If this isn't something the map driver can't do
we may want to enhance that interface so it can handle more peculiar
cases in the future.

Eric

  parent reply	other threads:[~2003-11-15  8:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-15  6:09 JEDEC probing redux Joshua Wise
2003-11-15  6:29 ` Joshua Wise
2003-11-15  8:08 ` Eric W. Biederman [this message]
2003-11-15  8:35 ` David Woodhouse
2003-11-15 23:44   ` Joshua Wise
2003-11-16 19:05   ` Joshua Wise
2003-11-16 22:22 ` David Woodhouse
2003-11-17  1:17   ` Eric W. Biederman
2003-11-17  1:40     ` Joshua Wise
2003-11-17  8:23       ` David Woodhouse
2003-11-17  8:55     ` 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=m3ptfuoxzb.fsf@maxwell.lnxi.com \
    --to=ebiederman@lnxi.com \
    --cc=joshua@joshuawise.com \
    --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