From owner-freebsd-arm@freebsd.org Wed Apr 26 11:10:11 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 A75A1D50BA8 for ; Wed, 26 Apr 2017 11:10:11 +0000 (UTC) (envelope-from tvijlbrief@gmail.com) Received: from mail-yb0-x22c.google.com (mail-yb0-x22c.google.com [IPv6:2607:f8b0:4002:c09::22c]) (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 65BF7FDD for ; Wed, 26 Apr 2017 11:10:11 +0000 (UTC) (envelope-from tvijlbrief@gmail.com) Received: by mail-yb0-x22c.google.com with SMTP id 11so545740yby.0 for ; Wed, 26 Apr 2017 04:10:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=meD7NDoft7oiCUWunahvAmzclcNNBVJzA/TpSGAo1Ao=; b=NzMa1FYNuPkZ+ePnX1a9diCt+2jfk0xZ9TxdnXAo8M3pOtiuPuQ5XmFAVEr6uPYeLk YtfE4blGK/3JhNnFoG85v2FT1bYBV1Y4eYnubPp6XS6aHW3VOrM7Pdjyj6FZ/0+SV6uj gwYX7UOc1lLyqZVLxpc/hiJUDqMzBSxtc0I7zW67nGDM/m7wGbppISCZXd2U9h8h7IBK FzokkFQjQrNFPPnQ68e9QC8HpxId/5lvj7nE5WtExbq0rzxK/3XltE32Hyj8SzwN+0LG 5IGOZPmalKj0opw3Q4vC/XqFt3uT+ho16rl/PloOPT6YUeJzk0LJVK0GPr6jjO3nSoPQ vIaw== 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=meD7NDoft7oiCUWunahvAmzclcNNBVJzA/TpSGAo1Ao=; b=pDXLerjxSg3sdIPA0cJFtGMrCY1DHckr4anP5kKQZK4ootOSystXutfyQjLN0WGxkl DE7wSO6bFP+03t8r03E4/q3BrpQyczvrsR/rLO/ctK8nkYSKV0xFkZifZ4O6WMKfoheo aHJ+NgSXbqP3P0Bz/HMCVl4a4LfYnhE++lMdOqaj9Ozf6ztHgM1dmCe2jaLEV1W4zlDH TFSMPvDawYSWbD/aMS/mcBhbdYtoRXaJteOw3fmr4aFpD2u0Wa1Yh8Ypw6a75FSyg/ij wRf7Z/I7fz2JpcMnDG3r6xqOPhyr6yu9E1ZA6d8u9InwVr276KHZkV6BqSSUFoqHDNdx Ff9w== X-Gm-Message-State: AN3rC/4zpN5UC7O4tyvust8aOprEzsv+lLpW3ekjbzspMlRaWtCljEwo fjIdQjgGuj40/KD3wyvrE7Trc3NZAEB2 X-Received: by 10.37.176.1 with SMTP id q1mr12658944ybf.26.1493205010372; Wed, 26 Apr 2017 04:10:10 -0700 (PDT) MIME-Version: 1.0 References: <61985953-493F-432C-888E-3F4A06BBCA38@dsl-only.net> In-Reply-To: From: Tom Vijlbrief Date: Wed, 26 Apr 2017 11:09:59 +0000 Message-ID: Subject: Re: FreeBSD status for/on ODroid-C2? To: Mark Millard Cc: freebsd-arm Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 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: Wed, 26 Apr 2017 11:10:11 -0000 I am pretty sure the Odroid-C2 wil run stable with the recent fork fixes, but I reallocated my Odroid-C2 to a non-freebsd purpose, so I cannot test this. Note that the ethernet and SD-card are still non functional, which makes the Odroid-2 not really usable with FreeBSD, in it's current state. I had to boot the kernel over the network with U-Boot and use an USB Ethernet adapter and file system on USB-disk... The Odroid-C2 is still a nice piece of hardware for an energy efficient small (FreeBSD) server. The CPU runs at 1.5Ghz because it uses a more modern production process than the RPI3 or Pine and it has a standard cooling element mounted on the chips. It is also very compact compared to the Pine. Op wo 26 apr. 2017 om 12:12 schreef Mark Millard : > On 2016-Oct-2, at 7:17 AM, Tom Vijlbrief wrote: > > > No change (at least in my tree) since my last report on this list > somewhere in May or June. > > > > The kernel boots with 4 cpus and working usb. I use an usb ethernet > device and usb disk with the root filesysteem. Compiling and running ports > works, but a build world fails randomly with a memory access error eg after > running 15 minutes. > > Modern head (12) should no longer have the (same?) > buildworld problems now that head and stable/11 > both have the 2 fixes that fix the fork behavior > (avoiding trashing a special register and > copy-on-write now working). > > It would be interesting to see how things go now > if you rebuilt the Odroid-C2 based on modern head > (12). > > > I don't think it makes sense to work on this until a freebsd rpi3 arm64 > port is officially supported... > > FreeBSD for Odroid-C2 may go easier now that the > fork problems are addressed. > > Both Pine64+ 2GB and rpi3 are now well behaved for > buildworld. They were not before. > > > Op zo 2 okt. 2016 15:04 schreef Mark Millard : > > [Context switching to ODroid-C2 from Pine64. . .] > > > > On 2016-Oct-2, at 12:19 AM, Tom Vijlbrief > wrote: > > > > > I have a script which creates a bootable image: > > > > > > https://github.com/tomtor/image-freebsd-pine64 > > > > > > You can use the boot version from the Ubuntu image and change uEnv.txt > and > > > create an additional partition which holds the kernel image. So you > skip > > > ubldr. > > > > > > Note that the kernel boots, but I got none of the hardware devices > working > > > (I spend more time on the Odroid-C2) and haven't been working on it the > > > last months... > > > > Anything worth reporting on the ODroid-C2 details for FreeBSD: what > works, what does not, what needs to be done to boot FreeBSD, and so on? (I > assume head [CURRENT-12 these days].) > > > > > > Looking around. . . > > > > > > https://github.com/tomtor/image-freebsd-c2 > > > > seems to have last been updated on May 7 (vs. > https://github.com/tomtor/image-freebsd-pine64 's April 17). > > > > > > https://github.com/tomtor/freebsd/tree/tc2 > > > > seems to have last been updated on June 17. > > === > Mark Millard > markmi at dsl-only.net > > >