From: Prakash Punnoor <prakash@punnoor.de>
To: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Subject: Re: [PATCH] nvidiafb: allow ignoring EDID info
Date: Sun, 28 Jan 2007 12:05:09 +0100
User-Agent: KMail/1.9.6
Cc: linux-kernel@vger.kernel.org
References: <ephv35$4i3$1@sea.gmane.org>
In-Reply-To: <ephv35$4i3$1@sea.gmane.org>
MIME-Version: 1.0
Content-Type: multipart/signed;
  boundary="nextPart1174971.eNndTCJJu1";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <200701281205.13078.prakash@punnoor.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1339
Lines: 42

--nextPart1174971.eNndTCJJu1
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Am Sonntag 28 Januar 2007 schrieb Giuseppe Bilotta:
> From: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>

> Solve the issue by introducing a new boolean module parameter (useedid)
> which can be set to 0 to prevent the driver from using the EDID
> information.

I don't know whether this is possible, but wouldn't be a cleaner approach b=
e=20
to put this parameter to something fb specific and not nvidia specific? As=
=20
Nvidia fb proabably isn't the only one using edid and so it wouldn't be=20
necessary to introduce such a parameter for every fb driver...

=2D-=20
(=B0=3D                 =3D=B0)
//\ Prakash Punnoor /\\
V_/                 \_V

--nextPart1174971.eNndTCJJu1
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.1 (GNU/Linux)

iD8DBQBFvINpxU2n/+9+t5gRAgHQAKDYLyO87C1UGP6UjASuvRYiQKuhLACfVZal
YEjvm/quHNHFCaY2Nen4CLQ=
=U6bx
-----END PGP SIGNATURE-----

--nextPart1174971.eNndTCJJu1--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/