Some serial port drivers on Windows, notably usbser.sys, does not
care about DCB.fParity and only relies on DCB.Parity to contain
the correct value. In the case where we need to configure it for
no parity, the DCB.Parity field needs to be explicitly set to
NOPARITY.
The above statment has been checked using Wireshark and look at the
SET LINE CODING Request package (it contained ODDPARITY although
DCB.fParity=FALSE). The statement was also somewhat confirmed by
this post: https://stackoverflow.com/questions/36411498.
Change-Id: I2e2ab3da5da547e0420e3e61f91452ef0edeb755
Signed-off-by: Torbjörn SVENSSON <torbjorn.svensson@st.com>
1c4271836b