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

Yes, I thought about doing it that way, and it COULD be done, but right now
the driver allocates command buffer for IOCTLs as needed.  

So the pci_dev set to NULL allows to continue to do that... 

		-----Original Message-----
		From:	Matt_Domsch@Dell.com [mailto:Matt_Domsch@Dell.com]
		Sent:	Monday, July 09, 2001 10:20 AM
		To:	White, Charles
		Cc:	linux-ia64@linuxia64.org
		Subject:	RE: [Linux-ia64] RE: DMA memory limitation?

		> My device has the limitation that the command buffers I
send 
		> must be in 32
		> bit space, but the IO can be in 64 bit.  But there is only

		> ONE dma_mask for the device.

		Ahh, yes.  The AMI MegaRAID driver/controllers have the same
requirements.
		megaraid solved it as:

		pci_find_device() finds their device, they get a pci_dev
back which has a
		32-bit dma_mask.
		pci_alloc_consistent() the mailbox (this must be in 32-bit
space).
		if it's a 64-bit-capable controller, set pci_dev->dma_mask ~0L.
		pci_alloc_consistent() the command buffers and
scatter-gather lists (these
		can be in 64-bit space).

		Could something similar work for you?

		Thanks,
		Matt

		--
		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)!
		


  parent reply	other threads:[~2001-07-09 15:33 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
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 [this message]
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-105590693005829@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.