Modify ↓
Opened 15 years ago
Closed 15 years ago
#32 closed enhancement (fixed)
pcilib should handle endianess
| Reported by: | Matthias Vogelgesang | Owned by: | Suren A. Chilingaryan |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | pcilib | Version: | |
| Keywords: | Cc: | Suren A. Chilingaryan, Matthias Vogelgesang |
Description
It is quite inconvient that each client application that wants to use pcilib has to find the endianess of the host machine and act according to it. This could be done in the initialization of pcilib.
Attachments (0)
Note: See
TracTickets for help on using
tickets.
![(please configure the [header_logo] section in trac.ini)](/ufo/chrome/site/your_project_logo.png)
If I correctly understood you and you complaining about pcilib_memcpy and pcilib_datacpy calls. It is not the endianess of the host machine, but the endianess of the memory representation of PCI device that you should consider.
Generally, you are not expected to use this methods directly, but register and event API. Both this APIs should handle endianess automatically (for performance reason except of PACKED event data,in future).
Anyway, I have provided the information about device endianess within model descriptions (pcilib_model). You can use endianess variable from there and pass it to pcilib_datacpy if you want to do memcpy.