in smi.c
It is done in the attached patch.
Now, the max. latency values on this new system are below 10 us.
Although, not tested very long.
Regards,
Ulrich Schwab
--
inmess GmbH
Frankfurter Str. 74
D - 64521 Gross-Gerau
Phone: +49 6152 97790
On Wednesday 09 August 2006 13:42, Dmitry Adamushko wrote:
So could anyone test this patch and let me know if it works?
Note : I haven't compiled it even as I don't have a proper environment. But
the changes are pretty simple so it should be ok.
I just did run the test program supplied by
On Thursday 10 August 2006 00:44, Jan Kiszka wrote:
Thanks for the patch, we just need some additional define of
PCI_DEVICE_ID_INTEL_ICH7_0 for kernel 2.4 compatibility. And if you
additionally provide a ChangeLog fragment, your patch would be perfect!
(I tend to forget the last part often
On Thursday 10 August 2006 10:27, Jan Kiszka wrote:
Ulrich Schwab wrote:
On Thursday 10 August 2006 00:44, Jan Kiszka wrote:
Thanks for the patch, we just need some additional define of
PCI_DEVICE_ID_INTEL_ICH7_0 for kernel 2.4 compatibility. And if you
additionally provide a ChangeLog
why not checking for irq origin like this:
int my_isr_handler (xnintr_t *irq)
{
if ( ! test_my_card_for_irq_origin )
return XN_ISR_NONE | XN_ISR_PROPAGATE;
... /* handling */
return XN_ISR_HANDLED;
}
this way XN_ISR_PROPAGATE is never returned in the not-shared case.
On Wed, Jul 16, 2008
On Tue, Jul 29, 2008 at 4:20 PM, Gilles Chanteperdrix
[EMAIL PROTECTED] wrote:
Gilles Chanteperdrix wrote:
Ulrich Schwab wrote:
why not checking for irq origin like this:
int my_isr_handler (xnintr_t *irq)
{
if ( ! test_my_card_for_irq_origin )
return XN_ISR_NONE | XN_ISR_PROPAGATE
On Wed, Jul 30, 2008 at 10:31 AM, Gilles Chanteperdrix
[EMAIL PROTECTED] wrote:
... you loose the RT response, as was (correctly) said in my first answer.
You are right, of course.
It was my error not to mention this in the original post.
For me this is just the solution to avoid the infinte