Introduction
Codenames are used to differentiate between projects and computer hardware.
The current codename system is used more or less as an inventory system until proper inventory management is set up with either CAMS or something else. Codenames for specific devices may be retired or significantly less relied on once an inventory management system is put into place. Hardware design and software projects will continue to have codenames.
Throughout lists below, any codename that has a link and/or is in bold is currently in use or is assigned to a future device.
Rules for codenames
- As of February 22, 2022, codenames shall no longer be directly related to real persons. Though the codename "Paris" will continue to be used by MediaCow Touch 2.
- Codenames should not be longer than 30 characters but with some exceptions when seen fit such as "polyoxybenzylmethylenglycolanhydride"
Specific to embedded device project codenames
- Codenames for embedded device projects must have codenames of real places and not fictional ones. (e.g. Lakewood Plaza Turbo)
Specific to workstation device codenames
- Codenames must not have symbols and numbers except for commas, dashes and numbers when they are needed to differeniate between codenames. An example of such exception is 4-Hydroxyamphetamine.
- Codenames are unique and are not reused, they are bound to the PCB (circuit board) that contains the main processor(s), such as a motherboard.
- Codenames stay linked to the motherboard even if the device's application changes such as the reuse of parts from a workstation in a server. An example of this is Polyethylene.
Workstation Codenames
Codenames given to specific systems are different from hardware project codenames as codenames for such projects are linked to the project idea itself and not a specific device/prototype.
Starting with "Polyethylene Terephthalate" in 2021, chemical compounds are used for any device codename.
With chemical compound names: - The existence of a chemical compound must be verified - Starting February 6, 2024, codenames relating to chiral chemical compounds must use the names of its optical rotations
Codenames do not differeniate devices on a network; they are not hostnames or part of hostnames. Hostnames are short descriptions of what purpose the device currently serves and are seen on the network by that name, such as "SVCS" for virtualization systems.
Names to Use
Chemical compounds may have multiple ways to name their chemical structures. Generally, the most common chemical name for a substance is used.
Due to the length of many of the codenames, a shorthand version is given in this format: <codename> - <shorthand codename>
For example, with Serdexmethylphenidate, the IUPAC name (2S)-3-hydroxy-2-[[1-[[(2R)-2-[(1R)-2-methoxy-2-oxo-1-phenylethyl]piperidine-1-carbonyl]oxymethyl]pyridin-1-ium-3-carbonyl]amino]propanoate
could not be used for a device codename for multiple reasons.
Another example, with lisdexamfetamine, the INN name is used over L-lysine-dextroamphetamine or lisdexamphetamine because the lisdexamfetamine name is more common.
Chlorofluorocarbons and Hydrochlorofluorocarbon
Starting June 2, 2023, Chlorofluorocarbon and Hydrochlorofluorocarbon codenames are reserved for Intel systems without ECC memory support. This excludes devices originally classified as a Chromebook or Chromebox, as they may get a chromium compound codename. Intel systems with ECC memory support may get a plastics-related codename instead.
This scheme was originally started to poke fun at the potential environmental effects of Windows 11.
On January 19, 2024, the categories for Chlorofluorocarbons and Hydrochlorofluorocarbons were extended to include Chlorofluoroolefins and Hydrochlorofluoroolefins respectively.
Chlorofluorocarbons/Chlorofluoroolefins
Chlorofluorocarbon/Chlorofluoroolefin codenames are used for desktops
- Trichlorofluoromethane - R11
- Dichlorodifluoromethane - R12
- Bromochlorodifluoromethane - R12B1
- Chlorotrifluoromethane - R13
- Pentachlorofluoroethane - R111
- Dichlorotetrafluoroethane - R114
- Chloropentafluoroethane - R115
- Hexachlorodifluoropropane - R212
- Dichlorohexafluorocyclobutane - C316
- Note: May be used with Intel Processor N hardware due to containing cyclobutane
- Chloroheptafluorocyclobutane - C317
- Note: May be used with Intel Processor N hardware due to containing cyclobutane
Hydrochlorofluorocarbons/Hydrochlorofluoroolefins
Hydrochlorofluorocarbon/Hydrochlorofluoroolefin codenames are used for laptops
- Dichlorofluoromethane - R21
- Chlorodifluoromethane - R22
- Dichloromethane - R30
- Chlorofluoromethane - R31
- Tetrachlorofluoroethane - R121
- Trichlorodifluoroethane - R122
- Dichlorotrifluoroethane - R123
- Chlorotetrafluoroethane - R124
- Trichlorofluoroethane - R131
- Dichlorodifluoroethane - R132
- Chlorotrifluoroethane - R133
- Dichlorofluoroethane - R141
- Chlorodifluoroethane - R142
- Chlorofluoroethane - R151
Polymers
Polymer-related codenames, specifically plastics, are reserved for workstations with ECC memory support. This along with started with Polyethylene Terephthalate in 2021 with inspiration by the plastic's use in textiles.
Uncategorized polymer codenames are for general use at the moment.
- Polycarbonate - PC
- Polyoxybenzylmethyleneglycolanhydride - Bakelite
Polyolefins and Polystyrene
Polyolefin codenames historically have been used with dual-socket systems and systems with high core count CPUs.
Currently, this includes any dual-socket AMD Opteron, dual-socket Intel Xeon and single-socket AMD EPYC systems. Dual-socket AMD EPYC systems may be assigned a polyvinyl codename instead.
- Polyethylene - PE
- Polyisobutylene - PIB
- Polymethylpentene - PMP
- Polypropylene - PP and Polypropylene v2 - PPv2
- Polystyrene - PS
Acrylics
Codenames of acrylic-family polymers are used for laptops that have support for ECC memory.
- Polyacrylic acid - PAA
- Polyacrylonitrile - PAN
- Polybenzylacrylate - PBA
- Polybenzylacrylate - PBEA
- Polybutylacrylate - PBUA
- Polycyanomethylacrylate - PCMA
- Polycyclohexylacrylate - PCHA
- Polyethylacrylate - PEA
- Polyhexylacrylate - PHA
- Polyisobutylacrylate - PIBA
- Polyisopropylacrylate - PIPA
- Polymethylacrylate - PMA
- Polymethylmethacrylate - PMMA
- Polyoctylacrylate - POA
- Polypropylacrylate - PPA
- Polysec-butylacrylate - PSBA
- Polystearylacrylate - PSA
- Polytert-butylacrylate - PTBA
Polyesters
Polyester-family polymers are used for general-purpose workstation systems designated as WBPC1.
- Polybutylene Terephthalate - PBT
- Polyethylene Naphthalate - PEN
- Polyethylene Terephthalate and Polyethylene Terephthalate v2 - PET and PETv2 respectively
- Polylatic Acid - PLA
- Polytrimethylene Terephthalate - PTT
Polyvinyls
Codenames of polymers made of monomers with a vinyl group are for future use with systems with multiple AMD EPYC processors.
- Polyvinyl Chloride - PVC
Vinyl Monomers
Though unrelated to the hardware in the "Polyvinyls" section above, codenames of monomers with a vinyl group are used for systems using VIA x86/x86-64 processors with or without ECC memory support regardless of application.
- Vinyl Chloride - VC
Psychoactives
Codenames of psychoactive substances are generally used for server systems starting early 2023. All of these systems have ECC memory unless otherwise specififed. The use of names of psychoactive substances started with stimulants for the reason specified in the Stimulants section below.
Stimulants
Stimulant drug-related codenames are generally for use with virtualization and compute servers. The use of stimulants for codenames of compute servers is inspired by the use of stimulants for the treatment of ADHD (Attention Deficit Hyperactivity Disorder).
Starting October 3, 2024, amphetamine-related codenames are to be used with Intel systems while methylphenidate-related codenames are to be used with AMD systems. Prior to this, amphetamine-related codenames were to be used with specifically the HP ProLiant BladeSystem-compatible hardware that I received on May 5, 2023 and methylphenidate-based codenames were to be used specifically with Supermicro AMD EPYC hardware.
Starting December 3, 2024, the codename scheme for Intel-based compute servers have been extended from amphetamine to any substituted phenethylamine, including Solriamfetol, Bupropion and others.
Substituted Phenethylamine
Codenames of substituted phenethylamines are to be used with virtualization/compute servers with Intel CPUs.
- Dextroamphetamine - "DXA"
- Levoamphetamine - "LVA"
- Lisdexamfetamine - "LDX"
Methylphenidates
Codenames of methylphenidates and related analogs are to be used with virtualization/compute servers with AMD CPUs. Currently, no systems are assigned these codenames. "Serdexmethylphenidate" is planned to be the first codename used in this series.
- Dexmethylphenidate - DMP
- Levomethylphenidate - LMP
- Serdexmethylphenidate - SDX
Hallucinogens
Codenames of hallucinogenic compounds are generally for use with non-embedded network router/gateway devices. This specific theme, along with "Sedatives" listed below, are based off the 2010 Far East Movement single, "Like a G6".
- Dextromethorphan - DXM
Sedatives
Sedative drug-related compounds are generally for use with non-embedded storage servers.
- Alprazolam - AZM
- Promethazine - PM or PRM
Cannabinoids
Cannabinoids, due to their unique effect, are used for critical mobile devices instead of servers. Formerly, codenames derived from methylxanthines were used for mobile devices but that theme was later discontinued for multiple reasons, one of them being that methylxanthines are considered stimulants.
Phytocannabinoids
Codenames derived from phytocannabinoids, or naturally-occuring cannabinoids, are to be used with mobile devices that use SoCs or microprocessors. I rarely ever refer to the one device under this classification by its codename so I plan to discontinue this part of the codename scheme.
- Tetrahydrocannabinol - THC
Synthetic cannabinoids
Codenames derived from synthetic cannabinoids; cannabinoids that are not naturally-occuring, are to be used with mobile devices that use microcontrollers. This specific theme was defined for deciding a codename for a Flipper Zero device.
- Dimethylheptylpyran - DMHP
Thiols
Thiol-related codenames are reserved for AMD Ryzen systems without motherboard ECC memory support. AMD Ryzen systems with ECC memory support may get a plastics-related codename instead. This includes devices with customized AMD processors using the Zen series CPU architecture such as the Valve Steam Deck's APU and the APUs used in the Xbox Series X/S and PlayStation 5. Thiols that are used in the odorization of fuel gases are used first.
Unlike the HCFC/CFC theme for Intel-based devices, codenames for these devices are chosen regardless to their form factor.
- Butanethiol - BTH
- Decanethiol - DTH
- Dodecanethiol - DDTH
- Ethanethiol - ETH
- Ethylhexanethiol - ETTH
- Hexadecanethiol - HDTH
- Hexanethiol - HTH
- Methanethiol - MTH
- Octadecanethiol - ODTH
- Octanethiol - OTH
- Pentadecanethiol - PDTH
- Pentanethiol - PETH
- Propanethiol - PTH
- tert-Butylthiol
- tert-Dodecanethiol - TDDTH
- tert-Nonanethiol - TNTH
- Tetradecanethiol - TDTH
- Undecanethiol - UDTH
Chromium-based Compounds
Chromium-based compound codenames are for use with systems originally designed for Chrome OS such as Chromebooks or Chromeboxes but had the firmware replaced with Coreboot or similar, allowing them to be designated a codename.
- Chromium Acetate - CrA
- Chromium Chloride - CrC
- Chromium Nitrate - CrN
- Chromium Oxide - CrO
- Chromium Phosphate - CrP
- Chromium Sulfate - CrS
- Ammonium Dichromate - CrD
- Calcium Chromate - CaC
- Chromium Trioxide - CrT
- Potassium Chromate - CrK
- Sodium Chromate - CrU
- Barium Chromate - CrB
- Lead Chromate - CrL
- Strontium Chromate - CrR
Development Hardware
Development hardware are systems used in the development of other hardware such as system on modules, single-board computers and evaluation kits. This codename scheme makes use of the names of hydrocarbons in relation to how they are used to "build" other chemical compounds.
Codename schemes for development systems are chosen in relation to what CPU architecture they use instead of the other codename schemes that are based on application.
ARM Development Hardware
For ARM-based development systems using ARM applications processors currently use codenames of alkanes.
- Methane
- Ethane
- Propane
- Butane
- Pentane
- Hexane
- Heptane
- Octane
- Nonane
- Decane
x86 Development Hardware
x86-based systems currently use the codenames of cycloalkanes. This would start with "Cyclobutane" for the LattePanda Mu used for MediaCow Touch 2.
- Cyclopropane
- Cyclobutane
- Cyclopentane
- Cyclohexane
- Cycloheptane
- Cyclooctane
- Cyclononane
- Cyclodecane
- Cycloundecane
- Cyclododecane
- Cyclotridecane
- Cyclotetradecane
MIPS Development Hardware
MIPS development hardware uses codenames of alkylcycloalkanes.
RISC-V Development Hardware
RISC-V development hardware uses codenames of polycycloalkanes.
Special
Special chemical compound names are reserved for rare hardware platforms.
- Positronium Hydride
- Helium Hydride
Embedded Project Codenames
Embedded circuit design projects are codenamed after specific locations such as cities, towns and villages. The design idea is what receives the codename, unlike the workstation codenames that are linked to a single unique motherboard.
Specific hardware units used in embedded hardware projects may receive a codename specific to it. For example, the LattePanda Mu received for the MediaCow Touch 2 "Paris" project was given the codename "Cyclobutane". CTCL-designed hardware can receive codenames such as if a mobile device not using an SoM; has the SoC on a custom PCB, it can receive a Cannabinoid codename as described in the sections above.
For hardware projects starting after 2020, to receive a codename, the circuit design must have at least one microcontroller, microprocessor, System on Module or SoC on the PCB.
Codenames must contain just the name of the city, town, village or CDP. Codenames that are of different places with the same name cannot be used, for example: If a project codenamed "Richmond" after Richmond, Virginia already exists, another project cannot use a codename named after Richmond, California as both would be "Richmond".
Starting August 4, 2024, codenames for hardware design projects will no longer have themes and projects would receive any codename seen fit. This is due to multiple reasons: for one, categorization has limited creativity in codename assignment. Categorization can overcomplicate assignemt of codenames (just look at how long this document is). Codenames for individual computer systems is planned to be phased out in favor for inventory IDs with the introduction of CAMS.
Generally Reserved Codenames
These codenames are reserved for special purposes due to the personal value
Due to this list becoming too long, it has been split by location of what the codename represents
New York, US
- Canastota, New York, US
- Clay, New York, US
- May be used for something DRAM related
- Old Forge, New York, US
- Oneida, New York, US
- Solvay, New York, US
- Verona, New York, US
- Whitelaw, New York, US
Florida, US
- Fort Myers Beach, Florida
- Any device, regardless to whatever series it belongs to, that is the first project that require designing with DDR2 or later memory generations receives the codename "Fort Myers Beach". This is due to how such project would be seen as a significant turning point like the 2022 business trip to Fort Myers Beach, Florida.
- Jacksonville, Florida, US
- Residence from 2011 to 2012
Maryland, US
- Ocean City, Maryland, US
North Carolina, US
- Asheville, North Carolina, US
- Bryson City, North Carolina, US
- Sylva, North Carolina, US
Tennessee, US
- Knoxville, Tennessee, US
- May be used with a device similar to MediaCow Touch (1)
- Some inspiration from the band Whitechapel
Virginia, US
- Elko, Virginia, US
- May be used for something DRAM related
- Jamesville, Virginia, US
- Midlothian, Virginia, US
- Richmond, Virginia, US
- Sandston, Virginia, US
- May be used for something DRAM related
- Virginia Beach, Virginia, US
- Doswell, Virginia, US
- May be used for something using the SP7021 or SP7350 SoC
- Smith Mountain Lake, Virginia, US
- White Oak Lake, Virginia, US
Austria
- Graz, Austria
Brazil
- Curitiba, Paraná, Brazil
- São Paulo (city), Brazil
Germany
- Dresden, Saxony, Germany
- May be used for something DRAM related
Assigned
- Floyds Knobs - MediaCow Touch Mini SP7021
- Dedicated to Jason "Leinfors" Parker (1986-2023)
- Floyds Knobs, Indiana, US
- Fort Myers - MathPad
- Fort Myers, Florida, US
- Nashville - MediaCow Touch 1
- Nashville, Tenneesee, US
- Paris - MediaCow Touch 2
- Paris, France
- Bear Creek Lake - Block-SP7021
- Bear Creek Lake, Virginia, US
- Salisbury - MediaCow Micro R
- Salisbury, Maryland, US
Software
Standalone software projects use the names of animals. Embedded software written for hardware projects do not receive their own codename as such software is considered to be part of the hardware project.
Starting November 29, 2024, codenames for software projects are no longer chosen in relation to their implementation language. Instead, codenames are to be chosen based on the software's purpose.