[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnewsense-dev] Re: gNewSense-MIPS and SiliconMotion video driver
From: |
Daniel Clark |
Subject: |
[Gnewsense-dev] Re: gNewSense-MIPS and SiliconMotion video driver |
Date: |
Thu, 04 Mar 2010 02:33:13 -0500 |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9pre) Gecko/20100217 Shredder/3.0.3pre |
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/570549e3d7894fef/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,
--
Daniel JB Clark | http://pobox.com/~dclark