From: "BALBIR SINGH" <balbir.singh@wipro.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [QUESTION] ISA overhead
Date: Wed, 03 Oct 2001 12:50:33 +0530 [thread overview]
Message-ID: <3BBABC41.50203@wipro.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]
With 2.5 coming soon, something about ISA has been bothering me.
All DMA has been limited to 16MB, this is ofcourse going to go
away with the PCI DMA patch which allows PCI-DMA to use all the
memory (4GB for 32 bit cards). All the setup of page-frames, etc
is done with the knowledge of ISA.
I was wondering if ISA should be treated as a special case in 2.5
and only if the ISA bus and/or ISA device is present should we do
the 16MB setup. Are there other devices (like MCA) limited to doing
16 MB or so of DMA?, if so they too should be handled as a special case.
I think this is the correct approach, now that all available devices
are almost PCI. The default DMA space should be 32 bit, with special
devices or buses like ISA being handled differently. The current code
should be hidden under a #ifdef and be enabled only if CONFIG_
ISA_DMA or something similar is set.
Comments, suggestions
Balbir
PS: Please do not worry about the attachment, I have no control over it.
"Accepting criticism is the fastest way to learn the right things"
- Just made it up (I am no longer scared of being flamed)
[-- Attachment #2: Wipro_Disclaimer.txt --]
[-- Type: text/plain, Size: 853 bytes --]
----------------------------------------------------------------------------------------------------------------------
Information transmitted by this E-MAIL is proprietary to Wipro and/or its Customers and
is intended for use only by the individual or entity to which it is
addressed, and may contain information that is privileged, confidential or
exempt from disclosure under applicable law. If you are not the intended
recipient or it appears that this mail has been forwarded to you without
proper authority, you are notified that any use or dissemination of this
information in any manner is strictly prohibited. In such cases, please
notify us immediately at mailto:mailadmin@wipro.com and delete this mail
from your records.
----------------------------------------------------------------------------------------------------------------------
next reply other threads:[~2001-10-03 7:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-03 7:20 BALBIR SINGH [this message]
2001-10-03 8:52 ` [QUESTION] ISA overhead Alan 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=3BBABC41.50203@wipro.com \
--to=balbir.singh@wipro.com \
--cc=linux-kernel@vger.kernel.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