From: Hollis Blanchard <hollis@austin.ibm.com>
To: Sven Dickert <Sven.Dickert@planb.de>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 601 BAT's
Date: Wed, 25 Jul 2001 14:42:39 -0500 [thread overview]
Message-ID: <20010725144239.A11885@austin.ibm.com> (raw)
In-Reply-To: <20010724105114.A17706@remote.org>; from Sven.Dickert@planb.de on Tue, Jul 24, 2001 at 10:51:14AM +0200
On Tue, Jul 24, 2001 at 10:51:14AM +0200, Sven Dickert wrote:
>
> At the moment I'm working on sound support. I changed
> -#define CAROLINA_IRQ_EDGE_MASK_HI 0xA4 /* IRQ's 8-15 [10,13,15] */
> +#define CAROLINA_IRQ_EDGE_MASK_HI 0xA0 /* IRQ's 8-15 [10,13,15] */
> in arch/ppc/kernel/prep_pci.c
> I found this 'patch' at http://penguinppc.org/dev/prep/tp850.diff
Neither the 40P nor the Thinkpad 850 are Carolina systems, so those constants
should remain how they are and new ones for other systems introduced. That
will mean slight changes to the IBM section of prep_route_pci_interrupts(),
but nothing major.
In your patch you're using a segment register because 601 BAT's are only 8MB
(and we need more for IO space). Someone suggested using ioremap in the driver
(the one causing the page fault), but I suspect the whole reason those BAT
regions are there is to support legacy IO and not have to get everything to
ioremap? Is there an equivalent to ioremap that allows the virtual address to
be specified (want to map 0x80000000 physical to 0x80000000 virtual [NOT
n+io_base] for IO ports)?
-Hollis
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-07-25 19:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-24 8:51 sound runs double speed on rs6k Sven Dickert
2001-07-25 19:42 ` Hollis Blanchard [this message]
2001-07-26 8:18 ` CAROLINA_IRQ_EDGE_MASK_HI, Segment Register 8 instead of BATs on 601 Sven Dickert
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=20010725144239.A11885@austin.ibm.com \
--to=hollis@austin.ibm.com \
--cc=Sven.Dickert@planb.de \
--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).