Romain Lenglet wrote:
Actually, Dmitry and I are discussing IRQ sharing between
real-time driver, not across the RT/non-RT border.
Sorry, I misunderstood.
The latter case almost always a no-go and should rather be
solved at hardware level by rearranging the IRQ usage (where
possible...).
Romain Lenglet wrote:
- A kernel option that causes Xenomai (or Adeos) to blatantly
malfunction or even crash is a freaking BUG, and should be
reported asap to the Xenomai-core list or the Adeos-main list.
IOW, there is no such thing as options allowed to crash your
box with Adeos/Xenomai
Romain Lenglet wrote:
...
Otherwise, my biggest source of problems is IRQ sharing between
realtime and non-realtime drivers: this predictably provokes
kernel panics. But Jan seems to be working on it.
Actually, Dmitry and I are discussing IRQ sharing between real-time
driver, not across
Actually, Dmitry and I are discussing IRQ sharing between
real-time driver, not across the RT/non-RT border.
Sorry, I misunderstood.
The latter case almost always a no-go and should rather be
solved at hardware level by rearranging the IRQ usage (where
possible...). The problem is that the
Romain Lenglet wrote:
Actually, Dmitry and I are discussing IRQ sharing between
real-time driver, not across the RT/non-RT border.
Sorry, I misunderstood.
The latter case almost always a no-go and should rather be
solved at hardware level by rearranging the IRQ usage (where
possible...).
CONFIG_PCI_MSI
This option messes with the oneshot timer (timer freezes).
(thanks to Gilles to have found this out)
Could you confirm that this issue still happens with
adeos-ipipe-2.6.13-1.0-05 or higher?
Ok. I have just checked adeos-ipipe-2.6.14-1.0-09 with
CONFIG_PCI_MSI enabled,
Romain Lenglet wrote:
- A kernel option that causes Xenomai (or Adeos) to blatantly
malfunction or even crash is a freaking BUG, and should be
reported asap to the Xenomai-core list or the Adeos-main list.
IOW, there is no such thing as options allowed to crash your
box with Adeos/Xenomai
