From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Trenton D. Adams" To: "'Grant Edwards'" Cc: "'Andrew Lunn'" , "'eCos Discussion'" Subject: RE: [ECOS] Network programming for eCos under linux Date: Wed, 08 Aug 2001 08:14:00 -0000 Message-id: <002001c1201c$a87186b0$090110ac@TRENT> References: <20010808101113.A13989@visi.com> X-SW-Source: 2001-08/msg00231.html > > > > > Watch out for endianness issues. i386 linux is little endian. > > > Whats the endianness of your target? Things like this affects > > > network code. > > > > 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. > > You're headed for trouble. I work on software where the author > "knew" data was being sent from one little endian machine to > another over the network. Unfortunately one of the ends is now > big-endian, and it's now a royal PITA to maintain this stuff. > Unfortunalyte there aren't standard host-to-little-endian and > little-endian-to-host macros. > How so? Are you referring to the networking code, or the data types? We're not going to be sending to anything other than a PC so either way it shouldn't be a problem should it?