OpenCloudOS-Kernel/drivers/staging/sm750fb
Timo A. Aranjo dbd8c64947 Staging: sm750fb: Fix basic coding style issues
The word "enought" was changed to read as "enough".
In addition to this, there was a missing new-line after varaible
declarations within a function.

Signed-off-by: Timo A. Aranjo <timo.aranjo@aol.com>
Link: https://lore.kernel.org/r/20200826012101.12162-1-timo.aranjo@aol.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2020-08-28 12:19:15 +02:00
..
Kconfig docs: kbuild: convert docs to ReST and rename to *.rst 2019-06-14 14:21:21 -06:00
Makefile staging: sm750fb: Fix of long line in makefile variable 2020-03-19 15:11:35 +01:00
TODO staging: sm750fb: add drm development branch details 2018-05-06 18:51:38 -07:00
ddk750.h staging: sm750fb: fix odd license text 2019-08-15 14:43:57 +02:00
ddk750_chip.c staging: sm750fb: Remove set but not used variable 'actual_mx_clk' 2019-10-08 14:52:56 +02:00
ddk750_chip.h staging: sm750fb: CHECK: Avoid CamelCase 2019-09-30 21:57:56 +02:00
ddk750_display.c staging: sm750fb: Fix lines over 80 characters 2019-10-15 18:45:11 +02:00
ddk750_display.h staging: sm750fb: Eliminate camel case 2019-03-20 07:50:35 +01:00
ddk750_dvi.c staging: sm750fb: Edit CamelCase in local variables 2019-03-18 07:05:22 +01:00
ddk750_dvi.h Staging/IIO patches for 4.15-rc1 2017-11-13 20:53:28 -08:00
ddk750_hwi2c.c
ddk750_hwi2c.h
ddk750_mode.c staging: sm750fb: Fix lines over 80 characters 2019-10-15 18:45:11 +02:00
ddk750_mode.h staging: sm750fb: Remove typedefs from enums 2018-02-16 15:41:27 +01:00
ddk750_power.c Staging/IIO patches for 4.15-rc1 2017-11-13 20:53:28 -08:00
ddk750_power.h staging: sm750fb: Eliminate camel case 2019-03-20 07:50:35 +01:00
ddk750_reg.h
ddk750_sii164.c staging: sm750fb: align arguments with open parenthesis in ddk750_sii164.c 2019-10-24 23:11:27 -04:00
ddk750_sii164.h staging: sm750fb: Fix lines over 80 characters 2019-10-15 18:45:11 +02:00
ddk750_swi2c.c staging: sm750fb: fix odd license text 2019-08-15 14:43:57 +02:00
ddk750_swi2c.h staging: sm750fb: fix odd license text 2019-08-15 14:43:57 +02:00
readme
sm750.c Staging: sm750fb: Fix basic coding style issues 2020-08-28 12:19:15 +02:00
sm750.h staging: sm750fb: Add names to proc_setBLANK args 2020-05-29 12:35:59 +02:00
sm750_accel.c staging: sm750fb: Replace multiple spaces with tabs when it suits 2019-10-30 10:38:47 +01:00
sm750_accel.h staging: sm750fb: align arguments with open parenthesis in file sm750_accel.h 2019-10-24 23:11:27 -04:00
sm750_cursor.c Staging/IIO patches for 4.15-rc1 2017-11-13 20:53:28 -08:00
sm750_cursor.h staging: sm750fb: align arguments with open parenthesis in file sm750_cursor.h 2019-10-24 23:11:27 -04:00
sm750_hw.c staging: sm750fb: Make function arguments alignment match open parenthesis 2020-04-16 12:33:03 +02:00

readme

Introduction:
	SM750 of Silicon MOtion is pci express display controller device.
	The SM750 embedded graphics features include:
	- dual display
	- 2D acceleration
	- 16MB integrated video memory

About the kernel module parameter of driver:

	Use 1280,8bpp index color and 60 hz mode:
	insmod ./sm750fb.ko g_option="1280x1024-8@60"

	Disable MTRR,Disable 2d acceleration,Disable hardware cursor,
	and use a 800x600 mode :
	insmod ./sm750fb.ko g_option="noaccel:nomtrr:nohwc:800x600"

	dual frame buffer for driver with "dual" parameter
	insmod ./sm750fb.ko g_option="dual,800x600:1024x768"
	it will create fb0 and fb1 (or fb1,fb2 if fb0 already exist) under /dev
	and user can use con2fb to link fbX and ttyX

	Notes:
	1) if you build the driver with built-in method, the parameter
		you edited in the grub config file will be also the
		same format as above modular method,but additionally add
		"video=sm750fb:"
		ahead of parameters,so,it looks like:
		video=sm750fb:noaccel,1280x1024@60,otherparam,etc...
		it equal to modular method with below command:
		insmod ./sm750fb.ko g_option="noaccel:1280x1024@60:otherparm:etc..."

	2) if you put 800x600 into the parameter without bpp and
		refresh rate, kernel driver will defaulty use 16bpp and 60hz

Important:
	if you have vesafb enabled in your config then /dev/fb0 will be created by vesafb
	and this driver will use fb1, fb2. In that case, you need to configure your X-server
	to use fb1. Another simple althernative is to disable vesafb from your config.