Re: intel 440bx unshadow for doc2001

[roger <rogerxxmaillist@san.rr.com>]

On Mon, 2003-07-14 at 04:09, David Woodhouse wrote:
> On Sun, 2003-07-13 at 12:08, roger wrote:
> > If i'm correct, the unshadow code just needs to be written into MTD for
> > everything to work easily? 
> 
> Seems perfectly reasonable.
> 
> In theory, we ought to already have the appropriate unshadowing code in
> drivers/mtd/maps/l440gx.c; it's just that that driver will only then
> look for NOR flash chips rather than a DiskOnChip. Does it work if you
> load l440gx.c, watch it fail to find any flash chips, then unload it and
> load docprobe.c?

no. on 440BX.B683 motherboard, the l440gx.o module fails to even load. 
believe me, in my prior posts, you'll probably notice that i did
everything including pulling a rabbit out of my computer's rear port.

on my 440BX.tyan motherboard, I think the l440gx.o module will load but
it still fails to find the doc(?) (or vice versa with the motherboards)

> I'm working on a rewrite of the DiskOnChip drivers; I'll probably make
> it so that a separate driver can call a 'probe for DiskOnChip at address
> XXXX' function, then we can make that an option for l440gx and other
> such drivers rather than having hard-coded tables in the docprobe code
> itself.

I was scanning over the openbios/devbios/pcisets.c and looks like
there's only a couple lines of code that are required to unshadow the
bus so that the DOC (or motherboard's original bios chip) can become
visible to the mtd modules. The other motherboards (other chipsets)
appear to require more code to unshadow.

If i'm not mistaken, I won't be able to use the DOC with linux bios
until mtd can recognize the chip on bootup. (?)

well, code is there. it just needs to be integrated correct?

-- 

Roger
http://www.eskimo.com/~roger/index.html