On Sat, 11 Sep 2004, Alan Cox wrote:
On Sad, 2004-09-11 at 16:53, Vladimir Dergachev wrote:Lastly, I am not saying you have to put all the code in the same file. All I am saying we can mandate that all Radeon HW specific code is linked in one module - and this would make things easier for developers.
And if I want dri but not frame buffer, or vice versa, as the majority of current users do
You are missing my point - I do not say we need to *activate* the framebuffer, just link the mode setting (and other hardware dependent code) into DRM driver.
This is kinda like vesafb driver is doing now - if I don't pass vga=XX parameter on the command line it does not touch the graphics card.
Thus, even if framebuffer support is not compiled into the kernel the DRM driver is able to reinitialize the card into a sane state.
I would agree that this can be coded as well - but why bother ? Or is it done and working already ?
Splitting the modules up is the easy bit. The API is the hard bit so you might as well formalize it. It also gives the users the ability to not load huge radeon modules.
This is a good point - if we don't need DMA or 3d acceleration we can reduce memory footprint. This would seem that current DRM driver would need to be dependent on whatever driver contains the mode setting code.
What do you think ?
best
Vladimir Dergachev
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
--
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
