From: Thiemo Seufer <ths@networkno.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] mips-user socket-related syscall support
Date: Tue, 20 Jun 2006 09:28:03 +0100 [thread overview]
Message-ID: <20060620082802.GH24070@networkno.de> (raw)
In-Reply-To: <44979BB4.5060703@twilight-hall.net>
Raphaël Rigo wrote:
> Fabrice Bellard wrote:
> > Hi,
> >
> > Is it really needed to duplicate socket.h ? What are the differences for
> > mips ?
> >
> > Regards,
> >
> > Fabrice.
> >
> Hi,
> almost all socket related constants are different on MIPS. I thought it would be
> cleaner to define all constants for each target, so that if we add support for
> another platform with different constants, it will be easy.
Historically Linux/MIPS followed MIPS Inc.'s RiscOS numbering scheme,
this explains most of the seemingly deliberate deviations from i386.
Thiemo
next prev parent reply other threads:[~2006-06-20 8:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 9:00 [Qemu-devel] [PATCH] mips-user socket-related syscall support Raphaël Rigo
2006-06-19 22:03 ` Fabrice Bellard
2006-06-20 6:54 ` Raphaël Rigo
2006-06-20 8:28 ` Thiemo Seufer [this message]
2006-06-19 22:52 ` Fabrice Bellard
2006-06-20 8:47 ` Raphaël Rigo
2006-06-22 17:14 ` Raphaël Rigo
2006-06-24 15:08 ` Fabrice Bellard
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=20060620082802.GH24070@networkno.de \
--to=ths@networkno.de \
--cc=qemu-devel@nongnu.org \
/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 NNTP newsgroup(s).