public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Doug Beattie <dbb@caldera.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Driver development document
Date: Fri, 19 Oct 2001 18:12:21 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805374@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805372@msgid-missing>

FWIW - It may be good, for someone in the real know, to document how
to modify or write a driver source so it would detect whether it was
running on ia32 or ia64 or even other type system and thereby be able
to take advantage of larger memory models.

From what I understand, many of the current drivers go through
copydown when used in the ia64 architecture and could be improved
upon.

My $0.02 worth of thoughts on this discussion.

n0ano@indstorage.com wrote:
> 
> Gururaj-
> 
> The same document that explains how to write IA32 drivers :-)
> 
> Seriously, all of the kernel interfaces you should need should
> be the same between IA32 and IA64.  It's amazing how many IA64
> drivers were created by just re-compiling the IA32 versiion with
> no source code changes.
> 
> I would recommend starting with the book `Linux Device Drivers'
> by Rubini.  It's kind of out of date (written for the 2.0 kernel)
> but it gives you a good idea about the basics.
> 
> On Fri, Oct 19, 2001 at 10:00:13AM -0700, Gururaj Ananthateerta wrote:
> > I am newbie to Linux.
> > Is there any document which explains howto write linux network drivers for
> > ia-64.?
> >
> > Thanks
> >
> >
> >
> >
> >
> > _______________________________________________
> > Linux-IA64 mailing list
> > Linux-IA64@linuxia64.org
> > http://lists.linuxia64.org/lists/listinfo/linux-ia64
> 
> --
> Don Dugger
> "Censeo Toto nos in Kansa esse decisse." - D. Gale
> n0ano@indstorage.com
> Ph: 303/652-0870x117
> 
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64

-- 
Douglas B. Beattie
------------------
Linux Test Architect - Caldera, Inc.
dbb@caldera.com


  parent reply	other threads:[~2001-10-19 18:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-19 17:00 [Linux-ia64] Driver development document Gururaj Ananthateerta
2001-10-19 17:46 ` n0ano
2001-10-19 18:12 ` Doug Beattie [this message]
2001-10-19 18:39 ` KOCHI, Takayoshi
2001-10-31 23:10 ` Jes Sorensen

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-105590698805374@msgid-missing \
    --to=dbb@caldera.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