From: "L.C. Chang" <lcchang@sis.com.tw>
To: "Daniela Engert" <dani@ngrt.de>,
"Lionel Bouton" <Lionel.Bouton@inet6.fr>
Cc: "???" <ollie@sis.com.tw>, "???" <kmliu@sis.com.tw>,
"linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: SiS 5513 ATA133 support patch for 2.4.19-rc3-ac3
Date: Mon, 29 Jul 2002 19:35:40 +0800 [thread overview]
Message-ID: <003d01c236f4$110b0450$e6d113ac@sis2262> (raw)
In-Reply-To: 20020729105626.A16395@bouton.inet6-interne.fr
SiS 745/746/750/... like 645/646/650/..., is an independent north bridge
which may be paired with SiS 961a/961b/962(963).
And as you known, the northbridge ID alone was not able to distinguish
the UDMA support in those chipset family. So I changed all of them
to ATA133 in my patch. When ATA133 family found in
pci_init_sis5513(), I would look for further information to determine
which family it belongs to (ATA100/ATA133a/ATA133).
L.C.
> On lun, jui 29, 2002 at 09:11:34 +0200, Daniela Engert wrote:
> > On Mon, 29 Jul 2002 01:37:54 +0200, Lionel Bouton wrote:
> >
> >
> > Lionel,
> >
> > as you already figured out, looking at the northbridge IDs is simply
> > not sufficient to find out which capabilities and register layout the
> > IDE controller in the southbridge (no matter if integrated or external)
> > has.
> >
> > Some comments:
> >
> > 1) the 745 has an integrated southbridge and an ATA/100 capable IDE
> > controller
> >
>
> I believed so too, but Lei-Chun patch changed it to ATA133.
> Lei-Chun, could you tell us what we can expect from 745 chips ?
>
> > 2) the 646 (and most likely the 645 and others as well) may be paired
> > with a 961 (ATA/100) or 961B (ATA133) MutIOL southbridge with different
> > register programming values.
> >
> > Thus simply ripping out some northbridge IDs wouldn't prevent
> > corruption problems.
> >
>
> I don't see why (unless you refer to the 962/963 problem I did mention).
> If we remove the IDs, the chips will be detected as SiS5513 (ATA_16). If
> I'm correct, in this mode (only allowing PIO modes and SW/MW DMA modes)
> all chips are OK.
> I didn't dig in all specs to check each config register change, but all I
> saw was OK and I *never* received any data corruption report for a chip
that
> was configured as original SiS5513 (though I have many reports of bad
> performance due to PIO modes being used in such cases).
>
> LB.
next prev parent reply other threads:[~2002-07-29 11:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-28 23:37 SiS 5513 ATA133 support patch for 2.4.19-rc3-ac3 Lionel Bouton
2002-07-28 23:43 ` Alan Cox
2002-07-29 7:11 ` Daniela Engert
2002-07-29 8:56 ` Lionel Bouton
2002-07-29 9:15 ` Daniela Engert
2002-07-29 11:35 ` L.C. Chang [this message]
2002-07-29 19:12 ` Marcelo Tosatti
2002-07-30 16:38 ` Lionel Bouton
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='003d01c236f4$110b0450$e6d113ac@sis2262' \
--to=lcchang@sis.com.tw \
--cc=Lionel.Bouton@inet6.fr \
--cc=dani@ngrt.de \
--cc=kmliu@sis.com.tw \
--cc=linux-kernel@vger.kernel.org \
--cc=ollie@sis.com.tw \
/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