Signed-off-by: Kieran Tyrrell
---
diff --git a/drivers/net/ethernet/intel/igb/igb.h
b/drivers/net/ethernet/intel/igb/igb.h
index 5387b3a..671c579 100644
--- a/drivers/net/ethernet/intel/igb/igb.h
+++ b/drivers/net/ethernet/intel/igb/igb.h
@@ -352,6 +352,7 @@ struct hwmon_buff
> On 15 Sep 2016, at 12:33, Richard Cochran wrote:
>
> On Thu, Sep 15, 2016 at 09:56:24AM +0100, Kieran Tyrrell wrote:
>
>> My signal delivery problem was a bug in the igb interrupt handler,
>> where I was assuming I could set a new trigger time for TT0 before
>>
I don't have a working version to post I'm afraid. But I'm considering making
the effort. Sounds like it'd be well received!
Can you share the TC concept you did? And the direction you need it to go? It
wouldn't happen to be this would it:
https://github.com/richardcochran/linuxptp-as/
I’d like to use the JBOD mode with intel i210s.
It seems like the “just use standard Linux interfaces” approach means it will
work with just about any configuration!
From: Chris Healy [mailto:cphe...@gmail.com]
Sent: Thursday, September 15, 2016 2:21 PM
To: Erik Hons
Subject:
On Thu, Sep 15, 2016 at 06:51:35PM +, Erik Hons wrote:
> Is there a technical or deliberate reason that ptp4l doesn't support
> 802.1AS time-aware bridge?
The only reason is that this feature would be a lot of work.
> If not, would the project be open to that being contributed?
(Wow, you
> On 12 Sep 2016, at 18:14, Richard Cochran wrote:
>
> On Mon, Sep 12, 2016 at 02:52:03PM +0100, Kieran Tyrrell wrote:
>
>> I agree. Previously I was finding that sending the signals directly
>> from ptp_clock_event unreliable (around 1 in 1,000,000 signals
>> seemed
On Thu, Sep 15, 2016 at 12:46:14PM +0100, Kieran Tyrrell wrote:
> I wouldn’t be comfortable removing one of the periodic outputs from
> igb in case anyone is using both.
I only meant doing this for testing purposes.
> I’ve added an ioctl to enable/disable the timer functionality on
> either of
On Thu, Sep 15, 2016 at 09:56:24AM +0100, Kieran Tyrrell wrote:
> My signal delivery problem was a bug in the igb interrupt handler,
> where I was assuming I could set a new trigger time for TT0 before
> acknowledging the interrupt. Turns out I have to disable TT0,
> acknowledge the interrupt,