[Fwd: Re: I2C drivers]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> Would anybody mind allocating Ralf a couple ID's?  Thanks!
> 
> Phil
> 
> -------- Original Message --------
> (...)
> The two new driver IDs are:

I see three of them. Or I am drunk? ;)

> #define I2C_DRIVERID_MAX1617    56     /* temp sensor */
> #define I2C_DRIVERID_SAA7191   57      /* video encoder */
> #define I2C_DRIVERID_INDYCAM   50      /* SGI IndyCam */

MAX1617 and SAA7191 are OK, but INDYCAM will be 58.

> Also two new algorithms:
> 
> #define I2C_ALGO_SIBYTE	0x150000	/* Broadcom SiByte SOCs         */
> #define I2C_ALGO_SGI	0x160000	/* SGI algorithm                */

OK, they are yours.

> I need an ID for both 2.4 and 2.6 but I assume you keep those numbers
> in sync anyway?  The numbers above are what I'm currently using.

Yes, the numbers are more or less kept in sync. Sadly enough, not
everyone requests IDs before using them, so 2.4, 2.6 and i2c-I2C are
sometimes slightly out of sync, but most of the time everything ends up
;)

> Thanks,

You're welcome.

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/



[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux