Date: Tue, 14 Nov 2023 08:01:48 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 266990] FreeBSD can not drive 16950 chip correctly Message-ID: <bug-266990-227-czchOaemgL@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-266990-227@https.bugs.freebsd.org/bugzilla/> References: <bug-266990-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D266990 --- Comment #4 from Andrey Korobkov <alster@vinterdalen.se> --- In 14.0-RELEASE it still works well, but new message appeared: "ns8250: UART FCR is broken". What does it mean? # dmesg.boot puc0: <Moxa Technologies, Smartio CP-104EL-A/PCIe> port 0x1000-0x103f,0x1040-0x104f mem 0xba000000-0xba000fff irq 27 at device 0.0 = on p ci7 ns8250: UART FCR is broken ns8250: UART FCR is broken uart2: <16950 or compatible> at port 1 on puc0 ns8250: UART FCR is broken ns8250: UART FCR is broken uart3: <16950 or compatible> at port 2 on puc0 ns8250: UART FCR is broken ns8250: UART FCR is broken uart4: <16950 or compatible> at port 3 on puc0 ns8250: UART FCR is broken ns8250: UART FCR is broken uart5: <16950 or compatible> at port 4 on puc0 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-266990-227-czchOaemgL>