From: Jon Smirl <jonsmirl@gmail.com>
To: Dave Airlie <airlied@linux.ie>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
dri-devel@lists.sourceforge.net, Andrew Morton <akpm@osdl.org>,
Evan Paul Fletcher <evanpaul@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] DRM: add missing pci_enable_device()
Date: Tue, 14 Sep 2004 19:41:28 -0400 [thread overview]
Message-ID: <9e47339104091416416b9ae310@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0409150008130.23838@skynet>
It appears that the kernel bk tree is lagging behind the DRM CVS
source. Allow more DRM updates into the kernel and these things will
be fixed. If you want more up to date drivers get them directly from
DRM CVS.
pci_enable/disable_device are correct in the dyn-minor patch. They
also appear to correct in the currently checked in DRM cvs. If fbdev
is loaded DRM does not do pci_enable/disable_device. It is assumed
that these calls are handled by the fbdev device.
You must follow the order rules if using them together.
modprobe fbdev
modprobe DRM
rmmod DRM
rmmod fbdev
You cannot remove these modules out of order or things will break.
On Wed, 15 Sep 2004 00:12:01 +0100 (IST), Dave Airlie <airlied@linux.ie> wrote:
> >
> > OK, I'll assume you understand the issue and will resolve it. In the
> > meantime, users of DRM will have to supply "pci=routeirq".
> >
>
> is this -mm only or is it mainline kernel stuff now?
>
> I'll throw an enable in to the bk tree later on....
>
> Dave.
>
> --
> David Airlie, Software Engineer
> http://www.skynet.ie/~airlied / airlied at skynet.ie
> pam_smb / Linux DECstation / Linux VAX / ILUG person
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
> Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
> Camcorder. More prizes in the weekly Lunch Hour Challenge.
> Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m
>
>
> --
> _______________________________________________
> Dri-devel mailing list
> Dri-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dri-devel
>
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2004-09-14 23:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200409131651.05059.bjorn.helgaas@hp.com>
2004-09-13 23:28 ` [PATCH] DRM: add missing pci_enable_device() Dave Airlie
2004-09-14 14:45 ` Bjorn Helgaas
2004-09-14 23:12 ` Dave Airlie
2004-09-14 23:27 ` Bjorn Helgaas
2004-09-14 23:41 ` Jon Smirl [this message]
2004-09-15 12:22 ` Alan Cox
2004-09-15 15:35 ` Jon Smirl
2004-09-15 17:07 ` Alan Cox
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=9e47339104091416416b9ae310@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=airlied@linux.ie \
--cc=akpm@osdl.org \
--cc=bjorn.helgaas@hp.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=evanpaul@gmail.com \
--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