RE: DiskOnChip in h6300 device

Thanks for the reply,  I had made all of these changes and that how I got 
the MDOC+ to return the ID but the reset of the information was wron at less 
the size of flash chip.

Anyway I had loook at mtd malling list and I found post which suggest 
somebody adding MDOC + 32M/64M to the new driver.

http://lists.infradead.org/pipermail/linux-mtd/2005-March/012214.html

Thanks again


> From: Torbjörn Jansson 
> <torbjorn.jansson-uX2xELSR4yiPucsbkbhDUcugMpMbD5Xr@xxxxxxxxxxxxxxxx>
> To: "'Husam Senussi'" 
> <husamsenussi-PkbjNfxxIARBDgjK7y7TUQ@xxxxxxxxxxxxxxxx>,<kernel-discuss-CN5wO63fgwogsBAKwltoeQ@xxxxxxxxxxxxxxxx>
> Subject: RE: DiskOnChip in h6300 device
> Date: Thu, 22 Dec 2005 23:18:46 +0100
>
> Husam Senussi <mailto:husamsenussi-PkbjNfxxIARBDgjK7y7TUQ@xxxxxxxxxxxxxxxx> 
> wrote:
> > I had look at the new driver 32M/64M is not supported, but
> > from what I
> > understand from you reply in h4100 mailling list that you manage to
> > get the old driver to work by making changes to one of the header
> > files.
> >
> > Do you remeber which !!!
> >
> > Thanks
>
> This was with the old driver and i still had problems.
> But, the thing i changed was in include/linux/mtd/doc2000.h
>
> In that file there is a few defines for ReadDOC and WriteDOC i just
> commented out the first two cases of those and kept the last one with readb
> and writeb.
>
> I remeber there was something odd going on tho, the module wasn't always
> loading and i think i had to load docprobe too.
> I think it had something to do with the probing of the chip, it wasn't
> always able to bring the chip out of reset mode.
>
> The doc chip have a tendency to enter reset mode, i had a test program to
> dump memory but this didn't return anything usefull since simply reading
> from the memory where the doc chip is makes it enter reset mode.
>
> I also thing i changed the address where it probed for the doc chip, i 
> think
> this was in docprobe or something like that.
>
>
> Anyway, this is all from memory and it was a long time since i experimented
> with it, so i may have remeberd some things wrong.