Hi,

The linux VLAN interface was a good idea and we tried it.
We are using the 1588 power profile 2011, and it states that the 
device should receive untagged frames and frames with the configured VLAN ID, 
(and send with the configured VLAN ID).
This requirement to receive both untagged and configured VLAN IDs, is something 
I could not get working with the idea of giving a linux VLAN interface to 
linuxptp.

BR,
Magnus Armholt


> -----Original Message-----
> From: Magnus Armholt <magnus.armh...@gmail.com>
> Sent: maanantai 21. marraskuuta 2022 11.16
> To: Kurt Kanzenbach <k...@linutronix.de>
> Cc: Mika Paulamaki <mika.paulam...@fi.abb.com>; linuxptp-
> de...@lists.sourceforge.net
> Subject: Re: [Linuxptp-devel] [PATCH 1/1] Add configurable VLAN tags for
> Ethernet
> 
> Hi,
> Thanks a lot for the input Kurt.
> I wasnt aware of the VLAN Interface usage compatibility with linuxptp, I
> would need to try it.
> Given that the interface hw timestamping still is available through the VLAN,
> this seems like a good approach.
> 
> BR,
> Magnus Armholt
> 
> 
> 
> On Thu, Nov 17, 2022 at 1:56 PM Kurt Kanzenbach <k...@linutronix.de
> <mailto:k...@linutronix.de> > wrote:
> 
> 
>       Hi,
> 
>       On Thu Nov 17 2022, Magnus Armholt wrote:
>       > From: Mika Paulamäki <mika.paulam...@fi.abb.com
> <mailto:mika.paulam...@fi.abb.com> >
>       >
>       > Add option to include and configure VLAN tags
>       > when using transport type IEEE 802.3 (Ethernet).
> 
>       Instead of patching this to linuxptp, can't you make use of
> Linux VLAN
>       interfaces and point ptp4l to it using -i option? Also the PCP
> field can
>       be derived by setting egress-qos-map and specifying --
> socket_priority.
> 
>       Thanks,
>       Kurt
> 


_______________________________________________
Linuxptp-devel mailing list
Linuxptp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-devel

Reply via email to