Re: 64-bit jiffies, a better solution take 2
Daniel Jacobowitz (dan@debian.org)
Sat, 11 May 2002 12:41:24 -0400
On Sat, May 11, 2002 at 08:01:34AM -0700, george anzinger wrote:
> Russell King wrote:
> > 
> > On Fri, May 10, 2002 at 05:42:46PM -0700, george anzinger wrote:
> > > diff -urP -I \$Id:.*Exp \$ -X /usr/src/patch.exclude linux-2.5.14-org/arch/arm/vmlinux-armo.lds.in linux/arch/arm/vmlinux-armo.lds.in
> > > --- linux-2.5.14-org/arch/arm/vmlinux-armo.lds.in     Tue May  7 15:59:35 2002
> > > +++ linux/arch/arm/vmlinux-armo.lds.in        Fri May 10 17:07:31 2002
> > > @@ -4,6 +4,7 @@
> > >   */
> > >  OUTPUT_ARCH(arm)
> > >  ENTRY(stext)
> > > +jiffies = jiffies_64 + 4;
> > >  SECTIONS
> > >  {
> > >       . = TEXTADDR;
> > > diff -urP -I \$Id:.*Exp \$ -X /usr/src/patch.exclude linux-2.5.14-org/arch/arm/vmlinux-armv.lds.in linux/arch/arm/vmlinux-armv.lds.in
> > > --- linux-2.5.14-org/arch/arm/vmlinux-armv.lds.in     Tue May  7 15:59:35 2002
> > > +++ linux/arch/arm/vmlinux-armv.lds.in        Fri May 10 17:07:34 2002
> > > @@ -4,6 +4,7 @@
> > >   */
> > >  OUTPUT_ARCH(arm)
> > >  ENTRY(stext)
> > > +jiffies = jiffies_64 + 4;
> > >  SECTIONS
> > >  {
> > >       . = TEXTADDR;
> > 
> > Eurgh.  This seems to be a popular misconception.  What makes you think
> > ARM is big endian, or was it just a guess?
> > 
> 
> >From byteorder.h:
> 
> #ifdef __ARMEB__
> #include <linux/byteorder/big_endian.h>
> #else
> #include <linux/byteorder/little_endian.h>
> #endif
> 
> So, yes, given no hints on who or what configures __ARMEB__.  Is it always little endian?
The compiler does; that's true of most __*__ macros used in the kernel. 
If you build a big-endian compiler, you'll get __ARMEB__.
-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/