From: Adrian Bunk <bunk@fs.tum.de>
To: Thomas Winischhofer <thomas@winischhofer.net>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, jsimmons@infradead.org
Subject: Re: 2.6.1-mm1: drivers/video/sis/sis_main.c link error
Date: Tue, 13 Jan 2004 20:04:43 +0100 [thread overview]
Message-ID: <20040113190443.GR9677@fs.tum.de> (raw)
In-Reply-To: <3FFF79E5.5010401@winischhofer.net>
On Sat, Jan 10, 2004 at 05:04:53AM +0100, Thomas Winischhofer wrote:
> Adrian Bunk wrote:
>
> > On Fri, Jan 09, 2004 at 01:40:03AM -0800, Andrew Morton wrote:
> >
> >> ...
> >> All 393 patches
> >> ...
> >> use-soft-float.patch
> >> Use -msoft-float
> >> ...
> >
> >
>
> I know. The version of sisfb in 2.6 vanilla is from stone-age. This is
> has been fixed a long time ago in my current development version (and
> will be in 2.4 as soon as Marcelo applies my patch which I sent him
> about a week ago). For 2.6, using my current version requires James
> Simmons's fbdev-patch because of low-level fbdev-interface changes (like
> sysfs usage, etc).
>
> The whole framebuffer stuff in 2.6 is ancient. (Look at the file dates.)
Until the framebuffer stuff in 2.6 gets updated, I'm suggesting the
patch below to mark FB_SIS as BROKEN.
> Thomas
cu
Adrian
--- linux-2.6.1-mm2/drivers/video/Kconfig.old 2004-01-13 20:02:28.000000000 +0100
+++ linux-2.6.1-mm2/drivers/video/Kconfig 2004-01-13 20:02:55.000000000 +0100
@@ -696,7 +696,7 @@
config FB_SIS
tristate "SIS acceleration"
- depends on FB && PCI
+ depends on FB && PCI && BROKEN
help
This is the frame buffer device driver for the SiS 630 and 640 Super
Socket 7 UMA cards. Specs available at <http://www.sis.com.tw/>.
next prev parent reply other threads:[~2004-01-13 19:04 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 9:40 2.6.1-mm1 Andrew Morton
2004-01-09 14:47 ` 2.6.1-mm1 Christoph Hellwig
2004-01-09 14:53 ` 2.6.1-mm1 Wojciech 'Sas' Cieciwa
2004-01-09 14:21 ` 2.6.1-mm1 Bartlomiej Zolnierkiewicz
2004-01-09 15:24 ` 2.6.1-mm1 (compile stats) John Cherry
2004-01-09 16:30 ` 2.6.1-mm1 Prakash K. Cheemplavam
2004-01-09 21:20 ` 2.6.1-mm1 Andrew Morton
2004-01-09 21:24 ` 2.6.1-mm1 Prakash K. Cheemplavam
2004-01-09 23:04 ` 2.6.1-mm1 - nforce2 timer patch sum up cheuche+lkml
2004-01-09 19:31 ` 2.6.1-mm1: sound/pci/cmipci.c compile error Adrian Bunk
2004-01-09 22:43 ` Andrew Morton
2004-01-09 23:37 ` 2.6.1-mm1: drivers/video/sis/sis_main.c link error Adrian Bunk
2004-01-10 4:04 ` Thomas Winischhofer
2004-01-12 2:58 ` Linus Torvalds
2004-01-12 4:53 ` Gene Heskett
2004-01-12 5:42 ` Andrew Morton
2004-01-12 6:11 ` Valdis.Kletnieks
2004-01-12 6:47 ` Gene Heskett
2004-01-12 7:05 ` Andrew Morton
2004-01-12 7:20 ` Gene Heskett
2004-01-12 12:38 ` Gene Heskett
2004-01-12 6:21 ` Gene Heskett
2004-01-12 6:34 ` Andrew Morton
2004-01-12 6:58 ` Gene Heskett
2004-01-12 7:03 ` Gene Heskett
2004-01-12 16:33 ` Dave Jones
2004-01-12 17:00 ` Gene Heskett
2004-01-12 17:04 ` Dave Jones
2004-01-12 8:58 ` Thomas Winischhofer
2004-01-12 14:32 ` Moritz Muehlenhoff
2004-01-12 10:36 ` Andrew Walrond
2004-01-13 19:04 ` Adrian Bunk [this message]
2004-01-14 0:35 ` Thomas Winischhofer
2004-01-15 11:32 ` Adrian Bunk
2004-01-15 11:42 ` Thomas Winischhofer
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=20040113190443.GR9677@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=akpm@osdl.org \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@winischhofer.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).