public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roger Heflin <rheflin@atipa.com>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: What determines which interrupts are shared under Linux?
Date: Tue, 15 Aug 2006 18:11:18 -0500	[thread overview]
Message-ID: <44E25496.20705@atipa.com> (raw)
In-Reply-To: <44E252E9.40704@shaw.ca>

Robert Hancock wrote:
> Roger Heflin wrote:
>> On the specific kernel that I have I appear to have both IDE and
>> sata_nv drivers, is there a way to force things to use sata_nv/libata
>> rather than the older ide driver for the NVIDIA sata controller?
> 
> Are you saying that drivers/ide is binding to the NVIDIA SATA 
> controller? That seems odd, at least in the Fedora Core 5 kernel 
> configuration, drivers/ide would never try to bind to the SATA 
> controllers for me, only sata_nv would. Maybe you have some 
> configuration option turned on to make drivers/ide grab anything that 
> looks like an IDE controller, which probably shouldn't be turned on.
> 

This kernel is a bit weird, ide is build into the kernel so it gets
first shot at anything it can manage.    I am not sure why the choices
were made to set it up the way it is setup, probably something historical.

I adjusted it so that IDE is a module and setup IDE to load after
sata_nv, so sata_nv is picking up the NVIDIA stuff, and it appears to
be alot better behaved.

                                   Roger

  reply	other threads:[~2006-08-15 23:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.xiop2gho7OdOydmzXzpUsR5ksXM@ifi.uio.no>
2006-08-15 14:29 ` What determines which interrupts are shared under Linux? Robert Hancock
     [not found] ` <fa.1abHK6YDIfV51f77xhbkgnQpLwk@ifi.uio.no>
     [not found]   ` <fa.UkMpPU+vkXMkIeBVGEpBG9C87M4@ifi.uio.no>
     [not found]     ` <fa.9EHh5X478LQIXFY79H/n57rBfRE@ifi.uio.no>
     [not found]       ` <fa.OQ0aZlfKc9NmI+ugRx8PT515Nks@ifi.uio.no>
2006-08-15 23:04         ` Robert Hancock
2006-08-15 23:11           ` Roger Heflin [this message]
2006-08-15 14:17 Roger Heflin
2006-08-15 14:30 ` Sergei Shtylyov
2006-08-15 14:38   ` Roger Heflin
2006-08-15 14:47 ` Len Brown
2006-08-15 15:06 ` Alan Cox
2006-08-15 15:24   ` Roger Heflin
2006-08-15 15:55     ` Alan Cox
2006-08-15 17:47       ` Roger Heflin
2006-08-15 18:13         ` Alan Cox
2006-08-16 22:54         ` Mark Lord
2006-08-17  0:39           ` Alan Cox
2006-08-17 13:18             ` Roger Heflin
2006-08-15 15:19 ` linux-os (Dick Johnson)
2006-08-15 17:31 ` Terence Ripperda
2006-08-15 17:42   ` Sergei Shtylyov
2006-08-15 17:43     ` Terence Ripperda

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=44E25496.20705@atipa.com \
    --to=rheflin@atipa.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hancockr@shaw.ca \
    --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