20 Dec, 2011
1 commit
-
This API will be used to support YUV frame buffer formats in a standard
way.Last but not least, create a much needed fbdev API documentation and
document the format setting APIs.Signed-off-by: Laurent Pinchart
Signed-off-by: Florian Tobias Schandinat
24 Aug, 2011
3 commits
-
Signed-off-by: Bernie Thompson
Signed-off-by: Florian Tobias Schandinat -
Enables page fault based detection of mmap writes to the framebuffer,
which allows standard fbdev apps (like the generic fbdev xorg driver)
to work on DisplayLink devices.Not all bugs are shaken out of the fb_defio path of udlfb, but it's
tantalizingly close, so this seems a good time to enable by default.Alternatively, option can be disabled when running with an xorg driver
that can more directly communicate damaged regions of the framebuffer
via IOCTL. This is a simpler, higher perf option, when available.Signed-off-by: Bernie Thompson
Signed-off-by: Florian Tobias Schandinat -
By default, udlfb allocates a 2nd buffer to shadow what's across
the bus on the USB device. It can operate without this shadow,
but then it cannot tell which pixels have changed, and must send all.Saves host memory, but worsens the USB 2.0 bus bottleneck.
This option allows users in very low memory situations (e.g.
bifferboard) to optionally turn off this shadow framebuffer.Signed-off-by: Stuart Hopkins
Signed-off-by: Bernie Thompson
Signed-off-by: Florian Tobias Schandinat
25 Jul, 2011
1 commit
-
The video= parameter of the DRM drivers supports some additional flags that
the normal fb drivers do not have. They also allow to limit these flags to
specific outputs. Both things were previously undocumented.Also the parsing of the line had some oddities:
-A lot of misplaced options were silently ignored or partly rejected instead
of stopping the parsing immediately
-The 'R' option is documented to follow the 'M' option if specified. It is not
documented that 'M' is needed to specify 'R' (also this is the case for normal
fb drivers). In fact the code is correct for normal fb drivers but wrong for
DRM ones.
The old code allowed 'R' only _before_ 'M' (since it parses backwards) and only
if 'M' is given at all which is not needed for the DRM drivers.
-the margins option ('m') was parsed but later ignored even if the later
functions support it.
-specifying multiple enable options at the same time did not lead to an error.
-specifying something bogus for horizontal resolution (i.e. other things as
digits) did not lead to an error but an invalid resolution was used.If any errors are encountered the position of the faulting string is now
printed to the user and the complete mode is ignored. This gives much
more consistent error behaviour.I also removed some useless assignments and changed the local flag variables
to be bool.Signed-off-by: Rolf Eike Beer
Signed-off-by: Dave Airlie
31 Mar, 2011
1 commit
-
Fixes generated by 'codespell' and manually reviewed.
Signed-off-by: Lucas De Marchi
22 Mar, 2011
1 commit
-
- add commandline options:
sm501fb.mode:
Specify resolution as "x[-][@]"
sm501fb.bpp:
Specify bit-per-pixel if not specified mode- Add support for encoding display mode information
in the device tree using verbatim EDID block.If the "edid" entry in the "smi,sm501" node is present,
the driver will build mode database using EDID data
and allow setting the display modes from this database.Signed-off-by: Heiko Schocher
cc: linux-fbdev@vger.kernel.org
cc: devicetree-discuss@ozlabs.org
cc: Ben Dooks
cc: Vincent Sanders
cc: Samuel Ortiz
cc: linux-kernel@vger.kernel.org
cc: Randy Dunlap
cc: Paul Mundt
Signed-off-by: Paul Mundt
06 Jan, 2011
1 commit
18 Nov, 2010
1 commit
-
This is a simple update of the file Documentation/fb/00-INDEX based on
the directory content.Signed-off-by: Vicente Jimenez Aguilar
Signed-off-by: Paul Mundt
16 Nov, 2010
1 commit
-
udlfb has undergone a fair bit of cleanup recently and is effectively at
the point where it can be liberated from staging purgatory and promoted
to a real driver.The outstanding cleanups are all minor, with some of them dependent on
drivers/video headers, so these will be done incrementally from udlfb's
new home.Requested-by: Bernie Thompson
Signed-off-by: Paul Mundt
28 Oct, 2010
1 commit
-
* 'viafb-next' of git://github.com/schandinat/linux-2.6: (29 commits)
viafb: add initial VX900 support
viafb: fix hardware acceleration for suspend & resume
viafb: make suspend and resume work (on all machines?)
viafb: restore display on resume
Minimal support for viafb suspend/resume
viafb: use proper register for colour when doing fill ops
viafb: add documentation for proc interface
viafb: rename output devices
viafb: add a mapping of supported output devices
viafb: set sync polarity for all output devices
viafb: add function to change sync polarity per device
viafb: reduce I2C timeout and delay
viafb: enable I2C for CRT
viafb: fix i2c_transfer error handling
viafb: vt1636 cleanup
viafb: introduce per output device power management
viafb: limit LCD code impact
viafb: add interface for output device configuration
viafb: merge the remaining output path with enable functions
viafb: use new device routing
...
24 Sep, 2010
1 commit
-
This patch adds documentation for the new proc interface that allows
modification of the output device configuration. Should be stable and
useful enough now for daily use.Signed-off-by: Florian Tobias Schandinat
Acked-by: Jonathan Corbet
Cc: Joseph Chan
Cc: Andrew Morton
04 Aug, 2010
1 commit
-
Below you will find an updated version from the original series bunching all patches into one big patch
updating broken web addresses that are located in Documentation/*
Some of the addresses date as far far back as 1995 etc... so searching became a bit difficult,
the best way to deal with these is to use web.archive.org to locate these addresses that are outdated.
Now there are also some addresses pointing to .spec files some are located, but some(after searching
on the companies site)where still no where to be found. In this case I just changed the address
to the company site this way the users can contact the company and they can locate them for the users.Signed-off-by: Justin P. Mattock
Signed-off-by: Thomas Weber
Signed-off-by: Mike Frysinger
Cc: Paulo Marques
Cc: Randy Dunlap
Cc: Michael Neuling
Signed-off-by: Jiri Kosina
07 Apr, 2010
1 commit
-
Rename imacfb.txt to efifb.txt since imacfb was moved to efifb,and change
imacfb to efifb.Signed-off-by: Justin P. Mattock
Cc: Geert Uytterhoeven
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
16 Dec, 2009
1 commit
-
We now support the VX855, and the VX800 is no longer unaccellerated.
viafb_video_dev was removed as it was useless.Signed-off-by: Harald Welte
Signed-off-by: Florian Tobias Schandinat
Cc: Joseph Chan
Cc: Scott Fang
Cc: Krzysztof Helt
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
01 Dec, 2009
1 commit
-
The fbdev mailing lists at SourceForge have been migrated to a single
mailing list at kernel.org: linux-fbdev@vger.kernel.org.Signed-off-by: Geert Uytterhoeven
Acked-by: Jean Delvare
Signed-off-by: Linus Torvalds
23 Sep, 2009
2 commits
-
I would like to get rid of option CONFIG_FB_MATROX_MULTIHEAD and just
always enable it. There are many reasons for doing this:* CONFIG_FB_MATROX_MULTIHEAD=y is what all x86 distributions do, so it
definitely works or we would know by now.* Building the matroxfb driver with CONFIG_FB_MATROX_MULTIHEAD not set
results in the following build warning:drivers/video/matrox/matroxfb_crtc2.c: In function 'matroxfb_dh_open':
drivers/video/matrox/matroxfb_crtc2.c:265: warning: the address of 'matroxfb_global_mxinfo' will always evaluate as 'true'
drivers/video/matrox/matroxfb_crtc2.c: In function 'matroxfb_dh_release':
drivers/video/matrox/matroxfb_crtc2.c:285: warning: the address of 'matroxfb_global_mxinfo' will always evaluate as 'true'This is nothing to be worried about, the driver will work fine, but build
warnings are still annoying.* The trick to get multihead support without CONFIG_FB_MATROX_MULTIHEAD,
which is described in the config help text, no longer works: you can't
load the same kernel module more than once.* I fail to see how CONFIG_FB_MATROX_MULTIHEAD=y would make the code
significantly slower, contrary to what the help text says. A few extra
parameters on the stack here and there can't really slow things down in
comaprison to the rest of the code, and register access.* The driver built without CONFIG_FB_MATROX_MULTIHEAD is larger than the
driver build with CONFIG_FB_MATROX_MULTIHEAD=y by 8%.* One less configuration option makes things simpler. We add options
all the time, being able to remove one for once is nice. It improves
testing coverage. And I don't think the Matrox adapters are still
popular enough to warrant overdetailed configuration settings.* We should be able to unobfuscate the driver code quite a bit after
this change (patches follow.)Signed-off-by: Jean Delvare
Acked-by: Petr Vandrovec
Cc: Krzysztof Helt
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
EP93xx video driver plus documentation.
Signed-off-by: Ryan Mallon
Acked-by: H Hartley Sweeten
Cc: Daniele Venzano
Cc: Russell King
Cc: Krzysztof Helt
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
17 Jun, 2009
1 commit
-
Signed-off-by: Paul Menzel
Cc: Gerd Knorr
Cc: Nico Schmoigl
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
13 Jun, 2009
1 commit
-
Fix various typos in documentation txts.
Signed-off-by: Matt LaPlante
Signed-off-by: Jiri Kosina
07 Apr, 2009
1 commit
-
Update the uvesafb documentation to accurately reflect the default options
used by the driver.Signed-off-by: Michal Januszewski
Cc: Krzysztof Helt
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
01 Apr, 2009
1 commit
-
A tridentfb driver has all the functionality of the cyblafb driver without
the bugs of the latter.Changes to the tridentfb driver:
- FBINFO_READS_FAST added to the tridentfb. The cyblafb used a blitter
for scrolling which is faster than color expansion on Cyberblade
chipsets. The blitter is slower on a discrete Blade3D core. Use the
blitter for scrolling in the tridentfb only for integrated Blade3D
cores. Now, scrolling speed is about equal for the tridentfb and the
cyblafb.- a copyright notice addition is done on request of Jani Monoses (the
first author of the tridentfb).Tested on AGP Blade3D card and PCChips
M787CLR motherboard: VIA C3 cpu +
VT8601 north bridge (aka Cyberblade/i1).Signed-off-by: Krzysztof Helt
Cc: "Jani Monoses"
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
29 Dec, 2008
2 commits
-
PXA27x and later processors support overlay1 and overlay2 on-top of the
base framebuffer (although under-neath the base is also possible). They
support palette and no-palette RGB formats, as well as YUV formats (only
available on overlay2). These overlays have dedicated DMA channels and
behave in a similar way as a framebuffer.This heavily simplified and re-structured work is based on the original
pxafb_overlay.c (which is pending for mainline merge for a long time).The major problems with this pxafb_overlay.c are (if you are interested
in the history):1. heavily redundant (the control logics for overlay1 and overlay2 are
actually identical except for some small operations, which are now
abstracted into a 'pxafb_layer_ops' structure)2. a lot of useless and un-tested code (two workarounds which are now
fixed on mature silicons)3. cursorfb is actually useless, hardware cursor should not be used
this way, and the code was actually un-tested for a long time.The code in this patch should be self-explanatory, I tried to add minimum
comments. As said, this is basically simplified, there are several things
still on the pending list:1. palette mode is un-supported and un-tested (although re-using the
palette code of the base framebuffer is actually very easy now with
previous clean-up patches)2. fb_pan_display for overlay(s) is un-supported
3. the base framebuffer can actually be abstracted by 'pxafb_layer' as
well, which will help further re-use of the code and keep a better
and consistent structure. (This is the reason I named it 'pxafb_layer'
instead of 'pxafb_overlay' or something alike)See Documentation/fb/pxafb.txt for additional usage information.
Signed-off-by: Eric Miao
Cc: Rodolfo Giometti
Signed-off-by: Eric Miao -
The amount of video memory size is decided according to the following
order:1. x x by default, which is the backward
compatible way2. size specified in platform data
3. size specified in module parameter 'options' string or specified in
kernel boot command line (see updated Documentation/fb/pxafb.txt)And now since the memory is allocated from system memory, the pxafb_mmap
can be removed and the default fb_mmap() should be working all right.Also, since we now have introduced the 'struct pxafb_dma_buff' for DMA
descriptors and palettes, the allocation can be separated cleanly.NOTE: the LCD DMA actually supports chained transfer (i.e. page-based
transfers), to simplify the logic and keep the performance (with less
TLB misses when accessing from memory mapped user space), the memory
is allocated by alloc_pages_*() to ensures it's physical contiguous.Signed-off-by: Eric Miao
Signed-off-by: Eric Miao
17 Oct, 2008
3 commits
-
Document the change from the old "mode" parameter to the "mode_option"
parameter.Signed-off-by: Mike Pagano
Cc: Krzysztof Halasa
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
Add support for Intel's 945GME graphics chip to the intelfb driver. I
have assumed that the 945GME is identical to the already-supported 945GM
apart from its PCI IDs; this is based on a quick look at the X driver for
these chips which seems to treat them identically.The 945GME is used in the ASUS Eee 901, and I coded this in the hope that
I'd be able to use it to get a console at the native 1024x600 resolution
which is not known to the BIOS. I realised too late that the intelfb
driver does not support mode changing on laptops, so it won't be any
use for me.Signed-off-by: Phil Endecott
Acked-by: Krzysztof Helt
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
Correct via_fb_ to viafb_ and remove the Kconfig part in viafb.txt.
viafb.modes: supported mode table
viafb.txt: documentation of viafb driverSigned-off-by: Joseph Chan
Cc: Krzysztof Helt
Cc: Geert Uytterhoeven
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
25 Jul, 2008
2 commits
-
Framebuffer driver for the SH7760/SH7763 integrated LCD controller.
Signed-off-by: Manuel Lauss
Signed-off-by: Nobuhiro Iwamatsu
Reviewed-by: Paul Mundt
Cc: Krzysztof Helt
Cc: "Antonino A. Daplas"
Cc: Siegfried Schaefer
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
Make the tridentfb documentation closer to current state of the tridentfb
driver. Fix also some formatting.Signed-off-by: Krzysztof Helt
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
28 Apr, 2008
7 commits
-
Add support for the 965G and 965GM graphic chipsets to the intelfb driver. I
have a notebook with an Intel Mobile GM965/GL960 Integrated Graphics
Controller and with the attached patch the framebuffer comes up. I have
tested it a bit with DirectFB to make sure it is working stable.I also have an Intel Mobile GM945 and I compared the results, the programming
interface of the 9xx series from Intel is mostly the same, so I think the
patch should add all the functionality which the 945GM has.Signed-off-by: Maik Broemme
Cc: Dave Airlie
Cc: Antonino Daplas
Cc: Geert Uytterhoeven
Cc: Krzysztof Halasa
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
This patch splits metronomefb into the platform independent metronomefb and
the platform dependent am200epd.Signed-off-by: Jaya Kumar
Cc: "Antonino A. Daplas"
Cc: Geert Uytterhoeven
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
By default disable VT switch, but allow it to be overridden via the
'vt_switch' module arg.Signed-off-by: Andres Salomon
Cc: "Antonino A. Daplas"
Cc: Jordan Crouse
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
Match other fb drivers (including gxfb). Also, document the current boot
arguments in Documentation/fb/lxfb.txt.Signed-off-by: Andres Salomon
Cc: "Antonino A. Daplas"
Cc: Jordan Crouse
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
Add names of drivers converted to "mode_option" parameter.
This is one step toward changing all fb drivers to have common "mode_option"
parameter.Signed-off-by: Krzysztof Helt
Cc: "Antonino A. Daplas"
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
Prior to suspend, we allocate and switch to a new VT; after suspend, we switch
back to the original VT. This can be slow, and is completely unnecessary if
the framebuffer we're using can restore video properly.This adds a hook that allows drivers to select whether or not to do this vt
switch, and changes the gxfb driver to call this hook. It also adds a module
param to gxfb to allow controlling of the vt switch (defaulting to no switch).(Note: I'm not convinced that console_sem is the best way to protect this, but
we should probably have some form of locking..)[akpm@linux-foundation.org: build fix]
Signed-off-by: Andres Salomon
Cc: Jordan Crouse
Cc: "Antonino A. Daplas"
Cc: Pavel Machek
Cc: "Rafael J. Wysocki"
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
Use a command line option (vram) rather than hardcoding the vram size. LxFB
already does this; it's useful for machines that can't query the BIOS for fb
size. This patch originated from David Woodhouse, was modified by Jordan
Crouse, and was then modified further by me.This also adds some gxfb documentation in Documentation/fb.
Signed-off-by: Andres Salomon
Cc: Jordan Crouse
Cc: "Antonino A. Daplas"
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
20 Mar, 2008
1 commit
-
Implement support for the E-Ink Metronome controller. It provides an mmapable
interface to the controller using defio support. It was tested with a gumstix
pxa255 with Vizplex media using Xfbdev and various X clients such as xeyes,
xpdf, xloadimage.This patch also fixes the following bug: Defio would cause a hang on write
access to the framebuffer as the page fault would be called ad-infinitum. It
fixes fb_defio by setting the mapping to be used by page_mkclean.Signed-off-by: Jaya Kumar
Cc: "Antonino A. Daplas"
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
07 Feb, 2008
1 commit
-
Convert fb defio from nopage to fault.
Switch from OOM to SIGBUS if the resource is not available.Signed-off-by: Nick Piggin
Cc: "Antonino A. Daplas"
Cc: Paul Mundt
Cc: Jaya Kumar
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
20 Oct, 2007
1 commit
-
Most of these fixes were already submitted for old kernel versions, and were
approved, but for some reason they never made it into the releases.Because this is a consolidation of a couple old missed patches, it touches both
Kconfigs and documentation texts.Signed-off-by: Matt LaPlante
Acked-by: Randy Dunlap
Signed-off-by: Adrian Bunk
17 Oct, 2007
1 commit
-
An update to Documentation/fb/00-INDEX is long overdue. This patch adds
entries for new files in the directory and removes entries for files that no
longer exist. The files are now also sorted alphabetically.Signed-off-by: Jesper Juhl
Signed-off-by: Antonino Daplas
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
