K
Hi Mario,
You are correct about the pointer thing. I wish that RTLinux(TM) had some sort of process MMU protection of some sort. I guess to have determinism it is worth the risk for some people. They also have a debugger which you can supposedly run all the time that helps to safeguard a lot of these kinds of problems ... I am currently researching and developing for RTLinux now and haven't gotten that far yet.
I like your idea of trying out a port of Puffin on RTLinux at the early stage. As far as device drivers, you have direct access to the IO ports ( inb() outb() , etc) and also direct access to memory but you have to use some function calls first. My guess is that any device driver written for direct access would port very nicely. You might have to add some ifdefs or something to the code, but other than that the code should be the same I would think. The biggest problem with running puffin in RTLinux (I am guessing) will be in the segregation of real time space and linux space. This becomes most apparrent with the HMI interfaces and such which need linux services. I will be willing to contribute as time goes on with helping to acheive this. Right now I am in a learning curve with RTLinux(TM), but it is subsiding a bit. I'll let you guys know as I learn.
~Ken
_______________________________________________
LinuxPLC mailing list
[email protected]
http://linuxplc.org/mailman/listinfo/linuxplc
You are correct about the pointer thing. I wish that RTLinux(TM) had some sort of process MMU protection of some sort. I guess to have determinism it is worth the risk for some people. They also have a debugger which you can supposedly run all the time that helps to safeguard a lot of these kinds of problems ... I am currently researching and developing for RTLinux now and haven't gotten that far yet.
I like your idea of trying out a port of Puffin on RTLinux at the early stage. As far as device drivers, you have direct access to the IO ports ( inb() outb() , etc) and also direct access to memory but you have to use some function calls first. My guess is that any device driver written for direct access would port very nicely. You might have to add some ifdefs or something to the code, but other than that the code should be the same I would think. The biggest problem with running puffin in RTLinux (I am guessing) will be in the segregation of real time space and linux space. This becomes most apparrent with the HMI interfaces and such which need linux services. I will be willing to contribute as time goes on with helping to acheive this. Right now I am in a learning curve with RTLinux(TM), but it is subsiding a bit. I'll let you guys know as I learn.
~Ken
_______________________________________________
LinuxPLC mailing list
[email protected]
http://linuxplc.org/mailman/listinfo/linuxplc