From: Gabriel C <nix.or.die@googlemail.com>
To: Dave Airlie <airlied@linux.ie>
Cc: Gabriel C <crazy@frugalware.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fbdev-devel@lists.sourceforge.net,
"Antonino A. Daplas" <adaplas@gmail.com>,
Wang Zhenyu <zhenyu.z.wang@intel.com>
Subject: Re: intelfb and G33 / Q33 / Q35 chipsets support ?
Date: Tue, 29 Apr 2008 03:24:22 +0200 [thread overview]
Message-ID: <481678C6.7050400@googlemail.com> (raw)
In-Reply-To: <alpine.DEB.0.82.0804282016440.5277@skynet.skynet.ie>
Dave Airlie wrote:
> On Mon, 28 Apr 2008, Gabriel C wrote:
>
>> Hello ,
>>
>> are there any plans to add G33 / Q33 / Q35 chipsets support for the intelfb driver ?
>> Is this driver still maintained ?
>>
>> ( I'm not really sure who maintains this driver so I've add peoples to CC I saw worked on it ,
>> I've also added Wang Zhenyu to CC while he added this support for AGP )
>>
>
> Intel fb is unmaintained (well I've done trivial fixes in the past), and
> I'd rather not add new chipset support to it.
>
> We are working (RH and Intel) on a new kernel modesetting layer which will
> allow fbs integrated with proper memory management and support all intel
> hw,
Good news :)
Are there any patch(es) / git tree one could try out ?
>
> The main problem with intelfb is it trips up the userspace X drivers a lot
> and generally break things..
Really ? I didn't knew that.
>
> Dave.
Gabriel
next prev parent reply other threads:[~2008-04-29 1:24 UTC|newest]
Thread overview: 16+ 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 [this message]
2008-04-29 18:04 ` Jesse Barnes
2008-04-29 18:04 ` Jesse Barnes
2008-04-29 23:05 ` Gabriel C
2008-04-29 23:05 ` Gabriel C
2008-04-30 2:16 ` Gabriel C
2008-04-30 2:16 ` Gabriel C
2008-05-05 16:38 ` Jesse Barnes
2008-05-05 20:59 ` Gabriel C
2008-05-05 20:59 ` Gabriel C
2008-05-05 21:11 ` Jesse Barnes
2008-05-05 22:55 ` Gabriel C
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=481678C6.7050400@googlemail.com \
--to=nix.or.die@googlemail.com \
--cc=adaplas@gmail.com \
--cc=airlied@linux.ie \
--cc=crazy@frugalware.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 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.