linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: "John Stoffel" <stoffel@lucent.com>
Cc: linux-kernel@vger.kernel.org, andre@linux-ide.org
Subject: Re: 2.6.5-rc3: cat /proc/ide/hpt366 kills disk on second channel
Date: Tue, 6 Apr 2004 23:02:17 +0200	[thread overview]
Message-ID: <200404062302.17698.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <16499.3204.604627.205193@gargle.gargle.HOWL>

On Tuesday 06 of April 2004 22:01, John Stoffel wrote:
> Bart,
>
> You're patch does the trick, I can now do cat /proc/ide/hpt366 without
> any problems.  Time to re-sync my md mirror.
>
> I'll also pull this patch forward to 2.6.5 and make sure to submit it
> to Linus/Andrew, unless you'll do that part?

I'll take care of it. :)

> I do wish the cable detection stuff worked though... too bad about the

Cable detection works just fine, see init_hwif_hpt366().

> outb() stuff.  Maybe I can poke at it and figure out what kind of
> locking is required here to make this work right.  Would it need to be
> queued up as a regular HWIF command?  Can you tell I don't know what
> I'm talking about?  *grin*

regular HWIF command?  It can be fixed using REQ_SPECIAL special request
but I don't think it's worth the work - remove #ifdef/#endif DEBUG around
printk() in init_hwif_hpt366() if you need info about cable.

Thanks,
Bartlomiej


  reply	other threads:[~2004-04-06 20:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-05  0:00 2.6.5-rc3: cat /proc/ide/hpt366 kills disk on second channel John Stoffel
2004-04-06 16:06 ` John Stoffel
2004-04-06 17:00   ` Bartlomiej Zolnierkiewicz
2004-04-06 18:35     ` John Stoffel
2004-04-06 20:01     ` John Stoffel
2004-04-06 21:02       ` Bartlomiej Zolnierkiewicz [this message]
2004-04-07 15:41         ` John Stoffel

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=200404062302.17698.bzolnier@elka.pw.edu.pl \
    --to=b.zolnierkiewicz@elka.pw.edu.pl \
    --cc=andre@linux-ide.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stoffel@lucent.com \
    /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).