porting linux driver in Fiasco.OC

[Shabnam Engineer]

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 at 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 at 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 at 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 at 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 at os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers




   

  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://os.inf.tu-dresden.de/pipermail/l4-hackers/attachments/20150808/5f23a39e/attachment.htm>