From: Martin Costabel <costabel@wanadoo.fr>
To: "Kevin M. Myer" <kevin_myer@elanco.k12.pa.us>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: devel kernels 2.3.41
Date: Mon, 31 Jan 2000 23:22:28 +0100 [thread overview]
Message-ID: <38960B24.39C5A8F3@wanadoo.fr> (raw)
In-Reply-To: Pine.LNX.4.20.0001311609090.2282-100000@marble.elanco.k12.pa.us
"Kevin M. Myer" wrote:
[]
> --- linux/include/asm-ppc/types.h.old Mon Jan 31 16:07:01 2000
> +++ linux/include/asm-ppc/types.h Mon Jan 31 16:03:28 2000
> @@ -41,6 +41,10 @@
>
> #define BITS_PER_LONG 32
>
> +/* Dma addresses are 32-bits wide for now. */
> +
> +typedef u32 dma_addr_t;
> +
> #endif /* __KERNEL__ */
>
> #endif
>
> In init/main.c, it included linux/pci.h, in which the struct pci_dev has a
> new member "dma_mask". This is of type dma_addr_t, which is defined for
> i386 and sparc64 but no other architectures that I can tell.
Yes, this one is obvious. But if you have IDE enabled, there are later
on a whole bunch of new functions that are undefined, and I think it
must be pretty hard to write them. In drivers/block/ide-dma.c, you get
pci_map_sg, sg_dma_len, sg_dma_address, pci_unmap_sg,
pci_free_consistent, pci_alloc_consistent all undefined.
> That at least got me around the initial compile problem. I'm working on
> an Apple Network Server with a somewhat less than vanilla 2.3.41 so I'm
> not sure if it compiles and boots fully (seeing as I've goofed up some
> code for the secondary PCI bus on the ANS and it won't compile fully).
--
Martin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-01-31 22:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <B4B7C54D.602%pajama1@mindspring.com>
2000-01-30 3:56 ` HFS+ format Brad Boyer
2000-01-30 13:58 ` Olaf Hering
2000-01-31 4:04 ` devel kernels 2.3.41 ramp
2000-01-31 7:20 ` Martin Costabel
2000-01-31 21:23 ` Kevin M. Myer
2000-01-31 22:22 ` Martin Costabel [this message]
2000-02-01 17:18 ` Ani Joshi
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=38960B24.39C5A8F3@wanadoo.fr \
--to=costabel@wanadoo.fr \
--cc=kevin_myer@elanco.k12.pa.us \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).