public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Josh Boyer <jdub@us.ibm.com>
To: David Vrabel <dvrabel@arcom.com>
Cc: linux-mtd list <linux-mtd@lists.infradead.org>
Subject: Re: [patch] Only probe for device combinations that fit in map's bankwidth.
Date: Thu, 16 Sep 2004 06:50:10 -0500	[thread overview]
Message-ID: <1095335409.23972.2.camel@weaponx.rchland.ibm.com> (raw)
In-Reply-To: <41496FA5.5010901@arcom.com>

On Thu, 2004-09-16 at 05:49, David Vrabel wrote:
> Hi,
> 
> Recent MTD changed how chip probing is done and it now probes for chips 
> of all bus widths.  On my board (IXP425 with 16-bit AMD AM29LV128 flash) 
> probing for 8-bit wide devices cannot work because 8-bit writes/reads to 
> 16-bit devices aren't allowed (they cause data aborts). So...
> 
> Make genprobe_new_chip() only probe for combinations that fit in the 
> map's bankwidth.

MTD CVS has this fixed already.  I noticed the same behavior right after
dwmw2 merged with Linus.  Can you try what's there and see if it fixes
your problem?

josh

      reply	other threads:[~2004-09-16 11:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-16 10:49 [patch] Only probe for device combinations that fit in map's bankwidth David Vrabel
2004-09-16 11:50 ` Josh Boyer [this message]

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=1095335409.23972.2.camel@weaponx.rchland.ibm.com \
    --to=jdub@us.ibm.com \
    --cc=dvrabel@arcom.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