Lines Matching +full:target +full:- +full:module
24 3.1 Built-in:
25 3.2 Module:
55 major and minor numbers are associated with each vty-server. Directions
68 built into the kernel. If not, the default can be over-ridden by inserting
69 the driver as a module with insmod parameters.
71 3.1 Built-in:
72 -------------
77 Device Drivers --->
78 Character devices --->
83 3.2 Module:
84 -----------
87 driver as a kernel module::
89 Device Drivers --->
90 Character devices --->
95 - hvcs.ko
96 - hvcserver.ko
98 To insert the module with the default allocation execute the following
104 The hvcserver module contains architecture specific firmware calls and must
105 be inserted first, otherwise the hvcs module will not find some of the
121 In order to remove the driver module execute the following command::
125 The recommended method for installing hvcs as a module is to use depmod to
126 build a current modules.dep file in /lib/modules/`uname -r` and then
138 modprobe -r hvcs
148 |-- *other sysfs base dirs*
150 |-- class
151 | |-- *other classes of devices*
153 | `-- tty
154 | |-- *other tty devices*
156 | |-- hvcs0
157 | | `-- dev
158 | |-- hvcs1
159 | | `-- dev
160 | |-- hvcs2
161 | | `-- dev
162 | |-- hvcs3
163 | | `-- dev
165 | |-- *other tty devices*
167 |-- *other sysfs base dirs*
201 the hvcs module will result in an error message similar to the following::
206 is a vty-server device configured for that node.
212 interact with the device node entries using any standard tty-interactive
215 which requires the use of applications that provide bi-directional,
249 Hotplug add and remove of vty-server adapters affects which /dev/hvcs* node
250 is used to connect to each vty-server adapter. In order to determine which
251 vty-server adapter is associated with which /dev/hvcs* node a special sysfs
252 attribute has been added to each vty-server sysfs entry. This entry is
255 index attribute of vty-server adapter 30000004 shows the following::
260 This index of '2' means that in order to connect to vty-server adapter
264 system the /dev/hvcs* entry that interacts with a particular vty-server
272 unintended target the Power5 system firmware disables the fetching of data
273 and discards that data when a connection between a vty-server and a vty has
274 been severed. As an example, when a vty-server is immediately disconnected
286 manually terminated vty-server connections on tty close this would close
287 the vty-server and vty connection before the target vty has had a chance to
290 Additionally, disconnecting a vty-server and vty only on module removal or
291 adapter removal is impractical because other vty-servers in other
292 partitions may require the usage of the target vty at any time.
294 Due to this behavioral restriction disconnection of vty-servers from the
296 outlined below, on the other hand the initial vty-server connection to a
297 vty is established automatically by this driver. Manual vty-server
300 In order to terminate the connection between a vty-server and vty the
301 "vterm_state" sysfs attribute within each vty-server's sysfs entry is used.
303 vty-server adapter. A zero means that the vty-server is not connected to a
307 connection between the vty-server and target vty ONLY if the vterm_state
311 the vty-server connection status and disconnecting a vty-server connection::
321 All vty-server connections are automatically terminated when the device is
322 hotplug removed and when the module is removed.
327 Each vty-server has a sysfs entry in the /sys/devices/vio directory, which
334 By design, firmware notifies the hvcs driver of vty-server lifetimes and
338 firmware and update the partner info for all the vty-servers that this
348 Vty-server entries in this directory are a 32 bit partition unique unit
349 address that is created by firmware. An example vty-server sysfs entry
361 vty-server
368 /vdevice/vty-server@30000004
370 Each vty-server sysfs dir is provided with two read-only attributes that
382 U5112.428.103048A-V3-C0
383 U5112.428.103048A-V3-C2
384 U5112.428.103048A-V3-C3
385 U5112.428.103048A-V4-C0
386 U5112.428.103048A-V5-C0
389 numbering is only per-partition-unique so entries will frequently repeat.
392 composed of a system serial number followed by "-V*", where the '*' is the
393 target partition number, and "-C*", where the '*' is the slot of the
397 A vty-server can only be connected to a single vty at a time. The entry,
405 8A-V4-C0 > current_vty
407 Changing the current_vty when a vty-server is already connected to a vty
431 the next vty-server connection (which may be from another
434 ---------------------------------------------------------------------------
446 ---------------------------------------------------------------------------
462 ---------------------------------------------------------------------------
479 vty-server connection established. They need to free this using the method
481 to the target vty.
490 A: You probably haven't inserted the hvcs.ko module yet but the /dev/hvcs*
495 A: There is not a corresponding vty-server device that maps to an existing
498 ---------------------------------------------------------------------------
504 does? Maybe you haven't inserted the module (on systems with udev).
506 ---------------------------------------------------------------------------
515 ---------------------------------------------------------------------------
520 A: Yes. Of course this means that there must be more than one vty-server
523 ---------------------------------------------------------------------------
531 ---------------------------------------------------------------------------
533 Q: For some reason /dev/hvcs* doesn't map to the same vty-server adapter
536 A: Assignment of vty-server adapters to /dev/hvcs* entries is always done
538 this driver assignment of hotplug added vty-servers may be in a different
539 order than how they would be exposed on module load. Rebooting or
540 reloading the module after dynamic addition may result in the /dev/hvcs*
541 and vty-server coupling changing if a vty-server adapter was added in a
542 slot between two other vty-server adapters. Refer to the section above
543 on how to determine which vty-server goes with which /dev/hvcs* node.
544 Hint; look at the sysfs "index" attribute for the vty-server.
546 ---------------------------------------------------------------------------
554 Super Admin must create an additional "serial server" for the target
555 partition with the HMC gui which will show up as /dev/hvc* when the target
559 current partition and points this at the target partition's newly created
563 Now a program on the target system can be configured to read or write to
568 ---------------------------------------------------------------------------
577 linuxppc-dev@lists.ozlabs.org