Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Actually I am beginner to Linux Enviromnent and presently working on porting my existing DMA device driver to Linux 2.6.14. I am working on this since last 1 month but still could not find the right approach for a jumpstart.
My earlier DMA driver which I tested on ARM926EJS on Non-OS and VxWorks have couple of DMA API's which are exposed to end user application. Just to give you breif snapshot of 1 simple DMA API: DMA_Copy(DMA_channel Number,Source Address, Dest. Address, Size)
Now End user simply gives DMA channel number(which he already opened using other DMA API), source and destination addres of data buffer(say, placed in DDR) and any data size. My DMA driver internally configures some of the DMA hardware registers and can perform the DMA copy without any problem .
But in Linux, using ioclt calls now I can configure any DMA channel to open in kernel mode but my real problem starts when I need to pass source and destination address to perform any DMA copy from user to kernel mode. Bcoz internally driver is working at kernel mode and needs kernel Virtual address to perform any DMA copy and end user is passing User mode addresses.
So, Could anyone let me know what should be the right way to approach this driver implementation in Linux. I am also following DMA chapter of Linux Device Driver 3rd edition by Rubini but finding it really cumbersome to grasp.So it would be great if I can expect your comments on this driver implementation