Re: 2.6.22.7 autoconf.h is screwed up
On Sep 24 2007 16:25, Jaswinder Singh wrote: >So it is obsolete for user's point of view, right ? .config is human-readable and serves as input for kconfig, and autoconf.h is kconfig's output for the C binding that you do not mess with. Neither is obsolete, end of story. If Linux were to have Perl bindings, there would probably be an autoconf.pl. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22.7 autoconf.h is screwed up
Hi Jaswinder. On Mon, Sep 24, 2007 at 05:36:43PM +0530, Jaswinder Singh wrote: > Dear Sam, > > On 9/24/07, Sam Ravnborg <[EMAIL PROTECTED]> wrote: > > On Mon, Sep 24, 2007 at 03:50:43PM +0530, Jaswinder Singh wrote: > > > Hi all, > > > > > > 2.6.22.7's include/linux/autoconf.h is completely screwed up as > > > compare to 2.6.10's autoconf.h . > > > > > > 2.6.22.7 totally changed the meaning of autoconf.h > > > > autoconf.h has always been autogenerated. And autoconf.h has always > > been used to publish the configuration to .c files. > > > > What changed between 2.6.10 and 26.22 are the algorithm used to > > produce autoconf.h. > > I just curious, how algorithm is written that it makes readable to > non-readable. Part of a larger change. git has full history. Try to look here: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;f=scripts/kconfig/confdata.c;h=b2913e9da495bf921b9d004012adef18996f4efa;hb=HEAD It is the changes around 2006-06-09 Sam - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22.7 autoconf.h is screwed up
Hi Jaswinder. On Mon, Sep 24, 2007 at 05:36:43PM +0530, Jaswinder Singh wrote: Dear Sam, On 9/24/07, Sam Ravnborg [EMAIL PROTECTED] wrote: On Mon, Sep 24, 2007 at 03:50:43PM +0530, Jaswinder Singh wrote: Hi all, 2.6.22.7's include/linux/autoconf.h is completely screwed up as compare to 2.6.10's autoconf.h . 2.6.22.7 totally changed the meaning of autoconf.h autoconf.h has always been autogenerated. And autoconf.h has always been used to publish the configuration to .c files. What changed between 2.6.10 and 26.22 are the algorithm used to produce autoconf.h. I just curious, how algorithm is written that it makes readable to non-readable. Part of a larger change. git has full history. Try to look here: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;f=scripts/kconfig/confdata.c;h=b2913e9da495bf921b9d004012adef18996f4efa;hb=HEAD It is the changes around 2006-06-09 Sam - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22.7 autoconf.h is screwed up
On Sep 24 2007 16:25, Jaswinder Singh wrote: So it is obsolete for user's point of view, right ? .config is human-readable and serves as input for kconfig, and autoconf.h is kconfig's output for the C binding that you do not mess with. Neither is obsolete, end of story. If Linux were to have Perl bindings, there would probably be an autoconf.pl. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22.7 autoconf.h is screwed up
Dear Sam, On 9/24/07, Sam Ravnborg <[EMAIL PROTECTED]> wrote: > On Mon, Sep 24, 2007 at 03:50:43PM +0530, Jaswinder Singh wrote: > > Hi all, > > > > 2.6.22.7's include/linux/autoconf.h is completely screwed up as > > compare to 2.6.10's autoconf.h . > > > > 2.6.22.7 totally changed the meaning of autoconf.h > > autoconf.h has always been autogenerated. And autoconf.h has always > been used to publish the configuration to .c files. > > What changed between 2.6.10 and 26.22 are the algorithm used to > produce autoconf.h. I just curious, how algorithm is written that it makes readable to non-readable. Thank you, Jaswinder Singh. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22.7 autoconf.h is screwed up
On Mon, Sep 24, 2007 at 03:50:43PM +0530, Jaswinder Singh wrote: > Hi all, > > 2.6.22.7's include/linux/autoconf.h is completely screwed up as > compare to 2.6.10's autoconf.h . > > 2.6.22.7 totally changed the meaning of autoconf.h autoconf.h has always been autogenerated. And autoconf.h has always been used to publish the configuration to .c files. What changed between 2.6.10 and 26.22 are the algorithm used to produce autoconf.h. The interface to the kernel configuration is .config - and overwriting .config is an easy way to introduce a new config. autoconf.h is not suitable for this purpose and thus the actual layout does not matter. If you used to use autoconf.h for distributing kernel versions before I recommend you to use .config for now on. This should to my best knowlege also work for your 2.6.10 kernel. Sam - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22.7 autoconf.h is screwed up
hello rday, On 9/24/07, Robert P. J. Day <[EMAIL PROTECTED]> wrote: > On Mon, 24 Sep 2007, Jaswinder Singh wrote: > > > hello rday, > > > > On 9/24/07, Robert P. J. Day <[EMAIL PROTECTED]> wrote: > > > On Mon, 24 Sep 2007, Jaswinder Singh wrote: > > > > > > > hello rday, > > > > > > > > In my view autoconf.h is the index of kernel you are using. By > > > > reading autoconf.h you will know what Architecture, drivers is > > > > selected. > > > > > > > > For example, If we are using some ARM based board, If you give me > > > > your autoconf.h , I can replicate same environment as yours. If it > > > > is not properly formatted it is very difficult to read and come to > > > > some conclusion. > > > > > > no, the proper thing to do is give someone your .config file if you > > > want them to reproduce your configuration, and leave autoconf.h out of > > > it. > > > > > > > yes, you are right. So autoconf.h is obsolete and replaced by .config > > . And now autoconf.h looks so funny and scary that no body dares to > > open autoconf.h in future ;-) > > no, you're missing the point. the .config file represents your > selection of kernel options, it's what you can hand to someone if they > want to reproduce your configuration. autoconf.h, on the other hand, > is automatically generated from your .config file once you start the > build process. it is in no way "obsolete", it's used by the build > process -- it's just not meant to be manipulated by users. > > don't worry about autoconf.h, just leave it alone -- the build process > takes care of it. > So it is obsolete for user's point of view, right ? That's why it is written in such a way that no human can read it (Not human readable). right ? Thank you, Jaswinder Singh. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22.7 autoconf.h is screwed up
On Mon, 24 Sep 2007, Jaswinder Singh wrote: > hello rday, > > On 9/24/07, Robert P. J. Day <[EMAIL PROTECTED]> wrote: > > On Mon, 24 Sep 2007, Jaswinder Singh wrote: > > > > > hello rday, > > > > > > In my view autoconf.h is the index of kernel you are using. By > > > reading autoconf.h you will know what Architecture, drivers is > > > selected. > > > > > > For example, If we are using some ARM based board, If you give me > > > your autoconf.h , I can replicate same environment as yours. If it > > > is not properly formatted it is very difficult to read and come to > > > some conclusion. > > > > no, the proper thing to do is give someone your .config file if you > > want them to reproduce your configuration, and leave autoconf.h out of > > it. > > > > yes, you are right. So autoconf.h is obsolete and replaced by .config > . And now autoconf.h looks so funny and scary that no body dares to > open autoconf.h in future ;-) no, you're missing the point. the .config file represents your selection of kernel options, it's what you can hand to someone if they want to reproduce your configuration. autoconf.h, on the other hand, is automatically generated from your .config file once you start the build process. it is in no way "obsolete", it's used by the build process -- it's just not meant to be manipulated by users. don't worry about autoconf.h, just leave it alone -- the build process takes care of it. rday -- Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA http://crashcourse.ca - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22.7 autoconf.h is screwed up
hello rday, On 9/24/07, Robert P. J. Day <[EMAIL PROTECTED]> wrote: > On Mon, 24 Sep 2007, Jaswinder Singh wrote: > > > hello rday, > > > > In my view autoconf.h is the index of kernel you are using. By > > reading autoconf.h you will know what Architecture, drivers is > > selected. > > > > For example, If we are using some ARM based board, If you give me > > your autoconf.h , I can replicate same environment as yours. If it > > is not properly formatted it is very difficult to read and come to > > some conclusion. > > no, the proper thing to do is give someone your .config file if you > want them to reproduce your configuration, and leave autoconf.h out of > it. > yes, you are right. So autoconf.h is obsolete and replaced by .config . And now autoconf.h looks so funny and scary that no body dares to open autoconf.h in future ;-) Thank you, Jaswinder Singh. > rday > -- > > Robert P. J. Day > Linux Consulting, Training and Annoying Kernel Pedantry > Waterloo, Ontario, CANADA > > http://crashcourse.ca > > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22.7 autoconf.h is screwed up
On Mon, 24 Sep 2007, Jaswinder Singh wrote: > hello rday, > > In my view autoconf.h is the index of kernel you are using. By > reading autoconf.h you will know what Architecture, drivers is > selected. > > For example, If we are using some ARM based board, If you give me > your autoconf.h , I can replicate same environment as yours. If it > is not properly formatted it is very difficult to read and come to > some conclusion. no, the proper thing to do is give someone your .config file if you want them to reproduce your configuration, and leave autoconf.h out of it. rday -- Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA http://crashcourse.ca - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22.7 autoconf.h is screwed up
hello rday, In my view autoconf.h is the index of kernel you are using. By reading autoconf.h you will know what Architecture, drivers is selected. For example, If we are using some ARM based board, If you give me your autoconf.h , I can replicate same environment as yours. If it is not properly formatted it is very difficult to read and come to some conclusion. Thank you, Jaswinder Singh. On 9/24/07, Robert P. J. Day <[EMAIL PROTECTED]> wrote: > On Mon, 24 Sep 2007, Jaswinder Singh wrote: > > > Hi all, > > > > 2.6.22.7's include/linux/autoconf.h is completely screwed up as > > compare to 2.6.10's autoconf.h . > > > > 2.6.22.7 totally changed the meaning of autoconf.h > ... snip ... > > why do you care what autoconf.h looks like? it's automatically > generated, it's not something you should be messing with. > > rday > > -- > > Robert P. J. Day > Linux Consulting, Training and Annoying Kernel Pedantry > Waterloo, Ontario, CANADA > > http://crashcourse.ca > > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22.7 autoconf.h is screwed up
On Mon, 24 Sep 2007, Jaswinder Singh wrote: > Hi all, > > 2.6.22.7's include/linux/autoconf.h is completely screwed up as > compare to 2.6.10's autoconf.h . > > 2.6.22.7 totally changed the meaning of autoconf.h ... snip ... why do you care what autoconf.h looks like? it's automatically generated, it's not something you should be messing with. rday -- Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA http://crashcourse.ca - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22.7 autoconf.h is screwed up
On Mon, 24 Sep 2007, Jaswinder Singh wrote: Hi all, 2.6.22.7's include/linux/autoconf.h is completely screwed up as compare to 2.6.10's autoconf.h . 2.6.22.7 totally changed the meaning of autoconf.h ... snip ... why do you care what autoconf.h looks like? it's automatically generated, it's not something you should be messing with. rday -- Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA http://crashcourse.ca - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22.7 autoconf.h is screwed up
hello rday, In my view autoconf.h is the index of kernel you are using. By reading autoconf.h you will know what Architecture, drivers is selected. For example, If we are using some ARM based board, If you give me your autoconf.h , I can replicate same environment as yours. If it is not properly formatted it is very difficult to read and come to some conclusion. Thank you, Jaswinder Singh. On 9/24/07, Robert P. J. Day [EMAIL PROTECTED] wrote: On Mon, 24 Sep 2007, Jaswinder Singh wrote: Hi all, 2.6.22.7's include/linux/autoconf.h is completely screwed up as compare to 2.6.10's autoconf.h . 2.6.22.7 totally changed the meaning of autoconf.h ... snip ... why do you care what autoconf.h looks like? it's automatically generated, it's not something you should be messing with. rday -- Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA http://crashcourse.ca - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22.7 autoconf.h is screwed up
On Mon, 24 Sep 2007, Jaswinder Singh wrote: hello rday, In my view autoconf.h is the index of kernel you are using. By reading autoconf.h you will know what Architecture, drivers is selected. For example, If we are using some ARM based board, If you give me your autoconf.h , I can replicate same environment as yours. If it is not properly formatted it is very difficult to read and come to some conclusion. no, the proper thing to do is give someone your .config file if you want them to reproduce your configuration, and leave autoconf.h out of it. rday -- Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA http://crashcourse.ca - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22.7 autoconf.h is screwed up
hello rday, On 9/24/07, Robert P. J. Day [EMAIL PROTECTED] wrote: On Mon, 24 Sep 2007, Jaswinder Singh wrote: hello rday, In my view autoconf.h is the index of kernel you are using. By reading autoconf.h you will know what Architecture, drivers is selected. For example, If we are using some ARM based board, If you give me your autoconf.h , I can replicate same environment as yours. If it is not properly formatted it is very difficult to read and come to some conclusion. no, the proper thing to do is give someone your .config file if you want them to reproduce your configuration, and leave autoconf.h out of it. yes, you are right. So autoconf.h is obsolete and replaced by .config . And now autoconf.h looks so funny and scary that no body dares to open autoconf.h in future ;-) Thank you, Jaswinder Singh. rday -- Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA http://crashcourse.ca - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22.7 autoconf.h is screwed up
On Mon, 24 Sep 2007, Jaswinder Singh wrote: hello rday, On 9/24/07, Robert P. J. Day [EMAIL PROTECTED] wrote: On Mon, 24 Sep 2007, Jaswinder Singh wrote: hello rday, In my view autoconf.h is the index of kernel you are using. By reading autoconf.h you will know what Architecture, drivers is selected. For example, If we are using some ARM based board, If you give me your autoconf.h , I can replicate same environment as yours. If it is not properly formatted it is very difficult to read and come to some conclusion. no, the proper thing to do is give someone your .config file if you want them to reproduce your configuration, and leave autoconf.h out of it. yes, you are right. So autoconf.h is obsolete and replaced by .config . And now autoconf.h looks so funny and scary that no body dares to open autoconf.h in future ;-) no, you're missing the point. the .config file represents your selection of kernel options, it's what you can hand to someone if they want to reproduce your configuration. autoconf.h, on the other hand, is automatically generated from your .config file once you start the build process. it is in no way obsolete, it's used by the build process -- it's just not meant to be manipulated by users. don't worry about autoconf.h, just leave it alone -- the build process takes care of it. rday -- Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA http://crashcourse.ca - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22.7 autoconf.h is screwed up
hello rday, On 9/24/07, Robert P. J. Day [EMAIL PROTECTED] wrote: On Mon, 24 Sep 2007, Jaswinder Singh wrote: hello rday, On 9/24/07, Robert P. J. Day [EMAIL PROTECTED] wrote: On Mon, 24 Sep 2007, Jaswinder Singh wrote: hello rday, In my view autoconf.h is the index of kernel you are using. By reading autoconf.h you will know what Architecture, drivers is selected. For example, If we are using some ARM based board, If you give me your autoconf.h , I can replicate same environment as yours. If it is not properly formatted it is very difficult to read and come to some conclusion. no, the proper thing to do is give someone your .config file if you want them to reproduce your configuration, and leave autoconf.h out of it. yes, you are right. So autoconf.h is obsolete and replaced by .config . And now autoconf.h looks so funny and scary that no body dares to open autoconf.h in future ;-) no, you're missing the point. the .config file represents your selection of kernel options, it's what you can hand to someone if they want to reproduce your configuration. autoconf.h, on the other hand, is automatically generated from your .config file once you start the build process. it is in no way obsolete, it's used by the build process -- it's just not meant to be manipulated by users. don't worry about autoconf.h, just leave it alone -- the build process takes care of it. So it is obsolete for user's point of view, right ? That's why it is written in such a way that no human can read it (Not human readable). right ? Thank you, Jaswinder Singh. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22.7 autoconf.h is screwed up
On Mon, Sep 24, 2007 at 03:50:43PM +0530, Jaswinder Singh wrote: Hi all, 2.6.22.7's include/linux/autoconf.h is completely screwed up as compare to 2.6.10's autoconf.h . 2.6.22.7 totally changed the meaning of autoconf.h autoconf.h has always been autogenerated. And autoconf.h has always been used to publish the configuration to .c files. What changed between 2.6.10 and 26.22 are the algorithm used to produce autoconf.h. The interface to the kernel configuration is .config - and overwriting .config is an easy way to introduce a new config. autoconf.h is not suitable for this purpose and thus the actual layout does not matter. If you used to use autoconf.h for distributing kernel versions before I recommend you to use .config for now on. This should to my best knowlege also work for your 2.6.10 kernel. Sam - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22.7 autoconf.h is screwed up
Dear Sam, On 9/24/07, Sam Ravnborg [EMAIL PROTECTED] wrote: On Mon, Sep 24, 2007 at 03:50:43PM +0530, Jaswinder Singh wrote: Hi all, 2.6.22.7's include/linux/autoconf.h is completely screwed up as compare to 2.6.10's autoconf.h . 2.6.22.7 totally changed the meaning of autoconf.h autoconf.h has always been autogenerated. And autoconf.h has always been used to publish the configuration to .c files. What changed between 2.6.10 and 26.22 are the algorithm used to produce autoconf.h. I just curious, how algorithm is written that it makes readable to non-readable. Thank you, Jaswinder Singh. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
