Hi Christian, On Thu, 9 Jan 2014 17:24:22 +0100, Christian Herzog wrote: > sorry to bother you again, but this might save you some work: I just compiled > 3.13.0-rc7 on the apu board and i2c works out of the box. I'm pretty stumped > as I'm pretty sure it didn't work OOTB on -rc3, but now it does.. Are you > aware of any Hudson-1 specific changes recently? I am not aware of anything related to Hudson-1. I don't even know the PCI IDs for that device. The git history tells that there was no change to the i2c-piix4 driver since kernel version 3.12-rc1. This is when support for secondary SMBus on AMD SB800 and AMD FCH chipsets was added. I think FCH and Hudson-2 are the same thing, not sure how Hudson-1 fits into the picture. Are you certain that the kernel version change fixed it? A BIOS update could have helped as well, or even just changing some BIOS settings. Another possibility is that some PCI or architecture quirk was added meanwhile. However a quick search did not reveal anything between 3.13-rc3 and 3.13-rc7. If you are really sure that 3.13-rc3 didn't work and 3.13-rc7 does work, and you really want to understand why, then you can bisect the git kernel tree between both points and it'll point you to the commit that fixed it. As for me, if things work for you now, I see no point in investigating further. As Wolfram already pointed out, your contribution came in a format we can't do anything with. The patch is huge, reversed, based on a source file which had indentation changes, mixes actual changes with (mostly unjustified) white-space changes, etc. If you ever need to get changes into the kernel, please follow the rules listed in Documentation/SubmittingPatches, otherwise nobody will review your work, no matter how needed you think it is. -- Jean Delvare -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
