linux-kernel - Re: [v4l-dvb-maintainer] [GIT PATCHES] V4L/DVB changes for 2.6.24

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 11 Oct 2007 12:20:06 +0200
From:	"Markus Rechberger" <mrechberger@...il.com>
To:	"Marcel Siegert" <mws@...uxtv.org>
Cc:	"Aurelien Jarno" <aurelien@...el32.net>,
	video4linux-list@...hat.com, linux-kernel@...r.kernel.org,
	"Mauro Carvalho Chehab" <mchehab@...radead.org>,
	linux-dvb-maintainer@...uxtv.org,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Linus Torvalds" <torvalds@...ux-foundation.org>
Subject: Re: [v4l-dvb-maintainer] [GIT PATCHES] V4L/DVB changes for 2.6.24

On 10/11/07, Marcel Siegert <mws@...uxtv.org> wrote:
> Markus Rechberger schrieb:
> > On 10/11/07, Aurelien Jarno <aurelien@...el32.net> wrote:
> >> Markus Rechberger a écrit :
> >>> On 10/11/07, Linus Torvalds <torvalds@...ux-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
>
> markus,
>
> its the same old story you are telling over and over again.
>
> of course there might be a huge community builded up the
> last month @ mcentral,
> of course your driver supports newer devices,
>
> BUT
>
> the same old story is - and you always miss that part
>
> we discussed a lot on your changes and also ACCEPTED those
> for merging, if you would have changed your UNNECCESSARY touching
> of dvb-core. its proven that things could work without that
> nacked change to dvb core. but, you decided to stop discussion then,
> and went away to perform your own tree/userspace thing.
>
> as linus and andrew stated within this thread they think they will not
> merge your code like it is cause of different reasons,
> i am wondering a bit whats your next step is.
>

I didn't read a clean statement about it. If so I won't continue to
pull out opensource drivers from that company.
Marcel, you haven't been and you are not into that topic otherwise
you'd write about missing parts and address codeparts which I have
mentioned in the past which are not ok in the kernel and how to solve
that best.
I remember the mail [1] where you (and Michael) tried to point me to
something that doesn't work out. Please get into the whole topic which
includes studying the requirements and what parts I'm complaining
about.

Markus

(just for the record, although it's not relevant anymore)
http://threebit.net/mail-archive/video4linux/msg07548.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/