ok, I now understood where my error was. It was a mismatch between my
old kernel headers and my new kernel that I am running Pretty
stupid !
Tank's you for your time, you learn me some stuff, I appreciate it.
Antoine
2007/11/13, Eric Dumazet <[EMAIL PROTECTED]>:
> Antoine Zen-Ruffinen a éc
Antoine Zen-Ruffinen a écrit :
THIS is what I did at the beginning. But is seem me to be some thing
wrong. So I put a static value in skb->tstamp instead of
ktime_get_real() for debug purpose. And I was still becoming the
amount of second, microsecond since 1970. We are back to my initial
mail !
THIS is what I did at the beginning. But is seem me to be some thing
wrong. So I put a static value in skb->tstamp instead of
ktime_get_real() for debug purpose. And I was still becoming the
amount of second, microsecond since 1970. We are back to my initial
mail ! The value of skb->tsamp doesn't
Antoine Zen-Ruffinen a écrit :
This is exactly my problem : The driver of the network card I am using
(see rt2x00.serialmonkey.com) do the minimum in the hardware interrupt
(not filling skb->tstamp). Then netif_rx() is called later using a
tasklet (also not filling skb->tstamp). As it seem to me
no worries ont that side, In my code timeStamp is a "struct timeval".
2007/11/13, Antoine Zen-Ruffinen <[EMAIL PROTECTED]>:
> This is exactly my problem : The driver of the network card I am using
> (see rt2x00.serialmonkey.com) do the minimum in the hardware interrupt
> (not filling skb->tstamp).
This is exactly my problem : The driver of the network card I am using
(see rt2x00.serialmonkey.com) do the minimum in the hardware interrupt
(not filling skb->tstamp). Then netif_rx() is called later using a
tasklet (also not filling skb->tstamp). As it seem to me (maybe I am
wrong, if so please t
Antoine Zen-Ruffinen a écrit :
What does it bring me to have a nanosecond precision if it is not
related to the actual arrival of frame time ? As it seem I can feel
skb->tstamp with whatever I want, I always become something else using
ioctl(). (I'm using kernel 2.6.23).
2007/11/12, Eric Dumazet
Antoine Zen-Ruffinen a écrit :
What does it bring me to have a nanosecond precision if it is not
related to the actual arrival of frame time ? As it seem I can feel
skb->tstamp with whatever I want, I always become something else using
ioctl(). (I'm using kernel 2.6.23).
I guess you misunders
What does it bring me to have a nanosecond precision if it is not
related to the actual arrival of frame time ? As it seem I can feel
skb->tstamp with whatever I want, I always become something else using
ioctl(). (I'm using kernel 2.6.23).
2007/11/12, Eric Dumazet <[EMAIL PROTECTED]>:
> On Mon, 1
On Mon, 12 Nov 2007 16:42:34 +0100
"Antoine Zen-Ruffinen" <[EMAIL PROTECTED]> wrote:
> Dear all,
>
> I'm writing a network analyzer software using Linux and I need a VERY
> precise frame time stamping. Therefor I am planing to add my own time
> stamping algorithm on a modified network driver. For
Dear all,
I'm writing a network analyzer software using Linux and I need a VERY
precise frame time stamping. Therefor I am planing to add my own time
stamping algorithm on a modified network driver. For test purpose I
did so :
skb->tstamp.tv64 = 0x00010002;
netif_rx(skb);
On the
11 matches
Mail list logo
