public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: "S.Salman Ahmed" <ssahmed@pathcom.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ATA100/UDMA100 Support on the ASUS-CUSL2 mobo
Date: Thu, 30 Nov 2000 10:18:32 +0100	[thread overview]
Message-ID: <20001130101832.A344@suse.cz> (raw)
In-Reply-To: <14885.64113.780609.704554@phoenix.somewhere.out.there>
In-Reply-To: <14885.64113.780609.704554@phoenix.somewhere.out.there>; from ssahmed@pathcom.com on Thu, Nov 30, 2000 at 01:57:54AM -0500

On Thu, Nov 30, 2000 at 01:57:54AM -0500, S.Salman Ahmed wrote:
> 
> [I am not subscribed to the list, so please CC: me]
> 
> Hi,
> 
> How well is the ATA100/UDMA100 supported in the development kernels ? I
> have a system with an ASUS CUSL2 mobo, which has built-in ATA100 IDE
> channels, alongwith a Maxtor 20Gb ATA100 HD.
> 
> I looked at the kernel config for 2.4.0-test11, but in the "IDE, ATA and
> ATAPI Block devices" section couldn't find chipset-specific support for
> either the:
> 
> (1) Intel i815 chipset, which is what the ASUS-CUSL2 has
> 
> or the
> 
> (2) Intel I/O Controller Hub 2 (ICH2)
> 
> I'd like to get my system working using the built-in ATA100 controller
> on the ASUS CUSL2, but what options do I need in 2.4.0-test11's kernel
> config ?
> 
> Is there support for the Intel i815 chipset ?

Yes, the PIIX driver should be able to handle ICH2 and ATA100.

-- 
Vojtech Pavlik
SuSE Labs
-
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/

      reply	other threads:[~2000-11-30  9:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-30  6:57 ATA100/UDMA100 Support on the ASUS-CUSL2 mobo S.Salman Ahmed
2000-11-30  9:18 ` Vojtech Pavlik [this message]

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=20001130101832.A344@suse.cz \
    --to=vojtech@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ssahmed@pathcom.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