Documentation/fb/sm712fb.rst

File Facts

System

Linux kernel

Corpus path

Documentation/fb/sm712fb.rst

Extension

.rst

Size

983 bytes

Lines

36

Domain

Support Tooling And Documentation

Bucket

Documentation

Inferred role

Support Tooling And Documentation: documentation

Status

atlas-only

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

• Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Dependency Surface

• No C-style include directives detected by the generator.

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

==========================================================
sm712fb - Silicon Motion SM712 graphics framebuffer driver
==========================================================

This is a graphics framebuffer driver for Silicon Motion SM712 based processors.

How to use it?
==============

Switching modes is done using the video=sm712fb:... boot parameter.

If you want, for example, enable a resolution of 1280x1024x24bpp you should
pass to the kernel this command line: "video=sm712fb:0x31B".

You should not compile-in vesafb.

Currently supported video modes are:

Graphic modes
-------------

===  =======  =======  ========  =========
bpp  640x480  800x600  1024x768  1280x1024
===  =======  =======  ========  =========
  8  0x301    0x303    0x305     0x307
 16  0x311    0x314    0x317     0x31A
 24  0x312    0x315    0x318     0x31B
===  =======  =======  ========  =========

Missing Features
================
(alias TODO list)

	* 2D acceleration
	* dual-head support

Annotation

• Atlas domain: Support Tooling And Documentation / Documentation.
• Implementation status: atlas-only.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.