[haiku-development] Re: RFC : re-factoring multimon to be generic (non-radeon)
- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Sun, 24 Jul 2011 11:47:44 +0200 (MEST)
Alexander von Gluck<kallisti5@xxxxxxxxxxx> wrote:
> > Still, I think it makes sense to factor it out as other drivers might
> > at
> > least try to provide the same limited multiscreen support meanwhile.
> > As Axel suggested, it could go to a private header probably.
> Done in http://pastebin.com/Tksu5h5i
>
> Going to wait again for any push back before committing. While this
> isn't a large
> change... I definitely want to make sure there isn't any *huge*
> push-back before
> committing it :)
I don't think it makes any sense to rework it (no use in using public looking
names, for example), and you actually made some names worse and non-compliant
(like MODE_MASK -> MODEMASK, POSITION_HORIZONTAL -> HPOS) - I wonder how often
one need to note that.
Besides that, since you happen to work on a radeon driver as well, I would just
reuse the existing setup, and names.
> Have any future plans been laid out on how we are going to handle multiple
> monitors in the future?
In the app_server yes, but not about the accelerant API.
> Are we still worried about Be binary compatibility when it comes to the video
> drivers and accelerants?
It depends. We should probably just introduce a new API (alongside the old
one), and take all recent and not so recent developments in graphics devices
into account (like multi monitor, but also for compositing).
For multi monitor, it might make sense to clone the accelerant for each monitor
attached, I guess it's a bit of trial and error, though, to see what works
best. Looking at other solutions in the open source world first is definitely a
good idea, and would be a good starting point.
Bye,
Axel.
Other related posts:
