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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 30 May 2019 08:01:47 -0700
From:   Richard Cochran <>
To:     Vladimir Oltean <>
Cc:     Florian Fainelli <>,
        Vivien Didelot <>,
        Andrew Lunn <>,
        "David S. Miller" <>,
        John Stultz <>,
        Thomas Gleixner <>,
        Stephen Boyd <>,
        lkml <>,
        netdev <>
Subject: Re: [PATCH net-next 3/5] net: dsa: mv88e6xxx: Let taggers specify a
 can_timestamp function

On Thu, May 30, 2019 at 05:47:55PM +0300, Vladimir Oltean wrote:
> Yes, they don't identify the original frame.
> The hardware's line of thinking seems to be "The meta frame is sent
> immediately after the trapped frame that triggered the action." (quote
> from


> If there was any other way to retrieve RX timestamps I would have done
> it already.

So it cannot even possibly work.

Powered by blists - more mailing lists