[EMAIL PROTECTED] said:
> Thanks for all the explanation, I think I now understand all the
> stuff your kernel thread is doing. Your solution sounds like a decent
> solution for the problem described. I have not looked at the socket
> driver code observe parse_events() usage, so I cannot say whether your
> problem description is accurate however :)
It's the socket drivers which _aren't_ in the kernel source which are most
likely to exhibit this problem. Anything in the kernel tree was probably
converted by Linus, and hence done right. As there are so few socket drivers
in his tree, the amount of code duplication wasn't immediately obvious
either.
The offenders are the multitude of PCMCIA and CF socket drivers for
embedded boards which are floating around. They aren't likely to get merged
into 2.4, unfortunately - but I think we should at least make this
available in order for them to work correctly.
--
dwmw2
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
