From owner-freebsd-arm@freebsd.org Tue Sep 26 21:07:32 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 488C1E21BB6 for ; Tue, 26 Sep 2017 21:07:32 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: from mail-lf0-x236.google.com (mail-lf0-x236.google.com [IPv6:2a00:1450:4010:c07::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 CD27376818; Tue, 26 Sep 2017 21:07:31 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: by mail-lf0-x236.google.com with SMTP id c80so5804046lfh.0; Tue, 26 Sep 2017 14:07:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=heQ9xIr7LvseFPvbaTquXfvINXRaKaX+jvY/zCPx5qA=; b=FOdqUdQTNKq3cdGZK1abWBl1PmMVP38crk0smE/LYBPT3INucIkeOa9SujhBIvYkIX L6xzpKCd+QdZq20ISkzkZd7A8p1kX5WPdpErwTMx/kDE567P4+SxG2Vfi2jktZb07fiO rXEP+35DX2CPMxvFmb6DQ3+22I2iCaMCqUqGJR3WmanE6+6gYQgPuKhr9h78TsjmZ+0w 2r+jh5QBFYmkP0f6mMUilgYoo1Hw52n0d+RwRKYOnyGW6xgP/noicACYQgXYm/woN7wy I2j15nKvDYS/xPwWo1IULuqL86I8ziwHoguNrEItYUlxlYLPwHprrxX8cMoLGxfwosNf Ajdw== 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=heQ9xIr7LvseFPvbaTquXfvINXRaKaX+jvY/zCPx5qA=; b=KpH/wy6dE8Mz9EjoLpr5/eTG1+Wnrk0nQ3kigRWXz2UAyG0e7qoPCIkrcbFVxpRKCS y3ciAPge5J5YV/O7yGzVH6OypODsFsv8KQS6hozt68wR3TLPKmtHigRJKQTUHygfvURP 8/eouPQpvJ5EnPBcgAAV5YJzNwLFQ/LpxnVpXTNtL6OjNCi1uImMrFhTZFh5I4bKpx26 NK9LZlbl40WsTF4wtWsXqDsxOFFBL5PcVVV6zSdwA5/nTMIx5/os/i5BiIW9uDMFuZFr GzTnVQi8j330luumxT6qzsCIMY2VOJ7T4VZiqdYHqh2mG4zxYk99SwjMFAWVjXqtJTpc cTWA== X-Gm-Message-State: AHPjjUjzNRVfUEyp2uyB5Wi7WoX0/K/HAK1UKF5LZSoMGFOK0Yki5TFk OX3GX5vuQTooQn0YkDi6kCMUEhLrLcwRysBBxi+XKAj1 X-Google-Smtp-Source: AOwi7QBYKzqHfOKIf5KLuX+8cMCNOgDpagzmZLYyQTdeC3MMmFgZ7a5yHcTwBd7+ccpJX1RbiwVxEZkMNeYxNm7JoV4= X-Received: by 10.25.81.85 with SMTP id f82mr3771369lfb.70.1506460049913; Tue, 26 Sep 2017 14:07:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.81.65 with HTTP; Tue, 26 Sep 2017 14:07:29 -0700 (PDT) In-Reply-To: <20170926204622.67ae9edbca62e2dcdbd1ea31@bidouilliste.com> References: <201709260339.VAA16701@mail.lariat.net> <1506435673.73082.129.camel@freebsd.org> <201709261732.LAA21422@mail.lariat.net> <20170926200446.c188fda613df2ffb894b1ff3@bidouilliste.com> <1506450112.73082.143.camel@freebsd.org> <20170926204622.67ae9edbca62e2dcdbd1ea31@bidouilliste.com> From: Russell Haley Date: Tue, 26 Sep 2017 14:07:29 -0700 Message-ID: Subject: Re: CUBOX snapshots working? To: Emmanuel Vadot Cc: Ian Lepore , freebsd-arm Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Sep 2017 21:07:32 -0000 On Tue, Sep 26, 2017 at 11:46 AM, Emmanuel Vadot wrote: > On Tue, 26 Sep 2017 12:21:52 -0600 > Ian Lepore wrote: > >> On Tue, 2017-09-26 at 20:04 +0200, Emmanuel Vadot wrote: >> > On Tue, 26 Sep 2017 11:32:21 -0600 >> > Brett Glass wrote: >> > >> > > >> > > One would think that sauce for the goose would be sauce for the >> > > gander. But is this particular Cubox now useless with FreeBSD? >> > > And if so, why? It is not an unusual model. The Cubox does work >> > > if I flash their "Ignition" startup software (which is used to >> > > bootstrap by downloading various OS images) to the same >> > > Micro SD card. >> > > >> > > --Brett Glass >> > The problem isn't FreeBSD related, it's U-Boot related. >> > >> > You could test build mainline u-boot just to confirm that it isn't >> > something due to our ports. >> > >> >> If we used to provide working cubox images and we don't anymore, it's >> hard to call that anything but a freebsd problem. > > There is working cubox images, the last one is from yesterday. > You even say yourself that you did test it and that it worked. > Do we even know if the snapshot worked for this board ? > Brett, could you test the 11.0 release for example ? (I don't remember > if for 11.1 we already switch u-boot or not). I believe the change is in the u-boot port itself. However, I don't think it's a u-boot problem (IMHO), it's a u-boot build configuration problem. There are different board variants with different hardware layout. u-boot has code for it, but our build does not account for. Unless the scripts that build the 11.1 image use a different revision of the u-boot port, wouldn't it just use the current 2017.7 base? I'm trying to figure out how to generate a u-boot with the correct SPL portion of u-boot. One could pull the SolidRun u-boot repo, or go find the ports commit before the changeover and see if we can generate the correct SPL. I looked at Mainline u-boot and there is a board directory for solid run. https://github.com/u-boot/u-boot/blob/master/board/solidrun/mx6cuboxi/mx6cuboxi.c seems to support multiple memory configurations based on defines, so this should just be a configuration problem. We clearly need to start supporting the lower spec'd SolidRun boards because this has come up a couple of times now since the changeover. It should be just a matter of creating a port that does the same thing but generates the correct SPL file? My SOM is a i2eX so I can't be too much help (and I've also over volunteered myself!). Russ >> You seem to be implying that this is another problem caused by >> switching from vendor-specific to mainline uboot. I'm not sure that's >> the case here, but if it is, be clear: It is purely a freebsd problem, >> because it was purely our choice (not mine) to switch from something >> that worked to something that doesn't. >> >> -- Ian > > Yes, maybe switching to mainline for IMX boards was a premature one, I > honestly don't have IMX board and don't know which way we should take. > All I can say is that for TI and Allwinner board, mainline U-Boot is > better (at least the support is the same). If you want to switch back > to vendor u-boot for IMX board fell free to do so (as long as you don't > change the other SoC U-Boot). >> > > >> > > At 08:21 AM 9/26/2017, Ian Lepore wrote: >> > > >> > > > >> > > > I just DLed and booted that snapshot on my Cubox-4i without any >> > > > problems. As near as I can tell, the only difference is you've >> > > > got the >> > > > dual-core chip and mine has the quad. >> > > > >> > > > The same u-boot should work for both. At least, that was the >> > > > case when >> > > > using the vendor-provided u-boot; the images are now built from >> > > > mainline u-boot. The output you provided does show that it >> > > > detected >> > > > the right kind of chip and amount of ram, so I think it should >> > > > support >> > > > both flavors of cubox. >> > > > >> > > > -- Ian >> > > _______________________________________________ >> > > freebsd-arm@freebsd.org mailing list >> > > https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.o >> > > rg" >> > > > > -- > Emmanuel Vadot > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"