HP Workstation zx2000 HP Graphics Administration Guide for HP-UX 11.X (IPF ver - Page 27

Device Device, Identifier, Driver, BusID

Get HP Workstation zx2000 PDF manuals and user guides View all HP Workstation zx2000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 27 highlights

configuring an X Server on HP-UX Device section The configuration file may have multiple Device sections. There must be at least one, for the video card being used. Device sections have the following format: Section "Device" Identifier Driver VendorName [BusID Option ... . . . "DeviceID" "driver" "Vname" "busid"] EndSection The Identifier entry specifies the unique name for this graphics device. It must match a DriverID in the active Screen section. The Driver entry specifies the name of the driver to use for this graphics device. When using the loadable server, the driver module "driver" is loaded for each active Device section. Supported drivers are: firegl23, radeon The keyword BusID specifies the bus location of the graphics card. For PCI/AGP cards, the busid string has the form PCI:bus:device:function. This field is optional in single-head configurations when using the primary graphics card. In multi-head configurations, or when using a secondary graphics card in a single-head configuration, this entry is mandatory. Its main purpose is to make an unambiguous connection between the Device section and the hardware it is representing. To find the bus ID of the graphics device you can use the command ioscan -f | grep gvid Beginning with the December, 2002 X Server patch, the brokering mechanism is supported and the Driver and BusID keywords are no longer supported in the "Device" section. They have been replaced by the Devicefile keyword. The Devicefile keyword identifies which character device provides the interface with the actual hardware. The device should be a /dev/gvid device (for example, /dev/gvid0, /dev/gvid1) Options are device dependant and should be searched for in device specific sections of this document. Graphics Administration Guide 4-15

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
Graphics Administration Guide
4–15
configuring an X Server on HP-UX
Device section
The configuration file may have multiple
Device
sections. There must be at least one, for the
video card being used. Device sections have the following format:
Section “Device”
Identifier
“DeviceID”
Driver
“driver”
VendorName
“Vname”
[BusID
“busid”]
Option …
. . .
EndSection
The
Identifier
entry specifies the unique name for this graphics device. It must match a DriverID
in the active Screen section.
The
Driver
entry specifies the name of the driver to use for this graphics device. When using the
loadable server, the driver module “driver” is loaded for each active Device section.
Supported drivers are:
firegl23, radeon
The keyword
BusID
specifies the bus location of the graphics card. For PCI/AGP cards, the
busid
string has the form
PCI:bus:device:function
. This field is optional in single-head
configurations when using the primary graphics card. In multi-head configurations, or when
using a secondary graphics card in a single-head configuration, this entry is mandatory. Its main
purpose is to make an unambiguous connection between the
Device
section and the hardware it is
representing.
To find the bus ID of the graphics device you can use the command
ioscan -f | grep gvid
Beginning with the December, 2002 X Server patch, the brokering mechanism is supported and
the Driver and BusID keywords are no longer supported in the “Device” section. They have been
replaced by the Devicefile keyword. The Devicefile keyword identifies which character device
provides the interface with the actual hardware. The device should be a
/dev/gvid device
(for example,
/dev/gvid0, /dev/gvid1
)
Options are device dependant and should be searched for in device specific sections of this
document.