I tried in rewriting the driver... but I can't understand the right way...

since sb800 is a southbus, the mux driver must be defined as
i2c_device, platform_device, or pci_device?

I tried using i2c_device structure, but I can't make sb800 to match
the id_Table..
I tried usign pci_device structure, but the driver overwrite the pci
space so kernel hangs...

Regards, Eddi.

On Sat, Dec 3, 2011 at 6:08 PM, Jean Delvare <kh...@linux-fr.org> wrote:
> Hi Eddi,
> On Sat, 3 Dec 2011 17:42:16 +0100, Eddi De Pieri wrote:
>> Actually I don't have a development system with latest git. I build my
>> patch on my debian with 2.6.32 kernel..
>> The patch is based on i2c-amd756-s4882.c and adapted to work with sb8xx...
>> i2c-amd756-s4882.c is still present and don't use i2c-mux infrastructure.
> That's because i2c-amd756-s4882.c was written before the i2c-mux
> infrastructure was available. Ideally SMBus multiplexing support on the
> Tyan S4882 would be converted to i2c-mux (i.e. i2c-amd756-s4882.c would
> be deleted and the multiplexer would be instantiated in i2c-amd756.c
> itself, based on DMI data.) This shouldn't be particularly difficult,
> the real difficulty is to find someone with one of these boards to test
> the changes.
>> However if you are interested in porting my work to latest git, you
>> will be welcome!
> That's not how it works, sorry. Submissions must be based on a recent
> kernel in order to be accepted upstream. If you want SMBus multiplexing
> support on your system, it will have to be based on i2c-mux, because
> that's how things work now. Otherwise I will not accept your code.
> --
> Jean Delvare
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to