> I don't know which pin(s) it is. And it's been a while since I read
> the description. But I as I recall, there is a pin that carries
> digital data from the monitor to the computer. Memory is very fuzzy by
> now, but I _think_ it's something like I²C slowed down by an order of
> magnitude or
On Tue, Apr 21, 2020 at 06:22:39PM -0400, Mouse wrote:
> > If I was working on this, I would aim for something like this:
> > - Report an event to userland upon a monitor hotplug.
>
> I've been investigating more, and it turns out all the infrastructure
> is there - there is already such an event
>> I've been investigating more, and it turns out all the
>> infrastructure is there - there is already such an event defined by
>> Xrandr.
> Do you mean "monitor connected" or "DDC info populated" as the event?
I meant "monitor connected", but "DDC info newly available" is perhaps
closer to what
On Tue, 21 Apr 2020, Mouse wrote:
I've been investigating more, and it turns out all the infrastructure is
there - there is already such an event defined by Xrandr.
Do you mean "monitor connected" or "DDC info populated" as the event?
In 8.0 it doesn't actually work - the event isn't sent
> If I was working on this, I would aim for something like this:
> - Report an event to userland upon a monitor hotplug.
I've been investigating more, and it turns out all the infrastructure
is there - there is already such an event defined by Xrandr. In 8.0 it
doesn't actually work - the event
On Fri, Apr 17, 2020 at 06:21:18PM +, m...@netbsd.org wrote:
> On Wed, Apr 15, 2020 at 02:23:19PM -0400, Mouse wrote:
> > It would also be enough if I could force the X server to run 1280x1024
> > whether or not it has a monitor connected. Under 5.2, I added options
> > to the X server, one
On Wed, Apr 15, 2020 at 02:23:19PM -0400, Mouse wrote:
> It would also be enough if I could force the X server to run 1280x1024
> whether or not it has a monitor connected. Under 5.2, I added options
> to the X server, one to capture DDC info to a file and one to provide a
> file to be read to
> have you looked at xrandr?
Doh! Thank you. Yes, that does the trick nicely. I really should not
have needed to have been told that.
While I could bring xrandr itself into the (*severely* stripped-down)
installed filesystem, I'd prefer to UTSL and make the appropriate code
use the relevant
On Wed, Apr 15, 2020 at 2:58 PM matthew green wrote:
>
> have you looked at xrandr? you may be able to just run
> xrandr --auto after connecting the display, or you can
> explicitly ask for a mode with it with --output
> --mode .
>
>
> .mrg.
IIRC xvidtune can query and set modes too
have you looked at xrandr? you may be able to just run
xrandr --auto after connecting the display, or you can
explicitly ask for a mode with it with --output
--mode .
.mrg.
I have a turnkey product I'm working on moving from 5.2 to 8.0, and
I've run into a behaviour difference. I'm wondering how hard it would
be to fix. I'm not sure whether this is more correctly fixed in the
kernel or on the X side of things, hence the cross-post.
Under 5.2, if I start the X
11 matches
Mail list logo
