From: Alan Hourihane <alanh@fairlite.demon.co.uk>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Jakob Bornecrantz <wallbraker@gmail.com>,
dri-devel@lists.sourceforge.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: DRM modesetting & sysfs
Date: Wed, 09 Apr 2008 18:23:46 +0100 [thread overview]
Message-ID: <1207761826.14588.390.camel@localhost> (raw)
In-Reply-To: <200804090934.37219.jbarnes@virtuousgeek.org>
On Wed, 2008-04-09 at 09:34 -0700, Jesse Barnes wrote:
> On Wednesday, April 09, 2008 9:15 am Alan Hourihane wrote:
> > On Wed, 2008-04-09 at 08:17 -0700, Jesse Barnes wrote:
> > > On Wednesday, April 09, 2008 1:57 am Jakob Bornecrantz wrote:
> > > > I was going to suggest that you plug it into the hotplug_stage_two
> > > > function but it looks like you have already done that. Things might be
> > > > routed differently now then since the last time I looked at the code,
> > > > are you sure that stage_two is being run?
> > >
> > > I'll have to check, I'm not sure I'm even getting interrupts...
> >
> > Jesse,
> >
> > Is this i915 or i945/i965 you are testing on ??
>
> I've been testing on my i915 based laptop, haven't tried my other systems
> yet...
With VGA (i.e. ADPA) output ?
If so, that's the problem. From what I can tell of i915 docs, they only
support hotplug for SDVO devices only, so that's how it's coded up at
the moment. For i945/i965 it can go the whole hog.
Alan.
next prev parent reply other threads:[~2008-04-09 17:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 20:17 DRM modesetting & sysfs Jesse Barnes
2008-04-09 8:57 ` Jakob Bornecrantz
2008-04-09 15:17 ` Jesse Barnes
2008-04-09 16:15 ` Alan Hourihane
2008-04-09 16:34 ` Jesse Barnes
2008-04-09 17:23 ` Alan Hourihane [this message]
2008-04-09 17:39 ` Jesse Barnes
2008-04-09 18:12 ` Jesse Barnes
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=1207761826.14588.390.camel@localhost \
--to=alanh@fairlite.demon.co.uk \
--cc=dri-devel@lists.sourceforge.net \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wallbraker@gmail.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.