From: msokolov@ivan.Harhan.ORG (Michael Sokolov)
To: adrian@humboldt.co.uk, d.mueller@elsoft.ch
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: ISA DMA
Date: Thu, 20 Dec 01 08:42:49 PST [thread overview]
Message-ID: <0112201642.AA25515@ivan.Harhan.ORG> (raw)
Adrian Cox <adrian@humboldt.co.uk> wrote:
> Via686a. As I understand it, 32-bit DMA uses the DMA_HI_PAGE_x registers
> from 0x487 to 0x48a, and the Via manual doesn't claim to have any
> registers in that range.
It is also my understanding that VT82C686/A/B offers 24-bit DMA addressing
only.
On the Adirondack I plan to use the floppy disk controller (the only ISA DMA
user) in non-DMA mode only. I hope Linux can do that. The memory map we've
adopted does not have memory at PCI address 0 at all, so 24-bit DMA means no
DMA at all rather than bottom 16 MB only. It is really too late to change the
memory map now, it would be so much pain that I would much rather settle for
using non-DMA mode only for floppies.
> The only 32-bit DMA southbridge I've
> encountered is the Winbond chip on the Sandpoint, and that chip doesn't
> have UDMA66, USB, and audio.
Acer Labs 1543 has it according to its manual (see the latter for where the
registers are, I don't remember).
We have that bridge on the K2. Ironically, there we don't have a floppy disk
port, so we have good ISA DMA on the board where we don't need it but don't
have it on a board where we do...
MS
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-12-20 16:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-20 16:42 Michael Sokolov [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-19 10:21 ISA DMA Adrian Cox
2001-12-20 8:36 ` David Müller (ELSOFT AG)
2001-12-20 9:50 ` Adrian Cox
2001-12-20 10:09 ` Geert Uytterhoeven
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=0112201642.AA25515@ivan.Harhan.ORG \
--to=msokolov@ivan.harhan.org \
--cc=adrian@humboldt.co.uk \
--cc=d.mueller@elsoft.ch \
--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).