Re: 2.6.22.7 autoconf.h is screwed up

2007-09-25 Thread Jan Engelhardt
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

Re: 2.6.22.7 autoconf.h is screwed up

2007-09-25 Thread Sam Ravnborg
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

Re: 2.6.22.7 autoconf.h is screwed up

2007-09-25 Thread Sam Ravnborg
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

Re: 2.6.22.7 autoconf.h is screwed up

2007-09-25 Thread Jan Engelhardt
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

Re: 2.6.22.7 autoconf.h is screwed up

2007-09-24 Thread Jaswinder Singh
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

Re: 2.6.22.7 autoconf.h is screwed up

2007-09-24 Thread Sam Ravnborg
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

Re: 2.6.22.7 autoconf.h is screwed up

2007-09-24 Thread Jaswinder Singh
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

Re: 2.6.22.7 autoconf.h is screwed up

2007-09-24 Thread Robert P. J. Day
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

Re: 2.6.22.7 autoconf.h is screwed up

2007-09-24 Thread Jaswinder Singh
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

Re: 2.6.22.7 autoconf.h is screwed up

2007-09-24 Thread Robert P. J. Day
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

Re: 2.6.22.7 autoconf.h is screwed up

2007-09-24 Thread Jaswinder Singh
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

Re: 2.6.22.7 autoconf.h is screwed up

2007-09-24 Thread Robert P. J. Day
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

2.6.22.7 autoconf.h is screwed up

2007-09-24 Thread Jaswinder Singh
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 By just reading autoconf.h of 2.6.10 , we can understand what is the system and its configuration, it is properly arranged and divided into

2.6.22.7 autoconf.h is screwed up

2007-09-24 Thread Jaswinder Singh
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 By just reading autoconf.h of 2.6.10 , we can understand what is the system and its configuration, it is properly arranged and divided into

Re: 2.6.22.7 autoconf.h is screwed up

2007-09-24 Thread Robert P. J. Day
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,

Re: 2.6.22.7 autoconf.h is screwed up

2007-09-24 Thread Jaswinder Singh
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

Re: 2.6.22.7 autoconf.h is screwed up

2007-09-24 Thread Robert P. J. Day
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

Re: 2.6.22.7 autoconf.h is screwed up

2007-09-24 Thread Jaswinder Singh
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

Re: 2.6.22.7 autoconf.h is screwed up

2007-09-24 Thread Robert P. J. Day
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

Re: 2.6.22.7 autoconf.h is screwed up

2007-09-24 Thread Jaswinder Singh
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

Re: 2.6.22.7 autoconf.h is screwed up

2007-09-24 Thread Sam Ravnborg
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

Re: 2.6.22.7 autoconf.h is screwed up

2007-09-24 Thread Jaswinder Singh
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