From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: Jurriaan on Alpha <thunder7@xs4all.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: compiling cmipci in 2.5.10 on Alpha doesn't work
Date: Fri, 26 Apr 2002 13:05:14 +0400 [thread overview]
Message-ID: <20020426130514.A20345@jurassic.park.msu.ru> (raw)
In-Reply-To: <20020426073130.GB28217@alpha.of.nowhere> <20020426074416.GA8415@alpha.of.nowhere>
On Fri, Apr 26, 2002 at 09:44:16AM +0200, Jurriaan on Alpha wrote:
> -#if defined(__i386__) || defined(__ppc__)
> +#if defined(__i386__) || defined(__ppc__) || defined(__alpha__)
> /*
> * Here a dirty hack for 2.4 kernels.. See kernel/memory.c.
> */
No, alpha doesn't need any kind of "dirty hacks". :-)
We only need to get <linux/pci.h> included properly.
Ivan.
--- 2.5.10/include/sound/driver.h Mon Mar 18 23:37:12 2002
+++ linux/include/sound/driver.h Tue Mar 26 23:47:32 2002
@@ -50,12 +50,12 @@
*/
#if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 4, 0)
+#include <linux/pci.h>
#if defined(__i386__) || defined(__ppc__)
/*
* Here a dirty hack for 2.4 kernels.. See kernel/memory.c.
*/
#define HACK_PCI_ALLOC_CONSISTENT
-#include <linux/pci.h>
void *snd_pci_hack_alloc_consistent(struct pci_dev *hwdev, size_t size,
dma_addr_t *dma_handle);
#undef pci_alloc_consistent
next prev parent reply other threads:[~2002-04-26 9:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-26 7:31 Jurriaan on Alpha
2002-04-26 7:44 ` Jurriaan on Alpha
2002-04-26 9:05 ` Ivan Kokshaysky [this message]
2002-04-26 9:17 ` Jaroslav Kysela
2002-04-26 9:40 ` Russell King
2002-04-26 9:56 ` Takashi Iwai
2002-04-26 10:18 ` Ivan Kokshaysky
2002-04-26 10:26 ` Jaroslav Kysela
2002-04-26 10:49 ` Ivan Kokshaysky
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=20020426130514.A20345@jurassic.park.msu.ru \
--to=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=thunder7@xs4all.nl \
/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
all inboxes | Powered by JetHome®