Google for "kmalloc":<br>About 182,000 results (0.11 seconds)<br><br><a href="http://lwn.net/Kernel/LDD3/" target="_blank">http://lwn.net/Kernel/LDD3/</a><br><br><a href="http://tldp.org/LDP/lkmpg/2.6/html/index.html" target="_blank">http://tldp.org/LDP/lkmpg/2.6/html/index.html</a><br>
<br>Make an effort. It usually helps :-)<br><br><div class="gmail_quote">On Mon, May 9, 2011 at 1:57 PM, Aravind Vijayan <span dir="ltr"><<a href="mailto:aravind1123@gmail.com" target="_blank">aravind1123@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div>On 5/9/11, Manohar Vanga <<a href="mailto:manohar.vanga@gmail.com" target="_blank">manohar.vanga@gmail.com</a>> wrote:<br>
> This line is incorrect. You need to learn how kmalloc (or any *alloc for<br>
> that matter) works because it seems like you don't realise what is happening<br>
> with this statement.<br>
><br>
> memory_buffer = kmalloc(1, GFP_KERNEL);<br>
><br>
><br>
<br>
</div>I am totally newbie to kernel and to drivers i wish to study about<br>
them seeking you all's help.....<br>
</blockquote></div><br><br clear="all"><br>-- <br>/manohar<br>