<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/video, branch v3.0</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v3.0</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v3.0'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2011-07-04T07:02:48Z</updated>
<entry>
<title>vesafb: fix memory leak</title>
<updated>2011-07-04T07:02:48Z</updated>
<author>
<name>Daniel J Blueman</name>
<email>daniel.blueman@gmail.com</email>
</author>
<published>2011-06-27T23:08:53Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=3e86f1d8e397b1ef59a97910089e16a99e8f31f7'/>
<id>urn:sha1:3e86f1d8e397b1ef59a97910089e16a99e8f31f7</id>
<content type='text'>
When releasing framebuffer, free colourmap allocations.

Signed-off-by: Daniel J Blueman &lt;daniel.blueman@gmail.com&gt;
Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>fbdev: amba: Link fb device to its parent</title>
<updated>2011-06-24T08:11:50Z</updated>
<author>
<name>Loïc Minier</name>
<email>loic.minier@linaro.org</email>
</author>
<published>2011-06-20T20:44:17Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=17e8c4e1ebf139743e3830439fa65fd906af4a43'/>
<id>urn:sha1:17e8c4e1ebf139743e3830439fa65fd906af4a43</id>
<content type='text'>
Some pieces of userspace like debian-installer expect to find the fb0
driver name by readlink-ing /sys/class/graphics/fb0/device/driver but
this was broken with amba-clcd as it sets up fb_info manually and missed
the .device parent pointer.

Signed-off-by: Loïc Minier &lt;loic.minier@linaro.org&gt;
Cc: Russell King &lt;linux@arm.linux.org.uk&gt;
Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>fsl-diu-fb: remove check for pixel clock ranges</title>
<updated>2011-06-24T08:08:49Z</updated>
<author>
<name>Timur Tabi</name>
<email>timur@freescale.com</email>
</author>
<published>2011-06-23T20:20:26Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=39785eb1d3e6c58cc8bf8f6990956a58037ecc75'/>
<id>urn:sha1:39785eb1d3e6c58cc8bf8f6990956a58037ecc75</id>
<content type='text'>
The Freescale DIU framebuffer driver defines two constants, MIN_PIX_CLK and
MAX_PIX_CLK, that are supposed to represent the lower and upper limits of
the pixel clock.  These values, however, are true only for one platform
clock rate (533MHz) and only for the MPC8610.  So the actual range for
the pixel clock is chip-specific, which means the current values are almost
always wrong.  The chance of an out-of-range pixel clock being used are also
remote.

Rather than try to detect an out-of-range clock in the DIU driver, we depend
on the board-specific pixel clock function (e.g. p1022ds_set_pixel_clock)
to clamp the pixel clock to a supported value.

Signed-off-by: Timur Tabi &lt;timur@freescale.com&gt;
Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>udlfb: Correct sub-optimal resolution selection.</title>
<updated>2011-06-24T08:08:44Z</updated>
<author>
<name>William Katsak</name>
<email>william.katsak@alcatel-lucent.com</email>
</author>
<published>2011-06-23T13:16:29Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=9377c51752970c305fae29ac634501fde44378cb'/>
<id>urn:sha1:9377c51752970c305fae29ac634501fde44378cb</id>
<content type='text'>
The situation in which the problem occurred was with a Plugable UGA-2K-A
connected to a Samsung EX2220X display. The driver indicates that
1920x1080 is a valid mode (the first mode available, in fact), but
proceeds to set the framebuffer size to 1600x1200.

The patch corrects what seems to be a logic error, regarding unsetting
the FB_MISC_1ST_DETAIL flag, if the first (top/best) mode is invalid.
The existing code unset the flag if ANY mode was invalid.

Signed-off-by: William Katsak &lt;william.katsak@alcatel-lucent.com&gt;
Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>Merge branch 'common/fbdev-meram' of git://git.kernel.org/pub/scm/linux/kernel/git/lethal/sh-3.x into fbdev-fixes-for-linus</title>
<updated>2011-06-24T08:00:57Z</updated>
<author>
<name>Paul Mundt</name>
<email>lethal@linux-sh.org</email>
</author>
<published>2011-06-24T08:00:57Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=2bceec57fa7d660dffd4fbe423d84411cafb1acf'/>
<id>urn:sha1:2bceec57fa7d660dffd4fbe423d84411cafb1acf</id>
<content type='text'>
</content>
</entry>
<entry>
<title>hecubafb: add module_put on error path in hecubafb_probe()</title>
<updated>2011-06-24T08:00:39Z</updated>
<author>
<name>Pavel Shved</name>
<email>shved@ispras.ru</email>
</author>
<published>2011-06-17T16:25:12Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=291600193e5c0c3f0a9af1f23a8076dd7417c02a'/>
<id>urn:sha1:291600193e5c0c3f0a9af1f23a8076dd7417c02a</id>
<content type='text'>
In hecubafb_probe(), after a successful try_module_get, vzalloc may
fail and make the hecubafb_probe return, but the module is not put on
this error path.

