From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Dave Airlie <airlied@linux.ie>
Cc: 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 17:27:15 -0600 [thread overview]
Message-ID: <200409141727.15643.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0409150008130.23838@skynet>
On Tuesday 14 September 2004 5:12 pm, Dave Airlie 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?
It's been in -mm for about a month so far, and it still
needs some cooking before it's ready for mainline. The
remaining issues are:
- nvidia: Nvidia posted a patch for the open-source part
of their driver, but we'll likely have to keep
the "pci=routeirq" option longer than I originally
hoped.
- swsusp: Some devices like prism54, USB don't
work after suspend/resume. Prototype patch
being tested. I suspect we'll trip over
more issues here, because the resume hooks
are poorly documented and inconsistently
implemented.
- DRI: Sounds like you can do the trivial "enable-only"
change that will make things work.
I'm a little surprised that I've only heard one report about
DRI, actually.
> I'll throw an enable in to the bk tree later on....
Great, thanks!
next prev parent reply other threads:[~2004-09-14 23:28 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 ` Dave Airlie
2004-09-14 14:45 ` Bjorn Helgaas
2004-09-14 23:12 ` Dave Airlie
2004-09-14 23:27 ` Bjorn Helgaas [this message]
2004-09-14 23:41 ` Jon Smirl
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=200409141727.15643.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=airlied@linux.ie \
--cc=akpm@osdl.org \
--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
all inboxes | Powered by JetHome®