All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt_Domsch@Dell.com
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] Simple Question Simple Answer
Date: Tue, 14 Nov 2000 04:39:16 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205719@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205701@msgid-missing>

Allow me to pass on some words of wisdom I received from Alan Cox a while
back.  Particularly for IA-64, the comment to use the new PCI DMA
architecture (linux/Documentatation/DMA-mapping.txt) has become especially
important, as >4GB systems will be fairly common, and many drivers I've seen
(as of September) were limiting system memory to 4GB because they hadn't
migrated to this yet.

Thanks,
Matt



   Alan Cox porting notes   6/12/2000 
The 2.2 to 2.4 porting should be easy. The big points are:

Remember to use pci_enable_device

dev->base_address[foo]. is now dev->resource[foo].start
and does not need masking for the flag bits

cli()/sti() type locking is now right out. In 2.2 its bad in 2.4 its
very very bad 8)

Use the new scsi error handling  - it really is a big win handling
degrading setups.

The scsi proc has changed

If its a PCI irq allocate using SA_SHIRQ but you must now pass
something other than NULL for the dev_id


If you want it to work on stuff like ia64 it needs to be both 64bit clean
and touch mmio space only using readb/readw/readl etc not by direct pointer
references.

If you want it to work with >4Gb of RAM you really want to use the new
pci_alloc_consistent API - but I would worry about that once it works
not before.

Alan
 


      parent reply	other threads:[~2000-11-14  4:39 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
2000-11-14  4:39 ` Matt_Domsch [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=marc-linux-ia64-105590678205719@msgid-missing \
    --to=matt_domsch@dell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.