I'm also interested in 64 bit PPC, as I have a Talos II (dual POWER9) and have a second machine coming soon for driver debugging work (Talos II Lite "special developer system" -- https://secure.raptorcs.com/content/TLSDS1/intro.html )
I'm currently spending time doing driver debugging on FreeBSD, but would prefer using OpenBSD. I don't have an actual background in driver/kernel development but I'm starting to learn. On Fri, Jul 6, 2018, at 3:43 AM, Peter J. Philipp wrote: > Well I got started. Since I've never done a port to any architecture, I did > not know where to begin. I felt the header files needed work first especially > _types.h. This is taking a long time and it's in the > "20% of the work is elsewhere" category. I did about 6 header files > this morning, this morning was rare that I had time, I don't always have this > much time. In order to not duplicate work of other people attempting a port > I put my files in my cvsweb on my vps. Regarding porting resources, there are several presentations listed on the events and papers page ( https://www.openbsd.org/events.html ) that describe other people's experiences in porting OpenBSD to new platforms and CPUs. Grep for "porting". > We can share if you're working on this too. And if I give up then the work is > not in vain. The URL to this repo is: > > http://centroid.eu/cgi-bin/cvsweb/powerpc64/ > > The reason I decided to reuse the header files from the powerpc arch is that > this is what FreeBSD is doing... this way I don't have to convert FreeBSD's > stuff to OpenBSD semantics, I just change it all to 64 bit and hope it'll > work. > > I did my best converting the ASM in atomic.h to 64 bit instructions with help > of an IBM programmers guide and the FreeBSD repo for hints. > > I'll keep going when I find more time :-). Crontab to sync this repo to my > vps's repo is set at hourly. > > Regards, > -peter > -- Brandon Bergren Technical Generalist
