On 04.07.19 12:15, Jan Kiszka wrote:
On 04.07.19 10:57, Lange Norbert via Xenomai wrote:
Hello,
using the rt_igb driver with the recent ipipe/kernel will result in a broken
state
(I assume one cpu core is “stuck”).
This is a quote from Phillipe (note that I tested the plain upstream
revivis
On 04.07.19 10:57, Lange Norbert via Xenomai wrote:
Hello,
using the rt_igb driver with the recent ipipe/kernel will result in a broken
state
(I assume one cpu core is “stuck”).
This is a quote from Phillipe (note that I tested the plain upstream revivision
below)
This happens specifically w
On 21.06.19 11:49, Philippe Gerum via Xenomai wrote:
Currently, rtdm_dev_unregister() will hang soft until all references
on the dismantled device have been dropped, which in turn cannot
happen until all rtdm_fds on the device have been closed, which cannot
happen until all references on those fd
On 20.06.19 19:29, Philippe Gerum via Xenomai wrote:
Having the RTDM core return -EBADF to indicate that it does not manage
a file descriptor is a problem, as several drivers also raise this
error to notify userland about an aborted wait due to a connection
being dismantled (e.g. RTnet). In this
On 20.06.19 19:29, Philippe Gerum via Xenomai wrote:
RTDM already refcounts rtdm_fd descriptors to prevent unsafe module
unloading while connections are still active. We can remove the legacy
module refcounting done by the generic socket code, since every socket
is covered by an RTDM file descrip
756806
Thank You
-- next part --
A non-text attachment was scrubbed...
Name: config-4.19.tar.xz
Type: application/octet-stream
Size: 22800 bytes
Desc: config-4.19.tar.xz
URL:
<http://xenomai.org/pipermail/xenomai/attachments/20190704/d32a914d/attachment.obj>