From: DervishD <lkml@dervishd.net>
To: James Simmons <jsimmons@infradead.org>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: tdfx framebuffer garbles display in 2.6.19.5
Date: Mon, 26 Feb 2007 18:04:41 +0100 [thread overview]
Message-ID: <20070226170441.GA13496@DervishD> (raw)
In-Reply-To: <Pine.LNX.4.64.0702261520420.27244@pentafluge.infradead.org>
Hi James :)
* James Simmons <jsimmons@infradead.org> dixit:
> > From time to time, the tdfxfb driver from 2.6.19.5 (sorry, I cannot
> > test in 2.6.20.x because it doesn't compile, the infamous BDF negative
> > offset problem) garbles the display, leaving only a lot of thin lines,
> > just like sync was lost. The display can be repaired by switching to
> > another console, but this is annoying. This happens with a Voodoo 3
> > 3000, using 800x600x8@100 mode.
> >
> > Anyone has this problem? Can it be solved changing anything?
>
> Does not compile? Can you post the compile error. For my setup it does
> compile.
I think I didn't explain it well: the tdfxfb driver compiles, but
the *kernel* doesn't. At link time the linker warns about a negative
offset being used and building stops. The driver itself builds perfectly
as far as I can tell.
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736 | http://www.dervishd.net
It's my PC and I'll cry if I want to... RAmen!
prev parent reply other threads:[~2007-02-26 17:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070226144744.GA3615@DervishD>
2007-02-26 15:24 ` tdfx framebuffer garbles display in 2.6.19.5 Antonino A. Daplas
2007-02-26 17:13 ` DervishD
2007-02-26 17:24 ` Antonino A. Daplas
2007-02-26 20:32 ` DervishD
2007-02-27 23:09 ` Antonino A. Daplas
2007-02-28 10:49 ` DervishD
2007-03-01 16:01 ` DervishD
2007-03-06 1:33 ` Antonino A. Daplas
2007-03-06 6:25 ` DervishD
2007-03-06 6:53 ` Antonino A. Daplas
2007-03-06 11:17 ` DervishD
2007-03-07 10:02 ` DervishD
2007-03-14 9:06 ` [TESTED] " DervishD
2007-02-26 15:24 ` James Simmons
2007-02-26 17:04 ` DervishD [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=20070226170441.GA13496@DervishD \
--to=lkml@dervishd.net \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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).