linux-kernel - Re: worth submitting a detailed EDID structure?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sat, 3 Jan 2009 04:21:42 -0500 (EST)
From:	"Robert P. J. Day" <rpjday@...shcourse.ca>
To:	Eric Anholt <eric@...olt.net>
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: worth submitting a detailed EDID structure?

On Fri, 2 Jan 2009, Eric Anholt wrote:

> On Fri, 2009-01-02 at 09:08 -0500, Robert P. J. Day wrote:
> > just noticed the header file include/video/edid.h, which defines
> > video EDID info as simply:
> >
> >   struct edid_info {
> >         unsigned char dummy[128];
> >   };
> >
> > a couple months back, i had to mess with EDID info and defined a
> > detailed structure to manipulate EDID fields.  is it worth
> > submitting that as a patch and union'ing that with the above?
> > not a big deal for me either way.
>
> The KMS code already has detailed EDID structures in drm_edid.h, for
> what it's worth.  We still need to get CEA extension bits ported
> over, though.

  ah, i hadn't noticed that.  eggcellent, thanks.

rday
--

========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
    Have classroom, will lecture.

http://crashcourse.ca                          Waterloo, Ontario, CANADA
========================================================================
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/