Linux Media Controller development
 help / color / mirror / Atom feed
From: Trent Piepho <xyzzy@speakeasy.org>
To: Jean Delvare <khali@linux-fr.org>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
	Hans Verkuil <hverkuil@xs4all.nl>,
	linux-media@vger.kernel.org
Subject: Re: bttv, tvaudio and ir-kbd-i2c probing conflict
Date: Mon, 16 Mar 2009 12:43:33 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0903161202330.28292@shell2.speakeasy.net> (raw)
In-Reply-To: <20090316152802.7492dd20@hyperion.delvare>

On Mon, 16 Mar 2009, Jean Delvare wrote:
> Come on, just look at ir-kbd-i2c and tvaudio again, see how great are
> these drivers which have been "designed" on top of the legacy i2c
> binding model. Look at the bttv mess. Look at the zoran driver
> conversion done by Hans a few weeks ago, which killed what, 3000 lines
> of code? The old binding model was so bad that DVB doesn't even use it.

IIRC, the zoran patch removed more like 1000 lines.  But it also deleted
v4l1 support, highmem support, and bigphys_area support.  Maybe other
things, Hans doesn't decribe his patches, so there's really no way to know
what the zoran patch really did other than to weed through 10,000+ lines of
diff which is mostly but not entirely moving blocks of code from one space
to another and reindenting them.

If one includes the v4l1-compat module that is now providing v4l1 support
(though it doesn't work correctly for zoran), the driver and the compat
module are larger than the old driver was.  Of course one can now turn off
v4l1 support and get a smaller driver than before.  And the v4l1 compat
already existed and can be shared.  But I think it's more correct to say
the size reduction of the zoran driver was from removing features and not
from v4l2_subdev.  It seems like more of the the other subdev conversions
have overall added more code than they removed.

  parent reply	other threads:[~2009-03-16 19:43 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-15 12:44 bttv, tvaudio and ir-kbd-i2c probing conflict Hans Verkuil
2009-03-15 17:12 ` Jean Delvare
2009-03-15 17:42   ` Trent Piepho
2009-03-15 17:53     ` Jean Delvare
2009-03-16  9:08       ` Mauro Carvalho Chehab
2009-03-16  9:34       ` Mauro Carvalho Chehab
2009-03-16 11:18         ` Jean Delvare
2009-03-16 12:52           ` Mauro Carvalho Chehab
2009-03-16 14:28             ` Jean Delvare
2009-03-16 15:31               ` Mauro Carvalho Chehab
2009-03-16 19:43               ` Trent Piepho [this message]
2009-03-16 21:40                 ` Jean Delvare
2009-03-16 21:58                   ` Hans Verkuil
2009-03-16 22:47                   ` Trent Piepho
2009-03-17  9:31                     ` Jean Delvare
2009-03-17 20:23                       ` Trent Piepho
2009-03-15 19:34   ` Andy Walls
2009-03-15 22:09     ` Hans Verkuil
2009-03-15 22:28       ` Jean Delvare
2009-03-15 22:26     ` Jean Delvare
2009-03-16  0:52       ` Andy Walls
2009-03-16  4:26         ` hermann pitton
2009-03-16 12:58         ` Jean Delvare
2009-03-15 23:46     ` Trent Piepho
2009-03-16  8:35       ` Jean Delvare
2009-03-16 11:35 ` Andy Walls
  -- strict thread matches above, loose matches on Subject: below --
2009-03-16 11:56 Hans Verkuil

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=Pine.LNX.4.58.0903161202330.28292@shell2.speakeasy.net \
    --to=xyzzy@speakeasy.org \
    --cc=hverkuil@xs4all.nl \
    --cc=khali@linux-fr.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox