From: William Park <opengeometry@yahoo.ca>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Lee Revell <rlrevell@joe-job.com>,
linux-kernel@vger.kernel.org
Subject: Re: DMA in PCI chipset -- module vs. compiled-in
Date: Tue, 7 Feb 2006 23:37:28 -0500 [thread overview]
Message-ID: <20060208043728.GA3357@node1.opengeometry.net> (raw)
In-Reply-To: <58cb370e0602070314l35b7c88blbe53844939c86f66@mail.gmail.com>
On Tue, Feb 07, 2006 at 12:14:09PM +0100, Bartlomiej Zolnierkiewicz wrote:
> On 2/7/06, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > On Maw, 2006-02-07 at 09:14 +0100, Bartlomiej Zolnierkiewicz wrote:
> > > * chipset specific driver
> > >
> > > The most common mistake is to built-in ide-generic driver
> > > and compile chipset specific driver as module...
> >
> > Oh that no longer works. That worked in 2.4, as it would take over the
> > chipset. Didn't work if it was in use at the time but did work correctly
> > if idle.
>
> I'm talking about _driver_ here and it works just fine.
>
> If you are talking about "taking over" feature, you are right.
> It was racy and indeed "worked" depending on timing.
Interesting. I'll move the "generic" as module, and see how it goes.
--
William Park <opengeometry@yahoo.ca>, Toronto, Canada
ThinFlash: Linux thin-client on USB key (flash) drive
http://home.eol.ca/~parkw/thinflash.html
BashDiff: Super Bash shell
http://freshmeat.net/projects/bashdiff/
next prev parent reply other threads:[~2006-02-08 4:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 3:43 DMA in PCI chipset -- module vs. compiled-in 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
2006-02-07 11:07 ` Alan Cox
2006-02-07 11:14 ` Bartlomiej Zolnierkiewicz
2006-02-08 4:37 ` William Park [this message]
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=20060208043728.GA3357@node1.opengeometry.net \
--to=opengeometry@yahoo.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.