On Monday 18 October 2010 22:30:17 Arnd Bergmann wrote:
> I don't think the code path you patch here actually gets used, since
> intel_lvds_init gets called by intel_setup_outputs only for mobile devices.
FWIW, the patch below does work.
Arnd
--- a/drivers/gpu/drm/i915/intel_display.c
+
On Monday 18 October 2010 22:15:23 Jesse Barnes wrote:
> On Mon, 18 Oct 2010 21:57:05 +0200 Arnd Bergmann wrote:
> > i915 is a module with kms enabled, the blur seems to show up on the
> > text console the moment that the module gets loaded during boot.
> > Before that, the console is in VGA text
On Monday 18 October 2010 21:28:01 Jesse Barnes wrote:
>
> On Mon, 18 Oct 2010 21:13:59 +0200
> Arnd Bergmann wrote:
>
> > On Monday 18 October 2010 20:56:48 Jesse Barnes wrote:
> > > Hm, the LVDS code should take care of panel fitting in
> > > the !HAS_PCH_SPLIT case. Does this patch achieve t
On Monday 18 October 2010 20:56:48 Jesse Barnes wrote:
> Hm, the LVDS code should take care of panel fitting in
> the !HAS_PCH_SPLIT case. Does this patch achieve the same thing as
> yours? Maybe we were leaving a stale PFIT value in place...
No, your patch doesn't have any effect for me.
On Mon, 18 Oct 2010 22:37:43 +0200
Arnd Bergmann wrote:
> On Monday 18 October 2010 22:30:17 Arnd Bergmann wrote:
>
> > I don't think the code path you patch here actually gets used, since
> > intel_lvds_init gets called by intel_setup_outputs only for mobile devices.
>
> FWIW, the patch below
On Mon, 18 Oct 2010 22:37:43 +0200
Arnd Bergmann wrote:
> On Monday 18 October 2010 22:30:17 Arnd Bergmann wrote:
>
> > I don't think the code path you patch here actually gets used, since
> > intel_lvds_init gets called by intel_setup_outputs only for mobile devices.
>
> FWIW, the patch below
On Monday 18 October 2010 22:30:17 Arnd Bergmann wrote:
> I don't think the code path you patch here actually gets used, since
> intel_lvds_init gets called by intel_setup_outputs only for mobile devices.
FWIW, the patch below does work.
Arnd
--- a/drivers/gpu/drm/i915/intel_display.c
+
On Monday 18 October 2010 22:15:23 Jesse Barnes wrote:
> On Mon, 18 Oct 2010 21:57:05 +0200 Arnd Bergmann wrote:
> > i915 is a module with kms enabled, the blur seems to show up on the
> > text console the moment that the module gets loaded during boot.
> > Before that, the console is in VGA text
On Mon, 18 Oct 2010 21:57:05 +0200
Arnd Bergmann wrote:
> On Monday 18 October 2010 21:28:01 Jesse Barnes wrote:
> >
> > On Mon, 18 Oct 2010 21:13:59 +0200
> > Arnd Bergmann wrote:
> >
> > > On Monday 18 October 2010 20:56:48 Jesse Barnes wrote:
> > > > Hm, the LVDS code should take care of pa
On Mon, 18 Oct 2010 21:57:05 +0200
Arnd Bergmann wrote:
> On Monday 18 October 2010 21:28:01 Jesse Barnes wrote:
> >
> > On Mon, 18 Oct 2010 21:13:59 +0200
> > Arnd Bergmann wrote:
> >
> > > On Monday 18 October 2010 20:56:48 Jesse Barnes wrote:
> > > > Hm, the LVDS code should take care of pa
On Monday 18 October 2010 21:28:01 Jesse Barnes wrote:
>
> On Mon, 18 Oct 2010 21:13:59 +0200
> Arnd Bergmann wrote:
>
> > On Monday 18 October 2010 20:56:48 Jesse Barnes wrote:
> > > Hm, the LVDS code should take care of panel fitting in
> > > the !HAS_PCH_SPLIT case. Does this patch achieve t
On Mon, 18 Oct 2010 21:13:59 +0200
Arnd Bergmann wrote:
> On Monday 18 October 2010 20:56:48 Jesse Barnes wrote:
> > Hm, the LVDS code should take care of panel fitting in
> > the !HAS_PCH_SPLIT case. Does this patch achieve the same thing as
> > yours? Maybe we were leaving a stale PFIT value
On Mon, 18 Oct 2010 21:13:59 +0200
Arnd Bergmann wrote:
> On Monday 18 October 2010 20:56:48 Jesse Barnes wrote:
> > Hm, the LVDS code should take care of panel fitting in
> > the !HAS_PCH_SPLIT case. Does this patch achieve the same thing as
> > yours? Maybe we were leaving a stale PFIT value
On Monday 18 October 2010 20:56:48 Jesse Barnes wrote:
> Hm, the LVDS code should take care of panel fitting in
> the !HAS_PCH_SPLIT case. Does this patch achieve the same thing as
> yours? Maybe we were leaving a stale PFIT value in place...
No, your patch doesn't have any effect for me.
On Sun, 17 Oct 2010 19:37:13 +0200
Arnd Bergmann wrote:
> Commit e9e331a8ab "drm/i915/lvds: Ensure panel is unlocked for Ironlake or
> the panel fitter" broke my HDMI output on GMA4500HD, it seemed to be driving
> the output with the wrong resolution, while still showing the native panel
> resolu
On Sun, 17 Oct 2010 19:37:13 +0200
Arnd Bergmann wrote:
> Commit e9e331a8ab "drm/i915/lvds: Ensure panel is unlocked for Ironlake or
> the panel fitter" broke my HDMI output on GMA4500HD, it seemed to be driving
> the output with the wrong resolution, while still showing the native panel
> resolu
Commit e9e331a8ab "drm/i915/lvds: Ensure panel is unlocked for Ironlake or
the panel fitter" broke my HDMI output on GMA4500HD, it seemed to be driving
the output with the wrong resolution, while still showing the native panel
resolution of 1680x1050 being in use. This caused a very irritating blur
Commit e9e331a8ab "drm/i915/lvds: Ensure panel is unlocked for Ironlake or
the panel fitter" broke my HDMI output on GMA4500HD, it seemed to be driving
the output with the wrong resolution, while still showing the native panel
resolution of 1680x1050 being in use. This caused a very irritating blur
18 matches
Mail list logo
