Re: i2c fix?

[Sir Ace]

I doubled the original lines to this:
#define I2C_ALGO_MAX    8               /* control memory consumption   */
#define I2C_ADAP_MAX    32
#define I2C_DRIVER_MAX  32
#define I2C_CLIENT_MAX  64
#define I2C_DUMMY_MAX 8

and it did not fix my problem....  This is starting to appear
non-trivial..

Help?

  -- Sir Ace

On Tue, 24 Jun 2003, Sir Ace wrote:

>
> Ok, wrong again, the line directly above it:
> #define I2C_ALGO_MAX    4               /* control memory consumption   */
>
> That is my problem, so is it safe to up that value.
>   {Yes my final answer}
>
> {grin}
>
>   -- Sir Ace
>
> On Tue, 24 Jun 2003, Sir Ace wrote:
>
> >
> > 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 [e-mail]
> > > > > 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 [e-mail]
> > > > 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 [e-mail]
> > > 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 [e-mail]
> > 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 [e-mail]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>