Hi Hugh,
Thanks a lot for getting back to me so quickly.

We first tried the PCI server from the BSP for mpc8548e and struggled
with it for quite a while, but unfortunately failed to get it work
confidently. In additional to that, our FPGA applications code (created
by a tool) take physically addresses and then map them to user space
addresses to use. I have to make many changes in the PCI sever to cope
with our applications. At last we decided to use our own PCI driver as
we don't know the QNX 82537L driver depends on the QNX PCI server.  To
run the PCI sever on top of our driver could make things really mess I
think.

We have a fairly static and simple PCIe topology. Is it possible for the
82573L driver to get the 82573L BAR addresses from command line? We
could first run our PCIe driver and then run QNX 82573L driver with BAR
addresses for 82573L.

Is there any chance for us to have the QNX source for the 82573L driver
and see if it is possible to adapt it to our system? Intel has source
for Linux, but it is too much work to get it work in QNX.

Many thanks,
Song


-----Original Message-----
From: Hugh Brown [mailto:community-noreply@qnx.com] 
Sent: Thursday, December 03, 2009 2:03 PM
To: drivers-networking
Subject: RE: RE: Intel 82537L/devnp-i82544 driver questions

Hi Song,

The QNX PCI server should still work with your setup. If the PCI server
finds that base address registers are already programmed with valid
addresses, it leaves them alone. This also applies to IRQs.

The network driver needs to connect to the PCI server to get the base
address register and IRQ information. It will be quite a job to change
the driver to not work with the PCI server.

Hugh.

-----Original Message-----
From: Yingsheng Song [mailto:community-noreply@qnx.com] 
Sent: Thursday, December 03, 2009 8:32 AM
To: drivers-networking
Subject: Re: RE: Intel 82537L/devnp-i82544 driver questions

Hi Hugh,

I'm worried that the qnx driver for 82573L depends on QNX PCI server. At
the moment we didn't use the QNX PCI server for various reasons.
Basically we developed a simple generic PCI driver to enumerate all
devices in our system and then reconfigure the BARs and memory filter
windows for all devices statically.  Memory map is statically defined
for all devices at design time and all applications are aware of them.
Everything in our system is static, all devices and system memory to be
allocated to devices are known at design time.

My understand about the PCI server and the 82573L driver is as follows:
The PCI server will discover the 82573L device and configure the PCIe
related registers, especially assign system memory addresses for the
BARs of the 82573L device so that 82573L driver can access 82573L
internal memory/registers or external SPI flash through the BARs, is it
right?
Our PCIe driver could do all the above. If the above is true, how much
work would be needed to adapt the QNX 82573L driver to work with our PCI
driver? If the QNX 82573L driver dynamically scan the system to find the
82573L device and retrieve the BARs addresses after our PCI driver being
run, it should still work in our system. If the QNX 82573L driver tries
to use database created by the QNX PCI server, then it wouldn't work in
our case. Just some guess as I don't have 82573 driver source code.

We really appreciate your advice for us on how to proceed with this
issue. 

Song




_______________________________________________

Networking Drivers
http://community.qnx.com/sf/go/post43086




_______________________________________________

Networking Drivers
http://community.qnx.com/sf/go/post43092

------------------------------------------------------------------------------
The information in this e-mail (and any attachments) is confidential.  The 
contents may not be disclosed or used by anyone other than the addressee.  
If you are not the intended recipient, please...