Re: suggestions: development environment

[Brett Lymn <blymn%baesystems.com.au@localhost>]

On Tue, May 20, 2008 at 11:53:46AM -0400, Jason Beaudoin wrote:
> 
> I shall be working on implementing an extension to wscons,
> incorporating a wstablet framework for better tablet support. I've
> never really worked on code for system integration or kernel
> development, so I'm curious what suggestions or notes you might be
> willing to share in setting up a test/development environment for this
> type of work.
> 

This probably won't be of much use to you since you have to talk to
a bit of real hardware but I have found running the development kernel
in qemu is a rather convenient way of testing new kernel code without
needing another machine or risking your development machine with a
buggy kernel.  An extra bonus with qemu is the -s flag which sets up
a listening port on tcp 1234 which you can attach to using gdb and
debug the kernel.  You cannot single step because the timer interrupts
get in the way but you can set breakpoints and examine data without the
kernel even being aware that you are debugging it.

-- 
Brett Lymn
"Warning:
The information contained in this email and any attached files is
confidential to BAE Systems Australia. If you are not the intended
recipient, any use, disclosure or copying of this email or any
attachments is expressly prohibited.  If you have received this email
in error, please notify us immediately. VIRUS: Every care has been
taken to ensure this email and its attachments are virus free,
however, any loss or damage incurred in using this email is not the
sender's responsibility.  It is your responsibility to ensure virus
checks are completed before installing any data sent in this email to
your computer."