From: Simon Kenyon <simon@koala.ie>
To: Markus Rechberger <mrechberger@gmail.com>
Cc: DVB ML <linux-dvb@linuxtv.org>
Subject: Re: [linux-dvb] Multiproto API/Driver Update
Date: Mon, 08 Sep 2008 12:14:39 +0100 [thread overview]
Message-ID: <48C5091F.3050807@koala.ie> (raw)
In-Reply-To: <d9def9db0809071252x708f1b1ch6c23cb3d2b5796e9@mail.gmail.com>
Markus Rechberger wrote:
> On Sun, Sep 7, 2008 at 9:15 PM, Simon Kenyon <simon@koala.ie> wrote:
>
>> Steven Toth wrote:
>>
>>> A big difference between can and will, the em28xx fiasco tells us this.
>>>
>>>
>> just wondering if your tree will go any way towards resolving that
>> little problem?
>>
>
> I don't see any fiasco nor problem here, it's more comfortable to have
> the em28xx in an extra
> tree and do ongoing development with it. People who followed the
> development during the last
> few years know that newer things got added and newer chips are
> supported by it, it will continue
> to evolve anyway.
>
> The driverwork is currently around 30% of it, patching applications
> and providing full support from
> the driver till the endapplications is what everything's focussing on
> mcentral.de not just driver only
> development.
>
> We do dedicated application support for several customers too (analog
> tv, radio, dvb integration in their
> business applications).
> There are many new products coming up, adding support for them is on
> the roadmap.
>
> Markus
>
>
i have had the device for a while now
i originally got it because the wiki showed that support was being worked on
then that all changed and you moved your stuff elsewhere
i really don't understand your rationale. i really don't.
i'm not trying to start a flame war, but your arguments for having your
own tree and doing stuff user side makes no sense
let my try to explain:
you say:
> it is more comfortable to have the em28xx in an extra tree
it may very well be comfortable for you. but it is impossible for me
i have lots of different devices. i can choose between using your tree
and having support for one of them.
or i change choose the linuxtv.org tree and have supoort for all the
other. how is that "more comfortable"?
i really don't understand that argument
you then say:
> newer things get added and newer chips are supported by it
how does that help me? it doesn't, as far as i can see
next you say:
> the driverwork is currently around 30% of it, patching applications
and providing full support from the driver till the...
apart from the little speedbump that is multiproto vs. s2api most apps
don't need "supporting". they are already supported by their respective
communities.
> we do dedicated application support for several customers...
now i think we get to the heart of the matter.
you have built up a nice little business providing support for the
various devices. you have customers who (in my humble opinion
misguidedly) think that by having support in your tree that they can
proudly boast "linux supported". all i can say is well done.
congratulations on building a sucessful business.
but please do not mistake that for providing linux support for the
em28xx devices in linux. what you are providing and "linux support of
the em28xx class of devices" are not one and the same thing. for better
or worse, linux support means that at some point (and it may well be one
year from now) it will be in the kernel.
have you not seen all the software that has come and gone because linus
will not put it in the tree. right now the only route to doing that is
to get it in the linuxtv.org tree. from there it stands some chance of
making it into the kernel. i seriously doubt that any other approach has
any chance of success.
this may not be of concern or interest to you. well so be it. but it is
important to me.
regards and best of luck
--
simon
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-09-08 11:14 UTC|newest]
Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48C00822.4030509@gmail.com>
[not found] ` <48C01698.4060503@gmail.com>
2008-09-04 17:27 ` [linux-dvb] Multiproto API/Driver Update Manu Abraham
2008-09-04 18:38 ` Goga777
2008-09-04 20:39 ` Manu Abraham
2008-09-04 20:47 ` Johannes Stezenbach
2008-09-04 23:32 ` Markus Rechberger
2008-09-05 13:45 ` Steven Toth
2008-09-07 19:15 ` Simon Kenyon
2008-09-07 19:52 ` Markus Rechberger
2008-09-08 11:14 ` Simon Kenyon [this message]
2008-09-08 12:21 ` Markus Rechberger
2008-09-08 13:19 ` Halim Sahin
2008-09-08 16:07 ` Steven Toth
2008-09-08 17:54 ` Manu Abraham
2008-09-08 18:19 ` Hans Werner
2008-09-08 18:25 ` Markus Rechberger
2008-09-08 18:38 ` Manu Abraham
2008-09-08 16:03 ` Steven Toth
2008-09-08 15:57 ` Steven Toth
2008-09-05 14:32 ` Steven Toth
2008-09-05 1:01 ` hermann pitton
2008-09-05 18:04 ` Francesco Schiavarelli
2008-09-06 11:56 ` Manu Abraham
2008-09-08 19:45 ` barry bouwsma
2008-09-08 20:37 ` Manu Abraham
2008-09-08 20:47 ` Jelle De Loecker
2008-09-08 20:54 ` Manu Abraham
2008-09-08 21:24 ` Markus Rechberger
2008-09-08 22:13 ` Manu Abraham
2008-09-08 23:22 ` Uri Shkolnik
2008-09-09 8:22 ` Manu Abraham
2008-09-11 20:51 ` barry bouwsma
2008-09-11 22:23 ` Uri Shkolnik
2008-09-11 23:16 ` Christophe Thommeret
2008-09-18 19:05 ` Uri Shkolnik
2008-09-12 9:17 ` barry bouwsma
2008-09-18 19:11 ` Uri Shkolnik
2008-09-18 19:24 ` Christophe Thommeret
2008-09-10 0:52 ` barry bouwsma
2008-09-10 9:16 ` Uri Shkolnik
2008-09-10 15:40 ` Michael Krufky
2008-09-12 21:43 ` Manu Abraham
2008-09-12 22:35 ` hermann pitton
2008-09-14 11:15 ` Klaus Schmidinger
2008-09-14 19:15 ` Manu Abraham
2008-09-14 23:02 ` Manu Abraham
2008-09-04 18:12 lucian orasanu
2008-09-04 20:41 ` Manu Abraham
[not found] <20080908195603.GE10714@braindead1.acher>
2008-09-09 0:43 ` barry bouwsma
2008-09-09 1:17 ` hermann pitton
2008-09-09 12:02 ` barry bouwsma
2008-09-09 12:12 ` Rudy Zijlstra
2008-09-09 15:33 ` Markus Rechberger
2008-09-09 20:59 ` Simon Kenyon
2008-09-09 21:14 ` Markus Rechberger
2008-09-10 0:02 ` Steven Toth
2008-09-13 22:46 ` Manu Abraham
2008-09-13 22:56 ` Markus Rechberger
2008-09-13 23:31 ` Manu Abraham
2008-09-14 2:10 ` Markus Rechberger
2008-09-14 10:51 ` barry bouwsma
2008-09-14 13:51 ` Markus Rechberger
2008-09-14 14:29 ` Steven Toth
2008-09-14 14:27 ` Steven Toth
2008-09-14 15:14 ` barry bouwsma
2008-09-14 15:28 ` Markus Rechberger
2008-09-14 16:54 ` Steven Toth
2008-09-14 19:51 ` Markus Rechberger
2008-09-14 21:57 ` Steven Toth
2008-09-14 22:03 ` Andreas Oberritter
2008-09-14 22:27 ` Steven Toth
2008-09-14 22:33 ` Markus Rechberger
2008-09-14 22:41 ` hermann pitton
2008-09-16 16:45 ` Benny Amorsen
2008-09-14 15:38 ` Markus Rechberger
2008-09-14 17:02 ` Steven Toth
2008-09-14 18:51 ` Manu Abraham
2008-09-14 20:08 ` Christophe Thommeret
2008-09-15 0:17 ` hermann pitton
2008-09-14 20:45 ` Andy Walls
2008-09-14 21:01 ` Manu Abraham
2008-09-14 22:20 ` Andy Walls
2008-09-14 22:36 ` Manu Abraham
2008-09-15 4:23 ` hermann pitton
2008-09-14 21:03 ` Manu Abraham
2008-09-15 5:50 ` Julian Scheel
2008-09-15 15:42 ` Michael Krufky
2008-09-19 10:58 ` Julian Scheel
2008-09-19 19:51 ` VDR User
2008-09-24 16:54 ` Oliver Endriss
2008-09-15 23:10 ` Andy Walls
2008-09-16 2:55 ` hermann pitton
2008-09-14 3:39 ` hermann pitton
2008-09-14 19:08 ` Simon Kenyon
2008-09-14 19:25 ` Markus Rechberger
2008-09-14 20:54 ` Simon Kenyon
2008-09-14 21:00 ` Markus Rechberger
-- strict thread matches above, loose matches on Subject: below --
2008-09-10 15:55 Otto Kekäläinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48C5091F.3050807@koala.ie \
--to=simon@koala.ie \
--cc=linux-dvb@linuxtv.org \
--cc=mrechberger@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox