Hi Eric, On Mon, Mar 04, 2019 at 12:02:16PM -0800, Eric Anholt wrote: > Maxime Ripard <maxime.rip...@bootlin.com> writes: > > > Signed-off-by: Maxime Ripard <maxime.rip...@bootlin.com> > > Googling for users of the firmware's hdmi_drive= flag, I'm seeing lots > of people with hdmi_drive=2 (force HDMI mode) due to Raspberry Pi not > allowing HDMI audio with DMT modes, which it looks like DRM does allow. > > The only users of hdmi_drive=1 (force HDMI mode) I'm seeing are people > setting things up for non-EDID monitors, but I think the expectation in > DRM is that people would provide an EDID. So, I'm not sure it makes > sense to support an equivalent of this flag? Or, it should probably be > part of specifying a custom mode on the command line.
That would be adding one more check before registering the card, or even coming up with something else entirely to mark the output as non-working at the moment. Maybe we should start the discussion with Mark Brown about this, and see what his opinion is? Maxime -- Maxime Ripard, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
signature.asc
Description: PGP signature
_______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
