From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Christer Weinigel <christer@weinigel.se>,
Nathan Laredo <laredo@gnu.org>,
linux-kernel@vger.kernel.org, video4linux-list@redhat.com,
v4l-dvb maintainer list <v4l-dvb-maintainer@linuxtv.org>
Subject: Re: Stradis driver conflicts with all other SAA7146 drivers
Date: Sun, 28 May 2006 11:04:47 -0300 [thread overview]
Message-ID: <1148825088.1170.45.camel@praia> (raw)
In-Reply-To: <44799D24.7050301@gmail.com>
Em Dom, 2006-05-28 às 14:52 +0159, Jiri Slaby escreveu:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> > For anyone submitting a new SAA7146 driver to the kernel in the
> > future, please be aware that your card isn't the only one that uses
> > that chip, so always add a subvendor/subdevice to your drivers.
The better is to use the existent driver instead of creating newer
ones.
> The only difference is in order of searching for devices. Stradis now gets
> control before your "real" driver. Kick stradis from your config or blacklist
> it.
This sucks. Distros should compile all drivers to support as much
hardware as possible. For now, it is better to implement Christer
suggestions.
> Or, why you ever load module, you don't want to use?
There's no safe way to make a driver to get control after the others, if
both are modules, so the option is to use the saa7146 driver instead of
stradis.
> There is no change in searching devices, it didn't check for subvendors before
> not even now. If Nathan knows, there are some subvendor/subdevices ids, which we
> should compare to, then yes, we can change the behaviour, otherwise, I am
> afraid, we can't. It's vendors' problem, that they don't use this pci registers
> (and it's evil) -- i think, that stradis cards have that two zeroed.
This is, in fact, a trouble on several video capture boards. A real
merge work should be done by migrating stradis to use the generic
support for SAA7146. Then, having just one board, those conflicts won't
happen.
>
> regards,
> - --
> Jiri Slaby www.fi.muni.cz/~xslaby
Cheers,
Mauro.
next prev parent reply other threads:[~2006-05-28 14:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-28 12:33 Christer Weinigel
2006-05-28 12:53 ` Jiri Slaby
2006-05-28 14:04 ` Mauro Carvalho Chehab [this message]
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
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=1148825088.1170.45.camel@praia \
--to=mchehab@infradead.org \
--cc=christer@weinigel.se \
--cc=jirislaby@gmail.com \
--cc=laredo@gnu.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®