Re: [Xenomai-help] RTDM or native Xenomai API
Thank you very much Gilles for the explanations! I think I understand the overall picture better now. Thank you, Andrey. On 16 April 2012 01:52, Gilles Chanteperdrix gilles.chanteperd...@xenomai.org wrote: On 04/16/2012 01:47 AM, Gilles Chanteperdrix wrote: On 04/16/2012 12:53 AM, Andrey Nechypurenko wrote: Hi Gilles, Thank you very much for such low-latency reply! :-) RTDM is the API of choice for developing drivers for real-time applications using xenomai. Please correct me if I just misunderstand something here, but as I understand, RTDM is an abstraction layer with concrete implementation using xenomai API. As stated in the referenced paper from Jan Kiszka, the original reason for introducing this layer was to achieve portability across different RT solutions for Linux. Since that time, a lot of considered RT solutions becomes irrelevant. In fact, I would say, there are only Xenomai and preempt_rt. If this assumption is true, then I can not see the advantages of the additional layer unless it is more then just an abstraction layer. Does RTDM API makes certain tasks easier/better compared to the similar native xenomai API? Just to give concrete example - what is the advantage of using rtdm_task_init() vs. rt_task_create or xnintr_init() vs. rtdm_irq_request()? The native API is designed to write applications, not drivers. The RTDM API is designed to write drivers. Using the native API in user-space is deprecated, the native API is made for user-space. Using the native API in *kernel-space* is deprecated, the native API is made for user-space. Writing applications in kernel-space is not what we recommend, as much as writing drivers in user-space. -- Gilles. ___ Xenomai-help mailing list Xenomai-help@gna.org https://mail.gna.org/listinfo/xenomai-help
Re: [Xenomai-help] RTDM or native Xenomai API
On 04/16/2012 08:55 AM, Andrey Nechypurenko wrote: Thank you very much Gilles for the explanations! I think I understand the overall picture better now. Thank you, Andrey. To summarize again: - the native API and posix API were made available in kernel-space at the beginning of the xenomai project as a mean to help porting applications from rtai and rtlinux to xenomai, they could also be used to write drivers, but it started to no longer make sense as soon as the RTDM API appeared; - they will both be gone in xenomai 3.0, only the RTDM API will be available in kernel-space. native and posix will still be available in user-space of course. -- Gilles. ___ Xenomai-help mailing list Xenomai-help@gna.org https://mail.gna.org/listinfo/xenomai-help
Re: [Xenomai-help] RTDM or native Xenomai API
- they will both be gone in xenomai 3.0, only the RTDM API will be available in kernel-space. I think you convinced me to start with RTDM API with the statement above :-) Thanks, Andrey. ___ Xenomai-help mailing list Xenomai-help@gna.org https://mail.gna.org/listinfo/xenomai-help
[Xenomai-help] Pandaboard, Xenomai and Wifi drivers
Hello, I have a pandaboard with Xenomai compilled with vanilla kernel source 2.6.38-8, but with this kernel tree there is no wifi support for panda. How and which kernel should I compile to remain a wifi usability? ___ Xenomai-help mailing list Xenomai-help@gna.org https://mail.gna.org/listinfo/xenomai-help
Re: [Xenomai-help] Pandaboard, Xenomai and Wifi drivers
On 04/16/2012 02:44 PM, Robert wrote: Hello, I have a pandaboard with Xenomai compilled with vanilla kernel source 2.6.38-8, but with this kernel tree there is no wifi support for panda. How and which kernel should I compile to remain a wifi usability? I do not think this list is the right place to ask this question, what we can tell you however is the most recent kernel supported by xenomai. You can try xenomai-2.6 from the git repository which supports linux 3.0. xenomai-2.6 will support linux 3.2 soon, but we are not there yet. -- Gilles. ___ Xenomai-help mailing list Xenomai-help@gna.org https://mail.gna.org/listinfo/xenomai-help
