Skip to Content.
Sympa Menu

baslinux - [BL] patching kernel source code

baslinux AT lists.ibiblio.org

Subject: Baslinux mailing list

List archive

Chronological Thread  
  • From: baslinux AT lists.ibiblio.org
  • To: baslinux AT lists.ibiblio.org
  • Subject: [BL] patching kernel source code
  • Date: Sat, 17 Mar 2007 03:36:34 +0000 (UTC)

I have 2.2.18 source code from SW8.1 CD.

Kernel source bz2 for 2.2.26 is 15MB. (2 hours download)

The patches from 2.2.19 to 2.2.26 add up to about 2.5MB.

Busybox includes patch. patch [-p<num>] [-i <diff>] ????

I think I put the patch in the top directory of the kernel source code

patch < patch-2.2.19 (etc for 20-06)
or maybe patch patch-* ?

If I want to also keep 2.2.16 do I make a copy of 2.2.16 to /usr/src/linux-2.2.26/ and patch that, otherwise just rename it?

The only file I found with 2.2.16 in it in all of source code is version.h, which I hope the patch will modify. Can I use a 2.2.26 module with 2.2.16 and insmod -f rather than compile for 2.2.16, or maybe edit version.h before compiling for 2.2.16 again? I know that a 2.2.14 lucent module can be used in 2.2.16 with -f, but can you go backwards too?

The changes slowed down - 2.4MB in 18, 800K in 19 and 20, 200-300 K in 21-22, then a few K per version 23-26. Backports then bugfixes?

Does anyone want modules other than the Broadcom ethernet one or
an updated version of any of my kernels (which are smaller than the BL3 'big' but support things like sound, scsi, and/or framebuffer)?
The lucent modules were already compiled for 2.2.26.

keesan AT sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org




Archive powered by MHonArc 2.6.24.

Top of Page