Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tempura San <tempura.san@gmail.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: i915 module does not find 82865G if configured as secondary
Date: Sun, 09 Oct 2011 22:20:03 +0200	[thread overview]
Message-ID: <4E9201F3.9030005@gmail.com> (raw)
In-Reply-To: <d08817$1pjt6r@azsmga001.ch.intel.com>

I've integrated your patches into the i915 driver I am using.
If I just rebuild the module the result is the same as with Daniel's
suggestion.

As there is also a change in vgaarb.c - which is not a module - I need
to do a full build and check again.

If this is not fixing the behaviour either, is there a possibility to
use a recent i915 driver with this kernel?

Yours,
Tempura

On Sun, 09 Oct 2011 19:36:27 +0100, Chris Wilson wrote:
> On Sun, 9 Oct 2011 14:44:30 +0200, Daniel Vetter <daniel@ffwll.ch> wrote:
>> On Sun, Oct 09, 2011 at 01:07:25PM +0200, Tempura San wrote:
>>> Here is the output of lspci -nn:
>>>
>>> 00:00.0 Host bridge [0600]: Intel Corporation 82865G/PE/P DRAM
>>> Controller/Host-Hub Interface [8086:2570] (rev 02)
>>> 00:02.0 Display controller [0380]: Intel Corporation 82865G Integrated
>>> Graphics Controller [8086:2572] (rev 02)
>> The issue seems to be that the igd isn't a VGA pci class device anymore
>> when used as secondary. The below (untested) patch should allow to still
>> bind the i915 driver. Please test how far that gets us.
> Note the old kernel, and probable lack of:
>
> commit 934f992c763ae1e5eefcce8af769c16444085df7
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date:   Thu Jan 20 13:09:12 2011 +0000
>
>     drm/i915: Recognise non-VGA display devices
>     
>     Starting with SandyBridge (though possible with earlier hacked BIOSes),
>     the BIOS may initialise the IGFX as secondary to a discrete GPU. Prior,
>     it would simply disable the integrated GPU. So we adjust our PCI class
>     mask to match any DISPLAY_CLASS device.
>     
>     In such a configuration, the IGFX is not a primary VGA controller and
>     so should not take part in VGA arbitration, and the error return from
>     vga_client_register() is expected.
>     
>     Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>     Cc: stable@kernel.org
>
> and
>
> commit 5fe49d86f9d01044abf687a8cd21edef636d58aa
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date:   Tue Feb 1 19:43:02 2011 +0000
>
>     drm/i915: Only bind to function 0 of the PCI device
>     
>     Early chipsets (gen2/3) used function 1 as a placeholder for multi-head.
>     We used to ignore these since they were not assigned to
>     PCI_CLASS_DISPLAY_VGA. However with 934f992c7 we attempt to bind to all
>     Intel PCI_CLASS_DISPLAY devices (and functions) to work in multi-gpu
>     systems. This fails hard on gen2/3.
>     
>     Reported-by: Ferenc Wágner <wferi@niif.hu>
>     Tested-by: Ferenc Wágner <wferi@niif.hu>
>     Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=28012
>     Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>     Cc: stable@kernel.org
> -Chris
>

  reply	other threads:[~2011-10-09 20:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-08 15:25 i915 module does not find 82865G if configured as secondary Tempura San
2011-10-08 16:33 ` Felix Miata
2011-10-09  9:52   ` Tempura San
2011-10-08 19:37 ` Dave Airlie
2011-10-09  9:34   ` Tempura San
2011-10-09 10:38     ` Daniel Vetter
2011-10-09 11:07       ` Tempura San
2011-10-09 12:44         ` Daniel Vetter
2011-10-09 18:36           ` Chris Wilson
2011-10-09 20:20             ` Tempura San [this message]
2011-10-10 19:06             ` Julien Cristau
2011-10-10 20:32               ` Tempura San
2011-10-10 20:53                 ` Chris Wilson
2011-10-11  8:25                   ` Dave Airlie
2011-10-15 11:44                   ` Tempura San
2011-10-09 20:19           ` Tempura San
2011-10-10  6:55             ` Daniel Vetter

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=4E9201F3.9030005@gmail.com \
    --to=tempura.san@gmail.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    /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