[vdr] [PATCH] Priority of transfer-mode should not be -1

Thomas Bergwinkl bergwinkl.thomas at vr-web.de
Mon Aug 29 21:33:42 CEST 2005


Klaus Schmidinger wrote:
> Anssi Hannula wrote:
> > Klaus Schmidinger wrote:
> >
> >>> Anssi Hannula wrote:
> >>>
> >>>> The transfer-mode uses always priority -1.
> >>>>
> >>>> That presents a problem: If I connect to that vdr using
> streamdev, it
> >>>> switches the first budget device off from the multiplex
> transfered to
> >>>> the FF card, although there is a second identical budget
> >>>> device available.
> >>>>
> >
> >> Actually, the PrimaryLimit was implemented at a time where
> the FF DVB
> >> cards were unable to record and replay at the same time.
> In that case,
> >> when a timer needed to use the primary device, it was no
> longer possible
> >> to switch to a different channel. These times are long
> gone, so I would
> >> instead tend to remove the PrimaryLimit altogether. It
> would make things
> >> simpler instead of more complex ;-)
> >>
> >> If somebody has programmed so many timers that all of the DVB cards
> >> are needed to record them, so be it.
> >>
> >> Comments?
> >>
> >
> > How exactly would that resolve the situation I described above?
>
> Well, it wouldn't. Apparently I overread that this was a
> streamdev issue.
> But then again, it's of course the same problem if you are in
> Transfer-Mode
> and a recording starts and selects the receiver device, even
> though an other
> device would be free.
>
> I'll think over this again...

What do you think about the attached patch?

Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: device.c.diff
Type: application/octet-stream
Size: 1310 bytes
Desc: not available
Url : http://www.linuxtv.org/pipermail/vdr/attachments/20050829/e7fd6d5a/device.c.obj


More information about the vdr mailing list