From owner-freebsd-current@freebsd.org Fri May 18 20:24:04 2018 Return-Path: Delivered-To: freebsd-current@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 5512BEDAB0A for ; Fri, 18 May 2018 20:24:04 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (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 D47D868425 for ; Fri, 18 May 2018 20:24:03 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x236.google.com with SMTP id z4-v6so7657689iof.5 for ; Fri, 18 May 2018 13:24:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=sSaeiabjN7z3rHXnVuX9Qhdth3qSvFymrDa5ZSJLZJw=; b=Upb2ltkdp9PzVHN9MhRDdot8fy1I5o19hWJCdPyHo006lrG2vGR348yMaD/s1Hn9/4 W4yM+jqMlH96B9hnEmxuSOVxOSSoXtfZycq2TxI8755prhvPTjb9O1PqFAxgkYMGMtXn 2AMXFal0tTnlS47pGbqOfqPGNAAfvJ9l742ZjfYdSiX/tZRxRdgEUY2bxMJFTM+BdGKS Do713GEw3m1K5Xwq5b8lDbStu0N9PaIZOan685SVs2RZWJ8o2llmjTK7T3xcjDUYcTeG G8LK4FSEJ/V7W+eAOJ34nb898za3XsvUFjghvmHi9wQmO08z1wy++JC8QfptOPeCUlhc H+XQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=sSaeiabjN7z3rHXnVuX9Qhdth3qSvFymrDa5ZSJLZJw=; b=jAXK6NDtEN5U6BvJcvzGuRAU4+Xi/UA2j5WOBQrsFOsP/lLo8zShUocHrarx+oF3cI DWjbeKnFtAuWw3YWOU7irh51WNSWdY3GYR6FIDZQk11smV0Y3UBJ+vnX5puTK2z06l0O qDSzNM2lytpbdq2ddNr9z2eIVBgB3tUUvF/cFUxtOdy8Tv9V2uAwdBzoXdlRbAXnGhKV r9j3aYvHpiD8N74Zc725SqSbcymZe4e3TAZOE2jiagLrgfVblZA500zlWOrXJuQ5Diol fM1XJJgkJImIuZiTzOxwXIOR3Pk4DEvUEJ1flmhAvkqg7nOqsL6+iq/lzoIHWlcQpRSR PF7A== X-Gm-Message-State: ALKqPwf5xx4t00k+GotBt8zCSEQ7NWQ33VrnQoswXrHSX5iwHu9ufBKo SAyecnBCpZslDNbaRhgVVUS6QHc9dQRkNJdCCDilag== X-Google-Smtp-Source: AB8JxZoKWe+jDXsBOObgtmLn7IWddyZDtsA8NfUDhsYe2xUbUoggRH8SkhiRK4Y2o7yiPXHufPuoONZv7UPeBsSp7VE= X-Received: by 2002:a6b:be01:: with SMTP id o1-v6mr11522778iof.299.1526675043200; Fri, 18 May 2018 13:24:03 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:a649:0:0:0:0:0 with HTTP; Fri, 18 May 2018 13:24:02 -0700 (PDT) X-Originating-IP: [50.253.99.174] In-Reply-To: References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> From: Warner Losh Date: Fri, 18 May 2018 14:24:02 -0600 X-Google-Sender-Auth: WLsB_3DzB5s1UEyL9Sq3dOWp-m0 Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Daniel Eischen Cc: Steve Kargl , Andreas Nilsson , FreeBSD X11 mailing list , Current FreeBSD Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 May 2018 20:24:04 -0000 On Fri, May 18, 2018 at 2:19 PM, Daniel Eischen wrote: > On Fri, 18 May 2018, Warner Losh wrote: > > On Fri, May 18, 2018 at 1:30 PM, Steve Kargl < >> sgk@troutmask.apl.washington.edu> wrote: >> >>> >>> Check the Makefiles >>> >>> % more /usr/ports/graphics/drm-next-kmod/Makefile >>> >>> ONLY_FOR_ARCHS= amd64 >>> ONLY_FOR_ARCHS_REASON= the new KMS components are only supported on >>> amd64 >>> >>> Not to ia32 friendly. >>> >>> >> So do people use i386 for desktop? And need the latest KMS stuff? >> > > I can easily imagine an embedded x86 kiosk type appliance. Does > basic xorg stuff work without drm? They'd be running current on such boxes? I'm asking if we have any known users. The crux of the problem is that it's hard to get any graphics support from Intel. What little support we get from them is amd64 only. And what little resources we have do support graphics is 64-bit only. There's nobody doing the work for i386, and we're not able to snag it from upstream either. So it boils down to the question of allowing old, obsolete hardware, which nobody's sure works anyway, to get in the way of moving forward to more modern hardware? I'm trying to find value from supporting i386, and a community willing to do that work and I'm not seeing much of either. Warner