From owner-freebsd-arm@freebsd.org Wed Apr 3 13:38:36 2019 Return-Path: Delivered-To: freebsd-arm@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 59897156E43A for ; Wed, 3 Apr 2019 13:38:36 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-it1-f181.google.com (mail-it1-f181.google.com [209.85.166.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8F266817CC for ; Wed, 3 Apr 2019 13:38:35 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-it1-f181.google.com with SMTP id x132so9052321itf.2 for ; Wed, 03 Apr 2019 06:38:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=4pAYXV6a1+GdjNDtrGAyVnyAWx6X8aqjQ4ja0p1SGTA=; b=MkqVoXldE93dOShfeIHJSopkFynyixnvMp+X41HJfoSQfD0n/H+Bu1XguMHW2kAGO6 PifyQfl0iAN9wPZt3HPNXe1+rHibju+D5ZE8xma/HZBuM0nb0aAJC0FmiNHSyKuVN2c4 tfFWc1oVHm4ocnSB42wogsRv+gJyb+E/FGVYI4pRmy3BTqJsn/0dsX53Qc06Gw0lCQ5n gFfDLZJs3H8/YQUtPmU15X2Q/zfkiS+WtEp88WE3Bku/kOc4HCo22MuAvnMxMtikWsiN YqhBMo2YFbW2gURgE5+fjZYqmSa5HKUzCv2qvb/s5dEhQdnJCeVOxU3ysNxQpptJiw6d CRTw== X-Gm-Message-State: APjAAAWnv7zL7dAJjplv1Tw0gnCSmqUOngYIV9LCvTMBGZNUcSDkHfLH yDW8knDmKCWam2d/DCviPmmQFFSGrNbS25tmeLs6Lt+d X-Google-Smtp-Source: APXvYqxHnlpRhQzq7bK2YVg16JF73OCRrFU3tfYT0zi0tI0uret7wrDNjGzi1YHfAz7s33B3kLUdvJRJ9ipb9GOp/OI= X-Received: by 2002:a02:a399:: with SMTP id y25mr249457jak.58.1554298708980; Wed, 03 Apr 2019 06:38:28 -0700 (PDT) MIME-Version: 1.0 References: <20190218022911.72261m7v5l6g1i7b@webmail.omc.net> In-Reply-To: <20190218022911.72261m7v5l6g1i7b@webmail.omc.net> From: Ed Maste Date: Wed, 3 Apr 2019 09:55:42 -0400 Message-ID: Subject: Re: Restore broken ThunderX support in 12 by MFCing r343764? To: kraileth@elderlinux.org Cc: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 8F266817CC X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of carpeddiem@gmail.com designates 209.85.166.181 as permitted sender) smtp.mailfrom=carpeddiem@gmail.com X-Spamd-Result: default: False [-4.90 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; IP_SCORE(-2.99)[ip: (-8.82), ipnet: 209.85.128.0/17(-3.88), asn: 15169(-2.17), country: US(-0.06)]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[181.166.85.209.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.90)[-0.900,0]; RCVD_TLS_LAST(0.00)[]; FORGED_SENDER(0.30)[emaste@freebsd.org,carpeddiem@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[181.166.85.209.rep.mailspike.net : 127.0.0.17]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[emaste@freebsd.org,carpeddiem@gmail.com]; SUBJECT_ENDS_QUESTION(1.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Apr 2019 13:38:36 -0000 On Sun, 17 Feb 2019 at 20:29, wrote: > > Not being a developer though, I cannot judge if [r343764] cannot be MFC'd > into 12-STABLE due to making invasive changes or if it simply never > was because it was thought to be an improvement for 13 only and not an > actually pretty vital fix for 12. I suspect jchandra@ just didn't realize it's needed also on ThunderX, and I did not encounter any trouble with the ThunderX systems I have. It could just be that our (older) ThunderX reference firmware has fewer regions in its ACPI info and so works fine without r343764. Anyhow I've now merged the change to stable/12. With respect to vt_efifb the tunable is a simple workaround, but we really need this to work out-of-the-box. Do you have any further details on the failure when vt_efifb is enabled? Also, if you're aware of any other ThunderX issues please let me know.