Bob Picco wrote:[Thu May 03 2007, 08:17:07PM EDT]
Hi Jason:
Jason Wessel wrote: [Thu May 03 2007, 11:45:55AM EDT]
Greetings KGDB experts,
I upreved the patches from the 2.6.18 testing git archive and patched in
the missing files from the 2.6.18 git master archive on
Sergei,
While I would agree with your change, I guess I had not noticed how the
defaults had changed since I originally pushed this upstream.
My original intent was to have the default be config
KGDB_ONLY_MODULES. Then there is no need for the conditionals and
folks who need KGDB as a built
Sergei Shtylyov wrote:
I ask the question of Sergei and anyone else, if it makes more sense
to have the KGDB_ONLY_MODULES as the default?
If yes, I will make the change to have the default as using I/O
modules. If no, it makes sense to merge Sergei's change.
I'd vote against it...
I
On Sun, May 06, 2007 at 11:51:24PM -0700, Piet Delaney wrote:
On Sat, 2007-05-05 at 10:59 -0700, Tom Rini wrote:
On Fri, May 04, 2007 at 07:36:17PM -0700, Pete/Piet Delaney wrote:
Last evening I asked Andrew about it and his option is that the kernel
supports being compiled with gcc
Hello, I wrote:
While I would agree with your change, I guess I had not noticed how the
defaults had changed since I originally pushed this upstream.
When you first select KGDB, the default selected driver will be specific
to the platform, and without the change it's *always* 8250.
My
Sergei Shtylyov wrote:
In fact, you've brought up an interesting point -- when I tried
using KGDBoE as a module, I failed at that. How did you manage to
make it work?
WBR, Sergei
It used to be the case that you could build a built-in rs232 driver as
well kgdboe and load that as a
Hello.
Amit S. Kale wrote:
Looks good.
May I ask why it hasn't been committed then? :-/
Must have been difficult to find out that this was the reason for the
problems
you'd seen :-).
-Amit
Hello folks,
we've been observing different kinds of lockups and even firmware
corruption
Hello, I wrote:
Looks good.
May I ask why it hasn't been committed then? :-/
Oh, I see -- CVS didn't have lib/Kconfig.kgdb file, and Vitaly didn't care
to patch the proper file. :-)
Must have been difficult to find out that this was the reason for the
problems
you'd seen :-).
-Amit
Fix errors/warnings in the PXA and AMBA PL011 UARTs' KGDB serial drivers:
- PXA UART selection was missing;
- KGDB baud rate option was not enabled;
- write_char method took argument of type 'int' instead of 'u8'.
Signed-off-by: Vitaly Wool [EMAIL PROTECTED]
Signed-off-by: Sergey Shtylyov
Sergei Shtylyov wrote:
Fix errors/warnings in the PXA and AMBA PL011 UARTs' KGDB serial drivers:
- PXA UART selection was missing;
- KGDB baud rate option was not enabled;
- write_char method took argument of type 'int' instead of 'u8'.
Signed-off-by: Vitaly Wool [EMAIL PROTECTED]
Hello.
Jason Wessel wrote:
Fix errors/warnings in the PXA and AMBA PL011 UARTs' KGDB serial drivers:
- PXA UART selection was missing;
- KGDB baud rate option was not enabled;
- write_char method took argument of type 'int' instead of 'u8'.
Signed-off-by: Vitaly Wool [EMAIL PROTECTED]
Sergei Shtylyov wrote:
[snip snip]
we've been observing different kinds of lockups and even firmware
corruption stepping through functions w/ KGDB when KGDB and
DEBUG_PREEMPT
are enabled in the kernel. It looks like such can't be avoided,
it's just
KGDB and DEBUG_PREEMPT can't safely work
What did you run that caused the warnings to show up?
Jason.
-Original Message-
From: Pete/Piet Delaney [mailto:[EMAIL PROTECTED]
Sent: Monday, May 07, 2007 06:23 PM Pacific Standard Time
To: Wessel, Jason
Cc: Sergei Shtylyov; kgdb-bugreport@lists.sourceforge.net; Amit S.
13 matches
Mail list logo
