Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263380AbTFYBhh (ORCPT ); Tue, 24 Jun 2003 21:37:37 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263310AbTFYBhh (ORCPT ); Tue, 24 Jun 2003 21:37:37 -0400 Received: from user-vc8fdp3.biz.mindspring.com ([216.135.183.35]:19718 "EHLO mail.nateng.com") by vger.kernel.org with ESMTP id S263451AbTFYBhf (ORCPT ); Tue, 24 Jun 2003 21:37:35 -0400 X-RAV-AntiVirus: This e-mail has been scanned for viruses on host: mail.nateng.com Date: Tue, 24 Jun 2003 18:51:09 -0700 (PDT) From: Sir Ace X-X-Sender: chandler@jordan.eng.nateng.com To: linux-kernel@vger.kernel.org Subject: Re: i2c BUG easy fix? In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2198 Lines: 69 Man how many times can I reply to my own post? Anyway I found this: linux/i2c.h:#define I2C_ADAP_MAX 16 Is there a danger is setting it to say 32? {or 31 if there is a high bit problem}? On Tue, 24 Jun 2003, Sir Ace wrote: > > Nope sory, that was wrong... I should have read the rest of the code... > Any ideas yet? {grin} > > On Tue, 24 Jun 2003, Sir Ace wrote: > > > > > It looks like the offending code might be in: > > i2c-algo-bit.c > > > > in function: > > static int test_bus(struct i2c_algo_bit_data *adap, char* name) { > > > > > > I'm no coder but it looks like it is limited to 4 devices as a hardcode? > > anyone know of a way to do it so that it does: > > > > for x := {n devices} do > > crap > > > > On Tue, 24 Jun 2003, Sir Ace wrote: > > > > > > > > I have 5 vidcapture cards, all of which show up in /proc/pci > > > Only the first 4 show up in /proc/bus/i2c* > > > > > > I tried this on 2 completely unidentical systems, and both 2.4.21, and > > > 2.4.20 > > > > > > I verified that all 5 cards are actually good... {before people start > > > pointing fingers} > > > > > > Where do I need to start looking to fix it? > > > - > > > 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/ > > > > > - > > 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/ > > > - > 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/ > - 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/