<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 6, 2015 at 9:57 AM, Greg KH <span dir="ltr"><<a href="mailto:greg@kroah.com" target="_blank">greg@kroah.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="">On Tue, Oct 06, 2015 at 09:26:23AM -0400, Kenneth Adam Miller wrote:<br>
> No, I didn't try it. I just wanted to ask before I got started. Thanks that<br>
> answers everything.<br>
><br>
> Any body know about the issue of assigning a process a region of physical<br>
> memory to use for it's malloc and free? I'd like to just have the process call<br>
> through to a UIO driver with an ioctl, and then once that's done it gets all<br>
> it's memory from a specific region.<br>
<br>
</span>UIO drivers do not support ioctl, why would you need/want that? What's<br>
wrong with just using the correct mmap/munmap logic that UIO userspace<br>
drivers use today?<br>
<br></blockquote><div><br></div><div><br class="">Oops, well what I wrote is the result of me doing this for the first time. Let me respond to the previous email, and in the process of doing that, you'll see what my understanding is. I don't actually need ioctl specifically, I just need to be able to have the mmap userland call to resolve specifically to what this specific driver supports. <br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
thanks,<br>
<br>
greg k-h<br>
</blockquote></div><br></div></div>