From: Jani Nikula <jani.nikula@linux.intel.com>
To: Jocelyn Falempe <jfalempe@redhat.com>,
tzimmermann@suse.de, 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: Thu, 06 Jul 2023 13:14:47 +0300 [thread overview]
Message-ID: <87edllxs6g.fsf@intel.com> (raw)
In-Reply-To: <fdb25b67-92fa-d010-39b4-a14ab3fa4edc@redhat.com>
On Thu, 06 Jul 2023, Jocelyn Falempe <jfalempe@redhat.com> wrote:
> Yes, so maybe a better way would be to add a remote/bmc connector, with
> proper default resolution ?
> That will better reflect what the hardware does.
I'm afraid I don't know enough about the hardware or use case to say.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-07-06 10:15 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 [this message]
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
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=87edllxs6g.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jammy_huang@aspeedtech.com \
--cc=jfalempe@redhat.com \
--cc=kuohsiang_chou@aspeedtech.com \
--cc=tzimmermann@suse.de \
/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.