[linuxtv-softmpeg] Re: EPIA MII 12000

["Ray Glendenning" <ray.glendenning@hackery.demon.co.uk>]

Hi

Sorry for not getting back til now, but I have been drining too much and
seeing too many friends due to it being my birthday :-)

I really want to get kernel 2.6 working if at all possible, and if you can
point me in the right direction I'm not afraid of C or kernel level
programming (not good at, bit what the hell) ;)

Basically I need to get a system up and running ie. normal fbdev or whatever
directfb needs, then I can hopefully be of some use.

Thanks
Ray

----- Original Message ----- 
From: "Nicolas Huillard" <nhuillard@ghs.fr>
To: <linuxtv-softmpeg@linuxtv.org>
Sent: Thursday, June 17, 2004 4:26 PM
Subject: [linuxtv-softmpeg] Re: EPIA MII 12000


> Ray Glendenning wrote:
>
> > Hi
> >
> > I decided to take the plunge and bought myself an EPIA.  I am using
kernel
>
> Nice. It ths fan noisy on that one ? I had to remove the fan on my
> M10000 because it was too noisy, and replaced it with a nearby 8cm
> low-voltage fan. Still too loud, though...
>
> > 2.6.6 with epia patch from
> > http://www3.sympatico.ca/howlettfamily/epia/epia_howto/x822.html, but
when I
> > insert viafb, I get a corrupted image on my tv (no monitor connected to
this
> > machine).  Does anyone have any pointers or know where I should start
and
> > look to see what the problem is?
>
> The 2.6.6 viafb module is still not updated to DirectFB specs (as of a
> few days ago). I reverted back to 2.4.26, with the -epia2 kernel patch
> from www.epiawiki.org
> Read my posts and replies from Michael Hunold and others on this very
> mailing-list (dated 2004-06-10 or so).
>
> >
> > The line used to insert the module is:
> > modprobe via mode=720x576 refresh=50 TVon=1 TVtype=2
>
> I think this one will work with the 2.4.26 viafb.
>
> Do you plan to use the softmpeg vdr plug-in, or something else related
> to lisoftmpeg ?
> I for myself still have problems with softmpeg, but the specs sound
> promising (even CLE266 hardware MPEG2 decoder code). The problem of this
> code is that the community around it seems to be quite... absent...
>
> Please keep us informed of your work.
>
> NH
>
>
>