On 2022-09-13 16:01, Greg Kroah-Hartman wrote:
On Tue, Sep 13, 2022 at 02:43:03PM +0200, Anders Blomdell wrote:
On 2022-09-13 14:30, Greg Kroah-Hartman wrote:
On Tue, Sep 13, 2022 at 02:16:39PM +0200, Anders Blomdell wrote:
I get incorrect baudrates, my oscilloscope gives:
Programmed Measured
2400 5208
4800 13150
9600 10410
19200 71420
38400 142000
57600 201600
115200 138800
I'm sorry, I have no context here at all, what does this pertain to?
Programmed baudrate and the measured (actual) baudrate
I really don't know what to do here, sorry. Are you saying a specific
commit has broken this? If so, did you test if you made a change it
fixed the issue?
Yes, commit 366f6c955d4d1a5125ffcd6875ead26a3c7a2a1c broke the one to one correspondence
between programmed and actual baudrate; reverting it (and 9c5c8aaed50bf3478073ab51b8b1f3f5327d3cfa
that builds on that patch) restores the expected functionality (i.e. you get the baudrate you ask for)
on 5.19.8.
What do you suggest happen here?
Either there is a bug in the code, or the chipset on my card (a Delock 2xRS232 card) is not a true oxford
chipset (the package and PCI id's says that they are).
Since the chip seems to be discontinued since 2014 (see https://www.mouser.com/PCN/PLX_Technology_2013_8.pdf),
I think a revert would not be uncalled for.
still confused,
So am I
greg k-h
/Anders
--
Anders Blomdell Email: anders.blomdell@xxxxxxxxxxxxxx
Department of Automatic Control
Lund University Phone: +46 46 222 4625
P.O. Box 118
SE-221 00 Lund, Sweden
