Page MenuHomeFreeBSD

arm64: add a std.aws config
ClosedPublic

Authored by kevans on Sep 28 2022, 8:50 PM.

Details

Summary

Mostly to document basic harware present on the platform; knowing that
Graviton exposes an ns8250 uart alone is quite helpful.

Sponsored by: NetApp, Inc.
Sponsored by: Klara, Inc.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

I always use GENERIC in EC2, but this seems accurate as far as it goes. Maybe you want to throw in an explicit device nvme as well since that's what modern EC2 systems use? But (as with acpi) that's something people are likely to have anyway.

I always use GENERIC in EC2, but this seems accurate as far as it goes. Maybe you want to throw in an explicit device nvme as well since that's what modern EC2 systems use? But (as with acpi) that's something people are likely to have anyway.

IIRC, ideally we include things here that *aren't* in std.arm64 or std.dev, even if they are in some of the other std.* SoC configs. Modulo the NVME_USE_NVD=0 line, which I realize now needs to go away because we have that in std.dev anyways, the bare minimum kernel config for ec2 (should this have been std.ec2 instead?) would be:

cpu        ARM64
ident     GRAVITON

include    "std.arm64"
include    "std.dev"
include    "std.aws"

(Tested to work, too, with exception to an FDT dependency that crept in to mmc bits via regulator headers that I'll work on separately)

This revision is now accepted and ready to land.Sep 29 2022, 6:33 AM
This revision was automatically updated to reflect the committed changes.