From: David Miller <davem@davemloft.net>
To: avorontsov@mvista.com
Cc: netdev@vger.kernel.org, Manfred.Rudigier@omicron.at,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] gianfar: Revive the driver for eTSEC devices (disable timestamping)
Date: Wed, 09 Jun 2010 16:27:25 -0700 (PDT) [thread overview]
Message-ID: <20100609.162725.189714554.davem@davemloft.net> (raw)
In-Reply-To: <20100609193219.GA8629@oksana.dev.rtsoft.ru>
From: Anton Vorontsov <avorontsov@mvista.com>
Date: Wed, 9 Jun 2010 23:32:19 +0400
> Since commit cc772ab7cdcaa24d1fae332d92a1602788644f7a ("gianfar: Add
> hardware RX timestamping support"), the driver no longer works on
> at least MPC8313ERDB and MPC8568EMDS boards (and possibly much more
> boards as well).
>
> That's how MPC8313 Reference Manual describes RCTRL_TS_ENABLE bit:
>
> Timestamp incoming packets as padding bytes. PAL field is set
> to 8 if the PAL field is programmed to less than 8. Must be set
> to zero if TMR_CTRL[TE]=0.
>
> I see that the commit above sets this bit, but it doesn't handle
> TMR_CTRL. Manfred probably had this bit set by the firmware for
> his boards. But obviously this isn't true for all boards in the
> wild.
>
> Also, I recall that Freescale BSPs were explicitly disabling the
> timestamping because of a performance drop.
>
> For now, the best way to deal with this is just disable the
> timestamping, and later we can discuss proper device tree bindings
> and implement enabling this feature via some property.
>
> Signed-off-by: Anton Vorontsov <avorontsov@mvista.com>
Agreed, applied, thanks Anton.
next prev parent reply other threads:[~2010-06-09 23:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 19:32 [PATCH] gianfar: Revive the driver for eTSEC devices (disable timestamping) Anton Vorontsov
2010-06-09 23:27 ` David Miller [this message]
2010-06-10 6:29 ` Richard Cochran
2010-06-10 9:31 ` Anton Vorontsov
2010-06-10 10:22 ` Richard Cochran
2010-06-10 10:41 ` Anton Vorontsov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100609.162725.189714554.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Manfred.Rudigier@omicron.at \
--cc=avorontsov@mvista.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).