<div dir="ltr"><div><div><br> >>>> Thanks for your answers, it sounds very straightforward.<br><br></div>ofcourse it's straightforward. Believe me its not really difficult to write low level drivers in linux. You should be more comfortable with the <br>
</div>hardware to write low level stuff. Beauty of linux is the framework it provides to make to it so easy !<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Oct 30, 2013 at 9:47 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 08:15:08PM +0530, srinivas bakki wrote:<br>
> If you don't want dynamic memory allocation for framebuffer and neither do<br>
> you want it in the user space, All you need is to pass<br>
> memmap = <size>$<start address> to the kernel and then write a kernel<br>
> module module where you ioremap that physical address space.<br>
><br>
> This is just like any other device driver where device registers are mapped.<br>
<br>
</div>Thanks for your answers, it sounds very straightforward.<br>
<br>
One more question: Currently I'm using the book Linux Device Drivers 3rd<br>
Edition (2005) as a reference, and it's discussing Kernel 2.6.10. Do you<br>
think that's still okay, or should I get/buy a more recent book on this<br>
topic, and which would you recommend?<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>