From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Petr Vandrovec <vandrove@vc.cvut.cz>,
linux-fbdev@vuser.vu.union.edu, linux-kernel@vger.kernel.org,
geert@linux-m68k.org
Subject: Re: [linux-fbdev] [PATCH] matroxfb as a module (PPC)
Date: Wed, 3 Jan 2001 19:25:22 MET-1 [thread overview]
Message-ID: <118A418518B3@vcnet.vc.cvut.cz> (raw)
On 3 Jan 01 at 10:54, Tom Rini wrote:
> I agree this sounds good. I just think it's too late to do it now. :)
>
> The vmode/cmode/vesa number stuff should stick around in 2.4 (it's too late
> now to remove it) but documented as obsolete, and removed in 2.5.
I personally prefer 'video=matrox:vesa:0x105' over
'video=matrox:1024x768-8', as with matroxfb you can modify this mode with
'left', 'right', 'fv', 'fh'... options, and without these parameters it is
unusable on fixed sync monitors (f.e. 'sync' is vital to specify
sync-on-green feature).
If someone will create modedb, which will allow specifying all parameters
of fb_var_screeninfo, I'll remove this parsing code from matroxfb. But
without it I think that 'vesa' will survive forever... And as I can test
only vga16fb and matroxfb, I'm not probably right one to do this.
Best regards,
Petr Vandrovec
vandrove@vc.cvut.cz
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-03 18:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-03 19:25 Petr Vandrovec [this message]
2001-01-03 22:24 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2001-01-03 16:16 Tom Rini
2001-01-03 17:44 ` [linux-fbdev] " Geert Uytterhoeven
2001-01-03 17:54 ` Tom Rini
2001-01-03 22:21 ` Geert Uytterhoeven
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=118A418518B3@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev@vuser.vu.union.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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
all inboxes | Powered by JetHome®