lm_sensors2/prog/dump i2cbusses.c

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

 



On Sat, Nov 29, 2003 at 08:17:41PM +0100, Jean Delvare wrote:
> > The 2.6 i2c-dev bus numbers don't necessarily match i2c-adapter bus
> > numbers.
> > If you rmmod and re-insmod a bus driver, the driver seems to get its
> > old i2c-dev bus number back. But the i2c-adapter number increments.
> > Don't know why. It would be much better if they matched.
> > 
> > Most userspace tools need the i2c-dev numbers since they are going
> > to use /dev/i2c-x devices to access the bus.
> > 
> > The bus numbers reported by libsensors apps are the i2c-adapter
> > numbers. I think it has to be that way since we don't need i2c-dev and
> > therefore can't count on it being installed.
> > 
> > So you can't take a bus number from 'sensors' and then take that
> > number and use it in 'i2cdump', for example.
> 
> This is odd. Any idea how to correct this? I'm a bit lost, I don't even
> understand how there can be two values, since it obviously represent the
> same thing (i.e. a bus identifier).

No, they are independent things.  Just so happens that they were the
same in all previous kernels :)

But if it's a big pain, I can see about fixing it up to match.

thanks,

greg k-h



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

  Powered by Linux