I'm not familiar with the chaining of shared interrupts in the RTDM
architecture. I think the EOI should somehow be done in the very last
invocation of rt_16550_interrupt() by the last peripheral needing service.
I read this from an old interrupt handler:
(assuming IBM PC (Intel) architecture)
On 2018-05-20 09:43, C Smith wrote:
> An update:
> In the modprobe, I tried putting first the two ports which share IRQ 5:
> modprobe xeno_16550A io=0x02f8,0x2e8,0x3f8 irq=5,5,4
BTW, the x86 platform UARTs use IRQ4 (port 1 and 3) and IRQ3 (port 2 and 4).
Jan
--
Siemens AG, Corporate
This is highly likely, I'm not sure when this driver was last tested.
Are you able to put a patch together? Has anyone else sense similar
behaviour?
-Greg
On Tue, May 22, 2018 at 2:31 PM, C Smith wrote:
> I think I may have found a bug in the rtl_16550A driver when
I think I may have found a bug in the rtl_16550A driver when using shared
interrupts. (I am on Xenomai 2.6.5. Kernel 3.18.20.)
I think the interrupt handler is not sending an EOI to the lower (ISA 8259)
interrupt controller, though it certainly is doing the right thing for
higher IRQs above 16.
On 05/22/2018 07:06 AM, Dmitriy Cherkasov wrote:
> On 05/20/2018 08:07 AM, Philippe Gerum wrote:
>> On 05/18/2018 06:24 PM, Singh, Raman wrote:
>>> Environment: ARM Cortex-A53 quad-core processor (ARM 64-bit) on a
>>> Zynq Ultrascale+ ZCU102 dev board, Xenomai 3 next branch from May
>>> 14, 2018
On 05/18/2018 12:00 AM, Jan Kiszka wrote:
> On 2018-05-17 04:13, Dmitriy Cherkasov wrote:
>> On Wed, May 16, 2018, at 11:13 AM, Auel, Kendall wrote:
>>> I'm trying to build a xenomai-enabled kernel for an arm64 (quad A53
>>> cores). Something is not configured correctly, but I haven't been able
Update:
I installed a Moxa 4 port PCI serial card, which has a shared interrupt for
all 4 ports.
I did this:
modprobe xeno_16550A io=0xd040,0xd048,0xd050,0xd058 irq=17,17,17,17
baud_base=921600,921600,921600,921600
This worked fine, I was able to communicate bidirectionally on all four
ports in