Hi all,
How PCI and VME and other bus arctecture are vary from one another? How can i get the configuration space address in PCI,VME and others.?I’m newbie in this.suggest some idea about wrting WDM and windriver based drivers.and also differnece between windriver and WDM?
helps are appreciated…
thanks
VME Bus?
Is anyone still using it?
http://en.wikipedia.org/wiki/VMEbus
Why would you want to know anything about this IO bus interface?
Generally hardware direct connect devices for windows platforms (i.e.
‘pcs’) are all PCI bus or PCI bus variants. You write a driver for
them using KMDF if you are a newbie.
Mark Roddy
On Fri, May 1, 2009 at 12:20 PM, wrote:
> VME
xxxxx@gmail.com wrote:
How PCI and VME and other bus arctecture are vary from one another?
This is a subject for a graduate-level course in college. It can’t
possibly be answered on a mailing list like this one. There are,
however, good books available for both of those buses.
How can i get the configuration space address in PCI,VME and others.?
You don’t. For PCI, the configuration space is owned and managed by the
PCI bus driver. A driver for a PCI device is given a structure at
startup time that tells it which memory, I/O port, and interrupt
resources it has been assigned.
VME doesn’t have a configuration space. Further, I don’t think Windows
currently runs on any VME systems. There were a few early NT 3.51
systems that did, but not any more.
I’m newbie in this.suggest some idea about wrting WDM and windriver based drivers.
You have a lot of reading to do. There are a couple of good books on
writing WDM drivers, but at this point you should be looking at WDF
instead. Are you doing this for a job? Remember that different kinds
of drivers need very different approaches. What kind of device will you
be aiming at?
and also differnece between windriver and WDM?
You can search the list archives for more, but the executive summary is
that WDM works and WinDriver doesn’t.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
----- Original Message -----
From: “Mark Roddy”
To: “Windows System Software Devs Interest List”
Sent: Friday, May 01, 2009 9:38 AM
Subject: Re: [ntdev] PCI Configuration Space
> VME Bus?
>
> Is anyone still using it?
>
> http://en.wikipedia.org/wiki/VMEbus
>
> Why would you want to know anything about this IO bus interface?
It’s still used a lot in the avionics field (where they are migrating now
to Ethernet).
Have a nice day
GV
>
> Generally hardware direct connect devices for windows platforms (i.e.
> ‘pcs’) are all PCI bus or PCI bus variants. You write a driver for
> them using KMDF if you are a newbie.
>
> Mark Roddy
>
>
>
> On Fri, May 1, 2009 at 12:20 PM, wrote:
>> VME
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
Indeed, VMEbus is still being used. I just did a project for a company
which makes products (boards, enclosures, etc.) for the industrial
control market. One of their boards is a x86 SBC for the VMEbus. It
contains a bridge chip which allows access from the PC to the VMEbus as
a master, and also allows you to set up regions of memory which can be
accessed as a slave by other VME masters. Apparently, some customers
prefer to write their applications on Windows, and this product lets
them do that. In many ways, it was one of the more unusual drivers I’ve
done.
Cheers,
–mkj
Mark Roddy wrote:
VME Bus?
Is anyone still using it?
http://en.wikipedia.org/wiki/VMEbus
Why would you want to know anything about this IO bus interface?
Generally hardware direct connect devices for windows platforms (i.e.
‘pcs’) are all PCI bus or PCI bus variants. You write a driver for
them using KMDF if you are a newbie.Mark Roddy
On Fri, May 1, 2009 at 12:20 PM, wrote:
>> VME
>
–
//
// Michael K. Jones
// Stone Hill Consulting, LLC
// http://www.stonehill.com
//