<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux.git/drivers/staging/udlfb, branch v2.6.37</title>
<subtitle>Linux kernel source tree</subtitle>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/'/>
<entry>
<title>Staging: udlfb: fix up my fixup for some sysfs attribute permissions</title>
<updated>2010-11-18T19:27:19+00:00</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@suse.de</email>
</author>
<published>2010-11-18T19:21:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=926c11151e3b82e4facbf2bd2bea15f0ca0ac6f9'/>
<id>926c11151e3b82e4facbf2bd2bea15f0ca0ac6f9</id>
<content type='text'>
They should be writable by root, not readable.
Doh, stupid me with the wrong flags.

Reported-by: Jonathan Cameron &lt;jic23@cam.ac.uk&gt;
Cc: Bernie Thompson &lt;bernie@plugable.com&gt;
Cc: stable &lt;stable@kernel.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
They should be writable by root, not readable.
Doh, stupid me with the wrong flags.

Reported-by: Jonathan Cameron &lt;jic23@cam.ac.uk&gt;
Cc: Bernie Thompson &lt;bernie@plugable.com&gt;
Cc: stable &lt;stable@kernel.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Staging: udlfb: fix up some sysfs attribute permissions</title>
<updated>2010-11-16T19:21:36+00:00</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@suse.de</email>
</author>
<published>2010-11-16T19:21:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=cc9ca9dfddda46b1802d325891a69d7efdbe1f1e'/>
<id>cc9ca9dfddda46b1802d325891a69d7efdbe1f1e</id>
<content type='text'>
They should not be writable by any user

Reported-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Cc: Bernie Thompson &lt;bernie@plugable.com&gt;
Cc: stable &lt;stable@kernel.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
They should not be writable by any user

Reported-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Cc: Bernie Thompson &lt;bernie@plugable.com&gt;
Cc: stable &lt;stable@kernel.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Staging: udlfb.c: Fix k.alloc switched arguments</title>
<updated>2010-11-09T22:05:24+00:00</updated>
<author>
<name>Joe Perches</name>
<email>joe@perches.com</email>
</author>
<published>2010-10-31T22:33:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=31a9f47aa081292d1c750002724aa23b3bd44bb8'/>
<id>31a9f47aa081292d1c750002724aa23b3bd44bb8</id>
<content type='text'>
Signed-off-by: Joe Perches &lt;joe@perches.com&gt;
Cc: Bernie Thompson &lt;bernie@plugable.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Signed-off-by: Joe Perches &lt;joe@perches.com&gt;
Cc: Bernie Thompson &lt;bernie@plugable.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>staging: udlfb: fix checkpatch and style</title>
<updated>2010-09-06T02:46:14+00:00</updated>
<author>
<name>Bernie Thompson</name>
<email>bernie@plugable.com</email>
</author>
<published>2010-09-06T01:29:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=2685cffa9e799278cdbfa5f524dd9e548be6598d'/>
<id>2685cffa9e799278cdbfa5f524dd9e548be6598d</id>
<content type='text'>
Fix warnings detected by tools

Signed-off-by: Bernie Thompson &lt;bernie@plugable.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Fix warnings detected by tools

Signed-off-by: Bernie Thompson &lt;bernie@plugable.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>staging: udlfb: fix incorrect fb_defio implementation for multiple framebuffers</title>
<updated>2010-09-06T02:45:59+00:00</updated>
<author>
<name>Bernie Thompson</name>
<email>bernie@plugable.com</email>
</author>
<published>2010-09-06T01:28:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=5bea1fbf942363e4114a086aefc67cdca21be7f0'/>
<id>5bea1fbf942363e4114a086aefc67cdca21be7f0</id>
<content type='text'>
Fix fb_defio bug in udlfb for multiple framebuffers

Previously when using fb_defio with multiple DisplayLink attached displays
udlfb incorrectly used a shared datastructure where it needed to have
one per fb_info struct. This was completely broken and caused all kinds of
problems, including rendering to one framebuffer affecting others.

