linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mickael Marchand <marchand@kde.org>
To: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Silicon image 3114 SATA link (really basic support)
Date: Fri, 12 Dec 2003 01:07:49 +0100	[thread overview]
Message-ID: <200312120107.55031.marchand@kde.org> (raw)
In-Reply-To: <200312092114.47241.bzolnier@elka.pw.edu.pl>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

if anyone is able to tell me how to find the io address of the SATA ports I 
could make this patch support the 4 drives of Sil3114 (only the 2 first are 
working atm).
As I really don't know how to find this, I prefer ask to the kernel experts ;)
Once I have this info, making the patch is a matter of a few minutes I think

I tried looking at lspci/scanpci outputs but could not really find any usefull 
informations recording io ports.

Cheers,
Mik

Le Tuesday 09 December 2003 21:14, Bartlomiej Zolnierkiewicz a écrit :
> On Tuesday 09 of December 2003 19:54, Mickael Marchand wrote:
> > the attached patch makes _both_ drivers work (whereas the previous one
> > made only the libata one working)
>
> Great!  Now I know it is really working.
>
> I've already corrected your previous patch and included it in -bart1 patch:
> http://www.kernel.org/pub/linux/kernel/people/bart/2.6.0-test11-bart1/broke
>n-out/ide-siimage-sil3114.patch
>
> Yes, I forgot to send you corrected patch, sorry. :-)
>
> --bart
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/2QbVyOYzc4nQ8j0RAhO/AJ9bm0gJ7uwGlKquhXaIYm1GMRBVWQCdGPwn
wbQskwDqvS7PI54zTefPquM=
=p1UV
-----END PGP SIGNATURE-----

  reply	other threads:[~2003-12-12  0:07 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-03 20:44 Serial ATA (SATA) for Linux status report Jeff Garzik
2003-12-03 23:27 ` Andre Tomt
2003-12-03 23:36   ` Jeff Garzik
2003-12-03 23:49     ` Othmar Pasteka
2003-12-03 23:51       ` Jeff Garzik
2003-12-04  0:59     ` Samuel Flory
2003-12-04  1:02     ` Andre Tomt
2003-12-04 13:38     ` Justin Cormack
2003-12-04 14:54       ` Jeff Garzik
2003-12-04  8:17 ` Arnaud Launay
2003-12-04 15:01   ` Jeff Garzik
     [not found] ` <200312051842.26599.marchand@kde.org>
     [not found]   ` <3FD0C4B0.8020106@pobox.com>
     [not found]     ` <200312051907.13727.marchand@kde.org>
2003-12-09 18:22       ` [PATCH] Silicon image 3114 SATA link (really basic support) Aron Rubin
2003-12-09 18:54         ` Mickael Marchand
2003-12-09 20:14           ` Bartlomiej Zolnierkiewicz
2003-12-12  0:07             ` Mickael Marchand [this message]
2003-12-09 19:59 ` Serial ATA (SATA) for Linux status report J. Ryan Earl
2004-01-14 22:18 ` Greg Stark
2004-01-14 22:56   ` Erik Andersen
2004-01-14 23:31     ` James Courtier-Dutton
2004-01-15  0:41       ` Jeff Garzik
2004-01-15  2:38         ` Erik Andersen
2004-01-18 12:34         ` Martin Schlemmer
2004-01-14 23:12   ` Erik Steffl
2004-01-18 13:32 ` Witold Krecicki
2004-01-18 18:00   ` Jeff Garzik
2004-01-18 20:33     ` Craig Bradney

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=200312120107.55031.marchand@kde.org \
    --to=marchand@kde.org \
    --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).