From: Gabriel C <nix.or.die@googlemail.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Gabriel C <crazy@frugalware.org>,
linux-fbdev-devel@lists.sourceforge.net,
Wang Zhenyu <zhenyu.z.wang@intel.com>,
"Antonino A. Daplas" <adaplas@gmail.com>,
Dave Airlie <airlied@linux.ie>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: intelfb and G33 / Q33 / Q35 chipsets support ?
Date: Mon, 05 May 2008 22:59:31 +0200 [thread overview]
Message-ID: <481F7533.6070503@googlemail.com> (raw)
In-Reply-To: <200805050938.54453.jbarnes@virtuousgeek.org>
Jesse Barnes wrote:
> On Tuesday, April 29, 2008 7:16 pm Gabriel C wrote:
>>>> See the modesetting-101 branch of
>>>> git://git.freedesktop.org/git/mesa/drm. It's a bit rough in spots but
>>>> the i915 driver should be pretty close to feature parity with the Intel
>>>> X driver at this point.
>>> Thx , I will try out the tree.
>> modesetting-101 does not compile on current git , NOPAGE_SIGBUS , nopage
>> and friends gone.
>
> Yeah the DRM tree doesn't have a full kernel included, so it'll occasionally
> be out-of-sync. You could try a different kernel version (it almost always
> works with the last stable release of Linux) or merging DRM master into
> modesetting-101. Assuming there are no conflicts that might also fix
> things. :)
Hehe yes , I noticed :)
I've fixed myself local but it died later with:
WARNING: "i2c_bit_add_bus" [/work/git/drm/linux-core/i915.ko] undefined!
I didn't got time to investigate this one.
>
> Jesse
>
Gabriel
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
next prev parent reply other threads:[~2008-05-05 20:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 15:35 intelfb and G33 / Q33 / Q35 chipsets support ? Gabriel C
2008-04-28 5:47 ` Arjan van de Ven
2008-04-28 19:18 ` Dave Airlie
2008-04-29 1:24 ` Gabriel C
2008-04-29 18:04 ` Jesse Barnes
2008-04-29 23:05 ` Gabriel C
2008-04-30 2:16 ` Gabriel C
2008-05-05 16:38 ` Jesse Barnes
2008-05-05 20:59 ` Gabriel C [this message]
2008-05-05 21:11 ` Jesse Barnes
2008-05-05 22:55 ` Gabriel C
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=481F7533.6070503@googlemail.com \
--to=nix.or.die@googlemail.com \
--cc=adaplas@gmail.com \
--cc=airlied@linux.ie \
--cc=crazy@frugalware.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zhenyu.z.wang@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).