All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 16336] i915 crashes when loading X.org server with vesa driver
Date: Fri, 23 Jul 2010 19:38:30 GMT	[thread overview]
Message-ID: <201007231938.o6NJcURf021861@demeter.kernel.org> (raw)
In-Reply-To: <bug-16336-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=16336


Jesse Barnes <jbarnes@virtuousgeek.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WILL_NOT_FIX




--- Comment #3 from Jesse Barnes <jbarnes@virtuousgeek.org>  2010-07-23 19:38:26 ---
The kernel has no way of doing this right now.  A suitably privileged X server
can open /dev/mem or any of the sysfs resource files and start poking
regsiters.

The reason NV and VESA work together is that the NV driver isn't a kernel mode
driver, when you switch between servers in that config the whole hardware state
is saved and restored, whereas in the i915 case, the i915 driver expects to be
in sole control of the hw once it loads.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.

------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
--

      parent reply	other threads:[~2010-07-23 19:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-16336-2300@https.bugzilla.kernel.org/>
2010-07-04 12:33 ` [Bug 16336] i915 crashes when loading X.org server with vesa driver bugzilla-daemon
2010-07-04 14:33 ` bugzilla-daemon
2010-07-23 19:38 ` bugzilla-daemon [this message]

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=201007231938.o6NJcURf021861@demeter.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.sourceforge.net \
    /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.