From: Christoph Hellwig <hch@caldera.de>
To: David Mosberger <davidm@hpl.hp.com>
Cc: Michael Madore <mmadore@turbolinux.com>,
linux-ia64@linuxia64.org, linux-kernel@vger.kernel.org,
torvalds@transmeta.com
Subject: Re: [Linux-ia64] Proper fix for sym53c8xx_2 driver and dma64_addr_t
Date: Wed, 6 Feb 2002 09:21:29 +0100 [thread overview]
Message-ID: <20020206092129.A8739@caldera.de> (raw)
In-Reply-To: <3C6043E5.D1F40E5D@turbolinux.com> <20020205223804.A22012@caldera.de> <15456.21030.840746.209377@napali.hpl.hp.com>
In-Reply-To: <15456.21030.840746.209377@napali.hpl.hp.com>; from davidm@hpl.hp.com on Tue, Feb 05, 2002 at 01:44:06PM -0800
On Tue, Feb 05, 2002 at 01:44:06PM -0800, David Mosberger wrote:
> Christoph> IA64 needs to define dma64_addr_t.
>
> Not before the driver writers understand when to use it.
Architecture maintainers are not supposed to decide whether driver
writers understand APIs. The dma64_addr_t type is part of the PCI
DMA interface and IA64 needs to defines it.
Linus, could you please accept the below patch to define dma64_addr_t
on IA64?
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
Index: include/asm-ia64/types.h
===================================================================
RCS file: /vger/linux/include/asm-ia64/types.h,v
retrieving revision 1.3
diff -u -u -r1.3 types.h
--- include/asm-ia64/types.h 22 Apr 2000 00:45:18 -0000 1.3
+++ include/asm-ia64/types.h 6 Feb 2002 08:24:24 -0000
@@ -63,6 +63,7 @@
/* DMA addresses are 64-bits wide, in general. */
typedef u64 dma_addr_t;
+typedef u64 dma64_addr_t;
# endif /* __KERNEL__ */
#endif /* !__ASSEMBLY__ */
next parent reply other threads:[~2002-02-06 8:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C6043E5.D1F40E5D@turbolinux.com>
[not found] ` <20020205223804.A22012@caldera.de>
[not found] ` <15456.21030.840746.209377@napali.hpl.hp.com>
2002-02-06 8:21 ` Christoph Hellwig [this message]
2002-02-06 8:29 ` [Linux-ia64] Proper fix for sym53c8xx_2 driver and dma64_addr_t David S. Miller
2002-02-06 8:35 ` Christoph Hellwig
2002-02-06 8:45 ` David S. Miller
2002-02-05 21:23 ` Gérard Roudier
2002-02-06 17:10 ` Christoph Hellwig
2002-02-06 17:15 ` Christoph Hellwig
2002-02-06 17:15 ` David Mosberger
2002-02-05 21:34 ` Gérard Roudier
2002-02-07 2:09 ` David S. Miller
2002-02-06 21:38 ` Gérard Roudier
2002-02-06 16:54 ` David Mosberger
2002-02-05 20:43 Michael Madore
2002-02-05 21:23 ` Gérard Roudier
2002-02-05 21:26 ` David Mosberger
2002-02-05 21:34 ` Gérard Roudier
2002-02-05 21:38 ` Christoph Hellwig
2002-02-05 21:44 ` David Mosberger
2002-02-06 8:21 ` Christoph Hellwig
2002-02-06 8:29 ` David S. Miller
2002-02-06 8:35 ` Christoph Hellwig
2002-02-06 8:45 ` David S. Miller
2002-02-06 16:54 ` David Mosberger
2002-02-06 17:10 ` Christoph Hellwig
2002-02-06 17:15 ` Christoph Hellwig
2002-02-06 17:15 ` David Mosberger
2002-02-06 21:38 ` Gérard Roudier
2002-02-07 2:09 ` David S. Miller
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=20020206092129.A8739@caldera.de \
--to=hch@caldera.de \
--cc=davidm@hpl.hp.com \
--cc=linux-ia64@linuxia64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmadore@turbolinux.com \
--cc=torvalds@transmeta.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.