linux-kernel - Re: [PATCH] Add nForce MCP61 support to i2c-nforce2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <45F4B624.7010901@vandrovec.name>
Date:	Sun, 11 Mar 2007 19:08:36 -0700
From:	Petr Vandrovec <petr@...drovec.name>
To:	Jean Delvare <khali@...ux-fr.org>
Cc:	i2c@...sensors.org, Hans-Frieder Vogt <hfvogt@....net>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Add nForce MCP61 support to i2c-nforce2

Jean Delvare wrote:
> Hi Petr,
> 
> On Sat, 10 Mar 2007 09:00:03 +0100, Petr Vandrovec wrote:
>> Hello,
>>   patch below adds support for nVidia's SMBus adapter present on Gateway's GT5414E 
>> motherboard (ECS's MCP61 PM-AM).  Patch is for current Linus's git tree.
> 
> We already have a patch doing exactly this in -mm:
> http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc3/2.6.21-rc3-mm2/broken-out/jdelvare-i2c-i2c-nforce2-add-mcp61-mcp65-support.patch

Thanks.

>> 00:01.1 SMBus: nVidia Corporation MCP61 SMBus (rev a2)
>>         Subsystem: Elitegroup Computer Systems Unknown device 2601
>>         Flags: 66MHz, fast devsel, IRQ 10
>>         I/O ports at fc00 [size=64]
>>         I/O ports at 1c00 [size=64]
>>         I/O ports at f400 [size=64]
>>         Capabilities: [44] Power Management version 2
> 
> BTW, note how the MCP61 has not 2 but 3 64-byte I/O areas declared. The
> previous chips used BAR 4 and 5, this new one additionally uses BAR 0.
> Without documentation it's hard to be sure this is a 3rd SMBus channel,
> but it sure looks so. Maybe you'll want to hack the i2c-nforce2 driver
> a bit to confirm or infirm this theory.

I had same idea as you have, so I tried to modify driver to use BAR0 as 
well, and (1) i2cdump then said that nobody is there and (2) dump of 
range fc00 was quite different from range 1c00 and f400.

So for my hardware I'm sure that BAR0 is of no use for me - if it is 3rd 
channel then either it uses different interface from nforce2, or nothing 
is connected to it.
								Petr
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/