<div dir="ltr"><div><div>If you don't want dynamic memory allocation for framebuffer and neither do you want it in the user space, All you need is to pass<br></div>memmap = <size>$<start address> to the kernel and then write a kernel module module where you ioremap that physical address space.<br>
<br></div>This is just like any other device driver where device registers are mapped.<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Oct 30, 2013 at 7:56 PM, Kai <span dir="ltr"><<a href="mailto:kai@kunfoo.org" target="_blank">kai@kunfoo.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Wed, Oct 30, 2013 at 04:20:30PM +0530, srinivas bakki wrote:<br>
> But otherwise am wondering why would you need to tell the FPGA these<br>
> kernel mapped addresses ? How is it connected to the memory module ?<br>
<br>
</div>The FPGA seems to have direct access to the memory. If I would allocate<br>
memory for the framebuffer dynamically, I would first have to find out<br>
the physical adress of this area, and then tell it to the FPGA, so it<br>
can read the frames from there. We are implementing a "GPU" on the FPGA<br>
here, or at least something that's reading frames from the RAM, to send<br>
it to the VGA port.<br>
<div class="HOEnZb"><div class="h5">--<br>
Grüße, Kai<br>
<br>
"In a world without walls and fences, who needs Windows and Gates?"<br>
<br>
_______________________________________________<br>
Kernelnewbies mailing list<br>
<a href="mailto:Kernelnewbies@kernelnewbies.org">Kernelnewbies@kernelnewbies.org</a><br>
<a href="http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" target="_blank">http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies</a><br>
</div></div></blockquote></div><br></div>