From: Wes Newell <w.newell@verizon.net>
To: Arnaud Patard <apatard@mandriva.com>
Cc: Uwe Koziolek <uwe.koziolek@gmx.net>,
"linux.ide" <linux-ide@vger.kernel.org>
Subject: Re: maintenence sata_sis
Date: Tue, 23 Aug 2005 16:14:41 -0500 [thread overview]
Message-ID: <430B91C1.6040407@verizon.net> (raw)
In-Reply-To: <m3fyt02y2t.fsf@anduin.mandrakesoft.com>
Arnaud Patard wrote:
>Wes Newell <w.newell@verizon.net> writes:
>
>
>
>>Uwe Koziolek wrote:
>>
>>
>>
>>>Wes Newell wrote:
>>>
>>>
>>>
>>>>I've got a Jetway S755MAX that also has a real SIS180 onboard and have
>>>>been trying to get PATA support for it without any luck for several
>>>>months now. The sata_sis driver from SIS just locks up the machine
>>>>when I attach a pata drive. With the help of a few here, I patched the
>>>>sis5513 driver, but it has lost interrupt problems. I basically gave
>>>>up on this ever working a couple of months ago. Do you think there's
>>>>any hope at all? I'm willing to try whatever some can point me
>>>>towards, but I'm not a C programmer. I can compile kernels though and
>>>>follow instructions.
>>>>
>>>>
>>>>
>>>The SiS180 has disabled the interrupts by default. You must enable the
>>>interrupts in the PCI-config space.
>>>You can find a function pci_enable_intx() in the sata_sis.c.
>>>
>>>regards
>>>Uwe Koziolek
>>>
>>>
>>>
>>Well, now you've really lost me. I wasn't using sata_sis when I got
>>the drive to work with lost interrupts. I was using a patched sis5513
>>ide driver. So maybe I should just forget that and say that the
>>
>>
>
>the sis5513 driver is the ide driver and sata_sis for sata/pata.
>
>
>
This much I know, but since the original sata_sis with 2.6.11 didn't see
the drives at all and the SIS sata_sis locked up the machine with a pata
drive atached, and I don't have any sata drives, I just tried patching
it, and it at least saw the drives and I could read and write to them,
but because of the lost interrrupts, it was realllll slow. I would much
prefer to get both sata and pata portion of it working with sata_sis if
possible.
>>machine locks up solid when I try and load sata_sis from
>>sis18x_2.6.10_1.00.00. So I really don't understand what you are
>>saying I need to do here. Remember, I'm not a C programmer and only
>>came here some months back to see if someone could fix this. I'm
>>willing to help in any way I can testing, but if you want me to patch
>>something or enable something, you're going to have to lead me by the
>>
>>
>
>Even if it was not perfect as concern the pata support, you may also
>test the patch I mailed.
>
>
>
What patch was this and for which sata_sis was it for and where do i get it.
next prev parent reply other threads:[~2005-08-23 21:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 16:39 [RFC][PATCH] add support for SIS 182 sata chipset in sata sis Arnaud Patard
2005-08-22 10:01 ` maintenence sata_sis Uwe Koziolek
2005-08-22 10:41 ` Rainer Koenig
2005-08-22 11:48 ` Arnaud Patard
2005-08-23 4:31 ` Wes Newell
2005-08-23 8:04 ` Uwe Koziolek
2005-08-23 17:58 ` Wes Newell
2005-08-23 20:32 ` Arnaud Patard
2005-08-23 21:14 ` Wes Newell [this message]
2005-08-23 22:02 ` Sis180 Jetway S755Max Uwe Koziolek
2005-08-24 6:20 ` Wes Newell
2005-08-29 13:29 ` Arnaud Patard
2005-08-29 17:58 ` Wes Newell
2005-08-30 7:46 ` Wes Newell
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=430B91C1.6040407@verizon.net \
--to=w.newell@verizon.net \
--cc=apatard@mandriva.com \
--cc=linux-ide@vger.kernel.org \
--cc=uwe.koziolek@gmx.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.