From owner-freebsd-x11@freebsd.org Mon May 23 22:20:49 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 4187DB47648 for ; Mon, 23 May 2016 22:20:49 +0000 (UTC) (envelope-from alexander.m.mishurov@gmail.com) Received: from mail-lb0-x231.google.com (mail-lb0-x231.google.com [IPv6:2a00:1450:4010:c04::231]) (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 9CB0614ED for ; Mon, 23 May 2016 22:20:48 +0000 (UTC) (envelope-from alexander.m.mishurov@gmail.com) Received: by mail-lb0-x231.google.com with SMTP id k7so39042792lbm.0 for ; Mon, 23 May 2016 15:20:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:subject:to:references:cc:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=YyU18DsW0pNaqnqYkjvFPAGNH7+iItOlNiKgZIxq2DI=; b=NwRiDrkq5CUeED+RlU4KwYRBRI70JBT9mCZQe4J5A9rHXuyNSpIjmAXDCKEQzn1rp3 bzrGUnAcsQJg134ClstmZ/ZlM3xROuuarLUp4x8KvfLiG2MNaaGxc00MlRTV3IBmFkJI VIAJ/6CgDBbpNSpsOr5p3KFps4qPpUU3vRmXXrb5ir2Hqsv3MV/GnhyO9aunnVY+5zkR oYkQ8OAqK/+qYoPAiYUIthjG+u2uzqfWpY99ToyYTKw3fndnPRMAMjOCRdEauWcnkMJ9 JbX7mpLBTW+4MQrlwlAYnzLpucHOHWJmUlBBQb8sTFbIbeiEfSYqACcA0rmLlmJrBEhJ c+6w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:subject:to:references:cc:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=YyU18DsW0pNaqnqYkjvFPAGNH7+iItOlNiKgZIxq2DI=; b=cGigV5WB4FU5HrYfho3dPQuXBKJKd2oAzNL9Hm6uY4TD0gPBtD5FbfEepafPFAfK0i 5drhnZc6GqtlmfmpJG3kf6OTgBJOxBtgDGDcQEKTFrFBnNRk5tGbL46EczlJ1q0nFPwX iy8D0x5uWiwZJyF07Oj3tS0P+QV1+p34bW97aaKMraXOut4GY/JFgOEpLffnAGWVhKl3 gu3gZz3PGILeTWQoIDvq4qWnXn1ADpfOGXziTNtpq8UeIHSmBm9xDYd6UEa+sanheQL3 jexRUaXknHusSsIIE+tdkXm9NFesHR76Ku/v3MG3ZM1o2Joxp6tGMugF5ayvyE6DdJfR FfgQ== X-Gm-Message-State: ALyK8tKh8OLHIQ3N2TiD8dWZVXJiNhPRrSx67FCU/c9FfNm873ZKsqBhyZQ7GvoGzuHTbQ== X-Received: by 10.112.167.225 with SMTP id zr1mr2506063lbb.96.1464042046736; Mon, 23 May 2016 15:20:46 -0700 (PDT) Received: from [192.168.0.98] ([176.194.173.153]) by smtp.gmail.com with ESMTPSA id mq1sm5946207lbb.21.2016.05.23.15.20.45 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 23 May 2016 15:20:46 -0700 (PDT) From: Alexander Mishurov Subject: Re: Update 2 the state of drm-next-4.6 and next steps To: Matthew Macy References: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> <15449ec286e.11def424858288.297669375175006270@nextbsd.org> <1549f266cc5.ea588cba219264.3594536435079440635@nextbsd.org> <20160521231734.GM21899@ivaldir.etoilebsd.net> <57436A8E.4020109@gmail.com> <154df5bc8e2.b7d4a800194520.6901257599921444588@nextbsd.org> Cc: "" Message-ID: <5743824C.6050308@gmail.com> Date: Tue, 24 May 2016 01:21:00 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 MIME-Version: 1.0 In-Reply-To: <154df5bc8e2.b7d4a800194520.6901257599921444588@nextbsd.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2016 22:20:49 -0000 This is the output of a kldloading the latest commit. Nothing changed from user's point of view, just couple of lines from the previous output disappeared. May 24 00:57:31 fbsd kernel: [drm] Initialized drm 1.1.0 20060810 May 24 00:57:31 fbsd kernel: bus_register unimplemented!!! May 24 00:57:31 fbsd kernel: May 24 00:57:31 fbsd kernel: [drm:drm_pci_init] May 24 00:57:31 fbsd kernel: drmn0: on vgapci0 May 24 00:57:31 fbsd kernel: [drm:drm_get_pci_dev] May 24 00:57:31 fbsd kernel: vgapci0: May 24 00:57:31 fbsd kernel: child drmn0 requested pci_enable_io May 24 00:57:31 fbsd kernel: vgapci0: child drmn0 requested pci_enable_io May 24 00:57:31 fbsd kernel: [drm:drm_minor_register] May 24 00:57:31 fbsd kernel: [drm:drm_minor_register] new minor registered 64 May 24 00:57:31 fbsd kernel: [drm:drm_minor_register] May 24 00:57:31 fbsd kernel: [drm:drm_minor_register] new minor registered 128 May 24 00:57:31 fbsd kernel: [drm:drm_minor_register] May 24 00:57:31 fbsd kernel: [drm:drm_minor_register] May 24 00:57:31 fbsd kernel: new minor registered 0 May 24 00:57:31 fbsd kernel: [drm:i915_dump_device_info] i915 device info: gen=7, pciid=0x0f31 rev=0x00 flags=is_mobile,need_gfx_hws,is_valleyview,has_hotplug, On 23/05/2016 23:43, Matthew Macy wrote: > > ---- On Mon, 23 May 2016 13:39:42 -0700 Alexander Mishurov wrote ---- > > I'm experiencing the same issue. The keyboard works only in the terminal > > where a kldload was launched from, if I try to log in to another > > terminal, Alt+F(x), it doesn't respond on a typing. > > > > My hardware is Bay Trail, ValleyView. > > > > Output is: > > May 22 18:05:12 fbsd kernel: [drm] Initialized drm 1.1.0 20060810 > > May 22 18:05:12 fbsd kernel: bus_register unimplemented!!! > > May 22 18:05:12 fbsd kernel: > > May 22 18:05:12 fbsd kernel: [drm:drm_pci_init] > > May 22 18:05:12 fbsd kernel: drmn0: on vgapci0 > > May 22 18:05:12 fbsd kernel: [drm:drm_get_pci_dev] > > May 22 18:05:12 fbsd kernel: simple_pin_fs is dodgy -- see your local > > kernel hacker > > May 22 18:05:12 fbsd kernel: vgapci0: child drmn0 requested pci_enable_io > > May 22 18:05:12 fbsd kernel: vgapci0: child drmn0 requested pci_enable_io > > May 22 18:05:12 fbsd kernel: [drm:drm_minor_register] > > May 22 18:05:12 fbsd kernel: [drm:drm_minor_register] new minor > > registered 64 > > May 22 18:05:12 fbsd kernel: [drm:drm_minor_register] > > May 22 18:05:12 fbsd kernel: [drm:drm_minor_register] new minor > > registered 128 > > May 22 18:05:12 fbsd kernel: [drm:drm_minor_register] > > May 22 18:05:12 fbsd kernel: [drm:drm_minor_register] new minor registered 0 > > May 22 18:05:12 fbsd kernel: __pm_runtime_resume not implemented -- see > > your local kernel hacker > > May 22 18:05:12 fbsd kernel: [drm:i915_dump_device_info] i915 device > > info: gen=7, pciid=0x0f31 rev=0x00 > > flags=is_mobile,need_gfx_hws,is_valleyview,has_hotplug, > > May 22 18:05:24 fbsd kernel: ath0: ath_edma_rxbuf_alloc: > > bf=0xfffffe00010dfbc8, rxbuf alloc failed! error=55 > > May 22 18:05:24 fbsd kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc > > failed: i=0, nbufs=128? > > May 22 18:05:24 fbsd kernel: ath0: ath_edma_rxbuf_alloc: > > bf=0xfffffe00010dfef8, rxbuf alloc failed! error=55 > > May 22 18:05:24 fbsd kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc > > failed: i=0, nbufs=128? > > It's probably not fixed, but please try the latest. Based on what I see there I'll instrument the attach path. > > (ath(9) doesn't look so happy either). > > -M > > > > On 23/05/16 23:28, Lundberg, Johannes wrote: > > >> happily running my broadwell laptop > > > That's interesting. On my Cherry View dev board which is also Broadwell > > > graphics (I think) I get some output from kldload i915kms but then it > > > halts. USB keyboard still works (as in I can press enter and console > > > scrolls up) but no response from OS. > > > > > > I do get some message about bus_register something missing.. > > > > > > Maybe not ready for testing? > > > > > > > > > On Sat, May 21, 2016 at 4:17 PM, Baptiste Daroussin > > > wrote: > > > > > >> On Wed, May 11, 2016 at 02:29:36AM -0700, Matthew Macy wrote: > > >>> > > >>> At least to some degree hw accelerated 3d works on the 4.6 i915 driver > > >> (which in principle supports up through Kaby lake - I don't yet have > > >> anything newer than Haswell). > > >>>https://plus.google.com/114029301710423058970/posts/485LyZegC9B > > >>> > > >>> I anticipate maintaining all the pieces: linuxkpi, drm, i915, amdgpu, > > >> amdkfd as ports for the foreseeable future to make maintenance and > > >> continued development simpler. > > >>> I hope to post a call for testers this weekend or early next week. > > >>> > > >>> Cheers. > > >>> > > >>> -M > > >>> > > >>> > > >>> ---- On Sun, 24 Apr 2016 13:18:14 -0700 Matthew Macy > > >> wrote ---- > > >>> > > > >>> > > > >>> > > > >>> > ---- On Tue, 12 Apr 2016 12:57:34 -0700 Matthew Macy < > > >>mmacy@nextbsd.org> wrote ---- > > >>> > > There seems to be some confusion about the state of drm-next-3.9. > > >> All the work is currently going on in jmd's fork of freebsd-base-graphics: > > >>> > > > > >>> > >https://github.com/iotamudelta/freebsd-base-graphics > > >>> > > > > >>> > > The emphasis has been on bringing i915 and the drm code in > > >> dev/drm2 closer to upstream as opposed to a simple driver refresh. I'm > > >> currently implementing missing linuxkpi bits and hope to actually be > > >> testing in the next week or so. > > >>> > > > > >>> > > As of this moment there is nothing available for general > > >> consumption. I very much hope to have this phase done before code freeze. I > > >> will update the list as soon as there is anything to test. Until then, hold > > >> your horses. > > >>> > > > > >>> > > > >>> > 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. > > >>> > > > >>> > > > >>> > My general feeling is that unless you have one of the half-dozen > > >> Haswell PCIIDS that aren't support by 3.8 it probably isn't worth testing > > >> yet. I'm only sending this out to let users track its progress. > > >>> > > > >>> > > > >>> > Cheers. > > >>> > -M > > >>> > > >> as a follow-up I want to share that I cherry-picked the code from the > > >> drm-next-4.6 branch on the current source tree and I am now happily > > >> running my > > >> broadwell laptop with the i915 driver (lenovo x250) so far no problem for > > >> normal > > >> usage. I have a few glitches with xrandr but nothing that makes it > > >> unusable. > > >> > > >> I will test with the next version of xorg server and latest xorg intel > > >> driver to > > >> see if that fixes the glitches. > > >> > > >> Thnak you all for you work! > > >> > > >> Bapt > > >> > > > > _______________________________________________ > >freebsd-x11@freebsd.org mailing list > >https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > > To unsubscribe, send any mail to"freebsd-x11-unsubscribe@freebsd.org" > > >