From: "Bruno Prémont" <bonbons@linux-vserver.org>
To: <JosephChan@via.com.tw>
Cc: <linux-fbdev-devel@lists.sourceforge.net>,
<linux-kernel@vger.kernel.org>,
akpm@linux-foundation.org, geert@linux-m68k.org
Subject: Re: [Linux-fbdev-devel] [PATCH 1/13] viafb: viafb.modes, viafb.txt
Date: Mon, 30 Jun 2008 12:46:28 +0200 [thread overview]
Message-ID: <20080630124628.194b782f@neptune.home> (raw)
In-Reply-To: <C80EF34A3D2E494DBAF9AC29C7AE4EB8074E7705@exchtp03.taipei.via.com.tw>
On Mon, 30 June 2008 <JosephChan@via.com.tw> wrote:
> diff -Nur a/Documentation/fb/viafb.txt b/Documentation/fb/viafb.txt
> --- a/Documentation/fb/viafb.txt 1970-01-01 08:00:00.000000000
> +0800 +++ b/Documentation/fb/viafb.txt 2009-01-02 16:28:20.000000000 +0800
> [...]
> +[Using the viafb module]
> +-- -- --------------------
> + Start viafb with default settings:
> + #modprobe viafb
> +
> + Start viafb with with user options:
> + #modprobe viafb viafb_mode=800x600 via_fb_bpp=16 viafb_refresh=60
> + viafb_active_dev=CRT+DVI viafb_dvi_port=DVP1
> + viafb_mode1=1024x768 via_fb_bpp=16 viafb_refresh1=60
> + viafb_SAMM_ON=1
> +
> + viafb_mode:
> + 640x480 (default)
> + 720x480
> + 800x600
> + 1024x768
> + ......
> +
> + via_fb_bpp:
> + 8, 16, 32 (default:32)
> +
> + viafb_refresh:
> + 60, 75, 85, 100, 120 (default:60)
> +
> [...]
Is there a specific reason why some module options start with via_fb_
and others with viafb_?
> +[Building viafb as a built - in driver on Linux kernel 2.6.xx]
> +--------------------------------------------------------------
> + Step 1: Get kernel source and put them under /usr/src/linux
> + Step 2: Copy FBDev to proper location.
> + # cp -a FBDev /usr/src/linux/drivers/video/via
> + Step 3: Modify Makefile and Kconfig under /usr/src/linux/drivers/video:
> + add line to Makefile
> + "obj-$(CONFIG_FB_VIA) += via/"
> +
> + add below lines to Kconfig
> + config FB_VIA
> + tristate "VIA UniChrome (Pro) and Chrome9 display support"
> + depends on FB && PCI
> + select FB_CFB_FILLRECT
> + select FB_CFB_COPYAREA
> + select FB_CFB_IMAGEBLIT
> + select FB_SOFT_CURSOR
> +
> + help
> + This is the frame buffer device driver for Graphics
> + chips of VIA UniChrome Family(CLE266, PM800 / CN400 / CN300,
> + P4M800CE / P4M800Pro / CN700,
> + VN800 / CX700 / VX700, K8M890,
> + P4M890 / CN896 / P4M900, VX800)
> + Say Y if you have a VIA UniChrome graphics board. To compile
> + this driver as a module, choose M here: the module will be
> + called viafb.
This section can be dropped, the patch series aiming to merge viafb into
mainline tree. (the patch series does this already)
-
Bruno
next prev parent reply other threads:[~2008-06-30 10:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-30 6:31 [PATCH 1/13] viafb: viafb.modes, viafb.txt JosephChan
2008-06-30 10:46 ` Bruno Prémont [this message]
2008-07-01 1:17 ` [Linux-fbdev-devel] " JosephChan
2008-06-30 17:09 ` Geert Uytterhoeven
2008-07-01 1:12 ` JosephChan
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=20080630124628.194b782f@neptune.home \
--to=bonbons@linux-vserver.org \
--cc=JosephChan@via.com.tw \
--cc=akpm@linux-foundation.org \
--cc=geert@linux-m68k.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