From owner-freebsd-arm@freebsd.org Thu Jan 3 20:52:00 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 591291436DB3 for ; Thu, 3 Jan 2019 20:52:00 +0000 (UTC) (envelope-from c.jayachandran@gmail.com) Received: from mail-io1-f51.google.com (mail-io1-f51.google.com [209.85.166.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 82DCC8F309; Thu, 3 Jan 2019 20:51:59 +0000 (UTC) (envelope-from c.jayachandran@gmail.com) Received: by mail-io1-f51.google.com with SMTP id m19so28040736ioh.3; Thu, 03 Jan 2019 12:51:59 -0800 (PST) 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=S3VvELCBRUappLOUrT1rBSfant6PXzJfSFbQFbKTrg0=; b=MuqcKFaYY/hPEnMpDgTbhUK/mKSPV+7gA5WeMt3nMmZgSX2HJrYeZyTi+Fduw3X9Uu jQnpZb16f4uYy6/r19OgV68XO332Aq0gndDAM9U3sisBXpRZmPLXkg1xZ4YXPyRLhzPo NMM0G4wOncsiyD3Mr+61igmEBt153duoENKOirXr0pvh79k31F8l8VTQ4YvsFzYUi2Wa S1M36k5izTGT2gg/p1hORXc2LAush+HBV62fyfFGbENq7u4oKzEkGcchqOkhnr2s2njv +Up+cQ7dKqLlmsvMfEPk754NJ6g34wbZgGKSrTXAjp3idtdOoRBAwQs1lSqtb/M1ZJix 645A== X-Gm-Message-State: AJcUukc02bZ47tiumip8KLP547yeBR18YwGIRsGG4mesudH/+NlohznK aLTS5z//hogndymJJvIjUnSunm6WVDOsOw2gXF3FnRwD X-Google-Smtp-Source: ALg8bN4qGOfdnfZe/TNgZabfd/DqNk+ldgDU/9WDAhdNwpJzzSRinX7ZiQ09U6V9Vq/206rF275Uj7zvYN3oqWGBM4c= X-Received: by 2002:a5e:d808:: with SMTP id l8mr32836658iok.299.1546548713336; Thu, 03 Jan 2019 12:51:53 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: "Jayachandran C." Date: Thu, 3 Jan 2019 12:51:26 -0800 Message-ID: Subject: Re: ThunderX2 support in FreeBSD/arm64 To: Ed Maste Cc: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 82DCC8F309 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of cjayachandran@gmail.com designates 209.85.166.51 as permitted sender) smtp.mailfrom=cjayachandran@gmail.com X-Spamd-Result: default: False [-5.92 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; TAGGED_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[freebsd.org]; NEURAL_HAM_LONG(-1.00)[-0.998,0]; IP_SCORE(-3.02)[ip: (-9.59), ipnet: 209.85.128.0/17(-3.78), asn: 15169(-1.64), country: US(-0.08)]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[51.166.85.209.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.90)[-0.896,0]; NEURAL_HAM_MEDIUM(-1.00)[-0.996,0]; FORGED_SENDER(0.30)[jchandra@freebsd.org,cjayachandran@gmail.com]; MIME_TRACE(0.00)[0:+]; 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)[jchandra@freebsd.org,cjayachandran@gmail.com]; 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: Thu, 03 Jan 2019 20:52:00 -0000 (Was AFK for a while, sorry for the late reply) Hi Ed, On Fri, Dec 21, 2018 at 11:15 AM Ed Maste wrote: > > On Mon, 17 Dec 2018 at 21:51, Jayachandran C. wrote: > > > > Over the last few weeks I have committed changes for a few outstanding > > items needed for ThunderX2 support in FreeBSD/arm64. > > I see that D10082, D10083, D10084 are still open, awaiting review. > Should I apply them to my test tree? > > My current status - loader claims to start the kernel, but I see no > further output. Can you share the kernel config file you used (or > perhaps a git tree you built from)? There seems to be 2 issues here - both of them happen when the AMI firmware is used. The first issue is that the efi framebuffer does not work, and I am not able to select the serial console with AMI firmware. The second issue is that the on-chip SATA controller is not setup correctly by the AMI firmware and can cause a 'NBU BAR error' failure. I have uploaded a test firmware and instructions to https://people.freebsd.org/~jchandra/testfw/ which should boot FreeBSD fine. This is an internal build which does not have both the problems above. Let me know if this works, and I will try to push the fixes to AMI. Thanks, JC.