From: "Nicolas Léveillé" <knos@free.fr>
To: linux-media@vger.kernel.org
Subject: Strange PCI IDs
Date: Mon, 25 May 2009 23:26:36 +0200 [thread overview]
Message-ID: <4A1B0D0C.7040707@free.fr> (raw)
Hello,
While discovering the bttv code (I'd like to add support to a yet
unsupported bttv derivative, the PMS PDI Deluxe) I found a strange commit:
changeset: 10944:6b90215088f0
user: Mauro Carvalho Chehab <mchehab@redhat.com>
date: Wed Mar 11 08:18:53 2009 -0300
summary: Conceptronic CTVFMI2 PCI Id
within: linux/drivers/media/video/bt8xx/bttv-cards.c
{ 0x109e036e, BTTV_BOARD_CONCEPTRONIC_CTVFMI2, "Conceptronic
CTVFMi v2"},
Does the above work at all for autodetecting this card?
The PCI ID looks suspiciously like a generic PCI ID, especially
considering that:
109e : vendor id for "Brooktree Corporation"
036e : device id for "Bt878 Video Capture"
So I immediately was surprised to see the above PCI ID constant.
It does not appear it would cause any problem since the vendor and
device ids are reversed anyway, however is this really correct?
Shouldn't there be a comment about it?
Cheers,
Nicolas Léveillé
next reply other threads:[~2009-05-25 21:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 21:26 Nicolas Léveillé [this message]
2009-05-25 22:21 ` Strange PCI IDs hermann pitton
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=4A1B0D0C.7040707@free.fr \
--to=knos@free.fr \
--cc=linux-media@vger.kernel.org \
/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