Compiling thee kernel
Hi all. I cloned the kernel source-code from git://dev.laptop.org/olpc-kernel, and ran make from my Dell x86-based laptop. The compilation ran to completion successfully. However, I noticed that marvell module (in drivers/media/video) was not compiled. As a very vague guess, the reason seems to be that compiling this module requires the presence of I2C network-bus, which does not seem to be the case with the x86-based Dell laptop (which used SMBus). Is my reasoning correct? Is there a way at all to (cross-)compile the marvell module on the x86 Dell laptop? I will be grateful for any pointers :) (I am sorry if I sound too stupid.) Regards, Ajay ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Compiling thee kernel
G'day Ajay, I've never heard of such a restriction. Can you tell us the name of the branch you compiled, and what method you used? Perhaps share the output? -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Compiling thee kernel
Hi James. Thanks a ton for the reply Here are the steps I followed on my x86-based Dell laptop:: a) cd ~ b) git clone git://dev.laptop.org/olpc-kernel c) cd olpc-kernel d) make e) Wait many minutes (if not hours). Everything runs to completion. f) Haphazardly edit drivers/media/video/ov7670.c. g) Now, run make again. Because of the haphazard editing of the file in step f), the build should break. However, it doesn't, and it runs to completion as before. h) At any time, there is no object file (.o) or kernel-object (.ko) file whatsoever in the directory drivers/media/video/marvell-ccic. i) Because of observation of step h), and the fact that ov7670.h is used in the file drivers/media/video/marvell-ccic/mcam-core.c, I doubt if the marvell module is being compiled at all. j) Moreover, the I2C VS SMBus has stemmed into my imagination, looking at the file drivers/media/video/Kconfig :) Note that following the steps f) and g) after haphazardly editing a different file like drivers/media/video/tvaudio.c DOES break the build. That means that I am at least following the right ways to break the build :P James, please let me know if you require any more info. Thanks again for the help !! On Tue, Jun 11, 2013 at 4:05 PM, James Cameron qu...@laptop.org wrote: G'day Ajay, I've never heard of such a restriction. Can you tell us the name of the branch you compiled, and what method you used? Perhaps share the output? -- James Cameron http://quozl.linux.org.au/ -- Regards, Ajay Garg Dextrose Developer Activity Central: http://activitycentral.com ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Compiling thee kernel
ajay wrote: Hi James. Thanks a ton for the reply Here are the steps I followed on my x86-based Dell laptop:: a) cd ~ b) git clone git://dev.laptop.org/olpc-kernel c) cd olpc-kernel you left out: cp arch/x86/configs/xo_1.5_defconfig .config make oldconfig paul d) make e) Wait many minutes (if not hours). Everything runs to completion. f) Haphazardly edit drivers/media/video/ov7670.c. g) Now, run make again. Because of the haphazard editing of the file in step f), the build should break. However, it doesn't, and it runs to completion as before. h) At any time, there is no object file (.o) or kernel-object (.ko) file whatsoever in the directory drivers/media/video/marvell-ccic. i) Because of observation of step h), and the fact that ov7670.h is used in the file drivers/media/video/marvell-ccic/mcam-core.c, I doubt if the marvell module is being compiled at all. j) Moreover, the I2C VS SMBus has stemmed into my imagination, looking at the file drivers/media/video/Kconfig :) Note that following the steps f) and g) after haphazardly editing a different file like drivers/media/video/tvaudio.c DOES break the build. That means that I am at least following the right ways to break the build :P James, please let me know if you require any more info. Thanks again for the help !! On Tue, Jun 11, 2013 at 4:05 PM, James Cameron qu...@laptop.org wrote: G'day Ajay, I've never heard of such a restriction. Can you tell us the name of the branch you compiled, and what method you used? Perhaps share the output? -- James Cameron http://quozl.linux.org.au/ -- Regards, Ajay Garg Dextrose Developer Activity Central: http://activitycentral.com part 2 text/plain 129 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Compiling thee kernel
On Tue, Jun 11, 2013 at 6:25 PM, Paul Fox p...@laptop.org wrote: ajay wrote: Hi James. Thanks a ton for the reply Here are the steps I followed on my x86-based Dell laptop:: a) cd ~ b) git clone git://dev.laptop.org/olpc-kernel c) cd olpc-kernel you left out: cp arch/x86/configs/xo_1.5_defconfig .config make oldconfig Ohh ok.. Currently, I do not see any such file as arch/x86/configs/xo_1.5_defconfig :-\ Doing ls -l arch/x86/configs gives me :: [ajay@localhost olpc-kernel]$ ls -l arch/x86/configs/ total 16 -rw-rw-r--. 1 ajay ajay 7511 Jun 9 05:37 i386_defconfig -rw-rw-r--. 1 ajay ajay 7528 Jun 9 05:37 x86_64_defconfig Paul, a) Are there some additional steps to generate the config file for XO-1.5? b) Secondly, is the marvell module generatable only on the XO-1.5? As far as I know, the OmniVersion sensor works since the earliest series of laptops? paul d) make e) Wait many minutes (if not hours). Everything runs to completion. f) Haphazardly edit drivers/media/video/ov7670.c. g) Now, run make again. Because of the haphazard editing of the file in step f), the build should break. However, it doesn't, and it runs to completion as before. h) At any time, there is no object file (.o) or kernel-object (.ko) file whatsoever in the directory drivers/media/video/marvell-ccic. i) Because of observation of step h), and the fact that ov7670.h is used in the file drivers/media/video/marvell-ccic/mcam-core.c, I doubt if the marvell module is being compiled at all. j) Moreover, the I2C VS SMBus has stemmed into my imagination, looking at the file drivers/media/video/Kconfig :) Note that following the steps f) and g) after haphazardly editing a different file like drivers/media/video/tvaudio.c DOES break the build. That means that I am at least following the right ways to break the build :P James, please let me know if you require any more info. Thanks again for the help !! On Tue, Jun 11, 2013 at 4:05 PM, James Cameron qu...@laptop.org wrote: G'day Ajay, I've never heard of such a restriction. Can you tell us the name of the branch you compiled, and what method you used? Perhaps share the output? -- James Cameron http://quozl.linux.org.au/ -- Regards, Ajay Garg Dextrose Developer Activity Central: http://activitycentral.com part 2 text/plain 129 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- Regards, Ajay Garg Dextrose Developer Activity Central: http://activitycentral.com ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Compiling thee kernel
ajay wrote: On Tue, Jun 11, 2013 at 6:25 PM, Paul Fox p...@laptop.org wrote: ajay wrote: Hi James. Thanks a ton for the reply Here are the steps I followed on my x86-based Dell laptop:: a) cd ~ b) git clone git://dev.laptop.org/olpc-kernel c) cd olpc-kernel you left out: cp arch/x86/configs/xo_1.5_defconfig .config make oldconfig Ohh ok.. oops. you're probably still on master. there's another missing step: git checkout x86-3.3 paul Currently, I do not see any such file as arch/x86/configs/xo_1.5_defconfig :-\ Doing ls -l arch/x86/configs gives me :: [ajay@localhost olpc-kernel]$ ls -l arch/x86/configs/ total 16 -rw-rw-r--. 1 ajay ajay 7511 Jun 9 05:37 i386_defconfig -rw-rw-r--. 1 ajay ajay 7528 Jun 9 05:37 x86_64_defconfig Paul, a) Are there some additional steps to generate the config file for XO-1.5? b) Secondly, is the marvell module generatable only on the XO-1.5? As far as I know, the OmniVersion sensor works since the earliest series of laptops? paul d) make e) Wait many minutes (if not hours). Everything runs to completion. f) Haphazardly edit drivers/media/video/ov7670.c. g) Now, run make again. Because of the haphazard editing of the file in step f), the build should break. However, it doesn't, and it runs to completion as before. h) At any time, there is no object file (.o) or kernel-object (.ko) file whatsoever in the directory drivers/media/video/marvell-ccic. i) Because of observation of step h), and the fact that ov7670.h is used in the file drivers/media/video/marvell-ccic/mcam-core.c, I doubt if the marvell module is being compiled at all. j) Moreover, the I2C VS SMBus has stemmed into my imagination, looking at the file drivers/media/video/Kconfig :) Note that following the steps f) and g) after haphazardly editing a different file like drivers/media/video/tvaudio.c DOES break the build. That means that I am at least following the right ways to break the build :P James, please let me know if you require any more info. Thanks again for the help !! On Tue, Jun 11, 2013 at 4:05 PM, James Cameron qu...@laptop.org wrote: G'day Ajay, I've never heard of such a restriction. Can you tell us the name of the branch you compiled, and what method you used? Perhaps share the output? -- James Cameron http://quozl.linux.org.au/ -- Regards, Ajay Garg Dextrose Developer Activity Central: http://activitycentral.com part 2 text/plain 129 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- Regards, Ajay Garg Dextrose Developer Activity Central: http://activitycentral.com =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Compiling thee kernel
On Tue, Jun 11, 2013 at 6:38 PM, Paul Fox p...@laptop.org wrote: ajay wrote: On Tue, Jun 11, 2013 at 6:25 PM, Paul Fox p...@laptop.org wrote: ajay wrote: Hi James. Thanks a ton for the reply Here are the steps I followed on my x86-based Dell laptop:: a) cd ~ b) git clone git://dev.laptop.org/olpc-kernel c) cd olpc-kernel you left out: cp arch/x86/configs/xo_1.5_defconfig .config make oldconfig Ohh ok.. oops. you're probably still on master. there's another missing step: git checkout x86-3.3 That did it !!! ( Also, sorry and thanks to James, since the branch was the first thing he asked ). I could compile the kernel by replacing the config-file, and also managed to break it after haphazardly editing drivers/media/video/ov7670.c :) Thanks again James and Paul !!! paul Currently, I do not see any such file as arch/x86/configs/xo_1.5_defconfig :-\ Doing ls -l arch/x86/configs gives me :: [ajay@localhost olpc-kernel]$ ls -l arch/x86/configs/ total 16 -rw-rw-r--. 1 ajay ajay 7511 Jun 9 05:37 i386_defconfig -rw-rw-r--. 1 ajay ajay 7528 Jun 9 05:37 x86_64_defconfig Paul, a) Are there some additional steps to generate the config file for XO-1.5? b) Secondly, is the marvell module generatable only on the XO-1.5? As far as I know, the OmniVersion sensor works since the earliest series of laptops? paul d) make e) Wait many minutes (if not hours). Everything runs to completion. f) Haphazardly edit drivers/media/video/ov7670.c. g) Now, run make again. Because of the haphazard editing of the file in step f), the build should break. However, it doesn't, and it runs to completion as before. h) At any time, there is no object file (.o) or kernel-object (.ko) file whatsoever in the directory drivers/media/video/marvell-ccic. i) Because of observation of step h), and the fact that ov7670.h is used in the file drivers/media/video/marvell-ccic/mcam-core.c, I doubt if the marvell module is being compiled at all. j) Moreover, the I2C VS SMBus has stemmed into my imagination, looking at the file drivers/media/video/Kconfig :) Note that following the steps f) and g) after haphazardly editing a different file like drivers/media/video/tvaudio.c DOES break the build. That means that I am at least following the right ways to break the build :P James, please let me know if you require any more info. Thanks again for the help !! On Tue, Jun 11, 2013 at 4:05 PM, James Cameron qu...@laptop.org wrote: G'day Ajay, I've never heard of such a restriction. Can you tell us the name of the branch you compiled, and what method you used? Perhaps share the output? -- James Cameron http://quozl.linux.org.au/ -- Regards, Ajay Garg Dextrose Developer Activity Central: http://activitycentral.com part 2 text/plain 129 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- Regards, Ajay Garg Dextrose Developer Activity Central: http://activitycentral.com =- paul fox, p...@laptop.org -- Regards, Ajay Garg Dextrose Developer Activity Central: http://activitycentral.com ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
