From: "Buttchereit, Axel (XL)" <XL@XLsigned.net>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: James Simmons <jsimmons@www.infradead.org>,
James Simmons <jsimmons@pentafluge.infradead.org>,
sylvain.meyer@worldonline.fr
Subject: Re: [PATCH] sysfs support for fbdev
Date: Fri, 04 Mar 2005 20:48:08 +0100 [thread overview]
Message-ID: <4228BB78.2090703@XLsigned.net> (raw)
In-Reply-To: <4228AE13.8050202@worldonline.fr>
Sylvain Meyer wrote:
> Axel Buttchereit did a patch to implement it. It should be in the
> latest mm tree.
>
> Jon Smirl a écrit:
>
>> On Fri, 4 Mar 2005 18:26:57 +0000 (GMT), James Simmons
>> <jsimmons@www.infradead.org> wrote:
>>
>>
>>>> Doesn't the i830/i915/etc require a user space helper to change modes
>>>> since that part of the chip spec hasn't been released? The user space
>>>> helper would use Int10 VBIOS calls to list and set the modes. I
>>>> haven't worked with these chips, so this is just based off from what
>>>> has been posted to dri-devel. Is this why we don't have fbdev drivers
>>>> for these chips?
>>>>
>>>
>>> drivers/intel/*.[ch]
>>>
>>> No user space helper there.
>>>
>>>
>>>
>>
>> What about the i915? We don't seem to have a fbdev driver for it yet.
>>
It is (intelfb-...). Including Tony's corresponding "modehelper" kernel-config
patch and -- since 2.6.11-rc5-mm1 -- with an additional patch from Andrew
that fixes some compiler warnings (missing type casts).
The driver is still not complete (no hardware cursor, ...) but it
does its job pretty good (at least on my machine).
Only a few changes are required to add support for i915 and they
can all easily be derived from the xorg/xfree-driver that already
(fully) supports the chipset.
Obviously there is someone at xfree/xorg that is either a "hell of a hacker"
or in the position to access the required documentation from intel.
Or both.
:-) Axel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-04 19:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-01 10:00 [PATCH] sysfs support for fbdev Jon Smirl
2005-03-01 21:11 ` James Simmons
2005-03-02 18:13 ` Jon Smirl
2005-03-03 0:12 ` James Simmons
2005-03-03 0:57 ` Jon Smirl
2005-03-07 18:05 ` James Simmons
2005-03-07 18:10 ` Jon Smirl
2005-03-04 4:08 ` Jon Smirl
2005-03-04 18:26 ` James Simmons
2005-03-04 18:48 ` Jon Smirl
2005-03-04 18:50 ` Sylvain Meyer
2005-03-04 19:48 ` Buttchereit, Axel (XL) [this message]
2005-03-04 18:43 ` Sylvain Meyer
2005-03-04 18:50 ` Jon Smirl
2005-03-04 18:54 ` Sylvain Meyer
2005-03-01 23:49 ` Benjamin Herrenschmidt
2005-03-02 1:05 ` James Simmons
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=4228BB78.2090703@XLsigned.net \
--to=xl@xlsigned.net \
--cc=jsimmons@pentafluge.infradead.org \
--cc=jsimmons@www.infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=sylvain.meyer@worldonline.fr \
/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).