FreeBSD status for/on ODroid-C2?

[O. Hartmann]

On Wed, 26 Apr 2017 11:09:59 +0000
Tom Vijlbrief <tvijlbrief at gmail.com> wrote:

> 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.

Not to mention its really phantastic small form factor (compared to RPi3 or
Pine64).

I hope that some near day we can run FreeBSD on top of this SoC. Its lack of a
wireless interface and its 2GB as well as its high performance CPU makes it
suitable for some security-relevant applications, were WiFi is strictly
prohibited (we have such). Its eMMC interface is also pretty nice.

> 
> 
> Op wo 26 apr. 2017 om 12:12 schreef Mark Millard <markmi at dsl-only.net>:
> 
> > 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.
> >  
> > > 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 at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe at freebsd.org"