From owner-freebsd-x11@FreeBSD.ORG Wed Nov 2 16:31:03 2011 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 52F04106564A for ; Wed, 2 Nov 2011 16:31:03 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 16D228FC15 for ; Wed, 2 Nov 2011 16:31:02 +0000 (UTC) Received: by ggnq2 with SMTP id q2so426038ggn.13 for ; Wed, 02 Nov 2011 09:31:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=1FY8tSbTRHcgDaO6d6vlSk7L2nm63Y1WJZqB/F2UNLI=; b=F32yuv1H7j8yBVDG/oPBvaV9u2tu2QHcnbUszXwhNtNCuvymFqSlB6OQn6GU+sDr9s B6Mh+hgR6yl7gSPlhi1LUy4QoCAfn9/ATi+mqcJ2jkq3sQUiT8sKQyhmYTIGJDveWCEe wQvffpkmLrttngOZ0txnGq0azkj2OnELEhAyY= MIME-Version: 1.0 Received: by 10.50.89.227 with SMTP id br3mr3785514igb.14.1320251462019; Wed, 02 Nov 2011 09:31:02 -0700 (PDT) Received: by 10.231.46.198 with HTTP; Wed, 2 Nov 2011 09:31:01 -0700 (PDT) In-Reply-To: <20111102075720.GG50300@deviant.kiev.zoral.com.ua> References: <20111102075720.GG50300@deviant.kiev.zoral.com.ua> Date: Wed, 2 Nov 2011 09:31:01 -0700 Message-ID: From: Kevin Oberman To: Kostik Belousov Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-x11@freebsd.org Subject: Re: Intel driver patch 11.0 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2011 16:31:03 -0000 On Wed, Nov 2, 2011 at 12:57 AM, Kostik Belousov wrote: > The patch 11.0 contains the merge of the latest Linux changes after the > 3.2 merge window was opened. Mostly, there are fixes for (e)DP, which I > am not convinced are working on FreeBSD at all, and further support for > the not yet released IvyBridge. > > Also, I fixed a FreeBSD-specific regression in GEM which seems to cause > random GPU hangs several people reported to me. > > Still no estimation of the time when the code will be committed in HEAD. > I am sorry, but this is not under my control. Any idea when vty switching might show up? Or is it still too much a glimmer in the distance to guess? vty switching is the main feature that is still missing for people like me who don't use advanced capabilities for gaming or eye candy. And thanks for all of your work on this! -- R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com