Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

pci_create_slot(9) [centos man page]

PCI_CREATE_SLOT(9)						Hardware Interfaces						PCI_CREATE_SLOT(9)

pci_create_slot - create or increment refcount for physical PCI slot SYNOPSIS
struct pci_slot * pci_create_slot(struct pci_bus * parent, int slot_nr, const char * name, struct hotplug_slot * hotplug); ARGUMENTS
parent struct pci_bus of parent bridge slot_nr PCI_SLOT(pci_dev->devfn) or -1 for placeholder name user visible string presented in /sys/bus/pci/slots/<name> hotplug set if caller is hotplug driver, NULL otherwise DESCRIPTION
PCI slots have first class attributes such as address, speed, width, and a struct pci_slot is used to manage them. This interface will either return a new struct pci_slot to the caller, or if the pci_slot already exists, its refcount will be incremented. Slots are uniquely identified by a pci_bus, slot_nr tuple. There are known platforms with broken firmware that assign the same name to multiple slots. Workaround these broken platforms by renaming the slots on behalf of the caller. If firmware assigns name N to MULTIPLE SLOTS
The first slot is assigned N The second slot is assigned N-1 The third slot is assigned N-2 etc. PLACEHOLDER SLOTS
In most cases, pci_bus, slot_nr will be sufficient to uniquely identify a slot. There is one notable exception - pSeries (rpaphp), where the slot_nr cannot be determined until a device is actually inserted into the slot. In this scenario, the caller may pass -1 for slot_nr. The following semantics are imposed when the caller passes slot_nr == -1. First, we no longer check for an existing struct pci_slot, as there may be many slots with slot_nr of -1. The other change in semantics is user-visible, which is the 'address' parameter presented in sysfs will CONSIST SOLELY OF A DDDD
bb tuple, where dddd is the PCI domain of the struct pci_bus and bb is the bus number. In other words, the devfn of the 'placeholder' slot will not be displayed. COPYRIGHT
Kernel Hackers Manual 3.10 June 2014 PCI_CREATE_SLOT(9)

Check Out this Related Man Page

CHARSET(1)							Linux User's Manual							CHARSET(1)

charset - Set an ACM for use in one of the G0/G1 charset slots. SYNOPSIS
charset [-v] G0|G1 [cp437|iso01|vt100|user|<acm_name>] DESCRIPTION
The linux console has 2 slots for charsets, labeled G0 and G1. charset changes the slot in use by the current VT to either G0 or G1, and fills the slot either with one of the 3 predefined ACMs (cp437, iso01, vt100) or with a user-defined ACM. You can ask for the current user-defined ACM by specifying user, or ask a new ACM to be loaded from a file into the user slot, by specify- ing a filename. You will note that, although each VT has its own slot settings, there is only one user-defined ACM for all the VTs. That is, whereas you can have tty1 using G0=cp437 and G1=vt100, at the same time as tty2 using G0=iso01 and G1=iso02 (user-defined), you cannot have at the same time tty1 using iso02 and tty2 using iso03. This is a limitation of the linux kernel. Note that you can emulate such a setting using the filterm(1) utility, with your console in UTF8-mode, by telling filterm to translate screen output on-the-fly to UTF8. You'll find filterm(1) in the konwert(1) package, by Marcin Kowalczyk, which is available from OPTIONS
-v be verbose. charset will then print what it does as it does it. BUGS
charset cannot determine which of the 2 slots is in use at a given time, so you have to tell him which one you want, even if you don't want to change to the other one. This is a limitation of the console driver. SEE ALSO
consolechars(8), unicode_start(1), filterm(1). Console tools 10 Aug 1998 CHARSET(1)
Man Page