mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	William Park <opengeometry@yahoo.ca>,
	linux-kernel@vger.kernel.org
Subject: Re: DMA in PCI chipset -- module vs. compiled-in
Date: Tue, 7 Feb 2006 09:14:27 +0100	[thread overview]
Message-ID: <58cb370e0602070014p3d21c8a4u1ca3c5951892cf52@mail.gmail.com> (raw)
In-Reply-To: <1139257535.2791.298.camel@mindpipe>

On 2/6/06, Lee Revell <rlrevell@joe-job.com> wrote:
> On Mon, 2006-02-06 at 19:49 +0000, Alan Cox wrote:
> > On Sul, 2006-02-05 at 23:32 -0500, Lee Revell wrote:
> > > Generic and chipset specific support are not complementary, they are
> > > mutually exclusive.  Having generic PCI IDE support enabled will prevent
> > > the chipset specific support from working properly.
> >
> > Untrue.
> >
> > The PCI generic driver by default grabs only hardware with PCI IDS it
> > knows can be driven generically. That list purposefully has no overlaps
> > with chipset drivers.
>
> OK.  But wasn't this a problem in previous kernels?

It wasn't.  The issue is more complicated, you can have
three host drivers driving the same hardware:

* ide-generic driver
  - ISA like support
  - also works for PCI in legacy mode

* IDE PCI generic (the one Alan refers to)
  - generic IDE PCI support
  - by default doesn't grab IDs for which we have other drivers
    (can be forced by using kernel parameter)

* chipset specific driver

The most common mistake is to built-in ide-generic driver
and compile chipset specific driver as module...

To William:
CONFIG_IDE_GENERIC=n is a likely solution for your problem.

Bartlomiej

  reply	other threads:[~2006-02-07  8:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-06  3:43 William Park
2006-02-06  4:32 ` Lee Revell
2006-02-06 19:31   ` Ingo Oeser
2006-02-06 20:26     ` Lee Revell
2006-02-06 19:49   ` Alan Cox
2006-02-06 20:25     ` Lee Revell
2006-02-07  8:14       ` Bartlomiej Zolnierkiewicz [this message]
2006-02-07 11:07         ` Alan Cox
2006-02-07 11:14           ` Bartlomiej Zolnierkiewicz
2006-02-08  4:37             ` William Park
2006-02-07  2:04     ` William Park

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=58cb370e0602070014p3d21c8a4u1ca3c5951892cf52@mail.gmail.com \
    --to=bzolnier@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=opengeometry@yahoo.ca \
    --cc=rlrevell@joe-job.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

all inboxes | Powered by JetHome®