linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Otto Solares <solca@guug.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: James Simmons <jsimmons@infradead.org>,
	Louis Garcia <louisg00@bellsouth.net>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: syncing to mainline kernel
Date: Thu, 9 Oct 2003 12:20:54 -0600	[thread overview]
Message-ID: <20031009182054.GB5249@guug.org> (raw)
In-Reply-To: <1065685406.7081.68.camel@gaston>

On Thu, Oct 09, 2003 at 09:43:26AM +0200, Benjamin Herrenschmidt wrote:
> 
> > Ben, i have problems with your new radeonfb driver, apart that i have
> > to update the pci_ids.h and r200.c in both stock 2.6 and your bk tree
> > to make work my radeon 9200 (rv280 Ya), in your new driver, spaces
> > becomes '_', and after a while all characteres get messy.  My normal
> > setup is 1024x768-32@75 but with your driver the only reliable mode is
> > 640x480-8@60.  Any idea?
> 
> Regarding PCI IDs, I'm changing that now, I decided to add a separate
> drivers/video/aty/ati_ids.h containing a copy of XFree ATI PCI IDs
> instead of using the include/linux/pci_ids.h one. That may see odd,
> but it helps a lot avoiding the merge problems and makes it easier
> to resync with XFree. This is already the case in my bk btw.

Good, adding new cards would become easy but i really like the pci_ids.h
approach as is a centralized db, it doesn't take much time to update
the driver to work with my card.

> Regarding your problem, I don't know what's up with spaces vs '_',
> that doesn't ring any bell to me, especially since there is no use
> of HW accel in this version, so the chars are really only drawn
> by the core fbdev layer.
>
> What do you mean by "reliable mode". What do you get when trying to
> use another mode ? It's normal that fbset doesn't work properly in
> 2.6, this is a known issue. What did you try and what result did you
> get ?

I can't set my fbdev to anything different than the booted mode 640x480-8@60,
trying anything else brings me a black screen or unsynched monitor,
i am using Jon's merged driver (benh+khronos) so probably is not your driver's
fault (but edid support is very tempting, although is not used because i'm
working now on an old monitor without ddc :), i will try your driver alone and
report back.

-solca



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php

  reply	other threads:[~2003-10-09 18:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-05  9:13 syncing to mainline kernel Louis Garcia
2003-10-08 14:31 ` Benjamin Herrenschmidt
2003-10-08 18:50   ` James Simmons
2003-10-08 18:53     ` Benjamin Herrenschmidt
2003-10-09  0:41       ` Otto Solares
2003-10-09  7:43         ` Benjamin Herrenschmidt
2003-10-09 18:20           ` Otto Solares [this message]
2003-10-09  4:51     ` Louis Garcia

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=20031009182054.GB5249@guug.org \
    --to=solca@guug.org \
    --cc=benh@kernel.crashing.org \
    --cc=jsimmons@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=louisg00@bellsouth.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 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).