AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20090618114245.1bef2545@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	2779531E7C760D4491C96305019FEEB52AD1B85EFE@exch1.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 18 Jun 2009 11:42:49 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: Rendell Fong <rendell.fong@onstor.com>
Subject: Re: kgdb patches
Message-ID: <20090618114249.5b6ed060@ripper.onstor.net>
In-Reply-To: <2779531E7C760D4491C96305019FEEB52AD1B85EFE@exch1.onstor.net>
References: <20090618103547.05f7fdfc@ripper.onstor.net>
	<2779531E7C760D4491C96305019FEEB52AD1B85EFE@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

actually, the branch is probably not onstor-2.6.22-upstream-pull, I
think maybe it's onstor-2.6.22-tuxrx.  maybe.

On Thu, 18 Jun 2009 11:06:50 -0700 Rendell Fong
<rendell.fong@onstor.com> wrote:

> Should I be looking at the latest 2.6.22.x release?  If not, then up
> to 2.6.[23-29]?  It's still not clear to me.  Do I apply patches to
> our git tree or do I cherry pick?
> 
> 
> > -----Original Message-----
> > From: Andy Sharp
> > Sent: Thursday, June 18, 2009 10:36 AM
> > To: Rendell Fong
> > Subject: Re: kgdb patches
> > 
> > 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
> > >
> > >
> > >
> > >
> > >
