From diy-linux-dev@diy-linux.org  Sat Jan 26 02:13:16 2008
From: diy-linux-dev@diy-linux.org (Greg Schafer)
Date: Sat, 26 Jan 2008 12:13:16 +1100
Subject: 2.6.24 kernel
Message-ID: <20080126011316.GA3050@eyo32.local>

Hi list,

If you've been following kernel development lately you'll know that the i386
and x86_64 arches have been merged into one super arch, "x86". This has the
interesting side-effect for headers_install of creating identical header
sets for each arch ie: following commands all produce an identical set of
headers:

make headers_install INSTALL_HDR_PATH=temp
make headers_install INSTALL_HDR_PATH=temp ARCH=i386
make headers_install INSTALL_HDR_PATH=temp ARCH=x86_64
make headers_install INSTALL_HDR_PATH=temp ARCH=x86

This means I could simplify this section of the Temptools headers install in
the Next Gen build:

case $DIY_TARGET in
  i?86*)	KARCH=i386 ;;
  powerpc-*)	KARCH=powerpc ;;
  x86_64*)	KARCH=x86_64 ;;
esac

And another interesting tidbit I haven't seen publicized, if you configure
your kernel like this:

make menuconfig ARCH=x86

you'll get an additional new menu item to choose a 64-bit kernel. Just try
it out to see what I mean. Of course, you'll need a 64-bit capable toolchain
to compile such a kernel. BTW, I haven't tested any of this yet..

Regards
Greg


From diy-linux-dev@diy-linux.org  Sat Jan 26 02:52:36 2008
From: diy-linux-dev@diy-linux.org (George Boudreau)
Date: Fri, 25 Jan 2008 20:52:36 -0500
Subject: 2.6.24 kernel
In-Reply-To: <20080126011316.GA3050@eyo32.local>
References: <20080126011316.GA3050@eyo32.local>
Message-ID: <cacf166b0801251752g15a62933y7c3afb70e3cb762d@mail.gmail.com>

------=_Part_2142_6347459.1201312356853
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Greg,

On Jan 25, 2008 8:13 PM, Greg Schafer <gschafer@zip.com.au> wrote:

> Hi list,
>
> If you've been following kernel development lately you'll know that the
> i386
> and x86_64 arches have been merged into one super arch, "x86". This has
> the
> interesting side-effect for headers_install of creating identical header
> sets for each arch ie: following commands all produce an identical set of
> headers:
>
> make headers_install INSTALL_HDR_PATH=temp
> make headers_install INSTALL_HDR_PATH=temp ARCH=i386
> make headers_install INSTALL_HDR_PATH=temp ARCH=x86_64
> make headers_install INSTALL_HDR_PATH=temp ARCH=x86
>
> This means I could simplify this section of the Temptools headers install
> in
> the Next Gen build:
>
> case $DIY_TARGET in
>  i?86*)        KARCH=i386 ;;
>  powerpc-*)    KARCH=powerpc ;;
>  x86_64*)      KARCH=x86_64 ;;
> esac
>
> And another interesting tidbit I haven't seen publicized, if you configure
> your kernel like this:
>
> make menuconfig ARCH=x86


 This is used when creating .config for cross-compile apps. It is handy when
creating mini-config files. (see Rob Landley's Firmware
Linux)<http://www.landley.net/code/firmware/new_platform.html>


>
> you'll get an additional new menu item to choose a 64-bit kernel. Just try
> it out to see what I mean. Of course, you'll need a 64-bit capable
> toolchain
> to compile such a kernel. BTW, I haven't tested any of this yet..
>
> Regards
> Greg
>
> __________________________
> Unsubscribe information at
> http://www.diy-linux.org/mailman/listinfo/diy-linux-dev
>

------=_Part_2142_6347459.1201312356853
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Greg,<br><br><div class="gmail_quote">On Jan 25, 2008 8:13 PM, Greg Schafer &lt;<a href="mailto:gschafer@zip.com.au">gschafer@zip.com.au</a>&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi list,<br><br>If you&#39;ve been following kernel development lately you&#39;ll know that the i386<br>and x86_64 arches have been merged into one super arch, &quot;x86&quot;. This has the<br>interesting side-effect for headers_install of creating identical header<br>
sets for each arch ie: following commands all produce an identical set of<br>headers:<br><br>make headers_install INSTALL_HDR_PATH=temp<br>make headers_install INSTALL_HDR_PATH=temp ARCH=i386<br>make headers_install INSTALL_HDR_PATH=temp ARCH=x86_64<br>
make headers_install INSTALL_HDR_PATH=temp ARCH=x86<br><br>This means I could simplify this section of the Temptools headers install in<br>the Next Gen build:<br><br>case $DIY_TARGET in<br> &nbsp;i?86*) &nbsp; &nbsp; &nbsp; &nbsp;KARCH=i386 ;;<br>
 &nbsp;powerpc-*) &nbsp; &nbsp;KARCH=powerpc ;;<br> &nbsp;x86_64*) &nbsp; &nbsp; &nbsp;KARCH=x86_64 ;;<br>esac<br><br>And another interesting tidbit I haven&#39;t seen publicized, if you configure<br>your kernel like this:<br><br>make menuconfig ARCH=x86</blockquote>
<div><br>&nbsp;This is used when creating .config for cross-compile apps. It is handy when creating mini-config files. (see Rob Landley&#39;s <a href="http://www.landley.net/code/firmware/new_platform.html">Firmware Linux)</a><br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><br>you&#39;ll get an additional new menu item to choose a 64-bit kernel. Just try<br>
it out to see what I mean. Of course, you&#39;ll need a 64-bit capable toolchain<br>to compile such a kernel. BTW, I haven&#39;t tested any of this yet..<br><br>Regards<br>Greg<br><br>__________________________<br>Unsubscribe information at<br>
<a href="http://www.diy-linux.org/mailman/listinfo/diy-linux-dev" target="_blank">http://www.diy-linux.org/mailman/listinfo/diy-linux-dev</a><br></blockquote></div><br>

------=_Part_2142_6347459.1201312356853--


From diy-linux-dev@diy-linux.org  Sat Jan 26 03:45:17 2008
From: diy-linux-dev@diy-linux.org (Greg Schafer)
Date: Sat, 26 Jan 2008 13:45:17 +1100
Subject: 2.6.24 kernel
In-Reply-To: <cacf166b0801251752g15a62933y7c3afb70e3cb762d@mail.gmail.com>
References: <20080126011316.GA3050@eyo32.local> <cacf166b0801251752g15a62933y7c3afb70e3cb762d@mail.gmail.com>
Message-ID: <20080126024517.GA3299@eyo32.local>

On Fri, Jan 25, 2008 at 08:52:36PM -0500, George Boudreau wrote:
> On Jan 25, 2008 8:13 PM, Greg Schafer <gschafer@zip.com.au> wrote:
> > And another interesting tidbit I haven't seen publicized, if you configure
> > your kernel like this:
> >
> > make menuconfig ARCH=x86
> 
> 
>  This is used when creating .config for cross-compile apps.

Umm, of course. But I think you may have missed my point..

> It is handy when creating mini-config files. (see Rob Landley's Firmware
> Linux)<http://www.landley.net/code/firmware/new_platform.html>

Thanks for the link.

Regards
Greg