Hi, re subject, would it be inappropriate to use read and write calls to communicate with a 32 bit wide interface? The fpga cannot accept byte accesses and nor do I want it to anyway. So, should I control the file position so it can only ever be on 32 bit boundaries and accept accesses in multiples of 4 bytes (returning errors otherwise), or would I be better off acessing via specific ioctl calls (passing in a pointer to a structure specifying the access) and not using normal read and write calls? The former seems unnatural and therefore probably plain wrong. If there are known examples of this in the source then please feel free to point me at them, thanks very much. Sorry again for footer - company will not remove :-(
This electronic transmission is strictly confidential and intended solely for the addressee(s). If you are not the intended addressee, you must not disclose, copy or take any action in reliance of this email. If you have received this email in error please notify the sender as soon as possible. Any views expressed within this email may not necessarily be the views held by Calrec Audio Ltd. Calrec Audio Ltd have taken measures to ensure this email is free from computer viruses, however it is recommended that you also employ anti-virus measures on your computer systems. Calrec Audio Ltd. Registered in England. Registration number: 02392336. WEEE registration number: WEE/JE0051TQ/PRO. Registered address: Nutclough Mill, Hebden Bridge, West Yorks, HX7 8EZ.
_______________________________________________ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
