All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jimmy Jazz <Jimmy.Jazz@gmx.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: radeonfb doesn't work with an ati X800	pcie card
Date: Fri, 13 Apr 2007 11:04:33 +0200	[thread overview]
Message-ID: <461F47A1.5030606@gmx.net> (raw)
In-Reply-To: <1176329514.8061.106.camel@localhost.localdomain>

Benjamin Herrenschmidt a écrit :
> On Wed, 2007-04-11 at 14:17 +0200, Jimmy Jazz wrote:
>> Hello,
>>
>> i sent it without care and i forgot to add some diff files you will have 
>> to apply to radeonfb.h, ati_ids.h and radeon_base.c with both 
>> radeon_accel.c and radeon_monitor.c patches. Otherwise, you won't be 
>> able to compile the kernel anymore. Sorry for the inconvenient.
>>
>> Thank you all of you who contributed to these patches, the initiator of 
>> the radeonfb driver and of course the Xorg team who made ATI cards 
>> compatible with the xorg server.
> 
> There are already patches from Solomon for Atom BIOSes.
> 
> I admit that I never found the time to fully cleanup, split, test,
> etc... those along with other fixes I have in my queue. I could use a
> co-maintainer for radeonfb...
> 
> Ben.

Hello  Ben,

I would be happy to help you to improve ATI framebuffer driver but
really i have few knowlegdes about videocards. I followed the logic of
the program and compared it to the xorg version. Besides, it is sad that
xorg and kernel teams didn't follow the same code writing conventions.
Also, i tried to stay as near as possible with the original kernel
version without increasing the size of the binary code. Moreover, i'm a
bit lost about the notion of connectors and how they share s-video, dvi
and vga and why we need to invert them sometimes :). Really, it is
hardly explained and there is too much exceptions thru the source code
that make it difficult to understand what is a dirty hack and what is
not. Perhaps, i could bypass many difficulties just because my bios card
is "well programmed".


Jj

PS: I don't know if tables are used exclusively by laptops or if they
have atom bios too, so i didn't try to include code about it.



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

      parent reply	other threads:[~2007-04-13  9:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-27 15:49 radeonfb doesn't work with an ati X800 pcie card Jimmy Jazz
2007-03-27 16:58 ` Jimmy Jazz
2007-03-27 17:44   ` Alex Deucher
2007-03-28 19:24     ` Jimmy Jazz
2007-03-28 21:08 ` Jimmy Jazz
2007-03-28 21:42   ` Alex Deucher
2007-03-28 22:03 ` Jimmy Jazz
2007-03-28 22:26   ` Alex Deucher
2007-04-10 18:03 ` Jimmy Jazz
2007-04-11 12:17   ` Jimmy Jazz
2007-04-11 22:11     ` Benjamin Herrenschmidt
2007-04-12 23:38       ` Luca Tettamanti
2007-04-14 10:17         ` Jimmy Jazz
2007-04-13  9:04       ` Jimmy Jazz [this message]

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=461F47A1.5030606@gmx.net \
    --to=jimmy.jazz@gmx.net \
    --cc=benh@kernel.crashing.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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.