public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Jan Dittmer" <jdi@l4x.org>
Cc: "Dave Airlie" <airlied@gmail.com>,
	"Diego Calleja" <diegocg@gmail.com>,
	linux-kernel@vger.kernel.org, eric.anholt@iintel.com,
	airlied@linux.ie
Subject: Re: intel kms "Failed to allocate space for kernel memory manager"
Date: Mon, 12 Jan 2009 09:56:30 -0800	[thread overview]
Message-ID: <200901120956.31728.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <621d098f0901120037y4e17b4bn8d52a8ecdbc3fcff@mail.gmail.com>

On Monday, January 12, 2009 12:37 am Jan Dittmer wrote:
> On Mon, Jan 12, 2009 at 9:04 AM, Dave Airlie <airlied@gmail.com> wrote:
> > the latest git should work with kms on most chipsets, we are still
> > chasing down some issues on some chipsets,
>
> So is there anything I can test to help you get it going on 'my' chipset
> (GM965, Lenovo X300)?

I do much of my testing on GM965, so you should be able to get it to work with 
the latest bits:
  - libdrm from git master of mesa/drm
  - mesa from git master of mesa/mesa
  - xf86-video-intel from git master
  - drm-intel-next from anholt's kernel tree
    (git://git.kernel.org/pub/scm/linux/kernel/git/anholt/drm-intel)

You'll need to use UXA as your AccelMethod.  If you run into issues with the 
above, please file bugs (if you don't already see your issue filed) at 
bugs.freedesktop.org.

Thanks,
-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2009-01-12 17:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <621d098f0901110546p2b99a525k5de54e37fa181197@mail.gmail.com>
2009-01-11 13:51 ` intel kms "Failed to allocate space for kernel memory manager" Jan Dittmer
2009-01-11 21:21   ` Diego Calleja
2009-01-11 21:39     ` Dave Airlie
2009-01-11 22:04       ` Diego Calleja
2009-01-12  7:42       ` Jan Dittmer
2009-01-12  8:04         ` Dave Airlie
2009-01-12  8:37           ` Jan Dittmer
2009-01-12 17:56             ` Jesse Barnes [this message]
2009-01-12 18:30               ` Diego Calleja
2009-01-12 21:19               ` Jan Dittmer
2009-01-12 21:33                 ` Jan Dittmer
2009-01-12 21:53                 ` Jesse Barnes
2009-01-12 22:08                   ` Jan Dittmer
2009-01-12 22:29                     ` Jan Dittmer
2009-01-12 23:19                       ` Jesse Barnes
2009-01-12 13:03           ` Olivier Galibert
2009-01-12 17:53             ` Jesse Barnes
2009-01-12 21:32               ` Olivier Galibert
2009-01-12 21:59                 ` Jesse Barnes

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=200901120956.31728.jbarnes@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=airlied@gmail.com \
    --cc=airlied@linux.ie \
    --cc=diegocg@gmail.com \
    --cc=eric.anholt@iintel.com \
    --cc=jdi@l4x.org \
    --cc=linux-kernel@vger.kernel.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