All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Toth <stoth@linuxtv.org>
To: linux-media@vger.kernel.org
Cc: linux-dvb <linux-dvb@linuxtv.org>
Subject: Re: [linux-dvb] Fwd: HVR2250 Status - Where am I?
Date: Fri, 27 Feb 2009 14:29:18 -0500	[thread overview]
Message-ID: <49A83F0E.5070402@linuxtv.org> (raw)
In-Reply-To: <412bdbff0902271050r4c53a655na8cd0f404a83895e@mail.gmail.com>

Devin Heitmueller wrote:
> On Fri, Feb 27, 2009 at 1:38 PM, John Drescher <drescherjm@gmail.com> wrote:
>> So now (with my donation) we have him working at $1/hour assuming that
>> it takes only 100 hours..
> 
> Well, this assumes that it would only take 100 hours, of which given
> the complexity of the device, it will probably take more than twice
> that (since it's a PCI device and the estimates I gave are for USB
> devices).
> 
> If nothing else, it offers some insight as to how valuable the work of
> people like Steven is (he has written a whole bunch of different
> drivers).  It also demonstrates one reason there are so few developers
> willing to do this sort of work.  Getting a developer to donate a
> couple of evening's worth of time is pretty easy.  Getting them to
> make a commitment of every day for the next two to three months is
> quite harder.

It takes a massive amount of time from all of the core developers to keep the 
v4l-dvb tree up to date and to add new functionality.

Adding a new style of board to an existing driver can take a couple of hours 
with testing. It's bread a butter maintenance task.

However, adding a brand new bridge driver to the kernel can take 6 months just 
for the first release, and is then slowly improved over the next 12-24 months.

It's a large task.

- Steve



      reply	other threads:[~2009-02-27 19:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-20  4:57 [linux-dvb] HVR2250 Status - Where am I? Steven Toth
2009-02-20  5:25 ` John Drescher
2009-02-20 14:59   ` Steven Toth
2009-02-20 15:07     ` John Drescher
     [not found]       ` <e816454e0902270833i73cd59f0t1129ab7011b0024c@mail.gmail.com>
2009-02-27 16:45         ` [linux-dvb] Fwd: " John Drescher
2009-02-27 17:07           ` Steven Toth
2009-02-27 17:18             ` John Drescher
2009-02-27 17:19               ` Steven Toth
2009-02-27 18:27                 ` Andrew Barbaccia
2009-02-27 18:34                   ` Devin Heitmueller
2009-02-27 18:38                     ` John Drescher
2009-02-27 18:47                       ` Andrew Barbaccia
2009-02-27 18:50                       ` Devin Heitmueller
2009-02-27 19:29                         ` Steven Toth [this message]

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=49A83F0E.5070402@linuxtv.org \
    --to=stoth@linuxtv.org \
    --cc=linux-dvb@linuxtv.org \
    --cc=linux-media@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.