Results 1 to 6 of 6

Thread: X Server 1.8 Snapshot 2 Released

  1. #1
    Join Date
    Jan 2007
    Posts
    15,130

    Default X Server 1.8 Snapshot 2 Released

    Phoronix: X Server 1.8 Snapshot 2 Released

    With there being just more than three months left until the planned release of X Server 1.8, Keith Packard has just issued the second snapshot for those interested in trying out this developmental X.Org server. The first X Server 1.8 snapshot came two months ago, but this second snapshot is arriving later than expected after having to deal with some bugs. What is important to note with this second snapshot is that it breaks the X Server ABI for input, video, and extension interfaces...

    http://www.phoronix.com/vr.php?view=NzgyNw

  2. #2
    Join Date
    Dec 2008
    Location
    Poland
    Posts
    119

    Smile

    if based upon AMD's past actions, it will be some months before the Catalyst Linux driver delivers on X Server 1.8 support.
    How brutally true and funny in one

  3. #3
    Join Date
    Oct 2008
    Posts
    3,174

    Default

    Heck, it could be next september before we get AMD support, since Ubuntu 10.04 isn't using it.

  4. #4
    Join Date
    May 2008
    Posts
    598

    Default

    What is important to note with this second snapshot is that it breaks the X Server ABI for input, video, and extension interfaces.
    Sounds very much like Keith is dropping /dev/mem

    He have been wanting to do that for a loooong time.

  5. #5
    Join Date
    Aug 2008
    Posts
    233

    Default

    Quote Originally Posted by Louise View Post
    Sounds very much like Keith is dropping /dev/mem

    He have been wanting to do that for a loooong time.
    Why? Is /dev/mem a bad thing?

  6. #6
    Join Date
    Nov 2008
    Posts
    776

    Default

    yes. /dev/mem gives an application direct access to the physical address space, totally bypassing memory protection mechanisms. This has lead to a couple of security holes in the past. It'd be best to disable /dev/mem once and for all, but that cannot be done as long as X depends on it. I don't think it's needed any more when KMS is used.

    It doesn't look like the ABI changes are actually related to /dev/mem, though. The announcement doesn't mention anything about /dev/mem and the two ABI changes look unrelated. /dev/mem was only used to access the address space occupied by the gfx hardware anyway, that shouldn't cause ABI changes in the input modules.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •