<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi,<div><br><div><div>On 19/04/2013, at 07:13 , Owain wrote:</div><blockquote type="cite"><p dir="ltr">On 19 Apr 2013 01:39, "Andrew Cooks" <<a href="mailto:acooks@gmail.com">acooks@gmail.com</a>> wrote:<br>
><br>
> Hi Owain<br>
><br>
> How's the kernel hacking going?</p><p dir="ltr">> [snip]</p><p dir="ltr">Thanks for the support. Getting the debug messages were the key :). Find a book - Kernel device drivers, third edition, published by o'reilly helped massively also.</p></blockquote></div><br></div><div>A few pointers that might help</div><div><br></div><div>* 2.6 has BUG_ON(). Be assert()ive ;)</div><div><br></div><div>* kdb will let you go digging</div><div><br></div><div>* JTAG adaptors aren't that expensive anymore and are really useful, especially for hardware & initialisation</div><div><br></div><div>* It's common to add an ioctl() command which returns lots of debugging info. Sure it requires you make a userland tool but its often easier and better than /proc</div><div><br></div><div>Good luck with it all.</div><div><br></div><div><br></div><div>Regards,</div><div>Sheldon</div></body></html>