[Libdlo] Howto install displaylink drive with ubunut

[Face Man]

Tim,        for some reason  i could not Figure out howto post a readable email :)  therefore,  here is a link <a href="http://blogs.aldimna.com/?65a55cf2-3426-4447-b680-d51de33f8064">http://blogs.aldimna.com/?65a55cf2-3426-4447-b680-d51de33f8064</a>Sincerely, Face

> From: libdlo-request at lists.freedesktop.org

> Subject: Libdlo Digest, Vol 13, Issue 12

> To: libdlo at lists.freedesktop.org

> Date: Wed, 26 May 2010 12:00:08 -0700

> 

> Send Libdlo mailing list submissions to

> libdlo at lists.freedesktop.org

> 

> To subscribe or unsubscribe via the World Wide Web, visit

> http://lists.freedesktop.org/mailman/listinfo/libdlo

> or, via email, send a message with subject or body 'help' to

> libdlo-request at lists.freedesktop.org

> 

> You can reach the person managing the list at

> libdlo-owner at lists.freedesktop.org

> 

> When replying, please edit your Subject line so it is more specific

> than "Re: Contents of Libdlo digest..."

> 

> 

> Today's Topics:

> 

> 1. Re: Howto install displaylink drive with ubunut 10.04 (Tim Green)

> 2. Re: defio mmap issues (Bernie Thompson)

> 3. Re: defio mmap issues (Justin Hammond)

> 

> 

> ----------------------------------------------------------------------

> 

> Message: 1

> Date: Tue, 25 May 2010 20:18:38 +0100

> From: Tim Green <timothy.j.green at gmail.com>

> Subject: Re: [Libdlo] Howto install displaylink drive with ubunut

> 10.04

> To: libdlo <libdlo at lists.freedesktop.org>

> Message-ID:

> <AANLkTinDkYSGlKBH05U0AxugWxCxfJWBdBI2-ptQvAIj at mail.gmail.com>

> Content-Type: text/plain; charset=ISO-8859-1

> 

> Thanks for the tips, but could you post again with new line characters?

> 

> Regards,

> Tim.

> 

> On 25 May 2010 19:24, Face Man <solo9300 at hotmail.com> wrote:

>>

>> well,?? ?i ?really had problem getting my USB Display Adapter (Kensington Universal Multi-Display Adapter )?? to work and i hope this could help others.?? ??? ?Installation Guide?? ??? ?1- update your linux kernel to linux kernel 2.6.34?? ? ? ?open Terminal:?? ? ? ? ? ?cd ~/Desktop?? ? ? ? ? ?mkdir kernel-2.6.34?? ? ? ? ? ?cd kernel-2.6.34

> 

> 

> ------------------------------

> 

> Message: 2

> Date: Tue, 25 May 2010 12:50:52 -0700

> From: Bernie Thompson <bernie at plugable.com>

> Subject: Re: [Libdlo] defio mmap issues

> To: justin at dynam.ac, libdlo at lists.freedesktop.org

> Message-ID:

> <AANLkTimPijck7SJWxm4DsHdohAswl2tBgXxN_QJIp5rd at mail.gmail.com>

> Content-Type: text/plain; charset=UTF-8

> 

> Just an update on this problem (detail below) of horizontal artifacts

> with defio enabled in udlfb, and then using a standard (non-damage

> aware) mmap client like the generic fbdev X server ....

> 

> Others ran across these same problems in a different (non-DisplayLink)

> context, and are working on a fix. I've not tested these patches to

> defio yet, but they may resolve this issue

> 

> http://marc.info/?l=linux-fbdev&m=127369791432181

> 

> Note: There's some further discussion on the list, so this is likely

> not the final patch they'll run with. But it's great that there

> appears to be a fix on the horizon for this.

> 

> Best wishes,

> Bernie

> http://plugable.com/

> 

> On Wed, Jan 13, 2010 at 4:36 PM, Bernie Thompson <bernie at plugable.com> wrote:

>> On Mon, Jan 11, 2010 at 6:57 AM, <justin at dynam.ac> wrote:

>>>

>>> On a side note, and maybe for a latter email, I'm also getting horizontal

>>> artifacts on the screen after several hours of operations. Reading the

>>> archives, I saw someone else post on this, and there was a thought there

>>> was a race condition on the memmap. This is very reproducible for me

>>> (takes about 1 hour though) so if I can provide further info to help debug

>>> that, I'm willing to take on the challenge!

>>

>>

>> Here are some datapoints from trying to track down this issue:

>>

>> * The problem happens both with the latest udlfb from git.plugable.com, and

>> with jaya's original defio driver patch posted a few months back. So it

>> could be a problem carried forward, but it doesn't look like a new problem

>> ..

>> * It can be seen more frequently with faster processors and larger screens.

>> On my atom with 1920x1080, it's intermittent and small corruption.? On a

