Krzysztof Halasa writes:
>> Something like the attached patch would be preferred (there's no need to
>> set up the overlay if the destination area isn't going to be visible
>> anyway).
>
> []
>
>> --- a/src/smi_video.c
>> +++ b/src/smi_video.c
>> @@ -1060,7 +1060,7 @@ SMI_PutVideo(
>> if(!xf
Krzysztof Halasa writes:
> Hi,
>
> the SMI driver segfaults when I try to run mplayer -vo xv. I haven't
> investigated too much, perhaps it's caused by the initial video window
> being placed off screen. This is a really old Lynx 3DM (SM720 or
> something), a virtual screen (with traditional mous
Piotr Lukawski writes:
> Just tried:
> (II) LoadModule: "siliconmotion"
> (II) Loading /usr/local/lib/xorg/modules/drivers//siliconmotion_drv.so
> (II) Module siliconmotion: vendor="X.Org Foundation"
> compiled for 1.6.5, module version = 1.7.3
> Module class: X.Org Video Driver
>
Alan Coopersmith (2):
Remove xorgconfig & xorgcfg from See Also list in man page
Add README with pointers to mailing list, bugzilla & git repos
Francisco Jerez (8):
Dynamically switch virtual refresh mode.
Set dualhead to on by default on SM72x chipsets.
Hi,
"Timothy S. Nelson" writes:
> Hi all. There's a patch that's attached to bugzilla bug 18160 that
> fixes the problem specified in that bug; now that it prevents xorg from
> hanging the machine, other bugs have become visible, but the patch attached
> to
> comment 30 seems to solve
Hi.
Since I switched to libpciaccess, I've been seeing errors like:
> error setting MTRR (base = 0x1420, size = 0x0080, type = 1) Invalid
> argument (22)
It's because the GPU I'm using (a siliconmotion SM720) has a register
area at the beginning of the PCI BAR which shouldn't be set to
"Richard Schwarting" writes:
> Suspending without X has the same effect as suspending with X. A
> blank screen that slowly bleeds white across it.
>
> vbetool doesn't seem to help. I will investigate this issue more
> outside of X.
>
> Do you still need anything re: the silicon motion driver?
"Richard Schwarting" writes:
> Hey. The patches cured XAA slowness for me and obviate the need for
> the "UseBIOS" "NO" option for both EXA and XAA for me. Hurrah.
>
> I mentioned before that after suspending in Fedora, resuming gives me
> a blank screen. If I do any VT switches, than light st
Hi,
"Richard Schwarting" <[EMAIL PROTECTED]> writes:
> Hello again.
>
> I am a goat and in an effort to verify that the XAA and EXA
> performance difference was or wasn't just a Ubuntu issue, I tried
> installing Fedora 10. Yada yada, Ubuntu got clobbered, Fedora has
> broken dbus and .gstreamer
very much. I hope to repay your helpfulness some day, as
> you've really made my life a lot easier :)
>
> Cheers,
> Richard Schwarting
>
>
In fact, the only Silicon Motion hardware I've got access to is another
SM720 card. I'm not experiencing those problems on i
/show_bug.cgi?id=18816
>
Hello again,
I've done some corrections to the mode setting code (I'm attaching the
patch). Could you try it out over the last one and tell me if it works?
> On Tue, Dec 2, 2008 at 15:32, Francisco Jerez <[EMAIL PROTECTED]> wrote:
>>>
tions of modes and v/hsync, though
> I'm wondering whether the offset weird display is actually caused by
> incorrectly set values for them, as I've tried rates that had worked
> previously.
>
> Cheers,
> Richard Schwarting
>
> On Tue, Dec 2, 2008 at 04:48, Franci
Hi,
"Richard Schwarting" <[EMAIL PROTECTED]> writes:
> Thanks for the responses.
>
> == Silicon Motion from git ==
>
> Yes Francisco, I've tried the latest code from
> git://anongit.freedesktop.org/xorg/driver/xf86-video-siliconmotion and
> that led to what I thought was the same error, since I w
"Richard Schwarting" <[EMAIL PROTECTED]> writes:
> Hello.
>
> I have a Silicon Motion SM720 Lynx3DM card which X in Ubuntu 8.10 (and
> Fedora 9) will not start on. The log seems fine but ends with:
> AddScreen/ScreenInit failed for driver 0
>
> The issue it experience seems to have been introduc
14 matches
Mail list logo