linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Backlund <tmb@mandriva.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Problem with SiS Ide/Pata/Sata on 2.6.22-rc7-git4
Date: Tue, 10 Jul 2007 23:51:54 +0300	[thread overview]
Message-ID: <4693F16A.4050709@mandriva.org> (raw)
In-Reply-To: <20070709232742.004def28@the-village.bc.nu>

Alan Cox skrev:
>> If you modprobe only sis5513
>>   OR
>> If you modprobe only sis5513 and then sata_sis/pata_sis:
>>   - you get this:
>>     (the hdb drive does not get detected/usable)
> 
> Don't mix old and new IDE like that. We allow both so you can use old SIS
> and new Jmicron etc for example but there are some cases where trying to
> load both old and new IDE support for the same chip will do strange
> things.
> 

But there is still a regression here compared to 2.6.17...

If you load only sis5513 on a 2.6.22 you still get:
--- quote ---
<6>SIS5513: chipset revision 1
<6>SIS5513: not 100% native mode: will probe irqs later
<6>SIS5513: SiS 962/963 MuTIOL IDE UDMA133 controller
<6>    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:pio, hdb:pio
<6>    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:pio
<7>Probing IDE interface ide0...
<4>hdb: QUANTUM FIREBALLlct15 07, ATA DISK drive
<4>hdb: host side 80-wire cable detection failed, limiting max speed to 
UDMA33
<7>hdb: selected mode 0x42
--- quote ---

wich does not happend on 2.6.17...

The disk in question is ATA66 capable

--
Thomas

  parent reply	other threads:[~2007-07-10 20:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-09 21:25 Problem with SiS Ide/Pata/Sata on 2.6.22-rc7-git4 Thomas Backlund
2007-07-09 22:27 ` Alan Cox
2007-07-09 22:40   ` Thomas Backlund
2007-07-10 20:51   ` Thomas Backlund [this message]
2007-07-13 21:32     ` Bartlomiej Zolnierkiewicz

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=4693F16A.4050709@mandriva.org \
    --to=tmb@mandriva.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).