From owner-freebsd-x11@freebsd.org Wed May 30 13:47:33 2018 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6D689EFDEC7 for ; Wed, 30 May 2018 13:47:33 +0000 (UTC) (envelope-from kevin.bowling@kev009.com) Received: from mail-it0-x244.google.com (mail-it0-x244.google.com [IPv6:2607:f8b0:4001:c0b::244]) (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 F19FA83EEF for ; Wed, 30 May 2018 13:47:32 +0000 (UTC) (envelope-from kevin.bowling@kev009.com) Received: by mail-it0-x244.google.com with SMTP id d10-v6so23179282itj.1 for ; Wed, 30 May 2018 06:47:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kev009.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=IURdYtqG73CSlUEhcocpRJMDUJZbx/XPoGbHhwmuZ7U=; b=Z1S/m5maiy2qT5Xt3t6zZuLCmSbqeC6USaxBsu1lTIU5p96qhtuv8HHPxbRcWqn9jL dDyHaddX0EOkyTyDBoMAfmKYVIwpYfPFC5x4vebN1/FrTu1xJn2vsxVXXrVyzq1FbDLK J/J1GaHFhYt2mHjAGcwVq7lEi91P0K8MSE3EI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=IURdYtqG73CSlUEhcocpRJMDUJZbx/XPoGbHhwmuZ7U=; b=Lmv1gveLfJQbUcbqhskLBQP3Ic4gb9mbS3ge2zA0HE14DvXNNgEnaI2RWRrHDkdAlA WCx6rR86pBXPLY4Vri9baCMpLzIljmybfs7PQklQssHvGC8c3TquW2ud0yFKeeQ7+xWx Xpq2M2+K7y/tyHD1hlRsskE4j0QDRzP4OGAiSo/iwz9gPlFHPBHQryhr4v+ZfRtv7myh lPKbzZdhqmbAZz0bHU94zk3T/Aso+xHCOCktfqWB9WyHmDec3+j8S8xt9uYheoSZ5ftn y42P7i3MWRMixnDQK4X7yMQ8+PIbfZQLrG9z3n1E4fhPG0qTJXn8wfDGJxgtzezT3+5F 82bQ== X-Gm-Message-State: ALKqPwcoTLWCgy8ZjksU4a8VWdmVKxrQsw5QLOUjwSB0fFq1oop+h5no QuiC8i4g2IGpdwQ8BOWHo5Bur43DrxKIQDxzAG/Ddg== X-Google-Smtp-Source: ADUXVKKSqpi2CT/kKaM+5TKDmtcgPi6mk+nr5jS6NfhEW+/wJt41+q7ogoHSC7i+QpdZXVxw3luZFAvkM8McXV/XzmA= X-Received: by 2002:a24:1f4a:: with SMTP id d71-v6mr1715913itd.53.1527688051699; Wed, 30 May 2018 06:47:31 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a02:a1cd:0:0:0:0:0 with HTTP; Wed, 30 May 2018 06:47:31 -0700 (PDT) In-Reply-To: <5b0e8026.1c69fb81.100eb.ce66SMTPIN_ADDED_MISSING@mx.google.com> References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <50b21ccf-f89d-cfd0-fb23-39ba80732143@freebsd.org> <5b0e8026.1c69fb81.100eb.ce66SMTPIN_ADDED_MISSING@mx.google.com> From: Kevin Bowling Date: Wed, 30 May 2018 06:47:31 -0700 Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Thomas Mueller Cc: freebsd-current@freebsd.org, x11-list freebsd Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.26 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, 30 May 2018 13:47:33 -0000 32b compat is quite different than i386 arch. It makes sense to maintain 32b compat for quite a while. On Wed, May 30, 2018 at 3:33 AM, Thomas Mueller wrote: >> Wow, this blew up quite a lot bigger than I anticipated. I'll try to >> summarize the discussion a bit below and then suggest a way forward. > >> The primary reasons we want to do this is because there are conflicts between >> the new drm drivers in ports, and the drm drivers in base, since they control >> the same hardware. It is hard to make conflicting drivers to auto load in a >> consistent way. In order to improve the desktop experience I'd like to see >> that graphics drivers are loaded on system boot. There is also a push from >> upstream to have the xf86-video* drivers stop loading driver kernel modules. >> It is also easier to keep a port updated than keeping the base system updated, >> and updates can propagate to multiple FreeBSD versions at once. This will >> also ensure that all ports use the same firmware blobs. > >> So, to the summary. A lot of people are using i386, and as such still need >> the old drm drivers. There were also some reports about issues with the >> drm-next/stable drivers, which needs investigating. Power is another >> architecture that also is not supported by drm-next/stable, although we hope >> to extend support to powerpc in the future. There was a lot of discussion >> regarding making it into a port, or only excluding the driver on amd64, and >> similar suggestions. > >> To move forward, we'll do the following: Note that this is for current only. >> We take the drm and drm2 drivers and make a port for it, maintained by the >> graphics team (x11@). After a transition period, then the drivers are removed >> from base. At the same time, pkg-messages are added to relevant places to >> point people to the various available drm drivers. > >> Regards > >> Niclas Zeising >> FreeBSD graphics/x11 team > > One reason I can think of to maintain i386 compatibility is to be able to run wine and possibly other software that requires i386 compatibility. > > That said, I currently have no active FreeBSD i386 installation, and probably won't get around to it anytime soon. > > I believe Linux can run wine on an amd64 multilib installation, but FreeBSD is not up to that yet. > > For the above purpose, keeping drm and drm2 as a port might be good enough, as opposed to being part of base. > > i386 is not dead. While some Linux distros (such as Arch) and DragonFlyBSD have quit i386 support, Haiku maintains 32-bit support to be able to run old BeOS software as well as newer things. > > Tom > > _______________________________________________ > 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"