public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christer Weinigel <christer@weinigel.se>
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
Subject: Re: Stradis driver conflicts with all other SAA7146 drivers
Date: 28 May 2006 18:02:44 +0200	[thread overview]
Message-ID: <m3slmui1cr.fsf@zoo.weinigel.se> (raw)
In-Reply-To: <44799D24.7050301@gmail.com>

Jiri Slaby <jirislaby@gmail.com> writes:

> Christer Weinigel napsal(a):
> > Hi,
> > 
> > [Nathan Laredo is the maintainer of the stradis driver but Jiri Slaby
> > submitted the PCI probing change that went into 2.6.16 so I'm Cc-ing
> > him too.  I'm not a member of the video4linux mailing list so please
> > Cc me on any responses.]
> > 
> > The stradis driver in the 2.6.16 kernel only looks at the SAA7146
> > vendor and product ID and binds to any SAA7146 based device even if it
> > is not a stradis card.  This stops all other SAA7146 drivers from
> > working, for example my WinTV Nova-T card using the budget-ci driver
> > doesn't work any longer.  A lot of other people have also been bitten
> > by this.

> 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. Or, why you ever load module, you don't want to use?
> 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.

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.

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?

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.

  /Christer

-- 
"Just how much can I get away with and still go to heaven?"

Freelance consultant specializing in device driver programming for Linux 
Christer Weinigel <christer@weinigel.se>  http://www.weinigel.se

  parent reply	other threads:[~2006-05-28 16:02 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 [this message]
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=m3slmui1cr.fsf@zoo.weinigel.se \
    --to=christer@weinigel.se \
    --cc=jirislaby@gmail.com \
    --cc=laredo@gnu.org \
    --cc=linux-kernel@vger.kernel.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