Hi thanks for your answersI want to implement Fiasco.OC on a board and test some RTOS beside other non realtime OS .. at first I want to be sure that if I need a driver for our special tests and the Fiasco.OC does not support that, Could I choose it from linux drivers and port it to Fiasco.OC microkernel?does someone do this work?thanks for your considering my question.regards, shabnam
On Saturday, August 8, 2015 10:39 AM, Shabnam Engineer shabnam.engineer72@yahoo.com wrote:
Hi thanks for your answerI want to implement Fiasco.OC on a board and test some RTOS beside other non realtime OS .. at first I want to be sure that if I need a driver for our special tests and the Fiasco.OC does not support that, Could I choose it from linux drivers and port it to Fiasco.OC microkernel?does someone do this work?thanks for your considering my question.regards, shabnam
On Thursday, July 30, 2015 5:53 PM, Jorge Alberto Garcia jorge.garcia.gonzalez@gmail.com wrote:
Hi!This is very interesting!, is there any resource about what needs to be done for a user space component handling hw ?Thanks!
On Thu, Jul 30, 2015 at 1:51 AM, Matthias Lange matthias.lange@kernkonzept.com wrote:
Hi,
On 07/29/2015 12:29 PM, Shabnam Engineer wrote:
hi I have a question about porting linux drivers in Fiasco.OC. Can I port linux drivers into Fiasco.OC ?
In a microkernel system device drivers are implemented as isolated user space components. No devices drivers, except from selected very low level devices like timer and interrupt controller, are implemented in the kernel.
Matthias.
-- Matthias Lange, matthias.lange@kernkonzept.com, +49 - 351 - 41 88 86 14
Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden, HRB 31129. Geschäftsführer: Dr.-Ing. Michael Hohmuth
_______________________________________________ l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
On Sat Aug 08, 2015 at 07:53:17 +0000, Shabnam Engineer wrote:
Hi thanks for your answersI want to implement Fiasco.OC on a board and test some RTOS beside other non realtime OS .. at first I want to be sure that if I need a driver for our special tests and the Fiasco.OC does not support that, Could I choose it from linux drivers and port it to Fiasco.OC microkernel?does someone do this work?thanks for your considering my question.regards, shabnam
I'm not sure I understand. Which type of driver do you think you need? Which type of board do you have?
Adam
Adam Lackorzynski <adam <at> os.inf.tu-dresden.de> writes:
On Sat Aug 08, 2015 at 07:53:17 +0000, Shabnam Engineer wrote:
Hi thanks for your answersI want to implement Fiasco.OC on a board and
test some RTOS beside other non
realtime OS .. at first I want to be sure that if I need a driver for
our special tests and the Fiasco.OC
does not support that, Could I choose it from linux drivers and port it
to Fiasco.OC microkernel?does
someone do this work?thanks for your considering my
question.regards, shabnam
I'm not sure I understand. Which type of driver do you think you need? Which type of board do you have?
Adam
Hello Adam Our test does not exactly specify till now, but I think we need a net driver and some other necessary drivers. We want to use arm-based board like raspberry Pi or exynos or lpc3250. We want to be sure that we will not face the problem at the middle of our works if we choose Fiasco.OC. Regards, Shabnam
On Mon Aug 10, 2015 at 06:37:27 +0000, shabnam wrote:
Adam Lackorzynski <adam <at> os.inf.tu-dresden.de> writes:
On Sat Aug 08, 2015 at 07:53:17 +0000, Shabnam Engineer wrote:
Hi thanks for your answersI want to implement Fiasco.OC on a board and
test some RTOS beside other non
realtime OS .. at first I want to be sure that if I need a driver for
our special tests and the Fiasco.OC
does not support that, Could I choose it from linux drivers and port it
to Fiasco.OC microkernel?does
someone do this work?thanks for your considering my
question.regards, shabnam
I'm not sure I understand. Which type of driver do you think you need? Which type of board do you have?
Adam
Hello Adam Our test does not exactly specify till now, but I think we need a net driver and some other necessary drivers. We want to use arm-based board like raspberry Pi or exynos or lpc3250. We want to be sure that we will not face the problem at the middle of our works if we choose Fiasco.OC.
In this case L4Linux is the faster approach to have drivers. But still, on ARM, it's generally not a plug'n'play experience.
Adam
l4-hackers@os.inf.tu-dresden.de
-
Adam Lackorzynski -
shabnam -
Shabnam Engineer