All of lore.kernel.org
 help / color / mirror / Atom feed
From: "White, Charles" <Charles.White@COMPAQ.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] RE: DMA memory limitation?
Date: Mon, 09 Jul 2001 13:54:51 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005825@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005820@msgid-missing>

Is there a patch that fixes the pci_alloc_consistent for older versions of
the IA-64 kernels?  To do 64bit DMA in my driver I need to pass
pci_alloc_consistent pci_dev pointer of NULL.  

I'm interested in getting this to work on the older IA64 kernels that are
currently on distribution CDs. 
		

		From: Matt_Domsch@Dell.com
		To: jgarzik@mandrakesoft.com, sp@scali.no
		Cc: alan@lxorguk.ukuu.org.uk, helgehaf@idb.hist.no, 
			pvvvarma@techmas.hcltech.com,
linux-kernel@vger.kernel.org, 
			davem@redhat.com, linux-ia64@linuxia64.org
		Date: Fri, 6 Jul 2001 10:56:47 -0500 
		Subject: [Linux-ia64] RE: DMA memory limitation?

		> The important thing is that pci_alloc_consistent and the
other PCI DMA
		> functions work as advertised on IA64.  If you pass NULL to
		> pci_alloc_consistent, IA64 should give you an ISA DMA-able

		> address.  If
		> you don't, you get a 32-bit PCI DMA address.  Use of
GFP_DMA is a
		> arch-specific detail, so don't let me confuse you there.

		Until recently, on IA-64, pci_alloc_consistent() given a
NULL pci_dev would
		fault.  It's been fixed in at least the most recent IA-64
patch.
		pci_map_single() and pci_map_sg() still have the same
problem, as they
		dereference pci_dev w/o checking for NULL first.


		-- 
		Matt Domsch
		Sr. Software Engineer
		Dell Linux Solutions
		www.dell.com/linux
		#2 Linux Server provider with 17% in the US and 14%
Worldwide (IDC)!
		#3 Unix provider with 18% in the US (Dataquest)!

		


  reply	other threads:[~2001-07-09 13:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-06 15:56 [Linux-ia64] RE: DMA memory limitation? Matt_Domsch
2001-07-09 13:54 ` White, Charles [this message]
2001-07-09 14:46 ` Matt_Domsch
2001-07-09 15:02 ` White, Charles
2001-07-09 15:20 ` Matt_Domsch
2001-07-09 15:33 ` White, Charles
2001-07-10 15:42 ` 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-105590693005825@msgid-missing \
    --to=charles.white@compaq.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.