<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">We have a large-ish codebase of real-time components based on Linux with RTAI. I am attempting to add EtherCAT support on various hardware including the Beckhoff CX5020/30/40. This hardware contains the Intel I210 (82575), which is supported
by the igb.ko driver under Linux. This driver seems to be related to the e1000e driver, but etherlab currently doesn’t have a native replacement for the igb driver.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">So I’m looking for suggestions on how to proceed:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Figure out how to modify the igb driver:<o:p></o:p></p>
<p class="MsoNormal">Most obvious, but I have no familiarity with Linux network hardware drivers so I’m uncomfortable doing this myself from scratch. This seems like a fairly common piece of hardware, so maybe someone is already working on this. I’d happily
test & help debug if so.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Figure out how to remove the RTAI dependency:<o:p></o:p></p>
<p class="MsoNormal">The RT-Preempt patches are eroding support for RTAI, but I’m kind of stuck with existing code. Perhaps there exist wrappers/libraries for emulating the RTAI services using only the RT-Preempt kernel? This seems unlikely, but not impossible.
I’d prefer this, since I believe RTAI support will only continue to decline. Anyone know of something like this?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Support both RTAI and RT-Preempt:<o:p></o:p></p>
<p class="MsoNormal">This would allow existing, legacy RTAI code and use of the generic driver via RT-Preempt. However, I’ve not seen anyone actually talking about doing this. I’ve not tried applying both the RTAI patches and the RT-preempt patches, but I
strongly suspect they will have conflicts. Also, I’m using 3.16 currently but the RT-Preempt patches are only available for 3.14 and 3.18 (naturally). The basic idea here is worrying, but I guess it might work…<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Suggestions?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal">-Scott Tillman<o:p></o:p></p>
</div>
</body>
</html>