From: "Grant Edwards" <grante@visi.com>
To: Andrew Lunn <andrew.lunn@ascom.ch>
Cc: "Trenton D. Adams" <tadams@theone.dnsalias.com>,
eCos Disuss <ecos-discuss@sourceware.cygnus.com>
Subject: [ECOS] Re: Network programming for eCos under linux
Date: Wed, 08 Aug 2001 09:00:00 -0000 [thread overview]
Message-ID: <20010808160045.7F5137A926@visi.com> (raw)
In-Reply-To: <20010808172107.B3798@biferten.ma.tech.ascom.ch>
Andrew Lunn writes:
>> 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.
>
Pedant mode on...
Stricly speaking, it doesn't matter whether you're running Solaris or
Linux. Both are BE on SPARC and LE on IA32. What you want is a mixed
SPARC & IA32 setup. That said, if you pick a Linux machine at random
there's probably a 99+ percent chance it's IA32 -- and if you pick a Solaris
machine at random there's a 99+ percent chance it's SPARC.
--
Grant Edwards
grante@visi.com
prev parent reply other threads:[~2001-08-08 9:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-07 15:41 [ECOS] " Trenton D. Adams
2001-08-08 0:35 ` Andrew Lunn
2001-08-08 6:27 ` Jonathan Larmour
2001-08-08 6:51 ` Andrew Lunn
2001-08-08 7:13 ` Grant Edwards
2001-08-08 7:52 ` Jonathan Larmour
2001-08-08 8:02 ` Andrew Lunn
2001-08-08 8:06 ` Trenton D. Adams
2001-08-08 8:14 ` Jonathan Larmour
2001-08-08 8:47 ` Trenton D. Adams
2001-08-08 8:58 ` Trenton D. Adams
2001-08-08 9:04 ` Mark Salter
2001-08-08 9:06 ` Jonathan Larmour
2001-08-08 9:19 ` [ECOS] " Grant Edwards
2001-08-08 9:07 ` Grant Edwards
2001-08-08 8:32 ` [ECOS] " Grant Edwards
2001-08-08 8:43 ` Trenton D. Adams
2001-08-08 8:57 ` [ECOS] " Grant Edwards
2001-08-08 7:57 ` [ECOS] " Trenton D. Adams
2001-08-08 8:09 ` Grant Edwards
2001-08-08 8:14 ` Trenton D. Adams
2001-08-08 8:42 ` Grant Edwards
2001-08-08 8:21 ` Andrew Lunn
2001-08-08 8:27 ` Trenton D. Adams
2001-08-08 9:00 ` Grant Edwards [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010808160045.7F5137A926@visi.com \
--to=grante@visi.com \
--cc=andrew.lunn@ascom.ch \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=tadams@theone.dnsalias.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).