lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 31 Oct 2008 18:38:49 +0530 From: "Shivdas Gujare" <shivdas.tech@...il.com> To: linux-kernel@...r.kernel.org Cc: beagleboard@...glegroups.com Subject: Diff between Linux-2.6.27-omap1-dirty and Linux-2.6.27-omap1 ? Hi All, I am working on testing Linux-2.6.27 omap kernel on beagle board. I cloned kernel from git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git and checked out to tag v2.6.27-omap1, I loaded kernel on beagle board, and was able to boot properly like.... OMAP3 beagleboard.org # bootm 0x80300000 ## Booting kernel from Legacy Image at 80300000 ... Image Name: Linux-2.6.27-omap1 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1614320 Bytes = 1.5 MB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Now, I done some operations, like checkout to master, checkout to v2.6.26-omap1 and v2.6.25-omap1, loaded corresponding uImages to beagle board and was able to boot board every time. After this, I again checkout to v2.6.27-omap1, compiled and loaded uImage to beagleboard But this time I am not able to boot the board. and Got the message like OMAP3 beagleboard.org # bootm 0x80300000 ## Booting kernel from Legacy Image at 80300000 ... Image Name: Linux-2.6.27-omap1-dirty Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1669176 Bytes = 1.6 MB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux........................................................................................................... done, booting the kernel. and it, stucks at here.. Here, the only difference I observed is "Image Name: Linux-2.6.27-omap1" and "Image Name: Linux-2.6.27-omap1-dirty", where uImage with second Image name is not booting. I think, I have done something wrong here, while compilation and checkout. I just want to know in what cases "-dirty" is appended to linux kernel Image Names or anything I done wrong? Thanks for your Helps. Regards, Shivdas -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists