DXR3 driver for Linux

Nicolas Boullis | 21 Dec 2009 00:46

0.18.0 is out

Hi,

For those who care, I just released version 0.18.0 of the em8300 driver.

It is exactly the same as 0.18.0-rc2, and is only meant to fix bugs in 
0.17.4, including the problem with the colors of the OSD/subtitles with 
linux >= 2.6.31.

This release is numbered 0.18.0 rather than 0.17.4 because it introduces 
an important modification of the userspace binary interface. Hence, all 
applications that use the em8300 driver MUST be rebuild against the new 
em8300.h file. Please ensure the new em8300.h file is really installed 
in /usr/include/linux/em8300.h before you rebuild anything.

This release is expected to work with linux up to 2.6.32. Status with 
the upcoming 2.6.33 is unknown, any feedback would be nice.

Cheers,

Nicolas

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev

_______________________________________________

(Continue reading)

headers

Ville Skyttä | 29 Dec 2009 21:49

Re: 0.18.0 is out

On Mon, Dec 21, 2009 at 1:46 AM, Nicolas Boullis <nboullis <at> debian.org> wrote:

> This release is numbered 0.18.0 rather than 0.17.4 because it introduces
> an important modification of the userspace binary interface. Hence, all
> applications that use the em8300 driver MUST be rebuild against the new
> em8300.h file. Please ensure the new em8300.h file is really installed
> in /usr/include/linux/em8300.h before you rebuild anything.

xine-lib ships and compiles against an "internal" copy of em8300.h, so
the above might not be enough for it.  src/dxr3/em8300.h in the
xine-lib source tree probably requires updating as well.

Bug report requesting updating or removal of that internal copy is
filed here: http://bugs.xine-project.org/show_bug.cgi?id=298

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev

headers

Roman Müllenschläder | 6 Feb 2010 08:57

Re: 0.18.0 is out

Nicolas,

are you able to tell anything about em8300-headers in coming debian/ubuntu?

There are no packages in sid nor in lucid anymore?!

Me need the to build MMS ;)

Lg
Roman

Am Montag 21 Dezember 2009 schrieb Nicolas Boullis:
> Hi,
> 
> For those who care, I just released version 0.18.0 of the em8300 driver.
> 
> It is exactly the same as 0.18.0-rc2, and is only meant to fix bugs in
> 0.17.4, including the problem with the colors of the OSD/subtitles with
> linux >= 2.6.31.
> 
> This release is numbered 0.18.0 rather than 0.17.4 because it introduces
> an important modification of the userspace binary interface. Hence, all
> applications that use the em8300 driver MUST be rebuild against the new
> em8300.h file. Please ensure the new em8300.h file is really installed
> in /usr/include/linux/em8300.h before you rebuild anything.
> 
> This release is expected to work with linux up to 2.6.32. Status with
> the upcoming 2.6.33 is unknown, any feedback would be nice.
> 
>

(Continue reading)

headers

Roman Müllenschläder | 6 Feb 2010 11:52

Re: 0.18.0 is out

Am Samstag 06 Februar 2010 schrieb Roman Müllenschläder:
> Nicolas,
> 
> are you able to tell anything about em8300-headers in coming debian/ubuntu?
> 
> There are no packages in sid nor in lucid anymore?!
> 
> Me need the to build MMS ;)
> 
> Lg
> Roman
> 

Hi ... me again ;)

I updated the debian package from 0.16.4 to 0.18.0!

The sources are available from my server:
http://www.prodeia.de/mms/source/

so it would be nice, if Nicolas could review the source and comment, as he was 
the one maintaining the package until now.

I had some problems with the debian/config.h.good file, as I don't know the real 
meaning of it and the diff in debian/rules.

Together with that, I disabled all patches in debian/patches/00list, as they 
seemed to only be pre-upstream patches.

This is the changelog:

(Continue reading)