linux-toradex.git/drivers/char, branch v2.6.35.8

agp/intel: Fix cache control for Sandybridge

2010-10-29T04:51:44+00:00

commit f8f235e5bbf4e61f3e0886a44afb1dc4cfe8f337 upstream.

Sandybridge GTT has new cache control bits in PTE, which controls
graphics page cache in LLC or LLC/MLC, so we need to extend the mask
function to respect the new bits.

And set cache control to always LLC only by default on Gen6.

Signed-off-by: Zhenyu Wang 
Signed-off-by: Chris Wilson 
Signed-off-by: Greg Kroah-Hartman

virtio: console: Don't block entire guest if host doesn't read data

2010-10-29T04:51:39+00:00

commit 531295e63be8c2b8b909d7400739e8b8df60d61f upstream.

If the host is slow in reading data or doesn't read data at all,
blocking write calls not only blocked the program that called write()
but the entire guest itself.

To overcome this, let's not block till the host signals it has given
back the virtio ring element we passed it.  Instead, send the buffer to
the host and return to userspace.  This operation then becomes similar
to how non-blocking writes work, so let's use the existing code for this
path as well.

This code change also ensures blocking write calls do get blocked if
there's not enough room in the virtio ring as well as they don't return
-EAGAIN to userspace.

Signed-off-by: Amit Shah 
Acked-by: Hans de Goede 
Signed-off-by: Rusty Russell 
Signed-off-by: Linus Torvalds 
Signed-off-by: Greg Kroah-Hartman

char: Mark /dev/zero and /dev/kmem as not capable of writeback

2010-09-27T00:18:24+00:00

commit 371d217ee1ff8b418b8f73fb2a34990f951ec2d4 upstream.

These devices don't do any writeback but their device inodes still can get
dirty so mark bdi appropriately so that bdi code does the right thing and files
inodes to lists of bdi carrying the device inodes.

Signed-off-by: Jan Kara 
Signed-off-by: Jens Axboe 
Signed-off-by: Greg Kroah-Hartman

drm/i915,agp/intel: Add second set of PCI-IDs for B43

2010-09-27T00:18:23+00:00

commit 41a51428916ab04587bacee2dda61c4a0c4fc02f upstream.

There is a second revision of B43 (a desktop gen4 part) floating around,
functionally equivalent to the original B43, so simply add the new
PCI-IDs.

Bugzilla: https://bugs.freedesktop.org/show_bugs.cgi?id=30221
Signed-off-by: Chris Wilson 
Signed-off-by: Greg Kroah-Hartman

agp/intel: fix dma mask bits on sandybridge

2010-09-27T00:18:21+00:00

[This is backport patch from upstream 877fdacf.]

Signed-off-by: Zhenyu Wang 
Signed-off-by: Greg Kroah-Hartman

agp/intel: fix physical address mask bits for sandybridge

2010-09-27T00:18:21+00:00

[This is backport patch from upstream 8dfc2b14.]

Signed-off-by: Zhenyu Wang 
Signed-off-by: Greg Kroah-Hartman

intel_agp, drm/i915: Add all sandybridge graphics devices support

2010-09-27T00:18:21+00:00

New pci ids for all sandybridge graphics versions on desktop/mobile/server.

[This is backport patch from upstream commit 4fefe435 and 85540480.]

Signed-off-by: Zhenyu Wang 
Signed-off-by: Greg Kroah-Hartman

virtio: console: Fix poll blocking even though there is data to read

2010-09-27T00:18:20+00:00

commit 6df7aadcd9290807c464675098b5dd2dc9da5075 upstream.

I found this while working on a Linux agent for spice, the symptom I was
seeing was select blocking on the spice vdagent virtio serial port even
though there were messages queued up there.

virtio_console's port_fops_poll checks port->inbuf != NULL to determine
if read won't block. However if an application reads enough bytes from
inbuf through port_fops_read, to empty the current port->inbuf,
port->inbuf will be NULL even though there may be buffers left in the
virtqueue.

This causes poll() to block even though there is data to be read,
this patch fixes this by using will_read_block(port) instead of the
port->inbuf != NULL check.

Signed-off-By: Hans de Goede 
Signed-off-by: Amit Shah 
Signed-off-by: Rusty Russell 
Signed-off-by: Greg Kroah-Hartman

virtio: console: Prevent userspace from submitting NULL buffers

2010-09-27T00:18:20+00:00

commit 65745422a898741ee0e7068ef06624ab06e8aefa upstream.

A userspace could submit a buffer with 0 length to be written to the
host.  Prevent such a situation.

This was not needed previously, but recent changes in the way write()
works exposed this condition to trigger a virtqueue event to the host,
causing a NULL buffer to be sent across.

Signed-off-by: Amit Shah 
Signed-off-by: Rusty Russell 
Signed-off-by: Greg Kroah-Hartman

agp/intel: Promote warning about failure to setup flush to error.

2010-09-20T20:36:47+00:00

commit df51e7aa2cf204e3a65657a1d60b96cfda133e9b upstream.

Make sure we always detect when we fail to correctly allocate the Isoch
Flush Page and print an error to warn the user about the likely memory
corruption that will result in invalid rendering or worse.

Signed-off-by: Chris Wilson 
Signed-off-by: Greg Kroah-Hartman