From: Brian Boerner <brian_boerner@ntc.adaptec.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Simple Question Simple Answer
Date: Mon, 13 Nov 2000 21:46:54 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205701@msgid-missing> (raw)
Let me begin by saying that I'm not really new to Linux but have only
been doing Linux development for about a year now. I'm looking for a
list of differences one must consider when trying to write drivers that
are portable.
Correct me if I'm wrong, but the 2.2 code stream for Linux is ia32 while
the 2.4 code stream is going to support ia64. Is there a list of
gottchas somewhere that ISVs should watch out for? Please forgive me if
this is something that has been asked a 1000 times, but hey.. I'm new.
-bmb-
next reply other threads:[~2000-11-13 21:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-13 21:46 Brian Boerner [this message]
2000-11-13 22:54 ` [Linux-ia64] Simple Question Simple Answer David Mosberger
2000-11-13 23:20 ` Jes Sorensen
2000-11-14 4:39 ` Matt_Domsch
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=marc-linux-ia64-105590678205701@msgid-missing \
--to=brian_boerner@ntc.adaptec.com \
--cc=linux-ia64@vger.kernel.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