should this change apply to COMPAT_LINUX32 only, as with amd64?

curious why this is needed now

curious about why these are excluded from __powerpc64__, perhaps a comment in the src

this should probably be a separate commit with a stated rationale

undo this

?

?

According to Linux's arch/powerpc/kernel/syscalls/syscall.tbl llseek is common. This really should be powerpc, not powerpc64, on the off-chance I add 32-bit compat.

Curious. I didn't know, so just checked Linux. powerpc seems to be the *only* arch that uses lowercase 't'. I'll add a comment for it. This is also the case for TCSETS, etc., so all of these should be in one block, not sprinkled like this.

I'll have to rework this.

That's an odd one, don't know how it snuck in here.

My fault. My GSoC student (last year) had made some changes to this file that I didn't want to fully revert while I was doing the final merge. I forgot to remove this and below before submitting the review.

As above.

I know that PowerPC is the odd-man out for ABI issues, encoding, termios definitions, etc. All the others platforms we support on Linux use the common ABI stuff (by and large, there's interesting exceptions for i386 sometimes, but the common stuff often is the i386 stuff given Linux's development history).

When I did similar things for kboot, I created a per-arch .h file for this stuff as well as a common .h file that most things use. This ifdef soup is crazy and avoided that way.

This is bogus. Drop it. :)

The -FreeBSD SPDX identifier is obsolete and shouldn't be used at all.

Here and everywhere else: remove $FreeBSD$ and #include <sys/cdefs.h>

Should we return an error instead?

It's even weirder than I thought. The powerpc ioctl list breaks the linuxulator ioctl registration code. There are two groups of terminal ioctls for powerpc: those that are formed via the macros, and those that match the rest (0x54xx). So in order to do this right, I'll need to break up the existing ioctl list into two lists, and register them separately.

Interestingly, the powerpc ioctls here match the FreeBSD ioctls perfectly in many cases. Since our ABIs aren't changing... ever... I can just use our ioctl definitions for many of these in the powerpc case, and even use the _IOC() macros to generate them.

Linux on powerpc defines LINUX_IOC_VOID as 0x20000000 (same as IOC_VOID on FreeBSD), all other archs FreeBSD runs on, Linux defines it as 0.

It's a trivial function, so implementing it.