From: "Matthew Dharm" <mdharm@momenco.com>
To: "David Woodhouse" <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: RE: DiskOnChip 2000 128Mb problem
Date: Tue, 13 May 2003 11:34:58 -0700 [thread overview]
Message-ID: <NEBBLJGMNKKEEMNLHGAICEHLDAAA.mdharm@momenco.com> (raw)
In-Reply-To: <1052811622.10222.42.camel@imladris.demon.co.uk>
> -----Original Message-----
> From: David Woodhouse [mailto:dwmw2@infradead.org]
> Sent: Tuesday, May 13, 2003 12:40 AM
> To: Matthew Dharm
> Cc: Edward A. Hildum; linux-mtd@lists.infradead.org
> Subject: RE: DiskOnChip 2000 128Mb problem
>
>
> On Tue, 2003-05-13 at 02:42, Matthew Dharm wrote:
> > Well, I found at least one part of the problem.
> >
> > The Linux driver doc2001.c assumes that addresses (in
> DoC_Address) are
> > 23 bits max. On some parts, the max is 31, so an extra
> write of the
> > address component is needed.
>
> Interesting. If we make this change, does it still work
> with the older
> units?
Doubtful. The doc2000 'integrated' code actually has a system for
marking certain parts as needed 3 or 4 bytes of address, depending on
the part ID. I can't use that code, since it can't ID my parts (and I
haven't figured out why).
Matt
next prev parent reply other threads:[~2003-05-13 18:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-07 20:37 DiskOnChip 2000 128Mb problem Matthew Dharm
2003-05-08 6:17 ` David Woodhouse
2003-05-08 18:04 ` Matthew Dharm
2003-05-09 14:25 ` David Woodhouse
2003-05-09 14:35 ` David Woodhouse
2003-05-09 16:40 ` Matthew Dharm
2003-05-09 16:48 ` David Woodhouse
2003-05-09 16:58 ` Matthew Dharm
2003-05-09 20:23 ` Edward A. Hildum
2003-05-09 20:29 ` Matthew Dharm
2003-05-12 20:42 ` Edward A. Hildum
2003-05-13 1:42 ` Matthew Dharm
2003-05-13 7:40 ` David Woodhouse
2003-05-13 8:03 ` Daniel Toussaint
2003-05-13 16:22 ` David Woodhouse
2003-05-13 18:34 ` Matthew Dharm [this message]
2003-05-13 8:22 ` David Woodhouse
2003-05-13 17:09 ` Edward A. Hildum
2003-05-31 13:08 ` David Woodhouse
2003-05-31 13:19 ` 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=NEBBLJGMNKKEEMNLHGAICEHLDAAA.mdharm@momenco.com \
--to=mdharm@momenco.com \
--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