Hi,
This patch fixes the CRC error on ARM Platform.
Making the fcoe_hdr as packed structure generates correct CRC and thus
packets are not dropped.
--- open-fcoe-target.orig/fcoe/fc_fcoe.h
+++ open-fcoe-target/fcoe/fc_fcoe.h
@@ -113,7 +113,7 @@ struct fcoe_hdr {
net8_t fcoe_ver; /* version field - upper 4 bits */
net8_t fcoe_resvd[12]; /* reserved - send zero and ignore
*/
net8_t fcoe_sof; /* start of frame per RFC 3643 */
-};
+}__attribute__((packed));
#define FC_FCOE_DECAPS_VER(hp) ((hp)->fcoe_ver >> 4)
#define FC_FCOE_ENCAPS_VER(hp, ver) ((hp)->fcoe_ver = (ver) << 4)
Thanks,
Vandana
2008/6/5 Adhiraj Joshi <[EMAIL PROTECTED]>
> Hi All,
>
> I am trying to bring up fcoe on a setup where the initiator is the intel
> machine and the target is an arm machine.
> I am using Solar Flare's 10G ethernet interface for FCoE.
> After running "fcconf eth0 enable" on the initiator machine, on target I
> see following errors:
>
> fcoe_percpu_receive_thread: dropping frame with CRC error
> Oct 9 06:56:49 iop13xx kernel: frame with CRC error 000129 -> fe0000 xids
> ffff 0000 ff BLS op 0
>
> Any idea on this? Has anyone successfully tested FCoE on arm as the target
> machine?
>
> Regards,
> Adhiraj.
>
> _______________________________________________
> devel mailing list
> [email protected]
> http://www.open-fcoe.org/mailman/listinfo/devel
>
>
_______________________________________________
devel mailing list
[email protected]
http://www.open-fcoe.org/mailman/listinfo/devel
