From: Jiri Slaby <jirislaby@gmail.com>
To: Christer Weinigel <christer@weinigel.se>
Cc: Jiri Slaby <jirislaby@gmail.com>, Nathan Laredo <laredo@gnu.org>,
linux-kernel@vger.kernel.org, video4linux-list@redhat.com,
Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: Stradis driver conflicts with all other SAA7146 drivers
Date: Sun, 28 May 2006 18:35:28 +0159 [thread overview]
Message-ID: <4479D167.4020203@gmail.com> (raw)
In-Reply-To: <m3slmui1cr.fsf@zoo.weinigel.se>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Christer Weinigel napsal(a):
> I'm running the stock Fedora Core 5 kernels, and for some reason the
> stradis driver is loaded. I suppose there's some magic in the FC5
> hotplug scripts that tries to load all device drivers that claim to
> support a certain PCI device.
Userspace now knows, that stradis can take control of this hardware, so US loads
it, because MODULE_DEVICE_TABLE is present in the driver (you may compare old
and new /lib/modules/`uname -r`/modules.pcimap). It shows us the next way, how
to solve this -- delete this TABLE line from the driver, to not advertise "I can
take control of it".
>
> I have blacklisted the stradis driver on my system, which fixes it for
> me, but it does feels as a workaround for a problem that ought to be
> fixed in the driver. If the card doesn't have a subvendor/subdevice,
> is there some way of doing a sanity check on the board to see if it
> actually is a stradis card and then release the board if it isn't?
Unfortunately not.
>
> If the driver isn't fixed I'll file a bug report on the Fedora
> bugzilla asking them to blacklist or just not compile that driver.
It is the best short-term solution, I think.
So, what to do now, Mauro, Nathan? Fix it in US (i.e. blacklist) or KS (i.e.
delete TABLE entry -- hope this helps) for the time until the driver will be
integrated?
regards,
- --
Jiri Slaby www.fi.muni.cz/~xslaby
\_.-^-._ jirislaby@gmail.com _.-^-._/
B67499670407CE62ACC8 22A032CC55C339D47A7E
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFEedFnMsxVwznUen4RAnv3AKCthKpF67t+R+iAu0cs31icG1KH2ACgnwXw
UKrSzuXdr/sBAr+rDmAdPIk=
=2R9i
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-05-28 16:35 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
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 [this message]
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=4479D167.4020203@gmail.com \
--to=jirislaby@gmail.com \
--cc=christer@weinigel.se \
--cc=laredo@gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.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