AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20090618103544.4bb0358e@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:mail.onstor.net
NSV:
SSH:
R:<rendell.fong@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@exch1.onstor.net/INBOX	0	2779531E7C760D4491C96305019FEEB52AD1B85EFD@exch1.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 18 Jun 2009 10:35:47 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: Rendell Fong <rendell.fong@onstor.com>
Subject: Re: kgdb patches
Message-ID: <20090618103547.05f7fdfc@ripper.onstor.net>
In-Reply-To: <2779531E7C760D4491C96305019FEEB52AD1B85EFD@exch1.onstor.net>
References: <2779531E7C760D4491C96305019FEEB52AD1B85EFD@exch1.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

I'm talking about the kernel source on linux-mips.org, which is the
mips specific tree.  Forget about 2.6.30, way too many things have
changed which will be dependencies to using that version.

On Thu, 18 Jun 2009 10:21:31 -0700 Rendell Fong
<rendell.fong@onstor.com> wrote:

> Andy,
> 
> I've looked the majority of change logs for releases from 2.6.22 to
> 2.6.30 trying to spot kgdb fixes. There are numerous fixes in 2.6.24,
> 2.6.26, 2.6.27 and so on.  But it's hard to tell whether they are
> relevant to our mips target. So I skipped to the latest release
> (2.6.30) and noticed that the generic arch/mips kgdb code has been
> re-factored.  It's been moved to the kernel directory and in a
> different file.  More importantly, the command set it supports is
> more robust.  We will need this updated code to support retrieving
> thread specific info and other queries.  Basically, our gdb64 expects
> the "H" and "q" commands to be supported.  It isn't in our current
> git tree but it is in 2.6.30.  I expect that more recent versions of
> gdb will expect the same and perhaps even more.
> 
> The big question is:  How do we merge in the latest kgdb updates?
> 
> Thanks,
> Rendell
> 
> 
> 
> 
> 
