Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933469AbZFQMhk (ORCPT ); Wed, 17 Jun 2009 08:37:40 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1764744AbZFQMh1 (ORCPT ); Wed, 17 Jun 2009 08:37:27 -0400 Received: from mail.mev.co.uk ([62.49.15.74]:54644 "EHLO mail.mev.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1765419AbZFQMh0 (ORCPT ); Wed, 17 Jun 2009 08:37:26 -0400 X-Greylist: delayed 680 seconds by postgrey-1.27 at vger.kernel.org; Wed, 17 Jun 2009 08:37:26 EDT Message-ID: <4A38E0D8.1000202@mev.co.uk> Date: Wed, 17 Jun 2009 13:26:00 +0100 From: Ian Abbott User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: Herton Ronaldo Krzesinski CC: Greg KH , LKML , Gianluca Palli , David Schleef , Frank Mori Hess Subject: Re: staging driver s626 clashes with philips SAA7146 media/dvb based cards References: <200906161701.45234.herton@mandriva.com.br> <20090616205121.GB2810@suse.de> <200906161830.02308.herton@mandriva.com.br> In-Reply-To: <200906161830.02308.herton@mandriva.com.br> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2178 Lines: 52 Herton Ronaldo Krzesinski wrote: > Em Ter?a-feira 16 Junho 2009, ?s 17:51:21, Greg KH escreveu: >> On Tue, Jun 16, 2009 at 05:01:44PM -0300, Herton Ronaldo Krzesinski wrote: >>> Hi, >>> >>> The s626 (comedi) driver in staging conflicts with philips SAA7146 >>> media/dvb based cards, because it claims the same vendor:device pci id >>> for all subdevice/subvendor ids. What happens is that for people that >>> have a philips SAA7146 based card, s626 if available gets loaded by udev >>> and makes system freeze (https://qa.mandriva.com/show_bug.cgi?id=51445). >> So a PCI device that does different things has the same device ids? >> ick, stupid vendors... >> >>> Looks like s626 shouldn't claim all 1131:7146 devices, either by >>> specifying specific subdevice/subvendor ids specific to s626 devices or >>> doing additional checks in its probe/attach function. >> If you can propose the proper sub ids, or the needed checks, please send >> a patch. > > Can't propose proper sub ids here etc., as I don't know about/don't have s626 > device, s626 author is CC'ed here to check this. But I could send a patch to > disable just the build of s626 if acceptable/desired for the moment. The Windows driver () has this in the models section of the INF file: %sx26.DeviceDesc%=sxdrv.Device,PCI\VEN_1131&DEV_7146&SUBSYS_02726000 And it looks like the correct device because this the strings section contains: sx26.DeviceDesc= "Sensoray Model 626 Analog/Digital I/O" Interpreting the above information gives us: PCI Vendor ID = 0x1131 PCI Device ID = 0x7146 PCI Subvendor ID = 0x6000 PCI Subdevice ID = 0x0272 (626) The Linux SDK for this board ( has the same info in the s626core.h file. -- -=( Ian Abbott @ MEV Ltd. E-mail: )=- -=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/