All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@redhat.com>
To: Fritz Katz <frtzkatz@yahoo.com>
Cc: video4linux-list@redhat.com
Subject: Re: What info does V-4-L expect to be in the "Identifier EEprom"?
Date: Wed, 30 Jul 2008 12:07:48 -0400	[thread overview]
Message-ID: <20080730160748.GA6695@devserv.devel.redhat.com> (raw)
In-Reply-To: <840865.6007.qm@web63010.mail.re1.yahoo.com>

On Wed, Jul 30, 2008 at 08:54:36AM -0700, Fritz Katz wrote:
> I'm a consultant for a company that wishes to produce a video cards that will run Video-4-Linux applications. The company currently produces tuners and video capture cards for Microsoft Windows.
> 
> The company wishes to include an "Identifier EEprom" on the board so V4L will 
> recognize the card and load appropriate drivers at boot-up.
> 
> Please point me in the direction of documentation for the info V4L expects to 
> be found in the ID eeprom.

This depends on the chipset. The kernel matches drivers generally by using the
PCI class code, PCI vendor/device and PCI subvendor/device. For some video
capture devices multiple vendors shipped different devices with no real
distinguishing features except internal eeprom detail.

Peering into eeproms to tell them apart is generally a last resort and if there
are unique subvendor/devicd identifiers for your card that should be all you
need except to add entries to the relevant device driver indicating the relevant
GPIO pins/tuner etc for board specific stuff.

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

  reply	other threads:[~2008-07-30 16:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-30 15:54 What info does V-4-L expect to be in the "Identifier EEprom"? Fritz Katz
2008-07-30 16:07 ` Alan Cox [this message]
2008-07-30 16:13 ` Hans Verkuil
2008-07-30 18:37   ` Fritz Katz
2008-07-30 19:04     ` Hans Verkuil
2008-07-30 20:44       ` Fritz Katz
2008-07-30 22:23         ` hermann pitton
2008-07-31 15:13 ` Steven Toth

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=20080730160748.GA6695@devserv.devel.redhat.com \
    --to=alan@redhat.com \
    --cc=frtzkatz@yahoo.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.