by Guest »
Hi Eli,
Yes, VC1 is virtual channel 1 and some specially server version supporting even 7 virtual channels.
In the TLP header of a PCIE packet there is a 3-bit-field "traffic class", so each virtual channel can be configure with a one or more classes
In this way is it possible to configure different traffic ways which are connect to different applications.
Traffic Class=0 is alway connect to VC0, this is the pcie-base configuration for each intel Ixxx-chip
Before windows is loaded, in our bootloader we see VC1 isn't enabled when the bootloader then start windows
and once runnig windows what we see is windows enabled & configure the virtual channel for the hdaudio device....
The PCH chip we use, used only this VC1 channel for audio...
But it can also be use for external pcie-devices(like I350...) which support virtual-0 & 1 channelS.
And a I350 ethernet controller and if you look on the intel website all ethernet controller specially for windows-server ... support more then one virtual channel.
But this is also true not all I7 & PCH support this VC1.. even in the same family like kabe-lake some don't other support VC1.2.3....
Any way by all this discussions and the information I find on the net, step by step I see the possibilities.
Next step try to configure in such way we could avoid the jitter on our communication port.
regards, Paul.
Hi Eli,
Yes, VC1 is virtual channel 1 and some specially server version supporting even 7 virtual channels.
In the TLP header of a PCIE packet there is a 3-bit-field "traffic class", so each virtual channel can be configure with a one or more classes
In this way is it possible to configure different traffic ways which are connect to different applications.
Traffic Class=0 is alway connect to VC0, this is the pcie-base configuration for each intel Ixxx-chip
Before windows is loaded, in our bootloader we see VC1 isn't enabled when the bootloader then start windows
and once runnig windows what we see is windows enabled & configure the virtual channel for the hdaudio device....
The PCH chip we use, used only this VC1 channel for audio...
But it can also be use for external pcie-devices(like I350...) which support virtual-0 & 1 channelS.
And a I350 ethernet controller and if you look on the intel website all ethernet controller specially for windows-server ... support more then one virtual channel.
But this is also true not all I7 & PCH support this VC1.. even in the same family like kabe-lake some don't other support VC1.2.3....
Any way by all this discussions and the information I find on the net, step by step I see the possibilities.
Next step try to configure in such way we could avoid the jitter on our communication port.
regards, Paul.