PCI Device Drivers

PCI Device Drivers

Post by cr.. » Thu, 21 May 1998 04:00:00



Hello,

I am interested in developing an IEEE1394 (FireWire) PCI adapter device
driver. I was wondering if there are any sample source code of PCI adapter
device drivers available out there. I did look through the www.wrs.com web
site and didn't find anything. I would appreciate very much any hints on
where I could find some sample code.

Thanks in advance,

Craig Mathewson

System Programmer
Sederta Inc.
www.sederta.com

-<< Posted with Actif News --- http://www.actifnews.com >>-

 
 
 

PCI Device Drivers

Post by Frank » Sat, 23 May 1998 04:00:00




> Hello,

> I am interested in developing an IEEE1394 (FireWire) PCI adapter device
> driver. I was wondering if there are any sample source code of PCI
adapter
> device drivers available out there. I did look through the www.wrs.com
web
> site and didn't find anything. I would appreciate very much any hints on
> where I could find some sample code.

> Thanks in advance,

> Craig Mathewson

> System Programmer
> Sederta Inc.
> www.sederta.com

> -<< Posted with Actif News --- http://www.actifnews.com >>-

Hi Craig,

the main problem is to find the PnP resources ( base address, irq ...).
I'm using the pciIomapLib functions to get this informations.
Take a look in the pc486 BSP sysNetif.c . This module find the resouces
and enables the memory (base address +  size) in the MMU.
If You have this it's no difference to any other device (VMEbus, on
board...).
( Ok some little differences, read/write cache of the PCItoPCI bridge,
timing)

Mit freundlichen Gruessen / Best regards

Ulf Franke

================================
men mikro elektronik nuernberg
software development

Phone           +49/911-99335-67
Fax             +49/911-99335-95

WWW:            http://www.men.de
================================

 
 
 

1. some problems about pci device driver in vxworks.

hi,all.

I am a beginner of vxworks bsp and English, now I have succeed developping a
driver of pci device in x86 platform. such is the steps:
1, according to information such as vendor ID, I found the specific device.
2, get the memory and I/O base address and size by reading and writing the
registers in config space.
3, call the function named sysMmuMapAdd() and add this these base address
and size to MMU table.
4, enable the device.
so ,my driver works well and I can access the memory and PIO spaces easily
by using "d" command. so I wonder who configged the bars at first, is it the
bios? this is my first problem.

now I should do the same thing under mpc8265. however things differs, you
see, there is not a function with the name "sysMmuMapAdd", at the same time,
in syslib.c ,the global array sysPhysMemDesc[] doesnot support the dummy
struct for future entry. while there are several structs filled with macros
defined in config.c, so question 2: should I change the value of these
macros for MMU map? if yes, so what is the principle to modify the default
value?

the 3rd, after the value of macros changed, is it still necessary to write
driver such as in x86? if yes, the most necessary part is to enable the
device, right?

my last question: for mpc, a processor without bios, so the bar configing
must be accomplished in bsp, so which function does this?

thanks to all,

yours sincelery:
solo

2. FF15 zipfiles ?

3. PCI device driver

4. How to use TeXExec 2.6 - ConTeXt ?

5. writing PCI device drivers

6. cyrus imap imtest problem

7. PCI device driver

8. can't see software metering from remote mmc

9. job in Montreal (PCI device drivers)

10. PCI device driver implementation ?

11. need some tutorial for writing PCI device driver for QNX

12. PCI device driver