Messages in this thread | | | Date | Sat, 18 Nov 2000 14:14:26 +0100 | From | Werner Almesberger <> | Subject | Re: BTTV detection broken in 2.4.0-test11-pre5 |
| |
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/
| |