On 2013-10-07 11:10, Hidde Verstoep (E2M) wrote:
> On Fri, Oct 4, 2013 at 8:34 AM, Jan Kiszka <jan.kis...@web.de> wrote:
>> On 2013-10-03 11:16, Hidde Verstoep (E2M) wrote:
>>> Hello Sam,
>>>
>>> I recently posted a version of the driver I ported from a more recent
>>> Linux driver. You can just drop it over the old file and it should
>>> work. http://sourceforge.net/mailarchive/message.php?msg_id=31389885.
>>
>> I just had a quick look at the code: Unfortunately, it still contains
>> some bugs like calling Linux services while holding RTDM locks
>> (__rtl8169_check_link_status and rtl8169_phy_timer, at least). Maybe you
>> check again (take a look at existing drivers for solution patterns) and
>> post it here as a patch.
> 
> The timer is only used when the interface is going up, going down, or
> the speed is changed. All these things are not time critical (in my
> opinion). So I believe the driver can be used as-is in a realtime
> environment, or do these Linux functions prevent the driver from
> running in primary mode?

These bugs can cause sporadic misbehavior or even crashes during
startup/shutdown, network reconfiguration etc., so this is a matter of
robustness.

> 
> I agree it would be nice if it would be fixed properly. However, it
> might be a while before I get around to it.

OK. Who knows, maybe someone else interested in the driver as well will
pick earlier.

Jan


Attachment: signature.asc
Description: OpenPGP digital signature

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
_______________________________________________
RTnet-users mailing list
RTnet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rtnet-users

Reply via email to