From owner-freebsd-x11@freebsd.org Mon Jan 11 08:34:08 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 E9C8CA6C03D for ; Mon, 11 Jan 2016 08:34:08 +0000 (UTC) (envelope-from n.pajkovsky@gmail.com) Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (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 87AED1ADA for ; Mon, 11 Jan 2016 08:34:08 +0000 (UTC) (envelope-from n.pajkovsky@gmail.com) Received: by mail-wm0-x234.google.com with SMTP id f206so202902749wmf.0 for ; Mon, 11 Jan 2016 00:34:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type:content-transfer-encoding; bh=fzWBComFywIeW4YRUshv0av9w6mycJMVlT1W78TZhaY=; b=OAeRr03jY3YZonDB/DNmET8ZUhaA3CVBXTH70xS0Sq5JGRY1uDbrRUqIxY0utJGiDg R8u4FdtTs7g7h53Vxg25fw1y3TG4dDJAZX99T93lTJTpuhlswel4DVvCJbCUnPF1K7av 6RCDlqd8XvKqFb/eYxpFQUKB5fgfp26SQvw7EmAQ5SVmjGq66jElXExSFq6bVVCA41+E h0odlYo4Ckax0ZBWCZ+w31/a0uX8z+wiGqhoxc2E/tt0UdpSkUVxQnhwtG6gmUmOsHKP art7RutYSYFz7j1r8mXmsL1ifKzFSGo5VwhjkEC7OaRQ+Q3la88jdhpSfa33xYw/4yik 2Y9A== X-Received: by 10.194.134.134 with SMTP id pk6mr16900254wjb.176.1452501246102; Mon, 11 Jan 2016 00:34:06 -0800 (PST) Received: from localhost (gw-brno.gooddata.com. [194.213.40.134]) by smtp.gmail.com with ESMTPSA id xx3sm59717331wjc.32.2016.01.11.00.34.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 11 Jan 2016 00:34:05 -0800 (PST) From: Nikola Pajkovsky To: =?utf-8?Q?Jean-S=C3=A9bastien_P=C3=A9dron?= Cc: freebsd-x11@freebsd.org Subject: Re: Contributing to the kernel video drivers References: <5681731A.5090909@FreeBSD.org> <87egdv3ga7.fsf@gooddata.com> <56929FB6.5090606@dumbbell.fr> Date: Mon, 11 Jan 2016 09:34:04 +0100 In-Reply-To: <56929FB6.5090606@dumbbell.fr> (=?utf-8?Q?=22Jean-S=C3=A9bast?= =?utf-8?Q?ien_P=C3=A9dron=22's?= message of "Sun, 10 Jan 2016 19:15:18 +0100") Message-ID: <87r3hocy6b.fsf@gooddata.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.20 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, 11 Jan 2016 08:34:09 -0000 Jean-S=C3=A9bastien P=C3=A9dron writes: > On 05/01/2016 21:47, Nikola Pajkovsky wrote: >> From my point of view, moving kernel by kernel does not make sense, >> because there are too much of them. However, moving long term kernel >> by long term kernel, makes more sense to me. I can imagine, that we can >> do that file-by-file basic until last lt-kernel. > > Hmm, I didn't thought about considering longterm kernels as milestones, > that's interesting. The next longterm kernel (compared to where we are > now) is 3.10.x, the latest is 4.1.x. It feel it would still be longer > between each of our "releases" compared to one kernel at a time (ie. 3.8 > -> 3.9 -> 3.10) but with the same risks as jumping to the latest kernel. > > Furthermore, if we take eg. 3.10.94, it would include many patches > already included in later versions. 3.10.94 is probably more stable than > maybe 3.11, but it looks like we may duplicate work. Quite frankly, I don't want to jump directly to 3.10.94, but rather 3.10.0 before code freeze. After that, someone could sync to longterm 3.10.94 in stable branch, while others backporting in master branch to another milestone. Can we update during 11.x releases whole graphic stack or at least kernel part (drm + drivers)? --=20 Nikola