From: David Woodhouse <dwmw2@infradead.org>
To: angainor@evo.evopolska.com
Cc: gerg@snapgear.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: MTD drivers for DoC Millenium Plus
Date: Wed, 11 Jun 2003 10:53:45 +0100 [thread overview]
Message-ID: <1055325225.2097.38.camel@passion.cambridge.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0306041127320.8546-100000@evo.evopolska.com>
On Wed, 2003-06-04 at 11:56, angainor@evo.evopolska.com wrote:
> First of all, docprobe successfuly identifies DOCMP,
> but total size of the DoC is only half of its actual
> size (64MiB chip is identified as 32MiB).
Hmmm. Sounds like a bug in the hardware driver. Greg?
> I have studied the "DiskOnChip 2000 128Mb problem"
> thread here on list and tried to change the
> MAX_CHIPS_MPLUS define to something else than 1.
> Well, this way I got an 128MiB disk, then a
> 256MiB one, and so on... :). way too many chips found.
> 1. inftlcore.c
>
> if (mtd->ecctype != MTD_ECC_RS_DiskOnChip)
> return;
>
> does indeed return. I guess it shouldn't...
Mea Culpa. I've fixed that in CVS now.
>
> INFTL: Media Header ->
> bootRecordID = BNAND
> NoOfBootImageBlocks = -1
> NoOfBinaryPartitions = 1
> NoOfBDTLPartitions = 1
> BlockMultiplerBits = 0
> FormatFlgs = 1
> OsakVersion = 0x30343135
> PercentUsed = 98
> PARTITION[0] ->
> virtualUnits = 10
> firstUnit = 0
> lastUnit = 0
> flags = 0x20000000
> spareUnits = 0
> INFTL: Media Header Parition 0 sanity check failed
> firstUnit 0 : lastUnit 0 > virtualUnits 0
>
> Basically, the start is ok and does reflect the
> reality. So what goes wrong afterwards?
Can you dump the contents of the media header using the DOS tools? How
big is the 'binary' partition? If you comment out that sanity check does
it actually work?
> 2. doc2000.h
>
> I found the following definition:
>
> #define DoC_Mplus_OutputControl 0x1002
>
> Shouldn't this be rather:
>
> #define DoC_Mplus_OutputControl 0x100c
>
> This is what I found in DOC_Millennium_Plus_DS_Rev1.7.pdf.
> 0x1002 is actually NOP. I don't think this will help me
> much though ;)
I haven't seen that documentation. Greg?
--
dwmw2
next prev parent reply other threads:[~2003-06-11 9:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-04 10:56 MTD drivers for DoC Millenium Plus angainor
2003-06-11 9:53 ` David Woodhouse [this message]
2003-06-11 11:18 ` angainor
2003-06-11 13:13 ` angainor
2003-06-11 13:28 ` David Woodhouse
2003-06-12 1:22 ` Greg Ungerer
2003-06-12 10:10 ` angainor
2003-06-12 14:42 ` Greg Ungerer
2003-06-20 5:48 ` Greg Ungerer
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=1055325225.2097.38.camel@passion.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=angainor@evo.evopolska.com \
--cc=gerg@snapgear.com \
/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