Re: [PATCH 2/2] Added verbosity to 16550A serial driver.

2022-01-03 Thread Jan Kiszka via Xenomai
On 17.12.21 08:55, C Smith wrote: > There are development scenarios where different versions of a driver > are substituted. I can tell you some long stories when one day we meet > over a few beers... I can imagine those cases - but only when you patch the driver locally anyway. In that case, a

Re: [PATCH 1/1] Added verbosity to 16550A serial driver.

2022-01-03 Thread Jan Kiszka via Xenomai
On 17.12.21 09:03, Konstantin Smola via Xenomai wrote: > Added verbosity to 16550A serial driver. dmesg shows the driver version, > ports, irqs, baudbase. > Signed-off-by: Konstantin Smola > --- > kernel/drivers/serial/16550A.c | 16 ++-- > 1 file changed, 14 insertions(+), 2

Re: [PATCH 9/9] cobalt/debug: Detect vDSO via absence of vm_file

2022-01-03 Thread Jan Kiszka via Xenomai
On 03.01.22 17:34, Florian Bezdeka wrote: > On 13.10.21 13:55, Jan Kiszka via Xenomai wrote: >> From: Jan Kiszka >> >> VM_DENYWRITE was removed in 5.15, so we need a different criteria. >> Absence of a file-backing seems to be a good one. > > Bringing this one up, because we recently had a

[PATCH v2] cobalt/debug: Detect DSOs via presence of vm_file

2022-01-03 Thread Jan Kiszka via Xenomai
From: Jan Kiszka VM_DENYWRITE was removed in 5.15, so we need a different criteria. Presence of a file-backing seems to be a good one. Signed-off-by: Jan Kiszka --- Changes in v2: - fixed inverted logic - adjusted description kernel/cobalt/debug.c | 12 +--- 1 file changed, 5

Re: [PATCH 9/9] cobalt/debug: Detect vDSO via absence of vm_file

2022-01-03 Thread Florian Bezdeka via Xenomai
On 13.10.21 13:55, Jan Kiszka via Xenomai wrote: > From: Jan Kiszka > > VM_DENYWRITE was removed in 5.15, so we need a different criteria. > Absence of a file-backing seems to be a good one. Bringing this one up, because we recently had a "report" on the ML regarding VM_DENYWRITE. I scanned

Re: [PATCH 9/9] cobalt/debug: Detect vDSO via absence of vm_file

2022-01-03 Thread Jan Kiszka via Xenomai
On 03.01.22 19:04, Jan Kiszka via Xenomai wrote: > On 03.01.22 17:34, Florian Bezdeka wrote: >> On 13.10.21 13:55, Jan Kiszka via Xenomai wrote: >>> From: Jan Kiszka >>> >>> VM_DENYWRITE was removed in 5.15, so we need a different criteria. >>> Absence of a file-backing seems to be a good one. >>

Re: [PATCH v5 1/8] drivers/can: add corectl to retrieve configuration

2022-01-03 Thread Jan Kiszka via Xenomai
On 19.12.21 10:38, Dario Binacchi wrote: > Signed-off-by: Dario Binacchi > > --- > > Changes in v5: > - Add the patch to the series. > > include/cobalt/uapi/corectl.h | 2 ++ > kernel/drivers/can/Makefile | 4 +-- > kernel/drivers/can/corectl.c | 41

Re: x86 kernel Oops in Xeno-3.1/3.2

2022-01-03 Thread C Smith via Xenomai
On Sun, Jan 2, 2022 at 11:38 PM Jan Kiszka wrote: > > On 03.01.22 08:29, C Smith wrote: > > I have been getting kernel Oopses with x86 Xenomai 3.1 (and 3.2.1). > > In numerous tests, I can't keep a computer running for more than a day > > before the computer hard-locks (no kbd/mouse/ping).

Re: x86 kernel Oops in Xeno-3.1/3.2

2022-01-03 Thread Jan Kiszka via Xenomai
On 03.01.22 22:12, C Smith wrote: > On Sun, Jan 2, 2022 at 11:38 PM Jan Kiszka wrote: >> >> On 03.01.22 08:29, C Smith wrote: >>> I have been getting kernel Oopses with x86 Xenomai 3.1 (and 3.2.1). >>> In numerous tests, I can't keep a computer running for more than a day >>> before the computer

Re: x86 kernel Oops in Xeno-3.1/3.2

2022-01-03 Thread C Smith via Xenomai
On Mon, Jan 3, 2022 at 11:05 PM Jan Kiszka wrote: > > On 03.01.22 22:12, C Smith wrote: > > On Sun, Jan 2, 2022 at 11:38 PM Jan Kiszka wrote: > >> > >> On 03.01.22 08:29, C Smith wrote: > >>> I have been getting kernel Oopses with x86 Xenomai 3.1 (and 3.2.1). > >>> In numerous tests, I can't