From owner-freebsd-x11@freebsd.org Sun Apr 24 21:25:41 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 11E1AB1BA76 for ; Sun, 24 Apr 2016 21:25:41 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-oi0-f65.google.com (mail-oi0-f65.google.com [209.85.218.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D5EB017E5 for ; Sun, 24 Apr 2016 21:25:40 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-oi0-f65.google.com with SMTP id f63so20913552oig.0 for ; Sun, 24 Apr 2016 14:25:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:cc; bh=2kD5E5AzXfEQspVRadRZtTsuWJTlOLPfv+OlvdBNLic=; b=mLdhkjVR1hB/0QmkI6B5HeLMyC3WxB4u4kaY6Z6/oPjH0mniB5j54GWyD7j79FH7Kr 4bbG0j6X1s0tRH0Qo8qt8NOhYIVXxemKgIJ8A9aDDh+925UFAOdJiWNsPjGkjJAnbW6S mbEDk5S0MDMtyvkcGnaZgiPilH+JFV9jDob4+RcaSi9AaeUX8KwnnqIPCdbIFPUaXON3 ZRmaPUlax2SD0ohOvLTYkFyOPsW3PRX40mhREcBag1jjjVrnpZ0YLtPKAsX6tmJXGMKx s7SGhCNGhzmuIWAuHYIkZHw3HcKuIwTlCTTJsUcYKp795zxwuU96U4khCUmLNF3VfSai OuLw== X-Gm-Message-State: AOPr4FUOUg80/3qvZj02MxbzSbXbKnWFgu0YRh44NBEhlt7pYZW4fph6zDcE0xtpefAL+A== X-Received: by 10.157.25.166 with SMTP id k35mr12304253otk.100.1461529401144; Sun, 24 Apr 2016 13:23:21 -0700 (PDT) Received: from mail-oi0-f48.google.com (mail-oi0-f48.google.com. [209.85.218.48]) by smtp.gmail.com with ESMTPSA id s127sm5501761oie.4.2016.04.24.13.23.20 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 24 Apr 2016 13:23:20 -0700 (PDT) Received: by mail-oi0-f48.google.com with SMTP id x19so26069788oix.2 for ; Sun, 24 Apr 2016 13:23:20 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.202.169.131 with SMTP id s125mr1859896oie.35.1461529400542; Sun, 24 Apr 2016 13:23:20 -0700 (PDT) Reply-To: cem@FreeBSD.org Received: by 10.157.6.111 with HTTP; Sun, 24 Apr 2016 13:23:20 -0700 (PDT) In-Reply-To: <15449ec286e.11def424858288.297669375175006270@nextbsd.org> References: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> <15449ec286e.11def424858288.297669375175006270@nextbsd.org> Date: Sun, 24 Apr 2016 13:23:20 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Update 1 was Re: clarifying the state of drm-next-3.9 and next steps From: Conrad Meyer To: Matthew Macy Cc: "freebsd-x11@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2016 21:25:41 -0000 On Sun, Apr 24, 2016 at 1:18 PM, Matthew Macy wrote: > X now runs i915kms accelerated on the 3.9 driver update. Currently *only* SNA works. > Known issues: > - UXA will fail with: "(EE) failed to create screen resources(EE)". > If someone has pointer on how to diagnose other than the usual trawling > through Xorg sources let me know. > - The module currently leaks memory on unload. This might not even be a new issue (or: not a major regression). The 3.8 driver leaked during unload when I tried it. Best, Conrad