[Libdlo] udlfb 0.4.0

[Bernie Thompson]

Hi Greg,

No problem.  Working through the essential todos will take a few
releases and some time -- so we just need to find a way where the work
can keep going on a daily basis, and can get versioned somewhere,
while still generating tested patches in a format that works for the
staging tree.

This release is built off the most current staging tree, so
http://git.plugable.com/gitphp/index.php?p=udlfb&a=commitdiff&h=bd4d6c6592b8a2c55aa9676c97f169bccb1ffa2c
should patch cleanly -- assuming quilt is ok with patching a
subdirectory. Please let me know if that won't work.

I'll exchange more emails with you 1-1 until we have a smooth way of
handling this.  I'll modify whatever I'm doing to meet the needs of
staging, since the whole point here is getting that moving forward.

Thanks!
Bernie

On Wed, Nov 11, 2009 at 7:04 PM, Greg KH <greg at kroah.com> wrote:
> On Wed, Nov 11, 2009 at 11:21:39AM -0800, Bernie Thompson wrote:
>> This is a new release of the DisplayLink kernel framebuffer driver, udlfb.
>>
>> udlfb was accepted into the Linux kernel staging tree of 2.6 a few
>> months ago. It needs some work to add key features and get it promoted
>> out of the staging tree. Roberto De Iorio, the author of udlfb and
>> displaylink-mod, is focusing on X server work, and is happy with this
>> work happening in parallel to move udlfb forward.
>>
>> This first release intentionally adds no fundamentally new features.
>> It only gets udlfb up to sync with the displaylink-mod branch (up to
>> Roberto?s last 0.3 release in July 2009) that has been in use the past
>> few months. With this update, displaylink-mod users should be able to
>> switch to this version of udlfb transparently.
>>
>> Bug reports are very welcome, especially regressions or problems that
>> would stand in the way of moving this driver forward out of staging
>> (comments on the post are fine for bug reports).  This is a
>> development release, but it should be stable for daily use.
>>
>> New in 0.4.0 (since 0.2.3 currently in the Linux kernel staging tree)
>
> Um, care to send me a patch to update the in-kernel version?  Doing this
> outside of the tree only causes maintance nightmares :)
>
> thanks,
>
> greg k-h
>