From: Jeff Garzik <jgarzik@pobox.com>
To: "Mukker, Atul" <Atulm@lsil.com>
Cc: "'hch@infradead.org'" <hch@infradead.org>,
"'James Bottomley'" <James.Bottomley@SteelEye.com>,
"'marcelo.tosatti@cyclades.com'" <marcelo.tosatti@cyclades.com>,
Matt_Domsch@dell.com,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
linux-scsi@vger.kernel.org
Subject: Re: ANNOUNCE: megaraid driver version 2.10.1
Date: Fri, 30 Jan 2004 10:40:39 -0500 [thread overview]
Message-ID: <20040130154039.GA14003@gtf.org> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E57033BC33D@exa-atlanta.se.lsil.com>
On Fri, Jan 30, 2004 at 10:03:00AM -0500, Mukker, Atul wrote:
> Hello Christoph,
>
> I am in process of testing the next version of the megaraid driver. I faced
> an issue while doing the insmod-rmmod sequence. Your patch for PCI hotplug
> does "pci_disable_device" when the driver is unloaded.
>
> The insmod-rmmod-insmod fails the first time unless you do an explicit
> pci_set_master at driver load time, since pci_enable_device does not seem to
> enable bus mastering, which is disabled by pci_disable_device.
If your driver does DMA, but does not call pci_set_master(), that is a bug.
Jeff
next prev parent reply other threads:[~2004-01-30 15:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-30 15:03 ANNOUNCE: megaraid driver version 2.10.1 Mukker, Atul
2004-01-30 15:40 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-13 21:39 Mukker, Atul
2004-01-14 9:22 ` 'hch@infradead.org'
2004-01-10 13:52 Xose Vazquez Perez
2004-01-09 23:54 Mukker, Atul
2004-01-11 14:06 ` 'hch@infradead.org'
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=20040130154039.GA14003@gtf.org \
--to=jgarzik@pobox.com \
--cc=Atulm@lsil.com \
--cc=James.Bottomley@SteelEye.com \
--cc=Matt_Domsch@dell.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.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.