Hello, We are currently working with a development module which contains a FT232H chip and communicates via UART with another chip at a baud rate of exactly 115200. After the last patch of the ftdi_sio driver we saw that, theoretically, the FT232H should be fully supported by the driver. But, when we tried to use it, it didn't work. After digging further, we got to the 'get_ftdi_divisor()' function where the FT232H chip was placed on the same branch as FT2232H and FT4232H and, for a baud rate of 115200, 0xC068 was calculated as the divisor, when the correct value should have been 0x1A. The latter being confirmed by both the application note (AN120 from FTDI [1]) and the 'ftdi_set_baudrate()' in libftdi. On the other side, the 'ftdi_232bm_baud_to_divisor()', used for the FT232BM, FT2232C and FT232RL appears to also return the correct divisor for FT232H. Basically, we have 2 issues that aren't really clear: 1) Is the FT232H placed in the correct branch when calculating the divisor? 2) What't the explanation behind the algorithm which calculates the divisor in function "ftdi_2232h_baud_base_to_divisor()" ? [1] http://www.ftdichip.com/Support/Documents/AppNotes/AN_120_Aliasing_VCP_Baud_Rates.pdf Regards, Alex Stefan -- 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
