public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: matthieu castet <castet.matthieu@free.fr>
Cc: Linux and Kernel Video <video4linux-list@redhat.com>,
	Christer Weinigel <christer@weinigel.se>,
	linux-kernel@vger.kernel.org, Nathan Laredo <laredo@gnu.org>
Subject: Re: Stradis driver conflicts with all other SAA7146 drivers
Date: Sun, 28 May 2006 22:28:34 +0159	[thread overview]
Message-ID: <447A0809.7050207@gmail.com> (raw)
In-Reply-To: <4479E1F8.4030606@free.fr>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

matthieu castet napsal(a):
> Jiri Slaby wrote:
>> Christer Weinigel napsal(a):
>>> Why not?  There's an I2C bus with a bunch of devices on it.  Isn't it
>>> possible to do an I2C scan and if it doesn't match what's supposed to
>>> be on the card fail the probe and release the PCI resources?
>>
>> This is an older method not used for device drivers, but only for
>> searching for
>> busses or i2c et al, of which drivers stands aside and controls the
>> device.
>>
>>> If there is no FPGA or the FPGA fails to respond, that should also be
>>> a fairly good indicator that it is not a stradis board.
>>
>> Yup, but pci probing doesn't have such mechanism.
> Hum ?
> The driver have to return an error (negative value) in the probbing
> function if it detect that the card fails to respond correctly.
I meant something other. Now it's clear, ignore that sentence in my reply,
please. Of course, there is a mechanism how driver can tell layers upwards it
can't drive the device.

regrads,
- --
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

iD8DBQFEeggJMsxVwznUen4RAprXAKCNwSJpVIItEPm7cPSLvtS5xeT/gwCeI6UP
4SXefweIJhM0j2DA1wxlyZ4=
=RmKM
-----END PGP SIGNATURE-----

      reply	other threads:[~2006-05-28 20:28 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
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 [this message]

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=447A0809.7050207@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=castet.matthieu@free.fr \
    --cc=christer@weinigel.se \
    --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