9front - general discussion about 9front
 help / color / mirror / Atom feed
From: "Dave Woodman" <dave@naffnet.org.uk>
To: <9front@9front.org>
Subject: [9front] Adding AMD Jaguar and Puma SOCs
Date: Fri, 14 Jul 2023 09:32:02 +0100	[thread overview]
Message-ID: <001101d9b62d$aa1b26f0$fe5174d0$@naffnet.org.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 931 bytes --]

Hello,

With the sudden glut of Igel thin clients being seen at the moment, I
invested and found to my pleasure that 9front runs nicely on them

These are based on AMD X86  SOCs, so I modified devarch.c (/sys/src/9/pc) to
include them, and ask that they be considered for addition.

The patch is attached, but is so short I’ll put it here verbatim.

diff e52c3b4a5ba1574b1ff65e134fb9118fe2a86bba uncommitted
--- a/sys/src/9/pc/devarch.c
+++ b/sys/src/9/pc/devarch.c
@@ -435,6 +435,8 @@
        { 6,    -1,     11,     "AMD-Athlon", },/* guesswork */
        { 0xF,  -1,     11,     "AMD-K8", },    /* guesswork */
        { 0x1F, -1,     11,     "AMD-K10", },   /* guesswork */
+       { 22,   0,      11,     "AMD Jaguar", },
+       { 22,   3,      11,     "AMD Puma", },
        { 23,   1,      13,     "AMD Ryzen" },

        { -1,   -1,     11,     "unknown", },   /* total default */

Regards,
Dave.

[-- Attachment #2: devarch.c.patch --]
[-- Type: application/octet-stream, Size: 433 bytes --]

diff e52c3b4a5ba1574b1ff65e134fb9118fe2a86bba uncommitted
--- a/sys/src/9/pc/devarch.c
+++ b/sys/src/9/pc/devarch.c
@@ -435,6 +435,8 @@
 	{ 6,	-1,	11,	"AMD-Athlon", },/* guesswork */
 	{ 0xF,	-1,	11,	"AMD-K8", },	/* guesswork */
 	{ 0x1F,	-1,	11,	"AMD-K10", },	/* guesswork */
+	{ 22,	0,	11,	"AMD Jaguar", },
+	{ 22,	3,	11,	"AMD Puma", },
 	{ 23,	1,	13,	"AMD Ryzen" },
 
 	{ -1,	-1,	11,	"unknown", },	/* total default */

             reply	other threads:[~2023-07-14  8:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-14  8:32 Dave Woodman [this message]
2023-07-16 21:34 ` cinap_lenrek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='001101d9b62d$aa1b26f0$fe5174d0$@naffnet.org.uk' \
    --to=dave@naffnet.org.uk \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).