Alex Deucher wrote: > i2c bit algo hooks. Next, make sure you are opening the correct i2c > bus. On radeons, we expose all of the on board i2c buses. In most > cases, each connector uses a different i2c bus and there are
If it's all too hard to actually put the i2c interface into the XRandR I/F, how about at least making sure that the display i2c device name is set as an output property ? That way there wouldn't need to be any guessing, or require some user action for software to talk to the display associated with a particular output. The property name needs to be standardised too, "OUTPUT_I2C_DEVICE_NAME", or something. [And what are the permissions on the i2c device ? Does the user have to jump through hoops for the application to actually do I/O ? If so, is there a means to add the display output i2c device to udev ? ] Graeme Gill. _______________________________________________ [email protected]: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: [email protected]
