gnewsense-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 答复: 答复: [Gnewsense-dev] Re: gNewSense-MIPS and SiliconMotion video


From: Wu Zhangjin
Subject: Re: 答复: 答复: [Gnewsense-dev] Re: gNewSense-MIPS and SiliconMotion video driver
Date: Mon, 08 Mar 2010 18:24:43 +0800

On Mon, 2010-03-08 at 03:09 -0430, Octavio Rossell wrote:
> WOW!!!
> 
> This are very good news. Thanks, Wu !!
> 
> What is needed to to have a new driver adding this proposals (besides of
> patching it)?
> 

I got the following steps about how to recompile xorg-server:
(from http://www.heiher.info/category/computer/os/linux)

mkdir xorg-server
cd xorg-server
apt-get source xorg-server
dpkg-source -x xorg-server*.dsc

cd xorg-server*/debian/patches/
// Get the patch for xorg-server
echo "<the name of the patch>" >> series
cd ../../

dpkg-buildpackage -rfakeroot -uc -b

cd ../
rm xserver-xorg-core-dbg*
sudo dpkg -i *.deb

Then edit the xorg.conf ...

But I don't know how to compile the silicon motion driver,
Liu Shiwei have done it, he may know, and of course,
Teddy is the maintainer, he should know it too, and also,
Zhang Le should have played with it. so, put all of them
into the CC: list.

Regards,
        Wu Zhangjin

> Wu Zhangjin escribió:
> > Shiwei have found, with this patch, the performance is increaced very
> > obviously:
> > 
> > -----------------
> > 
> > address@hidden:~$ mplayer -benchmark -nosound -vo xv Flack.avi
> > no loongson2f patch:
> > BENCHMARKs: VC: 132.980s VO: 121.602s A:   0.000s Sys:  12.882s
> > =  267.465s
> > BENCHMARK%: VC: 49.7188% VO: 45.4648% A:  0.0000% Sys:  4.8164% =
> > 100.0000%
> > loongson2f patch:
> > BENCHMARKs: VC: 128.548s VO:  42.528s A:   0.000s Sys:   5.600s
> > =  176.676s
> > BENCHMARK%: VC: 72.7592% VO: 24.0712% A:  0.0000% Sys:  3.1697% =
> > 100.0000%
> > 
> > --------------------
> > 
> > from: http://www.bjlx.org.cn/node/753
> > 
> > The tested patches for Xorg and silicon motion driver were also put on
> > the above web page.
> > 
> > Regards,
> >     Wu Zhangjin
> > 
> > On Mon, 2010-03-08 at 00:45 -0430, Octavio Rossell wrote:
> >> Teddy, in this list:
> >>
> >> http://groups.google.com/group/loongson-dev/browse_thread/thread/570549e3d7894fef/07ba7be1fd1b15c8
> >>
> >> there was a proposed patch to the current version:
> >>
> >> http://loongson-dev.googlegroups.com/attach/c8ccd2a1370f5927/xf86-video-siliconmotion-1.7.3-fix-loongson.patch
> >>
> >> It is possible to study this to add the proposed changes into the
> >> oficial driver?
> >>
> >> Teddy Wang escribió:
> >>>     Now our new SM502 and SM712 driver can support latest XServer. But the
> >>> new SM712 driver doesn't test in the loongson platform.  The new SM502
> >>> Xserver driver you used in the AIO platform also can support latest 
> >>> Xserver.
> >>>
> >>> -----邮件原件-----
> >>> 发件人: zhangfx [mailto:address@hidden 
> >>> 发送时间: 2010年3月5日 8:55
> >>> 收件人: Teddy Wang
> >>> 抄送: 'yanhua'; 'Daniel Clark'; 'chenj'; '崔春波'; address@hidden;
> >>> 'Bernie Innocenti'
> >>> 主题: Re: 答复: [Gnewsense-dev] Re: gNewSense-MIPS and SiliconMotion video
> >>> driver
> >>>
> >>> It seems that people are complaining that the performance is much worse 
> >>> than current one.
> >>>
> >>> Teddy Wang wrote:
> >>>> Hi, yanhua,
> >>>>
> >>>>  Now the Siliconmotion driver in freedesktop port can support higher X
> >>>> server. It can support SM712 and SM502. You can refer to
> >>>> http://cgit.freedesktop.org/xorg/driver/xf86-video-siliconmotion/
> >>>>  
> >>>>
> >>>> Best Regards,
> >>>> Teddy Wang 王力强
> >>>> Silicon Motion, Inc. (China)
> >>>> Tel: 86 21 65107780 ext.7162
> >>>> Mobile: 86 13817794114
> >>>> -----邮件原件-----
> >>>> 发件人: yanhua [mailto:address@hidden 
> >>>> 发送时间: 2010年3月4日 17:30
> >>>> 收件人: Daniel Clark; Teddy Wang; chenj; 崔春波
> >>>> 抄送: address@hidden; Bernie Innocenti; zhangfx
> >>>> 主题: Re: [Gnewsense-dev] Re: gNewSense-MIPS and SiliconMotion video
> >>> driver
> >>>> We only test yeeloong siliconmotion driver for sm712 in x server 1.4.2. 
> >>>> some work is  needed to  make higher x server work properly.
> >>>>
> >>>> High Teddy:
> >>>>      We need to port siliconmotion  x driver to higher x server, the 
> >>>> best is the newest x server.  Could you please help to do this work?
> >>>>
> >>>> Daniel Clark 写道:
> >>>>   
> >>>>> On 02/28/2010 11:24 PM, Octavio Rossell wrote:
> >>>>>     
> >>>>>> We need to recompile the Silicon Motion Driver into the gNewSense 
> >>>>>> Lemote
> >>>>>> Yeelong. There is an existing effort in this [1] but the package 
> >>>>>> appears
> >>>>>> to crash or to not work properly in some reeboot situation.
> >>>>>>       
> >>>>> There are actually several projects / hacks to get X working better in 
> >>>>> various ways on the yeeloong. I believe all of them suffer from 
> >>>>> various problems, and most are dead ends (code that would never be 
> >>>>> accepted against upstream and/or against really old versions of X).
> >>>>>
> >>>>> Bernie has a pretty comprehensive overview of the situation as it was 
> >>>>> a month or two ago posted somewhere; I'll try to gather all the 
> >>>>> mailing list posts about and put summaries/references to them on a 
> >>>>> wiki page somewhere if you tell me you would find that to be useful.
> >>>>>
> >>>>> The most recent effort I've seen has code (patch file) and discussion 
> >>>>> here:
> >>>>>
> >>>>>
> >>>>>     
> >>> http://groups.google.com/group/loongson-dev/browse_thread/thread/570549e3d78
> >>>> 94fef/07ba7be1fd1b15c8?lnk=gst&q=x11#07ba7be1fd1b15c8 
> >>>>   
> >>>>> Or here if that URL is broken:
> >>>>>
> >>>>> http://ur1.ca/obkd
> >>>>>
> >>>>>     
> >>>>>> Any help, advice or information will be helpful.
> >>>>>>       
> >>>>> Advice:
> >>>>>
> >>>>> (a) Check mailing list archives, monitor and keep up to date at least 
> >>>>> this mailing list, loongson-dev, #gnewsense-dev irc. Email 
> >>>>> address@hidden and ask for access to address@hidden and its archives.
> >>>>>
> >>>>> (b) Get on the proper xorg lists / channels.
> >>>>>
> >>>>> (c) If you don't have commit access to xorg version control, be sure 
> >>>>> to form a relationship with someone who does, and is willing to help 
> >>>>> you get your changes in. Ditto for the upstream Debian packages, 
> >>>>> unless you have resources to maintain seperate gNS-specific packages 
> >>>>> until the end of time, and kk is cool with that.
> >>>>>
> >>>>> (d) Make sure any development happens in a publicly available version 
> >>>>> control repository. Tell at least this list and loongson-dev where 
> >>>>> that is once anything at all useful is there.
> >>>>>
> >>>>> (e) Keep in mind that the goal is to be included in upstream xorg; 
> >>>>> avoid quick hacks that will never be accepted upstream.
> >>>>>
> >>>>> (f) If the people working on this on your end are not good at English, 
> >>>>> see if you can get someone who is to translate the available doc / 
> >>>>> list threads to them and vice versa.
> >>>>>
> >>>>> (g) You may also want to follow Zhang Le's Gentoo work, it seems to be 
> >>>>> the most advanced loongson2f-optimized GNU/Linux distribution at the 
> >>>>> moment (i.e. it's actually all compiled with proper mipsel abi, 
> >>>>> loongson2f optimization, loongson2f bug workarounds). Also 
> >>>>> collaborating with people working on OpenBSD/Loongson may be useful; 
> >>>>> we may disagree politically at times, but we use the same upstream 
> >>>>> xorg code.
> >>>>>
> >>>>> (h) You are probably more likely to get technical help regarding the 
> >>>>> work on loongson-dev or xorg lists.
> >>>>>
> >>>>> (i) Some low level info on the SM hardware is at 
> >>>>> http://groups.google.com/group/loongson-dev/files
> >>>>>
> >>>>> (j) If you need to speed up compiles bug me on #gnewsense-dev - I'm 
> >>>>> close to having an icecc setup done, and should have 10 more 2f boxes 
> >>>>> to add to the existing 4 in the farm Monday.
> >>>>>
> >>>>> Happy Hacking,
> >>>>>     
> >>>>   
> >> _______________________________________________
> >> gNewSense-dev mailing list
> >> address@hidden
> >> http://lists.nongnu.org/mailman/listinfo/gnewsense-dev
> > 
> > 
> > 
> 






reply via email to

[Prev in Thread] Current Thread [Next in Thread]