Sorry for digging out an old message. But... (I also started
to write this a couple weeks back, then set it aside to do
more observation, so dates referenced may be inaccurate)
I've been intending for some time to gradually migrate my
production machine from its 2005-era solid-like-rock kernel,
En/na BOUWSMA Barry ha escrit:
The above observations are so far, just observations, and I
don't expect anyone to be able to `fix' anything
They're nevertheless interesting, since I'm in a similar position: my
vdr machine is using (almost flawlessly) a Skystar 2 (though I don't
believe in th
On Sat, 25 Apr 2009, Luca Olivetti wrote:
> > The above observations are so far, just observations, and I
> > don't expect anyone to be able to `fix' anything
>
> They're nevertheless interesting, since I'm in a similar position: my vdr
> machine is using (almost flawlessly) a Skystar 2 (though I
On Fri, 16 Jan 2009, AlexW wrote:
> Patrick Boettcher wrote:
> > For years there has been the Video Data Stream Borken-error with VDR and
> > Technisat cards: The error occured randomly and unfrequently. A
> > In fact it turned out, that the problem is worse with setups not based
> > on VDR an
Hi Barry,
Hi Walter,
On Sat, 17 Jan 2009, BOUWSMA Barry wrote:
For years there has been the Video Data Stream Borken-error with VDR and
Technisat cards: The error occured randomly and unfrequently. A
In fact it turned out, that the problem is worse with setups not based
on VDR and the "VDSB-e
On Sat, 17 Jan 2009, Patrick Boettcher wrote:
> > Same here -- never experienced this ever in some four-ish years
> > with one SkyStar2 of model long forgotten, with that card being
> Using VDR or a single application (like kaffeine), you most likely don't see
> the error anymore thanks to the wo
Following up to myself is a sign of a sick mind.
On Sat, 17 Jan 2009, BOUWSMA Barry wrote:
> > shell 1: $ tzap channel
> > shell 2: $ dvbtraffic
> > [lots of output that streaming is working]
> > shell 1: $
> > shell 1: $ tzap "channel2_which is on a different frequency"
> > shell 2: no output o
Patrick,
Please ignore my comment prior in this thread about using
spin_lock_irq() vs. spin_lock_irqsave(). Between lack of sleep and
trying to install Fedora 10 and recover my data on what now appears to
be a failing motherboard/cpu, I made an error. I realized spinlock
functions should always
El Sat, 17 Jan 2009 09:29:29 +0100 (CET)
Patrick Boettcher escribió:
> I have to say, that the user which showed me the problem was using
> the rev2.8 and due to the lack of time I couldn't check with other
> versions than this card yet.
Well, I'm definitely seeing this with an old skystar 2 (I'
