From: Keith Owens <kaos@ocs.com.au>
To: "-=da TRoXX=-" <TRoXX@LiquidXTC.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Framebuffer as a module
Date: Sat, 06 Jan 2001 18:41:25 +1100 [thread overview]
Message-ID: <18019.978766885@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Fri, 05 Jan 2001 18:52:45 BST." <000d01c07740$516a30e0$fd1942c3@bluescreen>
On Fri, 5 Jan 2001 18:52:45 +0100,
"-=da TRoXX=-" <TRoXX@LiquidXTC.nl> wrote:
>I have a very simple question:
>I used to compile-in my framebuffer-device in the kernel
>then i just appended "video=tdfxfb:1024x768-32@70" in lilo.conf and it
>worked..
>
>now i compiled it as a module, and want modprobe to start it up for me..
>how can this be done?
>modprobe tdfxfb 1024x768-32@70
>won't work, because there is no '=' sign in it so modprobe doesn't recognize
>it as a parameter, and doesn't pass it.
A quick look at drivers/video/tdfxfb.c shows a complete lack of
MODULE_PARM entries so modprobe/insmod will not let specify any
parameters. Ask the tdfxfb author to add this feature, or code it
yourself.
-
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 prev parent reply other threads:[~2001-01-06 7:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-05 17:52 Framebuffer as a module -=da TRoXX=-
2001-01-06 7:41 ` Keith Owens [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-05 16:05 [PATCH] VESA framebuffer w/ MTRR locks 2.4.0 on init Alan Cox
2001-01-06 1:20 ` [PATCH] VESA framebuffer w/MTRR " David Wragg
2001-01-06 17:28 ` Framebuffer as a module Bryan Mayland
[not found] ` <002501c07819$21343900$fd1942c3@bluescreen>
2001-01-06 20:04 ` Bryan Mayland
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=18019.978766885@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=TRoXX@LiquidXTC.nl \
--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