This patch adds an exit point that calls module_put in such situation.

Found by Linux Driver Verification project (linuxtesting.org).

Signed-off-by: Pavel Shved &lt;shved@ispras.ru&gt;
Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>sm501fb: fix section mismatch warning</title>
<updated>2011-06-24T08:00:35Z</updated>
<author>
<name>Randy Dunlap</name>
<email>randy.dunlap@oracle.com</email>
</author>
<published>2011-06-16T19:32:40Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=9845afc8fa32de145d56c8e69b7900e10371255d'/>
<id>urn:sha1:9845afc8fa32de145d56c8e69b7900e10371255d</id>
<content type='text'>
Fix section mismatch warning in sm501fb:

WARNING: drivers/video/sm501fb.o(.text+0x21d6): Section mismatch in reference from the function sm501fb_init_fb() to the variable .devinit.data:sm501_default_mode
The function sm501fb_init_fb() references
the variable __devinitdata sm501_default_mode.
This is often because sm501fb_init_fb lacks a __devinitdata
annotation or the annotation of sm501_default_mode is wrong.

Signed-off-by: Randy Dunlap &lt;randy.dunlap@oracle.com&gt;
Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>gx1fb: Fix section mismatch warnings</title>
<updated>2011-06-24T08:00:31Z</updated>
<author>
<name>Randy Dunlap</name>
<email>randy.dunlap@oracle.com</email>
</author>
<published>2011-06-16T19:31:19Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=3535ed3fa7a87244410696880000e03bc224315d'/>
<id>urn:sha1:3535ed3fa7a87244410696880000e03bc224315d</id>
<content type='text'>
Fix a chain of section mismatches in geode driver, beginning with:

WARNING: drivers/video/geode/gx1fb.o(.data+0x70): Section mismatch in reference from the variable gx1fb_driver to the function .init.text:gx1fb_probe()
The variable gx1fb_driver references
the function __init gx1fb_probe()
If the reference is valid then annotate the
variable with __init* or __refdata (see linux/init.h) or name the variable:
*_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console

Making the changes that Paul pointed out resulted in a few more
changes being needed, so they are all included here.

Signed-off-by: Randy Dunlap &lt;randy.dunlap@oracle.com&gt;
Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>fbdev: sh_mobile_meram: Correct pointer check for YCbCr chroma plane</title>
<updated>2011-06-24T07:40:28Z</updated>
<author>
<name>Damian Hobson-Garcia</name>
<email>dhobsong@igel.co.jp</email>
</author>
<published>2011-06-22T07:46:25Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=06c8a6a3e40265ff580428bbf51991617477f65b'/>
<id>urn:sha1:06c8a6a3e40265ff580428bbf51991617477f65b</id>
<content type='text'>
The check was intended to test if we have a valid pointer to write into,
but it mistakenly checks the pointer contents instead.

Since a valid pointer is mandatory for the chroma data if a YCbCr format
is used, the pointer check has been removed.

Signed-off-by: Damian Hobson-Garcia &lt;dhobsong@igel.co.jp&gt;
Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>Merge branch 'fbdev-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/lethal/fbdev-3.x</title>
<updated>2011-06-16T16:45:47Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2011-06-16T16:45:47Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=f4ef084226f82ca923bf0a2658bb2876bd215ec1'/>
<id>urn:sha1:f4ef084226f82ca923bf0a2658bb2876bd215ec1</id>
<content type='text'>
* 'fbdev-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/lethal/fbdev-3.x:
  fbdev: sh_mobile_hdmi: fix regression: statically enable RTPM
  fbdev/atyfb: Fix 2 defined-but-not-used warnings
  efifb: Fix call to wrong unregister function
  video: s3c-fb: move enabling channel for window
  video: s3c-fb: fix virtual resolution checking
  video: s3c-fb: fix misleading kfree in remove function
</content>
</entry>
</feed>
