public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@linuxcare.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Simple Question Simple Answer
Date: Mon, 13 Nov 2000 23:20:43 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205714@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205701@msgid-missing>

>>>>> "Brian" = Brian Boerner <brian_boerner@ntc.adaptec.com> writes:

Brian> Let me begin by saying that I'm not really new to Linux but
Brian> have only been doing Linux development for about a year
Brian> now. I'm looking for a list of differences one must consider
Brian> when trying to write drivers that are portable.

Brian> Correct me if I'm wrong, but the 2.2 code stream for Linux is
Brian> ia32 while the 2.4 code stream is going to support ia64. Is
Brian> there a list of gottchas somewhere that ISVs should watch out
Brian> for? Please forgive me if this is something that has been asked
Brian> a 1000 times, but hey.. I'm new.

That kinda depends on what you are trying to achieve. Are you trying
to write drivers that run under both 2.2 and 2.4 (covering all
applicaple architectures of course: little endian/big endian - 32 vs
64 bit) or just code that will run in 2.4?

There are some API changes which you have to deal with, but a lot of
that can be handled by putting in backwards compatibility macros for
2.2 in your code. I use that trick in the AceNIC Gigabit Ethernet
driver for instance (drivers/net/acenic.[ch]).

Jes


  parent reply	other threads:[~2000-11-13 23:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-13 21:46 [Linux-ia64] Simple Question Simple Answer Brian Boerner
2000-11-13 22:54 ` David Mosberger
2000-11-13 23:20 ` Jes Sorensen [this message]
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-105590678205714@msgid-missing \
    --to=jes@linuxcare.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