Hi Guys, Even through we understand the code by reading, having a debug front would absolutely make many more things evident right. I have developed a flash media block driver kernel module long back for 2.4 and 2.6. I just used printk, proc for my debugging and nothing else. Is there a better way to debug a driver module. How do the real kernel developers do that? how do they verify the code? How if we wanne to debug the filesystem interface and some char driver interfaces like ttys etc. Regards, Mukund Jampala On 4/12/08, sahlot arvind <asahlot@xxxxxxxxx> wrote: > This much should be enough. Try to look into the source code as well. You > might not understand at this stage but just get a feel of it, that should be > fine. > Some part of any operating system is h/w specific and thus stick with one > arch at this stage e.g. x86 or ARM. > Understanding Linux kernel talks about x86 arch. So some times you might > wish to look into x86 manual in order to get a clear pic of arch and h/w > specific part of Linux. > But I would suggest for first go, just skip the h/w specific functions, just > know what they do and concentrate more on concepts and h/w independent part. > > All the best > - Arvind > > > On Sat, Apr 12, 2008 at 2:34 PM, Tero Mäntyvaara <termant@xxxxxxxxx> wrote: > > Hi, > > > > I am reading books 'Understanding Linux Kernel', 'Linux Kernel In A > Nutshell', 'Linux Device Drivers' and 'Linux Kernel Development'. Should I > read other books? What would be a nice way to start working with Linux > kernel development or maintenance? > > > > > > Tero Mäntyvaara > > > > -- > > To unsubscribe from this list: send an email with > > "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx > > Please read the FAQ at http://kernelnewbies.org/FAQ > > > > > > -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
