On Wed, 23 Dec 2020, Martin Husemann wrote:
Can you narrow down the pullup that broke it?
I can only tell you when I noticed it. It was OK in
9.0 RELEASE; then I tried one of the final 9.0-STABLE
images (the last or next-to-last) before 9.1 and found
the bug.
Is it still broken in -current
On Wed, 23 Dec 2020, Michael van Elst wrote:
If you had multiple wsdisplay* instances, there would be some
corresponding ttyE* that you could send the ioctl to.
Hmm: wsdisplay0 at intelfb0; wsdisplay1 at nouveaufb0 ?
What about multiple multiple monitors connected to
the same card?
-RVP
On Wed, Dec 23, 2020 at 06:56:31AM +, RVP wrote:
> /usr/sbin/wsmoused has been non-working since slightly
> before 9.1 was released. Specifically, any button click
> or release generates:
Can you narrow down the pullup that broke it? Is it still broken in -current?
I see nothing obvious in CHA
/usr/sbin/wsmoused has been non-working since slightly
before 9.1 was released. Specifically, any button click
or release generates:
wsmoused: ioctl(WSDISPLAYIO_GETWSCHAR) failed: Invalid argument
and click+drags produce a torrent of the same. Here is a patch
which fixes this problem:
---START-
Is there a way to retrieve EDID data from displays other than
the default one using ioctl(WSDISPLAYIO_GET_EDID) ?
On my Asus X202E laptop with 3 physical outputs (LVDS, VGA, HDMI)
the ioctl gets the EDID only of the LVDS panel. This is for
situations where X is not running/can't run and xrandr un
On Wed, Dec 23, 2020 at 07:36:10AM +, RVP wrote:
> On Wed, 23 Dec 2020, Michael van Elst wrote:
>
> > If you had multiple wsdisplay* instances, there would be some
> > corresponding ttyE* that you could send the ioctl to.
>
> Hmm: wsdisplay0 at intelfb0; wsdisplay1 at nouveaufb0 ?
> What abou
