Hello, Wolf. 2014-06-26 11:21 GMT+02:00 Wolf Ramovsky <[email protected]>:
> > You should probably start by creating a completely isolated driver (you > > can call it "vesa", "vbe" or something like that). Piggybacking on the > > kfb is fine for the proof-of-concept, but kfb is also used on non-PC > > platforms and therefore should not be polluted by the PC-specific code. > > Since it would be PC-specific driver, should I connect it to the > rootpc rather than to rootvirt? If I should, how to do that? I see > that drivers use .ma file, but I can't understand how to tell that > "vesa" driver should be connected to rootpc. > In the same way rootpc adds PCI bus. See rootpc_add_functions() in [rootpc.c]. But if the card is attached through PCI, it would make more sense to create .ma file matching the device in a similar way as, for example, [uhci]. The first option is definitely simpler to start with, the second option is probably cleaner as the device tree would represent more closely the physical hierarchy. But the second option might be an overkill if we do not have separate drivers for different cards/vendors. - Vojta [rootpc.c] http://trac.helenos.org/browser/mainline/uspace/drv/infrastructure/rootpc/rootpc.c#L198 [uhci] http://trac.helenos.org/browser/mainline/uspace/drv/bus/usb/uhci/uhci.ma > > _______________________________________________ > HelenOS-devel mailing list > [email protected] > http://lists.modry.cz/listinfo/helenos-devel >
_______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/listinfo/helenos-devel
