Lines Matching refs:vty

52 major and minor numbers are associated with each vty-server.  Directions
203 is a vty-server device configured for that node.
246 Hotplug add and remove of vty-server adapters affects which /dev/hvcs* node
247 is used to connect to each vty-server adapter.  In order to determine which
248 vty-server adapter is associated with which /dev/hvcs* node a special sysfs
249 attribute has been added to each vty-server sysfs entry.  This entry is
252 index attribute of vty-server adapter 30000004 shows the following.
257 This index of '2' means that in order to connect to vty-server adapter
261 system the /dev/hvcs* entry that interacts with a particular vty-server
270 and discards that data when a connection between a vty-server and a vty has
271 been severed.  As an example, when a vty-server is immediately disconnected
272 from a vty following output of data to the vty the vty adapter may not have
283 manually terminated vty-server connections on tty close this would close
284 the vty-server and vty connection before the target vty has had a chance to
287 Additionally, disconnecting a vty-server and vty only on module removal or
288 adapter removal is impractical because other vty-servers in other
289 partitions may require the usage of the target vty at any time.
291 Due to this behavioral restriction disconnection of vty-servers from the
292 connected vty is a manual procedure using a write to a sysfs attribute
293 outlined below, on the other hand the initial vty-server connection to a
294 vty is established automatically by this driver.  Manual vty-server
297 In order to terminate the connection between a vty-server and vty the
298 "vterm_state" sysfs attribute within each vty-server's sysfs entry is used.
300 vty-server adapter.  A zero means that the vty-server is not connected to a
301 vty.  A one indicates that a connection is active.
304 connection between the vty-server and target vty ONLY if the vterm_state
308 the vty-server connection status and disconnecting a vty-server connection.
318 All vty-server connections are automatically terminated when the device is
324 Each vty-server has a sysfs entry in the /sys/devices/vio directory, which
331 By design, firmware notifies the hvcs driver of vty-server lifetimes and
332 partner vty removals but not the addition of partner vtys.  Since an HMC
335 firmware and update the partner info for all the vty-servers that this
346 address that is created by firmware.  An example vty-server sysfs entry
358 	vty-server
365 	/vdevice/vty-server@30000004
367 Each vty-server sysfs dir is provided with two read-only attributes that
368 provide lists of easily parsed partner vty data: "partner_vtys" and
391 adapter.  The first vty partner corresponds to the first clc item, the
392 second vty partner to the second clc item, etc.
394 A vty-server can only be connected to a single vty at a time.  The entry,
395 "current_vty" prints the clc of the currently selected partner vty when
404 Changing the current_vty when a vty-server is already connected to a vty
428 	the next vty-server connection (which may be from another
461 A: Some other Power5 console mechanism has a connection to the vty and
473 vty-server connection established.  They need to free this using the method
475 to the target vty.
489 A: There is not a corresponding vty-server device that maps to an existing
511 A: Yes.  Of course this means that there must be more than one vty-server
512 configured for this partition and each must point to a disconnected vty.
522 Q: For some reason /dev/hvcs* doesn't map to the same vty-server adapter
525 A: Assignment of vty-server adapters to /dev/hvcs* entries is always done
527 this driver assignment of hotplug added vty-servers may be in a different
530 and vty-server coupling changing if a vty-server adapter was added in a
531 slot between two other vty-server adapters.  Refer to the section above
532 on how to determine which vty-server goes with which /dev/hvcs* node.
533 Hint; look at the sysfs "index" attribute for the vty-server.