Adapt to the new device name for interface attachments.

share/man/man4/ugen.4

@@ -1,4 +1,4 @@
-.\" $NetBSD: ugen.4,v 1.34 2018/02/20 15:56:43 wiz Exp $
+.\" $NetBSD: ugen.4,v 1.35 2018/03/05 09:37:30 ws Exp $
 .\"
 .\" Copyright (c) 1999 The NetBSD Foundation, Inc.
 .\" All rights reserved.
@@ -35,7 +35,7 @@
 .Nd USB generic device support
 .Sh SYNOPSIS
 .Cd "ugen* at uhub? flags N"
-.Cd "ugen* at uhub? vendor V product P configuration C interface I flags 1"
+.Cd "ugenif* at uhub? vendor V product P configuration C interface I"
 .Sh DESCRIPTION
 The
 .Nm
@@ -66,16 +66,20 @@ The second form of attachment can be used to
 only one interface from some device for use by the
 .Nm
 driver.
-Be sure to include
-.Dq flags 1
-on the attachment.
+Most likely you want to explicitily specify at least vendor,
+product and interface with this form,
+as otherwise the
+.Nm
+driver would capture all of your
+.Nm usb
+devices.
 .Em NOTE :
 You have to be extremely careful,
-when using this,
+when using this form,
 as the attached
 .Nm
 driver has access to all of the device
-and can easily interfere with the driver used for
+and can easily interfere with the driver(s) used for
 the other interface(s).
 .Pp
 As an example of this second form of attachment there are
@@ -84,16 +88,15 @@ where one interface is used for JTAG debugging
 and the other is used as a serial interface.
 In this case you want to attach the
 .Nm
-driver to interface 0
-while using
+driver to interface 0 of this particular board identified by
+.Cd vendor
+and
+.Cd product
+while letting
 .Xr uftdi 4
 together with
 .Xr ucom 4
-at interface 1 of this particular board
-identified by
-.Cd vendor
-and
-.Cd product .
+to attach at interface 1.
 .Pp
 There can be up to 127 USB devices connected to a USB bus.
 Each USB device can have up to 16 endpoints.