Signed-off-by: Bernie Thompson &lt;bernie@plugable.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Fix fb_defio bug in udlfb for multiple framebuffers

Previously when using fb_defio with multiple DisplayLink attached displays
udlfb incorrectly used a shared datastructure where it needed to have
one per fb_info struct. This was completely broken and caused all kinds of
problems, including rendering to one framebuffer affecting others.

Signed-off-by: Bernie Thompson &lt;bernie@plugable.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>staging: udlfb: add module options for console and fb_defio</title>
<updated>2010-09-05T23:50:22+00:00</updated>
<author>
<name>Bernie Thompson</name>
<email>bernie@plugable.com</email>
</author>
<published>2010-09-05T23:35:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=d5ed54322e54d48e5fa66dff0086b79211f1cde7'/>
<id>d5ed54322e54d48e5fa66dff0086b79211f1cde7</id>
<content type='text'>
Add module options for console and fb_defio

Convert fb_defio on/off switch to module option and add console option.

&gt;From the command line, pass options to modprobe
modprobe udlfb defio=1 console=1

Or for permanent option, create file like /etc/modprobe.d/options with text
options udlfb defio=1 console=1

Accepted options:

fb_defio	Make use of the fb_defio (CONFIG_FB_DEFERRED_IO) kernel
		module to track changed areas of the framebuffer by page faults.
        	Standard fbdev applications that use mmap but that do not
		report damage, may be able to work with this enabled.
		Disabled by default because of overhead and other issues.

console		Allow fbcon to attach to udlfb provided framebuffers. This
		is disabled by default because fbcon will aggressively consume
		the first framebuffer it finds, which isn't usually what the
		user wants in the case of USB displays.

Signed-off-by: Bernie Thompson &lt;bernie@plugable.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Add module options for console and fb_defio

Convert fb_defio on/off switch to module option and add console option.

&gt;From the command line, pass options to modprobe
modprobe udlfb defio=1 console=1

Or for permanent option, create file like /etc/modprobe.d/options with text
options udlfb defio=1 console=1

Accepted options:

fb_defio	Make use of the fb_defio (CONFIG_FB_DEFERRED_IO) kernel
		module to track changed areas of the framebuffer by page faults.
        	Standard fbdev applications that use mmap but that do not
		report damage, may be able to work with this enabled.
		Disabled by default because of overhead and other issues.

console		Allow fbcon to attach to udlfb provided framebuffers. This
		is disabled by default because fbcon will aggressively consume
		the first framebuffer it finds, which isn't usually what the
		user wants in the case of USB displays.

Signed-off-by: Bernie Thompson &lt;bernie@plugable.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>staging: udlfb: support for writing backup EDID to sysfs file</title>
<updated>2010-09-05T23:50:21+00:00</updated>
<author>
<name>Bernie Thompson</name>
<email>bernie@plugable.com</email>
</author>
<published>2010-09-05T23:35:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=8ef8cc4fca4a92e77c0b5aa7a852a6c3d2fba844'/>
<id>8ef8cc4fca4a92e77c0b5aa7a852a6c3d2fba844</id>
<content type='text'>
Support writing default/backup edid via /sys/class/graphics/fb?/edid

Writing a backup edid blob to the 'edid' file will cause udlfb to
attempt to re-read the edid from hardware.
If we still don't have a good edid, it will use the backup edid instead.
The intent is to 1) enable user-supplied edid
2) enable udev rules to backup the last known good edid
for a device, and then provide that edid as a backup for all future starts

Signed-off-by: Bernie Thompson &lt;bernie@plugable.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Support writing default/backup edid via /sys/class/graphics/fb?/edid

Writing a backup edid blob to the 'edid' file will cause udlfb to
attempt to re-read the edid from hardware.
If we still don't have a good edid, it will use the backup edid instead.
The intent is to 1) enable user-supplied edid
2) enable udev rules to backup the last known good edid
for a device, and then provide that edid as a backup for all future starts

