From: Lionel Bouton <Lionel.Bouton@inet6.fr>
To: Silvio Cesare <silvio@big.net.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sis650/5513 in 2.4.19 (still broken for 650)
Date: Tue, 19 Nov 2002 11:58:25 +0100 [thread overview]
Message-ID: <20021119115825.A4742@bouton.inet6-interne.fr> (raw)
In-Reply-To: <20021118222401.GA3777@localhost.localdomain>; from silvio@big.net.au on mar, nov 19, 2002 at 09:24:01 +1100
On mar, nov 19, 2002 at 09:24:01 +1100, Silvio Cesare wrote:
> Attachment.
>
> --
> Silvio
> No fixes here.. just reports for anyone interested :(
>
> 1) sis650/5513 chipset does not work with UDMA - this was reported a while
> ago, and also reported fixed.. but I don't think its been tested on a
> sis650 specifically, which (for me) appears still broken (fs
> corruptions etc).
>
This is fixed in AC tree.
> this was reported fixed in 2.4.19; i took a 2.4.18 kernel, and replaced
> drivers/ide/sis5513.c (theres some includes also, but perhaps not
> important). this came up with the same problems as 2.4.18.
>
The driver in 2.4.19-pre broke latest SiS chipsets in DMA modes. Some 650
were affected -> to be safe DMA was disabled for all of them.
Stock 2.4.19 should not fail but only disable DMA, could you confirm this ?
> 2.4.18 incidentally has a function #if 0, at the end of sis5513.c,
> which I had to make #if 1 (remove) to get a compile (there appears to be
> no other declaration of this code in the tree) - this has probably
> been noticed a long time ago I imagine (?).
>
IIRC this #ifdef is only for compatibility purpose between different IDE
framework versions.
> for the UDMA issues, recompiling with -->
>
> #define BROKEN_LEVEL XFER_SW_DMA_0
>
> gets it up and running again (ie, without UDMA).
>
> incidentally.. the sis 0.13 code by the maintainers have patches
> against 2.4.18 which break when you run it with #define DEBUG, as
> some var names have been slightly modified.
?! Could you please try the AC tree with #define DEBUG and report the result
to me ?
> 2) External floppy drive via USB not 100% working.. No idea on this one;
> I've included very small snippets of bootup messages, but it's no
> major drama currently (works for the most part), so I don't really
> expect anyone to look at this (especially with the minimal info
> I've provided here) :)
Won't be of much help here anyway :-)
> For the sis650, maybe (?) the following will help -->
> [ I've no real clue how useful or non useful this is, but maybe its
> worth a look for the current development ]
The dump is rather usefull, especially if I know your BIOS config.
Here I assume that each controller is enabled and DMA activated for hda and
hdc, am I right ?
Happy AC compile :-)
LB.
prev parent reply other threads:[~2002-11-19 10:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-18 22:24 Silvio Cesare
2002-11-19 10:58 ` Lionel Bouton [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=20021119115825.A4742@bouton.inet6-interne.fr \
--to=lionel.bouton@inet6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=silvio@big.net.au \
/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
all inboxes | Powered by JetHome®