From: "Paul Fulghum" <paulkf@microgate.com>
To: <reddog83@chartermi.net>, <davej@suse.de>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.5.3-dj5 synclink.c fix so that it compiles
Date: Mon, 11 Feb 2002 09:38:23 -0600 [thread overview]
Message-ID: <001701c1b312$24448ca0$0c00a8c0@diemos> (raw)
In-Reply-To: <auto-000058815980@front2.chartermi.net>
> This is a temp fix for thje synclink.c file in drivers/char it work's for
me
> so DJ will you please apply this patch.
> Thank you Victor Torres.
> All it does it removes the #error please convert me to
> Documentation/DMA-mapping.txt
> it compiles and work's great for me.
> Please apply
There is nothing in the DMA-mapping.txt that
applies to the PCI version of the synclink adapter
(which does not do DMA to/from system memory).
The ISA version of the synclink adapter does do
ISA DMA bus master transfers. After reading
DMA-mapping.txt twice it is unclear what changes
need to be applied. The documentation seems to imply
that ISA devices need to make some pci_xxx calls.
I'm not sure how this works when there is no PCI bus.
For now, removing the #error line should work fine
for the PCI adapter and probably for the ISA as well.
I will look at this again as time allows.
I usually wait 6-12 months after the new development
kernel opens before attempting to sync my drivers
to the latest changes. This avoids most of the eat-your-file-system
phase, prevents wasting time chasing after a rapidly changing API,
and still leaves another 12 months for tweaking.
Paul Fulghum, paulkf@microgate.com
Microgate Corporation, www.microgate.com
next prev parent reply other threads:[~2002-02-11 15:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-11 5:12 [PATCH] 2.5.3-dj5 synclink.c fix so that it compiles reddog83
2002-02-11 9:49 ` Jens Axboe
2002-02-11 15:38 ` Paul Fulghum [this message]
2002-02-11 20:48 ` reddog83
2002-02-12 6:56 ` Jens Axboe
2002-02-12 7:03 ` Jens Axboe
2002-02-12 7:07 ` Jens Axboe
2002-02-12 7:11 ` David S. Miller
2002-02-12 7:14 ` Jens Axboe
2002-02-12 14:24 ` Paul Fulghum
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='001701c1b312$24448ca0$0c00a8c0@diemos' \
--to=paulkf@microgate.com \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=reddog83@chartermi.net \
/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