<font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2"><div>I am getting different behavior between QNX 6.5 and 6.6 with different code. I am experimenting and will let you know my results. Fairly swamped at the moment, so it may take a while.</div><div><br>Todd Peterson<br>Chief Embedded Systems Engineer<br>Management Sciences, Inc.<br>6022 Constitution Ave NE<br>Albuquerque, NM 87110<br>505-255-8611 (office)<br>505-205-7057 (cell)</div><br><br><font color="#990099">-----Elad Lahav <community-noreply@qnx.com> wrote: -----</font><div class="iNotesHistory" style="padding-left:5px;"><div style="padding-right:0px;padding-left:5px;border-left:solid black 2px;">To: "ostech-core_os@community.qnx.com" <ostech-core_os@community.qnx.com><br>From: Elad Lahav <community-noreply@qnx.com><br>Date: 09/17/2018 11:53AM<br>Subject: Re: RE: Pin mux UARTs Beaglebone Black<br><br><div><font face="Courier New,Courier,monospace" size="3">If you are suggesting that mmap(MAP_PHYS) (which is really what<br>mmap_device_io() is) depends on I/O privileges then that should not be<br>the case. It is a privileged operation, but it is based on abilities,<br>not the I/O thread flag (and the root user has the ability by default).<br><br>--Elad<br><br>On Mon, 2018-09-17 at 08:09 -0400, Albrecht Uhlmann wrote:<br>> Have you checked the return value of mmap_device_io()?<br>> <br>> <br>> <br>> _______________________________________________<br>> <br>> OSTech<br>> <a href="http://community.qnx.com/sf/go/post119117">http://community.qnx.com/sf/go/post119117</a><br>> To cancel your subscription to this discussion, please e-mail ostech-<br>> core_os-unsubscribe@community.qnx.com<br><br><br><br>_______________________________________________<br><br>OSTech<br><a href="http://community.qnx.com/sf/go/post119121">http://community.qnx.com/sf/go/post119121</a><br>To cancel your subscription to this discussion, please e-mail ostech-core_os-unsubscribe@community.qnx.com<br></font></div></div></div><div><br><br>This email message and any attachments are for the sole use of the intended recipient(s) and may contain proprietary and/or confidential information which may be privileged or otherwise protected from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient(s), please contact the sender by reply email and destroy the original message and any copies of the message as well as any attachments to the original message.</div></font> _______________________________________________ OSTech http://community.qnx.com/sf/go/post119123 To cancel your subscription to this discussion, please e-mail ostech-core_os-unsubscribe@community.qnx.com