From: Thomas Zimmermann <tzimmermann@suse.de>
To: Jocelyn Falempe <jfalempe@redhat.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
airlied@redhat.com, kuohsiang_chou@aspeedtech.com,
jammy_huang@aspeedtech.com
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/ast: Fix default resolution when no monitor is connected on DP
Date: Fri, 7 Jul 2023 09:30:18 +0200 [thread overview]
Message-ID: <81c57344-289d-fe41-8518-503249ea8d64@suse.de> (raw)
In-Reply-To: <23d80964-d2d0-b688-e3cd-bf25a8135e5e@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 723 bytes --]
Hi
Am 06.07.23 um 18:37 schrieb Jocelyn Falempe:
[...]
>>>
>>> You could out-comment the VGA code in the ast driver for testing.
>>
>> Oh, Thanks for the idea, I will try that.
>>
>
> The result is that I get a black screen on the remote BMC. So maybe
> adding a remote/bmc connector will solve that.
Could work. That would be a connector and encoder of type 'virtual'?
Not all ast devices have a BMC. Do you know how to detect its presence?
Best regards
Thomas
>
>
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2023-07-07 7:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 9:46 [PATCH] drm/ast: Fix default resolution when no monitor is connected on DP Jocelyn Falempe
2023-07-04 14:19 ` Thomas Zimmermann
2023-07-04 14:21 ` Thomas Zimmermann
2023-07-04 14:54 ` Jani Nikula
2023-07-04 16:45 ` Jocelyn Falempe
2023-07-06 9:16 ` Jocelyn Falempe
2023-07-06 9:32 ` Jani Nikula
2023-07-06 10:07 ` Jocelyn Falempe
2023-07-06 10:14 ` Jani Nikula
2023-07-06 10:26 ` Thomas Zimmermann
2023-07-06 11:31 ` Jocelyn Falempe
2023-07-06 16:37 ` Jocelyn Falempe
2023-07-07 7:30 ` Thomas Zimmermann [this message]
2023-07-10 8:07 ` Jocelyn Falempe
2023-07-12 15:05 ` Sui Jingfeng
2023-07-12 15:25 ` Jocelyn Falempe
2023-07-13 8:32 ` Michel Dänzer
2023-07-13 8:49 ` Thomas Zimmermann
2023-07-13 8:53 ` Michel Dänzer
2023-07-13 9:09 ` Thomas Zimmermann
2023-07-13 9:41 ` Michel Dänzer
2023-07-13 8:53 ` Jocelyn Falempe
2023-07-13 8:55 ` Michel Dänzer
2023-07-13 8:50 ` Thomas Zimmermann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=81c57344-289d-fe41-8518-503249ea8d64@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jammy_huang@aspeedtech.com \
--cc=jani.nikula@linux.intel.com \
--cc=jfalempe@redhat.com \
--cc=kuohsiang_chou@aspeedtech.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.