public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergey Vlasov <vsu@altlinux.ru>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Sergei Organov <osv@javad.com>, linux-kernel@vger.kernel.org
Subject: Re: SATA ICH6M problems on Sharp M4000
Date: Tue, 6 Dec 2005 13:31:30 +0300	[thread overview]
Message-ID: <20051206103129.GA18233@master.mivlgu.local> (raw)
In-Reply-To: <439484EC.5080406@pobox.com>

[-- Attachment #1: Type: text/plain, Size: 1530 bytes --]

On Mon, Dec 05, 2005 at 01:20:28PM -0500, Jeff Garzik wrote:
> Sergei Organov wrote:
> >Sergey Vlasov <vsu@altlinux.ru> writes:
> >>See http://lkml.org/lkml/2005/10/18/167 and the reply to it :-\
> >
> >Well, Jef's answer was:
> >
> >  This is a reasonable point, but the rare person who runs modular IDE on 
> >  these PATA/SATA combined mode beasts can certainly tell the IDE driver 
> >  to not probe certain ports.
> >
> >I can say that the kernel I have problem with is from Debian "testing"
> >distribution so those "rare person" going to become quite a few in the
> >near future. Besides, Debian loads ata_piix first, then IDE, so telling
> >the IDE to ignore certain ports won't help.

mkinitrd in ALT Linux has some hacks to detect driver type (IDE or SCSI
subsystem) and load all IDE drivers before SCSI - exactly for this reason.

> >Though one can argue that that's yet another distribution problem, I
> >fail to see a way for a distribution to overcome the problem provided it
> >doesn't know the exact hardware it will run on. No hope for modularized
> >kernel to run out of the box on given hardware?
> >
> >Jeff, is there any hope it will be fixed in the kernel.org sources, or
> >should I report the problem to Debian instead so that they consider
> >maintaining their own patch?
> 
> Debian doesn't need to maintain a patch, they should load modules in the 
> proper order.

This will not help - without my patch the combined mode support code is
not compiled if IDE is modular.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-12-06 10:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200511221013.04798.marekw1977>
2005-12-02 19:33 ` SATA ICH6M problems on Sharp M4000 Sergei Organov
2005-12-05 17:22   ` Sergey Vlasov
2005-12-05 18:15     ` Sergei Organov
2005-12-05 18:20       ` Jeff Garzik
2005-12-05 18:48         ` Sergei Organov
2005-12-06 10:31         ` Sergey Vlasov [this message]
2005-11-21 22:30 Josh Litherland
2005-11-21 22:39 ` Randy.Dunlap
2005-11-21 23:13   ` Marek W
2005-11-21 23:41 ` Jeff Garzik
2005-11-22 16:20   ` Josh Litherland
2005-11-22 16:28     ` 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=20051206103129.GA18233@master.mivlgu.local \
    --to=vsu@altlinux.ru \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=osv@javad.com \
    /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