All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien@aurel32.net>
To: Markus Rechberger <mrechberger@gmail.com>
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:08:07 +0200	[thread overview]
Message-ID: <470DBDC7.8000304@aurel32.net> (raw)
In-Reply-To: <d9def9db0710102150l3aa0626es90184c24875bc2e9@mail.gmail.com>

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.

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.

> it requires a firmware from userspace too so I don't think it matters
> at all if the algorithm is done in kernelspace or userspace since it
> depends on such a blob (and I cannot get the source for that firmware,
> if someone's interested in that he has to disassemble the firmware).
> 

-- 
  .''`.  Aurelien Jarno	            | GPG: 1024D/F1BCDB73
 : :' :  Debian developer           | Electrical Engineer
 `. `'   aurel32@debian.org         | aurelien@aurel32.net
   `-    people.debian.org/~aurel32 | www.aurel32.net

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

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-10 21:50 [GIT PATCHES] V4L/DVB changes for 2.6.24 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 [this message]
2007-10-11  6:31         ` Markus Rechberger
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=470DBDC7.8000304@aurel32.net \
    --to=aurelien@aurel32.net \
    --cc=akpm@linux-foundation.org \
    --cc=linux-dvb-maintainer@linuxtv.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=mrechberger@gmail.com \
    --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 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.