Jan Kiszka wrote:
R. Tai wrote:

Hi Jan, Thinus,

in general, I am planning to work on the e1000, but I need some more
time to understand all the concepts (especially under high load wich
currently and simply freezes my P4).


Then you might be interested in the kgdb-over-ipipe patch [1]. Works
fine for x86 on 2.6.16, so far tested with Xenomai, but I guess it
should work for RTAI as well. Don't know if RTAI keeps a valid "current"
pointer (current Linux task_struct) for any context, including kernel
RT-tasks. If not, you would need a similar patch like I posted for Xenomai.


There should be no special need in RTAI. RTAI can work with Linux schedulable objects only and everywhere, thus with a valid Linux "current" always. So it should be enough to use the scheduler option that does not make use of any RTAI proper kernel task and all of RTAI will be working in Linux context anyhow.
Users can switch the scheduler option without changing their programs.

Paolo.


Further, I will only need a subset of rtnet (TX), whilst RX is not
important to me. However, if I start with the e1000, I will [try to]
make it compliant to RTNet and define out things that I do not need, so
the community gets back some work.

Jan, is there any chance to get you into a chat or 15 min. voice
conversation about that topic (and maybe others)?


Feasible. I just fired up our #rtnet channel on freenode.net, I'm now
logged in, but I may show some latencies due to real-life interrupts.

Jan


[1] https://mail.gna.org/public/xenomai-core/2006-05/msg00138.html





-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
RTnet-users mailing list
RTnet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rtnet-users

Reply via email to