Kernel Conf File For Kernel 2.6.24.4-yonggun, I've solution provided for cross compile Options

[abm_y4k]

Can someone provide me the kernel config file for this kernel version?

If possible the patches as well?

I am trying to rebuild the kernel for hostap injection support with PRISM2_DOWNLOAD_SUPPORT enable.


Thanks,

[abm_y4k]

Questions:

1. Are we missing the step to patch the kernel sources?

2. Does this cross-compiler support distcc?

3. Will

CODE

make uImage

instead of

CODE

make zImage

build for uBoot?

4. Could someone point me in the direction of the "fastfpe" and "cpufreq" patches?
(4a. They need to be applied separately right?)

5. How about tetsu's pressure sensitive patches? http://translate.google.com/translate?hl=e...cial%26hs%3D4zc

1. get the patch from yonggun's site. and apply it using patch -p0 < patch-2.6.24

2. Not sure.

3. I've not tried with uImage... since I am on sharp loader. I found uBoot give me a lot of trouble.. so I stick with the sharp

4. fastfpe and cpufreg should be in that patch provided by 2or0

5. tetsu's patch are only refer to kernel 2.4.x not for 2.6.24.4

Hope helps.

[radiochickenwax]

Thanks a lot for your help. I'm not very experienced with kernel building and still having troubles.


1.==============================================

1. get the patch from yonggun's site. and apply it using patch -p0 < patch-2.6.24

I'm not sure if this is right, but I renamed the patch from http://yonggun.tistory.com/66 to patch-2.6.24.4 and applied using

CODE

patch -p1 < patch-2.6.24.4

instead of -p0 (-p0 asked me on every step which file to patch). Is this patch valid for 2.6.24 only?

It also says on http://yonggun.tistory.com/66 that

These are patched with angstrom patches and without cpufreq.

I think the correct page for the patches is: http://yonggun.tistory.com/64, but I don't know for sure.

2.==============================================

doing

CODE

make zImage ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-

works okay.

3.==============================================

doing

CODE

make uImage ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-

immediately after says:

CODE

  CHK     include/linux/version.h
make[1]: `include/asm-arm/mach-types.h' is up to date.
  CHK     include/linux/utsrelease.h
  CALL    scripts/checksyscalls.sh
<stdin>:1097:2: warning: #warning syscall fadvise64 not implemented
<stdin>:1265:2: warning: #warning syscall migrate_pages not implemented
<stdin>:1321:2: warning: #warning syscall pselect6 not implemented
<stdin>:1325:2: warning: #warning syscall ppoll not implemented
<stdin>:1365:2: warning: #warning syscall epoll_pwait not implemented
  CHK     include/linux/compile.h
  Kernel: arch/arm/boot/Image is ready
  Kernel: arch/arm/boot/zImage is ready
  UIMAGE  arch/arm/boot/uImage
"mkimage" command not found - U-Boot images will not be built
  Image arch/arm/boot/uImage is ready

running

CODE

make clean

before doing

CODE

make uImage ...

seems to work, but I haven't flashed yet. It gives "arch/arm/boot/Image" instead of "arch/arm/boot/uImage" as I'd anticipated.

[radiochickenwax]

My next question is: how do I get uBoot to boot the kernel from SD or CF... i.e. why are there four copies (hda1,hda2,sd1,sd2) of the kernel on http://yonggun.tistory.com/72? Is this just to tell the kernel where the rootfs is?

[abm_y4k]

My next question is: how do I get uBoot to boot the kernel from SD or CF... i.e. why are there four copies (hda1,hda2,sd1,sd2) of the kernel on http://yonggun.tistory.com/72? Is this just to tell the kernel where the rootfs is?

You need to modify the kernel .config file and recompile it:

CONFIG_CMDLINE="console=ttyS0,115200n8 console=tty1 noinitrd root=/dev/hda1 rootfstype=ext3 rootdelay=1 rw fbcon=rotate:1 dyntick=enable debug"

change root=<device you want to boot it at>

[radiochickenwax]

You need to modify the kernel .config file and recompile it:

CONFIG_CMDLINE="console=ttyS0,115200n8 console=tty1 noinitrd root=/dev/hda1 rootfstype=ext3 rootdelay=1 rw fbcon=rotate:1 dyntick=enable debug"

change root=<device you want to boot it at>

Thanks! but I still don't think I'm building for uBoot properly, since there is no "uImage" in "arch/arm/boot" despite the output

CODE

make uImage ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-

gives

CODE

  Kernel: arch/arm/boot/Image is ready
  Kernel: arch/arm/boot/zImage is ready
  UIMAGE  arch/arm/boot/uImage
/usr/bin/mkimage [OPTIONS]

Options:
-f <MD5 name>       Specify an input MD5 file. MD5s must be in jigdo's
                     pseudo-base64 format
-j <jigdo name>     Specify the input jigdo file
-t <template name>  Specify the input template file
-m <item=path>      Map <item> to <path> to find the files in the mirror
-M <missing name>   Rather than try to build the image, just check that
                     all the needed files are available. If any are missing,
                     list them in this file.
-v                  Make the output logging more verbose
-l <logfile>        Specify a logfile to append to.
                     If not specified, will log to stderr
-o <outfile>        Specify a file to write the ISO image to.
                     If not specified, will write to stdout
-q                  Quick mode. Don't check MD5sums. Dangerous!
-s <bytenum>        Start byte number; will start at 0 if not specified
-e <bytenum>        End byte number; will end at EOF if not specified
-z                  Don't attempt to rebuild the image; simply print its
                     size in bytes
  Image arch/arm/boot/uImage is ready

...so I think I'm using the wrong version of "mkimage"

[abm_y4k]

You need to modify the kernel .config file and recompile it:

CONFIG_CMDLINE="console=ttyS0,115200n8 console=tty1 noinitrd root=/dev/hda1 rootfstype=ext3 rootdelay=1 rw fbcon=rotate:1 dyntick=enable debug"

change root=<device you want to boot it at>

Thanks! but I still don't think I'm building for uBoot properly, since there is no "uImage" in "arch/arm/boot" despite the output

CODE

make uImage ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-

gives

CODE

  Kernel: arch/arm/boot/Image is ready
  Kernel: arch/arm/boot/zImage is ready
  UIMAGE  arch/arm/boot/uImage
/usr/bin/mkimage [OPTIONS]

Options:
-f <MD5 name>       Specify an input MD5 file. MD5s must be in jigdo's
                     pseudo-base64 format
-j <jigdo name>     Specify the input jigdo file
-t <template name>  Specify the input template file
-m <item=path>      Map <item> to <path> to find the files in the mirror
-M <missing name>   Rather than try to build the image, just check that
                     all the needed files are available. If any are missing,
                     list them in this file.
-v                  Make the output logging more verbose
-l <logfile>        Specify a logfile to append to.
                     If not specified, will log to stderr
-o <outfile>        Specify a file to write the ISO image to.
                     If not specified, will write to stdout
-q                  Quick mode. Don't check MD5sums. Dangerous!
-s <bytenum>        Start byte number; will start at 0 if not specified
-e <bytenum>        End byte number; will end at EOF if not specified
-z                  Don't attempt to rebuild the image; simply print its
                     size in bytes
  Image arch/arm/boot/uImage is ready

...so I think I'm using the wrong version of "mkimage"

Sorry I've not did any image for uboot... maybe you can ask 2or0. He is very helpful.

uboot is not stable... why not use sharp?

Regards,