mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Markus Rechberger" <mrechberger@gmail.com>
To: "Aurelien Jarno" <aurelien@aurel32.net>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
	"Mauro Carvalho Chehab" <mchehab@infradead.org>,
	linux-dvb-maintainer@linuxtv.org,
	"Andrew Morton" <akpm@linux-foundation.org>,
	video4linux-list@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [v4l-dvb-maintainer] [GIT PATCHES] V4L/DVB changes for 2.6.24
Date: Thu, 11 Oct 2007 08:31:11 +0200	[thread overview]
Message-ID: <d9def9db0710102331h68e1d9b0rf3095bd9e261ec21@mail.gmail.com> (raw)
In-Reply-To: <470DBDC7.8000304@aurel32.net>

On 10/11/07, Aurelien Jarno <aurelien@aurel32.net> wrote:
> Markus Rechberger a écrit :
> > On 10/11/07, Linus Torvalds <torvalds@linux-foundation.org> wrote:
> >> As such, the old and decrepit em28xx driver seems more useful to people,
> >> since at least it supports the limited set of hardware on its own.
> >
> > it does not since it's broken and feature limited. On the other side
>
> I have a device which works perfectly with it if you add the vendor and
> product ID to the list. I don't really call that broken. And it doesn't
> need a firmware.
>

Aurelien,

the device you're using is around 2 years old. You're one of the lucky
ones, I have tonns of support mails in my mail account from people who
own almost a similar device but with different videodecoders which are
not fully supported in the kernel or which worked and got broken
during the time.
It took me around 4 hours to debug such an issue last years remotly
with an enduser (which includes that noone cared to ask me if I'm fine
with such an update, neither did someone ask people who own such
devices that they should test the changes).
Please also take other devices and upcoming devices into account,
since i'm willing to spend that time and since I'm in contact with
various companies who provide several components of those devices.

> Please think that a lot of persons do not have enough knowledge to
> compile out of tree drivers, and that a lot more do not even know about
> this out of tree driver.
>

this is what all is about, the project does not depend on certain
broken drivers anymore. And people who initially disagreed without
having any solution nor contributed any code can continue to play
their game without having an impact on that driver anymore.

Markus

  reply	other threads:[~2007-10-11  6:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-10 21:50 Mauro Carvalho Chehab
2007-10-10 23:00 ` [v4l-dvb-maintainer] " Markus Rechberger
2007-10-10 23:24   ` Markus Rechberger
2007-10-10 23:35     ` Chuck Ebbert
2007-10-11  4:59       ` Markus Rechberger
2007-10-11  9:50         ` Aidan Thornton
2007-10-11 10:42           ` Pádraig Brady
2007-10-11 11:39             ` Markus Rechberger
2007-10-10 23:36   ` Andrew Morton
2007-10-11  5:09     ` Markus Rechberger
2007-10-11  5:32       ` Andrew Morton
2007-10-11  5:50         ` Markus Rechberger
2007-10-11  7:11       ` Dave Jones
2007-10-14 10:40     ` Markus Rechberger
2007-10-14 11:12       ` Hans Verkuil
2007-10-14 11:28         ` Markus Rechberger
2007-10-14 20:49       ` Johannes Stezenbach
2007-10-10 23:42   ` Linus Torvalds
2007-10-11  4:50     ` Markus Rechberger
2007-10-11  6:08       ` Aurelien Jarno
2007-10-11  6:31         ` Markus Rechberger [this message]
2007-10-11  9:33           ` Marcel Siegert
2007-10-11 10:20             ` Markus Rechberger
2007-10-11 12:54               ` Marcel Siegert
2007-10-11 13:01                 ` Markus Rechberger
2007-10-11 13:22           ` Aurelien Jarno

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=d9def9db0710102331h68e1d9b0rf3095bd9e261ec21@mail.gmail.com \
    --to=mrechberger@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=aurelien@aurel32.net \
    --cc=linux-dvb-maintainer@linuxtv.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=torvalds@linux-foundation.org \
    --cc=video4linux-list@redhat.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

all inboxes | Powered by JetHome®