Dear coreboot developers:
The problems with SIO devices were resolved:
I will give you a brief explanation of what I did after my previous mail just
for the record, thinking this might be useful for someone else in the future.
The problem was that ttyS0 from W83627DHG was not working properly
Dear All,
After following the recommendations from Rudolf and other people on this mail
list I was able to make the following to make my LPC SIO to work (with issues).
1.- Enable SERIRQ in CONTINUOUS_MODE
2.- Add SUPERIO_WINBOND_W83627DHG driver to the Konfig file.
3.- Add the SIO
Dear Rudolf/All,
Today I tried several things to try to make COM1 to work unsuccessfully.
In my last test today I crossed the COM configuration from:
COM1 (not working)COM2 (OK)
0x3f8, IRQ4 0x2f8, IRQ3
to:
0x3f8, IRQ3 0x2f8, IRQ4 (Both not
Thank you Rudolf for your advise,
I checked the interrupts in Linux and showed me that the interrupts were
already in EDGE mode but anyway I changed the interrupt mode in southcluster.c
from quiet to edge.
The default PNP configuration for the Winbond SIO was crashing Windows 7 and 10
and
Hi,
In general I would check ELCR (I/O port register 0x4d0) to check if it is
correctly programmed to EDGE/LEVEL (it should be edge)
Also, how the Linux is supposed to detect the I/O port irq? I think you need
some PNP device in ACPI to let linux infer the IRQ.
I would also try to disable the
Dear coreboot developers:
My system is Baytrail FSP E3845
2 LPC SIO WINBOND_W83627DHG and FINTEK_F81803 (disabled at this moment)
SERIRQ has been enabled.
I have the following issue in the W83627DHG SIO:
ttyS2 @ 0x3e8, irq 4 doesn't work. (changing IRQ 4 to 6 does not make any
difference)
6 matches
Mail list logo
