From: Adrian Cox <adrian@humboldt.co.uk>
To: LinuxPPC-Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: ISA DMA take 2
Date: Wed, 09 Jan 2002 18:27:10 +0000 [thread overview]
Message-ID: <3C3C8B7E.4020406@humboldt.co.uk> (raw)
In-Reply-To: 0201091753.AA22414@ivan.Harhan.ORG
Michael Sokolov wrote:
> As I understand it, you also have to have no I/O hole in the mapping of the
> bottom 16 MB of memory onto PCI, right? As I understand it, Linux/PPC is a sane
> PPC OS and treats all PPC memory as normal, without any special treatment for
> 0xA0000-0xFFFFF, so your DMA buffer could legitimately end up in that region
> and if your memory map has an I/O hole you would be screwed, right? And of
> course main memory on PCI at 0 with no I/O hole means you can't have video on
> the same PCI bus... !@#$ing pee sea legacy :(
I have two CT69030 VGA chips on the same PCI bus, but I only enable
their PCI memory mapped regions, and never use the legacy VGA addresses.
Linux on this board doesn't hand out memory in the 0xa0000 to 0xfffff
region as DMA buffers, because that range is part of the kernel text
segment. Linux on i386 explicity removes that range from the memory
map, and for completeness I should probably ensure that those pages are
marked reserved in case a minimal kernel comes below the 1MB barrier.
--
Adrian Cox http://www.humboldt.co.uk/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-01-09 18:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 17:53 ISA DMA take 2 Michael Sokolov
2002-01-09 18:27 ` Adrian Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-09 20:18 Michael Sokolov
2002-01-09 20:43 ` Adrian Cox
2002-01-09 17:21 Michael Sokolov
2002-01-09 17:40 ` Adrian Cox
2002-01-08 15:33 Adrian Cox
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=3C3C8B7E.4020406@humboldt.co.uk \
--to=adrian@humboldt.co.uk \
--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).