All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>,
	Jeff Garzik <jgarzik@pobox.com>,
	mike.miller@hp.com, akpm@osdl.org, axboe@suse.de,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: DMA mapping (was Re: [PATCH] cciss 2.6; replaces DMA masks with kernel defines)
Date: Fri, 10 Jun 2005 16:59:55 -0400	[thread overview]
Message-ID: <1118437196.6423.60.camel@mindpipe> (raw)
In-Reply-To: <1118436306.5272.37.camel@laptopd505.fenrus.org>

On Fri, 2005-06-10 at 22:45 +0200, Arjan van de Ven wrote:
> On Fri, 2005-06-10 at 16:39 -0400, Lee Revell wrote:
> > On Fri, 2005-06-10 at 12:55 -0400, Jeff Garzik wrote:
> > > mike.miller@hp.com wrote:
> > > > This patch removes our homegrown DMA masks and uses the ones defined in
> > > > the kernel instead.
> > > > Thanks to Jens Axboe for the code. Please consider this for inclusion.
> > > > 
> > > > Signed-off-by: Mike Miller <mike.miller@hp.com>
> > > 
> > > You need to add '#include <linux/dma-mapping.h>'
> > > 
> > 
> > Why doesn't this file define 29, 30, 31 bit DMA masks, required by many
> > devices?  I know of at least 2 soundcards that need a 29 bit DMA mask.
> 
> your mail unfortunately was not in diff -u form ;)
> I'm pretty sure that such constants are welcome

Which reminds me, the SBLive has a 29 bit mask in the OSS driver but 31
in the ALSA driver.  I'm going to preserve the discrepancy, it seems
pointless to change the behavior of a deprecated driver.

Lee


  parent reply	other threads:[~2005-06-10 20:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-10 14:34 [PATCH] cciss 2.6; replaces DMA masks with kernel defines mike.miller
2005-06-10 16:55 ` Jeff Garzik
2005-06-10 20:39   ` DMA mapping (was Re: [PATCH] cciss 2.6; replaces DMA masks with kernel defines) Lee Revell
2005-06-10 20:45     ` Arjan van de Ven
2005-06-10 20:49       ` Lee Revell
2005-06-11 18:32         ` jgarzik
2005-06-13  2:58           ` Jeff Garzik
2005-06-10 20:59       ` Lee Revell [this message]
2005-06-10 21:17       ` Lee Revell
2005-06-10 21:30         ` Matthew Wilcox
2005-06-10 23:08           ` Lee Revell
2005-06-11 13:54             ` Matthew Wilcox
2005-06-15 18:19               ` Lee Revell
2005-06-10 23:17           ` Lee Revell
2005-06-11 15:39             ` Pavel Machek

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=1118437196.6423.60.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=akpm@osdl.org \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=arjan@infradead.org \
    --cc=axboe@suse.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mike.miller@hp.com \
    /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.