by rajavazrala »
Hi Eli,
Thank you for the reply. Whatever we write into the device will be treated as strings, So, the driver tries to convert this to ASCII and then puts it into the FIFO.
For example, if I want to put binary 1010 into the FIFO, I will use the below command
cat > /dev/xillybus_write_32
1010
Then the driver below the device file understands this is as "1010", hence it transforms into ASCII(1)ASCII(0)ASCII(1)ASCII(0) and the resultant 32-bit word is put into the FIFO. This is how it works on the xillybus Linux platform.
So, in my case, I don't want the driver to convert from binary to strings. If I write 1010....(32bit binary) , I should see that written into FIFO without storing its equivalent ASCII value.
Thanks,
Raja
Hi Eli,
Thank you for the reply. Whatever we write into the device will be treated as strings, So, the driver tries to convert this to ASCII and then puts it into the FIFO.
For example, if I want to put binary 1010 into the FIFO, I will use the below command
cat > /dev/xillybus_write_32
1010
Then the driver below the device file understands this is as "1010", hence it transforms into ASCII(1)ASCII(0)ASCII(1)ASCII(0) and the resultant 32-bit word is put into the FIFO. This is how it works on the xillybus Linux platform.
So, in my case, I don't want the driver to convert from binary to strings. If I write 1010....(32bit binary) , I should see that written into FIFO without storing its equivalent ASCII value.
Thanks,
Raja