allow the loading of kernels from a NetBSD file system by a RISC-OS-based
bootloader. Currently, there's just about enough functionality to allow
BtNetBSD (and hence presumably boot32 on systems where it works) to load
a kernel. This code has the great advantages over our existing UnixFS
that we actually have the source and can compile it under NetBSD.
and require one additional byte for string termination
in the GSI_PLATFORM_NAME case.
This should fix PR kern/33198 by Nicolas Joly.
-Make sysinfo() behave more like the original: return
the length needed and copy out as much as possible.
instead of a separate accessops entry. There is no need to introduce bloat
for the majority of drivers which don't implement this feature.
This should also resolve PR kern/33186 by Valeriy E. Ushakov.
Use the opt_ah.h for the provided HAL to get options like AH_REGOPS_FUNC.
Add AH_REGOPS_FUNC to a few opt_ah.h that don't have it in this version
of the HAL but need it. (The next version from Sam should have this fixed
in it. If it doesn't, then we'll have to take care at import time.)
Ultimately, this should make future imports even easier, and individual ports
should not have to worry about whether AH_REGOPS_FUNC is properly defined or
not, since the opt_ah.h will just take care of it automatically.
Ok'd by dyoung@.
can automatically use the AH_XXX options that the HAL was built, without
requiring additional machine-specific configuration.
A follow up commit will activate this change.
Eliminate all mentions of rasops_info from igsfb_ioctl(), we have all
the information in igsfb_devconfig now. It's semantically correct to
serve that info from there, not from a cached copy in rasops_info.
necessary.
When we attach as console on netwinder, the timer is not yet attached,
so delay() resorts to a busy loop. That loop takes BIGNUM seconds(!)
to complete. That makes you think the machine wedged.
dereferencing it. (I added this during search for the problem fixed by
the earlier readlink buffer allocation fix, and the checks have not
triggered. Still, it's wrong of the kernel to use pointers from user
space without validation.)
