All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Vegter <martin.vegter@aol.com>
To: intel-gfx@lists.freedesktop.org
Subject: backporting support for Intel HD 4600 into Debian Wheezy
Date: Sat, 12 Apr 2014 16:07:28 +0200	[thread overview]
Message-ID: <534948A0.9050701@aol.com> (raw)

Hello,
I am using Debian Wheezy, and I am trying to backport support for Intel
HD 4600 into xserver-xorg-video-intel-2.19.0

I have made following changes to intel_driver.h and intel_module.c
(based on commit 45c09bfe58c37bbf7965af25bdd4fa5c37c0908f), but it still
does not work properly.

Could somebody please advise what else I need to change?

src/intel_driver.h
194a195,201
> #define PCI_CHIP_HASWELL_D_GT1		0x0402
> #define PCI_CHIP_HASWELL_D_GT2		0x0412
> #define PCI_CHIP_HASWELL_M_GT1		0x0406
> #define PCI_CHIP_HASWELL_M_GT2		0x0416
> #define PCI_CHIP_HASWELL_CRW_D_GT2	0x0D12
> #define PCI_CHIP_HASWELL_CRW_M_GT2	0x0D16


src/intel_module.c
98a99,102
> static const struct intel_device_info intel_haswell_info = {
>         .gen = 075,
> };
> 
147a152,159
> 
> 	{PCI_CHIP_HASWELL_D_GT1,                "HD Graphics" },
> 	{PCI_CHIP_HASWELL_D_GT2,                "HD Graphics 4600" },
> 	{PCI_CHIP_HASWELL_M_GT1,                "HD Graphics" },
> 	{PCI_CHIP_HASWELL_M_GT2,                "HD Graphics 4600" },
> 	{PCI_CHIP_HASWELL_CRW_D_GT2,            "HD Graphics 4600" },
> 	{PCI_CHIP_HASWELL_CRW_M_GT2,            "HD Graphics 4600" },
> 
216a229,235
> 
> 	INTEL_DEVICE_MATCH (PCI_CHIP_HASWELL_D_GT1, &intel_haswell_info ),
> 	INTEL_DEVICE_MATCH (PCI_CHIP_HASWELL_D_GT2, &intel_haswell_info ),
> 	INTEL_DEVICE_MATCH (PCI_CHIP_HASWELL_M_GT1, &intel_haswell_info ),
> 	INTEL_DEVICE_MATCH (PCI_CHIP_HASWELL_M_GT2, &intel_haswell_info ),
> 	INTEL_DEVICE_MATCH (PCI_CHIP_HASWELL_CRW_D_GT2, &intel_haswell_info
> 	),
> 	INTEL_DEVICE_MATCH (PCI_CHIP_HASWELL_CRW_M_GT2, &intel_haswell_info
> 	),

                 reply	other threads:[~2014-04-12 14:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=534948A0.9050701@aol.com \
    --to=martin.vegter@aol.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.