public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Evan Thompson <evaner@bigfoot.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Additional info. for PCI VIA IDE crazyness.  Please read.
Date: Tue, 2 Jan 2001 20:08:55 -0600	[thread overview]
Message-ID: <20010102200855.A278@evaner.penguinpowered.com> (raw)
In-Reply-To: <20010102102900.A328@evaner.penguinpowered.com> <Pine.LNX.4.10.10101021046330.25012-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.10.10101021046330.25012-100000@penguin.transmeta.com>; from torvalds@transmeta.com on Tue, Jan 02, 2001 at 10:56:27AM -0800

Oh, and adding that option DID fix the lost interrupt problems
(ide1=0x170,0x376,15), so yeah, that fix fixed it.

Thanks for your help.  Maybe it should become a config option to enable
that (CONFIG_BLK_DEV_MESSED_UP_VIA_CHIPSET_FIX).
-- 
| Evan Thompson                    | ICQ:    2233067   |
| Freelance Computer Nerd          | AIM:    Evaner517 |
| evaner@bigfoot.com               | Yahoo!: evanat    |
| http://evaner.penguinpowered.com | MSN:    evaner517 |
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2001-01-03  2:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-02  2:34 Additional info. for PCI VIA IDE crazyness. Please read Evan Thompson
2001-01-02  4:33 ` Linus Torvalds
     [not found] ` <200101020433.UAA23808@penguin.transmeta.com>
2001-01-02 16:29   ` Evan Thompson
2001-01-02 18:56     ` Linus Torvalds
2001-01-03  1:57       ` Evan Thompson
2001-01-03  2:08       ` Evan Thompson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-01-02  5:52 Ray Strode

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=20010102200855.A278@evaner.penguinpowered.com \
    --to=evaner@bigfoot.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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