From: jmerkey <jmerkey@utah-nac.org>
To: Dave Airlie <airlied@gmail.com>
Cc: Nix <nix@esperi.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: Why no XML in the Kernel?
Date: Wed, 05 Oct 2005 16:22:48 -0600 [thread overview]
Message-ID: <43445238.5030900@utah-nac.org> (raw)
In-Reply-To: <21d7e9970510051636g29012748o77124c1c1abc9259@mail.gmail.com>
Dave Airlie wrote:
>>Ah. So, er, the DRM<-> userspace protocol is stable, then?
>>
>>Looks like I was working on bad assumptions (assuming the DRM and X were
>>tied). I'm not sure where those assumptions came from. Possibly just
>>that they shared a CVS repo, although I'd hope I'd had more evidence
>>than that. I realy can't recall.
>>
>>
>
>In theory yes, on occasion I do get bugs that break XFree86 4.3, but
>these are bugs as opposed to design decisions, upgrading the kernel
>should never require upgrading to a new version of X or anything like
>that, however upgrading X can sometimes require a newer kernel in
>order to take advantage of newer drm features.. but X should always
>work with the older drms...
>
>Dave.
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
>
How about putting the ability to disable graphics mode in the kernel and
moving this capability from X, and saving the video state. Would make
kernel debuggers work a hell of a lot better when the damn thing crashes
in X in the kernel. At least then the screen won;t be locked up (of
course you can type "reboot " from memory while the system is still hung
in X).
Jeff
next prev parent reply other threads:[~2005-10-05 23:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-02 9:41 Ahmad Reza Cheraghi
2005-10-02 9:50 ` Nick Piggin
2005-10-02 11:02 ` James Courtier-Dutton
2005-10-02 10:37 ` Nick Piggin
2005-10-02 11:57 ` Bas Westerbaan
2005-10-02 11:09 ` James Bruce
2005-10-02 13:47 ` Willy Tarreau
2005-10-03 19:21 ` Bill Davidsen
2005-10-02 18:53 ` Jon Masters
2005-10-03 15:08 ` Nix
2005-10-03 15:35 ` Al Viro
2005-10-03 19:47 ` Nix
2005-10-03 19:56 ` linux-os (Dick Johnson)
2005-10-05 21:11 ` Dave Airlie
2005-10-05 21:31 ` Nix
2005-10-05 22:57 ` Dave Airlie
2005-10-05 23:07 ` Nix
2005-10-05 23:36 ` Dave Airlie
2005-10-05 22:22 ` jmerkey [this message]
2005-10-05 23:46 ` Dave Airlie
2005-10-07 22:14 ` Matan Ziv-Av
2005-10-02 21:55 ` Martin J. Bligh
2005-10-03 4:45 ` Nick Piggin
2005-10-08 1:34 Luke Kenneth Casson Leighton
2005-10-09 15:38 ` Horst von Brand
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=43445238.5030900@utah-nac.org \
--to=jmerkey@utah-nac.org \
--cc=airlied@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nix@esperi.org.uk \
/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
Powered by JetHome