strange doc issues

[Lindstrom James-A19027]

Hi, I wrote this list about two months ago.  I was trying to get my embedded
Arm platform to support the diskonchip using the open source drivers, rather
than the mystery drivers left to me by a previous engineer (presumably
relying upon msys's binary-only drivers).  I wrote several emails (see the
archives) detailing how I had to change my erasesize from 0x4000 to 0x2000 
in order for the drivers to find the BNAND header.  I eventually paused 
and decided to order the pci eval board from msys so I could get at the
device from dos (under a known working configuration). 

I got the card and am now back at it.  What I found is that if I set the
Erasesize back to the normal setting, but set the MultiplierBits to 1 (which
is effectively the same as incrementing the phys_erase_shift.  When I did
that, I get a bit further.  Now I get to a point where the bad block table
is not found, but the partition table (there's just one partition , I made
it using dformat under dos) is correctly parsed.  But then inftl_format goes
nuts giving me corrupt block messages, trying to erase/format the suspect
blocks, but then deciding that the disk is write protected.

Does anyone have a feel for what might be going on?  First of all, it seems
fishy that I've had to arbitrarily add one to MultiplierBits to get the
BNAND header to be found.  But given that I did, perhaps I also need to muck
With the other shift values to get things working?  I tried adding deltas 
>From -3 to +3 to the bbt_erase_shift, but had no luck getting the bbt found.
And I still don't have a good feel for why I'm getting these corrupt block
messages (on a doc coming straight from dformat).

Can anyone offer advice?  I appreciate all the help you guys have had.
Thanks,

jbl