From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Proposal for new generic device API: dma_get_required_mask()
Date: Fri, 18 Jun 2004 10:21:20 +0100 [thread overview]
Message-ID: <20040618102120.A29213@flint.arm.linux.org.uk> (raw)
In-Reply-To: <m33c4tsnex.fsf@defiant.pm.waw.pl>; from khc@pm.waw.pl on Fri, Jun 18, 2004 at 02:46:46AM +0200
On Fri, Jun 18, 2004 at 02:46:46AM +0200, Krzysztof Halasa wrote:
> If we fix the API we should IMHO also remove set_dma_mask() and add
> the number of address bits to the arguments of actual mapping
> functions.
Good idea, except for the fact that we have drivers merged which have
real masks like 0x0fefffff. It _really is_ a mask and not a number
of bits.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2004-06-18 9:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 14:08 Proposal for new generic device API: dma_get_required_mask() James Bottomley
2004-06-17 14:51 ` Meelis Roos
2004-06-17 15:28 ` Matthew Wilcox
2004-06-17 20:12 ` James Bottomley
2004-06-18 0:46 ` Krzysztof Halasa
2004-06-18 1:45 ` James Bottomley
2004-06-18 23:07 ` Krzysztof Halasa
2004-06-19 15:00 ` James Bottomley
2004-06-19 23:39 ` Krzysztof Halasa
2004-06-20 16:56 ` James Bottomley
2004-06-18 9:21 ` Russell King [this message]
2004-06-18 23:10 ` Krzysztof Halasa
2004-06-19 20:22 ` Russell King
2004-06-20 0:00 ` Krzysztof Halasa
2004-06-20 19:47 ` Russell King
2004-06-23 19:32 ` Krzysztof Halasa
2004-06-18 5:59 ` Jeremy Higdon
2004-06-18 14:19 ` James Bottomley
-- strict thread matches above, loose matches on Subject: below --
2004-06-17 14:52 Salyzyn, Mark
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=20040618102120.A29213@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=James.Bottomley@steeleye.com \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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