From: Michael Hunold <hunold@linuxtv.org>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: Christer Weinigel <christer@weinigel.se>,
v4l-dvb maintainer list <v4l-dvb-maintainer@linuxtv.org>,
linux-kernel@vger.kernel.org, video4linux-list@redhat.com,
Jiri Slaby <jirislaby@gmail.com>, Nathan Laredo <laredo@gnu.org>
Subject: Re: [v4l-dvb-maintainer] Re: Stradis driver conflicts with all other SAA7146 drivers
Date: Mon, 29 May 2006 15:43:36 +0200 [thread overview]
Message-ID: <447AFA88.1010700@linuxtv.org> (raw)
In-Reply-To: <1148909606.1170.94.camel@praia>
Hi,
on 29.05.2006 15:33 Mauro Carvalho Chehab said the following:
> On bttv and other boards, were we have such conflicts, we have an option
> to specify what board is used (called card). When the driver locates a
> board without PCI subvendor ID, it shows a help msg at dmesg and exits
> (or load a generic handler). The user may then use card=xx (where xx is
> the number of the board). IMHO, this is the better for saa7146 boards.
bttv is a monolithic driver for all devices using Bt8x8 chipsets,
whereas saa7146 and saa7146_vv only hold the core infrastructure that is
common for all saa7146 cards.
saa7146 does not know anything about a card, but the so-called extension
driver (like mxb, hexium_orion or dpc7146) does. It holds the PCI IDs
and is responsible for telling the system what card it supports and do
any probing if necessary.
I don't know where to put the card=xx parameter in that case, because
the hexium_orion does not know mxb nor dpc7146. 8-(
Since these cards don't have subvendor/subdevice IDs, it's impossible to
find out which card is in the system.
CU
Michael.
next prev parent reply other threads:[~2006-05-29 13:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-28 12:33 Stradis driver conflicts with all other SAA7146 drivers Christer Weinigel
2006-05-28 12:53 ` Jiri Slaby
2006-05-28 14:04 ` Mauro Carvalho Chehab
2006-05-28 16:01 ` Nathan Laredo
2006-05-28 16:17 ` Jiri Slaby
2006-05-28 17:31 ` Mauro Carvalho Chehab
2006-05-28 17:58 ` Christer Weinigel
2006-05-28 18:40 ` Mauro Carvalho Chehab
2006-05-29 12:46 ` [v4l-dvb-maintainer] " Michael Hunold
2006-05-29 13:33 ` Mauro Carvalho Chehab
2006-05-29 13:43 ` Michael Hunold [this message]
2006-05-29 13:58 ` Mauro Carvalho Chehab
2006-05-29 14:38 ` Gerd Hoffmann
2006-05-31 14:01 ` Alan Cox
2006-05-31 14:29 ` Arjan van de Ven
2006-05-29 12:44 ` Michael Hunold
2006-05-29 22:51 ` Christer Weinigel
2006-05-28 16:02 ` Christer Weinigel
2006-05-28 16:36 ` Jiri Slaby
2006-05-28 17:17 ` Christer Weinigel
2006-05-28 17:36 ` Jiri Slaby
2006-05-28 17:46 ` matthieu castet
2006-05-28 20:29 ` Jiri Slaby
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=447AFA88.1010700@linuxtv.org \
--to=hunold@linuxtv.org \
--cc=christer@weinigel.se \
--cc=jirislaby@gmail.com \
--cc=laredo@gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=v4l-dvb-maintainer@linuxtv.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox