Date: Wed, 26 Apr 2017 13:10:27 +0200 From: "O. Hartmann" <ohartmann@walstatt.org> To: Mark Millard <markmi@dsl-only.net> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: FreeBSD status for/on ODroid-C2? Message-ID: <20170426131014.03207043@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: <E8BD720C-7064-441D-A02F-BCFDE5BF1410@dsl-only.net> References: <61985953-493F-432C-888E-3F4A06BBCA38@dsl-only.net> <CAOQrpVdt-OcA05YFrt=6zwMdyf6Q38PjWP7wAzqSULUQqREPaQ@mail.gmail.com> <E8BD720C-7064-441D-A02F-BCFDE5BF1410@dsl-only.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 26 Apr 2017 03:12:57 -0700 Mark Millard <markmi@dsl-only.net> wrote: > On 2016-Oct-2, at 7:17 AM, Tom Vijlbrief <tvijlbrief at gmail.com> 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. Ah, thank you very much. As soon I get into howto create a bootable image, I'll try. I have both the Pine64 and the Odroid-C2. While 12-CURRENT (as of today) compiles now very well (buildworld and buildkernel produce no errors while building world/kernel and using the built world as the foundation of an ARM64 poudriere-jail), there are some issues with the ports tree system. With recent sources, ports-mgmt/pkg fails to build with arm64 jail and so the whole ports tree. > > > Op zo 2 okt. 2016 15:04 schreef Mark Millard <markmi at dsl-only.net>: > > [Context switching to ODroid-C2 from Pine64. . .] > > > > On 2016-Oct-2, at 12:19 AM, Tom Vijlbrief <tvijlbrief at gmail.com> 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 > > > _______________________________________________ > 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170426131014.03207043>