Hello,
I read data from the SAS controller chip in my Windows7 driver. When I examine the values of the data that is read from the chip on Windbg watch window and compare it with the Linux “dmesg” command output for the same controller card, the values match.
But in the Linux driver code for this controller, when they read the data from the chip, for some values, they use le32_to_cpu before it is saved onto variables in the kernel space.
Both my Windows driver and the Linux driver are meant to be loaded on x86 PCs.
So, in my Win 7 driver, do I have to convert the endianness of the value read from the chip before saving to kernel variables ?
Hello, I read data from the SAS controller chip in my Windows7 driver. When I examine the values of the data that is read from the chip on Windbg watch window and compare it with the Linux “dmesg” command output for the same controller card, the values match. But in the Linux driver code for this controller, when they read the data from the chip, for some values, they use le32_to_cpu before it is saved onto variables in the kernel space.
Both my Windows driver and the Linux driver are meant to be loaded on x86 PCs. So, in my Win 7 driver, do I have to convert the endianness of the value read from the chip before saving to kernel variables ?