From: Werner Almesberger <Werner.Almesberger@epfl.ch>
To: Gerd Knorr <kraxel@bytesex.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BTTV detection broken in 2.4.0-test11-pre5
Date: Sat, 18 Nov 2000 14:14:26 +0100 [thread overview]
Message-ID: <20001118141426.B23033@almesberger.net> (raw)
In-Reply-To: <20001117013157.A21329@almesberger.net> <slrn91b42n.fs.kraxel@bogomips.masq.in-berlin.de>
In-Reply-To: <slrn91b42n.fs.kraxel@bogomips.masq.in-berlin.de>; from kraxel@bytesex.org on Fri, Nov 17, 2000 at 08:08:55PM +0000
Gerd Knorr wrote:
> It simply did'nt work correctly and often used to misdetect
> random bt848 cards as either MIRO or Hauppauge (which where the first
> available cards).
Well, this means there's yet another mandatory __setup parameter :-(
Should it be called bttv_card or bt484_card (i.e. are there cases
where a user would want to override the card detection for non-848
bttv cards ?)
Likewise, in my radio patch, I called the parameter bt848_radio,
following the naming convention chosen for the config option. If
there are other chips, this may not be a good idea. Should I rename
this one to bttv_radio or are there no radios on non-848 chips ?
(I'll make a patch with both setup functions, since the
documentation changes overlap anyway.)
- Werner
--
_________________________________________________________________________
/ Werner Almesberger, ICA, EPFL, CH Werner.Almesberger@epfl.ch /
/_IN_N_032__Tel_+41_21_693_6621__Fax_+41_21_693_6610_____________________/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-18 13:44 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-17 0:31 BTTV detection broken in 2.4.0-test11-pre5 Werner Almesberger
2000-11-17 20:08 ` Gerd Knorr
2000-11-18 13:14 ` Werner Almesberger [this message]
2000-11-19 8:24 ` Gerd Knorr
2000-11-19 10:46 ` David Ford
2000-11-19 12:56 ` Gerd Knorr
2000-11-19 13:49 ` Keith Owens
2000-11-19 19:03 ` Gerd Knorr
2000-11-19 21:45 ` Keith Owens
2000-11-19 15:16 ` David Lang
2000-11-19 14:49 ` Alexander Viro
2000-11-19 15:11 ` Dan Hollis
2000-11-19 15:08 ` Christer Weinigel
2000-11-19 15:45 ` Alexander Viro
2000-11-19 15:54 ` Dan Hollis
2000-11-19 21:08 ` Ben Ford
2000-11-19 15:50 ` Dan Hollis
2000-11-19 16:53 ` Alan Cox
2000-11-19 20:53 ` Rogier Wolff
2000-11-20 3:22 ` Dan Hollis
2000-11-20 1:16 ` David Woodhouse
2000-11-20 3:00 ` Dan Hollis
2000-11-20 15:47 ` Ragnar Hojland Espinosa
2000-11-19 16:21 ` David Ford
2000-11-19 21:06 ` Ben Ford
2000-11-19 14:49 ` Keith Owens
2000-11-19 17:36 ` Gerd Knorr
2000-11-19 16:02 ` David Ford
2000-11-20 10:22 ` [PATCH] " Richard Guenther
2000-11-20 2:14 ` [PATCH] bttv_card & bttv_radio (was Re: BTTV detection broken in 2.4.0-test11-pre5) Werner Almesberger
-- strict thread matches above, loose matches on Subject: below --
2000-11-20 4:39 BTTV detection broken in 2.4.0-test11-pre5 Wayne.Brown
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=20001118141426.B23033@almesberger.net \
--to=werner.almesberger@epfl.ch \
--cc=kraxel@bytesex.org \
--cc=linux-kernel@vger.kernel.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