/illumos-gate/usr/src/contrib/bhyve/dev/usb/ |
H A D | usbdi.h | 425 struct usb_device *device; /* current device */ member
|
/illumos-gate/usr/src/data/hwdata/ |
H A D | pci.ids | 25 # device device_name <-- single tab 215 00b1 Remote Insight II board - PCI device 1863 1002 2000 Rage Fury MAXX AGP 4x (TMDS) (VGA device) 1864 1002 2001 Rage Fury MAXX AGP 4x (TMDS) (Extra device?!) 4252 …d, since all other ID numbers on this mainboard including the sub-device of this device has used s… 4458 ac12 Theater HD T507 (DVB-T) TV tuner/capture device 4883 04ed Internal Shared Memory (ISM) virtual PCI device 5130 # Server device 5787 0009 Remote Access Card III: BMC/SMIC device not present 5793 000d Embedded Remote Access: BMC/SMIC device [all …]
|
H A D | usb.ids | 20 # device device_name <-- single tab 108 2022 at90usbkey sample firmware (composite device) 863 b0c0 microSensys RFID device 864 b0c1 microSensys RFID device 865 b0c2 iID contactless RFID device 866 b0c3 iID contactless RFID device 867 b0c4 RFID device 868 b0c5 RFID device 2331 0079 IXI Ogo CT-17 handheld device 2356 00ce Generic PPC Flash device [all …]
|
/illumos-gate/usr/src/data/terminfo/ |
H A D | termcap.src | 8960 # On this device, cursor addressability isn't possible. The LCD expects: 12732 # attributes may or may not be supported by the device driver. 15550 # of the TTY device (which reports incorrectly on my hardware.) The 18585 # (S) MC parameters: 0 = start xfer to primary aux device, 1 = start xfer from 18586 # primary aux device, 2 = start xfer to secondary aux device, 3 = start xfer 18587 # from secondary aux device, 4 = stop relay to primary aux device, 5 = 18588 # start relay to primary aux device, 6 = stop relay to secondary aux device, 18589 # 7 = start relay to secondary aux device. 18691 # overstrike unless you also know whether the output device is in an "insert
|
H A D | terminfo.src | 10060 # On this device, cursor addressability isn't possible. The LCD expects: 14369 # attributes may or may not be supported by the device driver. 17499 # of the TTY device (which reports incorrectly on my hardware.) The 20803 # (S) MC parameters: 0 = start xfer to primary aux device, 1 = start xfer from 20804 # primary aux device, 2 = start xfer to secondary aux device, 3 = start xfer 20805 # from secondary aux device, 4 = stop relay to primary aux device, 5 = 20806 # start relay to primary aux device, 6 = stop relay to secondary aux device, 20807 # 7 = start relay to secondary aux device. 20909 # overstrike unless you also know whether the output device is in an "insert
|
/illumos-gate/usr/src/grub/grub-0.97/ |
H A D | AUTHORS | 59 network device completion.
|
H A D | ChangeLog | 182 * lib/device.c (get_drive_geometry): Use ST.ST_SIZE instead of 250 * lib/device.c (read_device_map): Likewise. 425 * lib/device.c (read_device_map): Change the max number of DRIVE 484 * lib/device.c: Mangle __FreeBSD_* macro usage to support 655 * lib/device.c (get_drive_geometry): Set GEOM->SECTOR_SIZE to 676 device names. 677 * lib/device.c (get_ataraid_disk_name) [__linux__]: New 687 * lib/device.c (get_drive_geometry): Do not open the same device 761 * lib/device.c [__linux__] (MAJOR): Support 32 bit and 64 bit 794 * lib/device.c (read_device_map) (sho_warning): New internal [all …]
|
H A D | INSTALL | 246 Simulate the slowness of a serial device in the grub shell. This
|
H A D | NEWS | 42 * Add support for an install device in GRUB's notation with no 128 this option is specified, probe a device map, even if it already 189 simulate the speed of a serial device on a psuedo terminal. 254 * The grub shell loads the BIOS drive mapping information from a device 279 Most of the device drivers are stolen from it, so we now have many 287 network device and get IP addresses from a network. 308 * The command "device" assigns a BIOS drive to an arbitrary filename in 400 * Changed device strings used in filesystem code to more logical
|
H A D | TODO | 56 modify the function `convert' so that it can translate a native device
|
H A D | configure | 909 simulate the slowness of a serial device
|
H A D | configure.ac | 543 dnl Simulation of the slowness of a serial device. 546 simulate the slowness of a serial device])
|
/illumos-gate/usr/src/grub/grub-0.97/docs/ |
H A D | grub.info | 250 Access data on any installed device 253 device. 339 The device syntax used in GRUB is a wee bit different from what you may 347 First of all, GRUB requires that the device name be enclosed with 378 need to use the device specification in a command, like `root (fd0)' or 475 The device file name may be different. Consult the manual for your 501 Command-line interface::). First, set the GRUB's "root device"(1) 515 Once you've set the root device correctly, run the command `setup' 538 (1) Note that GRUB's root device doesn't necessarily mean your OS's 553 file called the "device map", which you must fix if it is wrong. *Note [all …]
|
H A D | grub.info-1 | 249 Access data on any installed device 252 device. 338 The device syntax used in GRUB is a wee bit different from what you 346 First of all, GRUB requires that the device name be enclosed with 377 need to use the device specification in a command, like `root (fd0)' or 474 The device file name may be different. Consult the manual for your 500 Command-line interface::). First, set the GRUB's "root device"(1) 514 Once you've set the root device correctly, run the command `setup' 537 (1) Note that GRUB's root device doesn't necessarily mean your OS's 552 file called the "device map", which you must fix if it is wrong. *Note [all …]
|
H A D | grub.info-2 | 328 device is equivalent to which OS device. Normally, that will be clear if 329 you see the files in a device or use the command `find' (*note find::). 343 The device syntax is like this: 392 in the first partition of the first hard disk. If you omit the device 393 name in an absolute file name, GRUB uses GRUB's "root device" 394 implicitly. So if you set the root device to, say, `(hd1,0)' by the 415 does not contain a device name, then GRUB uses GRUB's "root device". So 416 `(hd0,1)+1' is the same as `+1' when the root device is `(hd0,1)'. 709 * bootp:: Initialize a network device via BOOTP 711 * device:: Specify a file as a drive [all …]
|
H A D | grub.info-3 | 57 writes the completed Stage 1 to the first block of the device 161 Set the active partition on the root disk to GRUB's root device. 263 - Command: root device [hdbias] 264 Set the current "root device" to the device DEVICE, then attempt 283 - Command: rootnoverify device [hdbias] 286 the disk that GRUB can read, but setting the correct root device 334 backend and installs GRUB into the device INSTALL_DEVICE. If 336 Images::) in the device IMAGE_DEVICE, otherwise use the current 337 "root device", which can be set by the command `root'. If 526 11 : Unrecognized device string [all …]
|
H A D | grub.info-4 | 186 * device: device.
|
H A D | grub.texi | 302 @item Access data on any installed device 304 by the BIOS, independent of the setting of the root device. 377 The device syntax used in GRUB is a wee bit different from what you may 387 First of all, GRUB requires that the device name be enclosed with 426 need to use the device specification in a command, like @samp{root 527 The device file name may be different. Consult the manual for your OS. 551 device}@footnote{Note that GRUB's root device doesn't necessarily mean 570 Once you've set the root device correctly, run the command 604 @dfn{device map}, which you must fix if it is wrong. @xref{Device 613 argument can be either a device file (like @samp{/dev/hda}) or a [all …]
|
H A D | internals.texi | 73 Raw device buffer 196 The @dfn{drive} part of the root device. 199 The @dfn{partition} part of the root device.
|
H A D | multiboot.info | 631 valid, and indicates which BIOS disk device the boot loader loaded the 635 device, but is not required to. The `boot_device' field is laid out in 895 * BIOS device mapping techniques:: 900 File: multiboot.info, Node: Notes on PC, Next: BIOS device mapping techniques, Up: Examples 914 BIOS drive maps to which device driver in an operating system is 918 this problem, there are 2 BIOS device mapping techniques (*note BIOS 919 device mapping techniques::). 932 File: multiboot.info, Node: BIOS device mapping techniques, Next: Example OS code, Prev: Notes o… 934 4.2 BIOS device mapping techniques 957 …e: Data comparison technique, Next: I/O restriction technique, Up: BIOS device mapping techniques [all …]
|
H A D | multiboot.texi | 669 field is valid, and indicates which @sc{bios} disk device the boot 673 determining its own @dfn{root} device, but is not required to. The 964 * BIOS device mapping techniques:: 982 @sc{bios} drive maps to which device driver in an operating system is 986 this problem, there are 2 @sc{bios} device mapping techniques 987 (@pxref{BIOS device mapping techniques}). 1000 @node BIOS device mapping techniques 1001 @section BIOS device mapping techniques 1026 Before activating @emph{any} of the device drivers, gather enough data 1030 After activating the device drivers, compare data from the drives using [all …]
|
/illumos-gate/usr/src/grub/grub-0.97/grub/ |
H A D | asmstub.c | 238 assign_device_name (int drive, const char *device) in assign_device_name() argument 252 if (! device) in assign_device_name() 255 device_map[drive] = strdup (device); in assign_device_name() 1239 serial_set_device (const char *device) in serial_set_device() argument 1244 serial_device = strdup (device); in serial_set_device()
|
/illumos-gate/usr/src/grub/grub-0.97/lib/ |
H A D | Makefile.am | 6 libcommon_a_SOURCES = getopt.c getopt1.c getopt.h device.c device.h
|
H A D | Makefile.in | 57 device.$(OBJEXT) 184 libcommon_a_SOURCES = getopt.c getopt1.c getopt.h device.c device.h 232 @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/device.Po@am__quote@
|
H A D | Makefile.solaris | 15 LIBCOMMON_OBJS = device.o \ 25 SRC_FILES = Makefile.am Makefile.in device.c device.h \
|