From: Dominik 'Rathann' Mierzejewski <dominik@greysector.net>
To: Hans de Goede <hdegoede@redhat.com>
Cc: David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel.vetter@intel.com>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/gma500: Add CedarView LVDS blacklist
Date: Wed, 10 Apr 2019 13:18:29 +0200 [thread overview]
Message-ID: <20190410111829.GC3178@sakura.greysector.net> (raw)
In-Reply-To: <82afbb86-433a-a0ba-e06f-8badd5862943@redhat.com>
On Wednesday, 10 April 2019 at 11:08, Hans de Goede wrote:
> On 10-04-19 11:00, Patrik Jakobsson wrote:
> > On Wed, Apr 10, 2019 at 9:27 AM Hans de Goede <hdegoede@redhat.com> wrote:
> > > On 09-04-19 21:31, Dominik 'Rathann' Mierzejewski wrote:
> > > > On Tuesday, 09 April 2019 at 16:44, Hans de Goede wrote:
> > > > > On 09-04-19 14:05, Patrik Jakobsson wrote:
[...]
> > > > > > I'm not totally against this but not sure about the consequences. Is
> > > > > > there perhaps a better dmi string to match against?
> > > > >
> > > > > No there are no better DMI strings to match against I'm afraid.
> > > >
> > > > I did load default settings in BIOS setup and there's no change in
> > > > behaviour. LVDS gets detected as connected:
> > > > $ cat /sys/class/drm/card0-LVDS-1/status
> > > > connected
> > > >
> > > > Only VGA output is physically connected at the moment.
> > >
> > > To be clear what Dominik means here is that he has a VGA monitor
> > > connected. There is no LVDS panel in this device at all.
> >
> > Thanks for testing. I dusted off my DN2800MT and tried turning LVDS
> > on/off in the BIOS. With LVDS disabled gma500 reports it as connected.
> > When LVDS is enabled in bios I instead get a connected eDP connector.
> > I'm starting to think that broken VBT parsing might be the actual
> > problem.
>
> Maybe, but I assume there are CedarView based laptops with LVDS panels
> which works, so I suspect this might be more of a bug in your BIOS.
>
> So what is the next step in debugging this?
To add a small twist, I got an updated BIOS from the vendor to fix
another issue (https://bugzilla.kernel.org/show_bug.cgi?id=199117)
and the DMI string has changed to: "CDV W Series 05", so Hans' patch
no longer matches my machine.
Regards,
Dominik
--
Fedora https://getfedora.org | RPM Fusion http://rpmfusion.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
-- from "Collected Sayings of Muad'Dib" by the Princess Irulan
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-04-10 11:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 6:51 [PATCH] drm/gma500: Add CedarView LVDS blacklist Hans de Goede
2019-04-09 9:47 ` Patrik Jakobsson
2019-04-09 10:20 ` Hans de Goede
2019-04-09 12:05 ` Patrik Jakobsson
2019-04-09 14:44 ` Hans de Goede
2019-04-09 19:31 ` Dominik 'Rathann' Mierzejewski
2019-04-10 7:27 ` Hans de Goede
2019-04-10 9:00 ` Patrik Jakobsson
2019-04-10 9:08 ` Hans de Goede
2019-04-10 11:18 ` Dominik 'Rathann' Mierzejewski [this message]
2019-04-10 11:33 ` Patrik Jakobsson
2019-04-10 11:51 ` Dominik 'Rathann' Mierzejewski
2019-04-16 14:32 ` Patrik Jakobsson
2019-04-16 15:36 ` Hans de Goede
2019-04-10 11:37 ` Patrik Jakobsson
2019-04-10 10:43 ` Ville Syrjälä
2019-04-10 11:34 ` Patrik Jakobsson
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=20190410111829.GC3178@sakura.greysector.net \
--to=dominik@greysector.net \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox