[UPDATE] DOCBoot support for NFTL-based DOC2000
dan_brown at ieee.org
Thu Mar 31 21:13:05 EST 2005
Zeri Virgo wrote:
> > - How big is your firmware area? (I'm assuming you resized it using
> > the DOS-based tools)
> Well, I used dformat on a different chip as suggested, but that was with
> the unpatched kernel, so the chip probing failed (but didn't crash).
> I'm now using a fresh one - I didn't think I should _have_ to resize the
> firmware area first, should I? I'll try the patched kernel with a
> resized-firmware-area chip tomorrow....ZZZ
No, you're quite right. In fact, it's very useful for me to know that
the code crashes even when you don't have a resized firmware area.
Don't even bother trying it with a resized firmware tomorrow :)
> > - Did the diskonchip driver work for you without crashing before my
> > latest changes?
> Yes, I've been using 18.104.22.168 with the diskonchip driver compiled in -
> see first dmesg section below...
So is it correct to say that you've just switched from the diskonchip
driver which is distributed as part of 22.214.171.124, to the diskonchip
driver from the MTD CVS repository?
If so, then any of the changes between the MTD version in 126.96.36.199 and
the current CVS are potentially the problem, not just my latest change
The version of diskonchip.c in 188.8.131.52 is 1.45. I don't see anything
in the changes between then and now (1.50) that should cause the
behavior you're seeing, which means either the problem is in a different
file or I'm just not seeing it :)
I'll stare at it some more tomorrow. Anyone else (Thomas?) have any
ideas where to look?
> Sorry I haven't offered any real help on this!
> - Zeri
On the contrary, you're much better at providing the right information
than most people.
More information about the linux-mtd