[vdr] future VDR and Net??eiver OEM from Reelmultimedia

Anssi Hannula anssi.hannula at gmail.com
Sat Jun 30 13:17:48 CEST 2007


Stefan Lucke wrote:
> On Friday 29 June 2007 18:24, Georg Acher wrote:
>> On Fri, Jun 29, 2007 at 08:21:45AM -0700, Jeremy Jones wrote:
>>  
>>> I checked out the latest Reelbox testing svn code and browsed the code to
>>> see if it supports this device.  I didn't look too thoroughly but it appears
>>> the reelbox-0.9.0 plugin does support it.  It looks like communication to
>>> the kernel space driver is done through shared memory and I did see some
>>> kernel space code to create this shared memory device (/dev/hdshmem).  I'm
>>> sure there is a closed source firmware or kernel module that is also used
>>> but since Reelbox is based on vdr this shouldn't be too much of a problem.
>> Actually there's not much closed source that affects the usage. On the PC
>> side there's none, on the card side it's only the driver for the HDMI-chip
>> in the kernel 
> 
> Damm, that's the nvidia way.
> 
> They decide on which kernel it runs. If I need for some other device
> a different kernel which they don't / won't support, I'm left alone.

If I understood correctly, you only need proprietary parts for the 
kernel that runs *in* the card. The kernel running on your actual system 
does not need proprietary parts, leaving you free to use a different kernel.

> To my opinion that is a nogo way.
> I doubt if that's compatible with GPL.
> 
>> (otherwise Silicon Image would shoot us) and of course the 
>> firmwares for the internal audio/video-coprocessors (delivered by Micronas).

-- 
Anssi Hannula



More information about the vdr mailing list