LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jacob Luna Lundberg <kernel@gnifty.net>
To: Dan Hollis <goemon@anime.net>
Cc: Vojtech Pavlik <vojtech@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: AMD viper chipset and UDMA100
Date: Thu, 27 Sep 2001 19:21:46 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0109271904170.28015-100000@inbetween.blorf.net> (raw)
In-Reply-To: <Pine.LNX.4.30.0109271551400.20621-100000@anime.net>
On Thu, 27 Sep 2001, Dan Hollis wrote:
> And Andre's didnt make it into the kernel either it seems :-)
He hasn't even been updating his patch with taskfile and destroke support
in it for recent kernels, sadly (sadly because I need destroke). However,
I've been trying to bring it forward myself; you can find it at:
http://chaos2.org/~jacob/code/linux/
I don't know if it's got anything useful to you in it, particularly given
that there are items like the two below which seem to be help chunks for
things that have recently made it into the kernel (without help, heh):
-AMD7409 chipset support
-CONFIG_BLK_DEV_AMD7409
- This driver ensures (U)DMA support for the AMD756 Viper chipset.
+AMD Viper (7401/7409/7411) chipset support
+CONFIG_BLK_DEV_AMD74XX
+ This driver ensures (U)DMA support for the AMD756/760 Viper chipset.
[and]
-CONFIG_AMD7409_OVERRIDE
+CONFIG_AMD74XX_OVERRIDE
At any rate, I don't know if it's applicable for your problems at all
(it's not a small patch) but you're welcome to a copy of it if you want.
-Jacob
next prev parent reply other threads:[~2001-09-28 2:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-27 21:26 AMD viper chipset and UDMA100 Sean Swallow
2001-09-27 21:36 ` Nicholas Knight
2001-09-27 21:59 ` Vojtech Pavlik
2001-09-27 22:16 ` Dan Hollis
2001-09-27 22:24 ` Vojtech Pavlik
2001-09-27 22:54 ` Dan Hollis
2001-09-28 2:21 ` Jacob Luna Lundberg [this message]
2001-09-27 23:37 ` Sean Swallow
2001-09-28 10:21 ` [patch] " Vojtech Pavlik
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=Pine.LNX.4.21.0109271904170.28015-100000@inbetween.blorf.net \
--to=kernel@gnifty.net \
--cc=goemon@anime.net \
--cc=jacob@chaos2.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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).