[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4EDE2B3B.2080905@linuxtv.org>
Date: Tue, 06 Dec 2011 15:48:27 +0100
From: Andreas Oberritter <obi@...uxtv.org>
To: Mark Brown <broonie@...nsource.wolfsonmicro.com>
CC: Mauro Carvalho Chehab <mchehab@...hat.com>,
HoP <jpetrous@...il.com>,
Florian Fainelli <f.fainelli@...il.com>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
linux-media@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC] vtunerc: virtual DVB device - is it ok to NACK driver because
of worrying about possible misusage?
On 06.12.2011 15:19, Mark Brown wrote:
> On Tue, Dec 06, 2011 at 01:01:43PM +0100, Andreas Oberritter wrote:
>> On 06.12.2011 12:21, Mark Brown wrote:
>>> On Mon, Dec 05, 2011 at 09:41:38PM +0100, Andreas Oberritter wrote:
>
>>>> Are you serious? Lower networking layers should be transparent to the
>>>> upper layers. You don't implement VPN or say TCP in all of your
>>>> applications, do you? These are just some more made-up arguments which
>>>> don't have anything to do with the use cases I explained earlier.
>
>>> For real time applications it does make a big difference - decisions
>>> taken at the application level can greatly impact end application
>>> performance. For example with VoIP on a LAN you can get great audio
>
>> Can you please explain how this relates to the topic we're discussing?
>
> Your assertatation that applications should ignore the underlying
> transport (which seems to be a big part of what you're saying) isn't
> entirely in line with reality.
Did you notice that we're talking about a very particular application?
VoIP really is totally off-topic. The B in DVB stands for broadcast.
There's only one direction in which MPEG payload is to be sent (using
RTP for example). You can't just re-encode the data on the fly without
loss of information.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists