linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Uwe Koziolek <uwe.koziolek@gmx.net>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: Sven Ladegast <sven@linux4geeks.de>,
	uwe.koziolek@web.de, linux-ide@vger.kernel.org
Subject: Re: sata_sis and SIS180 in combined mode
Date: Mon, 04 Dec 2006 01:50:19 +0100	[thread overview]
Message-ID: <457370CB.60008@gmx.net> (raw)
In-Reply-To: <20061204001114.066b10f3@localhost.localdomain>


>> Because you are only using the PATA port, you can make a private
>> solution, move the PCI-ID 180 from  sata_sis.c  to  sis5513.c  or 
>> pata_sis.c
>> dependend on the ide driver you want to use.
>>
>> The SiS180 has no hardware RAID functionality, It is only a BIOS based
>> software raid. The SiS180 is a combined  SATA/PATA controller.
>>
>> I will try a patch for this issue.
>>     
>
> Are both ports off the same set of PCI resources ? If not then it would
> be better to put a set of entry points into pata_sis that allow sata_sis
> to "plug in" pata support. I'm happy to help hack on this given enough
> info.
>
> Alan
>
>   
One port is PATA, the other port is SATA, they have the same PCI
resources. It is possible to configure
the controller to use both ports in SATA mode without slave. Then the
PATA part of the controller is not
reachable.

Uwe

  reply	other threads:[~2006-12-04  0:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-03 17:34 sata_sis and SIS180 in combined mode Sven Ladegast
2006-12-03 23:04 ` Alan
2006-12-03 23:06   ` Sven Ladegast
2006-12-03 23:18 ` Uwe Koziolek
2006-12-04  0:11   ` Alan
2006-12-04  0:50     ` Uwe Koziolek [this message]
2006-12-04 12:56       ` Alan
2006-12-05  0:12         ` Uwe Koziolek
2006-12-05  0:31           ` Alan
2006-12-10 15:01             ` Uwe Koziolek
2006-12-10 15:51               ` Alan
2006-12-18 22:14 ` Uwe Koziolek

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=457370CB.60008@gmx.net \
    --to=uwe.koziolek@gmx.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-ide@vger.kernel.org \
    --cc=sven@linux4geeks.de \
    --cc=uwe.koziolek@web.de \
    /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).