linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Hans-Jürgen Koch" <hjk@linutronix.de>
To: Wanda <wanda@cryosphere.shacknet.nu>
Cc: linux-fbdev-devel@lists.sourceforge.net, xorg@lists.freedesktop.org
Subject: Re: Radeon X300, radeonfb, dual head
Date: Thu, 19 Apr 2007 10:44:06 +0200	[thread overview]
Message-ID: <200704191044.07083.hjk@linutronix.de> (raw)
In-Reply-To: <46272535.5040303@cryosphere.shacknet.nu>

Am Donnerstag, 19. April 2007 10:15 schrieb Wanda:
> 
> Hello,
> 
> i had the same issue about fifo timeout. You certainly get very random
> refresh of the screen too if you activate dri. That is not a Xorg bug
> but rather a radeonfb one. It comes from radeonfb_accel.c, if i remember
> well. Just try and read the patch i send to the list (thread "radeonfb
> doesn't work with an ati X800 pcie", file: radeon_accel.c.2.6.20.diff) 
> Also, you will certainly need all the xxx.c.2.6.20.diff as well. You
> will find them in the april archive. If that doesn't help you try luca's
> one + aty.patch (same thread) In that case you are integrated a bunch of
> xorg code in radeonfb :). Luca's patch isn't compatible with mine except
> when applyed with aty.patch. I need it for my card, otherwise it doesn't
> work. But it could be incompatible with your card. Luca's patch still
> generates 2 *.rej file. You can install them manually and very easily by
> reading the rej file.
> 
> If nothing works for you , you have certainly a legacy instead an atom
> bios. In that case most of the patches won't help you. But keep trying.
> I get finally my x800  working with them. xorg and radeonfb work now
> together without a problem. Indeed, i don't have black screens or screen
> corruptions any more ;)

Hi,
thanks for your hints. But at the moment, I'd be lucky if I could get xorg
working with dual head even without radeonfb. It would be nice if I could
have a framebuffer console, though. Is one of these patches about to get
in mainline? I (have to) work with new kernels all the time, so it would 
be quite inconvenient if I had to apply (and maintain) an out-of-tree
patch every time I compile a new kernel.

If one of these patches looks acceptable for the fb-devel folks, I'm
willing to review, test, and submit updated patches if it works.

Thanks,
Hans

  parent reply	other threads:[~2007-04-19  8:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-18 12:09 Radeon X300, radeonfb, dual head Hans-Jürgen Koch
2007-04-18 12:58 ` Jerome Glisse
2007-04-18 13:26   ` Hans-Jürgen Koch
2007-04-18 13:45 ` Michel Dänzer
2007-04-18 15:02   ` [Linux-fbdev-devel] " Hans-Jürgen Koch
2007-04-18 21:20     ` Hans-Jürgen Koch
2007-04-18 21:45       ` Alex Deucher
2007-04-19  7:00         ` Hans-Jürgen Koch
2007-04-19  6:04       ` Michel Dänzer
2007-04-19  8:35 ` Jimmy Jazz
     [not found] ` <46272535.5040303@cryosphere.shacknet.nu>
2007-04-19  8:44   ` Hans-Jürgen Koch [this message]
2007-04-20 21:54 ` Radeon X300, radeonfb, dual head - conclusion Hans-Jürgen Koch

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=200704191044.07083.hjk@linutronix.de \
    --to=hjk@linutronix.de \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=wanda@cryosphere.shacknet.nu \
    --cc=xorg@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).