Am Freitag, den 20.04.2012, 07:02 +0200 schrieb Thierry Reding: > * Jon Mayo wrote: > > On 04/19/2012 01:40 PM, Thierry Reding wrote: > [...] > > >So would it be possible to get a basic dumb KMS driver into mainline > > >(non-staging) and phase in acceleration later on, with ABI guarantees? I > > >guess development can go on in separate trees until the ABI is stable and can > > >subsequently be ported to the mainline driver. > > > > > >Is that an acceptable approach? > > > > That certainly seems like the most reasonable approach to me. Get > > KMS only in first. It's a useful driver as-is, and has the lowest > > barrier to entry into upstream. > > > > Then later we can phase in enhancements. We certainly have plenty of > > places internally and externally to hash out acceleration > > interfaces, and come to some consensus at at later date (either on > > linux-tegra or direct email). > > Okay. Let's do that then. Yes, I think we should go the route that Jerome Glisse pointed out: get in a basic KMS driver first and hide any accel ioctl under a staging config option. > > > We have a lot of concerns here. What is best for X11, what is best > > for Android, how do we keep healthy open source implementations, and > > how does NVIDIA move forward with supporting new Tegra on an open > > source implementation. > > I think by supporting the DRM we can get pretty far for X11. Writing a Tegra- > specific driver based off xf86-video-modesetting can be done to use advanced > features if they can't be abstracted away properly. DRM also paves the way > for Wayland support. > > What I see as somewhat of a problem is how to get NVIDIA and the community to > work together (and work together well). We'll have to see how this works out, > but I'd hate to see more resources wasted because everybody starts doing > their own thing. I'm really interested how this turns out in the end. I hope we can get a somewhat stable cooperation between NVIDIA and the community, like AMD has established at the moment. > > > (My vote is NVIDIA starts using this DRM in-house and builds new > > extensions on top of it, sharing patches on LKML when the hardware is > > released) > > That sounds like a good plan. Ideally you should even share the patches as > soon as they're ready. That'll give viewers some head start and you can fix > the code even before the hardware is released. One thing I would like to have is upstream first. We have seen much Tegra development in both the nv-linux and chromium trees, but those things are going upstream extremely slowly. I can understand that this strategy was beneficial for a fast bring up of the new Tegra hardware, but the DRM driver shouldn't be time critical and so everything should be done to meet upstream quality from the start. -- Lucas -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
