From: "Matthew Dharm" <mdharm@momenco.com>
To: "Edward A. Hildum" <ehildum@mail.arc.nasa.gov>
Cc: linux-mtd@lists.infradead.org
Subject: RE: DiskOnChip 2000 128Mb problem
Date: Fri, 9 May 2003 13:29:53 -0700 [thread overview]
Message-ID: <NEBBLJGMNKKEEMNLHGAIOEGGDAAA.mdharm@momenco.com> (raw)
In-Reply-To: <5.1.1.5.2.20030509131915.015142c0@mail.arc.nasa.gov>
Did the Linux drivers work for you?
Matt
--
Matthew D. Dharm Senior Software Designer
Momentum Computer Inc. 1815 Aston Ave. Suite 107
(760) 431-8663 X-115 Carlsbad, CA 92008-7310
Momentum Works For You www.momenco.com
> -----Original Message-----
> From: Edward A. Hildum [mailto:ehildum@mail.arc.nasa.gov]
> Sent: Friday, May 09, 2003 1:24 PM
> To: Matthew Dharm
> Cc: linux-mtd@lists.infradead.org
> Subject: RE: DiskOnChip 2000 128Mb problem
>
>
> I had a similar experience using a DOC 2000 TSOP 256M part.
> Its chip ID is
> 0x30, which is right for a Millenium part, even though it
> has a DOC 2000
> part number. The part also has an IPL which can be updated
> like Millenium
> parts.
>
> Ted Hildum
>
> At 09:58 AM 5/9/2003 -0700, you wrote:
> > > -----Original Message-----
> > > From: David Woodhouse [mailto:dwmw2@infradead.org]
> > > Sent: Friday, May 09, 2003 9:48 AM
> > > To: Matthew Dharm
> > > Cc: linux-mtd@lists.infradead.org
> > > Subject: RE: DiskOnChip 2000 128Mb problem
> > >
> > >
> > > On Fri, 2003-05-09 at 17:40, Matthew Dharm wrote:
> > > > Is it normal for a DoC 2000 to be detected as a Millenium?
> > >
> > > No, but it's not normal for its contents to be read back as
> > > 0x01 0x02
> > > 0x03 etc. either: )
> >
> >Okay, so we're all on the same page.
> >
> > > > I've already checked the bus width and timing.
> > >
> > > And it's definitely not set to 16-bit? -ECONFUSED.
> >
> >No kidding. I'm hoping the docs will have something
> useful, and I'm
> >about to pull out the bus analyizer.
> >
> >
> >Matt
> >
> >
> >______________________________________________________
> >Linux MTD discussion mailing list
> >http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
next prev parent reply other threads:[~2003-05-09 20:29 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 [this message]
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
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=NEBBLJGMNKKEEMNLHGAIOEGGDAAA.mdharm@momenco.com \
--to=mdharm@momenco.com \
--cc=ehildum@mail.arc.nasa.gov \
--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