>> faster Celeron with 3 1680x1050 screens, it starts happening quickly with

>> any significant screen activity.

>> * And a fun one: on that multi-screen setup, once you get large areas of the

>> one screen (one DL device) to fail to render ... then moving the mouse and

>> triggering rendering on the *other* DL device/screen, for the corresponding

>> lines on the screen, refreshes the first device/screen properly (!)? Since

>> udlfb keeps no shared state between different DisplayLink devices,

>> apparently this confusion is happening at the defio/vma/page table level.

>>

>> Defio is used by several other framebuffer drivers, but perhaps not at these

>> resolutions and not for multiple screens.? Has anyone seen other evidence

>> that would support/contradict this being a general defio problem?? Or

>> perhaps something simple/stupid that udlfb is doing to trigger it?

>>

>> Thanks,

>> Bernie

>>

> 

> 

> ------------------------------

> 

> Message: 3

> Date: Wed, 26 May 2010 12:20:18 +0800

> From: Justin Hammond <justin at dynam.ac>

> Subject: Re: [Libdlo] defio mmap issues

> To: Bernie Thompson <bernie at plugable.com>

> Cc: "libdlo at lists.freedesktop.org" <libdlo at lists.freedesktop.org>

> Message-ID: <79C72CC3-66DB-4E03-81EB-DCDCE4A595E7 at dynam.ac>

> Content-Type: text/plain;	charset=us-ascii;	format=flowed;	delsp=yes

> 

> Hi Bernie,

> Thanks for the heads up. I'll do some testing and see how it goes.

> 

> Justin

> 

> On 26-May-2010, at 3:50 AM, Bernie Thompson <bernie at plugable.com> wrote:

> 

>> Just an update on this problem (detail below) of horizontal artifacts

>> with defio enabled in udlfb, and then using a standard (non-damage

>> aware) mmap client like the generic fbdev X server ....

>>

>> Others ran across these same problems in a different (non-DisplayLink)

>> context, and are working on a fix. I've not tested these patches to

>> defio yet, but they may resolve this issue

>>

>> http://marc.info/?l=linux-fbdev&m=127369791432181

>>

>> Note: There's some further discussion on the list, so this is likely

>> not the final patch they'll run with. But it's great that there

>> appears to be a fix on the horizon for this.

>>

>> Best wishes,

>> Bernie

>> http://plugable.com/

>>

>> On Wed, Jan 13, 2010 at 4:36 PM, Bernie Thompson 

>> <bernie at plugable.com> wrote:

>>> On Mon, Jan 11, 2010 at 6:57 AM, <justin at dynam.ac> wrote:

>>>>

>>>> On a side note, and maybe for a latter email, I'm also getting 

>>>> horizontal

>>>> artifacts on the screen after several hours of operations. Reading 

>>>> the

>>>> archives, I saw someone else post on this, and there was a thought 

>>>> there

>>>> was a race condition on the memmap. This is very reproducible for me

>>>> (takes about 1 hour though) so if I can provide further info to 

>>>> help debug

>>>> that, I'm willing to take on the challenge!

>>>

>>>

>>> Here are some datapoints from trying to track down this issue:

>>>

>>> * The problem happens both with the latest udlfb from git.plugable.com 

>>> , and

>>> with jaya's original defio driver patch posted a few months back. 

>>> So it

>>> could be a problem carried forward, but it doesn't look like a new 

>>> problem

>>> ..

>>> * It can be seen more frequently with faster processors and larger 

>>> screens.

>>> On my atom with 1920x1080, it's intermittent and small corruption. 

>>> On a

>>> faster Celeron with 3 1680x1050 screens, it starts happening 

>>> quickly with

>>> any significant screen activity.

>>> * And a fun one: on that multi-screen setup, once you get large 

>>> areas of the

>>> one screen (one DL device) to fail to render ... then moving the 

>>> mouse and

>>> triggering rendering on the *other* DL device/screen, for the 

>>> corresponding

>>> lines on the screen, refreshes the first device/screen properly 

>>> (!) Since

>>> udlfb keeps no shared state between different DisplayLink devices,

>>> apparently this confusion is happening at the defio/vma/page table 

>>> level.

>>>

>>> Defio is used by several other framebuffer drivers, but perhaps not 

>>> at these

>>> resolutions and not for multiple screens. Has anyone seen other 

>>> evidence

>>> that would support/contradict this being a general defio problem? Or

>>> perhaps something simple/stupid that udlfb is doing to trigger it?

>>>

>>> Thanks,

>>> Bernie

>>>

> 

> 

> ------------------------------

> 

> _______________________________________________

> Libdlo mailing list

> Libdlo at lists.freedesktop.org

> http://lists.freedesktop.org/mailman/listinfo/libdlo

> 

> 

> End of Libdlo Digest, Vol 13, Issue 12

> **************************************