[Haiku-commits] r31213 - in haiku/trunk/src/add-ons: accelerants/nvidia accelerants/nvidia/engine kernel/drivers/graphics/nvidia
rudolf.cornelissen at gmail.com
Fri Jun 26 19:08:00 CEST 2009
I'll have a look at it soon. :-)
On Wed, Jun 24, 2009 at 9:00 PM, Axel Dörfler <axeld at pinc-software.de>wrote:
> Rudolf Cornelissen <rudolf.cornelissen at gmail.com> wrote:
> > No, I think not.
> > These are accelerant hooks just like setmode, proposemode and such?
> > And: does the app_server actually use it, and how? Is there doc on
> > this?
> There are three new (optional) hooks, there are no docs available, but
> this should help:
> 1) status_t get_edid_info(void* info, size_t size, uint32* _version);
> You just copy the edid1_info, and set version to EDID_VERSION_1.
> If you support EDID, you should implement this one.
> 2) status_t get_preferred_display_mode(display_mode *preferredMode);
> If you don't have EDID info (for example, because it's a laptop/TV
> display that does
> not support EDID), you can implement this function to tell the
> app_server that it
> should use a certain mode by default.
> 3) status_t get_monitor_info(monitor_info *info);
> If you don't have EDID info, you can implement this call to provide
> extra information
> about the monitor. This info is used in the app_server to store and
> settings; if you attach a new monitor, a setting is reused if it's
> the same model of
> an existing setting.
> This is all used to choose the right mode on first boot, such that you
> usually never have to use the Screen preferences application at all. 1)
> is implemented by the Intel Extreme, Radeon, S3, ATI and VESA drivers,
> 2) is implemented by the Radeon, and ATI driver only.
> And yes, the app_server makes use of all three hooks.
> Haiku-commits mailing list
> Haiku-commits at lists.berlios.de
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Haiku-commits