[PATCH 1/3] gianfar: Implement workaround for eTSEC74 erratum

Anton Vorontsov avorontsov at mvista.com
Thu Jul 1 02:38:04 EST 2010

On Tue, Jun 29, 2010 at 03:16:26PM -0700, David Miller wrote:
> I really don't see any value at all to this config option,
> the errata fixup code should be there all the time.

Well, at least for eTSEC76 erratum (patch 2/3) we have to touch
fast path (i.e. start_xmit), so I just wanted to make zero
overhead for controllers that don't need any fixups.

Not that there's much of the overhead in a single additional
'if' condition, no. ;-)

> It really does no harm to be there in the cases where it isn't
> used, and forcing users to turn this on is just another
> obscure way to end up with an incorrect configuration.

OK, resending the new patches, without Kconfig stuff...

If we'll have too many or too big errata so that it would cause
major performance or code size penalty for non-affected SOCs, we
can always do:

enum gfar_errata {

And then, priv->errata & GFAR_ERRATA_FOO will be optimized
away by the compiler.


Anton Vorontsov
email: cbouatmailru at gmail.com

More information about the Linuxppc-dev mailing list