public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Rainer Koenig <Rainer.Koenig@fujitsu-siemens.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SATA status report updated
Date: Fri, 19 Aug 2005 14:34:11 -0400	[thread overview]
Message-ID: <43062623.607@pobox.com> (raw)
In-Reply-To: <871x4ql24a.fsf@ABG3595C.abg.fsc.net>

Rainer Koenig wrote:
> Hi Simon,
> 
> Simon Oosthoek <simon.oosthoek@ti-wmc.nl> writes:
> 
> 
>>I'm wondering how the support for the SIS 182 controller is doing, I
>>noticed they have a GPL driver on their website for kernel 2.6.10,
>>which is not a drop in replacement for sata_sis.c in 2.6.12.5, I
>>haven't tried compiling it as an add-on module outside the tree,
>>though...
> 
> 
> I tried the sources from the SiS website (that seem to add more
> details than my simple patch that just adds the device ID) as a drop
> in for the Fedora installation kernel 2.6.11-1.1369_FC4, but the
> kernel build process ran into an error at the sata_sis module. The
> problem is that the source from SiS has a conditional code that
> depends on the definition of a symbol "KERN_2_6_10" which is defined
> by their "outside build makefile", but not in the standard kernel
> build process. I added a #define KERN_2_6_10 to the source and then it
> compiled also inside the kernel build process.
> 
> 
>>Adding the 0x182 identifier to the 180 driver does compile (duh!), but
>>I haven't tried it on hardware.
> 
> 
> Working at a PC manufacturer I have access to hardware and I tried out
> a lot and didn't run into any problem so far. 
> 
> 
>>As a temporary measure, there was a patch posted to this list [1] a
>>while ago, would it be a good idea to include this while full support
>>is being worked on?
> 
> 
> Seeing that the source from the SiS website is much more going into the
> details than my simple adding of the device ID (of course SiS has hopefully
> a much deeper knowledge of their hardware than I have ;-) I would rather
> go for integrating the SiS source in the current kernel. 

Yes, that's why I have resisted the "just add the PCI ID" patches that 
have cropped up.

SiS submitted patches that duplicated portions of libata inside their 
driver, rather than simply fixing libata as would be proper.

So we are stuck in the middle :(

Someone needs to work with the SiS submission until it's kosher with the 
upstream kernel, then everybody will be happy.

	Jeff



  reply	other threads:[~2005-08-19 18:34 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4AA7B-4jm-5@gated-at.bofh.it>
     [not found] ` <4DagM-7c8-43@gated-at.bofh.it>
2005-08-19  9:14   ` SATA status report updated Rainer Koenig
2005-08-19 18:34     ` Jeff Garzik [this message]
2005-08-19 23:01       ` Simon Oosthoek
2005-08-20  0:02         ` Jeff Garzik
2006-05-15 15:20 Jeff Garzik
2006-05-15 17:07 ` Sven-Haegar Koch
2006-05-15 18:17   ` Jeff Garzik
     [not found] <4DbcF-8ux-3@gated-at.bofh.it>
     [not found] ` <4DbcG-8ux-5@gated-at.bofh.it>
     [not found]   ` <4DbcF-8ux-1@gated-at.bofh.it>
     [not found]     ` <4DjWG-4ea-19@gated-at.bofh.it>
     [not found]       ` <4Do9X-1IZ-5@gated-at.bofh.it>
     [not found]         ` <4Dp62-304-15@gated-at.bofh.it>
2005-08-20 15:36           ` Rainer Koenig
2005-08-22  8:07             ` Simon Oosthoek
2005-08-22 18:07               ` Rainer Koenig
  -- strict thread matches above, loose matches on Subject: below --
2005-08-12 10:24 Daniel J Blueman
2005-08-12 21:30 ` Jeff Garzik
2005-08-12  5:09 Jeff Garzik
2005-08-12  5:40 ` Rob van Nieuwkerk
2005-08-12  5:45   ` Jeff Garzik
2005-08-12 18:07     ` David Greaves
2005-08-12 10:44 ` Matthew Garrett
2005-08-12 21:30   ` Jeff Garzik
2005-08-13  8:45     ` Erik Slagter
2005-08-12 14:18 ` Luben Tuikov
2005-08-12 14:46 ` Luben Tuikov
2005-08-12 19:17 ` Mogens Valentin
2005-08-12 21:33   ` Jeff Garzik
2005-08-19  8:09 ` Simon Oosthoek
2005-08-21 17:11 ` Mogens Valentin
2005-08-21 18:05   ` Jeff Garzik

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=43062623.607@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=Rainer.Koenig@fujitsu-siemens.com \
    --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