public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David van Hoose <davidvh@cox.net>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] Support for SiS 961/961B/962/963/630S/630ET/633/733 IDE
Date: Fri, 16 May 2003 12:07:53 -0400	[thread overview]
Message-ID: <3EC50CD9.6020508@cox.net> (raw)
In-Reply-To: <20030516143021.A17346@ucw.cz>

Vojtech Pavlik wrote:
> Hi!
> 
> The goal of this patch is to add support for the new generation of
> MuTIOL southbridges by SiS, namely the 961/961B, 962 and 963. These
> integrate the IDE controller, unlike all other SiS chipsets where the
> controller is bound to the northbridge.
> 
> I had to do quite some research on what SiS IDE controllers exist that
> don't use the 96* southbridges, and thus found out that the 633 and 733
> controllers were missing. So those were added too.
> 
> This patch hovewer integrates a patch from Lionel which adds 630S/ET
> UDMA100 support.
> 
> And while doing the changes I did also some cleanups, mainly removing a
> bunch of debug code that doesn't seem very useful when lspci does the
> same job. And removing the config_drive_xfer_rate in favor of functions
> from ide-timing.h.
> 
> Tested on SiS963, works great.
> 
> Patches for current 2.4 and 2.5 attached.

I never thought about it, but my SiS963 is not recognized in lspci. The 
below is a link which has a diagram of the SiS648/SiS963 combo that is 
on my motherboard. Would it enhance performance any or would this 
correction just be cosmetic?

Thanks,
David

Link: http://www.sis.com/products/chipsets/oa/pentium4/648.htm


  reply	other threads:[~2003-05-16 15:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-16 12:30 [patch] Support for SiS 961/961B/962/963/630S/630ET/633/733 IDE Vojtech Pavlik
2003-05-16 16:07 ` David van Hoose [this message]
2003-05-16 16:25   ` Vojtech Pavlik
2003-05-16 17:14 ` Bartlomiej Zolnierkiewicz
2003-05-17  8:16   ` Vojtech Pavlik

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=3EC50CD9.6020508@cox.net \
    --to=davidvh@cox.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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