From: michi1@michaelblizek.twilightparadox.com (Michael Blizek)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Requirement of Linux port
Date: Fri, 1 Apr 2011 07:14:24 +0200 [thread overview]
Message-ID: <20110401051423.GA2041@michaelblizek.twilightparadox.com> (raw)
In-Reply-To: <4D9546C6.4000004@gmail.com>
Hi!
On 11:30 Fri 01 Apr , Jacky Lam wrote:
> Hi All,
>
> Is there any document on web summarized the hardware (especially,
> CPU) that a Linux depends on. For example, if a CPU doesn't support
> misaligned access (no exception will be generated when misalignment
> access), can Linux run on that?
I do not know of such a document, but I have not looked for one so far. But
basically:
- CPUs which do not support misaligned access are supported.
- CPUs less than 32 bit are not supported. When compiling with gcc, int is
always 32 bit, long is 32/64 bit (depending on 32/64 bit CPU) and long long
is always 64 bit. You can also use __u8 __u16 __u32 __u64 __s8 __s16 __s32
and __s64, if you want to.
- Both big endian and little endian is supported.
The interesting stuff starts if you want to port a program to/from other OSes.
Then you have to take care of missing libs/syscalls (like I/O multiplexer and
a lot of GUIs stuff) or syscalls which behave differently (like fsync())...
-Michi
--
programing a layer 3+4 network protocol for mesh networks
see http://michaelblizek.twilightparadox.com
prev parent reply other threads:[~2011-04-01 5:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 3:30 Requirement of Linux port Jacky Lam
2011-04-01 5:14 ` Michael Blizek [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=20110401051423.GA2041@michaelblizek.twilightparadox.com \
--to=michi1@michaelblizek.twilightparadox.com \
--cc=kernelnewbies@lists.kernelnewbies.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).