From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: Pierfrancesco Caci <pf@tippete.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.5.68] matroxfb still doesn't compile
Date: Mon, 21 Apr 2003 01:06:58 +0200 [thread overview]
Message-ID: <20030420230658.GA2583@ppc.vc.cvut.cz> (raw)
In-Reply-To: <87r87x2f6z.fsf@home.tippete.net>
On Sun, Apr 20, 2003 at 08:31:48PM +0200, Pierfrancesco Caci wrote:
>
> This error is still present:
> here it is:
>
> /usr/bin/make -f scripts/Makefile.build obj=drivers/video/matrox
> gcc -Wp,-MD,drivers/video/matrox/.matroxfb_base.o.d -D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=athlon -Iinclude/asm-i386/mach-default -fomit-frame-pointer -nostdinc -iwithprefix include -DKBUILD_BASENAME=matroxfb_base -DKBUILD_MODNAME=matroxfb_base -c -o drivers/video/matrox/.tmp_matroxfb_base.o drivers/video/matrox/matroxfb_base.c
> In file included from drivers/video/matrox/matroxfb_base.c:105:
Patch for 2.5.68 is at usual place
(ftp://platan.vc.cvut.cz/pub/linux/matrox-latest). I think that there
is regression in handling cursor on other heads than primary one,
but I can confirm it only on tuesday, as my current system has only
one video output.
I have no plans about submitting fixes to Linus, so please next time
before reporting problem try latest updates from my ftp. It is well
known that matroxfb does not build, and it will stay that way until
I'll get satisfied with quality of driver & interaction with fbdev
& fbcon level. I think that it is better to have no driver than
driver without cursor...
Best regards,
Petr Vandrovec
prev parent reply other threads:[~2003-04-20 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-20 18:31 Pierfrancesco Caci
2003-04-20 23:06 ` Petr Vandrovec [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=20030420230658.GA2583@ppc.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=pf@tippete.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
all inboxes | Powered by JetHome®