On Sunday 11 October 2009 16:36:38 Jeff Epler wrote: > This is very interesting -- thanks for working on it. I have a few > questions, though. > > How do hardware drivers work with --realtime=linux?
They don't, yet. I'm currently focussing on the latency tester. However, in x86 it's easy to do raw I/O from userspace. On other architectures a kernel helper will be required, however for the parport case the kernel parport driver might be enough (it's very optimized, already). > Is there a reason to keep --enable-simulator? Well, yes, I think so for people running the stuff on standard kernels. RT-enabled kernels will never be the standard, because they cause serious throughput issues. > (I suspect the answers here may be tied together: hardware driver > support will require something, perhaps linux_rtapi_app, to be setuid; Yeah. > but maybe the underlying code can be identical, with the difference > being the setuid bit?) Hm, well. The rtapi code currently is not identical. Maybe it turns out later that the rtapi code for linux-rt is also usable for simulator, though. For now I'd like to keep the sim and linux-rt code separate, for simplicity and regression safeness. > Unless this is a clear winner over rtai on almost all hardware, how (if > at all) will we present it to users, particularly new ones who have to > choose what to download/install? I think we should stick to rtai for the default install and the distribution, until rt is in mainline-linux and no regressions are known. That will be a few years from now, so I don't really have any plans on that ;) -- Greetings, Michael. ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
