Re: Move kgdb init code?

Matt Porter wrote:

.... At any rate, every
one of them is potentially different and so should be calling
early_serial_init from the <board>.c or <board>_setup.c to pass in
the board-specific UART values.

I see.  I was wondering if we should move the kgdb start up
back into the board specific setup again......That way we can
choose to start up kgdb at any point in there according to board
initialization.  Of course, I still like to use xmon, and it uses
the same serial port functions as kdgb, so if we move the kgdb
initialization we should also move xmon.

Damn people. :)

My experience has been it usually gets fixed as the last required
feature before a product ships to a customer :-)

So, my concern at the beginning is whether moving it from before
ppc_md.setup_arch to after that call would have adverse effects
on those using kgdb.

Let's move it back into the board specific setup.  IMHO, it doesn't
really affect what we can debug with kgdb/xmon.  I just didn't want it
to go all of the way back to the way it was........

I'm surprised more people don't use xmon.  That is the first debugger
I usually use, since you can make it easily understand some complex
kernel data structures and associations.

Thanks.


	-- Dan


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/