netdev - mv643xx_eth: Delay required in reading the PHY registers.

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

Message-ID: <bb58ac4d0905052238m59ca2767i1e84d90b6abb46d4@mail.gmail.com>
Date:	Wed, 6 May 2009 11:08:07 +0530
From:	Upakul Barkakaty <upakul@...il.com>
To:	netdev@...r.kernel.org
Subject: mv643xx_eth: Delay required in reading the PHY registers.

Hi all,

I am using the Marvell ethernet driver[mv643xx_eth]. The function
eth_port_read_smi_reg(), uses a delay in order to wait for the SMI
register to become available.

Does anyone have any clue how much time it actually takes for the SMI
register to become available? Actually I am using an older version of
the driver which does not use the udelay functions in the loops. It
rather has a "for" loop for putting a timeout. Now the gcc-4.3.1
compiler optimizes out the "for" loop. So I need to replace the "for"
loop with a delay function. Now the question is "how much delay would
be appropriate".

Any replies in this regard would be appreciated.

--
Regards,
Upakul Barkakaty
--
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