Christian König <deathsim...@vodafone.de> writes: >[...] > On 26.03.2012 17:20, Francisco Jerez wrote: >> Essentially it's an interface to enumerate the graphic devices that are >> present in the system (and by extension to create screens on them, >> enumeration alone is useless without having a way to do something with >> the devices you find). >> >> You're right that traditionally this hasn't been part of the winsys API, >> but the task is very tightly coupled with the underlying window system: >> to my innocent eyes it seems that it would make more sense to extend the >> winsys API with something like this. > > Well, they key point is that even if it is closely related to the > different window systems, it isn't a window system of its own!
Hm, I think we should first settle on what a winsys is. In my understanding it's a set of primitives that abstract the platform specific details of the implementation, where "details" include: - device binding - memory management - command submission My proposal boils down to including "device enumeration" among these categories, because the implementation to use is going to be highly dependent on the specific platform and display architecture we're running on, e.g. it's not going to be the same when running on X/DRI, on the bare DRM device, on other operating systems... Of course this doesn't rule out moving parts of winsys/loader to auxiliary/ if they're judged to be reusable enough, or if they're judged to be completely unrelated to the task a winsys is supposed to accomplish, but AFAICT the interface itself makes sense in winsys/. > So I would also rather put it under src/gallium/auxiliary/winsysloader > instead. > > Christian. >[...]
pgpQsuYrz4zNB.pgp
Description: PGP signature
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
