Lines Matching refs:dev

110 There is a maximum number of dev entries that can be specified on insmod.
154 	|       |   `-- dev
156 	|       |   `-- dev
158 	|       |   `-- dev
160 	|       |   `-- dev
167 "dev" entry in the hvcs directory:
169 	Pow5:/sys/class/tty/hvcs0/ # cat dev
172 	Pow5:/sys/class/tty/hvcs1/ # cat dev
175 	Pow5:/sys/class/tty/hvcs2/ # cat dev
178 	Pow5:/sys/class/tty/hvcs3/ # cat dev
181 The output from reading the "dev" attribute is the char device major and
186 Given the example output above, to manually create a /dev/hvcs* node entry
189 	mknod /dev/hvcs0 c 254 0
190 	mknod /dev/hvcs1 c 254 1
191 	mknod /dev/hvcs2 c 254 2
192 	mknod /dev/hvcs3 c 254 3
197 Attempting to connect an application to /dev/hvcs* prior to insertion of
200 	"/dev/hvcs*: No such device".
232 sure that once connected to a /dev/hvcs console that the console's $TERM
235 kermit to connect to /dev/hvcs0 when the console prompt becomes available
246 Hotplug add and remove of vty-server adapters affects which /dev/hvcs* node
248 vty-server adapter is associated with which /dev/hvcs* node a special sysfs
251 /dev/hvcs* entry to use to connect to that device.  For instance cating the
258 30000004 the user should interact with /dev/hvcs2.
261 system the /dev/hvcs* entry that interacts with a particular vty-server
418 	1. The creator of the /dev/hvcs* nodes has the ability to restrict
435 A: You can use "screen" to directly connect to the /dev/hvcs* device and
459 "Sorry, can't open connection: /dev/hvcs*"What is happening?
472 /dev/hvcs device but the vterm_state may reveal that they still have the
480 permissions to use the /dev/hvcs* device.
484 A: You probably haven't inserted the hvcs.ko module yet but the /dev/hvcs*
490 /dev/hvcs* entry.
496 A: The /dev/hvcs* entry you have specified doesn't exist where you said it
504 A: Yes granted that your are connected to the /dev/hvcs* device using
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
529 reloading the module after dynamic addition may result in the /dev/hvcs*
532 on how to determine which vty-server goes with which /dev/hvcs* node.
536 Q: Can I use /dev/hvcs* as a conduit to another partition and use a tty
540 for extra /dev/hvc* devices (where /dev/hvc0 is most likely the console).
543 partition with the HMC gui which will show up as /dev/hvc* when the target
549 additional /dev/hvcs* device.
552 /dev/hvc* and another program on the current partition can be configured to
553 read or write to /dev/hvcs*.  Now you have a tty conduit between two
563 linuxppc-dev@ozlabs.org