Quote:>We are porting some software and hardware from Solaris 1 to Solaris 2.
>The hardware is a very simple vme16d16 card which does no interrupting
>or DMA. We have been opening /dev/vme16d16 and mmaping the appropriate
>addresses to talk to the registers. This has been very convenient, as
>we have not had to port a driver since we started on SunOS 3.5.
>Unfortunately, Solaris 2.X (SunOS 5.x) no longer supports the vme
>devices, in /dev or /devices. Is there a simple way to do this without
>writing a driver, or are we going to have to write one supporting open,
>close, and mmap?
Hum, I wonder. If I do a strings on /kernel/drv/vme I find:
vmemem
vme16d16
vme24d16
vme32d16
vme16d32
vme24d32
vme32d32
And because of driver.conf I wonder whether you can't simply write
those drivers in vme.conf or vmemem.conf.
I haven't got any Solaris 2.x machines with a vme bus at this moment,
but have you looked in /devices/vmemem?
(The device will only be created if you have a VME bus).
Not the following commen at the end of ucblinks.awk:
#
# XXX Bus device support yet to go in, so the following are TBD:
#
# sbus vme16d16 vme24d16 vme32d16 vme32d32
#
#
# XXX Other device support to be added as drivers are added:
#
# mcp oct mti
To me this reads as:
the generic drivers of the sbus and VME bus are supported, but we don't
make the links. Mcp oct and mit don't even have drivers yet.
For the sbus these links would probably be:
But I can't guess what the vme links could be, as I haven't got any of
those devices.
Casper
by