We must take care that the common KDB patch (kdb-v2.0-2.4.17-common-3)
conflicts with the IA64 patch on 2.4.17(linux-2.4.17-ia64-011226.diff). (needs
to merge both patches).
I did not notice that first time and got a strange KDB behavior ( kdb_init()
was not called, and no way to quit kdb after breaking into it ).
Xavier BRU BULL ISD/R&D/INTEL office: FREC B1-422
tel : +33 (0)4 76 29 77 45 http://www-frec.bull.fr
fax : +33 (0)4 76 29 77 70 mailto:Xavier.Bru@xxxxxxxx
addr: BULL, 1 rue de Provence, BP 208, 38432 Echirolles Cedex, FRANCE
Keith Owens writes:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Content-Type: text/plain; charset=us-ascii
> Starting with kdb v2.0 there is a common patch against each kernel which
> contains all the architecture independent code plus separate architecture
> dependent patches. Apply the common patch for your kernel plus at least
> one architecture dependent patch, the architecture patches activate kdb.
> The naming convention for kdb patches is :-
> vx.y The version of kdb. x.y is updated as new features are added to kdb.
> - -v.p.s The kernel version that the patch applies to. 's' may include
> -rc or whatever numbering system the kernel keepers have thought up
> - -common The common kdb code. Everybody needs this.
> - -i386 Architecture dependent code for i386.
> - -ia64 Architecture dependent code for ia64, etc.
> - -n If there are multiple kdb patches against the same kernel version
> the last number is incremented.
> To build kdb for your kernel, apply the common kdb patch which is less
> than or equal to the kernel v.p.s, taking the highest value of '-n'
> if there is more than one. Apply the relevant arch dependent patch
> with the same value of 'vx.y-v.p.s-', taking the highest value of '-n'
> if there is more than one.
> For example, to use kdb v2.0 for i386 on kernel 2.4.17, apply
> in that order.
> This release is functionally equivalent to kdb v1.9-2.4.16, the only
> change is the reorganisation. I have a backlog of kdb changes which
> were on hold until the patches had been split, it was getting too messy
> trying to maintain at least six versions of the common kdb code and
> keep them in sync. I hope to clear the backlog soon.
> Ethan Solomita (ethan@xxxxxxxxxxxxxxx) has done a port of kdb to
> sparc64 against 2.4.13. I will upgrade that to 2.4.17 and issue
> kdb-v2.0-2.4.17-sparc64-1.bz2 "soon". kdb for ia64 has to wait until
> the 2.4.17-ia64 kernel patch is issued.
> Changelog extract.
> 2001-12-22 Keith Owens <kaos@xxxxxxx>
> * Upgrade to 2.4.17.
> * Clean up ifdef CONFIG_KDB.
> * Add ifdef CONFIG_KDB around include kdb.h.
> * Delete dummy kdb.h files for unsupported architectures.
> * Delete arch i386 and ia64 specific files. This changelog now
> applies to kdb common code only.
> * Release as kdb v2.0-2.4.17-common-1.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.4 (GNU/Linux)
> Comment: Exmh version 2.1.1 10/15/1999
> -----END PGP SIGNATURE-----