Bug 90524 - hwdb needs entry for BenQ monitors
Summary: hwdb needs entry for BenQ monitors
Status: RESOLVED FIXED
Alias: None
Product: systemd
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: systemd-bugs
QA Contact: systemd-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-19 23:37 UTC by Federico Mena-Quintero
Modified: 2016-06-24 15:31 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
systemd-hwdb-benq.patch (655 bytes, text/plain)
2015-05-19 23:37 UTC, Federico Mena-Quintero
Details

Description Federico Mena-Quintero 2015-05-19 23:37:17 UTC
Created attachment 115903 [details]
systemd-hwdb-benq.patch

For reference, see https://bugzilla.gnome.org/show_bug.cgi?id=748914

Here is a patch to add an entry for "LAP" -> BenQ.  This is for the vendor id string from an EDID blob of a monitor.
Comment 1 Lennart Poettering 2016-06-10 12:48:36 UTC
I have now prepped this PR:

https://github.com/systemd/systemd/pull/3491

It adds your EDID/EISA/ACPI/UEFI/PNP id of "LAP" to the database, among other things.

Closing this bug hence. Let's continue discussion in that PR.

(BTW, your submission made via gnome bug 748914 got reverted again, since they updated their database from hwdb again which doesn't carry LAP.)
Comment 2 Bastien Nocera 2016-06-24 15:31:13 UTC
(In reply to Lennart Poettering from comment #1)
> I have now prepped this PR:
> 
> https://github.com/systemd/systemd/pull/3491
> 
> It adds your EDID/EISA/ACPI/UEFI/PNP id of "LAP" to the database, among
> other things.
> 
> Closing this bug hence. Let's continue discussion in that PR.
> 
> (BTW, your submission made via gnome bug 748914 got reverted again, since
> they updated their database from hwdb again which doesn't carry LAP.)

No, we didn't. https://bugzilla.gnome.org/show_bug.cgi?id=590059 is still opened, because it's waiting for an answer from a systemd developer...


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.