From: "Amit S. Kale" <amitkale@emsyssoft.com>
To: Pavel Machek <pavel@suse.cz>, Tom Rini <trini@kernel.crashing.org>
Cc: "Amit S. Kale" <akale@users.sourceforge.net>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Split kgdb into "lite" and "normal" parts
Date: Wed, 25 Feb 2004 12:45:07 +0530 [thread overview]
Message-ID: <200402251245.07602.amitkale@emsyssoft.com> (raw)
In-Reply-To: <20040225000819.GE9209@elf.ucw.cz>
On Wednesday 25 Feb 2004 5:38 am, Pavel Machek wrote:
> Hi!
>
> > > I'll try to import kgdb into quilt to make working with it
> > > easier. [But don't expect miracles.]
> >
> > Just let us know what it takes to do so. :)
>
> This is what I did to get it under quilt. (Then, patches directory
> should be put under CVS and replace what we have in the CVS now).
Quilt is a great tool!
I follow a slightly different procedure.
I manually copy files from patches directory to cvs tree and back.
I trash my tree too many times, perhaps because I am new to quilt. Above
procedure saves my cvs tree. While cvs is meant for precisely this purpose
(save repository in a separate place where it can't be trashed), cvs sync can
take a long time when done over internet.
-Amit
>
> root@amd:/usr/src# cp -a clean.2.5/ linux-mm
> root@amd:/usr/src/linux-mm# exit
> pavel@amd:/usr/src$ cd linux-mm
> pavel@amd:/usr/src/linux-mm$ mkdir patches
> pavel@amd:/usr/src/linux-mm$ mkdir txt
> pavel@amd:/usr/src/linux-mm$ mkdir .pc
> pavel@amd:/usr/src/linux-mm$ quilt import -n core-lite
> ~/sf/kgdb-2/core-lite.patch Importing patch core-lite (stored as
> patches/core-lite)
> pavel@amd:/usr/src/linux-mm$ quilt import -n i386-lite
> ~/sf/kgdb-2/i386-lite.patch Importing patch i386-lite (stored as
> patches/i386-lite)
> pavel@amd:/usr/src/linux-mm$ quilt import -n 8250 ~/sf/kgdb-2/8250.patch
> Importing patch 8250 (stored as patches/8250)
> pavel@amd:/usr/src/linux-mm$ quilt import -n x86_64
> ~/sf/kgdb-2/x86_64.patch Importing patch x86_64 (stored as patches/x86_64)
> pavel@amd:/usr/src/linux-mm$ quilt import -n ppc ~/sf/kgdb-2/ppc.patch
> Importing patch ppc (stored as patches/ppc)
> pavel@amd:/usr/src/linux-mm$ quilt import -n core ~/sf/kgdb-2/core.patch
> Importing patch core (stored as patches/core)
> pavel@amd:/usr/src/linux-mm$ quilt import -n i386 ~/sf/kgdb-2/i386.patch
> Importing patch i386 (stored as patches/i386)
> pavel@amd:/usr/src/linux-mm$ quilt import -n eth ~/sf/kgdb-2/eth.patch
> Importing patch eth (stored as patches/eth)
> pavel@amd:/usr/src/linux-mm$
>
> At this point project is controlled with quilt. If I do
>
> pavel@amd:/usr/src/linux-mm$ quilt push 5
> Applying eth
> ...
>
> It applies all -lite patches and non-conflicting patches. I can modify
> them as I wish. At the end I need to do quilt refresh <whatever patch
> I changed>.
>
> If I wanted my changes to go into the non-lite version, instead, I'd
> have to begin with quilt push 7.
>
> > > > - All of the function pointer games (of which the weak symbols, but
> > > > not all of them) are a part of.
> > > > - kgdb_schedule/process_breakpoint, required for kgdboe, harmless to
> > > > use on serial.
> > > >
> > > >
> > > > There's still a lot of stuff I checked into linux-2.6-kgdb that's
> > > > non-trivially important
> > > > (http://ppc.bkbits.net:8080/linux-2.6-kgdb/ChangeSet@-4w?nav=index.ht
> > > >ml)
> > >
> > > Hmm, I'm not allowed to use bt :-(.
> >
> > You can look at it all via the web 'tho. There's nothing to agree to,
> > to view the web page :)
>
> Well, I took a look at the web page, but could not find all the
> kgdb-related changes easily...
> Pavel
next prev parent reply other threads:[~2004-02-25 7:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 22:50 Split kgdb into "lite" and "normal" parts Pavel Machek
2004-02-19 7:52 ` Amit S. Kale
2004-02-24 21:39 ` Tom Rini
2004-02-24 22:15 ` Pavel Machek
2004-02-24 23:21 ` Tom Rini
2004-02-24 23:27 ` Pavel Machek
2004-02-24 23:38 ` Tom Rini
2004-02-24 23:49 ` Pavel Machek
2004-02-24 23:57 ` Tom Rini
2004-02-25 0:08 ` Pavel Machek
2004-02-25 7:15 ` Amit S. Kale [this message]
2004-02-25 7:19 ` Amit S. Kale
2004-02-25 15:58 ` Tom Rini
2004-02-25 20:58 ` Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200402251245.07602.amitkale@emsyssoft.com \
--to=amitkale@emsyssoft.com \
--cc=akale@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=trini@kernel.crashing.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox