Roland Tollenaar wrote: > Hi Jan, > >>> If not, is it possible with limited experience in writing drivers to >>> adapt a non-rt driver? Is there any documentation as to how to go >>> about this? >> >> There is a conversion guide under Documentation/README.drvporting. It >> may help to perform 90% or more of the mechanical steps. Beyond this, > Ho ho ho, this document is no small thing. It looks like my own notes > with the same characteristic that I don't understand them when I read > them again. :) > > > > >> also remarked in that guide, you need to perform a critical review of >> the real-time code paths: do they influence other parts of the system >> unacceptably or do they suffer from potential latencies caused by non-RT >> parts of the driver? Anyway, that's the freestyle part of the work we >> can also perform over the list once the obligatory conversion and build >> system integration is done. > > Lets say I am crazy enough to try this where would I find the compilable > source of say the > > LAN chip à Intel LAN 82562EZ BGA 196
Ask you Linux system: What driver does it load to support this chip? I bet it's e100, so the approach would be to add the missing bits to rt_eepro100 that are required to include support for it (maybe just some PCI IDs). Jan
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________ RTnet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rtnet-users
