Re: [U-Boot] [PATCH] keystone2: use appropriate HD field for destination port

On 08.07.15 22:22, ivan.khoronzhuk wrote: Vitaly, On 08.07.15 21:28, Vitaly Andrianov wrote: On 07/08/2015 01:50 PM, ivan.khoronzhuk wrote: Vitaly, On 08.07.15 20:26, Vitaly Andrianov wrote: On 07/08/2015 01:05 PM, Ivan Khoronzhuk wrote: Vitaly, On 08.07.15 20:05, Vitaly Andrianov wr

Re: [U-Boot] [PATCH] keystone2: use appropriate HD field for destination port

Vitaly, On 08.07.15 20:26, Vitaly Andrianov wrote: On 07/08/2015 01:05 PM, Ivan Khoronzhuk wrote: Vitaly, On 08.07.15 20:05, Vitaly Andrianov wrote: On 07/08/2015 12:38 PM, Ivan Khoronzhuk wrote: Hi, Vitaly I suppose it's better to decide in upper driver how to use swinfo field. Like in

Re: [U-Boot] [PATCH] keystone2: use appropriate HD field for destination port

Vitaly, On 08.07.15 21:28, Vitaly Andrianov wrote: On 07/08/2015 01:50 PM, ivan.khoronzhuk wrote: Vitaly, On 08.07.15 20:26, Vitaly Andrianov wrote: On 07/08/2015 01:05 PM, Ivan Khoronzhuk wrote: Vitaly, On 08.07.15 20:05, Vitaly Andrianov wrote: On 07/08/2015 12:38 PM, Ivan Khoronzh

Re: [U-Boot] [PATCH] keystone2: use appropriate HD field for destination port

Hi, Vitaly I suppose it's better to decide in upper driver how to use swinfo field. Like in drivers/net/keystone_net.c The keystone navigator supposed to be used as a tool for communicating between different IPs, and each of them decide how to use swinfo fields. It's protocol specific informatio

Re: [U-Boot] [PATCH] keystone2: use appropriate HD field for destination port

Vitaly, On 08.07.15 20:05, Vitaly Andrianov wrote: On 07/08/2015 12:38 PM, Ivan Khoronzhuk wrote: Hi, Vitaly I suppose it's better to decide in upper driver how to use swinfo field. Like in drivers/net/keystone_net.c The keystone navigator supposed to be used as a tool for communicating bet

Re: [U-Boot] [PATCH] keystone2: use appropriate HD field for destination port

Hi, Vitaly I suppose it's better to decide in upper driver how to use swinfo field. Like in drivers/net/keystone_net.c The keystone navigator supposed to be used as a tool for communicating between different IPs, and each of them decide how to use swinfo fields. It's protocol specific informatio

Re: [U-Boot] [PATCH] keystone2: use appropriate HD field for destination port

On 07/08/2015 01:50 PM, ivan.khoronzhuk wrote: Vitaly, On 08.07.15 20:26, Vitaly Andrianov wrote: On 07/08/2015 01:05 PM, Ivan Khoronzhuk wrote: Vitaly, On 08.07.15 20:05, Vitaly Andrianov wrote: On 07/08/2015 12:38 PM, Ivan Khoronzhuk wrote: Hi, Vitaly I suppose it's better to decid

Re: [U-Boot] [PATCH] keystone2: use appropriate HD field for destination port

On 07/08/2015 01:05 PM, Ivan Khoronzhuk wrote: Vitaly, On 08.07.15 20:05, Vitaly Andrianov wrote: On 07/08/2015 12:38 PM, Ivan Khoronzhuk wrote: Hi, Vitaly I suppose it's better to decide in upper driver how to use swinfo field. Like in drivers/net/keystone_net.c The keystone navigator s

Re: [U-Boot] [PATCH] keystone2: use appropriate HD field for destination port

On 07/08/2015 12:38 PM, Ivan Khoronzhuk wrote: Hi, Vitaly I suppose it's better to decide in upper driver how to use swinfo field. Like in drivers/net/keystone_net.c The keystone navigator supposed to be used as a tool for communicating between different IPs, and each of them decide how to us

[U-Boot] [PATCH] keystone2: use appropriate HD field for destination port

K2L and L2E have different from K2HK EthSS version, which uses tag_info field for destination slave port. This commit adds the dest_port_info field to the struct pktdma_cfg, to configure which HD filed tag_info or pkt_info shall be used to configure descriptor. Before that commit the swinfo[2] was