All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: krishna m <krishnamurthyjs@domain.hid>
Cc: jan.kiszka@domain.hid, xenomai@xenomai.org
Subject: Re: [Xenomai-core] MSI support in Xenomai
Date: Tue, 29 Mar 2011 15:47:54 +0200	[thread overview]
Message-ID: <4D91E30A.2070702@domain.hid> (raw)
In-Reply-To: <COL122-W63A38C16F12405076DCC54BDBD0@domain.hid>

krishna m wrote:
> Just wanted to add 3 more questions:
> 1. Which versions of Linux, Adeos patch and xenomai are tested for stable MSI functionality ? Please let me know.
> 2. I am using the Xenomai Version linux-2.6.37, xenomai-2.5.6 and adeos-ipipe-2.6.37-x86-2.9-00. Is this combination fine ?
> 3. I looked at the /proc/interrupts and with out xenomai loaded [i.e. default linux kernel] I see my card beaing assigned MSI-EDGE interrupt and with xenomai kernel i don't see the entry in the /proc/interrupts but in /proc/xenomai/irq i see this entry 
> IRQ           CPU0   
> 16:              0       test_drv
> 521:             0       [IPI]
> 524:        869467       [timer]
> 525:             0       [critical sync]
> 546:             0       [virtual]
>  
> Hi Jan and Chanteperdrix,
> Any thoughts or inputs on my updates of MSI not working ?

Ok. Since you are asking me directly I am going to answer:
my point of view is, as I already told you, that MSI are not supported,
so still from my point of view the answer to question 1 is: "none"

Question 2 is yes, it is fine, but since MSI is not supported, it is not
supposed to work.

Answer to question 3 is that /proc/interrupts shows the interrupts
registered with request_irq whereas /proc/xenomai/irq shows the
interrupts which have been registered by xnintr_init, which
rtdm_request_irq uses. So, this is not the same code, the two files do
not have the same layout.

The reason why I did not answer is that Jan probably has a different
point of view for question 1, so, I let him answer you. But as far as I
know, Jan asked you some questions, in answer to your last post, to
which you did not answer.

-- 
					    Gilles.


      reply	other threads:[~2011-03-29 13:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-16 13:20 [Xenomai-core] MSI support in Xenomai krishna m
2011-03-16 13:26 ` Gilles Chanteperdrix
2011-03-17  8:30   ` Jan Kiszka
2011-03-21 12:48     ` krishna m
2011-03-22 12:13       ` Jan Kiszka
2011-03-22 15:55         ` krishna m
2011-03-22 16:51           ` Jan Kiszka
2011-03-22 17:03             ` Gilles Chanteperdrix
2011-03-22 18:20               ` krishna m
2011-03-25 12:21                 ` krishna m
2011-03-29 13:07                   ` krishna m
2011-03-29 13:47                     ` Gilles Chanteperdrix [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D91E30A.2070702@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=jan.kiszka@domain.hid \
    --cc=krishnamurthyjs@domain.hid \
    --cc=xenomai@xenomai.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.