From owner-freebsd-arm@freebsd.org Sat May 23 01:26:00 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A5D932F3379 for ; Sat, 23 May 2020 01:26:00 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qt1-x844.google.com (mail-qt1-x844.google.com [IPv6:2607:f8b0:4864:20::844]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49TQfc0stfz48Yt for ; Sat, 23 May 2020 01:25:59 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qt1-x844.google.com with SMTP id l1so9832539qtp.6 for ; Fri, 22 May 2020 18:25:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=LrATBp/1hebNLFn/mqo/X1iYjMouZPG/2MukCxthVnA=; b=pZVPKGWXu/xttOAr/m2x/XRpHGwN2Ji06hGIDaleBgf7hL9ChiBLBuo0G7xUA2GMHo CzYoWBod5H9Z31CKnI0MvwxiAbeNF9qhDubsP46lb2H+NES7n5TEpmHRTrtrAxxvVNML AGI2ftFAwHYll6snbOmpNhr0UDoRw02rVvOKG67SYj3dKCEMZnAbw1wfq/ZVbVwxgsn4 LIGMkSO9d55fredJ5GC1gGSZyOjAn1cHFIkjnscRYmJ1yRv3uNsHVm9j079IR4J4WRoN pd7hR7s2LIRfA2Bo5E5IcFBMebyOpiiRqIU6rZrelDKnYdy5uRVy6klqMrdjC8ASwP+U /j3A== 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=LrATBp/1hebNLFn/mqo/X1iYjMouZPG/2MukCxthVnA=; b=f2MWz7g5dM44zZOTc7rn/I5zRlfzWY53sfp2pwBvtcUmWQ4H0kKXOHdT2Sx2jrtc8R EVI8TRnxVuE2hi4WZrm/po+qf0nqTQ9kULjsGM/s2qQuGGxtjp7p5Xg1yTFmIEhB7Vrx pkEVreNc4VJE4U+wx1tgW/v5gj8JOCEe4Y+8ugpypgy/m3d/jNRDYYOnmGyYz/wPT/mV V9SbpILBF5GTA2sh5jg1Yll2WFVVk4UST8aOkqwsJYi7jJLKT5Si7pNSLTKHymhY1c0V POMMV677bBfB+rkfbQqPAWjXOU8eqCQBfCoOixL4XsRbs3soWl9eP8LbuHn3DoWe8TuN kzVQ== X-Gm-Message-State: AOAM533Gpvf0d1cpGmPRVG79xg3ZZVWCwbrki3tyHgzU0o6gtZ+jXlGS cYgXsQPntoa5QwFOnZmUBHu1cyIEn6EebISBtRBNB5I/ X-Google-Smtp-Source: ABdhPJycN7emmTohd6XwUkTAnfSQkGCN2JskbI8LLJtxVec1vsa4SmVbb1BZVT9Nmz+ASGeDbr7LqiOsxY9avWFj5kA= X-Received: by 2002:ac8:3722:: with SMTP id o31mr18421624qtb.175.1590197159132; Fri, 22 May 2020 18:25:59 -0700 (PDT) MIME-Version: 1.0 References: <3e81db774e0fc1a3c2251c89b7629e1b@unrelenting.technology> <86119565e5927716a9feebabcb611871@unrelenting.technology> <37858865a8ebddd3fe1e3a228a19ef62@unrelenting.technology> <7066da0bc417ed047dc27b4741c90e81@unrelenting.technology> In-Reply-To: From: Warner Losh Date: Fri, 22 May 2020 19:25:48 -0600 Message-ID: Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X To: Dan Kotowski Cc: "greg@unrelenting.technology" , freebsd-arm X-Rspamd-Queue-Id: 49TQfc0stfz48Yt X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=pZVPKGWX; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::844) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [-2.08 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-0.94)[-0.939]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; NEURAL_HAM_SHORT(-0.16)[-0.157]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::844:from]; NEURAL_HAM_MEDIUM(-0.98)[-0.980]; R_SPF_NA(0.00)[no SPF record]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_COUNT_TWO(0.00)[2]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.33 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 May 2020 01:26:00 -0000 On Fri, May 22, 2020 at 7:07 PM Dan Kotowski wrote: > > > > > I spent some time looking at that NetBSD Layerscape code - I > couldn't figure out how to add it > > > > > trivially to the current HEAD on my own, so I'm looking forward to > seeing how we're going to yeet > > > > > that in for testing... > > > > > Something like this: > > > > > > https://github.com/myfreeweb/freebsd/commit/6cbdafbc310b9a0fa4d046f71979aa01302e8b0b > > > > > > https://send.firefox.com/download/ec0419c6d3fa856e/#QOMHO8pBq1dP1K2_4P4CBw > > > > > > > > https://gist.github.com/agrajag9/b214aa837d0ed6bb14139770ff5835ff > > > > Line 404: panic: Misaligned access from kernel space! > > > > oops, I actually have to care about the`bytes` parameter.. > > > > at least I got the ACPI-walking on the first try :) > > > > > https://send.firefox.com/download/6406af63fee41a8a/#FnEEayn7igQ_eTGs0Wq0uw > > > > > > https://gist.github.com/agrajag9/b47d63484fa51eed535d8a43625a5276 > > > > hmmm. there's now a pcib2: at device 0.0 on pci1 > > > > and it actually does allocate memory, after the root fails to: > > > > pcib1: rman_reserve_resource: start=0x670000000, end=0x67003ffff, > count=0x40000 > > pcib1: pci_host_generic_core_alloc_resource FAIL: type=3, rid=28, > start=0000000670000000, end=000000067003ffff, count=0000000000040000, > flags=4800 > > pcib2: allocated memory range (0x70040000-0x7007ffff) for rid 1c of > pci1:1:0:0 > > > > iiiinteresting. Try to kldload mpr/mps/whatever? Also insert the nvme > drive > > https://gist.github.com/agrajag9/226018f25c9c5dd9c5dec4d5ea1b767d > > It just kept looping like that for about 5min before I killed it. But it > definitely reads the firmware version correctly - it's been on a shelf for > a while. But I'm thinking maybe the card isn't initializing right - there's > none of the usual output during POST - so I'm going to dig up that PCI > power cable and the RX480 tomorrow and try those. > > As for NVMe, it panics before I get to a shell. > Where? Warner