On Thu, Dec 10, 2009 at 11:02 AM, James Simmons <jsimmons@xxxxxxxxxxxxx> wrote: > That shouldn't happen. In the xorg.conf do you have in the > > Option UseFBDev "True" That option appears to have no effect (have tried both ways). Do you know who parses it? Couldn't find it in core xserver. The DisplayLink support is still very rough, but it's currently using its own X server driver (http://libdlo.freedesktop.org/wiki/xf86-driver-displaylink), which has some IOCTLs to its framebuffer driver, including a mode setting IOCTL. If the arbitration between fbdev clients is intended to happen at the point of mode setting, rather than at open(), that would explain the problem. Are there any old posts or docs which describe how arbitration is handled for the fbdev driver and multiple clients? Jaya Kumar has written an alternative DisplayLink fbdev driver that uses defio and works with the standard fbdev X servers. That support will be merged in soon, so then it'll be easy to test what happens where there's no special mode set paths between X and the framebuffer driver. Thanks, Bernie -- To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
