From: Jonathan Gray <jsg@jsg.id.au>
Subject: Re: Add Qualcomm Oryon V3 CPU
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: Tobias Heider <tobias.heider@stusta.de>, tech@openbsd.org
Date: Thu, 10 Sep 2026 10:18:54 +1000

On Wed, Sep 09, 2026 at 11:23:06PM +0200, Mark Kettenis wrote:
> > Date: Wed, 9 Sep 2026 22:13:54 +0200
> > From: Tobias Heider <tobias.heider@stusta.de>
> > 
> > This makes the Oryon V3 CPUs in the X2 SoCs print nicely in dmesg.
> > 
> > Had to double check but 0x2 does indeed map to v3 according to
> > https://github.com/pytorch/cpuinfo/commit/002c213d16b9dc3ddfb7ab388b13183df0e81c49
> > and https://en.wikipedia.org/wiki/Oryon#3rd_generation
> > 
> > ok?
> 
> Naming seems to be a bit of a mess, but let's go with this for now.

right, Linux device tree names now use numbers from MIDR:
qcom,oryon-PART-VAR

llvm and gcc don't have part 2 yet

of course there is no public documentation from Qualcomm on this

> 
> ok kettenis@
> 
> > diff /usr/src
> > path + /usr/src
> > commit - 303f0454ea786951e3502c98882a6ee825276479
> > blob - 70e0a58c989bc57cd9f8850160f39ac620d8e946
> > file + sys/arch/arm64/arm64/cpu.c
> > --- sys/arch/arm64/arm64/cpu.c
> > +++ sys/arch/arm64/arm64/cpu.c
> > @@ -128,6 +128,7 @@
> >  
> >  /* Qualcomm */
> >  #define CPU_PART_ORYON		0x001
> > +#define CPU_PART_ORYON_V3	0x002
> >  #define CPU_PART_KRYO400_GOLD	0x804
> >  #define CPU_PART_KRYO400_SILVER	0x805
> >  
> > @@ -233,6 +234,7 @@ struct cpu_cores cpu_cores_qcom[] = {
> >  	{ CPU_PART_KRYO400_GOLD, "Kryo 400 Gold" },
> >  	{ CPU_PART_KRYO400_SILVER, "Kryo 400 Silver" },
> >  	{ CPU_PART_ORYON, "Oryon" },
> > +	{ CPU_PART_ORYON_V3, "Oryon V3" },
> >  	{ 0, NULL },
> >  };
> > 
> > 
> 
>