linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Uwe Koziolek <uwe.koziolek@gmx.net>
To: fbourdonnec@chez.com
Cc: Jeff Garzik <jeff@garzik.org>, linux-ide@vger.kernel.org
Subject: Re: SiS driver K2.4 for 180/182/965/966....
Date: Sun, 05 Aug 2007 12:36:44 +0200	[thread overview]
Message-ID: <46B5A83C.4070506@gmx.net> (raw)
In-Reply-To: <200707300140.18940.fbourdonnec@chez.com>

Franck Bourdonnec wrote:
> Hello Uwe & Jeff,
>
>
> I'm trying to follow the 'life' of this driver "sata_sis.c".
>
> I want to report back in Kernel 2.4.34 the additions found
> since some time. I do this to extend IPCOP usage of
> SATA boards and also to contribute to linux kernel if
> possible.
>   
As far as i know the kernel 2.4 is nearly frozen.
> It's not easy because there is many source, that seems
> like each others, but not exactly
>
> 1) http://driver.sis.com/linux/raid/sis18x_20060508.zip
> 2) what is today in kernel 2.6.21
>   
The 2.6.22 supports the actual SiS hardware, in 2.6.21 not all hardware
works, like the SATA SiS968
> 3) the list of patch against sata_sis.c (git)
> 4) the kernel 2.4.34 "sata_sis.c" source
>
> After compiling all this, result is a kernel 2.4 driver
> that I think, ressemble a lot to the actual 2.6 version.
>
> I would like you just to read the source (test it??) for advice.
>
>
> ========================
>
> Strange thing I noted is:
>
> Sis1180,1184: present in sis18x_20060508.zip but inexistant
>   
The 1180 is supported in 2.6.22, see pata_sis.c , the 1184 is supported
in ahci.c. The 1183 and the 0x0180 support was done by
PATA.
> elsewhere (particulary in K2.6). Why?
>
> ========================
>
> in this fix 
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.22.y.git;a=commitdiff;h=29da9f6d9cc3685ae7f6c8b817f6ed8864c78a4c
>
> the call to "ata_pci_init_native_mode" function is a little bit changed: 
> &ppi becomes ppi.
>   
libata v2 supports 2 ports with different data. This is not supported in
the libata v1. A ppi array is not necessary.
> probe_ent = ata_pci_init_native_mode(pdev, ppi, ATA_PORT_PRIMARY | 
> ATA_PORT_SECONDARY);
>
> just a confirmation that this match K2.4 prototype. Sometimes I don't really 
> follow some C notation with **  ;-)
>
> ==========================
>
> I wasn't sure here:
>
> 1)
> .host_flags  = ATA_FLAG_SATA | ATA_FLAG_SLAVE_POSS | ATA_FLAG_SATA_RESET |
>                           ATA_FLAG_NO_LEGACY,
> 2)
> .host_flags  = ATA_FLAG_SATA | ATA_FLAG_SATA_RESET |
>                           ATA_FLAG_NO_LEGACY,
> 3)
> .host_flags  = ATA_FLAG_SATA | ATA_FLAG_NO_LEGACY,
>
>
>
> Choosed 2) because
> ATA_FLAG_SLAVE_POSS is positionned in the code (set to one)
>
>
>   
It is ok.
> =========================
>
> Thank you to have read this.
> Hope it's ok. For my project (IPCop) or directly in k2.4
> if you don't see major obstacle.
>
> Franck
>   
Uwe

      reply	other threads:[~2007-08-05 10:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-29 23:40 SiS driver K2.4 for 180/182/965/966 Franck Bourdonnec
2007-08-05 10:36 ` Uwe Koziolek [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=46B5A83C.4070506@gmx.net \
    --to=uwe.koziolek@gmx.net \
    --cc=fbourdonnec@chez.com \
    --cc=jeff@garzik.org \
    --cc=linux-ide@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).