Re: New proposed DRM interface design

[Dave Airlie]

Actually after sleeping on this, I've just realised technically whether
the code is in a core separate module or driver module is only going to
affect maybe 5% of the work and the Makefiles/Kconfig at the end, so
following the principles of a)least surprise, b) kernel must remain
stable, I think I can proceed with moving stuff into libraries and the
likes without making the final decision until later, we will probably
start with having the library type code in the driver (where it is now)
and make it possible to change later, as it evolves..

I'll do some more research...

Dave.

 >
> It's still useful, it just is built into the drivers as a library rather
> than the kernel, and the actual "core" is just a major number sharing
> scheme, again the only advantage of building the library functions into
> the kernel or as a separate module are a small memory saving on a rare use
> case, hardly an astounding reason,
>
> New functions added to the library can be made available to new drivers,
> and vendors can ship their own set of library sources and not use
> the kernels ones..
>
> Dave.
>
>

-- 
David Airlie, Software Engineer
http://www.skynet.ie/~airlied / airlied at skynet.ie
pam_smb / Linux DECstation / Linux VAX / ILUG person

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/