From: Paul Mundt <lethal@linux-sh.org>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] drivers/video/udlfb bind framebuffer to interface.
Date: Wed, 13 Jul 2011 08:17:53 +0000 [thread overview]
Message-ID: <20110713081752.GD13701@linux-sh.org> (raw)
In-Reply-To: <1309910651-3483-1-git-send-email-bernie@plugable.com>
On Tue, Jul 05, 2011 at 05:04:11PM -0700, bernie@plugable.com wrote:
> Udlfb has been binding the framebuffer device to its parent, which
> isn't correct and causes confusion with operations like udev remove.
>
> Coming plug and play multiseat support is dependent on this fix.
>
> Signed-off-by: Bernie Thompson <bernie@plugable.com>
On Sun, Jul 10, 2011 at 12:30:00AM -0700, bernie@plugable.com wrote:
> Match udlfb only against vendor-specific class (e.g. only DisplayLink
> graphics, not composite standard audio class interfaces). This enables
> compatibility with composite graphics+audio devices (e.g. HDMI).
>
> Match udlfb only against compatible subclass 0 and protocol 0 chips.
> DisplayLink's USB 3.0 generation chips increment these values
> to signal that they have a incompatible protocol, preventing udlfb
> from erroneously matching to hardware it does not support.
>
> Tested to confirm proper behavior on both USB 2.0 and USB 3.0
> generation devices.
>
> Reported-by: Andrew Kephart <akephart@akephart.org>
> Signed-off-by: Bernie Thompson <bernie@plugable.com>
Both queued for 3.0, thanks.
prev parent reply other threads:[~2011-07-13 8:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 0:04 [PATCH] drivers/video/udlfb bind framebuffer to interface bernie
2011-07-11 4:26 ` JinGoo Han
2011-07-13 8:17 ` Paul Mundt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110713081752.GD13701@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-fbdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).