From mboxrd@z Thu Jan 1 00:00:00 1970 References: <55AE3AAB.5070403@siemens.com> <55AE4068.5050102@xenomai.org> From: Jan Kiszka Message-ID: <55AE5D0B.60300@siemens.com> Date: Tue, 21 Jul 2015 16:54:03 +0200 MIME-Version: 1.0 In-Reply-To: <55AE4068.5050102@xenomai.org> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai] Xenomai 3: comapt issues with RTDM List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Philippe Gerum Cc: Xenomai On 2015-07-21 14:51, Philippe Gerum wrote: > On 07/21/2015 02:27 PM, Jan Kiszka wrote: >> Hi Philippe, >> >> just a heads up, I'll try to address this later: >> >> I received a report that include/rtdm/uapi/rtdm.h contains some data >> structures that are used between the kernel and the userspace library >> (so not directly by applications) and are not compatible with >> 32-on-64-bit (compat) scenarios. We should probably promote anything >> that is longer on 64-bit to that size, unconditionally. As this affects >> the ABI, it should be fixed before 3.0 release, ideally. >> > > That would require to fix up the client drivers (setsockopt, getsockopt > typically). Ok, I'll have a look when I'm done with testing the blackfin > port. Indeed. Just realized that there are already compat structs for the socket stuff. However, and that was what our user stumbled over, there is none for _rtdm_mmap_request. But that should be really internal, right? Jan -- Siemens AG, Corporate Technology, CT RTC ITP SES-DE Corporate Competence Center Embedded Linux