public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: hermann pitton <hermann-pitton@arcor.de>
To: Ben Collins <ben.collins@canonical.com>,
	Hartmut Hackmann <hartmut.hackmann@t-online.de>
Cc: v4l-dvb-maintainer@linuxtv.org,
	kernel list <linux-kernel@vger.kernel.org>,
	video4linux-list@redhat.com
Subject: Re: [v4l-dvb-maintainer] saa7134 duplicate device in module, but different device_data?
Date: Fri, 27 Jun 2008 01:56:20 +0200	[thread overview]
Message-ID: <1214524580.4480.32.camel@pc10.localdom.local> (raw)
In-Reply-To: <1214501094.7150.29.camel@cunning>

Hello,

Am Donnerstag, den 26.06.2008, 13:24 -0400 schrieb Ben Collins:
> In the saa7134 module, there are these two entries in
> MODULE_DEVICE_TABLE():
> 
> 
>         },{
>                 .vendor       = PCI_VENDOR_ID_PHILIPS,
>                 .device       = PCI_DEVICE_ID_PHILIPS_SAA7133,
>                 .subvendor    = 0x185b,
>                 .subdevice    = 0xc100,
>                 .driver_data  = SAA7134_BOARD_VIDEOMATE_TV,
>         },{
>                 .vendor       = PCI_VENDOR_ID_PHILIPS,
>                 .device       = PCI_DEVICE_ID_PHILIPS_SAA7133,
>                 .subvendor    = 0x185b,
>                 .subdevice    = 0xc100,
>                 .driver_data  = SAA7134_BOARD_VIDEOMATE_TV_GOLD_PLUS,
>         },{
> 
> Both will exactly match, and I assume only the first one will ever be
> used, hence the second is just a wasted dupe. At least, I would assume
> if not for the differing driver_data. Anyway to clear up this ambiguity?
> 

there are even more devices with the same PCI device and subsystem ID
from that vendor and the problem goes also over saa7133 and saa7135
devices, for which we have no means to detect them as different, but the
saa7133 does only NTSC-M system TV sound decoding and saa7135 and the
even later saa7131e global analog TV sound.

For the early saa7133 SAA7134_BOARD_VIDEOMATE_TV we don't have eeprom
readout data and the contributor doesn't have the card anymore.
A request for helping out with such on the list had no result so far.

As of now, we can't try to separate them by eeprom differences, which
would be the best attempt and is done for some other Compro products
with similar flaws already.

Before that likely possible eeprom detection ever happens, we have two
options left to make you feel better.

Kick both out of the auto detection and the users will get a list of
supported devices printed out, from which they have to choose.

Leave the oldest one in and print some warnings that they have to look
it up for their newer cards. Naming is quite consistent, except some
early Gold Plus II variants seen first in New Zealand coming with Gold
Plus only stickers. They also come with different tuners, latest have a
separate silicon radio tuner and all such usual ...

Patches are always welcome.

Internally it was only a reminder for missing eeprom data to be
investigated.

Cheers,
Hermann





  reply	other threads:[~2008-06-26 23:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-26 17:24 saa7134 duplicate device in module, but different device_data? Ben Collins
2008-06-26 23:56 ` hermann pitton [this message]
2008-06-27  0:06   ` [v4l-dvb-maintainer] " Ben Collins
2008-06-27  0:59     ` hermann pitton
2008-06-27  1:58       ` 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=1214524580.4480.32.camel@pc10.localdom.local \
    --to=hermann-pitton@arcor.de \
    --cc=ben.collins@canonical.com \
    --cc=hartmut.hackmann@t-online.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=v4l-dvb-maintainer@linuxtv.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