[linux-dvb] Re: V4 API Implementation Q's

2004-04-30 Thread Johannes Stezenbach
On Fri, Apr 30, 2004 at 11:13:00AM +0200, Michael Hunold wrote: > > You can of course fake a recording filter again by creating a separate > recording buffer memory, where the data from the indivudal pid filters > is written to (like the av7110 does). Our av7110 firmware actually implements one

[linux-dvb] Re: V4 API Implementation Q's

2004-04-30 Thread Michael Hunold
Hello Rob, OK, from our discussions it sounds like it will be the responsibility of the code "underneath" the API to control the resources. We just specify the max number of *h/w* filters of each type - right? e.g. If you don't have dedicated record h/w then you should set the DVB_DMX_CAP_NUM_REC

[linux-dvb] Re: V4 API Implementation Q's

2004-04-14 Thread Rob . McConnell
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]cc: e> Subject: [linux-dvb]

[linux-dvb] Re: V4 API Implementation Q's

2004-04-13 Thread Johannes Stezenbach
On Tue, Apr 13, 2004 at 06:14:11PM +0100, [EMAIL PROTECTED] wrote: > > > Well, I think if you write a simple zapping application you would > > statically allocate filters for audio, video, pcr, and allocate > > and set filters for PAT, PMT, EIT-p/f. Then for zapping you just > > set some PIDs and

[linux-dvb] Re: V4 API Implementation Q's

2004-04-13 Thread Rob . McConnell
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]cc: e> Subject: [linux-dvb]

[linux-dvb] Re: V4 API Implementation Q's

2004-04-13 Thread Johannes Stezenbach
On Tue, Apr 13, 2004 at 12:15:56PM +0100, [EMAIL PROTECTED] wrote: > Hi Johannes, > > > However, the V3 API allows one to allocate+set a filter now, and > > start the filter later. I don't know how useful this is. I left > > this out in V4 because the software I know does not actually make > > use

[linux-dvb] Re: V4 API Implementation Q's

2004-04-13 Thread Rob . McConnell
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]cc: e> Subject: [linux-dvb]

[linux-dvb] Re: V4 API Implementation Q's

2004-04-12 Thread Johannes Stezenbach
On Tue, Apr 06, 2004 at 07:27:24PM +0100, [EMAIL PROTECTED] wrote: > Michael Hunold wrote: > > If you have a hardware that mixes all these kind of filters to one > > device, you'll have a hard time to calculate how many filters are > > actually available of each kind. > > OK, from our discussions

[linux-dvb] Re: V4 API Implementation Q's

2004-04-06 Thread Rob . McConnell
AIL PROTECTED]To: [EMAIL PROTECTED] ce.de> cc: Johannes Stezenbach <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Subject: Re: [linux-dvb

[linux-dvb] Re: V4 API Implementation Q's

2004-04-06 Thread Michael Hunold
Hello Rob, Would the "query capability" ioctl return a "snap-shot" of the actual number of filters left of a certain type or would it return the max number of filters for each type? I would prefer the former, as you could easily have the scenario that there are 32 PID filters in a demux device th

[linux-dvb] Re: V4 API Implementation Q's

2004-04-06 Thread Michael Hunold
Hello Rob, On 03/26/04 16:45, [EMAIL PROTECTED] wrote: This leads me into the next point/question regarding output devices. Wouldn't it be better to have output demux devices such as PID filter, recording filter, section filter, decoder feed with each one allocated a different minor number. Then

[linux-dvb] Re: V4 API Implementation Q's

2004-03-26 Thread Johannes Stezenbach
[EMAIL PROTECTED] wrote: > > Just got around to having a look @ the V4 API code in CVS and was well > impressed at how far we have got since I spoke last : ) > I see that we have decided on using the original V4 API as intended by > Johannes/Holger rather than Michael's with different output devic