From: David Woodhouse <dwmw2@infradead.org>
To: Clive Davies <cdavies@altera.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Intel protection register read
Date: Thu, 08 Nov 2001 12:10:10 +0000 [thread overview]
Message-ID: <6720.1005221410@redhat.com> (raw)
In-Reply-To: <01110811501001.09516@uk-proclin2>
cdavies@altera.com said:
> I sent the patch below to this list a few days ago but had no
> response. Has anyone had a chance to look at it? If its ok, could
> someone apply it?
Sorry. Thanks for retrying :)
> + unsigned char *ProtRegData; /* Protection register data bytes */
> struct flchip chips[0]; /* per-chip data structure for each chip */
The ProtRegData are per-chip, but you've only left space for one pointer.
What happens when people have arrays of multiple chips side-by-side and/or
consecutively mapped?
Also, isn't it possible to _write_ to the user areas of the chips?
Is this present in all versions of the Intel command sets, or do you need
to check the version number?
--
dwmw2
next prev parent reply other threads:[~2001-11-08 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-08 11:50 Intel protection register read Clive Davies
2001-11-08 12:10 ` David Woodhouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-08 14:41 Clive Davies
2001-11-08 15:02 ` 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=6720.1005221410@redhat.com \
--to=dwmw2@infradead.org \
--cc=cdavies@altera.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