From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Trenton D. Adams" <tadams@theone.dnsalias.com>
To: "'Andrew Lunn'" <andrew.lunn@ascom.ch>
Cc: "'eCos Disuss'" <ecos-discuss@sourceware.cygnus.com>
Subject: RE: [ECOS] Network programming for eCos under linux
Date: Wed, 08 Aug 2001 08:27:00 -0000
Message-id: <002801c1201e$786e0b30$090110ac@TRENT>
References: <20010808172107.B3798@biferten.ma.tech.ascom.ch>
X-SW-Source: 2001-08/msg00234.html

  > 
  > > This shouldn't pose a problem since I've configured my ARM as
  > > little-endian.  However, htons (), htonl (), etc should solve that
  > > problem anyhow, shouldn't it?  I mean as far networking code goes
that
  > > is.  I would obviously have to be careful about data types between
the
  > > two if they were different.  It's nice to have the ARM with 32-bit
  > > little-endian!  Makes my life a lot easier since I'm sending data
to a
  > > PC.
  > 
  > The problem is, if your machines both use the same endianness, you
  > never know when you have missed out a htons(). If they are different
  > endianness, it breaks. That why i like to write network code on a
  > mixed Solaris & linux network, just to make sure.
  > 
If you miss an htons () though, your program won't work anyhow if you're
on a little-endian architecture.  Take for instance watching on port 10.
If you don't do an htons () to convert to network byte order (BIG
ENDIAN), then your program would watch on port 2560 instead of 10.