Re: [cobalt-developers] PCI issues with RAQ3

[Dennis <dennis@xxxxxxxxx>]

At 01:44 PM 2/18/00 -0800, you wrote:
>Dennis wrote:
>> 
>> We are trying to run our PCI serial cards in a RAQ3 PCI slot, but the
>> driver is failing. Its seems that the ioremap (which is used to map the
>> registers into memory) is returning a NULL. The register value looks
correct.
>> 
>> The driver is loaded as a module...is there any reason why this is
>> happening? Does cobalt not allow mapping after system initialization?
>
>Our kernel is 100% standard wrt ioremap.  What PCI device, and are you
>sure you are getting the value from the BAR correctly?
>

The "devices" are our Synchronous serial cards. The following problems exist:

1) With our card in the box, the eepro100 driver locks the system on probe
using the C5 kernel or the C3 kernel (the original kernel in the box). With
the rom kernel it doesnt.

2) with the ROM kernel an ioremap of our board's base[0] address returns a
NULL when loading the module. The address (e800) that we are trying to map
appears valid.

I've noticed that board modules (include eepro100.o)  compiled on PCs dont
load on cobalt machines without recompiling them so obviously there is
something different. I'm going to have to hack the eepro100 driver to see
why it hangs, but if you can fill me in on the bus issues it might help.

Our cards are installed in hundreds of linux systems worldwide and there
hasnt been one MB that they havent worked with. The hang occurs with no
driver for the board present, so nothing *should* be accessing the card.

dennis 
Emerging Technologies, Inc.
----------------------------------------------------------------------------
---------

http://www.etinc.com
ISA and PCI T1/T3/V35/HSSI Cards for FreeBSD and LINUX
Multiport T1 and HSSI/T3 UNIX-based Routers
Bandwidth Management Standalone Systems
Bandwidth Management software for LINUX and FreeBSD
DSL Frame Relay Bridging over T1 and T3