> > I need 115200, since that is what most of my development systems use > > for the serial console. Will the normal path, tty_get_baud_rate(tty), > > handle baud rates above 57600? > > Yes, cfsetospeed can be used up to 4Mbaud for example. > > > The hardware is also capable of "custom divisor" although you don't > > pass the divisor you need, but the actual baud rate. The moxa vendor > > driver had a custom IOCTL call for that, which i ripped out, but i've > > not yet looked how to implement it correctly. > > Isn't that the way you do it today with RQ_VENDOR_SET_BAUD? Yes, that part i know. I've only used custom divisors once, on an FTDI chipset. As far as i remember, you pass the divisor you want, not the baud rate. I've no idea what the base clock is, before the divider. I've also no idea how the device maps the baud rate to a divisor. So i would need to experiment with different values passed to RQ_VENDOR_SET_BAUD and see what the hardware actually does. For the moment i won't support it. > > So you are assuming the endpoints all have the same buffer size? At > > least for the one device i have, that is true. But is it guaranteed? > > What would happen if the event endpoint actually had a smaller size? > > No, remember that we're setting up all ports to use the first bulk-out > endpoint, so the fields can be retrieved from port0. Doh! I've been away from this code too long. Thanks Andrew -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
