[ Next-in-Thread ]  [ Next Message ] 

Maybe a very particular hardware fault 

Forum: PCMCIA Installation and Configuration Issues
Re: Sad: "Bad address mapping" on Sony N505VE (toby cabot)
Re: A strange problem (David Hinds)
Re: Sad: you're not kidding (toby cabot)
Date: 2000, Jun 20
From: David Hinds <dhinds@pcmcia.sourceforge.org> 

> I scanned my messages log and found that the bridge mapping used to be
> 0x68000000 when things were working. So I tried setting the cb_mem_base
> to 0x68000000 but then get "Bad bridge mapping at 0x680000dc!".

This smells like a hardware failure.  The PCMCIA drivers are writing
0x68000000 to a register, and it is reading back as 0x680000dc.  Maybe
Windows works because it only writes to this register and never relies
on reading it back.

Just for kicks, you could try editing modules/i82365.c, find the line
that says:

 pci_readl(s, PCI_BASE_ADDRESS_0, &s->cb_phys);

and add right after that:

 s->cb_phys &= ~0x0fff;

-- Dave

[ Next-in-Thread ]  [ Next Message ] 

Messages Inline: [ 0 ]  [ 1 ] 

Agree: looks like you're right

Re: Maybe a very particular hardware fault (David Hinds)
Date: 2000, Jun 21
From: toby cabot toby

Dave,

Great suggestion! When we meet the beer is on me.

By hard-wiring i82365.c I'm now back online. I went for the full-bore hardcoded memory address:

s->cb_phys = 0x68000000;

Thanks,
Toby

PS. I'm also seeing the dropped ethernet interrupts after a suspend/resume. I'm not a driver programmer but if you need someone to guinea pig some new code on a N505VE please give me a shout.
Maybe a very particular hardware fault

[ Add Message ]  to: "Maybe a very particular hardware fault"

[ Members ]  [ Subscribe ]  [ Admin Mode ] 
[ Show Frames ]  [ Help for HyperNews at pcmcia-cs.sourceforge.net 1.10 ]