From: Kasper Dupont <kasperd@daimi.au.dk>
To: Andre Hedrick <andre@linux-ide.org>, Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ALi IDE problem
Date: Tue, 04 Jun 2002 12:52:56 +0200 [thread overview]
Message-ID: <3CFC9C08.9D73FF62@daimi.au.dk> (raw)
In-Reply-To: <Pine.LNX.4.10.10206021436530.5846-100000@master.linux-ide.org> <3CFC58DC.269E0C88@daimi.au.dk>
Kasper Dupont wrote:
>
> Andre Hedrick wrote:
> >
> > Kasper,
> >
> > http://www.linuxdiskcert.org/ide-2.4.19-p8-ac1.all.convert.10.patch.bz2
> > http://www.linuxdiskcert.org/ide-2.4.19-p7.all.convert.10.patch.bz2
> >
> > Please try this on top of a stock 2.4.19-pre8-ac1 plus patch.
> > Also try a stock 2.4.19-pre7 plus patch.
> >
> > First, at line 553.
> >
> > #define ALI_INIT_CODE_TEST
> >
> > Change to
> >
> > #undef ALI_INIT_CODE_TEST
>
> Many hourse of kernel compilations later:
>
> The following works:
> -pre7
> -pre8-ac1
> -pre8-ac2
>
> The following fails:
> -pre7 with ide patch
> -pre8-ac1 with ide patch
> -pre8-ac3
> -pre8-ac4
> -pre8-ac5
>
> Changing ALI_INIT_CODE_TEST doesn't help.
> It fails both with #define and #undef.
>
> Perhaps I should try reverting the patch
> against -pre9-ac3?
Reverting the patch against 2.4.19-pre9-ac3 seems to solve my
problem. Now DMA works. (A single hunk got rejected and had
to be applied by hand.)
--
Kasper Dupont -- der bruger for meget tid på usenet.
For sending spam use mailto:razor-report@daimi.au.dk
next parent reply other threads:[~2002-06-04 10:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10206021436530.5846-100000@master.linux-ide.org>
[not found] ` <3CFC58DC.269E0C88@daimi.au.dk>
2002-06-04 10:52 ` Kasper Dupont [this message]
2002-06-05 17:42 ` ALi IDE problem Andre Hedrick
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=3CFC9C08.9D73FF62@daimi.au.dk \
--to=kasperd@daimi.au.dk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.org \
--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