Signed-off-by: Bernie Thompson &lt;bernie@plugable.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>staging: udlfb: fix big endian rendering error</title>
<updated>2010-09-05T23:50:20+00:00</updated>
<author>
<name>Bernie Thompson</name>
<email>bernie@plugable.com</email>
</author>
<published>2010-09-05T23:35:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=1572f91cffd7c0d64ab4e0cec71e1d2d1a3349e1'/>
<id>1572f91cffd7c0d64ab4e0cec71e1d2d1a3349e1</id>
<content type='text'>
Fix big endian rendering bug (affects PowerPC)

Thanks to Christian Melki at Ericsson for finding and suggesting patch.

Signed-off-by: Bernie Thompson &lt;bernie@plugable.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Fix big endian rendering bug (affects PowerPC)

Thanks to Christian Melki at Ericsson for finding and suggesting patch.

Signed-off-by: Bernie Thompson &lt;bernie@plugable.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>staging: udlfb: enhance EDID and mode handling support</title>
<updated>2010-09-05T23:50:19+00:00</updated>
<author>
<name>Bernie Thompson</name>
<email>bernie@plugable.com</email>
</author>
<published>2010-09-05T23:35:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=18dffdf8913ab9e4ac7403a624879a15afa5262e'/>
<id>18dffdf8913ab9e4ac7403a624879a15afa5262e</id>
<content type='text'>
Enhance EDID and mode table handling

* Adds support for lower-end DL chips on higher-end monitors
* Adds support for using fbdev standard EDID parsing and handling
* Adds support for more dynamic reallocation of framebuffer, based on new EDID

Queries EDID from hardware with several retries then
queries DisplayLink chip for max pixel area via vendor descriptor.
Uses existing fbdev mode handling service funcations to build mode list
of common modes between adapter and monitor.
This enables lower-end chips (e.g. DL-125) to successfully pick a compatible
mode on higher end monitors (e.g. whose default mode is over 1280x1024).
Reallocate framebuffer if necessary in response to new max mode.

Signed-off-by: Bernie Thompson &lt;bernie@plugable.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Enhance EDID and mode table handling

* Adds support for lower-end DL chips on higher-end monitors
* Adds support for using fbdev standard EDID parsing and handling
* Adds support for more dynamic reallocation of framebuffer, based on new EDID

Queries EDID from hardware with several retries then
queries DisplayLink chip for max pixel area via vendor descriptor.
Uses existing fbdev mode handling service funcations to build mode list
of common modes between adapter and monitor.
This enables lower-end chips (e.g. DL-125) to successfully pick a compatible
mode on higher end monitors (e.g. whose default mode is over 1280x1024).
Reallocate framebuffer if necessary in response to new max mode.

Signed-off-by: Bernie Thompson &lt;bernie@plugable.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>staging: udlfb: revamp reference handling to insure successful shutdown</title>
<updated>2010-09-05T23:50:18+00:00</updated>
<author>
<name>Bernie Thompson</name>
<email>bernie@plugable.com</email>
</author>
<published>2010-09-05T23:35:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=33077b8d3042e01da61924973e372abe589ba297'/>
<id>33077b8d3042e01da61924973e372abe589ba297</id>
<content type='text'>
Revamp reference handling and synchronization for unload/shutdown

Udlfb is a "virtual" framebuffer device that really exists on
two separate stacks: at the bottom of the framebuffer interface,
and on top of USB.  During unload, there's no guarantee which
one will tear down first. So reference counting must be solid
to handle all possibilities and not access anything once its gone.

Signed-off-by: Bernie Thompson &lt;bernie@plugable.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Revamp reference handling and synchronization for unload/shutdown

Udlfb is a "virtual" framebuffer device that really exists on
two separate stacks: at the bottom of the framebuffer interface,
and on top of USB.  During unload, there's no guarantee which
one will tear down first. So reference counting must be solid
to handle all possibilities and not access anything once its gone.

Signed-off-by: Bernie Thompson &lt;bernie@plugable.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</pre>
</div>
</content>
</entry>
</feed>
