public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Ben Dooks <ben-mtd@fluff.org>
To: Alexander Hoffmann <ahoffmann@sysgo.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Usage of MTD_UADDR_UNNECESSARY broken?
Date: Mon, 8 Nov 2004 12:06:24 +0000	[thread overview]
Message-ID: <20041108120624.GE13105@home.fluff.org> (raw)
In-Reply-To: <418F5E68.3010200@sysgo.de>

On Mon, Nov 08, 2004 at 12:54:16PM +0100, Alexander Hoffmann wrote:
> Hi everyone,
> 
> can anybody please explain me the exact difference between 
> MTD_UADDR_DONT_CARE and MTD_UADDR_UNNECESSARY .
> Because if I use MTD_UADDR_UNNECESSARY an not existing field in the 
> unlock_addrs array is beeing referenced
> (/drivers/mtd/chips/jedec_probe.c, function cfi_jedec_setup, line 1740):
> 
> /* Mask out address bits which are smaller than the device type */
> mask = ~(p_cfi->device_type-1);
> p_cfi->addr_unlock1 = unlock_addrs[uaddr].addr1 & mask;
> p_cfi->addr_unlock2 = unlock_addrs[uaddr].addr2 & mask;

hmm, thought this masking had been eliminated in later copies of
the mtd code?

-- 
Ben (ben@fluff.org, http://www.fluff.org/)

  'a smiley only costs 4 bytes'

  reply	other threads:[~2004-11-08 12:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-08 11:54 Usage of MTD_UADDR_UNNECESSARY broken? Alexander Hoffmann
2004-11-08 12:06 ` Ben Dooks [this message]
2004-11-08 12:55   ` Alexander Hoffmann
2004-11-08 19:50     ` Thayne Harbaugh
2004-11-12 15:15       ` Alexander Hoffmann
2004-11-12 15:55         ` Erwin Authried
2004-11-12 16:17           ` Alexander Hoffmann
2004-11-12 16:41             ` Erwin Authried
2004-11-18 10:50               ` Alexander Hoffmann
2004-11-18 14:44                 ` Thayne Harbaugh
2004-11-18 15:26                   ` Erwin Authried
2004-11-19 12:50                     ` Marius Groeger
2004-11-19 13:13                       ` Marius Groeger
2004-11-19 20:35                 ` Thayne Harbaugh
2004-11-08 18:30 ` Thayne Harbaugh

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=20041108120624.GE13105@home.fluff.org \
    --to=ben-mtd@fluff.org \
    --cc=ahoffmann@sysgo.de \
    --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