From: Samuel Flory <sflory@rackable.com>
To: Ian Chilton <ian@ichilton.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Anyone use HPT366 + UDMA in Linux?
Date: Fri, 15 Nov 2002 11:10:49 -0800 [thread overview]
Message-ID: <3DD546B9.3040000@rackable.com> (raw)
In-Reply-To: 20021115184202.GB32543@buzz.ichilton.co.uk
Ian Chilton wrote:
>Hello,
>
>
>
>>If it still doesnt work in 2.4.20-rc1-ac2 or later please send me a
>>detailed bug report
>>
>>
>
>Does that mean you know it's been broken and/or are there changes to
>HPT366 in 2.4.20-rc1-ac2?
>
>
What is means is Alan is doing a thankless job fixing the current ide
mess. The ac 2.4/2.5 trees are being used to test a number of updates.
If you can provide Alan good bug report on the issue in 2.4.20-rc1-ac2.
He will take a look at fixing the code. I think the info he needs
would be:
-The ide section of dmesg or all of dmesg
-output of hdparm -vi /dev/hd(whatever)
-result of hdparm -d 1 /dev/hd(whatever)
>I've been trying 2.4.19, 2.4.20-pre11 and 2.4.20-rc1 with and without
>Rik's fairsched patch.
>
>
>
>
next prev parent reply other threads:[~2002-11-15 19:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-15 12:35 Anyone use HPT366 + UDMA in Linux? Ian Chilton
2002-11-15 14:39 ` Alan Cox
2002-11-15 18:42 ` Ian Chilton
2002-11-15 19:10 ` Samuel Flory [this message]
2002-11-15 22:44 ` Ian Chilton
2002-11-15 22:15 ` Miloslaw Smyk
2002-11-15 22:51 ` Ian Chilton
2002-11-15 23:29 ` Miloslaw Smyk
2002-11-16 11:18 ` Zdenek SUTR Kaminski
2002-11-15 16:27 ` Leopold Gouverneur
2002-11-15 16:28 ` Ian Chilton
[not found] ` <20021115173120.GA1152@gouv>
2002-11-15 18:34 ` Ian Chilton
2002-11-15 19:15 ` Samuel Flory
2002-11-16 0:19 ` Kevin Krieser
-- strict thread matches above, loose matches on Subject: below --
2002-11-15 21:04 Ian Castle
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=3DD546B9.3040000@rackable.com \
--to=sflory@rackable.com \
--cc=ian@ichilton.co.uk \
--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