From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4EF4A9A7.2070308@domain.hid> Date: Fri, 23 Dec 2011 11:17:43 -0500 From: Makarand Pradhan MIME-Version: 1.0 References: <56F449AE83D74177BAC5887692E0EF55@domain.hid> <4EF44DB9.9000609@domain.hid> <4EF49DA3.8070904@domain.hid> <4EF4A3E2.9030709@domain.hid> In-Reply-To: <4EF4A3E2.9030709@domain.hid> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-help] Interrupt numbers List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gilles Chanteperdrix Cc: "xenomai@xenomai.org" Thanks. On 23/12/11 10:53 AM, Gilles Chanteperdrix wrote: > On 12/23/2011 04:26 PM, Makarand Pradhan wrote: >> On 23/12/11 04:45 AM, Gilles Chanteperdrix wrote: >>> Xenomai uses the same interrupt numbers as linux. But rt_intr_create is >>> deprecated in user-space, you should instead write a driver using the >>> rtdm skin. The enable bit is handled by xenomai when you request the irq >>> at xenomai level. >>> >> Hi Gilles, >> >> We use rt_intr_create in our code. So I am trying to understand the >> reasons for it being deprecated. So far, I have not been able to see any >> comments in the code regarding the deprecation or anything in the git log. > Splitting your code between driver and application enforces a clean > separation between the two, which helps maintenance, so is good on the > long run. > >> Can you pl comment on the reasons for deprecating rt_intr_create? Will >> it be removed in the next release? > We never change ABI in a branch, so, all releases in the 2.6 branch are > guaranteed to support the same services as xenomai 2.6.0. > > But in xenomai 3.0, rt_intr_create will certainly no longer be available. -- ___________________________________________________________________________ NOTICE OF CONFIDENTIALITY: This e-mail and any attachments may contain confidential and privileged information. If you are not the intended recipient, please notify the sender immediately by return e-mail and delete this e-mail and any copies. Any dissemination or use of this information by a person other than the intended recipient is unauthorized and may be illegal. _____________________________________________________________________