From: Rene Herman <rene.herman@keyaccess.nl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@elte.hu>,
video4linux-list@redhat.com,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] V4L1: make PMS not auto-grab port 0x250
Date: Sun, 10 Aug 2008 00:01:36 +0200 [thread overview]
Message-ID: <489E13C0.4010807@keyaccess.nl> (raw)
In-Reply-To: <20080809214657.3b5318d1@lxorguk.ukuu.org.uk>
On 09-08-08 22:46, Alan Cox wrote:
> I have a PMS card. It was the hot technology of 199x about the same
> time as doom came out. I'm probably the only person who still has one
> ;)
Tsss. Lots of people still have doom...
> I'm going to NAK this however because passing in a port is a really
> dumb interface. The PMS card can only be at port 0x250 so if you load
> it there is no doubt and confusion involved.
>
> The code is fine, the behaviour is correct. Ingo should fix his
> config stuff.
He already did. The deep legacy ones such as this though I myself feel
are better of just not doing what they do.
> Just apply a tiny bit of rational thought here. There is exactly ONE
> Ingo.
And as you say yourself -- close to exactly 1 person who still has this
hardware and closer still to 0 who use it. Really, you contradict yourself:
> He's a smart cookie and can add exception lists to his tester. There
> are millions of users some of whom are brilliant, others are not
> computer wizards. The code should be optimised for them not for Ingo
> - Ingo is an optimisation for the special case not the normal
> workload!
Millions of users using PMS? I expect you are still going to NAK this
anyway out of a theoretical standpoint but please stop contradicting
yourself ;-)
We know this driver breaks the boot during useful kernel work. We know
that changing it has about a 0.0001% percent change of mattering to
anyone and then only as long as all those person can't be bothered to
setup a value in his modprobe.conf.
Now, mind you, I don't care really deeply or anything but this is the
second time today that I get a comment that places something theoretical
over something actual. I had deluded myself into thinking that was not
the way things were done here. Silly me.
Rene.
next prev parent reply other threads:[~2008-08-09 22:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-09 18:57 [PATCH] V4L1: make PMS not auto-grab port 0x250 Rene Herman
2008-08-09 20:46 ` Alan Cox
2008-08-09 20:46 ` Alan Cox
2008-08-09 22:01 ` Rene Herman [this message]
2008-08-09 21:55 ` Alan Cox
2008-08-09 21:55 ` Alan Cox
2008-08-09 22:17 ` Rene Herman
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=489E13C0.4010807@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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.