netdev - Re: Driver SFC: Possible bug in LM87 temperature XFP detection code

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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 29 Apr 2009 13:47:40 +0100
From:	Ben Hutchings <bhutchings@...arflare.com>
To:	Jesper Dangaard Brouer <hawk@...u.dk>
Cc:	Jesper Dangaard Brouer <hawk@...x.dk>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	Robert Olsson <Robert.Olsson@...a.slu.se>
Subject: Re: Driver SFC: Possible bug in LM87 temperature XFP detection code

On Wed, 2009-04-29 at 10:52 +0200, Jesper Dangaard Brouer wrote:
[...]
> > The "internal" temperature sensor (temp1_input) is in the LM87, which is
> > placed at the corner of the board away from the bracket and the edge
> > connector.
> >
> > The "external" temperature sensor (temp2_input) is in the SFC4000.
> 
> I though this was read from the XFP.

No.

> I was hoping the NIC supported 
> reading i2c stuff from the XFP.  Does it support that? (Robert Olsson 
> wanted to play with this stuff)

That's connected to the PHY and not the controller.  According to the
datasheet for the QT2022, you can read out the EEPROM from MDIO
registers 1.32775-1.33030 (ignoring bits 8-15).  Use the MII ioctl
interface and set phy_id to 0x441 (the formula is 0x400 | (prtad << 5) |
devad).

Ben.

-- 
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html