Wikibooks:Requests for deletion

<mediawiki xmlns="http://www.mediawiki.org/xml/export-0.11/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.mediawiki.org/xml/export-0.11/ http://www.mediawiki.org/xml/export-0.11.xsd" version="0.11" xml:lang="en">
  <siteinfo>
    <sitename>Wikibooks</sitename>
    <dbname>enwikibooks</dbname>
    <base>https://en.wikibooks.org/wiki/Main_Page</base>
    <generator>MediaWiki 1.47.0-wmf.24</generator>
    <case>first-letter</case>
    <namespaces>
      <namespace key="-2" case="first-letter">Media</namespace>
      <namespace key="-1" case="first-letter">Special</namespace>
      <namespace key="0" case="first-letter" />
      <namespace key="1" case="first-letter">Talk</namespace>
      <namespace key="2" case="first-letter">User</namespace>
      <namespace key="3" case="first-letter">User talk</namespace>
      <namespace key="4" case="first-letter">Wikibooks</namespace>
      <namespace key="5" case="first-letter">Wikibooks talk</namespace>
      <namespace key="6" case="first-letter">File</namespace>
      <namespace key="7" case="first-letter">File talk</namespace>
      <namespace key="8" case="first-letter">MediaWiki</namespace>
      <namespace key="9" case="first-letter">MediaWiki talk</namespace>
      <namespace key="10" case="first-letter">Template</namespace>
      <namespace key="11" case="first-letter">Template talk</namespace>
      <namespace key="12" case="first-letter">Help</namespace>
      <namespace key="13" case="first-letter">Help talk</namespace>
      <namespace key="14" case="first-letter">Category</namespace>
      <namespace key="15" case="first-letter">Category talk</namespace>
      <namespace key="102" case="first-letter">Cookbook</namespace>
      <namespace key="103" case="first-letter">Cookbook talk</namespace>
      <namespace key="108" case="first-letter">Transwiki</namespace>
      <namespace key="109" case="first-letter">Transwiki talk</namespace>
      <namespace key="110" case="first-letter">Wikijunior</namespace>
      <namespace key="111" case="first-letter">Wikijunior talk</namespace>
      <namespace key="112" case="first-letter">Subject</namespace>
      <namespace key="113" case="first-letter">Subject talk</namespace>
      <namespace key="710" case="first-letter">TimedText</namespace>
      <namespace key="711" case="first-letter">TimedText talk</namespace>
      <namespace key="828" case="first-letter">Module</namespace>
      <namespace key="829" case="first-letter">Module talk</namespace>
      <namespace key="1728" case="first-letter">Event</namespace>
      <namespace key="1729" case="first-letter">Event talk</namespace>
    </namespaces>
  </siteinfo>
  <page>
    <title>Wikibooks:Requests for deletion</title>
    <ns>4</ns>
    <id>385</id>
    <revision>
      <id>4676535</id>
      <parentid>4676488</parentid>
      <timestamp>2026-10-17T14:37:05Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>/* Wikibooks:FlaggedRevs Extension */ reply to SHB ([[mw:c:Special:MyLanguage/User:JWBTH/CD|CD]])</comment>
      <origin>4676535</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="45167" sha1="8qrsur93khoneqpd3imh5lil8ui9ab9" xml:space="preserve">__NEWSECTIONLINK__
[[Category:Wikibooks deletion|{{PAGENAME}}]]
{{Discussion Rooms}}
{{TOCleft}}
{{shortcut|WB:RFD}}
{{Requests for deletion/New deletion}}
{{Requests for deletion/Deletion intro}}
&lt;!-- New deletion nominations go at the bottom of page. --&gt;

== [[Salute, Jonathan!]] and its translations ==

&lt;div style=&quot;column-count: 7;&quot;&gt;
* [[Salute, Jonathan!|Interlingue/Occidental]] ([[w:en:Occidental|w]], original)
* [[Òla, Ionatà!|Audià]]
* [[Holo, Jonathan!|Cristianés]]
* [[Terve, Jonathan!|Ekumenski]]
* [[Hej, Jonathan! (Germanisch)|Germanisch]]
* [[Salom, Jonatan!|Globasa]]
* [[Àlŏ, Jonathan!|Guosa]] ([[w:en:Guosa|w]])
* [[Salut, Jonathan!|Idiom Neutral]] ([[w:en:Idiom Neutral|w]])
* [[Saluto, Jonathan! (Ido)|Ido]] ([[w:en:Ido|w]])
* [[Hallo, Jonathan!|Interlingua]] ([[w:en:Interlingua|w]])
* [[Salut, Jonathan! (Interocidental)|Interocidental]]
* [[Bune Ğonatan!|Lingaust]]
* [[Oila, Jonatan!|Lingue Simple]]
* [[Haloo, Jonatan!|Lingwa de Planeta]] ([[w:en:Lingwa de Planeta|w]])
* [[Sin Chao, Jonathan!|Masa Tang]]
* [[Salut, ionatano!|Meteza]]
* [[Salu, Jon!|Mini]]
* [[Hay, Jonathan!|Mirad]]
* [[Hai, Jon!|Monav]]
* [[Sesan Jon!|Monkel]]
* [[Salam, Jonathan!|Mundeze]]
* [[Dag, Jonathan!|Negerhollands]] ([[w:en:Negerhollands|w]])
* [[Salut Jonathan!|Neo]] ([[w:en:Neo|w]])
* [[Hej, Jonathan!|Nordien]]
* [[Saluto, Jonathan!|Novial]] ([[w:en:Novial|w]])
* [[Salute, Jonathan! (Novlingue)|Novlingue]]
* [[Alo, Jonathan!|Numo]]
* [[Hela, Jonathan!|Proyo]]
* [[Salute, Jonathan! (Romanica)|Romanica]] ([[w:en:Romanica|w]])
* [[Simi, Jonathan!|Solresol]] ([[w:en:Solresol|w]])
* [[Toki a, jan Jonatan!|Toki Pona]] ([[w:en:Toki Pona|w]])
* [[Glidis, o Jonathan!|Volapük]] ([[w:en:Volapük|w]])
&lt;/div&gt;

There are a couple of issues here:

# Beyond their introductions, all of these books are written in languages which are not English, making them out of scope for the English Wikibooks.
# All but one of these books are in fact written in constructed languages, most of them in recently created conlangs. In some cases (e.g. [[Sin Chao, Jonathan!]]), I can't find any reliable sources describing the target language outside of the translation itself.
# Most of the translations (i.e. other than [[Salute, Jonathan!]] itself) were abandoned within the first five or so chapters (out of 100); none of them are complete, and there seems to be little effort to complete any of them.

While I recognize that this is an unusual project, and potentially one which could have some value, it's not at all clear to me that the English Wikibooks is the right place for it. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:24, 29 September 2024 (UTC)

: I'm really not sure what to do about these ones. While I recognize that this approach is certainly one method of teaching a language, I'm not sure that it constitutes an educational textbook. We do require that the English Wikibooks be written in English—for language-learning books, this typically means that the instructional parts are in English while the exercises are in the language being taught. I do think that if the language doesn't have much supporting evidence outside the book itself, it can safely be deleted. — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:01, 29 September 2024 (UTC)

: Author of the book here. I originally wanted to put it in the Interlingue Wikibooks https://ie.wikibooks.org/wiki/Principal_p%C3%A1gine but it somehow got locked when I wasn't paying attention and so I ended up putting it here. Getting it unlocked requires going through the process of starting an Incubator and all the rest so I opted for here and then started putting some English-only content once it was done. It's sort of in the same vein as books like Lingua Latina per se Illustrata that have separate versions with teacher notes and whatnot. [[Salute, Jonathan!/Capitul 1 - with notes]] After it was done the auxlang community really took to it which was a nice surprise. I think Ido has the largest number of chapters at the moment at 15.
:If the vast content of this book could be used to justify a quick reopening of the Interlingue Wikibooks to move it there, I'd love to do that. I imagine that an incubator with 100+ book chapters would be enough to open a Wikibooks and that's what this is. — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:02, 29 September 2024 (UTC)

: Ah, I just realized that we do have a proposal to reopen the Interlingue Wikibooks: https://meta.wikimedia.org/wiki/Requests_for_new_languages/Wikibooks_Interlingue along with an Incubator page here. https://incubator.wikimedia.org/wiki/Wb/ie/Principal_p%C3%A1gine
: How easy would it be to migrate the entirety of Salute Jonathan to there? — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:30, 29 September 2024 (UTC)

:: Hi @[[User:Mithridates|Mithridates]]! I'm not sure how incubator projects work, but I fully support migrating these books there. You may want to inquire over there and link to this discussion to support your request to move the content over there. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:16, 29 September 2024 (UTC)

::: Hi! Actually I have a third idea to propose after thinking about this again today (haven't been here much since I finished the book): I noticed that there is more English content than I remember and that might make it an awkward fit for the Interlingue Wikibooks. I definitely agree that having all the auxlang translations for new auxlang projects goes well beyond the scope of this Wikibooks. Finally, there are some auxlangs that are notable with their own Wikipedias.
::: So the idea is the following:
:::# Leave the original here and I can continue the work on the version with English notes and grammar. That will make it the same as Lingua Latina per se Illustrata, English by the Nature Method, Athenaze and all the rest.
:::# The Interlingua one can move to the Interlingua Wikibooks (maybe Romanica too if they want as it is sort of a dialect of Interlingua).
:::# For Ido and Lingua Franca Nova which have a Wikipedia but not a Wikibooks, I'm a little bit unsure...technically they could have their own version like the original one but would require English explanations. I could let them know and see if they are willing to do so and see what they think (work on adding English to the books vs. move the content elsewhere).
:::# The rest can move to a Github repo, then be deleted, and the front page of this book can have a single link to the repo.
::: Any thoughts on that? Adding the extra English content will be easy as it is my book and I know it inside and out.
::: Edit: [https://en.wikibooks.org/wiki/Salute,_Jonathan!/Grammar_(pronouns) this page] I just added.  — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 13:50, 29 September 2024 (UTC)

:::: Thanks for taking the time to consider this! Here are my responses/questions:
::::* Is the original [[Salute, Jonathan!]] (Occidental)? Since that one is quite fleshed out, I agree that if you edit it so the primary language of the book (e.g. headers, instructions, etc) are written in English while leaving the actual story in Occidental, it would be okay and fit in more with instructional language textbooks.
::::* For your points 2 and 3, I'm not sure how those other projects work, so I'll leave it up to them. I'm not quite sure why they would need to move, since in theory they could be revised with English as the language of instruction? Although, they have been left incomplete for a long time.
::::* For your point 4, I have no problem with that. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:51, 29 September 2024 (UTC)

::::: Hello again, it's the weekend so I have a bit more time to work on this. I've decided to merge the extra content from the following five chapters since the difference is fairly small and the original chapters should now have this English content. Could you delete these five pages now that they are no longer needed? [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC)
::::: [[Salute, Jonathan!/Capitul 1 - with notes]]
::::: [[Salute, Jonathan!/Capitul 2 - with notes]]
::::: [[Salute, Jonathan!/Capitul 3 - with notes]]
::::: [[Salute, Jonathan!/Capitul 4 - with notes]]
::::: [[Salute, Jonathan!/Capitul 5 - with notes]] [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC)
:::::: [[File:Yes_check.svg|{{#ifeq:|small|8|15}}px|link=|alt=]] {{#ifeq:|small|&lt;small&gt;|}}'''Done'''{{#ifeq:|small|&lt;/small&gt;|}} — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:34, 5 October 2024 (UTC)

::::::: Hi again! No luck trying to find a home for the random language translations on other auxlang wikis, can't find one that is actively maintained.
::::::: The thought struck me that maybe I could just put those ones on a sub page of my user page, would that be permitted? If not, I think I'll just stick them somewhere in GitHub and call it a day since none of the people who started the translations seem to care enough to do anything about them. I'd rather not see them outright disappear but since they aren't mine I don't care enough about them to do much more work than copy and paste them somewhere.
::::::: (I would leave the ones in languages with an ISO-639 code and Wikipedia here, of course) — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:13, 9 November 2024 (UTC)

:::::::: Thank you for checking! I don't personally see an issue with moving them to your user space right now. Cheers — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:21, 9 November 2024 (UTC)

::::::::: Thanks a lot! I've started a single page where I will put them all here [[User:Mithridates/SJ]] and will proceed slowly due to lack of time and also to avoid stepping on any toes / asking you to delete too much at a time and possibly deleting the wrong content.
::::::::: For this week I have put the content for the languages Audia, Cristianès, Guosa, Lingaust, Mini, Mirad, and Monav on that page as they all have a single page of content and didn't take much time to move. Please delete those. Once they are gone I will add a note on the main page letting people know where they have gone (in addition to a thank you for their interest in the book! I do love how many people have recognized it as a good source material for teaching a language). — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 04:09, 10 November 2024 (UTC)

: {{keep}} the translations for languages that have an article on the English Wikipedia, i.e. Guosa, Idiom Neutral, Ido, Interlingua, Lingwa de Planeta, Negerhollands, Neo, Novial, Occidental, Romanica, Solresol, Toki Pona, and Volapük.
: Translations for languages that don't have an article can be kept if they have reliable sources, which I was able to find for the following languages (if you think they are not reliable, please let me know):
:* Globasa: [https://www.languagesandnumbers.com/how-to-count-in-globasa/en/globasa/] [https://greyson.conlang.org/2020/01/29/shouting-out-globasa-and-pandunia/]
:* Mini: [https://jprogr.github.io/mini] [https://www.omniglot.com/language/phrases/mini.htm] [https://www.languagesandnumbers.com/how-to-count-in-mini/en/mini/]
: {{del}} and move to [[User:Mithridates/SJ]] the rest of the translations, i.e. Audià/Audian, Cristianés, Ekumenski, Germanisch, Interocidental, Lingaust, Lingue Simple, Masa Tang, Mirad, Monav, Monkel, Mundeze, Nordien, Novlingue, Numo, Proyo, and Scuian/Meteza. If you can find reliable sources for those languages, please let me know.
: In particular, I could not find resources for Audià/Audian and Monav after searching through 15 and 17 pages on Google, respectively. It doesn't help that [[Òla, Ionatà!|their]] [[Hai, Jon!|translations]] don't explain what those languages are and where to find resources for them. This makes contributing to those translations almost impossible until @[[User:Caro de Segeda|Caro de Segeda]] can provide resources to us. It's possible that the resources may have disappared from the Internet, or that those languages were created by Caro de Segeda him/herself. If you can find resources for Audià/Audian and Monav, please let me know.
: I'm notifying the primary contributors of the translations: @[[User:Caro de Segeda|Caro de Segeda]], @[[User:Frzzl|Frzzl]], @[[User:Greatscotteh|Greatscotteh]], @[[User:IHateNumbers234|IHateNumbers234]], @[[User:Jayeless2|Jayeless2]], @[[User:Morozof|Morozof]], @[[User:Omnihom|Omnihom]], @[[User:Omoutuazn|Omoutuazn]], @[[User:PovriNaivon|PovriNaivon]], @[[User:Sir Beluga|Sir Beluga]] and @[[User:Tyoyafud|Tyoyafud]]. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 09:52, 30 June 2025 (UTC)

:: Caro de Segeda said on [https://www.reddit.com/r/conlangs/comments/1lcnz9g/comment/n0sc3wx/ Reddit] that Monav was created by him/her and that he/she didn't publish any resources about it other than [[Hai, Jon!]]. With '''zero''' other resources to rely on for contributing to the translation, and the fact that Monav is in [[User:Mithridates/SJ]], [[Hai, Jon!]] should be speedy deleted. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 01:38, 3 July 2025 (UTC)

::: I've undone the speedy deletion as Caro de Segeda posted a [https://prexins.wordpress.com/2025/07/04/monav/ resource] for Monav. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 07:18, 4 July 2025 (UTC)

:::: You can delete all the ones that I have created myself, I have already moved them to other places. — [[User:Caro de Segeda|Caro de Segeda]] ([[User talk:Caro de Segeda|discuss]] • [[Special:Contributions/Caro de Segeda|contribs]]) 12:39, 5 July 2025 (UTC)

{{outdent|::::}}I don't know if this is helpful since it wouldn't apply to most of these, but [[s:mul:]] could hold some of these. — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 09:18, 30 November 2025 (UTC)

: I don't think that would be within the scope of that project. I'm not aware of any other situation where Wikisource publishes translations of texts created on Wikimedia projects - that's usually left up to other language editions of the same project. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 05:34, 1 December 2025 (UTC)

:: In this situation there isn't a separate [[s:ie:]] distinct from Multilingual Wikisource (see [[meta:Wikisource#List of Wikisources]]). In fact, there are very few multilingual wikis in the Wikimedia sphere; while this project ''could'' move to a Miraheze-hosted or similar wiki farm location, I think it would be a missed opportunity. I suppose an [[Interlingue]] book could be started in [[shelf:Constructed languages]] which would have all 100 chapters as an appendix (and likewise for the other languages), but that also seems non-ideal since it requires an English-language text that doesn't currently exist to be created. [[WB:AT]] seems to describe a similar situation to this one and prescribe Wikisource as the solution, and [[WB:SOURCE]] mentions fiction as out-of-scope for Wikibooks (even as in this case, language-educational fiction). [[s:mul:Wikisource:about Wikisource]] simply speaks of source texts and doesn't mention publication requirements, so maybe that is specific to some of the monolingual editions? — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 22:28, 5 December 2025 (UTC)

:{{keep}} 100% keep. These books are a core part of language textbooks on Wikibooks and have been for years. Not sure why this is even being debated.--[[User:Xania|Xania]] [[Image:Flag_of_Estonia.svg|15px]]  [[Image:Flag_of_Ukraine.svg|15px]] [[User talk:Xania|&lt;sup&gt;talk&lt;/sup&gt;]] 17:55, 16 May 2026 (UTC)

::With all due respect, some of the books included in this nomination (like [[Sin Chao, Jonathan!]]) are written in constructed languages which are not substantially attested anywhere else. I struggle to imagine any educational purpose for such a book. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:12, 17 May 2026 (UTC)

== [[International Baccalaureate]] ==

Not actually a book in and of itself; rather, it is just a compilation of links to other books —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:24, 18 October 2024 (UTC)
: Could this be salvaged as a shelf? [[User:Pppery|Pppery]] ([[User talk:Pppery|discuss]] • [[Special:Contributions/Pppery|contribs]]) 05:23, 27 January 2025 (UTC)
::Probably, but are the linked books even useful? IB exams change from year to year - sometimes quite dramatically - so an old exam guide is of very limited value. Many of these books were written 10-15 years ago, and some of them (like [[IB French]]) even have comments indicating that they're no longer applicable. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 02:18, 8 December 2025 (UTC)
:I  would be interested in a book that explains what an [[International Baccalaureate]] is. They may be books about it in the real world, but they are not free and with the online world becoming a fortress of paywalls I wonder how much longer one would be able to find such information on the web. This is what the  wikipedia article says:
:* This article '''is missing information''' about the educational programs and curricula. Please expand the article to include this information. Further details may exist on the [[wikipedia:Talk:International_Baccalaureate#|talk page]].  ''(March 2025)''
:[[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 02:05, 13 October 2026 (UTC)

== [[Character List for Baxter&amp;Sagart]] ==

Seems completely out of scope as an educational book; it's just a list of characters and outlinks —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:53, 18 October 2024 (UTC)

:Adding [[Character List for Karlgren's GSR]] and [[Character List for Schuessler's CGSR]] for the same reason —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:55, 18 October 2024 (UTC)

:These three books do make a package and I agree they should be considered together. However, I strongly object to deleting them. They are really extremely useful resources. I use them every week and I know that many people who do work on Old Chinese phonology do so. There are lots of books out there that are lists of characters, these are called dictionaries. For example Axel Schuessler's ABC Etymological Dictionary of Old Chinese, or Pulleyblank's Lexicon of Reconstructed Pronunciation in Early Middle Chinese, Late Middle Chinese, and Early Mandarin. I see it as entirely a good thing for reference works of this kind to be available free online rather than only in expensive books in university research libraries. If this is in violation of a Wikibooks policy, I would at least like that policy to be drawn to my attention and to have some constructive comment offered about which Wikiproject such a resource should fall under. I will also say on a personal note that I have put literally hundreds of hours of work into these projects and it would grieve me a lot to see this work simply vanish, in particular when I know that colleagues around the world use these books. --[[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 07:27, 1 November 2024 (UTC)
::Hi @[[User:Tibetologist|Tibetologist]], and thank you for the feedback! Official Wikibooks policy does not permit standalone dictionaries (see [[WB:DICT]]), though I understand the argument that it is a useful resource. I am wondering if there might be a home for it at [[Wiktionary:Wiktionary:Welcome, newcomers|Wiktionary]] or [[Wikiversity:Wikiversity:SHARE|Wikiversity]]? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 12:14, 1 November 2024 (UTC)
:::The policy says to use Wiktionary, but these books cannot be moved there. In fact they link there, you can understand me as having made an index to wiktionary, if you like, where the ORDER of the characters is extremely important, information that would be lost in Wiktionary. 
:::Wikiversity is not a project I participate in, and in any event my books here are older than it, so this option was not available for me at the relevant moment. If you are offering to move my books to Wikiversity, that is very kind of you and I will very graciously accept. [[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 14:10, 1 November 2024 (UTC)
::::I have pinged over at Wikiversity Colloquium to ask about suitability and have looped you into the conversation over there. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:20, 1 November 2024 (UTC)
::I concur. I'm just an undergrad who tries to learn about Sino-Tibetan historical linguistics in his free time but I've found this wikibook to be incredibly useful, and I keep it open in one tab while I watch Professor Nathan Hill's lectures that he uploads to youtube in another tab, and another tab for taking notes. In fact if I remember correctly Professor Hill actually pointed his students to this wikibook. 
::I'm not familiar with [[wikiversity:Wikiversity:SHARE|Wikiversity]] but if all the content were as accessible there as it is here then I think that could work.  [[User:ChromeBones|ChromeBones]] ([[User talk:ChromeBones|discuss]] • [[Special:Contributions/ChromeBones|contribs]]) 02:43, 9 July 2025 (UTC)
:Per [[:v:Wikiversity:Colloquium#Import_Resource_From_Wikibooks?]], I recommend copying and pasting, including attribution via the edit summary and talk page, add appropriate categories and links, and then it could be deleted locally. —[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''vf&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 22:32, 3 November 2024 (UTC)

== [[Suomen kieli käyttöön]] ==

Multiple pages in this book are written entirely in Finnish, which is out of the enWB scope. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:09, 19 October 2024 (UTC)

:I was going to say whether we should ask any fiwikibooks sysop to maybe see if this could be transwikied to fiwb if it's within the scope there. But [[:fi:Toiminnot:Käyttäjät/sysop]] indicates that there are only 3 sysops, and only {{u|Anr}} and {{u|Zache}} have made edits this ''year''. If they deem it to be salvageable, then transwiki + delete, otherwise straight-up delete. --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 11:24, 14 November 2024 (UTC)
::It seems that the idea behind the book was for the pages to be bilingual, as it’s a language learning book. That’s why there are Finnish texts included intentionally even on the pages that are complete. There are similar books in dewikibooks and ruwikibooks as well. For the English version, I think the easiest way to proceed would be to clean up and adjust the page layout to fit enwikibooks better, and then translate the missing parts. By the way, if anyone wants to update the book’s name in English, it can be titled ''&quot;Using the Finnish Language&quot;'' or ''&quot;Put Finnish Language into Use&quot;'' for a direct translation.   [[User:Zache|Zache]] ([[User talk:Zache|discuss]] • [[Special:Contributions/Zache|contribs]]) 11:57, 14 November 2024 (UTC)

== [[AT&amp;T Mobility FAQ]] ==

* [[AT&amp;T Mobility FAQ]]
* [[AT&amp;T Mobility FAQ/MEdia Net Configuration]]
* [[AT&amp;T Mobility FAQ/Data Connect Configuration]]
An ''extremely'' outdated FAQ on AT&amp;T's cell phone services. Most of this document was written 20+ years ago as a Usenet FAQ; very little of it is accurate or useful anymore (particularly the two subpages, which have to do with obsolete configurations for &quot;tethering&quot; a computer to a cell phone). No objection if someone wants to update it, but there's clearly been no appetite to do that. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 22:20, 30 December 2024 (UTC)

:I'm wondering if it might make sense for us to develop some kind of policy on archiving books here. There are many like this one that have a good deal of content but are extremely out of date and just not useful as originally intended. ——[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:34, 30 December 2024 (UTC)
::@[[User:Kittycataclysm|Kittycataclysm]]: See the newly developed [[Wikibooks:Outdated books]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 00:16, 31 December 2024 (UTC)
:::Ooh, thanks - something like that seems like it could be an appropriate way to handle this book. A lot of the other outdated books I've tagged have been so incomplete that they wouldn't have been particularly useful even as historical references; this one might at least have some interest.
:::Any chance we can get a separate namespace (maybe &quot;Archive:&quot;) set up for archived book content? That'd make it possible to do things like exclude them from on-site search by default. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:07, 31 December 2024 (UTC)
::::I think this might be a more extended discussion, so I'll bump it over to the [[Wikibooks talk:Outdated books|talk page of the draft policy]]! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:54, 31 December 2024 (UTC)

== Algebra/Chapter 10/Symmetric Polynomials ==

I personally believe that [[Algebra/Chapter 10/Symmetric Polynomials|this]], and all of the sections should be deleted for the fact that this goes WAY beyond the scope of what was intended for the Chapter (Algebra II level polynomials). [[User:GoreyCat|GoreyCat]] ([[User talk:GoreyCat|discuss]] • [[Special:Contributions/GoreyCat|contribs]]) 15:07, 6 February 2025 (UTC)

:'''Split''': Deletion here is not the best solution (see [[w:WP:ATD]]). Instead, this page and its subpages should be moved to another book, most likely [[Abstract Algebra]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 17:35, 6 February 2025 (UTC)
:{{keep}} since there is a good amount of content. If [[Abstract Algebra]] is appropriate, it seems like a fine idea to move there. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:59, 7 February 2025 (UTC)
::Eh, yeah, I supposed moving it is better. I just don't think it's suitable for where it appears. [[User:GoreyCat|GoreyCat]] ([[User talk:GoreyCat|discuss]] • [[Special:Contributions/GoreyCat|contribs]]) 01:40, 8 February 2025 (UTC)
== [[Puredyne]] ==

Development of Puredyne Linux was discontinued in 2012, and the software no longer appears to be available for download anywhere. (An archive of the web site is still up - with a bunch of embedded spam links - but the download links are all dead.) Is this a suitable candidate for archival (cf. [[Wikibooks:Outdated books]]), or should it just be deleted? [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 04:35, 5 March 2025 (UTC)

:I'd just archive stuff like this. Looks like a decent bit of work went into it, and you never know when someone might need to use Puredyne for some obscure project. I'd be willing to bet mirrors exist of it somewhere, or someone has it on a drive. If you want to find some stuff worth deleting, comb through [[:Category:Allbooks categories]]. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:30, 5 March 2025 (UTC)

== [[Template:Qr-twwp]] ==
This isn't exactly a request to delete the template, but rather to merge it with {{tlx|Copypaste}}. The {{tlx|Qr-twwp}} template serves the same purpose as {{tlx|Copypaste}}, but without the seven-day period after which the page is deleted. This leads to confusion, as well as a perpetually full [[:Category:Queried pages]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 17:37, 30 March 2025 (UTC)

== [[Ghouls of the Miskatonic]] ==

I don't think that a plot summary of a book is in-scope here. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:43, 20 August 2025 (UTC)

:{{vd}} - at least, not a summary of ''this'' book. A summary and/or study guide to a notable work of literature might be in scope, but this is certainly not one. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:23, 25 August 2025 (UTC)
::Hi. I am the creator of the pages of this book. If I understand correctly, it has to be a summary of a notable work of literature? So what exactly is defined as such? I only started this as I thought it would be fun, interesting and encouraging to others who read the Arkham Horror novels, and I thought it was permitted as I've seen other summaries of books on wikibooks. [[User:Dayne90|Dayne90]] ([[User talk:Dayne90|discuss]] • [[Special:Contributions/Dayne90|contribs]]) 13:27, 26 August 2025 (UTC)
:::Your problem is it is just the plot... it needs to include an educational textual analysis to be in scope [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 12:47, 28 August 2025 (UTC)
::::And ideally it'd be a text which has ''already'' been the subject of literary analysis, such that the analysis on Wikibooks isn't original research. A notable work of literature like ''Frankenstein'' or ''Moby-Dick'' would easily meet that requirement; a tie-in novel for a tabletop RPG probably does not. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 22:08, 29 August 2025 (UTC)

== [[A-level Computing AQA Paper 1 Skeleton program 2027]] ==
{{closed|Considering the recent comments and due to no objections, I converted it to a soft redirect until another admin decides if the page can be deleted. CC to [[user:MrBerard|MrBerard]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:51, 15 October 2026 (UTC)}}
This was proposed for speedy deletion by [[User:Omphalographer]] as 'not being a book'. However, I think this page's future requires further discussion from the community. Maybe some input would be appreciated?[[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 23:51, 21 September 2026 (UTC)

:As best I can tell, this is a page students are using to collaborate on solutions for a standardized test. There are a number of similar pages for other years linked from [[A-level Computing/AQA/Paper 1/Skeleton program]].
:This is not a good fit for Wikibooks. If these students are interested in this kind of collaboration, it should take place elsewhere. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:14, 22 September 2026 (UTC)
::The project can be moved to Wikiversity, I think. If the students can contribute it and make sure it complies with Wikibooks' guidelines, it can stay here. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:17, 22 September 2026 (UTC)
:::@[[User:Omphalographer|Omphalographer]] @[[User:TechVindicator|TechVindicator]]
:::There's been a Wikibook on this every single year, as I mentioned in my comment on the deletion notice. That doesn't mean that this shouldn't be on Wikiversity, just that there is ample precedent of it being a Wikibook.  Dunno if this matter to those kind of editorial decisions, though. [[Special:Contributions/~2026-51010-27|~2026-51010-27]] ([[User talk:~2026-51010-27|talk]]) 13:39, 22 September 2026 (UTC)
::::@[[User:~2026-51010-27|~2026-51010-27]]: How would the page comply with [[WB:What is Wikibooks?|Wikibooks' mission]]?. Could you provide an explanation of what the project is?  If it's a collaborative project to work on solutions for a standardized test (like @[[User:Omphalographer|Omphalographer]] said), it would be more suitable for Wikiversity. If it's a textbook about A-level computing, then it would be suitable here. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:58, 22 September 2026 (UTC)
:::::Hi,
:::::This is definitely the former, not the latter. As I said, I don't particularly think this should be on Wikibooks, it just happens the previous years had been, and clearly they weren't subject to this degree of scrutiny 😅
:::::I have created https://en.wikiversity.org/wiki/A-level_Computer_Science_AQA_Paper_1_Skeleton_program_2027 - I'll delete the content of the page and put the link at the top. If there is a more appropriate banner to indicate the migration, please make it look how it should :D [[User:MrBerard|MrBerard]] ([[User talk:MrBerard|discuss]] • [[Special:Contributions/MrBerard|contribs]]) 10:23, 29 September 2026 (UTC)
::::::I can't seem to put a link without the edit being deemed destructive, so I'll let you trusted people do what's needed. [[User:MrBerard|MrBerard]] ([[User talk:MrBerard|discuss]] • [[Special:Contributions/MrBerard|contribs]]) 10:27, 29 September 2026 (UTC)
: {{comment}}: I cannot determine consensus in this request on whether or not it should either be deleted or imported to English Wikiversity. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:28, 13 October 2026 (UTC)
::I've actioned the migration to Wikiversity as per my comment of 29 sep. I'd rather this stayed in as a stub with a link to the Wikiversity entry, for a couple of months, though I'm sure search engines are still vaguely good enough that this shouldn't matter too much. [[User:MrBerard|MrBerard]] ([[User talk:MrBerard|discuss]] • [[Special:Contributions/MrBerard|contribs]]) 14:35, 13 October 2026 (UTC)
{{end closed}}

== [[Talmudic aramic]] ==
{{closed|Deleted per consensus below. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:18, 13 October 2026 (UTC)}}
Per the user's other mass-created pages, I concur with the AI flagging that Kittycataclysm placed on the page. I believe this to be LLM-generated, and it should thus be deleted. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 03:29, 30 September 2026 (UTC)

:{{vd}}, LLM spam. [[User:Ternera|Ternera]] ([[User talk:Ternera|discuss]] • [[Special:Contributions/Ternera|contribs]]) 13:22, 30 September 2026 (UTC)
:{{vd}} - like most LLM-generated books, this is heavy on structure and light on substance. Most of the content amounts to a poorly organized glossary, and there are a lot of pieces missing. (For instance, there is no discussion of the grammar of the language beyond a couple of fixed expressions.) [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:11, 1 October 2026 (UTC)
:{{vd}} per stated reasoning. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:43, 12 October 2026 (UTC)
{{end closed}}

== [[Job Search]] ==
{{closed|Per minimal consensus, I deleted these books, but I only kept the main pages of these books by creating them as redirects for [[Find Employment]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:24, 13 October 2026 (UTC)}}
* as well as [[Job Search Automation for College Students]].

Neither of these books contains any useful information. The first book seems to be written primarily to funnel users to the second, and the second to funnel users to [[PlanoTse Handbook for Job Search Automation]], which was deleted last year. (The deletion request doesn't seem to have been archived.)

The sum total of information in these two books is, essentially, &quot;you can search for jobs online&quot;, which is insultingly trivial. The second book's suggestion that users automate the job search process is of no practical value; most web search engines and job search sites nowadays will detect and block automated access.

[[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:36, 1 October 2026 (UTC)
: {{vd}} and redirect to [[Find Employment]]. ‑‑[[User:Kai Burghardt|Kai Burghardt]] ([[User talk:Kai Burghardt|discuss]] • [[Special:Contributions/Kai Burghardt|contribs]]) 05:14, 2 October 2026 (UTC)
{{end closed}}

== [[Wikipage]] ==
{{closed|Deleted per minimal consensus below. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:26, 13 October 2026 (UTC)}}
Like a few other books created by this user, the purpose of this book appears to have been to promote a piece of software written by the author ([[User:Planotse]]). The software is no longer available, and there is no actual content in the book.

[[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:40, 1 October 2026 (UTC)

:{{Vd}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 15:30, 12 October 2026 (UTC)
{{end closed}}

== [[Becoming a Linguistic Mastermind]] ==
{{closed|Deleted. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:11, 15 October 2026 (UTC)}}
Old book (created 2007) with no substantial content. The intent of this book appears to have been to create a single textbook encompassing ''all'' languages, with sub-courses for each language at [[Becoming a Linguistic Mastermind/The courses]], but no such courses were ever created. An analogous project on dewikibooks [[:b:de:Wikibooks:Löschkandidaten/ 2011-04#Der einfache Weg zum Sprachgenie|was deleted in 2011 for similar reasons]]. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:20, 7 October 2026 (UTC)

:{{Vd}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 15:30, 12 October 2026 (UTC)
{{end closed}}

== [[The Permanent Advantage]] ==
{{closed|Speedily deleted —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 20:15, 14 October 2026 (UTC)}}
Probably LLM-generated, given broken templates, references to Claude, and section identifiers. This could probably be speedied, but not 100% sure so throwing it to RfD. Even regardless of whether it's LLM-generated or not, I can't see any way it's really suitable for the project. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 07:49, 10 October 2026 (UTC)

:{{vd}} - a book ''about'' chess problems isn't necessarily out of scope, but there needs to be some written content to accompany the problems. And I'm not sure these are even meaningful problems - the few problems with viewable Lichess links appear to be in the early game, so there aren't necessarily objective &quot;solutions&quot; to them. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:51, 10 October 2026 (UTC)
:{{vd}}, the Claude references throughout the book support that it's LLM-generated. [[User:Ternera|Ternera]] ([[User talk:Ternera|discuss]] • [[Special:Contributions/Ternera|contribs]]) 14:55, 11 October 2026 (UTC)
:This looked like a speedy to me, so I went ahead and deleted it. Thanks! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 20:14, 14 October 2026 (UTC)
{{end closed}}

== [[Digital Synthora]] ==
Not within WB scope since it seems to be entirely fabricated by the editor. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:20, 12 October 2026 (UTC)

:{{vd}} While some amount of original research is allowed here, completely fabricated topics aren't. This is just fiction writing, which is nice, but not within our scope. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 15:30, 12 October 2026 (UTC)
:{{vd}} - per my initial tag, this appears to be an invention of the page creator; I can't find anything relevant online beyond the empty https://synthoraactstuff.fandom.com/. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 01:32, 13 October 2026 (UTC)
== [[Wikibooks:FlaggedRevs Extension]] ==
Flagged Revisions is dead. Flagged Revisions remains dead. And we have killed it. How shall we comfort ourselves, the murderers of all murderers? Well, not in the least by deleting its project page and subpages. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 06:16, 17 October 2026 (UTC)

:Would it be better to mark it as historical, or update the page to say it's dead? I only say this because we've used this extension for a ''very'' long time. {{vd}} all the subpages, however. //[[User:SHB|SHB]] ([[User talk:SHB|discuss]] • [[Special:Contributions/SHB|contribs]]) 09:16, 17 October 2026 (UTC)
:: So far, there is only one subpage, [[Wikibooks:FlaggedRevs Extension/Unstable]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:37, 17 October 2026 (UTC)</text>
      <sha1>8qrsur93khoneqpd3imh5lil8ui9ab9</sha1>
    </revision>
    <revision>
      <id>4676569</id>
      <parentid>4676535</parentid>
      <timestamp>2026-10-17T18:33:53Z</timestamp>
      <contributor>
        <username>Omphalographer</username>
        <id>3427146</id>
      </contributor>
      <comment>/* Wikibooks:FlaggedRevs Extension */ Reply</comment>
      <origin>4676569</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="45406" sha1="323u96guoo4o6zcl1hejspy49aoj3qu" xml:space="preserve">__NEWSECTIONLINK__
[[Category:Wikibooks deletion|{{PAGENAME}}]]
{{Discussion Rooms}}
{{TOCleft}}
{{shortcut|WB:RFD}}
{{Requests for deletion/New deletion}}
{{Requests for deletion/Deletion intro}}
&lt;!-- New deletion nominations go at the bottom of page. --&gt;

== [[Salute, Jonathan!]] and its translations ==

&lt;div style=&quot;column-count: 7;&quot;&gt;
* [[Salute, Jonathan!|Interlingue/Occidental]] ([[w:en:Occidental|w]], original)
* [[Òla, Ionatà!|Audià]]
* [[Holo, Jonathan!|Cristianés]]
* [[Terve, Jonathan!|Ekumenski]]
* [[Hej, Jonathan! (Germanisch)|Germanisch]]
* [[Salom, Jonatan!|Globasa]]
* [[Àlŏ, Jonathan!|Guosa]] ([[w:en:Guosa|w]])
* [[Salut, Jonathan!|Idiom Neutral]] ([[w:en:Idiom Neutral|w]])
* [[Saluto, Jonathan! (Ido)|Ido]] ([[w:en:Ido|w]])
* [[Hallo, Jonathan!|Interlingua]] ([[w:en:Interlingua|w]])
* [[Salut, Jonathan! (Interocidental)|Interocidental]]
* [[Bune Ğonatan!|Lingaust]]
* [[Oila, Jonatan!|Lingue Simple]]
* [[Haloo, Jonatan!|Lingwa de Planeta]] ([[w:en:Lingwa de Planeta|w]])
* [[Sin Chao, Jonathan!|Masa Tang]]
* [[Salut, ionatano!|Meteza]]
* [[Salu, Jon!|Mini]]
* [[Hay, Jonathan!|Mirad]]
* [[Hai, Jon!|Monav]]
* [[Sesan Jon!|Monkel]]
* [[Salam, Jonathan!|Mundeze]]
* [[Dag, Jonathan!|Negerhollands]] ([[w:en:Negerhollands|w]])
* [[Salut Jonathan!|Neo]] ([[w:en:Neo|w]])
* [[Hej, Jonathan!|Nordien]]
* [[Saluto, Jonathan!|Novial]] ([[w:en:Novial|w]])
* [[Salute, Jonathan! (Novlingue)|Novlingue]]
* [[Alo, Jonathan!|Numo]]
* [[Hela, Jonathan!|Proyo]]
* [[Salute, Jonathan! (Romanica)|Romanica]] ([[w:en:Romanica|w]])
* [[Simi, Jonathan!|Solresol]] ([[w:en:Solresol|w]])
* [[Toki a, jan Jonatan!|Toki Pona]] ([[w:en:Toki Pona|w]])
* [[Glidis, o Jonathan!|Volapük]] ([[w:en:Volapük|w]])
&lt;/div&gt;

There are a couple of issues here:

# Beyond their introductions, all of these books are written in languages which are not English, making them out of scope for the English Wikibooks.
# All but one of these books are in fact written in constructed languages, most of them in recently created conlangs. In some cases (e.g. [[Sin Chao, Jonathan!]]), I can't find any reliable sources describing the target language outside of the translation itself.
# Most of the translations (i.e. other than [[Salute, Jonathan!]] itself) were abandoned within the first five or so chapters (out of 100); none of them are complete, and there seems to be little effort to complete any of them.

While I recognize that this is an unusual project, and potentially one which could have some value, it's not at all clear to me that the English Wikibooks is the right place for it. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:24, 29 September 2024 (UTC)

: I'm really not sure what to do about these ones. While I recognize that this approach is certainly one method of teaching a language, I'm not sure that it constitutes an educational textbook. We do require that the English Wikibooks be written in English—for language-learning books, this typically means that the instructional parts are in English while the exercises are in the language being taught. I do think that if the language doesn't have much supporting evidence outside the book itself, it can safely be deleted. — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:01, 29 September 2024 (UTC)

: Author of the book here. I originally wanted to put it in the Interlingue Wikibooks https://ie.wikibooks.org/wiki/Principal_p%C3%A1gine but it somehow got locked when I wasn't paying attention and so I ended up putting it here. Getting it unlocked requires going through the process of starting an Incubator and all the rest so I opted for here and then started putting some English-only content once it was done. It's sort of in the same vein as books like Lingua Latina per se Illustrata that have separate versions with teacher notes and whatnot. [[Salute, Jonathan!/Capitul 1 - with notes]] After it was done the auxlang community really took to it which was a nice surprise. I think Ido has the largest number of chapters at the moment at 15.
:If the vast content of this book could be used to justify a quick reopening of the Interlingue Wikibooks to move it there, I'd love to do that. I imagine that an incubator with 100+ book chapters would be enough to open a Wikibooks and that's what this is. — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:02, 29 September 2024 (UTC)

: Ah, I just realized that we do have a proposal to reopen the Interlingue Wikibooks: https://meta.wikimedia.org/wiki/Requests_for_new_languages/Wikibooks_Interlingue along with an Incubator page here. https://incubator.wikimedia.org/wiki/Wb/ie/Principal_p%C3%A1gine
: How easy would it be to migrate the entirety of Salute Jonathan to there? — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:30, 29 September 2024 (UTC)

:: Hi @[[User:Mithridates|Mithridates]]! I'm not sure how incubator projects work, but I fully support migrating these books there. You may want to inquire over there and link to this discussion to support your request to move the content over there. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:16, 29 September 2024 (UTC)

::: Hi! Actually I have a third idea to propose after thinking about this again today (haven't been here much since I finished the book): I noticed that there is more English content than I remember and that might make it an awkward fit for the Interlingue Wikibooks. I definitely agree that having all the auxlang translations for new auxlang projects goes well beyond the scope of this Wikibooks. Finally, there are some auxlangs that are notable with their own Wikipedias.
::: So the idea is the following:
:::# Leave the original here and I can continue the work on the version with English notes and grammar. That will make it the same as Lingua Latina per se Illustrata, English by the Nature Method, Athenaze and all the rest.
:::# The Interlingua one can move to the Interlingua Wikibooks (maybe Romanica too if they want as it is sort of a dialect of Interlingua).
:::# For Ido and Lingua Franca Nova which have a Wikipedia but not a Wikibooks, I'm a little bit unsure...technically they could have their own version like the original one but would require English explanations. I could let them know and see if they are willing to do so and see what they think (work on adding English to the books vs. move the content elsewhere).
:::# The rest can move to a Github repo, then be deleted, and the front page of this book can have a single link to the repo.
::: Any thoughts on that? Adding the extra English content will be easy as it is my book and I know it inside and out.
::: Edit: [https://en.wikibooks.org/wiki/Salute,_Jonathan!/Grammar_(pronouns) this page] I just added.  — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 13:50, 29 September 2024 (UTC)

:::: Thanks for taking the time to consider this! Here are my responses/questions:
::::* Is the original [[Salute, Jonathan!]] (Occidental)? Since that one is quite fleshed out, I agree that if you edit it so the primary language of the book (e.g. headers, instructions, etc) are written in English while leaving the actual story in Occidental, it would be okay and fit in more with instructional language textbooks.
::::* For your points 2 and 3, I'm not sure how those other projects work, so I'll leave it up to them. I'm not quite sure why they would need to move, since in theory they could be revised with English as the language of instruction? Although, they have been left incomplete for a long time.
::::* For your point 4, I have no problem with that. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:51, 29 September 2024 (UTC)

::::: Hello again, it's the weekend so I have a bit more time to work on this. I've decided to merge the extra content from the following five chapters since the difference is fairly small and the original chapters should now have this English content. Could you delete these five pages now that they are no longer needed? [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC)
::::: [[Salute, Jonathan!/Capitul 1 - with notes]]
::::: [[Salute, Jonathan!/Capitul 2 - with notes]]
::::: [[Salute, Jonathan!/Capitul 3 - with notes]]
::::: [[Salute, Jonathan!/Capitul 4 - with notes]]
::::: [[Salute, Jonathan!/Capitul 5 - with notes]] [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC)
:::::: [[File:Yes_check.svg|{{#ifeq:|small|8|15}}px|link=|alt=]] {{#ifeq:|small|&lt;small&gt;|}}'''Done'''{{#ifeq:|small|&lt;/small&gt;|}} — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:34, 5 October 2024 (UTC)

::::::: Hi again! No luck trying to find a home for the random language translations on other auxlang wikis, can't find one that is actively maintained.
::::::: The thought struck me that maybe I could just put those ones on a sub page of my user page, would that be permitted? If not, I think I'll just stick them somewhere in GitHub and call it a day since none of the people who started the translations seem to care enough to do anything about them. I'd rather not see them outright disappear but since they aren't mine I don't care enough about them to do much more work than copy and paste them somewhere.
::::::: (I would leave the ones in languages with an ISO-639 code and Wikipedia here, of course) — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:13, 9 November 2024 (UTC)

:::::::: Thank you for checking! I don't personally see an issue with moving them to your user space right now. Cheers — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:21, 9 November 2024 (UTC)

::::::::: Thanks a lot! I've started a single page where I will put them all here [[User:Mithridates/SJ]] and will proceed slowly due to lack of time and also to avoid stepping on any toes / asking you to delete too much at a time and possibly deleting the wrong content.
::::::::: For this week I have put the content for the languages Audia, Cristianès, Guosa, Lingaust, Mini, Mirad, and Monav on that page as they all have a single page of content and didn't take much time to move. Please delete those. Once they are gone I will add a note on the main page letting people know where they have gone (in addition to a thank you for their interest in the book! I do love how many people have recognized it as a good source material for teaching a language). — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 04:09, 10 November 2024 (UTC)

: {{keep}} the translations for languages that have an article on the English Wikipedia, i.e. Guosa, Idiom Neutral, Ido, Interlingua, Lingwa de Planeta, Negerhollands, Neo, Novial, Occidental, Romanica, Solresol, Toki Pona, and Volapük.
: Translations for languages that don't have an article can be kept if they have reliable sources, which I was able to find for the following languages (if you think they are not reliable, please let me know):
:* Globasa: [https://www.languagesandnumbers.com/how-to-count-in-globasa/en/globasa/] [https://greyson.conlang.org/2020/01/29/shouting-out-globasa-and-pandunia/]
:* Mini: [https://jprogr.github.io/mini] [https://www.omniglot.com/language/phrases/mini.htm] [https://www.languagesandnumbers.com/how-to-count-in-mini/en/mini/]
: {{del}} and move to [[User:Mithridates/SJ]] the rest of the translations, i.e. Audià/Audian, Cristianés, Ekumenski, Germanisch, Interocidental, Lingaust, Lingue Simple, Masa Tang, Mirad, Monav, Monkel, Mundeze, Nordien, Novlingue, Numo, Proyo, and Scuian/Meteza. If you can find reliable sources for those languages, please let me know.
: In particular, I could not find resources for Audià/Audian and Monav after searching through 15 and 17 pages on Google, respectively. It doesn't help that [[Òla, Ionatà!|their]] [[Hai, Jon!|translations]] don't explain what those languages are and where to find resources for them. This makes contributing to those translations almost impossible until @[[User:Caro de Segeda|Caro de Segeda]] can provide resources to us. It's possible that the resources may have disappared from the Internet, or that those languages were created by Caro de Segeda him/herself. If you can find resources for Audià/Audian and Monav, please let me know.
: I'm notifying the primary contributors of the translations: @[[User:Caro de Segeda|Caro de Segeda]], @[[User:Frzzl|Frzzl]], @[[User:Greatscotteh|Greatscotteh]], @[[User:IHateNumbers234|IHateNumbers234]], @[[User:Jayeless2|Jayeless2]], @[[User:Morozof|Morozof]], @[[User:Omnihom|Omnihom]], @[[User:Omoutuazn|Omoutuazn]], @[[User:PovriNaivon|PovriNaivon]], @[[User:Sir Beluga|Sir Beluga]] and @[[User:Tyoyafud|Tyoyafud]]. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 09:52, 30 June 2025 (UTC)

:: Caro de Segeda said on [https://www.reddit.com/r/conlangs/comments/1lcnz9g/comment/n0sc3wx/ Reddit] that Monav was created by him/her and that he/she didn't publish any resources about it other than [[Hai, Jon!]]. With '''zero''' other resources to rely on for contributing to the translation, and the fact that Monav is in [[User:Mithridates/SJ]], [[Hai, Jon!]] should be speedy deleted. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 01:38, 3 July 2025 (UTC)

::: I've undone the speedy deletion as Caro de Segeda posted a [https://prexins.wordpress.com/2025/07/04/monav/ resource] for Monav. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 07:18, 4 July 2025 (UTC)

:::: You can delete all the ones that I have created myself, I have already moved them to other places. — [[User:Caro de Segeda|Caro de Segeda]] ([[User talk:Caro de Segeda|discuss]] • [[Special:Contributions/Caro de Segeda|contribs]]) 12:39, 5 July 2025 (UTC)

{{outdent|::::}}I don't know if this is helpful since it wouldn't apply to most of these, but [[s:mul:]] could hold some of these. — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 09:18, 30 November 2025 (UTC)

: I don't think that would be within the scope of that project. I'm not aware of any other situation where Wikisource publishes translations of texts created on Wikimedia projects - that's usually left up to other language editions of the same project. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 05:34, 1 December 2025 (UTC)

:: In this situation there isn't a separate [[s:ie:]] distinct from Multilingual Wikisource (see [[meta:Wikisource#List of Wikisources]]). In fact, there are very few multilingual wikis in the Wikimedia sphere; while this project ''could'' move to a Miraheze-hosted or similar wiki farm location, I think it would be a missed opportunity. I suppose an [[Interlingue]] book could be started in [[shelf:Constructed languages]] which would have all 100 chapters as an appendix (and likewise for the other languages), but that also seems non-ideal since it requires an English-language text that doesn't currently exist to be created. [[WB:AT]] seems to describe a similar situation to this one and prescribe Wikisource as the solution, and [[WB:SOURCE]] mentions fiction as out-of-scope for Wikibooks (even as in this case, language-educational fiction). [[s:mul:Wikisource:about Wikisource]] simply speaks of source texts and doesn't mention publication requirements, so maybe that is specific to some of the monolingual editions? — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 22:28, 5 December 2025 (UTC)

:{{keep}} 100% keep. These books are a core part of language textbooks on Wikibooks and have been for years. Not sure why this is even being debated.--[[User:Xania|Xania]] [[Image:Flag_of_Estonia.svg|15px]]  [[Image:Flag_of_Ukraine.svg|15px]] [[User talk:Xania|&lt;sup&gt;talk&lt;/sup&gt;]] 17:55, 16 May 2026 (UTC)

::With all due respect, some of the books included in this nomination (like [[Sin Chao, Jonathan!]]) are written in constructed languages which are not substantially attested anywhere else. I struggle to imagine any educational purpose for such a book. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:12, 17 May 2026 (UTC)

== [[International Baccalaureate]] ==

Not actually a book in and of itself; rather, it is just a compilation of links to other books —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:24, 18 October 2024 (UTC)
: Could this be salvaged as a shelf? [[User:Pppery|Pppery]] ([[User talk:Pppery|discuss]] • [[Special:Contributions/Pppery|contribs]]) 05:23, 27 January 2025 (UTC)
::Probably, but are the linked books even useful? IB exams change from year to year - sometimes quite dramatically - so an old exam guide is of very limited value. Many of these books were written 10-15 years ago, and some of them (like [[IB French]]) even have comments indicating that they're no longer applicable. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 02:18, 8 December 2025 (UTC)
:I  would be interested in a book that explains what an [[International Baccalaureate]] is. They may be books about it in the real world, but they are not free and with the online world becoming a fortress of paywalls I wonder how much longer one would be able to find such information on the web. This is what the  wikipedia article says:
:* This article '''is missing information''' about the educational programs and curricula. Please expand the article to include this information. Further details may exist on the [[wikipedia:Talk:International_Baccalaureate#|talk page]].  ''(March 2025)''
:[[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 02:05, 13 October 2026 (UTC)

== [[Character List for Baxter&amp;Sagart]] ==

Seems completely out of scope as an educational book; it's just a list of characters and outlinks —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:53, 18 October 2024 (UTC)

:Adding [[Character List for Karlgren's GSR]] and [[Character List for Schuessler's CGSR]] for the same reason —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:55, 18 October 2024 (UTC)

:These three books do make a package and I agree they should be considered together. However, I strongly object to deleting them. They are really extremely useful resources. I use them every week and I know that many people who do work on Old Chinese phonology do so. There are lots of books out there that are lists of characters, these are called dictionaries. For example Axel Schuessler's ABC Etymological Dictionary of Old Chinese, or Pulleyblank's Lexicon of Reconstructed Pronunciation in Early Middle Chinese, Late Middle Chinese, and Early Mandarin. I see it as entirely a good thing for reference works of this kind to be available free online rather than only in expensive books in university research libraries. If this is in violation of a Wikibooks policy, I would at least like that policy to be drawn to my attention and to have some constructive comment offered about which Wikiproject such a resource should fall under. I will also say on a personal note that I have put literally hundreds of hours of work into these projects and it would grieve me a lot to see this work simply vanish, in particular when I know that colleagues around the world use these books. --[[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 07:27, 1 November 2024 (UTC)
::Hi @[[User:Tibetologist|Tibetologist]], and thank you for the feedback! Official Wikibooks policy does not permit standalone dictionaries (see [[WB:DICT]]), though I understand the argument that it is a useful resource. I am wondering if there might be a home for it at [[Wiktionary:Wiktionary:Welcome, newcomers|Wiktionary]] or [[Wikiversity:Wikiversity:SHARE|Wikiversity]]? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 12:14, 1 November 2024 (UTC)
:::The policy says to use Wiktionary, but these books cannot be moved there. In fact they link there, you can understand me as having made an index to wiktionary, if you like, where the ORDER of the characters is extremely important, information that would be lost in Wiktionary. 
:::Wikiversity is not a project I participate in, and in any event my books here are older than it, so this option was not available for me at the relevant moment. If you are offering to move my books to Wikiversity, that is very kind of you and I will very graciously accept. [[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 14:10, 1 November 2024 (UTC)
::::I have pinged over at Wikiversity Colloquium to ask about suitability and have looped you into the conversation over there. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:20, 1 November 2024 (UTC)
::I concur. I'm just an undergrad who tries to learn about Sino-Tibetan historical linguistics in his free time but I've found this wikibook to be incredibly useful, and I keep it open in one tab while I watch Professor Nathan Hill's lectures that he uploads to youtube in another tab, and another tab for taking notes. In fact if I remember correctly Professor Hill actually pointed his students to this wikibook. 
::I'm not familiar with [[wikiversity:Wikiversity:SHARE|Wikiversity]] but if all the content were as accessible there as it is here then I think that could work.  [[User:ChromeBones|ChromeBones]] ([[User talk:ChromeBones|discuss]] • [[Special:Contributions/ChromeBones|contribs]]) 02:43, 9 July 2025 (UTC)
:Per [[:v:Wikiversity:Colloquium#Import_Resource_From_Wikibooks?]], I recommend copying and pasting, including attribution via the edit summary and talk page, add appropriate categories and links, and then it could be deleted locally. —[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''vf&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 22:32, 3 November 2024 (UTC)

== [[Suomen kieli käyttöön]] ==

Multiple pages in this book are written entirely in Finnish, which is out of the enWB scope. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:09, 19 October 2024 (UTC)

:I was going to say whether we should ask any fiwikibooks sysop to maybe see if this could be transwikied to fiwb if it's within the scope there. But [[:fi:Toiminnot:Käyttäjät/sysop]] indicates that there are only 3 sysops, and only {{u|Anr}} and {{u|Zache}} have made edits this ''year''. If they deem it to be salvageable, then transwiki + delete, otherwise straight-up delete. --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 11:24, 14 November 2024 (UTC)
::It seems that the idea behind the book was for the pages to be bilingual, as it’s a language learning book. That’s why there are Finnish texts included intentionally even on the pages that are complete. There are similar books in dewikibooks and ruwikibooks as well. For the English version, I think the easiest way to proceed would be to clean up and adjust the page layout to fit enwikibooks better, and then translate the missing parts. By the way, if anyone wants to update the book’s name in English, it can be titled ''&quot;Using the Finnish Language&quot;'' or ''&quot;Put Finnish Language into Use&quot;'' for a direct translation.   [[User:Zache|Zache]] ([[User talk:Zache|discuss]] • [[Special:Contributions/Zache|contribs]]) 11:57, 14 November 2024 (UTC)

== [[AT&amp;T Mobility FAQ]] ==

* [[AT&amp;T Mobility FAQ]]
* [[AT&amp;T Mobility FAQ/MEdia Net Configuration]]
* [[AT&amp;T Mobility FAQ/Data Connect Configuration]]
An ''extremely'' outdated FAQ on AT&amp;T's cell phone services. Most of this document was written 20+ years ago as a Usenet FAQ; very little of it is accurate or useful anymore (particularly the two subpages, which have to do with obsolete configurations for &quot;tethering&quot; a computer to a cell phone). No objection if someone wants to update it, but there's clearly been no appetite to do that. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 22:20, 30 December 2024 (UTC)

:I'm wondering if it might make sense for us to develop some kind of policy on archiving books here. There are many like this one that have a good deal of content but are extremely out of date and just not useful as originally intended. ——[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:34, 30 December 2024 (UTC)
::@[[User:Kittycataclysm|Kittycataclysm]]: See the newly developed [[Wikibooks:Outdated books]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 00:16, 31 December 2024 (UTC)
:::Ooh, thanks - something like that seems like it could be an appropriate way to handle this book. A lot of the other outdated books I've tagged have been so incomplete that they wouldn't have been particularly useful even as historical references; this one might at least have some interest.
:::Any chance we can get a separate namespace (maybe &quot;Archive:&quot;) set up for archived book content? That'd make it possible to do things like exclude them from on-site search by default. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:07, 31 December 2024 (UTC)
::::I think this might be a more extended discussion, so I'll bump it over to the [[Wikibooks talk:Outdated books|talk page of the draft policy]]! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:54, 31 December 2024 (UTC)

== Algebra/Chapter 10/Symmetric Polynomials ==

I personally believe that [[Algebra/Chapter 10/Symmetric Polynomials|this]], and all of the sections should be deleted for the fact that this goes WAY beyond the scope of what was intended for the Chapter (Algebra II level polynomials). [[User:GoreyCat|GoreyCat]] ([[User talk:GoreyCat|discuss]] • [[Special:Contributions/GoreyCat|contribs]]) 15:07, 6 February 2025 (UTC)

:'''Split''': Deletion here is not the best solution (see [[w:WP:ATD]]). Instead, this page and its subpages should be moved to another book, most likely [[Abstract Algebra]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 17:35, 6 February 2025 (UTC)
:{{keep}} since there is a good amount of content. If [[Abstract Algebra]] is appropriate, it seems like a fine idea to move there. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:59, 7 February 2025 (UTC)
::Eh, yeah, I supposed moving it is better. I just don't think it's suitable for where it appears. [[User:GoreyCat|GoreyCat]] ([[User talk:GoreyCat|discuss]] • [[Special:Contributions/GoreyCat|contribs]]) 01:40, 8 February 2025 (UTC)
== [[Puredyne]] ==

Development of Puredyne Linux was discontinued in 2012, and the software no longer appears to be available for download anywhere. (An archive of the web site is still up - with a bunch of embedded spam links - but the download links are all dead.) Is this a suitable candidate for archival (cf. [[Wikibooks:Outdated books]]), or should it just be deleted? [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 04:35, 5 March 2025 (UTC)

:I'd just archive stuff like this. Looks like a decent bit of work went into it, and you never know when someone might need to use Puredyne for some obscure project. I'd be willing to bet mirrors exist of it somewhere, or someone has it on a drive. If you want to find some stuff worth deleting, comb through [[:Category:Allbooks categories]]. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:30, 5 March 2025 (UTC)

== [[Template:Qr-twwp]] ==
This isn't exactly a request to delete the template, but rather to merge it with {{tlx|Copypaste}}. The {{tlx|Qr-twwp}} template serves the same purpose as {{tlx|Copypaste}}, but without the seven-day period after which the page is deleted. This leads to confusion, as well as a perpetually full [[:Category:Queried pages]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 17:37, 30 March 2025 (UTC)

== [[Ghouls of the Miskatonic]] ==

I don't think that a plot summary of a book is in-scope here. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:43, 20 August 2025 (UTC)

:{{vd}} - at least, not a summary of ''this'' book. A summary and/or study guide to a notable work of literature might be in scope, but this is certainly not one. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:23, 25 August 2025 (UTC)
::Hi. I am the creator of the pages of this book. If I understand correctly, it has to be a summary of a notable work of literature? So what exactly is defined as such? I only started this as I thought it would be fun, interesting and encouraging to others who read the Arkham Horror novels, and I thought it was permitted as I've seen other summaries of books on wikibooks. [[User:Dayne90|Dayne90]] ([[User talk:Dayne90|discuss]] • [[Special:Contributions/Dayne90|contribs]]) 13:27, 26 August 2025 (UTC)
:::Your problem is it is just the plot... it needs to include an educational textual analysis to be in scope [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 12:47, 28 August 2025 (UTC)
::::And ideally it'd be a text which has ''already'' been the subject of literary analysis, such that the analysis on Wikibooks isn't original research. A notable work of literature like ''Frankenstein'' or ''Moby-Dick'' would easily meet that requirement; a tie-in novel for a tabletop RPG probably does not. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 22:08, 29 August 2025 (UTC)

== [[A-level Computing AQA Paper 1 Skeleton program 2027]] ==
{{closed|Considering the recent comments and due to no objections, I converted it to a soft redirect until another admin decides if the page can be deleted. CC to [[user:MrBerard|MrBerard]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:51, 15 October 2026 (UTC)}}
This was proposed for speedy deletion by [[User:Omphalographer]] as 'not being a book'. However, I think this page's future requires further discussion from the community. Maybe some input would be appreciated?[[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 23:51, 21 September 2026 (UTC)

:As best I can tell, this is a page students are using to collaborate on solutions for a standardized test. There are a number of similar pages for other years linked from [[A-level Computing/AQA/Paper 1/Skeleton program]].
:This is not a good fit for Wikibooks. If these students are interested in this kind of collaboration, it should take place elsewhere. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:14, 22 September 2026 (UTC)
::The project can be moved to Wikiversity, I think. If the students can contribute it and make sure it complies with Wikibooks' guidelines, it can stay here. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:17, 22 September 2026 (UTC)
:::@[[User:Omphalographer|Omphalographer]] @[[User:TechVindicator|TechVindicator]]
:::There's been a Wikibook on this every single year, as I mentioned in my comment on the deletion notice. That doesn't mean that this shouldn't be on Wikiversity, just that there is ample precedent of it being a Wikibook.  Dunno if this matter to those kind of editorial decisions, though. [[Special:Contributions/~2026-51010-27|~2026-51010-27]] ([[User talk:~2026-51010-27|talk]]) 13:39, 22 September 2026 (UTC)
::::@[[User:~2026-51010-27|~2026-51010-27]]: How would the page comply with [[WB:What is Wikibooks?|Wikibooks' mission]]?. Could you provide an explanation of what the project is?  If it's a collaborative project to work on solutions for a standardized test (like @[[User:Omphalographer|Omphalographer]] said), it would be more suitable for Wikiversity. If it's a textbook about A-level computing, then it would be suitable here. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:58, 22 September 2026 (UTC)
:::::Hi,
:::::This is definitely the former, not the latter. As I said, I don't particularly think this should be on Wikibooks, it just happens the previous years had been, and clearly they weren't subject to this degree of scrutiny 😅
:::::I have created https://en.wikiversity.org/wiki/A-level_Computer_Science_AQA_Paper_1_Skeleton_program_2027 - I'll delete the content of the page and put the link at the top. If there is a more appropriate banner to indicate the migration, please make it look how it should :D [[User:MrBerard|MrBerard]] ([[User talk:MrBerard|discuss]] • [[Special:Contributions/MrBerard|contribs]]) 10:23, 29 September 2026 (UTC)
::::::I can't seem to put a link without the edit being deemed destructive, so I'll let you trusted people do what's needed. [[User:MrBerard|MrBerard]] ([[User talk:MrBerard|discuss]] • [[Special:Contributions/MrBerard|contribs]]) 10:27, 29 September 2026 (UTC)
: {{comment}}: I cannot determine consensus in this request on whether or not it should either be deleted or imported to English Wikiversity. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:28, 13 October 2026 (UTC)
::I've actioned the migration to Wikiversity as per my comment of 29 sep. I'd rather this stayed in as a stub with a link to the Wikiversity entry, for a couple of months, though I'm sure search engines are still vaguely good enough that this shouldn't matter too much. [[User:MrBerard|MrBerard]] ([[User talk:MrBerard|discuss]] • [[Special:Contributions/MrBerard|contribs]]) 14:35, 13 October 2026 (UTC)
{{end closed}}

== [[Talmudic aramic]] ==
{{closed|Deleted per consensus below. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:18, 13 October 2026 (UTC)}}
Per the user's other mass-created pages, I concur with the AI flagging that Kittycataclysm placed on the page. I believe this to be LLM-generated, and it should thus be deleted. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 03:29, 30 September 2026 (UTC)

:{{vd}}, LLM spam. [[User:Ternera|Ternera]] ([[User talk:Ternera|discuss]] • [[Special:Contributions/Ternera|contribs]]) 13:22, 30 September 2026 (UTC)
:{{vd}} - like most LLM-generated books, this is heavy on structure and light on substance. Most of the content amounts to a poorly organized glossary, and there are a lot of pieces missing. (For instance, there is no discussion of the grammar of the language beyond a couple of fixed expressions.) [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:11, 1 October 2026 (UTC)
:{{vd}} per stated reasoning. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:43, 12 October 2026 (UTC)
{{end closed}}

== [[Job Search]] ==
{{closed|Per minimal consensus, I deleted these books, but I only kept the main pages of these books by creating them as redirects for [[Find Employment]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:24, 13 October 2026 (UTC)}}
* as well as [[Job Search Automation for College Students]].

Neither of these books contains any useful information. The first book seems to be written primarily to funnel users to the second, and the second to funnel users to [[PlanoTse Handbook for Job Search Automation]], which was deleted last year. (The deletion request doesn't seem to have been archived.)

The sum total of information in these two books is, essentially, &quot;you can search for jobs online&quot;, which is insultingly trivial. The second book's suggestion that users automate the job search process is of no practical value; most web search engines and job search sites nowadays will detect and block automated access.

[[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:36, 1 October 2026 (UTC)
: {{vd}} and redirect to [[Find Employment]]. ‑‑[[User:Kai Burghardt|Kai Burghardt]] ([[User talk:Kai Burghardt|discuss]] • [[Special:Contributions/Kai Burghardt|contribs]]) 05:14, 2 October 2026 (UTC)
{{end closed}}

== [[Wikipage]] ==
{{closed|Deleted per minimal consensus below. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:26, 13 October 2026 (UTC)}}
Like a few other books created by this user, the purpose of this book appears to have been to promote a piece of software written by the author ([[User:Planotse]]). The software is no longer available, and there is no actual content in the book.

[[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:40, 1 October 2026 (UTC)

:{{Vd}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 15:30, 12 October 2026 (UTC)
{{end closed}}

== [[Becoming a Linguistic Mastermind]] ==
{{closed|Deleted. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:11, 15 October 2026 (UTC)}}
Old book (created 2007) with no substantial content. The intent of this book appears to have been to create a single textbook encompassing ''all'' languages, with sub-courses for each language at [[Becoming a Linguistic Mastermind/The courses]], but no such courses were ever created. An analogous project on dewikibooks [[:b:de:Wikibooks:Löschkandidaten/ 2011-04#Der einfache Weg zum Sprachgenie|was deleted in 2011 for similar reasons]]. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:20, 7 October 2026 (UTC)

:{{Vd}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 15:30, 12 October 2026 (UTC)
{{end closed}}

== [[The Permanent Advantage]] ==
{{closed|Speedily deleted —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 20:15, 14 October 2026 (UTC)}}
Probably LLM-generated, given broken templates, references to Claude, and section identifiers. This could probably be speedied, but not 100% sure so throwing it to RfD. Even regardless of whether it's LLM-generated or not, I can't see any way it's really suitable for the project. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 07:49, 10 October 2026 (UTC)

:{{vd}} - a book ''about'' chess problems isn't necessarily out of scope, but there needs to be some written content to accompany the problems. And I'm not sure these are even meaningful problems - the few problems with viewable Lichess links appear to be in the early game, so there aren't necessarily objective &quot;solutions&quot; to them. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:51, 10 October 2026 (UTC)
:{{vd}}, the Claude references throughout the book support that it's LLM-generated. [[User:Ternera|Ternera]] ([[User talk:Ternera|discuss]] • [[Special:Contributions/Ternera|contribs]]) 14:55, 11 October 2026 (UTC)
:This looked like a speedy to me, so I went ahead and deleted it. Thanks! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 20:14, 14 October 2026 (UTC)
{{end closed}}

== [[Digital Synthora]] ==
Not within WB scope since it seems to be entirely fabricated by the editor. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:20, 12 October 2026 (UTC)

:{{vd}} While some amount of original research is allowed here, completely fabricated topics aren't. This is just fiction writing, which is nice, but not within our scope. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 15:30, 12 October 2026 (UTC)
:{{vd}} - per my initial tag, this appears to be an invention of the page creator; I can't find anything relevant online beyond the empty https://synthoraactstuff.fandom.com/. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 01:32, 13 October 2026 (UTC)
== [[Wikibooks:FlaggedRevs Extension]] ==
Flagged Revisions is dead. Flagged Revisions remains dead. And we have killed it. How shall we comfort ourselves, the murderers of all murderers? Well, not in the least by deleting its project page and subpages. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 06:16, 17 October 2026 (UTC)

:Would it be better to mark it as historical, or update the page to say it's dead? I only say this because we've used this extension for a ''very'' long time. {{vd}} all the subpages, however. //[[User:SHB|SHB]] ([[User talk:SHB|discuss]] • [[Special:Contributions/SHB|contribs]]) 09:16, 17 October 2026 (UTC)
:: So far, there is only one subpage, [[Wikibooks:FlaggedRevs Extension/Unstable]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:37, 17 October 2026 (UTC)
:::Mark both as historical. I don't see any compelling reason to delete them. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:33, 17 October 2026 (UTC)</text>
      <sha1>323u96guoo4o6zcl1hejspy49aoj3qu</sha1>
    </revision>
    <revision>
      <id>4676571</id>
      <parentid>4676569</parentid>
      <timestamp>2026-10-17T18:37:33Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>/* Wikibooks:FlaggedRevs Extension */ reply ([[mw:c:Special:MyLanguage/User:JWBTH/CD|CD]])</comment>
      <origin>4676571</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="45685" sha1="gesapyiqv1ls4ird5o7pfxgqq74q4mw" xml:space="preserve">__NEWSECTIONLINK__
[[Category:Wikibooks deletion|{{PAGENAME}}]]
{{Discussion Rooms}}
{{TOCleft}}
{{shortcut|WB:RFD}}
{{Requests for deletion/New deletion}}
{{Requests for deletion/Deletion intro}}
&lt;!-- New deletion nominations go at the bottom of page. --&gt;

== [[Salute, Jonathan!]] and its translations ==

&lt;div style=&quot;column-count: 7;&quot;&gt;
* [[Salute, Jonathan!|Interlingue/Occidental]] ([[w:en:Occidental|w]], original)
* [[Òla, Ionatà!|Audià]]
* [[Holo, Jonathan!|Cristianés]]
* [[Terve, Jonathan!|Ekumenski]]
* [[Hej, Jonathan! (Germanisch)|Germanisch]]
* [[Salom, Jonatan!|Globasa]]
* [[Àlŏ, Jonathan!|Guosa]] ([[w:en:Guosa|w]])
* [[Salut, Jonathan!|Idiom Neutral]] ([[w:en:Idiom Neutral|w]])
* [[Saluto, Jonathan! (Ido)|Ido]] ([[w:en:Ido|w]])
* [[Hallo, Jonathan!|Interlingua]] ([[w:en:Interlingua|w]])
* [[Salut, Jonathan! (Interocidental)|Interocidental]]
* [[Bune Ğonatan!|Lingaust]]
* [[Oila, Jonatan!|Lingue Simple]]
* [[Haloo, Jonatan!|Lingwa de Planeta]] ([[w:en:Lingwa de Planeta|w]])
* [[Sin Chao, Jonathan!|Masa Tang]]
* [[Salut, ionatano!|Meteza]]
* [[Salu, Jon!|Mini]]
* [[Hay, Jonathan!|Mirad]]
* [[Hai, Jon!|Monav]]
* [[Sesan Jon!|Monkel]]
* [[Salam, Jonathan!|Mundeze]]
* [[Dag, Jonathan!|Negerhollands]] ([[w:en:Negerhollands|w]])
* [[Salut Jonathan!|Neo]] ([[w:en:Neo|w]])
* [[Hej, Jonathan!|Nordien]]
* [[Saluto, Jonathan!|Novial]] ([[w:en:Novial|w]])
* [[Salute, Jonathan! (Novlingue)|Novlingue]]
* [[Alo, Jonathan!|Numo]]
* [[Hela, Jonathan!|Proyo]]
* [[Salute, Jonathan! (Romanica)|Romanica]] ([[w:en:Romanica|w]])
* [[Simi, Jonathan!|Solresol]] ([[w:en:Solresol|w]])
* [[Toki a, jan Jonatan!|Toki Pona]] ([[w:en:Toki Pona|w]])
* [[Glidis, o Jonathan!|Volapük]] ([[w:en:Volapük|w]])
&lt;/div&gt;

There are a couple of issues here:

# Beyond their introductions, all of these books are written in languages which are not English, making them out of scope for the English Wikibooks.
# All but one of these books are in fact written in constructed languages, most of them in recently created conlangs. In some cases (e.g. [[Sin Chao, Jonathan!]]), I can't find any reliable sources describing the target language outside of the translation itself.
# Most of the translations (i.e. other than [[Salute, Jonathan!]] itself) were abandoned within the first five or so chapters (out of 100); none of them are complete, and there seems to be little effort to complete any of them.

While I recognize that this is an unusual project, and potentially one which could have some value, it's not at all clear to me that the English Wikibooks is the right place for it. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:24, 29 September 2024 (UTC)

: I'm really not sure what to do about these ones. While I recognize that this approach is certainly one method of teaching a language, I'm not sure that it constitutes an educational textbook. We do require that the English Wikibooks be written in English—for language-learning books, this typically means that the instructional parts are in English while the exercises are in the language being taught. I do think that if the language doesn't have much supporting evidence outside the book itself, it can safely be deleted. — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:01, 29 September 2024 (UTC)

: Author of the book here. I originally wanted to put it in the Interlingue Wikibooks https://ie.wikibooks.org/wiki/Principal_p%C3%A1gine but it somehow got locked when I wasn't paying attention and so I ended up putting it here. Getting it unlocked requires going through the process of starting an Incubator and all the rest so I opted for here and then started putting some English-only content once it was done. It's sort of in the same vein as books like Lingua Latina per se Illustrata that have separate versions with teacher notes and whatnot. [[Salute, Jonathan!/Capitul 1 - with notes]] After it was done the auxlang community really took to it which was a nice surprise. I think Ido has the largest number of chapters at the moment at 15.
:If the vast content of this book could be used to justify a quick reopening of the Interlingue Wikibooks to move it there, I'd love to do that. I imagine that an incubator with 100+ book chapters would be enough to open a Wikibooks and that's what this is. — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:02, 29 September 2024 (UTC)

: Ah, I just realized that we do have a proposal to reopen the Interlingue Wikibooks: https://meta.wikimedia.org/wiki/Requests_for_new_languages/Wikibooks_Interlingue along with an Incubator page here. https://incubator.wikimedia.org/wiki/Wb/ie/Principal_p%C3%A1gine
: How easy would it be to migrate the entirety of Salute Jonathan to there? — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:30, 29 September 2024 (UTC)

:: Hi @[[User:Mithridates|Mithridates]]! I'm not sure how incubator projects work, but I fully support migrating these books there. You may want to inquire over there and link to this discussion to support your request to move the content over there. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:16, 29 September 2024 (UTC)

::: Hi! Actually I have a third idea to propose after thinking about this again today (haven't been here much since I finished the book): I noticed that there is more English content than I remember and that might make it an awkward fit for the Interlingue Wikibooks. I definitely agree that having all the auxlang translations for new auxlang projects goes well beyond the scope of this Wikibooks. Finally, there are some auxlangs that are notable with their own Wikipedias.
::: So the idea is the following:
:::# Leave the original here and I can continue the work on the version with English notes and grammar. That will make it the same as Lingua Latina per se Illustrata, English by the Nature Method, Athenaze and all the rest.
:::# The Interlingua one can move to the Interlingua Wikibooks (maybe Romanica too if they want as it is sort of a dialect of Interlingua).
:::# For Ido and Lingua Franca Nova which have a Wikipedia but not a Wikibooks, I'm a little bit unsure...technically they could have their own version like the original one but would require English explanations. I could let them know and see if they are willing to do so and see what they think (work on adding English to the books vs. move the content elsewhere).
:::# The rest can move to a Github repo, then be deleted, and the front page of this book can have a single link to the repo.
::: Any thoughts on that? Adding the extra English content will be easy as it is my book and I know it inside and out.
::: Edit: [https://en.wikibooks.org/wiki/Salute,_Jonathan!/Grammar_(pronouns) this page] I just added.  — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 13:50, 29 September 2024 (UTC)

:::: Thanks for taking the time to consider this! Here are my responses/questions:
::::* Is the original [[Salute, Jonathan!]] (Occidental)? Since that one is quite fleshed out, I agree that if you edit it so the primary language of the book (e.g. headers, instructions, etc) are written in English while leaving the actual story in Occidental, it would be okay and fit in more with instructional language textbooks.
::::* For your points 2 and 3, I'm not sure how those other projects work, so I'll leave it up to them. I'm not quite sure why they would need to move, since in theory they could be revised with English as the language of instruction? Although, they have been left incomplete for a long time.
::::* For your point 4, I have no problem with that. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:51, 29 September 2024 (UTC)

::::: Hello again, it's the weekend so I have a bit more time to work on this. I've decided to merge the extra content from the following five chapters since the difference is fairly small and the original chapters should now have this English content. Could you delete these five pages now that they are no longer needed? [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC)
::::: [[Salute, Jonathan!/Capitul 1 - with notes]]
::::: [[Salute, Jonathan!/Capitul 2 - with notes]]
::::: [[Salute, Jonathan!/Capitul 3 - with notes]]
::::: [[Salute, Jonathan!/Capitul 4 - with notes]]
::::: [[Salute, Jonathan!/Capitul 5 - with notes]] [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC)
:::::: [[File:Yes_check.svg|{{#ifeq:|small|8|15}}px|link=|alt=]] {{#ifeq:|small|&lt;small&gt;|}}'''Done'''{{#ifeq:|small|&lt;/small&gt;|}} — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:34, 5 October 2024 (UTC)

::::::: Hi again! No luck trying to find a home for the random language translations on other auxlang wikis, can't find one that is actively maintained.
::::::: The thought struck me that maybe I could just put those ones on a sub page of my user page, would that be permitted? If not, I think I'll just stick them somewhere in GitHub and call it a day since none of the people who started the translations seem to care enough to do anything about them. I'd rather not see them outright disappear but since they aren't mine I don't care enough about them to do much more work than copy and paste them somewhere.
::::::: (I would leave the ones in languages with an ISO-639 code and Wikipedia here, of course) — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:13, 9 November 2024 (UTC)

:::::::: Thank you for checking! I don't personally see an issue with moving them to your user space right now. Cheers — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:21, 9 November 2024 (UTC)

::::::::: Thanks a lot! I've started a single page where I will put them all here [[User:Mithridates/SJ]] and will proceed slowly due to lack of time and also to avoid stepping on any toes / asking you to delete too much at a time and possibly deleting the wrong content.
::::::::: For this week I have put the content for the languages Audia, Cristianès, Guosa, Lingaust, Mini, Mirad, and Monav on that page as they all have a single page of content and didn't take much time to move. Please delete those. Once they are gone I will add a note on the main page letting people know where they have gone (in addition to a thank you for their interest in the book! I do love how many people have recognized it as a good source material for teaching a language). — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 04:09, 10 November 2024 (UTC)

: {{keep}} the translations for languages that have an article on the English Wikipedia, i.e. Guosa, Idiom Neutral, Ido, Interlingua, Lingwa de Planeta, Negerhollands, Neo, Novial, Occidental, Romanica, Solresol, Toki Pona, and Volapük.
: Translations for languages that don't have an article can be kept if they have reliable sources, which I was able to find for the following languages (if you think they are not reliable, please let me know):
:* Globasa: [https://www.languagesandnumbers.com/how-to-count-in-globasa/en/globasa/] [https://greyson.conlang.org/2020/01/29/shouting-out-globasa-and-pandunia/]
:* Mini: [https://jprogr.github.io/mini] [https://www.omniglot.com/language/phrases/mini.htm] [https://www.languagesandnumbers.com/how-to-count-in-mini/en/mini/]
: {{del}} and move to [[User:Mithridates/SJ]] the rest of the translations, i.e. Audià/Audian, Cristianés, Ekumenski, Germanisch, Interocidental, Lingaust, Lingue Simple, Masa Tang, Mirad, Monav, Monkel, Mundeze, Nordien, Novlingue, Numo, Proyo, and Scuian/Meteza. If you can find reliable sources for those languages, please let me know.
: In particular, I could not find resources for Audià/Audian and Monav after searching through 15 and 17 pages on Google, respectively. It doesn't help that [[Òla, Ionatà!|their]] [[Hai, Jon!|translations]] don't explain what those languages are and where to find resources for them. This makes contributing to those translations almost impossible until @[[User:Caro de Segeda|Caro de Segeda]] can provide resources to us. It's possible that the resources may have disappared from the Internet, or that those languages were created by Caro de Segeda him/herself. If you can find resources for Audià/Audian and Monav, please let me know.
: I'm notifying the primary contributors of the translations: @[[User:Caro de Segeda|Caro de Segeda]], @[[User:Frzzl|Frzzl]], @[[User:Greatscotteh|Greatscotteh]], @[[User:IHateNumbers234|IHateNumbers234]], @[[User:Jayeless2|Jayeless2]], @[[User:Morozof|Morozof]], @[[User:Omnihom|Omnihom]], @[[User:Omoutuazn|Omoutuazn]], @[[User:PovriNaivon|PovriNaivon]], @[[User:Sir Beluga|Sir Beluga]] and @[[User:Tyoyafud|Tyoyafud]]. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 09:52, 30 June 2025 (UTC)

:: Caro de Segeda said on [https://www.reddit.com/r/conlangs/comments/1lcnz9g/comment/n0sc3wx/ Reddit] that Monav was created by him/her and that he/she didn't publish any resources about it other than [[Hai, Jon!]]. With '''zero''' other resources to rely on for contributing to the translation, and the fact that Monav is in [[User:Mithridates/SJ]], [[Hai, Jon!]] should be speedy deleted. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 01:38, 3 July 2025 (UTC)

::: I've undone the speedy deletion as Caro de Segeda posted a [https://prexins.wordpress.com/2025/07/04/monav/ resource] for Monav. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 07:18, 4 July 2025 (UTC)

:::: You can delete all the ones that I have created myself, I have already moved them to other places. — [[User:Caro de Segeda|Caro de Segeda]] ([[User talk:Caro de Segeda|discuss]] • [[Special:Contributions/Caro de Segeda|contribs]]) 12:39, 5 July 2025 (UTC)

{{outdent|::::}}I don't know if this is helpful since it wouldn't apply to most of these, but [[s:mul:]] could hold some of these. — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 09:18, 30 November 2025 (UTC)

: I don't think that would be within the scope of that project. I'm not aware of any other situation where Wikisource publishes translations of texts created on Wikimedia projects - that's usually left up to other language editions of the same project. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 05:34, 1 December 2025 (UTC)

:: In this situation there isn't a separate [[s:ie:]] distinct from Multilingual Wikisource (see [[meta:Wikisource#List of Wikisources]]). In fact, there are very few multilingual wikis in the Wikimedia sphere; while this project ''could'' move to a Miraheze-hosted or similar wiki farm location, I think it would be a missed opportunity. I suppose an [[Interlingue]] book could be started in [[shelf:Constructed languages]] which would have all 100 chapters as an appendix (and likewise for the other languages), but that also seems non-ideal since it requires an English-language text that doesn't currently exist to be created. [[WB:AT]] seems to describe a similar situation to this one and prescribe Wikisource as the solution, and [[WB:SOURCE]] mentions fiction as out-of-scope for Wikibooks (even as in this case, language-educational fiction). [[s:mul:Wikisource:about Wikisource]] simply speaks of source texts and doesn't mention publication requirements, so maybe that is specific to some of the monolingual editions? — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 22:28, 5 December 2025 (UTC)

:{{keep}} 100% keep. These books are a core part of language textbooks on Wikibooks and have been for years. Not sure why this is even being debated.--[[User:Xania|Xania]] [[Image:Flag_of_Estonia.svg|15px]]  [[Image:Flag_of_Ukraine.svg|15px]] [[User talk:Xania|&lt;sup&gt;talk&lt;/sup&gt;]] 17:55, 16 May 2026 (UTC)

::With all due respect, some of the books included in this nomination (like [[Sin Chao, Jonathan!]]) are written in constructed languages which are not substantially attested anywhere else. I struggle to imagine any educational purpose for such a book. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:12, 17 May 2026 (UTC)

== [[International Baccalaureate]] ==

Not actually a book in and of itself; rather, it is just a compilation of links to other books —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:24, 18 October 2024 (UTC)
: Could this be salvaged as a shelf? [[User:Pppery|Pppery]] ([[User talk:Pppery|discuss]] • [[Special:Contributions/Pppery|contribs]]) 05:23, 27 January 2025 (UTC)
::Probably, but are the linked books even useful? IB exams change from year to year - sometimes quite dramatically - so an old exam guide is of very limited value. Many of these books were written 10-15 years ago, and some of them (like [[IB French]]) even have comments indicating that they're no longer applicable. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 02:18, 8 December 2025 (UTC)
:I  would be interested in a book that explains what an [[International Baccalaureate]] is. They may be books about it in the real world, but they are not free and with the online world becoming a fortress of paywalls I wonder how much longer one would be able to find such information on the web. This is what the  wikipedia article says:
:* This article '''is missing information''' about the educational programs and curricula. Please expand the article to include this information. Further details may exist on the [[wikipedia:Talk:International_Baccalaureate#|talk page]].  ''(March 2025)''
:[[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 02:05, 13 October 2026 (UTC)

== [[Character List for Baxter&amp;Sagart]] ==

Seems completely out of scope as an educational book; it's just a list of characters and outlinks —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:53, 18 October 2024 (UTC)

:Adding [[Character List for Karlgren's GSR]] and [[Character List for Schuessler's CGSR]] for the same reason —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:55, 18 October 2024 (UTC)

:These three books do make a package and I agree they should be considered together. However, I strongly object to deleting them. They are really extremely useful resources. I use them every week and I know that many people who do work on Old Chinese phonology do so. There are lots of books out there that are lists of characters, these are called dictionaries. For example Axel Schuessler's ABC Etymological Dictionary of Old Chinese, or Pulleyblank's Lexicon of Reconstructed Pronunciation in Early Middle Chinese, Late Middle Chinese, and Early Mandarin. I see it as entirely a good thing for reference works of this kind to be available free online rather than only in expensive books in university research libraries. If this is in violation of a Wikibooks policy, I would at least like that policy to be drawn to my attention and to have some constructive comment offered about which Wikiproject such a resource should fall under. I will also say on a personal note that I have put literally hundreds of hours of work into these projects and it would grieve me a lot to see this work simply vanish, in particular when I know that colleagues around the world use these books. --[[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 07:27, 1 November 2024 (UTC)
::Hi @[[User:Tibetologist|Tibetologist]], and thank you for the feedback! Official Wikibooks policy does not permit standalone dictionaries (see [[WB:DICT]]), though I understand the argument that it is a useful resource. I am wondering if there might be a home for it at [[Wiktionary:Wiktionary:Welcome, newcomers|Wiktionary]] or [[Wikiversity:Wikiversity:SHARE|Wikiversity]]? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 12:14, 1 November 2024 (UTC)
:::The policy says to use Wiktionary, but these books cannot be moved there. In fact they link there, you can understand me as having made an index to wiktionary, if you like, where the ORDER of the characters is extremely important, information that would be lost in Wiktionary. 
:::Wikiversity is not a project I participate in, and in any event my books here are older than it, so this option was not available for me at the relevant moment. If you are offering to move my books to Wikiversity, that is very kind of you and I will very graciously accept. [[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 14:10, 1 November 2024 (UTC)
::::I have pinged over at Wikiversity Colloquium to ask about suitability and have looped you into the conversation over there. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:20, 1 November 2024 (UTC)
::I concur. I'm just an undergrad who tries to learn about Sino-Tibetan historical linguistics in his free time but I've found this wikibook to be incredibly useful, and I keep it open in one tab while I watch Professor Nathan Hill's lectures that he uploads to youtube in another tab, and another tab for taking notes. In fact if I remember correctly Professor Hill actually pointed his students to this wikibook. 
::I'm not familiar with [[wikiversity:Wikiversity:SHARE|Wikiversity]] but if all the content were as accessible there as it is here then I think that could work.  [[User:ChromeBones|ChromeBones]] ([[User talk:ChromeBones|discuss]] • [[Special:Contributions/ChromeBones|contribs]]) 02:43, 9 July 2025 (UTC)
:Per [[:v:Wikiversity:Colloquium#Import_Resource_From_Wikibooks?]], I recommend copying and pasting, including attribution via the edit summary and talk page, add appropriate categories and links, and then it could be deleted locally. —[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''vf&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 22:32, 3 November 2024 (UTC)

== [[Suomen kieli käyttöön]] ==

Multiple pages in this book are written entirely in Finnish, which is out of the enWB scope. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:09, 19 October 2024 (UTC)

:I was going to say whether we should ask any fiwikibooks sysop to maybe see if this could be transwikied to fiwb if it's within the scope there. But [[:fi:Toiminnot:Käyttäjät/sysop]] indicates that there are only 3 sysops, and only {{u|Anr}} and {{u|Zache}} have made edits this ''year''. If they deem it to be salvageable, then transwiki + delete, otherwise straight-up delete. --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 11:24, 14 November 2024 (UTC)
::It seems that the idea behind the book was for the pages to be bilingual, as it’s a language learning book. That’s why there are Finnish texts included intentionally even on the pages that are complete. There are similar books in dewikibooks and ruwikibooks as well. For the English version, I think the easiest way to proceed would be to clean up and adjust the page layout to fit enwikibooks better, and then translate the missing parts. By the way, if anyone wants to update the book’s name in English, it can be titled ''&quot;Using the Finnish Language&quot;'' or ''&quot;Put Finnish Language into Use&quot;'' for a direct translation.   [[User:Zache|Zache]] ([[User talk:Zache|discuss]] • [[Special:Contributions/Zache|contribs]]) 11:57, 14 November 2024 (UTC)

== [[AT&amp;T Mobility FAQ]] ==

* [[AT&amp;T Mobility FAQ]]
* [[AT&amp;T Mobility FAQ/MEdia Net Configuration]]
* [[AT&amp;T Mobility FAQ/Data Connect Configuration]]
An ''extremely'' outdated FAQ on AT&amp;T's cell phone services. Most of this document was written 20+ years ago as a Usenet FAQ; very little of it is accurate or useful anymore (particularly the two subpages, which have to do with obsolete configurations for &quot;tethering&quot; a computer to a cell phone). No objection if someone wants to update it, but there's clearly been no appetite to do that. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 22:20, 30 December 2024 (UTC)

:I'm wondering if it might make sense for us to develop some kind of policy on archiving books here. There are many like this one that have a good deal of content but are extremely out of date and just not useful as originally intended. ——[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:34, 30 December 2024 (UTC)
::@[[User:Kittycataclysm|Kittycataclysm]]: See the newly developed [[Wikibooks:Outdated books]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 00:16, 31 December 2024 (UTC)
:::Ooh, thanks - something like that seems like it could be an appropriate way to handle this book. A lot of the other outdated books I've tagged have been so incomplete that they wouldn't have been particularly useful even as historical references; this one might at least have some interest.
:::Any chance we can get a separate namespace (maybe &quot;Archive:&quot;) set up for archived book content? That'd make it possible to do things like exclude them from on-site search by default. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:07, 31 December 2024 (UTC)
::::I think this might be a more extended discussion, so I'll bump it over to the [[Wikibooks talk:Outdated books|talk page of the draft policy]]! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:54, 31 December 2024 (UTC)

== Algebra/Chapter 10/Symmetric Polynomials ==

I personally believe that [[Algebra/Chapter 10/Symmetric Polynomials|this]], and all of the sections should be deleted for the fact that this goes WAY beyond the scope of what was intended for the Chapter (Algebra II level polynomials). [[User:GoreyCat|GoreyCat]] ([[User talk:GoreyCat|discuss]] • [[Special:Contributions/GoreyCat|contribs]]) 15:07, 6 February 2025 (UTC)

:'''Split''': Deletion here is not the best solution (see [[w:WP:ATD]]). Instead, this page and its subpages should be moved to another book, most likely [[Abstract Algebra]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 17:35, 6 February 2025 (UTC)
:{{keep}} since there is a good amount of content. If [[Abstract Algebra]] is appropriate, it seems like a fine idea to move there. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:59, 7 February 2025 (UTC)
::Eh, yeah, I supposed moving it is better. I just don't think it's suitable for where it appears. [[User:GoreyCat|GoreyCat]] ([[User talk:GoreyCat|discuss]] • [[Special:Contributions/GoreyCat|contribs]]) 01:40, 8 February 2025 (UTC)
== [[Puredyne]] ==

Development of Puredyne Linux was discontinued in 2012, and the software no longer appears to be available for download anywhere. (An archive of the web site is still up - with a bunch of embedded spam links - but the download links are all dead.) Is this a suitable candidate for archival (cf. [[Wikibooks:Outdated books]]), or should it just be deleted? [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 04:35, 5 March 2025 (UTC)

:I'd just archive stuff like this. Looks like a decent bit of work went into it, and you never know when someone might need to use Puredyne for some obscure project. I'd be willing to bet mirrors exist of it somewhere, or someone has it on a drive. If you want to find some stuff worth deleting, comb through [[:Category:Allbooks categories]]. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:30, 5 March 2025 (UTC)

== [[Template:Qr-twwp]] ==
This isn't exactly a request to delete the template, but rather to merge it with {{tlx|Copypaste}}. The {{tlx|Qr-twwp}} template serves the same purpose as {{tlx|Copypaste}}, but without the seven-day period after which the page is deleted. This leads to confusion, as well as a perpetually full [[:Category:Queried pages]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 17:37, 30 March 2025 (UTC)

== [[Ghouls of the Miskatonic]] ==

I don't think that a plot summary of a book is in-scope here. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:43, 20 August 2025 (UTC)

:{{vd}} - at least, not a summary of ''this'' book. A summary and/or study guide to a notable work of literature might be in scope, but this is certainly not one. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:23, 25 August 2025 (UTC)
::Hi. I am the creator of the pages of this book. If I understand correctly, it has to be a summary of a notable work of literature? So what exactly is defined as such? I only started this as I thought it would be fun, interesting and encouraging to others who read the Arkham Horror novels, and I thought it was permitted as I've seen other summaries of books on wikibooks. [[User:Dayne90|Dayne90]] ([[User talk:Dayne90|discuss]] • [[Special:Contributions/Dayne90|contribs]]) 13:27, 26 August 2025 (UTC)
:::Your problem is it is just the plot... it needs to include an educational textual analysis to be in scope [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 12:47, 28 August 2025 (UTC)
::::And ideally it'd be a text which has ''already'' been the subject of literary analysis, such that the analysis on Wikibooks isn't original research. A notable work of literature like ''Frankenstein'' or ''Moby-Dick'' would easily meet that requirement; a tie-in novel for a tabletop RPG probably does not. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 22:08, 29 August 2025 (UTC)

== [[A-level Computing AQA Paper 1 Skeleton program 2027]] ==
{{closed|Considering the recent comments and due to no objections, I converted it to a soft redirect until another admin decides if the page can be deleted. CC to [[user:MrBerard|MrBerard]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:51, 15 October 2026 (UTC)}}
This was proposed for speedy deletion by [[User:Omphalographer]] as 'not being a book'. However, I think this page's future requires further discussion from the community. Maybe some input would be appreciated?[[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 23:51, 21 September 2026 (UTC)

:As best I can tell, this is a page students are using to collaborate on solutions for a standardized test. There are a number of similar pages for other years linked from [[A-level Computing/AQA/Paper 1/Skeleton program]].
:This is not a good fit for Wikibooks. If these students are interested in this kind of collaboration, it should take place elsewhere. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:14, 22 September 2026 (UTC)
::The project can be moved to Wikiversity, I think. If the students can contribute it and make sure it complies with Wikibooks' guidelines, it can stay here. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:17, 22 September 2026 (UTC)
:::@[[User:Omphalographer|Omphalographer]] @[[User:TechVindicator|TechVindicator]]
:::There's been a Wikibook on this every single year, as I mentioned in my comment on the deletion notice. That doesn't mean that this shouldn't be on Wikiversity, just that there is ample precedent of it being a Wikibook.  Dunno if this matter to those kind of editorial decisions, though. [[Special:Contributions/~2026-51010-27|~2026-51010-27]] ([[User talk:~2026-51010-27|talk]]) 13:39, 22 September 2026 (UTC)
::::@[[User:~2026-51010-27|~2026-51010-27]]: How would the page comply with [[WB:What is Wikibooks?|Wikibooks' mission]]?. Could you provide an explanation of what the project is?  If it's a collaborative project to work on solutions for a standardized test (like @[[User:Omphalographer|Omphalographer]] said), it would be more suitable for Wikiversity. If it's a textbook about A-level computing, then it would be suitable here. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:58, 22 September 2026 (UTC)
:::::Hi,
:::::This is definitely the former, not the latter. As I said, I don't particularly think this should be on Wikibooks, it just happens the previous years had been, and clearly they weren't subject to this degree of scrutiny 😅
:::::I have created https://en.wikiversity.org/wiki/A-level_Computer_Science_AQA_Paper_1_Skeleton_program_2027 - I'll delete the content of the page and put the link at the top. If there is a more appropriate banner to indicate the migration, please make it look how it should :D [[User:MrBerard|MrBerard]] ([[User talk:MrBerard|discuss]] • [[Special:Contributions/MrBerard|contribs]]) 10:23, 29 September 2026 (UTC)
::::::I can't seem to put a link without the edit being deemed destructive, so I'll let you trusted people do what's needed. [[User:MrBerard|MrBerard]] ([[User talk:MrBerard|discuss]] • [[Special:Contributions/MrBerard|contribs]]) 10:27, 29 September 2026 (UTC)
: {{comment}}: I cannot determine consensus in this request on whether or not it should either be deleted or imported to English Wikiversity. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:28, 13 October 2026 (UTC)
::I've actioned the migration to Wikiversity as per my comment of 29 sep. I'd rather this stayed in as a stub with a link to the Wikiversity entry, for a couple of months, though I'm sure search engines are still vaguely good enough that this shouldn't matter too much. [[User:MrBerard|MrBerard]] ([[User talk:MrBerard|discuss]] • [[Special:Contributions/MrBerard|contribs]]) 14:35, 13 October 2026 (UTC)
{{end closed}}

== [[Talmudic aramic]] ==
{{closed|Deleted per consensus below. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:18, 13 October 2026 (UTC)}}
Per the user's other mass-created pages, I concur with the AI flagging that Kittycataclysm placed on the page. I believe this to be LLM-generated, and it should thus be deleted. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 03:29, 30 September 2026 (UTC)

:{{vd}}, LLM spam. [[User:Ternera|Ternera]] ([[User talk:Ternera|discuss]] • [[Special:Contributions/Ternera|contribs]]) 13:22, 30 September 2026 (UTC)
:{{vd}} - like most LLM-generated books, this is heavy on structure and light on substance. Most of the content amounts to a poorly organized glossary, and there are a lot of pieces missing. (For instance, there is no discussion of the grammar of the language beyond a couple of fixed expressions.) [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:11, 1 October 2026 (UTC)
:{{vd}} per stated reasoning. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:43, 12 October 2026 (UTC)
{{end closed}}

== [[Job Search]] ==
{{closed|Per minimal consensus, I deleted these books, but I only kept the main pages of these books by creating them as redirects for [[Find Employment]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:24, 13 October 2026 (UTC)}}
* as well as [[Job Search Automation for College Students]].

Neither of these books contains any useful information. The first book seems to be written primarily to funnel users to the second, and the second to funnel users to [[PlanoTse Handbook for Job Search Automation]], which was deleted last year. (The deletion request doesn't seem to have been archived.)

The sum total of information in these two books is, essentially, &quot;you can search for jobs online&quot;, which is insultingly trivial. The second book's suggestion that users automate the job search process is of no practical value; most web search engines and job search sites nowadays will detect and block automated access.

[[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:36, 1 October 2026 (UTC)
: {{vd}} and redirect to [[Find Employment]]. ‑‑[[User:Kai Burghardt|Kai Burghardt]] ([[User talk:Kai Burghardt|discuss]] • [[Special:Contributions/Kai Burghardt|contribs]]) 05:14, 2 October 2026 (UTC)
{{end closed}}

== [[Wikipage]] ==
{{closed|Deleted per minimal consensus below. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:26, 13 October 2026 (UTC)}}
Like a few other books created by this user, the purpose of this book appears to have been to promote a piece of software written by the author ([[User:Planotse]]). The software is no longer available, and there is no actual content in the book.

[[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:40, 1 October 2026 (UTC)

:{{Vd}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 15:30, 12 October 2026 (UTC)
{{end closed}}

== [[Becoming a Linguistic Mastermind]] ==
{{closed|Deleted. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 00:11, 15 October 2026 (UTC)}}
Old book (created 2007) with no substantial content. The intent of this book appears to have been to create a single textbook encompassing ''all'' languages, with sub-courses for each language at [[Becoming a Linguistic Mastermind/The courses]], but no such courses were ever created. An analogous project on dewikibooks [[:b:de:Wikibooks:Löschkandidaten/ 2011-04#Der einfache Weg zum Sprachgenie|was deleted in 2011 for similar reasons]]. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:20, 7 October 2026 (UTC)

:{{Vd}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 15:30, 12 October 2026 (UTC)
{{end closed}}

== [[The Permanent Advantage]] ==
{{closed|Speedily deleted —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 20:15, 14 October 2026 (UTC)}}
Probably LLM-generated, given broken templates, references to Claude, and section identifiers. This could probably be speedied, but not 100% sure so throwing it to RfD. Even regardless of whether it's LLM-generated or not, I can't see any way it's really suitable for the project. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 07:49, 10 October 2026 (UTC)

:{{vd}} - a book ''about'' chess problems isn't necessarily out of scope, but there needs to be some written content to accompany the problems. And I'm not sure these are even meaningful problems - the few problems with viewable Lichess links appear to be in the early game, so there aren't necessarily objective &quot;solutions&quot; to them. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:51, 10 October 2026 (UTC)
:{{vd}}, the Claude references throughout the book support that it's LLM-generated. [[User:Ternera|Ternera]] ([[User talk:Ternera|discuss]] • [[Special:Contributions/Ternera|contribs]]) 14:55, 11 October 2026 (UTC)
:This looked like a speedy to me, so I went ahead and deleted it. Thanks! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 20:14, 14 October 2026 (UTC)
{{end closed}}

== [[Digital Synthora]] ==
Not within WB scope since it seems to be entirely fabricated by the editor. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:20, 12 October 2026 (UTC)

:{{vd}} While some amount of original research is allowed here, completely fabricated topics aren't. This is just fiction writing, which is nice, but not within our scope. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 15:30, 12 October 2026 (UTC)
:{{vd}} - per my initial tag, this appears to be an invention of the page creator; I can't find anything relevant online beyond the empty https://synthoraactstuff.fandom.com/. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 01:32, 13 October 2026 (UTC)
== [[Wikibooks:FlaggedRevs Extension]] ==
Flagged Revisions is dead. Flagged Revisions remains dead. And we have killed it. How shall we comfort ourselves, the murderers of all murderers? Well, not in the least by deleting its project page and subpages. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 06:16, 17 October 2026 (UTC)

:Would it be better to mark it as historical, or update the page to say it's dead? I only say this because we've used this extension for a ''very'' long time. {{vd}} all the subpages, however. //[[User:SHB|SHB]] ([[User talk:SHB|discuss]] • [[Special:Contributions/SHB|contribs]]) 09:16, 17 October 2026 (UTC)
:: So far, there is only one subpage, [[Wikibooks:FlaggedRevs Extension/Unstable]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:37, 17 October 2026 (UTC)
:::Mark both as historical. I don't see any compelling reason to delete them. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:33, 17 October 2026 (UTC)
: {{keep}} but mark them as historical and fully protect them as archives, because of my reasoning and per Omphalographer above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:37, 17 October 2026 (UTC)</text>
      <sha1>gesapyiqv1ls4ird5o7pfxgqq74q4mw</sha1>
    </revision>
  </page>
  <page>
    <title>World History/Ancient Civilizations</title>
    <ns>0</ns>
    <id>5765</id>
    <revision>
      <id>4676579</id>
      <parentid>4612161</parentid>
      <timestamp>2026-10-17T22:13:57Z</timestamp>
      <contributor>
        <username>Classclown18</username>
        <id>3503220</id>
      </contributor>
      <minor />
      <origin>4676579</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="54692" sha1="habbitlesyr6tyw70az75tdfw52hb36" xml:space="preserve">{{WHP - page top 1}}

==The Neolithic Revolution and Early Agricultural Societies==
[[File:Asikli Hoyuk sarah c murray 6176.jpg|thumb|Reconstruction of Neolithic housing.]]
[[File:Catalhöyük, the first large settlement of mankind.webm|thumb|Catalhöyük, the first large settlement of mankind]]
Early nomadic hunter-gatherers lived off the land and had a minimal effect on the environment around them. Around 10,000 years ago people started to settle down and developed agriculture possibly in response to a warming climate. The origin of agriculture is often referred to as the Neolithic Revolution. Keep in mind that different societies domesticated plants and animals, and consequently agriculture, independently i.e. Mesopotamia, Nile River Valley, Ancient China. These farmers had to overcome obstacles such as dry land with technologies like large scale irrigation. This large agricultural byproduct, irrigation, had a large impact on the environment. Pastoralism, the branch of agriculture concerned with raising livestock, developed in Afro-Eurasian grassland, negatively affecting the environment when pastures were overgrazed. 

The switch to agriculture created a much more reliable and abundant food source which allowed populations to soar. This led to diversification of labor which meant that food requirements could be on the backs of certain people and new classes like artisans or warriors could develop. These people developed technologies like pottery, metallurgy or plows.

== The Development and Interactions of Early Societies ==
About 5,000 years ago the first urban societies developed laying the foundations for the first civilizations. Nearly all civilizations share the same few features—they have abundant food surpluses, contained cities, political bureaucracies, armies, defined religious and social hierarchies and long distance trading.

==Civilization makes its debut (8000 - 3000 BC)==
[[File:Dagon Museum, Mortars from Natufian Culture, Grinding stones from Neolithic pre-pottery phase.JPG|thumb|Natufian mortars used for grinding.]]
Neolithic means &quot;new stone&quot;, even though agriculture was the crowning achievement of the period.  Civilizations started out small.  Agriculture at first tended to tie only small groups together.  These groups  all settled along rivers, important as a reliable and predictable source of water.  As time passed, families usually worked the same plot of land over successive generations, leading to the concept of ownership.

[[File:Natufian-SupportingWall-Elwad.jpg|thumb|Remains of a Natufian house]]
The earliest examples of settlements date to about 12000 BC to 9500 BC, and seem to predate agriculture. These settlements, termed Natufian, suggest cultivation of rye. The first such excavation was at Tell Es-Sultan, just outside of Jericho.  

Ancient mortars and grinding tools unearthed in a large mound in the Zagros Mountains of Iran reveal that people were grinding wheat and barley about 11,000 years ago. Grass pea, wild wheat, wild barley, and lentils were found throughout the site, including some of the earliest known samples. This was much further east than most sites known for early agriculture. These were found with stone figurines in levels where earthen buildings had been flattened and destroyed, as though civilization had kept building atop their own ruins, or re-purposing land, as  needs changed. 

Evidence in the middle east shows pottery styles moving throughout the Arabian peninsula, especially during the late Halaf-Ubaid period, where painted pottery and flint arrowheads have been discovered in great number. Pottery decorations are used to indicate trade and cultural contact, or widespread immigration during this period. The excavations on Dalma Island in the Persian gulf show the first date stones (pits from a fruit known to be from a widely cultivated palm in the middle east) known from a human settlement, approximately 5000 BC and may be the precursor to agriculture. Interestingly, at this same site, bones were found from long-tail tuna, dolphin, dugong and turtle, gazelle, needle-fish, grouper, sea bream, emperor, and jack. Some of the groupers found would have been nearly a meter long, indicating considerable fishing skill. 

As agriculture became more and more widespread, people began to accumulate surpluses of food, meaning that a single family grew more than it consumed.  At the same time, the increasing tendency to remain in a single location put pressure on groups to protect themselves from other still nomadic peoples.  In addition, when peoples stayed rooted near one another, cultural and social bonds began to form.  People began to do things in similar ways (it is a property of human nature to want to belong).  Because of these factors, especially a surplus of food, labor began to specialize and branch out away from just farming.  When everyone did not have to farm all of the time to live, people began to become artisans and craftsmen.  Such developments also brought trade, and a class of merchants.  Merchants often traveled along the same routes.  Also, within individual villages, artisans contributed to the homogenization of culture.  Merchants caused further interaction and exchange, known as Cultural Diffusion.  Human religion also began to evolve.  Rising above the past nomadic &quot;religions&quot;, cultures developed a unified polytheism within their ranks, which led them to further bond themselves together.  Priests became a class as well.  As you can see, specialization of labor was a direct offshoot of an agricultural surplus.

The new societies had one problem, however: now that the labor was specialized, agricultural surpluses had to happen every year without a break if the new culture was to remain intact.  In stepped governments to fill the void.  Government most likely began with religious leaders, such as priests, exercising control. Governments also provided roads for their citizens and merchants.  They further cemented the bonds between people within villages and regions, unifying culture to the point that it might be called a ''civilization''.  However, governments needed a way to pay the laborers who built and worked on their projects.  Taxes thus first, perhaps unfortunately, appeared on the scene, usually in the form of a tax-in-kind (taking a portion of a product, such as grain from a farmer, the use of money was yet to appear).  Suddenly, all the parts of an ancient civilization appeared.  Governments soon fell into a type of system known as a monarchy, or rule by hereditary leaders (such as kings or princes).  The reason for this was two-fold: monarchy came naturally because it was like the family, with the parents on top and the children beneath; eventually the parents grew old and the children became adults and parents in their own right and the cycle continued.  Secondly, monarchy was predictable and reliable.  In an age without mass communication or speedy travel, it was important for any void left by the death of a leader to be filled quickly, without fuss and strife.  Most of the new governments were, however, small city-states, or independent countries composed of a city and some surrounding farmland.  This was the beginning of the world's oldest civilizations in Ancient Mesopotamia.

'''An insight into the spread of farming:'''

The spread of farming and early domestication of plants and animals was extensive, as the practices expanded from three specific regions (7000 BC) of the world to various other regions, spreading to five continents by the year 3000 BC. Agriculture first started in the Middle East around 10,000-9500 BC. By 7000 BC it had spread to the western part of the Indian subcontinent, and by 6000 BC to Egypt. By 5000 BC, it had reached China, and around 2700 BC, corn was being farmed in Mesoamerica. The Middle East, covering the areas of modern day Turkey, Iraq, Palestine, and Israel, had domesticated cattle and pigs. They were also successful in the domestication and farming of several crops and plants like wheat, barley, rye, onions, peas, and grapes. The Mesoamericans had begun farming corn, beans, avocados, squash, pumpkins, and cotton. They had not domesticated any animals. In the Andes region (Peru), potatoes, tomatoes, lima beans, peanuts, and sweet potatoes were farmed. The Andeans had also domesticated the llama. The spread in the Middle East had the greatest expansion in terms of area. Sheep were domesticated in the greater Middle East; goats were originally domesticated in Central Europe, olives in the Mediterranean. Cotton was first farmed in the Indian sub-continent, and hemp, camels, and buckwheat were originally domesticated west of the Caspian Sea. Furthermore, in the Americas, the Mesoamericans expanded north and south, spreading farming and herding to Central and slightly further into North America. From there the practice extended to South America. The Andeans had minimum spread, expanding farming and herding to regions immediately around theirs. The farming and domestication of plants and animals, by 3000 BC, had been independently innovated in Southeast Asia, China, and North-central Africa. In Southeast Asia, rice, citrus, and chickens were originally farmed and domesticated.  The farming of millet and soybean was practiced in China. Sorghum and coffee were farmed originally in north-central Africa. In a brief period of 4000 years, humans had farmed and domesticated over 30 plants and animals. The spread of farming and herding had reached over five continents, and ten regions of the world.

==River Valley Civilizations==

The first civilizations came about in river valleys which provided a constant source of water for crops. Irrigation works were often needed which required leadership perhaps leading to the creation of the first states. In addition rivers facilitated travel helping a common culture spread along its banks. The four river valley civilizations were the world’s first and each shared many common characteristics.       
The four river valley civilizations: 
China (along the Yellow River aka  Huáng Hé) 
Indus Valley (along the Indus River) 
Mesopotamia (along the Tigris and Euphrates river)  
Egypt (along the Nile)

Each Civilization had: 
*A form of writing 
*Cities
*Agriculture and surplus of food 
*A form of government (usually claiming divine right) 
*A polytheistic or henotheistic religion
*Art and Architecture 

Whereas historians argue on what exactly civilization is, writing, cities, agriculture, government, religion and art are usually on the list.

==Ancient Mesopotamia==

While the earliest agricultural tools are known from beneath Jericho, approximately 7000 BC, further signs of civilization and tool making quickly cropped up across the Zagros mountain range. 

The Halaf civilization (estimates vary but generally run either from 6100-5100 BC or 5100-4100 BC) is known from a number of different locations, primarily in Syria where pottery has been found. The different types of designs found in specific locations especially Tel Sabi Abyad) seem to indicate a significant trade, or possibly migration from the surrounding mountains. During the Halaf period, a variety of grains and herbs (including barley, emmer wheat, einkorn wheat, free threshing wheat, oats, hawthorne, crosswort flax, lentils, legumes, cornelian cherry, clover, sweet clover, fleawort,  field peas, linseed,  wild olive, pistachio, grape, fig and hawthorn) were commonly found at the archaeological site at Ras Shamra in northwest Syria. 

Halaf pottery has been found as far as the earliest cities in Sumer.

[[File:Enthroned King of Ur.jpg|thumb|Sumerian art depicting the King of Ur.]]

Mesopotamia (modern Iraq) was home to the world's first truly urban cultures -- societies featuring permanent cities whose populations were fed from the surrounding countryside, but themselves engaged in other activities besides agriculture, such as trade, specialist crafts and record-keeping.  From 4000 to 3000 BC,  the Sumerians established some of the first known cities in the then-moist land of Sumer (modern southern Iraq, called ''Ki-en-gir'' by the Sumerians).  It is not currently known with certainty where the Sumerians came from, but immigration from elsewhere seems probable; their myths suggested a seafaring background.  From an anthropological viewpoint Sumerians belonged to the Caucasian, Mediterranean, Balkan European race.

Historians speculate that the first Sumerian settlers may have been driven by overpopulation or conflict, as Sumeria was superficially inhospitable to stone-age man; it lacked the stones needed in Neolithic life to make most tools. However, the early Sumerians discovered that mud could be dried and used as a building material, and the soil was rich in clay to use to make farm tools. Once the Sumerians began to plant, they realized that Sumeria's rich mud yielded far greater quantities of food than they could consume. This surplus resulted in some of the first known exports in history.  

Situated near the head of the Persian Gulf, Sumer was well-positioned for sea trade, as well as having land connections to neighboring Anatolia and Elam (modern southern Iran), both of which harbored simpler cultures.  The early Sumerians began to trade their surplus grain with their neighbors for the items that Sumeria did not have, such as livestock and stone. This influx of goods (and therefore merchants) gave rise to some of the first true cities.  Sumerian cities spoke the same language and worshipped the same gods. However, they were not one, with whole cities being burnt to the ground in their inter-city warfare. A typical run-of-the-mill city-state consisted of the city proper and much of the countryside around it. Early Sumerian government was strictly theocratic, and governed everything from sacrifices to taxation to irrigation. Therefore, the central point of each city was its great platform/ziggurat in the centre. These ziggurats became the main form of the later Babylonian monument architecture in the same region.  

Writing in its strictest sense was first invented and used by the Mesopotamians around 3100 BC. It evolved out of a Mesopotamian trade tradition. When two merchants made an agreement, they would make clay models of the items being traded and then would seal them in a clay ball. However, if one of the merchants wanted to double check the quantities agreed upon in the contract, the merchants would need to break open the clay ball, literally breaking the contract. Therefore, the merchants began to scratch little picture of the items onto the outside of the clay ball. Eventually someone realized that the ball and models were no longer necessary. Later the Sumerians created more symbols for use in writing down laws and eventually even stories. This form of writing was called ''cuneiform''.

As many as a thousand clay tablets were found in the Uruk archaeological layer dating to the 30th century B.C. From Sumer, cuneiform script and civilization spread to all the peoples of Asia Minor (Assyrians, Hittites, Urartuans, etc). For instance, the ancient Asomtavruli alphabet of the modern Georgian language has ethno-cultural contacts with the Sumerian world. Georgian specialists study the similarity of Sumerian and Iberian-Caucasian languages. Sumerian remained the language of religion and science in the 2nd-1st millennium B.C. before its replacement by Semitic languages.  But Sumerian did not confide the Semites with the Majuscule alphabet, the secret spiritual alphabet that has a lot of similarity to ancient Georgian Asomtavruli alphabet. More than 200 Sumerian and Svanian terms are identical both phonetically and semantically. Sumerians created a new simplified 22 simple letter-signs alphabet. The Semitic alphabet created by Sumerian scientists for Accadians laid the foundation for various people's writing creation and spreading (Moabs, Phoenicians, Hebrews, Greeks, Latins, Arabs and others) Sumerian sacral alphabet of 35 letter signs that concealed the Sun and the Moon calendar.

After flourishing for the better part of a millennium, Mesopotamia apparently experienced a climate change, which led to drought, exhaustion of the heavily-used soil, agricultural failure, and the decline of the Sumerian city-states that had become dependent on reliable surplus food production. Neighbouring peoples and tribes launched military incursions against the weakened city-states, resulting in political power shifts and the rise of new states and cities further north. Sumerologist Samuel Noah Kramer wrote &quot;in the last quarter of the 3rd millennium B.C. the Semites inhabiting the town of Akkad conquered Sumer and made the Sumerian scientists create an alphabet for them, which subsequently came to be called the Semitic&quot; This event took place in 2125 B.C.


===The Akkadians: The First Empire===
[[File:Bronze head of an Akkadian ruler, discovered in Nineveh in 1931, presumably depicting either Sargon or Sargon's grandson Naram-Sin (Rijksmuseum van Oudheden).jpg|thumb|Bronze head depicting an Akkadian ruler.]]
====Origins of Akkad====

Semitic speakers seem to have already been present in Mesopotamia at the dawn of the historical record, and soon achieved preeminence with the first Dynasty of Kish and numerous localities to the north of Sumer—where rulers with Semitic names had already established themselves by ca. the 3rd millennium BC. One of these, contemporary with the last Sumerian ruler, Lugal-Zage-Si of Uruk, was Alusarsid (or Urumus) who &quot;subdued Elam and Barahs (Barahsi?)&quot; thus beginning the trend towards regional empire.

The first known mention of Akkad is in an inscription of Enshakushanna of Uruk, where he claims to have defeated Agade—indicating that it was in existence well before the days of Sargon of Akkad, who the Sumerian kinglist claims to have built it. Sargon has often been cited as the first ruler of a combined empire of Akkad and Sumer, although more recently discovered data suggests there had been Sumerian expansions under previous kings, including Lugal-Anne-Mundu of Adab, Eannatum of Lagash, and Lugal-Zage-Si.

====Sargon and his sons====

The fame of the early establisher of Semitic supremacy was far eclipsed by that of Sargon of Akkad (Sharru-kin = &quot;legitimate king&quot;, probably a title he took on gaining power[5]) (23rd century BC), who defeated and captured Lugal-Zage-Si, conquering his empire.

The earliest records in Akkadian all date to the time of Sargon. Sargon was claimed to be the son of La'ibum or Itti-Bel, a humble gardener, and possibly a hierodule, prostitute, or priestess to Ishtar or Inanna.

One legend related of Sargon in neo-Assyrian times says that &quot;My mother was a changeling, my father I knew not. The brothers of my father loved the hills. My city is Azurpiranu (the wilderness herb fields), which is situated on the banks of the Euphrates. My changeling mother conceived me, in secret she bore me. She set me in a basket of rushes, with bitumen she sealed my lid. She cast me into the river which rose not over me. The river bore me up and carried me to Akki, the drawer of water. Akki, the drawer of water, took me as his son and reared me. Akki the drawer of water, appointed me as his gardener. While I was gardener Ishtar granted me her love, and for four and (fifty?) ... years I exercised kingship.&quot;

Originally a cupbearer to a king of Kish with a Semitic name, Ur-Zababa, Sargon thus became a gardener, responsible for the task of clearing out irrigation canals. This gave him access to a disciplined corps of workers, who also may have served as his first soldiers. Displacing Ur-Zababa, the crown was set upon Sargon's head, and he entered upon a career of foreign conquest.[7] Four times he invaded Syria and Canaan, and he spent three years thoroughly subduing the countries of &quot;the west&quot; to unite them with Mesopotamia &quot;into a single empire.&quot;

However, Sargon took this process further, conquering many of the surrounding regions to create an empire that reached as far as the Mediterranean Sea and Anatolia, and extending his rule to Elam, and as far south as Magan (Oman), an area over which he reigned for 56 years. Trade extended from the silver mines of Anatolia to the lapis lazuli mines in Afghanistan, the cedars of Lebanon and the copper of Oman. This consolidation of the city-states of Sumer and Akkad reflected the growing economic and political power of Mesopotamia. The empire's breadbasket was the rain-fed agricultural system of northern Mesopotamia and a chain of fortresses was built to control the imperial wheat production.

Images of Sargon were erected on the shores of the Mediterranean, in token of his victories, and cities and palaces were built at home with the spoils of the conquered lands. Elam and the northern part of Mesopotamia (Subartu) were also subjugated and rebellions in Sumer were put down. Contract tablets have been found dated in the years of the campaigns against Canaan and against Sarlak, king of Gutium.

Sargon, throughout his long life, showed special deference to the Sumerian deities, particularly Inanna, his patroness, and Zababa, the warrior god of Kish. He called himself &quot;The anointed priest of Anu&quot; and &quot;the great ensi of Enlil&quot; and his daughter, Enheduanna the famous poet, was installed as priestess to Nanna at the temple in Ur.

He also boasted of having subjugated the &quot;four quarters&quot;—the lands surrounding Akkad to the north (Subartu), the south (Sumer), the east (Elam) and the west (Martu). Some of the earliest texts credit him with rebuilding the city of Babylon (Bab-ilu) in a new location.

Troubles multiplied toward the end of his reign. A later Babylonian text states &quot;In his old age, all the lands revolted against him, and they besieged him in Akkad (the city)&quot;...but &quot;he went forth to battle and defeated them, he knocked them over and destroyed their vast army&quot;. Also shortly after, &quot;the Subaru (mountainous tribes of) the upper country—in their turn attacked, but they submitted to his arms, and Sargon settled their habitations, and he smote them grievously&quot;.

These difficulties broke out again in the reign of his sons. Revolts broke out during the 9-year reign of his son, Mush, who fought hard to retain the empire—and in the fifteen year reign of Mush's elder brother, Humanist. The latter king seems to have fought a sea battle against 32 kings who had gathered against him. Both appear to have been assassinated.

====Naram-Sin====

Naram-Sin (Beloved of Sin), Sargon's grandson, who assumed the imperial title of &quot;King Naram-Sin, of the four quarters (Lugal Naram-Sin, Šar kibrat 'arbaim)&quot;, and, like his grandfather, was addressed as &quot;the god (Sumerian = DIN.GIR, Akkadian = ilu) of Agade&quot; (Akkad), also faced revolts at the start of his reign.

Naram-Sin also recorded the Akkadian conquest of Ebla and Armani (also read Armanum or Armanim). The Assyrians, who are direct descendants of Akkadians, to this day refer to Armenians by the inscription from Armani. They were located between Carchemish and Ebla. To better police this area, he built a royal residence at Tell Brak, a crossroads at the heart of the Khabur basin of the Jezirah. Naram-Sin is supposed to have possessed an army of over 360,000 men, the largest of any state up until that date. It enabled him to campaign against Magan (thought to be Oman) which also revolted; Naram-Sin, &quot;marched against Magan and personally caught Mandannu, its king&quot;. The chief threat seemed to be coming from the northeastern mountaineers. A campaign against the Lullubi led to the carving of the famous stele, now in the Louvre. This newfound Akkadian wealth may have been based upon benign climatic conditions, huge agricultural surpluses and the confiscation of the wealth of other peoples.[8]

The economy was highly planned. After the advancing Akkadian forces from Tell Brak took the massive (100 acre) site of Tell Leilan, they destroyed nearby villages and brought the organization of farming and grain distribution into its bureaucratic control. Grain was cleaned, and rations of grain and oil were distributed in standardized vessels made by the city's potters. Taxes were paid in produce and labour on public walls, including city walls, temples, irrigation canals and waterways, producing huge agricultural surpluses.
Stele of Naram-Sin, king of Akkad, celebrating his victory against the Lullubi from Zagros.

In later Babylonian texts, the name Akkad, together with Sumer, appears as part of the royal title, as in the Sumerian LUGAL KI.EN.GIRKI URUKI or Akkadian Šar māt Šumeri u Akkadi,[10] translating to &quot;king of Sumer and Akkad&quot;. This title was assumed by the king who seized control of Nippur,[11] the intellectual and religious centre of southern Mesopotamia.

During the Akkadian period, the Akkadian language became the lingua franca of the Middle East, and was officially used for administration, although the Sumerian language remained as a literary language. The spread of Akkadian stretched from Syria to Elam, and even the Elamite language was temporarily written in Mesopotamian cuneiform. Akkadian texts later found their way to far-off places, from Egypt (in the Amarna period) and Anatolia, to Persia (Behistun).

====Collapse of Akkad====

Within 100 years the Empire of Akkad collapsed, almost as fast as it had developed, ushering in a Dark Age. By the end of the reign of Naram-Sin's son, Shar-Kali-Sharri, the empire collapsed outright from the invasion of barbarians of the Zagros known as &quot;Gutians&quot;. It has recently been suggested that the Dark Age at the end of the Akkadian period (and First Intermediary Period of the Ancient Egyptian Old Kingdom) was associated with rapidly increasing aridity, and failing rainfall in the region of the Ancient Near East, caused by a global centennial-scale drought.[12]

The fall of the empire established by Sargon seems to have been as sudden as its rise, and little is known about the Gutian period. From the fall of Akkad until around 2100 BC, there is much that is still dark.

The Sumerian king list, for the period after the death of Sharkalishari, states:

{{cquote|Who was king? Who was not king? Igigi the king; Nanum, the king; Imi the king; Elulu, the king—the four of them were kings but reigned only three years. Dudu reigned 21 years; Shudurul, the son of Dudu, reigned 15 years. (A total of) 11 kings reigned 197 years. Agade was defeated and its kingship carried off to Uruk. In Uruk, Urnigin reigned 7 years, Irgigir, son of Urnigin, reigned 6 years; Kudda reigned 6 years; Puzur-ili reigned 5 years, Utu-utu reigned 6 years. Uruk was smitten with weapons and its kingship carried off by the Gutian hordes.}}

(These kings of Uruk may have been contemporaries of the last kings of Akkad.)

{{cquote|In the Gutian hordes, (first reigned) a nameless king; (then) Imta reigned 3 years as king; Shulme reigned 6 years; Elulumesh reigned 6 years; Inimbakesh reigned 5 years; Igeshuash reigned 6 years; Iarlagab reigned 15 years; Ibate reigned 3 years; ... reigned 3 years; Kurum reigned 1 year; ... reigned 3 years; ... reigned 2 years; Iararum reigned 2 years; Ibranum reigned 1 year; Hablum reigned 2 years; Puzur-Sin son of Hablum reigned 7 years; Iarlaganda reigned 7 years; ... reigned 7 years; ... reigned 40 days. Total 21 kings reigned 91 years, 40 days.}}

Evidence from Tell Leilan in Northern Mesopotamia shows what may have happened. The site was abandoned soon after the city's massive walls were constructed, its temple rebuilt and its grain production reorganised. The debris, dust and sand that followed show no trace of human activity. Soil samples show fine wind-blown sand, no trace of earthworm activity, reduced rainfall and indications of a drier and windier climate. Evidence shows that skeleton-thin sheep and cattle died of drought, and up to 28,000 people abandoned the site, seeking wetter areas elsewhere. Tell Brak shrank in size by 75%. Trade collapsed. Nomadic herders such as the Amorites moved herds closer to reliable water supplies, bringing them into conflict with farmers. This climate-induced collapse seems to have affected the whole of the Middle East, and to have coincided with the collapse of the Egyptian Old Kingdom. A relatively well-known king from that period is Gudea, king of Lagash.

This collapse of rain-fed agriculture in &quot;the Upper Country&quot; meant the loss to southern Mesopotamia of the agrarian subsidies which had kept the Akkadian Empire solvent. Water levels within the Tigris and Euphrates fell 1.5 metres beneath the level of 2600 BC, and although they stabilised for a time during the following Ur III period, rivalries between pastoralists and farmers increased. Attempts were undertaken to prevent the former from herding their flocks in agricultural lands, such as the building of a 180 km wall between the Tigris and Euphrates under the neo-Sumerian ruler Shu-Sin. Such attempts led to increased political instability; meanwhile, severe depopulation occurred to re-establish demographic equilibrium with the less favourable climatic conditions.

It has also been suggested (Burroughs, 2007) that the rapid climatic collapse, marking the Akkadian Dark Age, may have been responsible for the religiously prescribed prohibition against the raising and consumption of pigs that spread through the Ancient Middle East from the end of the third millennium BC.

The period between ca. 2100 BC and 2000 BC is sometimes called the 3rd dynasty of Ur or &quot;Sumerian Renaissance&quot;, founded by Ur-Nammu (originally a general). Though documents again began to be written in Sumerian, this dynasty may also have been Semitic; Sumerian was becoming a purely literary or liturgical language, much as Latin later would be in Medieval Europe.

====The Curse of Akkad====

Later material described how the fall of Akkad was due to Naram-Sin's attack upon the city of Nippur. When prompted by a pair of inauspicious oracles, the king sacked the E (temple)E-kur temple, supposedly protected by the god Enlil, head of the pantheon. As a result of this, eight chief deities of the Anunaki pantheon were supposed to have come together and withdrawn their support from Akkad.
{{cquote|
&lt;poem&gt;
For the first time since cities were built and founded,
The great agricultural tracts produced no grain,
The inundated tracts produced no fish,
The irrigated orchards produced neither syrup nor wine,
The gathered clouds did not rain, the masgurum did not grow.
At that time, one shekel's worth of oil was only one-half quart,
One shekel's worth of grain was only one-half quart. . . .
These sold at such prices in the markets of all the cities!
He who slept on the roof, died on the roof,
He who slept in the house, had no burial,
People were flailing at themselves from hunger.
&lt;/poem&gt;
}}
For many years, the events described in &quot;The Curse of Akkad&quot; were thought, like the details of Sargon's birth, to be purely fictional. But now the evidence of Tel Leilan, and recent findings of elevated dust deposits in sea-cores collected off Oman, that date to the period of Akkad's collapse suggest that climate change may have been the culprit.

===The Babylonians===
The Babylonians built the Hanging Gardens of Babylon and sun baked clay houses.  They also introduced the convention of using 360 degrees in a circle, and of dividing the day into 24 hours, and each hour into 60 minutes.

==Ancient Andes==
3500BCE


==Valdiva 3500 BCE-1800BCE==
[[Valdiva culture]] were an Andean Civilization of [[Ecuador]]. They lived on coastal areas of [[Guayas]]. Many of their houses were put into circular positions in the central plaza. They are known for their pottery work. Most of their pottery resembled females. Females possibly held a high position in their society. Valdivia Culture domesticated llamas and cultivated cotton.  
* Their diet included:
* [[Maize]]
* [[Squash]]
* [[Kidney beans]]
* [[Cassava]]
* [[Hot peppers]]
* [[Fish]]
* Occasionally [[deer]]

==Ancient Egypt==
[[File:Ancient Egypt map-en.svg|thumb|Map of Ancient Egypt]]
3100 BC-30 BC


===The Protodynastic Period===

===The Old Kingdom===
[[File:Kheops-Pyramid.jpg|thumb|The Great Pyramid was built during the Old Kingdom.]]
'''The Old Kingdom''' started circa 2700 BC during Egypt's 3rd dynasty. During this period of Egyptian history the Pharaohs were absolute rulers. It was during the Old Kingdom that the Great Pyramid was built as a tomb for Khufu, a Pharaoh during Egypt's 4th dynasty. The Old Kingdom failed at around 2150 BC for a number of reasons. These included the long life span of Pepi II, who ruled 94 years. Pepi II lived to be about 100 years of age, outliving many of his heirs. Additionally, the lower Nile inundation became irregular and led to failed harvests, which may have been caused by a drier climate.

===The First Intermediate Period===
Monarches competed for control of Egypt and civil wars were common. Famines were common during this period and it is called the dark age of Egyptian History.

===The Middle Kingdom===
Egypt's Middle Kingdom was Egypt's golden age because of trading, and new conquest. It lasted from 2050-1650 BC. The Pharaohs period of this period called themselves good shepherds and they were not as powerful as they were during the Old Kingdom. Their pyramids were smaller. The Middle Kingdom ended because of weak Pharaohs and an invasion by Asiantic people called the Hyksos.

===The Second Intermediate Period===
The Hyksos ruled Lower Egypt from about 1650-1550 BC until the Thebean king named Ahmose I expelled them out of the country and started the New Kingdom.

===The New Kingdom===
During the New Kingdom, Egypt was at its height of power. This period lasted from 1550-1070 BC. During this period Egypt became an empire when Thutmose III conquered Palestine, Syria, and Nubia this empire lasted to Amenhoptep VI who ended Egypt's worship of many gods in favour of one god Aton. Later his son Tutankhamen restored the old religion, Tutankhamen died at 18 leaving no heirs to the throne. Seti I restored some of Egypt's empire in Palestine and Syria and his son Ramses II fought the Hitties at Kadesh, then made the first peace treaty with them. He ruled for 67 years. The last great Pharaoh was Ramses III, who was not a relative of Ramses II. He protected Egypt from invasion. About 1070 BC the New Kingdom ended.

===The Postdynastic Period===

== Ancient Indian Civilization==
The earliest known farming cultures in south Asia emerged in the hills of Balochistan, Pakistan, which included Mehrgarh in the 7th millennium BC. These semi-nomadic peoples domesticated wheat, barley, sheep, goat and cattle. Pottery was in use by the 6th millennium BC. Their settlement consisted of mud buildings that housed four internal subdivisions. Burials included elaborate goods such as baskets, stone and bone tools, beads, bangles, pendants and occasionally animal sacrifices. Figurines and ornaments of sea shell, limestone, turquoise, lapis lazuli, sandstone and polished copper have been found. By the 4th millennium BC we find much evidence of manufacturing. Technologies included stone and copper drills, updraft kilns, large pit kilns and copper melting crucibles. Button seals included geometric designs.

===Indus Valley civilization===

By 4000 BC a pre-Harappan culture emerged, with trade networks including lapis lazuli and other raw materials. Villagers domesticated numerous other crops, including peas, sesame seed, dates, and cotton, plus a wide range of domestic animals, including the water buffalo which still remains essential to intensive agricultural production throughout Asia today. There is also evidence of sea-going craft. Archaeologists have discovered a massive, dredged canal and docking facility at the coastal city of Lothal, India, perhaps the world's oldest sea-faring harbour. Judging from the dispersal of artifacts the trade networks integrated portions of Afghanistan, the Persian coast, northern and central India, Mesopotamia (see Meluhha) and Ancient Egypt (see Silk Road).

Archaeologists studying the remains of two men from Mehrgarh, Pakistan, discovered that these peoples in the Indus Valley Civilization had knowledge of medicine and dentistry as early as circa 3300 BC. The Indus Valley Civilization gains credit for the earliest known use of decimal fractions in a uniform system of ancient weights and measures, as well as negative numbers (see Timeline of mathematics). Ancient Indus Valley artifacts include beautiful, glazed stone faïence beads.

The Indus Valley Civilization boasts the earliest known accounts of urban planning. As seen in Harappa, Mohenjo-daro and (recently discovered) Rakhigarhi, their urban planning included the world's first urban sanitation systems. Evidence suggests efficient municipal governments. Streets were laid out in perfect grid patterns comparable to modern New York. Houses were protected from noise, odors and thieves. The sewage and drainage systems developed and used in cities throughout the Indus Valley were far more advanced than that of contemporary urban sites in Mesopotamia.

===Vedic Civilization===

The Vedic civilization is the Indo-Aryan culture associated with the Vedas, which are the oldest extant Indo-European texts, composed in Vedic Sanskrit. The exact connection of the genesis of this civilization with the Indus Valley civilization on one hand, and a possible Indo-Aryan migration on the other hand, is the subject of disputes. Early Vedic society was largely pastoral. Later on, the society became agricultural, and was organized around four Varnas, or classes. Several small kingdoms and tribes merged to form a few large ones which were often at war with each other.

In addition to the principle texts of Hinduism, (the Vedas), the great Indian epics, the Ramayana and Mahabharata, the latter of which constitutes the longest poem in the world, are said to have been first written during this period, perhaps from a longer spoken tradition of unwritten recitation. The Bhagavad Gita, another primary text of Hinduism, is contained within the Mahabharata.

Early Indo-Aryan presence probably corresponds to the presence of ochre coloured pottery, archaeologically. The kingdom of the Kurus marks flowering of the Vedic civilization, corresponding to the Black and Red Ware and the beginning of the Iron Age in Northern India begins, around 1100 BC, likely also contemporary with the composition of the Atharvaveda. Painted Grey Ware spread over all of Northern India marks the late Vedic period, corresponding to a wave of urbanization occurred across the Indian sub-continent, spreading from Afghanistan to Bengal, in the 7th century BC. A number of kingdoms and republics emerged across the Indo-Gangetic plain and southern India during this period. 16 Mahajanapadas (great kingdoms) are referred to in ancient literature of the period.

===The Mahajanapadas===

By 600 BC, sixteen hereditary monarchies known as the Mahajanapadas stretched across the Indo-Gangetic plains from modern-day Afghanistan to Bangladesh. The largest of these nations were Magadha, Kosala, Kuru and Gandhara. The right of a king to his throne, no matter how it was gained, was usually legitimized through religious right and genealogies concocted by priests who ascribed to the king divine origins.

Hindu rituals at that time were complicated and conducted by the priestly class. It is thought that the Upanishads, the secondary texts of ancient Hinduism, dealing mainly with philosophy, were first composed early in this period. The court language at that time was Sanskrit, while the dialects of the general population of northern India were referred to as Prakrits. In 537 BC, Gautama Buddha gained enlightenment and thus founded Buddhism, which was initially intended as a supplement to the existing Hindu Vedic dharma. Around the same time period, in mid-6th century BC, Mahavira founded Jainism. Both religions had a simple doctrine and were preached in Prakrit which helped it gain acceptance by the masses. While the geographic impact of Jainism was limited, Buddhist nuns and monks spread their teachings of Buddha to Tibet, Sri Lanka and South East Asia.

In around 500 BC, the Indus Valley region was invaded by the Persian ruler Darius I making the far north-west of India a satrapy of the Achaemenid Empire. Though the Persians made Taxila the capital, their influence was marginal and governed the region for around 150 years. The Persians were defeated by Alexander the Great in the 4th century BC. In 326 BC, Alexander the Great crossed the Hindu Kush mountains and invaded what is now Pakistan. However, costly campaigns against the forces of Porus (also known as Puru), and the tired troops forced him to retreat to his empire after reaching the Beas River in Punjab. He appointed Greek governors to rule the newly acquired province to keep open trade routes between India and Greece.

====Maurya Dynasty====

In 321 BC, exiled general Chandragupta Maurya overthrew reigning king Dhana Nanda to establish the Mauryan Empire. Chandragupta was succeeded by his son Bindusara, who expanded the kingdom over most of present day India, barring the extreme south and east. During this time, most of the subcontinent was united under a single government for the first time.

The kingdom was inherited by his son Ashoka the Great who initially sought to expand his kingdom. In the aftermath of the carnage caused in the invasion of Kalinga, he renounced bloodshed and pursued a policy of non-violence or ahimsa after converting to Buddhism. The Edicts of Ashoka are the oldest preserved historical documents of India, and from Ashoka's time, approximate dating of dynasties becomes possible. The Mauryan dynasty under Ashoka was responsible for the proliferation of Buddhist ideals across the whole of East Asia and South East Asia, fundamentally altering the history and development of Asia. Ashoka the Great has been described as one of the greatest rulers the world has seen.

====Shunga Dynasty====

The Sunga dynasty was established in 185 BC, about 50 years after Ashoka's death, when the king Brihadratha, the last of the Mauryan rulers, was brutally murdered by the then commander-in-chief of the Mauryan armed forces, Pusyamitra Sunga, while he was taking the Guard of Honour of his forces. Pusyamitra Sunga then ascended the throne.

== Ancient Chinese Civilization ==
The earliest written record of China's takes the form of inscriptions of divination records on the bones or shells of animals—so-called &quot;oracle bones&quot;. 

The earliest comprehensive history of China, the &quot;Historical Records&quot; written by Sima Qian, a renowned Chinese historiographer of the 2nd century BC, begins perhaps 3600 BC with an account of the Five Emperors (五帝). These rulers were legendary sage-kings and moral exemplars, and one of them, the Yellow Emperor, is sometimes said to be the ancestor of all Chinese people. Following this period Sima Qian relates that a system of inherited rulership was established during the Xia dynasty, and that this model was perpetuated in the successor Shang and Zhou dynasties. It is during this period of the Three Dynasties (Chinese: 三代) that the historical China begins to appear.

===Xia Dynasty===
Sima Qian's account dates the founding of the Xia Dynasty (夏) to some 4,000 years ago, but this date has not yet been corroborated. Some archaeologists connect the Xia to excavations at Erlitou in central Henan province, where a bronze smelter from around 2000 BC was unearthed. Early markings from this period, found on pottery and shells, have been alleged to be ancestors of modern Chinese characters, but such claims are unsupported. With no clear written records to match the Shang oracle bones or the Zhou bronze vessel writings, the Xia remains poorly understood.

===Shang Dynasty===
[[File:HouMuWuDingFullView.jpg|thumb|Bronzework from the Shang Dynasty.]]
Archaeological findings provide evidence for the existence of the Shang dynasty (商), ca. 1600 to 1046 BC, and the archaeological evidence is divided into two sets. The first, from the earlier Shang period (ca. 1600 to 1300) comes from sources at Erligang, Zhengzhou and Shangcheng. The second set, from the later Shang or Yin period, consists of a large body of oracle bone writings. Anyang in modern day Henan has been confirmed as the last of the six capitals of the Shang (ca. 1300 to 1046 BC).

Chinese historians living in later periods were accustomed to the notion of one dynasty succeeding another, but the actual political situation in early China is known to have been much more complicated. Hence, as some scholars of China suggest, the Xia and the Shang can possibly refer to political entities that existed at the same time, just as the early Zhou (successor state of the Shang), is known to have existed at the same time as the Shang.
What was the religion?

===Zhou Dynasty===
By the end of the 2nd millennium BC, the Zhou Dynasty (周) began to emerge in the Huanghe valley, overrunning the Shang. The Zhou appeared to have begun their rule under a semi-feudal system. Nevertheless, power became decentralized during the Spring and Autumn Period when regional feudal lords began to assert their power, absorb smaller powers, and vie for hegemony. The Hundred Schools of Thought of Chinese philosophy blossomed during this period and such influential intellectual movements as Confucianism, Taoism, Legalism and Mohism were founded. After further political consolidation, seven prominent states remained by the end of 5th century BC, and the years in which these few states battled each other is known as the Warring States period. Though there remained a nominal Zhou king until 256 BC, he was largely a figurehead and held little real power.

Meanwhile, neighboring territories of these warring states were gradually annexed, including areas of modern Sichuan and Liaoning, and governed under the new local administrative system of commandery and prefecture (郡县), which had been in use since the Spring and Autumn Period and was very loosely a primitive prototype of the modern system of Sheng and Xian (province and county). The final expansion in this period began during the reign of Ying Zheng, the king of Qin. His unification of the other six powers, and further annexations in the modern regions of Zhejiang, Fujian, Guangdong and Guangxi in 214 BC enabled him to proclaim himself the First Emperor (始皇帝，Shi Huangdi), forming the first Chinese empire under the Qin Dynasty (秦), that laid the foundation for the consolidation of the Chinese territories that we know today.

==The Hittites==
[[File:Hattusa, capital of the Hittite Empire 04.jpg|thumb|Remains of the Great Temple in Hattusa, capital city of the Hittite Empire.]]
The Hittites were the prescendants of the Caucasian Kartvelian group of nations and were the descendants of Sumerians. Their innovations in the design of chariots, moving the wheel to the centre from the back, gave them a military advantage over other civilizations. Another point of note is that the first international peace treaty was signed by the Hittites and the Egyptians after the Battle of Kadesh. The original copy is kept in the headquarters of the United Nations. After 600 years as a major empire in the Ancient Middle East the Hittites, crippled by the attacks of the Sea Peoples abandoned their capital, Hattusa, and seemed to vanish from history.

==The Assyrians==
The Assyrians were a civilization located near modern Iraq, along the Tigris River. The Assyrians eventually grew to occupy modern-day Iraq, northern Egypt, the eastern parts of Asia Minor and modern-day Jordan.

Assyria started around 2000 BC with Semitic barbarians invading the area and establishing the roots for a civilization. By 1800 BC the Assyrians had firm control over most of northern Mesopotamia, but later lost it to the Babylonians.

By 1076 BC, the Assyrians reached the Mediterranean coast. The Empire reached its peak at around 1000 to 700 BC, with the conquering of northern Egypt and Babylon. However, the Assyrians were very harsh with the lands they conquered, and thus its citizens were very unhappy with the ruling class. By 600 BC, their capital, Nineveh, fell to the revolting vassal states, including Babylon. Soon after, the Assyrians existed only in the history books.

Though the Assyrians did not advance far in the fields of science and technology, philosophy or the arts, they were mentioned in Biblical records for being great warriors, and their tactics of war would influence later powers, such as the Persians.

==The Persians==
The Persian Empire started in the north west corner of what is now Iran. It grew through military conquest to cover a huge region that roughly encompasses today's Iran, Iraq, Armenia, Afghanistan, Turkey, Bulgaria, many parts of Greece, Egypt, Syria, much of what is now Pakistan, Jordan, Israel, Palestine, Lebanon, Caucasia, Central Asia, Libya, and northern parts of Arabia. The empire eventually became the largest empire of the ancient world.
Persepolis was the ceremonial capitol of Persia. Susa and Pasargadas also acted as capital cities at different times in Persian history. They were all in what is now Iran.

=== What did they eat?===

The food prepared for Persian kings was luxurious. Persians ate stews made from meat and fruit with herbs. They ate rice and bread made with wheat. Yoghurt was also a staple in Persian food. Tablets from the time of these ancient peoples indicate that the inhabitants of Mesopotamia were using basil, cilantro, cumin and caraway in their food in 4,000 BC. Apricots, artichokes, eggplants, lemons, lime, oranges, pistachios, spinach, saffron or tarragon all came to Europe through Persia. Other condiments and spices such as cinnamon, cardamom, cloves, coriander, dill, nutmeg, pomegranates, saffron, sumac, turmeric, as well as orange-flower water and rose water were used in Persian food. Lamb and goat were the primary meats eaten by Persians.

===What did their buildings look like?===
[[File:Gate of All Nations, Persepolis.jpg|thumb|Ruins in Persepolis.]]
Persians made very interesting buildings. The Ruins at Persepolis are an example of ancient Persian buildings. Persians were among the first to use mathematics, geometry, and astronomy in their building. Their buildings were grand and were created by skillful workers. Some Persian buildings had huge barrel-vaulted chambers. The Persians created huge domes of rock and clay and supported their roofs with tall columns. They also decorated the walls of their palaces with lions, bulls and flowers.
The Kharaghan twin towers and the Shah Mosque are two other old buildings built in a Persian style.

===What did they wear?===
The Persian king wore a robe of honour that was a large piece of fabric that was draped around him. For the king and other aristocracy, their clothes were often decorated with golden clothing ornaments. Some of these are in the form of roundels, while others are gold plaques with loops or rings on the back so they can be sewn onto the cloth. Rich people also liked to wear gold jewelry such as bracelets with animal head carvings.
Common people wore coats and pants made out of leather. Men's coats reached from their shoulders down to their knees and were fastened with a girdle. Their sleeves were somewhat tight and went down to their wrists.
Originally woman's clothing was quite similar to men's clothing but as time went their style changed. Initially their clothes were short and tight but when the style changed their clothes were made longer, more voluminous and were made out of softer materials.
Persian shoes were usually just pieces of leather that were wrapped around their feet and were tied up on the top. These would have look similar to moccasins.

===What did their writing look like?===
Old Persian was written from left to right in Old Persian cuneiform script. Old Persian cuneiform script was supposedly invented by King Darius I, one of ancient Persia's famous kings. There were 36 letters in their alphabet, although some of them essentially represented different syllables. For example they had one symbol for &quot;ka&quot; and another symbol for &quot;ku&quot;. They used these symbols even though they also had symbols that represented &quot;a&quot; and &quot;u&quot;.

===What did they believe?===
The Persian civilization spawned three major religions: Zoroastrianism, Mithraism, and Manichaeanism.
The Persian thinker Zoroaster (who propagated Zoroastrianism) was the main religious movement leader. Living around 3500 years ago, he helped to unite the Persian empire. He rejected the old Persian gods and introduced that a single wise god, Ahura Mazda, ruled the world. However, Ahura Mazda was often in battle with the prince of evil and lies, Ahriman. On Earth, each person had to choose which side to support.
Zoroaster's teaching were written in a book, the Zend-Avesta. It said that Ahura Mazda would conquer over the forces of evil, Ahriman, at the end. On that day, all the people would be judges for their actions. Those who did good would enter paradise. Those who did evil would be condemned to eternal suffering.

===Are some of them famous even today?===
Of course, but perhaps the most famous Persian of all time is Cyrus the Great who founded the Persian Empire. In fact, in 1992 he was ranked #87 on Michael H. Hart's list of the most influential figures in history. Other famous Persian kings were Cambises and Darius the Great.
Darius III is famous only because he suffered under the hands of Alexander the Great of Greece. During Darius' reign, the whole Persian Empire was destroyed by Alexander, who first attacked the Persians in what is now modern Turkey. He then moved on into the heart of the Empire where he captured the capital Susa. Darius ran away from battle against Alexander twice, but was murdered by his governor Bessus who wanted the throne for himself. Alexander was angry this happened and respected his dead opponent. He held a great funeral for the dead king. Later, Bessus was captured and executed.


===What is left of them today?===
Persians are one of the only ancient civilizations that has made significant contributions to humanity from prehistoric times by their Persian empire all the way through to the modern day in their country Iran. Most Persians are now Muslims, although there are Jews, Christians, and Zoroastrians still living and practicing their religion in Iran. There are also some Persians, called Parsis, living in mainly the north and west of India.


{{BookCat}}</text>
      <sha1>habbitlesyr6tyw70az75tdfw52hb36</sha1>
    </revision>
  </page>
  <page>
    <title>Aros/User/Docs</title>
    <ns>0</ns>
    <id>13106</id>
    <revision>
      <id>4676722</id>
      <parentid>4675910</parentid>
      <timestamp>2026-10-18T10:09:04Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4676722</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="139898" sha1="do709s43ppv8ozqyik77k0tid08re8p" xml:space="preserve">{{ArosNav}}

==What is AROS==

Google translation 
[http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=de&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FUser%2FDocs German], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=nl&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FUser%2FDocs Dutch], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=fr&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FUser%2FDocs French], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=it&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FUser%2FDocs Italian], 
[http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=da&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FUser%2FDocs Danish], 
[http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=es&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FUser%2FDocs Spanish], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=hi&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FUser%2FDocs Hindi], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=zh-CN&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FUser%2FDocs Chinese], 
[http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=ru&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FUser%2FDocs Russian], 
[http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=pl&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FUser%2FDocs Polish], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=ja&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FUser%2FDocs Japanese], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=ko&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FUser%2FDocs Korean], 
[http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=pt&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FUser%2FDocs Portuguese], 


*Computer Hardware
*AROS (operating system)
*Applications and Games
*User


[http://www.osnews.com/story/15819 AROS] is one of the intermediate levels between the computer hardware and the user. It is an open-source, clean-room implementation of AmigaOS 3.x that can be run on many different computer architectures. It runs primarily on PC x86 32bit and 64bit but also on amiga motorola 68k and compatibles, some ARM like the Pi and Apple Silicon, RISC-V and some old PowerPC. 

This page will cover enough to be able to write the downloaded image to your preferred media, to run a LiveUSB, LiveCD or LiveDVD on your office/home PC (Live meaning you can test without changing your existing setup) and, ultimately, to use it.  

Intel / AMD PC hardware support mostly covers the years 2000 to 2024. At the moment, AROS is '''not''' recommended to be '''installed''' on a working vital data holding machine. Instead, writing to and booting from a '''USB stick''' could be a much better option. 

AROS is an hobby OS and can co-exist with Windows(TM), MacOSX(TM), Android(TM) or Linux(TM) and act as an alternative. 
Unfortunately, Aros has few developers so upgrades and improvements can take [https://sourceforge.net/p/aros/mailman/aros-cvs/ time to appear]. 

AROS core is now [http://en.wikibooks.org/wiki/Aros/Developer/IncompleteAPIs ~80%] finished and is usable, so keep in mind that the software is still considered ALPHA/BETA and in constant development. Currently AROS is fun to play with on a curiosity level, but it is also interesting to program. AROS has some multimedia features and has internet access.  

Most importantly, use AROS to its maximum potential as it stands now, find ways to have fun with it and share your experiences. 


Good Sites to visit 

: [https://www.arosworld.org/home.php Aros World User forum] 
: [https://arosnews.github.io/ AROS News]
: [https://www.facebook.com/ArosWorkshop/ Aros Workshop], 
: [https://www.osnews.com/topic/amiga-aros/ OSNews] 
: [https://www.reddit.com/r/aros/ Reddit]


: [https://archives.arosworld.org Aros Archives] 
: [https://aminet.net/ Aminet]
: [http://www.amiga-news.de/en/ English translation of German site]


: [https://aros.sourceforge.io AROS] with [https://aros.sourceforge.io/download.html ABIv1 downloads] 
: [https://github.com/aros-development-team/AROS Aros ABIv1 Codebase]
: [https://github.com/aros-development-team/AROS/issues register ABIv1 issues] and [https://sourceforge.net/p/aros/bugs/ old defunct bugs notification site] 


: [https://sites.google.com/view/arosone Aros One x86, x64] 
: [https://tinyarosdistro.flazio.com/ Tiny Aros x86 and x64]
: [https://arosnews.github.io/aros-portable/ AROS portable USB3 stick images of hosted Aros One x86 and x64 on debian] 
: [http://vmwaros.blogspot.com Icaros Desktop x86 now on sabbatical, very old edition] 
: [https://sites.google.com/site/arosaspireone AspireOS, of the netbook Aspire One, very old edition] 
: [https://github.com/deadwood2 Deadwood's builds], [https://www.axrt.org/download/aros/v11/ v11 64bit PC builds], [https://axrt.org/downloads-aros Updated i386 32bit PC builds], 
: [https://github.com/ezrec Ezrec x86 m68k mirror of old svn version]


: [http://arosalive.blogspot.co.uk/p/10-basic-aros-how-tos-tutorials.html Basic How To guides] 
: [http://arosgamer.blogspot.co.uk/ AROS Playground], [http://thewetmachine.net/tag/aros/ Jess Wet Machine], [https://aroshacking.wordpress.com/ Jon Robertson's AROS Experiences and FPC Free Pascal], [], 
:[http://www.apollo-accelerators.com/ Apollo Accelerators m68k], [http://www.amigablogs.net/ Amiga Blogs], [http://blog.a-eon.biz/blog/ Trevor Dickinson blog], 


: [https://forum.amiga.org/ Amiga OS AOS 3.x forum] 
: [http://eab.abime.net/ EAB Amiga] 
: [http://www.amigaworld.net/ AmigaWorld] 
: [http://www.ppa.pl/ Polish Amiga Like News] 
: [http://www.apollo-core.com/ Apollo Forum] 
: [https://amigaalive.blogspot.com/ AmigaAlive]
: [https://www.amigalove.com/software Disk Mags]
: [https://amigachristmastree.ultimateamiga.com/ Xmas Amiga Game Jam]
: [https://www.reddit.com/r/amiga/ Amiga]


== Distributions aka Distros ==

For end users there are distributions (ready made with selected apps aiming to be easy to use), mostly created and maintained by one person in their own workflow/style. They reuse the nightly boot compiles to suit their needs and possibly other end users. You are free to create your own if required. 

* For native 64bit Intel/AMD: [https://sites.google.com/view/arosone Aros One x64], [https://tinyarosdistro.flazio.com/ Tiny Aros],
* For native 32bit Intel/AMD which will run on 64bit machines: [https://sites.google.com/view/arosone Aros One x86], [https://www.tinyaros.it/ Tiny Aros], 
* For native 68k [https://sites.google.com/view/arosone Aros One m68k], [http://www.aros-platform.de/ AROS Vision], 

'''Please, keep in mind that the distros listed above use a different ABI (abi v11) , which is NOT binary compatible with the official ABI V1.'''
* For hosted Linux usb drive image [https://arosnews.github.io/aros-portable/ x64 Debian hosted version of Aros One], 
* For hosted ARM there is [https://github.com/jonx/AROS-AArch64/releases alpha for Apple Silicon] and [https://aros.sourceforge.io/nightly1.html RaspberryPi Pi3, Pi4, Pi400, Pi5, 500+ raspi-aarch64-system native 64bit] 


AROS was originally developed on Linux but can run on an Intel-based Linux distro as an app. As time has gone on, it can be run as an app on many more operating systems (Windows, FreeBSD, Linux and limited on MacOS). This may sound strange: an OS running on top of another OS. 
Basically, this is to take advantage of drivers (audio, internet, graphics, etc.) and compiler environments, in the existing OS, with which people may be already familiar. The term we use for what AROS does is &quot;Hosted&quot;. 

AROS Native is the term coined to describe AROS being run without any OS underneath it. It runs alone just like AmigaOS(TM) did. As this version does not benefit from &quot;Hosted&quot; drivers, dedicated ones have to be ported/written. Hence the smaller range of supported hardware / peripherals. We have other pages highlighting this support 


AROS is open source so basically everyone can take part. The source is public on github and there are new commits most days. AROS is automatically compiled daily, result are the nightly builds hosted on Sourceforge. The nightly builds are only used for testing changes, testing software and the starting point for distribution maintainers or even your own distribution. They are very basic, miss some functionality and apps like web browsers and generic general appearance which can be changed. 

* The [https://sourceforge.net/projects/aros/files/nightly2/ Nightly2], [http://aros.sourceforge.net/download.php nightly builds File Release Service] or [http://aros.sourceforge.net/downloads/ Sourceforge Project Web builds] are made automatically every night directly from the Github and in the past, SVN (Subversion) tree and contain the latest code for the AROS operating system. It should be noted that the builds have not been tested in any way and can be horribly broken but usually are not. 

*ABIv1 standard for most nightly builds, it is where the most work is done by developers 
*ABIv11 offspring aka fork of 64bit PC ABIv1 i.e. another PC 64bit build 
*ABIv0 standard for PC 32bit intel / amd PC distributions for historic reasons 


==Media==

AROS media tends to boot in this tier list of media types, first internal HDD SSD, CD DVD drive, and finally usb drive (last two can depend on bios boot order) 

* USB .VHD 

[https://sites.google.com/view/arosone Aros One x86 and x64], with md5 below 

&lt;pre&gt;
0a656d53a9c902e9934000d8392e30ec *ArosOne-USB-1.3-64Bit.zip
7dd7119ab3e56d75ee852c137226b4d7 *ArosOne-USB-v1.2-x86_64-v11.zip
cf906eeaad4a83b3520b1896bdc6b0d3 *ArosOne-USB-v1.1-x86_64-v11.zip

e2eb8fe8cfd61c567b0152a61cf85251 *ArosOne-x86-v2.8-USB-IMG.zip
559909c75c2f56472c74267a7d075355 *ArosOne-x86-v2.7-USB-IMG.zip
93da5898508c1a8c05bb8991ab7bd117 *AROS One Image-USB-2.4.zip
59fcabd7090e47f12d54f7eb78cf0f45 *ArosOne-x86-v2.2-USB-Image.zip
24fb8de726ae8fc5fe5bac6d30f03dc5  ArosOne-x86-v2.0-USB-Image.zip
f3d725e990072edce633b59747911b6b  ArosOne-x86-v1.8-USB-IMG.zip
e089a24ae310e92fcc407a0125602ce8  Aros-One x86-IMG-USB-v1.6.zip
&lt;/pre&gt; 


[https://tinyaros.flazio.com/ Tiny AROS]

22bc993625b7c75b17263c0cc7e7baaa *Tiny Aros_copy.vhd (March 2024) 


There is usually a vhd image inside the zip that can be written to USB sticks which is so much faster than the old ISO written to physical CD DVD method. This .vhd can be written to an USB stick / ssd with these pieces of software below but it will erase the previous contents from the usb 

Windows - [https://www.raspberrypi.com/software/ RPi Raspberry Imager, use custom and see all files], [https://hddguru.com/software/HDD-Raw-Copy-Tool/ HDD-Raw-Copy-Tool], [https://rufus.ie/ Rufus up to version 3.20 may work with VirtualBox HD vhd images with Win7 but not some Rufus 4.x versions], [https://etcher.balena.io/ Balena Etcher but may spy on you], 

Linux   - [https://www.raspberrypi.com/software/ Raspberry Imager Ubuntu], Suse Image / Multi writer, dd, 

Mac     - 


* Virtual Machine .ISO or CDs DVDs 

 The native iso images are currently not compatible with Ventoy, Yumi, MultiBootUSB, Easy2Boot E2B, or similar 

&lt;pre&gt;
617a905b1665128c5e05f94dcc48e7f1 *AROS-One-v1.3-64Bit-v11.zip
11c8a147fcad7ecf52ae3a43e1934b69 *ArosOne-DVD-v1.2-x86_64-v11.zip
f93053d3b9ccf304d7e6ac3389e1987b *ArosOne-DVD-v1.1-x86_64-v11.zip

86d808a40dc7be389a758799a9b4f595 *ArosOne-x86-v2.0-ISO-DVD.zip
f1fc8599ef6a39e5df394e0f41d55526 *AROS-One-x86-ISO-DVD-v1.6.zip
&lt;/pre&gt;


You can use a virtual emulator like VirtualBox, VMWare to mount the iso image which can then be used to boot and/or install to USB. 

No current software can write an AROS ISO to a Pendrive. The author of ‘Rufus’ (who used an Amiga 500 as a child) once tried, but when he saw the system composition, he said he was unable to do it.

The solution is to boot the ISO from a VM (WMware, VBox), then install the AROS build on the Pendrive, which will eventually become a Live Pendrive that can be booted on a PC.

The only precaution is that in some cases it is necessary to thoroughly clean the Pendrive of any partitions and remove any bootloader that is not AROS. The Pendrive must remain raw without any partitions.

You can clean the USB stick on a PC with a program that manages hard disks. You need to do a partition wipe. On some USB sticks, you can clean it with InstallAROS.
For some USB pendrives, please use a reputable partition editor to remove any and all partitions from a usb pendrive as HDToolbox cannot do this task sometimes with a wipe all option. 


Previously the only installation option was CD-RW or DVD-RW, since the whole system can be burnt onto a single disk and can be reused when the next version is released. Good branded discs like Taiyo Yuden (later JVC) or Verbatim should be used to reduce frustration later. The days for this media is gone but kept here for information 

Since nobody currently sells AROS on any other media, you will need access to a CD/DVD burner to create the installation disk yourself. After it is on a CD or DVD, then access and writing to USB pendrives becomes available (this should be viewed as an outdated or last resort alternative method now), as well as using good USB manufacturers like Sandisk, Kingston, etc. rather than some other no-names. 

Try burning it to a CD-RW or DVD-RW using your CD/DVD burning program (most burning software have a burn iso option). The ideal writing speed is 2x or 4x, higher speeds can give errors and problems.  Check the writing integrity of your CD or DVD if your software has an option to do so before going any further. 

Standalone portable usb cd dvd drives do not boot physical burnt discs, please use an internal ide sata drive instead. 


* SD-card
For [https://aros.sourceforge.io/nightly1.html ARM Pi Aros 64bit], copy the files onto a FAT32 formatted micro SD card. 


==Booting==

The LiveUSB, and in the past LiveCD LiveDVD, is designed to trial (test drive) various operating systems without having to install them to your working system. 

Since 2011, UEFI was introduced to replace the original PC BIOS which made booting media more confusing. Some changes in the UEFI/bios may be needed 

*go into the bios using esc, f2 or f? and disable the Security -&gt; Secure Boot and maybe apply option for Legacy IDE mode 
*you may have to press F9, F10 or F12 or p on boot up to present a device boot options like USB or CD/DVD 
*disable the Fast Boot config so it would recognize portable DVD-drive and changed the Boot-sequence

Secure boot was introduced by Microsoft and later consortium, control what operating systems work with Secure Boot via shims. 
For Aros, it is best to disable and save the turn off change to Secure Boot (if you dual boot with Windows this will cause issues with further Window boots) 

 For the best experience, it is advised to install to another SSD than the one Windows resides on. 

The grub part of the boot should be fully automatic, and you should see a multiple choice graphic card screen after 10 seconds for USB or 40 seconds CDs and DVDs. 
If boot does not occur within a minute, please reboot and choose the VGA boot option as it relays a message stream so you can see where the issue lies. 

After the grub graphics choice, AROS takes over the booting and any issues can arise here 

If possible please use a branded usb pen drive as most of the time when we get reports of &quot;crashes right after grub boot selection&quot; it is mostly due to the recorded pendrive as they are made, notoriously on a will it work / will it fail nature, every time it is used. 
&lt;pre&gt;
So one usb drive written may stop at a System halted. Reset the machine. 
Or another pendrive will show give errors Smart Filesystem request - Volume 'Aros Live Drive' (DU0: usbscsi.device unit 0) There was an error while accessing this volume: 
Or if a FAT32 partition present - FAT filesystem - Device USBSCSI0P1 has a read error on block xxxxxxxx - 
&lt;/pre&gt;
Sadly, no drive even branded are resistant or totally reliable, so the only solution is to try another pendrive, and possibly to repeat, until no errors. 
It will give an indication on how reliable the usb drive could be. 


=====Advice for various machines=====

Some of the stages involved and shown on the display in a typical AROS boot start up 

&lt;pre&gt;
[MultiLoader]
[ELF Loader]
[Boot]

[HPET] 
[Kernel:ACPI]
[Kernel:APIC-IA32]
[Kernel:SMP APIC]
[HiddStorage]

ACPI: ????
ACPI Error 
[ACPI]AcpiOs????
[BattClock] Got RTC century offset 0x32 from ACPI 

[PCI] Scanning bus ? 
[AHCI] Sata 
[Vesa]  only if vesa is chosen as graphics option 

[ATA] detect hd &amp; cd drives 
[ATA0?] ata-identity 
[packet] fat.handler be.handler, etc. 
[DOS] 
[Storage:Bus]
[Storage:Controller]

[MSS] USB setup
[ehciInit] Port ? maps to controller ? 

[I2C] 
[ATI]
[drm] nouveau 
[AROSTCP]   if you have network driver prefs set up to start when booting 


&lt;/pre&gt;

; If boot fails, please give us some indication (pictures or videos) where the boot stops and the message(s) on screen. 


AROS's native SATA/AHCI driver doesn't always work. If you get errors related to ahci.device, try disabling it. At your chosen boot entry in the GRUB menu, Press E, scroll down to the ahci.device entry, and add a # or ; at the start of that line or delete it with Ctrl-K. Then press Ctrl-X or F10 to boot. 

If your disk isn't accessible at all with this change, you might need to change the SATA controller to IDE legacy mode in the BIOS: however, making this change will likely cause problems booting Windows on the same machine (if it's already installed). To disable ahci.device permanently, edit the text file &quot;SYS:Arch/pc/grub/grub.cfg&quot;, and remove the ahci.device line from all boot entries you intend to use.

SATA AHCI Timeout while waiting for device to complete operations with BIOS SATA entry set to AHCI mode stops at &quot;waiting for bootable media&quot; screen, changing BIOS SATA setting back to IDE mode may allow it to continue booting 

The ATA driver doesn't always work. If you get errors related to ata.device, try using the alternative in sys:devs/alt which is an older version.  Press E when your chosen boot entry is highlighted in the GRUB menu, scroll down to the ata.device entry, and change it to read &quot;module /Devs/Alt/ata.device&quot;. Then press Ctrl-X to boot. To make this change permanent, edit the text file &quot;SYS:Arch/pc/grub/grub.cfg&quot;, and change the path to ata.device in all boot entries you intend to use.


Further options (removing the &quot; &quot;) to add to the GRUB menus to disable certain other components for debugging:

&lt;pre&gt;
Disable AHCI                        &quot;AHCI=disable&quot;
Disable NVME                        &quot;NVME=disable&quot;

Disable ATA:                        &quot;ATA=disable&quot;
Disable ATA:                        &quot;ATA=nopci,nolegacy&quot;
ATA safe mode:                      &quot;ATA=nodma,32bit&quot;
Disable IDE from SATA:              &quot;ATA=32bit,nosata2pata&quot;
VIA / SIS with cdrom read io errors &quot;ATA=nodma,nopoll&quot; 

noacpi                   all [PCI] devices to be invisible to AROS. disk drives work but network, sound won't 
acpi=strict              if there are issues with sound after boot 

noioapic                 alternative to no acpi 

Set AHCI                            &quot;AHCI=force150/force300/force600&quot;
Disable AHCI/SATA:       comment out with a # ; or remove ahci.device line with Ctrl-K

Disable USB:             comment out # ; or remove pciusb.device and poseidon.library lines with Ctrl-K
Disable native graphics: &quot;nomonitors&quot;
USB3                     &quot;USB=xhci&quot; 
&lt;/pre&gt; 

Other useful grub command line options - nomonitors, noacpi, vesahack, nopoll 

Press Ctrl and X together (or F10) to exit and boot with the new options. Just experiment with different variations until successful. Those working options will need to be reused with every reboot of AROS until you can edit the grub.cfg and make it permanent i.e. install to hard disk or USB. 


* If you use VESA mode, you can see the debug log if you add 'vesahack' to the command  line.  This  will set up split-screen mode. In the upper half you'll see AROS screen, in the bottom - debug log. 
* ACPI ie. PCI hardware - If  you  get  crashes  at  early boot, try adding 'NOACPI' to the command line 


If you're having boot issues and have a null modem cable and a spare pc, a boot log is always useful. Edit your grub line to include debug=serial but would try with an with sysdebug=all in the line later as it can cause issues booting on machines with sysdebug=all enabled (corrupts the cpu initialization). 

However, if you feel you have found a genuine bug/fault in AROS that needs attention, please use the [http://sourceforge.net/tracker/?atid=439463&amp;group_id=43586&amp;func=browse bug submission form] to record as much information about what happened, why, and what hardware etc. you have so that people may try to assist you 


For Virtual machines VMWare VirtualBox, etc., attach and press play to start the ISO image 

If booting hasn't worked then it could be down to Bios/UEFI settings  


=====nvme.device=====

 Since 2018, nvme drives are standard on most machines 

The requirement is that a PC can boot with legacy mode/BIOS at the moment - Now as far as hardware goes on a newer machine with an NVME drive you may need to add NVME=disable as the NVME driver could potentially cause lockups. 

 This is still in testing and its' use should not be on or near precious own data 


=====AHCI=====

 Starting taking over since 2011 on a lot of machines 

* Check that UEFI (replacement for PC BIOS) has options set to remove UEFI SecureBoot option and apply CSM 
* SATA drive is set for Legacy or a mixture AHCI/IDE and not AHCI 


 AHCI sata can be very difficult to get working

Most Windows installs are already set to AHCI sata, changing this to a legacy IDE mode setting can help but please check if Windows will still boot. Some hardware like Lenovo laptops do not always like being set in legacy mode so only use as a last resort and aware of issues that can be caused. 

Now as far as hardware goes on a newer machine with an NVME drive you may need to add NVME=disable as the NVME driver could potentially cause lockups. 

With a 16C/32T chip machine, disable SMT and it should boot. 


=====ata.device for old BIOS's =====

 Pre 2010 this was the de facto standard method of providing settings to the computer at a lower level 

Some adjustments to the BIOS setup options are necessary (usually by pressing a key like DEL, F1, F2, F12 or ESC, p on the very early boot up of the computer). 

*Adjust booting options like moving USB hdd, CDROM higher as it is quite often disabled or placed lower by default, i.e. USB hdd, CD/DVD are placed at the top above the hard drive. Try looking here [http://www.windowsreinstall.com/articles/bios/ Windows] or [http://www.hiren.info/pages/bios-boot-cdrom Bios] or [http://www.wikihow.com/Set-Bios-to-Boot-from-a-CD-ROM Boot] or web search &quot;BIOS BOOT CDROM&quot;

* At the '''SAME''' time, check if the SATA/AHCI option is set to Emulate or IDE Legacy, though this can have '''issues''' with any OS already on the hard disk. If in doubt, do nothing and seek advice. 

* check that under BIOS settings you '''DO NOT''' have plug&amp;play OS selected as Aros at this point is unable to route interrupts on its own and needs the BIOS to do that. 

'''Save''' options changed at the end. 

PCITool can show if the motherboard chipset is in IDE mode. 
Class = 0x01 means STORAGE, Subclass = 0x01 means IDE. Also ProductID 0x3a20 resolves to non-AHCI mode in Intel ICH10 documentation.


==Installing==

We have a separate section [https://en.wikibooks.org/wiki/Aros/Platforms/x86_installing here]

We have a specific section for each CPU platform under the Specific platforms in the NavBar navigation bar on the right hand side menu 

error code (-6) when using the ahci.device (has writing to disk problem but not reading) is enabled. change this line in your grub and reboot 

&lt;pre&gt;
#module /Devs/ahci.device      &lt;&lt; disable
module /Devs/Alt/ata.device    &lt;&lt; add this line instead
&lt;/pre&gt;


==File structure overview==

AROS' directory structure is mostly identical to AmigaOS directory structure, with some additions.

AROS: or SYS: also known as DH0: (i.e. the drive partition with AROS system) has the following simplified list of the main drawers (Amigas term for directories/folders). 


{| class=&quot;wikitable&quot;
|boot:
| grub bootloader 
|----
|C:
| small apps, where AROS looks first for applications/games but will look at Tools, System afterwards
|----
|Classes:
| .class as well as datatypes 
|----
|Devs:
| .device .resource and in their own drawers (folders) .audio, .hidd, network, graphics 
|----
|L:
| where .handler files go 
|----
|Libs:
| where .library files go 
|----
|Locale:
| where help guide txt readme files go 
|----
|Prefs:
| applications that adjust or setup AROS functions and capabilities 
|----
|S:
| startup scripts (for the aros boot process '''not''' grub) are stored here
|----
|Storage:
| place to keep old or alternative device drivers
|----
|System:
| applications associated with AROS operating system
|----
|Tools:
| extra applications
|----
|Utilities:
| extra applications
|----
|WBStartup:
| copy applications here to autostart with needed icons, drawers, data etc
|----
|}

See [[Aros/User/DOS#Drives.2C_Files.2C_Assigns.2C_Directories|DOS manual: Drives, Files, Assigns, Directories]]


=== Filesystem ===

Whilst the kernel is the heart, the filesystem is the blood of the system they are split into two categories (only a few are supported) 
&lt;pre&gt;
Journalling     - SFS PFS3 but also NTFS ZFS XFS ext4 
Non-journaling  - FFS FAT32(VFAT) but also exFAT BtrFS ext2  
&lt;/pre&gt;

Filesystem options for AROS to install 
* SFS default 
* Professional File System PFS3 [http://eab.abime.net/showthread.php?t=52234&amp;highlight=pfs3+free&amp;page=13 only on motorola 68k at the moment] [https://github.com/aros-development-team/AROS/blob/e34170ea87da3b32935b60ed99d837b2b903a021/rom/filesys/pfs3/fs/mmakefile.src issues to compile on other platforms] 
* FFS very old now but left in for legacy usage 

Other [https://archives.arosworld.org/index.php?function=browse&amp;cat=driver/filesystem filesystems] for storage purposes 
* FAT32 favorite as most OSs support 
* NTFS (can lock AROS) 
* exFAT there is a [https://www.jkn.me/blog/bringing-exfat-to-aros/ standalone version] as well as the fuse based one 

The only filesystems that really NEED defragging (i.e. disk tidy up) are from Microsoft(TM) - exFAT/VFAT/NTFS
*SFS tries to do exactly the same thing, but in certain cases it doesn't do as well as PFS. But you can defrag SFS 
*PFS *minimises* the amount of fragmentation, but does not automatically defrags as it saves files to the drive 

The setup of the below filesystems is usually done by the distro maintainer but if not....
&lt;pre&gt;
Copy L/exfat-handler L:

DOSDriver or Mountlist entry for an exFAT partition make sure that the FileSystem and Handler are set as follows:

FileSystem     = exfat-handler
DosType        = 0x46415458
&lt;/pre&gt;

&lt;pre&gt;
Copy L/ntfs3g-handler L:

DOSDriver or Mountlist entry for an NTFS partition make sure that the FileSystem and Handler are set as follows:

FileSystem     = ntfs3g-handler
DosType        = 0x4e544653

Also to make a read-only mount you can set:

Control        = ro
&lt;/pre&gt;


The Smart File System (SFS) is a journaling filesystem used on Amiga computers and AmigaOS-derived operating systems. It is designed for performance, scalability and integrity, offering improvements over standard Amiga filesystems as well as some special or unique features.  

SFS is written in C and was originally created and released as freeware in 1998 by John Hendrikx. After the original author left the Amiga scene in 2000, the source code to SFS was released and its development continued by Ralph Schmidt in MorphOS. 

Its development has now forked; as well as the original Amiga version, there are now versions for MorphOS, AROS, AmigaOS 3, and a version for AmigaOS 4, which have different feature sets but remain compatible to each other.  Versions for AROS, AmigaOS and MorphOS are based on different branches.  

In addition, there is a driver for Linux to read Amiga SFS volumes, GRUB natively supports it and there are free drivers to use it from UEFI.  The Linux version is [http://home.elka.pw.edu.pl/~mszyprow/programy/asfs/ independent code].  

SFS (Smart File System) partially defragments itself while the filesystem is in use. The defragmentation process is almost completely stateless 

AROS SFS version has a 120GB partition size limit on hard disks and DVDs current 4gig size limit. 
The sources for the MorphOS 64-bit version of SFS were available but no porting to AROS has happened so far due to endian issues, etc. 

SFS Tools 
* GUI - arSFSDoctor, 
* CLI - sfscheck , [http://www.portacall.org/ sfsundelete], sfsformat, setcache hits a usability ceiling around the 10GB / 100,000 file mark, 

 sfscheck dh0: seek purge fraglist defragment

If there are two simultaneous file writes in progress and you reboot machine (or it locks up or crashes) you may end up with a corrupted filesystem. Although arSFSDoctor may help, you might have to copy the files to another partition, format the partition with the errors on and copy the files back. 


PFS / SFS are way more advanced and much much faster than the FFS. FFS is supported for legacy reasons only. 
The Professional File System (PFS) is a filesystem originally developed commercially for the Amiga and now distributed on Aminet with a 4-clause BSD license. It is a compatible successor of AmiFileSafe (AFS), with an emphasis on added reliability and speed compared to standard Amiga filesystems.  It also features multi-user abilities like the older MuFS. 

PFS has so many advantages including the important things, speed, the ability to recover all deleted files even simply same name by typing the command &quot;. Deldir&quot; convenient if done in Directory Opus, virtually deleted files are copied normally as if they had never been deleted, other convenience is to not ever invalidate the filesystem, just put it on top of the startup-sequence command &quot;diskvalid&quot;, which automatically corrects any irregularities in the system startup; PFS also provides a device for floppy which makes them very fast and takes advantage of the full capacity of the floppy including the area dedicated to the bootloader.

The device is split into two main areas. At the beginning of the device is the metadata section, which consists of a root block, and a generic array of blocks that can be allocated to store metadata. The rest of the device is another contiguous generic array of blocks that can be allocated to store data. The metadata section usually uses a few percent of the device, depending on the size of the device.

The metadata is stored as a tree of single blocks in the metadata section. The entire directory structure is recorded in the metadata, so the data section purely contains data from files. The metadata describes the location of data in files with extents of blocks, which makes the metadata quite compact.   

When a metadata update occurs, the system looks at the block containing the metadata to be changed, and copies it to a newly allocated block from the metadata section, with the change made, then it recursively changes the metadata in the block that points to that block in the same way. This way, eventually the root block needs to be changed, which causes the atomic metadata update.   

The filesystem is reasonably good at keeping files unfragmented, although there is a defragmentation tool available which will work on an online filesystem ie whilst being used. 

It was the first filesystem to introduce the concept of the Recycle Bin natively at filesystem-level to the Amiga, holding the last few deleted files in a hidden directory on the disk root.  

PFS version 5.3 was developed in C and a small portion of assembly code by Michiel Pelt.  There are endian issues to be overcome and adapting the small amount of m68k to C before use on intel based machines, etc.  


Autoupdate of files in a directory is already implemented in Wanderer, but not all file systems handle dos.library/StartNotify() in its full extent. It seems to work correctly in Ram Disk (thanks to AmberRAM handler), and it also works on SFS formatted devices. Other file systems might not yet have it implemented correctly though. 

The PC equivalent of the Amiga's RDB is the master boot record (MBR).


===Installing Applications===

The typical means to install applications under AROS/AmigaOS involves simply copying/extracting the archive (.zip .lha .rar .tar.gz) file containing the applications files to your own desired location i.e. drawer/folder. Once extracted, launching it by double clicking on an icon (recommended) or using the shell (alternative). Generally, this is on a separate partition from your AROS system files, however in reality it can be any location - including RAM: if you don't want it staying around too long especially when you switch off. 

At some time in the future it may be desirable for AROS to have a package-manager like subsystem able to retrieve information online about packages available for AROS and whether they update anything you currently have installed, however at the moment no such ability exists.


===User Data files===

AmigaOS has no notion of a default location to store user data files, and presently neither does AROS - though it may be desirable at some time to provide a common start location.

Some people, have extra small FAT32 partition(s) using HDToolbox, and not Qparted, to store data especially if a reinstall is ever needed. And then setup the usual Sys: (DH0:) and maybe Work: (DH1:) / Live USB (DU0:) and maybe Briefcase (DU1:) partitions. 


===User Environment configuration files===

AmigaOS/AROS stores persistent system configuration data in directory assigned to ENVARC:.  This, by default, points to SYS:Prefs/EnvArc.

During boot a copy is made to another assign, ENV:, which is for runtime usage.  Changes to the files here will not survive a reboot.

Setting the env variables is generally done by applications themselves, or when necessary by the user using the SetEnv command. SetEnv has a SAVE switch to force the persistent copy in ENVARC: to be written also for when you are sure the change should be permanent.

Under the standard installation of AmigaOS style OSs, ENVARC: is copied to ENV: upon startup, which, if you have a hard drive installation, is in RAM:, hence, ENV: ends up being RAM:Env.

ENVARC: is the Environment Archive, which is the permanent copy of ENV:, which is the Environment.  It's roughly like the Registry in Windoze. 

Most programs do (and all should) store their settings in ENVARC: somewhere, and load them from ENV:.  The effect of this can be seen in the Preference editors.  If you Save your preferences, they go in ENVARC: and ENV:.  If you click Use, they only go in ENV:.  If you reboot, normally, anything saved to ENV: is lost, and is replaced with a copy of what is in ENVARC:.

you can set the default public screen for any tool started from a cli with the PUBSCREEN variable. So open the pubscreen, set PUBSCREEN to the name and start newcli for example, then the new cli window (and all following windows opened from that window) will appear on that public screen.


===Drivers===

For certain hardware, e.g audio, networking and , there is no auto setup. Just like the original Amiga OS. 
For audio, use AHI in the Prefs folder to set Music and at least Unit 0 with the appropriate driver and press Save. For ethernet and wifi, please use SYS:Prefs/Network 

All hardware support is placed in the Devs drawer (folder/directory). The network drivers &lt;something.device&gt; go in the Networks sub-drawer. Audio drivers &lt;something.audio&gt; are put in the AHI sub-drawer. Graphics drivers &lt;something.hidd&gt; are put in the Drivers sub-drawer. 


==Configuring==

AROS has mainly decided on a MUI-like requester&amp;menu clone called Zune so changing the background, icons, font, menus can be done with SYS:Prefs/Zune 

AROS has several desktop GUI front ends like 
* DOpus5 Magellan II, Wanderer and Scalos (medium) 
* AROS Workbench, Workbook (smaller) 

File / Directory managers like Dopus4, MCAmiga, 

App Launch Shortcuts like FKey, BoingIconBar, right mouse click on magellan, wanderer desktop, Amistart, etc. 

General usability decisions - Prefs/IControl, Prefs/Locale, Prefs/Input, Prefs/Fonts, 


Select an icon with left mouse button and then right click the mouse button and selecting Icon -&gt; Information gains access to the tooltypes tab where information can be edited 

CLI in icon's tooltypes means 'run it as if it was run from shell'
If, on the other hand, the WB parameter (or no parameter) is present in Tooltypes, Wanderer will execute the binary and, if provided, the options included in Tooltypes. 

WBxCLI is very useful for adding options to DOS Commands.

Important: AROS has a different way of managing icons. If you have an executable file, you will never be able to add a project icon. AROS will automatically recognise that it is an executable file and will transform the icon into a tool icon.


Icons are typically now .png pictures renamed as .info e.g. so Office application name would have a Office.png renamed as Office.info or MyApp.png as MyApp.info, etc.  

Leave Out menu option to leave app icon on desktop 

To select multiple icons and save their positions, click on the first icon and after while you hold the Shift key down select further icons and don't release it before SnapShot is finished.  You can also select a whole group of icons by pressing the LMB at the top left of the icons and while keeping the LMB down moving the power towards the bottom right. A expanding bounding box will appear and all the icons within it will be selected.  

Clean Up menu option (right mouse button -&gt; Icons) rearranges icons in a drawer or disk window into a neater condition. To use, open the window to rearrange and select Clean Up. To keep the icons in the new positions, select all the icons (shift key or mouse selection) and select 'Snapshot' and then Window and then again with All.  

In DOpus5, Scalos, wanderer, most files have an icon file associated with it. To change the default tool, select Icon menu, Information, and change the default tool string. For example, you could use Multiview, Editor and so on for most text, graphics and some sound files as long as the appropriate Datatype classes are installed. For scripts, set the tool to C:IconX 


We have new Icon edit tools in progress but if you need to...
 C:Join Image1.png Image2.png TO MyFile.info
is enough to make a dual state icon from two png images. You can then use Wanderer's menu Icon/Information on it to edit its fields and tooltypes.

[https://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/icon AISS toolbar images] unpack unarc them into RAM: and copy Images directory to SYS:Prefs/Presets/  AISS icons are looked for in PROGDIR:, PROGDIR:Images, SYS:Prefs/Presets/Images and then in TBImages: according to Open Amiga guidelines.  

there is Demos/iconscale which could be launched from S:User-Startup with two arguments, telling it the horizontal and vertical size. IE something like 
 Demos/iconscale 40 40
It will shrink icons... not sure if it will be very nice though. it doesn't work for the icons on the main desktop. 

there is an option to scale an icon to a bounding box afair, try iconsize followed by two numbers, like:
 iconsize 32 32

Is there any way in AROS to change an icon type from Project to Tool or vice versa?
Either the SIT option of [ ProcessIcon], or the TYPE option of HandleInfo (not sure if this one works at all, please test with care).
 processicon sys:pathoftheicon SIT=Project 

SIT Set type of ICON. Allowed types are: &quot;Disk&quot;, &quot;Drawer&quot;, &quot;Tool&quot;,  &quot;Project&quot;, &quot;Garbage&quot;, &quot;Device&quot;, &quot;Kick&quot; and &quot;AppIcon&quot;.

Btw, are your icons, the #?.info files, writable, is the W flag set ?


'''Decoration''' is Aros' way to provides a way to hide the old Workbench 3.1 style of windows and screens. In Prefs/Appearance some decorative theming elements need work 

Themes - SYS:Prefs -&gt; Appearance 
The default content of Prefs/Env-Archive/SYS/themes.var should be &quot;themes:ice&quot; but can be changed via the Appearance prefs, please do NOT click the Use button. Its useless. As you know, it will ask for the theme volume. Just pick the theme you want, click on Save, then reboot. 

* Decoration is on. Any time trying to change theme, you get: &quot;Please insert volume Theme: in any drive&quot;? 
You could check if you find SYS:System/Themes or if it is missing. Then you could open startup-sequence which you can find in drawer &quot;S&quot;. There should be a line: 
 Assign THEMES: SYS:SYSTEM/THEMES &gt;Nil: 
This does the trick. 
Open a shell and run: 
 Assign THEMES: SYS:SYSTEM/THEMES 
Than start the Theme prefs again... this should work 

* The theme is the only thing that could slow the system a bit, but it's not that performance impacting on most uses, and you can switch it off completely. Remove C:Decoration from the bottom of the file sys:s/startup-sequence. 

In each theme directory is 
*Env-Archive -&gt; Zune -&gt; global.prefs
*images -&gt; Gadgets -&gt; 20x20 pngs for Down etc 
*menu -AmigaKey - Background - Checkmark - SubMenu and config
*system - Arrowdown, Arrowleft, Arrowright, Arrowup, etc 


There is an [https://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/theme ALua/Zulu script] built for faster Wanderer skin management. You can modify config files, install new (wdz format/zipped skin files) and delete skins via the Theme Manager. This has not been updated in a long time and may not work. 


Certain features are added if from Tools/Commodities like Blanker screensaver, ClickToFront and DepthMenu with .info icons are selected and dragged to /WBStartup folder 

Most apps can be autostarted by copying into SYS:WBStartup directory folder 
e.g. WeatherBar.zip can be downloaded, unzip and the contents of the zip copied to wbstartup folder 
 ClicktoFront and .info to SYS:WBStartup so always be activated when turning on the computer 

or add a text line to user-startup is SYS:S (scripts version of wbstartup) 

e.g. standard Amiga / AROS does not allow clicking of background windows to come to the front to make it easy to get to the window you need but it has the ability if these apps are copied again to WBStartUp or are added to SYS:S/user-startup script 

 run QUIET sys:Tools/Commodities/ClickToFront &gt;Nil: 
 run QUIET sys:Tools/Commodities/DepthMenu &gt;Nil: 
 run QUIET sys:Tools/Commodities/Blanker seconds=300 &gt;Nil: 


Exchange controls Commodities and can be opened with alt, ctrl, h 

*AltKeyQ uses left Alt key to add strange letters 
*AutoPoint 
*Blanker screensaver 
*ClickToFront allows windows to be easily brought to the front 
*DepthMenu adds menu to select window easily 
*NoCapsKey
*Opaque 
*FKey - Although there are heaps of docks, menus and other launcher programs on the Amiga like OSs, FKey has got to be one of the quickest once learnt ways to launch programs, and it comes with the OS. In SYS:Tools/Commodities, the FKey commodity (Ctrl Alt F) allows you to make actions assigned to some combinations of keys 

&lt;pre&gt;
ALT TAB       Cycle Windows
              Cycle Screens
              Enlarge Window
              Shrink Window
              Toggle Window Size
              Insert Text
              Run Program
              Run Arexx Script
&lt;/pre&gt;

e.g.
&lt;pre&gt;
LAmiga F1               = Avail Flush
LAmiga F2               = Open Prefs
LAmiga F3               = Finder
Alt Tab                 = Cycle Windows
LAmiga Tab or M         = Cycle Screens
Alt Up arrow            = Enlarge Window 
Alt Down arrow          = Shrink Window
Alt Home                = Toggle Window Size 
                        = Insert Text             
LAmiga e                = Run Program             
                        = Run Arexx Script        
&lt;/pre&gt;

If your FKey GUI pops up when you start your Workbench up and you don't want it to, click once on the icon, go to the Icons-Information in the menu and make sure it has the tooltype set &quot;CX_POPUP=NO&quot;. 

Now let's launch it and assign the locale switching. After you double-click on FKey icon, launch the Exchange, choose the FKey from list and click the Show button. This will invoke the FKey window. You can see the ALT TAB in list assigned to window switching. Now enter the first key combination, say, ALT Z and go to the right panel. Choose Launch the program from pulldown menu and enter SYS:Prefs/Input as an argument. Append the USE switch and english preset name to the string as shown:

SYS:Prefs/Input USE SYS:Prefs/Presets/english

Click on the New Button to add the another combination. Now set the combination for your locale as shown above, replacing English name with your preset name. Click New button again and then Save Settings. Now you can use defined combinations to switch the layouts.


There is a system wide ARexx script capability (based on regina) that can manage many file manipulation task(s) but this would work only with those program that support [https://en.wikibooks.org/wiki/Aros/Developer/Docs/Rexx ARexx] like 

*Desktop - DOpus5, Scalos 
*Dock - FKey, 
*Files - Multiview, DOpus4, 
*Internet Apps - Odyssey, WookieChat, 
*General Apps - 


the shell can be modified with escape strings but not needed in most cases 


 Common Keyboard Shortcuts

&lt;pre&gt;
RAlt Right Alt Key 
LAlt Left Alt Key 
RWinKey Right Windows Key 
LWinKey Left Windows Key 
RAmiga Right Amiga Key (if one)
LAmiga Left Amiga Key (if one)
&lt;/pre&gt;

;Bootup Options 
:Spacebar during boot, enters the bootmenu which allows a boot without startup sequence, etc  

;Left Click 
:LAmiga = LWinKey = F11 

;Right Click 
:RAmiga = Help = F12 

;Mark 
:RAmiga and B 

;Cut 
:RAmiga and X 

;Copy 
:RAmiga and C 

;Paste 
:RAmiga and V 

;Search 
:RAmiga and S 

;Mouse Movement 
LAmiga and together with arrow keys - shift as well at the same time as well to move faster 

;Mouse Selection 
LAmiga and LAlt to select 

;Screen Switching 
LAmiga and M or N 

;HELP key 
Can sometimes be mapped to F11 but can be changed via FKey 


ComKeyRemapper or AmigaKeyremapper could swap RAmiga to another key press 


===DOpus 5 Directory Opus Magellan II===

Dopus 5.x is a whole desktop replacement on the Amiga Workbench (Desktop). Please describe any replicable errors [https://github.com/BlitterStudio/dopus5/issues here] 

DirectoryOpus app will assign DOpus5: to it's PROGDIR: automatically but if not add the below (edit SYS:System to suit where Dopus5 was installed) to your startup-sequence 

&lt;pre&gt;
Assign DOpus5: SYS:System/DOpus5 
DOpus5:DirectoryOpus 
;DOpus5:C/LoadDB
&lt;/pre&gt;

Left mouse button clicked twice on the desktop background brings up the Device List window. 
Green strip notifies SRCE (source) and if another is open it will be red for DEST (destination). clicking on the red strip changes to green 

Word list of actions with a left mouse click on the DOWN Arrow and directory stuff with &lt; button which mirrors the icons at the top of each lister 

single-key hotkeys? exactly the same as in dopus4, edit your functions (button bank, toolbar, menus etc.) and under the flags gadget is a key gadget, just click in it and press the key you want to use.

As for the extra text field... try turning off Extended lister key selection in environment / miscellaneous.

Shift and click on the icon - runs the icon 


DOpus5 Magellan 2 Directory folder drawer structure 
&lt;pre&gt;
ARexx       - Arexx scripts .rexx and .dopus5 to perform tasks 
Buttons     - 
Commands    - 
Desktop     - 
Environment - two environment files bundled:
 default gets loaded if you run DOpus as a normal app
 workbench gets loaded if you run DOpus as a WB Replacement (with LoadDB on startup)
Filetypes   - 
Groups      - 
Icons       - 
Images      - 
Modules     - compiled tasks 
Settings    - 
Sounds      - 
Themes      - 
WBStartup   - Use this if standard SYS:WBStartup gives cannot wait error messages 
&lt;/pre&gt;


Settings -&gt; Environment -&gt; Display -&gt; Workbench (Use) 


*Settings -&gt; Clock (add to title bar as well as the date) 

*Toolbar  -&gt; Editor (Right Win Key together with 1) for Copy, Move, Delete, etc above the Device List 
*Menu     -&gt;  (Right Win Key together with 2) 
*Buttons  -&gt; Editor (Right Win Key together with 3) 

*Settings         -&gt; Environment (Right Win key together with 4) for Backgrounds, etc 
*File Types       -&gt;  (Right Win key together with 5)
*User Menus       -&gt;  (Right Win key together with 6)
*Hotkeys          -&gt; Setup for quick shortcut keypresses (Right Win Key together with 7) 
*Scripts          -&gt;  (Right Win key together with 8)
*Icon Positioning -&gt;   (Right Win key together with 9)


Each Dopus5 theme are stored in a separate directory, named appropriately, which contains further sub directories 

* Font (amiga bitmap fonts)
* Screens (jpg or any picture supported by datatypes but not animations) 
* Sounds (wav but not iff 8svx ) 
* Icons (png newicons glowicons ) 
* Patterns (iff jpg png ) 


Just use wildcards in background filenames and you get a different picture every reboot 

For example, configure in Environment -&gt; Backgrounds -&gt; Desktop something like this:
&lt;pre&gt;
Work:Pictures/Backgrounds/#?
...or 
Work:Pictures/back#?.iff
...etc...
&lt;/pre&gt;


[https://aminet.net/util/dopus arcdir and themes]  


If you want to change the backdrop pic after a period of time, paste below into a text file called dopusrandbg.rexx and place in DOPus5:ARexx 

&lt;pre&gt;
/* Changes DOpus background image forever

   Start with:
   Run &gt;NIL: RX dopusrandbg.rexx 
*/

if ~show(&quot;L&quot;, &quot;rexxsupport.library&quot;) then do
	if ~addlib(&quot;rexxsupport.library&quot;, 0, -30,0) then exit 10
end

/* Configure these two lines for your needs: */
minutes=1
picpath=&quot;Work:Pics/#?.iff&quot;

address DOPUS.1

do forever
	call delay 3000*minutes
	dopus set background '&quot;'picpath'&quot;' desktop center custom
	dopus refresh background custom
end
&lt;/pre&gt;


If you don't want to use/open rexxsupport.library just for DELAY() then use the DOS Wait command

&lt;pre&gt;
/* random diropus backdrop changer */
/* by paul trauth, 1999 */
/* to do: non-repeatable randomness? */

options results

parse arg path

address DOPUS.1

/* get current backdrop pattern so it actually changes */

dopus query background desktop custom
currentpatt=result
lastslash=lastpos('/',currentpatt)
currentpatt=substr(currentpatt,lastslash+1,(pos('&quot;',currentpatt,2)-lastslash-1))

dir=showdir(path,'FILE','/')
num=0
do while dir~=''
    where=pos('/',dir)
    if where&gt;0 then do
        file=left(dir,where-1)
        dir=right(dir,length(dir)-where)
    end
    else do
        file=dir
        dir=''
    end

    if left(file,1) ~='.' &amp; file~=currentpatt then
        do
            pics.num=file
            num=num+1
        end
end

which=random(0,num-1,time(s))
newbg='&quot;'||path||'/'||pics.which||'&quot;'

dopus set background newbg desktop tile precision exact
dopus set background on
dopus refresh background
&lt;/pre&gt;


Clock format commands available are defined by locale. They are:
&lt;pre&gt;
 %a - abbreviated weekday name
 %A - weekday name
 %b - abbreviated month name
 %B - month name
 %c - same as &quot;%a %b %d %H:%M:%S %Y&quot;
 %d - day number with leading 0s
 %D - same as &quot;%m/%d/%y&quot;
 %e - day number with leading spaces
 %h - abbreviated month name
 %H - hour using 24-hour style with leading 0s
 %I - hour using 12-hour style with leading 0s
 %j - julian date
 %m - month number with leading 0s
 %M - the number of minutes with leading 0s
 %p - AM or PM strings
 %q - hour using 24-hour style
 %Q - hour using 12-hour style
 %r - same as &quot;%I:%M:%S %p&quot;
 %R - same as &quot;%H:%M&quot;
 %S - number of seconds with leadings 0s
 %T - same as &quot;%H:%M:%S&quot;
 %U - week number, taking Sunday as first day of week
 %w - weekday number
 %W - week number, taking Monday as first day of week
 %x - same as &quot;%m/%d/%y&quot;
 %X - same as &quot;%H:%M:%S&quot;
 %y - year using two digits with leading 0s
 %Y - year using four digits with leading 0s
&lt;/pre&gt;
like %a %d-%b-%y %H:%M or 


A WB ARexx interface, you could enter a cli command as a menu item to open a WB drawer like this...
 RX &quot;address WORKBENCH;WINDOW 'device:drawer' OPEN&quot;
Where device:drawer is replaced by the path of the drawer to open. 

The ARexx script would be capable to manage such a task but this would work only with those program that support ARexx 

&lt;pre&gt;
dopus addappicon
dopus addtrap
dopus back
dopus checkdesktop
dopus clear
dopus command
dopus desktoppopup
dopus error
dopus front
dopus getdesktop
dopus getfiletype
dopus getstring
dopus matchdesktop
dopus progress
dopus query background, font, palette, pens
dopus read
dopus refresh all, background, icons, lister
dopus remappicon
dopus remtrap
dopus request
dopus script
dopus screen
dopus send
dopus set background, font, palette, pens
dopus setappicon
dopus version
&lt;/pre&gt;

&lt;pre&gt;
lister add
lister addstem
lister copy
lister clear value
lister clearcaches
lister close
lister empty
lister findcache
lister getstring
lister iconify
lister new
lister query active all, dest source
lister query abort, busy, case, dirs, display, entries, entry, files, flags, handler, header, hide 
lister query label, lock, mode, namelength, numdirs, numentries, numfiles, numseldirs, numselfiles
lister query path, proc, position, seldirs, selentries, selfiles, separate, show, sort, 
lister query title, toolbar, value, visible, window
lister read
lister refresh
lister reload
lister remove
lister request
lister set busy, case, dest, display, field, flags, handler, header, hide, label, lock, mode
lister set namelength, newprogress, off, path, position, progress, separate, show, sort, source
lister set title, toolbar, value, variable
lister select
lister wait
&lt;/pre&gt;

The '''command''' allows you to call internal DOpus commands from an ARexx script

&lt;pre&gt;
command all
command wait copy
command read s:startup-sequence
command source 12345 makedir name noicon
&lt;/pre&gt;


*SFTP secure encrypted comms over internet using libssh2 and zlib (different protocol to the two below) on port 22 
*FTPS secured with https like security on port 21 
*FTP not secure and unencrypted protocol over internet on port 21 (should not be used today on the internet but for your own server) 


===Wanderer ===


Wanderer prefs in the prefs drawer - Appearance tab and Workbench icon allows backgrounds (wallpapers) icon text sizes, colors, etc but cannot use #? or *.* in the backgrounds file entry to randomly choose pictures - [https://developers.google.com/speed/webp/docs/riff_container webp riff container] issues with this format but Multiview has none. 

Enable the bar, you need to edit the text file ‘statusbar.prefs’. The change is simple: just change “False” to ‘True’.

Prefs/Env-Archive/SYS/Wanderer/statusbar.prefs 


===Scalos===

[https://web.archive.org/web/20180922220139/http://scalos.noname.fr/ Scalos] is not an OS replacement, it's a Workbench replacement. It replaces the desktop and graphical file management components. 

Scalos is 100% Workbench replacement with most functions working like the original Workbench ones. Undo and Redo available for most window and icon operations. Fully multitasking so every window has its own task. While loading icons, any window function (e.g. Drag&amp;Drop) is available. 

24bit color support with window patterns - Unlimited and easily configurable via tooltypes. Optimised backgroundpatterns routine so patterns can be tiled, centred or even scaled to fit into the windows. Live updating window scrolling - Supports middle mouse button panning and drawer (folder) windows can be iconified on the desktop. 

Icon imagetypes with all types are supported such as backfill or complement. Configurable surrounding iconborder. Icon support also visually highlights files which are soft-links in the file system. Icon dragging is more stable and far less flickery on graphics cards. Whilst dragging, icons are displayed with text and they can become transparent over anything where they can be dropped. 

Single-window lasso mode, with scrolling window contents invoked by dragging mouse with configurable qualifier key. Text icon lasso selection used to ignore &quot;Name column selects text icons&quot; flag. Support for backfilled thumbnail icons, with selectable color and transparency. Added option to always generate square thumbnail icons with preview icons for images - Thumbnails can be permanently saved in icons. 

Supports PNG icons with alpha channel and real transparency and displays OS3.5 GlowIcons and are all scalable. Iconborders with variations (normal, shadowed, outlined). 

Completely configurable, filetype-specific user-definable popup menus and tooltips. Plugin system to exchange or add features and can enhance the Workbench and make it more configurable. 

Filetype plugins to display filetype-specific information. - Currently, EXIF information viewer for JPEG images is included. Plugin included for 100% support of OS3.9 Workbench features. Plugin included for AREXX API compatible to OS3.9 Workbench. 

Online update with updater.module


Scalos works also as a Workbench replacement. In this case the 'emulation mode' has to be set by using Scalos' own version of LoadWB and offers 
* Scalos uses the Workbench Screen for its windows instead opening a new one 
* AppIcon, AppMenuItem, AppWindow functions are redirected to Scalos
* all Programs placed in &quot;WBStartup&quot; should start 
* The Screen will be reopened in case of changes in ScreenMode and Palette settings


&lt;pre&gt;
v1.0 (V39.201) - November 1999
v1.1 (V39.212) - December 1999
v1.2b (39.220) - June 6, 2000
v1.2d (39.222) - 2000 (latest public beta executable)
v1.3 (40.7) (beta) - August 2, 2001
v1.3 (40.22) - September 25, 2002
v1.4 (40.32) (beta) March 31, 2005
v1.6 (41.4) - March 27, 2007
v1.7 (41.5) - August 12, 2007
v1.8 (41.6) - March 12, 2009
v1.9 (41.7) (beta) - March 15, 2010
v1.9 (41.8) (RC1) - August 25, 2012 open source 
v1.9.2 (41.10) Deadwoods' AROS late 2022 32bit and 64bit build unifying the code base of ` for AROS x86 ABIv0, AROS x86_64 ABIv11 and AROS m68k  
&lt;/pre&gt;


Distros may have Scalos files under SYS:System/Scalos or Extras:Scalos. Known [https://github.com/deadwood2/AROS/issues/75 bug list], 


 Certain files like Menu13.prefs, Palette13.prefs, Pattern.prefs and scalos.prefs need to be in SYS:Prefs/Env-Archive/Scalos they can be found in Scalos:Storage/envarc and country drawer 

or run the &quot;Scalos Menu&quot; preferences program. Note if already setup with sub-menu entries and then re-save your menu prefs as it will now generate a new/overwrite prefs file called &quot;Menu13.prefs&quot; in &quot;envarc:scalos/&quot;. The same is also required for the new Palette prefs update, click 'Save' and a &quot;Palette13.prefs&quot; file will be saved in to &quot;envarc:scalos/&quot; directory. 


&lt;pre&gt;
ASSIGN Scalos:             SYS:xxx/xxx DEFER   
ASSIGN Libs:               Scalos:Libs add    
;ASSIGN SYS:Devs/Datatypes  Scalos:Devs/Datatypes   add  
Assign Theme:              Scalos:Themes/Default_Theme add 
Assign Locale:             Scalos:Locale add 

Protect Scalos:Tools/browse.script s add quiet 
Protect Scalos:Tools/OpenShell s add quiet 
Protect Scalos:Tools/run.script s add quiet 

run Scalos:Tools/LoadWB 
;Scalos:Scalos
&lt;/pre&gt;

Add the above to SYS:S/startup-sequence or SYS:S/user-startup '''before any Wanderer entries''' 


In the prefs drawer (folder) is the big prefs app Scalos_Prefs which covers these user setup areas 
&lt;pre&gt;
About Scalos
Paths               - should be preset 
Startup             - WBStartup drawer contents should auto run on each startup 
Desktop             - edit titlebar, icon layout and in misc, auto leave-out (drag icon to desktop) 
Icons               - 
Drag and Drop       - 
Windows             -
Text Windows        -   in misc, drawer sorting at start of listing if needed 
TrueType Fonts      - use Truetype fonts rather than system ones 
Miscellaneous       - 

Plugins             - after adding oop/title_clock.plugin %ti %da does not work, maybe needs ASCII .prefs added 
Modules             - ??
Menu                - setup for MainMenu and PopupsMenu with New Menu, RE Name, Key: shortcut, Command Properties 
FileTypes           - already added def_Project icons and def_Disk (hdd sdd cd dvd etc) support 
PopupMenu           - tweak how popups appear 
Pattern             - Wallpaper backgrounds with Type DE, each pattern in the list can be edited, Save as Pattern.pre 
Palette             - change the color of things , Save as Palette.pre 
&lt;/pre&gt;


Scalos_Prefs - Pattern - Minimum options to be changed are 
*DE Desktop/Background 
*SC Screen 
*TW Window/TextBackground ie Text listing showing if icon type not recognised 
*IW Window/Background ie Icons showing 

 Workflow - In &quot;Pattern List&quot; tab, select New - choose a picture, highlight in list, click in number box under New button and slide to another number, click on &quot;Defaults&quot; tab and adjust Pattern numbers slider to choose right picture for each of the above options - Click &quot;Pattern List&quot; tab to check eveything is OK and click Save 

Pattern List tab on Patterns Page - Allows you to compile a list of pictures (one at a time rather than a whole folder e.g. with #? or *.*), assigning a number Nr to one or more of them for easy reference. Using this number you will be able to assign the pictures to specific windows on the Defaults tab Page. If multiple pictures have the same number, one of the pictures will be chosen randomly. This will allow you to have random desktop pictures, random window backdrops etc. 

Defaults tab on Patterns Page - Here you can set the defaults for the background pictures for the Desktop, Screen, Window and/or Text Mode throughout Scalos. 
Randomize every time [check box] - Usually Pictures with the same number will be randomly selected as soon as the configuration loads. If this option is set, the picture will be selected as soon as a window with the same number assignment is opened. 

*Fit size: The picture will be resized to the dimension of the new window.You *MUST* have set GUIGfx on. asyncron layout: Pictures will be loaded and rendered while the windows opens (Like original Workbench). If this function is 'off', pictures will always be loaded before opening the windows. 
*Use friendbitmap : The picture is present twice in memory for best speed. This option has no effect if V43 picture.datatype or GUIGfx are used. Always relayout: If &quot;Fit size&quot; is set, the picture will be scaled everytime the window's dimensions change.
*Randomize everytime: Usually Pictures with the same number will be randomly selected as soon as the If more pictures have the same number, one of them will be chosen randomly. 

Patternlist New/Delete : Add a new picture. After that you should assign a number to it. The picture will be rendered as tiles. configuration loads. If this option is set, the picture

Asyncron-Task priority: You can set the CPU priority for the Task if &quot;asyncron layout&quot; is set. 
&lt;pre&gt;
Desktop: Number of the Picture for the main window.
Screen: Number of the picture for the Scalos-Screen.
Window: Number of the picture for the Scalos-windows.
TextMode: Number of the picture for the Scalos-windows in Text Mode.
&lt;/pre&gt;


Popup Menu preferences fully configurable menus (includes ToolsDaemon and ParM launch apps import), including support for context-sensitive Popup menus configs for top pull down menus for apps, etc. 

 Workflow - Scalos_Prefs then Menu, New Item, New Command add name at top then in Command Properties e.g. add Workbench and location e.g. DOpus:DOpus4 for apps  Command for c apps or Rexx for scripts or Plugin for  or AmigaDos for modules 

&lt;pre&gt;
DESCRIPTION	NAME/A      This is the title that is displayed in the top line of any popup menu  
INCLUDE NAME/A          Name of file to be included. Path can be relative to &quot;Scalos:FileTypes&quot; 

POPUPMENU      Starts the popup menu description section for this filetype.
&lt;/pre&gt;

The following Subcommands are allowed inside popup menus:
&lt;pre&gt;
SUBMENU &quot;NAME/A&quot;
ENDSUBMENU 


MENUENTRY &quot;NAME/A,KEY/K,DEFAULTACTION/S&quot;
ENDMENUENTRY 

INTERNALCMD	&quot;NAME/A&quot;
WBCMD &quot;NAME/A,STACK/K/N,WBARGS/S,PRI=PRIORITY/K/N&quot;
AREXXCMD &quot;NAME/A,STACK/K/N,WBARGS/S,P=PRIORITY/K/N&quot;
CLICMD &quot;NAME/A,STACK/K/N,WBARGS/S,P=PRIORITY/K/N&quot;

ICONWINDOWCMD &quot;NAME/A&quot;

PLUGINCMD
MENUSEPARATOR

ENDPOPUPMENU

TOOLTIP 
ENDTOOLTIP
&lt;/pre&gt;

&lt;pre&gt;
Starts the tooltip description section for this filetype. The following Subcommands are allowed inside popup menus:

GROUP &quot;ORIENTATION/K&quot;
ENDGROUP  
MEMBER &quot;HIDE/K&quot;
ENDMEMBER  

HBAR 
STRING &quot;ID/K,TEXT/K,SRC/K,TEXTPEN/K,HALIGN/K,STYLE/K,FONT/K,VALIGN/K&quot;
SPACE &quot;SIZE/N/A&quot;

DTIMAGE &quot;FILENAME/A&quot;
&lt;/pre&gt;


Each theme drawer (folder) has these further folders 
&lt;pre&gt;
About            - 
Desktop          - 
FileTrans        - 
FileType         - 
Icons            - 
Menu             - 
Modules          - 
PointerIcons     - 
Prefs            - 
Sound            - 
Window           - 
&lt;/pre&gt;


*Plugins
&lt;pre&gt;
devicefilter.plugin       
persist.plugin            should a crash or reboot occur - next time Scalos started, all windows re-opened 
title_clock.plugin        add digital clock to title see more below 
title_envvar.plugin       %ev, which can be used to display the value (a string) of the variable in the titlebar 
title_freepens.plugin     
volumegauge.plugin        
wb39.plugin               
wbrexx.plugin             plugin adds a Workbench 3.5+ compatible AREXX interface to Scalos internals 
xtwindows.plugin          left or right ALT or left or right SHIFT keys when open/close windows 
filetype.plugin           then run FileTypes-prefs and customize the filetypes (eg import from a DefIcons-brainfile) 
menu.plugin               
&lt;/pre&gt;


*Modules - delete, empty_trashcan, execute, find, format_disk, information, iconproperties, newdrawer, reboot, rename, systeminfo, windowproperties 


*Tools - scripts like LoadWB, quit.rexx, open_volume.rexx, 


In Scalos_Prefs-&gt;Filetype-&gt;Recognition  you can define the filetypes and on &quot;Action&quot; you define specific context menu for all filetypes defined in recognition (similar to magellan)
there is the same you must show all first (list is only limited) so you created a file type AAABBB, you need to have def_AAABBB icon 

Associating files with &quot;Scalos_FileTypes&quot; is very simple, practically it is very similar to Dopus4, first you create the Def_icons to assign to the file type (will be seen automatically ), then run &quot;Scalos_FileTypes&quot; you add the extension, fill in the descriptor (MATCH or PATTERN etc..) and save 

then you create an appropriate entry in the list and rename it, if def icon exists it is shown. Below you can define how files are identified. Use &quot;pattern&quot;, similar to magellan to identify file by ending. Then you click on the shown icon and define in it what program is used when you double-klick on it and save it. On the tab action you can define popup menu for it. 

defined all archive types from XAD in &quot;filetypes&quot;. If you change to &quot;action&quot; and click on &quot;archive&quot; you can define the context menu that is shown if you do not define a specific context menu for a filetype


Reset to Default in Scalos_Prefs resets all settings so '''BEWARE''' 


&lt;pre&gt;
The Scalos desktop screen titlebar may be configured using the main Scalos Preference program. This oop/time_clock plugin adds some additional placeholders:

    %ti, displays the current time in the default Locale format. e.g. &quot;10:43:37&quot;
    %da, displays the date in the default Locale format. e.g. &quot;Saturday 14 July 2001&quot;

Using the supplied prefs program for the plugin, or editing the ASCII file ENVARC:Scalos/title_clock.prefs you can use the following standard Amiga Locale values to change the formatting 

    %a - abbreviated weekday name
    %A - weekday name
    %b - abbreviated month name
    %B - month name
    %c - same as &quot;%a %b %d %H:%M:%S %Y&quot;
    %C - same as &quot;%a %b %e %T %Z %Y&quot;
    %d - day number with leading 0s
    %D - same as &quot;%m/%d/%y&quot;
    %e - day number with leading spaces
    %h - abbreviated month name
    %H - hour using 24-hour style with leading 0s
    %I - hour using 12-hour style with leading 0s
    %j - julian date
    %m - month number with leading 0s
    %M - the number of minutes with leading 0s
    %n - insert a linefeed
    %p - AM or PM strings
    %q - hour using 24-hour style
    %Q - hour using 12-hour style
    %r - same as &quot;%I:%M:%S %p&quot;
    %R - same as &quot;%H:%M&quot;
    %S - number of seconds with leadings 0s
    %t - insert a tab character
    %T - same as &quot;%H:%M:%S&quot;
    %U - week number, taking Sunday as first day of week
    %w - weekday number
    %W - week number, taking Monday as first day of week
    %x - same as &quot;%m/%d/%y&quot;
    %X - same as &quot;%H:%M:%S&quot;
    %y - year using two digits with leading 0s
    %Y - year using four digits with leading 0s

 like %d %m %y or %a %d %B %Y %p
&lt;/pre&gt;


Shutdown -&gt; right mouse button Scalos, About, Reboot, Shutdown 


ToolTypes can be added to the Scalos.info icon like 
*SCALOS_PATTERNNO=&lt;number&gt; : background image matching the number 
*SCALOS_NOTEXT : The Icon will be drawn without Text.
*SCALOS_NODRAG : The Icon will not be draggable. Its position will be fixed.
*Module iconproperties - Added SCALOS_BROWSERMODE tooltype support

runcommand parameters... in which case:
&lt;pre&gt;
%p = parameters
%w = directory path
%d = device-name
%% = literal percentage token
&lt;/pre&gt;


With the help of the wbrexx.plugin Scalos gains support for more of the compatible arexx API 

If an arexx command produces an error you will find the error code placed in the WORKBENCH.LASTERROR variable.

ACTIVATEWINDOW
&lt;pre&gt;
/* Activate the root window */
ADDRESS workbench
ACTIVATEWINDOW root

/* Activate the &quot;Work:&quot; partition's window if already open*/
ACTIVATEWINDOW &quot;Work:&quot;
&lt;/pre&gt;

CHANGEWINDOW
&lt;pre&gt;
/* Change the root window; move it to position 10,30. * and change its size to 200100 pixels */
ADDRESS workbench
CHANGEWINDOW root LEFTEDGE 10 TOPEDGE 30 WIDTH 200 HEIGHT 100

/* Change the currently active window */
CHANGEWINDOW active 20 40 200 100
&lt;/pre&gt;


Most of Scalos' issue are due to the flexibility of its' user configuring nature but if 


The sort menu plugin needs to be ported from ASM to C.

IIRC Scalos has a command line option to fully replace Workbench/Wanderer.

The Theme: assign is used by both Wanderer and Scalos but I didn't have any problems using both at the same time.


The Program will be started from the Shell.
If &quot;WB Args&quot; is set, with the Argument &quot;%p&quot; will be replaced by the path of the activated Icons. The Program will started with the specified Stack value.
IconWindow: Scalos opens the window of the specified path.


PlugIn: Starts a Scalos Menu-PlugIn.
If a Menu Item with empty name is specified, Scalos displays a separator line.
It's possible to Drag&amp;Drop an Icon in the Configuration Window. All values will be set accordingly. Entries may be dragged across the list.


Mac-like selection : This function activates a multiselection method used on MacOS or Win95. Don't have to hold down shift to drag them. Clicking on an already activated icon will
not deselect all other icons. 

MMB move: The window contents may be moved using the middle mouse button. 

WindowPopup title only: PopupMenu for windows can be opened only on window's title bars. 

FullBench: Screen-Titles removed and Main Window set Full Size. 
Scalos Prefs. Go to Settings-&gt;Scalos-&gt;Prefs and then the Misc section. Remove the tick against Full Bench. If you've enabled it, the titlebar will disappear when you select backdrop.


Default Icons saveable : The icons which Scalos generates if &quot;show all files&quot; is enabled, can now be saved
using &quot;snapshot&quot; menu option. load DefDisk first : Try to read the icons first from the DefIcons Path before using disk info. 


Hide hidden files : If this function is activated all files or directories where the &quot;hide&quot; flag is set will not be shown.

Many of my Icons display more than once on the screen, while on the workbench all seems ok.
The Workbench filters double displayed icons, Scalos does not. Solution: please edit the &quot;.backdrop&quot; file and clear double lines.

Background images not scaled. GUIGfx option not set or guigfx.library and/or render.library not installed.

If working with CD's causes crashs or Scalos doesn't work correctly.
Most Filesystems doesn't support the ExAll function correctly. Disable &quot;Use ExAll&quot; in Scalos prefs.

Scalos doesn't start any program in the WBStartup. WBStartup Path may be set wrongly or Scalos was not started in Emulation Mode (LoadWB etc) 
Some programs will not startup with error message &quot;has not returned, wait some more&quot;? and &quot;unable to open your tool&quot; 


need a def_icon with the same name predefined, then create an appropriate entry in the list and rename it, if def icon exists it is shown. Below this can define how files are identified. 
* either &quot;pattern&quot;, similar to magellan to identify file by ending
* or 
Then click on the shown icon and define in it what program is used when you double-click on it and save it. On the tab action you can define popup menu for it. All in all handling is of course different to magellan but can do similar 

For the RAM Icon, to obtain this you have only to copy the icon in the Icon Path as &quot;RAM.info&quot; or &quot;Ram Disk.info&quot;. All functions will automatically be performed 

sometimes cut into half or quarters when scrolled off screen or drawers moved - settings issue probably  

Sometimes leaves initial drawer window imprint on desktop when moved - settings issue 


Scalos AROS released a [https://github.com/deadwood2/contrib/tree/master/scalos new build V2022-07-21] with the following changes noted:
&lt;pre&gt;
Fixed:
    Numerous crashes when working on 64-bit with 64-bit heap
    Wrong background color of Scalos logo on Scalos splash window
    Backgroung image of Scalos splash window and Scalos About window is not visible
    Icon labels on desktop and in drawer windows are displayed using Topaz instead of Arial font
    Font.prefs are not being loaded on 64-bit
    Font.prefs are being wrongly saved on 64-bit
    scalos.prefs are not being loaded on x86 and x86_64, scalos is using always default preference
    scalos.prefs are being saved on x86 and x86_64 in format not compatible with m68k 
    NewPopupmenu.prefs is wrongly written
    Plugins are not loading at Scalos startup
    wbrexx.plugin is crashing at startup on 64-bit
    Multiple controls missing on Scalos Prefs/Icons page
    System crash when clicking on def icon image on FileTypes Prefs/Recognition page
    Status bar, control bar, buttons sometimes don't have images displayed
    Buttons in Scalos About window have white corners rendered where they should be transparent
    Crash when leaving out an icon
    Crash when adding a User-defined Button to Control bar without setting it's properties in Scalos Prefs
    Crash when removing any button from Control bar in Scalos Prefs
    Scalos Prefs allows editing TTEngine font properties when TTEngine is not present causing crash in Icons/Labels and Text Windows/Fonts pages
    deficons.prefs are not being loaded on x86 and x86_64
    Reset to default in FileType Prefs and Save does not save preferences

Won't fix:
    Scrollbars visible on titles of TrueType Fonts, PopupMenu, Menu, FileTypes, Pallette and Pattern pages of Scalos Preferences

Not fixed:
    Wrong rendering on DualPNG icons 
    Refreshing drawer windows is slow 
    Starting Prefs/Locale or Prefs/Input from Scalos causes other preferences to fail 
    Desktop wallpaper is damaged where Splay window was displayed 
    When started from Wanderer, after saving Scalos Prefs, reload does not re-open main Scalos window
    Difference in behavior between Cleanup from popup menu and Cleanup from top menu - possibly due to missing plugin, check Cleanup association in Menu Prefs
&lt;/pre&gt;


===DOpus 4 Directory Opus===

Copy DOpus4 app to WBStartup directory folder so it starts on boot up each time 

Another method is add the below to the bottom of the user-startup script in SYS:S drawer/directory 
&lt;pre&gt;
run DOPUS:DirectoryOpus -i &gt;NIL
&lt;/pre&gt;
makes DOpus starts up in Iconified state at the top of Wanderer's screen. Left click on this to highlight and right mouse click to open. 


Just click on the sides of either outer edges of DOpus windows and it will display the parent device/volume list. 


DOpus4 saves it features in a PROGDIR:s/DirectoryOpus.CFG file which can be edited to suit anyones' needs, '''C''' bottom right button in DOpus4 and by reading the [https://arosarchives.os4depot.net/index.php?function=browse&amp;cat=utility/filetool Dopus4 guide Manual and Arexx calls].

*[https://www.youtube.com/watch?v=DCyXDs8baSE Pt1 Introduction] 
*[https://www.youtube.com/watch?v=7fiVmopiK9I Pt2 Dopus Config] 
*[] 
*[] 


*Button little rectangle with name inside
*Bank vertical stack of buttons 

 Buttons 
*Workbench app {f} i.e. first  use {F} for all selected items with app 
*AmigaDos  c type apps with arguments after 
*Arexx     
*Command   c type apps with no arguments after 

 Flags (most used)
*CD Destination to extract etc 
*Do all files
*Output window 
*Run asynchronously
*Workbench to front

*Buffer above 100000 for 64bit 


 Filetypes
Defines how certain files are handled like '''default tool''' 


 Screen
Fonts, set each element to any font 
Screenmode, Workbench Use (same screen like Windows), Workbench clone (like Linux workspaces) 

 System 
Shell startup, set to SYS:s/shell-startup 


===BoingIconBar===

User chooses the apps to add to the dock at the centre bottom of the screen but has to be done manually, please use Save afterwards 

Or easier edit the text file of SYS:Prefs/Env-Archive/iconbar.prefs and save 

&lt;pre&gt;
BOING_PREFS
;Tools
SYS:System/Shell 
SYS:Tools/DOpus4/DOpus4
SYS:Utilities/Editor
SYS:System/SysMon
SYS:System/Scout
Work:Extras/Internet/OWB/OWB
Work:Extras/Graphics/Lunapaint
Work:Extras/Graphics/ZunePaint
AROS:Tools/MPlayer/MPlayer
Extras:Internet/AmiFox/AmiFox
RAM Disk:Amelinium/Amelinium
&lt;/pre&gt;

right mouse click on bottom edge of screen where boingiconbar shows - select settings which opens BoingIconBar Preferences to add apps 

If no dock showing Add, to add apps click Add Program and search for the executable 

another method is to drag icons to ends of the bar and move them on the Bar using the Prefs/BoingIconBar 


===AmiStart===

On 32bit PCs only - auto generates the apps menu but scans the drive each time - AmiStart can choose apps you are not interested 

* how to disable annoying zune/mui 'bubbles'? 
try a right-click on AmiStart and release on Global settings. Then click on the bubbles gadget. Move the Show Bubbles slider all the way to the left.


===Fonts===

Install the #?.ttf files to SYS:Fonts/TrueType. Use SYS:System/FTManager to &quot;Install Font&quot; each #?.ttf file which will generate associated #?.otag and #?.font in SYS:Fonts. Use SYS:Prefs/Fonts to change system fonts and SYS:Prefs/Zune to change others. 

To achieve our goal we will use the Setup Locale, Input, Zune and Fonts, as well as The FTManager.

Begin

The first step you should do is to get the system to know that we speak and write in another language. What you need to do is to open the setup program and choose Locale country, and list &quot;preferred languages&quot; to put it first and then English. If you want the tab &quot;Time Zone&quot; and select city of residence to set the clock correctly. Of course we save our changes and continue opening the setup program Input. This sets the keyboard language as our beginning. When the language layout was created there was no option to switch to Aros keyboard (layout switching), so to write in the language you had to hold down Alt, something you encounter in other functions. This time working with the team of Aros to create a new keyboard layout to replace the old so we can get rid of the button Alt. For now though let only selected this layout and do not turn the switch on the keyboard.


Custom Keyboard Layout

[http://repo.or.cz/w/AROS.git/tree/HEAD:/workbench/devs/keymaps keymaps are in place but unfortunately when they are not, then indeed things become a bit 'low-level' as it involves redefining some tables with values that match your keyboards] 

only need to add your compiled table as new keymap. 

So taking a little peek here shows that it should be possible to compile using
 gcc -opc105_tr pc_105.c -nostdlib
where the pc105_gr/pc_105.c needs to be replaced with your own adjusted keymapname/c-file

[https://en.wikiversity.org/wiki/Enabling_Greek_Characters_on_Your_Keyboard General overview of Greek letters on keyboards] 


Installing fonts

*[http://aminet.net/package/util/wb/EPAGrWb System jaggy] 
*Outline resizable .font .otag 
In this step you need to download some fonts that can support the encoding in our system. The easiest way is to run the script &quot;Download Fonts&quot; you'll find in the folder OWB. This script downloads from the Internet, and unpacks some fonts for OWB web browser, which is placed under the folder Fonts:TrueType. But as these can only be used by OWB and not the system, which unfortunately does not see. To make them available to the rest of the system, open the program FTManager, you will find the folder AROS: System /. From there select the field &quot;Codepage&quot; option &quot;ISO-8859-7&quot; and list the font &quot;Arial&quot; and &quot;Regular&quot; form in which you must double-click with the mouse. In the window that appears, select the bottom right the checkbox &quot;Anti-aliasing&quot; button and then &quot;Install&quot;. Immediately folder Fonts: created files &quot;arialregular.font&quot; and &quot;arialregular.otag&quot;, which are necessary in order to see the system font. Do the same steps if you wish for other fonts.


Final stages 

After completing the above, open the folder AROS: Prefs / and run the program settings Fonts. In the new window, select the fields &quot;Icons&quot; and &quot;Screen&quot; as the font &quot;ArialRegular&quot; to the size you want. In the field &quot;System&quot; to give &quot;s_courier&quot;, which, however, because it is not True Type Font support Antialising, and may seem a little broken. You can also use the CourierNew, if you have installed the above procedure. After you save the changes and open the Zune program settings. In this set the &quot;ArialRegular&quot; font fields in tabs &quot;Windows&quot; and &quot;Groups&quot;, and save the changes. Reboot the system. To make sure that the above worked properly run NoWinED, which you will find under the folder AROS: Tools /. If that everything is working correctly you will see the menu and the settings window with Greek letters. You can also write in the language using the button Alt. Second program that you can try, which is fully localized, is WookieChat, which you will find in the folder AROS: Extras / Networking. And in this place all the menu and settings window works. 


===Windows===

*Intuition
The window you position and resize, you right click on that windows title bar and in the dropdown menu you snapshot from there.  Right click to show menu -&gt; Window -&gt; Snapshot Windows or All but it will NOT work if that folder has no icon (e.g. Disk.nfo) attached to it. You need a folder icon. The window information gets saved in it.  

As for maximising the window using a shortcut key - Alt and up arrow key 

The AROS-Shell windows can be moved, resized by editing sys:s/startup-sequence 

&lt;pre&gt;
; run shell
run QUIET c:newshell &gt;NIL:
&lt;/pre&gt;

; slimmer right aros the screen 
run QUIET c:newshell con:0/150//300/ &gt;NIL:

; top right corner scr-x scr-y win-x win-y
run QUIET c:newshell con:600/150//300/ &gt;NIL:


*EdgeSnap 

Commodity EdgeSnap allows resize and position windows on your screen by dragging them to the edges but not corners of the screen and/or other windows 

EdgeSnap Prefs (once pressed Use button) lets you arrange windows but not different applications in layouts half (left or right) or full size (top) and choose to adjust the border padding 

There is outline to show shape taken to aid placement and space available 


*Zune - AROS version of MUI
Magic Menu type functionality is implemented in IControl preferences editor: in the frame called Menus, switch type from Pull-Down to Pop-Up and/or iControl just tick the sticky menu option. 


Windows outside screens causing a problem either uncheck &quot;Offscreen move&quot; for windows in IControl prefs editor. Or use FKey commodity and define two key shortcuts: 

* the first using the command &quot;cycle windows&quot; (for example ALT TAB); 
* the second using the command &quot;rescue window&quot; (for example ALT F5). 

Now you can cycle windows until the one you want to rescue, and then &quot;rescue&quot; it: it will move back inside your screen. 


How to save the window size on wanderer (snapshot all, snapshot windows)

Same for icon position on wanderer, can't save the position. Icon position cannot be saved yet, but you should be able to save the window position and size. sys:prefs - wanderer icon has option to save window size on exit but just for dh0. To get saving working on (DH1: Extras:) partitions try deleting the dh1 disk.info file, then reboot. The system should create a new dh1 icon. 


* how to set up permanently 'view all files'?
As for viewing all files, removing disk.info for that disk did the job 

* how to list and kill processes (xkill would be useful) ? 
sys:Extras/System/Scout can kill apps 

sys:Tools/Commodities/Exchange can remove available commodities


* how to restore 'go up' button in wanderer window? (it doesn't show up anymore).
If you're using Icaros, go to the theme prefs and make sure that decoration is checked. Also, some themes do not use a parent button, so try another theme. You may have to restart Aros before the theme will change.

* Is it really safe to turn off (hardware button) computer at any time (worried about USB hard disk)
yes you can turn off the computer IF none of the drives are in progress (i.e. writing). Best to use Wanderer menu option Quit otherwise 


===Say narrator===

Say &quot;Hello World&quot; for a simple robotic voice 

SPEAK: is a write-only DOS device for text-to-speech abbreviated as tts. 
To check if available, type assign into the shell and at the bottom in the Devices: section should be SPEAK 

Examples of use 
&lt;pre&gt;
Copy S:Startup-Sequence SPEAK:
Echo &quot;Hello&quot; &gt;SPEAK:M/R/S150/P110
Echo &quot;DH1 EH0 L OW1&quot; &gt;SPEAK:A1
&lt;/pre&gt;

Classic options are M/F, R/N, S&lt;rate&gt;, P&lt;pitch&gt;, O0/O1, A0/A1, and D0/D1. O1 recognizes lines beginning with OPT/ as option changes. A1 treats input as narrator phonemes.

Long options select a speech engine:

Echo &quot;Hello&quot; &gt;SPEAK:ENGINE=narrator/VOICE=female/STYLE=natural/LANGUAGE=en-US

Supported selectors are ENGINE=, VOICE=, STYLE=, and LANGUAGE=. Values are case-sensitive backend identifiers. ENGINE=DEFAULT selects the system default. Narrator-compatible selectors continue through the classic translator/narrator pair. Other engines use speech.device. Direct phonemes require a narrator-compatible selection.


===Printing===

This needs further [http://www.aminet.net/package/docs/help/PrinterGuide drivers written], we have postscript and write to file support only 

;There are no individual drivers yet for HP's Photosmart, EPSON's EPL, CANON's, Lexmark, CUPS PPD, etc. 


*Postscript

Best to set Printer Prefs in the Prefs drawer to print-to-file or parallel/USB port 


Save document in postscript or convert picture/text to postscript 

Print using compatible Postscript printer 


*printer is simply not accepting IPP connections at the moment.

Please try the following steps:

Open the printer web interface in a browser:

 http://192.168.1.x/

Look for the network or protocol settings.

Enable IPP / Internet Printing Protocol.

Make sure TCP port 631 is open/enabled.

Save the settings and reboot the printer if the web interface asks for it.

 ipp://192.168.1.xx:631/ipp/print

 ipp://192.168.1.xxx:631/ipp/


===Files===

====File endings and datatypes====

* Check if the file has his own .info icon file with a tool set to open it. IIRC this has higher priority over the def_XYZ.info file association. 
* In ENVARC:SYS/def_Text.info or whatever def_ file needs changing, use Wanderer's menu Icon -&gt; Information and change the def_XYZ.info there. If you're on ABIv0 and want it to be applied immediately, you might have to copy it to ENV:SYS/ (or to reboot). 
* Identifying file types by file ending is only a fallback. Far better it is to search for magic words, for flac files this would be &quot;flaC&quot; according to this [http://flac.sourceforge.net/documentation_format_overview.html documentation]. 

For instance, to open PDFs with arospdf not localised in the default drawer of Icaros (Work:Extras/Applications/arospdf) but localised in a custom drawer in AROS. The default tools are defined in the icons in sys:prefs/env-archive/sys e.g. def_PDF. 


File type identification is done by datatype descriptors which you can find in Devs/Datatypes. The AROS build system has a tool which creates such datatype descriptors. 


'''Changing of default tools of existing icons is easy as shown above. Adding of new file types is not hard, but needs knowledge of the AROS build system.'''


The enduser way would be to download the attached file, which contained two executables:
1) createdtdesc, to make a new datatype description
2) examinedtdesc, to read/show existing datatype descriptions

use 2 to get an idea on how it things are currently done in aros by providing this executable a file from the drawer sys:devs/datatypes/ (alternatively you can find the original .dtd files here).

use 1 to make your new datatype. Use the accompanied FORMAT file (also here) to read how to make your own datatype descriptor. use 2 to get hints from other datatype descriptors.

Note:
When creating a new descriptor would advise against using the pattern property, but instead use the default pattern of #? and create a Mask that matches your filetype. This requires some research in order to discover how your filetype can be recognized properly. Of course with making something like a descriptor for an ascii textfile, you would fallback to using the pattern (e.g. #?.text as the filetype cannot be determined easily otherwise). 

&lt;pre &gt;
# name - choose wisely and informative. also used for icon's name.
# version - choose as you like as long as it complies with version rules
# basename - the 'root' datatype class. be aware that e.g. it can influence behaviour. for example when choosing binary and using tool multiview in project icon, the file will be viewed as binary file (choosing sound would tell mulitview to view the file as a soundfile). So this can influence the underlying tool being used. Could become messy if users started to modify the tool manually. 
# pattern - This is the file pattern match e.g. #?.text
# Mask - A mask to identify the file. Requires knowledge of the actual file structure. For example 'M' 'Z' for an msdos executable.
# GroupdID - not supported (AROS native) files - use syst as that would be the least intrusive in case an AROS tool/program tries to load such datatyped file.
# ID - In your case, the first four characters of the name at subchapter 1 (in lower case) (or less if name is shorter).
# flags - How the mask needs to be interpreted. In your case would be mostly DTF_BINARY in combination with (wanted or not) DTF_CASE (to tell if mask used letters are case sensitive or not)
# priority - the priority of how the type is handled so that on datatype could have precedence over another? In any case, document tells it to be mostly 0. 
&lt;/pre &gt; 

Now that you know each field and what it does (more or less), you write this fields in a text file for your own invented datatype, save it and create the actual dt with the tool in 1. in the end the created dt must reside in sys:devs/datatypes/ drawer.

Then you would create a default icon in sys:prefs/Env-archive/SYS drawer. Don't forget to reboot or copy .info file to ram:env/sys in order to test. also don't forget to set which tool to start f.e. c:lx or dh4:emulators/mycoolemulator

To test, open Wanderer then show all files and doubleclick on a file of type you just created. Alternatively you could use the 'open' command from shell (with file of datatype you just created as parameter).

And as a last note. it would perhaps be welcome to have a program like xicon and/or runprglist for AROS (unfortunately both without source, but something similar could be created for AROS).

Sounds complicated ?

Perhaps... but OS like windows needs a complete registry to be able to do things like this. And yes, i am aware windows has gui tools that does it (more or less) for you (by manipulating the registry). Same could be done for AROS (without integrating a registry in AROS that is ).

Would that suffice ?

red1+2: typos, reformatting.

disclaimer: please note that using these tools can screw up your currently installed support for datatypes when used incorrectly. Do not use if you do not understand what you are doing. Use at own risk.


==Network Connection==

AROS currently only has one real choice for TCP/IP networking - AROSTCP.  This is a port of the AmiTCP package from AmigaOS (TM), with a number of enhancements/fixes from AROS developers. 


===Wired===

Use Network Prefs to setup 


=====IPv6=====

Some support 


128bit IPv6 address packet 
&lt;pre&gt;
Local FD::/8
Global 2000::/3
64:ff9b::/96
&lt;/pre&gt;
NAT64 translates IPv6 to IPv4 
DNS64 


OS routing works with 
&lt;pre&gt;
MacOS Ventura 
Windows 11 with cloud account 
Ubuntu Jammy Jellyfish 
Android 10 (block google dns) 
&lt;/pre&gt;


====IPv4====

The top half of the IPv4 Configuration tab on the Network Prefs deals with the network card/USB and the lower half the router part. 

[[File:AROS Wanderer Network Prefs DHCP.png|thumb|DHCP Settings]]

'''Upper part of IPv4 tab''' 
* Click Add on the top right of the Prefs which opens a window called '''Interface''' 
* Enter Name as net0 (but can be anything as long as it is consistently used in other sections) 
* check mark on Active
* select device to be used using the '''right hand-side gadget''' of the box where the device name will go 
* set Unit to 0 
* IP Mode is default set to '''Get address from DHCP''' 


* IP Mode set to Manual if DHCP does not work automatically 

From the shell CLI,  ifconfig -a

Under net0: section, inet starting 192.168.x.xxx

* inet or '''Address''' of network card 
* netmask convert to decimal so 0x'''ffffff7f''' becomes 255.255.255.247 which is used to adjust the above '''Address''' into 
* broadcast 192.168.xxx.xxx

click OK


[[File:AROS Wanderer Network Prefs Manual.png|thumb|Manual Settings]]

'''Lower part of IPv4 tab''' 
* IP Mode Get address from DHCP (default) 


* or changing to Manual if automatic DHCP set up does not work 
* '''Gateway''' (Router Internal LAN-IP) (Default Route) = 192.168.0.1 (D-Link Netgear), 192.168.1.1 (Linksys 3com), 192.168.2.1 (SMC Microsoft), 192.168.1.254 (Belkin), 192.168.123.254 (USRobotics) else check with your router manual 
* first DNS = use 208.67.222.222 (opendns) or Gateway number above (to test web browser access to router) or 212.50.160.100 (google)  i.e. or whatever your ISP needs you to set 
* second DNS = use 208.67.220.220 (opendns) or Gateway number above (to test web browser access to router) or 213.249.130.100 (google) i.e. or whatever your ISP needs you to set 


* At the bottom of IPv4 tab, check mark the '''Start networking during system boot''' option 
* Save and reboot (sometimes Network restart fails, so reboot every time to be sure) 


'''an alternative way''' to AROS ifconfig -a, other OSs have similar for the same internet connection. Another connection will have different settings. 

e.g. From [http://www.ncsu.edu/resnet/windows/ipconfig/ Windows], '''ipconfig /all''' 
and note down the IP, subnet mask, default gateway, and DNS servers values and put these values in &quot;manually&quot; into AROS Network prefs. 

e.g. From Linux via dhcp router have a look at etc./dhcpc/dhcpcd-eth0.info 
* for manual input look at /etc/networks (IP or Gateway) and /etc/resolv.conf (DNS) 

 Please note that all in one routers (wired+wireless) or separate routers may need different settings 

IPv4 involves routing (192,168.x.x), firewall, NAT 


===Wireless===

 You may have a Wifi Prefs to use for wireless setup 

[[File:MyArosWirelessSetup.png|thumb|Setting up]]

[[File:MyArosWirelessTCP.png|thumb|Shell commands to work out what is happening]]

We must first make certain you have a Atheros 5k chip inside acting as the wireless wifi option. Open PCITool in Tools directory. Down left hand side are a series of numbers 0.00.0 etc. Click on some at the bottom and hopefully one of them will say Atheros AR5??? or AR242?. 

or a Realtek RTL8187B, we can check using Prefs/Trident as this one is USB based 


There are many similarities with the above Wired set up so please read the above section as well 


* open Network/Prefs
* In '''IPv4 Configuration''' tab - click Add - enter net0 / active tick / #?.device / Unit 0 / IP Mode = manual (important if default DHCP does not work automatically) 

Make sure that any extra network names (e.g. eth1 or net1) should be deleted. If net0 already st previously, change net0 so that it shows associated with the appropriate device name like atheros5000.device or realtek8180.device. Having two entries here will cause sub-net problems. 

* Go to '''Wireless''' tab and click on &quot;Add&quot; button. 
* Insert network name (SSID your wireless network name use wirelessmanager to get it), select right &quot;encyption&quot; that is most likely &quot;WPA&quot;. 
* Key Type set as &quot;Passphrase&quot;. i.e. type in your password for your router (aka access key). 
* Unselect (no tick) &quot;hidden&quot; if it is selected, then apply. You may have to tick it if wireless does not work. 
* Finally, Save and '''reboot'''. 

For the best chance of success, set networking to start at boot, and then reboot with the USB adapter plugged in. 


===USB Ethernet===

Open SYS:Prefs/Network and in the IPv4 Configuration tag (top table covers your usb stick) 

* click Add button
* set Name as net0
* Tick Active box
* enter the usb-ethernet.device e.g. dm9601eth.device, usbpegasus.device or usbasixeth.device use SYS:c/devlist, '''Scout''' or trident prefs to get the correct spelling 
* set Unit to 0 (which is usual but check the messages from the bottom of the Trident prefs whilst plugging the device in to determine the unit number otherwise) 
* IP Mode is set to Get address from DHCP (make sure your router is set right for that) 
'''or manual'''
* IP Address of network card, i.e. 192.168.0.xx or 192.168.1.xx (xx being greater than 1) 
* Subnet netmask = 255.255.255.0 
* click OK

There can be sometimes be boot failures when using USB ethernet - plug the USB device in after boot and save the network prefs to make it work again. 


Lower part of IPv4 tab covers the router information 

* IP Mode Get address from DHCP 
'''or if manual settings'''
* Gateway (IP Address of router) = usually 192.168.0.1 or 192.168.1.1 but see router manual to make sure. 
* first DNS = use 8.8.8.8, 208.67.222.222 (opendns) or 212.50.160.100 
* second DNS = use 8.8.4.4, 208.67.220.220 (opendns) or 213.249.130.100 


===USB Tethering via Android smartphone===


Go to AROS Network Prefs (IPv4 configuration tab) and write type in &quot;usbrndis.device&quot; in the &quot;device&quot; textfield of &quot;Interface&quot; sub-window, which appears when you add a new device (or modify an existing one). Select &quot;Start Network during system boot&quot; and saved the configuration, the Connection is immediate no reboot is needed.&lt;br&gt;

usbrndis.device is a resident device (virtually always there) in fact, a driver is not present in DEVS:Networks &lt;br&gt;&lt;br&gt;

Plug in USB cable, go to Android settings and enable &quot;USB Tethering&quot; &lt;br&gt;

A reboot should not be necessary.

When restarting AROS, the Smartphone deactivates the connection and to access the network again have to reactivate it before starting the browser. 


===Solving Issues===

[[File:MyArosTCP.png|thumb|Aros network setup diagnostics - why does it not work?]]

* In Network Preferences, have '''only one''' item in the IPv4 Configuration tab 
* If using manual settings, make sure all numbers are correct, especially for IP address of the card/usb (changing the last number in chain of four) 
* For any USB based networking, it is often necessary to save in Prefs/Network, reboot AROS and network support can begin 


* For wired, make sure that the LAN-cable is plugged in before starting the computer 


* If wireless, try getting closer to the router. 
* Switch off the encryption option from your router then try wifi, if successful then your ip/dns is ok. If not then your ip/dns settings are most probably wrong or need to use one or more opendns numbers 
* Replace detachable wireless antenna (best wireless option to buy if you can) with a stronger antenna ie. 5&amp;nbsp;dBi or 7&amp;nbsp;dBi 
* Try with another computer/laptop/machine 

Program Error  C:WirelessManager 

* Test with another OS 
* Check that Wifi works before changeover (if possible) 
* Check that socket and card are working 
* Check if card is too new for laptop (date code on card MMYY blue askey date 2005-2007 etc)   


Are you connecting with the Router ? 

Check with protection off e.g. wps and wep to see if it makes a difference. 


For USB wireless - stopping and starting may be needed...

&lt;pre&gt;

; $VER: AROSTCP-startnet 1.0 (01/08/06)
; AROSTCP-startnet (c) The AROS Dev Team.
;
Run &lt;NIL: &gt;NIL: AROSTCP
WaitForPort AROSTCP
If NOT Warn
  ; echo &quot;Stack online&quot;
Else
  echo &quot;Wait for Stack Failed&quot;
EndIf

; stop and restart
execute &quot;sys:system/network/AROSTCP/s/stopnet&quot;

Run &lt;NIL: &gt;NIL: AROSTCP
WaitForPort AROSTCP
If NOT Warn
  ; echo &quot;Stack online&quot;
Else
  echo &quot;Wait for Stack Failed&quot;
EndIf

run &lt;NIL: &gt;NIL: wirelessmanager realtek8180.device

&lt;/pre&gt;


What IRQ number is assigned to the device? You can check with Tools/PCITool? 
It's possible the BIOS hasn't set the right IRQ number. If you have a Linux CD/DVD handy, could you check if it boots with the options &quot;acpi=off noapic nolapic&quot;? 


If the following does nothing, this will help us figure out why networking doesn't start automatically at boot

open a shell and run the following commands:

&lt;pre&gt;
echo ${AROSTCP/AutoRun}
echo ${AROSTCP/WirelessAutoRun}
echo ${AROSTCP/WirelessDevice}
&lt;/pre&gt;

Please report the output, typically it will look like this  

# True  (explanation this variable is related to the &quot;Start networking during system boot&quot; checkbox in network prefs) 
# True  ()
# Devs:networks/atheros5000.device unit 0


If there's a problem with the AROSTCP package. What's the output of this?

 ENV:sys/packages/AROSTCP 

should return a string = Sys:System/Network/AROSTCP


By the way, a quicker way to check networking is working would be to run some shell commands such as:


&lt;pre&gt;
ping www.google.com
ifconfig net0
&lt;/pre&gt;


The best way to list the available networks and diagnose / troubleshoot problems with connecting to a wireless network is to run WirelessManager manually. First uncheck the &quot;Start networking during system boot&quot; box in the Network prefs app, then save and reboot. Then run this in a shell:

 C:wirelessmanager atheros5000.device verbose 

or 

 C:wirelessmanager realtek8180.device verbose 

and capture the output 


If the above does not help, could you edit the file SYS:System/Network/AROSTCP/S/Package-Startup, and change &quot;&gt;NIL:&quot; to &quot;&gt;T:wifi.log&quot; on the WirelessManager line and add this as well Wait 5?

&lt;pre&gt;
if ${AROSTCP/WirelessAutoRun} eq &quot;True&quot;
Run QUIET &quot;C:WirelessManager ${AROSTCP/WirelessDevice} &gt;T:wifi.log&quot;
wait 5
EndIf
&lt;/pre&gt;

Then save, reboot and post the log file (T:wifi.log) here.


&lt;pre&gt;

c:wirelessmanager atheros5000.device verbose
Initializing interface 'atheros5000.device:0' conf 'ENV:Wireless.prefs' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file 'ENV:Wireless.prefs' -&gt; 'ENV:Wireless.prefs'
Reading configuration file 'ENV:Wireless.prefs'
Line: 1 - start of a new network block
ssid - hexdump_ascii(len=7)
65 63 68 65 6c 6f 6e echelon
PSK (ASCII passphrase) - hexdump_ascii(len=14): [REMOVED]
key_mgmt: 0x2
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='echelon'


Then it just sits there. Not sure what a normal dump looks like, I don't see anything that looks wrong in the configuration.
&lt;/pre&gt;

looks like the driver isn't working with that card. Has anyone else successfully used that exact model number (AR2413)?


&lt;pre&gt;

Initializing interface 'atheros5000.device:0' conf 'ENV:Wireless.prefs' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file 'ENV:Wireless.prefs' -&gt; 'ENV:Wireless.prefs'
Line: 1 - start of a new network block
ssid - hexdump_ascii(len=7):
65 63 68 65 6c 6f 6e echelon
PSK (ASCII passphrase) - hexdump_ascii(len=14): [REMOVED]
key_mgmt: 0x2
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='echelon'
*** [wpa_sm_init] sm-&gt;pmksa=02c66fd4 ***
Own MAC address: 00:01:36:15:ae:0c
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: Supplicant port status: Unauthorized
EAPOL: Supplicant port status: Unauthorized
Added interface atheros5000.device:0
State: DISCONNECTED -&gt; SCANNING
Started AP scan for wildcard SSID
MLME: starting scan
MLME: scan channel 1 (2412 MHz)
sana2: sending MLME frame


Then it stops. Does this mean the router is not authorizing this NIC?

IRQ 4 (A)

&lt;/pre&gt;

apparently locking up when the first frame is sent (a scan request).


&lt;pre&gt;

Devs/Networks/atheros5000.device:0
Initializing interface 'Devs/Networks/atheros5000.device:0' conf 'ENV:Wireless.prefs' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file 'ENV:Wireless.prefs' -&gt; 'ENV:Wireless.prefs'
Reading configuration file 'ENV:Wireless.prefs'
Line: 1 - start of a new network block
ssid - hexdump_ascii(len=12):
41 69 72 4c 69 6e 6b 35 39 33 30 30 AirLink59300
PSK (ASCII passphrase) - hexdump_ascii(len=8): [REMOVED]
key_mgmt: 0x2
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='AirLink59300'
*** [wpa_sm_init] sm-&gt;pmksa=0224e444 ***
Own MAC address: 00:1f:e1:42:e3:7a
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
[eloop_reg_timeout] Timeout is at 1317686594.160000
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: Supplicant port status: Unauthorized
EAPOL: Supplicant port status: Unauthorized
[eloop_reg_timeout] Timeout is at 1317686595.060000
[eloop_reg_timeout] Timeout is at 1317686604.060000
Added interface Devs/Networks/atheros5000.device:0
[eloop_run] Starting
State: DISCONNECTED -&gt; SCANNING
Starting AP scan for wildcard SSID
MLME: starting scan
[eloop_reg_timeout] Timeout is at 1317686594.160001
MLME: scan channel 1 (2412 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.193000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.233000
MLME: scan channel 2 (2417 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.253000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.293000
MLME: scan channel 3 (2422 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.333000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.373000
MLME: scan channel 4 (2427 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.393000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.433000
MLME: scan channel 5 (2432 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.473000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.513000
MLME: scan channel 6 (2437 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.553000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.573000
MLME: scan channel 7 (2442 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.613000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.653000
MLME: scan channel 8 (2447 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.693000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.713000
MLME: scan channel 9 (2452 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.753000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.793000
MLME: scan channel 10 (2457 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.833000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.853000
MLME: scan channel 11 (2462 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.893000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.933000
MLME: scan channel 12 (2467 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.973000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.013000
MLME: scan channel 13 (2472 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.033000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.073000
EAPOL: disable timer tick
EAPOL: Supplicant port status: Unauthorized
MLME: scan channel 14 (2484 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.113000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.153000
MLME: scan channel 1 (2412 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.193000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.213000
MLME: scan channel 2 (2417 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.253000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.293000
MLME: scan channel 3 (2422 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.333000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.353000
MLME: scan channel 4 (2427 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.393000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.433000
MLME: scan channel 5 (2432 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.473000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.493000
MLME: scan channel 6 (2437 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.533000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.573000
MLME: scan channel 7 (2442 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.613000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.653000
MLME: scan channel 8 (2447 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.673000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.713000
MLME: scan channel 9 (2452 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.753000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.793000
MLME: scan channel 10 (2457 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.833000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.853000
MLME: scan channel 11 (2462 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.893000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.933000
MLME: scan channel 12 (2467 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.973000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.993000
MLME: scan channel 13 (2472 MHz)
[eloop_reg_timeout] Timeout is at 1317686596.033000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686596.073000
MLME: scan completed

&lt;/pre&gt;

Is your network hidden? If so, did you enable the 'Hidden' checkbox in the network prefs? What distro version are you using? 


&lt;pre&gt;
&quot;ENV:sys/wireless.prefs&quot; looks like this:
network={
ssid=&quot;testadhoc&quot;
key_mgmt=NONE
wep_key0=&quot;12345&quot;
wep_tx_keyidx=0
}
&lt;/pre&gt; 


If your router doesn't broadcast its SSID (hidden), you need to add this option to the network block of the wpa_supplicant.conf on your aros machine and make changes after  # Example blocks: 

 scan_ssid=1

Here's a full description of all the [http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=wpa_supplicant/wpa_supplicant.conf config file options]. 

&lt;pre&gt;
ap_scan=1

network={
ssid=&quot;YOURESSID&quot;
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP
group=CCMP
psk=YOURPASSWORD
}
&lt;/pre&gt;

&lt;pre&gt;
filter_ssids=1
ap_scan=2

network={
ssid=&quot;REMOVED&quot;
scan_ssid=1
bssid=REMOVED
priority=100
mode=0
proto=RSN
key_mgmt=WPA-PSK
auth_alg=OPEN
pairwise=CCMP
group=CCMP
psk=REMOVED
}
&lt;/pre&gt;


Error 6: Couldn't resolve host name.

Check Scout -&gt; Devices and look at the device that you are using, in the OCnt column it should state 2 which means AROSTCP and Wirelessmanager are both accessing this driver. If 0 or 1, then uncheck the checkbox in Network prefs for starting networking at boot, save and reboot. Then run this is the shell:

C:WirelessManager realtek8180.device unit 0


some quirks setting up the wireless network as well 

1) it's far better setting up either the wired OR the wireless network adapter as net0:, or weird things happen

2) it's better using fixed IP on the local network instead of DHCP

3) network setting must be placed in network setting panel in /prefs, using the wirelessmanager helped me finding available SSIDs, but not actually connecting to them

once done, reboot.


If previous setup is proving problematic 

&lt;pre &gt;

SYS:Prefs/Env-Archive/Wireless.prefs
SYS:Prefs/Env-Archive/Zune/OWB.config
SYS:Prefs/Env-Archive/Zune/global.config
SYS:Prefs/Env-Archive/AROSTCP/WirelessDevice
SYS:Prefs/Env-Archive/AROSTCP/db/Interfaces
&lt;/pre &gt; 

Make a copy of these files and restore in case of problems. 


Please try this test to check if you can connect to your router, ie established that the WiFi layer is working 

̊̊̊̊Boot with networking disabled, by make sure that &quot;Start networking at boot&quot; in Network Prefs is unchecked (no tick).  
̊ Run this in a shell: C:WirelessManager atheros5000.device VERBOSE
̊If the output of that command is too long to summarise here, you can redirect it to a file by adding &gt;RAM:wifi.log to the end, then attach or paste that file here.


try running &quot;status&quot; in the shell and check that AROSTCP is listed/running
If AROStcp is not showing, then AROSTCP is not running. attempted to start it by clicking Use or Save in network prefs, or checking the &quot;start networking at boot&quot; box or typing into a shell. 

 Execute SYS:System/Network/AROSTCP/s/startnet

(run Status again afterwards).


The &quot;cannot resolve hostname&quot; will appear if you are blocked on the wifi network by the router as well as aros not being able to assign correct network address.

One way of testing this might be to disable the firewall in the router. you might also check the router how it sees the attempts aros do to speak to it. The easiest way to do that would be to manually give aros an IP number in the routers accepted range. and see if it shows up at all within the router.


Tests that can be undertaken to determine correct settings and functions 

 pciinfo
 sanautil -d broadcom4400.device status

&lt;pre &gt;
 ping &lt;router-address&gt; e.g. 192.168.0.1 (aka inet) or 80.237.146.33 (www.amiganews.de) 
 ifconfig net0
 ifconfig net0 up
 extras:networking/utils/sanautil/sanautil -d atheros5000.device status
 WirelessManager atheros5000.device verbose &gt;RAM:wifi.log
 ;to send the log to RAM disk to be read easier or if detected, 
 Run WirelessManager atheros5000.device &gt;NIL:
 Run WirelessManager atheros5000.device ssid=&quot;mynet1&quot; &gt;NIL: 
 C:WirelessManager realtek8180.device unit 0 
&lt;/pre &gt; 

Please look at the task list in Scout, and check if WirelessManager and AROSTCP are running. Also look at the device list in Scout to check if realtek8180.device is open. 


start tools/debug/sashimi, maybe it shows some debug messages when disconnection happens.


Firstly, let's take a look at what your setup most likely looks like, assuming you use a router. See diagram below: 

&lt;pre&gt;
Internet &lt;---------&gt; home router &lt;---------&gt; computer 
-----------external IP------------------internal IP-------------
&lt;/pre&gt;

Okay, so what am I trying to show you with that diagram. A few things. Firstly, the IP address that connects you to the Internet is not the same one that connects you to your router. What happens is that your computer doesn't have a direct connection to the Internet, instead your router connects to the Internet, and your computer connects to the router.

You can see the external and internal IP addresses in these example settings...

* Default Gateway : 76.91.64.1 (external IP for ISP/Internet host)
* IP Address : 76.91.71.184 (external IP for home router)

* IP Address : 192.168.0.1 (internal IP for home router)
* Address = 192.168.0.161 (internal IP for computer)

As you can see, there are two internal IP addresses and two external IP addresses. This is because there is a client/server relationship, effectively one address is for the service (server) and one address is for the device trying to access that service (client).

The server addresses in your case are 76.91.64.1 (your ISP's address, serving the Internet), and 192.168.0.1 (your home router's address, serving your home network). The term gateway applies here, they are your gateway to those services.

Subnet masks are used along with IP addresses to determine which IP addresses are allowed access to a network. I did learn the more in-depth rules about subnet masks once (watched a CCNA vid), but I've forgotten about it. The basic level of understanding you'll need is easy to remember though. A subnet mask value of 255 means that portion of the IP address must stay constant, whereas a subnet value of 0 means any unassigned value up to 255 is allowed in the IP address.

By far the most common subnet value is 255.255.255.0. What this means is that the first three parts of the IP address you use to connect to a service must stay the same as the server/gateway address, and only the last section can change.

So if your router's internal IP address is 192.168.0.1, and the subnet mask is 255.255.255.0, the only addresses that will be allowed to be used on that network are between 192.168.0.2 and 192.168.0.255 (I think 192.168.0.0 is reserved for other uses).

Final point to make is about DHCP (a.k.a. dynamic IP) vs static IP. A server/router using DHCP gives a device that connects to it an address within the acceptable range. It usually starts with the lowest numbered free address, so with your router it'll give the first device that connects to it 192.168.0.2, the next device 192.168.0.3, and so on. Static IP addresses are where you set the IP address you want to connect with in advance. 

When using static IP addresses on a router where DHCP is active, it's good to use a high number to avoid conflicts with other devices that are connected to your network, to reduce the risk that both devices will try using the same IP. That's why your current choice of 192.168.0.161 is good, unless you have over 159 devices connected on your current network!


Okay, so what's the next step. Well, if you can use ping, I'd suggest pinging 192.168.0.1. If you get a positive response it means you're connected to your router, if you don't get a response it means the connection between your router and your computer is at fault.

Documentation on configuring the AROSTCP environment further can be found [http://en.wikibooks.org/wiki/Aros/User/Networking here] 


===File Sharing===

As AROS knows only a few filesystems (FFS, OFS, SFS, PFS (amiga only), FAT12, 16, 32, Microsoft NTFS (windows), UDF (Blu-ray)). 
The others in regular use like MacOSX hfs+, Linux ext2/ext3 and ext4, Haiku BeFS provide a problem in transferring files. 

Linux can access SFS partitions but it needs to be compiled. The latest full source are [http://home.elka.pw.edu.pl/~mszyprow/programy/asfs/ here]. It compiled fine with a 2.6.30 kernel in Puppy Linux 4.31. 

An alternative, is to use a FAT32 partition to share. Setup a 4G FAT32 partition using HDToolbox for sharing, and the rest of the space as SFS for an Aros install. It works very well. 

Files could be transferred via TCP internet network. 


====SMB2/3====

With Windows you can share one folder or all folders of the &quot;Public&quot; user.

On Windows what is important is to enable sharing (Network and Sharing Center).

AROS Mountlist should look lke this 
&lt;pre&gt;
Handler = L:smb2-handler
StackSize = 65536
Priority = 5
GlobVec = -1
ACTIVATE=1
Startup = &quot;smb://UserAcc:password@PCShare/Sharefolder&quot;
&lt;/pre&gt;

which could also be
&quot;smb://UserPC:password@192.168.x.x/Public&quot;
or
&quot;smb://UserPC:password@Name-PC/Public&quot;

so
&quot;smb://UserPC:password@192.168.1.158/Folder&quot;
or
&quot;smb://UserPC:password@Name-PC/Folder&quot;


After you have configured a share generates a DOSDrivers it is named &quot;SMB0&quot; which includes the setting, and at each reboot it is Mounted. You can still delete the DOSDriver by hand, is located in Storage/DOSDrivers, the file &quot;ServerAutoMounts&quot;, in ENV:AROSTCP which indicates the DOSDriver to be mounted, should also be deleted. 
The per-mount files are written to ENV:SMB or SYS:Storage/DOSDrivers. There is also additional file ENV:AROSTCP/ServerAutoMounts which states what will be presented to the end user. 


====Old SMBFS====

e.g. to connect to a NAS share such as \\NASBOX\Shared use -:

SMBFS WORKGROUP=&lt;YOUR WORKGROUP NAME&gt; VOLUME=&lt;AROS volume name to use&gt;: SERVICE=&lt;UNC Path to connect to&gt;

SMBFS WORKGROUP=MYNET VOLUME=Shared: SERVICE=//NASBOX/Shared

And you will then have an icon appear on your desktop for the volume name you have chosen. 


You can put the above script into wbstartup or  

give it an icon, change it to a 'project' and give it the default tool c:iconx 

Open a shell and type copy sys:script.info &quot;sys:wbstartup/YOURSCRIPTNAME.info&quot;

This should create an icon for your script file.

Now right-click on your script and select 'information'.

Change 'tool' to 'project', put 'c:iconx' into the 'default tool' box, click save 

The reason being that scripts need to be opened with 'execute SCRIPTNAME' (or 'iconx') whereas the programs started from wbstartup are opened using 'run PROGRAMNAME'. It's the same as trying to start a command-line tool from the workbench by double-clicking it.


====Setup ISO images within AROS====

Use [http://archives.aros-exec.org/index.php?function=browse&amp;cat=driver/storage DiskImage] which supports many cd image formats ISO, CCD, MDF/MDS, CUE/BIN, NRG and UIF. To mount CD or DVD images use below....

&lt;pre &gt;
# Rename your iso 'Unit0' (note no extension).
# Do 'View/All files' on you Aros partition. You should now see a folder called 'Diskimages'. Copy your renamed iso to there. 
(Alternatively, you could type at the shell 'assign FDSK: xxx', where xxx is the location of your iso.) 
# From the shell, type 'mount CD0:' and the iso should appear on the Wanderer desktop. You can now access it like a real disk.
&lt;/pre &gt; 

 assign devname: dismount 
 Assign DOSVOLUME: remove
 [http://aminet.net/package/disk/misc/unmount-0.1 unmount] most filesystems work but SFS lacks support for ACTION_DIE packet 

If you are using an IcAros install, the startup scripts are set up to wipe the Diskimages directory on boot, so its worth keeping a second copy of the iso somewhere else. Alternatively, you could set up extra mountlists for additional iso images. I've made a file called iso1 in the Aros:devs directory that contains the following text:

&lt;pre&gt;
/* Entry for ISO image */

ISO1:
FileSystem = cdrom.handler
Device = fdsk.device
Unit = 1
LowCyl = 0
HighCyl = 0
Surfaces = 1
BlocksPerTrack = 1
DOSType = 0x41434400
Activate = 1
#
&lt;/pre&gt;

Then I just need an iso called 'Unit1' (corresponding to the 'Unit = 1' entry in the mountlist) in Diskimages (or wherever I assign FDSK: to) and to mount I type in at the shell:

 Mount iso1: from devs:iso1

Of course, if you create mountlists for ISO2, ISO3:, etc. (with the corresponding change to the 'Unit = ' line) you can have as many isos mounted as you wish. I just call mine ISO1: etc. to distinguish them from the real CD drives 


==Video Guides==


Video demonstrations and tutorials covering:

:00. '''Introduction''' 
::[https://www.youtube.com/@jamesmattson6813/videos Various Aros Installs], 
::[https://www.youtube.com/embed/j8EmSEby0Rg AROS repo in gource, view of AROS dev commits from 1997 to 2025], [http://www.youtube.com/watch?v=Vx_zqlBow40&amp;feature=related Gource view of AROS 1997 up to 2009], 
::[http://www.youtube.com/watch?v=s1RsvEm7UrU Why an Amiga OS in 2011], 
::[https://www.youtube.com/watch?v=1W886mheV74&amp;pp=ygUPYW1pZ2EgYXJvcyAyMDI2 Johan Grip on early days of AROS x86], [https://www.youtube.com/watch?v=mXaKDhtTTqQ&amp;t=14s&amp;pp=ygUPYW1pZ2EgYXJvcyAyMDI2 Michel Schulz on Aros and PiStorm], 

:01. '''Installation'''
::[https://www.youtube.com/watch?v=M7YjufrJqDs Aros One install], [https://www.youtube.com/watch?v=iIMguHTdC5E Aros One USB install], [https://www.youtube.com/watch?v=ZNXauy5m5Wc Aros One install], [http://vimeo.com/11013489 Modify Grub boot], 
::[http://www.youtube.com/watch?v=wyQVeyXIywc&amp;feature=channel iMica Silent Pt3], [http://www.youtube.com/watch?v=o2AnkoflY14 Wipe whole drive and Install - warning loss of data on drive], 
::[http://www.youtube.com/watch?v=OVXm6_-witQ VirtualBox install], [ VMware install], 
::[http://www.youtube.com/watch?v=0k2PEmT8I14 Broadway AROS Install], 
::[https://www.youtube.com/watch?v=PtDiXhjSIfs Is Aros Icaros a choice?], 
::[ driver install], 
::[http://www.vimeo.com/10491104 HDAudio install but needs account], [], 

:02. '''Amiga Basics'''
::[http://www.youtube.com/watch?v=TY8mWxwzH5o Screens tutorial], 
::[https://m.youtube.com/user/AMIGASYSTEM/videos General], [ Dos Scripts tutorial], [http://www.youtube.com/watch?v=hPT7SmVEpjc OS 1.2], [http://www.youtube.com/watch?v=n6kX3FqH8Ww&amp;feature=related OS 1.3], 

:03. '''Customisation demos'''
::[https://www.youtube.com/@AMIGASYSTEM/videos Prefs tutorial], [ Decoration tutorial], [http://www.youtube.com/watch?v=Dn5C8G3aDXU Scalos], 

:04. '''Setting up''' internet access and surfing the web, FTP, IRC and Mail apps 
::[ Network Prefs], [ AirCOS tutorial], [ jabberwocky tutorial], 

:05. '''Native bundled Games and Applications''' 
::[http://www.youtube.com/watch?v=aYlFv2B-VXc 3D Games], [http://www.youtube.com/watch?v=MXK7wwhd-R0 Latest Games], [http://www.youtube.com/watch?v=RUgiVThv23Q&amp;feature=mfu_in_order&amp;list=UL PrBoom GL], [http://www.youtube.com/watch?v=0s7u8TPy7V4 Assault Cubes], [http://www.youtube.com/watch?v=fih6aCXKeqs Cube 2], [http://www.youtube.com/watch?v=-X0ay0MGOms DosBox on Aros], [http://www.youtube.com/watch?v=7nKduDjf14k Oct 2010], 

::[http://www.youtube.com/watch?v=FziV2z_uxnQ Apps Pt 1], [http://www.youtube.com/watch?v=xs37_nfa5CI Apps Pt 2], [http://www.youtube.com/watch?v=Bn59_VvbQR0&amp;feature=related Apps Pt 3], 
::DOpus4 [http://www.youtube.com/watch?v=aSRybWjrrME DOpus 4], 
::Milkytracker [http://www.youtube.com/watch?v=VxBOEPzpdKg&amp;feature=related Laying Down Base Tracks], 
::[http://www.youtube.com/watch?v=k2uKQ0-ieOE Audio Evolution 4 in action], [http://www.youtube.com/watch?v=Zq4r9k0_jZI Quick Videos], 
::[http://www.youtube.com/watch?v=gGKCFZcIc0I&amp;feature=related ScreenRecorder], [http://www.youtube.com/watch?v=974c2e-Fqak&amp;feature=related TV out Tests], 
::[http://www.youtube.com/watch?v=fjq8ct5d5IY AmiFIG], [http://www.youtube.com/watch?v=h0rHvPhYJo4&amp;feature=youtu.be ZuneFIG], 
::[http://wiki.povray.org/content/Documentation:Tutorial_Section_1 POVray Tutorial 1], 
::[http://www.youtube.com/watch?v=Jk-ZNLfJsvQ pt 1, jan. 2008], [http://www.youtube.com/watch?v=nWRy33g1R7Y pt 2, feb. 2009], [http://www.youtube.com/watch?v=r5PbhCtm4vE pt 3, feb. 2010], 

::[https://www.youtube.com/watch?v=G7_FJUoQ89o Hollywood programming], [], [], [],

::[], [], [], 
::[], [], [], 
::[], [], [], 


:06. '''Commercial software available'''
::[http://www.youtube.com/watch?v=fKXY9B4R43s AntiryadGX 3D Game Editor], 
::[http://www.youtube.com/watch?v=TMS9NDzwm5U BOH indie Game], 

:07. '''Running classic amiga apps and games''' 
:: Amiberry [], [], 
::[http://vmwaros.blogspot.com/2008/11/introducing-amibridge.html Intro Amibridge], [http://www.youtube.com/watch?v=ee2PWvCZeLo Old Amiga Apps], [http://www.youtube.com/watch?v=ee2PWvCZeLo Why Janus UAE is good], 
::[https://www.youtube.com/watch?v=VhlsNSYSuDg DPaint tutorial]

::[http://vmwaros.blogspot.com/2009/11/can-icaros-play-my-amiga-games-and-why.html Play Amiga Games], [https://www.youtube.com/watch?v=XTaZCNOvCnE], 
::[http://www.youtube.com/watch?v=tMehS77LXQ4 Pagestream Introduction], [http://www.youtube.com/watch?v=284-w3hTzII Pagestream Tutorial 1], [http://www.youtube.com/watch?v=mlwEGwhZzl4 Pagestream Tutorial 2], 
::[http://www.youtube.com/watch?v=iIcrIjPOctc Catweasel Mk4 PCI Part 1] and [http://www.youtube.com/watch?v=BaitHeL6bEA Part 2], 

:08. '''Misc and History'''

::[http://www.youtube.com/watch?v=d6mDXKU29w0 Mum uses old AmigaOS Workbench 1.1 (1986)], [http://www.youtube.com/watch?v=DaRkacQ-YMg Why an Amiga 500 (1987)], [http://www.youtube.com/watch?v=k5CYsgVCzYY an Amiga 2000 (1987)], 

:09. '''Misc Shows and Events'''
::[http://www.youtube.com/watch?v=klgVSWKs4kE VCF 2010], [https://www.youtube.com/watch?v=eQ3d5qR-Hv8 24:06 Jason McMullan at amiwest 2012 about AROS], [https://www.youtube.com/watch?v=jpQO7XSfAv4 Aros SMP multi core amiwest 2013], [], [https://www.youtube.com/watch?v=gFRtAAmiFbE], [https://www.youtube.com/watch?v=DjdUEyjx8GM], [https://www.youtube.com/watch?v=ydYDqZQpim8], [], [https://www.youtube.com/@uminekoshouten/featured], [https://www.youtube.com/shorts/NfoY023w-vE], 

:10. 
::[https://www.youtube.com/shorts/6qJTNW4-6GY]


===History===

The project was originally started by a small group of Amiga [http://www.amigahistory.co.uk/aros.html enthusiasts] in 1995. These individuals were mainly computer-based college university students at the start, though that student trend has diminished since. An interview with Aaron Digulla [http://arosshow.blogspot.com/2006/12/interview-with-aaron-digulla-who.html here] 

* 1992 Commodore folds 
* 1996-1998 much of the early years was concerned with exec, dos and intuition libraries. 
* Early 1999, Haage &amp; Partner used parts of the AROS code in AmigaOS 3.9. 
* March 2001, floppy disk images of AROS became available. 
* Early 2002, AROS changed its name from Amiga Replacement Operating System to Amiga Research Operating System 
* June 2002, AROS devs decided to use Zune (MUI 3.8 rewrite) as the GUI system. 
* November 2002, Eric Schwartz drew Kitty for AROS usage. 
* Early 2003, AROS.org underwent a graphics facelift. 
* Late 2003, GCC C compiler arrived. 
* Early 2004, Aros-Exec opened. 
* Early 2005, Aros Max bootable CD arrived. 
* Late 2005, SFS filesystem ported and allowed fast access to apps and network support arrived 
* Early 2007, AROS.org underwent another graphics facelift. 
* Mid-2007, AROS changed to AROS Research Operating System after A.Inc. sued Hyperion with a trademark violation. 
* Late 2007, the hard disk installer added and VmwAROS (later called Icaros Desktop) distro launched. 
* Early 2009, Our first usable web browser (OWB)
* September 2010, first wireless support appears and AspireOS started as a distro 


* Early 2012, the first paper-cut bugfix and Fab's Odyssey Web Browser ported 
* Early 2017, work started on utilising the addition cores on modern CPUs starting with the 64bit x86 PC version  
* Mid-2017, m68k port optimized for the Vampire 2 / Apollo accelerators (68080 AMMX FPGA) 
* 2018 The old AROS Exec website closed and a new one opened 
* 2019 AROS One x86 32bit distribution started and now with USB install version 
* Early 2021, backport of more features of 32bit PC ABIv1 into 32bit PC ABIv0 (Aros One 1.5 and above) 
* 2025 year of 64bit pc builds and porting 32bit applications to 64bit ABIv11
* 2026 update of [https://www.youtube.com/watch?v=6FKTL068ULM&amp;pp=ygUPYXJvcyBhbWlnYSAyMDI2 nvidia nouveau driver for 64bit PC] 


===Bounties===

To help inspire developers with both ideas and monetary incentives, rewards are offered for the successful completion of &quot;bounties&quot; (requests for missing/new functionality) chosen by the community and handled by [http://power2people.org power2people] (formerly done by TeamAROS). A monthly option is [http://www.power2people.org/funds/aros/ here].


Future goals for AROS include expanding its underlying retargetability to support even more diverse architectures, provide memory protection features and user level file security, SMP and many other wonderful features missing from AmigaOS &amp;mdash; while still providing as much source level compatibility as is possible (however it is accepted that to achieve some goals code certain things may require a little recoding).


[http://www.ohloh.net/p/aros/contributors Developers] come and go as with any open source effort and we would like to thank them for their efforts... 

;1996-2000:In DigullaA (coordinator), GripJ, TempletonI (BSD), SchulzM, RittauS, voordenDagL, HolmM, JohanssonT, VanIngelgomH, SteigerwaldM, BortasP, deJongK, AlfredssonJ, InnocentiB, 

;2001-2005:In [http://chodorowski.com/adam/aros.html ChodorowskiA], StegerG, BergerS, HeutlingS, AlemagnaF (gcc), VerhaegenS (rexx), KielH, MatheussenKS (CAMD), SzczygielskiP, ErikssonP, LeCorfecD (Zune), BauerS (Zune), FurlongW, GustafssonJ, AndrewsN, CafferkeyN, GierichM (jpeg), PattonJ, ParsonsM, DietrichJ, SeilerT, BischoffL, LorentzenNH, AdamO, BerglundH, SmithP, HolmenD, BlomM, 

;2006-2010:In FedinP, RusslerM, SzymczykS (owb), SmiechowiczK (openGL), WeissM, NorrisR, BrunnerO, WiszkowskiT, GreppinA, [http://www.fukt.bsnet.se/~bearsoft/ Bearsoft Björn Screwelius], ErbY, CharletF, HodgesC, [http://aros-exec.org/modules/newbb/viewtopic.php?topic_id=4819&amp;forum=18&amp;post_id=43103#forumpost43103 HokstadV], McMullanJ (m68k), WilenT (m68k), 

;2011- :In MuijzenbergPHvanden, ALB42, JonesEM, weiju, DizzyofCRN, wawa, miker, 


* 1996 - The linux hosted version for i386 was the first to arrive 
* 1998 - i386, The native version for i386-based PC AT computers and compatibles.
* 2004 - x86/64, The native version for 64-bit (x86_64, amd64) PC computers.
* 2008 - sam440/ppc, The native version for Sam440EP, Sam440EP Flex and Sam460ex computers.
* 2009 - efika, The native version for PowerPC Efika computers.
* 2010 - m68k, The native version for m68k Amigas or WinUAE
* 2013 - raspi/armfh, early native version for ARMv6 based Raspberry Pi computers.
* 2017 - x86/64bit smp 


Debugging capture serial debug at all (especially with sysdebug=all or --sysdebug=all) to see it displayed on screen 

* yes, usb -&gt; rs232 adapters can work most of the time, some of the cheapest ones are not fully compatible with all rs232 devices to capture to another device 
* you will need a null modem cable (or a null modem adapter usually female to female) in addition to the usb -&gt; rs232 adapter (usb adapter is a normal modem ie. the pins are not crossed over) 

Normal modem cable - straight connection DCE 
&lt;pre&gt;
Pin 2 -&gt; Pin 2  RXD
Pin 3 -&gt; Pin 3  TXD 
Pin 5 -&gt; Pin 5  GND
&lt;/pre&gt;

Null modem cable connections DTE 
&lt;pre&gt;
Pin 2 -&gt; Pin 3
Pin 3 -&gt; Pin 2
Pin 5 -&gt; Pin 5
&lt;/pre&gt;
(9pole SUB-D)


&lt;pre&gt;
serial  ser: (amiga/aros)  tty2 tty1USB0 (linux)  COM1 (windows)  (depends on the os being used) 
speed baud transfer rate 9600 38400     lower baud might be more successful 
data bits 8
stop bits 1
parity none
handshaking flow control - none xon/xoff (most likely)  rts/cts  dsr/dtr (pins not connected so should not work) 
&lt;/pre&gt;


*You cannot use compiled aros X86-64 bit software (when ready) on aros X86 32bit. PPC compiled software on X86 and so on. 
*68k is tested with the UAE emulator (WinUAE) but some tests are done on native 68000 based Amigas and others. 
*PPC support is very limited to certain devices. 


If you use the WBStartup, you have to delete the other icons in the folder (readme etc..) and you have to add in the Icon Tooltype the parameter DONOTWAIT

If you use user-startup instead, you need to add the attached command &quot;after assignment to LUA&quot;
C:WBRun DH1:Extras/Utility/WeatherBar/WeatherBar &gt;NIL:
Change the command to match your WeatherBar path.

&lt;pre&gt;
PATH sys:Utilities/WeatherBar ADD
run &gt;nil: lua:amilua weatherforecast.lua
&lt;/pre&gt;

To enter data your Country or City, ist with city_id numbers can be found [http://bulk.openweathermap.org/sample/city.list.json.gz here] or you need to go to [https://www.bbc.com/weather BBC Weather], once you type the name of your city or town in the appropriate tab, and press enter, the 7 numbers to be added in the &quot;WeatherBar&quot; will appear on the Browser url address bar above 


Unicode v16.0 emojis are not supported but [https://github.com/jens-maus/libcodesets codesets.library] provides 

&lt;pre&gt;
internally supported (hardcoded) charsets/codesets are: (conversions are possible from and to each codeset):

    AmigaPL – Polish (Amiga)
    Amiga-1251 – Cyrillic (Amiga)
    ISO-8859-1 – Western European
    ISO-8859-1+Euro – West European (with EURO)
    ISO-8859-2 – Central/East European
    ISO-8859-3 – South European
    ISO-8859-4 – North European
    ISO-8859-5 – Slavic languages
    ISO-8859-9 – Turkish
    ISO-8859-15 – West European II
    ISO-8859-16 – South-Eastern European
    KOI8-R – Russian
    UTF-8 – Unicode

In addition, external charset table files can be stored in LIBS:Charsets or loaded by an application from PROGDIR:Charsets. The charset files included with this distributions are:

    IBM866 – Cyrillic (cp866)
    ISO-8859-7 – Greek (LatinGreek)
    ISO-8859-10 – Nordic (Latin 6)
    windows-1250 – Central/East Europe (Windows)
    windows-1251 – Cyrillic (Windows)
    windows-1252 – West European (Windows)
&lt;/pre&gt;


Icaros 2.3 USB image needs a header stripped so it can work correctly 
 dd bs=512 skip=1 status=progress if=icaros_light_2-3-0_pendrive.bin of=/dev/sdxy &amp;&amp; sync


Scalos 
&lt;pre&gt;
-------------------------------
{ &quot;STRING&quot;,		&quot;ID/K,TEXT/K,SRC/K,TEXTPEN/K,HALIGN/K,STYLE/K,FONT/K,VALIGN/K&quot;,

HALIGN		LEFT | CENTER | RIGHT

VALIGN		TOP | CENTER | BOTTOM

STYLE		NORMAL | BOLD | ITALIC | BOLDITALIC

FONT		// font specification - format: &quot;fontname.font/size&quot;

-------------------------------
arguments for STRING SRC

&quot;diskstate&quot;,		
&quot;diskusage&quot;,		
&quot;diskusagefree&quot;,	
&quot;diskusageinuse&quot;,	
&quot;diskusagepercent&quot;,	
&quot;fibfilename&quot;,	
&quot;filecomment&quot;,	
&quot;filedate&quot;,		
&quot;fileprotection&quot;,	
&quot;filesize&quot;,		
&quot;filetime&quot;,		
&quot;filetypestring&quot;,	
&quot;iconname&quot;,		
&quot;linktarget&quot;,		
&quot;plugin&quot;	pluginname &lt;optional plugin arguments&gt;
&quot;versionstring&quot;,	
&quot;volumecreateddate&quot;,	
&quot;volumecreatedtime&quot;,	
&quot;volumeordevicename&quot;,	

-------------------------------

arguments for HIDE

&quot;novolumenode&quot;,	
&quot;isempty&quot; (some STRING)	

-------------------------------

all internal commands:

&quot;about&quot;,		
&quot;backdrop&quot;,		
&quot;cleanup&quot;,		
&quot;cleanupbyname&quot;,	
&quot;cleanupbydate&quot;,	
&quot;cleanupbysize&quot;,	
&quot;cleanupbytype&quot;,	
&quot;clearselection&quot;,	
&quot;clone&quot;,		
&quot;close&quot;,		
&quot;copy&quot;,		
&quot;cut&quot;,		
&quot;delete&quot;,		
&quot;emptytrashcan&quot;,	
&quot;executecommand&quot;,	
&quot;formatdisk&quot;,		
&quot;iconify&quot;,		
&quot;iconinfo&quot;,		
&quot;lastmsg&quot;,		
&quot;leaveout&quot;,		
&quot;makedir&quot;,		
&quot;open&quot;,		
&quot;parent&quot;,		
&quot;paste&quot;,		
&quot;putaway&quot;,		
&quot;quit&quot;,		
&quot;redraw&quot;,		
&quot;redrawall&quot;,		
&quot;rename&quot;,		
&quot;reset&quot;,		
&quot;selectall&quot;,		
&quot;showallfiles&quot;,	
&quot;showonlyicons&quot;,	
&quot;shutdown&quot;,		
&quot;sizetofit&quot;,		
&quot;snapshot&quot;,		
&quot;snapshotall&quot;,	
&quot;snapshotwindow&quot;,	
&quot;unsnapshot&quot;,		
&quot;update&quot;,		
&quot;updateall&quot;,		
&quot;viewbydate&quot;,		
&quot;viewbyicon&quot;,		
&quot;viewbysize&quot;,		
&quot;viewbytype&quot;,		
&quot;viewbytext&quot;,		
&lt;/pre&gt;


{{status|50%}}
{{BookCat}}</text>
      <sha1>do709s43ppv8ozqyik77k0tid08re8p</sha1>
    </revision>
  </page>
  <page>
    <title>Chess/Playing The Game</title>
    <ns>0</ns>
    <id>26908</id>
    <revision>
      <id>4676692</id>
      <parentid>4638052</parentid>
      <timestamp>2026-10-18T05:25:03Z</timestamp>
      <contributor>
        <username>Mast303</username>
        <id>3416213</id>
      </contributor>
      <origin>4676692</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="33657" sha1="7qf36nmy76j71dabj9f8lbllnxlf0vd" xml:space="preserve">Chess, unlike many other games, does not involve direct chance such as the roll of a dice or which card is drawn. Moreover, both sides always know where all the pieces are. This is known as &quot;perfect information&quot;. However, because of its vast complexity, the far-reaching consequences of some decisions are practically unforeseeable.

One player (&quot;White&quot;) has the white pieces while the other (&quot;Black&quot;) has the black pieces. Sometimes the colors are not black and white (for instance, light and dark, or yellow and blue), but they generally contrast each other. In friendly games the choice of colors can be made by any method, such as flipping a coin. If there is no coin at hand, another typical way of deciding would be to conceal a black piece in one hand and a white piece in the other and ask one's opponent to select a hand. The colored piece selected will be the opponent's color. In competitive games the players are assigned their colors.

=== Order of play ===
Once all the pieces have been arranged, White (or the lighter color) makes the first move. White ''always'' makes the first move; this is important for notation, and any chess player will insist upon it. After White has made the move, Black will then make a move. The gameplay will continue in alternating fashion, White making a move, followed by Black.

===General movement rules===
*A move consists of moving a single piece, in accordance with its rules of movement, to a square that is unoccupied or occupied by an enemy piece. A player may never move a piece onto a square already occupied by another of his or her own pieces.
**''Exception'': There is a special move called &quot;castling&quot; where two pieces, a rook and the king, are moved; see below.
*If a piece is moved onto a square occupied by an enemy piece, the latter piece is removed from play and the first piece replaces it. The removed piece is said to have been ''captured'' or ''taken''. 
**''Exception'': In ''en passant'' capture, a pawn moves to an unoccupied square but still captures another pawn &quot;in passing&quot;; see below.
*Most pieces move and capture opponent pieces in the same way.
**''Exception'': The pawn has separate rules for moving and capturing opponent pieces.
*Most pieces may only make a move to a non-adjacent square if all the intervening squares are vacant (pieces may not 'jump over' other pieces).
**''Exception'': The knight can move to any suitable final square regardless of occupants of other squares.
**''Exception'': In castling, a king and a rook jump over each other.
*No player may make a move that leaves their own king &quot;in check&quot; (see below).
*The player must ''always'' make a move when it is his or her turn. In other words, he or she cannot choose not to make a move. If no legal move is possible the game ends in a draw (see below), except when the king is in check - this is called ''checkmate'', and is usually how the opposing player wins.

Also, when a pawn moves to a square at the opposite end of the board, it becomes a different piece (pawn promotion); all of these exceptions are covered below in more detail.

==The board==
Traditionally, the game is played on a board of 64 alternating black and white squares turned with a white square to each player's near right-hand corner. &quot;White on right&quot; is a helpful saying to remember this convention. The light and dark squares on the chessboard and the light and dark chess pieces are traditionally referred to as &quot;white&quot; and &quot;black&quot; respectively, although in modern chess sets almost any colors may be used (as long as they are not the ''same'' colors.) 

The horizontal rows of squares are called '''ranks''' and are numbered 1-8; the vertical columns of squares are called '''files''' and given the letters a-h. This way any single square can be easily identified by its rank and file, making it possible to record games by writing down the starting and ending position of the piece that moves every turn.

A chess diagram is always printed from the White player's perspective. 

{{Chess diagram|=
|tleft
|
|=
 8 |  |  |  |  |  |  |  |  |=
 7 |  |  |  |  |  |  |  |  |=
 6 |  |  |  |  |  |  |  |  |=
 5 |  |  |  |  |  |  |  |  |=
 4 |  |  |  |  |  |  |  |  |=
 3 |  |  |  |  |  |  |  |  |=
 2 |  |  |  |  |  |  |  |  |=
 1 |  |  |  |  |  |  |  |  |=
    a  b  c  d  e  f  g  h
|Chess board}}
{{-}}

==The pieces==
The movement of the individual pieces is described below. In all the board diagrams shown, the squares to which the piece in question can move are indicated with x's.


===Pawn===
[[Image:Chess pll45.svg|left]]
Pawns can move one square straight forward, or optionally and on their first move only, two squares straight forward. The pawn is the only piece that can't move backwards. This piece is worth 1 point.


{{Chess diagram|=
|tleft
|
|=
8 |  |  |  |  |  |  |  |  |=
7 |  |  |  |  |  |  |  |pd|=
6 |  |  |  |  |  |pd|  |xx|=
5 |  |  |  |  |  |xx|  |xx|=
4 |xx|  |xx|  |  |  |  |  |=
3 |xx|  |pl|  |  |  |  |  |=
2 |pl|  |  |  |  |  |  |  |=
1 |  |  |  |  |  |  |  |  |=
   a  b  c  d  e  f  g  h
|Pawn move}}
{{-}}

==== Capturing Pieces ====
The pawn can move one square diagonally forward to capture a piece, but cannot capture a piece by moving straight forward. For this reason, two opposing pawns on a file may become blocked by each other. In the first diagram below, legal capture moves for the white pawn are indicated with black circles.

To capture means to displace a piece, meaning, to replace the captured with the capturer.

In the second diagram below the White pawn is prevented from moving forwards by the Black pawn immediately in front of it (in the d-file) which it cannot capture, but it can capture the adjacent Black pawn by moving diagonally forward as seen in the last diagram.

The pawn is the only piece that moves and captures differently.

{{Chess diagram|=
|tleft
|
|=
8 |  |  |  |  |  |  |  |  |=
7 |  |  |  |  |  |  |  |  |=
6 |  |  |  |  |  |  |  |  |=
5 |  |  |xo|  |xo|  |  |  |=
4 |  |  |  |pl|  |  |  |  |=
3 |  |  |  |  |  |  |  |  |=
2 |  |  |  |  |  |  |  |  |=
1 |  |  |  |  |  |  |  |  |=
   a  b  c  d  e  f  g  h
|Pawn capture}}

{{Chess diagram|=
|tleft
|
|=
8 |  |  |  |  |  |  |  |  |=
7 |  |  |  |  |  |  |  |  |=
6 |  |  |  |  |  |  |  |  |=
5 |  |  |  |pd|pd|  |  |  |=
4 |  |  |  |pl|  |  |  |  |=
3 |  |  |  |  |  |  |  |  |=
2 |  |  |  |  |  |  |  |  |=
1 |  |  |  |  |  |  |  |  |=
   a  b  c  d  e  f  g  h
|Position before capture}}

{{Chess diagram|=
|tleft
|
|=
8 |  |  |  |  |  |  |  |  |=
7 |  |  |  |  |  |  |  |  |=
6 |  |  |  |  |  |  |  |  |=
5 |  |  |  |pd|pl|  |  |  |=
4 |  |  |  |  |  |  |  |  |=
3 |  |  |  |  |  |  |  |  |=
2 |  |  |  |  |  |  |  |  |=
1 |  |  |  |  |  |  |  |  |=
   a  b  c  d  e  f  g  h
|Position after capture}}
{{-}}

===Knight===
[[Image:Chess nll45.svg|left]]
The knight has a unique move that allows it to flank the other pieces. The easiest way to describe this move is that he moves to a square of the opposite color from the one he's on that is exactly two squares away from him. This piece is worth 3 points.

{{Chess diagram|=
|tleft
|
|=
 8 |  |  |  |  |  |  |  |  |=
 7 |  |  |  |xx|  |xx|  |  |=
 6 |  |  |xx|  |  |  |xx|  |=
 5 |  |  |  |  |nl|  |  |  |=
 4 |  |  |xx|  |  |  |xx|  |=
 3 |  |  |  |xx|  |xx|  |  |=
 2 |  |  |  |  |  |  |  |  |=
 1 |  |  |  |  |  |  |  |  |=
    a  b  c  d  e  f  g  h
|Knight move, when starting from a dark colored square he moves to a light square two away}}

{{Chess diagram|=
|tleft
|
|=
 8 |  |  |  |  |  |  |  |  |=
 7 |  |  |  |xx|  |  |  |  |=
 6 |  |  |  |  |  |  |  |  |=
 5 |  |  |xx|  |  |  |  |  |=
 4 |  |  |  |  |  |  |xo|  |=
 3 |  |xx|  |  |xo|  |  |  |=
 2 |  |  |xo|  |  |  |  |  |=
 1 |nl|  |  |  |  |  |  |  |=
    a  b  c  d  e  f  g  h
|The knight moves along straight lines like all other pieces, two such lines marked here}}
{{-}}

Another way to visualize the move is this: of the 16 squares that are 2 away from a knight he reaches the 8 that are of the opposite color of the square he's on and the other 8 can be reached by a queen where she on his square.

{{-}}
{{Chess diagram|=
|tleft
|
|=
 8 |xo|  |  |  |xo|  |  |  |=
 7 |  |xo|  |  |xo|  |  |xo|=
 6 |  |  |xo|xx|xo|xx|xo|  |=
 5 |  |  |xx|xo|xo|xo|xx|  |=
 4 |xo|xo|xo|xo|nl|xo|xo|xo|=
 3 |  |  |xx|xo|xo|xo|xx|  |=
 2 |  |  |xo|xx|xo|xx|xo|  |=
 1 |  |xo|  |  |xo|  |  |xo|=
    a  b  c  d  e  f  g  h
|Knight move compared to the queen move}}
{{Chess diagram|=
|tleft
|
|=
 8 |  |  |  |  |  |  |  |  |=
 7 |  |  |xo|xx|xo|xx|xo|  |=
 6 |  |  |xx|  |  |  |xx|  |=
 5 |  |  |xo|  |nl|  |xo|  |=
 4 |  |  |xx|  |  |  |xx|  |=
 3 |  |  |xo|xx|xo|xx|xo|  |=
 2 |  |  |  |  |  |  |  |  |=
 1 |  |  |  |  |  |  |  |  |=
    a  b  c  d  e  f  g  h
|Knight move compared to the queen again. Of the squares 2 away, the knight has 8 marked X and the queen could reach the other 8}}
{{-}}

It is important to remember that the knight moves in a straight line like all the other pieces, it's just along lines of movement no other piece uses. Consider this comparison: A queen moves ordinally along the ranks and files - North, East, South, and West on a compass rose; and she also moves diagonally - Northeast, Southeast, Southwest, and Northwest on a compass rose.  The knight moves along the wind lines of the rose - North by Northeast, East by Northeast, and so on. These lines pass between the squares adjacent to the knight and pass through the middle of the squares that are one square away from the knight.  The knight moves to the first square its line of movement passes through the middle of, so like the King the knight has eight squares he can move to when he is near the center of the board. Since the knight is moving between the squares adjacent to him pieces do not hinder his move whether they are allied or enemy.

==== Capturing Pieces ====
The knight captures any opponent's piece that occupies a square it can move to by removing that piece from the board and placing the knight in that square.  An important consequence of the knight's use of wind lines is that it can attack (that is, threaten to capture) pieces without being threatened in return so long as they are not also knights.  The reverse is also true - pieces attacking a knight are never threatened by it.


{{Chess diagram|=
|tleft
|
|=
 8 |  |  |  |  |  |  |  |  |=
 7 |  |  |  |  |  |  |  |  |=
 6 |  |  |  |pd|  |kd|  |  |=
 5 |  |  |rd|  |  |  |pd|  |=
 4 |  |  |  |  |nl|  |  |  |=
 3 |  |  |bd|  |  |  |rd|  |=
 2 |  |  |  |qd|  |pd|  |  |=
 1 |  |  |  |  |  |  |  |  |=
    a  b  c  d  e  f  g  h
|Knight capture}}
{{Chess diagram|=
|tleft
|
|=
 8 |  |  |  |  |  |  |  |  |=
 7 |  |  |  |  |  |  |  |  |=
 6 |  |  |  |qd|  |qd|  |  |=
 5 |  |  |qd|ql|ql|ql|qd|  |=
 4 |  |  |  |ql|nl|ql|  |  |=
 3 |  |  |qd|ql|ql|ql|qd|  |=
 2 |  |  |  |qd|  |qd|  |  |=
 1 |  |  |  |  |  |  |  |  |=
    a  b  c  d  e  f  g  h
|Knight capture - Jumping over pieces}}
{{-}}

===Bishop===
[[Image:Chess_bll44.png|left]]
The bishop can move any number of squares diagonally. The bishop may not jump over any piece of either color. 

The bishop is restricted to the color of squares on which it began the game. Each player starts out with one light-square bishop that moves on the light colored squares, and one dark-square bishop that moves on the dark colored squares. In the diagram below, the bishop stands on a light square and can only move to other light squares. This piece worth 3 points.

{{-}}
{{Chess diagram|=
|tleft
|
|=
8 |xx|  |  |  |  |  |  |  |=
7 |  |xx|  |  |  |  |  |xx|=
6 |  |  |xx|  |  |  |xx|  |=
5 |  |  |  |xx|  |xx|  |  |=
4 |  |  |  |  |bl|  |  |  |=
3 |  |  |  |xx|  |xx|  |  |=
2 |  |  |xx|  |  |  |xx|  |=
1 |  |xx|  |  |  |  |  |xx|=
   a  b  c  d  e  f  g  h
|Bishop move}}

{{Chess diagram|=
|tleft
|
|=
8 |  |  |  |  |  |  |  |  |=
7 |  |qd|  |  |  |  |  |  |=
6 |  |  |xx|  |  |  |  |  |=
5 |  |  |  |xx|  |qd|  |  |=
4 |  |  |  |  |bl|  |  |  |=
3 |  |  |  |xx|  |xx|  |  |=
2 |  |  |qd|  |  |  |xx|  |=
1 |  |  |  |  |  |  |  |qd|=
   a  b  c  d  e  f  g  h
|Bishop capture}}
{{-}}

==== Capturing Pieces ====
The bishop captures any opponent's piece that it encounters during the movement described above, and then occupies the captured piece's square. In the diagram above the bishop may take any of the black queens. Notice that bishop may not move (jump) to squares behind or capture pieces hiding behind the queens.

===Rook===
[[Image:Chess rll45.svg|left]]
The rook can be moved any number of squares horizontally or vertically, but not diagonally. Like the bishop, the rook cannot jump over any pieces, except for &quot;castling&quot;. This piece is worth 5 points.  

{{-}}
{{Chess diagram|=
|tleft
|
|=
8 |  |  |  |  |xx|  |  |  |=
7 |  |  |  |  |xx|  |  |  |=
6 |  |  |  |  |xx|  |  |  |=
5 |  |  |  |  |xx|  |  |  |=
4 |xx|xx|xx|xx|rl|xx|xx|xx|=
3 |  |  |  |  |xx|  |  |  |=
2 |  |  |  |  |xx|  |  |  |=
1 |  |  |  |  |xx|  |  |  |=
   a  b  c  d  e  f  g  h
|Rook move}}

{{Chess diagram|=
|tleft
|
|=
8 |  |  |  |  |qd|  |  |  |=
7 |  |  |  |  |xx|  |  |  |=
6 |  |  |  |  |xx|  |  |  |=
5 |  |  |  |  |xx|  |  |  |=
4 |  |qd|xx|xx|rl|qd|  |  |=
3 |  |  |  |  |xx|  |  |  |=
2 |  |  |  |  |qd|  |  |  |=
1 |  |  |  |  |  |  |  |  |=
   a  b  c  d  e  f  g  h
|Rook capture}}
{{-}}

==== Capturing Pieces ====
If the rook attempts to occupy a space already occupied by an opponent's piece, it captures the piece. In the diagram above the rook may take any of the black queens.

===Queen===
[[Image:Chess qll45.svg|left]]
The queen is the most powerful piece, being able to move any number of squares in any lateral or diagonal direction. It is best described as the combination of a rook's and bishop's movement capabilities.This piece is worth 9 points.

{{-}}
{{Chess diagram|=
|tleft
|
|=
8 |xx|  |  |  |xx|  |  |  |=
7 |  |xx|  |  |xx|  |  |xx|=
6 |  |  |xx|  |xx|  |xx|  |=
5 |  |  |  |xx|xx|xx|  |  |=
4 |xx|xx|xx|xx|ql|xx|xx|xx|=
3 |  |  |  |xx|xx|xx|  |  |=
2 |  |  |xx|  |xx|  |xx|  |=
1 |  |xx|  |  |xx|  |  |xx|=
   a  b  c  d  e  f  g  h
|Queen move}}

{{Chess diagram|=
|tleft
|
|=
8 |  |  |  |  |qd|  |  |  |=
7 |  |qd|  |  |xx|  |  |  |=
6 |  |  |xx|  |xx|  |qd|  |=
5 |  |  |  |xx|xx|xx|  |  |=
4 |  |  |qd|xx|ql|xx|xx|qd|=
3 |  |  |  |xx|xx|qd|  |  |=
2 |  |  |qd|  |qd|  |  |  |=
1 |  |  |  |  |  |  |  |  |=
   a  b  c  d  e  f  g  h
|Queen capture}}
{{-}}

==== Capturing Pieces ====

The queen captures any opponent's piece that it encounters during the movement described above, and then occupies the captured piece's square. In the diagram above the queen may take any of the black queens.

===King===
[[Image:Chess_kll44.png|left]]
The king can move one square at a time in any direction, as long as doing so does not place himself in check (see below). This piece is worth ∞ points, because if you lose the king, you lose the game. (Note that the king would be 3.5 points as an attacker/defender.)
{{-}}
{{Chess diagram|=
|tleft
|
|= 
8 |  |  |  |  |  |  |  |  |=
7 |  |  |  |  |  |  |  |  |=
6 |  |  |  |  |  |  |  |  |=
5 |  |  |  |xx|xx|xx|  |  |=
4 |  |  |  |xx|kl|xx|  |  |=
3 |  |  |  |xx|xx|xx|  |  |=
2 |  |  |  |  |  |  |  |  |=
1 |  |  |  |  |  |  |  |  |=
   a  b  c  d  e  f  g  h
|King move}}

{{Chess diagram|=
|tleft
|
|= 
8 |  |  |  |  |  |  |  |  |=
7 |  |  |  |  |  |  |  |  |=
6 |  |  |  |  |  |  |  |  |=
5 |  |  |  |nd|  |nd|  |  |=
4 |  |  |  |  |kl|  |  |  |=
3 |  |  |  |nd|  |nd|  |  |=
2 |  |  |  |  |  |  |  |  |=
1 |  |  |  |  |  |  |  |  |=
   a  b  c  d  e  f  g  h
|King capture}}

{{Chess diagram|=
|tleft
|
|= 
8 |  |  |  |  |  |  |  |  |=
7 |  |  |  |  |  |  |  |  |=
6 |  |  |  |  |  |  |  |  |=
5 |  |  |  |  |nd|  |  |  |=
4 |  |  |  |nd|kl|nd|  |  |=
3 |  |  |  |  |nd|  |  |  |=
2 |  |  |  |  |  |  |  |  |=
1 |  |  |  |  |  |  |  |  |=
   a  b  c  d  e  f  g  h
|King capture}}
{{-}}

==== Capturing Pieces ====
The king may capture any opponent's piece adjacent to it, as long as doing so does not place himself in check (see below). In the diagrams above the king may take any of the black knights.

==== Check ====

The king is the most important piece belonging to each player, though not the most powerful. If a player moves a piece such that he threatens to capture his opponent's king in the next move, that king is said to be in ''check''. 

If a player's king is in check, he must immediately remove the check by moving the king, blocking the check with another piece, or capturing the checking piece. 

In the diagram below black's rook has checked the white king. White may avoid the check by moving the king one step sideways, blocking the check by putting the rook between the attacking black rook and the white king, or capture the black rook using the white bishop. Other normally legal moves, like moving one of the pawns, are illegal in this position since they will not remove the check.   

In a friendly game, a check is usually announced by saying ''check'' after the move is completed.

{{Chess diagram|=
|tleft
|
|= 
8 |  |  |  |  |rl|  |  |  |=
7 |  |  |  |  |  |  |  |  |=
6 |  |  |  |  |  |  |  |  |=
5 |  |  |  |  |  |  |  |  |=
4 |  |  |  |bl|  |  |  |  |=
3 |  |  |  |  |  |  |  |pl|=
2 |  |  |  |  |  |pl|pl|xx|=
1 |rd|  |  |  |xx|  |kl|  |=
   a  b  c  d  e  f  g  h
|White king in check, the X marks the moves white can make. }}
{{-}}

==== Checkmate ====

If the king is placed in check and can not escape, it is said to have been ''checkmated'' (or &quot;''mated''&quot; for short). The first player to checkmate the opponent's king wins the game. Note that the king is never actually captured, since it is obliged to move out of check whenever possible (and the game ends when it is impossible). In the diagram below white has no options to escape the check from black's rook, he is therefore checkmated.

{{Chess diagram|=
|tleft
|
|= 
8 |  |  |  |  |  |  |  |  |=
7 |  |  |  |  |  |  |  |  |=
6 |  |  |  |  |  |  |  |  |=
5 |  |  |  |  |  |  |  |  |=
4 |  |  |  |  |  |  |  |  |=
3 |  |  |  |  |  |  |  |  |=
2 |  |  |  |  |  |pl|pl|pl|=
1 |rd|  |  |  |  |  |kl|  |=
   a  b  c  d  e  f  g  h
|White king in checkmate}}
{{-}}

====Special Restrictions — Avoiding &quot;Self-check&quot; ====

Players may not make any move which allows their king to be captured in the next move, i.e. places their own king in check. Thus two kings may never occupy adjacent squares, since they would have put themselves in check by moving there.  This is called the &quot;opposition&quot; and is indispensable when, for instance, you are using a queen or rook to checkmate a king.

The white king in the following diagram cannot move upwards or to the left since it would be in check from the bishop, or diagonally downwards which would leave it adjacent to the black king. Also, as no piece is threatening it if it fails to move, the king is not currently in check. Similarly, the black king cannot move diagonally upwards as that would put it next to the White king.

{{Chess diagram|=
|tleft
|
|= 
8 |  |  |  |  |  |  |  |  |=
7 |  |  |  |  |  |  |bd|  |=
6 |  |  |  |  |  |  |  |  |=
5 |  |  |  |xx|  |xx|  |  |=
4 |  |  |  |  |kl|xx|  |  |=
3 |  |  |  |xx|xx|  |xo|xo|=
2 |  |  |  |  |  |xo|kd|xo|=
1 |  |  |  |  |  |xo|xo|xo|=
   a  b  c  d  e  f  g  h
|King may not move to an attacked square}}
{{-}}

The diagram below shows a position where the white bishop's movement is restricted by the same rule; the bishop can not be moved since the move would let black capture the white king in his next move. The white king on the other hand may move to any of the adjacent squares. 
{{Chess diagram|=
|tleft
|
|= 
8 |  |  |  |  |rd|  |  |  |=
7 |  |  |  |  |  |  |  |  |=
6 |  |  |  |  |  |  |  |  |=
5 |  |  |  |  |  |  |  |  |=
4 |  |  |  |  |  |  |  |  |=
3 |  |  |  |  |  |  |  |  |=
2 |  |  |  |  |bl|  |  |  |=
1 |  |  |  |  |kl|  |  |  |=
   a  b  c  d  e  f  g  h
|Bishop may not move}}
{{-}}

==Special Moves==
====Pawn Promotion====
If a pawn makes it to one of the eight squares along the far edge of the board from their initial position, the pawn is &quot;promoted&quot;. Upon reaching the far rank the player exchanges the pawn with either a queen, a rook, a bishop, or a knight. The player's move ends when the new piece occupies the promoted square.  

The new piece need not be a previously captured piece. Thus a player can have more than one queen, and more than two rooks, bishops or knights on the board. The player may never have more than one king, since the pawn can not be promoted to a king. In theory it is possible to get up to nine queens, or ten rooks, bishops or knights since there are eight pawns to promote. In practice however the pawn is usually promoted to a queen, since it is the most powerful piece, and it is rare for a player to have more than two queens on the board. If an extra queen is not at hand, an upside-down rook is usually used as a substitute. Sometimes, a player might want a different piece like a knight, if the queen's movements would not be helpful. 

{{Chess diagram|=
|tleft
|
|=
8 |  |  |  |  |xx|  |  |  |=
7 |  |  |  |  |pl|  |  |  |=
6 |  |  |  |  |  |  |  |  |=
5 |  |  |  |  |  |  |  |  |=
4 |  |  |  |  |  |  |  |  |=
3 |  |  |  |  |  |  |  |  |=
2 |  |  |  |  |  |  |  |  |=
1 |  |  |  |  |  |  |  |  |=
   a  b  c  d  e  f  g  h
|Pawn promotion - before move}}

{{Chess diagram|=
|tleft
|
|=
8 |  |  |  |  |ql|  |  |  |=
7 |  |  |  |  |  |  |  |  |=
6 |  |  |  |  |  |  |  |  |=
5 |  |  |  |  |  |  |  |  |=
4 |  |  |  |  |  |  |  |  |=
3 |  |  |  |  |  |  |  |  |=
2 |  |  |  |  |  |  |  |  |=
1 |  |  |  |  |  |  |  |  |=
   a  b  c  d  e  f  g  h
|Pawn promotion - after move}}
{{-}}

====Castling====

[[Image:SCD_castle_kingside.png|frame|right|Kingside castling: O-O]]
[[Image:SCD_castle_queenside.png|frame|right|Queenside castling: O-O-O]]

Castling is a move involving the king and either of the rooks. Castling performed with the king's rook is called kingside castling, performed with the queen's rook is called queenside castling. A castling is typically done to move the king to a protective 'castle' surrounded by three pawns and a rook. 

Subject to restrictions detailed below, a player may move his king two squares towards the rook, and subsequently, ''on the same turn'', move the rook adjacent to but on the opposite side of the king, (onto the square over which the king has just passed).

The restrictions specific to castling are:

#Neither the king nor the participating rook may have moved previously in the game
#The king must not be in check at the start of the move, though it may have been in check previously in the game.
#The square over which the king passes must not be under attack ('in check') from an enemy piece.  (This would expose the king to a &quot;check&quot; in passing.)  The rook(s) may be under attack, or the queens' rooks may pass through an attacked queens' knight square.
#The king must not be in check at the end of the move. (Also applies to all normal moves.)
#The squares between the king and rook must be vacant.
#The king can also only castle horizontally. 

The diagrams below show examples of positions where castling is not legal.

{{Chess diagram|=
|tleft
|
|=
8 |  |  |  |  |rd|  |  |  |=
7 |  |  |  |  |  |  |  |  |=
6 |  |  |  |  |  |  |  |  |=
5 |  |  |  |  |  |  |  |  |=
4 |  |  |  |  |  |  |  |  |=
3 |  |  |  |  |  |  |  |  |=
2 |  |  |  |  |  |pl|pl|pl|=
1 |  |  |  |  |kl|  |  |rl|=
   a  b  c  d  e  f  g  h
|King in check before move}}

{{Chess diagram|=
|tleft
|
|=
8 |  |  |  |  |  |  |  |  |=
7 |  |  |  |  |  |  |  |  |=
6 |  |  |  |  |  |  |  |  |=
5 |  |bd|  |  |  |  |  |  |=
4 |  |  |  |  |  |  |  |  |=
3 |  |  |  |  |  |  |  |  |=
2 |  |  |  |  |  |pl|pl|pl|=
1 |  |  |  |  |kl|xx|  |rl|=
   a  b  c  d  e  f  g  h
|King passing attacked square}}

{{Chess diagram|=
|tleft
|
|=
8 |  |  |  |  |  |  |  |  |=
7 |  |  |  |  |  |  |  |  |=
6 |  |  |  |  |  |  |  |  |=
5 |  |  |  |  |  |  |  |  |=
4 |  |  |  |  |  |  |  |  |=
3 |  |  |  |  |  |  |pl|nd|=
2 |  |  |  |  |  |pl|  |pl|=
1 |  |  |  |  |kl|  |xx|rl|=
   a  b  c  d  e  f  g  h
|King in check after move}}

{{Chess diagram|=
|tleft
|
|=
8 |  |  |  |  |  |  |  |  |=
7 |  |  |  |  |  |  |  |  |=
6 |  |  |  |  |  |  |  |  |=
5 |  |  |  |  |  |  |  |  |=
4 |  |  |  |  |  |  |  |  |=
3 |  |  |  |  |  |  |  |  |=
2 |  |  |  |  |  |pl|pl|pl|=
1 |  |  |  |  |kl|nd|nd|rl|=
   a  b  c  d  e  f  g  h
|Square(s) occupied}}
{{-}}

Note that the king must be the first piece moved and it must be moved two squares before it is released. If the rook is touched or moved first, then the king must stay where it is. This rule mainly applies in &quot;strict rules of chess&quot; where if a piece is touched, it must be moved. Touching the rook first indicates a rook only move, while releasing the king after one square indicates a king only move. Moving the king two squares is not a legal move by itself, and indicates a castling move.

{{-}}

====''En passant'' capture====
''En passant'' is French for &quot;in passing&quot;; you capture an enemy pawn as it is passing you.

When a pawn on its first move advances two squares onto the same rank as an opposing pawn on an adjacent file, this opposing pawn may, on that player's next move only, capture the advancing pawn as though it had only moved one square (provided the move is otherwise legal).  The pawn's ability to move two squares on their first move was a relatively late addition to the game of chess.  En Passant was introduced to prevent abuses of the new rule.

In the following example, the Black pawn advances two squares, and is captured by the White pawn which moves diagonally forwards and to the right (as if the Black pawn had moved only one square forward and been there). This move is only allowed on the turn in which the option is presented.

{{Chess diagram|=
|tleft
|
|=
8 |  |  |  |  |kd|  |  |  |=
7 |  |  |  |  |  |pd|  |  |=
6 |  |  |  |  |  |  |  |  |=
5 |  |  |  |  |pl|xx|  |  |=
4 |  |  |  |  |  |  |  |  |=
3 |  |  |  |  |  |  |  |  |=
2 |  |  |  |  |  |  |  |  |=
1 |  |  |  |  |kl|  |  |  |=
   a  b  c  d  e  f  g  h
|En passant black is about to move the pawn}}

{{Chess diagram|=
|tleft
|
|=
8 |  |  |  |  |kd|  |  |  |=
7 |  |  |  |  |  |  |  |  |=
6 |  |  |  |  |  |xx|  |  |=
5 |  |  |  |  |pl|pd|  |  |=
4 |  |  |  |  |  |  |  |  |=
3 |  |  |  |  |  |  |  |  |=
2 |  |  |  |  |  |  |  |  |=
1 |  |  |  |  |kl|  |  |  |=
   a  b  c  d  e  f  g  h
|En passant before capture}}

{{Chess diagram|=
|tleft
|
|=
8 |  |  |  |  |kd|  |  |  |=
7 |  |  |  |  |  |  |  |  |=
6 |  |  |  |  |  |pl|  |  |=
5 |  |  |  |  |  |  |  |  |=
4 |  |  |  |  |  |  |  |  |=
3 |  |  |  |  |  |  |  |  |=
2 |  |  |  |  |  |  |  |  |=
1 |  |  |  |  |kl|  |  |  |=
   a  b  c  d  e  f  g  h
|En passant after capture}}
{{-}}

==Initial position==
{{Chess diagram|=
|tleft
|
|=
8 |rd|nd|bd|qd|kd|bd|nd|rd|=
7 |pd|pd|pd|pd|pd|pd|pd|pd|=
6 |  |  |  |  |  |  |  |  |=
5 |  |  |  |  |  |  |  |  |=
4 |  |  |  |  |  |  |  |  |=
3 |  |  |  |  |  |  |  |  |=
2 |pl|pl|pl|pl|pl|pl|pl|pl|=
1 |rl|nl|bl|ql|kl|bl|nl|rl|=
   a  b  c  d  e  f  g  h
|Initial position}}

In the initial position each side has eight pawns, two rooks, two knights, two bishops, a queen and a king arranged as shown in the diagram below. Note that the only pieces on either side which can initially move are the pawns and knights.

Beginners often set up the board incorrectly; it is a complex position to remember. The following mnemonics may help you remember where the pieces go.

*'''White on the Right''' It is important that the bottom-right-hand square is light-colored.
*'''Knights live in castles''' One knight is placed next to each rook (rooks look like the towers of a castle, and are sometimes [incorrectly] even ''called'' castles.)
*'''Queens on their color''' OR '''The dress matches the shoes''' The White Queen goes on a White Square, Black Queen goes on a Black Square
*'''Bishops are advisers to the Royalty''' Bishops surround the King and Queen.
*'''White King on the Right''' From the White Player's perspective, both Kings are on the right, and from the Black Player's perspective, the Kings are on the left.

If the ranks and files are printed on the board, the following rules may be helpful:
* White's pieces should be placed on the 1st and 2nd rank, and Black's pieces should be placed on the 7th and 8th rank. 
* The Queens should be positioned on the d-file (''D for Dame''). 
{{-}}

==Conclusion of the game==
Play continues to alternate between White and Black until one of the following outcomes is reached:

===Winning and losing===
*One player's king is checkmated. The game is lost by that player.
*In a competitive game, one player runs out of time. The game is lost by that player (with two important exceptions, see draws below).
*One player resigns, which is equivalent to quitting the game. A player may resign on either his or his opponent's turn. Resignation is often symbolized by the resigning player tipping over his king.

===Draws===
*The player to move has been ''stalemated'', meaning that he has no legal move and is not in check.
*Both players agree to draw the game. Either player may offer a draw to the opponent upon completion of his move. If the offer is accepted, the game is drawn. If the offer is rejected, the game will continue.
*A player can claim a draw with if any of the following are true:
**If the exact same position occurs or will occur three times with the same player to move, the player on move may claim a draw by threefold repetition. Note that the same set of moves must be available for each player (including castling and ''en passant'').
**No pawn has moved and no piece was captured in the last 50 moves.
**The opponent does not have sufficient material to checkmate him by any legal sequence of moves.
**Both players have run out of time in a competitive game.
**One player has run out of time in a competitive game, but the opponent does not have sufficient pieces to checkmate him by any legal sequence of moves.

{{Chess diagram|=
|tleft
|
|=
8 |  |  |  |  |  |  |  |kd|=
7 |  |  |  |  |  |  |  |  |=
6 |  |pd|  |  |  |kl|ql|  |=
5 |  |pl|  |  |  |  |  |  |=
4 |  |  |  |  |  |  |  |  |=
3 |  |  |  |  |  |  |  |  |=
2 |  |  |  |  |  |  |  |  |=
1 |  |  |  |  |  |  |  |  |=
   a  b  c  d  e  f  g  h
|Black (to move) is stalemated}}

{{Chess diagram|=
|tleft
|
|=
8 |  |  |  |  |  |  |  |ql|=
7 |  |  |  |  |  |  |  |  |=
6 |  |  |  |  |  |  |  |  |=
5 |  |  |  |  |  |  |  |  |=
4 |  |  |  |  |  |  |  |  |=
3 |  |  |  |  |  |  |pl|pl|=
2 |  |  |  |  |  |rd|kl|  |=
1 |  |  |  |  |kd|xo|xx|xx|=
   a  b  c  d  e  f  g  h
|Threefold repetition}}

{{Chess diagram|=
|tleft
|
|=
8 |  |  |  |  |kd|bd|  |  |=
7 |  |  |  |  |  |  |  |  |=
6 |  |  |  |  |  |  |  |  |=
5 |  |  |  |  |  |  |  |  |=
4 |  |  |  |  |  |  |  |  |=
3 |  |  |  |  |  |  |  |  |=
2 |  |  |  |  |  |  |  |  |=
1 |  |  |  |  |kl|bl|nl|  |=
   a  b  c  d  e  f  g  h
|50 move rule}}

{{Chess diagram|=
|tleft
|
|=
8 |  |  |  |  |  |  |  |  |=
7 |  |  |  |  |  |  |  |  |=
6 |  |  |  |  |  |  |  |  |=
5 |  |  |  |  |  |kd|  |  |=
4 |  |  |  |  |  |nl|  |  |=
3 |  |  |  |  |  |kl|  |  |=
2 |  |  |  |  |  |  |  |  |=
1 |  |  |  |  |  |  |  |  |=
   a  b  c  d  e  f  g  h
|Insufficient mating material}}

{{-}}

The diagrams above shows example of some of the draw rules:
* Stalemate: Since black can not move the pawn or the king without placing himself in self-check, the game results in a stalemate.
* Threefold repetition: Black has checked white, and can continue to check white forever by moving the rook back and forth between f2 and f1. The same position will thus occur again and again. 
* 50 move rule: White has material advantage and enough material to mate, but if black plays correctly black will use his bishop to avoid being mated forever.   
* Insufficient mating material: White has material advantage, but not enough material to mate.

==Chess Etiquette==
Generally, chess games at tournaments are conducted under the following rules:
*'''Touch-move rule''' - If a player touches his own piece, he must move it, and if a player touches an opponents piece, he must capture it (unless the capture is not possible).  If he releases a piece on a square, the move is completed and can't be taken back. If you need to center a piece on its square, it is traditional to say ''j'adoube'' (I adjust).
*'''Be silent when your opponent is on the move''' - You can only adjust pieces, offer a draw, or claim a draw when it is their turn to move.

A friendly game may be played in any way that is mutually agreeable.  Generally it is considerate to avoid distracting your opponent.

==Glossary==
&lt;!--It's just a coincidence that these are in alphabetical order. If you would like to add terms, please put them in such an order so that it would make sense only by reading straight down with more basic series of terms at the top. Terms for which it is unnecessary to read other definitions, please place them at the bottom in alphabetical order.--&gt;
*'''Capture''' - To move one's piece into the same square as one of one's opponent's pieces.  The opponent's piece is removed from the board.
*'''Check''' - The king is 'in check' when it is being attacked by an enemy piece.
*'''Checkmate''' - The player whose turn it is can make no legal move to get his king out of check.
*'''Stalemate''' - The player whose turn it is can make no legal move, but the king is not in check.
&lt;noinclude&gt;{{Chess/Navigation|Arranging The Board|Notating The Game}}&lt;/noinclude&gt;

[[es:Manual de Ajedrez/Iniciación del juego]]
[[it:Scacchi/Le regole del gioco]]
[[ms:Catur/Bermain]]
[[nl:Schaken/Spelregels]]
[[pt:Xadrez/Regras]]
[[ro:Şah/Reguli de bază]]
[[zh:国际象棋/规则]]</text>
      <sha1>7qf36nmy76j71dabj9f8lbllnxlf0vd</sha1>
    </revision>
  </page>
  <page>
    <title>OpenSSH/Cookbook/Public Key Authentication</title>
    <ns>0</ns>
    <id>51866</id>
    <revision>
      <id>4676709</id>
      <parentid>4675819</parentid>
      <timestamp>2026-10-18T08:53:09Z</timestamp>
      <contributor>
        <username>Larsnooden</username>
        <id>430753</id>
      </contributor>
      <minor />
      <comment>grammar</comment>
      <origin>4676709</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="81899" sha1="gk2u3ndyhu5onggmpqpe26630e4np4c" xml:space="preserve">&lt;noinclude&gt;{{simple chapter navigation|previous=File Transfer with SFTP|next=Certificate-based Authentication}}&lt;/noinclude&gt;
&amp;nbsp;

Authentication keys can improve efficiency, if done properly.  As a bonus advantage, the passphrase and private key never leave the client&lt;ref name=&quot;RFC4252§7&quot;&gt;{{cite web |url=https://tools.ietf.org/html/rfc4252#section-7 |title=The Secure Shell (SSH) Authentication Protocol |publisher=IETF |year=2006| accessdate=2015-05-06}}&lt;/ref&gt;.  Key-based authentication is generally recommended for outward facing systems so that password authentication can be turned off.  

==Key-based authentication==

OpenSSH can use public key cryptography for authentication.  In public key cryptography, encryption and decryption are asymmetric.  The keys are used in pairs, a public key to encrypt and a private key to decrypt.  The [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] utility can make RSA, Ed25519, MLDSA44-Ed25519, ECDSA, Ed25519-SK, or ECDSA-SK keys for authenticating.  Even though DSA keys can still be made, being exactly 1024 bits in size, they are no longer recommended and should be avoided.  RSA keys are allowed to vary from 1024 bits on up.  The default is now 3072.  However, there is only limited benefit after 2048 bits and that makes elliptic curve algorithms preferable.  ECDSA can be 256, 384 or 521 bits in size.  Ed25519, Ed25519-SK, and ECDSA-SK keys each have a fixed length of 256 bits.  Shorter keys are faster, but less secure.  Longer keys are much slower to work with but provide better protection, up to a point.  

Keys can be named to help remember what they are for.  Because the key files can be named anything it is possible to have many keys each named for different services or tasks.  The comment field at the end of the public key can also be useful in helping to keep the keys sorted, if you have many of them or use them infrequently.  

The process of key-based authentication uses these keys to make a couple of exchanges using the keys to encrypt and decrypt some short message.  At the start, a copy of the client's public key is stored on the server and the client's private key is on the client, both stay where they are.  The private key never leaves the client.  As the client first contacts the server, the server responds by using the client's public key to encrypt a random number and return that encrypted random number as a challenge to the client.  The client responds to the challenge by using the matching private key to decrypt the message and extract the random number.  The client then makes an MD5 hash of the session ID along with the random number from the challenge and returns that hash to the server.  The server then makes its own hash of the session ID and the random number and compares that to the hash returned by the client.  If there is a match, the login is allowed.  If there is not a match, then the next of any public keys on the server registered as belonging to the same account is tried until either a match is found or all the keys have been tried or the maximum number of failures has been reached. &lt;ref name=&quot;How Key Challenges Work&quot;&gt;{{cite web | url=http://www.unixwiz.net/techtips/ssh-agent-forwarding.html#chal | title=An Illustrated Guide to SSH Agent Forwarding | author=Steve Friedl | date=2006-02-22 | accessdate=2013-04-27 | publisher=Unixwiz.net }}&lt;/ref&gt;

When an agent is used on the client side to manage authentication, the process is similar.  The difference is that [http://man.openbsd.org/ssh.1 ssh(1)] passes the challenge off to the agent which then calculates the response and passes it back to [http://man.openbsd.org/ssh.1 ssh(1)] which then passes the agent's response back to the server.  

===Basics of Public Key Authentication===

A matching pair of SSH keys, one public and one private, is needed for public key authentication.  The [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] utility is used to make such a key pair.  Out of that pair the public key must be properly stored on the remote host before using key-based authentication.  The default location for it is the designated '''authorized_keys''' file, usually one such file resides inside each remote user account.  The private key stays stored safely on the client.  

Once the keys have been prepared and the remote account configured, they can be used for login.  Before starting, there must already be an account on the remote system.  The details of doing that are outside of the scope of this book.  However, once you have a remote account, there are four steps to set up key-based authentication for it:

'''1''') Prepare a directory on the client (say a laptop or a desktop) where the keys will stay, if there isn't one already.  For example, if the '''.ssh''' directory is not on the client machine, create it and set the permissions correctly.  It is important that it not be writable by any account except its owner:
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ mkdir ~/.ssh/
$ chmod 0700 ~/.ssh/
&lt;/syntaxhighlight&gt;

'''2''') Create a key pair inside the designated directory.  The example here creates an Ed25519 key pair in the directory '''~/.ssh'''.  The option '''-t''' decides the key type and the option '''-f''' assigns the key file a name.  It is good to give key files descriptive names, especially if larger numbers of keys are managed.  Below, the public key will be named '''fred_example_org_ed25519.pub''' and the private key will be called '''fred_example_org_ed25519'''.  Lastly, the '''-C''' option is used to embed a descriptive comment inside the private key itself.  The comment is useful for figuring out later what the key is for when one has many keys or a lot of time has passed or both.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -t ed25519 -f ~/.ssh/fred_example_org_ed25519 \
        -C &quot;from fred's laptop to server.example.org&quot;
&lt;/syntaxhighlight&gt;

Be sure to enter a solid passphrase so that the private key gets encrypted using 128-bit AES.  That way the private key can only be read or used when the passphrase is given.  

Ed25519, Ed25519-SK, and ECDSA-SK keys have fixed lengths.  For RSA and ECDSA keys, the '''-b''' option sets the number of bits used for those kinds of keys.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -o -b 4096 -t rsa -f ~/.ssh/fred_example_org_rsa \
        -C &quot;from fred's laptop to server.example.org&quot;
&lt;/syntaxhighlight&gt;

Since 6.5 a new private key format is available using a [http://man.openbsd.org/bcrypt.3 bcrypt(3)] key derivative function (KDF) to better protect keys at rest.  This new format is always used for Ed25519 keys, and sometime in the future will be the default for all keys.  But for right now it may be requested when generating or saving existing keys of other types via the '''-o''' option in [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  

Details of the new format are found in the source code in the file '''PROTOCOL.key'''.

'''3''') Get the keys to the right places.  Transfer only the public key to remote machine.  The following assume the default locations for the authorized keys as specified in the server's configuration file by the '''AuthorizedKeysFile''' directive.  

'''3a''') If the utility &lt;code&gt;ssh-copy-id&lt;/code&gt; exists, and if password authentication is allowed, then it can be used to put the public key into place on the remote system.  The ''.pub'' is optional here, the script will figure it out if omitted. 
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-copy-id -i ~/.ssh/fred_example_org_ed25519 fred@server.example.org
&lt;/syntaxhighlight&gt;

If that script was successful in transferring the public key, then go on to step 4 below and test the key.  If not, then try transferring the public key manually as described in step 3b next.

'''3b''') Or the public key can be put in place manually on the remote machine.  For that the remote '''.ssh''' directory is needed, and within that a special file to store the public keys, the default file name is '''authorized_keys'''.  If either the '''authorized_keys''' file or '''.ssh''' directory do not exist on the remote machine, they need to be created.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ mkdir -m 700 ~/.ssh/
$ touch ~/.ssh/authorized_keys
$ chmod 0600 ~/.ssh/authorized_keys
$ nano -w ~/.ssh/authorized_keys
&lt;/syntaxhighlight&gt;

Then any editor which does not wrap long lines can be used to add the public key.  However the '''authorized_keys''' file is edited to add the key, the key itself must be in the file whole and unbroken on a single  line.  For example, [http://linux.die.net/man/1/nano nano(1)] can be started with the '''-w''' option to prevent wrapping of long lines.  (Another way to set line wrapping permanently in [http://linux.die.net/man/1/nano nano(1)] is by editing [http://linux.die.net/man/5/nanorc nanorc(5)].)  

If the key pair is not already on the client, transfer both the public and private keys there.  It is usually best to keep both the public and private keys together in the directory '''~/.ssh/''', though the public key is not always needed on the client after this step and could even be regenerated if it is ever needed again.  

'''4''') Test the keys

While remaining logged in via the first terminal, use the client system to open another window and in it start another SSH session and try authenticating to the remote machine from the client using the private key.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -i ~/.ssh/fred_example_org_ed25519 -l fred server.example.org
&lt;/syntaxhighlight&gt;

The option '''-i''' tells [http://man.openbsd.org/ssh.1 ssh(1)] which private key to try.  
Only after verifying that the key-based authentication works should you close the original window.  

It is possible to make permanent shortcuts on the client using [http://man.openbsd.org/ssh_config.5 ssh_config(5)], explained further below, once key-based authentication is working.  In particular, see the '''IdentityFile''',  '''IdentitiesOnly''', and '''AddKeysToAgent''' configuration directives, to name three.  

It is also a good idea to turn off password authentication, if and only if key-based authentication is setup for all the necessary remote accounts.  

➥ '''Troubleshooting of Key-based Authentication''':

If the server refuses to accept the key and fails over to the next authentication method (e.g.: &quot;Server refused our key&quot;), then there are several possible mistakes to look for on the server side.  

One of the most common errors is that the file and directory permissions are wrong.  The authorized keys file must be owned by the user in question and not be group writable.  Nor may the key file's directory be group or world writable.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ chmod u=rwx,g=rx,o= ~/.ssh
$ chmod u=rw,g=,o=  ~/.ssh/authorized_keys 
&lt;/syntaxhighlight&gt;

Another mistake that can happen is if the key inside the '''authorized_keys''' file on the remote host is broken by line breaks or has other whitespace in the middle.  That can be fixed by joining up the lines and removing the spaces or by recopying the key more carefully.  

And, though it should go without saying, the halves of the key pair need to match.  The public key on the server needs to match the private key held on the client.  If the public key is lost, then a new one can be generated with the '''-y''' option, but not the other way around.  If the private key is lost, then the public key should be erased as it is no longer of any use.  If many keys are in use for an account, it might be a good idea to add comments to them.  On the client, it can be a good idea to know which server the key is for, either through the file name itself or through the comment field.  A comment can be added using the '''-C''' option.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -t ed25519 -f ~/.ssh/fred_example_org_ed25519 -C &quot;web server mirror&quot;
&lt;/syntaxhighlight&gt;

On the server, it can be important to annotate which client they key is from if there is more than one public key there in an account.  There the comment can be added to the authorized keys file on the server in the last column if a comment does not already exist.  Again, the format of the authorized keys file is given in the manual page for [http://man.openbsd.org/sshd.8 sshd(8)] in the section &quot;AUTHORIZED_KEYS FILE FORMAT&quot;.  If the keys are not labeled they can be hard to match, which might or might not be what you want.  

====Associating Keys Permanently with a Server====

A key can be specified at run time, but to save retyping the same paths again and again, the '''Host''' directive in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] can apply specific settings to a target host.  In this case, by changing '''~/.ssh/config''' it is possible to assign particular keys to be tried automatically whenever making a connection to that specific host.  After adding the following lines to '''~/.ssh/config''', all that's needed is to type &lt;code&gt;ssh ''web1''&lt;/code&gt; to connect with the key for that server.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host web1
	Hostname 198.51.100.32
	IdentitiesOnly yes
	IdentityFile /home/fred/.ssh/web_key_ed25519
&lt;/syntaxhighlight&gt;

The '''~/.ssh/config''' below uses different keys for ''server'' versus ''server.example.org'',  regardless whether they resolve to the same machine.   This is possible because the host name argument given to [http://man.openbsd.org/ssh.1 ssh(1)] is not converted to a canonicalized host name before matching.

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host server
	IdentitiesOnly yes
	IdentityFile /home/fred/.ssh/key_a_ed25519

Host server.example.org
	IdentitiesOnly yes
	IdentityFile /home/fred/.ssh/key_b_ed25519
&lt;/syntaxhighlight&gt;

In this example the shorter name is tried first, but of course less ambiguous shortcuts can be made instead.  The configuration file gets parsed on a first-match basis.  So the most specific rules go at the beginning and the most general rules go at the end.  

====Encrypted Home Directories====

When using encrypted home directories the keys must be stored in an unencrypted directory.  That means somewhere outside the actual home directory which means [http://man.openbsd.org/sshd.8 sshd(8)] needs to be configured appropriately to find the keys in that special location.  

Here is one method for solving the access problem.  Each user is given a subdirectory under '''/etc/ssh/keys/''' which they can then use for storing their '''authorized_keys''' file.  This is set in the server's configuration file '''/etc/ssh/sshd_config'''

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthorizedKeysFile      /etc/ssh/keys/%u/authorized_keys
&lt;/syntaxhighlight&gt;

Setting a special location for the keys opens up more possibilities as to how the keys can be managed and multiple key file locations can be specified if they are separated by whitespace.  The user does not have to have write permissions for the '''authorized_keys''' file.  Only read permission is needed to be able to log in.  But if the user is allowed to add, remove, or change their keys, then they will need write access to the file to do that.  

One symptom of having an encrypted home directory is that key-based authentication only works when you are already logged into the same account, but fails when trying to make the first connection and log in for the first time.

Sometimes it is also necessary to add a script or call a program from '''/etc/ssh/sshrc''' immediately after authentication to decrypt the home directory.

====Passwordless Login====

One solution for passwordless logins is to still have a passphrase and work with an authentication agent in conjunction with a single-purpose key.  Most desktop environments launch an SSH agent automatically these days.  It will be visible in the '''SSH_AUTH_SOCK''' environment variable if it is.  On accounts with an agent, [http://man.openbsd.org/ssh-add.1 ssh-add(1)] can load private keys into an available agent.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-add ~/.ssh/fred_example_org_ed25519
&lt;/syntaxhighlight&gt;

Thereafter, the client will automatically check the agent for the key when appropriate.  If there are many keys in the agent, it will become necessary to set '''IdentitiesOnly'''.  See the above section on using '''~/.ssh/config''' for that.  See [[OpenSSH/Cookbook/Public_Key_Authentication#Key-based_Authentication_Using_an_Agent|Key-based Authentication Using an Agent]] below.  

Another, riskier, way of allowing passwordless logins is to follow the steps above, but simply do not enter a passphrase when asked for one while creating the key.  Note that using keys that lack a passphrase is very risky, so the key files should be very well protected and kept track of, and ideally locked down with a '''command=''' option or '''ForceCommand''' directive on the server.  That includes those keys which will only be used as single-purpose keys as described below.  

Timely key rotation becomes especially important.  In general, it is not a good idea to make a key without a passphrase.

====Requiring Both Keys and a Password====

While users should have strong passphrases for their keys, there is no way to enforce or verify that.  Indeed, since neither the private key nor its the passphrase ever leave the client machine there is nothing that the server can do to have any influence over that.  Instead, it is possible to require both a key and a password.  Starting with OpenSSH 6.2, it is possible for the server to require multiple authentication methods for login using the '''AuthenticationMethods''' directive.   
&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthenticationMethods publickey,password
&lt;/syntaxhighlight&gt;

This example from [http://man.openbsd.org/sshd_config.5 sshd_config(5)] requires that users first authenticate using a key and it only queries for a password if the key succeeds.  Thus with that configuration it is not possible to get to the system password prompt without first authenticating with a valid key.  Changing the order of the arguments changes the order of the authentication methods.

====Requiring Two or More Keys====

Since OpenSSH 6.8, the server now remembers which public keys have been used for authentication and refuses to accept previously-used keys.  This allows a set up requiring that users authenticate using two different public keys, maybe one in the file system and the other in a hardware token. 

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthenticationMethods publickey,publickey
&lt;/syntaxhighlight&gt;

The '''AuthenticationMethods''' directive, whether for keys or passwords, can also be set on the server under a '''Match''' directive to apply only to certain groups or situations.

====Requiring Certain Key Types For Authentication====

Also since OpenSSH 6.8, the '''PubkeyAcceptedKeyTypes''' directive, later changed to '''PubkeyAcceptedAlgorithms''', can specify which key algorithms are accepted for authentication.  Those not in the comma-separated pattern list are not allowed.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
PubkeyAcceptedAlgorithms ssh-ed25519*,ssh-rsa*,ecdsa-sha2*,sk-ssh-ed25519*,sk-ecdsa-sha2*
&lt;/syntaxhighlight&gt;

Either the actual key types or a pattern can be in the list.  Spaces are not allowed in the pattern list.  The exact list of key types supported for authentication can be found by the '''-Q''' option using the client.  The following two lines are equivalent.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -Q key-sig | sort

$ ssh -Q PubkeyAcceptedAlgorithms | sort
&lt;/syntaxhighlight&gt;

For host-based authentication, it is the '''HostbasedAcceptedAlgorithms''' directive which determines the key types which are allowed for authentication.

===Key-based Authentication Using the AuthorizedKeysCommand Directive===

It is possible to use a program or script to look up public keys rather than keeping them in a static file or files.  Any command called by the '''AuthorizedKeysCommand''' directive needs to either produce a syntactically correct public key while returning the exit code for a successful run or else return the exit code for failure.  The string sent to '''stdout''' will then be processed as part of the authentication work flow.  

Here is a shell script&lt;ref name=&quot;janpietmens&quot;&gt;{{cite web |url=https://jpmens.net/2025/03/25/authorizedkeyscommand-in-sshd/ |title=SSH keys from a command: sshd's AuthorizedKeysCommand directive |accessdate=2025-04-04 |date=2025-03-25 | author=Jan-Piet Mens }}&lt;/ref&gt; at its simplest, without constraints, demonstrating a public key lookup:

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
#!/bin/sh

echo &quot;ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIKs/UouletvojgB1YeRZ4MY6iRblQ2ERDuNhQO4tOvdL&quot;

exit 0
&lt;/syntaxhighlight&gt;

For authentication to succeed, the script must return exit code 0  (success) after sending the syntactically correct matching public key to '''stdout'''.  For the SSH daemon to even run the script in the first place, the script must have the correct file and directory permissions.

Both the '''AuthorizedKeysCommandUser''' directive and '''AuthorizedKeysCommand''' must be used together.  The former designates which account the script or program use when run.  If set to ''none'' or if it does not refer to a valid account then [http://man.openbsd.org/sshd sshd(8)] will just ignore the command.  If '''AuthorizedKeysCommand''' is set, and '''AuthorizedKeysCommandUser''' is left empty or missing, then [http://man.openbsd.org/sshd sshd(8)] won't even run when invoked.  The error will be:

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
AuthorizedKeysCommand set without AuthorizedKeysCommandUser
&lt;/syntaxhighlight&gt;

The '''AuthorizedKeysFile''' is always tried first when it is present in the server configuration.  The '''AuthorizedKeysCommand''' directive will not even be tried when the authorized keys file can provide a relevant key first.  

====A More Detailed Example Using the AuthorizedKeysCommand Directive====

By default the user name trying to log in is passed to the script when no tokens or arguments are provided.  Whether or how that information is used is up to the script.  The SSH daemon can also pass any combination of the tokens described in the TOKENS section of [http://man.openbsd.org/sshd_config sshd_config(5)] into the program or script being called.  Furthermore, the program or script can even be a front end for a database, such as OpenLDAP, or any similar system, as long as '''stdout''' produces a public key.  

Below is a more detailed example which uses a local script named '''keyfinder''' run with the account '''keys''' to look up the a public key for certain accounts.  First in [http://man.openbsd.org/sshd_config sshd_config(5)] the two directives:

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthorizedKeysCommand /usr/local/sbin/keyfinder %U
AuthorizedKeysCommandUser keys
&lt;/syntaxhighlight&gt;

The script below is only a demonstration and a more complex program can call databases or do advanced lookups or heuristics:  

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
#!/bin/sh

set -e

case $1 in
        &quot;1000&quot;)
                echo &quot;ssh-ed25519 AAAAC3NzaC1lZDIE5AAAAIK89...UT9hz&quot;
                ;;

        &quot;1001&quot;)
                echo &quot;restrict ssh-ed25519 AAAAC3NzaC1lZDI1NTAAIBvGx...Y0zxV&quot;
                ;;

        &quot;1002&quot;)
                echo &quot;command=\&quot;/usr/libexec/sftp-server\&quot; ssh-ed25519 AAAAC3NzaC1lZDI1TE5AIPSyY...cPTg3&quot;
                ;;

        *)
                exit 1
                ;;
   
esac

exit 0
&lt;/syntaxhighlight&gt;

The '''AuthorizedKeysCommand''' scripts or programs can return any correctly formatted public key to '''stdout''' for consideration in the authentication process.  That includes adding constraints to the keys.  Above, the account with the UID 1000 has no constraints, while the account with UID 1001 is quite constrained.  Finally, the account with the UID 1002 can only access the SFTP service.  See the section &quot;AUTHORIZED_KEYS FILE FORMAT&quot; in [http://man.openbsd.org/sshd sshd(8)] for the full set of possibilities.

===Key-based Authentication Using an Agent===

When an authentication agent, such as [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)], is going to be used, it should generally be started at the beginning of a session and used to launch the login session or X-session so that the environment variables pointing to the agent and its UNIX-domain socket are passed to each subsequent shell and process.  Many desktop distros do this automatically upon login or startup.  

Starting an agent entails setting a pair of environment variables:

* SSH_AGENT_PID : the process id of the agent
* SSH_AUTH_SOCK : the filename and full path to the UNIX-domain socket

The various SSH and SFTP clients find these variables automatically and use them to contact the agent and try when authentication is needed.   However, it is mainly SSH_AUTH_SOCK which is ever used.  If the shell or desktop session was launched using [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)], then these variables are already set and available.  If they are not available, then it is necessary to either set the variables manually inside each shell or for each application in order to use the agent or else to point to the agent's socket using the directive '''IdentityAgent''' in the client's configuration file.  

Once an agent is available, a relevant private key needs to be loaded before the agent can be used.  Once in the agent the private key can then be used many times.  Private keys are loaded into an agent with [http://man.openbsd.org/ssh-add.1 ssh-add(1)].
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-add /home/fred/.ssh/mykey_ed25519
Identity added: /home/fred/.ssh/mykey_ed25519 (/home/fred/.ssh/mykey_ed25519)
&lt;/syntaxhighlight&gt;

Keys stay in the agent for as long as it is running unless specified otherwise.  A timeout can be set either with the '''-t''' option when starting the agent itself or when actually loading the key using [http://man.openbsd.org/ssh-add.1 ssh-add(1)].  In either case, the '''-t''' option will set a timeout interval, after which the key will be purged from the agent.
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-add -t 1h30m /home/fred/.ssh/mykey_ed25519
Identity added: /home/fred/.ssh/mykey_ed25519 (/home/fred/.ssh/mykey_ed25519)
Lifetime set to 5400 seconds
&lt;/syntaxhighlight&gt;

The option '''-l''' will list the fingerprints of all of the identities in the agent.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-add -l                                    
256 SHA256:77mfUupj364g1WQ+O8NM1ELj0G1QRx/pHtvzvDvDlOk mykey for task x (ED25519)
3072 SHA256:7unq90B/XjrRbucm/fqTOJu0I1vPygVkN9FgzsJdXbk myotherkey rsa for task y (RSA)
&lt;/syntaxhighlight&gt;

It is also possible to remove individual identities from the agent using '''-d''' which will remove them one at a time if identified by file name, but only if the file name is given and without the file name of the private key to be remove, '''-d''' will fail silently.  Using '''-D''' instead will remove all of them at once without needing to specify any by name.  

By default [http://man.openbsd.org/ssh-add.1 ssh-add(1)] uses the agent connected via the socket named in the environment variable '''SSH_AUTH_SOCK''', if it is set.  Currently, that is its only option.  However, for [http://man.openbsd.org/ssh.1 ssh(1)] an alternative to using the environment variable is the client configuration directive '''IdentityAgent''' which tells the SSH clients which socket to use to communicate with the agent.  If both the environment variable and the configuration directive are available at the same time, then the value in '''IdentityAgent''' takes precedence over what's in the environment variable.  '''IdentityAgent''' can also be set to ''none'' to prevent the connection from trying to use any agent at all.  

The client configuration directive '''AddKeysToAgent''' can also be useful in getting keys into an agent as needed.  When set, it automatically loads a key into a running agent the first time the key is called for if it is not already loaded.  Likewise the '''IdentitiesOnly''' directive can ensure that the relevant key is offered on the first try.  Rather than typing these out whenever the client is run, they can be added to '''~/.ssh/config''' and thereby added automatically for designated host connections.  

====Agent Forwarding====

Agent forwarding is one means of passing through one or more intermediate hosts.  However, the '''-J''' option for '''ProxyJump''' would be a safer option.  See [[OpenSSH/Cookbook/Proxies_and_Jump_Hosts#Jump_Hosts_--_Passing_Through_a_Gateway_or_Two | Passing Through a Gateway or Two]] in the section on jump hosts about that.  With agent forwarding, intermediate machines forward challenges and responses back and forth between the client and the final destination.  This comes with some risks but eliminates the need for using passwords or holding keys on any of these intermediate machines.  

A main advantage of agent forwarding is that the private key itself is not needed on any remote machine, thus hindering unwanted file system access to it. &lt;ref name=&quot;OpenSSH key management, Part 3&quot;&gt;{{cite web | url=http://www.ibm.com/developerworks/library/l-keyc3/ | title=Common threads: OpenSSH key management, Part 3 | author=Daniel Robbins | publisher=IBM | date=2002-02-01 | accessdate=2013-04-27}}&lt;/ref&gt;  Another advantage is that the actual agent to which the user has authenticated does not go anywhere and is thus less susceptible to analysis.  

One risk with agents is that they can be re-used to tailgate in if the permissions allow it.  Keys cannot be copied this way, but authentication is possible when there are incorrect permissions.  Note that disabling agent forwarding does not improve security unless users are also denied shell access, as they can always install their own forwarders.

The risks of agent forwarding can be mitigated by confirming each use of a key by adding the '''-c''' option when adding the key to the agent.  This requires the SSH_ASKPASS variable be set and available to the agent process, but will generate a prompt on the host running the agent upon each use of the key by a remote system.  So if passing through one or more intermediate hosts, it is usually better to instead have the SSH client use stdio forwarding with '''-W''' or '''-J'''.

On the client side agent forwarding is disabled by default and so if it is to be used it must be enabled explicitly.  Put the following line in  [http://man.openbsd.org/ssh_config.5 ssh_config(5)] to enable agent forwarding for a particular server:
&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
        Host gateway.example.org
        ForwardAgent yes
&lt;/syntaxhighlight&gt;

On the server side the default configuration files allow authentication agent forwarding, so to use it, nothing needs to be done there, just on the client side.  However, again, it would be preferable to take a look at '''ProxyJump''' instead.  

=====Old Style, Somewhat Safer SSH Agent Forwarding=====

The best way to pass through one or more intermediate hosts is to use the '''ProxyJump''' option instead of authentication agent forwarding and thereby not risking the exposure of any private keys.  If authentication agent forwarding must be used, then it would be advisable in the interest of following the principle of least privilege to forward an agent containing the minimum necessary number of keys.  There are several ways to solve that.  

In version 8.8 and earlier a partial solution is to make a one-off, ephemeral agent to hold just the one key or keys needed for the task at hand.  Another partial solution would be to set up a user-accessible service at the operating system level and then use [http://man.openbsd.org/ssh_config.5 ssh_config] for the rest.  

Automatically launching an ephemeral agent unique to each session can be done by crafting either a special shell alias or function to launch a single-use agent.  Either the function or the alias can be written to require confirmation for each requested signature.  The following example is a function is inspired by an updated blog post by Vincent Bernat&lt;ref name=&quot;safer-agent-forwarding&quot;&gt;{{cite web |url=https://vincent.bernat.ch/en/blog/2020-safer-ssh-agent-forwarding |title=Safer SSH agent forwarding |author=Vincent Bernat|date=2020-04-05 |accessdate=2020-10-04}}&lt;/ref&gt; on SSH agent forwarding:
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ agentssh() {
        ssh-agent ssh -o AddKeysToAgent=confirm -o ForwardAgent=yes
}
&lt;/syntaxhighlight&gt;

Note the use of [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)].  When invoking that alias, the SSH client will be launched with a unique, ephemeral supporting key agent.  The alias sets up a new agent, including setting the two environment variables, and then sets two client options while calling the client.  This arrangement still checks with [http://man.openbsd.org/ssh_config.5 ssh_config(5)] for other options and settings.  When the SSH session is finished the agent which launched it ends and goes away, thus cleaning up after itself automatically.  

Another way is to rely on the client's configuration file for some of the settings.  Such methods rely mostly on [http://man.openbsd.org/ssh_config.5 ssh_config(5)] but still require an independent method to launch an ephemeral agent because the OpenSSH client is already running by the time it reads the configuration file and is thus not affected by any changes to environment variables caused by the configuration file and it is through the environment variables that contain information about the agent.  However, when the path to the UNIX-domain socket used to communicate with the authentication agent is decided in advance then the '''IdentityAgent''' option can point to it once the one-off agent&lt;ref name=&quot;wikimedia_ssh_agents&quot;&gt;{{cite web |url=https://wikitech.wikimedia.org/wiki/Managing_multiple_SSH_agents#Linux_solutions |title=Managing multiple SSH agents |publisher=Wikimedia|accessdate=2020-04-07}}&lt;/ref&gt; is actually launched.  The following uses a specific agent's pre-defined socket whenever connecting to either of two particular domains:

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host *.wikimedia.org *.wmflabs.org
        User fred
        IdentitiesOnly yes
        IdentityFile %d/.ssh/id_cloud_01
        IdentityAgent /run/user/%i/ssh-cloud-01.socket
        ForwardAgent yes
        AddKeysToAgent yes
&lt;/syntaxhighlight&gt;

The '''%d''' stands for the path to the home directory and the '''%i''' stands for the user id (UID) for the current account.  In some cases the '''%i''' token might also come in handy when setting the '''IdentityAgent''' option inside the configuration file.  Again, be careful when forwarding agents with which keys are in the forwarded agent.  See the section &quot;TOKENS&quot; in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] for more such abbreviations.  

With those configuration settings, the authentication agent must already be up and running and point to the designated socket prior to starting the SSH client for that configuration to work.  Additionally, it should place the socket in a directory which is inaccessible to any other accounts.  [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)] must use the '''-a''' option to name the socket:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-agent -a /run/user/${UID}/ssh-cloud-01.socket
&lt;/syntaxhighlight&gt;

That agent configuration can be launched manually or via a script or service manager.  However, in the interests of privacy and security in general, agent forwarding is to be avoided.  The configuration directive '''ProxyJump''' is the best alternative and, on older systems, host traversal using '''ProxyCommand''' with [http://man.openbsd.org/nc.1 netcat] are preferable.  Again, see the section on [[OpenSSH/Cookbook/Proxies and Jump Hosts|Proxies and Jump Hosts]] for how those methods are used.

=====New Style SSH Agent Destination Constraints=====

From 8.9 onward, [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)] will allow the agent to limit which hosts they will use for authentication as specified by [http://man.openbsd.org/ssh-add.1 ssh-add(1)] using the '''-h''' option.  These constraints have been added through two agent protocol extensions and a modification to the public key authentication protocol.  This feature may evolve, but for now the result is such that keys for account authentication can be loaded into the agent in four ways:

* no limits on forwarding (not recommended)
* local use only, these will not get forwarded
* forwarding, but only to specific remote hosts
* forwarding to specific remote hosts via specified routes

The intent is that the restrictions fail safely so that they do not allow authentication when one or more hosts in the route lack the needed protocol features.  The destinations and routes cannot be modified once the keys are loaded, but multiple routes to the same destination can be loaded and the routes can be any number of hops.  If the routes need changing, then the key must be reloaded into the agent with the new route or routes.  

The general default for the client is to keep keys in the agent for local use only.  However, that can be enforced explicitly by adding the '''-a''' option when starting the client or else setting the '''ForwardAgent''' directive in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] to 'no' in the relevant configuration block.  

In order to load keys for unlimited forwarding, which is not the best idea, just add them using [http://man.openbsd.org/ssh-add.1 ssh-add(1)] as normal.  Then use the '''-A''' option with the client or set the '''ForwardAgent''' directive in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] to 'yes' in the relevant configuration block.  

In order to limit keys for connection only to a specific remote host, or to load keys for connection to a specific remote host with forwarding via one or more intermediate hosts, use the '''-h''' option when loading keys into the agent.  Here the one key may be used only to connect to the specific destination:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-agent -h server.example.org server.key.ed25519
&lt;/syntaxhighlight&gt;

If an intermediate system is passed through, the best way is to use '''ProxyJump''' which is the '''-J''' option for the SSH Client.  If agent forwarding must be allowed then the tightest way is to constrain which systems may use the keys, again using the '''-h''' option.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-agent -h middle.example.org -h &quot;middle.example.org&gt;server.example.org&quot; server.key.ed25519
&lt;/syntaxhighlight&gt;

Multiple steps can be included, even multiple routes.  They just have to be enumerated explicitly, though patterns may still be used for the destination hosts as well as specific names.  Each host in the chain must support these protocol extensions for the connection to complete.  

Any keys designated for forwarding are unusable for authentication on any other hosts than those which have been explicitly identified for forwarding.  These permitted hosts are identified by host key or host certificate from the '''known_hosts''' file or another file designated by the '''-H''' option when loading the key with [http://man.openbsd.org/ssh-add.1 ssh-add(1)].  If '''-H''' is not used at the time the keys are loaded into the agent, then the default known hosts file(s) will be used: '''~/.ssh/known_hosts''', '''/etc/ssh/ssh_known_hosts''', '''~/.ssh/known_hosts2''', and '''/etc/ssh/ssh_known_hosts2'''.

In the case of keys, the '''known_hosts''' list must be maintained conscientiously &lt;ref name=&quot;ssh-agent-restrictions&quot;&gt;{{ cite web | author=Damien Miller|url=https://www.openssh.org/agent-restrict.html | title=SSH agent restriction | publisher=OpenSSH | date=2021-12-16|accessdate=2022-03-06}}&lt;/ref&gt;, perhaps with the help of the '''UpdateHostkeys''' and '''CanonicalizeHostname''' client configuration directives.  Use of certificates requires the agent to only need to be aware of the Certificate Authority (CA).

Again, see [[OpenSSH/Cookbook/Proxies_and_Jump_Hosts#Jump_Hosts_--_Passing_Through_a_Gateway_or_Two | Passing Through a Gateway or Two]] in the section on jump hosts about a way to pass through one or more intermediate machines without needing to forward an SSH agent.

====Checking the Agent for Specific Keys====

The [http://man.openbsd.org/ssh_add ssh_add(1)] utility's '''-T''' option can test whether a specific private key is available in the agent or not by looking up the matching public key.  That can be useful in a shell script.

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
#!/bin/sh

key=/home/fred/.ssh/some.key.ed25519.pub

if ssh-add -T ${key}; then
        echo &quot;Key ${key} Found&quot;
else
        echo &quot;Key ${key} missing&quot;
fi
&lt;/syntaxhighlight&gt;

Or it could be done with an alternate syntax just as well either in a script or in an interactive shell sessions,

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ key=/home/fred/.ssh/some.key.ed25519.pub
$ ssh-add -T ${key} &amp;&amp; echo &quot;Key found&quot; || echo &quot;Key missing&quot;
&lt;/syntaxhighlight&gt;

However, if the desired result would be to add key to the agent then the '''AddKeysToAgent''' client configuration option can ensure that a specific key is added to the SSH agent upon first use during any given login session.  That can be done using '''-o AddKeysToAgent=yes''' as a run-time argument, or by modifying [http://man.openbsd.org/ssh_config ssh_config(5)] as appropriate:

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host www
        HostName www.example.com
        IdentityFile %d/.ssh/www.ed25519
        IdentitiesOnly yes
        AddKeysToAgent yes
&lt;/syntaxhighlight&gt;

With those options in the configuration file, the first time &lt;code&gt;ssh www&lt;/code&gt; is run the specified key will get added to the agent and remain available.

===Key-based Authentication Using A Hardware Security Token===

While stand-alone keys have been around for a long time, it has been possible since version 8.2 to use keys backed by hardware security tokens, such as OnlyKey, Yubikey, or many others, though the FIDO2 protocol.  The Universal 2nd Factor (U2F) authentication is supported directly in OpenSSH through FIDO2 and does not need third party software.  At the moment there are two types of hardware backed keys, ECDSA-SK and Ed25519-SK, but only the latest hardware tokens support the latter.  If the key Ed25519-SK format is not supported by the token's firmware, then the following error message will be presented when attempts to use that key type are made:

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
Key enrollment failed: invalid format
&lt;/syntaxhighlight&gt; 

If supported, either key type can be created with [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  The steps are almost identical to creating normal keys but the token must be available to the system (plugged in) first.  Then if called for, the token's PIN must be entered and the token touched or otherwise activated.  After that, the key creation proceeds as normal.  Mind the key type as specified by the '''-t''' option.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -t ed25519-sk -f /home/fred/.ssh/server.ed25519-sk -C &quot;web server for fred&quot;
Generating public/private ed25519-sk key pair.
You may need to touch your authenticator to authorize key generation.
Enter passphrase (empty for no passphrase): 
Enter same passphrase again: 
Your identification has been saved in /home/fred/.ssh/server.ed25519-sk
Your public key has been saved in /home/fred/.ssh/server.ed25519-sk.pub
The key fingerprint is:
SHA256:41wVVDnKJ9gKr2Sj4CFuYMhcNvYebZ6zq0PWyP4rRDo web server
The key's randomart image is:
+[ED25519-SK 256]-+
|           .o... |
|             .o  |
|           +.. . |
|   = .  . ..= .  |
|+ + * + So.. o   |
|o+.EoO *+oo      |
|.o oBo+++o       |
|  o .=.+.        |
| .   .===        |
+----[SHA256]-----+
&lt;/syntaxhighlight&gt;

Once created, the public and private key files get handled like with any other type of key.  But when authenticating, the hardware token must be present and activated when called for.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -i /home/fred/.ssh/server.ed25519-sk server.example.org
Enter passphrase for key '/home/fred/.ssh/server.ed25519-sk': 
Confirm user presence for key ED25519-SK SHA256:41wVVDnKJ9gKr2Sj4CFuYMhcNvYebZ6zq0PWyP4rRDo
&lt;/syntaxhighlight&gt;

The resulting private key file is not actually the key itself but instead a &quot;key handle&quot; which is used by the hardware security token to derive the real private key on demand at the time it is actually used&lt;ref name=&quot;OpenBSD_tech_U2F_FIDO&quot;&gt;{{cite web |url=https://marc.info/?l=openbsd-tech&amp;m=157376801917387&amp;w=2 |title=OpenSSH U2F/FIDO support in base 
|publisher=OpenBSD-Tech Mailing List | date=2019-11-14
|accessdate=2021-03-24}}&lt;/ref&gt;.  As a result, the hardware-backed private key file is useless without the accompanying hardware token.  This also means that these key files are not portable across hardware tokens, say when having multiple tokens in reserve or as backup, even when used by the same account.  So when multiple hardware tokens are in use, different key pairs must be generated for each token.

====Hardware Security Token Resident Private Key====

It is possible to store the private key within the token itself, but for the moment it cannot be used directly from inside the token and must first be saved as a file.  Also, the key can only be loaded into the FIDO authenticator at the time of creation  using the '''-O resident''' option with [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  Otherwise, the process is the same as above.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -O resident -t ed25519-sk -f /home/fred/.ssh/server.ed25519-sk -C &quot;web server for fred&quot;
. . .
&lt;/syntaxhighlight&gt;

When needed, the resident key can be extracted from the FIDO2 hardware token and saved into a file using the '''-K''' option.  At this stage a passphrase can be added to the file, but no passphrase is kept within the token itself, only an optional PIN protects the key there.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -K
Enter PIN for authenticator: 
Enter passphrase (empty for no passphrase): 
Enter same passphrase again: 
Saved ED25519-SK key to id_ed25519_sk_rk

$ mv -i id_ed25519_sk_rk /home/fred/.ssh/server.ed25519-sk
&lt;/syntaxhighlight&gt;

Since the output file name is fixed, any pre-existing file with that name can get overwritten but there will be a warning first.  However, it is not recommended to keep the key on the hardware token because it provides more protection when kept separately.

==Single-purpose Keys==

Tailored single-purpose keys can eliminate use of remote root logins for many administrative activities.  A  finely tailored '''sudoers''' is needed along with an unprivileged account.  When done right, it gives just enough access to get the job done, following the security principle of Least Privilege.  

Single-purpose keys are accompanied by use of either the '''ForceCommand''' directive in [http://man.openbsd.org/ssh_config.5 sshd_config(5)] or the '''command=&quot;...&quot;''' directive inside the '''authorized_keys''' file.  The method is to generate a new key pair, transfer the public key to '''authorized-keys''' on the remote system, and then prepend the appropriate command or script there to the line with the key.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/usr/local/bin/somescript.sh&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIEcgdzDvSebOEjuegEx4W1I/aA7MM3owHfMr9yg2WH8H
&lt;/syntaxhighlight&gt;

The '''command=&quot;...&quot;''' directive inserted there overrides everything else and ensures that when logging in with just that key only the script '''/usr/local/bin/somescript.sh''' is run.  If it is necessary to pass parameters to the script, have a look at the contents of the '''SSH_ORIGINAL_COMMAND''' environment variable and use it in a case statement.  Do not ever trust the contents of that variable nor use the contents directly, always indirectly.  

Single-purpose keys are useful for allowing only a tunnel and nothing more.  The following key will only echo some text and then exit, unless used non-interactively with the '''-N''' option.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/bin/echo do-not-send-commands&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBzTIWCaILN3tHx5WW+PMVDc7DfPM9xYNY61JgFmBGrA 
&lt;/syntaxhighlight&gt; 

No matter what the user tries while logging in with that key, the session will only echo the given text and then exits.  Using the '''-N''' option disables running the remote program, allowing the connection to stay open, allowing a tunnel. 

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -L 3306:localhost:3306 \
	-i ~/.ssh/tunnel_ed25519 \
	-N \
	-l fred \
	server.example.com
&lt;/syntaxhighlight&gt;

That creates a tunnel and stays connected despite a key configuration which would close an interactive session.  See also the '''-n''' or '''-f''' option for [http://man.openbsd.org/ssh.1 ssh(1)].  

===Single-purpose Keys to Avoid Remote Root Access===

The easy way is to write a short shell script, place it '''/usr/local/bin/''', and then configure '''sudoers''' to allow the otherwise unprivileged account to run just that script and only that script.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
%wheel  ALL=(root:root) NOPASSWD: /usr/sbin/service httpd stop
%wheel  ALL=(root:root) NOPASSWD: /usr/sbin/service httpd start
&lt;/syntaxhighlight&gt;

Then the key calls the script using '''command=&quot;...&quot;''' inside '''authorized_keys'''.  Here the one key starts the web server, the other stops the web server.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/usr/bin/sudo /usr/sbin/service httpd stop&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIEcgdzDvSebOEjuegEx4W1I/aA7MM3owHfMr9yg2WH8H
command=&quot;/usr/bin/sudo /usr/sbin/service httpd start&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMidyqZ6OCvbWqA8Zn+FjhpYE6NoWSxVjFnFUk6MrNZ4
&lt;/syntaxhighlight&gt;

Complicated programs like [http://linux.die.net/man/1/rsync rsync(1)], [http://man.openbsd.org/tar.1 tar(1)], [http://linux.die.net/man/1/mysqldump mysqldump(1)], and so on require an advanced approach when building a single-purpose key.  For them, the '''-v''' option can show exactly what is being passed to the server so that '''sudoers''' can be set up correctly.  That way they can be restricted to only access designated parts of the file system.  For example, here is what &lt;code&gt;ssh -v&lt;/code&gt; shows from one particular usage of [http://linux.die.net/man/1/rsync rsync(1)], note the &quot;Sending command&quot; line:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ rsync -e 'ssh -v' fred@server.example.org:/etc/ ./backup/etc/
. . .
debug1: Sending command: rsync --server --sender -e.LsfxC . /etc/
. . .
&lt;/syntaxhighlight&gt;

That output can then be added to '''sudoers''' so that the key can do only that function.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
%backup ALL=(root:root) NOPASSWD: /usr/bin/rsync --server --sender -e.LsfxC . /etc/
&lt;/syntaxhighlight&gt;

Then to tie it all together, the account &quot;backup&quot; needs a key:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/usr/bin/rsync --server --sender -e.LsfxC . /etc/&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMm0rs4eY8djqBb3dIEgbQ8lmdlxb9IAEuX/qFCTxFgb 
&lt;/syntaxhighlight&gt;

Many of these programs have a '''--dry-run''' or equivalent option.  Remember to use it when figuring out the right settings.

===Read-only Access to Keys===

In some cases it is necessary to prevent accounts from being able to changing their own authentication keys.  However, such situations may be a better case for using certificates.  However, if done with keys it is accomplished by putting the key file in an external directory where the user has read-only access, both to the directory and to the key file.  Then the '''AuthorizedKeysFile''' directive assigns where [http://man.openbsd.org/sshd.8 sshd(8)] looks for the keys and can point to a secured location for the keys instead of the default location.

A good alternate location could be a new directory '''/etc/ssh/authorized_keys''' which could store the selected accounts' key files there.  The change can be made to apply to only a group of accounts by putting the settings under a '''Match''' directive.  The default location for keys on most systems is usually '''~/.ssh/authorized_keys'''.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Match Group sftpusers
	AuthorizedKeysFile /etc/ssh/authorized_keys/%u
&lt;/syntaxhighlight&gt;

Then the permissions there would allow the keys to be read but not written:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ls -dhln /etc/ssh/
drwxr-x--x 3 0 0 4.0K Mar 30 22:16 /etc/ssh/authorized_keys/

$ ls -dhln /etc/ssh/*.pub
-rw-r--r-- 1 0 0 173 Mar 23 13:34 /etc/ssh/fred
-rw-r--r-- 1 0 0  93 Mar 23 13:34 /etc/ssh/user1
-rw-r--r-- 1 0 0 565 Mar 23 13:34 /etc/ssh/user2
. . .
&lt;/syntaxhighlight&gt;

The keys could even be within subdirectories, though the same restrictions apply regarding permissions and ownership.  

For chrooted SFTP, the method is the same to keep the key files out of reach of the accounts:  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Match Group sftpusers
	ChrootDirectory /home
	ForceCommand internal-sftp -d %u
	AuthorizedKeysFile /etc/ssh/authorized_keys/%u
&lt;/syntaxhighlight&gt;

Of course a '''Match''' directive is not essential.  The settings could be made to apply to all accounts by putting the directive in the main part of the server configuration file instead.

==Mark Public Keys as Revoked==

Keys can be revoked.  Keys that have been revoked can be stored in '''/etc/ssh/revoked_keys''', a file specified in [http://man.openbsd.org/ssh_config.5 sshd_config(5)]  using the directive '''RevokedKeys''', so that [http://man.openbsd.org/sshd.8 sshd(8)] will prevent attempts to log in with them.  No warning or error on the client side will be given if a revoked key is tried.  Authentication will simply progress to the next key or method.

The revoked keys file should contain a list of public keys, one per line, that have been revoked and can no longer be used to connect to the server.  The key cannot contain any extras, such as [[OpenSSH/Client_Configuration_Files#Available_key_login_options | login options]] or it will be ignored. If one of the revoked keys is tried during a login attempt, the server will simply ignore it and move on to the next authentication method.  An entry will be made in the logs of the attempt, including the key's fingerprint.  See the section on [[OpenSSH/Logging_and_Troubleshooting | logging]] for a little more on that.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
RevokedKeys /etc/ssh/revoked_keys
&lt;/syntaxhighlight&gt;

The '''RevokedKeys''' configuration directive is not set in [http://man.openbsd.org/ssh_config.5 sshd_config(5)] by default.  It must be set explicitly if it is to be used.  This is another situation that might be better fulfilled through using certificate since a validity interval can be set in any combination of seconds, minutes, hours, days, or weeks can be set for certificates while keys are valid indefinitely.  

===Key Revocation Lists===

A Key Revocation List (KRL) is a compact, binary form of representing revoked keys and certificates.  In order to use a KRL, the server's configuration file must point to a valid list using the '''RevokedKeys''' directive.  KRLs themselves are generated with [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] and can be created from scratch or edited in place.  Here a new one is made, populated with a single public key: 

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -k -f /etc/ssh/revoked_keys -z 1 ~/.ssh/old_key_rsa.pub
&lt;/syntaxhighlight&gt;

Here an existing KRL is updated by adding the '''-u''' option:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -u -k -f /etc/ssh/revoked_keys -z 2 ~/.ssh/old_key_dsa.pub
&lt;/syntaxhighlight&gt;

Once a KRL is in place, it is possible to test if a specific key or certificate is in the revocation list.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -Q -f /etc/ssh/revoked_keys ~/.ssh/old_key_rsa.pub
&lt;/syntaxhighlight&gt;

Only public keys and certificates will be loaded into the KRL.  Corrupt or broken keys will not be loaded and will produce an error message if tried.  Like with the regular '''RevokedKeys''' list, the public key destined for the KRL cannot contain any extras like login options or it will produce an error when an attempt is made to load it into the KRL or search the KRL for it.

==Verify a Host Key by Fingerprint==

The above examples have been about using keys to authenticate the client to the server.  A different context in which keys are used is when the server identifies itself to the client, which happens automatically at the beginning of each non-multiplexed session.  In order for that identification to happen the client acquires a public key from the server, usually on or prior to first contact, which it can subsequently use to ensure that it is connecting to the same server again and not an impostor.  The default locations for storing these acquired host keys on the client are in '''/etc/ssh/ssh_known_hosts''', if managed by the system administrator, or in '''~/.ssh/known_hosts''' if managed by the client's own account.  The format of the contents is a line with a host address and its matching public key.  The file is described in detail in the [http://man.openbsd.org/sshd.8 sshd(8)] manual page in the section &quot;SSH_KNOWN_HOSTS FILE FORMAT&quot;.

When connecting for the first time to a remote host, the server's host key should be verified in order to ensure that the client is connecting to the right machine and not an impostor or anything else.  Usually this verification is done by comparing the fingerprint of the server's host key rather than trying to compare the whole key itself.  By default the client will show the fingerprint if the key is not already found in the '''known_hosts''' register.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -l fred server.example.org
The authenticity of host 'server.example.org (192.0.32.10)' can't be established.
ECDSA key fingerprint is SHA256:LPFiMYrrCYQVsVUPzjOHv+ZjyxCHlVYJMBVFerVCP7k.
Are you sure you want to continue connecting (yes/no)? 
&lt;/syntaxhighlight&gt;

That can be compared to a fingerprint received out of band, say by post, e-mail, SMS, courier, and so on.  Specifically, the example represents the key's fingerprint as a base64 encoded SHA256 checksum.  That is the default style.  The fingerprint can also be displayed as an MD5 hash in hexadecimal instead by passing the client's '''FingerprintHash''' configuration directive as a runtime argument or setting it in [http://man.openbsd.org/ssh_config.5 ssh_config(5)].  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -o FingerprintHash=md5 host.example.org
The authenticity of host 'host.example.org (192.0.32.203)' can't be established.
RSA key fingerprint is MD5:10:4a:ec:d2:f1:38:f7:ea:0a:a0:0f:17:57:ea:a6:16.
Are you sure you want to continue connecting (yes/no)?
&lt;/syntaxhighlight&gt;

But the default in new versions is SHA256 in base64 has a lower chance of collision.

In OpenSSH 6.7 and earlier, the client showed fingerprints as a hexadecimal MD5 checksum instead a of the base64-encoded SHA256 checksum currently used:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -l fred server.example.org
The authenticity of host 'server.example.org (192.0.32.10)' can't be established. 
RSA key fingerprint is 4a:11:ef:d3:f2:48:f8:ea:1a:a2:0d:17:57:ea:a6:16. 
Are you sure you want to continue connecting (yes/no)? 
&lt;/syntaxhighlight&gt;

Another way of comparing keys is to use the ASCII art visual host key.  See further below about that.  

===Downloading keys===

Even though a host’s key is usually displayed for review the first time the SSH client tries to connect, it can also be fetched on demand at any time using [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)]:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan server.example.org
# server.example.org:22 SSH-2.0-OpenSSH_10.6
server.example.org ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBEWKepJgkC2XTG5cAr2Nyew6hOp5AjG7vi2RYFtPWqN3bo5XGuCX2d2YVyn++/2PtyMYBaKWyFpCNTT9X0F1Epg=
# server.example.org:22 SSH-2.0-OpenSSH_10.6
server.example.org ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDKyERe8k+fnsrt4JrcLD3AW0kXj90r9ybrEZuY/CTrXIqYSizO335SxGJoWrKijaRy8htuueMkmNfxxhnBPoAjul/4T/FCRGKaV0jC96xYNnKcXbnXxSLVQ0OW2EIPvQhw/TU/G3vEqtiRYGyaNcZS6xrnVv3xuPuvVC1VRKspNLEq7zfvToC0OB89X5DIbvBbHY13PjJ0NrDdX3sSA8lxPsYagBuDIvyxH0S4Z5fQHeYrdvENS5zX6LwJeMeGSOqDuD0Zb4hpKxhaGVwP5e435VcFuImbFaDPM4w71PzaSUEj+tnUA0mGDoLiCrpW3txkJszog9lN3C/nLGghFaT7ajrfH55qut81JnvdhMju9+SzxrKPJmtQZfKVLIc4whEbtFsPCdm2bstz7ROWxTJ3t/Vr8/QVm2G2aY4FHuPwo2jUQDbQA7mCV+fe1sADy2jLzGhn1TCeYvWSv5PNJAT97IrLfD3+0Uo+qJD/6CU7F8oabj1Ql2H8fPN5kGSWfkM=
# server.example.org:22 SSH-2.0-OpenSSH_10.6
server.example.org ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIJo5gc4VrxVQ5apAOd7qK6UqGlLMpWOPuunjB53JBN2s
# server.example.org:22 SSH-2.0-OpenSSH_10.6
# server.example.org:22 SSH-2.0-OpenSSH_10.6
# server.example.org:22 SSH-2.0-OpenSSH_10.6
server.example.org ssh-mldsa44-ed25519 AAAAE3NzaC1tbGRzYTQ0LWVkMjU1MTkAAAVAyIw5r9FaniSYqBX0yd9vgBz5nCkebaQlMQN9N0p//Ukfn/CnZ3YtZWn6pUGjDM85/bqdL1gqah1OLfnl1eHk0qvTACrym07uKaMLoEHuakIXHbTi/ELPRoRP3F+DpEgjtYSjLc/fJiobRMgSvmLJxTUzZTStsqWAL1L9/1zuwHEngR+THpUcCSTi6KKkYcQiWGOFwpO22VdiuOg+zdQSH+9jW6eXYk1z81KU6UlHZps8zVrlqCd3FDDghgbH5U8DcGN2t6GvVfn6jFjpEk0ouj0of3/7010eRXjnv3QSbprCpMq73lAemQM+3LvTtrMBhFWNhCXhyOHfO1Yq7c8xaOwlFK78PlERjdHTvVJaCaDFDy7Pg9I+wxv+uC+W0wtzJ2S1y9XCYUgJo9yEiIGuSZdhMkYUwMnXLzQMm44hQOW153pdlHWze3kESCLg/LJf9RbUoSB43t6rghSHEiUkIi5TtCtFZ4nAGeH+wVwlB9Fwog5uZuJN1FYuuY5sSrLHJAQDUwudkdak0ifOhtPtsM/ClYr3baolQ/qi0ABYUVLKSV5b+A5DlTXa23zc7JAXm2YVfkWpOfVJG4TY81wrJoDumsd1y3XaH28/4QbADsZCE3wYsBou8ff0xKgPu8xm2K+sYSmzUbBGprArAQA0LtIDGNGqrb4JsZ1ru+viwzfSlxV7Nz7ZrSw6h+Ddq4J9A6oKXy6YS3uf1GFOtBQm6JfuyMHQEEUtYZrU4UK3C/fKHx9vjuw7YdhsL8JRgxbF14qJLFizkmVbK2e6aWEE4iCqLLLlZ0dC2peYUUqyGb9PsW7sewYzGbipzPpQ/GobRT3Obc3Gmu8P386pDGR7hmkOpFmVwIcfc431cUmZixK7CkPxzUvfaAAQkmNs/p4eNNoP0gq/xPGsV14/heULbWp/njGWk1ysjjGxP6YMwHcEZpUdSGbD05zbL0KkMtmKsr8yuJYjdVAgtH2bVAvrxXRXLgavmm97VYYq1A9rOYiQFlMrKRg6yZhT10Xt8Hukf6ySLk+fieFc3nH99YeysoA5rsfp9kdXr65GpwrBerZlf/20ZLJ7s4xaYb9SukR/8tiPt9iAVQjqPdb0MseZVrzhKo/jK44JHbHejHMoMMs7etPAS5TIjHxcJTP66B3eO9A0l2fAage2ka7ehTnHivxD3EE9KnqYBjIHDU7o6dTrX7UyQsdhax9bPKEL7OEtm6hXXfwzy4GdqGi124BclFAF0LeBSvBUgmSKIn3wfzJx/XXbt512eOn3WZk2v0TsiteH9kPEgDxVkUykawg2tleak9rTFMzYpDZRHvZD7uHWUZ8ktr2FEKWgq7/1Q2c80Z6H75VK9l1d3KZuoiWoF1s73R7ZAM+CWSrR+S5h+3AhYubDKPa/af+Lnlqe6ocVTqQPYaaRz25/cLBg6pgbdh18Ru6h3ljG2KiysyXeuoEoM5xVYtdIW7l9NeKDpGbZPAOqywXUpK+UCGjumIl7c48KCTIYcdtolnEbfVNBh0LRuftcVI+uF9cvQ0XacaNbgkYJYCjv4VR/n58EJ1b0c7tQBrVqMjDjIUKGhCMQqAeD3g75jeD60bBmVNPrq8RK+zH5VIa5eaBs3eitN98eVzd4b6UYTQd1QxLQZMrhQf4InRj39TZfGvQR5SXlLZQlweVHYkMps3IKbs3B3DCqlWCPUAnTAJBAG7HqWEYr5uEaKBawBSAx9jCQz00T+bp8KXpkOPzZCD6dfEfpHY6Rv6kmGJkiPUCb2hoX145HrS357G12+wDxKLN833oPVC0z
&lt;/syntaxhighlight&gt;

Once a key is acquired, its fingerprint can be shown using [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] to read from '''stdin'''.  This can be done directly with a pipe.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan server.example.org | ssh-keygen -l -f -
3072 SHA256:tQlw3vy325KrQibndP3gLS/YXUZjTLVA5yDFpg/Bb6I server.example.org (RSA)
256 SHA256:snnAtb/9csdy0BGhPjdg+VNWqN5bxCa/ge4C6zZ8muk server.example.org (ECDSA)
256 SHA256:agRZDZn8awhQ+tc19Ip/whkHoV33Ln2REO7v1kcYbdU server.example.org (ED25519)
512 SHA256:3Wdc6GbLIcc5mbuF2mhhokhARdMLuMK+ESRfJ+sM0QE server.example.org (MLDSA44-ED25519)
&lt;/syntaxhighlight&gt;

If there is more than one public key type is available from the server on the port polled, then [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] will fetch each of them.  If there is more than one key fed via '''stdin''' or a file, then [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] will process them in order.  Prior to OpenSSH 7.2 manual fingerprinting was a two step process, the key was read to a file and then processed for its fingerprint.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan -t ed25519 host.example.org &gt; key.pub
# host.example.org SSH-2.0-OpenSSH_6.8
$ ssh-keygen -lf key.pub                       
256 SHA256:ZmS+IoHh31CmQZ4NJjv3z58Pfa0zMaOgxu8yAcpuwuw host.example.org (ED25519)
&lt;/syntaxhighlight&gt;

Note that some output from [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] is sent to '''stderr''' instead of '''stdout'''.  

A hash, or fingerprint, can be generated manually with [http://linux.die.net/man/1/awk awk(1)], [http://linux.die.net/man/1/sed sed(1)] and [http://linux.die.net/man/1/xxd xxd(1)], on systems where they are found.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ awk '{print $2}' key.pub | base64 -d | md5sum -b | sed 's/../&amp;:/g; s/: .*$//'
$ awk '{print $2}' key.pub | base64 -d | sha256sum -b | sed 's/ .*$//' | xxd -r -p | base64 
&lt;/syntaxhighlight&gt;

It is possible to find all hosts from a file which have new or different keys from those in '''known_hosts''', if the host names are in clear text and not stored as hashes.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan -t ed25519,mldsa44-ed25519 -f ssh_hosts | \
  sort -u - ~/.ssh/known_hosts | \
  diff ~/.ssh/known_hosts -
&lt;/syntaxhighlight&gt;

====Using ssh-keyscan(1) with ssh_config(5)====

The utility [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] does not parse [http://man.openbsd.org/ssh_config.5 ssh_config(5)].  That is in part to keep the code base simple.  There are a lot of configuration options which would be complicated to implement, including but not limited to '''ProxyJump''', '''ProxyCommand''', '''Match''', '''BindInterface''', and '''CanonicalizeHostname'''&lt;ref name=&quot;keyscan&quot;&gt;{{cite mailing list |url=https://lists.mindrot.org/pipermail/openssh-unix-dev/2023-March/040605.html | title=Why does ssh-keyscan not use .ssh/config? |publisher=mindrot.org | access-date=2023-03-01 | date=2023-03-01 | mailing-list=OpenSSH UNIX-dev | first=Damien | last=Miller }}&lt;/ref&gt; .  Resolving host names via the client configuration file can be done by wrapping the utility in a short shell function:

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
my-ssh-keyscan() {
	for host in &quot;$@&quot; ; do
		ssh-keyscan $(ssh -G &quot;$host&quot; | awk '/^hostname/ {print $2}')
	done
}
&lt;/syntaxhighlight&gt;

That shell function uses the '''-G''' option of [http://man.openbsd.org/ssh.1 ssh(1)] to resolve each host name using [http://man.openbsd.org/ssh_config.5 ssh_config(5)] and then check the resulting host name for SSH keys.

===ASCII Art Visual Host Key===

An ASCII art representation of the key can be displayed along with the SHA256 base64 fingerprint: 

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -l -v -f key 
256 SHA256:BClQBFAGuz55+tgHM1aazI8FUo8eJiwmMcqg2U3UgWU www.example.org (ED25519)
+--[ED25519 256]--+
|o+=*++Eo         |
|+o .+.o.         |
|B=.oo.  .        |
|*B.=.o .         |
|= B *   S        |
|. .@ .           |
| +..B            |
|  *. o           |
| o.o.            |
+----[SHA256]-----+
&lt;/syntaxhighlight&gt;

In OpenSSH 6.7 and earlier the fingerprint is in MD5 hexadecimal form.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -l -v -f key 
2048 37:af:05:99:e7:fb:86:6c:98:ee:14:a6:30:06:bc:f0 www.example.net (RSA) 
+--[ RSA 2048]----+ 
|          o      | 
|         o .     | 
|        o o      | 
|       o +       | 
|   .  . S        | 
|    E ..         | 
|  .o.* ..        | 
|  .*=.+o         | 
|  ..==+.         | 
+-----------------+ 
&lt;/syntaxhighlight&gt;

==More on Verifying SSH Keys==

Keys on the client or the server can be verified against known good keys by comparing the base64-encoded SHA256 fingerprints.  

===Verifying Stray Client Keys===

Sometimes is is necessary to compare two uncertain key files to check if they are part of the same key pair.  However, public keys are more or less disposable.  So the easy way in such situations on the client machine is to just rename or erase the old, problematic, public key and replace it with a new one generated from the existing private key.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -y -f ~/.ssh/my_key_ed25519
&lt;/syntaxhighlight&gt;

But if the two parts must really be compared, it is done in two steps using [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  First, a new public key is re-generated from the known private key and used to make a fingerprint to '''stdout'''.  Next, the fingerprint of the unknown public key is generated for comparison.  In this example, the private key '''my_key_a_ed25519''' and the public key '''my_key_b_ed25519.pub''' are compared:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -y -f my_key_a_ed25519 | ssh-keygen -l -f -
$ ssh-keygen -l -f my_key_b_ed25519.pub
&lt;/syntaxhighlight&gt;

The result is a base64-encoded SHA256 checksum for each key with the one fingerprint displayed right below the other for easy visual comparison.  Older versions don't support reading from '''stdin''' so an intermediate file will be needed then.  Even older versions will only show an MD5 checksum for each key.  Either way, automation with a shell script is simple enough to accomplish but outside the scope of this book.

===Verifying Server Keys===

Reliable verification of a server's host key must be done when first connecting.  It can be necessary to contact the system administrator who can provide it out of band so as to know the fingerprint in advance and have it ready to verify the first connection.  

Here is an example of the server's Ed25519 key being read and its fingerprint shown as SHA256 base64:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -l -f /etc/ssh/ssh_host_ed25519_key.pub 
256 SHA256:bFzzouaWmE5HuZIv+YnGUYI2q06i6M43V+6jMU3LHpA root@server.example.org (ED25519)
&lt;/syntaxhighlight&gt;

And here the corresponding ECDSA key is read, but shown as an MD5 hexadecimal hash:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -E md5 -l -f /etc/ssh/ssh_host_ecdsa_key.pub
256 MD5:ed:d2:34:b4:93:fd:0e:eb:08:ee:b3:c4:b3:4f:28:e4 root@server.example.net (ECDSA)
&lt;/syntaxhighlight&gt;

Prior to 6.8, the fingerprint was expressed as an MD5 hexadecimal hash:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -l -f /etc/ssh/ssh_host_rsa_key.pub 
2048 MD5:e4:a0:f4:19:46:d7:a4:cc:be:ea:9b:65:a7:62:db:2c root@server.example.net (RSA)
&lt;/syntaxhighlight&gt;

It is also possible to use [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] to get keys from an active SSH server.  However, the fingerprints still needs to be verified out of band.  

====Warning: Remote Host Identification Has Changed!====

If a server's key does not match what the client finds has been recorded in either the system's or the local account's '''authorized_keys''' files, then the client will issue a warning along with the fingerprint of the suspicious key.  

&lt;pre&gt;
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ED25519 key sent by the remote host is
SHA256:bFzzouaWmE5HuZIv+YnGUYI2q06i6M43V+6jMU3LHpA.
Please contact your system administrator.
Add correct host key in /home/fred/.ssh/known_hosts to get rid of this message.
Offending ED25519 key in /home/fred/.ssh/known_hosts:11
Host key for server.example.org has changed and you have requested strict checking.
Host key verification failed.
&lt;/pre&gt;

Three reasons for the warning are common.  

One reason is that the server's keys were replaced, often because the server's operating system was reinstalled without backing up the old keys.  Another reason can be when the system administrator has phased out deprecated or compromised keys.  However that can be planned better and if there is time to plan the migration, new keys can just be added to the server and have the clients use the '''UpdateHostKeys''' option so that the new keys are accepted if the old keys match.  A third situation is when the connection is made to the wrong machine, such as when the remote system changes IP addresses because of dynamic address allocation.  

In all three cases where the key has changed there is only one thing to do: contact the system administrator and verify the key.   Ask if the OpenSSH-server was recently reinstalled, or was the machine restored from an old backup?  Keep in mind that the system administrator may be you yourself in some cases. 

The case which is rather rare but serious enough that it should be ruled out for sure is that the wrong machine is part of a man-in-the-middle attack.

In all four cases, an authentic key fingerprint can be acquired by any method where it is possible to verify the integrity and origin of the message, for example via PGP-signed e-mail.  If physical access is possible, then use the console to get the right fingerprint.  Once the authentic key fingerprint is available, return to the client machine where you got the error and remove the old key from '''~/.ssh/known_hosts'''

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -R server.example.org
&lt;/syntaxhighlight&gt;

Then try logging in, but compare the key fingerprints first and proceed if and '''only''' if the key fingerprint matches what you received out of band.  If the key fingerprint matches, then go through with the login process and the key will be automatically added.  If the key fingerprint does not match, stop immediately and figure out what you are connecting to.  It would be a good idea to get on the phone, a real phone not a computer phone, to the remote machine's system administrator or the network administrator.

===Multiple Keys for a Host, Multiple Hosts for a Key in known_hosts===
 
Multiple host names or IP addresses can use the same key in the '''known_hosts''' file by using pattern matching or simply by listing multiple systems for the same key.  That can be done in either the global list of keys in '''/etc/ssh/ssh_known_hosts''' and the local, account-specific lists of keys in each account's '''~/.ssh/known_hosts''' file.  Labs, computational clusters, and similar pools of machines can make use of keys in that way.  Here is a key shared by three specific hosts, identified by name, one host per line:
&lt;pre&gt;
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
server2 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
server3 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
&lt;/pre&gt;
Or a range can be specified by using globbing to a limited extent in either '''/etc/ssh/ssh_known_hosts''' or '''~/.ssh/known_hosts'''.
&lt;pre&gt;
172.19.40.* ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
&lt;/pre&gt;
Conversely, a pool of servers might have multiple keys for the same address.  In that case, it is necessary to make multiple entries in either '''/etc/ssh/ssh_known_hosts''' or '''~/.ssh/known_hosts''' for each key.
&lt;pre&gt;
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBrsIIaDl/bJ40vyprvF+HYAq+kE2jWUsOt+WqIheaBw fred@desk.example.org
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIC2CgwWTPH/qZDeHmW7ZUea18wa9As7Txq3P5dXCfoXj fred@desk.example.org 
&lt;/pre&gt;
Thus in order to get a pool of servers to share a pool of keys, each server-key combination must be added manually to the '''known_hosts''' file:
&lt;pre&gt;
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBrsIIaDl/bJ40vyprvF+HYAq+kE2jWUsOt+WqIheaBw fred@desk.example.org
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIC2CgwWTPH/qZDeHmW7ZUea18wa9As7Txq3P5dXCfoXj fred@desk.example.org 

server2 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAICPSs4OR2LT89mv2tM4TKqeVhh4XvoLQ77MSBmjyrMGm fred@desk.example.org
server2 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIHChTzAoJr53A7VP1BdMHqLTFK5cz/2Vc065+VcpP4VA fred@desk.example.org
server2 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIHP+4BvU4DzwYQgznARxx/qyBWmu49PAywHwDRgslRaM fred@desk.example.org
&lt;/pre&gt;

Though upgrading to certificates might be a more appropriate approach that manually updating lots of keys.

===Another way of Dealing with Dynamic (roaming) IP Addresses===
It is possible to manually point to the right key using '''HostKeyAlias''' either as part of [http://man.openbsd.org/ssh_config.5 ssh_config(5)]  or as a runtime parameter.  Here the key for machine ''Foobar'' is used to connect to host 192.168.11.15

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -o StrictHostKeyChecking=accept-new \
      -o HostKeyAlias=foobar   \
      192.168.11.15
&lt;/syntaxhighlight&gt;
This is useful when DHCP is not configured to try to keep the same addresses for the same machines over time or when using certain stdio forwarding methods to pass through intermediate hosts.

===Host Key Update and Rotation in known_hosts===

A protocol extension to rotate weak public keys out of '''known_hosts''' has been in OpenSSH from version 6.8&lt;ref name=&quot;djm_rotation&quot;&gt;
{{cite web
| title=Key rotation in OpenSSH 6.8+ 
| author=Damien Miller
| url=http://blog.djm.net.au/2015/02/key-rotation-in-openssh-68.html
| date=2015-02-01
| publisher=DJM's Personal Weblog
| accessdate=2016-03-05
}}
&lt;/ref&gt; and later.  With it the server is able to inform the client of all its host keys and update '''known_hosts''' with new ones when at least one trusted key already known.  This method still requires the private keys be available to the server &lt;ref name=&quot;djm_rotation_redux&quot;&gt;
{{cite web
| title=Hostkey rotation, redux 
| author=Damien Miller
| url=http://blog.djm.net.au/2015/02/hostkey-rotation-redux.html
| date=2015-02-17
| publisher=DJM's Personal Weblog
| accessdate=2016-03-05
}}
&lt;/ref&gt; so that proofs can be completed.  In [http://man.openbsd.org/ssh_config.5 ssh_config(5)], the directive '''UpdateHostKeys''' specifies whether the client should accept updates of additional host keys from the server after authentication is completed and add them to '''known_hosts'''.  A server can offer multiple keys of the same type for a period before removing the deprecated key from those offered, thus allowing an automated option for rotating keys as well as for upgrading from weaker algorithms to stronger ones.  See also [https://datatracker.ietf.org/doc/html/rfc4819 RFC 4819: Secure Shell Public Key Subsystem] about key management standards.

==Converting Between SSH Key Formats==

OpenSSH has its own format for keys which it uses by default when new keys are made.  However, other SSH clients and servers may use other formats such as [https://www.rfc-editor.org/rfc/rfc4716 RFC 4716], [https://www.rfc-editor.org/rfc/rfc5958 PKCS8], or [https://www.rfc-editor.org/rfc/rfc1421 PEM].  Any of these can be converted to the default OpenSSH format by [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  The default to format to try to convert from is RFC 4716.  The utility [https://linux.die.net/man/1/puttygen puttygen(1)] makes keys in that format for [https://linux.die.net/man/1/putty putty(1)] and they need conversion when used with OpenSSH's server.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -i -f /var/tmp/key_public.ppk
&lt;/syntaxhighlight&gt;

However, you can use the '''-m''' option to specify either that format explicitly or else choose another one to convert from.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -i -m RFC4716 -f /var/tmp/key_public.ppk
$ ssh-keygen -i -m PKCS8 -f /var/tmp/key_public.ppk
&lt;/syntaxhighlight&gt;

Both examples above are for importing public keys into OpenSSH's own format.  

By default OpenSSH will write newly-generated keys in its own format, so the '''-m''' option is obligatory to produce public keys in another format.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -e -m PKCS8 -f ~/.ssh/key.pub
&lt;/syntaxhighlight&gt;

It is not yet possible to export private keys from the OpenSSH format to one of the other formats using the '''-e''' option.  Even if a private key is specified as input, a public key is produced:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -e -m RFC4716 -f ~/.ssh/key
&lt;/syntaxhighlight&gt;

Not all key types are supported by all key formats.  

It is also possible to use export to display the key pair as a traditional hex dump.
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -e -m hexdump -f ~/.ssh/key
Enter passphrase for &quot;key&quot;: 
Public ED25519 key:
buffer len = 51
0000: 00 00 00 0b 73 73 68 2d 65 64 32 35 35 31 39 00  ....ssh-ed25519.
0016: 00 00 20 b0 c5 cc 2c cb d8 8b 8d 75 80 eb e6 e9  .. ...,....u....
0032: 2c f4 36 08 7b 5b ad ad 0b 54 4f 7f 21 9d 1b e8  ,.6.{[...TO.!...
0048: 9e e0 32                                         ..2

Private ED25519 key:
buffer len = 119
0000: 00 00 00 0b 73 73 68 2d 65 64 32 35 35 31 39 00  ....ssh-ed25519.
0016: 00 00 20 b0 c5 cc 2c cb d8 8b 8d 75 80 eb e6 e9  .. ...,....u....
0032: 2c f4 36 08 7b 5b ad ad 0b 54 4f 7f 21 9d 1b e8  ,.6.{[...TO.!...
0048: 9e e0 32 00 00 00 40 e1 c3 a2 4d d9 89 49 72 9b  ..2...@...M..Ir.
0064: 86 72 6c 07 17 1b 40 4f 62 50 62 45 4f 4c cf cf  .rl...@ObPbEOL..
0080: 57 8b 9d c0 04 8f 9b b0 c5 cc 2c cb d8 8b 8d 75  W.........,....u
0096: 80 eb e6 e9 2c f4 36 08 7b 5b ad ad 0b 54 4f 7f  ....,.6.{[...TO.
0112: 21 9d 1b e8 9e e0 32                             !.....2
&lt;/syntaxhighlight&gt;

&lt;noinclude&gt;

== References ==
{{reflist}}
{{OpenSSH/TOC|mini}}
&lt;/noinclude&gt;
{{BookCat}}
{{status|100%}}</text>
      <sha1>gk2u3ndyhu5onggmpqpe26630e4np4c</sha1>
    </revision>
    <revision>
      <id>4676712</id>
      <parentid>4676709</parentid>
      <timestamp>2026-10-18T09:01:23Z</timestamp>
      <contributor>
        <username>Larsnooden</username>
        <id>430753</id>
      </contributor>
      <comment>move subsections, clarify some text</comment>
      <origin>4676712</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="82126" sha1="qou85r6627dpnqyb808xo4sn8vuuz7p" xml:space="preserve">&lt;noinclude&gt;{{simple chapter navigation|previous=File Transfer with SFTP|next=Certificate-based Authentication}}&lt;/noinclude&gt;
&amp;nbsp;

Authentication keys can improve efficiency, if done properly.  As a bonus advantage, the passphrase and private key never leave the client&lt;ref name=&quot;RFC4252§7&quot;&gt;{{cite web |url=https://tools.ietf.org/html/rfc4252#section-7 |title=The Secure Shell (SSH) Authentication Protocol |publisher=IETF |year=2006| accessdate=2015-05-06}}&lt;/ref&gt;.  Key-based authentication is generally recommended for outward facing systems so that password authentication can be turned off.  

==Key-based authentication==

OpenSSH can use public key cryptography for authentication.  In public key cryptography, encryption and decryption are asymmetric.  The keys are used in pairs, a public key to encrypt and a private key to decrypt.  The [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] utility can make RSA, Ed25519, MLDSA44-Ed25519, ECDSA, Ed25519-SK, or ECDSA-SK keys for authenticating.  Even though DSA keys can still be made, being exactly 1024 bits in size, they are no longer recommended and should be avoided.  RSA keys are allowed to vary from 1024 bits on up.  The default is now 3072.  However, there is only limited benefit after 2048 bits and that makes elliptic curve algorithms preferable.  ECDSA can be 256, 384 or 521 bits in size.  Ed25519, Ed25519-SK, and ECDSA-SK keys each have a fixed length of 256 bits.  Shorter keys are faster, but less secure.  Longer keys are much slower to work with but provide better protection, up to a point.  

Keys can be named to help remember what they are for.  Because the key files can be named anything it is possible to have many keys each named for different services or tasks.  The comment field at the end of the public key can also be useful in helping to keep the keys sorted, if you have many of them or use them infrequently.  

The process of key-based authentication uses these keys to make a couple of exchanges using the keys to encrypt and decrypt some short message.  At the start, a copy of the client's public key is stored on the server and the client's private key is on the client, both stay where they are.  The private key never leaves the client.  As the client first contacts the server, the server responds by using the client's public key to encrypt a random number and return that encrypted random number as a challenge to the client.  The client responds to the challenge by using the matching private key to decrypt the message and extract the random number.  The client then makes an MD5 hash of the session ID along with the random number from the challenge and returns that hash to the server.  The server then makes its own hash of the session ID and the random number and compares that to the hash returned by the client.  If there is a match, the login is allowed.  If there is not a match, then the next of any public keys on the server registered as belonging to the same account is tried until either a match is found or all the keys have been tried or the maximum number of failures has been reached. &lt;ref name=&quot;How Key Challenges Work&quot;&gt;{{cite web | url=http://www.unixwiz.net/techtips/ssh-agent-forwarding.html#chal | title=An Illustrated Guide to SSH Agent Forwarding | author=Steve Friedl | date=2006-02-22 | accessdate=2013-04-27 | publisher=Unixwiz.net }}&lt;/ref&gt;

When an agent is used on the client side to manage authentication, the process is similar.  The difference is that [http://man.openbsd.org/ssh.1 ssh(1)] passes the challenge off to the agent which then calculates the response and passes it back to [http://man.openbsd.org/ssh.1 ssh(1)] which then passes the agent's response back to the server.  

===Basics of Public Key Authentication===

A matching pair of SSH keys, one public and one private, is needed for public key authentication.  The [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] utility is used to make such a key pair.  Out of that pair the public key must be properly stored on the remote host before using key-based authentication.  The default location for it is the designated '''authorized_keys''' file, usually one such file resides inside each remote user account.  The private key stays stored safely on the client.  

Once the keys have been prepared and the remote account configured, they can be used for login.  Before starting, there must already be an account on the remote system.  The details of doing that are outside of the scope of this book.  However, once you have a remote account, there are four steps to set up key-based authentication for it:

'''1''') Prepare a directory on the client (say a laptop or a desktop) where the keys will stay, if there isn't one already.  For example, if the '''.ssh''' directory is not on the client machine, create it and set the permissions correctly.  It is important that it not be writable by any account except its owner:
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ mkdir ~/.ssh/
$ chmod 0700 ~/.ssh/
&lt;/syntaxhighlight&gt;

'''2''') Create a key pair inside the designated directory.  The example here creates an Ed25519 key pair in the directory '''~/.ssh'''.  The option '''-t''' decides the key type and the option '''-f''' assigns the key file a name.  It is good to give key files descriptive names, especially if larger numbers of keys are managed.  Below, the public key will be named '''fred_example_org_ed25519.pub''' and the private key will be called '''fred_example_org_ed25519'''.  Lastly, the '''-C''' option is used to embed a descriptive comment inside the private key itself.  The comment is useful for figuring out later what the key is for when one has many keys or a lot of time has passed or both.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -t ed25519 -f ~/.ssh/fred_example_org_ed25519 \
        -C &quot;from fred's laptop to server.example.org&quot;
&lt;/syntaxhighlight&gt;

Be sure to enter a solid passphrase so that the private key gets encrypted using 128-bit AES.  That way the private key can only be read or used when the passphrase is given.  

Ed25519, Ed25519-SK, and ECDSA-SK keys have fixed lengths.  For RSA and ECDSA keys, the '''-b''' option sets the number of bits used for those kinds of keys.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -o -b 4096 -t rsa -f ~/.ssh/fred_example_org_rsa \
        -C &quot;from fred's laptop to server.example.org&quot;
&lt;/syntaxhighlight&gt;

Since 6.5 a new private key format is available using a [http://man.openbsd.org/bcrypt.3 bcrypt(3)] key derivative function (KDF) to better protect keys at rest.  This new format is always used for Ed25519 keys, and sometime in the future will be the default for all keys.  But for right now it may be requested when generating or saving existing keys of other types via the '''-o''' option in [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  

Details of the new format are found in the source code in the file '''PROTOCOL.key'''.

'''3''') Get the keys to the right places.  Transfer only the public key to remote machine.  The following assume the default locations for the authorized keys as specified in the server's configuration file by the '''AuthorizedKeysFile''' directive.  

'''3a''') If the utility &lt;code&gt;ssh-copy-id&lt;/code&gt; exists, and if password authentication is allowed, then it can be used to put the public key into place on the remote system.  The ''.pub'' is optional here, the script will figure it out if omitted. 
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-copy-id -i ~/.ssh/fred_example_org_ed25519 fred@server.example.org
&lt;/syntaxhighlight&gt;

If that script was successful in transferring the public key, then go on to step 4 below and test the key.  If not, then try transferring the public key manually as described in step 3b next.

'''3b''') Or the public key can be put in place manually on the remote machine.  For that the remote '''.ssh''' directory is needed, and within that a special file to store the public keys, the default file name is '''authorized_keys'''.  If either the '''authorized_keys''' file or '''.ssh''' directory do not exist on the remote machine, they need to be created.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ mkdir -m 700 ~/.ssh/
$ touch ~/.ssh/authorized_keys
$ chmod 0600 ~/.ssh/authorized_keys
$ nano -w ~/.ssh/authorized_keys
&lt;/syntaxhighlight&gt;

Then any editor which does not wrap long lines can be used to add the public key.  However the '''authorized_keys''' file is edited to add the key, the key itself must be in the file whole and unbroken on a single  line.  For example, [http://linux.die.net/man/1/nano nano(1)] can be started with the '''-w''' option to prevent wrapping of long lines.  (Another way to set line wrapping permanently in [http://linux.die.net/man/1/nano nano(1)] is by editing [http://linux.die.net/man/5/nanorc nanorc(5)].)  

If the key pair is not already on the client, transfer both the public and private keys there.  It is usually best to keep both the public and private keys together in the directory '''~/.ssh/''', though the public key is not always needed on the client after this step and could even be regenerated if it is ever needed again.  

'''4''') Test the keys

While remaining logged in via the first terminal, use the client system to open another window and in it start another SSH session and try authenticating to the remote machine from the client using the private key.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -i ~/.ssh/fred_example_org_ed25519 -l fred server.example.org
&lt;/syntaxhighlight&gt;

The option '''-i''' tells [http://man.openbsd.org/ssh.1 ssh(1)] which private key to try.  
Only after verifying that the key-based authentication works should you close the original window.  

It is possible to make permanent shortcuts on the client using [http://man.openbsd.org/ssh_config.5 ssh_config(5)], explained further below, once key-based authentication is working.  In particular, see the '''IdentityFile''',  '''IdentitiesOnly''', and '''AddKeysToAgent''' configuration directives, to name three.  

It is also a good idea to turn off password authentication, if and only if key-based authentication is setup for all the necessary remote accounts.  

➥ '''Troubleshooting of Key-based Authentication''':

If the server refuses to accept the key and fails over to the next authentication method (e.g.: &quot;Server refused our key&quot;), then there are several possible mistakes to look for on the server side.  

One of the most common errors is that the file and directory permissions are wrong.  The authorized keys file must be owned by the user in question and not be group writable.  Nor may the key file's directory be group or world writable.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ chmod u=rwx,g=rx,o= ~/.ssh
$ chmod u=rw,g=,o=  ~/.ssh/authorized_keys 
&lt;/syntaxhighlight&gt;

Another mistake that can happen is if the key inside the '''authorized_keys''' file on the remote host is broken by line breaks or has other whitespace in the middle.  That can be fixed by joining up the lines and removing the spaces or by recopying the key more carefully.  

And, though it should go without saying, the halves of the key pair need to match.  The public key on the server needs to match the private key held on the client.  If the public key is lost, then a new one can be generated with the '''-y''' option, but not the other way around.  If the private key is lost, then the public key should be erased as it is no longer of any use.  If many keys are in use for an account, it might be a good idea to add comments to them.  On the client, it can be a good idea to know which server the key is for, either through the file name itself or through the comment field.  A comment can be added using the '''-C''' option.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -t ed25519 -f ~/.ssh/fred_example_org_ed25519 -C &quot;web server mirror&quot;
&lt;/syntaxhighlight&gt;

On the server, it can be important to annotate which client they key is from if there is more than one public key there in an account.  There the comment can be added to the authorized keys file on the server in the last column if a comment does not already exist.  Again, the format of the authorized keys file is given in the manual page for [http://man.openbsd.org/sshd.8 sshd(8)] in the section &quot;AUTHORIZED_KEYS FILE FORMAT&quot;.  If the keys are not labeled they can be hard to match, which might or might not be what you want.  

====Associating Keys Permanently with a Server====

A key can be specified at run time, but to save retyping the same paths again and again, the '''Host''' directive in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] can apply specific settings to a target host.  In this case, by changing '''~/.ssh/config''' it is possible to assign particular keys to be tried automatically whenever making a connection to that specific host.  After adding the following lines to '''~/.ssh/config''', all that's needed is to type &lt;code&gt;ssh ''web1''&lt;/code&gt; to connect with the key for that server.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host web1
	Hostname 198.51.100.32
	IdentitiesOnly yes
	IdentityFile /home/fred/.ssh/web_key_ed25519
&lt;/syntaxhighlight&gt;

The '''~/.ssh/config''' below uses different keys for ''server'' versus ''server.example.org'',  regardless whether they resolve to the same machine.   This is possible because the host name argument given to [http://man.openbsd.org/ssh.1 ssh(1)] is not converted to a canonicalized host name before matching.

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host server
	IdentitiesOnly yes
	IdentityFile /home/fred/.ssh/key_a_ed25519

Host server.example.org
	IdentitiesOnly yes
	IdentityFile /home/fred/.ssh/key_b_ed25519
&lt;/syntaxhighlight&gt;

In this example the shorter name is tried first, but of course less ambiguous shortcuts can be made instead.  The configuration file gets parsed on a first-match basis.  So the most specific rules go at the beginning and the most general rules go at the end.  

====Encrypted Home Directories====

When using encrypted home directories the keys must be stored in an unencrypted directory.  That means somewhere outside the actual home directory which means [http://man.openbsd.org/sshd.8 sshd(8)] needs to be configured appropriately to find the keys in that special location.  

Here is one method for solving the access problem.  Each user is given a subdirectory under '''/etc/ssh/keys/''' which they can then use for storing their '''authorized_keys''' file.  This is set in the server's configuration file '''/etc/ssh/sshd_config'''

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthorizedKeysFile      /etc/ssh/keys/%u/authorized_keys
&lt;/syntaxhighlight&gt;

Setting a special location for the keys opens up more possibilities as to how the keys can be managed and multiple key file locations can be specified if they are separated by whitespace.  The user does not have to have write permissions for the '''authorized_keys''' file.  Only read permission is needed to be able to log in.  But if the user is allowed to add, remove, or change their keys, then they will need write access to the file to do that.  

One symptom of having an encrypted home directory is that key-based authentication only works when you are already logged into the same account, but fails when trying to make the first connection and log in for the first time.

Sometimes it is also necessary to add a script or call a program from '''/etc/ssh/sshrc''' immediately after authentication to decrypt the home directory.

====Passwordless Login====

One solution for passwordless logins is to still have a passphrase and work with an authentication agent in conjunction with a single-purpose key.  Most desktop environments launch an SSH agent automatically these days.  It will be visible in the '''SSH_AUTH_SOCK''' environment variable if it is.  On accounts with an agent, [http://man.openbsd.org/ssh-add.1 ssh-add(1)] can load private keys into an available agent.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-add ~/.ssh/fred_example_org_ed25519
&lt;/syntaxhighlight&gt;

Thereafter, the client will automatically check the agent for the key when appropriate.  If there are many keys in the agent, it will become necessary to set '''IdentitiesOnly'''.  See the above section on using '''~/.ssh/config''' for that.  See [[OpenSSH/Cookbook/Public_Key_Authentication#Key-based_Authentication_Using_an_Agent|Key-based Authentication Using an Agent]] below.  

Another, riskier, way of allowing passwordless logins is to follow the steps above, but simply do not enter a passphrase when asked for one while creating the key.  Note that using keys that lack a passphrase is very risky, so the key files should be very well protected and kept track of, and ideally locked down with a '''command=''' option or '''ForceCommand''' directive on the server.  That includes those keys which will only be used as single-purpose keys as described below.  

Timely key rotation becomes especially important.  In general, it is not a good idea to make a key without a passphrase.

====Requiring Both Keys and a Password====

While users should have strong passphrases for their keys, there is no way to enforce or verify that.  Indeed, since neither the private key nor its the passphrase ever leave the client machine there is nothing that the server can do to have any influence over that.  Instead, it is possible to require both a key and a password.  Starting with OpenSSH 6.2, it is possible for the server to require multiple authentication methods for login using the '''AuthenticationMethods''' directive.   
&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthenticationMethods publickey,password
&lt;/syntaxhighlight&gt;

This example from [http://man.openbsd.org/sshd_config.5 sshd_config(5)] requires that users first authenticate using a key and it only queries for a password if the key succeeds.  Thus with that configuration it is not possible to get to the system password prompt without first authenticating with a valid key.  Changing the order of the arguments changes the order of the authentication methods.

====Requiring Two or More Keys====

Since OpenSSH 6.8, the server now remembers which public keys have been used for authentication and refuses to accept previously-used keys.  This allows a set up requiring that users authenticate using two different public keys, maybe one in the file system and the other in a hardware token. 

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthenticationMethods publickey,publickey
&lt;/syntaxhighlight&gt;

The '''AuthenticationMethods''' directive, whether for keys or passwords, can also be set on the server under a '''Match''' directive to apply only to certain groups or situations.

====Requiring Certain Key Types For Authentication====

Also since OpenSSH 6.8, the '''PubkeyAcceptedKeyTypes''' directive, later changed to '''PubkeyAcceptedAlgorithms''', can specify which key algorithms are accepted for authentication.  Those not in the comma-separated pattern list are not allowed.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
PubkeyAcceptedAlgorithms ssh-ed25519*,ssh-rsa*,ecdsa-sha2*,sk-ssh-ed25519*,sk-ecdsa-sha2*
&lt;/syntaxhighlight&gt;

Either the actual key types or a pattern can be in the list.  Spaces are not allowed in the pattern list.  The exact list of key types supported for authentication can be found by the '''-Q''' option using the client.  The following two lines are equivalent.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -Q key-sig | sort

$ ssh -Q PubkeyAcceptedAlgorithms | sort
&lt;/syntaxhighlight&gt;

For host-based authentication, it is the '''HostbasedAcceptedAlgorithms''' directive which determines the key types which are allowed for authentication.

===Key-based Authentication Using the AuthorizedKeysCommand Directive===

It is possible to use a program or script to look up public keys rather than keeping them in a static file or files.  Any command called by the '''AuthorizedKeysCommand''' directive needs to either produce a syntactically correct public key while returning the exit code for a successful run or else return the exit code for failure.  The string sent to '''stdout''' will then be processed as part of the authentication work flow.  

Here is a shell script&lt;ref name=&quot;janpietmens&quot;&gt;{{cite web |url=https://jpmens.net/2025/03/25/authorizedkeyscommand-in-sshd/ |title=SSH keys from a command: sshd's AuthorizedKeysCommand directive |accessdate=2025-04-04 |date=2025-03-25 | author=Jan-Piet Mens }}&lt;/ref&gt; at its simplest, without constraints, demonstrating a public key lookup:

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
#!/bin/sh

echo &quot;ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIKs/UouletvojgB1YeRZ4MY6iRblQ2ERDuNhQO4tOvdL&quot;

exit 0
&lt;/syntaxhighlight&gt;

For authentication to succeed, the script must return exit code 0  (success) after sending the syntactically correct matching public key to '''stdout'''.  For the SSH daemon to even run the script in the first place, the script must have the correct file and directory permissions.

Both the '''AuthorizedKeysCommandUser''' directive and '''AuthorizedKeysCommand''' must be used together.  The former designates which account the script or program use when run.  If set to ''none'' or if it does not refer to a valid account then [http://man.openbsd.org/sshd sshd(8)] will just ignore the command.  If '''AuthorizedKeysCommand''' is set, and '''AuthorizedKeysCommandUser''' is left empty or missing, then [http://man.openbsd.org/sshd sshd(8)] won't even run when invoked.  The error will be:

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
AuthorizedKeysCommand set without AuthorizedKeysCommandUser
&lt;/syntaxhighlight&gt;

The '''AuthorizedKeysFile''' is always tried first when it is present in the server configuration.  The '''AuthorizedKeysCommand''' directive will not even be tried when the authorized keys file can provide a relevant key first.  

====A More Detailed Example Using the AuthorizedKeysCommand Directive====

By default the user name trying to log in is passed to the script when no tokens or arguments are provided.  Whether or how that information is used is up to the script.  The SSH daemon can also pass any combination of the tokens described in the TOKENS section of [http://man.openbsd.org/sshd_config sshd_config(5)] into the program or script being called.  Furthermore, the program or script can even be a front end for a database, such as OpenLDAP, or any similar system, as long as '''stdout''' produces a public key.  

Below is a more detailed example which uses a local script named '''keyfinder''' run with the account '''keys''' to look up the a public key for certain accounts.  First in [http://man.openbsd.org/sshd_config sshd_config(5)] the two directives:

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthorizedKeysCommand /usr/local/sbin/keyfinder %U
AuthorizedKeysCommandUser keys
&lt;/syntaxhighlight&gt;

The script below is only a demonstration and a more complex program can call databases or do advanced lookups or heuristics:  

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
#!/bin/sh

set -e

case $1 in
        &quot;1000&quot;)
                echo &quot;ssh-ed25519 AAAAC3NzaC1lZDIE5AAAAIK89...UT9hz&quot;
                ;;

        &quot;1001&quot;)
                echo &quot;restrict ssh-ed25519 AAAAC3NzaC1lZDI1NTAAIBvGx...Y0zxV&quot;
                ;;

        &quot;1002&quot;)
                echo &quot;command=\&quot;/usr/libexec/sftp-server\&quot; ssh-ed25519 AAAAC3NzaC1lZDI1TE5AIPSyY...cPTg3&quot;
                ;;

        *)
                exit 1
                ;;
   
esac

exit 0
&lt;/syntaxhighlight&gt;

The '''AuthorizedKeysCommand''' scripts or programs can return any correctly formatted public key to '''stdout''' for consideration in the authentication process.  That includes adding constraints to the keys.  Above, the account with the UID 1000 has no constraints, while the account with UID 1001 is quite constrained.  Finally, the account with the UID 1002 can only access the SFTP service.  See the section &quot;AUTHORIZED_KEYS FILE FORMAT&quot; in [http://man.openbsd.org/sshd sshd(8)] for the full set of possibilities.

===Key-based Authentication Using an Agent===

When an authentication agent, such as [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)], is going to be used, it should generally be started at the beginning of a session and used to launch the login session or X-session so that the environment variables pointing to the agent and its UNIX-domain socket are passed to each subsequent shell and process.  Many desktop distros do this automatically upon login or startup.  

Starting an agent entails setting a pair of environment variables:

* SSH_AGENT_PID : the process id of the agent
* SSH_AUTH_SOCK : the filename and full path to the UNIX-domain socket

The various SSH and SFTP clients find these variables automatically and use them to contact the agent and try when authentication is needed.   However, it is mainly SSH_AUTH_SOCK which is ever used.  If the shell or desktop session was launched using [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)], then these variables are already set and available.  If they are not available, then it is necessary to either set the variables manually inside each shell or for each application in order to use the agent or else to point to the agent's socket using the directive '''IdentityAgent''' in the client's configuration file.  

Once an agent is available, a relevant private key needs to be loaded before the agent can be used.  Once in the agent the private key can then be used many times.  Private keys are loaded into an agent with [http://man.openbsd.org/ssh-add.1 ssh-add(1)].
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-add /home/fred/.ssh/mykey_ed25519
Identity added: /home/fred/.ssh/mykey_ed25519 (/home/fred/.ssh/mykey_ed25519)
&lt;/syntaxhighlight&gt;

Keys stay in the agent for as long as it is running unless specified otherwise.  A timeout can be set either with the '''-t''' option when starting the agent itself or when actually loading the key using [http://man.openbsd.org/ssh-add.1 ssh-add(1)].  In either case, the '''-t''' option will set a timeout interval, after which the key will be purged from the agent.
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-add -t 1h30m /home/fred/.ssh/mykey_ed25519
Identity added: /home/fred/.ssh/mykey_ed25519 (/home/fred/.ssh/mykey_ed25519)
Lifetime set to 5400 seconds
&lt;/syntaxhighlight&gt;

The option '''-l''' will list the fingerprints of all of the identities in the agent.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-add -l                                    
256 SHA256:77mfUupj364g1WQ+O8NM1ELj0G1QRx/pHtvzvDvDlOk mykey for task x (ED25519)
3072 SHA256:7unq90B/XjrRbucm/fqTOJu0I1vPygVkN9FgzsJdXbk myotherkey rsa for task y (RSA)
&lt;/syntaxhighlight&gt;

It is also possible to remove individual identities from the agent using '''-d''' which will remove them one at a time if identified by file name, but only if the file name is given and without the file name of the private key to be remove, '''-d''' will fail silently.  Using '''-D''' instead will remove all of them at once without needing to specify any by name.  

By default [http://man.openbsd.org/ssh-add.1 ssh-add(1)] uses the agent connected via the socket named in the environment variable '''SSH_AUTH_SOCK''', if it is set.  Currently, that is its only option.  However, for [http://man.openbsd.org/ssh.1 ssh(1)] an alternative to using the environment variable is the client configuration directive '''IdentityAgent''' which tells the SSH clients which socket to use to communicate with the agent.  If both the environment variable and the configuration directive are available at the same time, then the value in '''IdentityAgent''' takes precedence over what's in the environment variable.  '''IdentityAgent''' can also be set to ''none'' to prevent the connection from trying to use any agent at all.  

The client configuration directive '''AddKeysToAgent''' can also be useful in getting keys into an agent as needed.  When set, it automatically loads a key into a running agent the first time the key is called for if it is not already loaded.  Likewise the '''IdentitiesOnly''' directive can ensure that the relevant key is offered on the first try.  Rather than typing these out whenever the client is run, they can be added to '''~/.ssh/config''' and thereby added automatically for designated host connections.  

====Agent Forwarding====

Agent forwarding is one means of passing through one or more intermediate hosts.  However, the '''-J''' option for '''ProxyJump''' would be a safer option.  See [[OpenSSH/Cookbook/Proxies_and_Jump_Hosts#Jump_Hosts_--_Passing_Through_a_Gateway_or_Two | Passing Through a Gateway or Two]] in the section on jump hosts about that.  With agent forwarding, intermediate machines forward challenges and responses back and forth between the client and the final destination.  This comes with some risks but eliminates the need for using passwords or holding keys on any of these intermediate machines.  

A main advantage of agent forwarding is that the private key itself is not needed on any remote machine, thus hindering unwanted file system access to it. &lt;ref name=&quot;OpenSSH key management, Part 3&quot;&gt;{{cite web | url=http://www.ibm.com/developerworks/library/l-keyc3/ | title=Common threads: OpenSSH key management, Part 3 | author=Daniel Robbins | publisher=IBM | date=2002-02-01 | accessdate=2013-04-27}}&lt;/ref&gt;  Another advantage is that the actual agent to which the user has authenticated does not go anywhere and is thus less susceptible to analysis.  

One risk with agents is that they can be re-used to tailgate in if the permissions allow it.  Keys cannot be copied this way, but authentication is possible when there are incorrect permissions.  Note that disabling agent forwarding does not improve security unless users are also denied shell access, as they can always install their own forwarders.

The risks of agent forwarding can be mitigated by confirming each use of a key by adding the '''-c''' option when adding the key to the agent.  This requires the SSH_ASKPASS variable be set and available to the agent process, but will generate a prompt on the host running the agent upon each use of the key by a remote system.  So if passing through one or more intermediate hosts, it is usually better to instead have the SSH client use stdio forwarding with '''-W''' or '''-J'''.

On the client side agent forwarding is disabled by default and so if it is to be used it must be enabled explicitly.  Put the following line in  [http://man.openbsd.org/ssh_config.5 ssh_config(5)] to enable agent forwarding for a particular server:
&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
        Host gateway.example.org
        ForwardAgent yes
&lt;/syntaxhighlight&gt;

On the server side the default configuration files allow authentication agent forwarding, so to use it, nothing needs to be done there, just on the client side.  However, again, it would be preferable to take a look at '''ProxyJump''' instead.  

=====New Style SSH Agent Destination Constraints=====

Using the '''ProxyJump''' option instead of authentication agent forwarding is still the best way to pass through other systems while avoiding the exposure of private keys, something which could happen fowarding agents.  However, from 8.9 onward, [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)] will allow the agent to limit which hosts it will use for authentication as specified by [http://man.openbsd.org/ssh-add.1 ssh-add(1)] using the '''-h''' option.  These constraints have been added through two agent protocol extensions and a modification to the public key authentication protocol.  This feature may evolve, but for now the result is such that keys for account authentication can be loaded into the agent in four ways:

* no limits on forwarding (not recommended)
* local use only, these will not get forwarded
* forwarding, but only to specific remote hosts
* forwarding to specific remote hosts via specified routes

The intent is that the restrictions fail safely so that they do not allow authentication when one or more hosts in the route lack the needed protocol features.  The destinations and routes cannot be modified once the keys are loaded, but multiple routes to the same destination can be loaded and the routes can be any number of hops.  If the routes need changing, then the key must be reloaded into the agent with the new route or routes.  

The general default for the client is to keep keys in the agent for local use only.  However, that can be enforced explicitly by adding the '''-a''' option when starting the client or else setting the '''ForwardAgent''' directive in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] to 'no' in the relevant configuration block.  

In order to load keys for unlimited forwarding, which is not the best idea, just add them using [http://man.openbsd.org/ssh-add.1 ssh-add(1)] as normal.  Then use the '''-A''' option with the client or set the '''ForwardAgent''' directive in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] to 'yes' in the relevant configuration block.  

In order to limit keys for connection only to a specific remote host, or to load keys for connection to a specific remote host with forwarding via one or more intermediate hosts, use the '''-h''' option when loading keys into the agent.  Here the one key may be used only to connect to the specific destination:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-agent -h server.example.org server.key.ed25519
&lt;/syntaxhighlight&gt;

If an intermediate system is passed through, the best way is to use '''ProxyJump''' which is the '''-J''' option for the SSH Client.  If agent forwarding must be allowed then the tightest way is to constrain which systems may use the keys, again using the '''-h''' option.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-agent -h middle.example.org -h &quot;middle.example.org&gt;server.example.org&quot; server.key.ed25519
&lt;/syntaxhighlight&gt;

Multiple steps can be included, even multiple routes.  They just have to be enumerated explicitly, though patterns may still be used for the destination hosts as well as specific names.  Each host in the chain must support these protocol extensions for the connection to complete.  

Any keys designated for forwarding are unusable for authentication on any other hosts than those which have been explicitly identified for forwarding.  These permitted hosts are identified by host key or host certificate from the '''known_hosts''' file or another file designated by the '''-H''' option when loading the key with [http://man.openbsd.org/ssh-add.1 ssh-add(1)].  If '''-H''' is not used at the time the keys are loaded into the agent, then the default known hosts file(s) will be used: '''~/.ssh/known_hosts''', '''/etc/ssh/ssh_known_hosts''', '''~/.ssh/known_hosts2''', and '''/etc/ssh/ssh_known_hosts2'''.

In the case of keys, the '''known_hosts''' list must be maintained conscientiously &lt;ref name=&quot;ssh-agent-restrictions&quot;&gt;{{ cite web | author=Damien Miller|url=https://www.openssh.org/agent-restrict.html | title=SSH agent restriction | publisher=OpenSSH | date=2021-12-16|accessdate=2022-03-06}}&lt;/ref&gt;, perhaps with the help of the '''UpdateHostkeys''' and '''CanonicalizeHostname''' client configuration directives.  Use of certificates requires the agent to only need to be aware of the Certificate Authority (CA).

Again, see [[OpenSSH/Cookbook/Proxies_and_Jump_Hosts#Jump_Hosts_--_Passing_Through_a_Gateway_or_Two | Passing Through a Gateway or Two]] in the section on jump hosts about a way to pass through one or more intermediate machines without needing to forward an SSH agent.

=====Old Style, Somewhat Safe SSH Agent Forwarding=====

The best way to pass through one or more intermediate hosts is to use the '''ProxyJump''' option instead of authentication agent forwarding and thereby not risking the exposure of any private keys.  If authentication agent forwarding must be used, then it would be advisable in the interest of following the principle of least privilege to forward an agent containing the minimum necessary number of keys.  There are several ways to solve that.  

In version 8.8 and earlier a partial solution is to make a one-off, ephemeral agent to hold just the one key or keys needed for the task at hand.  Another partial solution would be to set up a user-accessible service at the operating system level and then use [http://man.openbsd.org/ssh_config.5 ssh_config] for the rest.  

Automatically launching an ephemeral agent unique to each session can be done by crafting either a special shell alias or function to launch a single-use agent.  Either the function or the alias can be written to require confirmation for each requested signature.  The following example is a function is inspired by an updated blog post by Vincent Bernat&lt;ref name=&quot;safer-agent-forwarding&quot;&gt;{{cite web |url=https://vincent.bernat.ch/en/blog/2020-safer-ssh-agent-forwarding |title=Safer SSH agent forwarding |author=Vincent Bernat|date=2020-04-05 |accessdate=2020-10-04}}&lt;/ref&gt; on SSH agent forwarding:
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ agentssh() {
        ssh-agent ssh -o AddKeysToAgent=confirm -o ForwardAgent=yes
}
&lt;/syntaxhighlight&gt;

Note the use of [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)].  When invoking that alias, the SSH client will be launched with a unique, ephemeral supporting key agent.  The alias sets up a new agent, including setting the two environment variables, and then sets two client options while calling the client.  This arrangement still checks with [http://man.openbsd.org/ssh_config.5 ssh_config(5)] for other options and settings.  When the SSH session is finished the agent which launched it ends and goes away, thus cleaning up after itself automatically.  

Another way is to rely on the client's configuration file for some of the settings.  Such methods rely mostly on [http://man.openbsd.org/ssh_config.5 ssh_config(5)] but still require an independent method to launch an ephemeral agent because the OpenSSH client is already running by the time it reads the configuration file and is thus not affected by any changes to environment variables caused by the configuration file and it is through the environment variables that contain information about the agent.  However, when the path to the UNIX-domain socket used to communicate with the authentication agent is decided in advance then the '''IdentityAgent''' option can point to it once the one-off agent&lt;ref name=&quot;wikimedia_ssh_agents&quot;&gt;{{cite web |url=https://wikitech.wikimedia.org/wiki/Managing_multiple_SSH_agents#Linux_solutions |title=Managing multiple SSH agents |publisher=Wikimedia|accessdate=2020-04-07}}&lt;/ref&gt; is actually launched.  The following uses a specific agent's pre-defined socket whenever connecting to either of two particular domains:

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host *.wikimedia.org *.wmflabs.org
        User fred
        IdentitiesOnly yes
        IdentityFile %d/.ssh/id_cloud_01
        IdentityAgent /run/user/%i/ssh-cloud-01.socket
        ForwardAgent yes
        AddKeysToAgent yes
&lt;/syntaxhighlight&gt;

The '''%d''' stands for the path to the home directory and the '''%i''' stands for the user id (UID) for the current account.  In some cases the '''%i''' token might also come in handy when setting the '''IdentityAgent''' option inside the configuration file.  Again, be careful when forwarding agents with which keys are in the forwarded agent.  See the section &quot;TOKENS&quot; in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] for more such abbreviations.  

With those configuration settings, the authentication agent must already be up and running and point to the designated socket prior to starting the SSH client for that configuration to work.  Additionally, it should place the socket in a directory which is inaccessible to any other accounts.  [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)] must use the '''-a''' option to name the socket:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-agent -a /run/user/${UID}/ssh-cloud-01.socket
&lt;/syntaxhighlight&gt;

That agent configuration can be launched manually or via a script or service manager.  However, in the interests of privacy and security in general, agent forwarding is to be avoided.  The configuration directive '''ProxyJump''' is the best alternative and, on older systems, host traversal using '''ProxyCommand''' with [http://man.openbsd.org/nc.1 netcat] are preferable.  Again, see the section on [[OpenSSH/Cookbook/Proxies and Jump Hosts|Proxies and Jump Hosts]] for how those methods are used.

====Checking the Agent for Specific Keys====

The [http://man.openbsd.org/ssh_add ssh_add(1)] utility's '''-T''' option can test whether a specific private key is available in the agent or not by looking up the matching public key.  That can be useful in a shell script.

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
#!/bin/sh

key=/home/fred/.ssh/some.key.ed25519.pub

if ssh-add -T ${key}; then
        echo &quot;Key ${key} Found&quot;
else
        echo &quot;Key ${key} missing&quot;
fi
&lt;/syntaxhighlight&gt;

Or it could be done with an alternate syntax just as well either in a script or in an interactive shell sessions,

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ key=/home/fred/.ssh/some.key.ed25519.pub
$ ssh-add -T ${key} &amp;&amp; echo &quot;Key found&quot; || echo &quot;Key missing&quot;
&lt;/syntaxhighlight&gt;

However, if the desired result would be to add key to the agent then the '''AddKeysToAgent''' client configuration option can ensure that a specific key is added to the SSH agent upon first use during any given login session.  That can be done using '''-o AddKeysToAgent=yes''' as a run-time argument, or by modifying [http://man.openbsd.org/ssh_config ssh_config(5)] as appropriate:

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host www
        HostName www.example.com
        IdentityFile %d/.ssh/www.ed25519
        IdentitiesOnly yes
        AddKeysToAgent yes
&lt;/syntaxhighlight&gt;

With those options in the configuration file, the first time &lt;code&gt;ssh www&lt;/code&gt; is run the specified key will get added to the agent and remain available.

===Key-based Authentication Using A Hardware Security Token===

While stand-alone keys have been around for a long time, it has been possible since version 8.2 to use keys backed by hardware security tokens, such as OnlyKey, Yubikey, or many others, though the FIDO2 protocol.  The Universal 2nd Factor (U2F) authentication is supported directly in OpenSSH through FIDO2 and does not need third party software.  At the moment there are two types of hardware backed keys, ECDSA-SK and Ed25519-SK, but only the latest hardware tokens support the latter.  If the key Ed25519-SK format is not supported by the token's firmware, then the following error message will be presented when attempts to use that key type are made:

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
Key enrollment failed: invalid format
&lt;/syntaxhighlight&gt; 

If supported, either key type can be created with [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  The steps are almost identical to creating normal keys but the token must be available to the system (plugged in) first.  Then if called for, the token's PIN must be entered and the token touched or otherwise activated.  After that, the key creation proceeds as normal.  Mind the key type as specified by the '''-t''' option.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -t ed25519-sk -f /home/fred/.ssh/server.ed25519-sk -C &quot;web server for fred&quot;
Generating public/private ed25519-sk key pair.
You may need to touch your authenticator to authorize key generation.
Enter passphrase (empty for no passphrase): 
Enter same passphrase again: 
Your identification has been saved in /home/fred/.ssh/server.ed25519-sk
Your public key has been saved in /home/fred/.ssh/server.ed25519-sk.pub
The key fingerprint is:
SHA256:41wVVDnKJ9gKr2Sj4CFuYMhcNvYebZ6zq0PWyP4rRDo web server
The key's randomart image is:
+[ED25519-SK 256]-+
|           .o... |
|             .o  |
|           +.. . |
|   = .  . ..= .  |
|+ + * + So.. o   |
|o+.EoO *+oo      |
|.o oBo+++o       |
|  o .=.+.        |
| .   .===        |
+----[SHA256]-----+
&lt;/syntaxhighlight&gt;

Once created, the public and private key files get handled like with any other type of key.  But when authenticating, the hardware token must be present and activated when called for.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -i /home/fred/.ssh/server.ed25519-sk server.example.org
Enter passphrase for key '/home/fred/.ssh/server.ed25519-sk': 
Confirm user presence for key ED25519-SK SHA256:41wVVDnKJ9gKr2Sj4CFuYMhcNvYebZ6zq0PWyP4rRDo
&lt;/syntaxhighlight&gt;

The resulting private key file is not actually the key itself but instead a &quot;key handle&quot; which is used by the hardware security token to derive the real private key on demand at the time it is actually used&lt;ref name=&quot;OpenBSD_tech_U2F_FIDO&quot;&gt;{{cite web |url=https://marc.info/?l=openbsd-tech&amp;m=157376801917387&amp;w=2 |title=OpenSSH U2F/FIDO support in base 
|publisher=OpenBSD-Tech Mailing List | date=2019-11-14
|accessdate=2021-03-24}}&lt;/ref&gt;.  As a result, the hardware-backed private key file is useless without the accompanying hardware token.  This also means that these key files are not portable across hardware tokens, say when having multiple tokens in reserve or as backup, even when used by the same account.  So when multiple hardware tokens are in use, different key pairs must be generated for each token.

====Hardware Security Token Resident Private Key====

It is possible to store the private key within the token itself, but for the moment it cannot be used directly from inside the token and must first be saved as a file.  Also, the key can only be loaded into the FIDO authenticator at the time of creation  using the '''-O resident''' option with [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  Otherwise, the process is the same as above.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -O resident -t ed25519-sk -f /home/fred/.ssh/server.ed25519-sk -C &quot;web server for fred&quot;
. . .
&lt;/syntaxhighlight&gt;

When needed, the resident key can be extracted from the FIDO2 hardware token and saved into a file using the '''-K''' option.  At this stage a passphrase can be added to the file, but no passphrase is kept within the token itself, only an optional PIN protects the key there.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -K
Enter PIN for authenticator: 
Enter passphrase (empty for no passphrase): 
Enter same passphrase again: 
Saved ED25519-SK key to id_ed25519_sk_rk

$ mv -i id_ed25519_sk_rk /home/fred/.ssh/server.ed25519-sk
&lt;/syntaxhighlight&gt;

Since the output file name is fixed, any pre-existing file with that name can get overwritten but there will be a warning first.  However, it is not recommended to keep the key on the hardware token because it provides more protection when kept separately.

==Single-purpose Keys==

Tailored single-purpose keys can eliminate use of remote root logins for many administrative activities.  A  finely tailored '''sudoers''' is needed along with an unprivileged account.  When done right, it gives just enough access to get the job done, following the security principle of Least Privilege.  

Single-purpose keys are accompanied by use of either the '''ForceCommand''' directive in [http://man.openbsd.org/ssh_config.5 sshd_config(5)] or the '''command=&quot;...&quot;''' directive inside the '''authorized_keys''' file.  The method is to generate a new key pair, transfer the public key to '''authorized-keys''' on the remote system, and then prepend the appropriate command or script there to the line with the key.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/usr/local/bin/somescript.sh&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIEcgdzDvSebOEjuegEx4W1I/aA7MM3owHfMr9yg2WH8H
&lt;/syntaxhighlight&gt;

The '''command=&quot;...&quot;''' directive inserted there overrides everything else and ensures that when logging in with just that key only the script '''/usr/local/bin/somescript.sh''' is run.  If it is necessary to pass parameters to the script, have a look at the contents of the '''SSH_ORIGINAL_COMMAND''' environment variable and use it in a case statement.  Do not ever trust the contents of that variable nor use the contents directly, always indirectly.  

Single-purpose keys are useful for allowing only a tunnel and nothing more.  The following key will only echo some text and then exit, unless used non-interactively with the '''-N''' option.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/bin/echo do-not-send-commands&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBzTIWCaILN3tHx5WW+PMVDc7DfPM9xYNY61JgFmBGrA 
&lt;/syntaxhighlight&gt; 

No matter what the user tries while logging in with that key, the session will only echo the given text and then exits.  Using the '''-N''' option disables running the remote program, allowing the connection to stay open, allowing a tunnel. 

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -L 3306:localhost:3306 \
	-i ~/.ssh/tunnel_ed25519 \
	-N \
	-l fred \
	server.example.com
&lt;/syntaxhighlight&gt;

That creates a tunnel and stays connected despite a key configuration which would close an interactive session.  See also the '''-n''' or '''-f''' option for [http://man.openbsd.org/ssh.1 ssh(1)].  

===Single-purpose Keys to Avoid Remote Root Access===

The easy way is to write a short shell script, place it '''/usr/local/bin/''', and then configure '''sudoers''' to allow the otherwise unprivileged account to run just that script and only that script.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
%wheel  ALL=(root:root) NOPASSWD: /usr/sbin/service httpd stop
%wheel  ALL=(root:root) NOPASSWD: /usr/sbin/service httpd start
&lt;/syntaxhighlight&gt;

Then the key calls the script using '''command=&quot;...&quot;''' inside '''authorized_keys'''.  Here the one key starts the web server, the other stops the web server.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/usr/bin/sudo /usr/sbin/service httpd stop&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIEcgdzDvSebOEjuegEx4W1I/aA7MM3owHfMr9yg2WH8H
command=&quot;/usr/bin/sudo /usr/sbin/service httpd start&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMidyqZ6OCvbWqA8Zn+FjhpYE6NoWSxVjFnFUk6MrNZ4
&lt;/syntaxhighlight&gt;

Complicated programs like [http://linux.die.net/man/1/rsync rsync(1)], [http://man.openbsd.org/tar.1 tar(1)], [http://linux.die.net/man/1/mysqldump mysqldump(1)], and so on require an advanced approach when building a single-purpose key.  For them, the '''-v''' option can show exactly what is being passed to the server so that '''sudoers''' can be set up correctly.  That way they can be restricted to only access designated parts of the file system.  For example, here is what &lt;code&gt;ssh -v&lt;/code&gt; shows from one particular usage of [http://linux.die.net/man/1/rsync rsync(1)], note the &quot;Sending command&quot; line:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ rsync -e 'ssh -v' fred@server.example.org:/etc/ ./backup/etc/
. . .
debug1: Sending command: rsync --server --sender -e.LsfxC . /etc/
. . .
&lt;/syntaxhighlight&gt;

That output can then be added to '''sudoers''' so that the key can do only that function.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
%backup ALL=(root:root) NOPASSWD: /usr/bin/rsync --server --sender -e.LsfxC . /etc/
&lt;/syntaxhighlight&gt;

Then to tie it all together, the account &quot;backup&quot; needs a key:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/usr/bin/rsync --server --sender -e.LsfxC . /etc/&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMm0rs4eY8djqBb3dIEgbQ8lmdlxb9IAEuX/qFCTxFgb 
&lt;/syntaxhighlight&gt;

Many of these programs have a '''--dry-run''' or equivalent option.  Remember to use it when figuring out the right settings.

===Read-only Access to Keys===

In some cases it is necessary to prevent accounts from being able to changing their own authentication keys.  However, such situations may be a better case for using certificates.  However, if done with keys it is accomplished by putting the key file in an external directory where the user has read-only access, both to the directory and to the key file.  Then the '''AuthorizedKeysFile''' directive assigns where [http://man.openbsd.org/sshd.8 sshd(8)] looks for the keys and can point to a secured location for the keys instead of the default location.

A good alternate location could be a new directory '''/etc/ssh/authorized_keys''' which could store the selected accounts' key files there.  The change can be made to apply to only a group of accounts by putting the settings under a '''Match''' directive.  The default location for keys on most systems is usually '''~/.ssh/authorized_keys'''.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Match Group sftpusers
	AuthorizedKeysFile /etc/ssh/authorized_keys/%u
&lt;/syntaxhighlight&gt;

Then the permissions there would allow the keys to be read but not written:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ls -dhln /etc/ssh/
drwxr-x--x 3 0 0 4.0K Mar 30 22:16 /etc/ssh/authorized_keys/

$ ls -dhln /etc/ssh/*.pub
-rw-r--r-- 1 0 0 173 Mar 23 13:34 /etc/ssh/fred
-rw-r--r-- 1 0 0  93 Mar 23 13:34 /etc/ssh/user1
-rw-r--r-- 1 0 0 565 Mar 23 13:34 /etc/ssh/user2
. . .
&lt;/syntaxhighlight&gt;

The keys could even be within subdirectories, though the same restrictions apply regarding permissions and ownership.  

For chrooted SFTP, the method is the same to keep the key files out of reach of the accounts:  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Match Group sftpusers
	ChrootDirectory /home
	ForceCommand internal-sftp -d %u
	AuthorizedKeysFile /etc/ssh/authorized_keys/%u
&lt;/syntaxhighlight&gt;

Of course a '''Match''' directive is not essential.  The settings could be made to apply to all accounts by putting the directive in the main part of the server configuration file instead.

==Mark Public Keys as Revoked==

Keys can be revoked.  Keys that have been revoked can be stored in '''/etc/ssh/revoked_keys''', a file specified in [http://man.openbsd.org/ssh_config.5 sshd_config(5)]  using the directive '''RevokedKeys''', so that [http://man.openbsd.org/sshd.8 sshd(8)] will prevent attempts to log in with them.  No warning or error on the client side will be given if a revoked key is tried.  Authentication will simply progress to the next key or method.

The revoked keys file should contain a list of public keys, one per line, that have been revoked and can no longer be used to connect to the server.  The key cannot contain any extras, such as [[OpenSSH/Client_Configuration_Files#Available_key_login_options | login options]] or it will be ignored. If one of the revoked keys is tried during a login attempt, the server will simply ignore it and move on to the next authentication method.  An entry will be made in the logs of the attempt, including the key's fingerprint.  See the section on [[OpenSSH/Logging_and_Troubleshooting | logging]] for a little more on that.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
RevokedKeys /etc/ssh/revoked_keys
&lt;/syntaxhighlight&gt;

The '''RevokedKeys''' configuration directive is not set in [http://man.openbsd.org/ssh_config.5 sshd_config(5)] by default.  It must be set explicitly if it is to be used.  This is another situation that might be better fulfilled through using certificate since a validity interval can be set in any combination of seconds, minutes, hours, days, or weeks can be set for certificates while keys are valid indefinitely.  

===Key Revocation Lists===

A Key Revocation List (KRL) is a compact, binary form of representing revoked keys and certificates.  In order to use a KRL, the server's configuration file must point to a valid list using the '''RevokedKeys''' directive.  KRLs themselves are generated with [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] and can be created from scratch or edited in place.  Here a new one is made, populated with a single public key: 

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -k -f /etc/ssh/revoked_keys -z 1 ~/.ssh/old_key_rsa.pub
&lt;/syntaxhighlight&gt;

Here an existing KRL is updated by adding the '''-u''' option:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -u -k -f /etc/ssh/revoked_keys -z 2 ~/.ssh/old_key_dsa.pub
&lt;/syntaxhighlight&gt;

Once a KRL is in place, it is possible to test if a specific key or certificate is in the revocation list.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -Q -f /etc/ssh/revoked_keys ~/.ssh/old_key_rsa.pub
&lt;/syntaxhighlight&gt;

Only public keys and certificates will be loaded into the KRL.  Corrupt or broken keys will not be loaded and will produce an error message if tried.  Like with the regular '''RevokedKeys''' list, the public key destined for the KRL cannot contain any extras like login options or it will produce an error when an attempt is made to load it into the KRL or search the KRL for it.

==Verify a Host Key by Fingerprint==

The above examples have been about using keys to authenticate the client to the server.  A different context in which keys are used is when the server identifies itself to the client, which happens automatically at the beginning of each non-multiplexed session.  In order for that identification to happen the client acquires a public key from the server, usually on or prior to first contact, which it can subsequently use to ensure that it is connecting to the same server again and not an impostor.  The default locations for storing these acquired host keys on the client are in '''/etc/ssh/ssh_known_hosts''', if managed by the system administrator, or in '''~/.ssh/known_hosts''' if managed by the client's own account.  The format of the contents is a line with a host address and its matching public key.  The file is described in detail in the [http://man.openbsd.org/sshd.8 sshd(8)] manual page in the section &quot;SSH_KNOWN_HOSTS FILE FORMAT&quot;.

When connecting for the first time to a remote host, the server's host key should be verified in order to ensure that the client is connecting to the right machine and not an impostor or anything else.  Usually this verification is done by comparing the fingerprint of the server's host key rather than trying to compare the whole key itself.  By default the client will show the fingerprint if the key is not already found in the '''known_hosts''' register.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -l fred server.example.org
The authenticity of host 'server.example.org (192.0.32.10)' can't be established.
ECDSA key fingerprint is SHA256:LPFiMYrrCYQVsVUPzjOHv+ZjyxCHlVYJMBVFerVCP7k.
Are you sure you want to continue connecting (yes/no)? 
&lt;/syntaxhighlight&gt;

That can be compared to a fingerprint received out of band, say by post, e-mail, SMS, courier, and so on.  Specifically, the example represents the key's fingerprint as a base64 encoded SHA256 checksum.  That is the default style.  The fingerprint can also be displayed as an MD5 hash in hexadecimal instead by passing the client's '''FingerprintHash''' configuration directive as a runtime argument or setting it in [http://man.openbsd.org/ssh_config.5 ssh_config(5)].  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -o FingerprintHash=md5 host.example.org
The authenticity of host 'host.example.org (192.0.32.203)' can't be established.
RSA key fingerprint is MD5:10:4a:ec:d2:f1:38:f7:ea:0a:a0:0f:17:57:ea:a6:16.
Are you sure you want to continue connecting (yes/no)?
&lt;/syntaxhighlight&gt;

But the default in new versions is SHA256 in base64 has a lower chance of collision.

In OpenSSH 6.7 and earlier, the client showed fingerprints as a hexadecimal MD5 checksum instead a of the base64-encoded SHA256 checksum currently used:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -l fred server.example.org
The authenticity of host 'server.example.org (192.0.32.10)' can't be established. 
RSA key fingerprint is 4a:11:ef:d3:f2:48:f8:ea:1a:a2:0d:17:57:ea:a6:16. 
Are you sure you want to continue connecting (yes/no)? 
&lt;/syntaxhighlight&gt;

Another way of comparing keys is to use the ASCII art visual host key.  See further below about that.  

===Downloading keys===

Even though a host’s key is usually displayed for review the first time the SSH client tries to connect, it can also be fetched on demand at any time using [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)]:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan server.example.org
# server.example.org:22 SSH-2.0-OpenSSH_10.6
server.example.org ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBEWKepJgkC2XTG5cAr2Nyew6hOp5AjG7vi2RYFtPWqN3bo5XGuCX2d2YVyn++/2PtyMYBaKWyFpCNTT9X0F1Epg=
# server.example.org:22 SSH-2.0-OpenSSH_10.6
server.example.org ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDKyERe8k+fnsrt4JrcLD3AW0kXj90r9ybrEZuY/CTrXIqYSizO335SxGJoWrKijaRy8htuueMkmNfxxhnBPoAjul/4T/FCRGKaV0jC96xYNnKcXbnXxSLVQ0OW2EIPvQhw/TU/G3vEqtiRYGyaNcZS6xrnVv3xuPuvVC1VRKspNLEq7zfvToC0OB89X5DIbvBbHY13PjJ0NrDdX3sSA8lxPsYagBuDIvyxH0S4Z5fQHeYrdvENS5zX6LwJeMeGSOqDuD0Zb4hpKxhaGVwP5e435VcFuImbFaDPM4w71PzaSUEj+tnUA0mGDoLiCrpW3txkJszog9lN3C/nLGghFaT7ajrfH55qut81JnvdhMju9+SzxrKPJmtQZfKVLIc4whEbtFsPCdm2bstz7ROWxTJ3t/Vr8/QVm2G2aY4FHuPwo2jUQDbQA7mCV+fe1sADy2jLzGhn1TCeYvWSv5PNJAT97IrLfD3+0Uo+qJD/6CU7F8oabj1Ql2H8fPN5kGSWfkM=
# server.example.org:22 SSH-2.0-OpenSSH_10.6
server.example.org ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIJo5gc4VrxVQ5apAOd7qK6UqGlLMpWOPuunjB53JBN2s
# server.example.org:22 SSH-2.0-OpenSSH_10.6
# server.example.org:22 SSH-2.0-OpenSSH_10.6
# server.example.org:22 SSH-2.0-OpenSSH_10.6
server.example.org ssh-mldsa44-ed25519 AAAAE3NzaC1tbGRzYTQ0LWVkMjU1MTkAAAVAyIw5r9FaniSYqBX0yd9vgBz5nCkebaQlMQN9N0p//Ukfn/CnZ3YtZWn6pUGjDM85/bqdL1gqah1OLfnl1eHk0qvTACrym07uKaMLoEHuakIXHbTi/ELPRoRP3F+DpEgjtYSjLc/fJiobRMgSvmLJxTUzZTStsqWAL1L9/1zuwHEngR+THpUcCSTi6KKkYcQiWGOFwpO22VdiuOg+zdQSH+9jW6eXYk1z81KU6UlHZps8zVrlqCd3FDDghgbH5U8DcGN2t6GvVfn6jFjpEk0ouj0of3/7010eRXjnv3QSbprCpMq73lAemQM+3LvTtrMBhFWNhCXhyOHfO1Yq7c8xaOwlFK78PlERjdHTvVJaCaDFDy7Pg9I+wxv+uC+W0wtzJ2S1y9XCYUgJo9yEiIGuSZdhMkYUwMnXLzQMm44hQOW153pdlHWze3kESCLg/LJf9RbUoSB43t6rghSHEiUkIi5TtCtFZ4nAGeH+wVwlB9Fwog5uZuJN1FYuuY5sSrLHJAQDUwudkdak0ifOhtPtsM/ClYr3baolQ/qi0ABYUVLKSV5b+A5DlTXa23zc7JAXm2YVfkWpOfVJG4TY81wrJoDumsd1y3XaH28/4QbADsZCE3wYsBou8ff0xKgPu8xm2K+sYSmzUbBGprArAQA0LtIDGNGqrb4JsZ1ru+viwzfSlxV7Nz7ZrSw6h+Ddq4J9A6oKXy6YS3uf1GFOtBQm6JfuyMHQEEUtYZrU4UK3C/fKHx9vjuw7YdhsL8JRgxbF14qJLFizkmVbK2e6aWEE4iCqLLLlZ0dC2peYUUqyGb9PsW7sewYzGbipzPpQ/GobRT3Obc3Gmu8P386pDGR7hmkOpFmVwIcfc431cUmZixK7CkPxzUvfaAAQkmNs/p4eNNoP0gq/xPGsV14/heULbWp/njGWk1ysjjGxP6YMwHcEZpUdSGbD05zbL0KkMtmKsr8yuJYjdVAgtH2bVAvrxXRXLgavmm97VYYq1A9rOYiQFlMrKRg6yZhT10Xt8Hukf6ySLk+fieFc3nH99YeysoA5rsfp9kdXr65GpwrBerZlf/20ZLJ7s4xaYb9SukR/8tiPt9iAVQjqPdb0MseZVrzhKo/jK44JHbHejHMoMMs7etPAS5TIjHxcJTP66B3eO9A0l2fAage2ka7ehTnHivxD3EE9KnqYBjIHDU7o6dTrX7UyQsdhax9bPKEL7OEtm6hXXfwzy4GdqGi124BclFAF0LeBSvBUgmSKIn3wfzJx/XXbt512eOn3WZk2v0TsiteH9kPEgDxVkUykawg2tleak9rTFMzYpDZRHvZD7uHWUZ8ktr2FEKWgq7/1Q2c80Z6H75VK9l1d3KZuoiWoF1s73R7ZAM+CWSrR+S5h+3AhYubDKPa/af+Lnlqe6ocVTqQPYaaRz25/cLBg6pgbdh18Ru6h3ljG2KiysyXeuoEoM5xVYtdIW7l9NeKDpGbZPAOqywXUpK+UCGjumIl7c48KCTIYcdtolnEbfVNBh0LRuftcVI+uF9cvQ0XacaNbgkYJYCjv4VR/n58EJ1b0c7tQBrVqMjDjIUKGhCMQqAeD3g75jeD60bBmVNPrq8RK+zH5VIa5eaBs3eitN98eVzd4b6UYTQd1QxLQZMrhQf4InRj39TZfGvQR5SXlLZQlweVHYkMps3IKbs3B3DCqlWCPUAnTAJBAG7HqWEYr5uEaKBawBSAx9jCQz00T+bp8KXpkOPzZCD6dfEfpHY6Rv6kmGJkiPUCb2hoX145HrS357G12+wDxKLN833oPVC0z
&lt;/syntaxhighlight&gt;

Once a key is acquired, its fingerprint can be shown using [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] to read from '''stdin'''.  This can be done directly with a pipe.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan server.example.org | ssh-keygen -l -f -
3072 SHA256:tQlw3vy325KrQibndP3gLS/YXUZjTLVA5yDFpg/Bb6I server.example.org (RSA)
256 SHA256:snnAtb/9csdy0BGhPjdg+VNWqN5bxCa/ge4C6zZ8muk server.example.org (ECDSA)
256 SHA256:agRZDZn8awhQ+tc19Ip/whkHoV33Ln2REO7v1kcYbdU server.example.org (ED25519)
512 SHA256:3Wdc6GbLIcc5mbuF2mhhokhARdMLuMK+ESRfJ+sM0QE server.example.org (MLDSA44-ED25519)
&lt;/syntaxhighlight&gt;

If there is more than one public key type is available from the server on the port polled, then [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] will fetch each of them.  If there is more than one key fed via '''stdin''' or a file, then [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] will process them in order.  Prior to OpenSSH 7.2 manual fingerprinting was a two step process, the key was read to a file and then processed for its fingerprint.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan -t ed25519 host.example.org &gt; key.pub
# host.example.org SSH-2.0-OpenSSH_6.8
$ ssh-keygen -lf key.pub                       
256 SHA256:ZmS+IoHh31CmQZ4NJjv3z58Pfa0zMaOgxu8yAcpuwuw host.example.org (ED25519)
&lt;/syntaxhighlight&gt;

Note that some output from [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] is sent to '''stderr''' instead of '''stdout'''.  

A hash, or fingerprint, can be generated manually with [http://linux.die.net/man/1/awk awk(1)], [http://linux.die.net/man/1/sed sed(1)] and [http://linux.die.net/man/1/xxd xxd(1)], on systems where they are found.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ awk '{print $2}' key.pub | base64 -d | md5sum -b | sed 's/../&amp;:/g; s/: .*$//'
$ awk '{print $2}' key.pub | base64 -d | sha256sum -b | sed 's/ .*$//' | xxd -r -p | base64 
&lt;/syntaxhighlight&gt;

It is possible to find all hosts from a file which have new or different keys from those in '''known_hosts''', if the host names are in clear text and not stored as hashes.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan -t ed25519,mldsa44-ed25519 -f ssh_hosts | \
  sort -u - ~/.ssh/known_hosts | \
  diff ~/.ssh/known_hosts -
&lt;/syntaxhighlight&gt;

====Using ssh-keyscan(1) with ssh_config(5)====

The utility [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] does not parse [http://man.openbsd.org/ssh_config.5 ssh_config(5)].  That is in part to keep the code base simple.  There are a lot of configuration options which would be complicated to implement, including but not limited to '''ProxyJump''', '''ProxyCommand''', '''Match''', '''BindInterface''', and '''CanonicalizeHostname'''&lt;ref name=&quot;keyscan&quot;&gt;{{cite mailing list |url=https://lists.mindrot.org/pipermail/openssh-unix-dev/2023-March/040605.html | title=Why does ssh-keyscan not use .ssh/config? |publisher=mindrot.org | access-date=2023-03-01 | date=2023-03-01 | mailing-list=OpenSSH UNIX-dev | first=Damien | last=Miller }}&lt;/ref&gt; .  Resolving host names via the client configuration file can be done by wrapping the utility in a short shell function:

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
my-ssh-keyscan() {
	for host in &quot;$@&quot; ; do
		ssh-keyscan $(ssh -G &quot;$host&quot; | awk '/^hostname/ {print $2}')
	done
}
&lt;/syntaxhighlight&gt;

That shell function uses the '''-G''' option of [http://man.openbsd.org/ssh.1 ssh(1)] to resolve each host name using [http://man.openbsd.org/ssh_config.5 ssh_config(5)] and then check the resulting host name for SSH keys.

===ASCII Art Visual Host Key===

An ASCII art representation of the key can be displayed along with the SHA256 base64 fingerprint: 

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -l -v -f key 
256 SHA256:BClQBFAGuz55+tgHM1aazI8FUo8eJiwmMcqg2U3UgWU www.example.org (ED25519)
+--[ED25519 256]--+
|o+=*++Eo         |
|+o .+.o.         |
|B=.oo.  .        |
|*B.=.o .         |
|= B *   S        |
|. .@ .           |
| +..B            |
|  *. o           |
| o.o.            |
+----[SHA256]-----+
&lt;/syntaxhighlight&gt;

In OpenSSH 6.7 and earlier the fingerprint is in MD5 hexadecimal form.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -l -v -f key 
2048 37:af:05:99:e7:fb:86:6c:98:ee:14:a6:30:06:bc:f0 www.example.net (RSA) 
+--[ RSA 2048]----+ 
|          o      | 
|         o .     | 
|        o o      | 
|       o +       | 
|   .  . S        | 
|    E ..         | 
|  .o.* ..        | 
|  .*=.+o         | 
|  ..==+.         | 
+-----------------+ 
&lt;/syntaxhighlight&gt;

==More on Verifying SSH Keys==

Keys on the client or the server can be verified against known good keys by comparing the base64-encoded SHA256 fingerprints.  

===Verifying Stray Client Keys===

Sometimes is is necessary to compare two uncertain key files to check if they are part of the same key pair.  However, public keys are more or less disposable.  So the easy way in such situations on the client machine is to just rename or erase the old, problematic, public key and replace it with a new one generated from the existing private key.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -y -f ~/.ssh/my_key_ed25519
&lt;/syntaxhighlight&gt;

But if the two parts must really be compared, it is done in two steps using [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  First, a new public key is re-generated from the known private key and used to make a fingerprint to '''stdout'''.  Next, the fingerprint of the unknown public key is generated for comparison.  In this example, the private key '''my_key_a_ed25519''' and the public key '''my_key_b_ed25519.pub''' are compared:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -y -f my_key_a_ed25519 | ssh-keygen -l -f -
$ ssh-keygen -l -f my_key_b_ed25519.pub
&lt;/syntaxhighlight&gt;

The result is a base64-encoded SHA256 checksum for each key with the one fingerprint displayed right below the other for easy visual comparison.  Older versions don't support reading from '''stdin''' so an intermediate file will be needed then.  Even older versions will only show an MD5 checksum for each key.  Either way, automation with a shell script is simple enough to accomplish but outside the scope of this book.

===Verifying Server Keys===

Reliable verification of a server's host key must be done when first connecting.  It can be necessary to contact the system administrator who can provide it out of band so as to know the fingerprint in advance and have it ready to verify the first connection.  

Here is an example of the server's Ed25519 key being read and its fingerprint shown as SHA256 base64:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -l -f /etc/ssh/ssh_host_ed25519_key.pub 
256 SHA256:bFzzouaWmE5HuZIv+YnGUYI2q06i6M43V+6jMU3LHpA root@server.example.org (ED25519)
&lt;/syntaxhighlight&gt;

And here the corresponding ECDSA key is read, but shown as an MD5 hexadecimal hash:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -E md5 -l -f /etc/ssh/ssh_host_ecdsa_key.pub
256 MD5:ed:d2:34:b4:93:fd:0e:eb:08:ee:b3:c4:b3:4f:28:e4 root@server.example.net (ECDSA)
&lt;/syntaxhighlight&gt;

Prior to 6.8, the fingerprint was expressed as an MD5 hexadecimal hash:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -l -f /etc/ssh/ssh_host_rsa_key.pub 
2048 MD5:e4:a0:f4:19:46:d7:a4:cc:be:ea:9b:65:a7:62:db:2c root@server.example.net (RSA)
&lt;/syntaxhighlight&gt;

It is also possible to use [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] to get keys from an active SSH server.  However, the fingerprints still needs to be verified out of band.  

====Warning: Remote Host Identification Has Changed!====

If a server's key does not match what the client finds has been recorded in either the system's or the local account's '''authorized_keys''' files, then the client will issue a warning along with the fingerprint of the suspicious key.  

&lt;pre&gt;
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ED25519 key sent by the remote host is
SHA256:bFzzouaWmE5HuZIv+YnGUYI2q06i6M43V+6jMU3LHpA.
Please contact your system administrator.
Add correct host key in /home/fred/.ssh/known_hosts to get rid of this message.
Offending ED25519 key in /home/fred/.ssh/known_hosts:11
Host key for server.example.org has changed and you have requested strict checking.
Host key verification failed.
&lt;/pre&gt;

Three reasons for the warning are common.  

One reason is that the server's keys were replaced, often because the server's operating system was reinstalled without backing up the old keys.  Another reason can be when the system administrator has phased out deprecated or compromised keys.  However that can be planned better and if there is time to plan the migration, new keys can just be added to the server and have the clients use the '''UpdateHostKeys''' option so that the new keys are accepted if the old keys match.  A third situation is when the connection is made to the wrong machine, such as when the remote system changes IP addresses because of dynamic address allocation.  

In all three cases where the key has changed there is only one thing to do: contact the system administrator and verify the key.   Ask if the OpenSSH-server was recently reinstalled, or was the machine restored from an old backup?  Keep in mind that the system administrator may be you yourself in some cases. 

The case which is rather rare but serious enough that it should be ruled out for sure is that the wrong machine is part of a man-in-the-middle attack.

In all four cases, an authentic key fingerprint can be acquired by any method where it is possible to verify the integrity and origin of the message, for example via PGP-signed e-mail.  If physical access is possible, then use the console to get the right fingerprint.  Once the authentic key fingerprint is available, return to the client machine where you got the error and remove the old key from '''~/.ssh/known_hosts'''

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -R server.example.org
&lt;/syntaxhighlight&gt;

Then try logging in, but compare the key fingerprints first and proceed if and '''only''' if the key fingerprint matches what you received out of band.  If the key fingerprint matches, then go through with the login process and the key will be automatically added.  If the key fingerprint does not match, stop immediately and figure out what you are connecting to.  It would be a good idea to get on the phone, a real phone not a computer phone, to the remote machine's system administrator or the network administrator.

===Multiple Keys for a Host, Multiple Hosts for a Key in known_hosts===
 
Multiple host names or IP addresses can use the same key in the '''known_hosts''' file by using pattern matching or simply by listing multiple systems for the same key.  That can be done in either the global list of keys in '''/etc/ssh/ssh_known_hosts''' and the local, account-specific lists of keys in each account's '''~/.ssh/known_hosts''' file.  Labs, computational clusters, and similar pools of machines can make use of keys in that way.  Here is a key shared by three specific hosts, identified by name, one host per line:
&lt;pre&gt;
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
server2 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
server3 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
&lt;/pre&gt;
Or a range can be specified by using globbing to a limited extent in either '''/etc/ssh/ssh_known_hosts''' or '''~/.ssh/known_hosts'''.
&lt;pre&gt;
172.19.40.* ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
&lt;/pre&gt;
Conversely, a pool of servers might have multiple keys for the same address.  In that case, it is necessary to make multiple entries in either '''/etc/ssh/ssh_known_hosts''' or '''~/.ssh/known_hosts''' for each key.
&lt;pre&gt;
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBrsIIaDl/bJ40vyprvF+HYAq+kE2jWUsOt+WqIheaBw fred@desk.example.org
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIC2CgwWTPH/qZDeHmW7ZUea18wa9As7Txq3P5dXCfoXj fred@desk.example.org 
&lt;/pre&gt;
Thus in order to get a pool of servers to share a pool of keys, each server-key combination must be added manually to the '''known_hosts''' file:
&lt;pre&gt;
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBrsIIaDl/bJ40vyprvF+HYAq+kE2jWUsOt+WqIheaBw fred@desk.example.org
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIC2CgwWTPH/qZDeHmW7ZUea18wa9As7Txq3P5dXCfoXj fred@desk.example.org 

server2 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAICPSs4OR2LT89mv2tM4TKqeVhh4XvoLQ77MSBmjyrMGm fred@desk.example.org
server2 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIHChTzAoJr53A7VP1BdMHqLTFK5cz/2Vc065+VcpP4VA fred@desk.example.org
server2 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIHP+4BvU4DzwYQgznARxx/qyBWmu49PAywHwDRgslRaM fred@desk.example.org
&lt;/pre&gt;

Though upgrading to certificates might be a more appropriate approach that manually updating lots of keys.

===Another way of Dealing with Dynamic (roaming) IP Addresses===
It is possible to manually point to the right key using '''HostKeyAlias''' either as part of [http://man.openbsd.org/ssh_config.5 ssh_config(5)]  or as a runtime parameter.  Here the key for machine ''Foobar'' is used to connect to host 192.168.11.15

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -o StrictHostKeyChecking=accept-new \
      -o HostKeyAlias=foobar   \
      192.168.11.15
&lt;/syntaxhighlight&gt;
This is useful when DHCP is not configured to try to keep the same addresses for the same machines over time or when using certain stdio forwarding methods to pass through intermediate hosts.

===Host Key Update and Rotation in known_hosts===

A protocol extension to rotate weak public keys out of '''known_hosts''' has been in OpenSSH from version 6.8&lt;ref name=&quot;djm_rotation&quot;&gt;
{{cite web
| title=Key rotation in OpenSSH 6.8+ 
| author=Damien Miller
| url=http://blog.djm.net.au/2015/02/key-rotation-in-openssh-68.html
| date=2015-02-01
| publisher=DJM's Personal Weblog
| accessdate=2016-03-05
}}
&lt;/ref&gt; and later.  With it the server is able to inform the client of all its host keys and update '''known_hosts''' with new ones when at least one trusted key already known.  This method still requires the private keys be available to the server &lt;ref name=&quot;djm_rotation_redux&quot;&gt;
{{cite web
| title=Hostkey rotation, redux 
| author=Damien Miller
| url=http://blog.djm.net.au/2015/02/hostkey-rotation-redux.html
| date=2015-02-17
| publisher=DJM's Personal Weblog
| accessdate=2016-03-05
}}
&lt;/ref&gt; so that proofs can be completed.  In [http://man.openbsd.org/ssh_config.5 ssh_config(5)], the directive '''UpdateHostKeys''' specifies whether the client should accept updates of additional host keys from the server after authentication is completed and add them to '''known_hosts'''.  A server can offer multiple keys of the same type for a period before removing the deprecated key from those offered, thus allowing an automated option for rotating keys as well as for upgrading from weaker algorithms to stronger ones.  See also [https://datatracker.ietf.org/doc/html/rfc4819 RFC 4819: Secure Shell Public Key Subsystem] about key management standards.

==Converting Between SSH Key Formats==

OpenSSH has its own format for keys which it uses by default when new keys are made.  However, other SSH clients and servers may use other formats such as [https://www.rfc-editor.org/rfc/rfc4716 RFC 4716], [https://www.rfc-editor.org/rfc/rfc5958 PKCS8], or [https://www.rfc-editor.org/rfc/rfc1421 PEM].  Any of these can be converted to the default OpenSSH format by [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  The default to format to try to convert from is RFC 4716.  The utility [https://linux.die.net/man/1/puttygen puttygen(1)] makes keys in that format for [https://linux.die.net/man/1/putty putty(1)] and they need conversion when used with OpenSSH's server.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -i -f /var/tmp/key_public.ppk
&lt;/syntaxhighlight&gt;

However, you can use the '''-m''' option to specify either that format explicitly or else choose another one to convert from.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -i -m RFC4716 -f /var/tmp/key_public.ppk
$ ssh-keygen -i -m PKCS8 -f /var/tmp/key_public.ppk
&lt;/syntaxhighlight&gt;

Both examples above are for importing public keys into OpenSSH's own format.  

By default OpenSSH will write newly-generated keys in its own format, so the '''-m''' option is obligatory to produce public keys in another format.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -e -m PKCS8 -f ~/.ssh/key.pub
&lt;/syntaxhighlight&gt;

It is not yet possible to export private keys from the OpenSSH format to one of the other formats using the '''-e''' option.  Even if a private key is specified as input, a public key is produced:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -e -m RFC4716 -f ~/.ssh/key
&lt;/syntaxhighlight&gt;

Not all key types are supported by all key formats.  

It is also possible to use export to display the key pair as a traditional hex dump.
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -e -m hexdump -f ~/.ssh/key
Enter passphrase for &quot;key&quot;: 
Public ED25519 key:
buffer len = 51
0000: 00 00 00 0b 73 73 68 2d 65 64 32 35 35 31 39 00  ....ssh-ed25519.
0016: 00 00 20 b0 c5 cc 2c cb d8 8b 8d 75 80 eb e6 e9  .. ...,....u....
0032: 2c f4 36 08 7b 5b ad ad 0b 54 4f 7f 21 9d 1b e8  ,.6.{[...TO.!...
0048: 9e e0 32                                         ..2

Private ED25519 key:
buffer len = 119
0000: 00 00 00 0b 73 73 68 2d 65 64 32 35 35 31 39 00  ....ssh-ed25519.
0016: 00 00 20 b0 c5 cc 2c cb d8 8b 8d 75 80 eb e6 e9  .. ...,....u....
0032: 2c f4 36 08 7b 5b ad ad 0b 54 4f 7f 21 9d 1b e8  ,.6.{[...TO.!...
0048: 9e e0 32 00 00 00 40 e1 c3 a2 4d d9 89 49 72 9b  ..2...@...M..Ir.
0064: 86 72 6c 07 17 1b 40 4f 62 50 62 45 4f 4c cf cf  .rl...@ObPbEOL..
0080: 57 8b 9d c0 04 8f 9b b0 c5 cc 2c cb d8 8b 8d 75  W.........,....u
0096: 80 eb e6 e9 2c f4 36 08 7b 5b ad ad 0b 54 4f 7f  ....,.6.{[...TO.
0112: 21 9d 1b e8 9e e0 32                             !.....2
&lt;/syntaxhighlight&gt;

&lt;noinclude&gt;

== References ==
{{reflist}}
{{OpenSSH/TOC|mini}}
&lt;/noinclude&gt;
{{BookCat}}
{{status|100%}}</text>
      <sha1>qou85r6627dpnqyb808xo4sn8vuuz7p</sha1>
    </revision>
    <revision>
      <id>4676715</id>
      <parentid>4676712</parentid>
      <timestamp>2026-10-18T09:05:32Z</timestamp>
      <contributor>
        <username>Larsnooden</username>
        <id>430753</id>
      </contributor>
      <minor />
      <comment>typos</comment>
      <origin>4676715</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="82125" sha1="8ziips6fmbs1ioyspx5i7pxpy5u1f08" xml:space="preserve">&lt;noinclude&gt;{{simple chapter navigation|previous=File Transfer with SFTP|next=Certificate-based Authentication}}&lt;/noinclude&gt;
&amp;nbsp;

Authentication keys can improve efficiency, if done properly.  As a bonus advantage, the passphrase and private key never leave the client&lt;ref name=&quot;RFC4252§7&quot;&gt;{{cite web |url=https://tools.ietf.org/html/rfc4252#section-7 |title=The Secure Shell (SSH) Authentication Protocol |publisher=IETF |year=2006| accessdate=2015-05-06}}&lt;/ref&gt;.  Key-based authentication is generally recommended for outward facing systems so that password authentication can be turned off.  

==Key-based authentication==

OpenSSH can use public key cryptography for authentication.  In public key cryptography, encryption and decryption are asymmetric.  The keys are used in pairs, a public key to encrypt and a private key to decrypt.  The [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] utility can make RSA, Ed25519, MLDSA44-Ed25519, ECDSA, Ed25519-SK, or ECDSA-SK keys for authenticating.  Even though DSA keys can still be made, being exactly 1024 bits in size, they are no longer recommended and should be avoided.  RSA keys are allowed to vary from 1024 bits on up.  The default is now 3072.  However, there is only limited benefit after 2048 bits and that makes elliptic curve algorithms preferable.  ECDSA can be 256, 384 or 521 bits in size.  Ed25519, Ed25519-SK, and ECDSA-SK keys each have a fixed length of 256 bits.  Shorter keys are faster, but less secure.  Longer keys are much slower to work with but provide better protection, up to a point.  

Keys can be named to help remember what they are for.  Because the key files can be named anything it is possible to have many keys each named for different services or tasks.  The comment field at the end of the public key can also be useful in helping to keep the keys sorted, if you have many of them or use them infrequently.  

The process of key-based authentication uses these keys to make a couple of exchanges using the keys to encrypt and decrypt some short message.  At the start, a copy of the client's public key is stored on the server and the client's private key is on the client, both stay where they are.  The private key never leaves the client.  As the client first contacts the server, the server responds by using the client's public key to encrypt a random number and return that encrypted random number as a challenge to the client.  The client responds to the challenge by using the matching private key to decrypt the message and extract the random number.  The client then makes an MD5 hash of the session ID along with the random number from the challenge and returns that hash to the server.  The server then makes its own hash of the session ID and the random number and compares that to the hash returned by the client.  If there is a match, the login is allowed.  If there is not a match, then the next of any public keys on the server registered as belonging to the same account is tried until either a match is found or all the keys have been tried or the maximum number of failures has been reached. &lt;ref name=&quot;How Key Challenges Work&quot;&gt;{{cite web | url=http://www.unixwiz.net/techtips/ssh-agent-forwarding.html#chal | title=An Illustrated Guide to SSH Agent Forwarding | author=Steve Friedl | date=2006-02-22 | accessdate=2013-04-27 | publisher=Unixwiz.net }}&lt;/ref&gt;

When an agent is used on the client side to manage authentication, the process is similar.  The difference is that [http://man.openbsd.org/ssh.1 ssh(1)] passes the challenge off to the agent which then calculates the response and passes it back to [http://man.openbsd.org/ssh.1 ssh(1)] which then passes the agent's response back to the server.  

===Basics of Public Key Authentication===

A matching pair of SSH keys, one public and one private, is needed for public key authentication.  The [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] utility is used to make such a key pair.  Out of that pair the public key must be properly stored on the remote host before using key-based authentication.  The default location for it is the designated '''authorized_keys''' file, usually one such file resides inside each remote user account.  The private key stays stored safely on the client.  

Once the keys have been prepared and the remote account configured, they can be used for login.  Before starting, there must already be an account on the remote system.  The details of doing that are outside of the scope of this book.  However, once you have a remote account, there are four steps to set up key-based authentication for it:

'''1''') Prepare a directory on the client (say a laptop or a desktop) where the keys will stay, if there isn't one already.  For example, if the '''.ssh''' directory is not on the client machine, create it and set the permissions correctly.  It is important that it not be writable by any account except its owner:
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ mkdir ~/.ssh/
$ chmod 0700 ~/.ssh/
&lt;/syntaxhighlight&gt;

'''2''') Create a key pair inside the designated directory.  The example here creates an Ed25519 key pair in the directory '''~/.ssh'''.  The option '''-t''' decides the key type and the option '''-f''' assigns the key file a name.  It is good to give key files descriptive names, especially if larger numbers of keys are managed.  Below, the public key will be named '''fred_example_org_ed25519.pub''' and the private key will be called '''fred_example_org_ed25519'''.  Lastly, the '''-C''' option is used to embed a descriptive comment inside the private key itself.  The comment is useful for figuring out later what the key is for when one has many keys or a lot of time has passed or both.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -t ed25519 -f ~/.ssh/fred_example_org_ed25519 \
        -C &quot;from fred's laptop to server.example.org&quot;
&lt;/syntaxhighlight&gt;

Be sure to enter a solid passphrase so that the private key gets encrypted using 128-bit AES.  That way the private key can only be read or used when the passphrase is given.  

Ed25519, Ed25519-SK, and ECDSA-SK keys have fixed lengths.  For RSA and ECDSA keys, the '''-b''' option sets the number of bits used for those kinds of keys.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -o -b 4096 -t rsa -f ~/.ssh/fred_example_org_rsa \
        -C &quot;from fred's laptop to server.example.org&quot;
&lt;/syntaxhighlight&gt;

Since 6.5 a new private key format is available using a [http://man.openbsd.org/bcrypt.3 bcrypt(3)] key derivative function (KDF) to better protect keys at rest.  This new format is always used for Ed25519 keys, and sometime in the future will be the default for all keys.  But for right now it may be requested when generating or saving existing keys of other types via the '''-o''' option in [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  

Details of the new format are found in the source code in the file '''PROTOCOL.key'''.

'''3''') Get the keys to the right places.  Transfer only the public key to remote machine.  The following assume the default locations for the authorized keys as specified in the server's configuration file by the '''AuthorizedKeysFile''' directive.  

'''3a''') If the utility &lt;code&gt;ssh-copy-id&lt;/code&gt; exists, and if password authentication is allowed, then it can be used to put the public key into place on the remote system.  The ''.pub'' is optional here, the script will figure it out if omitted. 
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-copy-id -i ~/.ssh/fred_example_org_ed25519 fred@server.example.org
&lt;/syntaxhighlight&gt;

If that script was successful in transferring the public key, then go on to step 4 below and test the key.  If not, then try transferring the public key manually as described in step 3b next.

'''3b''') Or the public key can be put in place manually on the remote machine.  For that the remote '''.ssh''' directory is needed, and within that a special file to store the public keys, the default file name is '''authorized_keys'''.  If either the '''authorized_keys''' file or '''.ssh''' directory do not exist on the remote machine, they need to be created.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ mkdir -m 700 ~/.ssh/
$ touch ~/.ssh/authorized_keys
$ chmod 0600 ~/.ssh/authorized_keys
$ nano -w ~/.ssh/authorized_keys
&lt;/syntaxhighlight&gt;

Then any editor which does not wrap long lines can be used to add the public key.  However the '''authorized_keys''' file is edited to add the key, the key itself must be in the file whole and unbroken on a single  line.  For example, [http://linux.die.net/man/1/nano nano(1)] can be started with the '''-w''' option to prevent wrapping of long lines.  (Another way to set line wrapping permanently in [http://linux.die.net/man/1/nano nano(1)] is by editing [http://linux.die.net/man/5/nanorc nanorc(5)].)  

If the key pair is not already on the client, transfer both the public and private keys there.  It is usually best to keep both the public and private keys together in the directory '''~/.ssh/''', though the public key is not always needed on the client after this step and could even be regenerated if it is ever needed again.  

'''4''') Test the keys

While remaining logged in via the first terminal, use the client system to open another window and in it start another SSH session and try authenticating to the remote machine from the client using the private key.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -i ~/.ssh/fred_example_org_ed25519 -l fred server.example.org
&lt;/syntaxhighlight&gt;

The option '''-i''' tells [http://man.openbsd.org/ssh.1 ssh(1)] which private key to try.  
Only after verifying that the key-based authentication works should you close the original window.  

It is possible to make permanent shortcuts on the client using [http://man.openbsd.org/ssh_config.5 ssh_config(5)], explained further below, once key-based authentication is working.  In particular, see the '''IdentityFile''',  '''IdentitiesOnly''', and '''AddKeysToAgent''' configuration directives, to name three.  

It is also a good idea to turn off password authentication, if and only if key-based authentication is setup for all the necessary remote accounts.  

➥ '''Troubleshooting of Key-based Authentication''':

If the server refuses to accept the key and fails over to the next authentication method (e.g.: &quot;Server refused our key&quot;), then there are several possible mistakes to look for on the server side.  

One of the most common errors is that the file and directory permissions are wrong.  The authorized keys file must be owned by the user in question and not be group writable.  Nor may the key file's directory be group or world writable.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ chmod u=rwx,g=rx,o= ~/.ssh
$ chmod u=rw,g=,o=  ~/.ssh/authorized_keys 
&lt;/syntaxhighlight&gt;

Another mistake that can happen is if the key inside the '''authorized_keys''' file on the remote host is broken by line breaks or has other whitespace in the middle.  That can be fixed by joining up the lines and removing the spaces or by recopying the key more carefully.  

And, though it should go without saying, the halves of the key pair need to match.  The public key on the server needs to match the private key held on the client.  If the public key is lost, then a new one can be generated with the '''-y''' option, but not the other way around.  If the private key is lost, then the public key should be erased as it is no longer of any use.  If many keys are in use for an account, it might be a good idea to add comments to them.  On the client, it can be a good idea to know which server the key is for, either through the file name itself or through the comment field.  A comment can be added using the '''-C''' option.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -t ed25519 -f ~/.ssh/fred_example_org_ed25519 -C &quot;web server mirror&quot;
&lt;/syntaxhighlight&gt;

On the server, it can be important to annotate which client they key is from if there is more than one public key there in an account.  There the comment can be added to the authorized keys file on the server in the last column if a comment does not already exist.  Again, the format of the authorized keys file is given in the manual page for [http://man.openbsd.org/sshd.8 sshd(8)] in the section &quot;AUTHORIZED_KEYS FILE FORMAT&quot;.  If the keys are not labeled they can be hard to match, which might or might not be what you want.  

====Associating Keys Permanently with a Server====

A key can be specified at run time, but to save retyping the same paths again and again, the '''Host''' directive in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] can apply specific settings to a target host.  In this case, by changing '''~/.ssh/config''' it is possible to assign particular keys to be tried automatically whenever making a connection to that specific host.  After adding the following lines to '''~/.ssh/config''', all that's needed is to type &lt;code&gt;ssh ''web1''&lt;/code&gt; to connect with the key for that server.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host web1
	Hostname 198.51.100.32
	IdentitiesOnly yes
	IdentityFile /home/fred/.ssh/web_key_ed25519
&lt;/syntaxhighlight&gt;

The '''~/.ssh/config''' below uses different keys for ''server'' versus ''server.example.org'',  regardless whether they resolve to the same machine.   This is possible because the host name argument given to [http://man.openbsd.org/ssh.1 ssh(1)] is not converted to a canonicalized host name before matching.

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host server
	IdentitiesOnly yes
	IdentityFile /home/fred/.ssh/key_a_ed25519

Host server.example.org
	IdentitiesOnly yes
	IdentityFile /home/fred/.ssh/key_b_ed25519
&lt;/syntaxhighlight&gt;

In this example the shorter name is tried first, but of course less ambiguous shortcuts can be made instead.  The configuration file gets parsed on a first-match basis.  So the most specific rules go at the beginning and the most general rules go at the end.  

====Encrypted Home Directories====

When using encrypted home directories the keys must be stored in an unencrypted directory.  That means somewhere outside the actual home directory which means [http://man.openbsd.org/sshd.8 sshd(8)] needs to be configured appropriately to find the keys in that special location.  

Here is one method for solving the access problem.  Each user is given a subdirectory under '''/etc/ssh/keys/''' which they can then use for storing their '''authorized_keys''' file.  This is set in the server's configuration file '''/etc/ssh/sshd_config'''

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthorizedKeysFile      /etc/ssh/keys/%u/authorized_keys
&lt;/syntaxhighlight&gt;

Setting a special location for the keys opens up more possibilities as to how the keys can be managed and multiple key file locations can be specified if they are separated by whitespace.  The user does not have to have write permissions for the '''authorized_keys''' file.  Only read permission is needed to be able to log in.  But if the user is allowed to add, remove, or change their keys, then they will need write access to the file to do that.  

One symptom of having an encrypted home directory is that key-based authentication only works when you are already logged into the same account, but fails when trying to make the first connection and log in for the first time.

Sometimes it is also necessary to add a script or call a program from '''/etc/ssh/sshrc''' immediately after authentication to decrypt the home directory.

====Passwordless Login====

One solution for passwordless logins is to still have a passphrase and work with an authentication agent in conjunction with a single-purpose key.  Most desktop environments launch an SSH agent automatically these days.  It will be visible in the '''SSH_AUTH_SOCK''' environment variable if it is.  On accounts with an agent, [http://man.openbsd.org/ssh-add.1 ssh-add(1)] can load private keys into an available agent.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-add ~/.ssh/fred_example_org_ed25519
&lt;/syntaxhighlight&gt;

Thereafter, the client will automatically check the agent for the key when appropriate.  If there are many keys in the agent, it will become necessary to set '''IdentitiesOnly'''.  See the above section on using '''~/.ssh/config''' for that.  See [[OpenSSH/Cookbook/Public_Key_Authentication#Key-based_Authentication_Using_an_Agent|Key-based Authentication Using an Agent]] below.  

Another, riskier, way of allowing passwordless logins is to follow the steps above, but simply do not enter a passphrase when asked for one while creating the key.  Note that using keys that lack a passphrase is very risky, so the key files should be very well protected and kept track of, and ideally locked down with a '''command=''' option or '''ForceCommand''' directive on the server.  That includes those keys which will only be used as single-purpose keys as described below.  

Timely key rotation becomes especially important.  In general, it is not a good idea to make a key without a passphrase.

====Requiring Both Keys and a Password====

While users should have strong passphrases for their keys, there is no way to enforce or verify that.  Indeed, since neither the private key nor its the passphrase ever leave the client machine there is nothing that the server can do to have any influence over that.  Instead, it is possible to require both a key and a password.  Starting with OpenSSH 6.2, it is possible for the server to require multiple authentication methods for login using the '''AuthenticationMethods''' directive.   
&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthenticationMethods publickey,password
&lt;/syntaxhighlight&gt;

This example from [http://man.openbsd.org/sshd_config.5 sshd_config(5)] requires that users first authenticate using a key and it only queries for a password if the key succeeds.  Thus with that configuration it is not possible to get to the system password prompt without first authenticating with a valid key.  Changing the order of the arguments changes the order of the authentication methods.

====Requiring Two or More Keys====

Since OpenSSH 6.8, the server now remembers which public keys have been used for authentication and refuses to accept previously-used keys.  This allows a set up requiring that users authenticate using two different public keys, maybe one in the file system and the other in a hardware token. 

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthenticationMethods publickey,publickey
&lt;/syntaxhighlight&gt;

The '''AuthenticationMethods''' directive, whether for keys or passwords, can also be set on the server under a '''Match''' directive to apply only to certain groups or situations.

====Requiring Certain Key Types For Authentication====

Also since OpenSSH 6.8, the '''PubkeyAcceptedKeyTypes''' directive, later changed to '''PubkeyAcceptedAlgorithms''', can specify which key algorithms are accepted for authentication.  Those not in the comma-separated pattern list are not allowed.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
PubkeyAcceptedAlgorithms ssh-ed25519*,ssh-rsa*,ecdsa-sha2*,sk-ssh-ed25519*,sk-ecdsa-sha2*
&lt;/syntaxhighlight&gt;

Either the actual key types or a pattern can be in the list.  Spaces are not allowed in the pattern list.  The exact list of key types supported for authentication can be found by the '''-Q''' option using the client.  The following two lines are equivalent.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -Q key-sig | sort

$ ssh -Q PubkeyAcceptedAlgorithms | sort
&lt;/syntaxhighlight&gt;

For host-based authentication, it is the '''HostbasedAcceptedAlgorithms''' directive which determines the key types which are allowed for authentication.

===Key-based Authentication Using the AuthorizedKeysCommand Directive===

It is possible to use a program or script to look up public keys rather than keeping them in a static file or files.  Any command called by the '''AuthorizedKeysCommand''' directive needs to either produce a syntactically correct public key while returning the exit code for a successful run or else return the exit code for failure.  The string sent to '''stdout''' will then be processed as part of the authentication work flow.  

Here is a shell script&lt;ref name=&quot;janpietmens&quot;&gt;{{cite web |url=https://jpmens.net/2025/03/25/authorizedkeyscommand-in-sshd/ |title=SSH keys from a command: sshd's AuthorizedKeysCommand directive |accessdate=2025-04-04 |date=2025-03-25 | author=Jan-Piet Mens }}&lt;/ref&gt; at its simplest, without constraints, demonstrating a public key lookup:

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
#!/bin/sh

echo &quot;ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIKs/UouletvojgB1YeRZ4MY6iRblQ2ERDuNhQO4tOvdL&quot;

exit 0
&lt;/syntaxhighlight&gt;

For authentication to succeed, the script must return exit code 0  (success) after sending the syntactically correct matching public key to '''stdout'''.  For the SSH daemon to even run the script in the first place, the script must have the correct file and directory permissions.

Both the '''AuthorizedKeysCommandUser''' directive and '''AuthorizedKeysCommand''' must be used together.  The former designates which account the script or program use when run.  If set to ''none'' or if it does not refer to a valid account then [http://man.openbsd.org/sshd sshd(8)] will just ignore the command.  If '''AuthorizedKeysCommand''' is set, and '''AuthorizedKeysCommandUser''' is left empty or missing, then [http://man.openbsd.org/sshd sshd(8)] won't even run when invoked.  The error will be:

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
AuthorizedKeysCommand set without AuthorizedKeysCommandUser
&lt;/syntaxhighlight&gt;

The '''AuthorizedKeysFile''' is always tried first when it is present in the server configuration.  The '''AuthorizedKeysCommand''' directive will not even be tried when the authorized keys file can provide a relevant key first.  

====A More Detailed Example Using the AuthorizedKeysCommand Directive====

By default the user name trying to log in is passed to the script when no tokens or arguments are provided.  Whether or how that information is used is up to the script.  The SSH daemon can also pass any combination of the tokens described in the TOKENS section of [http://man.openbsd.org/sshd_config sshd_config(5)] into the program or script being called.  Furthermore, the program or script can even be a front end for a database, such as OpenLDAP, or any similar system, as long as '''stdout''' produces a public key.  

Below is a more detailed example which uses a local script named '''keyfinder''' run with the account '''keys''' to look up the a public key for certain accounts.  First in [http://man.openbsd.org/sshd_config sshd_config(5)] the two directives:

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthorizedKeysCommand /usr/local/sbin/keyfinder %U
AuthorizedKeysCommandUser keys
&lt;/syntaxhighlight&gt;

The script below is only a demonstration and a more complex program can call databases or do advanced lookups or heuristics:  

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
#!/bin/sh

set -e

case $1 in
        &quot;1000&quot;)
                echo &quot;ssh-ed25519 AAAAC3NzaC1lZDIE5AAAAIK89...UT9hz&quot;
                ;;

        &quot;1001&quot;)
                echo &quot;restrict ssh-ed25519 AAAAC3NzaC1lZDI1NTAAIBvGx...Y0zxV&quot;
                ;;

        &quot;1002&quot;)
                echo &quot;command=\&quot;/usr/libexec/sftp-server\&quot; ssh-ed25519 AAAAC3NzaC1lZDI1TE5AIPSyY...cPTg3&quot;
                ;;

        *)
                exit 1
                ;;
   
esac

exit 0
&lt;/syntaxhighlight&gt;

The '''AuthorizedKeysCommand''' scripts or programs can return any correctly formatted public key to '''stdout''' for consideration in the authentication process.  That includes adding constraints to the keys.  Above, the account with the UID 1000 has no constraints, while the account with UID 1001 is quite constrained.  Finally, the account with the UID 1002 can only access the SFTP service.  See the section &quot;AUTHORIZED_KEYS FILE FORMAT&quot; in [http://man.openbsd.org/sshd sshd(8)] for the full set of possibilities.

===Key-based Authentication Using an Agent===

When an authentication agent, such as [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)], is going to be used, it should generally be started at the beginning of a session and used to launch the login session or X-session so that the environment variables pointing to the agent and its UNIX-domain socket are passed to each subsequent shell and process.  Many desktop distros do this automatically upon login or startup.  

Starting an agent entails setting a pair of environment variables:

* SSH_AGENT_PID : the process id of the agent
* SSH_AUTH_SOCK : the filename and full path to the UNIX-domain socket

The various SSH and SFTP clients find these variables automatically and use them to contact the agent and try when authentication is needed.   However, it is mainly SSH_AUTH_SOCK which is ever used.  If the shell or desktop session was launched using [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)], then these variables are already set and available.  If they are not available, then it is necessary to either set the variables manually inside each shell or for each application in order to use the agent or else to point to the agent's socket using the directive '''IdentityAgent''' in the client's configuration file.  

Once an agent is available, a relevant private key needs to be loaded before the agent can be used.  Once in the agent the private key can then be used many times.  Private keys are loaded into an agent with [http://man.openbsd.org/ssh-add.1 ssh-add(1)].
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-add /home/fred/.ssh/mykey_ed25519
Identity added: /home/fred/.ssh/mykey_ed25519 (/home/fred/.ssh/mykey_ed25519)
&lt;/syntaxhighlight&gt;

Keys stay in the agent for as long as it is running unless specified otherwise.  A timeout can be set either with the '''-t''' option when starting the agent itself or when actually loading the key using [http://man.openbsd.org/ssh-add.1 ssh-add(1)].  In either case, the '''-t''' option will set a timeout interval, after which the key will be purged from the agent.
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-add -t 1h30m /home/fred/.ssh/mykey_ed25519
Identity added: /home/fred/.ssh/mykey_ed25519 (/home/fred/.ssh/mykey_ed25519)
Lifetime set to 5400 seconds
&lt;/syntaxhighlight&gt;

The option '''-l''' will list the fingerprints of all of the identities in the agent.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-add -l                                    
256 SHA256:77mfUupj364g1WQ+O8NM1ELj0G1QRx/pHtvzvDvDlOk mykey for task x (ED25519)
3072 SHA256:7unq90B/XjrRbucm/fqTOJu0I1vPygVkN9FgzsJdXbk myotherkey rsa for task y (RSA)
&lt;/syntaxhighlight&gt;

It is also possible to remove individual identities from the agent using '''-d''' which will remove them one at a time if identified by file name, but only if the file name is given and without the file name of the private key to be remove, '''-d''' will fail silently.  Using '''-D''' instead will remove all of them at once without needing to specify any by name.  

By default [http://man.openbsd.org/ssh-add.1 ssh-add(1)] uses the agent connected via the socket named in the environment variable '''SSH_AUTH_SOCK''', if it is set.  Currently, that is its only option.  However, for [http://man.openbsd.org/ssh.1 ssh(1)] an alternative to using the environment variable is the client configuration directive '''IdentityAgent''' which tells the SSH clients which socket to use to communicate with the agent.  If both the environment variable and the configuration directive are available at the same time, then the value in '''IdentityAgent''' takes precedence over what's in the environment variable.  '''IdentityAgent''' can also be set to ''none'' to prevent the connection from trying to use any agent at all.  

The client configuration directive '''AddKeysToAgent''' can also be useful in getting keys into an agent as needed.  When set, it automatically loads a key into a running agent the first time the key is called for if it is not already loaded.  Likewise the '''IdentitiesOnly''' directive can ensure that the relevant key is offered on the first try.  Rather than typing these out whenever the client is run, they can be added to '''~/.ssh/config''' and thereby added automatically for designated host connections.  

====Agent Forwarding====

Agent forwarding is one means of passing through one or more intermediate hosts.  However, the '''-J''' option for '''ProxyJump''' would be a safer option.  See [[OpenSSH/Cookbook/Proxies_and_Jump_Hosts#Jump_Hosts_--_Passing_Through_a_Gateway_or_Two | Passing Through a Gateway or Two]] in the section on jump hosts about that.  With agent forwarding, intermediate machines forward challenges and responses back and forth between the client and the final destination.  This comes with some risks but eliminates the need for using passwords or holding keys on any of these intermediate machines.  

A main advantage of agent forwarding is that the private key itself is not needed on any remote machine, thus hindering unwanted file system access to it. &lt;ref name=&quot;OpenSSH key management, Part 3&quot;&gt;{{cite web | url=http://www.ibm.com/developerworks/library/l-keyc3/ | title=Common threads: OpenSSH key management, Part 3 | author=Daniel Robbins | publisher=IBM | date=2002-02-01 | accessdate=2013-04-27}}&lt;/ref&gt;  Another advantage is that the actual agent to which the user has authenticated does not go anywhere and is thus less susceptible to analysis.  

One risk with agents is that they can be re-used to tailgate in if the permissions allow it.  Keys cannot be copied this way, but authentication is possible when there are incorrect permissions.  Note that disabling agent forwarding does not improve security unless users are also denied shell access, as they can always install their own forwarders.

The risks of agent forwarding can be mitigated by confirming each use of a key by adding the '''-c''' option when adding the key to the agent.  This requires the SSH_ASKPASS variable be set and available to the agent process, but will generate a prompt on the host running the agent upon each use of the key by a remote system.  So if passing through one or more intermediate hosts, it is usually better to instead have the SSH client use stdio forwarding with '''-W''' or '''-J'''.

On the client side agent forwarding is disabled by default and so if it is to be used it must be enabled explicitly.  Put the following line in  [http://man.openbsd.org/ssh_config.5 ssh_config(5)] to enable agent forwarding for a particular server:
&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
        Host gateway.example.org
        ForwardAgent yes
&lt;/syntaxhighlight&gt;

On the server side the default configuration files allow authentication agent forwarding, so to use it, nothing needs to be done there, just on the client side.  However, again, it would be preferable to take a look at '''ProxyJump''' instead.  

=====New Style SSH Agent Destination Constraints=====

Using the '''ProxyJump''' option instead of authentication agent forwarding is still the best way to pass through other systems while avoiding the exposure of private keys, something which could happen forwarding agents.  However, from 8.9 onward, [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)] will allow the agent to limit which hosts it will use for authentication as specified by [http://man.openbsd.org/ssh-add.1 ssh-add(1)] using the '''-h''' option.  These constraints have been added through two agent protocol extensions and a modification to the public key authentication protocol.  This feature may evolve, but for now the result is such that keys for account authentication can be loaded into the agent in four ways:

* no limits on forwarding (not recommended)
* local use only, these will not get forwarded
* forwarding, but only to specific remote hosts
* forwarding to specific remote hosts via specified routes

The intent is that the restrictions fail safely so that they do not allow authentication when one or more hosts in the route lack the needed protocol features.  The destinations and routes cannot be modified once the keys are loaded, but multiple routes to the same destination can be loaded and the routes can be any number of hops.  If the routes need changing, then the key must be reloaded into the agent with the new route or routes.  

The general default for the client is to keep keys in the agent for local use only.  However, that can be enforced explicitly by adding the '''-a''' option when starting the client or else setting the '''ForwardAgent''' directive in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] to 'no' in the relevant configuration block.  

In order to load keys for unlimited forwarding, which is not the best idea, just add them using [http://man.openbsd.org/ssh-add.1 ssh-add(1)] as normal.  Then use the '''-A''' option with the client or set the '''ForwardAgent''' directive in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] to 'yes' in the relevant configuration block.  

In order to limit keys for connection only to a specific remote host, or to load keys for connection to a specific remote host with forwarding via one or more intermediate hosts, use the '''-h''' option when loading keys into the agent.  Here the one key may be used only to connect to the specific destination:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-agent -h server.example.org server.key.ed25519
&lt;/syntaxhighlight&gt;

If an intermediate system is passed through, the best way is to use '''ProxyJump''' which is the '''-J''' option for the SSH Client.  If agent forwarding must be allowed then the tightest way is to constrain which systems may use the keys, again using the '''-h''' option.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-agent -h middle.example.org -h &quot;middle.example.org&gt;server.example.org&quot; server.key.ed25519
&lt;/syntaxhighlight&gt;

Multiple steps can be included, even multiple routes.  They just have to be enumerated explicitly, though patterns may still be used for the destination hosts as well as specific names.  Each host in the chain must support these protocol extensions for the connection to complete.  

Any keys designated for forwarding are unusable for authentication on any other hosts than those which have been explicitly identified for forwarding.  These permitted hosts are identified by host key or host certificate from the '''known_hosts''' file or another file designated by the '''-H''' option when loading the key with [http://man.openbsd.org/ssh-add.1 ssh-add(1)].  If '''-H''' is not used at the time the keys are loaded into the agent, then the default known hosts file(s) will be used: '''~/.ssh/known_hosts''', '''/etc/ssh/ssh_known_hosts''', '''~/.ssh/known_hosts2''', and '''/etc/ssh/ssh_known_hosts2'''.

In the case of keys, the '''known_hosts''' list must be maintained conscientiously &lt;ref name=&quot;ssh-agent-restrictions&quot;&gt;{{ cite web | author=Damien Miller|url=https://www.openssh.org/agent-restrict.html | title=SSH agent restriction | publisher=OpenSSH | date=2021-12-16|accessdate=2022-03-06}}&lt;/ref&gt;, perhaps with the help of the '''UpdateHostkeys''' and '''CanonicalizeHostname''' client configuration directives.  Use of certificates requires the agent to only need to be aware of the Certificate Authority (CA).

Again, see [[OpenSSH/Cookbook/Proxies_and_Jump_Hosts#Jump_Hosts_--_Passing_Through_a_Gateway_or_Two | Passing Through a Gateway or Two]] in the section on jump hosts about a way to pass through one or more intermediate machines without needing to forward an SSH agent.

=====Old Style, Almost Safe SSH Agent Forwarding=====

The best way to pass through one or more intermediate hosts is to use the '''ProxyJump''' option instead of authentication agent forwarding and thereby not risking the exposure of any private keys.  If authentication agent forwarding must be used, then it would be advisable in the interest of following the principle of least privilege to forward an agent containing the minimum necessary number of keys.  There are several ways to solve that.  

In version 8.8 and earlier a partial solution is to make a one-off, ephemeral agent to hold just the one key or keys needed for the task at hand.  Another partial solution would be to set up a user-accessible service at the operating system level and then use [http://man.openbsd.org/ssh_config.5 ssh_config] for the rest.  

Automatically launching an ephemeral agent unique to each session can be done by crafting either a special shell alias or function to launch a single-use agent.  Either the function or the alias can be written to require confirmation for each requested signature.  The following example is a function is inspired by an updated blog post by Vincent Bernat&lt;ref name=&quot;safer-agent-forwarding&quot;&gt;{{cite web |url=https://vincent.bernat.ch/en/blog/2020-safer-ssh-agent-forwarding |title=Safer SSH agent forwarding |author=Vincent Bernat|date=2020-04-05 |accessdate=2020-10-04}}&lt;/ref&gt; on SSH agent forwarding:
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ agentssh() {
        ssh-agent ssh -o AddKeysToAgent=confirm -o ForwardAgent=yes
}
&lt;/syntaxhighlight&gt;

Note the use of [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)].  When invoking that alias, the SSH client will be launched with a unique, ephemeral supporting key agent.  The alias sets up a new agent, including setting the two environment variables, and then sets two client options while calling the client.  This arrangement still checks with [http://man.openbsd.org/ssh_config.5 ssh_config(5)] for other options and settings.  When the SSH session is finished the agent which launched it ends and goes away, thus cleaning up after itself automatically.  

Another way is to rely on the client's configuration file for some of the settings.  Such methods rely mostly on [http://man.openbsd.org/ssh_config.5 ssh_config(5)] but still require an independent method to launch an ephemeral agent because the OpenSSH client is already running by the time it reads the configuration file and is thus not affected by any changes to environment variables caused by the configuration file and it is through the environment variables that contain information about the agent.  However, when the path to the UNIX-domain socket used to communicate with the authentication agent is decided in advance then the '''IdentityAgent''' option can point to it once the one-off agent&lt;ref name=&quot;wikimedia_ssh_agents&quot;&gt;{{cite web |url=https://wikitech.wikimedia.org/wiki/Managing_multiple_SSH_agents#Linux_solutions |title=Managing multiple SSH agents |publisher=Wikimedia|accessdate=2020-04-07}}&lt;/ref&gt; is actually launched.  The following uses a specific agent's pre-defined socket whenever connecting to either of two particular domains:

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host *.wikimedia.org *.wmflabs.org
        User fred
        IdentitiesOnly yes
        IdentityFile %d/.ssh/id_cloud_01
        IdentityAgent /run/user/%i/ssh-cloud-01.socket
        ForwardAgent yes
        AddKeysToAgent yes
&lt;/syntaxhighlight&gt;

The '''%d''' stands for the path to the home directory and the '''%i''' stands for the user id (UID) for the current account.  In some cases the '''%i''' token might also come in handy when setting the '''IdentityAgent''' option inside the configuration file.  Again, be careful when forwarding agents with which keys are in the forwarded agent.  See the section &quot;TOKENS&quot; in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] for more such abbreviations.  

With those configuration settings, the authentication agent must already be up and running and point to the designated socket prior to starting the SSH client for that configuration to work.  Additionally, it should place the socket in a directory which is inaccessible to any other accounts.  [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)] must use the '''-a''' option to name the socket:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-agent -a /run/user/${UID}/ssh-cloud-01.socket
&lt;/syntaxhighlight&gt;

That agent configuration can be launched manually or via a script or service manager.  However, in the interests of privacy and security in general, agent forwarding is to be avoided.  The configuration directive '''ProxyJump''' is the best alternative and, on older systems, host traversal using '''ProxyCommand''' with [http://man.openbsd.org/nc.1 netcat] are preferable.  Again, see the section on [[OpenSSH/Cookbook/Proxies and Jump Hosts|Proxies and Jump Hosts]] for how those methods are used.

====Checking the Agent for Specific Keys====

The [http://man.openbsd.org/ssh_add ssh_add(1)] utility's '''-T''' option can test whether a specific private key is available in the agent or not by looking up the matching public key.  That can be useful in a shell script.

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
#!/bin/sh

key=/home/fred/.ssh/some.key.ed25519.pub

if ssh-add -T ${key}; then
        echo &quot;Key ${key} Found&quot;
else
        echo &quot;Key ${key} missing&quot;
fi
&lt;/syntaxhighlight&gt;

Or it could be done with an alternate syntax just as well either in a script or in an interactive shell sessions,

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ key=/home/fred/.ssh/some.key.ed25519.pub
$ ssh-add -T ${key} &amp;&amp; echo &quot;Key found&quot; || echo &quot;Key missing&quot;
&lt;/syntaxhighlight&gt;

However, if the desired result would be to add key to the agent then the '''AddKeysToAgent''' client configuration option can ensure that a specific key is added to the SSH agent upon first use during any given login session.  That can be done using '''-o AddKeysToAgent=yes''' as a run-time argument, or by modifying [http://man.openbsd.org/ssh_config ssh_config(5)] as appropriate:

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host www
        HostName www.example.com
        IdentityFile %d/.ssh/www.ed25519
        IdentitiesOnly yes
        AddKeysToAgent yes
&lt;/syntaxhighlight&gt;

With those options in the configuration file, the first time &lt;code&gt;ssh www&lt;/code&gt; is run the specified key will get added to the agent and remain available.

===Key-based Authentication Using A Hardware Security Token===

While stand-alone keys have been around for a long time, it has been possible since version 8.2 to use keys backed by hardware security tokens, such as OnlyKey, Yubikey, or many others, though the FIDO2 protocol.  The Universal 2nd Factor (U2F) authentication is supported directly in OpenSSH through FIDO2 and does not need third party software.  At the moment there are two types of hardware backed keys, ECDSA-SK and Ed25519-SK, but only the latest hardware tokens support the latter.  If the key Ed25519-SK format is not supported by the token's firmware, then the following error message will be presented when attempts to use that key type are made:

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
Key enrollment failed: invalid format
&lt;/syntaxhighlight&gt; 

If supported, either key type can be created with [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  The steps are almost identical to creating normal keys but the token must be available to the system (plugged in) first.  Then if called for, the token's PIN must be entered and the token touched or otherwise activated.  After that, the key creation proceeds as normal.  Mind the key type as specified by the '''-t''' option.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -t ed25519-sk -f /home/fred/.ssh/server.ed25519-sk -C &quot;web server for fred&quot;
Generating public/private ed25519-sk key pair.
You may need to touch your authenticator to authorize key generation.
Enter passphrase (empty for no passphrase): 
Enter same passphrase again: 
Your identification has been saved in /home/fred/.ssh/server.ed25519-sk
Your public key has been saved in /home/fred/.ssh/server.ed25519-sk.pub
The key fingerprint is:
SHA256:41wVVDnKJ9gKr2Sj4CFuYMhcNvYebZ6zq0PWyP4rRDo web server
The key's randomart image is:
+[ED25519-SK 256]-+
|           .o... |
|             .o  |
|           +.. . |
|   = .  . ..= .  |
|+ + * + So.. o   |
|o+.EoO *+oo      |
|.o oBo+++o       |
|  o .=.+.        |
| .   .===        |
+----[SHA256]-----+
&lt;/syntaxhighlight&gt;

Once created, the public and private key files get handled like with any other type of key.  But when authenticating, the hardware token must be present and activated when called for.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -i /home/fred/.ssh/server.ed25519-sk server.example.org
Enter passphrase for key '/home/fred/.ssh/server.ed25519-sk': 
Confirm user presence for key ED25519-SK SHA256:41wVVDnKJ9gKr2Sj4CFuYMhcNvYebZ6zq0PWyP4rRDo
&lt;/syntaxhighlight&gt;

The resulting private key file is not actually the key itself but instead a &quot;key handle&quot; which is used by the hardware security token to derive the real private key on demand at the time it is actually used&lt;ref name=&quot;OpenBSD_tech_U2F_FIDO&quot;&gt;{{cite web |url=https://marc.info/?l=openbsd-tech&amp;m=157376801917387&amp;w=2 |title=OpenSSH U2F/FIDO support in base 
|publisher=OpenBSD-Tech Mailing List | date=2019-11-14
|accessdate=2021-03-24}}&lt;/ref&gt;.  As a result, the hardware-backed private key file is useless without the accompanying hardware token.  This also means that these key files are not portable across hardware tokens, say when having multiple tokens in reserve or as backup, even when used by the same account.  So when multiple hardware tokens are in use, different key pairs must be generated for each token.

====Hardware Security Token Resident Private Key====

It is possible to store the private key within the token itself, but for the moment it cannot be used directly from inside the token and must first be saved as a file.  Also, the key can only be loaded into the FIDO authenticator at the time of creation  using the '''-O resident''' option with [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  Otherwise, the process is the same as above.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -O resident -t ed25519-sk -f /home/fred/.ssh/server.ed25519-sk -C &quot;web server for fred&quot;
. . .
&lt;/syntaxhighlight&gt;

When needed, the resident key can be extracted from the FIDO2 hardware token and saved into a file using the '''-K''' option.  At this stage a passphrase can be added to the file, but no passphrase is kept within the token itself, only an optional PIN protects the key there.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -K
Enter PIN for authenticator: 
Enter passphrase (empty for no passphrase): 
Enter same passphrase again: 
Saved ED25519-SK key to id_ed25519_sk_rk

$ mv -i id_ed25519_sk_rk /home/fred/.ssh/server.ed25519-sk
&lt;/syntaxhighlight&gt;

Since the output file name is fixed, any pre-existing file with that name can get overwritten but there will be a warning first.  However, it is not recommended to keep the key on the hardware token because it provides more protection when kept separately.

==Single-purpose Keys==

Tailored single-purpose keys can eliminate use of remote root logins for many administrative activities.  A  finely tailored '''sudoers''' is needed along with an unprivileged account.  When done right, it gives just enough access to get the job done, following the security principle of Least Privilege.  

Single-purpose keys are accompanied by use of either the '''ForceCommand''' directive in [http://man.openbsd.org/ssh_config.5 sshd_config(5)] or the '''command=&quot;...&quot;''' directive inside the '''authorized_keys''' file.  The method is to generate a new key pair, transfer the public key to '''authorized-keys''' on the remote system, and then prepend the appropriate command or script there to the line with the key.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/usr/local/bin/somescript.sh&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIEcgdzDvSebOEjuegEx4W1I/aA7MM3owHfMr9yg2WH8H
&lt;/syntaxhighlight&gt;

The '''command=&quot;...&quot;''' directive inserted there overrides everything else and ensures that when logging in with just that key only the script '''/usr/local/bin/somescript.sh''' is run.  If it is necessary to pass parameters to the script, have a look at the contents of the '''SSH_ORIGINAL_COMMAND''' environment variable and use it in a case statement.  Do not ever trust the contents of that variable nor use the contents directly, always indirectly.  

Single-purpose keys are useful for allowing only a tunnel and nothing more.  The following key will only echo some text and then exit, unless used non-interactively with the '''-N''' option.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/bin/echo do-not-send-commands&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBzTIWCaILN3tHx5WW+PMVDc7DfPM9xYNY61JgFmBGrA 
&lt;/syntaxhighlight&gt; 

No matter what the user tries while logging in with that key, the session will only echo the given text and then exits.  Using the '''-N''' option disables running the remote program, allowing the connection to stay open, allowing a tunnel. 

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -L 3306:localhost:3306 \
	-i ~/.ssh/tunnel_ed25519 \
	-N \
	-l fred \
	server.example.com
&lt;/syntaxhighlight&gt;

That creates a tunnel and stays connected despite a key configuration which would close an interactive session.  See also the '''-n''' or '''-f''' option for [http://man.openbsd.org/ssh.1 ssh(1)].  

===Single-purpose Keys to Avoid Remote Root Access===

The easy way is to write a short shell script, place it '''/usr/local/bin/''', and then configure '''sudoers''' to allow the otherwise unprivileged account to run just that script and only that script.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
%wheel  ALL=(root:root) NOPASSWD: /usr/sbin/service httpd stop
%wheel  ALL=(root:root) NOPASSWD: /usr/sbin/service httpd start
&lt;/syntaxhighlight&gt;

Then the key calls the script using '''command=&quot;...&quot;''' inside '''authorized_keys'''.  Here the one key starts the web server, the other stops the web server.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/usr/bin/sudo /usr/sbin/service httpd stop&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIEcgdzDvSebOEjuegEx4W1I/aA7MM3owHfMr9yg2WH8H
command=&quot;/usr/bin/sudo /usr/sbin/service httpd start&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMidyqZ6OCvbWqA8Zn+FjhpYE6NoWSxVjFnFUk6MrNZ4
&lt;/syntaxhighlight&gt;

Complicated programs like [http://linux.die.net/man/1/rsync rsync(1)], [http://man.openbsd.org/tar.1 tar(1)], [http://linux.die.net/man/1/mysqldump mysqldump(1)], and so on require an advanced approach when building a single-purpose key.  For them, the '''-v''' option can show exactly what is being passed to the server so that '''sudoers''' can be set up correctly.  That way they can be restricted to only access designated parts of the file system.  For example, here is what &lt;code&gt;ssh -v&lt;/code&gt; shows from one particular usage of [http://linux.die.net/man/1/rsync rsync(1)], note the &quot;Sending command&quot; line:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ rsync -e 'ssh -v' fred@server.example.org:/etc/ ./backup/etc/
. . .
debug1: Sending command: rsync --server --sender -e.LsfxC . /etc/
. . .
&lt;/syntaxhighlight&gt;

That output can then be added to '''sudoers''' so that the key can do only that function.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
%backup ALL=(root:root) NOPASSWD: /usr/bin/rsync --server --sender -e.LsfxC . /etc/
&lt;/syntaxhighlight&gt;

Then to tie it all together, the account &quot;backup&quot; needs a key:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/usr/bin/rsync --server --sender -e.LsfxC . /etc/&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMm0rs4eY8djqBb3dIEgbQ8lmdlxb9IAEuX/qFCTxFgb 
&lt;/syntaxhighlight&gt;

Many of these programs have a '''--dry-run''' or equivalent option.  Remember to use it when figuring out the right settings.

===Read-only Access to Keys===

In some cases it is necessary to prevent accounts from being able to changing their own authentication keys.  However, such situations may be a better case for using certificates.  However, if done with keys it is accomplished by putting the key file in an external directory where the user has read-only access, both to the directory and to the key file.  Then the '''AuthorizedKeysFile''' directive assigns where [http://man.openbsd.org/sshd.8 sshd(8)] looks for the keys and can point to a secured location for the keys instead of the default location.

A good alternate location could be a new directory '''/etc/ssh/authorized_keys''' which could store the selected accounts' key files there.  The change can be made to apply to only a group of accounts by putting the settings under a '''Match''' directive.  The default location for keys on most systems is usually '''~/.ssh/authorized_keys'''.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Match Group sftpusers
	AuthorizedKeysFile /etc/ssh/authorized_keys/%u
&lt;/syntaxhighlight&gt;

Then the permissions there would allow the keys to be read but not written:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ls -dhln /etc/ssh/
drwxr-x--x 3 0 0 4.0K Mar 30 22:16 /etc/ssh/authorized_keys/

$ ls -dhln /etc/ssh/*.pub
-rw-r--r-- 1 0 0 173 Mar 23 13:34 /etc/ssh/fred
-rw-r--r-- 1 0 0  93 Mar 23 13:34 /etc/ssh/user1
-rw-r--r-- 1 0 0 565 Mar 23 13:34 /etc/ssh/user2
. . .
&lt;/syntaxhighlight&gt;

The keys could even be within subdirectories, though the same restrictions apply regarding permissions and ownership.  

For chrooted SFTP, the method is the same to keep the key files out of reach of the accounts:  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Match Group sftpusers
	ChrootDirectory /home
	ForceCommand internal-sftp -d %u
	AuthorizedKeysFile /etc/ssh/authorized_keys/%u
&lt;/syntaxhighlight&gt;

Of course a '''Match''' directive is not essential.  The settings could be made to apply to all accounts by putting the directive in the main part of the server configuration file instead.

==Mark Public Keys as Revoked==

Keys can be revoked.  Keys that have been revoked can be stored in '''/etc/ssh/revoked_keys''', a file specified in [http://man.openbsd.org/ssh_config.5 sshd_config(5)]  using the directive '''RevokedKeys''', so that [http://man.openbsd.org/sshd.8 sshd(8)] will prevent attempts to log in with them.  No warning or error on the client side will be given if a revoked key is tried.  Authentication will simply progress to the next key or method.

The revoked keys file should contain a list of public keys, one per line, that have been revoked and can no longer be used to connect to the server.  The key cannot contain any extras, such as [[OpenSSH/Client_Configuration_Files#Available_key_login_options | login options]] or it will be ignored. If one of the revoked keys is tried during a login attempt, the server will simply ignore it and move on to the next authentication method.  An entry will be made in the logs of the attempt, including the key's fingerprint.  See the section on [[OpenSSH/Logging_and_Troubleshooting | logging]] for a little more on that.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
RevokedKeys /etc/ssh/revoked_keys
&lt;/syntaxhighlight&gt;

The '''RevokedKeys''' configuration directive is not set in [http://man.openbsd.org/ssh_config.5 sshd_config(5)] by default.  It must be set explicitly if it is to be used.  This is another situation that might be better fulfilled through using certificate since a validity interval can be set in any combination of seconds, minutes, hours, days, or weeks can be set for certificates while keys are valid indefinitely.  

===Key Revocation Lists===

A Key Revocation List (KRL) is a compact, binary form of representing revoked keys and certificates.  In order to use a KRL, the server's configuration file must point to a valid list using the '''RevokedKeys''' directive.  KRLs themselves are generated with [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] and can be created from scratch or edited in place.  Here a new one is made, populated with a single public key: 

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -k -f /etc/ssh/revoked_keys -z 1 ~/.ssh/old_key_rsa.pub
&lt;/syntaxhighlight&gt;

Here an existing KRL is updated by adding the '''-u''' option:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -u -k -f /etc/ssh/revoked_keys -z 2 ~/.ssh/old_key_dsa.pub
&lt;/syntaxhighlight&gt;

Once a KRL is in place, it is possible to test if a specific key or certificate is in the revocation list.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -Q -f /etc/ssh/revoked_keys ~/.ssh/old_key_rsa.pub
&lt;/syntaxhighlight&gt;

Only public keys and certificates will be loaded into the KRL.  Corrupt or broken keys will not be loaded and will produce an error message if tried.  Like with the regular '''RevokedKeys''' list, the public key destined for the KRL cannot contain any extras like login options or it will produce an error when an attempt is made to load it into the KRL or search the KRL for it.

==Verify a Host Key by Fingerprint==

The above examples have been about using keys to authenticate the client to the server.  A different context in which keys are used is when the server identifies itself to the client, which happens automatically at the beginning of each non-multiplexed session.  In order for that identification to happen the client acquires a public key from the server, usually on or prior to first contact, which it can subsequently use to ensure that it is connecting to the same server again and not an impostor.  The default locations for storing these acquired host keys on the client are in '''/etc/ssh/ssh_known_hosts''', if managed by the system administrator, or in '''~/.ssh/known_hosts''' if managed by the client's own account.  The format of the contents is a line with a host address and its matching public key.  The file is described in detail in the [http://man.openbsd.org/sshd.8 sshd(8)] manual page in the section &quot;SSH_KNOWN_HOSTS FILE FORMAT&quot;.

When connecting for the first time to a remote host, the server's host key should be verified in order to ensure that the client is connecting to the right machine and not an impostor or anything else.  Usually this verification is done by comparing the fingerprint of the server's host key rather than trying to compare the whole key itself.  By default the client will show the fingerprint if the key is not already found in the '''known_hosts''' register.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -l fred server.example.org
The authenticity of host 'server.example.org (192.0.32.10)' can't be established.
ECDSA key fingerprint is SHA256:LPFiMYrrCYQVsVUPzjOHv+ZjyxCHlVYJMBVFerVCP7k.
Are you sure you want to continue connecting (yes/no)? 
&lt;/syntaxhighlight&gt;

That can be compared to a fingerprint received out of band, say by post, e-mail, SMS, courier, and so on.  Specifically, the example represents the key's fingerprint as a base64 encoded SHA256 checksum.  That is the default style.  The fingerprint can also be displayed as an MD5 hash in hexadecimal instead by passing the client's '''FingerprintHash''' configuration directive as a runtime argument or setting it in [http://man.openbsd.org/ssh_config.5 ssh_config(5)].  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -o FingerprintHash=md5 host.example.org
The authenticity of host 'host.example.org (192.0.32.203)' can't be established.
RSA key fingerprint is MD5:10:4a:ec:d2:f1:38:f7:ea:0a:a0:0f:17:57:ea:a6:16.
Are you sure you want to continue connecting (yes/no)?
&lt;/syntaxhighlight&gt;

But the default in new versions is SHA256 in base64 has a lower chance of collision.

In OpenSSH 6.7 and earlier, the client showed fingerprints as a hexadecimal MD5 checksum instead a of the base64-encoded SHA256 checksum currently used:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -l fred server.example.org
The authenticity of host 'server.example.org (192.0.32.10)' can't be established. 
RSA key fingerprint is 4a:11:ef:d3:f2:48:f8:ea:1a:a2:0d:17:57:ea:a6:16. 
Are you sure you want to continue connecting (yes/no)? 
&lt;/syntaxhighlight&gt;

Another way of comparing keys is to use the ASCII art visual host key.  See further below about that.  

===Downloading keys===

Even though a host’s key is usually displayed for review the first time the SSH client tries to connect, it can also be fetched on demand at any time using [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)]:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan server.example.org
# server.example.org:22 SSH-2.0-OpenSSH_10.6
server.example.org ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBEWKepJgkC2XTG5cAr2Nyew6hOp5AjG7vi2RYFtPWqN3bo5XGuCX2d2YVyn++/2PtyMYBaKWyFpCNTT9X0F1Epg=
# server.example.org:22 SSH-2.0-OpenSSH_10.6
server.example.org ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDKyERe8k+fnsrt4JrcLD3AW0kXj90r9ybrEZuY/CTrXIqYSizO335SxGJoWrKijaRy8htuueMkmNfxxhnBPoAjul/4T/FCRGKaV0jC96xYNnKcXbnXxSLVQ0OW2EIPvQhw/TU/G3vEqtiRYGyaNcZS6xrnVv3xuPuvVC1VRKspNLEq7zfvToC0OB89X5DIbvBbHY13PjJ0NrDdX3sSA8lxPsYagBuDIvyxH0S4Z5fQHeYrdvENS5zX6LwJeMeGSOqDuD0Zb4hpKxhaGVwP5e435VcFuImbFaDPM4w71PzaSUEj+tnUA0mGDoLiCrpW3txkJszog9lN3C/nLGghFaT7ajrfH55qut81JnvdhMju9+SzxrKPJmtQZfKVLIc4whEbtFsPCdm2bstz7ROWxTJ3t/Vr8/QVm2G2aY4FHuPwo2jUQDbQA7mCV+fe1sADy2jLzGhn1TCeYvWSv5PNJAT97IrLfD3+0Uo+qJD/6CU7F8oabj1Ql2H8fPN5kGSWfkM=
# server.example.org:22 SSH-2.0-OpenSSH_10.6
server.example.org ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIJo5gc4VrxVQ5apAOd7qK6UqGlLMpWOPuunjB53JBN2s
# server.example.org:22 SSH-2.0-OpenSSH_10.6
# server.example.org:22 SSH-2.0-OpenSSH_10.6
# server.example.org:22 SSH-2.0-OpenSSH_10.6
server.example.org ssh-mldsa44-ed25519 AAAAE3NzaC1tbGRzYTQ0LWVkMjU1MTkAAAVAyIw5r9FaniSYqBX0yd9vgBz5nCkebaQlMQN9N0p//Ukfn/CnZ3YtZWn6pUGjDM85/bqdL1gqah1OLfnl1eHk0qvTACrym07uKaMLoEHuakIXHbTi/ELPRoRP3F+DpEgjtYSjLc/fJiobRMgSvmLJxTUzZTStsqWAL1L9/1zuwHEngR+THpUcCSTi6KKkYcQiWGOFwpO22VdiuOg+zdQSH+9jW6eXYk1z81KU6UlHZps8zVrlqCd3FDDghgbH5U8DcGN2t6GvVfn6jFjpEk0ouj0of3/7010eRXjnv3QSbprCpMq73lAemQM+3LvTtrMBhFWNhCXhyOHfO1Yq7c8xaOwlFK78PlERjdHTvVJaCaDFDy7Pg9I+wxv+uC+W0wtzJ2S1y9XCYUgJo9yEiIGuSZdhMkYUwMnXLzQMm44hQOW153pdlHWze3kESCLg/LJf9RbUoSB43t6rghSHEiUkIi5TtCtFZ4nAGeH+wVwlB9Fwog5uZuJN1FYuuY5sSrLHJAQDUwudkdak0ifOhtPtsM/ClYr3baolQ/qi0ABYUVLKSV5b+A5DlTXa23zc7JAXm2YVfkWpOfVJG4TY81wrJoDumsd1y3XaH28/4QbADsZCE3wYsBou8ff0xKgPu8xm2K+sYSmzUbBGprArAQA0LtIDGNGqrb4JsZ1ru+viwzfSlxV7Nz7ZrSw6h+Ddq4J9A6oKXy6YS3uf1GFOtBQm6JfuyMHQEEUtYZrU4UK3C/fKHx9vjuw7YdhsL8JRgxbF14qJLFizkmVbK2e6aWEE4iCqLLLlZ0dC2peYUUqyGb9PsW7sewYzGbipzPpQ/GobRT3Obc3Gmu8P386pDGR7hmkOpFmVwIcfc431cUmZixK7CkPxzUvfaAAQkmNs/p4eNNoP0gq/xPGsV14/heULbWp/njGWk1ysjjGxP6YMwHcEZpUdSGbD05zbL0KkMtmKsr8yuJYjdVAgtH2bVAvrxXRXLgavmm97VYYq1A9rOYiQFlMrKRg6yZhT10Xt8Hukf6ySLk+fieFc3nH99YeysoA5rsfp9kdXr65GpwrBerZlf/20ZLJ7s4xaYb9SukR/8tiPt9iAVQjqPdb0MseZVrzhKo/jK44JHbHejHMoMMs7etPAS5TIjHxcJTP66B3eO9A0l2fAage2ka7ehTnHivxD3EE9KnqYBjIHDU7o6dTrX7UyQsdhax9bPKEL7OEtm6hXXfwzy4GdqGi124BclFAF0LeBSvBUgmSKIn3wfzJx/XXbt512eOn3WZk2v0TsiteH9kPEgDxVkUykawg2tleak9rTFMzYpDZRHvZD7uHWUZ8ktr2FEKWgq7/1Q2c80Z6H75VK9l1d3KZuoiWoF1s73R7ZAM+CWSrR+S5h+3AhYubDKPa/af+Lnlqe6ocVTqQPYaaRz25/cLBg6pgbdh18Ru6h3ljG2KiysyXeuoEoM5xVYtdIW7l9NeKDpGbZPAOqywXUpK+UCGjumIl7c48KCTIYcdtolnEbfVNBh0LRuftcVI+uF9cvQ0XacaNbgkYJYCjv4VR/n58EJ1b0c7tQBrVqMjDjIUKGhCMQqAeD3g75jeD60bBmVNPrq8RK+zH5VIa5eaBs3eitN98eVzd4b6UYTQd1QxLQZMrhQf4InRj39TZfGvQR5SXlLZQlweVHYkMps3IKbs3B3DCqlWCPUAnTAJBAG7HqWEYr5uEaKBawBSAx9jCQz00T+bp8KXpkOPzZCD6dfEfpHY6Rv6kmGJkiPUCb2hoX145HrS357G12+wDxKLN833oPVC0z
&lt;/syntaxhighlight&gt;

Once a key is acquired, its fingerprint can be shown using [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] to read from '''stdin'''.  This can be done directly with a pipe.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan server.example.org | ssh-keygen -l -f -
3072 SHA256:tQlw3vy325KrQibndP3gLS/YXUZjTLVA5yDFpg/Bb6I server.example.org (RSA)
256 SHA256:snnAtb/9csdy0BGhPjdg+VNWqN5bxCa/ge4C6zZ8muk server.example.org (ECDSA)
256 SHA256:agRZDZn8awhQ+tc19Ip/whkHoV33Ln2REO7v1kcYbdU server.example.org (ED25519)
512 SHA256:3Wdc6GbLIcc5mbuF2mhhokhARdMLuMK+ESRfJ+sM0QE server.example.org (MLDSA44-ED25519)
&lt;/syntaxhighlight&gt;

If there is more than one public key type is available from the server on the port polled, then [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] will fetch each of them.  If there is more than one key fed via '''stdin''' or a file, then [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] will process them in order.  Prior to OpenSSH 7.2 manual fingerprinting was a two step process, the key was read to a file and then processed for its fingerprint.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan -t ed25519 host.example.org &gt; key.pub
# host.example.org SSH-2.0-OpenSSH_6.8
$ ssh-keygen -lf key.pub                       
256 SHA256:ZmS+IoHh31CmQZ4NJjv3z58Pfa0zMaOgxu8yAcpuwuw host.example.org (ED25519)
&lt;/syntaxhighlight&gt;

Note that some output from [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] is sent to '''stderr''' instead of '''stdout'''.  

A hash, or fingerprint, can be generated manually with [http://linux.die.net/man/1/awk awk(1)], [http://linux.die.net/man/1/sed sed(1)] and [http://linux.die.net/man/1/xxd xxd(1)], on systems where they are found.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ awk '{print $2}' key.pub | base64 -d | md5sum -b | sed 's/../&amp;:/g; s/: .*$//'
$ awk '{print $2}' key.pub | base64 -d | sha256sum -b | sed 's/ .*$//' | xxd -r -p | base64 
&lt;/syntaxhighlight&gt;

It is possible to find all hosts from a file which have new or different keys from those in '''known_hosts''', if the host names are in clear text and not stored as hashes.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan -t ed25519,mldsa44-ed25519 -f ssh_hosts | \
  sort -u - ~/.ssh/known_hosts | \
  diff ~/.ssh/known_hosts -
&lt;/syntaxhighlight&gt;

====Using ssh-keyscan(1) with ssh_config(5)====

The utility [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] does not parse [http://man.openbsd.org/ssh_config.5 ssh_config(5)].  That is in part to keep the code base simple.  There are a lot of configuration options which would be complicated to implement, including but not limited to '''ProxyJump''', '''ProxyCommand''', '''Match''', '''BindInterface''', and '''CanonicalizeHostname'''&lt;ref name=&quot;keyscan&quot;&gt;{{cite mailing list |url=https://lists.mindrot.org/pipermail/openssh-unix-dev/2023-March/040605.html | title=Why does ssh-keyscan not use .ssh/config? |publisher=mindrot.org | access-date=2023-03-01 | date=2023-03-01 | mailing-list=OpenSSH UNIX-dev | first=Damien | last=Miller }}&lt;/ref&gt; .  Resolving host names via the client configuration file can be done by wrapping the utility in a short shell function:

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
my-ssh-keyscan() {
	for host in &quot;$@&quot; ; do
		ssh-keyscan $(ssh -G &quot;$host&quot; | awk '/^hostname/ {print $2}')
	done
}
&lt;/syntaxhighlight&gt;

That shell function uses the '''-G''' option of [http://man.openbsd.org/ssh.1 ssh(1)] to resolve each host name using [http://man.openbsd.org/ssh_config.5 ssh_config(5)] and then check the resulting host name for SSH keys.

===ASCII Art Visual Host Key===

An ASCII art representation of the key can be displayed along with the SHA256 base64 fingerprint: 

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -l -v -f key 
256 SHA256:BClQBFAGuz55+tgHM1aazI8FUo8eJiwmMcqg2U3UgWU www.example.org (ED25519)
+--[ED25519 256]--+
|o+=*++Eo         |
|+o .+.o.         |
|B=.oo.  .        |
|*B.=.o .         |
|= B *   S        |
|. .@ .           |
| +..B            |
|  *. o           |
| o.o.            |
+----[SHA256]-----+
&lt;/syntaxhighlight&gt;

In OpenSSH 6.7 and earlier the fingerprint is in MD5 hexadecimal form.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -l -v -f key 
2048 37:af:05:99:e7:fb:86:6c:98:ee:14:a6:30:06:bc:f0 www.example.net (RSA) 
+--[ RSA 2048]----+ 
|          o      | 
|         o .     | 
|        o o      | 
|       o +       | 
|   .  . S        | 
|    E ..         | 
|  .o.* ..        | 
|  .*=.+o         | 
|  ..==+.         | 
+-----------------+ 
&lt;/syntaxhighlight&gt;

==More on Verifying SSH Keys==

Keys on the client or the server can be verified against known good keys by comparing the base64-encoded SHA256 fingerprints.  

===Verifying Stray Client Keys===

Sometimes is is necessary to compare two uncertain key files to check if they are part of the same key pair.  However, public keys are more or less disposable.  So the easy way in such situations on the client machine is to just rename or erase the old, problematic, public key and replace it with a new one generated from the existing private key.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -y -f ~/.ssh/my_key_ed25519
&lt;/syntaxhighlight&gt;

But if the two parts must really be compared, it is done in two steps using [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  First, a new public key is re-generated from the known private key and used to make a fingerprint to '''stdout'''.  Next, the fingerprint of the unknown public key is generated for comparison.  In this example, the private key '''my_key_a_ed25519''' and the public key '''my_key_b_ed25519.pub''' are compared:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -y -f my_key_a_ed25519 | ssh-keygen -l -f -
$ ssh-keygen -l -f my_key_b_ed25519.pub
&lt;/syntaxhighlight&gt;

The result is a base64-encoded SHA256 checksum for each key with the one fingerprint displayed right below the other for easy visual comparison.  Older versions don't support reading from '''stdin''' so an intermediate file will be needed then.  Even older versions will only show an MD5 checksum for each key.  Either way, automation with a shell script is simple enough to accomplish but outside the scope of this book.

===Verifying Server Keys===

Reliable verification of a server's host key must be done when first connecting.  It can be necessary to contact the system administrator who can provide it out of band so as to know the fingerprint in advance and have it ready to verify the first connection.  

Here is an example of the server's Ed25519 key being read and its fingerprint shown as SHA256 base64:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -l -f /etc/ssh/ssh_host_ed25519_key.pub 
256 SHA256:bFzzouaWmE5HuZIv+YnGUYI2q06i6M43V+6jMU3LHpA root@server.example.org (ED25519)
&lt;/syntaxhighlight&gt;

And here the corresponding ECDSA key is read, but shown as an MD5 hexadecimal hash:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -E md5 -l -f /etc/ssh/ssh_host_ecdsa_key.pub
256 MD5:ed:d2:34:b4:93:fd:0e:eb:08:ee:b3:c4:b3:4f:28:e4 root@server.example.net (ECDSA)
&lt;/syntaxhighlight&gt;

Prior to 6.8, the fingerprint was expressed as an MD5 hexadecimal hash:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -l -f /etc/ssh/ssh_host_rsa_key.pub 
2048 MD5:e4:a0:f4:19:46:d7:a4:cc:be:ea:9b:65:a7:62:db:2c root@server.example.net (RSA)
&lt;/syntaxhighlight&gt;

It is also possible to use [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] to get keys from an active SSH server.  However, the fingerprints still needs to be verified out of band.  

====Warning: Remote Host Identification Has Changed!====

If a server's key does not match what the client finds has been recorded in either the system's or the local account's '''authorized_keys''' files, then the client will issue a warning along with the fingerprint of the suspicious key.  

&lt;pre&gt;
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ED25519 key sent by the remote host is
SHA256:bFzzouaWmE5HuZIv+YnGUYI2q06i6M43V+6jMU3LHpA.
Please contact your system administrator.
Add correct host key in /home/fred/.ssh/known_hosts to get rid of this message.
Offending ED25519 key in /home/fred/.ssh/known_hosts:11
Host key for server.example.org has changed and you have requested strict checking.
Host key verification failed.
&lt;/pre&gt;

Three reasons for the warning are common.  

One reason is that the server's keys were replaced, often because the server's operating system was reinstalled without backing up the old keys.  Another reason can be when the system administrator has phased out deprecated or compromised keys.  However that can be planned better and if there is time to plan the migration, new keys can just be added to the server and have the clients use the '''UpdateHostKeys''' option so that the new keys are accepted if the old keys match.  A third situation is when the connection is made to the wrong machine, such as when the remote system changes IP addresses because of dynamic address allocation.  

In all three cases where the key has changed there is only one thing to do: contact the system administrator and verify the key.   Ask if the OpenSSH-server was recently reinstalled, or was the machine restored from an old backup?  Keep in mind that the system administrator may be you yourself in some cases. 

The case which is rather rare but serious enough that it should be ruled out for sure is that the wrong machine is part of a man-in-the-middle attack.

In all four cases, an authentic key fingerprint can be acquired by any method where it is possible to verify the integrity and origin of the message, for example via PGP-signed e-mail.  If physical access is possible, then use the console to get the right fingerprint.  Once the authentic key fingerprint is available, return to the client machine where you got the error and remove the old key from '''~/.ssh/known_hosts'''

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -R server.example.org
&lt;/syntaxhighlight&gt;

Then try logging in, but compare the key fingerprints first and proceed if and '''only''' if the key fingerprint matches what you received out of band.  If the key fingerprint matches, then go through with the login process and the key will be automatically added.  If the key fingerprint does not match, stop immediately and figure out what you are connecting to.  It would be a good idea to get on the phone, a real phone not a computer phone, to the remote machine's system administrator or the network administrator.

===Multiple Keys for a Host, Multiple Hosts for a Key in known_hosts===
 
Multiple host names or IP addresses can use the same key in the '''known_hosts''' file by using pattern matching or simply by listing multiple systems for the same key.  That can be done in either the global list of keys in '''/etc/ssh/ssh_known_hosts''' and the local, account-specific lists of keys in each account's '''~/.ssh/known_hosts''' file.  Labs, computational clusters, and similar pools of machines can make use of keys in that way.  Here is a key shared by three specific hosts, identified by name, one host per line:
&lt;pre&gt;
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
server2 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
server3 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
&lt;/pre&gt;
Or a range can be specified by using globbing to a limited extent in either '''/etc/ssh/ssh_known_hosts''' or '''~/.ssh/known_hosts'''.
&lt;pre&gt;
172.19.40.* ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
&lt;/pre&gt;
Conversely, a pool of servers might have multiple keys for the same address.  In that case, it is necessary to make multiple entries in either '''/etc/ssh/ssh_known_hosts''' or '''~/.ssh/known_hosts''' for each key.
&lt;pre&gt;
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBrsIIaDl/bJ40vyprvF+HYAq+kE2jWUsOt+WqIheaBw fred@desk.example.org
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIC2CgwWTPH/qZDeHmW7ZUea18wa9As7Txq3P5dXCfoXj fred@desk.example.org 
&lt;/pre&gt;
Thus in order to get a pool of servers to share a pool of keys, each server-key combination must be added manually to the '''known_hosts''' file:
&lt;pre&gt;
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBrsIIaDl/bJ40vyprvF+HYAq+kE2jWUsOt+WqIheaBw fred@desk.example.org
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIC2CgwWTPH/qZDeHmW7ZUea18wa9As7Txq3P5dXCfoXj fred@desk.example.org 

server2 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAICPSs4OR2LT89mv2tM4TKqeVhh4XvoLQ77MSBmjyrMGm fred@desk.example.org
server2 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIHChTzAoJr53A7VP1BdMHqLTFK5cz/2Vc065+VcpP4VA fred@desk.example.org
server2 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIHP+4BvU4DzwYQgznARxx/qyBWmu49PAywHwDRgslRaM fred@desk.example.org
&lt;/pre&gt;

Though upgrading to certificates might be a more appropriate approach that manually updating lots of keys.

===Another way of Dealing with Dynamic (roaming) IP Addresses===
It is possible to manually point to the right key using '''HostKeyAlias''' either as part of [http://man.openbsd.org/ssh_config.5 ssh_config(5)]  or as a runtime parameter.  Here the key for machine ''Foobar'' is used to connect to host 192.168.11.15

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -o StrictHostKeyChecking=accept-new \
      -o HostKeyAlias=foobar   \
      192.168.11.15
&lt;/syntaxhighlight&gt;
This is useful when DHCP is not configured to try to keep the same addresses for the same machines over time or when using certain stdio forwarding methods to pass through intermediate hosts.

===Host Key Update and Rotation in known_hosts===

A protocol extension to rotate weak public keys out of '''known_hosts''' has been in OpenSSH from version 6.8&lt;ref name=&quot;djm_rotation&quot;&gt;
{{cite web
| title=Key rotation in OpenSSH 6.8+ 
| author=Damien Miller
| url=http://blog.djm.net.au/2015/02/key-rotation-in-openssh-68.html
| date=2015-02-01
| publisher=DJM's Personal Weblog
| accessdate=2016-03-05
}}
&lt;/ref&gt; and later.  With it the server is able to inform the client of all its host keys and update '''known_hosts''' with new ones when at least one trusted key already known.  This method still requires the private keys be available to the server &lt;ref name=&quot;djm_rotation_redux&quot;&gt;
{{cite web
| title=Hostkey rotation, redux 
| author=Damien Miller
| url=http://blog.djm.net.au/2015/02/hostkey-rotation-redux.html
| date=2015-02-17
| publisher=DJM's Personal Weblog
| accessdate=2016-03-05
}}
&lt;/ref&gt; so that proofs can be completed.  In [http://man.openbsd.org/ssh_config.5 ssh_config(5)], the directive '''UpdateHostKeys''' specifies whether the client should accept updates of additional host keys from the server after authentication is completed and add them to '''known_hosts'''.  A server can offer multiple keys of the same type for a period before removing the deprecated key from those offered, thus allowing an automated option for rotating keys as well as for upgrading from weaker algorithms to stronger ones.  See also [https://datatracker.ietf.org/doc/html/rfc4819 RFC 4819: Secure Shell Public Key Subsystem] about key management standards.

==Converting Between SSH Key Formats==

OpenSSH has its own format for keys which it uses by default when new keys are made.  However, other SSH clients and servers may use other formats such as [https://www.rfc-editor.org/rfc/rfc4716 RFC 4716], [https://www.rfc-editor.org/rfc/rfc5958 PKCS8], or [https://www.rfc-editor.org/rfc/rfc1421 PEM].  Any of these can be converted to the default OpenSSH format by [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  The default to format to try to convert from is RFC 4716.  The utility [https://linux.die.net/man/1/puttygen puttygen(1)] makes keys in that format for [https://linux.die.net/man/1/putty putty(1)] and they need conversion when used with OpenSSH's server.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -i -f /var/tmp/key_public.ppk
&lt;/syntaxhighlight&gt;

However, you can use the '''-m''' option to specify either that format explicitly or else choose another one to convert from.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -i -m RFC4716 -f /var/tmp/key_public.ppk
$ ssh-keygen -i -m PKCS8 -f /var/tmp/key_public.ppk
&lt;/syntaxhighlight&gt;

Both examples above are for importing public keys into OpenSSH's own format.  

By default OpenSSH will write newly-generated keys in its own format, so the '''-m''' option is obligatory to produce public keys in another format.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -e -m PKCS8 -f ~/.ssh/key.pub
&lt;/syntaxhighlight&gt;

It is not yet possible to export private keys from the OpenSSH format to one of the other formats using the '''-e''' option.  Even if a private key is specified as input, a public key is produced:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -e -m RFC4716 -f ~/.ssh/key
&lt;/syntaxhighlight&gt;

Not all key types are supported by all key formats.  

It is also possible to use export to display the key pair as a traditional hex dump.
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -e -m hexdump -f ~/.ssh/key
Enter passphrase for &quot;key&quot;: 
Public ED25519 key:
buffer len = 51
0000: 00 00 00 0b 73 73 68 2d 65 64 32 35 35 31 39 00  ....ssh-ed25519.
0016: 00 00 20 b0 c5 cc 2c cb d8 8b 8d 75 80 eb e6 e9  .. ...,....u....
0032: 2c f4 36 08 7b 5b ad ad 0b 54 4f 7f 21 9d 1b e8  ,.6.{[...TO.!...
0048: 9e e0 32                                         ..2

Private ED25519 key:
buffer len = 119
0000: 00 00 00 0b 73 73 68 2d 65 64 32 35 35 31 39 00  ....ssh-ed25519.
0016: 00 00 20 b0 c5 cc 2c cb d8 8b 8d 75 80 eb e6 e9  .. ...,....u....
0032: 2c f4 36 08 7b 5b ad ad 0b 54 4f 7f 21 9d 1b e8  ,.6.{[...TO.!...
0048: 9e e0 32 00 00 00 40 e1 c3 a2 4d d9 89 49 72 9b  ..2...@...M..Ir.
0064: 86 72 6c 07 17 1b 40 4f 62 50 62 45 4f 4c cf cf  .rl...@ObPbEOL..
0080: 57 8b 9d c0 04 8f 9b b0 c5 cc 2c cb d8 8b 8d 75  W.........,....u
0096: 80 eb e6 e9 2c f4 36 08 7b 5b ad ad 0b 54 4f 7f  ....,.6.{[...TO.
0112: 21 9d 1b e8 9e e0 32                             !.....2
&lt;/syntaxhighlight&gt;

&lt;noinclude&gt;

== References ==
{{reflist}}
{{OpenSSH/TOC|mini}}
&lt;/noinclude&gt;
{{BookCat}}
{{status|100%}}</text>
      <sha1>8ziips6fmbs1ioyspx5i7pxpy5u1f08</sha1>
    </revision>
    <revision>
      <id>4676716</id>
      <parentid>4676715</parentid>
      <timestamp>2026-10-18T09:23:16Z</timestamp>
      <contributor>
        <username>Larsnooden</username>
        <id>430753</id>
      </contributor>
      <comment>Add subsection for Disadvantages of Keys, in Contrast to Certificates</comment>
      <origin>4676716</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="83370" sha1="df3sgvf4iisvtqbh69vpbd9svt6y982" xml:space="preserve">&lt;noinclude&gt;{{simple chapter navigation|previous=File Transfer with SFTP|next=Certificate-based Authentication}}&lt;/noinclude&gt;
&amp;nbsp;

Authentication keys can improve efficiency, if done properly.  As a bonus advantage, the passphrase and private key never leave the client&lt;ref name=&quot;RFC4252§7&quot;&gt;{{cite web |url=https://tools.ietf.org/html/rfc4252#section-7 |title=The Secure Shell (SSH) Authentication Protocol |publisher=IETF |year=2006| accessdate=2015-05-06}}&lt;/ref&gt;.  Key-based authentication is generally recommended for outward facing systems so that password authentication can be turned off.  

==Key-based authentication==

OpenSSH can use public key cryptography for authentication.  In public key cryptography, encryption and decryption are asymmetric.  The keys are used in pairs, a public key to encrypt and a private key to decrypt.  The [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] utility can make RSA, Ed25519, MLDSA44-Ed25519, ECDSA, Ed25519-SK, or ECDSA-SK keys for authenticating.  Even though DSA keys can still be made, being exactly 1024 bits in size, they are no longer recommended and should be avoided.  RSA keys are allowed to vary from 1024 bits on up.  The default is now 3072.  However, there is only limited benefit after 2048 bits and that makes elliptic curve algorithms preferable.  ECDSA can be 256, 384 or 521 bits in size.  Ed25519, Ed25519-SK, and ECDSA-SK keys each have a fixed length of 256 bits.  Shorter keys are faster, but less secure.  Longer keys are much slower to work with but provide better protection, up to a point.  

Keys can be named to help remember what they are for.  Because the key files can be named anything it is possible to have many keys each named for different services or tasks.  The comment field at the end of the public key can also be useful in helping to keep the keys sorted, if you have many of them or use them infrequently.  

The process of key-based authentication uses these keys to make a couple of exchanges using the keys to encrypt and decrypt some short message.  At the start, a copy of the client's public key is stored on the server and the client's private key is on the client, both stay where they are.  The private key never leaves the client.  As the client first contacts the server, the server responds by using the client's public key to encrypt a random number and return that encrypted random number as a challenge to the client.  The client responds to the challenge by using the matching private key to decrypt the message and extract the random number.  The client then makes an MD5 hash of the session ID along with the random number from the challenge and returns that hash to the server.  The server then makes its own hash of the session ID and the random number and compares that to the hash returned by the client.  If there is a match, the login is allowed.  If there is not a match, then the next of any public keys on the server registered as belonging to the same account is tried until either a match is found or all the keys have been tried or the maximum number of failures has been reached. &lt;ref name=&quot;How Key Challenges Work&quot;&gt;{{cite web | url=http://www.unixwiz.net/techtips/ssh-agent-forwarding.html#chal | title=An Illustrated Guide to SSH Agent Forwarding | author=Steve Friedl | date=2006-02-22 | accessdate=2013-04-27 | publisher=Unixwiz.net }}&lt;/ref&gt;

When an agent is used on the client side to manage authentication, the process is similar.  The difference is that [http://man.openbsd.org/ssh.1 ssh(1)] passes the challenge off to the agent which then calculates the response and passes it back to [http://man.openbsd.org/ssh.1 ssh(1)] which then passes the agent's response back to the server.  

===Basics of Public Key Authentication===

A matching pair of SSH keys, one public and one private, is needed for public key authentication.  The [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] utility is used to make such a key pair.  Out of that pair the public key must be properly stored on the remote host before using key-based authentication.  The default location for it is the designated '''authorized_keys''' file, usually one such file resides inside each remote user account.  The private key stays stored safely on the client.  

Once the keys have been prepared and the remote account configured, they can be used for login.  Before starting, there must already be an account on the remote system.  The details of doing that are outside of the scope of this book.  However, once you have a remote account, there are four steps to set up key-based authentication for it:

'''1''') Prepare a directory on the client (say a laptop or a desktop) where the keys will stay, if there isn't one already.  For example, if the '''.ssh''' directory is not on the client machine, create it and set the permissions correctly.  It is important that it not be writable by any account except its owner:
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ mkdir ~/.ssh/
$ chmod 0700 ~/.ssh/
&lt;/syntaxhighlight&gt;

'''2''') Create a key pair inside the designated directory.  The example here creates an Ed25519 key pair in the directory '''~/.ssh'''.  The option '''-t''' decides the key type and the option '''-f''' assigns the key file a name.  It is good to give key files descriptive names, especially if larger numbers of keys are managed.  Below, the public key will be named '''fred_example_org_ed25519.pub''' and the private key will be called '''fred_example_org_ed25519'''.  Lastly, the '''-C''' option is used to embed a descriptive comment inside the private key itself.  The comment is useful for figuring out later what the key is for when one has many keys or a lot of time has passed or both.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -t ed25519 -f ~/.ssh/fred_example_org_ed25519 \
        -C &quot;from fred's laptop to server.example.org&quot;
&lt;/syntaxhighlight&gt;

Be sure to enter a solid passphrase so that the private key gets encrypted using 128-bit AES.  That way the private key can only be read or used when the passphrase is given.  

Ed25519, Ed25519-SK, and ECDSA-SK keys have fixed lengths.  For RSA and ECDSA keys, the '''-b''' option sets the number of bits used for those kinds of keys.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -o -b 4096 -t rsa -f ~/.ssh/fred_example_org_rsa \
        -C &quot;from fred's laptop to server.example.org&quot;
&lt;/syntaxhighlight&gt;

Since 6.5 a new private key format is available using a [http://man.openbsd.org/bcrypt.3 bcrypt(3)] key derivative function (KDF) to better protect keys at rest.  This new format is always used for Ed25519 keys, and sometime in the future will be the default for all keys.  But for right now it may be requested when generating or saving existing keys of other types via the '''-o''' option in [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  

Details of the new format are found in the source code in the file '''PROTOCOL.key'''.

'''3''') Get the keys to the right places.  Transfer only the public key to remote machine.  The following assume the default locations for the authorized keys as specified in the server's configuration file by the '''AuthorizedKeysFile''' directive.  

'''3a''') If the utility &lt;code&gt;ssh-copy-id&lt;/code&gt; exists, and if password authentication is allowed, then it can be used to put the public key into place on the remote system.  The ''.pub'' is optional here, the script will figure it out if omitted. 
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-copy-id -i ~/.ssh/fred_example_org_ed25519 fred@server.example.org
&lt;/syntaxhighlight&gt;

If that script was successful in transferring the public key, then go on to step 4 below and test the key.  If not, then try transferring the public key manually as described in step 3b next.

'''3b''') Or the public key can be put in place manually on the remote machine.  For that the remote '''.ssh''' directory is needed, and within that a special file to store the public keys, the default file name is '''authorized_keys'''.  If either the '''authorized_keys''' file or '''.ssh''' directory do not exist on the remote machine, they need to be created.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ mkdir -m 700 ~/.ssh/
$ touch ~/.ssh/authorized_keys
$ chmod 0600 ~/.ssh/authorized_keys
$ nano -w ~/.ssh/authorized_keys
&lt;/syntaxhighlight&gt;

Then any editor which does not wrap long lines can be used to add the public key.  However the '''authorized_keys''' file is edited to add the key, the key itself must be in the file whole and unbroken on a single  line.  For example, [http://linux.die.net/man/1/nano nano(1)] can be started with the '''-w''' option to prevent wrapping of long lines.  (Another way to set line wrapping permanently in [http://linux.die.net/man/1/nano nano(1)] is by editing [http://linux.die.net/man/5/nanorc nanorc(5)].)  

If the key pair is not already on the client, transfer both the public and private keys there.  It is usually best to keep both the public and private keys together in the directory '''~/.ssh/''', though the public key is not always needed on the client after this step and could even be regenerated if it is ever needed again.  

'''4''') Test the keys

While remaining logged in via the first terminal, use the client system to open another window and in it start another SSH session and try authenticating to the remote machine from the client using the private key.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -i ~/.ssh/fred_example_org_ed25519 -l fred server.example.org
&lt;/syntaxhighlight&gt;

The option '''-i''' tells [http://man.openbsd.org/ssh.1 ssh(1)] which private key to try.  
Only after verifying that the key-based authentication works should you close the original window.  

It is possible to make permanent shortcuts on the client using [http://man.openbsd.org/ssh_config.5 ssh_config(5)], explained further below, once key-based authentication is working.  In particular, see the '''IdentityFile''',  '''IdentitiesOnly''', and '''AddKeysToAgent''' configuration directives, to name three.  

It is also a good idea to turn off password authentication, if and only if key-based authentication is setup for all the necessary remote accounts.  

➥ '''Troubleshooting of Key-based Authentication''':

If the server refuses to accept the key and fails over to the next authentication method (e.g.: &quot;Server refused our key&quot;), then there are several possible mistakes to look for on the server side.  

One of the most common errors is that the file and directory permissions are wrong.  The authorized keys file must be owned by the user in question and not be group writable.  Nor may the key file's directory be group or world writable.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ chmod u=rwx,g=rx,o= ~/.ssh
$ chmod u=rw,g=,o=  ~/.ssh/authorized_keys 
&lt;/syntaxhighlight&gt;

Another mistake that can happen is if the key inside the '''authorized_keys''' file on the remote host is broken by line breaks or has other whitespace in the middle.  That can be fixed by joining up the lines and removing the spaces or by recopying the key more carefully.  

And, though it should go without saying, the halves of the key pair need to match.  The public key on the server needs to match the private key held on the client.  If the public key is lost, then a new one can be generated with the '''-y''' option, but not the other way around.  If the private key is lost, then the public key should be erased as it is no longer of any use.  If many keys are in use for an account, it might be a good idea to add comments to them.  On the client, it can be a good idea to know which server the key is for, either through the file name itself or through the comment field.  A comment can be added using the '''-C''' option.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -t ed25519 -f ~/.ssh/fred_example_org_ed25519 -C &quot;web server mirror&quot;
&lt;/syntaxhighlight&gt;

On the server, it can be important to annotate which client they key is from if there is more than one public key there in an account.  There the comment can be added to the authorized keys file on the server in the last column if a comment does not already exist.  Again, the format of the authorized keys file is given in the manual page for [http://man.openbsd.org/sshd.8 sshd(8)] in the section &quot;AUTHORIZED_KEYS FILE FORMAT&quot;.  If the keys are not labeled they can be hard to match, which might or might not be what you want.  

====Associating Keys Permanently with a Server====

A key can be specified at run time, but to save retyping the same paths again and again, the '''Host''' directive in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] can apply specific settings to a target host.  In this case, by changing '''~/.ssh/config''' it is possible to assign particular keys to be tried automatically whenever making a connection to that specific host.  After adding the following lines to '''~/.ssh/config''', all that's needed is to type &lt;code&gt;ssh ''web1''&lt;/code&gt; to connect with the key for that server.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host web1
	Hostname 198.51.100.32
	IdentitiesOnly yes
	IdentityFile /home/fred/.ssh/web_key_ed25519
&lt;/syntaxhighlight&gt;

The '''~/.ssh/config''' below uses different keys for ''server'' versus ''server.example.org'',  regardless whether they resolve to the same machine.   This is possible because the host name argument given to [http://man.openbsd.org/ssh.1 ssh(1)] is not converted to a canonicalized host name before matching.

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host server
	IdentitiesOnly yes
	IdentityFile /home/fred/.ssh/key_a_ed25519

Host server.example.org
	IdentitiesOnly yes
	IdentityFile /home/fred/.ssh/key_b_ed25519
&lt;/syntaxhighlight&gt;

In this example the shorter name is tried first, but of course less ambiguous shortcuts can be made instead.  The configuration file gets parsed on a first-match basis.  So the most specific rules go at the beginning and the most general rules go at the end.  

====Encrypted Home Directories====

When using encrypted home directories the keys must be stored in an unencrypted directory.  That means somewhere outside the actual home directory which means [http://man.openbsd.org/sshd.8 sshd(8)] needs to be configured appropriately to find the keys in that special location.  

Here is one method for solving the access problem.  Each user is given a subdirectory under '''/etc/ssh/keys/''' which they can then use for storing their '''authorized_keys''' file.  This is set in the server's configuration file '''/etc/ssh/sshd_config'''

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthorizedKeysFile      /etc/ssh/keys/%u/authorized_keys
&lt;/syntaxhighlight&gt;

Setting a special location for the keys opens up more possibilities as to how the keys can be managed and multiple key file locations can be specified if they are separated by whitespace.  The user does not have to have write permissions for the '''authorized_keys''' file.  Only read permission is needed to be able to log in.  But if the user is allowed to add, remove, or change their keys, then they will need write access to the file to do that.  

One symptom of having an encrypted home directory is that key-based authentication only works when you are already logged into the same account, but fails when trying to make the first connection and log in for the first time.

Sometimes it is also necessary to add a script or call a program from '''/etc/ssh/sshrc''' immediately after authentication to decrypt the home directory.

====Passwordless Login====

One solution for passwordless logins is to still have a passphrase and work with an authentication agent in conjunction with a single-purpose key.  Most desktop environments launch an SSH agent automatically these days.  It will be visible in the '''SSH_AUTH_SOCK''' environment variable if it is.  On accounts with an agent, [http://man.openbsd.org/ssh-add.1 ssh-add(1)] can load private keys into an available agent.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-add ~/.ssh/fred_example_org_ed25519
&lt;/syntaxhighlight&gt;

Thereafter, the client will automatically check the agent for the key when appropriate.  If there are many keys in the agent, it will become necessary to set '''IdentitiesOnly'''.  See the above section on using '''~/.ssh/config''' for that.  See [[OpenSSH/Cookbook/Public_Key_Authentication#Key-based_Authentication_Using_an_Agent|Key-based Authentication Using an Agent]] below.  

Another, riskier, way of allowing passwordless logins is to follow the steps above, but simply do not enter a passphrase when asked for one while creating the key.  Note that using keys that lack a passphrase is very risky, so the key files should be very well protected and kept track of, and ideally locked down with a '''command=''' option or '''ForceCommand''' directive on the server.  That includes those keys which will only be used as single-purpose keys as described below.  

Timely key rotation becomes especially important.  In general, it is not a good idea to make a key without a passphrase.

====Requiring Both Keys and a Password====

While users should have strong passphrases for their keys, there is no way to enforce or verify that.  Indeed, since neither the private key nor its the passphrase ever leave the client machine there is nothing that the server can do to have any influence over that.  Instead, it is possible to require both a key and a password.  Starting with OpenSSH 6.2, it is possible for the server to require multiple authentication methods for login using the '''AuthenticationMethods''' directive.   
&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthenticationMethods publickey,password
&lt;/syntaxhighlight&gt;

This example from [http://man.openbsd.org/sshd_config.5 sshd_config(5)] requires that users first authenticate using a key and it only queries for a password if the key succeeds.  Thus with that configuration it is not possible to get to the system password prompt without first authenticating with a valid key.  Changing the order of the arguments changes the order of the authentication methods.

====Requiring Two or More Keys====

Since OpenSSH 6.8, the server now remembers which public keys have been used for authentication and refuses to accept previously-used keys.  This allows a set up requiring that users authenticate using two different public keys, maybe one in the file system and the other in a hardware token. 

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthenticationMethods publickey,publickey
&lt;/syntaxhighlight&gt;

The '''AuthenticationMethods''' directive, whether for keys or passwords, can also be set on the server under a '''Match''' directive to apply only to certain groups or situations.

====Requiring Certain Key Types For Authentication====

Also since OpenSSH 6.8, the '''PubkeyAcceptedKeyTypes''' directive, later changed to '''PubkeyAcceptedAlgorithms''', can specify which key algorithms are accepted for authentication.  Those not in the comma-separated pattern list are not allowed.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
PubkeyAcceptedAlgorithms ssh-ed25519*,ssh-rsa*,ecdsa-sha2*,sk-ssh-ed25519*,sk-ecdsa-sha2*
&lt;/syntaxhighlight&gt;

Either the actual key types or a pattern can be in the list.  Spaces are not allowed in the pattern list.  The exact list of key types supported for authentication can be found by the '''-Q''' option using the client.  The following two lines are equivalent.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -Q key-sig | sort

$ ssh -Q PubkeyAcceptedAlgorithms | sort
&lt;/syntaxhighlight&gt;

For host-based authentication, it is the '''HostbasedAcceptedAlgorithms''' directive which determines the key types which are allowed for authentication.

===Key-based Authentication Using the AuthorizedKeysCommand Directive===

It is possible to use a program or script to look up public keys rather than keeping them in a static file or files.  Any command called by the '''AuthorizedKeysCommand''' directive needs to either produce a syntactically correct public key while returning the exit code for a successful run or else return the exit code for failure.  The string sent to '''stdout''' will then be processed as part of the authentication work flow.  

Here is a shell script&lt;ref name=&quot;janpietmens&quot;&gt;{{cite web |url=https://jpmens.net/2025/03/25/authorizedkeyscommand-in-sshd/ |title=SSH keys from a command: sshd's AuthorizedKeysCommand directive |accessdate=2025-04-04 |date=2025-03-25 | author=Jan-Piet Mens }}&lt;/ref&gt; at its simplest, without constraints, demonstrating a public key lookup:

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
#!/bin/sh

echo &quot;ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIKs/UouletvojgB1YeRZ4MY6iRblQ2ERDuNhQO4tOvdL&quot;

exit 0
&lt;/syntaxhighlight&gt;

For authentication to succeed, the script must return exit code 0  (success) after sending the syntactically correct matching public key to '''stdout'''.  For the SSH daemon to even run the script in the first place, the script must have the correct file and directory permissions.

Both the '''AuthorizedKeysCommandUser''' directive and '''AuthorizedKeysCommand''' must be used together.  The former designates which account the script or program use when run.  If set to ''none'' or if it does not refer to a valid account then [http://man.openbsd.org/sshd sshd(8)] will just ignore the command.  If '''AuthorizedKeysCommand''' is set, and '''AuthorizedKeysCommandUser''' is left empty or missing, then [http://man.openbsd.org/sshd sshd(8)] won't even run when invoked.  The error will be:

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
AuthorizedKeysCommand set without AuthorizedKeysCommandUser
&lt;/syntaxhighlight&gt;

The '''AuthorizedKeysFile''' is always tried first when it is present in the server configuration.  The '''AuthorizedKeysCommand''' directive will not even be tried when the authorized keys file can provide a relevant key first.  

====A More Detailed Example Using the AuthorizedKeysCommand Directive====

By default the user name trying to log in is passed to the script when no tokens or arguments are provided.  Whether or how that information is used is up to the script.  The SSH daemon can also pass any combination of the tokens described in the TOKENS section of [http://man.openbsd.org/sshd_config sshd_config(5)] into the program or script being called.  Furthermore, the program or script can even be a front end for a database, such as OpenLDAP, or any similar system, as long as '''stdout''' produces a public key.  

Below is a more detailed example which uses a local script named '''keyfinder''' run with the account '''keys''' to look up the a public key for certain accounts.  First in [http://man.openbsd.org/sshd_config sshd_config(5)] the two directives:

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthorizedKeysCommand /usr/local/sbin/keyfinder %U
AuthorizedKeysCommandUser keys
&lt;/syntaxhighlight&gt;

The script below is only a demonstration and a more complex program can call databases or do advanced lookups or heuristics:  

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
#!/bin/sh

set -e

case $1 in
        &quot;1000&quot;)
                echo &quot;ssh-ed25519 AAAAC3NzaC1lZDIE5AAAAIK89...UT9hz&quot;
                ;;

        &quot;1001&quot;)
                echo &quot;restrict ssh-ed25519 AAAAC3NzaC1lZDI1NTAAIBvGx...Y0zxV&quot;
                ;;

        &quot;1002&quot;)
                echo &quot;command=\&quot;/usr/libexec/sftp-server\&quot; ssh-ed25519 AAAAC3NzaC1lZDI1TE5AIPSyY...cPTg3&quot;
                ;;

        *)
                exit 1
                ;;
   
esac

exit 0
&lt;/syntaxhighlight&gt;

The '''AuthorizedKeysCommand''' scripts or programs can return any correctly formatted public key to '''stdout''' for consideration in the authentication process.  That includes adding constraints to the keys.  Above, the account with the UID 1000 has no constraints, while the account with UID 1001 is quite constrained.  Finally, the account with the UID 1002 can only access the SFTP service.  See the section &quot;AUTHORIZED_KEYS FILE FORMAT&quot; in [http://man.openbsd.org/sshd sshd(8)] for the full set of possibilities.

===Key-based Authentication Using an Agent===

When an authentication agent, such as [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)], is going to be used, it should generally be started at the beginning of a session and used to launch the login session or X-session so that the environment variables pointing to the agent and its UNIX-domain socket are passed to each subsequent shell and process.  Many desktop distros do this automatically upon login or startup.  

Starting an agent entails setting a pair of environment variables:

* SSH_AGENT_PID : the process id of the agent
* SSH_AUTH_SOCK : the filename and full path to the UNIX-domain socket

The various SSH and SFTP clients find these variables automatically and use them to contact the agent and try when authentication is needed.   However, it is mainly SSH_AUTH_SOCK which is ever used.  If the shell or desktop session was launched using [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)], then these variables are already set and available.  If they are not available, then it is necessary to either set the variables manually inside each shell or for each application in order to use the agent or else to point to the agent's socket using the directive '''IdentityAgent''' in the client's configuration file.  

Once an agent is available, a relevant private key needs to be loaded before the agent can be used.  Once in the agent the private key can then be used many times.  Private keys are loaded into an agent with [http://man.openbsd.org/ssh-add.1 ssh-add(1)].
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-add /home/fred/.ssh/mykey_ed25519
Identity added: /home/fred/.ssh/mykey_ed25519 (/home/fred/.ssh/mykey_ed25519)
&lt;/syntaxhighlight&gt;

Keys stay in the agent for as long as it is running unless specified otherwise.  A timeout can be set either with the '''-t''' option when starting the agent itself or when actually loading the key using [http://man.openbsd.org/ssh-add.1 ssh-add(1)].  In either case, the '''-t''' option will set a timeout interval, after which the key will be purged from the agent.
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-add -t 1h30m /home/fred/.ssh/mykey_ed25519
Identity added: /home/fred/.ssh/mykey_ed25519 (/home/fred/.ssh/mykey_ed25519)
Lifetime set to 5400 seconds
&lt;/syntaxhighlight&gt;

The option '''-l''' will list the fingerprints of all of the identities in the agent.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-add -l                                    
256 SHA256:77mfUupj364g1WQ+O8NM1ELj0G1QRx/pHtvzvDvDlOk mykey for task x (ED25519)
3072 SHA256:7unq90B/XjrRbucm/fqTOJu0I1vPygVkN9FgzsJdXbk myotherkey rsa for task y (RSA)
&lt;/syntaxhighlight&gt;

It is also possible to remove individual identities from the agent using '''-d''' which will remove them one at a time if identified by file name, but only if the file name is given and without the file name of the private key to be remove, '''-d''' will fail silently.  Using '''-D''' instead will remove all of them at once without needing to specify any by name.  

By default [http://man.openbsd.org/ssh-add.1 ssh-add(1)] uses the agent connected via the socket named in the environment variable '''SSH_AUTH_SOCK''', if it is set.  Currently, that is its only option.  However, for [http://man.openbsd.org/ssh.1 ssh(1)] an alternative to using the environment variable is the client configuration directive '''IdentityAgent''' which tells the SSH clients which socket to use to communicate with the agent.  If both the environment variable and the configuration directive are available at the same time, then the value in '''IdentityAgent''' takes precedence over what's in the environment variable.  '''IdentityAgent''' can also be set to ''none'' to prevent the connection from trying to use any agent at all.  

The client configuration directive '''AddKeysToAgent''' can also be useful in getting keys into an agent as needed.  When set, it automatically loads a key into a running agent the first time the key is called for if it is not already loaded.  Likewise the '''IdentitiesOnly''' directive can ensure that the relevant key is offered on the first try.  Rather than typing these out whenever the client is run, they can be added to '''~/.ssh/config''' and thereby added automatically for designated host connections.  

====Agent Forwarding====

Agent forwarding is one means of passing through one or more intermediate hosts.  However, the '''-J''' option for '''ProxyJump''' would be a safer option.  See [[OpenSSH/Cookbook/Proxies_and_Jump_Hosts#Jump_Hosts_--_Passing_Through_a_Gateway_or_Two | Passing Through a Gateway or Two]] in the section on jump hosts about that.  With agent forwarding, intermediate machines forward challenges and responses back and forth between the client and the final destination.  This comes with some risks but eliminates the need for using passwords or holding keys on any of these intermediate machines.  

A main advantage of agent forwarding is that the private key itself is not needed on any remote machine, thus hindering unwanted file system access to it. &lt;ref name=&quot;OpenSSH key management, Part 3&quot;&gt;{{cite web | url=http://www.ibm.com/developerworks/library/l-keyc3/ | title=Common threads: OpenSSH key management, Part 3 | author=Daniel Robbins | publisher=IBM | date=2002-02-01 | accessdate=2013-04-27}}&lt;/ref&gt;  Another advantage is that the actual agent to which the user has authenticated does not go anywhere and is thus less susceptible to analysis.  

One risk with agents is that they can be re-used to tailgate in if the permissions allow it.  Keys cannot be copied this way, but authentication is possible when there are incorrect permissions.  Note that disabling agent forwarding does not improve security unless users are also denied shell access, as they can always install their own forwarders.

The risks of agent forwarding can be mitigated by confirming each use of a key by adding the '''-c''' option when adding the key to the agent.  This requires the SSH_ASKPASS variable be set and available to the agent process, but will generate a prompt on the host running the agent upon each use of the key by a remote system.  So if passing through one or more intermediate hosts, it is usually better to instead have the SSH client use stdio forwarding with '''-W''' or '''-J'''.

On the client side agent forwarding is disabled by default and so if it is to be used it must be enabled explicitly.  Put the following line in  [http://man.openbsd.org/ssh_config.5 ssh_config(5)] to enable agent forwarding for a particular server:
&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
        Host gateway.example.org
        ForwardAgent yes
&lt;/syntaxhighlight&gt;

On the server side the default configuration files allow authentication agent forwarding, so to use it, nothing needs to be done there, just on the client side.  However, again, it would be preferable to take a look at '''ProxyJump''' instead.  

=====New Style SSH Agent Destination Constraints=====

Using the '''ProxyJump''' option instead of authentication agent forwarding is still the best way to pass through other systems while avoiding the exposure of private keys, something which could happen forwarding agents.  However, from 8.9 onward, [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)] will allow the agent to limit which hosts it will use for authentication as specified by [http://man.openbsd.org/ssh-add.1 ssh-add(1)] using the '''-h''' option.  These constraints have been added through two agent protocol extensions and a modification to the public key authentication protocol.  This feature may evolve, but for now the result is such that keys for account authentication can be loaded into the agent in four ways:

* no limits on forwarding (not recommended)
* local use only, these will not get forwarded
* forwarding, but only to specific remote hosts
* forwarding to specific remote hosts via specified routes

The intent is that the restrictions fail safely so that they do not allow authentication when one or more hosts in the route lack the needed protocol features.  The destinations and routes cannot be modified once the keys are loaded, but multiple routes to the same destination can be loaded and the routes can be any number of hops.  If the routes need changing, then the key must be reloaded into the agent with the new route or routes.  

The general default for the client is to keep keys in the agent for local use only.  However, that can be enforced explicitly by adding the '''-a''' option when starting the client or else setting the '''ForwardAgent''' directive in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] to 'no' in the relevant configuration block.  

In order to load keys for unlimited forwarding, which is not the best idea, just add them using [http://man.openbsd.org/ssh-add.1 ssh-add(1)] as normal.  Then use the '''-A''' option with the client or set the '''ForwardAgent''' directive in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] to 'yes' in the relevant configuration block.  

In order to limit keys for connection only to a specific remote host, or to load keys for connection to a specific remote host with forwarding via one or more intermediate hosts, use the '''-h''' option when loading keys into the agent.  Here the one key may be used only to connect to the specific destination:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-agent -h server.example.org server.key.ed25519
&lt;/syntaxhighlight&gt;

If an intermediate system is passed through, the best way is to use '''ProxyJump''' which is the '''-J''' option for the SSH Client.  If agent forwarding must be allowed then the tightest way is to constrain which systems may use the keys, again using the '''-h''' option.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-agent -h middle.example.org -h &quot;middle.example.org&gt;server.example.org&quot; server.key.ed25519
&lt;/syntaxhighlight&gt;

Multiple steps can be included, even multiple routes.  They just have to be enumerated explicitly, though patterns may still be used for the destination hosts as well as specific names.  Each host in the chain must support these protocol extensions for the connection to complete.  

Any keys designated for forwarding are unusable for authentication on any other hosts than those which have been explicitly identified for forwarding.  These permitted hosts are identified by host key or host certificate from the '''known_hosts''' file or another file designated by the '''-H''' option when loading the key with [http://man.openbsd.org/ssh-add.1 ssh-add(1)].  If '''-H''' is not used at the time the keys are loaded into the agent, then the default known hosts file(s) will be used: '''~/.ssh/known_hosts''', '''/etc/ssh/ssh_known_hosts''', '''~/.ssh/known_hosts2''', and '''/etc/ssh/ssh_known_hosts2'''.

In the case of keys, the '''known_hosts''' list must be maintained conscientiously &lt;ref name=&quot;ssh-agent-restrictions&quot;&gt;{{ cite web | author=Damien Miller|url=https://www.openssh.org/agent-restrict.html | title=SSH agent restriction | publisher=OpenSSH | date=2021-12-16|accessdate=2022-03-06}}&lt;/ref&gt;, perhaps with the help of the '''UpdateHostkeys''' and '''CanonicalizeHostname''' client configuration directives.  Use of certificates requires the agent to only need to be aware of the Certificate Authority (CA).

Again, see [[OpenSSH/Cookbook/Proxies_and_Jump_Hosts#Jump_Hosts_--_Passing_Through_a_Gateway_or_Two | Passing Through a Gateway or Two]] in the section on jump hosts about a way to pass through one or more intermediate machines without needing to forward an SSH agent.

=====Old Style, Almost Safe SSH Agent Forwarding=====

The best way to pass through one or more intermediate hosts is to use the '''ProxyJump''' option instead of authentication agent forwarding and thereby not risking the exposure of any private keys.  If authentication agent forwarding must be used, then it would be advisable in the interest of following the principle of least privilege to forward an agent containing the minimum necessary number of keys.  There are several ways to solve that.  

In version 8.8 and earlier a partial solution is to make a one-off, ephemeral agent to hold just the one key or keys needed for the task at hand.  Another partial solution would be to set up a user-accessible service at the operating system level and then use [http://man.openbsd.org/ssh_config.5 ssh_config] for the rest.  

Automatically launching an ephemeral agent unique to each session can be done by crafting either a special shell alias or function to launch a single-use agent.  Either the function or the alias can be written to require confirmation for each requested signature.  The following example is a function is inspired by an updated blog post by Vincent Bernat&lt;ref name=&quot;safer-agent-forwarding&quot;&gt;{{cite web |url=https://vincent.bernat.ch/en/blog/2020-safer-ssh-agent-forwarding |title=Safer SSH agent forwarding |author=Vincent Bernat|date=2020-04-05 |accessdate=2020-10-04}}&lt;/ref&gt; on SSH agent forwarding:
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ agentssh() {
        ssh-agent ssh -o AddKeysToAgent=confirm -o ForwardAgent=yes
}
&lt;/syntaxhighlight&gt;

Note the use of [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)].  When invoking that alias, the SSH client will be launched with a unique, ephemeral supporting key agent.  The alias sets up a new agent, including setting the two environment variables, and then sets two client options while calling the client.  This arrangement still checks with [http://man.openbsd.org/ssh_config.5 ssh_config(5)] for other options and settings.  When the SSH session is finished the agent which launched it ends and goes away, thus cleaning up after itself automatically.  

Another way is to rely on the client's configuration file for some of the settings.  Such methods rely mostly on [http://man.openbsd.org/ssh_config.5 ssh_config(5)] but still require an independent method to launch an ephemeral agent because the OpenSSH client is already running by the time it reads the configuration file and is thus not affected by any changes to environment variables caused by the configuration file and it is through the environment variables that contain information about the agent.  However, when the path to the UNIX-domain socket used to communicate with the authentication agent is decided in advance then the '''IdentityAgent''' option can point to it once the one-off agent&lt;ref name=&quot;wikimedia_ssh_agents&quot;&gt;{{cite web |url=https://wikitech.wikimedia.org/wiki/Managing_multiple_SSH_agents#Linux_solutions |title=Managing multiple SSH agents |publisher=Wikimedia|accessdate=2020-04-07}}&lt;/ref&gt; is actually launched.  The following uses a specific agent's pre-defined socket whenever connecting to either of two particular domains:

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host *.wikimedia.org *.wmflabs.org
        User fred
        IdentitiesOnly yes
        IdentityFile %d/.ssh/id_cloud_01
        IdentityAgent /run/user/%i/ssh-cloud-01.socket
        ForwardAgent yes
        AddKeysToAgent yes
&lt;/syntaxhighlight&gt;

The '''%d''' stands for the path to the home directory and the '''%i''' stands for the user id (UID) for the current account.  In some cases the '''%i''' token might also come in handy when setting the '''IdentityAgent''' option inside the configuration file.  Again, be careful when forwarding agents with which keys are in the forwarded agent.  See the section &quot;TOKENS&quot; in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] for more such abbreviations.  

With those configuration settings, the authentication agent must already be up and running and point to the designated socket prior to starting the SSH client for that configuration to work.  Additionally, it should place the socket in a directory which is inaccessible to any other accounts.  [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)] must use the '''-a''' option to name the socket:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-agent -a /run/user/${UID}/ssh-cloud-01.socket
&lt;/syntaxhighlight&gt;

That agent configuration can be launched manually or via a script or service manager.  However, in the interests of privacy and security in general, agent forwarding is to be avoided.  The configuration directive '''ProxyJump''' is the best alternative and, on older systems, host traversal using '''ProxyCommand''' with [http://man.openbsd.org/nc.1 netcat] are preferable.  Again, see the section on [[OpenSSH/Cookbook/Proxies and Jump Hosts|Proxies and Jump Hosts]] for how those methods are used.

====Checking the Agent for Specific Keys====

The [http://man.openbsd.org/ssh_add ssh_add(1)] utility's '''-T''' option can test whether a specific private key is available in the agent or not by looking up the matching public key.  That can be useful in a shell script.

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
#!/bin/sh

key=/home/fred/.ssh/some.key.ed25519.pub

if ssh-add -T ${key}; then
        echo &quot;Key ${key} Found&quot;
else
        echo &quot;Key ${key} missing&quot;
fi
&lt;/syntaxhighlight&gt;

Or it could be done with an alternate syntax just as well either in a script or in an interactive shell sessions,

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ key=/home/fred/.ssh/some.key.ed25519.pub
$ ssh-add -T ${key} &amp;&amp; echo &quot;Key found&quot; || echo &quot;Key missing&quot;
&lt;/syntaxhighlight&gt;

However, if the desired result would be to add key to the agent then the '''AddKeysToAgent''' client configuration option can ensure that a specific key is added to the SSH agent upon first use during any given login session.  That can be done using '''-o AddKeysToAgent=yes''' as a run-time argument, or by modifying [http://man.openbsd.org/ssh_config ssh_config(5)] as appropriate:

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host www
        HostName www.example.com
        IdentityFile %d/.ssh/www.ed25519
        IdentitiesOnly yes
        AddKeysToAgent yes
&lt;/syntaxhighlight&gt;

With those options in the configuration file, the first time &lt;code&gt;ssh www&lt;/code&gt; is run the specified key will get added to the agent and remain available.

===Key-based Authentication Using A Hardware Security Token===

While stand-alone keys have been around for a long time, it has been possible since version 8.2 to use keys backed by hardware security tokens, such as OnlyKey, Yubikey, or many others, though the FIDO2 protocol.  The Universal 2nd Factor (U2F) authentication is supported directly in OpenSSH through FIDO2 and does not need third party software.  At the moment there are two types of hardware backed keys, ECDSA-SK and Ed25519-SK, but only the latest hardware tokens support the latter.  If the key Ed25519-SK format is not supported by the token's firmware, then the following error message will be presented when attempts to use that key type are made:

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
Key enrollment failed: invalid format
&lt;/syntaxhighlight&gt; 

If supported, either key type can be created with [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  The steps are almost identical to creating normal keys but the token must be available to the system (plugged in) first.  Then if called for, the token's PIN must be entered and the token touched or otherwise activated.  After that, the key creation proceeds as normal.  Mind the key type as specified by the '''-t''' option.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -t ed25519-sk -f /home/fred/.ssh/server.ed25519-sk -C &quot;web server for fred&quot;
Generating public/private ed25519-sk key pair.
You may need to touch your authenticator to authorize key generation.
Enter passphrase (empty for no passphrase): 
Enter same passphrase again: 
Your identification has been saved in /home/fred/.ssh/server.ed25519-sk
Your public key has been saved in /home/fred/.ssh/server.ed25519-sk.pub
The key fingerprint is:
SHA256:41wVVDnKJ9gKr2Sj4CFuYMhcNvYebZ6zq0PWyP4rRDo web server
The key's randomart image is:
+[ED25519-SK 256]-+
|           .o... |
|             .o  |
|           +.. . |
|   = .  . ..= .  |
|+ + * + So.. o   |
|o+.EoO *+oo      |
|.o oBo+++o       |
|  o .=.+.        |
| .   .===        |
+----[SHA256]-----+
&lt;/syntaxhighlight&gt;

Once created, the public and private key files get handled like with any other type of key.  But when authenticating, the hardware token must be present and activated when called for.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -i /home/fred/.ssh/server.ed25519-sk server.example.org
Enter passphrase for key '/home/fred/.ssh/server.ed25519-sk': 
Confirm user presence for key ED25519-SK SHA256:41wVVDnKJ9gKr2Sj4CFuYMhcNvYebZ6zq0PWyP4rRDo
&lt;/syntaxhighlight&gt;

The resulting private key file is not actually the key itself but instead a &quot;key handle&quot; which is used by the hardware security token to derive the real private key on demand at the time it is actually used&lt;ref name=&quot;OpenBSD_tech_U2F_FIDO&quot;&gt;{{cite web |url=https://marc.info/?l=openbsd-tech&amp;m=157376801917387&amp;w=2 |title=OpenSSH U2F/FIDO support in base 
|publisher=OpenBSD-Tech Mailing List | date=2019-11-14
|accessdate=2021-03-24}}&lt;/ref&gt;.  As a result, the hardware-backed private key file is useless without the accompanying hardware token.  This also means that these key files are not portable across hardware tokens, say when having multiple tokens in reserve or as backup, even when used by the same account.  So when multiple hardware tokens are in use, different key pairs must be generated for each token.

====Hardware Security Token Resident Private Key====

It is possible to store the private key within the token itself, but for the moment it cannot be used directly from inside the token and must first be saved as a file.  Also, the key can only be loaded into the FIDO authenticator at the time of creation  using the '''-O resident''' option with [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  Otherwise, the process is the same as above.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -O resident -t ed25519-sk -f /home/fred/.ssh/server.ed25519-sk -C &quot;web server for fred&quot;
. . .
&lt;/syntaxhighlight&gt;

When needed, the resident key can be extracted from the FIDO2 hardware token and saved into a file using the '''-K''' option.  At this stage a passphrase can be added to the file, but no passphrase is kept within the token itself, only an optional PIN protects the key there.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -K
Enter PIN for authenticator: 
Enter passphrase (empty for no passphrase): 
Enter same passphrase again: 
Saved ED25519-SK key to id_ed25519_sk_rk

$ mv -i id_ed25519_sk_rk /home/fred/.ssh/server.ed25519-sk
&lt;/syntaxhighlight&gt;

Since the output file name is fixed, any pre-existing file with that name can get overwritten but there will be a warning first.  However, it is not recommended to keep the key on the hardware token because it provides more protection when kept separately.

==Single-purpose Keys==

Tailored single-purpose keys can eliminate use of remote root logins for many administrative activities.  A  finely tailored '''sudoers''' is needed along with an unprivileged account.  When done right, it gives just enough access to get the job done, following the security principle of Least Privilege.  

Single-purpose keys are accompanied by use of either the '''ForceCommand''' directive in [http://man.openbsd.org/ssh_config.5 sshd_config(5)] or the '''command=&quot;...&quot;''' directive inside the '''authorized_keys''' file.  The method is to generate a new key pair, transfer the public key to '''authorized-keys''' on the remote system, and then prepend the appropriate command or script there to the line with the key.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/usr/local/bin/somescript.sh&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIEcgdzDvSebOEjuegEx4W1I/aA7MM3owHfMr9yg2WH8H
&lt;/syntaxhighlight&gt;

The '''command=&quot;...&quot;''' directive inserted there overrides everything else and ensures that when logging in with just that key only the script '''/usr/local/bin/somescript.sh''' is run.  If it is necessary to pass parameters to the script, have a look at the contents of the '''SSH_ORIGINAL_COMMAND''' environment variable and use it in a case statement.  Do not ever trust the contents of that variable nor use the contents directly, always indirectly.  

Single-purpose keys are useful for allowing only a tunnel and nothing more.  The following key will only echo some text and then exit, unless used non-interactively with the '''-N''' option.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/bin/echo do-not-send-commands&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBzTIWCaILN3tHx5WW+PMVDc7DfPM9xYNY61JgFmBGrA 
&lt;/syntaxhighlight&gt; 

No matter what the user tries while logging in with that key, the session will only echo the given text and then exits.  Using the '''-N''' option disables running the remote program, allowing the connection to stay open, allowing a tunnel. 

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -L 3306:localhost:3306 \
	-i ~/.ssh/tunnel_ed25519 \
	-N \
	-l fred \
	server.example.com
&lt;/syntaxhighlight&gt;

That creates a tunnel and stays connected despite a key configuration which would close an interactive session.  See also the '''-n''' or '''-f''' option for [http://man.openbsd.org/ssh.1 ssh(1)].  

===Single-purpose Keys to Avoid Remote Root Access===

The easy way is to write a short shell script, place it '''/usr/local/bin/''', and then configure '''sudoers''' to allow the otherwise unprivileged account to run just that script and only that script.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
%wheel  ALL=(root:root) NOPASSWD: /usr/sbin/service httpd stop
%wheel  ALL=(root:root) NOPASSWD: /usr/sbin/service httpd start
&lt;/syntaxhighlight&gt;

Then the key calls the script using '''command=&quot;...&quot;''' inside '''authorized_keys'''.  Here the one key starts the web server, the other stops the web server.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/usr/bin/sudo /usr/sbin/service httpd stop&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIEcgdzDvSebOEjuegEx4W1I/aA7MM3owHfMr9yg2WH8H
command=&quot;/usr/bin/sudo /usr/sbin/service httpd start&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMidyqZ6OCvbWqA8Zn+FjhpYE6NoWSxVjFnFUk6MrNZ4
&lt;/syntaxhighlight&gt;

Complicated programs like [http://linux.die.net/man/1/rsync rsync(1)], [http://man.openbsd.org/tar.1 tar(1)], [http://linux.die.net/man/1/mysqldump mysqldump(1)], and so on require an advanced approach when building a single-purpose key.  For them, the '''-v''' option can show exactly what is being passed to the server so that '''sudoers''' can be set up correctly.  That way they can be restricted to only access designated parts of the file system.  For example, here is what &lt;code&gt;ssh -v&lt;/code&gt; shows from one particular usage of [http://linux.die.net/man/1/rsync rsync(1)], note the &quot;Sending command&quot; line:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ rsync -e 'ssh -v' fred@server.example.org:/etc/ ./backup/etc/
. . .
debug1: Sending command: rsync --server --sender -e.LsfxC . /etc/
. . .
&lt;/syntaxhighlight&gt;

That output can then be added to '''sudoers''' so that the key can do only that function.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
%backup ALL=(root:root) NOPASSWD: /usr/bin/rsync --server --sender -e.LsfxC . /etc/
&lt;/syntaxhighlight&gt;

Then to tie it all together, the account &quot;backup&quot; needs a key:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/usr/bin/rsync --server --sender -e.LsfxC . /etc/&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMm0rs4eY8djqBb3dIEgbQ8lmdlxb9IAEuX/qFCTxFgb 
&lt;/syntaxhighlight&gt;

Many of these programs have a '''--dry-run''' or equivalent option.  Remember to use it when figuring out the right settings.

===Read-only Access to Keys===

In some cases it is necessary to prevent accounts from being able to changing their own authentication keys.  However, such situations may be a better case for using certificates.  However, if done with keys it is accomplished by putting the key file in an external directory where the user has read-only access, both to the directory and to the key file.  Then the '''AuthorizedKeysFile''' directive assigns where [http://man.openbsd.org/sshd.8 sshd(8)] looks for the keys and can point to a secured location for the keys instead of the default location.

A good alternate location could be a new directory '''/etc/ssh/authorized_keys''' which could store the selected accounts' key files there.  The change can be made to apply to only a group of accounts by putting the settings under a '''Match''' directive.  The default location for keys on most systems is usually '''~/.ssh/authorized_keys'''.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Match Group sftpusers
	AuthorizedKeysFile /etc/ssh/authorized_keys/%u
&lt;/syntaxhighlight&gt;

Then the permissions there would allow the keys to be read but not written:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ls -dhln /etc/ssh/
drwxr-x--x 3 0 0 4.0K Mar 30 22:16 /etc/ssh/authorized_keys/

$ ls -dhln /etc/ssh/*.pub
-rw-r--r-- 1 0 0 173 Mar 23 13:34 /etc/ssh/fred
-rw-r--r-- 1 0 0  93 Mar 23 13:34 /etc/ssh/user1
-rw-r--r-- 1 0 0 565 Mar 23 13:34 /etc/ssh/user2
. . .
&lt;/syntaxhighlight&gt;

The keys could even be within subdirectories, though the same restrictions apply regarding permissions and ownership.  

For chrooted SFTP, the method is the same to keep the key files out of reach of the accounts:  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Match Group sftpusers
	ChrootDirectory /home
	ForceCommand internal-sftp -d %u
	AuthorizedKeysFile /etc/ssh/authorized_keys/%u
&lt;/syntaxhighlight&gt;

Of course a '''Match''' directive is not essential.  The settings could be made to apply to all accounts by putting the directive in the main part of the server configuration file instead.

==Mark Public Keys as Revoked==

Keys can be revoked.  Keys that have been revoked can be stored in '''/etc/ssh/revoked_keys''', a file specified in [http://man.openbsd.org/ssh_config.5 sshd_config(5)]  using the directive '''RevokedKeys''', so that [http://man.openbsd.org/sshd.8 sshd(8)] will prevent attempts to log in with them.  No warning or error on the client side will be given if a revoked key is tried.  Authentication will simply progress to the next key or method.

The revoked keys file should contain a list of public keys, one per line, that have been revoked and can no longer be used to connect to the server.  The key cannot contain any extras, such as [[OpenSSH/Client_Configuration_Files#Available_key_login_options | login options]] or it will be ignored. If one of the revoked keys is tried during a login attempt, the server will simply ignore it and move on to the next authentication method.  An entry will be made in the logs of the attempt, including the key's fingerprint.  See the section on [[OpenSSH/Logging_and_Troubleshooting | logging]] for a little more on that.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
RevokedKeys /etc/ssh/revoked_keys
&lt;/syntaxhighlight&gt;

The '''RevokedKeys''' configuration directive is not set in [http://man.openbsd.org/ssh_config.5 sshd_config(5)] by default.  It must be set explicitly if it is to be used.  This is another situation that might be better fulfilled through using certificate since a validity interval can be set in any combination of seconds, minutes, hours, days, or weeks can be set for certificates while keys are valid indefinitely.  

===Key Revocation Lists===

A Key Revocation List (KRL) is a compact, binary form of representing revoked keys and certificates.  In order to use a KRL, the server's configuration file must point to a valid list using the '''RevokedKeys''' directive.  KRLs themselves are generated with [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] and can be created from scratch or edited in place.  Here a new one is made, populated with a single public key: 

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -k -f /etc/ssh/revoked_keys -z 1 ~/.ssh/old_key_rsa.pub
&lt;/syntaxhighlight&gt;

Here an existing KRL is updated by adding the '''-u''' option:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -u -k -f /etc/ssh/revoked_keys -z 2 ~/.ssh/old_key_dsa.pub
&lt;/syntaxhighlight&gt;

Once a KRL is in place, it is possible to test if a specific key or certificate is in the revocation list.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -Q -f /etc/ssh/revoked_keys ~/.ssh/old_key_rsa.pub
&lt;/syntaxhighlight&gt;

Only public keys and certificates will be loaded into the KRL.  Corrupt or broken keys will not be loaded and will produce an error message if tried.  Like with the regular '''RevokedKeys''' list, the public key destined for the KRL cannot contain any extras like login options or it will produce an error when an attempt is made to load it into the KRL or search the KRL for it.

==Verify a Host Key by Fingerprint==

The above examples have been about using keys to authenticate the client to the server.  A different context in which keys are used is when the server identifies itself to the client, which happens automatically at the beginning of each non-multiplexed session.  In order for that identification to happen the client acquires a public key from the server, usually on or prior to first contact, which it can subsequently use to ensure that it is connecting to the same server again and not an impostor.  The default locations for storing these acquired host keys on the client are in '''/etc/ssh/ssh_known_hosts''', if managed by the system administrator, or in '''~/.ssh/known_hosts''' if managed by the client's own account.  The format of the contents is a line with a host address and its matching public key.  The file is described in detail in the [http://man.openbsd.org/sshd.8 sshd(8)] manual page in the section &quot;SSH_KNOWN_HOSTS FILE FORMAT&quot;.

When connecting for the first time to a remote host, the server's host key should be verified in order to ensure that the client is connecting to the right machine and not an impostor or anything else.  Usually this verification is done by comparing the fingerprint of the server's host key rather than trying to compare the whole key itself.  By default the client will show the fingerprint if the key is not already found in the '''known_hosts''' register.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -l fred server.example.org
The authenticity of host 'server.example.org (192.0.32.10)' can't be established.
ECDSA key fingerprint is SHA256:LPFiMYrrCYQVsVUPzjOHv+ZjyxCHlVYJMBVFerVCP7k.
Are you sure you want to continue connecting (yes/no)? 
&lt;/syntaxhighlight&gt;

That can be compared to a fingerprint received out of band, say by post, e-mail, SMS, courier, and so on.  Specifically, the example represents the key's fingerprint as a base64 encoded SHA256 checksum.  That is the default style.  The fingerprint can also be displayed as an MD5 hash in hexadecimal instead by passing the client's '''FingerprintHash''' configuration directive as a runtime argument or setting it in [http://man.openbsd.org/ssh_config.5 ssh_config(5)].  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -o FingerprintHash=md5 host.example.org
The authenticity of host 'host.example.org (192.0.32.203)' can't be established.
RSA key fingerprint is MD5:10:4a:ec:d2:f1:38:f7:ea:0a:a0:0f:17:57:ea:a6:16.
Are you sure you want to continue connecting (yes/no)?
&lt;/syntaxhighlight&gt;

But the default in new versions is SHA256 in base64 has a lower chance of collision.

In OpenSSH 6.7 and earlier, the client showed fingerprints as a hexadecimal MD5 checksum instead a of the base64-encoded SHA256 checksum currently used:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -l fred server.example.org
The authenticity of host 'server.example.org (192.0.32.10)' can't be established. 
RSA key fingerprint is 4a:11:ef:d3:f2:48:f8:ea:1a:a2:0d:17:57:ea:a6:16. 
Are you sure you want to continue connecting (yes/no)? 
&lt;/syntaxhighlight&gt;

Another way of comparing keys is to use the ASCII art visual host key.  See further below about that.  

===Downloading keys===

Even though a host’s key is usually displayed for review the first time the SSH client tries to connect, it can also be fetched on demand at any time using [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)]:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan server.example.org
# server.example.org:22 SSH-2.0-OpenSSH_10.6
server.example.org ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBEWKepJgkC2XTG5cAr2Nyew6hOp5AjG7vi2RYFtPWqN3bo5XGuCX2d2YVyn++/2PtyMYBaKWyFpCNTT9X0F1Epg=
# server.example.org:22 SSH-2.0-OpenSSH_10.6
server.example.org ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDKyERe8k+fnsrt4JrcLD3AW0kXj90r9ybrEZuY/CTrXIqYSizO335SxGJoWrKijaRy8htuueMkmNfxxhnBPoAjul/4T/FCRGKaV0jC96xYNnKcXbnXxSLVQ0OW2EIPvQhw/TU/G3vEqtiRYGyaNcZS6xrnVv3xuPuvVC1VRKspNLEq7zfvToC0OB89X5DIbvBbHY13PjJ0NrDdX3sSA8lxPsYagBuDIvyxH0S4Z5fQHeYrdvENS5zX6LwJeMeGSOqDuD0Zb4hpKxhaGVwP5e435VcFuImbFaDPM4w71PzaSUEj+tnUA0mGDoLiCrpW3txkJszog9lN3C/nLGghFaT7ajrfH55qut81JnvdhMju9+SzxrKPJmtQZfKVLIc4whEbtFsPCdm2bstz7ROWxTJ3t/Vr8/QVm2G2aY4FHuPwo2jUQDbQA7mCV+fe1sADy2jLzGhn1TCeYvWSv5PNJAT97IrLfD3+0Uo+qJD/6CU7F8oabj1Ql2H8fPN5kGSWfkM=
# server.example.org:22 SSH-2.0-OpenSSH_10.6
server.example.org ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIJo5gc4VrxVQ5apAOd7qK6UqGlLMpWOPuunjB53JBN2s
# server.example.org:22 SSH-2.0-OpenSSH_10.6
# server.example.org:22 SSH-2.0-OpenSSH_10.6
# server.example.org:22 SSH-2.0-OpenSSH_10.6
server.example.org ssh-mldsa44-ed25519 AAAAE3NzaC1tbGRzYTQ0LWVkMjU1MTkAAAVAyIw5r9FaniSYqBX0yd9vgBz5nCkebaQlMQN9N0p//Ukfn/CnZ3YtZWn6pUGjDM85/bqdL1gqah1OLfnl1eHk0qvTACrym07uKaMLoEHuakIXHbTi/ELPRoRP3F+DpEgjtYSjLc/fJiobRMgSvmLJxTUzZTStsqWAL1L9/1zuwHEngR+THpUcCSTi6KKkYcQiWGOFwpO22VdiuOg+zdQSH+9jW6eXYk1z81KU6UlHZps8zVrlqCd3FDDghgbH5U8DcGN2t6GvVfn6jFjpEk0ouj0of3/7010eRXjnv3QSbprCpMq73lAemQM+3LvTtrMBhFWNhCXhyOHfO1Yq7c8xaOwlFK78PlERjdHTvVJaCaDFDy7Pg9I+wxv+uC+W0wtzJ2S1y9XCYUgJo9yEiIGuSZdhMkYUwMnXLzQMm44hQOW153pdlHWze3kESCLg/LJf9RbUoSB43t6rghSHEiUkIi5TtCtFZ4nAGeH+wVwlB9Fwog5uZuJN1FYuuY5sSrLHJAQDUwudkdak0ifOhtPtsM/ClYr3baolQ/qi0ABYUVLKSV5b+A5DlTXa23zc7JAXm2YVfkWpOfVJG4TY81wrJoDumsd1y3XaH28/4QbADsZCE3wYsBou8ff0xKgPu8xm2K+sYSmzUbBGprArAQA0LtIDGNGqrb4JsZ1ru+viwzfSlxV7Nz7ZrSw6h+Ddq4J9A6oKXy6YS3uf1GFOtBQm6JfuyMHQEEUtYZrU4UK3C/fKHx9vjuw7YdhsL8JRgxbF14qJLFizkmVbK2e6aWEE4iCqLLLlZ0dC2peYUUqyGb9PsW7sewYzGbipzPpQ/GobRT3Obc3Gmu8P386pDGR7hmkOpFmVwIcfc431cUmZixK7CkPxzUvfaAAQkmNs/p4eNNoP0gq/xPGsV14/heULbWp/njGWk1ysjjGxP6YMwHcEZpUdSGbD05zbL0KkMtmKsr8yuJYjdVAgtH2bVAvrxXRXLgavmm97VYYq1A9rOYiQFlMrKRg6yZhT10Xt8Hukf6ySLk+fieFc3nH99YeysoA5rsfp9kdXr65GpwrBerZlf/20ZLJ7s4xaYb9SukR/8tiPt9iAVQjqPdb0MseZVrzhKo/jK44JHbHejHMoMMs7etPAS5TIjHxcJTP66B3eO9A0l2fAage2ka7ehTnHivxD3EE9KnqYBjIHDU7o6dTrX7UyQsdhax9bPKEL7OEtm6hXXfwzy4GdqGi124BclFAF0LeBSvBUgmSKIn3wfzJx/XXbt512eOn3WZk2v0TsiteH9kPEgDxVkUykawg2tleak9rTFMzYpDZRHvZD7uHWUZ8ktr2FEKWgq7/1Q2c80Z6H75VK9l1d3KZuoiWoF1s73R7ZAM+CWSrR+S5h+3AhYubDKPa/af+Lnlqe6ocVTqQPYaaRz25/cLBg6pgbdh18Ru6h3ljG2KiysyXeuoEoM5xVYtdIW7l9NeKDpGbZPAOqywXUpK+UCGjumIl7c48KCTIYcdtolnEbfVNBh0LRuftcVI+uF9cvQ0XacaNbgkYJYCjv4VR/n58EJ1b0c7tQBrVqMjDjIUKGhCMQqAeD3g75jeD60bBmVNPrq8RK+zH5VIa5eaBs3eitN98eVzd4b6UYTQd1QxLQZMrhQf4InRj39TZfGvQR5SXlLZQlweVHYkMps3IKbs3B3DCqlWCPUAnTAJBAG7HqWEYr5uEaKBawBSAx9jCQz00T+bp8KXpkOPzZCD6dfEfpHY6Rv6kmGJkiPUCb2hoX145HrS357G12+wDxKLN833oPVC0z
&lt;/syntaxhighlight&gt;

Once a key is acquired, its fingerprint can be shown using [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] to read from '''stdin'''.  This can be done directly with a pipe.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan server.example.org | ssh-keygen -l -f -
3072 SHA256:tQlw3vy325KrQibndP3gLS/YXUZjTLVA5yDFpg/Bb6I server.example.org (RSA)
256 SHA256:snnAtb/9csdy0BGhPjdg+VNWqN5bxCa/ge4C6zZ8muk server.example.org (ECDSA)
256 SHA256:agRZDZn8awhQ+tc19Ip/whkHoV33Ln2REO7v1kcYbdU server.example.org (ED25519)
512 SHA256:3Wdc6GbLIcc5mbuF2mhhokhARdMLuMK+ESRfJ+sM0QE server.example.org (MLDSA44-ED25519)
&lt;/syntaxhighlight&gt;

If there is more than one public key type is available from the server on the port polled, then [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] will fetch each of them.  If there is more than one key fed via '''stdin''' or a file, then [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] will process them in order.  Prior to OpenSSH 7.2 manual fingerprinting was a two step process, the key was read to a file and then processed for its fingerprint.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan -t ed25519 host.example.org &gt; key.pub
# host.example.org SSH-2.0-OpenSSH_6.8
$ ssh-keygen -lf key.pub                       
256 SHA256:ZmS+IoHh31CmQZ4NJjv3z58Pfa0zMaOgxu8yAcpuwuw host.example.org (ED25519)
&lt;/syntaxhighlight&gt;

Note that some output from [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] is sent to '''stderr''' instead of '''stdout'''.  

A hash, or fingerprint, can be generated manually with [http://linux.die.net/man/1/awk awk(1)], [http://linux.die.net/man/1/sed sed(1)] and [http://linux.die.net/man/1/xxd xxd(1)], on systems where they are found.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ awk '{print $2}' key.pub | base64 -d | md5sum -b | sed 's/../&amp;:/g; s/: .*$//'
$ awk '{print $2}' key.pub | base64 -d | sha256sum -b | sed 's/ .*$//' | xxd -r -p | base64 
&lt;/syntaxhighlight&gt;

It is possible to find all hosts from a file which have new or different keys from those in '''known_hosts''', if the host names are in clear text and not stored as hashes.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan -t ed25519,mldsa44-ed25519 -f ssh_hosts | \
  sort -u - ~/.ssh/known_hosts | \
  diff ~/.ssh/known_hosts -
&lt;/syntaxhighlight&gt;

====Using ssh-keyscan(1) with ssh_config(5)====

The utility [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] does not parse [http://man.openbsd.org/ssh_config.5 ssh_config(5)].  That is in part to keep the code base simple.  There are a lot of configuration options which would be complicated to implement, including but not limited to '''ProxyJump''', '''ProxyCommand''', '''Match''', '''BindInterface''', and '''CanonicalizeHostname'''&lt;ref name=&quot;keyscan&quot;&gt;{{cite mailing list |url=https://lists.mindrot.org/pipermail/openssh-unix-dev/2023-March/040605.html | title=Why does ssh-keyscan not use .ssh/config? |publisher=mindrot.org | access-date=2023-03-01 | date=2023-03-01 | mailing-list=OpenSSH UNIX-dev | first=Damien | last=Miller }}&lt;/ref&gt; .  Resolving host names via the client configuration file can be done by wrapping the utility in a short shell function:

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
my-ssh-keyscan() {
	for host in &quot;$@&quot; ; do
		ssh-keyscan $(ssh -G &quot;$host&quot; | awk '/^hostname/ {print $2}')
	done
}
&lt;/syntaxhighlight&gt;

That shell function uses the '''-G''' option of [http://man.openbsd.org/ssh.1 ssh(1)] to resolve each host name using [http://man.openbsd.org/ssh_config.5 ssh_config(5)] and then check the resulting host name for SSH keys.

===ASCII Art Visual Host Key===

An ASCII art representation of the key can be displayed along with the SHA256 base64 fingerprint: 

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -l -v -f key 
256 SHA256:BClQBFAGuz55+tgHM1aazI8FUo8eJiwmMcqg2U3UgWU www.example.org (ED25519)
+--[ED25519 256]--+
|o+=*++Eo         |
|+o .+.o.         |
|B=.oo.  .        |
|*B.=.o .         |
|= B *   S        |
|. .@ .           |
| +..B            |
|  *. o           |
| o.o.            |
+----[SHA256]-----+
&lt;/syntaxhighlight&gt;

In OpenSSH 6.7 and earlier the fingerprint is in MD5 hexadecimal form.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -l -v -f key 
2048 37:af:05:99:e7:fb:86:6c:98:ee:14:a6:30:06:bc:f0 www.example.net (RSA) 
+--[ RSA 2048]----+ 
|          o      | 
|         o .     | 
|        o o      | 
|       o +       | 
|   .  . S        | 
|    E ..         | 
|  .o.* ..        | 
|  .*=.+o         | 
|  ..==+.         | 
+-----------------+ 
&lt;/syntaxhighlight&gt;

==More on Verifying SSH Keys==

Keys on the client or the server can be verified against known good keys by comparing the base64-encoded SHA256 fingerprints.  

===Verifying Stray Client Keys===

Sometimes is is necessary to compare two uncertain key files to check if they are part of the same key pair.  However, public keys are more or less disposable.  So the easy way in such situations on the client machine is to just rename or erase the old, problematic, public key and replace it with a new one generated from the existing private key.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -y -f ~/.ssh/my_key_ed25519
&lt;/syntaxhighlight&gt;

But if the two parts must really be compared, it is done in two steps using [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  First, a new public key is re-generated from the known private key and used to make a fingerprint to '''stdout'''.  Next, the fingerprint of the unknown public key is generated for comparison.  In this example, the private key '''my_key_a_ed25519''' and the public key '''my_key_b_ed25519.pub''' are compared:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -y -f my_key_a_ed25519 | ssh-keygen -l -f -
$ ssh-keygen -l -f my_key_b_ed25519.pub
&lt;/syntaxhighlight&gt;

The result is a base64-encoded SHA256 checksum for each key with the one fingerprint displayed right below the other for easy visual comparison.  Older versions don't support reading from '''stdin''' so an intermediate file will be needed then.  Even older versions will only show an MD5 checksum for each key.  Either way, automation with a shell script is simple enough to accomplish but outside the scope of this book.

===Verifying Server Keys===

Reliable verification of a server's host key must be done when first connecting.  It can be necessary to contact the system administrator who can provide it out of band so as to know the fingerprint in advance and have it ready to verify the first connection.  

Here is an example of the server's Ed25519 key being read and its fingerprint shown as SHA256 base64:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -l -f /etc/ssh/ssh_host_ed25519_key.pub 
256 SHA256:bFzzouaWmE5HuZIv+YnGUYI2q06i6M43V+6jMU3LHpA root@server.example.org (ED25519)
&lt;/syntaxhighlight&gt;

And here the corresponding ECDSA key is read, but shown as an MD5 hexadecimal hash:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -E md5 -l -f /etc/ssh/ssh_host_ecdsa_key.pub
256 MD5:ed:d2:34:b4:93:fd:0e:eb:08:ee:b3:c4:b3:4f:28:e4 root@server.example.net (ECDSA)
&lt;/syntaxhighlight&gt;

Prior to 6.8, the fingerprint was expressed as an MD5 hexadecimal hash:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -l -f /etc/ssh/ssh_host_rsa_key.pub 
2048 MD5:e4:a0:f4:19:46:d7:a4:cc:be:ea:9b:65:a7:62:db:2c root@server.example.net (RSA)
&lt;/syntaxhighlight&gt;

It is also possible to use [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] to get keys from an active SSH server.  However, the fingerprints still needs to be verified out of band.  

====Warning: Remote Host Identification Has Changed!====

If a server's key does not match what the client finds has been recorded in either the system's or the local account's '''authorized_keys''' files, then the client will issue a warning along with the fingerprint of the suspicious key.  

&lt;pre&gt;
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ED25519 key sent by the remote host is
SHA256:bFzzouaWmE5HuZIv+YnGUYI2q06i6M43V+6jMU3LHpA.
Please contact your system administrator.
Add correct host key in /home/fred/.ssh/known_hosts to get rid of this message.
Offending ED25519 key in /home/fred/.ssh/known_hosts:11
Host key for server.example.org has changed and you have requested strict checking.
Host key verification failed.
&lt;/pre&gt;

Three reasons for the warning are common.  

One reason is that the server's keys were replaced, often because the server's operating system was reinstalled without backing up the old keys.  Another reason can be when the system administrator has phased out deprecated or compromised keys.  However that can be planned better and if there is time to plan the migration, new keys can just be added to the server and have the clients use the '''UpdateHostKeys''' option so that the new keys are accepted if the old keys match.  A third situation is when the connection is made to the wrong machine, such as when the remote system changes IP addresses because of dynamic address allocation.  

In all three cases where the key has changed there is only one thing to do: contact the system administrator and verify the key.   Ask if the OpenSSH-server was recently reinstalled, or was the machine restored from an old backup?  Keep in mind that the system administrator may be you yourself in some cases. 

The case which is rather rare but serious enough that it should be ruled out for sure is that the wrong machine is part of a man-in-the-middle attack.

In all four cases, an authentic key fingerprint can be acquired by any method where it is possible to verify the integrity and origin of the message, for example via PGP-signed e-mail.  If physical access is possible, then use the console to get the right fingerprint.  Once the authentic key fingerprint is available, return to the client machine where you got the error and remove the old key from '''~/.ssh/known_hosts'''

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -R server.example.org
&lt;/syntaxhighlight&gt;

Then try logging in, but compare the key fingerprints first and proceed if and '''only''' if the key fingerprint matches what you received out of band.  If the key fingerprint matches, then go through with the login process and the key will be automatically added.  If the key fingerprint does not match, stop immediately and figure out what you are connecting to.  It would be a good idea to get on the phone, a real phone not a computer phone, to the remote machine's system administrator or the network administrator.

===Multiple Keys for a Host, Multiple Hosts for a Key in known_hosts===
 
Multiple host names or IP addresses can use the same key in the '''known_hosts''' file by using pattern matching or simply by listing multiple systems for the same key.  That can be done in either the global list of keys in '''/etc/ssh/ssh_known_hosts''' and the local, account-specific lists of keys in each account's '''~/.ssh/known_hosts''' file.  Labs, computational clusters, and similar pools of machines can make use of keys in that way.  Here is a key shared by three specific hosts, identified by name, one host per line:
&lt;pre&gt;
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
server2 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
server3 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
&lt;/pre&gt;
Or a range can be specified by using globbing to a limited extent in either '''/etc/ssh/ssh_known_hosts''' or '''~/.ssh/known_hosts'''.
&lt;pre&gt;
172.19.40.* ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
&lt;/pre&gt;
Conversely, a pool of servers might have multiple keys for the same address.  In that case, it is necessary to make multiple entries in either '''/etc/ssh/ssh_known_hosts''' or '''~/.ssh/known_hosts''' for each key.
&lt;pre&gt;
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBrsIIaDl/bJ40vyprvF+HYAq+kE2jWUsOt+WqIheaBw fred@desk.example.org
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIC2CgwWTPH/qZDeHmW7ZUea18wa9As7Txq3P5dXCfoXj fred@desk.example.org 
&lt;/pre&gt;
Thus in order to get a pool of servers to share a pool of keys, each server-key combination must be added manually to the '''known_hosts''' file:
&lt;pre&gt;
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBrsIIaDl/bJ40vyprvF+HYAq+kE2jWUsOt+WqIheaBw fred@desk.example.org
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIC2CgwWTPH/qZDeHmW7ZUea18wa9As7Txq3P5dXCfoXj fred@desk.example.org 

server2 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAICPSs4OR2LT89mv2tM4TKqeVhh4XvoLQ77MSBmjyrMGm fred@desk.example.org
server2 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIHChTzAoJr53A7VP1BdMHqLTFK5cz/2Vc065+VcpP4VA fred@desk.example.org
server2 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIHP+4BvU4DzwYQgznARxx/qyBWmu49PAywHwDRgslRaM fred@desk.example.org
&lt;/pre&gt;

Though upgrading to certificates might be a more appropriate approach that manually updating lots of keys.

===Another way of Dealing with Dynamic (roaming) IP Addresses===
It is possible to manually point to the right key using '''HostKeyAlias''' either as part of [http://man.openbsd.org/ssh_config.5 ssh_config(5)]  or as a runtime parameter.  Here the key for machine ''Foobar'' is used to connect to host 192.168.11.15

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -o StrictHostKeyChecking=accept-new \
      -o HostKeyAlias=foobar   \
      192.168.11.15
&lt;/syntaxhighlight&gt;
This is useful when DHCP is not configured to try to keep the same addresses for the same machines over time or when using certain stdio forwarding methods to pass through intermediate hosts.

===Host Key Update and Rotation in known_hosts===

A protocol extension to rotate weak public keys out of '''known_hosts''' has been in OpenSSH from version 6.8&lt;ref name=&quot;djm_rotation&quot;&gt;
{{cite web
| title=Key rotation in OpenSSH 6.8+ 
| author=Damien Miller
| url=http://blog.djm.net.au/2015/02/key-rotation-in-openssh-68.html
| date=2015-02-01
| publisher=DJM's Personal Weblog
| accessdate=2016-03-05
}}
&lt;/ref&gt; and later.  With it the server is able to inform the client of all its host keys and update '''known_hosts''' with new ones when at least one trusted key already known.  This method still requires the private keys be available to the server &lt;ref name=&quot;djm_rotation_redux&quot;&gt;
{{cite web
| title=Hostkey rotation, redux 
| author=Damien Miller
| url=http://blog.djm.net.au/2015/02/hostkey-rotation-redux.html
| date=2015-02-17
| publisher=DJM's Personal Weblog
| accessdate=2016-03-05
}}
&lt;/ref&gt; so that proofs can be completed.  In [http://man.openbsd.org/ssh_config.5 ssh_config(5)], the directive '''UpdateHostKeys''' specifies whether the client should accept updates of additional host keys from the server after authentication is completed and add them to '''known_hosts'''.  A server can offer multiple keys of the same type for a period before removing the deprecated key from those offered, thus allowing an automated option for rotating keys as well as for upgrading from weaker algorithms to stronger ones.  See also [https://datatracker.ietf.org/doc/html/rfc4819 RFC 4819: Secure Shell Public Key Subsystem] about key management standards.

==Converting Between SSH Key Formats==

OpenSSH has its own format for keys which it uses by default when new keys are made.  However, other SSH clients and servers may use other formats such as [https://www.rfc-editor.org/rfc/rfc4716 RFC 4716], [https://www.rfc-editor.org/rfc/rfc5958 PKCS8], or [https://www.rfc-editor.org/rfc/rfc1421 PEM].  Any of these can be converted to the default OpenSSH format by [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  The default to format to try to convert from is RFC 4716.  The utility [https://linux.die.net/man/1/puttygen puttygen(1)] makes keys in that format for [https://linux.die.net/man/1/putty putty(1)] and they need conversion when used with OpenSSH's server.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -i -f /var/tmp/key_public.ppk
&lt;/syntaxhighlight&gt;

However, you can use the '''-m''' option to specify either that format explicitly or else choose another one to convert from.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -i -m RFC4716 -f /var/tmp/key_public.ppk
$ ssh-keygen -i -m PKCS8 -f /var/tmp/key_public.ppk
&lt;/syntaxhighlight&gt;

Both examples above are for importing public keys into OpenSSH's own format.  

By default OpenSSH will write newly-generated keys in its own format, so the '''-m''' option is obligatory to produce public keys in another format.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -e -m PKCS8 -f ~/.ssh/key.pub
&lt;/syntaxhighlight&gt;

It is not yet possible to export private keys from the OpenSSH format to one of the other formats using the '''-e''' option.  Even if a private key is specified as input, a public key is produced:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -e -m RFC4716 -f ~/.ssh/key
&lt;/syntaxhighlight&gt;

Not all key types are supported by all key formats.  

It is also possible to use export to display the key pair as a traditional hex dump.
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -e -m hexdump -f ~/.ssh/key
Enter passphrase for &quot;key&quot;: 
Public ED25519 key:
buffer len = 51
0000: 00 00 00 0b 73 73 68 2d 65 64 32 35 35 31 39 00  ....ssh-ed25519.
0016: 00 00 20 b0 c5 cc 2c cb d8 8b 8d 75 80 eb e6 e9  .. ...,....u....
0032: 2c f4 36 08 7b 5b ad ad 0b 54 4f 7f 21 9d 1b e8  ,.6.{[...TO.!...
0048: 9e e0 32                                         ..2

Private ED25519 key:
buffer len = 119
0000: 00 00 00 0b 73 73 68 2d 65 64 32 35 35 31 39 00  ....ssh-ed25519.
0016: 00 00 20 b0 c5 cc 2c cb d8 8b 8d 75 80 eb e6 e9  .. ...,....u....
0032: 2c f4 36 08 7b 5b ad ad 0b 54 4f 7f 21 9d 1b e8  ,.6.{[...TO.!...
0048: 9e e0 32 00 00 00 40 e1 c3 a2 4d d9 89 49 72 9b  ..2...@...M..Ir.
0064: 86 72 6c 07 17 1b 40 4f 62 50 62 45 4f 4c cf cf  .rl...@ObPbEOL..
0080: 57 8b 9d c0 04 8f 9b b0 c5 cc 2c cb d8 8b 8d 75  W.........,....u
0096: 80 eb e6 e9 2c f4 36 08 7b 5b ad ad 0b 54 4f 7f  ....,.6.{[...TO.
0112: 21 9d 1b e8 9e e0 32                             !.....2
&lt;/syntaxhighlight&gt;

==Disadvantages of Keys, in Contrast to Certificates==

Keys are quite useful in small environments.  There they are still considered established best practice.  However, keys have trouble scaling when deployments increase greatly in scope or duration.  The following limitations tend to get in the way as environments grow or age:

* Deployment and removal are done manually unless orchestration tools are already in place.  Copying and configuring each key for each account on each server takes more time and effort as either or both numbers grow.  
* Keys are valid indefinitely, with neither start dates nor expiration dates.  They are usable until hunted down and removed.  It's hard to find them all.  
* Host verification must be done manually and thus some will omit it.  
* Access control is not embedded inside keys but added in separate, server-side configurations which might or might not be editable by the accounts in question.  
* Identity information is not embedded inside keys either.  

When any of those limitations start to become problematic, it can be time to consider escalating to [[OpenSSH/Cookbook/Certificate-based_Authentication | Certificate-based Authentication]] instead.  It is addressed in the next chapter.  

&lt;noinclude&gt;

== References ==
{{reflist}}
{{OpenSSH/TOC|mini}}
&lt;/noinclude&gt;
{{BookCat}}
{{status|100%}}</text>
      <sha1>df3sgvf4iisvtqbh69vpbd9svt6y982</sha1>
    </revision>
  </page>
  <page>
    <title>Teachers' Toolbox/Ways to improve your own teaching</title>
    <ns>0</ns>
    <id>93533</id>
    <revision>
      <id>4676580</id>
      <parentid>4327683</parentid>
      <timestamp>2026-10-17T23:55:50Z</timestamp>
      <contributor>
        <username>BlueCuddleBear</username>
        <id>3627179</id>
      </contributor>
      <minor />
      <comment>/* Video feedback */</comment>
      <origin>4676580</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2295" sha1="fcsuajc0f89footvz5u4jsj7krm8fpv" xml:space="preserve">There are several ways to continuously improve and develop your own teaching.

==Peer coaching==
Resources
*[http://www.modares.ac.ir/elearning/Mchizari/AEA/Page/Class14/peer.htm Peer Coaching: An Innovation in Teaching]
*[http://webserver3.ascd.org/ossd/peercoaching.html Peer Coaching]

==Feedback to other teachers==
==Student evaluations==
===Feedback to the supervisor===
Below is a sample of a questionaire for the students. But keep contact to the students during the project, also outside the lab/classroom to get a feeling for how the group is working and what they might need from you.

====''EXAMPLE:'' Feedback questionnaire====
We would like you to write a brief answer to the following questions, so we can improve the supervision and overall teaching of courses:

The theory and background:
*Has the goal of the project been clear to you ?
*Have you been in doubt about why you were doing something (if yes, please give an example) ?
*Did you find the project matched and challenged your knowledge, or was it too easy/difficult ?
*How did your supervisor teach you - did you miss some specific kind of help (more help on basic theory, more structured teaching etc.) ?
*Whats the best experience you had during the project ?
*Whats the worst experience you had during the project ?
**if you had a bad experience, what would you suggest to avoid this in the future?

Groupwork:
*Are you satisfied with your own engagement in the project ?
*Are you satisfied with your groupmembers engagement ?
*What kind of problems did you encounter in the team and why did they occur ?
*Did you manage to distribute the workload evenly ?
*Did you manage to follow your strategy plan ?
*Could /should you supervisor help you more with how the group works, and how ? 

==Teaching portfolio==
Writing down in your CV or in a teaching portfolio what you have been working on and how you have approached the teaching with various methods depending on the aim and students level is a valuable source of inspiration when you get the 'grand picture' rather than solving day to day problems.

==Video feedback==
Nobody seems to like this, but having your teaching recorded on video and the having a look at yourself afterwards is probably a very efficient way to see what you could improve...

{{BookCat}}</text>
      <sha1>fcsuajc0f89footvz5u4jsj7krm8fpv</sha1>
    </revision>
  </page>
  <page>
    <title>Wikibooks:Reading room/General</title>
    <ns>4</ns>
    <id>112405</id>
    <revision>
      <id>4676695</id>
      <parentid>4676442</parentid>
      <timestamp>2026-10-18T06:22:06Z</timestamp>
      <contributor>
        <username>Pine</username>
        <id>504037</id>
      </contributor>
      <comment>/* October 2026 Wikimedia Café: legal issues on Commons, and WMF Board selection process */ new section</comment>
      <origin>4676695</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="23765" sha1="6cygworg3uj3fe1by2v94qm1ldzt0vp" xml:space="preserve">__NEWSECTIONLINK__ {{Discussion Rooms}} {{Shortcut|WB:CHAT|WB:RR/G|WB:GENERAL}} {{TOC left|limit=3}}
{{User:MiszaBot/config
|archive = Wikibooks:Reading room/Archives/%(year)d/%(monthname)s
|algo = old(60d)
|counter = 1
|minthreadstoarchive = 1
|minthreadsleft = 1
|key = 7a0ac23cf8049e4d9ff70cabb5649d1a
}}
Welcome to the '''General reading room'''. On this page, Wikibookians are free to talk about the Wikibooks project in general. For proposals for improving Wikibooks, see the [[../Proposals/]] reading room.
{{clear}}

[[Category:Reading room]]

== Call for administrators ==

Any experienced editor who has a good understanding of Wikibooks' policies should consider applying for administrator permissions at [[Wikibooks:Requests for permissions]]. Thank you. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 22:10, 5 August 2026 (UTC)

:Is there a page here that describes what admins do? I am curious because I checked [https://en.wikibooks.org/wiki/Special:ListUsers?username=&amp;group=sysop&amp;wpsubmit=&amp;wpFormIdentifier=mw-listusers-form&amp;limit=50 List of admins] and I see that there are already quite a few admins here and wonder which areas have a shortage.
:Just curious. [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 00:56, 16 September 2026 (UTC)
::[[Wikibooks:Administrators]]. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 01:09, 16 September 2026 (UTC)

== Wikibooks project is not defined by goal ==

If it is for texbooks why is it called Wikibooks? It should be called Wikitextbooks! If it is for textbooks why does it contain cookbooks? For textbooks it's not supposed to have a [[Wikibooks:Featured books]]. [[User:Vivairan2|Vivairan2]] ([[User talk:Vivairan2|discuss]] • [[Special:Contributions/Vivairan2|contribs]]) 09:20, 1 September 2026 (UTC)

:It's &quot;textbooks&quot; broadly construed: guides, manuals, how-tos, etc. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 11:15, 1 September 2026 (UTC)
::So we should change &quot;Wikibooks:Featured books&quot; to &quot;Wikibooks:Featured texts&quot;. [[User:Vivairan2|Vivairan2]] ([[User talk:Vivairan2|discuss]] • [[Special:Contributions/Vivairan2|contribs]]) 11:17, 1 September 2026 (UTC)
:::I disagree and even if I agreed, it would be priority #49,389. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 11:20, 1 September 2026 (UTC)
::::It's according to community consensus that says this website contains textbooks not books. [[User:Vivairan2|Vivairan2]] ([[User talk:Vivairan2|discuss]] • [[Special:Contributions/Vivairan2|contribs]]) 11:23, 1 September 2026 (UTC)
:::::&quot;[[wb:WIW|Simply, Wikibooks is a collection of open-content textbooks.]]&quot; [[User:Vivairan2|Vivairan2]] ([[User talk:Vivairan2|discuss]] • [[Special:Contributions/Vivairan2|contribs]]) 11:26, 1 September 2026 (UTC)
:Most textbooks are made by collaboration of some authors, co-authors and editors. Wikibooks help pages and guidelines remain silent when it comes to stages of writing a new texbooks. Even [[Using Wikibooks]] is not complete emough for enthusiasts. --[[User:Vivairan2|Vivairan2]] ([[User talk:Vivairan2|discuss]] • [[Special:Contributions/Vivairan2|contribs]]) 18:13, 3 September 2026 (UTC)
:@[[User:Vivairan2|Vivairan2]], In my opinion this is a good question. I wish more users would chime in. [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 16:10, 19 September 2026 (UTC)

== Wishlist 2027, invitation to share feedback ==

Hi, I’m [[m:User:SPerry-WMF|Sonja]] and I lead some of the [[mw:Contributors|teams]] at the Foundation who will be responsible for picking up wish work under the new wishlist process.

As you may know, the [[m:Community_Wishlist|Community Wishlist]] started out as an annual process through which Wikimedia contributors submit and vote on technical improvements they would like the Wikimedia Foundation to work on. The main goal of it is and has been to improve the editing experience by making changes and features the community asks for specifically.

In recent years, the process behind the wishlist has changed, and we’ve heard from many of you that it no longer meets many community members’ needs. So now, the Foundation is designing a new process with the community to improve how wishes are triaged, voted on, and prioritized in a way that is transparent, balanced across project families and language editions, and takes into account what the Foundation can deliver.

I would like to get community input specifically on these three stages of the Wishlist process:

* The [[m:Special:MyLanguage/Community_Wishlist/Community_Wishlist_2027#triage|'''triage stage''']], meaning how wishes are fleshed out, organized and filtered prior to voting
** We recommend to have a working group, including volunteers from various wikis and Wikimedia Foundation staff to work through this together
* The [[m:Special:MyLanguage/Community_Wishlist/Community_Wishlist_2027#vote|'''voting stage''']], including who may vote and how votes are structured
* The [[m:Special:MyLanguage/Community_Wishlist/Community_Wishlist_2027#postvote|'''post-vote stage''']], including how to bring equity into what work is prioritized
** One way to do this is to rank wishes within 3 categories: Large Wikipedias or covering all wikis, small and medium-sized Wikipedias, and '''sister projects''', so that top-voted wishes from smaller projects also get attention

This message is an abstract of the full proposed process. As you [[m:Special:MyLanguage/Community_Wishlist/Community_Wishlist_2027|read the proposed ideas on Meta]] (available in your language), please speak up about whether you think this will work well or if there are ways to make it stronger.

Regarding the timeline, this consultation is open for two weeks. You can post your feedback on Meta (in your preferred language) or in response below.

For this year’s cycle, [[m:Special:MyLanguage/Community_Wishlist/Community_Wishlist_2027#timeline|we plan]] to have the wish submission period in late October/early November and the triage process completed by late November. To respect the end-of-year holiday season, voting would happen in early to mid January. This first voting cycle is meant as a first step to try out a new process, and there will be more opportunities to provide feedback along the way, so that we can figure out the best process for future years together.

[[oldwikisource:M:User:SPerry-WMF|SPerry-WMF]], delivered by [[User:Trizek (WMF)|Trizek (WMF)]] ([[User talk:Trizek (WMF)|discuss]] • [[Special:Contributions/Trizek (WMF)|contribs]]) 13:52, 1 September 2026 (UTC)

:Thank you to everyone who engaged in the discussion around [[m:Talk:Community_Wishlist/Community_Wishlist_2027|the proposal from August 26]]. We've processed your feedback and [https://meta.wikimedia.org/w/index.php?title=Community_Wishlist/Community_Wishlist_2027&amp;diff=prev&amp;oldid=31041090 made changes] accordingly. Note that we weren’t able to implement all of it for this cycle, mostly for logistical reasons, but this is merely meant to be a first step and we will continue to improve this process with you all before we run through the next cycle. We plan to use [[m:Community_Wishlist/Community_Wishlist_2027#Updated_Community_Wishlist_Process_2027/2028|this updated version]] for the Wishlist 2027, and we look forward to hearing from you all during the submission and voting periods.
:[[:M:User:SPerry-WMF|SPerry-WMF]], delivered by [[User:Trizek (WMF)|Trizek (WMF)]] ([[User talk:Trizek (WMF)|discuss]] • [[Special:Contributions/Trizek (WMF)|contribs]]) 14:49, 17 September 2026 (UTC)
::@[[User:SPerry-WMF|User:SPerry-WMF]],@[[User:Trizek (WMF)|Trizek (WMF)]]: Thank you for posting info regarding the wishlist to the English Wikibooks. I am sure there are many new users here who can benefit.
::I used to participate in those discussions years ago and I know a lot of effort goes into making discussions useful not only for users of wikipedia, but also for the many language versions of the smaller wikimedia projects such as Wikibooks. [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 16:28, 19 September 2026 (UTC)

== How Do I Get My Book On A Shelf? ==

Help, I don't know how shelves work. I don't know how to put my book on a shelf. Can anyone help?
The book is called''' Art And AI''' [[User:3MMPEYTON|3MMPEYTON]] ([[User talk:3MMPEYTON|discuss]] • [[Special:Contributions/3MMPEYTON|contribs]]) 23:00, 8 September 2026 (UTC)
: Which shelf are you referring? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:45, 10 September 2026 (UTC)

== Who is allowed to delete pages here? ==

On Aug 14, 2026 a user by the name of Max deleted a page I created in my user space. I don't see max in the list of admins here. Do they have the right to delete pages? Is there any documentation here I can consult?

Thanks in advance, [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 22:38, 15 September 2026 (UTC)

:We have local admins who have the technical ability to delete pages and virtually all material deleted here would be done by us (I'm one of them). A fairly small amount of users have global rights across all Wikimedia Foundation wikis and they will very rarely make deletions (e.g. if there are some kind of legal implications to material). [[User:Ottawahitech/American politics]] was deleted by [[User:Max]], who has [[Special:UserRights/Max|no special rights here]] but is one of the [[:m:Global sysops|global sysops]] I mentioned earlier. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 22:55, 15 September 2026 (UTC)
: Probably unrelated to the above, but Ottawahitech should do that with their account, unless if they are blocked. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 23:33, 15 September 2026 (UTC)
::Agreed and [[User:Ottawahitech]] is not blocked here, so no idea why he's using a temp account. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 23:43, 15 September 2026 (UTC)
:::There may be many reasons registered users are &quot;editing&quot; without logging in. Is it possible that they want to go about peacefully without attracting too much attention? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 15:01, 16 September 2026 (UTC)
:::: We neither have a policy nor a guideline about this, probably. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:12, 20 September 2026 (UTC)
::::Notwithstanding a claim that the temp account is actually User:Ottawahitech, we have no idea that they are the same person. If the temp account is the same person, and they want to have a user space page, they can create temp account ones. The registered user account pages are intended for that registered user account and not as a dumping ground for anyone to create pages. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 08:29, 13 October 2026 (UTC)

== Assistance to get page reviewed ==

My page is a translation page: [[Baiyi Zhuan]] 

It is a single page, it is translated according to my own ability and familiarity with the language with a disclosure on external tools. I would like it to get reviewed if possible as I do not have the rights.  [[User:Taitesena|Taitesena]] ([[User talk:Taitesena|discuss]] • [[Special:Contributions/Taitesena|contribs]]) 11:19, 18 September 2026 (UTC)

== Translation of books ==

Hello,
I would like to translate books from other Wikibooks into English. Are there any guidelines regarding how to do this? [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:34, 20 September 2026 (UTC)
: This has yet to be expanded, but you might want to take a look at [[Wikibooks:Content translation]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:13, 20 September 2026 (UTC)

== Feedback on Wikibooks redirect ==

I would like your feedback on my proposal to make [[Wikibooks:Username|this page]] redirect to [[Using Wikibooks/Setting Up A User Account#Choosing a Username|this page]]? I would do it myself, but it is not possible due to the fact that [[Wikibooks:Username]] can only be made by admins. This is because [[Wikibooks:Username policy]] also links to [[Using Wikibooks/Setting Up A User Account#Choosing a Username|this page]]. Regards, [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 04:37, 21 September 2026 (UTC)

:{{support}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 00:00, 22 September 2026 (UTC)
:This seems like a good idea to me. [[User:Alextejthompson|''Alextejthompson'']] (''Ping me or leave a message on my [[User talk:Alextejthompson|talk page]]'') 17:49, 21 September 2026 (UTC)
: {{done}}, I restored the redirect per consensus here. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:03, 13 October 2026 (UTC)

== Pages created by [[User:Sisterian]] ==

I have checked with AI checkers (GPTZero, ZeroGPT) and they claim that these pages have been made with the use of GenAI. I do not know whether this is correct or not; because yes, AI checkers can and do make mistakes. I have tried reaching out to the person via talk page, to no response. I am asking for input just to see what the future of these pages are. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 12:00, 22 September 2026 (UTC)

:Thank you for flagging this @[[User:TechVindicator|TechVindicator]]. I have looked at these pages personally, and there is fairly conclusive evidence that this user has been using genAI/LLMs for their contributions. I have warned them accordingly. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 20:50, 22 September 2026 (UTC)

== I'm in the process of creating a separate page describing the removal of admin permissions ==

As the section title says, please see [[User:Codename Noreste/sandbox]] and feel free to make any adjustments. We might consider moving this to [[Wikibooks:Administrators/De-adminship]] someday. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:05, 24 September 2026 (UTC)

== Your feedback wanted: Remove ''(Language link added:) and similar'' edits from Special:RecentChanges ==

''(Apologies for posting in English. You can help by translating it)''

Hello, I’m Danny from [[:en:w:Wikimedia_Deutschland|Wikimedia Deutschland’s]] [[m:Wikidata_For_Wikimedia_Projects|Wikidata For Wikimedia Projects]] team.&lt;br/&gt;
We have been investigating and examining how Wikidata’s use in the [[Special:RecentChanges]] and [[Special:Watchlist]] pages can be made to be more useful, or less ‘noisy’ (fewer edits that have little value to the reader).

We are currently exploring to make a change in the volume and the type of Wikidata edits that appear in these pages, and '''we need your feedback''' to help us ensure this is a positive change for the Wikis and won’t disrupt your workflows.&lt;br/&gt;
Language links are also known as sitelinks or interlanguage links and describe when a Wikidata item is connected to a Wiki, adding it to the language dropdown tool for other connected Wikis.
[[File:Types of Lang Link changes.png|x350px|frame|A variety of &quot;Language Link&quot; edits as seen in the Recent Changes feed]]

The request for feedback is whether you support the removal of these language link edits from the Recent Changes and Watchlist feed, or would you oppose such a change and if so, why?
Please share you thoughts on the dedicated '''[[m:Talk:Wikidata_For_Wikimedia_Projects/Clearer_Wikidata_Edit_Summaries/Hide_Language_Link_edits|metawiki Talk page]]'''. 

Further information about this change: [[m:Wikidata_For_Wikimedia_Projects/Clearer_Wikidata_Edit_Summaries/Hide_Language_Link_edits|m:Wikidata_For_Wikimedia_Projects/Hide_Language_Link_edits]]

Thank you for any participation or feedback you give, -- [[m:User:Danny_Benjafield_(WMDE)|User:Danny Benjafield (WMDE)]] 11:46, 25 September 2026 (UTC)
&lt;!-- Message sent by User:Danny Benjafield (WMDE)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=User:Danny_Benjafield_(WMDE)/MassMessage_test_list&amp;oldid=31080832 --&gt;

== FlaggedRevs again ==

&lt;div class=&quot;cd-moveMark&quot;&gt;''Moved to [[Wikibooks:Reading room/Proposals#FlaggedRevs again]].  [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:01, 1 October 2026 (UTC)''&lt;/div&gt;

== Wikidata Sitelink changes in Recent Changes and Watchlist ==

''(Apologies for cross-posting in English, translating it will help spread the message)''

Editors on group 1 wikis, including Wikiquote, Wikibooks, Wikiversity, Wikivoyage, and Wikisource, will no longer see notifications on [[Special:RecentChanges|Recent Changes]] and [[Special:Watchlist|Watchlist]] when a link to ''another'' language version of a page is added, removed, or changed in its Wikidata item. This change will begin on '''October 5 at 07:00 UTC''' as a two-week trial to reduce high-volume, low-value notifications and make higher-value changes easier to identify. Editors who rely on these notifications should be aware of the change and can share feedback or concerns on the [[m:Wikidata For Wikimedia Projects/Clearer Wikidata Edit Summaries/Hide Language Link edits|project]] or [[m:Talk:Wikidata_For_Wikimedia_Projects/Clearer_Wikidata_Edit_Summaries/Hide_Language_Link_edits|talk page]].&lt;br/&gt;Please reach out if you have any questions, thank you! -- [[User:Danny_Benjafield_(WMDE)|Danny Benjafield (WMDE)]] ([[User_talk:Danny_Benjafield_(WMDE)|talk]])  sent via [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 12:42, 1 October 2026 (UTC)
&lt;!-- Message sent by User:Danny Benjafield (WMDE)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=User:Danny_Benjafield_(WMDE)/MassMessage_test_list&amp;oldid=31106967 --&gt;

== Approved Revs extension ==

If we were to have this extension, we should only limit this to the Wikijunior namespace, since we will eventually stop using FlaggedRevs, unless if we want Approved Revs to work in another namespace.

Remember, this is not a vote, but an overall discussion. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 01:17, 11 October 2026 (UTC)

== An apology ==
Due to the removal of the &lt;code&gt;editor&lt;/code&gt; and &lt;code&gt;autoreview&lt;/code&gt; user groups and my failure to immediately correct the [https://github.com/JJPMaster/jjpmaster-bot-enwb-t1 code of  my bot], the markAdmins gadget data has not been updated for 39 hours. I apologize if anyone has been affected. [https://github.com/JJPMaster/jjpmaster-bot-enwb-t1/commit/65e615ef04d82500674a3711f2d99fe7cd8968d0 This commit] corrected the problem. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 06:05, 17 October 2026 (UTC)

== October 2026 Wikimedia Café: legal issues on Commons, and WMF Board selection process ==
&lt;div class=&quot;border-box&quot; style=&quot;background-color: var(--background-color-warning-subtle, #f8eaba); max-width: 875px; padding: 5px; border: 1px solid black; margin: 5px; color: var(--clr-dark)&quot;&gt;
&lt;div class=&quot;box&quot; style=&quot;float:left; padding-top: 10px; padding-right: 10px; padding-left: 10px; padding-bottom: 10px;&quot;&gt;[[File:Wikimedia Café logo in plain SVG format.svg|60px|alt=The logo for the Wikimedia Café]]&lt;/div&gt;
Hello! There will be two '''[https://meta.wikimedia.org/wiki/Wikimedia_Caf%C3%A9 Wikimedia Café]''' discussion opportunities in October. In a change from the usual Café practice, this month's sessions will have different topics. Anyone who meets the Café attendance criteria is welcome to attend either or both sessions.

Session A will happen on Saturday, 24 October 2026 at 15:00 UTC ([https://zonestamp.toolforge.org/1792854000 timestamp converter]), at a time friendly to the Americas, Africa, and Europe. This session will feature [https://meta.wikimedia.org/wiki/User:PBradley-WMF Wikimedia Foundation lawyer Phil Bradley-Schmieg]. We will discuss legal issues on Wikimedia Commons, including complexities of international law. (I am hoping that in a future month, a similar Café session will be offered at a time friendly to Asia and the Pacific.)

Session B will happen on Sunday, 25 October 2026 at 03:00 UTC ([https://zonestamp.toolforge.org/1792897200 timestamp converter]), at a time friendly to Asia and the Pacific, we will discuss [https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections/2027/Proposed_eligibility_criteria proposed changes to how Wikimedia Foundation Board candidates are selected]. The latest proposals are much different from the earlier July 2026 proposals. The due date for feedback on current proposals is 27 October, and Wikimedians are welcome to participate on the [https://meta.wikimedia.org/wiki/Talk:Wikimedia_Foundation_elections/2027/Proposed_eligibility_criteria proposal talk page] regardless of Café attendance.

Please see the [https://meta.wikimedia.org/wiki/Wikimedia_Caf%C3%A9 Café] page for more information, including [https://meta.wikimedia.org/wiki/Wikimedia_Caf%C3%A9#How_to_attend_the_session how to register]!

To subscribe or unsubscribe for Café notices on your talk page please [https://meta.wikimedia.org/wiki/Global_message_delivery/Targets/Wikimedia_Caf%C3%A9 go here].
&lt;br /&gt;
[[File:Buntstifte Eberhard Faber crop 64h.jpg|860px|alt=cropped image of colored pencils]]&lt;/div&gt;
&lt;span style=&quot;white-space:nowrap;&quot;&gt;[[User:Pine|&lt;span style=&quot;color:#01796f; text-shadow:#00BFFF 0 0 1.0em&quot;&gt;༄ᨒ𖠰 Pine&lt;/span&gt;]] [[User talk:Pine|&lt;span style=&quot;color:DeepSkyBlue&quot;&gt;(&lt;b style=&quot;color:#FFDF00;text-shadow:#FFDF00 0 0 1.0em&quot;&gt;✉&lt;/b&gt;)&lt;/span&gt;]]&lt;/span&gt; 06:22, 18 October 2026 (UTC)</text>
      <sha1>6cygworg3uj3fe1by2v94qm1ldzt0vp</sha1>
    </revision>
  </page>
  <page>
    <title>Wikibooks:Reading room/Administrative Assistance</title>
    <ns>4</ns>
    <id>140081</id>
    <revision>
      <id>4676702</id>
      <parentid>4676477</parentid>
      <timestamp>2026-10-18T08:10:40Z</timestamp>
      <contributor>
        <username>ArchiverBot</username>
        <id>1227662</id>
      </contributor>
      <minor />
      <comment>Bot: Archiving 1 thread (older than 14 days) to [[Wikibooks:Reading room/Administrative Assistance/Archives/2026/October]]</comment>
      <origin>4676702</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4795" sha1="69ng8qlc8fzjsi8sfmptxw8575fcfpc" xml:space="preserve">{{/Header}} {{User:MiszaBot/config
|archive = Wikibooks:Reading room/Administrative Assistance/Archives/%(year)d/%(monthname)s
|algo = old(14d)
|counter = 1
|minthreadstoarchive = 1
|minthreadsleft = 1
}}

== ~2026-51118-27 reported by EggRoll97 ==

* {{anonlinks|~2026-51118-27}}

Vandalism &lt;!-- USERREPORTED:/~2026-51118-27/ --&gt; [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 07:28, 4 October 2026 (UTC)
: {{done}} by NDG (GS). [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:13, 4 October 2026 (UTC)
== ~2026-53393-86 reported by MathXplore ==

* {{anonlinks|~2026-53393-86}}

Vandalism &lt;!-- USERREPORTED:/~2026-53393-86/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:37, 5 October 2026 (UTC)

:Various contributions deleted—watching to see how this develops. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:15, 5 October 2026 (UTC)

== [[CustomChessTheory]] ==

Reason for reporting: Wrong title, renaming needed. [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:45, 5 October 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 15:21, 8 October 2026 (UTC)

== Siddhgiritubes reported by MathXplore ==

* {{userlinks|Siddhgiritubes}}

Spam &lt;!-- USERREPORTED:/Siddhgiritubes/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:31, 7 October 2026 (UTC)
: Page deleted by JJPMaster. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 15:09, 8 October 2026 (UTC)

== Editbots reported by MathXplore ==

* {{userlinks|Editbots}}

Link spam ([[Special:AbuseLog/316068]], [[Special:Contributions/~2026-54143-79]]) &lt;!-- USERREPORTED:/Editbots/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:13, 8 October 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 15:10, 8 October 2026 (UTC)
== Lenawalker1 reported by TechVindicator ==

* {{userlinks|Lenawalker1}}

Spam &lt;!-- USERREPORTED:/Lenawalker1/ --&gt; [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 04:07, 10 October 2026 (UTC)

:{{done|Dealt with}} by SHB —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 04:31, 11 October 2026 (UTC)
== Cleanwipes reported by MathXplore ==

* {{userlinks|Cleanwipes}}

Link spam, [[Special:AbuseLog/316154]] &lt;!-- USERREPORTED:/Cleanwipes/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:21, 14 October 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 15:20, 14 October 2026 (UTC)

== Suniluv2026 reported by MathXplore ==

* {{userlinks|Suniluv2026}}

Link spam, [[Special:AbuseLog/316149]] &lt;!-- USERREPORTED:/Suniluv2026/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:22, 14 October 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 15:21, 14 October 2026 (UTC)
== Rudrashares01 reported by MathXplore ==

* {{userlinks|Rudrashares01}}

Spam &lt;!-- USERREPORTED:/Rudrashares01/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:26, 15 October 2026 (UTC)

:{{done}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:25, 15 October 2026 (UTC)
== Rimshad12 reported by Morkoz ==

* {{userlinks|Rimshad12}}

Spam ([[:m:special:GlobalContributions/Rimshad12|cross-wiki]]) &lt;!-- USERREPORTED:/Rimshad12/ --&gt; [[User:Morkoz|Morkoz]] ([[User talk:Morkoz|discuss]] • [[Special:Contributions/Morkoz|contribs]]) 06:06, 16 October 2026 (UTC)

:{{done|Locked}} --[[User:SHB|SHB]] ([[User talk:SHB|discuss]] • [[Special:Contributions/SHB|contribs]]) 11:41, 16 October 2026 (UTC)</text>
      <sha1>69ng8qlc8fzjsi8sfmptxw8575fcfpc</sha1>
    </revision>
  </page>
  <page>
    <title>Wikibooks:Requests for import</title>
    <ns>4</ns>
    <id>140082</id>
    <revision>
      <id>4676698</id>
      <parentid>4669472</parentid>
      <timestamp>2026-10-18T07:21:32Z</timestamp>
      <contributor>
        <username>TechVindicator</username>
        <id>3626296</id>
      </contributor>
      <comment>/* Import this page→ User:TechVindicator/Wikibooks Magazine Layout */ new section</comment>
      <origin>4676698</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="6163" sha1="ednk1egrcaw50sjmqt3g033mm5jkany" xml:space="preserve">{{User:MiszaBot/config
|archive = Wikibooks:Requests for import/Archives/%(year)d/%(monthname)s
|algo = old(31d)
|counter = 1
|minthreadstoarchive = 1
|minthreadsleft = 1
|key = 
}}

__NEWSECTIONLINK__ {{Discussion Rooms}} {{shortcut|WB:RFI}} {{TOC left}}{{clear}}

=== Importing and import uploading ===

To preserve edit histories and observe the attribution requirements of the licenses, content from our sister projects should be '''imported''' rather than simply pasted into a new module. 

* [[Wikibooks:Importers|Importers]] can import pages from any of the English-language projects, Simple English Wikibooks, Meta, and Wikispecies.
* [[Wikibooks:Administrators|Administrators]], and import uploaders, can import from any wiki (even non-WMF).

'''Requests to import''' can be made to help in making or expanding a book, and to move works from other projects that fit [[Wikibooks:What is Wikibooks|Wikibooks' scope]]. 

* Place requests below and an administrator or importer will try to perform the import promptly.
* Note that administrators and importers are not responsible for moving and cleaning up pages. Please watch this page for when the import is complete and take care of the imported page.

'''Administrators and importers:''' 
* Please read [[Help:Importing]] first. 
* To import a page, go to [[Special:Import]]. 
* Pages will by default import into &lt;code&gt;Transwiki:Page's name&lt;/code&gt;, which can be moved to a new location.
* After import, add {{tl|dewikify}} to the page and make a note where the imported page has ended up. 
* Pages with extremely long edit histories may fail to import. In this case, a single revision which gives attribution to the source wiki will be imported. While this isn't ideal, it should satisfy our [[WB:CC-BY-SA|licensing]].  Note that repeated attempts to import may eventually bring over the history, so if it fails on the first attempt, you might want to try it a few more times. Please see [[phab:17000|T17000]], and ask for it to be resolved sooner.

{{Warning|In some cases an import may partially fail and need to be repeated. If this happens, the revisions may be out of sequence in the history so you need to check the current revision is the one you want to use as the base for your book}}

=== Non-free media uploading ===

'''Where non-free media is required''' in a book, editors may request an administrator or [[Wikibooks:Uploaders|uploader]] to upload the file by making a request at [[Wikibooks:Files for upload|files for upload]].

{{clear}}

=Import and Merge=
''Use this section for imports that need to be &quot;history-merged&quot; with a module that has already been started using copy-paste.''

Add requests using the form: &lt;pre&gt;*[[Project:Page name]] &amp;rarr; [[Target Page]] ~~~~&lt;/pre&gt;

== Import request: Transwiki: Laplace Transform ==

Hello, I'd like to request to import
https://en.wikibooks.org/wiki/Transwiki:Laplace_transform
(part of the curriculum of Differential Equations) to the book [[Ordinary Differential Equations]].

Neither seem to me to be actively maintained.
I believe the import within the scope of this project since there the book is completely missing the Transwiki topic. [[User:DavidMDay|DavidMDay]] ([[User talk:DavidMDay|discuss]]) 20:20, 11 August 2026 (UTC)

:I'm a little confused: the page is already imported here and [[Ordinary Differential Equations/Laplace Transform]] already exists. Do you want someone to merge the histories or overwrite the existing page or something? ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 22:06, 11 August 2026 (UTC)
:: Pinging [[User:DavidMDay|DavidMDay]] to Koavf's response above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 21:17, 31 August 2026 (UTC)
:Hi Justin, It's great to communicate with you.  I am '''new''' to Wikipedia and almost surely more confused than you.     My suggestion is to expand, but not revise, the book by appending the wiki page.  I do find this to be a big improvement.   I am guessing that orphan Wiki pages with long life spans are adopted by Wiki books that are missing the content.
:I did make a trivial change to the main page for the book.  The revision is pending review.  Did I do something wrong?  I don't remember the details.  If nothing is wrong, did I optionally request a review, or are reviews required?
:I do not know how revision history is archived at Wiki books.  The text of the revision history of the page could be included in the commit message that appends it to the book, for example.  I do not know the rules, much less the practices, at Wiki books.   I worry more about things like figuring out how to leave a webpage that I have opened.
:Yes, the book does have a section of a chapter is on the topic of the Wiki page.  The wiki page could be added after this section, instead of creating a new chapter.  Or nothing will happen.  In any case, thanks for responding and for your kind note,  -- David [[User:DavidMDay|DavidMDay]] ([[User talk:DavidMDay|discuss]] • [[Special:Contributions/DavidMDay|contribs]]) 20:05, 9 September 2026 (UTC)
::{{Ping|DavidMDay}} No worries: I think the material that you wanted to be here is already here. If it's not, please let me know. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 23:53, 9 September 2026 (UTC)

== Import [https://wikikids.nl/Sjabloon:WikiKids_Magazine_layout this page]→ [[User:TechVindicator/Wikibooks Magazine Layout]]  ==
Hello, could the page be imported please? The page is licensed under the CC-BY-SA-3.0 license (see [https://wikikids.nl/Wikikids:Voorwaarden this]) It will be translated. Thank you. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 07:21, 18 October 2026 (UTC)</text>
      <sha1>ednk1egrcaw50sjmqt3g033mm5jkany</sha1>
    </revision>
    <revision>
      <id>4676699</id>
      <parentid>4676698</parentid>
      <timestamp>2026-10-18T07:22:52Z</timestamp>
      <contributor>
        <username>TechVindicator</username>
        <id>3626296</id>
      </contributor>
      <minor />
      <comment>/* Import this page→ User:TechVindicator/Wikibooks Magazine Layout */</comment>
      <origin>4676699</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="6420" sha1="0p9fp1glsx5mgqgbmtxhrfyix029g37" xml:space="preserve">{{User:MiszaBot/config
|archive = Wikibooks:Requests for import/Archives/%(year)d/%(monthname)s
|algo = old(31d)
|counter = 1
|minthreadstoarchive = 1
|minthreadsleft = 1
|key = 
}}

__NEWSECTIONLINK__ {{Discussion Rooms}} {{shortcut|WB:RFI}} {{TOC left}}{{clear}}

=== Importing and import uploading ===

To preserve edit histories and observe the attribution requirements of the licenses, content from our sister projects should be '''imported''' rather than simply pasted into a new module. 

* [[Wikibooks:Importers|Importers]] can import pages from any of the English-language projects, Simple English Wikibooks, Meta, and Wikispecies.
* [[Wikibooks:Administrators|Administrators]], and import uploaders, can import from any wiki (even non-WMF).

'''Requests to import''' can be made to help in making or expanding a book, and to move works from other projects that fit [[Wikibooks:What is Wikibooks|Wikibooks' scope]]. 

* Place requests below and an administrator or importer will try to perform the import promptly.
* Note that administrators and importers are not responsible for moving and cleaning up pages. Please watch this page for when the import is complete and take care of the imported page.

'''Administrators and importers:''' 
* Please read [[Help:Importing]] first. 
* To import a page, go to [[Special:Import]]. 
* Pages will by default import into &lt;code&gt;Transwiki:Page's name&lt;/code&gt;, which can be moved to a new location.
* After import, add {{tl|dewikify}} to the page and make a note where the imported page has ended up. 
* Pages with extremely long edit histories may fail to import. In this case, a single revision which gives attribution to the source wiki will be imported. While this isn't ideal, it should satisfy our [[WB:CC-BY-SA|licensing]].  Note that repeated attempts to import may eventually bring over the history, so if it fails on the first attempt, you might want to try it a few more times. Please see [[phab:17000|T17000]], and ask for it to be resolved sooner.

{{Warning|In some cases an import may partially fail and need to be repeated. If this happens, the revisions may be out of sequence in the history so you need to check the current revision is the one you want to use as the base for your book}}

=== Non-free media uploading ===

'''Where non-free media is required''' in a book, editors may request an administrator or [[Wikibooks:Uploaders|uploader]] to upload the file by making a request at [[Wikibooks:Files for upload|files for upload]].

{{clear}}

=Import and Merge=
''Use this section for imports that need to be &quot;history-merged&quot; with a module that has already been started using copy-paste.''

Add requests using the form: &lt;pre&gt;*[[Project:Page name]] &amp;rarr; [[Target Page]] ~~~~&lt;/pre&gt;

== Import request: Transwiki: Laplace Transform ==

Hello, I'd like to request to import
https://en.wikibooks.org/wiki/Transwiki:Laplace_transform
(part of the curriculum of Differential Equations) to the book [[Ordinary Differential Equations]].

Neither seem to me to be actively maintained.
I believe the import within the scope of this project since there the book is completely missing the Transwiki topic. [[User:DavidMDay|DavidMDay]] ([[User talk:DavidMDay|discuss]]) 20:20, 11 August 2026 (UTC)

:I'm a little confused: the page is already imported here and [[Ordinary Differential Equations/Laplace Transform]] already exists. Do you want someone to merge the histories or overwrite the existing page or something? ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 22:06, 11 August 2026 (UTC)
:: Pinging [[User:DavidMDay|DavidMDay]] to Koavf's response above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 21:17, 31 August 2026 (UTC)
:Hi Justin, It's great to communicate with you.  I am '''new''' to Wikipedia and almost surely more confused than you.     My suggestion is to expand, but not revise, the book by appending the wiki page.  I do find this to be a big improvement.   I am guessing that orphan Wiki pages with long life spans are adopted by Wiki books that are missing the content.
:I did make a trivial change to the main page for the book.  The revision is pending review.  Did I do something wrong?  I don't remember the details.  If nothing is wrong, did I optionally request a review, or are reviews required?
:I do not know how revision history is archived at Wiki books.  The text of the revision history of the page could be included in the commit message that appends it to the book, for example.  I do not know the rules, much less the practices, at Wiki books.   I worry more about things like figuring out how to leave a webpage that I have opened.
:Yes, the book does have a section of a chapter is on the topic of the Wiki page.  The wiki page could be added after this section, instead of creating a new chapter.  Or nothing will happen.  In any case, thanks for responding and for your kind note,  -- David [[User:DavidMDay|DavidMDay]] ([[User talk:DavidMDay|discuss]] • [[Special:Contributions/DavidMDay|contribs]]) 20:05, 9 September 2026 (UTC)
::{{Ping|DavidMDay}} No worries: I think the material that you wanted to be here is already here. If it's not, please let me know. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 23:53, 9 September 2026 (UTC)

== Import [https://wikikids.nl/Sjabloon:WikiKids_Magazine_layout this page]→ [[User:TechVindicator/Wikibooks Magazine Layout]]  ==
Hello, could the page be imported please? The page is licensed under the CC-BY-SA-3.0 license (see [https://wikikids.nl/Wikikids:Voorwaarden this]) It will be translated. Thank you. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 07:21, 18 October 2026 (UTC)
:Note that the page will be a layout for a future Wikibooks Magazine, for news about Wikibooks. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 07:22, 18 October 2026 (UTC)</text>
      <sha1>0p9fp1glsx5mgqgbmtxhrfyix029g37</sha1>
    </revision>
    <revision>
      <id>4676704</id>
      <parentid>4676699</parentid>
      <timestamp>2026-10-18T08:11:00Z</timestamp>
      <contributor>
        <username>ArchiverBot</username>
        <id>1227662</id>
      </contributor>
      <minor />
      <comment>Bot: Archiving 1 thread (older than 31 days) to [[Wikibooks:Requests for import/Archives/2026/September]]</comment>
      <origin>4676704</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3486" sha1="ohxr7vlr9zvx6twsfqq6ly0hpmf02hi" xml:space="preserve">{{User:MiszaBot/config
|archive = Wikibooks:Requests for import/Archives/%(year)d/%(monthname)s
|algo = old(31d)
|counter = 1
|minthreadstoarchive = 1
|minthreadsleft = 1
|key = 
}}

__NEWSECTIONLINK__ {{Discussion Rooms}} {{shortcut|WB:RFI}} {{TOC left}}{{clear}}

=== Importing and import uploading ===

To preserve edit histories and observe the attribution requirements of the licenses, content from our sister projects should be '''imported''' rather than simply pasted into a new module. 

* [[Wikibooks:Importers|Importers]] can import pages from any of the English-language projects, Simple English Wikibooks, Meta, and Wikispecies.
* [[Wikibooks:Administrators|Administrators]], and import uploaders, can import from any wiki (even non-WMF).

'''Requests to import''' can be made to help in making or expanding a book, and to move works from other projects that fit [[Wikibooks:What is Wikibooks|Wikibooks' scope]]. 

* Place requests below and an administrator or importer will try to perform the import promptly.
* Note that administrators and importers are not responsible for moving and cleaning up pages. Please watch this page for when the import is complete and take care of the imported page.

'''Administrators and importers:''' 
* Please read [[Help:Importing]] first. 
* To import a page, go to [[Special:Import]]. 
* Pages will by default import into &lt;code&gt;Transwiki:Page's name&lt;/code&gt;, which can be moved to a new location.
* After import, add {{tl|dewikify}} to the page and make a note where the imported page has ended up. 
* Pages with extremely long edit histories may fail to import. In this case, a single revision which gives attribution to the source wiki will be imported. While this isn't ideal, it should satisfy our [[WB:CC-BY-SA|licensing]].  Note that repeated attempts to import may eventually bring over the history, so if it fails on the first attempt, you might want to try it a few more times. Please see [[phab:17000|T17000]], and ask for it to be resolved sooner.

{{Warning|In some cases an import may partially fail and need to be repeated. If this happens, the revisions may be out of sequence in the history so you need to check the current revision is the one you want to use as the base for your book}}

=== Non-free media uploading ===

'''Where non-free media is required''' in a book, editors may request an administrator or [[Wikibooks:Uploaders|uploader]] to upload the file by making a request at [[Wikibooks:Files for upload|files for upload]].

{{clear}}

=Import and Merge=
''Use this section for imports that need to be &quot;history-merged&quot; with a module that has already been started using copy-paste.''

Add requests using the form: &lt;pre&gt;*[[Project:Page name]] &amp;rarr; [[Target Page]] ~~~~&lt;/pre&gt;

== Import [https://wikikids.nl/Sjabloon:WikiKids_Magazine_layout this page]→ [[User:TechVindicator/Wikibooks Magazine Layout]] ==

Hello, could the page be imported please? The page is licensed under the CC-BY-SA-3.0 license (see [https://wikikids.nl/Wikikids:Voorwaarden this]) It will be translated. Thank you. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 07:21, 18 October 2026 (UTC)
:Note that the page will be a layout for a future Wikibooks Magazine, for news about Wikibooks. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 07:22, 18 October 2026 (UTC)</text>
      <sha1>ohxr7vlr9zvx6twsfqq6ly0hpmf02hi</sha1>
    </revision>
  </page>
  <page>
    <title>Talk:New Zealand History</title>
    <ns>1</ns>
    <id>141393</id>
    <revision>
      <id>4676568</id>
      <parentid>3327474</parentid>
      <timestamp>2026-10-17T18:24:47Z</timestamp>
      <contributor>
        <username>~2026-55888-47</username>
        <id>3628633</id>
      </contributor>
      <comment>/* Concise New Zealand History */ Reply</comment>
      <origin>4676568</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="522" sha1="elrdxe8615zklapu0e7gkb3zp42h74e" xml:space="preserve">== Concise New Zealand History ==

I have decided to change the name of the book to a Concise New Zealand History. I have done this because I have found that enormous books, especially informational ones, can be intimidating to some readers and put them off reading the book. I would like this book to be an easy read. [[User:Helpfulstuffnz|Helpfulstuffnz]] 03:24, 2 December 2007 (UTC)

:yes i agree. [[Special:Contributions/~2026-55888-47|~2026-55888-47]] ([[User talk:~2026-55888-47|talk]]) 18:24, 17 October 2026 (UTC)</text>
      <sha1>elrdxe8615zklapu0e7gkb3zp42h74e</sha1>
    </revision>
    <revision>
      <id>4676572</id>
      <parentid>4676568</parentid>
      <timestamp>2026-10-17T18:44:20Z</timestamp>
      <contributor>
        <username>~2026-55705-00</username>
        <id>3628636</id>
      </contributor>
      <comment>/* Concise New Zealand History */ Reply good point</comment>
      <origin>4676572</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="670" sha1="llaprsgxd5q1lwo745eslqzgud9sbm4" xml:space="preserve">== Concise New Zealand History ==

I have decided to change the name of the book to a Concise New Zealand History. I have done this because I have found that enormous books, especially informational ones, can be intimidating to some readers and put them off reading the book. I would like this book to be an easy read. [[User:Helpfulstuffnz|Helpfulstuffnz]] 03:24, 2 December 2007 (UTC)

:yes i agree. [[Special:Contributions/~2026-55888-47|~2026-55888-47]] ([[User talk:~2026-55888-47|talk]]) 18:24, 17 October 2026 (UTC)
:A good point made in 2007 [[Special:Contributions/~2026-55705-00|~2026-55705-00]] ([[User talk:~2026-55705-00|talk]]) 18:44, 17 October 2026 (UTC)</text>
      <sha1>llaprsgxd5q1lwo745eslqzgud9sbm4</sha1>
    </revision>
  </page>
  <page>
    <title>Solved Question Papers - IIT JEE/PhysicsSol1996</title>
    <ns>0</ns>
    <id>155713</id>
    <revision>
      <id>4676576</id>
      <parentid>4646348</parentid>
      <timestamp>2026-10-17T20:07:29Z</timestamp>
      <contributor>
        <username>WereSpielChequers</username>
        <id>248949</id>
      </contributor>
      <minor />
      <comment>typo</comment>
      <origin>4676576</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="9279" sha1="kujw3f1txg9ldd8di1iy40cczb2q5ok" xml:space="preserve">==Objectives==
===Cylindrical capacitor===
We might not have studied the structure of a cylindrical capacitor - that does not mean we can not solve this question!
So lets get started
Draw two concentric cylinders. For the electric field, we know we will use Gauss' law. The gaussian surface we choose is a cylinder of radius r (r = distance from the cente at which the field has to be found.)

Intg. E.dS = Qenc/Eo. We will not explain the simplifications on the LHS. However, simplifying it will tell you that the electric field is &lt;span style=&quot;color: red;&quot;&gt;&lt;B&gt;inversely proportional to r&lt;/b&gt;&lt;/span&gt; and not r^2.

===Field lines through a conductor===
There are two things you need to know while solving this: -
* Electric field inside a conductor is zero. So field lines (direction of electric field) are not defined inside a conductor.
* Electric field near a conductor is perpendicular to its surface, because a conducting surface is equipotential.

This immediately gives us the answer to be &lt;span style=&quot;color: red;&quot;&gt;&lt;B&gt;D&lt;/b&gt;&lt;/span&gt;.

Now we put forward some descriptive questions whose answers form a part of a normal High School Physics course.

* Why is the electric field inside a conductor always zero? (Answer relates to charge separation till equilibrium is attained between two forces. This is just a hint, the reader has to supply a CBSE styled i.e. explanatory answer.)

* Why is the electric field near an equipotent surface perpendicular to it? (Use the relation between voltage, electric field vector and displacement vector)

* The conductor was placed in an uniform electric field. Why is then the electric field not uniform now? What has caused the disturbance in it? Field lines terminate at the left surface and restart from the right surface. What does this tell you about the charge distribution on the &lt;B&gt;Neutral&lt;/B&gt; Sphere?

===RMS Speed===
Purely formulae based. We dont need to provide a solution! The answer is B.

===Virtual Images===
Note first of all that the question must be speaking of only real objects. (u &lt; 0 in standard convention)

Anyone who has drawn ray diagrams properly knows for sure that the answer is Concave lens and a Convex Mirror.

Infact, this is factual for most students. Hence, you might want to prove this using calculations. Go ahead! Do not hesitate here! Remember that whenever something is excessively imple, just pick the pen up and solve it. if you do not do it - you might not be able to reproduce those results when required.

For convex mirror - use the mirror equation to get V (image) in terms of u. Substitute V=(-X) and F=(+F) so that every term on the RHS becomes positive and can be analyzed. The magnification will always be positive u &lt; 0 meaning that the image is virtual!

Similarly for a concave lens.

Answer is &lt;span style=&quot;color: red;&quot;&gt;&lt;B&gt;B,C&lt;/B&gt;&lt;/span&gt;

===Holes===
Factual - p-type semiconductors

==On projectile motion==
===Introduction===
Collision in midair? Right. Have you ever encountered questions which, upon reading once, make you believe they are pretty difficult, but whose solution makes you slap your forehead? This is one of those typical problems. When you get down to it, there is absolutely no analysis involved! I emphasize through this example how simple questions can be made to look difficult by their presentation.

===Solution===
Shot A - The one which was launched at an angle.
Shot B - The one which was launched horizontally.

This is the first point which you need to think about. Which one of the two was launched first? Think about it, they have to collide. A has to cover the same horizontal displacement as B, but with a lesser horizontal velocity (why lesser horizontal velocity?). Its but obvious that A was launched first.

* If they collide, it just means that they are at the same position at the same instant of time. The two projectiles start from the same point, which means, in order to collide - their displacements must be same at a particular time instant.

For horizontal displacement, we have
[Hor. velocity of Particle 1] x [Time till collision] = [Hor. Vel. of particle 2] x [Time till collision]

* This is the best part about projectile motion! The horizontal motion of projectiles is uniform.

* All we have to do now is to substitute the values. Note that the time till collision for the two particles is not the same! If for the second particle it is T then for the first particle, it is T+t where t is the time interval between the firings.

Sx = xVA x (T+t) = xVB x (T)

This equation gives us T=t, after substituting the two velocities.
Sy = yVA x (T+t) - (0.5)(g)(T+t)^2 = yVB x (T) - (0.5)(g)(T)^2

Substituting T=t from the first equation and solving, we get &lt;span style=&quot;color: red;&quot;&gt;&lt;B&gt;t=1 second interval between the firings.&lt;/B&gt;&lt;/span&gt;

For the second part, we require horizontal and vertical displacements. Go back to the above equations, plug in t=1/T=1. We get Sx = 5(3)^0.5 and Sy = -5 m

The displacemtent is the final-initial coordinate, so &lt;span style=&quot;color: red;&quot;&gt;&lt;B&gt;X = 5root3 m, Y = -5 + 10 = 5 m.&lt;/B&gt;&lt;/span&gt; [Launched from (0,10), remember?]

==On adiabatic process==
===Introduction===
I just mentioned excessively simple problems in the projectile motion question above. Bless the heavens! This question on adiabatic expansion is a direct one! And direct means DIRECT! Pocket the 5 marks here - you'll have to work hard for them elsewhere.

===Final Temperature===
Use T1(V1)^(@-1) = T2(V2)^(@-1) where @ is the adiabatic exponent (gamma) of the gas, 5/3 in our case.

T2 = 300 K x (1/2)^(2/3) = &lt;span style=&quot;color: red;&quot;&gt;&lt;B&gt;189 K&lt;/B&gt;&lt;/span&gt;

===Change in internal energy===
nCv(T2-T1) = -2767J. We will not tell you what n and cv are. Please forgive us.

===Work done by the gas===
We wont even tell you the answer over here! Use the first law to relate Q, Work done (IntegPdV) and DelE.
===Note===
Please note that P(V)^@ = Constant is valid only for a reversible adiabatic process. The question paper does not mention specifically that the process carried out is reversible adiabatic. If the process were irreversible with expansion carried out against constant external pressure = final pressure, use
* PV = NRT over initial and final stages
* P(V2-V1) [Integ.PdV] + nCv(T2-T1) = 0 [Q=0. If we are dealing with adiabatic process, how can we forget to use this equation?]

Also note that this is NOT a trick question! If the student had to consider irreversible processes as well, the JEE would have given MAJOR hints pointing towards that possibility. e.g., &quot;Answer all possible cases&quot; and such.

==Question 4 - Fraunhofer Diffraction Pattern==
DIRECT Question. Two marks not to be missed!

The angular width is 2Lamda/b where b is slit width (constant).

* If by changing the wavelength we decrease the width by 30%, it is evident from the equation that the wavelength was also reduced by 30%. Hence the answer to this part is 6000 x (70/100) = 4200 Angstorms.

That is, we used light of wavelength &lt;span style=&quot;color: red;&quot;&gt;&lt;B&gt;4200 Angstorms&lt;/b&gt;&lt;/span&gt; the second time.

Now, even if the apparatus is immersed in some liquid (A hypothetical question), the answer will be judged by the change in wavelength of the 6000 A light in that medium.

It is clear that the light of wavelength 6000 A in air behaves as light of 4200 A wavelength.

* 4200 = (6000)/(Mu) giving &lt;span style=&quot;color: red;&quot;&gt;&lt;B&gt;Mu = 1.429&lt;/B&gt;&lt;/span&gt;
==Question 4 - The Prism==
===Introduction===
This is the first question that we expect prepared students to mess up at the JEE. However, bear in mind that I'm saying this just because the question involves more calculation than the others. However, it is as simple as the others.

===Critical incidence at the hypotenuse===
We are told to find that angle of incidence on AB for which the ray hits the cemented interface at the critical angle. Now, some students may find this a bit intriguing, but frankly speaking - I do not have anything to chase away that vagueness.

Recall the geometrical construction you made for a prism to find R1 + R2.

Here, R2 = Sin-1 (n1/n). If you realize that the normals at the two points and the two faces form a cyclic quadrilateral, it won't take you much time to realize that R1 = 45 - R2

Now relate R1 and the angle of incidence using Snell's law.

Finally we get Sin-1(sinI/n) = 45 - Sin-1 (n1/n).

i.e. (Sini) = n/root2[root(1-(n1/n)^2) - (n1/n)]

Tha angle i obtained from here is the answer. That is, &lt;span style=&quot;color: red;&quot;&gt;&lt;B&gt;sin-1 [n/root2[root(1-(n1/n)^2) - (n1/n)]]&lt;/B&gt;&lt;/span&gt;&lt;/red&gt;
===Angle of incidence for no deviatio


 the hypotenuse, either the two refractive indices need to be same or the ray has to be incident normally on the hypotenuse.

In that case - R2 = 0. Giving R1 = 45. the angle of incidence can then be found using Snell's law.

Sini = (1.352)/(root 2), giving i = sin-1 0.956

==Wrapping up the first four questions==
Considering the calculations involved in the last Question 4, we do not expect everyone to do it in examination conditions without any silly mistake. Then, we can expect that majority of the prepared students would fetch 18-21 marks in this section, however scoring full 25 in the first four questions is not difficult as well. Its just that the proportion of such students would be less.

{{BookCat}}</text>
      <sha1>kujw3f1txg9ldd8di1iy40cczb2q5ok</sha1>
    </revision>
  </page>
  <page>
    <title>Scheme Programming/A taste of Scheme</title>
    <ns>0</ns>
    <id>180265</id>
    <revision>
      <id>4676584</id>
      <parentid>4376529</parentid>
      <timestamp>2026-10-18T02:48:03Z</timestamp>
      <contributor>
        <username>Acrions</username>
        <id>3509296</id>
      </contributor>
      <comment>8 is being applied</comment>
      <origin>4676584</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="7213" sha1="nlbts355lgec85vynokp8k3i2i2439o" xml:space="preserve">{{Navigation|Book=Scheme Programming|previous=Using a Scheme interpreter|current=A taste of Scheme|next=Scheme Datatypes}}

Now that we have an idea of how to run a Scheme interpreter, let's see
what we can do with it in some short examples.  We won't consider these
programs in any depth.  For now, the intention is to give the reader a
feel for Scheme.

A Scheme interpreter evaluates Scheme expressions typed by the user.  With our
interpreter running, we first evaluate a very simple expression.

&lt;syntaxhighlight lang=&quot;scheme&quot;&gt;
&gt; 4
4
&lt;/syntaxhighlight&gt;

When we enter '4' and hit Enter, we are asking our Scheme interpreter
to evaluate the expression '4'.  Unsurprisingly, 4 evaluates to 4.

Next, we try some basic arithmetic.

&lt;syntaxhighlight lang=&quot;scheme&quot;&gt;
&gt; (+ 3 6)
9
&gt; (* 18 5)  ; multiplication
90
&gt; (- 4 7)
-3
&lt;/syntaxhighlight&gt;

These examples illustrate some important things about Scheme syntax.
First, the syntax is ''fully-parenthesized''; the parentheses in the
above expressions are required, and extra parentheses cannot be added
without changing the meaning of the expression.  For example, the
following causes the interpreter to report an error:

&lt;syntaxhighlight lang=&quot;scheme&quot;&gt;
&gt; ((+ 3 6))
;; Error: application of non-procedure 9
&lt;/syntaxhighlight&gt;

Secondly, we see that Scheme uses ''prefix notation''.  In each
expression, the ''operator'' (+, *, -) comes before the ''operands'' (the
numbers).  This is unlike the usual (&quot;infix&quot;) convention of
mathematical notation, in which the operator is written ''between'' the
operands.  For example, the following isn't a valid Scheme expression:

&lt;syntaxhighlight lang=&quot;scheme&quot;&gt;
&gt; (8 * 5 - 3)
;; Error: application of non-procedure 8
&lt;/syntaxhighlight&gt;

It's easy to translate it into Scheme, however:

&lt;syntaxhighlight lang=&quot;scheme&quot;&gt;
&gt; (- (* 8 5) 3)
37
&lt;/syntaxhighlight&gt;

Notice that here we've used the expression &lt;code&gt;(* 8 5)&lt;/code&gt; as an
operand of another expression!  This is valid Scheme, and we will see
such nested expressions everywhere.

Scheme allows us to name values for use in other expressions:

&lt;syntaxhighlight lang=&quot;scheme&quot;&gt;
&gt; (define x 20)
&gt; x
20
&gt; (define y (+ x 4))
&gt; (* y 2)
48
&lt;/syntaxhighlight&gt;

The ''definition'' &lt;code&gt;(define x 20)&lt;/code&gt; causes the interpreter to
define &lt;code&gt;x&lt;/code&gt; to mean the value &lt;code&gt;20&lt;/code&gt;.  When &lt;code&gt;x&lt;/code&gt;
appears in code following the definition, it will be replaced by this
value.  We can then use &lt;code&gt;x&lt;/code&gt; in the definition of &lt;code&gt;y&lt;/code&gt;.

We can also define ''procedures''.  Like the built-in operators
&lt;code&gt;+&lt;/code&gt;, &lt;code&gt;-&lt;/code&gt;, etc., a procedure takes a certain number
of ''parameters'' (also known as ''arguments'') and computes a value.

&lt;syntaxhighlight lang=&quot;scheme&quot;&gt;
&gt; (define (square x)
    (* x x))
&gt; (square 5)
25
&lt;/syntaxhighlight&gt;

Here, we have defined &lt;code&gt;square&lt;/code&gt; to mean a procedure taking one
parameter, &lt;code&gt;x&lt;/code&gt;, and returning the value of &lt;code&gt;(* x x)&lt;/code&gt;.
The form of this definition is a little different from those we saw
earlier; here, the name being defined appears in parentheses, followed
by the names of the procedure's parameters.  To use this newly-defined
procedure, we evaluate &lt;code&gt;(square 5)&lt;/code&gt;.

Here's a more complex procedure which calculates the area of a triangle
with sides &lt;math&gt;a&lt;/math&gt;, &lt;math&gt;b&lt;/math&gt;, and &lt;math&gt;c&lt;/math&gt; using
[[w:Heron's formula|Heron's formula]]:

&lt;syntaxhighlight lang=&quot;scheme&quot;&gt;
&gt; (define (heron a b c)
    (let ((s (/ (+ a b c) 2)))
      (sqrt (* s (- s a) (- s b) (- s c)))))
&gt; (heron 4 13 15)
24
&lt;/syntaxhighlight&gt;

In this procedure, we need to use the value &lt;math&gt;s&lt;/math&gt;, defined by

:&lt;math&gt;s = \frac{a + b + c}{2}&lt;/math&gt;,

four times.  The definition of &lt;code&gt;heron&lt;/code&gt; would be tedious to
write and hard to read if we were to use &lt;code&gt;(/ (+ a b c) 2)&lt;/code&gt;
&lt;ref&gt;In previous examples we gave &lt;code&gt;+&lt;/code&gt; two arguments.  Here,
though, we've given it three.  Is this correct?  In general, Scheme will
report an error if we give a procedure too few or too many arguments.
&lt;code&gt;+&lt;/code&gt;, though, is a ''variadic'' procedure, which means that it
can be passed any number of arguments.  The expression &lt;code&gt;(+ a b c)&lt;/code&gt;
is equivalent to &lt;code&gt;(+ (+ a b) c)&lt;/code&gt;.  &lt;code&gt;-&lt;/code&gt;,
&lt;code&gt;*&lt;/code&gt;, and &lt;code&gt;/&lt;/code&gt; are also variadic.&lt;/ref&gt;
for each occurrence of &lt;math&gt;s&lt;/math&gt;.  We solve this problem using the
&lt;code&gt;let&lt;/code&gt; form, which allows us to temporarily associate the name
&lt;code&gt;s&lt;/code&gt; with this value.&lt;ref&gt;If you're familiar with programming
languages with &quot;local variables&quot;, you can think of names bound by
&lt;code&gt;let&lt;/code&gt; as much the same thing.&lt;/ref&gt;

We can compare values, or test them for certain properties.

&lt;syntaxhighlight lang=&quot;scheme&quot;&gt;
&gt; (= 4 (+ 3 1))
#t
&gt; (&lt; 9 7)
#f
&gt; (positive? 5)
#t
&gt; (even? 5)
#f
&lt;/syntaxhighlight&gt;

What are the &lt;code&gt;#t&lt;/code&gt; and &lt;code&gt;#f&lt;/code&gt; values which Scheme
gives us back here?  As you may have guessed, these are ''boolean''
values representing &quot;true&quot; and &quot;false&quot;, respectively.

''Predicates'' like &lt;code&gt;positive?&lt;/code&gt; are procedures which take
one argument and return a boolean value.  It's a Scheme convention to
give predicates names ending with '?'; hence we have &lt;code&gt;even?&lt;/code&gt;,
&lt;code&gt;negative?&lt;/code&gt;, and many others.

Procedures can be [[w:Recursive definition|recursive]].  Here's a classic
example.

&lt;syntaxhighlight lang=&quot;scheme&quot;&gt;
&gt; (define (factorial n)
    (if (= n 0)
        1
        (* n (factorial (- n 1)))))
&gt; (factorial 5)
120
&lt;/syntaxhighlight&gt;

Evaluating &lt;code&gt;(factorial 5)&lt;/code&gt; gives us the value of &lt;math&gt;5!&lt;/math&gt;,
that is, &lt;math&gt;5 \times 4 \times 3 \times 2 \times 1&lt;/math&gt;, which we can
express recursively as &lt;math&gt;5 \times 4!&lt;/math&gt;.  More generally, we
say that factorial of &lt;math&gt;n&lt;/math&gt; is 1 if &lt;math&gt;n&lt;/math&gt; is zero, and
&lt;math&gt;n&lt;/math&gt; times the factorial of &lt;math&gt;n - 1&lt;/math&gt; otherwise.  This
is precisely what the definition of &lt;code&gt;factorial&lt;/code&gt; states in the
language of Scheme:

&lt;syntaxhighlight lang=&quot;scheme&quot;&gt;
(define (factorial n)
  (if (= n 0)                      ; is the argument 0?
      1                            ; then the answer is 1
      (* n (factorial (- n 1)))))  ; otherwise, it's n * (n - 1)!
&lt;/syntaxhighlight&gt;

Recursion is a critical notion in Scheme (and in computer science in
general) that we will discuss in greater depth in later sections.

Another new thing in the definition of &lt;code&gt;factorial&lt;/code&gt; is the use of
the &lt;code&gt;if&lt;/code&gt; form, which evaluates its first argument, then either its
second or third argument depending on whether the first was true or false.
If the first argument evaluates to true, then we get the second argument of
the &lt;code&gt;if&lt;/code&gt; form; otherwise, we get the third.
&lt;ref&gt;For now, we'll assume that saying something is &quot;true or false&quot; means it's
a boolean--that is, either &lt;code&gt;#t&lt;/code&gt; or &lt;code&gt;#f&lt;/code&gt;.  In
practice, every Scheme object has a boolean value; namely, &lt;code&gt;#f&lt;/code&gt; is
false and everything else is true.&lt;/ref&gt;

&lt;syntaxhighlight lang=&quot;scheme&quot;&gt;
&gt; (if #t 1 0)
1
&gt; (if (&gt; 2 3) 1 0)
0
&lt;/syntaxhighlight&gt;

{{Exercises|solutions=1|1=
# Why does evaluating &lt;code&gt;((+ 3 6))&lt;/code&gt; cause Scheme to report the &quot;application of a non-procedure&quot;?
}}

{{BookCat}}</text>
      <sha1>nlbts355lgec85vynokp8k3i2i2439o</sha1>
    </revision>
  </page>
  <page>
    <title>Aros/Platforms/AROS USB support</title>
    <ns>0</ns>
    <id>202147</id>
    <revision>
      <id>4676539</id>
      <parentid>4676243</parentid>
      <timestamp>2026-10-17T15:07:12Z</timestamp>
      <contributor>
        <username>R. Henrik Nilsson</username>
        <id>3395618</id>
      </contributor>
      <minor />
      <comment>Curent &gt; Current</comment>
      <origin>4676539</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="655218" sha1="jlbs6ltd4ti6p98lelils878f3e7t1d" xml:space="preserve">
{{ArosNav}}


==Host Adapter Protocol USB1 OHCI UHCI USB2 EHCI USB3.0 USB3.1 xHCI ==

Please let us know any mistakes or any information to be added, use Prefs/Trident to confirm Vendor and Product IDs 
Please chat at [https://www.arosworld.org/index.php AROS World]

*1996 USB1.0
*1998 USB1.1
*2000 USB2.0
*2008 USB3.0
*2013 USB3.1
*2017 USB3.2


AROS has these USB transfers 

*Control     - 
*Bulk        - Midi 1.0 ( 'send my data when you can' )
*Interrupt   - Midi 2.0
*Isochronous - USBAudio, Webcams, etc 

Isochronous is the starting point of modern types of multimedia creativity. IsoChronous isoc code is already in place in poseidon.library and '''scheduled''' transfers are queued to be later rerouted in the host driver code (needs to be written for each host protocol e.g. OCHI, UCHI, EHCI and [https://cdrdv2-public.intel.com/625472/625472_xHCI_Rev1_2b.pdf#:~:text=Page%203.%20Document%20Number:%20625472%2C%20Revision:%201.2b.%203. XHCI rev1.2], [https://www.intel.com/content/www/us/en/content-details/868296/extensible-host-controller-interface-for-universal-serial-bus-xhci-requirements-specification-r2-0.html rev2], etc). There seems to be 2 types of isoc transfers, one is just the normal isoc transfer and the other is realtime implementation of isoc transfer. 

For isoc transfer there needs to be a scheduler that makes sure no isoc transfers are dropped (in or out) and that they happen at the right time. It all gets difficult as the device making use of the isoc transfer may be at any point on the device tree. One needs to calculate the USB bandwidth for the packet based periodic transfers that are initiated by the host which have fixed but guaranteed bandwidth. Host controllers guarantee this bandwidth by planning a schedule of transfers ahead of time to ensure there is enough time reserved on the bus.

[https://www.intel.co.uk/content/www/uk/en/products/docs/io/universal-serial-bus/ehci-specification.html EHCI] [https://www.thegoodpenguin.co.uk/blog/understanding-why-usb-isochronous-bandwidth-errors-occur/ bus-bandwidth] vs payload-bandwidth and the algorithm of the EHCI scheduler. 
The bandwidth of the endpoint in terms of payload data (stuff we put in a packet) and the protocol overhead, signalling imposed bit stuffing, host delays etc. 

Poseidon controls the driver and device tree and it provides an API to communicate with the USB devices. Poseidon really doesn't care much about what sort of transfer pipe is opened or used, it only provides the means to do so and forwards the iorequests to the correct driver. Poseidon code is the higher level code for USB communication and drivers are of course the lower level one.


[[File:Psd.svg|220px|right]]


; Best Hardware - NEC Chipset (OHCI + EHCI), Intel Chipset (UHCI + EHCI), XHCI USB3.0, USB3.1 &amp; gen 2 Type-A Type-B Type-C 
; Next Best Set - General OHCI, SIS (OHCI + EHCI), 
; Buggy Chipset - [ Early AMD OHCI], ALi OHCI, VIA UHCI, Nvidia OHCI &amp; EHCI, 


=== USB1.1 ===
OHCI USB 1.1 - USB-IF sanctioned standard but hardware physical form removed with USB2.0 and replaced with virtual emulation of USB1 
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;5%&quot; |Product ID
! width=&quot;5%&quot; |Revision 
! width=&quot;10%&quot; |Boot from USB
! width=&quot;10%&quot; |Detect USB device 
! width=&quot;10%&quot; |USB device works 
! width=&quot;30%&quot; |Opinion
|-
| ALi Agere M5273 A1 M5237 Lucent USS-312 
| 
| 
| 
| &lt;!--Boots--&gt;{{Maybe}}
| &lt;!--Detects--&gt;{{Yes}}
| &lt;!--Works--&gt;{{Maybe|}}
| StarTech PCI425USB, CompUSA Iogear GIC220U-b, Nvidia 220 mobo, USBA2041P, ALi SU2A-PS, 
|-
| AMD 756 Chipset (onboard motherboard) 
| 0x1022 
| 0x740c 
| 0x06
| &lt;!--Boots--&gt;{{No}}
| &lt;!--Detects--&gt;{{No}}
| &lt;!--Works--&gt;{{Maybe|}}
| no [http://aros-exec.org/modules/newbb/viewtopic.php?post_id=31308#forumpost31308 usb devices detected] Geode GX1, 
|-
| CMD DU-A2 Silicon Image 0670 (pci AMD chipset)
| 0x1095
| 0x0670
| 0x06
| &lt;!--Boots--&gt;{{No}}
| &lt;!--Detects--&gt;{{No}}
| &lt;!--Works--&gt;{{Maybe|}}
| 
|-
| Silicon Image 0673 (pci AMD chipset)
| 0x1095
| 0x0673
| 0x06
| &lt;!--Boots--&gt;{{No}}
| &lt;!--Detects--&gt;{{No}}
| &lt;!--Works--&gt;{{Maybe|}}
| 
|-
| Nvidia Nforce2 USB
| 0x10de 
| 
| 
| &lt;!--Boots--&gt;{{Maybe|Bios options vary but does with Plop Boot}}
| &lt;!--Detects--&gt;{{Yes}}
| &lt;!--Works--&gt;{{Maybe|}}
| Tested with 20th Aug 2012 improvement 
|-
| NEC µPD720100AGM 
| 0x1033
| 0x0035
| 0x 
| &lt;!--Boots--&gt;{{Unk}}
| &lt;!--Detects--&gt;{{Unk}}
| &lt;!--Works--&gt;{{Maybe|}}
| untested - Amiga Spider card with possible bottleneck issues at higher speeds 
|-
| NEC µPD720101AGM 720101GJ
| 0x1033
| 0x0035
| 0x43
| &lt;!--Boots--&gt;{{Yes}}
| &lt;!--Detects--&gt;{{Yes}}
| &lt;!--Works--&gt;{{Maybe|}}
| Mac mini, Belkin F5U219vea (2+1 ports), Belkin F5U220vea1 (4+1 ports), Adaptec 3100LP, BAFO BF-460, GWC UC-160, IOGear GIC250U, Keyspan U2PCI-5, O'toLink U2-C2B U2-C2A U2-P20N U2-P50, Ratoc PCIU5, USBWholesale UII-PCIP 
|-
| NEC µPD720102
| 0x1033
| 0x00
| 0x 
| &lt;!--Boots--&gt;{{Unk|untested }}
| &lt;!--Detects--&gt;{{Unk|untested }}
| &lt;!--Works--&gt;{{Maybe|}}
| 
|-
| Opti 82C861 2-port 
| 0x1045
| 0xc861
| 
| &lt;!--Boots--&gt;{{No}}
| &lt;!--Detects--&gt;{{No}}
| &lt;!--Works--&gt;{{Maybe|}}
| no USB devices detected - Belkin F5U005, 
|-
| SIS 7001 OCHI 
| 0x1039
| 0x7001
| 0x0f
| &lt;!--Boots--&gt;{{No}}
| &lt;!--Detects--&gt;{{Yes}}
| &lt;!--Works--&gt;{{Maybe|}}
| 20th Aug 2012 - not booting stalls on GRUB word with Plop Boot 
|-
|}


UHCI USB 1.1 - Intel standard but since 2009 no hardware support as USB2 introduced virtual emulation of USB1 
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;5%&quot; |Product ID
! width=&quot;5%&quot; |Revision 
! width=&quot;10%&quot; |Boot from USB
! width=&quot;10%&quot; |Detect USB device
! width=&quot;10%&quot; |USB device works 
! width=&quot;30%&quot; |Opinion
|-
| Intel 
| 0x8086 
| 0x
| 0x01 
| &lt;!--Boots--&gt;{{No|not in bios use AROS floppy disc boot}}
| &lt;!--Detects--&gt;{{Maybe|}}
| &lt;!--Works--&gt;{{Maybe|}}
| 
|-
| Intel 82371AB EB MB PIIX4 
| 0x8086 
| 0x7112
| 0x01 
| &lt;!--Boots--&gt;{{No|none in bios use other booting options}}
| &lt;!--Detects--&gt;{{Maybe|Detects most devices}}
| &lt;!--Works--&gt;{{Maybe|most devices but not RTL8187b WG111v3 blue led not on and does not work}}
|  
|-
| Intel 82801DB/DBL/DBM (onboard i830 mbd)
| 0x8086 
| 0x24c4 
| 0x01 
| &lt;!--Boots--&gt;{{Yes|but not from bios but floppy options}}
| &lt;!--Detects--&gt;{{Yes|}}
| &lt;!--Works--&gt;{{Yes|}}
| RTL8187b WG111v3 blue led on and although device has software failure and recoverable error IT STILL WORKS. Fresh start sometimes needs Network Prefs Saved to work. 
|-
| VIA MVP4 (onboard mbd)
| 0x1106
| 0x30
| 0x40 
| &lt;!--Boots--&gt;{{No}}
| &lt;!--Detects--&gt;{{Maybe|most devices}}
| &lt;!--Works--&gt;{{Maybe|most devices but not wireless options}}
| RTL8187b WG111v3 detected but blue led not on and does not work 
|-
| VIA VT82xx (onboard mbd)
| 0x1106
| 0x3038
| 0x40 
| &lt;!--Boots--&gt;{{No}}
| &lt;!--Detects--&gt;{{Maybe|most devices}}
| &lt;!--Works--&gt;{{Maybe|most devices but not wireless usb}}
| RTL8187b WG111v3 blue led on but does not work 
|-
| VIA VT6202 (VIA VT83C572)
| 0x1106
| 0x3038
| 
| &lt;!--Boots--&gt;{{No}}
| &lt;!--Detects--&gt;{{Maybe|}} 
| &lt;!--Works--&gt;{{Maybe|}}
| A-Best USB-200, Cables N Mor USBPCI, CompUSA, D-Link DSB500, Digital/Research DRUSBCARD, Kouwell IOFlex 580, StarMount USB VIA, 
|-
| VIA VT6112 
| 
| 
| 
| &lt;!--Boots--&gt;{{No}}
| &lt;!--Detects--&gt;{{Maybe|}}
| &lt;!--Works--&gt;{{Maybe|}}
| 
|-
| VIA VT6212 (pci card)
| 0x1106
| 0x3038
| 0x61
| &lt;!--Boots--&gt;{{No}}
| &lt;!--Detects--&gt;{{Maybe|}}
| &lt;!--Works--&gt;{{Maybe|}}
| 2011 seems to have issues with other identical via based USB controller(s) present 
|-
| VIA VT6214L 
| 
| 
| 
| &lt;!--Boots--&gt;{{No}}
| &lt;!--Detects--&gt;{{Maybe|}}
| &lt;!--Works--&gt;{{Maybe|}}
| 
|-
|}


=== USB 2.0 EHCI ===
The USB-IF insisted on only one implementation of EHCI but it creates 4 virtual hcd to cover USB1.1 support. The virtual HCD on Intel and VIA EHCI controllers are UHCI. All other vendors use virtual OHCI controllers. Hardware EHCI USB2.0 ended in most chipsets in 2014/5 and is now virtual through most newer USB3.0 chipsets 

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;5%&quot; |Product ID
! width=&quot;5%&quot; |Revision 
! width=&quot;10%&quot; |Boot from USB
! width=&quot;10%&quot; |Detect USB device
! width=&quot;10%&quot; |USB device works 
! width=&quot;30%&quot; |Opinion
|-
| ALi Agere M5273 A1 Lucent USS-344 
| 
| 
| 
| &lt;!--Boots--&gt;
| &lt;!--Detects--&gt;
| &lt;!--Works--&gt;{{Maybe|}}
| {{N/A|untested}} belkin F5U006, 
|-
| Nvidia Nforce2 USB
| 
| 
| 
| &lt;!--Boots--&gt;{{No}}
| &lt;!--Detects--&gt;{{Yes}}
| &lt;!--Works--&gt;{{Maybe|}}
| 
|-
| Intel 82801DB/DBM (onboard mbd)
| 0x8086 
| 0x24cd 
| 0x01 
| &lt;!--Boots--&gt;{{Yes}}
| &lt;!--Detects--&gt;{{Yes}}
| &lt;!--Works--&gt;{{Maybe|}}
| 
|-
| NEC µPD720100AGM 
| 0x1033
| 0x00E0
| 0x 
| &lt;!--Boots--&gt;
| &lt;!--Detects--&gt;
| &lt;!--Works--&gt;{{Maybe|}}
| {{N/A|untested - Amiga Spider card}}
|-
| NEC 72101 GJ
| 0x1033 
| 0x00e0 
| 0x04
| &lt;!--Boots--&gt;{{Yes}}
| &lt;!--Detects--&gt;{{Yes}}
| &lt;!--Works--&gt;{{Maybe|}}
| Belkin F5U219 VEA1 (pci), 
|-
| SIS ECHI 
| 0x1039
| 0x7002
| 0x00
| &lt;!--Boots--&gt;{{No}}
| &lt;!--Detects--&gt;{{Maybe|issues about which port is used if it works at all}}
| &lt;!--Works--&gt;{{Maybe|}}
| 
|-
| VIA VT6202 
| 0x1106
| 0x3104
| 
| &lt;!--Boots--&gt;{{No}}
| &lt;!--Detects--&gt;{{Yes}}
| &lt;!--Works--&gt;{{Maybe|}}
| 
|-
| VIA VT6212 (pci card)
| 0x1106
| 0x3104
| 0x62
| &lt;!--Boots--&gt;{{No}}
| &lt;!--Detects--&gt;{{Yes|detects}}
| &lt;!--Works--&gt;{{Maybe|}}
| 
|-
|}


=== USB 3.x SuperSpeed SS (Speed 5Gbit/s 3.1 gen 1) aka xHCI eXtensible ===

USB Attached SCSI (UAS or UASP) is a protocol used for high-speed data transfer between computers and external storage devices like SSDs, HDDs, and some flash drives. It provides up to 70% faster read/write speeds than traditional Bulk-Only Transport (BOT) by allowing multiple commands to run in parallel, rather than waiting in a queue

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;5%&quot; |Product ID
! width=&quot;5%&quot; |Revision 
! width=&quot;10%&quot; |Boot from USB
! width=&quot;10%&quot; |Detect USB device
! width=&quot;10%&quot; |USB device works 
! width=&quot;30%&quot; |Opinion
|-
| &lt;!--Description--&gt;AMD 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{unk| }}
| &lt;!--Detects--&gt;{{unk|}}
| &lt;!--Works--&gt;{{unk|}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;AMD 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{unk| }}
| &lt;!--Detects--&gt;{{unk|}}
| &lt;!--Works--&gt;{{unk|}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;AMD 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{unk| }}
| &lt;!--Detects--&gt;{{unk|}}
| &lt;!--Works--&gt;{{unk|}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Fresco Logic FL1000 FL 1000 
| &lt;!--Vendor ID--&gt;0x1B73
| &lt;!--Product ID--&gt;0x1000 
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{unk| }}
| &lt;!--Detects--&gt;{{unk|}}
| &lt;!--Works--&gt;{{unk|}}
| &lt;!--Opinion--&gt;link power management (LPM, USB 3.0 power saving) cannot be disabled so random connection issues  
|-
| &lt;!--Description--&gt;Fresco Logic FL1009-200 FL 1009 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;0x1009 
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{unk| }}
| &lt;!--Detects--&gt;{{unk|}}
| &lt;!--Works--&gt;{{unk|}}
| &lt;!--Opinion--&gt;Orico PFU3-2P
|-
| &lt;!--Description--&gt;Fresco Logic FL1100-100 FL 1100SX 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;0x1100 
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{unk| }}
| &lt;!--Detects--&gt;{{unk|}}
| &lt;!--Works--&gt;{{unk|}}
| &lt;!--Opinion--&gt;LPM cannot be disabled so issues with disconnecting WD drives etc - CalDigit, ORICO PFU3-2P, FASTA-6GU3 Pro, inatech KTU3FR-2P 2 port USB 3.0,  and Inateck KT4004 (KTU3FR-4PA rev B2) for storage and hubs, etc 
|-
| &lt;!--Description--&gt;Fresco Logic FL1400 FL 1400 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;0x1400 
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{unk| }}
| &lt;!--Detects--&gt;{{unk|}}
| &lt;!--Works--&gt;{{unk|}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Fresco Logic 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;0x
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{unk| }}
| &lt;!--Detects--&gt;{{unk|}}
| &lt;!--Works--&gt;{{unk|}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;NEC Renesas xHCI µPD720200 uPD720200a chip
| &lt;!--Vendor ID--&gt;0x1d6b
| &lt;!--Product ID--&gt;0x0194
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{unk| }}
| &lt;!--Detects--&gt;{{unk|}}
| &lt;!--Works--&gt;{{Maybe|no USB3 but seems to works like USB2}}
| &lt;!--Opinion--&gt;recognized but not supported for USB3 but works like USB2 - ORICO PRU3-4P 4 Port USB, early Dell Wyse zx0 thin client,  
|-
| &lt;!--Description--&gt;NEC Renesas xHCI µPD720201 uPD720201 chip
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;0x114 0x0115 
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{unk| }}
| &lt;!--Detects--&gt;{{unk|}}
| &lt;!--Works--&gt;{{unk|}}
| &lt;!--Opinion--&gt;recognized but not supported 
|-
| &lt;!--Description--&gt;NEC Renesas xHCI µPD720202 uPD720202 chip
| &lt;!--Vendor ID--&gt;0x1912 
| &lt;!--Product ID--&gt;0x0015
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{unk| }}
| &lt;!--Detects--&gt;{{unk|}}
| &lt;!--Works--&gt;{{unk|}}
| &lt;!--Opinion--&gt;recognized but not supported 
|-
| &lt;!--Description--&gt;[http://www.ti.com/product/tusb7340 TI] tusb7340 TUSB732 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;0x8241
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{unk| }}
| &lt;!--Detects--&gt;{{unk|}}
| &lt;!--Works--&gt;{{unk|}}
| &lt;!--Opinion--&gt;recognized but not supported Koutech IO-PEU436 but only one with open docs 
|-
| &lt;!--Description--&gt;Intel xHCI 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{unk| }}
| &lt;!--Detects--&gt;{{unk|}}
| &lt;!--Works--&gt;{{unk|}}
| &lt;!--Opinion--&gt;recognized but not supported - integrated since Ivybridge 
|-
| &lt;!--Description--&gt;Intel xHCI 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{unk| }}
| &lt;!--Detects--&gt;{{unk|}}
| &lt;!--Works--&gt;{{unk|}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Marvell 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{unk| }}
| &lt;!--Detects--&gt;{{unk|}}
| &lt;!--Works--&gt;{{unk|}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Via Labs VL800 xHCI 0.96 support in VL800, VIA VL811 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;0x3432 0x3438 0x3515 and 0x9201
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{unk| }}
| &lt;!--Detects--&gt;{{unk|}}
| &lt;!--Works--&gt;{{Maybe|}} 2.0 backwards support 
| &lt;!--Opinion--&gt;Anker 68UPPCIE-2S20PU 2 port, Plugable 4-Port, GA-z77x-ud5h rev. 1.1 mobo, 
|-
| &lt;!--Description--&gt;Via Labs VL811+ 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{unk| }}
| &lt;!--Detects--&gt;{{unk|}}
| &lt;!--Works--&gt;{{unk|}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Via Labs VL812 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{unk| }}
| &lt;!--Detects--&gt;{{unk|}}
| &lt;!--Works--&gt;{{unk|}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;xHCI 1.0 support in VL805 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{unk| }}
| &lt;!--Detects--&gt;{{unk|}}
| &lt;!--Works--&gt;{{unk|}}
| &lt;!--Opinion--&gt;
|-
|}


USB 3.1 (power up to 100W and data 10Gbit/s USB 3.2 gen 2 - USB-A Full size plug - USB-B micro USB size - USB-C reversible) 
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;5%&quot; |Product ID
! width=&quot;5%&quot; |Revision 
! width=&quot;10%&quot; |Boot from USB
! width=&quot;10%&quot; |Detect USB device
! width=&quot;10%&quot; |USB device works 
! width=&quot;30%&quot; |Opinion
|-
| &lt;!--Description--&gt;Asmedia ASM1142 
| &lt;!--Vendor ID--&gt;0x1B21 
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{N/A}}
| &lt;!--Detects--&gt;{{N/A|}}
| &lt;!--Works--&gt;{{No| }}
| &lt;!--Opinion--&gt;Connector: USB Type C and  USB Type A x 1 - Ugreen USB C PCI Card 2 Port USB 3.1 Type C 
|-
| &lt;!--Description--&gt;Marvell 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{N/A}}
| &lt;!--Detects--&gt;{{N/A|}}
| &lt;!--Works--&gt;{{No| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;AMD 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{N/A}}
| &lt;!--Detects--&gt;{{N/A|}}
| &lt;!--Works--&gt;{{No| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Intel 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{N/A}}
| &lt;!--Detects--&gt;{{N/A|}}
| &lt;!--Works--&gt;{{No| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Intel xHCI 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{unk| }}
| &lt;!--Detects--&gt;{{unk|}}
| &lt;!--Works--&gt;{{unk|}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;[ Intel] Revision 1.8 1.9 Updated  
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{unk| }}
| &lt;!--Detects--&gt;{{unk|}}
| &lt;!--Works--&gt;{{unk|}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;VLI 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{N/A}}
| &lt;!--Detects--&gt;{{N/A|}}
| &lt;!--Works--&gt;{{N/A|}}
| &lt;!--Opinion--&gt;AUKEY 4 Ports USB C , 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{N/A}}
| &lt;!--Detects--&gt;{{N/A|}}
| &lt;!--Works--&gt;{{N/A|}}
| &lt;!--Opinion--&gt;Startech - PEXUSB312C - 2-port Usb 3.1 10Gbit/s
|-
|}

USB 3.2 (power up to 100W and data 20Gbit/s gen 2x2 - USB-A Full size plug - USB-B micro USB size - USB-C reversible) 
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;5%&quot; |Product ID
! width=&quot;5%&quot; |Revision 
! width=&quot;10%&quot; |Boot from USB
! width=&quot;10%&quot; |Detect USB device
! width=&quot;10%&quot; |USB device works 
! width=&quot;30%&quot; |Opinion
|-
| &lt;!--Description--&gt;Marvell 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{N/A}}
| &lt;!--Detects--&gt;{{N/A|}}
| &lt;!--Works--&gt;{{No| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;AMD 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{N/A}}
| &lt;!--Detects--&gt;{{N/A|}}
| &lt;!--Works--&gt;{{No| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Intel 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{N/A}}
| &lt;!--Detects--&gt;{{N/A|}}
| &lt;!--Works--&gt;{{No| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Intel xHCI 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{unk| }}
| &lt;!--Detects--&gt;{{unk|}}
| &lt;!--Works--&gt;{{unk|}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;[ Intel] Revision 2.6 Update  
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{unk| }}
| &lt;!--Detects--&gt;{{unk|}}
| &lt;!--Works--&gt;{{unk|}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;VLI 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{N/A}}
| &lt;!--Detects--&gt;{{N/A|}}
| &lt;!--Works--&gt;{{N/A|}}
| &lt;!--Opinion--&gt;
|-
|}

=== USB 4 (40Gbps thunderbolt, pcie 3.0 tunnelling, ) ===
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;5%&quot; |Product ID
! width=&quot;5%&quot; |Revision 
! width=&quot;10%&quot; |Boot from USB
! width=&quot;10%&quot; |Detect USB device
! width=&quot;10%&quot; |USB device works 
! width=&quot;30%&quot; |Opinion
|-
| &lt;!--Description--&gt;Marvell 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{N/A}}
| &lt;!--Detects--&gt;{{N/A|}}
| &lt;!--Works--&gt;{{No| }}
| 
|-
| &lt;!--Description--&gt;AMD Ryzen7 6800U 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{N/A}}
| &lt;!--Detects--&gt;{{N/A|}}
| &lt;!--Works--&gt;{{No| }}
| 
|-
| &lt;!--Description--&gt;Intel Goshen Ridge JHL8440 Controller 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{N/A}}
| &lt;!--Detects--&gt;{{N/A|}}
| &lt;!--Works--&gt;{{No| }}
| 
|-
| &lt;!--Description--&gt;VLI 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Boots--&gt;{{N/A}}
| &lt;!--Detects--&gt;{{N/A|}}
| &lt;!--Works--&gt;{{N/A|}}
|  
|-
|}


== hid.class (Human Interface Device) ==

=== Keyboard ===

 Some multi-finger touchpad support works but not on all touchpads  

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;8BitDo Retro N C64 edition Keyboard, the super button accessory and optional N30 mouse
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 87 keys Kailh white}}
|-
| &lt;!--Description--&gt;8bitdo 108 Retro Mechanical Keyboard (white kailh) and two superbuttons (green) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Apple Pro Keyboard
| 0x05ac
| 0x0205 
| 0x0122
| {{yes|works (its two hub ports) but mouse scroll wheel issues}}
|-
| Apple Pro Keyboard
| 0x05AC
| 0x020B 
| 
| {{yes|works (two onboard ports also)}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Aigo K68 60% red switches, A68 A87 wireless 2G 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;[http://amigakit.leamancomputing.com/catalog/product_info.php?cPath=49&amp;products_id=973 AmigaOne Keyboard]
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{yes|works}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Akko TAC87 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| 80% TKL }}
|-
| &lt;!--Description--&gt;Akko MonsGeek FUN60 PRO&amp;MAX HE
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| 60% hall effect }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Akko 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2025 hall effect, good but expensive and software poor}}
|-
| &lt;!--Description--&gt;Akko 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2026 magnetic hall effect software should be better and surpasses mechanical}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Arteck HW197 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2026 keyboard and touchpad combo, aluminum frame, aa battery }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Azio Cascade 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2022  }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Chilkey ND75 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2024  good 75% expensive}}
|-
| &lt;!--Description--&gt;Chilkey ND104 (Wuque Studios) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 premium clicky (WS Blue) or silent (WS White) key options with Ansi and ISO formats also numpad and calculator, aluminum machined, tri mode, }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2026 untested magnetic hall effect software should be better and surpasses mechanical}}
|-
| &lt;!--Description--&gt;Corsair K65 Mech MX no numeric keypad 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Corsair CH-9000045 K70 Blue MX 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Corsair K90 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Corsair K95 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Corsair K
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Cherry G80 G80-3000L[x]C[yy]-[z] 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Cooler Master CM Storm Quickfire Rapid 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Corsair K100 Air 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;2025 okay low profile but expensive 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2027 magnetic hall effect software should be better and surpasses mechanical}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Opinion
|-
| &lt;!--Description--&gt;Dell SK-8135 Dell USB Keyboard for Internet and Multimedia rev H for Dimension 4500, Dimension 8250, OptiPlex GX260n, OptiPlex GX60n, Precision 350 (R42232) 
| &lt;!--Vendor ID--&gt;0x413C
| &lt;!--Product ID--&gt;0x2010 
| &lt;!--Revision--&gt;0200 
| &lt;!--Opinion--&gt;{{Yes| usb1.1 keyboard hub 0x413C 0x1003 works as well - multimedia keys not mapped }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Deepcool KG722
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 65% }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Ducky Channel Zero DK2108 Mech Mechanical Cherry MX Red 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Ducky Shine 3 Brown or Blue (DK9087) MX keys 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Das Keyboard Model S Ultimate 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Epomaker Cidoo V75 Pro 
| &lt;!--Vendor ID--&gt;0x3151
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2023 untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;epomaker rt100 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2024 plastic build and no screws, numpad with small 0, mostly quiet seasalt switches, gimmick usb-c 1in screen}}
|-
| &lt;!--Description--&gt;EPOMAKER TH99  
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }} USB-C full numpad keyboard 
|-
| &lt;!--Description--&gt;eopmaker P75 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| expensive but good}}
|-
| &lt;!--Description--&gt;eopmaker p87 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| expensive but good}}
|-
| &lt;!--Description--&gt;epomaker x Leobog Hi75
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2024  }}
|-
| &lt;!--Description--&gt;epomaker x Feker Galaxy80
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2024  }}
|-
| &lt;!--Description--&gt;epomaker x Galaxy100 gmk/via 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2024 good 96% }}
|-
| &lt;!--Description--&gt;epomaker Aula F75 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2024 budget version good 75% choice of 4 leobog switches}}
|-
| &lt;!--Description--&gt;eopmaker Tide75 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2024 good 75% and not too expensive}}
|-
| &lt;!--Description--&gt;Epomaker Ajazz AK992 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2023 109 key }}
|-
| &lt;!--Description--&gt;Epomaker Ajazz AK820 Pro 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2024 }}
|-
| &lt;!--Description--&gt;Epomaker Ajazz AK35I V3 MAX 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 104 keys - two models: wired and tri-mode connection - }}
|-
| &lt;!--Description--&gt;epomaker Aula F108 PRO 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 pricy but okay 100% but only leobog graywood switches but hotswap available afterwards}}
|-
| &lt;!--Description--&gt;eopmaker Ajazz AK980 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 97 keys }}
|-
| &lt;!--Description--&gt;Epomaker G87 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 }}
|-
| &lt;!--Description--&gt;Epomaker RT82 RT85
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 }}
|-
| &lt;!--Description--&gt;Epomaker RT100 Pro 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 96% }}
|-
| &lt;!--Description--&gt;epomaker x Galaxy100 lite 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 good 96% }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;ATTACK SHARK X98 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 98% maybe silent linear feel with Two-color PBT keycap}}
|-
| &lt;!--Description--&gt;Epomaker ATTACK SHARK X68HE and X65HE 65% Wired Gaming Keyboard
| &lt;!--Vendor ID--&gt;0x3151
| &lt;!--Product ID--&gt;0x502D
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{yes|2025 tested on Aros running on Raspberry Pi wired usb-c with magnetic hall effect keys}}
|-
| &lt;!--Description--&gt;Epomaker 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2027 magnetic hall effect software should be better and surpasses mechanical}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Filco Ninja Majestouch-2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Focus FK-760 Wireless Keyboard &amp; Trackball
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| {{yes|works}} but quality build issues raised 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2027 magnetic hall effect software should be better and surpasses mechanical}}
|-
| &lt;!--Description--&gt;GMMK Tenkeyless 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested  default Gateron Brown switches for Kailh Box Jades default Gateron Brown switches for Kailh Box Jades}}
|-
| &lt;!--Description--&gt;GK61 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2023 untested }}
|-
| &lt;!--Description--&gt;GMK67 GMK87 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested budget good option}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2027 magnetic hall effect software should be better and surpasses mechanical}}
|-
| &lt;!--Description--&gt;Hengchangtong HCT Limeme gk103s Entry Keyboard
| &lt;!--Vendor ID--&gt;0xC0F4
| &lt;!--Product ID--&gt;0x0009
| &lt;!--Revision--&gt;0100
| &lt;!--Opinion--&gt;{{yes|half Keyboard left side only}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2027 magnetic hall effect software should be better and surpasses mechanical}}
|-
| &lt;!--Description--&gt;Hexgears M2
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2024 untested hotswap kaihl green switches}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Hexgears 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Iqunix mq80
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;2025 good 75% low profile keys
|-
| &lt;!--Description--&gt;Iqunix Magi65 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested good 65% low profile keys }}
|-
| &lt;!--Description--&gt;iqunix ez60 ez80 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2025 untested specific hall effect switches - actuation point, rapid trigger, etc }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2027 magnetic hall effect software should be better and surpasses mechanical}}
|-
| &lt;!--Description--&gt;Jomaa YiChip Wireless 50% key with touchpad 
| &lt;!--Vendor ID--&gt;0x3151 
| &lt;!--Product ID--&gt;0x3000
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|dongle detected, keys and pad not working - 2 AAA NM}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2027 magnetic hall effect software should be better and surpasses mechanical}}
|-
| &lt;!--Description--&gt;Keychron q0
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2022 untested numpad only}} 
|-
| &lt;!--Description--&gt;Keychron q1 v1 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2022 untested okay}} 
|-
| &lt;!--Description--&gt;Keychron Q6 Max 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2023 untested 75% with numeric numpad, barebones so choose switches and keycaps to suit }}
|-
| &lt;!--Description--&gt;Keychron q1 MAX V1 MAX 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2023 untested }} 
|-
| &lt;!--Description--&gt;Keychron Lemokey P1 QMK 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested best option to customise switches and keycaps}}
|-
| &lt;!--Description--&gt;Keychron LemoKey X1 X3
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2024 untested keycap swap only not switches}}
|-
| &lt;!--Description--&gt;Keychron K2HE
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested okay}} wireless hall effect analogue on all keys 
|-
| &lt;!--Description--&gt;Keychron K4HE 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2025 untested hall effect but software }}
|-
| &lt;!--Description--&gt;Keychron K5 K17 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 untested okay low profile but }}
|-
| &lt;!--Description--&gt;Keychron Q5 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 }}
|-
| &lt;!--Description--&gt;Keychron K10 HE 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2027 magnetic hall effect software should be better and surpasses mechanical}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2024 }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2024 }}
|-
| &lt;!--Description--&gt;Kiiboom Breeze 75 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2025 good 75% }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2025 }}
|-
| &lt;!--Description--&gt;Meletrix Boog 75 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2024 magnetic hall effect, good but expensive and software poor}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2025 }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2025 }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2027 magnetic hall effect software should be better and surpasses mechanical}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2025 }}
|-
| &lt;!--Description--&gt;Melgeek O2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2025 low profile 75% but not repairable}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2027 magnetic hall effect software should be better and surpasses mechanical}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2025 }}
|-
| &lt;!--Description--&gt;MOSART 2.4G Wireless 60% Keyboard Trackball 
| &lt;!--Vendor ID--&gt;0x062a
| &lt;!--Product ID--&gt;0x4105
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{Yes|dongle recognised HID, keys worked, roller worked, scroll wheel works and shoulders works but buttons around left, top and right hand side (RHS) do not work and plastic and 2 AA MN1500}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Mucai SiGma Micro MKA610 
| &lt;!--Vendor ID--&gt;0x1c4f
| &lt;!--Product ID--&gt;0x0084
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| unknown red keys - rgb backlighting - }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Opinion
|-
| &lt;!--Description--&gt;[http://hjldemo.clsc.cn/ Guangzhou Zhentian Electronics Ltd] Perixx Periboard 505 Plus with Trackball 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{Yes|okay dome keyboard - poor trackball}}
|-
| &lt;!--Description--&gt;Guangzhou Zhentian Electronics Co., Ltd Perixx Periboard 706 Plus with Trackball Wireless 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{Yes|generally okay dome with good sized keys but piano black surround fingerprint magnet, occasional brief trackball freezes after no use, takes some time to get used to the trackball size}} 
|-
| &lt;!--Description--&gt;Perixx Periboard-716 Wireless (Chicony)
| &lt;!--Vendor ID--&gt;04f2:1013
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{Yes|okay dome keyboard and trackpad}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}}
|-
| &lt;!--Description--&gt;Perixx Periboard-
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{Unk|okay keyboard}}
|-
| &lt;!--Description--&gt;Perixx Periboard-
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{Unk|okay keyboard}}
|-
| &lt;!--Description--&gt;Lenovo SK-8825 41A5327 SIL12-W07 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;works manufactured for 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Lite-On USB NetVista Full Width Keyboard 
| &lt;!--Vendor ID--&gt;0x04b3
| &lt;!--Product ID--&gt;0x3025
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;works 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Logitech K320 Wireless Keyboard 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|The Logitech USB Unifying, Bolt, Lightspeed, or Nano receiver pairing}}
|-
| &lt;!--Description--&gt;Logitech K340 Wireless Keyboard 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|The Logitech Unifying Receiver pairing}}
|-
| &lt;!--Description--&gt;Logitech K400
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{Unk|okay keyboard}}
|-
| &lt;!--Description--&gt;[http://www.logitech.com/en-us/product/wireless-touch-keyboard-k400r Logitech Wireless Touch Keyboard k400]
| &lt;!--Vendor ID--&gt; 0x046D
| &lt;!--Product ID--&gt; 0xC52B
| &lt;!--Revision--&gt; 1201
| &lt;!--Opinion--&gt; {{yes|All (including multimedia) keys work. Some keys requires remapping with Trident. Touchpad works and acts as normal mouse. Presents itself in Trident as USB Receiver from Logitech with 3 HID bindings}}
|-
| &lt;!--Description--&gt;Logitech K400 Plus K400+ 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{Unk|okay keyboard}}
|-
| &lt;!--Description--&gt;Logitech K600 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{Unk|okay keyboard}}
|-
| &lt;!--Description--&gt;Logitech TK820 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{Unk|okay keyboard}}
|-
| &lt;!--Description--&gt;Logitech TK830 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{Unk|okay keyboard}}
|-
| &lt;!--Description--&gt;Logitech G915 TKL
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{Unk|okay keyboard TKL means no number pad}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2027 magnetic hall effect software should be better and surpasses mechanical}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Lofree Lite84 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 }}
|-
| &lt;!--Description--&gt;Lofree Flow Lite100 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 silent switches and low profile keys}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Opinion
|-
| &lt;!--Description--&gt;MACHENIKE K500 Wired 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2024 94 keys untested Hot Swappable 94 Keys 90% Layout }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;MechLands Vibe99 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2024 100 keys untested Gasket-mounted Wired/Bluetooth/2.4GHz Wireless Mechanical Keyboard}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Microsoft Comfortable Curve 2000
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no| recognized but not supported}}
|-
| &lt;!--Description--&gt;Microsoft Natural Ergonomic Keyboard 4000
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|recognized but not supported}}
|-
| &lt;!--Description--&gt;Microsoft Wireless Media Desktop 1000 (1356)
| &lt;!--Vendor ID--&gt;0x045e
| &lt;!--Product ID--&gt;0x00f9 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{maybe|working but not mouse part}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2027 magnetic hall effect software should be better and surpasses mechanical}}
|-
| &lt;!--Description--&gt;Niz Micro84 Duo82 X87 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2022 electro capacitive }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2027 magnetic hall effect software should be better and surpasses mechanical}}
|-
| &lt;!--Description--&gt;nuphy gem80 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| expensive but good}}
|-
| &lt;!--Description--&gt;nuphy kick 75 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 low profile 75% }}
|-
| &lt;!--Description--&gt;nuphy Air75 V3 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025  75% }}
|-
| &lt;!--Description--&gt;nuphy node 100 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| 96% layout, }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2027 magnetic hall effect software should be better and surpasses mechanical}}
|-
| &lt;!--Description--&gt;Qpad MK-50 MK-80 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Qpad MK-90 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2027 magnetic hall effect software should be better and surpasses mechanical}}
|-
| &lt;!--Description--&gt;Razer Chroma 
| &lt;!--Vendor ID--&gt;0x1532
| &lt;!--Product ID--&gt;0203
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;[https://openrazer.github.io/ Razer] Lycosa 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Razer Blackwidow 2013 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|  Cherry MX Blue  }}
|-
| &lt;!--Description--&gt;Razr Blackwidow Ultimate 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|  Cherry MX Blue  }}
|-
| &lt;!--Description--&gt;Razer Blackwidow V4 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|  Razer Orange keys }}
|-
| &lt;!--Description--&gt;Razer Blackwidow V4 Low Profile 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|  Razer  keys }}
|-
| &lt;!--Description--&gt;Razer Blackwidow V4 Pro 75% 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|  Razer  keys }}
|-
| &lt;!--Description--&gt;Razer Cynosa Lite V2 
| &lt;!--Vendor ID--&gt;1532
| &lt;!--Product ID--&gt;0x023f
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|  }}
|-
| &lt;!--Description--&gt;Razer DeathStalker 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|  }}
|-
| &lt;!--Description--&gt;Razer HuntsMan 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|  }}
|-
| &lt;!--Description--&gt;Razer Ornata 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|  }}
|-
| &lt;!--Description--&gt;Razer Orbweaver Chroma Keypad 
| &lt;!--Vendor ID--&gt;0x1532
| &lt;!--Product ID--&gt;0207
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|  }}
|-
| &lt;!--Description--&gt;Razer Tartarus Keypad 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|  not hall effect and very expensive}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2027 magnetic hall effect software should be better and surpasses mechanical}}
|-
| &lt;!--Description--&gt;Redragon K668 RGB Gaming Keyboard Wired 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2023 untested 108 Keys Mechanical Keyboard w/Extra 4 Hotkeys Upgraded Hot-swappable Socket，Red Switch}}
|-
| &lt;!--Description--&gt;Redragon K689 PRO Wireless 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2024 untested Gasket RGB Gaming Keyboard, 108 Keys Mechanical Keyboard w/Extra 4 Hotkeys, Upgraded Hot-swappable}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Rii K22
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 keyboard trackpad combo, non replaceable lithium battery, very compact}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2027 magnetic hall effect software should be better and surpasses mechanical}}
|-
| &lt;!--Description--&gt;Risophy 60
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2024 75% mechanical, hotswap so okay for price untested }}
|-
| &lt;!--Description--&gt;Risophy 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2028 magnetic hall effect software should be better and surpasses mechanical}}
|-
| &lt;!--Description--&gt;Royal Kludge RK65 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested cream switches }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2028 magnetic hall effect software should be better and surpasses mechanical}}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Opinion
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;SINO WEALTH Gaming KB SkyLion K68 
| &lt;!--Vendor ID--&gt;0x258a
| &lt;!--Product ID--&gt;0x003a
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| blue stalks with rgb lighting}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;SKYLOONG GK104 Pro 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested gateron }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2028 magnetic hall effect software should be better and surpasses mechanical}}
|-
| &lt;!--Description--&gt;SteelSeries 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;TeckNet x300 2.4G Keyboard Mouse MosART 
| &lt;!--Vendor ID--&gt;0x062A
| &lt;!--Product ID--&gt;0x4101
| &lt;!--Revision--&gt;0312 
| &lt;!--Opinion--&gt;{{Yes|1 AAA for each and works well - mouse slightly better built than keyboard rubberised membrane}}
|-
| &lt;!--Description--&gt;TeckNet X331 HDE 2.4G Keyboard wireless RCMCU 
| &lt;!--Vendor ID--&gt;0x0C45
| &lt;!--Product ID--&gt;0x7000
| &lt;!--Revision--&gt;0001
| &lt;!--Opinion--&gt;{{Yes|wireless can be glitchy but few extra keys are mapped }}
|-
| &lt;!--Description--&gt;TeckNet X500 2.4G Keyboard Mouse MOSArt 
| &lt;!--Vendor ID--&gt;0x062A
| &lt;!--Product ID--&gt;0x2901
| &lt;!--Revision--&gt;0112 
| &lt;!--Opinion--&gt;{{Yes|works well especially large touchpad - usual rubber domed membraned keyboard mechanism }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Tecware Specter 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested good 75%}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2028 magnetic hall effect software should be better and surpasses mechanical}}
|-
| &lt;!--Description--&gt;Unicomp Model M USB 104 key 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }} IBM's and later Lexmark buckling spring switches 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Varmilo Minilo Bluebell (prestige silent) and Eculapytus (violet tactile)
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2023 75% plastic build no screws not great to mod}}
|-
| &lt;!--Description--&gt;Varmilo Sword 68 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| expensive but good}} 
|-
| &lt;!--Description--&gt;Varmilo 98 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2024 expensive but good and Kailh silent}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2028 magnetic hall effect software should be better and surpasses mechanical}}
|-
| &lt;!--Description--&gt;Weikav Velocifire Choice65 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Weikav Velocifire Lucky65 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2024 }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2028 magnetic hall effect software should be better and surpasses mechanical}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Wobkey Rainy 75
| &lt;!--Vendor ID--&gt;0x320F 
| &lt;!--Product ID--&gt;0x5055
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2024 good 75% but not as expensive CNC Aluminum HMX/JWK/Cocoa Switches}}
|-
| &lt;!--Description--&gt;Wobkey Crush 80 
| &lt;!--Vendor ID--&gt;0x320F 
| &lt;!--Product ID--&gt;0x5588 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Wobkey Crush80 Reboot Pro 
| &lt;!--Vendor ID--&gt;0x320F 
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2024 very good but expensive Aluminum Hotswap Wireless RGB}}
|-
| &lt;!--Description--&gt;Wobkey Rainy 75 Pro 
| &lt;!--Vendor ID--&gt;0x320F
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2026 magnetic hall effect software should be better and surpasses mechanical}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Wooting HE60 HE80 HE90 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2024 hall effect but expensive with good software}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2028 magnetic hall effect software should be better and surpasses mechanical}}
|-
| &lt;!--Description--&gt;Womier WK61 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2021 untested }}
|-
| &lt;!--Description--&gt;Womier Sk71 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2024  }}
|-
| &lt;!--Description--&gt;Womier Sk75 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2024  }}
|-
| &lt;!--Description--&gt;Womier Sk75 TMR 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025  hall effect }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2028 magnetic hall effect software should be better and surpasses mechanical}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Xenta White Wireless HK6718B+HM3302--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{Maybe|works with Raspberry Pi untested on AROS native}}
|-
| &lt;!--Description--&gt;Xinmeng X87 MAGIC_REFINER 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2024 untested keycap swap but not hotswapable switches}}
|-
| &lt;!--Description--&gt;Yunzii AL66 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| milk switches, cherry PBT, }}
|-
| &lt;!--Description--&gt;Yunzi B75 Pro 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2024 budget good with cocoa cream switches }}
|-
| &lt;!--Description--&gt;Yunzii AL75 Pro 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|good budget option with  swappable switches,  }}
|-
| &lt;!--Description--&gt;Yunzii AL80
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 switches }}
|-
| &lt;!--Description--&gt;Yunzi C75 Pro 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 budget good with  switches }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2028 magnetic hall effect software should be better and surpasses mechanical}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
|}

&lt;pre&gt;
linear  - creamy
tactile - thocky
clicky  - clacky 
&lt;/pre&gt;

&lt;pre &gt;
Cherry MX Black are linear switches (no feedback); good for gaming. 
Cherry MX Red are linear (less noise no click) but more squishy; 
Cherry MX Brown are in between Blue and Red in style and tactile; 
Cherry MX Clear switches have soft tactile feedback (with no click). 
Cherry MX Blue have tactile feedback with a click (noisy); good for typing. 

Gateron Yellows KS-3, KS-3x47 or better Pros have a milky top and black bottom and linear 

TTC Silent Frozen v2. Linear and dead silent 
Mouse the huano brown with yellow dot for silent mouse clicks
Kailh red dust proof encoder for smooth and close to silent scrolling
Boba U4 Silent Tactile switches
Husky linears

HMX 
&lt;/pre &gt;


=== Mouse ===

if the USB mouse is non-functional put a USB pendrive in before or add the following to user-startup in '''s''' drawer/folder/directory

 sys:prefs/trident NOGUI &gt; NIL:

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot; | Brand
! width=&quot;20%&quot; | Description 
! width=&quot;10%&quot; | Model
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| 3Dconnexion 
| 3D Mouse 
| &lt;!--Model--&gt;[http://www.3dconnexion.com/products/spacenavigator.html SpaceNavigator]
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| {{N/A|untested}}
|-
| 3Dconnexion 
| 3D Mouse
| &lt;!--Model--&gt;SpacePilot Pro
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| {{N/A|untested}}
|-
| 3Dconnexion 
| Mouse 
| &lt;!--Model--&gt;SpaceExplorer 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| {{N/A|untested}}
|-
| 3Dconnexion 
| Wireless Mouse 
| &lt;!--Model--&gt;SpaceMouse 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| {{N/A|untested}}
|-
| &lt;!--Brand--&gt;3D Optical 
| &lt;!--Description--&gt;Wired 
| &lt;!--Model--&gt;
| &lt;!--Vendor ID--&gt;0000:3825
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}}
|-
| &lt;!--Brand--&gt;
| &lt;!--Description--&gt;
| &lt;!--Model--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}}
|-
| Belkin
| Combo mouse
|
| 0x05FE
| 0x0011
| Low 0100
| {{yes|works}}
|-
| &lt;!--Brand--&gt;
| &lt;!--Description--&gt;
| &lt;!--Model--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}}
|-
| &lt;!--Brand--&gt;Cytec
| &lt;!--Description--&gt;Wired Mouse Gaming 
| &lt;!--Model--&gt;R.A.T 5 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}}
|-
| &lt;!--Brand--&gt;
| &lt;!--Description--&gt;
| &lt;!--Model--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}}
|-
| Dell
| Mouse
| MO56UC
| 0x413C
| 0x3200
|
| {{yes|works}}
|-
| &lt;!--Brand--&gt;
| &lt;!--Description--&gt;
| &lt;!--Model--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}}
|-
| &lt;!--Brand--&gt;
| &lt;!--Description--&gt;
| &lt;!--Model--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}}
|-
| &lt;!--Brand--&gt;equatech / clone logitech  
| &lt;!--Description--&gt;wireless mouse
| &lt;!--Model--&gt;49779 / M185 
| &lt;!--Vendor ID--&gt; 3151:2020 later 3151:3020 
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{Yes|detected and works}}
|-
| &lt;!--Brand--&gt;
| &lt;!--Description--&gt;
| &lt;!--Model--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}}
|-
| Hama
| RF Optical Mouse
| AM-6000
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| {{N/A|untested}}
|-
| &lt;!--Brand--&gt;Keychron 
| &lt;!--Description--&gt;Optical 
| &lt;!--Model--&gt;M3
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}}
|-
| &lt;!--Brand--&gt;Keychron 
| &lt;!--Description--&gt;Optical 
| &lt;!--Model--&gt;M5 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}}
|-
| &lt;!--Brand--&gt;Keycron 
| &lt;!--Description--&gt;Optical Wireless 
| &lt;!--Model--&gt;M6 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested 1k polling and 16k dpi }}
|-
| &lt;!--Brand--&gt;Keychron 
| &lt;!--Description--&gt;Optical Wireless 
| &lt;!--Model--&gt;M7
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested barebones 1k polling and 16k dpi, great for small hands, loud clicks}}
|-
| &lt;!--Brand--&gt;
| &lt;!--Description--&gt;
| &lt;!--Model--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}}
|-
| &lt;!--Brand--&gt;LogiCAD 3D
| &lt;!--Description--&gt;3D Mouse
| &lt;!--Model--&gt;Magellan 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| {{N/A|untested}}
|-
| &lt;!--Brand--&gt;
| &lt;!--Description--&gt;
| &lt;!--Model--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}}
|-
| Logitech
| Cordless Desktop Navigator 
| &lt;!--Model--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| {{No|The Logitech Unifying Receiver pairing}}
|-
| Logitech Inc.
| First/Pilot Wheel Mouse
| N48/M-BB48 M-BE58 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| {{N/A|untested }}
|-
| Logitech
| Wireless mouse
| [http://www.logitech.com/en-roeu/mice_pointers/mice/devices/5484 M305]
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| {{yes|works}}
|-
| Logitech
| Wireless RF Mouse
| MK710
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| {{No|The Logitech Unifying Receiver pairing}}
|-
| &lt;!--Brand--&gt;Logitach
| &lt;!--Description--&gt;Optical
| &lt;!--Model--&gt;G304
| &lt;!--Vendor ID--&gt;0x
| &lt;!--Product ID--&gt;0x
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2021 very clicky}}
|-
| &lt;!--Brand--&gt;Logitech
| &lt;!--Description--&gt;Wireless Mouse 
| &lt;!--Model--&gt;MX Master Anywhere 2S 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{No|untested}} micro USB charge port on front 
|-
| &lt;!--Brand--&gt;Logitech 
| &lt;!--Description--&gt;Wireless 
| &lt;!--Model--&gt;M220 silent touch MR0085
| &lt;!--Vendor ID--&gt;0x
| &lt;!--Product ID--&gt;0x
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2018 needs usb dongle - quiet clicking }}
|-
| &lt;!--Brand--&gt;Logitech Logi 
| &lt;!--Description--&gt;Optical 
| &lt;!--Model--&gt;MX Master 3S 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{No|2021 untested usb-c bluetooth, inbuilt battery but muted clicks}}
|-
| &lt;!--Brand--&gt;Logitach
| &lt;!--Description--&gt;Optical
| &lt;!--Model--&gt;G502 X Plus 
| &lt;!--Vendor ID--&gt;0x
| &lt;!--Product ID--&gt;0x
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2022 very clicky}}
|-
| &lt;!--Brand--&gt;Logitech 
| &lt;!--Description--&gt;Wireless 
| &lt;!--Model--&gt;M240 silent touch MR0105  
| &lt;!--Vendor ID--&gt;0x
| &lt;!--Product ID--&gt;0x
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{maybe|2022 no dongle as bluetooth enabled but could work with Logi Bolt USB Receiver - 1 aa battery - quiet clicking}}
|-
| &lt;!--Brand--&gt;Logitech
| &lt;!--Description--&gt;Optical 
| &lt;!--Model--&gt;MX Master 4 MXM
| &lt;!--Vendor ID--&gt;0x
| &lt;!--Product ID--&gt;0x
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|Bluetooth usb-c dongle, inbuilt lithium battery}}
|-
| &lt;!--Brand--&gt;
| &lt;!--Description--&gt;
| &lt;!--Model--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Brand
| Description
| Model
| Vendor ID
| Product ID
| Revision
| Opinion--&gt;
|-
| &lt;!--Brand--&gt;Maxxter 
| &lt;!--Description--&gt;Wireless
| &lt;!--Model--&gt;
| &lt;!--Vendor ID--&gt;248a:8566
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}}
|-
| &lt;!--Brand--&gt;Maxxter 
| &lt;!--Description--&gt;Wireless 
| &lt;!--Model--&gt;
| &lt;!--Vendor ID--&gt;248a:8518
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}}
|-
| &lt;!--Brand--&gt;OrzerHome Maxxter 
| &lt;!--Description--&gt;Wireless 
| &lt;!--Model--&gt;
| &lt;!--Vendor ID--&gt;248a:8514
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested 1 aa with no on/off switch }}
|-
| &lt;!--Brand--&gt;
| &lt;!--Description--&gt;
| &lt;!--Model--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}}
|-
| Microsoft
| Wheel Mouse optical
| &lt;!--Model--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| {{N/A|untested}}
|-
| Microsoft
| Sidewinder Mouse 
| &lt;!--Model--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| {{N/A|untested}}
|-
| Microsoft
| IntelliMouse Explorer USB optical
| &lt;!--Model--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| {{N/A|untested}}
|-
| Microsoft
| Wireless Optical Mouse 2000
|
| 0x045E
| 0x00F9 
|
| {{no|not working see keyboard Media Desktop 2000 above}}
|-
| &lt;!--Brand--&gt;Microsoft 
| &lt;!--Description--&gt;
| &lt;!--Model--&gt;1461 1447 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{No|usb dongle matched to one mouse only no others}}
|-
| &lt;!--Brand--&gt;
| &lt;!--Description--&gt;
| &lt;!--Model--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}}
|-
| &lt;!--Brand--&gt;
| &lt;!--Description--&gt;
| &lt;!--Model--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}}
|-
| &lt;!--Brand--&gt;Razer
| &lt;!--Description--&gt;USB optical
| &lt;!--Model--&gt;Orochi 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}} 
|-
| &lt;!--Brand--&gt;Razer
| &lt;!--Description--&gt;USB optical
| &lt;!--Model--&gt;Mamba 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}} 
|-
| &lt;!--Brand--&gt;Razer
| &lt;!--Description--&gt;USB optical
| &lt;!--Model--&gt;Naga
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}} 17 buttons 
|-
| &lt;!--Brand--&gt;Razer
| &lt;!--Description--&gt;USB Optical
| &lt;!--Model--&gt;Naga Hex V2
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}} MOBA Gaming Mouse, Professional Grade 16,000 DPI Sensor - RGB lighting 
|-
| &lt;!--Brand--&gt;Razer
| &lt;!--Description--&gt;USB optical 
| &lt;!--Model--&gt;DeathAdder 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}} 
|-
| &lt;!--Brand--&gt;Razer
| &lt;!--Description--&gt;USB optical
| &lt;!--Model--&gt;Viper 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}} 
|-
| &lt;!--Brand--&gt;Razer
| &lt;!--Description--&gt;USB optical
| &lt;!--Model--&gt;Basilisk V3 Pro 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested 1k polling, 35k dpi, }} 
|-
| &lt;!--Brand--&gt;
| &lt;!--Description--&gt;
| &lt;!--Model--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}}
|-
| Trust
| Slimline Lasermouse 
| &lt;!--Model--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| {{N/A|untested}}
|-
| SteelSeries 
| Tobii EyeX EyeMobile PCEye 
| Eye Tracking Control 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| {{N/A|untested}} gaze interaction track technology for augment augmentative and alternative communication (AAC). 
|-
| &lt;!--Brand--&gt;
| &lt;!--Description--&gt;
| &lt;!--Model--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}}
|-
| &lt;!--Brand--&gt;The Eye Tribe Tracker 
| &lt;!--Description--&gt;Eye 
| &lt;!--Model--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}}
|-
| &lt;!--Brand--&gt;
| &lt;!--Description--&gt;USB Optical Mouse 
| &lt;!--Model--&gt;MV3000
| &lt;!--Vendor ID--&gt;0x192f
| &lt;!--Product ID--&gt;0x0916
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{yes|works}}
|-
| &lt;!--Brand--&gt;
| &lt;!--Description--&gt;
| &lt;!--Model--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}}
|-
| &lt;!--Brand--&gt;
| &lt;!--Description--&gt;
| &lt;!--Model--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}}
|-
| &lt;!--Brand--&gt;
| &lt;!--Description--&gt;
| &lt;!--Model--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}}
|-
| &lt;!--Brand--&gt;
| &lt;!--Description--&gt;
| &lt;!--Model--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; {{N/A|untested}}
|}

=== Trackball ===
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;3Dconnexion SpaceBall 5000
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| {{N/A|untested}} Labtec designed and rolled into new company 3dconnexion 2001 by owners Logitech 
|-
| &lt;!--Description--&gt;ACCO Kensington Orbit optical F1233A 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Kensington Turbo Mouse 64210
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Clearly Superior Technologies. Model:CST 1000-RC
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Logitech Trackman Marble Mouse Wired USB
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Logitech Cordless Trackman Wheel 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Logitech Optical Trackman T-RB22 - Cordless 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Logitech M570 wireless
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Microsoft Trackball Mouse Optical 1.0 USB
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Microsoft X05-87473 Trackball USB Optical 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
|}


=== KVM ===
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;NanoKVM 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
|}


=== Gamepad ===

Controllers have mostly decided that the left analog joystick is keyboard equivalent of WASD and right joystick is your mouse. You also have 2 bumpers above the triggers. Shoot could be right trigger (so it doesn't involve taking your thumb off the right joystick). Face buttons for reloading or jump or other non-critical functions. Crank up the sensitivity and practice. 

Testing can be done with the TRIDENT Prefs, [https://devicetests.com/controller-tester html5], [https://greggman.github.io/html5-gamepad-test/ html5], or [https://gamepad-tester.com/ Tester]


==== Dinput Poseidon Default Plugin - Playstation(TM) style ====

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;35%&quot; |Description 
! width=&quot;5%&quot;  |Vendor ID
! width=&quot;5%&quot; |Product ID
! width=&quot;5%&quot; |Revision
! width=&quot;10%&quot; |Merge with USB on Digital Pad
! width=&quot;10%&quot; |Analogue Hack with Analog Stick
! width=&quot;30%&quot; |Opinion
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Betop Betong Bat D2E BTP-BD2E XD4D2E
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;  
|- 
| &lt;!--Description--&gt;Gravis Eliminator Gamepad Pro USB  
| &lt;!--Vendor ID--&gt;047d
| &lt;!--Product ID--&gt;4005
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;{{N/A}}
| &lt;!--Opinion--&gt;2002 2d only 
|-
| Hama Black Force USB Gamepad
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{Maybe| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{Maybe| }}
| &lt;!--Opinion--&gt;2003 psx clone look 
|- 
| &lt;!--Description--&gt;Jess Tech Game Elements Philips GGE909 PC Recoil Pad 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Merge with USB on Digital Pad
| Analogue Hack with Analog Stick
| Opinion
|-
| [http://www.youtube.com/watch?v=TCbAmIhj6P4 Logitech Wingman Precision USB] G-UC3B 
| &lt;!--Vendor ID--&gt;0x046d 
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;{{Yes| }} 
| &lt;!--Analogue Hack with Analog Stick--&gt;{{N/A| }} 
| 2002 no 3D but good for 2D retro games like Turrican II
|-
| &lt;!--Description--&gt;Logitech Wingman Action Pad G-UB3A 
| &lt;!--Vendor ID--&gt;0x046d
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{Yes| }} 
| &lt;!--Analogue Hack with Analog Stick--&gt;{{Maybe|untested }} 
| &lt;!--Opinion--&gt;2002 1 blue lucid translucent - thin analog stick N64 type - 
|- 
| Logitech Wingman RumblePad UB05B
| &lt;!--Vendor ID--&gt;0x046d 
| 0xc20a
| 1.12
| &lt;!--Merge with USB Digital Pad--&gt;{{Yes| }} 
| &lt;!--Analogue Hack with Analog Stick--&gt;{{Maybe|untesed }} 
| 2000 twin blue analogue sticks N64 type - poor 2d controls with single molded blue piece - vibration feedback - single shoulder buttons with throttle control below right one 
|-
| Logitech Wingman Cordless RumblePad G-RA4A 
| &lt;!--Vendor ID--&gt;0x046d 
| 0xc211
| 1.12
| &lt;!--Merge with USB Digital Pad--&gt;{{Yes| }} 
| &lt;!--Analogue Hack with Analog Stick--&gt;{{Maybe|untested }} 
| 2001 twin blue analogue sticks N64 type - poor 2d controls with single molded black piece - vibration feedback - dual shoulder buttons L1 L2 R1 R2 with blue throttle control below right one - 4 aa mn1500 batteries; life not great - C-UD10A usb dongle - overall big and bulky 
|-
| &lt;!--Description--&gt;Logitech Precision Wired G-UG15
| &lt;!--Vendor ID--&gt;0x046d 
| &lt;!--Product ID--&gt;0x
| &lt;!--Revision--&gt;0x
| &lt;!--Merge with USB on Digital Pad--&gt;{{Maybe| }} 
| &lt;!--Analogue Hack with Analog Stick--&gt;{{N/A|N/A}} 
| &lt;!--Opinion--&gt;2002 psx styling blue outer shell - no 3D analog and no shoulder buttons - no rumble 
|-
| &lt;!--Description--&gt;Logitech Cordless Precision G-X2E14A
| &lt;!--Vendor ID--&gt;0x046d 
| &lt;!--Product ID--&gt;0x
| &lt;!--Revision--&gt;0x
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }} 
| &lt;!--Analogue Hack with Analog Stick--&gt;{{N/A|N/A}} 
| &lt;!--Opinion--&gt;2002 ps2 styling blue outer shell - no 3D analog and no shoulder buttons - no rumble 
|-
| &lt;!--Description--&gt;Logitech G-X5C11A Cordless Precision Wireless Controllers
| &lt;!--Vendor ID--&gt;0x046d 
| &lt;!--Product ID--&gt;0x
| &lt;!--Revision--&gt;0x
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }} 
| &lt;!--Analogue Hack with Analog Stick--&gt;{{N/A|N/A}} 
| &lt;!--Opinion--&gt;2002 psx styling black outer shell - no 3D analog and no shoulder buttons - no rumble 
|-
| [http://www.testfreaks.co.uk/game-console-accessories-controls/logitech-dual-actiontm-gamepad/ Logitech Dual Action] 
* G-UD8 has no mode (2D only?) button and no rumble 
* G-UF13A later 
| &lt;!--Vendor ID--&gt;0x046d 
| 0xc2
| 
| &lt;!--Merge with USB Digital Pad--&gt;{{Yes| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{Yes|[http://www.morphzone.org/modules/newbb_plus/viewtopic.php?topic_id=7018&amp;forum=12 G-UF13A tested only]}} 
| 2003 New body shape psx style - dual analog 3D sticks - 4 small travel shoulder triggers no 5,6,7,8 
|-
| Logitech RumblePad 2 G-UF13
| &lt;!--Vendor ID--&gt;0x046d 
| 0xc218
| 1.00
| &lt;!--Merge with USB Digital Pad--&gt;{{Yes| }} 
| &lt;!--Analogue Hack with Analog Stick--&gt;{{Yes| }} 
| 2006 light blue top/black base - twin analogues 3D along with dual short travel shoulder buttons - rumble present - 
|-
| &lt;!--Description--&gt;[Logitech RumblePad 2 Cordless] 
* G-RC?? OLD version that take FOUR batteries and RED Logitech logo 
* G-RC14 uses TWO batteries has an ORANGE logo - dongle C-UE10 
| &lt;!--Vendor ID--&gt;0x046d
| &lt;!--Product ID--&gt;0xc219
| &lt;!--Revision--&gt;0x0200
| &lt;!--Merge with USB Digital Pad--&gt;{{Yes| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{Yes|mostly}}
| &lt;!--Opinion--&gt;2008 may have to remove 1 battery - G-RC?? 5 + 7 buttons - G-RC14 use buttons 6 + 8 to reset sticks - replace battery and push large button on receiver - 
|- 
| &lt;!--Description--&gt;Logitech F310 Wired Dual Action G-U0001 
| &lt;!--Vendor ID--&gt;0x046d 
| &lt;!--Product ID--&gt;0xc21
| &lt;!--Revision--&gt;0x
| &lt;!--Merge with USB on Digital Pad--&gt;{{Yes| }} 
| &lt;!--Analogue Hack with Analog Stick--&gt;{{Yes|D mode switch}} 
| &lt;!--Opinion--&gt;2010 dual analog 3D with pc-xbox/psx switch on back (only D works) - both rear shoulder RT LT buttons have excess travel - no rumble vibration - 
|-
| &lt;!--Description--&gt;Logitech F510 Wired G-UG0002 
| &lt;!--Vendor ID--&gt;0x046d 
| &lt;!--Product ID--&gt;0xc21
| &lt;!--Revision--&gt;0x
| &lt;!--Merge with USB on Digital Pad--&gt;{{Maybe| }} 
| &lt;!--Analogue Hack with Analog Stick--&gt;{{Maybe| }} 
| &lt;!--Opinion--&gt;2010 dual analog with dual xbox pc/psx X/D switched compatibility modes - 
|-
| Logitech F710 Wireless / Cordless RumblePad 2 G-R0001 
| &lt;!--Vendor ID--&gt;0x046d 
| 0xc219
| 3.05
| &lt;!--Merge with USB Digital Pad--&gt;{{Yes| }} 
| &lt;!--Analogue Hack with Analog Stick--&gt;{{Maybe| }} 
| When switch on top set to D and nano receiver for each controller to pair - 2 aa mn1500 batteries required - rumble support sometimes - rear back shoulder buttons excessive travel needed 
|- 
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Merge with USB on Digital Pad
| Analogue Hack with Analog Stick
| Opinion
|-
| &lt;!--Description--&gt;Megaworld 'TIME' USB pad
| &lt;!--Vendor ID--&gt;0x0735
| &lt;!--Product ID--&gt;0x9902
| &lt;!--Revision--&gt;Low 0100
| &lt;!--Merge with USB Digital Pad--&gt;{{Yes| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No |}}
| &lt;!--Opinion--&gt;2000 Poor quality
|-
| &lt;!--Description--&gt;Microsoft 
* SideWinder Precision Pro USB (1997)
* SideWinder Precision 2 (1998)
* Game Pad Pro (1999)
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Microsoft Sidewinder Game Pad USB 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{yes| }}}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{yes| }}
| &lt;!--Opinion--&gt;[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1149&amp;rowstart=140&amp;pid=5934#post_5931 must setup first]
|- 
| &lt;!--Description--&gt;Microsoft Sidewinder Gamepad X04 Freestyle 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;{{Maybe| }} 
| &lt;!--Analogue Hack with Analog Stick--&gt;{{N/A|N/A }} 
| &lt;!--Opinion--&gt;{{N/A|untested}} 1998 might need USB adapter 
|-
| &lt;!--Description--&gt;Microsoft Sidewinder X05 63895 92626 Flight stick
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;{{Yes| }} 
| &lt;!--Analogue Hack with Analog Stick--&gt;{{unk| }} 
| &lt;!--Opinion--&gt;{{Yes|2000 [https://ae.amigalife.org/index.php?topic=929.msg11309#new tested]}}
|-
| &lt;!--Description--&gt;Microsoft Sidewinder Flight Stick X08-58736 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Microsoft 
    Plug &amp; Play Game Pad (2000)
    SideWinder Joystick (2000)
    Game Pad 2.0 (2001)
    SideWinder Force Feedback 2 (2002)
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2002 long-standing static buildup problem and Force Feedback 2 was the removal of the power brick 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| Saitek [http://www.testfreaks.co.uk/game-console-accessories-controls/saitek-ps1000/ PS1000 Cyborg V.1], [http://www.testfreaks.co.uk/game-console-accessories-controls/saitek-ps2700-rumble-pad/ PS2700] 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;{{Yes| }} 
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2000 no rumble function 
|- 
| Saitek [http://www.youtube.com/watch?v=xG0v-hf6ZPA P2600] [http://compactiongames.about.com/od/hardware/tp/gamepads.htm P3600], 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;{{Yes| }} 
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2000 no rumble function
|- 
| Saitek P2900 wireless 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| {{N/A|untested but runs on 1 AA battery}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Merge with USB on Digital Pad
| Analogue Hack with Analog Stick
| Opinion
|-
| &lt;!--Description--&gt;Sony Batoh PS3 mini USB Wired hookup [http://ps3.jim.sh/sixaxis/usb/ SIXAXIS] 
*PCB  Ribbon      Notes
*Protos ALPS MSU Rev3 M3 and the later CBEH-1019
*?    SA1Q135A 	  for sixaxis
*PP4  
*V2   
*V25  
*VX   SA1Q146A    first dualshock 3 model
*VX   SA1Q147A    CECHZC2U (USA)
*VX35 SA1Q159A 	  
*VX3  SA1Q160A 	  
*VX?  SA1Q188A    
*VX4  SA1Q189A    shipped with a CECH-2504 datecode 0C 
*VX5  SA1Q194A    changed design ALPS, PS button changes
*VX6  SA1Q195A    red case, 
*VX7  SA1Q222A    superslims 2 ribbons
*VX8  SA1Q224A    superslims 2 ribbons 
| &lt;!--Vendor ID--&gt;0x054c
| &lt;!--Product ID--&gt;0x0268
| &lt;!--Revision--&gt;1.00 
| &lt;!--Merge with USB on Digital Pad--&gt;{{No|}}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No|}}
| &lt;!--Opinion--&gt;Sometimes detected but no support - no sixaxis features detected - mini usb lead will have varying results - 
|- 
| &lt;!--Description--&gt;Sony PS4 
*JDM JDS 001 010 011 
*JDM 030 040 055 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Sony PS5 Dual Sense 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Speed Link Strike 2 FX 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Thrustmaster Firestorm Dual Power 2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;{{Yes| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{Yes|[http://www.morphzone.org/modules/newbb_plus/viewtopic.php?topic_id=7018&amp;forum=12 only 1 axis joystick only]}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Trust Predator GM-1500 GM-1520
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Merge with USB on Digital Pad
| Analogue Hack with Analog Stick
| Opinion
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Haute42 M series Aluminum Metal Joystick Hitbox Controller Arcade Fighting Stick
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Haute42 T series 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Haute42 G series Gamefinger G12 G13 G16 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt; plastic - 
|- 
| &lt;!--Description--&gt;Haute42 S series 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;  thinner and lighter than G series 
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Mad Catz sf2 fightstick 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Mayflash Datel Paewang Arcade Pro Stick 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Mayflash F300 Fighting Stick 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Mayflash F500 Fighting Stick 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Pico Flatbox GP2040-CE Hot Swappable Mini Hitbox Keyboard 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;  default it is configured for PS4 but before plugging usbc cable in, X for Dinput, B Xinput, RT HID - plastic build case - Rev4 based on RP2040 chip and firmware is based on GP2040-CE (Community Edition) - 
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Shenzhen Onebitdo Tech 8bitdo Fighting stick 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Venom 8 button 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
|}


==== Xinput Xbox Style Plugin ====

2018 extension added originally called AROSx but later redacted. Latest [https://github.com/medusalix/xone linux driver] might be useful. 

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;35%&quot; |Description 
! width=&quot;5%&quot;  |Vendor ID
! width=&quot;5%&quot; |Product ID
! width=&quot;5%&quot; |Revision
! width=&quot;10%&quot; |Merge with USB on Digital Pad
! width=&quot;10%&quot; |Analogue Hack with Analog Stick
! width=&quot;30%&quot; |Opinion
|-
| &lt;!--Description--&gt;8bitdo Ultimate C Wired 82CB (Shenzhen ONEBITDO TECH - GWOWO) 
| &lt;!--Vendor ID--&gt;0x2dc8 
| &lt;!--Product ID--&gt;0x3106 
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;2022 - 4 t6 torx screws - non hall effect so drifting issues - triggers go faulty often - 
|- 
| &lt;!--Description--&gt;8bitdo Ultimate 2C Wired Controller 82CD 
| &lt;!--Vendor ID--&gt;0x2dc8 
| &lt;!--Product ID--&gt;0x310A
| &lt;!--Revision--&gt;0114
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;2024 - HID keyboard assigned - 4 t6 torx screws - hall effect analogs and triggers  - 1000Hz polling - 
|- 
| &lt;!--Description--&gt;8bitdo Ultimate 2C wireless 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;2024  - 400mw battery - hall effect 3d nubs and triggers - micro switch shoulder buttons - d-pad poor for retro games - 
|- 
| &lt;!--Description--&gt;8bitdo ULtimate Mini Wired Controller for Xbox 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2024 hall effect 
|- 
| &lt;!--Description--&gt;8BitDo Pro 2 
*Wired Controller 
*Wireless
*Bluetooth
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2024 hall effect - playstation style layout for pc - slide button for S-A-D-X switch, android, dinput or xinput -  
|-
| &lt;!--Description--&gt;8BitDo Pro 2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2025  tmr hall effect analogs, hall effect triggers and some microswitches - button swap - ps2 style layout - 
|- 
| &lt;!--Description--&gt;8bitdo Ultimate 3
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;2026  - mw battery - hall effect 3d nubs and triggers - micro switch shoulder buttons - d-pad  for retro games - 
|- 
| &lt;!--Description--&gt;8BitDo Pro 3
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2026  hall effect analogs, hall effect triggers and some microswitches - button swap - ps2 style layout - 
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Ace Aurora 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2025 hall effect joysticks with no deadzone mode, gyro, linear rumble, trigger stops, back paddles, button swap, macro, turbo, RGB LED effects -  tri-mode connection - 
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Betop Beitong Spartan BTP-2270U 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;  no hall effect 
|- 
| &lt;!--Description--&gt;Betop Betong Asura 2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;  no hall effect - noble linear trigger potentiometer and alps shoulder LB/RB micro switch 
|- 
| &lt;!--Description--&gt;BEITONG ASURA 2 Pro+ Game Controller Wireless Gamepad
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Beitong Zeus 2  
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;BebonCool Dinofire Model Number: Q218 / TP28
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2021  - triggers aren't progressive but ON/OFF - 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;EasySMX X05 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2024 hall effect analog and triggers - tri mode connection - 
|- 
| &lt;!--Description--&gt;EasySMX Wireless Controller PC PS3, 9013pro ESM-9013PRO
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2024 linear hall effect but device sometimes will not connect tried multiple attempts with the dongle
|- 
| &lt;!--Description--&gt;EasySMX X10 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;EasySMX X20 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2024 ABXY MICRO SWITCH - Bumpers Tactile switch Hall Effect analog 
|- 
| &lt;!--Description--&gt;EasySMX X15 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2025 hall effect analog and triggers - membrane buttons - 
|- 
| &lt;!--Description--&gt;EasySMX S10 Wireless Gamepad 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2025 TMR Hall effect and compatible with Switch 2/PC/Phone/TV/Steam, NFC, Gyro, HD Rumble - 
|- 
| &lt;!--Description--&gt;EasySMX 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;202
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Fantech World EOS Pro WGP15 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2024 hall effect trigger and sticks,2 back paddles, motion controlling 
|- 
| &lt;!--Description--&gt;Fantech EOS PRO II S 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2025 controller with TMR hall effect analogues, mechanical face buttons and D-pad, 63 input macro, back paddles, turbo - analog triggers with trigger stops - tri mode bt wifi and wired - slide switch on back for switch, macos/android and xinput - 
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Flydigi Apex 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;2023  luxury model 
|- 
| &lt;!--Description--&gt;Flydigi Vader Pro 3 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;2023 the Pro(Hall Effects) and Non-Pro (No Hall) 
|- 
| &lt;!--Description--&gt;Flydigi Direwolf 2
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;2023 hall effect sticks and triggers - poor wifi connection - 
|- 
| &lt;!--Description--&gt;Flydigi Apex 4
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;2024  luxury model 
|-
| &lt;!--Description--&gt;Flydigi Vader 4 Pro 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;2024 - hall effect, DInput mode (o+A hold) - 
|- 
| &lt;!--Description--&gt;Flydigi Direwolf 3 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;2024 hall effect analog and triggers but membrane buttons with gold contacts - 800mhA battery - 
|- 
| &lt;!--Description--&gt;Flydigi Dunefox 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;2024 basic model hall effect analog and triggers but membrane buttons - 500mha battery - no gyros - 
|- 
| &lt;!--Description--&gt;Flydigi Vader 5 Pro 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;2025 - hall effect stick with tension control, linear triggers, DInput mode (o+A hold) - 
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Gamesir T4K Keleid, T4C Cyclone wired 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2023 poor to ok switch 
|- 
| &lt;!--Description--&gt;Gamesir Nova 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{no|| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{no| }}
| &lt;!--Opinion--&gt;2024 - switch type layout 
|- 
| &lt;!--Description--&gt;Guangzhou Chicken Run Network Tech Nova Lite GameSir-T4n LITE - Zikway HID gamepad
*[https://www.reddit.com/r/Gamesir/comments/1c185ve/psa_keep_gamesir_nova_lite_t4n_lite_firmware_at/ fw 4200 seems to be xbox so B then Home for Xinput (green LED), A then Home for HID BT Android (green/yellow LED), Y then Home for Switch Pro (Red LED)] or X then Home for Wifi and start and select to alternatively swap modes 
* and if on [https://www.reddit.com/r/Gamesir/comments/1c185ve/psa_keep_gamesir_nova_lite_t4n_lite_firmware_at/ fw 5700 ds4 so Home + B (blue LED), ]
* firmware 6900 
| &lt;!--Vendor ID--&gt;0x3537
| &lt;!--Product ID--&gt;0x1040 0x1041
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{no| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{no| }}
| &lt;!--Opinion--&gt;2024 - hall effect 3d nubs - no usb-c cable - rubber membrane analog trigger travel and bumpers shoulder buttons - wifi 2.4G and bluetooth - xbox layout so ab and xy might need to be swapped via m and a buttons for switch type [https://www.youtube.com/watch?v=po-nNuC5fps fixes video] - 250Hz polling - 600mah battery - rigid carry case - poor d-pad esp diagonals - gamesir settings software only on android 6+ or ios based only - 
|- 
| &lt;!--Description--&gt;Gamesir Nova 2 Lite  
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;GameSir G7 SE Wired Controller 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2024 hall effect 
|- 
| &lt;!--Description--&gt;GameSir G8 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Gamesir TEGENARIA T3 Lite Wired 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2024 playstation aesthetic hall effect analog and membrane buttons - X+Home button connects as an Xbox controller
|- 
| &lt;!--Description--&gt;GameSir Cyclone 2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2024 TMR Joysticks with anti-friction rings and metal anti-friction rings around the stems, gyro, rumble, macro, turbo, 2 back paddles, hall analog triggers with micro-switch trigger - tri mode bluetooth, 2.4GHz wifi and wired, 1000hz polling rate - gamesir connect software - 
|- 
| &lt;!--Description--&gt;GameSir G7 Pro for Xbox 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2024 TMR hall effect - hall effect triggers, tri mode connection - gamesir nexus software - 
|-
| &lt;!--Description--&gt;GameSir Super Nova Pro 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2026 hall effect sticks and triggers, 1000Hz polling, tri mode connectivity, 
|- 
| &lt;!--Description--&gt;GameSir 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;GameSir 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;GameSir 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;GuliKit 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;GuliKit KingKong 2 NS08 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;Electromagnetic Stick hall effect - hall linear triggers - Mechanical face buttons - wired and wireless - Built-in rechargeable lithium battery 
|-
| &lt;!--Description--&gt;GuliKit KingKong 2 PRO NS09
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;hall efect - wired and wireless - Mechanical face buttons - Built-in rechargeable lithium battery 
|-
| &lt;!--Description--&gt;GuliKit KingKong MAX 3 KK3 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;hall effect - wired and wireless - lithium battery - 
|-
| &lt;!--Description--&gt;Gulikit KK3 Max USB-c Bluetooth Controller
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2024 Hall Joysticks and Triggers, Maglev/Rotor/HD Vibration, 1000Hz Polling Rate, 4 Back Buttons,  
|- 
| &lt;!--Description--&gt;GuliKit KK3 PRO 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;2024 smaller version of KK3 MAX - hall effect analog and triggers, face buttons , maglev rumble, gyro, 4 back paddles - rigid case - 950mAh up to 8 hrs - 
|-
| &lt;!--Description--&gt;GuliKit 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Hyperkin 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Hori EX2 Turbo UHX3-45 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Machenike G1 Pro 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2024 Wireless Gaming Controller with 1K Polling Rate Hall Effect Trigger Joystick For Nintendo Switch PC iOS Android 
|- 
| &lt;!--Description--&gt;Machenike G5 Pro Wireless Gaming Controller 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2024 ABXY Switch Membrane, Bumpers Tactile switch and hall effect analog 
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;microsoft sidewinder precision pro 
| &lt;!--Vendor ID--&gt;0x045E
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| [https://pineight.com/mw/index.php?title=USB_game_controllers Xbox 360 Wired Controller]
| 0x045e
| 0x028e
| 0x
| &lt;!--Merge with USB Digital Pad--&gt;{{No|needs specific driver and has poor 2D control pad}}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;
|- 
| Microsoft (R) [https://blog.tkjelectronics.dk/2012/12/xbox-360-receiver-added-to-the-usb-host-library/ Xbox 360] (TM) Wireless Receiver for Windows(R) Model 1086 and Controller 
| 0x045e 
| 0x0719, 0x or 0x0291
| 0x0100
| &lt;!--Merge with USB Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;{{No|separate standalone usb dongle detected and shows as 8 vendor interfaces but no class associated and so not working - may need new class from code from xpad or xboxdrv to work the controllor}}
|-
| &lt;!--Description--&gt;Xbox 360 Kinect [http://hackaday.com/2010/11/10/kinect-open-source-driver-demo-and-hacking/ Video] 
[http://git.marcansoft.com/?p=libfreenect.git;a=commit;h=7655fcf7239ba4907654089dba535a196685dbe5 GIT]
| &lt;!--Vendor ID--&gt;0x045E
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;2007  proprietary 2.4GHz RF protocol, 
|- 
| &lt;!--Description--&gt;Xbox One Wired Controller 
| &lt;!--Vendor ID--&gt;0x045E
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{no| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{no| }}
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Xbox One wireless controller newer model with the 3.5mm headphone jack 1537 1697 and microsoft adapter 
| &lt;!--Vendor ID--&gt;0x045E
| &lt;!--Product ID--&gt;0x02d1 or 0x02dd
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{no| }}
| &lt;!--Opinion--&gt;2014 
|- 
| &lt;!--Description--&gt;Microsoft Elite Series 1
| &lt;!--Vendor ID--&gt;0x045E
| &lt;!--Product ID--&gt;0x02e3
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{no| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{no| }}
| &lt;!--Opinion--&gt;2016 ok - 
|-
| &lt;!--Description--&gt;Xbox later models 1708+ Xbox One and Series use 5GHz and use Bluetooth, 
| &lt;!--Vendor ID--&gt;0x045E
| &lt;!--Product ID--&gt;0x02e0
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{no| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{no| }}
| &lt;!--Opinion--&gt;2017 
|- 
| &lt;!--Description--&gt;Xbox One S
| &lt;!--Vendor ID--&gt;0x045E
| &lt;!--Product ID--&gt;0x02ea 0x02fd
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{no| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{no| }}
| &lt;!--Opinion--&gt;2019
|- 
| &lt;!--Description--&gt;Microsoft Elite Series 2 Core 
| &lt;!--Vendor ID--&gt;0x045E
| &lt;!--Product ID--&gt;0x02ff
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{no| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{no| }}
| &lt;!--Opinion--&gt;2022 ok - no hall - 125Hz polling - 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Minisform MGP01 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2024 
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;MOBAPAD N1HD 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2024 has liquid silicone face buttons, hall effect analog, D-Pad swap, two back paddles, USB-A dongle, HD Rumble - 
|- 
| &lt;!--Description--&gt;Mobapad Huben 2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2025 
|- 
| &lt;!--Description--&gt;Mobapad 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;BIGBIG WON Gale 墨将 mòjiāng 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;BIGBIG WON Blitz PRO 2 TMR 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;BIGBIG WON now MOJHON AETHER 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2025 hall effect joysticks, hall effect triggers, mechanical bumpers, 1000hz polling rate, mechanical D-pad, membrane face buttons, mechanical back paddles, rumble, deadzone issues - tri mode 
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;MSI FORCE GC20 GC30 V2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2021 not hall effect 
|- 
| &lt;!--Description--&gt;MSI 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Mytrix Pro 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2024 
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;NACON GC-100XF Controller
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2024 average 
|- 
| &lt;!--Description--&gt;PXN P5 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2024 hall effect joysticks &amp; triggers, limited trigger stops, 1000hz polling rate on wired, 4 back paddles, 32 macro record, anti-deadzone mode, RAW mode, gyro, turbo, tri-mode connection - 
|- 
| &lt;!--Description--&gt;PXN P50L 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;PowerA 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;QRD Stellar T5 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;QRD Junior E5 Mini 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;QRD 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Razer Wolverine V3 Pro 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2024  hall 
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;RetroFlag 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Speedlink XEOX Pro Analog Wireless 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;enclosed lithium battery? - xbox layout - switchable on back of controller to directinput (dinput) or xinput - USB dongle switchable to pc and ps3 
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;SCUF Instinct Pro 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2022 good 
|- 
| &lt;!--Description--&gt;SCUF Envision Pro 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2023 good 
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Steel Series Stratus Duo XL 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;usb adapter needed 
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;[https://inputlabs.io/Inputlabs InputLabs Alpakka Open Source and build yourself] 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;DIY it with 3d printer, pcb and components  - pi pico needed - 2 gyros for better accuracy - 
|- 
| &lt;!--Description--&gt;[https://inputlabs.io/kapybara Inputlabs kapybara] 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;DIY one handed version wip 
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Vilcorn Z03 BT Wireless 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt;2024 - other Bluetooth modes (green, red, blue, purple, etc.) Select + M1 (or M2) - 400mAh - not great latency wired - 800mhz polling -  
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;zd ultimate legend 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;zd 0+ elite 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2024 
|- 
| &lt;!--Description--&gt;zd 0+excellent
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;2024 
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
|}

&lt;pre&gt;
#ifndef AROSX_LIBRARY_H
#define AROSX_LIBRARY_H

#include &lt;exec/types.h&gt;

#define AROSX_CONTROLLER_TYPE_UNKNOWN  0x00
#define AROSX_CONTROLLER_TYPE_GAMEPAD  0x01

#define AROSX_GAMEPAD_DPAD_UP          0x0001
#define AROSX_GAMEPAD_DPAD_DOWN        0x0002
#define AROSX_GAMEPAD_DPAD_LEFT        0x0004
#define AROSX_GAMEPAD_DPAD_RIGHT       0x0008
#define AROSX_GAMEPAD_START            0x0010
#define AROSX_GAMEPAD_BACK             0x0020
#define AROSX_GAMEPAD_LEFT_THUMB       0x0040
#define AROSX_GAMEPAD_RIGHT_THUMB      0x0080
#define AROSX_GAMEPAD_LEFT_SHOULDER    0x0100
#define AROSX_GAMEPAD_RIGHT_SHOULDER   0x0200
#define AROSX_GAMEPAD_A                0x1000
#define AROSX_GAMEPAD_B                0x2000
#define AROSX_GAMEPAD_X                0x4000
#define AROSX_GAMEPAD_Y                0x8000

struct AROSX_GAMEPAD {
    ULONG   Timestamp;
    UWORD   Buttons;
    UBYTE   LeftTrigger;
    UBYTE   RightTrigger;
    WORD    ThumbLX;
    WORD    ThumbLY;
    WORD    ThumbRX;
    WORD    ThumbRY;
};

#define AROSX_EHMB_CONNECT    0x00
#define AROSX_EHMB_DISCONNECT 0x01
#define AROSX_EHMF_CONNECT    (1L&lt;&lt;AROSX_EHMB_CONNECT)
#define AROSX_EHMF_DISCONNECT (1L&lt;&lt;AROSX_EHMB_DISCONNECT)

struct AROSX_EventHook {
    struct Node         eh_Node;
    struct MsgPort     *eh_MsgPort;
    ULONG               eh_MsgMask;
};

struct AROSX_EventNote {
    struct Message      en_Msg;
    ULONG               en_Event;
    APTR                en_Param1;
    APTR                en_Param2;
};

#endif /* AROSX_LIBRARY_H */
&lt;/pre&gt;


=== Joystick ===

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;10%&quot; |Merge with USB on Digital Pad
! width=&quot;10%&quot; |Analogue Hack with Analog Stick
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;CH Products CombatStick 568 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Cyborg X 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Logitech Extreme 3D
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| [Logitech Attack 3 Joystick] 
| 0x0464
| 0xC214
| 0205
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| {{yes|works}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;saitek X-52 x52 pro 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;saitek aviator 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| Speedlink Competition Pro USB 
| 
|
| 
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| {{maybe|works but games not working &quot;out of the box&quot;}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Trust Predator QZ 501
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{yes|works}}
|-
| &lt;!--Description--&gt;Trust Predator TH 400
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{yes|works}}
|-
| &lt;!--Description--&gt;Trust Predator GM-2500 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{yes|works}}
|-
| &lt;!--Description--&gt;Trust XK 100
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
|}

===[https://github.com/JacKeTUs/linux-steering-wheels Gaming Racing Steering Wheels]=== 
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;25%&quot; |Description 
! width=&quot;5%&quot;  |Vendor ID
! width=&quot;5%&quot; |Product ID
! width=&quot;5%&quot; |Revision
! width=&quot;10%&quot; |Merge with USB on Digital Pad
! width=&quot;10%&quot; |Analogue Hack with Analog Stick
! width=&quot;40%&quot; |Opinion
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;  [https://www.usb.org/sites/default/files/documents/pid1_01.pdf USB PID standard not supported], 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Cammus C5 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Fanatec CSL Elite 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;PS4 and Xbox - belt driven wheel - 30cm wheel swapping 
|-
| &lt;!--Description--&gt;Fanatec Club Sport 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt; top belt $600 £500 system 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;FFBeast 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Merge with USB on Digital Pad
| Analogue Hack with Analog Stick
| Opinion
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Genius TRIO RACER F1 Racing Wheel 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;Cheap and cheerful but not great - may need calibrating 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Hama PC Racing Wheel Thunder V18 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;Average 
|-
| &lt;!--Description--&gt;Hori Racing Wheel 3 with pedals 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;PS3 PC 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Logic3 PXU450 TopDrive GT450 Steering Wheel for PS3, PS4, XBox One and PC
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Merge with USB on Digital Pad
| Analogue Hack with Analog Stick
| Opinion
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Logitech MOMO 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;Very good 
|-
| &lt;!--Description--&gt;Logitech Driving Force GT 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Logitech Drive Force Pro DFP 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt; wheel 900 degree - weighs in at 15&amp;nbsp;lbs
|-
| &lt;!--Description--&gt;Logitech Formula Force EX 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;200 degrees turn for the EX model is arcade-like driving - adds PS3 compatibility via the PSx/2 adaptor - weighs in at 9&amp;nbsp;lbs
|-
| &lt;!--Description--&gt;Logitech G25 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;   - needs external psu - 
|-
| &lt;!--Description--&gt;Logitech G27 PC/PS3 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt; comes with gear shifter - needs external psu - 
|-
| &lt;!--Description--&gt;Logitech G29 PC PS3/PS4
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;  may need additional shifter - gear 900deg wheel / rumble - 3 peddle - needs external psu - 
|-
| &lt;!--Description--&gt;Logitech G920 PC XboxOne 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;  may need additional shifter - gear 900deg wheel / rumble - 3 peddle - needs external psu - 
|-
| &lt;!--Description--&gt;Logitech G923 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Microsoft(R) SideWinder Precision Racing Wheel (1999)
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Moza R3
| &lt;!--Vendor ID--&gt;0x346E
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Moza R5
| &lt;!--Vendor ID--&gt;0x346E
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Moza R9
| &lt;!--Vendor ID--&gt;0x346E
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Moza R12
| &lt;!--Vendor ID--&gt;0x346E
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;[https://github.com/Ultrawipf/OpenFFBoard OpenFFBoard], 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;PXN V10 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;PXN V12 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;PXN V12 Lite 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Merge with USB on Digital Pad
| Analogue Hack with Analog Stick
| Opinion
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Simagic M10 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt; base direct drive $900 £800 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Simplicity Simwheel 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt; direct 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Simucube 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Simucube 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Simucube 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Simxperience Accuforce V2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;SPEEDLINK Drift O.Z. Racing Wheel with Pedals and Gear Stick 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;SteelSeries Simraceway SRW-S1 Steering Wheel (PC) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Merge with USB on Digital Pad
| Analogue Hack with Analog Stick
| Opinion
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Thrustmaster Nascar Pro 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Thrustmaster Ferrari Challenge Wheel 
| &lt;!--Vendor ID--&gt;0x044f
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt; Poor  
|-
| &lt;!--Description--&gt;Thrustmaster Ferrari FGT Rumble GT Experience 3-in-1 (PC/PS3)
| &lt;!--Vendor ID--&gt;0x044f
| &lt;!--Product ID--&gt;b658
| &lt;!--Revision--&gt;0102
| &lt;!--Merge with USB Digital Pad--&gt;{{Yes|Wheel and all buttons detected}}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{Maybe|}}
| &lt;!--Opinion--&gt;Not great - gear driven 240deg wheel rotation - no psu needed - 2 peddle - flappy gear change - rumble untested - red switch for PC PS3 selection 
|-
| &lt;!--Description--&gt;Thrustmaster F430 
| &lt;!--Vendor ID--&gt;0x044f
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Thrustmaster T500 RS Wheel 
| &lt;!--Vendor ID--&gt;0x044f
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt; belt driven wheel/rumble for GT5 
|-
| &lt;!--Description--&gt;Thrustmaster T60 Challenge 
| &lt;!--Vendor ID--&gt;0x044f
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Thrustmaster T150 Wheel 
| &lt;!--Vendor ID--&gt;0x044f
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;  gear / belt combo wheel / rumble - 2 peddle 
|-
| &lt;!--Description--&gt;Thrustmaster TMX Pro PC/XboxOne
| &lt;!--Vendor ID--&gt;0x044f
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;{{No| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| &lt;!--Opinion--&gt; direct drive rumble - no manual gear shift included 
|-
| &lt;!--Description--&gt;Thrustmaster T80 
| &lt;!--Vendor ID--&gt;0x044f
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;Base level and OK - PS4 - 270deg rumble - 2 peddle 
|- 
| &lt;!--Description--&gt;Thrustmaster T300 RS GT 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;PS3 PS4 - belt driven - 900deg rotation and modular 28cm wheel out - 2 peddles but 3 available 
|-
| &lt;!--Description--&gt;Thrustmaster TX Leather 
| &lt;!--Vendor ID--&gt;0x044f
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;TX Xbox version - 900deg rotation 
|-
| &lt;!--Description--&gt;Thrustermaster TS PC 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;PC only belt wheel 
|-
| &lt;!--Description--&gt; TS XW Racer PC Xbox1 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt; top belt system 
|-
| &lt;!--Description--&gt;Thrustmaster T-GT 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;PS4 $700 £600 with T-DFB 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Merge with USB on Digital Pad
| Analogue Hack with Analog Stick
| Opinion
|-
| &lt;!--Description--&gt;Tracer Zonda Racing Steering Wheel PC PS3 Vibration Feedback Pedals Gearbox 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
|}


===Gamepad Joypad Adapters===

* Most adapters will work in most OS's without installing a driver. Special functions needing drivers will be noted. 
* Some adapters do not work with some [http://www.stepmania.com/wiki/Dance_Pads dance pads] because of voltage issues. Other adapters map the dancemat arrows as axes and not as buttons, causing problems.
* If using an adapters should be compatible with '''original''' PlayStation PS/Xbox Xbox/GameCube GC /Dreamcast DC/Sega Saturn SS gamepads. 

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;35%&quot; |Description 
! width=&quot;5%&quot;  |Vendor ID
! width=&quot;5%&quot; |Product ID
! width=&quot;5%&quot; |Revision
! width=&quot;10%&quot; |Merge with USB on Digital Pad
! width=&quot;10%&quot; |Analogue Hack with Analog Stick
! width=&quot;30%&quot; |Opinion
|- 
| &lt;!--Description--&gt;[http://www.maplin.co.uk/psx-usb-bridge-34887?tabid=3&amp;worldid=&amp;doy=21m9&amp;faqitem=playstation%20controller%20to%20pc%20adaptor Maplin] [http://www.rockfire.com.tw/ Padix Co. Ltd. Rockfire] PX-205 PSX/USB Bridge 
| &lt;!--Vendor ID--&gt;0x0583 
| &lt;!--Product ID--&gt;0x2050
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{Yes}} but buttons mapped different from others 
| &lt;!--Analogue Hack with Analog Stick--&gt;{{Maybe|poor}}
| &lt;!--Opinion--&gt;Ok with dpads, but very poor support with analogue hack 
|-
| Boom PS Joy Converter adaptor 
| 
| 
| 
| &lt;!--Merge with USB Digital Pad--&gt;{{Yes| }} 
| &lt;!--Analogue Hack with Analog Stick--&gt;
| discontinued (2004/5). Hold Up, Start, and Select for three seconds. Very good [http://www.stepmania.com stepmania] recommendation. 
|-
| [http://www.hkems.com/m_main.htm EMS] [http://www.hkems.com/product/ps2/ps2-usb2.htm USB2] grey plastic box with 2 PSX ports, one on either side - UP and Select pressed for 3 seconds at the same time or the dance code (start+select+up) 
| 
| 
| 
| &lt;!--Merge with USB Digital Pad--&gt;{{Yes|Tests/joystick shows the PS port works in digital mode on d-pad}}
| &lt;!--Analogue Hack with Analog Stick--&gt;
| Set in PC switch mode. Does not work when using 2 pads at the same time, likely higher power requirements. FPSE emu DualShock untested, Mat and Guitar untested but known lag involved 
|-
| Joytech (play.com) (EMS USB2 bad clone) Black box twin PSX
| 0x0b43
| 0x0003
| 0x0
| &lt;!--Merge with USB Digital Pad--&gt;{{Maybe| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No|buggy hardware}} 
| but poor on dance ddr mat and guitar hero as the left and right keys do not like being pressed together, Dual shock untested 
|-
| [ EMS Trio Linker ] 1 PSone connection at bottom
| 
| 
| 
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| 1PSX discontinued 2005 
|-
| [http://psxemulator.proboards.com/index.cgi?board=support&amp;action=display&amp;thread=421 EMS Trio Linker Plus] (blue box) 1 PSx at bottom
| 
| 
| 
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| 1PSX discontinued 
|-
| Gamtec [http://www.gamestone.co.uk/gradius/guides_usb_smartjoy_guide.php SmartJoy Plus] Lik Sang PS-&gt;USB converter Red 2005 
| 0x0925
| 0x0005
| Low 0110
| &lt;!--Merge with USB Digital Pad--&gt;{{Maybe|detected and digital dpad works with [http://aros-exec.org/modules/newbb/viewtopic.php?topic_id=4138&amp;forum=2&amp;post_id=35952#forumpost35952 joystick and testjoystick tests] but  the second analog control is not mapping correctly in digital mode}} 
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No|Analogue Hack - hardware buggy not useable}} 
| Dual shock untested, Mat and Guitar untested. Nothing picked up upon plugging it in. Quite common, these items have grounding issues or feed voltage back into the USB host and freeze the host controller, preventing any plugins or removals being detected. 
|-
| Gamtec SmartJoy Plus Dual PS-&gt;USB converter Red 
| 0x0925
| 0x00
| Low 
| &lt;!--Merge with USB Digital Pad--&gt;{{Maybe| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No|buggy hardware}}
| 
|-
| [http://uk.gear.ign.com/articles/700/700334p1.html Lik-Sang Super SmartJoy PSX] 
| 
| 
| 
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| 1PSX 
|-
| Soyo Kiki Kiky 
| 
| 
| 
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| 
|-
| eXcel PSX adaptor shaped a little like a stealth bomber with USB pass through 
| 
| 
| 
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| 
|-
| Venom 
| 
| 
| 
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| 
|-
| Dragon Plus (Radio Shack) Pantherlord GreenAsia USB to PS2/PS3 converter single black cable
| 0x0e8f
| 0x03
| 1.07
| &lt;!--Merge with USB Digital Pad--&gt;{{Yes| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{Yes| }}
| 
|-
| Deal Extreme 2 PSX black cables from 1 USB port
| 
| 
| 
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| {{N/A|untested }}
|- 
| &lt;!--Description--&gt;HDE 2014 Personal Communication Systems Inc 
| &lt;!--Vendor ID--&gt;0x0810
| &lt;!--Product ID--&gt;0x0001
| &lt;!--Revision--&gt;0106
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Same as single cable above but with black block midway along cable 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
|- 
| &lt;!--Description--&gt;TigerGame Ltd Mayflash PC001 Super Joy Box 3 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| TigerGame Ltd Mayflash PC016 Super Joy Box arrowhead triangle twin PSX] Original was lack with RED Leds. Clones Dilong pu203, Blue HDE Neewer ShineData SD-APS2USB, Red Octane and Black PC Power Box (NS3454) '''embossed circle''' on top 
| 0x0810
| 0x0001
| 1.06
| &lt;!--Merge with USB Digital Pad--&gt;{{Yes|Tests/joystick shows one PS port does not work with analog control at all but the other port does and maps correctly in digital mode}} 
| &lt;!--Analogue Hack with Analog Stick--&gt;{{Yes|Analogue hack works }}
| Still available 2013, poor construction though, falls to pieces easily. Dual Shock untested, Mat and Guitar untested 
|-
| &lt;!--Description--&gt;TigerGame Ltd [http://www.mayflash.com/pc/pc038/pc038-1.htm Mayflash PC038 Super Joy Box Pro triangle twin PSX] 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| TigerGame Limited Mayflash SuperJoy Box 5 PC006 long V-shaped 4 port PS/PS2 Game Controller Adapter  
| 
| 
| 
| &lt;!--Merge with USB Digital Pad--&gt;{{Yes| }} 
| &lt;!--Analogue Hack with Analog Stick--&gt;
| 
|- 
| &lt;!--Description--&gt;TigerGame Limited Mayflash SuperJoy Box 5 PRO PC039 PS/PS2 Game Controller Adapter
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Merge with USB on Digital Pad
| Analogue Hack with Analog Stick
| Opinion 
|- 
| Boom PSX+N64 USB converter (purple or blue see through box) (2003/4) - red led for psx and green led for n64
| 0x6666
| 0x0667
| 0x0
| &lt;!--Merge with USB Digital Pad--&gt;{{No|not detected by Tests/joystick}}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No|Analogue hack }}
| Rumble Pak untested
|-
| [http://www.hkems.com/product/ps2/TrioLinkerPlus2.htm EMS Trio Linker Plus II] 
| 
| 
| 
| &lt;!--Merge with USB Digital Pad--&gt;{{Yes| }} [http://aros-exec.org/modules/newbb/viewtopic.php?topic_id=4753&amp;forum=24&amp;post_id=43102#forumpost43102 ]
| &lt;!--Analogue Hack with Analog Stick--&gt;
| 1DC 1GC 1PSX but not for ddr mat games 
|-
| TigerGame Mayflash PC043 clone HuiJia Black twin N64 converter for PC USB 
| 0x0e8f
| 0x3013
| 0x0
| &lt;!--Merge with USB Digital Pad--&gt;{{No|detected by Tests/joystick though two digital pads have their settings wrong}} 
| &lt;!--Analogue Hack with Analog Stick--&gt;{{Yes|Analogue hack works well with middle handle/grip little joystick}}
| Rumble Pack untested 
|-
| TigerGame Mayflash PC MagicBox SuperBox 3 
| 
| 
| 
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| untested 1SS 1DC 1PSX }
|-
| &lt;!--Description--&gt;Lik Sang SmartJoy X 
| &lt;!--Vendor ID--&gt;0x045e
| &lt;!--Product ID--&gt;0x0285
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;SmartJoy X2 
| &lt;!--Vendor ID--&gt;0x045e
| &lt;!--Product ID--&gt;0x0289
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|-
| TigerGame Mayflash PC018 Super Joy Box 9 Xbox (NOT 360) 
| 0x05e3
| 0x060
| 
| &lt;!--Merge with USB Digital Pad--&gt;{{No|shows up as a Genesys Logic Hub}}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| does not work. Hub(s) 0x0288 detected but 0x0289 xbox1 joypads are not detected as hid let alone as [http://www.amiga.org/forums/archive/index.php/t-62940.html xpad] or [http://pingus.seul.org/~grumbel/xboxdrv/ linux xboxdrv driver] 
|-
| TigerGame Mayflash PC019 Super Joy Box 10 Xbox Twin ports (NOT 360) 
| 0x05e3
| 0x060
| 
| &lt;!--Merge with USB Digital Pad--&gt;{{No|shows up as a Genesys Logic Hub}}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| does not work with the big Fatty Duke or smaller S Akebono controller(s) 
|-
| TigerGame Ltd Mayflash PC020 Super Joy Box 11 Xbox Quad ports (NOT 360) 
| 0x05e3
| 0x0604
| 
| &lt;!--Merge with USB Digital Pad--&gt;{{No|shows up as a Genesys Logic Hub}}
| &lt;!--Analogue Hack with Analog Stick--&gt;{{No| }}
| 
|- 
| &lt;!--Description--&gt;TigerGame Ltd Mayflash PC035 3 in 1 Magic Joy box PS GC Xbox 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;USB to NES [http://wiki.nesdev.com/w/index.php/Standard_controller SPI like protocol] 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Buffalo Classic USB Pad SNES like 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{Yes| }} 
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Mayflash PC044 USB to SNES 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;USB to MEGADRIVE GENESIS Joypad 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;[http://www.retrousb.com/product_info.php?cPath=21&amp;products_id=70 USB to 9 pin ATARI RETROPORT style JOYSTICK PORT] 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;{{Yes| }} 
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Atari RetroLink 9pin to SB 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;SLS Sega Saturn USB pad 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB on Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Mayflash PC050 Dual Saturn ports 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Guitar Hero for PC/Mac 
| &lt;!--Vendor ID--&gt;0x1430
| &lt;!--Product ID--&gt;0x474C
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;{{Yes| }}
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Cronus Max 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;BrookX One 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Mayflash Gamecube to USB 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;Mayflash Magic NS 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt; WiiU 
|- 
| &lt;!--Description--&gt;Brook Converter WiiU P3 P4 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt;CooV Xbox One Converter 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Merge with USB Digital Pad--&gt;
| &lt;!--Analogue Hack with Analog Stick--&gt;
| &lt;!--Opinion--&gt;
|-
|}


* [http://www.bemanistyle.com/forum/f6/best-metal-pad-19066/ Metal dance pads with LEDs] - My My Box Blue Shark (Nexen), Cobalt Flux (CF) (Let's Groove), Red Octane Afterburner, TX-2000, Logic3 (Dance Dance Dance), Gamerose (Stay Cool), 
* Hard foam mat - [http://www.mayflash.eu/3in1-deluxe-dansmat-ignition-foam-ps2xboxpc-p-5.html Mayflash] FutureMax Deluxe 3 in 1 Ignition, [http://www.gamerose.com/ Gamerose] (Stay Cool), TrinPad orange, 
* Soft foam mat - Logic3 (PS420N), [http://www.positivegaming.com/index.php?id=36 Positive Gaming Impact],  Gamerose Miss Daisys Naki (Stay Cool), Pelican, MadCatz

*PS1 PS2 PS3 PS4 flex ribbon big source of button/trigger issues with all controllers 
*PS2 Phat KSA1Q40A (Board), SA1Q33A (Membrane) SCHP-10010 H 
*PS2 SA1Q42A SCHP-10010 A 
*PS2 SA1Q43-A SCHP-10010 H


The primary axes are either the Control Pad or the left stick. Buttons come in a rough order: face buttons, then shoulder buttons, then Select and Start, then buttons under sticks, and finally Control Pad directions if not assigned to a hat. But the order and number of buttons within a category are unpredictable, as is which button the user expects to use for each action.

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot; | Joypad 
! width=&quot;5%&quot; | HATS 
! width=&quot;5%&quot; | Button 01
! width=&quot;5%&quot; | Button 02
! width=&quot;5%&quot; | Button 03
! width=&quot;5%&quot; | Button 04
! width=&quot;5%&quot; | Button 05
! width=&quot;5%&quot; | Button 06
! width=&quot;5%&quot; | Button 07
! width=&quot;5%&quot; | Button 08
! width=&quot;5%&quot; | Button 09
! width=&quot;5%&quot; | Button 10
! width=&quot;5%&quot; | Button 11
! width=&quot;5%&quot; | Button 12
! width=&quot;5%&quot; | Button 13
! width=&quot;5%&quot; | Button 14
! width=&quot;5%&quot; | Axes 1 
! width=&quot;5%&quot; | Axes 2 
! width=&quot;5%&quot; | Axes 3 
! width=&quot;5%&quot; | Axes 4 
! width=&quot;5%&quot; | Axes 5 
! width=&quot;5%&quot; | Axes 6 
! width=&quot;10%&quot; | Comment 
|-
| [https://pineight.com/mw/index.php?title=USB_game_controllers Xbox 360 Wired Controller]
| 
| A (down-green) 
| B (right-red) 
| X (left-blue) 
| Y (up-yellow) 
| LB (white) 
| RB (black) 
| Back
| Start
| Guide 
| L3
| R3
| 
| 
| 
| Left X 
| Left Y
| LT
| Right X
| Right Y 
| RT 
| Poor 2D, Good 3D 
|- 
| &lt;!--Description--&gt;Gravis GamePad / Original PlayStation Controller 
| &lt;!--HATS DPAD--&gt; 
| &lt;!--Button 01--&gt;Red (Sqleft)
| Yellow X (X down)
| Green O (O right)
| Blue (Tri up)
| L1
| R1
| L2
| R2
| Select
| &lt;!--Button 10--&gt;Start
| 
| 
| 
| 
| &lt;!--Axes 1--&gt;Stick X
| Stick Y
| 
| 
|  
|  
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt; PlayStation 2 Older Adapters 
| &lt;!--HATS DPAD--&gt; 
| &lt;!--Button 01--&gt;Blue X (down) 
| Red O (right) 
| Pink Sq (left) 
| Green Tri (up) 
| L1
| R1
| L2
| R2
| Select
| &lt;!--Button 10--&gt;Start 
| Stick 1
| Stick 2
| 
| 
| &lt;!--Axes 1--&gt;
| 
| 
| 
|  
|  
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt; PlayStation 2 Newer Adapters 
| &lt;!--HATS DPAD--&gt; 
| &lt;!--Button 01--&gt;Up
| Right
| Down
| Left
| L2
| R2
| L1
| R1
| Select
| &lt;!--Button 10--&gt;Start
| Stick 1 (analogue Hack) 
| Stick 2 
| 
| 
| &lt;!--Axes 1--&gt;
| 
| 
| 
|  
|  
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt; Wish Technologies N64 Adaptoid 
| &lt;!--HATS DPAD--&gt; 
| &lt;!--Button 01--&gt; A
| C Down
| C Right
| B
| C Left
| C Up
| L
| R
| Start
| &lt;!--Button 10--&gt;Z
| Pad Up
| Pad Down 
| Pad Left
| Pad Right 
| &lt;!--Axes 1--&gt;Stick X
| Stick Y 
| 
| 
|  
|  
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt; 
| &lt;!--HATS DPAD--&gt; 
| &lt;!--Button 01--&gt;
| 
| 
| 
| 
| 
| 
| 
| 
| &lt;!--Button 10--&gt;
| 
| 
| 
| 
| &lt;!--Axes 1--&gt;
| 
| 
| 
|  
|  
| &lt;!--Opinion--&gt;
|- 
| &lt;!--Description--&gt; 
| &lt;!--HATS DPAD--&gt; 
| &lt;!--Button 01--&gt;
| 
| 
| 
| 
| 
| 
| 
| 
| &lt;!--Button 10--&gt;
| 
| 
| 
| 
| &lt;!--Axes 1--&gt;
| 
| 
| 
|  
|  
| &lt;!--Opinion--&gt;
|- 
|}

Just plug in your digital/analogue joystick or gamepad into USB port. The device will be handled by Poseidon USB stack. Poseidon is the USB stack with Trident adding a GUI (graphical user interface) prefs. 


the context sensitive page would come up right on pressing the help key inside the relevant window. The manual is in this archive, just in case it isn't in SYS:Locale/Help  


*How to change joystick mode to analogue?

By default a connected USB joystick emulates Amiga digital joystick. To change this behaviour so that the joystick is presented as analogue you need to use Trident preferences application (System:Prefs/Trident).

Open Trident and go to Devices on the left hand side (mouse click once on it). Select your controller from the list to the right and then click on Settings button below. This will open a new window. On the &quot;General&quot; tab find the &quot;Lowlevel Library Joypad Emulation&quot; section near the bottom. Find ports which are set to &quot;Merge with USB&quot; or &quot;Override with USB&quot; and change them to &quot;Analogue Hack&quot;. 

Please note that analogue joystick support is an extension of original Amiga functionality, thus an Amiga application must be explicitly written to use it. AROS SDL library uses this functionality, thus all SDL applications that use joystick, can use the analogue joystick feature.

The HID class has several options how to handle the input data: 

* Don't touch: The movement and button data for is not modified by the hid class. This is the default for the ports 0, 2, and 3. 

* Overwrite with USB: This will kill the  original  data  that  might  had  come  from  the internal  ports  and  overwrites it with the joypad data for this USB interface. Note well: If you have multiple  joypads  connected,  take care  which setting you have selected for each port, because only the last interface with this option will actually send the joypad data to the game. 

* Merge with USB: This option merges the input data of the  lowlevel.library  with  the USB  stream. This only works, if the connected device on the original Amiga  ports  is  NOT  a  mouse  (because  then   the   streams   are incompatible).  Merging  should  be  the preferred method, because it leaves the original joysticks working. 

* Disable: Turns off the port for the application.

* Analogue Hack: Tells Poseidon to force reporting  of  analogue  data  at  the  port. Please  note  that  this only works with programs that understand the analogue  data,  because  it's   an   extension   to   the   original lowlevel.library   standard   made  by  Commodore.  If  you  want  to incorporate this feature in your software, just contact me and I will send you the necessary information. 

* Rumble Port: As addition to the analogue data, the HID class  supports  applications and  games  that want to utilize a rumble pack or force feedback motors in the gamepads. This field selects to  which  lowlevel  port  the  hid device responds, when attempting to use the rumble pack. Normally, this corresponds to the port that has  been  set  in  the  actions  for  the joypad.


*How to change joystick port assignment?

The low  level  library  supports up to four ports. Port 0 is usually used by the mouse, port 1 is the standard port for joysticks/joypads. By default a connected USB joystick is present in Port 1. To change its location to Port 0 you need to use Trident preferences. 

Open Trident and go to Devices window. Select your controller from the list and then click on Settings button. This will open a new window. On the &quot;General&quot; tab find the &quot;Lowlevel Library Joypad Emulation&quot; section. Port 1 should be set as either &quot;Merge with USB&quot; or &quot;Override with USB&quot;. Change this setting to &quot;Don't touch&quot;. Change Port 0 setting to &quot;Merge with USB&quot;.

Go to &quot;Actions&quot; tab. In the &quot;Reports and collection&quot; select first entry named &quot;Joystick&quot;. in the &quot;Usage items&quot; select &quot;X axis&quot;. Go to &quot;Performed actions&quot; area. On the left there will be a list of triggers. Each of them should have (port1) in their params. Click on the first trigger and using buttons to the right of the list change port1 into port 0. Repeat this for all triggers and for all items on &quot;Usage items&quot; list.


*How to make joystick simulate keyboard keys?

With Poseidon it is possible to make the joystick simulate the keyboard pressings. This might enable using joystick for playing games which only have keyboard support. This feature is configured in Trident preferences.

Open Trident and go to Devices window. Select your controller from the list and then click on Settings button. This will open a new window. Go to &quot;Actions&quot; tab. On the right top window select X axis. On the left bottom list select an entry &quot;Digital Joystick, Push left(port 1)&quot;. On the panel to the right change &quot;Digital joystick&quot; into &quot;Raw Key&quot;. A list of keys will be displayed. Select key you wish to send. Repeat the same procedure for &quot;Digital Joystick, Release left (port 1)&quot; option but this time check &quot;Send key up even instead of key down&quot;. Open shell and move your joystick to the left - your selected letter should appear in the shell. 


*Analogue in Trident Prefs
* Open the Trident USB Prefs -&gt; Devices -&gt; Select your joypad -&gt; Settings button -&gt; Action TAB 
* See some &quot;axis&quot; listed under &quot;Usage items&quot; in the top right of the window. They are your analog stick(s) 
* Check [x] Track Incoming Events which is half way down the window on the left 
And you should see some axis activity in &quot;Usage items&quot; when you move the analog stick 


*Actions

HID class item -&gt; Settings -&gt; HID Class Window -&gt; Action Tab -&gt; Action handling area 

Reports and collections -&gt; Usage Items -&gt; Performed actions 


Qualifier keys are *special*. You don't only need to create the actual keypress but also modify the qualifiers.
Go to the keyboard panel and find the windows menu key by enabling key tracking and pressing the windows menu key. Then assign the right amiga key to it.

Go to the actions panel and find the right amiga key (it's called &quot;Keyboard right GUI&quot;). Remember the actions stored there, best write them down in exact order. Then delete them.
Find the windows menu item and add the missing qualifier action. Be sure the parameters are exactly the same and the order is right.

Set them to Raw, then assign an up and down button for each character, etc.
when you change the settings to RAW so you can assign keyboard strokes. it will always say, KEYDOWN or what ever on the left, it never provides and option for key release.

The problem still remains though that if I try to assign the Directional Pad (Hat) to Arrow Keys, that things will get screwed up and you either can not move with the directional PAD (HAT), or movements are assigned to the Left Analog, and do not work as they should, it's as if the right and down arrow keys are ALWAYS On, regardless of the fact that I did indeed assign a Key release command to each input.

check that by pressing analog directions and see the current values, and the thresholds configured in poseidon to bind them to left/right/up/down.

misconfigured too much stuff in the HID settings, you can always go in poseidon-&gt;config list entry and delete the config item related to your device (or the HID class setting itself), back to basics.


*Rumble in Trident Prefs
Open Trident Prefs and click on the Devices option in the left hand window. Click with the mouse once on your gamepad choice on the right hand side and again on the Settings button below. In the new window, select the '''General''' TAB and half way down on the right there is an &quot;Open Now&quot; button in the section &quot;HID output control window&quot;. Clicking on that button opens another window (HID Control) with sliders for the two rumble engines inside the controllers and you can test if they work. '''Sometimes clicking that button does nothing, other times it will open the window and say nothing is detected.''' The leftmost two sliders do nothing, the third one has a large rumble effect, and the fourth one has a small rumble effect.

===Graphic Drawing Tablet===

There is a standard in HID for tablets possibly mouse type. If the tablet is HID conforming in that sense, it should work. Aiptek does a fairly good job at this. The other competitor, Wacom, didn't pay too much attention to this and simply adapted their legacy serial protocol into HID in a very awkward way. Older Wacom tablets have worked with the special support in the HID class, but not the more recent ones. 

 to use graphic tablets fully, applications need to be written that make use of the AmigaOS NewTablet events (which AROS has) 


* Entry level - A6 (6x4) work area 
* Medium A5 (6x8) A4 (10x7) size   (recommended but only a few ie years 2000 to 2003 models supported) 
* Semi Pro A3 (12x9) 
* Pro  Cintiq


* 2005/6 Some support added for Wacom tablets  
* 2008 Wacom's patent on battery free pens expires


{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;Micrograf Tabby (late 1980s and early 1990s) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|Serial RS232 based }}
|-
| &lt;!--Description--&gt;podscat pt 3030 graphics tablet
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|Serial RS232 based }}
|-
| &lt;!--Description--&gt;Summagraphics 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|Serial RS232 based }}
|-
| &lt;!--Description--&gt;Wacom IV compatible (Graphire, ArtPad, A3, A4, A5 and PenPartner CT-0405-P - Wacom intuos GD-0405-R) Waycom Digitiser II UD-0608-R
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|Serial RS232 based }}
|-
| &lt;!--Description--&gt;Wacom Artpad II (KT-0405-R) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|Serial RS232 based }}
|-
| &lt;!--Description--&gt;AceCad boards 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|Serial RS232 based }}
|-
| &lt;!--Description--&gt;AipTek HyperPen 6000 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|Serial RS232 based }}
|-
| &lt;!--Description--&gt;Calcomp 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|Serial RS232 based }}
|-
| &lt;!--Description--&gt;AipTek HyperPen 8000 - Aldi/Medion MD 9310 and Aldi/Tevion LT 9310 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|Serial RS232 based }}
|-
| &lt;!--Description--&gt;Tablet PC penabled 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|Serial RS232 based like x61t X60t NC4200 NC4400 }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|Serial RS232 based }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Opinion 
|-
| &lt;!--Description--&gt;
* Wacom PenPartner
* PenPartner 2
* PenStation 2
| &lt;!--Vendor ID--&gt;0x056a
| &lt;!--Product ID--&gt;0x0000
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Wacom Graphire - Wacom Tablet ET-0405-U UV1.1-1 (Slate Blue)  ET-0405UL (lime)  (orange)  (red)  (purple) 
| &lt;!--Vendor ID--&gt;0x056A
| &lt;!--Product ID--&gt;0X0010
| &lt;!--Revision--&gt;0100
| &lt;!--Opinion--&gt;{{Yes|late 90s with A6 size - [Wacom Support] of X-axis 00000-10205  Y-AXIS 0000-7421 Tip Pressure 000-511 under Trident prefs. Air pen mouse type movements }}
|-
| &lt;!--Description--&gt;
* Grapphire 2 4x5  ET-0405A-U UV2.0-3 (Steel Blue) 
* Graphire 2 5x7 ET-0507A 
| &lt;!--Vendor ID--&gt;0x056A
| &lt;!--Product ID--&gt;0x0011 and 0x0012
| &lt;!--Revision--&gt;0110
| &lt;!--Opinion--&gt;{{Yes|A6 and A5 versions - [Wacom Support] of X-axis 00000-10205  Y-AXIS 0000-7421 Tip Pressure 000-511. Air pen mouse type movements - mouse EC-120-0K tested}}
|-
| &lt;!--Description--&gt;Wacom Graphire 3
* cte-430/w 4x5 pearl   sapphire 
* cte 630 6x8 
| &lt;!--Vendor ID--&gt;0x056A
| &lt;!--Product ID--&gt;0x0013 and 0x0014 
| &lt;!--Revision--&gt;0314
| &lt;!--Opinion--&gt;{{Yes|A6 and A5 size - [Wacom Support] Xaxis 0-10207 yaxis 0-7423 tip pressure 0-511 and the erase end appears to respond but avoid bluetooth BT versions }}
|-
| Wacom Graphire 4 
* cte-440/B Blue cte 440/s Silver 4x5
* cte-640 6x8 cte 640 u 0403 
| &lt;!--Vendor ID--&gt;0x056A
| &lt;!--Product ID--&gt;0x0015 and 0x0016 
| &lt;!--Revision--&gt;403
| {{Yes|A6 and A5 work area detected [Wacom Support] x-axis 0000-10207 Y axis 0000-7423 Tip Pressure 000-511 and delete rub out end of the pencil seems detected but avoid bluetooth BT versions }}
|-
| &lt;!--Description--&gt;
* Wacom Intuos 4x5 GD-0405 
* Intuos 6x8    GD-0608
* Intuos 9x12    GD-0912
* Intuos 12x12  GD-1212-U 
* Intuos 12x18 GD-1218
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;0x0020 0x0021 0x0022 0x0023 0x0024 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{Yes|detected and responses delivered back - x axis up to 30479 and y axis 31679, tip pressure up to 1023 and x and y tilt up to 127 - Wacom intuos GD-0912-A for Apple Macs NOT SUPPORTED}}
|-
| &lt;!--Description--&gt;
* Intuos 2 4x5 A6 - XD-0405-U 
* Intuos 2 6x8 A5 - xd 0608u uoc
* Intuos 2 9x12 XD-0912-U
* Intuos 2 12x12 XD-1212-U
* Intuos 2 12x18 XD-1218-U
| &lt;!--Vendor ID--&gt;0x056a
| &lt;!--Product ID--&gt;0x0041 0x0042 0x0043 0x0044 0x0045 
| &lt;!--Revision--&gt;0126
| &lt;!--Opinion--&gt;{{No|various sizes and recognised as [Wacom Support] but not working. x-axis 00000-20319 y-axis 00000-16239 tip presure 0000-1023 x-tilt y-tilt 000-127.  HID mouse xc-100-03 works but never could use it as a real tablet with pressure with TVPaint 3.6 }}
|-
| &lt;!--Description--&gt;
* Intuos 3 4x5 (PTZ-430) 
* Intuos 3 4x6   (PTZ-431W ) 
* Intuos 3 6x8   (PTZ-630 PTZ630) 
* Intuos 3 6x11 (PTZ-631W A3 wide)  
* Intuos 3 9x12 (A4 PTZ-930 PTZ930)  
* Intuos 3 
| &lt;!--Vendor ID--&gt;056a
| &lt;!--Product ID--&gt;0x00b0 0x00b1 0x00b2 0x00b3 0x00b4 0x00b5
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No}} Actions in HID setup window definitively locks the Pointer (mouse) reports settings and even after a clear and save, nothing changes, the configuration returns to default values.  &quot;[Wacom]&quot; reports don't see any events from the tablet, even with &quot;Pointer&quot; reports cleared and save, so is locked a in &quot;mouse&quot; state - but can send a special command to the tablet in order to put it into a special vendor mode. This mode enables Wacom specificities like pressure, tilt, absolute position, buttons, etc... you should send an HID report feature with ReportID=2 and data=2, the current HID class driver doesn't give a way to change that, even using the &quot;initial startup actions&quot; item in the extra collection. No listed features work 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| Wacom Volito - Promethean FT-0405-U06 UV1.4-1 
| &lt;!--Vendor ID--&gt;0x056A
| &lt;!--Product ID--&gt;0x0060
| &lt;!--Revision--&gt;0141
| &lt;!--Opinion--&gt;{{Yes|A6 work area with [Wacom Support] of x-axis 0000-5103 Y axis 0000-3711 Tip Pressure 000-511. Air and touch mouse movement - appears to be the budget option with some but limited features}}
|-
| &lt;!--Description--&gt;Wacom Volito 2 
* CTF-??? 2x3 
* CTF-420G CTF-420 V2.0-0 4x5
* Serif Penabled 6742 rebadge of CTF 420/020-B CTF-420/02
| &lt;!--Vendor ID--&gt;0x056A
| &lt;!--Product ID--&gt;0x0062
| &lt;!--Revision--&gt;0200
| &lt;!--Opinion--&gt;{{Yes|A6 work area with [Wacom Support] of x-axis 0000-5103 Y axis 0000-3711 Tip Pressure 000-511. Air and touch mouse movement - no erase function on the end of the pen - nylon nibs value option}}
|-
| &lt;!--Description--&gt;
* Wacom PL-400 LCD 
* PL-500
* PL-510
* PL-550
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;0x0030 0x0031 0x0032 0x0034 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
* PL-600
* PL-600 SX
* PL-700
* PL-710
* PL-800
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;0x0033 0x0035 0x0036 0x0037 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Wacom Cintiq 21 UX and Cintiq Partner DTF-720
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Opinion 
|-
| &lt;!--Description--&gt;Wacom PenTablet Bamboo (MTE), Bamboo Craft (CTH), Bamboo Fun (CTE), Bamboo Pen (CTL) and Bamboo Pen &amp; Touch (CTH) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| Wacom Bamboo Fun Medium CTE-650 
| 
| 0x0018 
| 
| {{Maybe|[http://www.a1k.org/forum/showthread.php?t=11432 works on a1k forum]}}
|-
| &lt;!--Description--&gt;Bamboo Fun Small CTE-450 white 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;0x0017 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Wacom Bamboo One CTF-430 V2.0-0 CTF 430/S
| &lt;!--Vendor ID--&gt;0x056A
| &lt;!--Product ID--&gt;0x0069
| &lt;!--Revision--&gt;0200
| &lt;!--Opinion--&gt;{{Maybe|A5 wired air pen and acts like a mouse only}}
|-
| &lt;!--Description--&gt;Wacom Intuos 4 
* Small PTK-440 PTK-540
* Medium - PTK-640 - PTK 540WL Wireless - 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested  Intuos4 surface sheet was revised in October 2010 to reduce nib wear}}
|-
| &lt;!--Description--&gt;Wacom Intuos 5 Touch 
*
* Medium - PTH-650 - USB Wired and Wireless Kit 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;0x0027 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested work, however wireless may glitch or drag }}
|-
| &lt;!--Description--&gt;Wacom Intuos Pro Medium - PTH-651 - 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Bamboo Small Pen Tablet - MTE 450 MTE-450A (MTE-450/k) - 
| &lt;!--Vendor ID--&gt;0x056A
| &lt;!--Product ID--&gt;0x0065
| &lt;!--Revision--&gt;0116
| &lt;!--Opinion--&gt;{{Maybe|A6 work area - mouse movement but no pen detection except x-axis 2 to -2 and y-axis 2 to -2 - mini usb lead - 4 blue led lit buttons not detected as well as circular touch button??  }}
|-
| &lt;!--Description--&gt;Bamboo Pen CTL 460
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested all Bamboo versions were criticized for the drawing surface's roughness (which got smoother over time), which caused the small pressure-sensitive 'nib' to wear down, and become slanted or scratchy in the same way as pencil lead, albeit more slowly}}
|-
| &lt;!--Description--&gt;Wacom Bamboo Fun CTH-461/S wired 
| &lt;!--Vendor ID--&gt;0x056A
| &lt;!--Product ID--&gt;0x00D2
| &lt;!--Revision--&gt;0106
| &lt;!--Opinion--&gt;{{Maybe|A6 size - Pen tracking not working but finger touch works }}
|-
| &lt;!--Description--&gt;Wacom Bamboo Connect Pen Tablet CTL-470 CTL-470K 470-DE 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;CTH 470K
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Wacom CTH 480/S wireless 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }} lithium battery for pad - 
|-
| &lt;!--Description--&gt;Wacom Intuos Pen Small CTL-480/S CTL 480 K wired 
| &lt;!--Vendor ID--&gt;0x056A
| &lt;!--Product ID--&gt;0x030E
| &lt;!--Revision--&gt;0200
| &lt;!--Opinion--&gt;{{No|A5 detected as Intuos PS  but not working although the RHS blue led responds to pen on tablet }}
|-
| &lt;!--Description--&gt;CTH 490 PK S Photo - CTH-490CK-S Comic - CTH-490AK-S Art 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested lower hovering height pen nibs wear fast and input lag/responsiveness}}
|-
| &lt;!--Description--&gt;Intuos Pen &amp; Touch Medium - CTH-680 - USB Wired and Wireless Kit work 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Wacom Intuos Pro (PTH-660 and PTH-860) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Opinion 
|-
| &lt;!--Description--&gt;Waltop Media Tablet 10.6&quot;
    Genius G-Pen M609
    Genius G-Pen M609X
    iVista Media Tablet 10.6
    Aiptek MediaTablet 10000u

| &lt;!--Vendor ID--&gt;172f:0501
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Slim Tablet 12.1&quot;
| &lt;!--Vendor ID--&gt;0x172F
| &lt;!--Product ID--&gt;0x0034
| &lt;!--Revision--&gt;0x1105
| &lt;!--Opinion--&gt;{{yes|works}}
|-
| &lt;!--Description--&gt;Waltop Media Tablet 12 by 9&quot; 
    Aiptek HyperPen 12000u T-12000U Tablet Series 
    Nisis T-12000u USB Tablet Series Version 1.05 (aiptek rebadged)

    Trust item #1535
    ADESSO Cyber Tablet 12000 Graphic design tablet
    iVista Media Tablet 12
    PENTAGRAM O'pen Wide P 2003
    Genius G-Pen M712
| &lt;!--Vendor ID--&gt;172f:0500, 0x08ca
| &lt;!--Product ID--&gt;0x0010
| &lt;!--Revision--&gt;0105
| &lt;!--Opinion--&gt;{{Yes|detected with Nisis/Aiptek functioning as a tablet, untested with others  - Puck (mouse) x axis 0000 to 6000 y axis 0000 to 6000 - stylus (pen) x axis 00000 to 12000 y axis 00000 to 12000 tip pressure 0000 to 1023 - 16 function keys - AAA battery needed for pen and another for the mouse}}
|-
| &lt;!--Description--&gt;Waltop Media Tablet 14.1&quot; v5.1e
    Genius G-Pen M714X
    Aiptek MediaTablet 14000u WMK-H141 
    Trust item #15358
    Adesso CyberTablet 14000 M14
    iVista Media Tablet 14.1
    PENTAGRAM O'pen Wide P 2004

| &lt;!--Vendor ID--&gt;0X172f
| &lt;!--Product ID--&gt;0X0500
| &lt;!--Revision--&gt;0114
| &lt;!--Opinion--&gt;{{Yes|detected with Nisis/Aiptek functioning as a tablet - Stylus (Pen) X 16838 Y 16838 Tip Pressure 1023 }}
|-
| &lt;!--Description--&gt;Waltop PID 0038
    Genius G-Pen F509
    Manhattan 177405

| &lt;!--Vendor ID--&gt;172f:0038
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Waltop PID 0052
    Yiynova MSP19

| &lt;!--Vendor ID--&gt;172f:0052
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Waltop Q Pad
    Aiptek HyperPen Mini
    NGS Flexi Style
    VisTablet PenPad
    iVistaTablet Q Flex Pad
    Bravod Q-PD65-S
    Trust Flex Design Tablet (#16937)

| &lt;!--Vendor ID--&gt;172f:0037
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Waltop Sirius Battery Free Tablet
    VisTablet Muse
    PENTAGRAM Designer P 2700
    Princeton PTB-S1BK

| &lt;!--Vendor ID--&gt;172f:0502
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Waltop Slim Tablet 12.1&quot;
    Genius G-Pen F610
    Trust Slimline Widescreen Tablet (#16529)
    VisTablet Original 12&quot;
    Adesso CyberTablet Z12
    Adesso CT-Z12A
    PenPower Tooya Pro
    Aiptek Slim 12.1 Inch
    Aiptek SlimTablet 600u Premium II
    NGS Slim Proguess
    iVistaTablet Slim 12.1
    PENTAGRAM ThinType P 2006

| &lt;!--Vendor ID--&gt;172f:0034
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Waltop Slim Tablet 5.8&quot;
    Genius G-Pen F350
    Trust item #16485
    VisTablet Mini
    iVistaTablet Slim 5.8
| &lt;!--Vendor ID--&gt;172f:0032
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Waltop Venus S Tablet
    Trust eBrush Widescreen Tablet (#17939)

| &lt;!--Vendor ID--&gt;172f:0503
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Aiptek GmBH MediaTablet Ultimate II - 16:10 Professional Graphic Tablet Model 1400U 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Opinion 
|-
| &lt;!--Description--&gt;Hanvon Beijing HanWang HW Micro Drawing Tablet ET0504U 
| &lt;!--Vendor ID--&gt;0x0b57
| &lt;!--Product ID--&gt;0x8030
| &lt;!--Revision--&gt;01111
| &lt;!--Opinion--&gt;{{No|does not work - recognised as an HID mouse - no tablet extensions detected}}
|-
| &lt;!--Description--&gt;KYE EasyPen 340, Genius EasyPen 340 
| &lt;!--Vendor ID--&gt;0458:5014
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|untested }}
|-
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Opinion 
|-
| Aiptek Hyper Pen 6000u PC Tablet APT
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| {{No|detected but does not work - win98 era cordless 6in by 4.5in - }}
|-
| &lt;!--Description--&gt;nisis T-8000U APT-2 Aiptek rebadge 
| &lt;!--Vendor ID--&gt;0x08CA
| &lt;!--Product ID--&gt;0x0021
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|A5 detected but no responses }}
|-
| &lt;!--Description--&gt;Acecad Flair II GT-504 Init Fkt  Fkt 0x5ab450c0
AIPTEK HyperPen 10000 U
Aiptek HyperPen 10000U, 
AIPTEK Slim Tablet U600 Premium II
| &lt;!--Vendor ID--&gt;0x0460
| &lt;!--Product ID--&gt;0x0004
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Ace Cad Enterprise Co., Ltd Tablet - 5x3.75 drawing area 
| &lt;!--Vendor ID--&gt;0x0460
| &lt;!--Product ID--&gt;0x0004
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Bosto's 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }} UCLogic Digitizer 
|-
| &lt;!--Description--&gt;Adesso CyberTablet Z7, Adesso CyberTablet 12000, Adesso CT-12000A  
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;UC-Logic / Lapazz WP8060, UC-Logic / Lapazz PF1209, UC-Logic / Lapazz Artistic Tablet 5540,   Manhattan 8&quot;x6&quot;, Manhattan 3&quot;x4&quot;, Manhattan
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested but suspect not working}}
|-
| &lt;!--Description--&gt;DigiPro 5.5×4” Graphics Tablet
Digital Ink Pad (A4 format) 
DigiPro WP8060, DigiPro WP5540,  
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Genius G-pen
G-Pen 4500
Genius Wizardpen
Genius Mousepen
Genius Easypen i405 M610 
Genius PenSketch 9x12, Genius MousePen i608, Genius MousePen 8x6, Genius MousePen / WizardPen 5x4, 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Genius G-Pen F610
Genius G-Pen M610 
Genius G-Pen 340 (UC-LOGIC Tablet WP4030U)
Genius G-Pen 450 (UC-LOGIC Tablet WP5540U)
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Genius
UC-LOGIC
iBall Tablet PF8060
iBall
Iball Pen Tablet 8060U, Iball Pen Tablet 5540U, Iball Pen Tablet 4030U, Iball Design Tablet PF1209,
NGS CADBOY (UC-LOGIC Tablet WP5540U)
Pentagram
QWare
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Trust TB-3100
Trust TB-5300 Trust 15356 
Trust TB-6300 Trust 15357  WP8060U  Slimline but bulky with metal backing A5 size 
Trust 16486, Trust 16447,  Sketch Design Tablet,
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|clashes with usb and crashes AROS }}
|-
| &lt;!--Description--&gt;UC-Logic Tablet WP1062
    Aiptek HyperPen 10000U
    Monoprice 10X6.25 Inches Graphic Drawing Tablet
    Pickle 10x6.25 Inch Graphic Drawing tabletguess

| &lt;!--Vendor ID--&gt;5543:0064
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Opinion 
|-
| [ VTech KidiPhoto Art Studio] 
| 
| 
|  
| {{yes|works}}
|-
|}

Tablet has a squared lines of wires which induce a current into the pen which is then detected by the metal grid in the tablet pad. Tablets report pressure (and tilt on expensive models) and are absolute pointing devices (put the pen at the top left and the mouse pointer will go to the top left of the screen). Graphic drawing area, what keys, report rate, resolution lpi lpmm, accuracy, pressure levels (may come from the app), origin position,

Wacom tablets use electromagnetic resonance technology.  Since the tablet provides power to the pen through resonant inductive coupling, no power is required for the pointing device. As a result, no batteries are inside the pen (or the accompanying puck), making them lighter and slimmer.

Under the tablet's surface (or LCD in the case of the Cintiq) is a printed circuit board with a grid of multiple send/receive coils and a magnetic reflector attached behind the grid. In send mode, the tablet generates a close-coupled electromagnetic field (also known as a B-field) at a frequency of 531&amp;nbsp;kHz. This close-coupled field stimulates oscillation in the pen's coil/capacitor (LC) circuit when brought into range of the B-field. Any excess resonant electromagnetic energy is reflected back to the tablet. In receive mode, the energy of the resonant circuit’s oscillations in the pen is detected by the tablet's grid. This information is analyzed by the computer to determine the pen's position, by interpolation and Fourier analysis of the signal intensity.

In addition, the pen communicates information such as pen tip pressure, side-switch status, tip vs. eraser orientation and ID number (to differentiate between different pens, mice, etc.). For example, applying more or less pressure to the tip of the pen changes the value of the pen's timing circuit capacitor. This signal change can be communicated in an analog or digital method. An analog implementation modulates the phase angle of the resonant frequency, while a digital method is communicated to a modulator that distributes the information digitally. The tablet forwards this and other relevant tool information in packets, up to 200 times per second, to the computer.


If you disable (delete all of them except for one that needs to be set to &quot;no action&quot;, so that it will not be regenerated as default) the Extra Startup actions, the tablet should remain in relative mouse mode—you will not get pressure information in that mode though. [http://tech.groups.yahoo.com/group/highway_usb/message/2394]}}


=== Handheld Barcode Scanner Readers ===

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;Farsun 9100 barcode scanner 0-12&quot; 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Motorola Symbol LS2203 CMOS 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Tysso 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested Simple}} Code 11, Code 39, Code 93, Code 128, Coda Bar, UPC-A, UPC-E, EAN-8, EAN-13, MSI/Plessey, Telepen, Interleaved 2 of 5, Industrial 2 of 5, Matrix 2 of 5 
|-
| &lt;!--Description--&gt;Unitech MS320 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Wasp WCS3905 CCD 1&quot; 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }} Code 93, Matrix 2 of 5, Industrial 2 of 5, Code 39, UCC/EAN-128, ISBN, Code 32, EAN/JAN-8 , EAN/JAN-13 , UPC-A, UPC-E, Codabar, Code 128, Code 11, Interleaved 2 of 5, MSI-Plessey, China Post, IATA 2 of 5, ISSN, UK-Plessey 
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Opinion 
|-
| &lt;!--Description--&gt;Datalogic Touch 90 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Intermec  
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Honeywell Metrologic MK9540-32A38 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Motorola LS2208 Laser 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Wasp WWS800 Laser 1D 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Opinion 
|-
| &lt;!--Description--&gt;Datalogic GD4130-BK-C066 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Honeywell 1202G-1USB-5 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Motorola / Symbol DS6707-DC20007ZZR 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Opinion 
|-
| &lt;!--Description--&gt;DataMan 8000 2D 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Honeywell Voyager 9520/40 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Metrologic MS1690 USB 2D Barcode Scanner  
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }} QR Code GS1 Databar PDF417
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Syscan GM800 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
|}

[http://www.scandit.com/2011/11/04/types-of-barcodes-choosing-the-right-barcode-type-ean-upc-code128-itf-14-or-code39/ Types of Barcode]

&lt;pre&gt;
UPC-A       Grocery most common 
Code 128    
EAN-13      Library Books ISBN &amp; ISSN, 
Code 39     
Codabar     blood bank,

2D barcodes such as 
Data Matrix 
PDF417e     
Maxicode    
Aztec       
QR Code     old Nokia handsets, 
MicroPDF417 
&lt;/pre&gt;


===TouchScreens===

Projected capacitive (PCAP) touch screen product, amongst many options the widely used are I2C and USB 

*USB host–device structure which dominates consumer and industrial electronics devices where higher bandwidth needed and user-friendly (multiswipes)
*I2C Inter-Integrated Circuit simple serial standard for LCD display in embedded systems because of cost and low power 
*SPI arduino and rpi single boards 

We cover the USB here 

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| eGalax Touch 4a
| 0eef 
| 0001 
| 0001
| {{yes|2009 works}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Lilliput HDMI Monitors
669GL-70NP/C/T (7 inch)
869GL-80NP/C/T (8 inch)
FA1011-NP/C/T (10 inch)
FA1046-NP/C/T (10 inch)
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Iilyama Prolite Monitors
PROLITE T1513SR-1 (15 inch)
PROLITE T1730 (17 inch)
PROLITE T1713SR-1 (17 inch)
PROLITE T1913SR-1 (19 inch)
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Smart Display Company (SDC) Touchscreens TFT Monitors
TOUCH-TFT-TS07 (7 inch)
TOUCH-TFT-TS08 (8 inch)
TOUCH-TFT-TS10 (10 inch)
TOUCH-TFT-TS12 (12 inch)
TOUCH-TFT-TS15 (15 inch)
TOUCH-TFT-TS17 (17 inch)
TOUCH-TFT-TS19W (19 inch wide)
TOUCH-TFT-TS22W (22 inch wide)
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;XENARC Monitors 7 inch models
700TSH
700TSU
700TSV
702TSV
705TSV
706TSA
700IDT
MDT-X7000
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;XENARC 
8 inch models:
800TSV
805TSV

10 inch models:
1020TSV
1026TSA
1040TS

12 inch models:
1200TS
1200TR
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Opinion 
|-
| &lt;!--Description--&gt;Asus VT229H 21.5&quot;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;CUQI 7&quot; Monitor Touchscreen 1024x600 IPS
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Espresso 15&quot; Portable Touchscreen Display Monitor
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Hannspree HT225HPB 21.5 inch
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;WaveShare 13.3inch HDMI LCD (H) (with case)
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
|}


===GPS tracking, running, cycling, biking, walking, hiking, ORIENTEERING, boaters and mapping===

Support for OpenStreetMap but not for Ordnance Survey, Map Pilot or National Geographic's Topo maps data gdb,

Data output supported nmea 0183 V1.5 APA, V1.5 XTE and V2.1 GSA formats, gpx, kml/kmz, tracks from tcx files, geo: URIs,  
NMEA0183(which is RS232, voltages range from -15 volts to 15 volts, 4800 baud), or need NMEA sentences connected to your computer

other method that some units support is a special serial cable that actually emits raw RS232 NMEA. These usually take 10-&gt;30 volts input, can run the unit, and have full voltage I/O for RS232 (not like spanner mode, which effectively turns the unit into a USB-&gt;Serial adapter inside the case).

Equivalent apps - merkator, mapsource,

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;Garmin gpsmap 180 GPS/chart plotter 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;1992 GARMIN GPS 55 AVD Portable System 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Garmin GPS V 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested - waas pinpoint within 3 metres - nmea - 4AA battery}}
|- 
| &lt;!--Description--&gt;Garmin GPS 12 12XL 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Garmin Legend C 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Garmin eMap 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|possibly through usbmodem rs232 connection nmea 0183 protocol}}
|-
| &lt;!--Description--&gt;Garmin eTrex 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}} rs232 these older units supported it and would provide the stream in either the standard NMEA 0183 format or a proprietary Garmin format.
|-
| &lt;!--Description--&gt;Garmin GPS 75 AVD 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Magellan GPS Map 7000 model 45006 (1994) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Magellan GPS Tracker
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Magellan Pioneer Satellite Navigator 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Magellan GPS 300 315 320 Mentor Receiver (2003) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Not for dedicated sat nav units like the Nuvi, TomTom, etc 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Opinion 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;NaviLock NL-402U 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested u-blox 5 SuperSense® chipset with receivers for GPS, GLONASS, Galileo, BeiDou and QZSS}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;GM1-86UB
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| U-BLOX UB-6010 GGA,GSA,GSV, RMC and support VTG, GLL, TXT ublox binary and NMEA Command Dynamic Condition }}
|-
| &lt;!--Description--&gt;NAVILOCK GPS NL-602U USB
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{Yes|works via usbmodem.device - ublox ag 6 chipset - 50 channel}}
|-
| &lt;!--Description--&gt;TOPGNSS ton Receiver &amp; Antenna GM702  u-blox 7 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{Yes|UBLOX7020 chip design bloc u-blox}}
|-
| &lt;!--Description--&gt;VK-162 G-MOUSE u blox 7 
| &lt;!--Vendor ID--&gt;0x1546
| &lt;!--Product ID--&gt;0x01a7
| &lt;!--Revision--&gt;0100
| &lt;!--Opinion--&gt;{{N/A|UBX G70xx with RMC VTG GSV TXT GLL GGA GSA}}
|-
| &lt;!--Description--&gt;VK-172 u-blox 7 G7020-KT gps gnss white pen stick receiver - over 1 inch long 
| &lt;!--Vendor ID--&gt;0x1546 
| &lt;!--Product ID--&gt;0x01a7
| &lt;!--Revision--&gt;0100 
| &lt;!--Opinion--&gt;{{N/A| detected as cdc controlled plug in device - 18x18x2mm patch antenna but can be slow to update - nmea 0183 and ublox binary protocol}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;GlobalSat BU-353 WaterProof USB GPS Receiver 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested SiRF Star III}}
|-
| &lt;!--Description--&gt;Haicom HI-206 USB GPS receiver with RS-232 interfaces, RJ11 and PS/II connector EB 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|usb-serial prolific pl2303 detected but GSP3F SiRF Star IV technology not detected or bound}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;BT760Y, 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested Skytraq Venus 5 GPS chipset}}
|-
| &lt;!--Description--&gt;GM-65 USB GPS Receiver
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested Skytraq Venus 6 GPS chipset - 65 channel}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested Skytraq Venus 7 GPS chipset}}
|-
| &lt;!--Description--&gt;GM-65 USB GPS Receiver
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested Skytraq Venus 8 GPS chipset - 167 channels}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Opinion 
|-
| &lt;!--Description--&gt;Garmin Colorado 300 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}} USB 
|-
| &lt;!--Description--&gt;Garmin Geko 101 201 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}} limited waas enabled only - waypoints - aaa battery 
|-
| &lt;!--Description--&gt;Garmin Edge 200 bike mount 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Garmin ForeRunner 10 15 watch 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Garmin Montana 600
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Garmin Dakota 10 20 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Garmin Map76s 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Garmin Oregon 450T  
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}} USB nmea 0183 
|-
| &lt;!--Description--&gt;Garmin eTrex 10 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested - no nmea0183 sentences data stream output - configuration an option to set it to &quot;Garmin&quot; mode, or &quot;Mass Storage&quot; mode. Since the mass storage mode seems to be required for waypoint/track/etc data exchange, the 'Garmin' mode would be for this data stream. Yet putting it in that mode doesnt seem to produce anything.}}
|-
| &lt;!--Description--&gt;Garmin Oregon 650T 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Garmin GPSMAP 64S 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{Maybe|untested}}
|-
| &lt;!--Description--&gt;GPSMap 78S or GPSMap 76CSX which has a NMEA port for talking to Nav equipment
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{Maybe|untested}}
|-
| &lt;!--Description--&gt;Garmin eTrex Vista Cx GPS Receiver 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested - 2AA battery}}
|-
| &lt;!--Description--&gt;Garmin GPSmap 276c
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Magellan 2000 XL 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Magellan 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Magellan 3000 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Magellan Triton 300
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}} SiRFstarIII™, Antenna Type Multidirectional Patch with WAAS, EGNOS, MSAS support 
|-
| &lt;!--Description--&gt;Magellan Triton 400 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
|}


==massstorage.class (MSC/UMS - most cameras and mp3 players)==

=== USB Card Readers ===
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;15%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;5%&quot; |Product ID
! width=&quot;5%&quot; |Revision 
! width=&quot;15%&quot; |Installing
! width=&quot;15%&quot; |Booting
! width=&quot;30%&quot; |Opinion
|-
| A-Tec Model CR-362 
| 
| 
|  
| &lt;!--Installing--&gt;
| &lt;!--Booting--&gt;
| {{N/A|untested}}
|-
| [http://www.belkin.com/IWCatProductPage.process?Merchant_Id=&amp;Section_Id=200406&amp;pcount=&amp;Product_Id=179164 Belkin 15 in 1 Card Reader]
|
|
|  
| &lt;!--Installing--&gt;
| &lt;!--Booting--&gt;
| {{yes|works}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Installing--&gt;
| &lt;!--Booting--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| Conrad CP440 60 in 1 
| 
| 
| 
| &lt;!--Installing--&gt;
| &lt;!--Booting--&gt;
| {{yes|works on a1k forum}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Installing--&gt;
| &lt;!--Booting--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| Genesys Gtech Logic 19 in 1
| 0x05E3
| 0x0710
| High 0200
| &lt;!--Installing--&gt;
| &lt;!--Booting--&gt;
| {{yes|works}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Installing--&gt;
| &lt;!--Booting--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| Hama 19 in 1 Card Reader 
|
|
|  
| &lt;!--Installing--&gt;
| &lt;!--Booting--&gt;
| {{yes|works}}
|-
| Hama 35 in 1 Card Reader 
|
|
|  
| &lt;!--Installing--&gt;
| &lt;!--Booting--&gt;
| {{yes|works}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Installing--&gt;
| &lt;!--Booting--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Integral Single Slot SD 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Installing--&gt;
| &lt;!--Booting--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Installing--&gt;
| &lt;!--Booting--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Kingston USB 3.0 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Installing--&gt;
| &lt;!--Booting--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Lexar microsd adapter 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Installing--&gt;
| &lt;!--Booting--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }} but wider than Sandisk version - could block other slot if below 
|-
| Pretec CardDriver 
|
|
| 
| &lt;!--Installing--&gt;
| &lt;!--Booting--&gt;
| {{no|no driver}}
|-
| Sandisk MicroMate 
|
|
|  
| &lt;!--Installing--&gt;
| &lt;!--Booting--&gt;
| {{yes|works}}
|-
| &lt;!--Description--&gt;Sandisk MobileMate SD 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Installing--&gt;
| &lt;!--Booting--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }} 
|-
| &lt;!--Description--&gt;Sandisk MobileMate Micro 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Installing--&gt;
| &lt;!--Booting--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }} has satisfying 'click' when microsd inserted 
|-
| &lt;!--Description--&gt;Sandisk MobileMate Duo MicroSD
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Installing--&gt;
| &lt;!--Booting--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }} no 'click' insertion uses pressure so future wear and tear issues 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Installing--&gt;
| &lt;!--Booting--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Serena metal cased microsd only 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Installing--&gt;
| &lt;!--Booting--&gt;
| &lt;!--Opinion--&gt;{{N/A|Maybe}} hit or miss on quality 
|-
| &lt;!--Description--&gt;Serena &quot;Sandisk MobileMate&quot; look-alike 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Installing--&gt;
| &lt;!--Booting--&gt;
| &lt;!--Opinion--&gt;{{N/A|Maybe}} hit or miss on quality 
|-
| SilverCrest 16in1 
|
|
|  
| &lt;!--Installing--&gt;
| &lt;!--Booting--&gt;
| {{yes|works}}
|-
| &lt;!--Description--&gt;Transcend 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Installing--&gt;
| &lt;!--Booting--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Transcend P5 8 in 1 TSRDP5K 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Installing--&gt;
| &lt;!--Booting--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Transcend P8 15 in 1 TSRDP8K
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Installing--&gt;
| &lt;!--Booting--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Installing--&gt;
| &lt;!--Booting--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| Zyxel integralmemory 8 in 1 
| 0x0aec
| 0x3260
|  
| &lt;!--Installing--&gt;
| &lt;!--Booting--&gt;
| {{no|not detected}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Installing--&gt;
| &lt;!--Booting--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
|}

=== USB Hard Drives ===
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| Datel MaxDrive 
| 
| 
|  
| {{N/A|untested}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Inateck 2.5 Inch USB 3.0 Hard Drive Disk Enclosure/ Case (FE2001) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }} Full USB 3.0 port but plastic teeth keeping drive in place can snap 
|-
| &lt;!--Description--&gt;Inateck case (FE2002) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }} full USB 3.0 port - updated design 
|-
| &lt;!--Description--&gt;Inateck case (FE3001) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }} wider USB 3.0 port and no on/off switch  Jmicron JMS578 chipset
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| Iomega Desktop Hard Drive 500GB, 3,5“, USB2.0 
| 
| 
| 
| {{N/A|untested}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| Samsung
|
|
|
| {{N/A|untested}}
|-
| Samsung
|
|
|
| {{N/A|untested}}
|-
| Samsung T3 SSD 
|
|
|
| {{N/A|untested}} USB 3.1 Gen 1 space grey / black metal/ plastic 
|-
| Samsung T5 SSD 
|
|
|
| {{N/A|untested}} USB 3.1 Gen 2 256GB 512GB alluring blue 1Tb 2Tb black unibody metal 
|-
| Samsung
|
|
|
| {{N/A|untested}}
|-
| Seagate
|
|
|
| {{N/A|untested}}
|-
| Seagate 
|
|
|
| {{N/A|untested}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Toshiba Canvio 1TB 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{Yes|partition fat32 or sfs to 100GB max - ntfs partitions not detected out of the box - select usb drive in trident prefs and press disable to shutdown}}
|-
| Verbatim 160GB Smartdisk 
| 
| 
|  
| {{yes|works }}
|-
| Western Digital USB 
|
|
|
| {{N/A|untested}}
|-
| &lt;!--Description--&gt;WD Essential 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;WD Passport 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
|}


=== USB DVD CD ROM Drives ===
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;12.5mm 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| Opinion 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| Opinion 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;12.5mm enclosure mini-sata dvd-rw 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested needs sole usb3 port to power it}}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| Opinion 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;9.5mm enclosure ECD829 mini-sata dvd-rw with Initio Corporation INIC-1618L SATA 
| &lt;!--Vendor ID--&gt;0x13fd
| &lt;!--Product ID--&gt;0x0840
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested but probably needs sole usb3 port to power it}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|}


=== USB to NGFF NVMe SDD HDD DVD CD ROM Drives ===

The older Jmicron JMS539B seems to result in massive filesystem corruption given the amount of corrupted content. Prehaps always avoided Jmicron and opted for Asmedia even if it costed a bit more. Realtek seems to be working okay for me generally speaking and newer Jmicron chipsets are less buggy – but evidently not perfect. 

From [https://goughlui.com/2025/08/17/psa-validate-your-storage-jmicron-jms583-kioxia-bg4-series-ssd-issue/ thread] 

Here is a [https://forums.anandtech.com/threads/stable-nvme-usb-adapter.2572973/ very long thread] that discusses data corruption and stability issues with these bridges. The majority of the posts are complaining of dropouts, hangs and the like, which usually down to either a poor USB 3.x implementation (SuperSpeed connections are very picky as to cables, ports and trace routing) or problematic compatibility. Regardless, the [https://www.legitreviews.com/jmicron-jms583-controller-version-matters-for-portable-usb-drives_219422 JMS583 is known to have several versions] noting that the last revision (C) in that article is a 2021 release which should fix earlier stability and cable quality compatibility issues. 
JMS583-STD-Release-v00.02.01.04-Bus Power.bin is the latest JMS583 firmware as of August 2025. 

Early firmware RTL9210 seems to have issues as well 


* RTL9210B
* JMS583 rev1 with firmware A2 or A3  

* RTL9210A
* JMS583 firmware 2.0.9 
* Asmedia ASM2362

* RTL9201A


The reference Hardware ID for the JMS583 chipset from JMicron is:
VID_152D&amp;PID_0583&amp;REV_0209
where &quot;VID_152D&quot; identifies a JMicron product;
&quot;PID_0583&quot; is the generation chipset;
&quot;REV_0209&quot; is the firmware version installed.

In the same way, the reference Hardware ID for the RTL9210 from Realtek is:
VID_0BDA&amp;PID_9210&amp;REV_3100
&quot;VID_0BDA&quot; is for a Realtek product, &quot;PID_9210&quot; is referred to the chipset and &quot;REV_3100&quot; to the firmware.


{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;ASM1153E / ASM1153 with firmware 140509_A1_82_40 or 141126_A1_EE_82. Both supports UASP and TRIM on USB 3.1 Gen.1 adapter
| &lt;!--Vendor ID--&gt;0x174c
| &lt;!--Product ID--&gt;0x55aa
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{maybe|works with sabrent ec-uasp}}
|-
| &lt;!--Description--&gt;ASM235CM Ugreen aluminum bridging the USB3.2 Gen2x1 to Serial ATA host interface 
| &lt;!--Vendor ID--&gt;0x174c
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| Opinion 
|-
| &lt;!--Description--&gt;TI 9261 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;ASM225
| &lt;!--Vendor ID--&gt;0x174c
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| Opinion 
|-
| &lt;!--Description--&gt;JMicron JMS578 issues USB 3.1 Gen.1 adapter 
| &lt;!--Vendor ID--&gt;152d
| &lt;!--Product ID--&gt;0578
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{maybe|needs fixing on pi4 storage quirks}}
|-
| &lt;!--Description--&gt;JMicron JMS576 issues USB 3 to usb-c adapter 
| &lt;!--Vendor ID--&gt;152d
| &lt;!--Product ID--&gt;0576
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{maybe|orico}}
|-
| &lt;!--Description--&gt;JMS562 JMicron Technology Corp
| &lt;!--Vendor ID--&gt;152d
| &lt;!--Product ID--&gt;0562
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;JMS561U
| &lt;!--Vendor ID--&gt;0x152d
| &lt;!--Product ID--&gt;0x1561
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{maybe|works with sabrent ec-uasp}}
|-
| &lt;!--Description--&gt;VL716Q4 Orico black meshed aluminum usb c
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Asmedia ASM1053E 
| &lt;!--Vendor ID--&gt;0x1B21 
| &lt;!--Product ID--&gt;0x55aa
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;ASmedia ASM1051E
| &lt;!--Vendor ID--&gt;0x174c
| &lt;!--Product ID--&gt;0x55aa
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Asmedia ASM1053
| &lt;!--Vendor ID--&gt;0x174C
| &lt;!--Product ID--&gt;0x1536
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }} 
|-
| &lt;!--Description--&gt;Asmedia ASM104x
| &lt;!--Vendor ID--&gt;0x1B21 
| &lt;!--Product ID--&gt;0x1042 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }} 
|-
| &lt;!--Description--&gt;Unknown Chinese version 
| &lt;!--Vendor ID--&gt;0x0bc2
| &lt;!--Product ID--&gt;0x2312 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{maybe|sometimes works}}
|-
| &lt;!--Description--&gt;JMicron N5321 gr
| &lt;!--Vendor ID--&gt;0x152d
| &lt;!--Product ID--&gt;0xa583
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| Opinion 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Initio Corp INIC-1618L mini slimline sata 6 + 7 pins to usb2 adapter 
| &lt;!--Vendor ID--&gt;0x13FD
| &lt;!--Product ID--&gt;0x0840
| &lt;!--Revision--&gt;0114
| &lt;!--Opinion--&gt;{{maybe|sometimes works mini sata to usb2 detects 201x laptop DVD as MassStorage(CD/DVD) but may need powered USB hub}}
|-
| &lt;!--Description--&gt;Unknown mini sata to usb3 adaptor 
| &lt;!--Vendor ID--&gt;0x01F75
| &lt;!--Product ID--&gt;0x0621
| &lt;!--Revision--&gt;0036 
| &lt;!--Opinion--&gt;{{maybe|sometimes works mini sata to usb3 detects 201x notebook DVD drive as MassStorage(SCSI) but 5V 1.5Amp needs powered hub to burn }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|}


=== External Floppy ===
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;[http://techtravels.org/amiga/amigablog/ Amiga Floppy Project]
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| {{no|no driver}}
|-
| &lt;!--Description--&gt;[http://amigakit.leamancomputing.com/catalog/product_info.php?products_id=842 Catweasel Mk4]
| 0xE159
| 0x0001
| 0x00
| {{yes|[http://archives.aros-exec.org/index.php?function=browse&amp;cat=driver/storage works]}}
|-
| &lt;!--Description--&gt;[http://hxc2001.free.fr/floppy_drive_emulator/ HxC Floppy Emulator]
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| {{no|no driver}}
|-
| &lt;!--Description--&gt;[http://www.softpres.org/glossary:kryoflux KyroFlux]
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| {{no|no driver}}
|-
| &lt;!--Description--&gt;Samsung SFD-321U/EP USB Floppy
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| {{no|no driver}} 
|-
| &lt;!--Description--&gt;[http://www.cbmstuff.com/proddetail.php?prod=SCP SuperCard Pro] 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;[https://github.com/tebl/Amiga-DrawBridge Amiga-DrawBridge][https://www.facebook.com/groups/greaseweazle Greaseweazle STM hardware], [https://cowlark.com/fluxengine/index.html Greaseweasel support], [https://github.com/keirf/Greaseweazle/wiki software], [https://amigakit.amiga.store/greaseweazle-p-91279.html buy], 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;FL-2501 USB Portable Diskette Drive  
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;2009 usb - [https://amiga.robsmithdev.co.uk/ Drawbridge] [https://github.com/RobSmithDev/ArduinoFloppyDiskReader software] ribbon cable compat with p/n 19308801-19 and s/n U356244 - model ASM P/N 27l4226 and FRU P/N 05k9283 - 
|-
| &lt;!--Description--&gt;Dell Floppy Drive Module USB External 3.5&quot; - Teac FD-05PUB 1.44mb 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;2004 usb 1.1 
|-
| &lt;!--Description--&gt;USB FLOPPY DISK DRIVE (USB External Floppy Disk) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;[https://github.com/SukkoPera/OpenFlops OpenFlops] with [https://github.com/keirf/flashfloppy FlashFloppy] Gotech clone 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;[https://github.com/hmerrett/HenryFlops HenryFlops reworked OpenFlops] 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
|}


==ptp.class (PTP and MTP - other cameras and mp3 players)==

=== Cameras ===
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;Canon EOS 20D
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2004  }}
|-
| &lt;!--Description--&gt;Canon 350D (also known as the Digital Rebel XT/Kiss Digital N) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2005 DIGIC II processor 8-megapixel }}
|-
| &lt;!--Description--&gt;Canon PowerShot A430 A560 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2006 }}
|-
| &lt;!--Description--&gt;Canon EOS 400D (XTi) digital SLR 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2007 }}
|-
| &lt;!--Description--&gt;Canon EOS 1000D also known as Rebel XS
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2008 10.2mp 720p  }}
|-
| &lt;!--Description--&gt;Canon 450D aka Rebel Xsi 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2008 12.2mp }}
|-
| &lt;!--Description--&gt;Canon PowerShot S90 S95 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2009 2010 720p video - 10Mpixel }}
|-
| &lt;!--Description--&gt;Canon Powershot SD960 IS Digtal ELPH 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2009 Still Image: Exif 2.2 (JPEG), Movie: MOV (Image: H.264; Audio: Linear PCM) Lithium-ion Battery Pack NB-4L }}
|-
| &lt;!--Description--&gt;Canon EOS 500D aka Rebel  
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2009 1080p 15.1MP Lithium  }}
|-
| &lt;!--Description--&gt;Canon EOS 550D 600D aka Rebel T2i T3i DSLR 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2010-2011 1080p 18MP Lithium LP-E8 }}
|-
| &lt;!--Description--&gt;Canon Powershot S100 S110 S120  
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2011-2013 720p-1080p video 12.1MP and above versions - }}
|-
| &lt;!--Description--&gt;Canon EOS 1100D DSLR Camera aka Rebel T3 SLR, EOS Kiss X50 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2011 720p 10Mpixels Lithium  }}
|-
| &lt;!--Description--&gt;Canon EOS 650D 700D aka Rebel T4i T5i T6i SLR 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2012-2013 1080p 18Mpixels Lithium LP-E8 articulating flip out twistable screen }}
|-
| &lt;!--Description--&gt;Canon ELPH 300 HS (IXUS 220 HS) 230 100 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2012 blogging camera }}
|-
| &lt;!--Description--&gt;Canon PowerShot N 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2013  12.1 MP CMOS, DIGIC 5 Wifi Lithium Battery Pack NB-9L }}
|-
| &lt;!--Description--&gt;Canon Powershot G7 X, G7X-II 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2014-2016 1080p video 12.1MP and above versions - }}
|-
| &lt;!--Description--&gt;Canon EOS 1300D DSLR Camera aka Rebel T6 SLR 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2016 1080p 16Mpixels Lithium  }}
|-
| &lt;!--Description--&gt;Canon Powershot G7x G5X 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| G7X flip up and G5X flip out - same batteries - no external microphone input - }}
|-
| &lt;!--Description--&gt;Canon EOS M3 M5 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| flip out - same batteries - }}
|-
| &lt;!--Description--&gt;Canon EOS 60D 70D 80D 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Canon 6D 7D 8D 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|untested}}
|-
| &lt;!--Description--&gt;Canon 5D Mark II III IV DSLR
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Canon 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Canon 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Fuji FinePix A850
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;FujiFilm Finepix F100fd
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Fuji FinePix F810
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Fuji xf1 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| pocketable exr cmos 12mp }}
|-
| &lt;!--Description--&gt;Fuji xt1  x-t1  x10 x-t10
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| 1080p }}
|-
| &lt;!--Description--&gt;Fujifilm x100 x100s x100t 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Fuji xPro1 xPro2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Fuji xt2 / x-t2 x-t20 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| 4K video }}
|-
| &lt;!--Description--&gt;Fuji 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Fuji 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|untested}}
|-
| &lt;!--Description--&gt;Fuji 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|untested}}
|-
| &lt;!--Description--&gt;GoPro HERO 3 HERO4 HERO 5 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Nikon 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Nikon D100, D60
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2004 Compact flash storage - non interchangeable lenses up to 12.3MP sensor }}
|-
| &lt;!--Description--&gt;Nikon D50, D50x 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2005  storage - 6.1MP sensor }}
|-
| &lt;!--Description--&gt;Nikon D70, D80, D90 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2006 Compact flash storage - 10MP sensor }}
|-
| &lt;!--Description--&gt;Nikon D40, D40x 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2007  storage -  10MP sensor }}
|-
| &lt;!--Description--&gt;Nikon D300, D700
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2008  storage -  12.3MP sensor }}
|-
| &lt;!--Description--&gt;Nikon D2Xs, D2Hs, D3 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2006-2008  storage - sensor }}
|-
| &lt;!--Description--&gt;Nikon D3000 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2008 720p video }}
|-
| &lt;!--Description--&gt;Nikon D5000 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2010 720p video unlike D3000 }}
|-
| &lt;!--Description--&gt;Nikon D6000 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2010 16mpixel}}
|-
| &lt;!--Description--&gt;Nikon D7000  
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2010 16.2mp 720p video }}
|-
| &lt;!--Description--&gt;Nikon L26 L27 L28 L29 L31 Coolpix compact cameras 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2011 720p video - 2 AA - pocket sized }}
|-
| &lt;!--Description--&gt;Nikon D3100   
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2011 720p video 14.2mp}}
|-
| &lt;!--Description--&gt;Nikon D5100 DSLR
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2011 16.2mp  720p}}
|-
| &lt;!--Description--&gt;Nikon L810 L820 L830 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2012-2014 720p video }}
|-
| &lt;!--Description--&gt;Nikon D4 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2012  storage - sensor }}
|-
| &lt;!--Description--&gt;Nikon D7100 D7200  
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2012-2014 up to 24.2mp 1080p video }}
|-
| &lt;!--Description--&gt;Nikon D3200  
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2012 1080p 24MPixel}}
|-
| &lt;!--Description--&gt;Nikon D5200 D5300  
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2013 24.1MP 1080p }}
|-
| &lt;!--Description--&gt;Nikon D800 D600 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2014 1080p video sd card storage - dust/oil issue at start}}
|-
| &lt;!--Description--&gt;Nikon D3300 DSLR
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2014 24.2MP 1080p  }}
|-
| &lt;!--Description--&gt;Nikon D500, a high-performance DX-format (APS-C) DSLR 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2016 }}
|-
| &lt;!--Description--&gt;Nikon D3400 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2016 24.2MP 1080p }}
|-
| &lt;!--Description--&gt;Nikon D5500 D5600 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2016-2018 24.1MP 1080p }}
|-
| &lt;!--Description--&gt;Nikon D810 D610 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2018 1080p video sd card storage }}
|-
| &lt;!--Description--&gt;Nikon D7300 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| 4K UHD video }}
|-
| &lt;!--Description--&gt;Nikon D900 D850 D820 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| 4k 46MP }}
|-
| &lt;!--Description--&gt;Nikon 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Nikon 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Olympus C-370 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2004 3.2mp }}
|- 
| &lt;!--Description--&gt;Olympus Camedia C-725 Ultrazoom
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2004 3mp aa batteries, }}
|-
| &lt;!--Description--&gt;Olympus Evolt E-500
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2005 8mp  }}
|- 
| &lt;!--Description--&gt;Olympus 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Olympus Evolt E-410 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2007  }}
|- 
| &lt;!--Description--&gt;Olympus Evolt E-510
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2007 10MP Live MOS sensor with TruePic III processor,  }}
|-
| &lt;!--Description--&gt;Olympus E-420
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2008 10mp, compactflash and xD cards,  }}
|-
| &lt;!--Description--&gt;Olympus E-520
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2008 10mp, compactflash and xD cards,  }}
|- 
| &lt;!--Description--&gt;Olympus E-620
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2009 12.3mp, compactflash, xD and microdrive cards,  }}
|- 
| &lt;!--Description--&gt;Olympus E-30 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2009  }}
|- 
| &lt;!--Description--&gt;Olympus E-450 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2009 10mp,  }}
|- 
| &lt;!--Description--&gt;Olympus 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|- 
| &lt;!--Description--&gt;Olympus 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|- 
| &lt;!--Description--&gt;Pentax * ist DS DSLR camera
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2005 6.1mp  }}
|- 
| &lt;!--Description--&gt;Pentax K10D
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2006 10.2mp APS-C CCD no video and older manual Pentax K-mount lenses}}
|-
| &lt;!--Description--&gt;Pentax K20D
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2008 14.6MP APS-C but no video recording mode }}
|-
| &lt;!--Description--&gt;Pentax K30 K-5 II 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2012 16MP full HD (1080p) recording at 24/25/30 fps}}
|-
| &lt;!--Description--&gt;Pentax K-3
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2014 24MP 1080p  }}
|-
| &lt;!--Description--&gt;Pentax K-3 II
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2015 24MP  }}
|-
| &lt;!--Description--&gt;Pentax K-3 III
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2021 25.7MP BSI CMOS sensor  }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Panasonic Lumix LZ10 LZ20 DMC-LZ30 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| 720p video }}
|-
| &lt;!--Description--&gt;Panasonic TZ1 TZ5  TZ9 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Panasonic Lumix GH1 GH2 like the DMC-GH2HEB-K - GH3 DMC-GH3HEB-K 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| Four Thirds (GH2)  MFT Micro Four Thirds (GH3) limited to 29mins recording }}
|-
| &lt;!--Description--&gt;Panasonic AF series AF100 AF101 AF102 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Panasonic Lumix DMC-G2 DMC-G3 G5 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Panasonic TZ60 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Panasonic DMC LX7 10 LX15 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Panasonic GF7 GX8 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Panasonic G80 G85 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| micro 4/3 }}
|-
| &lt;!--Description--&gt;Panasonic GH4 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| micro 4/3 - shooting in MOV or MP4 formats recording limited to sd card size but split files because the FAT32 file system only supports files up 4GB in size, which amounts to around 5 minutes of 4K (100mbps) footage - GH4 appears to create 4GB files as a rule, regardless of whether the memory card’s file system supports larger files or not - }}
|-
| &lt;!--Description--&gt;Panasonic GH5 gx80 gx85 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| Effective: 20.3 Megapixel 5184 x 3888 - 2 sd card slots compatible with high-speed, high capacity UHS-II - sd card v rating like the v90 should record at 60MB/s to be compatible with the GH5 in the All-I format - possible file corruption with .mdt files - new firmware 2.0 update, the Panasonic GH5 becomes the first 5K - }}
|-
| &lt;!--Description--&gt;Panasonic FZ2000 FZ2500 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Panasonic 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Samsung 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Samsung WB100 WB1100 WB150 WB2200 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| 16MP }}
|-
| &lt;!--Description--&gt;Samsung NX11 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Samsung  NX200, NX20, NX1000 and NX210
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| 20.3Mp APS-C sized CMOS image sensor }}
|-
| &lt;!--Description--&gt;Samsung 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Samsung 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Sanyo Xacti CG65
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Sanyo 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Sony Alpha DSLR-A100
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2005 6.1MP }}
|-
| &lt;!--Description--&gt;Sony Cyber-shot DSC camera models W110 W220 H300 H400 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2007 }}
|-
| &lt;!--Description--&gt;Sony Alpha DSLR-A200
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2008 10.2MP }}
|-
| &lt;!--Description--&gt;Sony Alpha DSLR-A230
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2009 10.2MP }}
|-
| &lt;!--Description--&gt;Sony A290 DSLR Camera 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2010 14.2MP }}
|-
| &lt;!--Description--&gt;Sony Cybershot HX20V HX30V 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2011 18mp 720p  - steady shot unit / optical block can cause buzzing noise and/or jumping image in lcd / viewfinder - dots are dirt and this voids the warranty }} 
|-
| &lt;!--Description--&gt;Sony Cybershot HX50V HX60V 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2012 20.2MP 1080p  - steady shot unit / optical block can cause buzzing noise and/or jumping image in lcd / viewfinder - dots are dirt and this voids the warranty }} 
|-
| &lt;!--Description--&gt;Sony A77 A99 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2012 }}
|-
| &lt;!--Description--&gt;Sony WX100 WX150 wx220 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2012 2014 }}
|-
| &lt;!--Description--&gt;Sony NEX-6 Sony NEX-7 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2011 16 to 24MP }}
|-
| &lt;!--Description--&gt;Sony NEX-3N Sony NEX-5N 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2013 16MP }}
|-
| &lt;!--Description--&gt;Sony α58 Sony α68 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2013 20.1 MP  2014 24mp }}
|-
| &lt;!--Description--&gt;Sony rx100 mk III 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2014 20.1MP 1.0-type back-illuminated Exmor R CMOS sensor, often after boot-up, the motor starts running for no reason for first versions' -  }}
|-
| &lt;!--Description--&gt;Sony α5000 a5000 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2014 20.1 Megapixel APS-C Exmor APS HD CMOS 1080p Sony E-mount [https://github.com/ma1co/Sony-PMCA-RE hack] using [https://www.youtube.com/watch?v=8M4hR9HiOzM this] }}
|-
| &lt;!--Description--&gt;Sony α6000 a6000 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2014 24MP APS-C sensor }}
|-
| &lt;!--Description--&gt;Sony α7 A7S a7r a7c 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2014 mirror less - more compact }}
|-
| &lt;!--Description--&gt;Sony α77 II, α99 II, 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2015 24.3 MP,  2016 42.4mp   }}
|-
| &lt;!--Description--&gt;Sony rx100 mk IV V 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2015 2016 }}
|-
| &lt;!--Description--&gt;Sony RX0 RX zero, RX0 II
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2015 2017 }}
|-
| &lt;!--Description--&gt;Sony α6500 a6500 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2016 24.2MP APS-C sensor 4K }}
|-
| &lt;!--Description--&gt;Sony α7 Alpha 7 II E-mount interchangeable lens mirrorless camera 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2017 24.2mp,  }}
|-
| &lt;!--Description--&gt;Sony α7 A7Sii a7r a7c 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2018 mirror less - more compact }}
|-
| &lt;!--Description--&gt;Sony a7 III α77 ILCE7M3/B Full-Frame Mirrorless Interchangeable-Lens Camera
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2019 24.2mp,  }}
|-
| &lt;!--Description--&gt;Sony ZV-1
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2021 24mm optical zoom, }}
|-
| &lt;!--Description--&gt;Sony ZV-1F
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2022 entry-level vlogging, 1-inch 20.1MP, ultra-wide 20mm f/2 prime lens}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|}

&lt;pre &gt;
Lens Mounts

Canon EF EF-S
Nikon F 
Panasonic 
Olympus OM 
Pentax DA, FA, F, A, M, and K series
Fujifilm X mount 
&lt;/pre &gt;

&lt;pre &gt;
Sensors

APS-C 
S35 
Full Frame 
43 Four Thirds 
M43 MFT Micro four thirds 
&lt;/pre &gt;


=== Digital Voice Recorder Dictaphone Dictation Machine Handheld ===
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Olympus VN-7000
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested 2011 }}
|-
| &lt;!--Description--&gt;Olympus VN-7200
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|untested 2012 no usb }}
|-
| &lt;!--Description--&gt;Olympus VN-7500 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested 2012 }}
|-
| &lt;!--Description--&gt;Olympus VN-7600 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested 2013 }}
|-
| &lt;!--Description--&gt;Olympus WS-100 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested usb}}
|-
| &lt;!--Description--&gt;Olympus VN-7700 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Olympus VN-8600 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Olympus VN-711PC
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Olympus VN-712PC
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Olympus VN-731PC 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Olympus 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Olympus WS-811
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested slide out usb-a - aaa battery - ok recordings }}
|-
| &lt;!--Description--&gt;Olympus VN-540PC Olympus VN-541PC 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Philips DVT1250
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Sony 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Sony 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Sony 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Sony ICD-UX470
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Sony ICD-UX560
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Sony ICD-UX570 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
|}


=== USB eBooks Readers drm free EPUB version 2.0.1 (2007), 3.0 (2011), 3.1 (2015) or [https://www.w3.org/TR/epub-33/ 3.3 (2024)] [https://github.com/thansen0/sample-epub-minimal epub examples] formats access ===

EPUB file format is an open standard based on XHTML for content and XML for metadata, contained in a zip file archive 

PDF v2.0 in 2017, 2009 takeover by ISO Org, 1.7 in 2006 , 1.6 in 2005, 1.4 in 2001, 1.3 in 1999, 1.0 in 1993 


{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;5%&quot; |Product ID
! width=&quot;5%&quot; |Revision 
! width=&quot;15%&quot; |Access
! width=&quot;30%&quot; |Opinion
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Barnes and Noble Nook Simple Touch NST BNRV300 
| &lt;!--Vendor ID--&gt;0x2080
| &lt;!--Product ID--&gt;0x0003
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;when finding the right micro usb cable that works, internal nook memory not accessible but sd card fat32 readable and writable outside 
| &lt;!--Opinion--&gt;{{N/A|2011 6in 600x800 e-ink 16 grayscale .jpg}} battery remove sd card and Torx T5 back top for Cameron Sino CS-BNR003SL - USA 1.2.2 md5sum 351e26527e80156183e74be2da2ce89f *nook_1_2_update.zip - 1.2.1 UK fdba3981f7f221cc5143db6329645bc2 *nook_1_2_update.zip - skip registration, Turn on the device, but do NOT start setting it up. Hold down the top right button on the front of the device and slide your finger from left to right across the top of the E Ink screen. A ‘Factory’ button should appear in the top left corner of the screen. Press it. Once in the Factory menu, hold down the top right button on the front of the device and tap the bottom right corner of the screen should now see a ‘Skip Oobe’ button. Tap that and the Nook should finally load the home screen. Poor battery management - 
|-
| &lt;!--Description--&gt;Barnes and Noble Nook Simple Touch with Glowlight 
*2012 Nook Simple Touch with GlowLight BNRV350 
*2013 Nook GlowLight BNRV500
| &lt;!--Vendor ID--&gt;0x2080
| &lt;!--Product ID--&gt;0x0004 0x0007 
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{N/A|2012 untested }} perform a hard reset: Turn off the nook completely, turn it on, as soon as you see the screen flash begin holding the bottom page turn buttons until the screen flashes with a message asking reset, press the 'n' key twice to start the reset - Poor battery management - 
|-
| &lt;!--Description--&gt;Nook Glowlight 4 Plus 7.8-inch screen 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }} Poor battery management - 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
*NOOK 1st Edition (2009-2018) BNRZ100
*NOOK Color (2010-2024) BNRV200
*NOOK Tablet (8GB/16GB) (2011-2024) BNTV250A / BNTV250
*NOOK HD (2012-2024) BNTV400 
*NOOK HD+ (2012-2024) BNTV600 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Elonex 511EB 
| &lt;!--Vendor ID--&gt;045e:ffff
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{N/A|2009 untested Preferences-&gt;advanced-&gt;debug device detection}}
|-
| &lt;!--Description--&gt;[https://jaforeck.wordpress.com/2012/08/05/ready-to-meet-viktor-navorski-gained-access-to-elonex-621ebs-terminal-52/ Elonex 621EB] eBook 
| &lt;!--Vendor ID--&gt;0x1f85
| &lt;!--Product ID--&gt;0x1688
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;unlocked ootb 
| &lt;!--Opinion--&gt;{{N/A|2010 untested usb mini charging 6&quot; diagonal eInk Screen - 800 x 600 pixels, 8 Level 166dpi Paperlike screen, Embedded 1GB Flash NAND, full SD Card Slot up to 16GB - WAV, MP3, JPG, PNG, BMP, GIF support and ePub and PDF(with reflow) (TXT, HTML) support}}
|-
| &lt;!--Description--&gt;Elonex 700eb 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{N/A|2011 untested adjust screen blanking by menu then settings then device standby, you can then turn it off}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;iRiver Story HD eBook 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }} freescale imx.508 arm mcimx508cvkbb cpu with 2gb samsung nand, m13892aj charging chip, eb07_main_mp1_110321 mobo, mini usb, atheros ar61026 wifi - 
|-
| &lt;!--Description--&gt;iRiver Story 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Kobo Rakuten Touch A/B	kobo3
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Kobo Touch C, Kobo Mini, Kobo Glo N613, Kobo Aura HD N514 N204	kobo4
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Kobo Aura, Kobo Aura H2O, kobo5
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{N/A|2013 6in untested }}
|-
| &lt;!--Description--&gt;Kobo Aura H2O Edition 2 v1, Kobo Glo HD, Kobo Touch 2.0, Kobo Aura ONE N709, Kobo Aura ONE Limited Edition, Kobo Aura Edition 2 v1 N236,	kobo6 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Kobo Aura H2O Edition 2 v2, Kobo Aura Edition 2 v2, Kobo Nia, Kobo Clara HD, Kobo Forma, Kobo Libra H2O	kobo7
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;Kobo Elipsa, Kobo Sage	kobo8
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
*Kobo Libra 2  kobo9, Kobo Clara 2E	kobo10, Kobo Elipsa 2E	kobo11
*Kobo Libra Colour	kobo13, Kobo Clara BW, Kobo Clara Colour	kobo12
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Pandigital Personal eReader aka? Papyre 6.2 very similar to BQ Avant Firmware
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk|2011  }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Sony PRS 300 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Sony PRS 350 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{N/A|2009 epub bbeb cbz untested }}
|-
| &lt;!--Description--&gt;Sony PRS-650
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Kindle K1 D00111 - Main Menu=: Settings: Menu=: Device Info shows S/N 
| &lt;!--Vendor ID--&gt;0x1949
| &lt;!--Product ID--&gt;0x0002
| &lt;!--Revision--&gt;100
| &lt;!--Access--&gt;256mb 
| &lt;!--Opinion--&gt;{{N/A|2007 untested Marvell Xscale PXA255}}
|-
| &lt;!--Description--&gt;Kindle K2, D00511 170-1012-00, D00701 D00801 S11S01B  
* k2 means K2 US
* k2i means K2 GW
* dx means KDX US
* dxi means KDX GW
* dxg means KDX Graphite 
| &lt;!--Vendor ID--&gt;0x1949
| &lt;!--Product ID--&gt;0x0003
| &lt;!--Revision--&gt;100
| &lt;!--Access--&gt;2gb unless jb 
| &lt;!--Opinion--&gt;{{N/A|2010 untested Freescale i.MX31 }} the Kindle is a small computer running Linux 2.6 on an ARM processor
|-
| &lt;!--Description--&gt;AMAZON Kindle D00901 3rd Gen with keyboard - Menu, Settings for S/N and then Menu again to choose Update 
* S/N starts B006 means k3g aka K3 3G US 
* S/N starts B008 means k3w aka K3 WiFi 
* S/N starts B00A means k3gb aka K3 3G UK EU 
 - debug mode with ;debugON and ~help
| &lt;!--Vendor ID--&gt;0x1949
| &lt;!--Product ID--&gt;0x0004
| &lt;!--Revision--&gt;100
| &lt;!--Access--&gt;{{yes|4Gb internal no access until jailbroken JB}} 
| &lt;!--Opinion--&gt;2010 with mobi and azw3 formats only - micro usb 5v 0.85a - freescale i.mx35 ARM soc with 12bit parallel interface with epson e-ink cpu, 256MB synchronous dynamic RAM, 4GB eMMC internal memory only but no sd slot, MC13892 PMIC - atheros wifi 54mbit pci-e a e keyed wifi - ?? later models wm96103 audio codec - display has 2Mbit serial memory ic on ribbon cable with 4bpp inverse grayscale display not touchscreen - 3g module - screen replacement really annoying - 4 test points near T07 = TX RX GND ? - as of 2025, JB v0.13.N, MKK2014, MKK2025, KUAL, KoReader Legacy2025, and maybe later SS v0.47.N, Python 0.14.N, Fonts v5.16.N, USBNet v0.57.N - USB-downloader mode when Vol+ is pressed during startup - Shift + Alt + M for Minesweeper - 
|-
| &lt;!--Description--&gt;Amazon Kindle 4th Generation k4 D01100 two buttons, square movement and two buttons at bottom 
*B00E 
plastic back clipped in [https://www.youtube.com/watch?v=LV1dyNkjjro many places] and strongly taped down to battery cover 
| &lt;!--Vendor ID--&gt;0x1949
| &lt;!--Product ID--&gt;0x0005
| &lt;!--Revision--&gt;100
| &lt;!--Access--&gt;2gb unless jb with USB MS, USBMS aka also known as USB MSC or UMS
| &lt;!--Opinion--&gt;{{unk|2012 once back off use Torx T5 to remove battery cover screws - battery glued down S2011-001-A 515-1058-01 DR-A015 MC-265360 - Freescale i.MX508 SOC, 2Gb eMMC storage, 256MiB of LPDDR1, MC13892 PMIC - vendor modified u-boot imximage based on u-boot v2009.08 - USB-downloader mode press the fiveway down button during startup resetmykindle - as of 2025 upgrade firmware from 4.1.x and to 4.1.4, sign into account and copy jb.1.8 bits, mkk-2014, mkk-2025, kual and then uninstall kual, koreader2025 - }}
|-
| &lt;!--Description--&gt;Kindle Touch WiFi (Kindle 5th Gen) D01200 K5, KT
*Once signed into an Amazon Account get S/N under Settings -&gt; Device Options
*B00F 	Kindle Touch 3G + WiFi (Kindle 5) (U.S. and Canada) [Mostly]
*B011 	Kindle Touch WiFi (Kindle 5)
*B010 	Kindle Touch 3G + WiFi (Kindle 5) (Europe) 
| &lt;!--Vendor ID--&gt;0x1949
| &lt;!--Product ID--&gt;0x0006
| &lt;!--Revision--&gt;100
| &lt;!--Access--&gt;4gb unless jb 
| &lt;!--Opinion--&gt;{{unk|2013 touchscreen i.MX508 SOC, 256MiB of LPDDR1 and USB-downloader mode by the SOC microcode when a specific key is pressed during startup: the home button on model D01200 - update firmware 5.3.2 to 5.3.7.3, access account, }} 
|-
| &lt;!--Description--&gt;Kindle PaperWhite 3G + WiFi (U.S.) [Mostly] PW 
&lt;pre&gt;
B024 	Kindle PaperWhite WiFi 
B01B 	Kindle PaperWhite 3G + WiFi (U.S.) [Mostly]
B020 	Kindle PaperWhite 3G + WiFi (Brazil) 
B01C 	Kindle PaperWhite 3G + WiFi (Canada)
B01D 	Kindle PaperWhite 3G + WiFi (Europe)
B01F 	Kindle PaperWhite 3G + WiFi (Japan)
&lt;/pre&gt;
| &lt;!--Vendor ID--&gt;0x1949
| &lt;!--Product ID--&gt;0x0007
| &lt;!--Revision--&gt;100
| &lt;!--Access--&gt;2gb 
| &lt;!--Opinion--&gt;{{unk|2013 Freescale i.MX508 }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;0x1949
| &lt;!--Product ID--&gt;0x0008
| &lt;!--Revision--&gt;100
| &lt;!--Access--&gt;2gb 
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Kindle PaperWhite 2 (2013) PW2 
*B0D4, 90D4 WiFi (U.S., Intl.) 
*B05A, 905A WiFi (Japan)
*B0D5, 90D5 3G + WiFi (U.S.) [Mostly]
*B0D6, 90D6 3G + WiFi (Canada] 
*B0D7, 90D7 3G + WiFi (Europe)
*B0D8, 90D8 3G + WiFi (Russia)
*B0F2, 90F2 3G + WiFi (Japan)
*B017, 9017 WiFi (4GB) (U.S., Intl.)
*B060, 9060 3G + WiFi (4GB) (Europe)
*B062, 9062 3G + WiFi (4GB) (U.S.) [Mostly]
*B05F, 905F 3G + WiFi (4GB) (Canada)
*B061, 9061 3G + WiFi (4GB) (Brazil) 
| &lt;!--Vendor ID--&gt;0x1949
| &lt;!--Product ID--&gt;0x0009
| &lt;!--Revision--&gt;100
| &lt;!--Access--&gt;2gb or 4gb 
| &lt;!--Opinion--&gt;{{unk| PW2 uses Freescale/NXP i.MX6 SoloLite  }}
|-
| &lt;!--Description--&gt;Kindle Paperwhite 3 PW3 i.e. Kindle 7th gen 
*G090G1 (2015) WiFi 
*G090G2 (2015) 3G + WiFi (U.S.) [Mostly] 
*G090G4 (2015) 3G + WiFi (Mexico)
*G090G5 (2015) 3G + WiFi (Europe, Australia) 
*G090G6 (2015) 3G + WiFi (Canada)
*G090G7 (2015) 3G + WiFi (Japan) 
*G090KB (2015) WiFi 
*G090KC (2015) 3G + WiFi (Japan) 
*G090KE (2016) 3G + WiFi (International) White 
*G090KF (2016) 3G + WiFi (International) White 
*G090LK (2016) WiFi, 32GB (Japan) 
*G090LL (2016) WiFi, 32GB (Japan) White 
| &lt;!--Vendor ID--&gt;0x1949
| &lt;!--Product ID--&gt;0x000A
| &lt;!--Revision--&gt;100
| &lt;!--Access--&gt;4gb 
| &lt;!--Opinion--&gt;{{unk| ease up glued down front bezel rim panel gently, remove 11 screws underneath and lift screen up from bottom end - battery underneath -  }}
|-
| &lt;!--Description--&gt;Kindle PaperWhite 4 (2018) PW4
*G000PP, G8S0PP WiFi, 8GB
*G000T6, G8S0T6 WiFi, 32GB
*G000T1  WiFi+4G, 32GB
*G000T2  WiFi+4G, 32GB (Europe)
*G00102  WiFi, 8GB (India)
*G000T3  WiFi+4G, 32GB (Japan)
*G0016T, G8S16T WiFi, 8GB Twilight Blue
*G0016Q, G8S16Q WiFi, 32GB Twilight Blue
*G0016U  WiFi, 8GB Plum
*G0016V, G8S16V WiFi, 8GB Sage 
*G00103  WiFi, 32GB (India) 
*G0016R  WiFi, 32GB Plum
*G0016S  WiFi, 32GB Sage 
| &lt;!--Vendor ID--&gt;0x1949
| &lt;!--Product ID--&gt;0x000B
| &lt;!--Revision--&gt;100
| &lt;!--Access--&gt;8gb or 32gb
| &lt;!--Opinion--&gt;{{unk| Freescale/NXP i.MX6 SoloLite }}
|-
| &lt;!--Description--&gt;Kindle Oasis 2 and 3 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;8gb or 32gb
| &lt;!--Opinion--&gt;{{unk| NXP i.MX7D  }}
|-
| &lt;!--Description--&gt;Kindle Paperwhite 5 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;8gb or 16gb
| &lt;!--Opinion--&gt;{{unk| MediaTek MT8110  }}
|-
| &lt;!--Description--&gt;Kindle 11 Scribe 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;8gb or 16gb
| &lt;!--Opinion--&gt;{{unk| MediaTek MT8113 }}
|-
| &lt;!--Description--&gt;Kindle Paperwhite 6 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;16gb or 32gb
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Kindle Paperwhite Gen 11 and 12 - Signature 
| &lt;!--Vendor ID--&gt;0x1949
| &lt;!--Product ID--&gt;0x0
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;16Gb or 32Gb 
| &lt;!--Opinion--&gt;{{unk|2024 account not blocked,  }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;[https://github.com/Modos-Labs Modos Labs] open source e-ink 60Hz 75Hz caster controller and glider monitor 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Xteink X3 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;[https://www.xteink.com Xteink X4] 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;2025 4.3in 220ppi no touchscreen so [https://www.youtube.com/watch?v=R7RuokaVauo buttons navigation] - 650mAh battery - micro-sd slot up to 512Gb covering epub, txt, and jpg in directories with [https://github.com/crosspoint-reader crosspoint reader] esp32 cpu custom rom firmware using [https://xteink.dve.al/ Flash website] on usb-c but no ecosystem store 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|}


{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;15%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;5%&quot; |Product ID
! width=&quot;5%&quot; |Revision 
! width=&quot;15%&quot; |Access
! width=&quot;30%&quot; |Opinion
|-
| &lt;!--Description--&gt;Amazon D01400 Kindle Fire (1st Generation) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{No|2010 too old }} android 2.3 and touchscreen digitizer fails often, battery SWE P/N 1002000004742 Model KC1 (EU) QP01 (US) 16.28whr, ti 257epl9l omap 4430 with elpida 88164b3pf-10-f88164b3pf or hynix,  mobo ??,, DAOKC1MB8F0 Rev F, ti aic3110 audio codec, 
|-
| &lt;!--Description--&gt;Amazon Fire 7in X43260 X43Z60 2nd Gen 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk|2012 untested FireOS Android 4 omap 4460 and PowerVR SGX540}}
|-
| &lt;!--Description--&gt;Amazon Kindle Fire HD (3rd Gen) P48WVB4 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk|2013 untested }}
|-
| &lt;!--Description--&gt;Amazon 
*Amazon Fire HD10 (2015) 
*Amazon Fire HD8 (2015)	
*Amazon Fire HD7 (2015)	(5th Generation) 7 inch 8GB SV98LN 
*Amazon Fire HD7 (2014)	
*Amazon Fire HD6 (2014) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk|untested android 5.1 max}}
|-
| &lt;!--Description--&gt;
*Amazon Fire 10 (2017) 
*Amazon Fire 8 (2017) 7th Gen 8 inch SX034OT 
*Amazon Fire 7 (2017) (7th Generation) 7 inch 16GB (SR043KL) 
*Amazon Kindle Fire 7 (7th Generation) 7 inch 8GB WIFI Tablet (SR043KL) 
*Amazon Fire HD8 (2016)	
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| Android 5.1 max 7in screen resolution of 1024 x 600, }}
|-
| &lt;!--Description--&gt;
*Amazon Fire 10/10+ (2021) 
*Amazon Fire 8/8+ (2020) 
*Amazon Fire 10 (2019) 
*Amazon Fire 7 (2019) 
*Amazon Kindle Fire 7 9th Gen 16GB M8S26G 
*Amazon Fire 8 (2018) 8th Gen 8 inch 32GB L5S83A 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| android 9 max}}
|-
| &lt;!--Description--&gt;Amazon 
*Amazon Fire HD 10 (2023)	
*Amazon Fire Max 11 (2023)	
*Amazon Fire 8 (2022)	
*Amazon Fire 7 (2022)
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| android 11 max}}
|-
| &lt;!--Description--&gt;Amazon Kindle Scribe 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk|2025  }}
|-
| &lt;!--Description--&gt;Amazon 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Minimal Phone, Mudita Kompakt 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| eink }}
|-
| &lt;!--Description--&gt;Bigme B751C 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{N/A|2022 android untested }}
|-
| &lt;!--Description--&gt;Bigme B7 Pro 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk|2025  }}
|-
| &lt;!--Description--&gt;Bigme B6
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 android based color eink small - 300dpi b/w 150ppi color -}}
|-
| &lt;!--Description--&gt;Bigme 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| e-ink }}
|-
| &lt;!--Description--&gt;Bigme Hibreak Pro, Hisense A9
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| e-ink}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;iFlyTech AINote 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk|2024 }}
|-
| &lt;!--Description--&gt;iFlyTech AINote 2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk|2026 }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Meebook 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Onyx Boox Page Palma 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk|2016 android untested }}
|-
| &lt;!--Description--&gt;Onyx Boox Leaf3C
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Onyx Boox Go Color 7 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk|2023 untested 7in e-ink e-reader android tablet }}
|-
| &lt;!--Description--&gt;Onyx BooxTab Ultra X C 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Onyx Boox Note Max Air4 C 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Onyx Boox Leaf5C
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Onyx Boox Poke6S 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Onyx Boox Go 10.3 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Onyx Boox MC 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| color e-ink 13.3in }}
|-
| &lt;!--Description--&gt;Onyx Boox Go 10.3 (Gen 2) Lumi 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk|2026 b/w eink with front light, no EMR annd capacitance pen,  }}
|-
| &lt;!--Description--&gt;Onyx Moaan Pantone 6 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;reMarkable 1 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{N/A|2021 untested but subscriptions needed for some features }}
|-
| &lt;!--Description--&gt;reMarkable 2
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{N/A|2023 untested but subscriptions needed for some features }}
|-
| &lt;!--Description--&gt;reMarkable Paper Pro Move 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{N/A|2024 untested but subscriptions needed for some features }}
|-
| &lt;!--Description--&gt;reMarkable 3 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk|2026 untested but subscriptions needed for some features}}
|-
| &lt;!--Description--&gt;reMarkable 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Supernote A5 X2 Manta
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk|2022 }}
|-
| &lt;!--Description--&gt;Supernote A6 X2 Nomad 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk|2023  }}
|-
| &lt;!--Description--&gt;Supernote 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Tolino Vision 2 3 4 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Tolino Epos2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Viwoods AI Paper and AI Paper Mini 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Access--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|}


==printer.class==

As the only printer driver that AROS supports natively is Postscript, our focus is on applications that generally output postscript formatted data for printing purposes. 
There has been an attempt at recent AirPrint support 

*Inkjet 


*Laser 


Start simple and then test every higher level...

* can if you ping your printer (the IP addy is good)?
* set up LPR/IPP to talk to that known good IP address.
* see if you can copy a few words of plain ASCII text to the IPP/LPR device (do you have a connection)?
* see if you can find a simple postscript file and then copy it to the IPP/LPR device.
* see if you can set up to print directly to the IPP/LPR device (set &quot;Output file&quot; to PRT: or LPR:).
* see if you can set up a PS printer config to the IPP/LPR device.
* go back and try the tests with the other driver (LPR or IPP).


See [http://www.irseesoft.de/tp_drive7.htm here] for compatibility with TP7 (TurboPrint 7) Last update 2004. Not tested under emulation. Janus-UAE, Emumiga, Amiberry etc 


usbparallel.device

untested with USB-&gt;Centronics - The printer.class is rather 'clever'. It remembers to which unit the printers were connected (until you reboot). So if you first plug in Printer1, it gets unit 0, and Printer2 gets unit 1. If you now remove both printers and replug Printer2, it still will get unit 1 and not 0. This is used not to confuse the programs using the different units (moreover, if some program uses the usbparallel.device unit of an USB printer, and the printer is unplugged, the device unit cannot be freed immediately as the application still keeps it open). 


{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| Beige cream D shape centronics end (Prolific chipset?) 
| 
| 
| 
| {{N/A|untested}}
|-
| Belkin F5U002v1 centronics end (chipset?) 
| 
| 
| 
| {{N/A|untested}}
|-
| Belkin F5U002VEA v2 centronics end (Prolific PL2305L chipset) 
| 
| 
| 
| {{N/A|untested}}
|-
| DYNAMODE USB-C-PP-1284 USB to 36pin (Prolific 2305 chipset) 
| 0x067b
| 0x2305
| 0x02
| {{N/A|untested but similar to BAFO below}}
|-
| IOGear GUC1284B 
| 
| 
| 
| {{N/A|untested}}
|-
| My-Link (raised ellipse on centronics plastic end) (unknown chipset) 
| 
| 
| 
| {{N/A|untested but more expensive }}
|-
| NEWLink (Prolific chipset?) 
| 
| 
| 
| {{N/A|untested}}
|-
| Targus PA096E centronics end (chipset?) 
| 
| 
| 
| {{N/A|untested}}
|-
| TRENDnet ware TU-P1284
| 
| 
| 
| {{N/A|untested}}
|-
| True PnP (Prolific chipset 2305) cheap 36pin Centronics (series of ridges along both short sides) 
| 0x067b
| 0x2305
| 2.00
| {{N/A|untested on BAFO BF-1284 but reports of poor quality and lack of support on other OSs }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| Opinion 
|-
| Transparent See Through Blue 
| 
| 
| 
| {{N/A|untested but possible poor quality build }}
|-
| Dynamode USB-PARALLEL 25pin female (prolific) 
| 0x067b
| 0x2305 
| 0x02 
| {{N/A|untested}}
|-
| FDL USB to 25pin 
| 
| 
| 
| {{N/A|untested}}
|-
| PlusKom USB to 25pin female connector for printer (IEEE 1284) 
| 
| 
| 
| {{N/A|untested}}
|-
| QinHeng Electronics (CH340S chipset) 
| 0x1a86
| 0x7584
| 
| {{N/A|untested curvy sides - flat top }}
|-
| StarTech 
| 
| 
| 
| {{N/A|untested}}
|-
| Syba SD-USB-DB25 
| 
| 
| 
| {{N/A|untested}}
|-
|}


Postscript interpreters (eg ghostscript) have been developed as a cheaper option which sit in between postscript data streams and non postscript printers.

Ghostscript has internal printer drivers

 gs -h

and with something like

 gs -sDEVICE=stcolor -r300 -sOutputFile=RAM:tempfile gs813:examples/tiger.ps
 copytopar ram:tempfile

It checks if in RAM: exists a outputfile (Cinnamon can export to PS postscript) then it sends this via copytopar to the printer. There was only support for parport (parallel) but Terminillis added support for USB and ethernet. A big issue with using ghostscript for drivers is that data has to originate as postscript (.PS) file.

 gs -dSAFER -dBATCH -dNOPAUSE -sDEVICE=ljet4 -sOutputFile=RAM:tempfile RAM:file.pdf

the ljet4 output device generates PCL

also the pxlmono driver, which generates more generic PXL (PCL 6)

 gs -q -sstdout=%stderr -sDEVICE=pswrite -sOutputFile=- -dBATCH -dNOPAUSE -dPARANOIDSAFER testpage-a4.ps &gt; test.pdf

 gs -q -sstdout=%stderr -sDEVICE=pxlmono -sOutputFile=- -dBATCH -dNOPAUSE -dPARANOIDSAFER test.pdf &gt; test.pxl


Printers supported by ghostscript...Explanation [http://freebooks.by.ru/view/RedHatLinux6Unleashed/rhl6u151.htm here] or [http://www.gnu.org/software/ghostscript/devices.html here] and [http://pages.cs.wisc.edu/~ghost/doc/printer.htm here]

&lt;pre&gt;
bit            cljet5          ljet4d          pjxl300         pxlcolor
bitcmyk        cljet5c         ljetplus        pkm             pxlmono
bitrgb         deskjet         nullpage        pkmraw          stp
bj10e          djet500         pbm             pksm            tiff12nc
bj200          epswrite        pbmraw          pksmraw         tiff24nc
bjc600         faxg3           pcx16           png16           tiffcrle
bjc800         faxg32d         pcx24b          png16m          tiffg3
bmp16          faxg4           pcx256          png256          tiffg32d
bmp16m         ijs             pcxcmyk         pnggray         tiffg4
bmp256         jpeg            pcxgray         pngmono         tifflzw
bmp32b         jpeggray        pcxmono         pnm             tiffpack
bmpgray        laserjet        pdfwrite        pnmraw          uniprint
bmpmono        lj5gray         pgm             ppm             x11
bmpsep1        lj5mono         pgmraw          ppmraw          x11alpha
bmpsep8        ljet2p          pgnm            psgray          x11cmyk
cdeskjet       ljet3           pgnmraw         psmono          x11gray2
cdj550         ljet3d          pj              psrgb           x11gray4
cdjcolor       ljet4           pjxl            pswrite         x11mono
cdjmono
&lt;/pre&gt;


==rawwrap.class - some old flatbed scanners supported==

Scandal is the MUI frontend to [http://www.ppa.pl/bugtracker/ Betascan Bugtracker] and [http://aminet.net/search?query=betascan Search for Betascan scanner drivers] derived from [http://www.sane-project.org/sane-backends.html sane backends] 


[http://www.sane-project.org/sane-backends.html#S-EPSON2 Epson2] 
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| Expression 1600 1640XL 1680 10000XL
| 0x04b8
| 0x0107 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Prefection 1200U, 1200 Photo, 
| 0x04b8
| 0x0104
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Perfection 1240U
| 0x04b8
| 0x010b
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{[https://amigaworld.net/modules/newbb/viewtopic.php?topic_id=45760&amp;forum=25 works]|Needs 24V 0.8A psu but in Trident, click on &quot;Classes&quot;, then on &quot;rawwrap.class&quot;, then on &quot;Configure&quot;. There, under &quot;Global&quot;, activate the Option &quot;Bind to Vendor/Unknown Interfaces&quot;. Now go to the second tab &quot;Default Interface&quot; and select/enter these values: 
Default usbraw.device Unit: 0
Exclusive access: Yes
Out NAK Timeout: 20000ms
In NAK Timeout: 20000ms
In Buffer Mode: No buffering
Buffer Size: 36 KB
Short Reads Terminate: Yes
Now click on &quot;Use as Default&quot; and select &quot;Devices&quot; on the left. There, click on your scanner and click on &quot;Class Scan&quot;. Now close Trident by clicking on &quot;Save&quot;. }}
|-
| Perfection 1640SU Photo
| 0x04b8
| 0x010a
| 0x0104
| {{yes|works, even the transparency unit}}
|-
| Perfection 1650 Photo, 1660 Photo, 3200 Photo
| 0x04b8
| 0x011c
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Perfection 2400 Photo, 2450 Photo 
| 0x04b8
| 0x011b 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Perfection 4870 Photo, 4990 Photo, 
| 0x04b8
| 0x0128
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Perfection V700 V750 Photo
| 0x04b8
| 0x012c
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Stylus CX2800 2900 3200 3500 3600 3650 3700 3800 3900

Stylus CX4100 4200 3500 4600 4700 4800 4900 500 5100 5200 5300 5400 5900
| 0x04b8 
| 0x0802 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Stylus Office BX300F USB 
| 0x04b8
| 0x0848
| 
| {{yes| works with good scan quality}}
|-
|}


[http://www.meier-geinitz.de/sane/gt68xx-backend/ gt68xx] scanners based on the Grandtech GT-6801 and GT-6816 &quot;System-On-Chip&quot; scanner chipsets 
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| Artec Ultima 2000 and e+, Trust Flat Scan USB 19200 (ePlus2k.usb / Gt680xfw.usb) 
| 0x05d8
| 0x4002
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Genius Colorpage Vivid3x 4x 1200x
| 0x0458
| 0x2011 to 0x201f
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|  (ccd548.fw)}}
|-
| &lt;!--Description--&gt;Lexmark	X70	also X73 [http://subfusion.net/drivers/oslo3071b2.usb OSLO3071b2.usb]
| &lt;!--Vendor ID--&gt;0x043d
| &lt;!--Product ID--&gt;0x002d
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Medion/Lifetec/Tevion/Cytron MD/LT 9375 and Artec Ultima 2000, MD LT 9385 Gt680xfw.usb 
| &lt;!--Vendor ID--&gt;0x05d8
| &lt;!--Product ID--&gt;0x4002
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|-
| BearPaw 2448 CS and TA Plus [http://www.meier-geinitz.de/sane/gt68xx-backend/firmware/A2Nfw.usb A2Nfw.usb]
| 0x055f
| 0x021a
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2009  }}
|-
| Mustek BearPaw 1200 CS 
| 0x055f
| 0x021e
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|  ([http://www.meier-geinitz.de/sane/gt68xx-backend/firmware/A1fw.usb A1fw.usb])}}
|-
| &lt;!--Description--&gt;Mustek 1200 CU Plus Scanner [http://www.meier-geinitz.de/sane/gt68xx-backend PS1Dfw.usb / SBSfw.usb]
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2000 }}
|-
| Mustek ScanExpress 1200 UB plus, Trust Compact Scan USB 19200, ScanMagic 1200 UB Plus
| 0x05d8
| 0x4002 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|  ([http://www.meier-geinitz.de/sane/gt68xx-backend/firmware/sbfw.usb sbfw.usb])}}
|-
| Mustek ScanExpress 1248 UB aka PC-World PC Line PCL-3000 
| 0x055f
| 0x021f
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| ([http://www.meier-geinitz.de/sane/gt68xx-backend/firmware/SBSfw.usb SBSfw.usb])}}
|-
| Mustek BearPaw 2400CS TA aka Goodmans GSC 12/24
| 0x055f
| 0x0218
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| (Transparency adapter untested) }}
|-
| BearPaw 2400 CS aka TA Plus
| 0x055f
| 0x0219
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|  (Transparency adapter) }}
|-
| Packard Bell Diamond 1200 Plus
| 0x055f
| 0x021c or 0x021b 
| 0x0
| {{yes|works - [http://www.meier-geinitz.de/sane/gt68xx-backend/ firmware required] but slow usb 1.1 speed with poor quality output (scanner fault not scandal)}}
|-
| Packard Bell Diamond 2400 Plus aka BearPaw 2400 CU Plus [http://www.meier-geinitz.de/sane/gt68xx-backend/ PS2Dfw2.usb firmware rename to PS2Dfw.usb]
| 0x055f
| 0x021d 
| 1.00
| {{yes|works slow usb 1.1 speed with ok quality output (scanner fault not scandal)}}
|-
| Plustek OpticPro 1248U
| 0x07B3
| 0x0400 0x0401
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| (ccd548.fw)}}
|-
| Plustek OpticSlim 2400
| 0x07b3
| 0x0422
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|  (cis3R5B1.fw)}}
|-
| Visioneer OneTouch 7300
| 0x04a7
| 0x0444
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|  (Cis3r5b1.fw)}}
|-
| &lt;!--Description--&gt;Mustek ScanEpress 1200 UB (Plus) clone [http://www.meier-geinitz.de/sane/ use mustek_usb backend]
| &lt;!--Vendor ID--&gt;0x055f
| &lt;!--Product ID--&gt;0x0006
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
|}


Lexmark - needs testing
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| Lexmark X1110 
| 
| 
| 
| {{N/A|untested}}
|-
| Lexmark X1140
| 
| 
| 
| {{N/A|untested}}
|-
| Lexmark X1150 
| 
| 
| 
| {{N/A|untested}}
|-
| Lexmark X1170 
| 
| 
| 
| {{N/A|untested}}
|-
| Lexmark X1180 
| 
| 
| 
| {{N/A|untested}}
|-
| Lexmark X1185
| 0x043d
| 0x007c
| 
| {{N/A|untested}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Lexmark X12xx 
| 
| 
| 
| {{N/A|untested in USB1.1, not fully tested in USB2.0}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Opinion 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Dell A920 
| 
| 
| 
| {{N/A|untested}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
|}


HP - no driver
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| HP ScanJet 4100C
| 0x03f0 
| 0x0101
| 
| {{no|no driver}}
|-
| HP ScanJet 5200C
| 0x03f0 
| 0x0401
| 
| {{no|no driver}}
|-
| HP ScanJet 62X0C
| 0x03f0 
| 0x0201
| 
| {{no|no driver}}
|-
| HP ScanJet 63X0C
| 0x03f0 
| 0x0601
| 
| {{no|no driver}}
|-
| HP  
| 0x03f0
| 0x0102, 0x0105, 0x0205, 0x0305, 0x0405
| 
| {{no|no driver}}
|-
| HP
| 0x03f0
| 0x0705, 0x0805, 0x0901, 0x0a01
| 
| {{no|no driver}}
|-
| HP
| 0x03f0
| 0x1205, 0x1305, 0x2005, 0x2205
| 
| {{no|no driver}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
|}


Plustek [http://www.sane-project.org/sane-backends.html#S-PLUSTEK LM983x] - no driver
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| Plustek OticPro U12 UT12 UT16 U24 UT24
| 0x07B3
| 0x0010 to 0x0017
| 
| {{no|no driver}}
|-
| KYE/Genius Colorpage HR6-V2 HR6A HR7 HR7LE HR6X
| 0x0458
| 0x2008 to 0x2016 
| 
| {{no|no driver}}
|-
| Hewlett-Packard ScanJet 2100C and 2200C
| 0x03F0
| 0x0505 and 0x0605
| 
| {{no|no driver}}
|-
| Mustek BearPaw 1200 and 2400 
| 0x0400 	
| 0x1000 and 0x1001
| 
| {{no|no driver}}
|-
| UMAX 3400/3450 and 5400 	
| 0x1606
| 0x0050, 0x0060 and 0x0160 
| 
| {{no|no driver}}
|-
| Epson Perfection 1250 and 1260
| 0x04B8
| 0x010f and 0x011d
| 
| {{no|no driver}}
|-
| CANON CanoScan N650/656U N1220U D660U N670/676U N1240U LIDE20 LIDE25 LIDE30
| 0x04A9
| 0x2206 to 0x2220
| 
| {{no|no driver}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|}


[http://snapscan.sourceforge.net/ SnapScan] - no driver
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| Acer Benq 310U, 320U, 340U
| 0x4a5
| 0x0
| 
| {{no|no driver}}
|-
| Acer Benq 620U, 620UT, 640U, 640UT
| 0x4a5
| 0x20
| 
| {{no|no driver}}
|-
| Acer Benq 1240 3300 4300
| 0x4a5
| 0x020
| 
| {{no|no driver}}
|-
| Agfa SnapScan e10 e20 e25 e26 e40 e42 e50 e52
| 0x06bd
| 0x20
| 
| {{no|no driver}}
|-
| Epson Perfection 660
| 0x04b8
| 0x0114
| 
| {{no|no driver}}
|-
| Epson Perfection 1270 1670
| 0x04b8
| 0x0
| 
| {{no|no driver}}
|-
| Epson Perfection 2480 2580
| 0x04b8
| 0x0
| 
| {{no|no driver}}
|-
| Epson Perfection 3490 3590
| 0x04b8
| 0x0
| 
| {{no|no driver}}
|-
| Mitsubishi
| 0x0
| 0x0
| 
| {{no|no driver}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
|}

==hub.class (self-powered and external ac powered hubs)==

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;Dynamode USB-H41 4 ports 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Opinion 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Belkin 4 Port 
| 
| 
| 
| {{yes|works}}
|-
| Conrad
| 
| 
| 
| {{yes|[http://www.a1k.org/forum/showthread.php?t=11432 works on a1k forum] }}
|-
| DLink DUB-H4 AC Adapter 
| 0x05e3
| 0x0608
| High 0200
| {{maybe|WARNING Genesys Logic Hub Broken - Will cause failures with USB}}
|-
| [http://service.targa.co.uk/faq.php?lang_id=2&amp;baseid=178&amp;artdesc=SilverCrest+USB+Hub+2040&amp;artid=760&amp;artpic=silvercrestHUB2040.jpg SilverCrest 4-port slim USB 2.0 HUB - HUB2040 (40775) - Targa GmbH]
| 0x05e3
| 0x0608
| 0901
| {{yes|works  Genesys Logic, Inc., [http://service.targa.co.uk/dokumente/USB_HUB_2040_0109_manual_EN.pdf Manual]}}
|-
| Skymaster
| 0x05e3
| 0x0605
| 060B
| {{yes|works}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| No Name active 4-port
| 0x1a40
| 0x0101
| 0111
| {{yes|works}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Opinion 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Thinkpad USB 3.0 Dock DU9019D1 
| &lt;!--Vendor ID--&gt;0x17e9
| &lt;!--Product ID--&gt;0x4302
| &lt;!--Revision--&gt;0014
| &lt;!--Opinion--&gt;{{Maybe|works a bit}} classed as dfu.class with two further USB 2.0 hubs - USB 3.0 ports detected and work (2.0 backwards compatibility) - DisplayLink DL-3900 with VIA VL811 chipset - usb ethernet not working - two dvi not working - 20V psu 2a (40w) with a 5.5 - 2.5mm tip (no bus power) - data through a-b printer/scanner usb lead - 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Opinion 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|-
|}


==Internet==

===rndis.class USB Tethering ===

The rndis class provides support for Ethernet access over Remote NDIS. Most USB based devices should be supported including smartfones.

Before opening Network Prefs, activate USB Tethering on the Smartfon, on Network prefs, type in usbrndis.device and tick &quot;Start Network during system boot&quot; and saved the configuration, the Connection is immediate no reboot is needed.

When restart AROS my Smartphone deactivates the connection and to access the network again, have to reactivate it before starting the browser.

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;Alcatel 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{yes|untested}}
|- 
| Huawei U8800
| 0x12d1
| 0x1039
| 
| {{yes|works}}
|- 
| &lt;!--Description--&gt;Huawei
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{yes|untested}}
|- 
| HTC (Android phone)
| 0x0bb4
| 0x0ffe
| 
| {{Yes|any android phone with usb tethering option}}
|- 
| &lt;!--Description--&gt;Nokia 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{yes|untested}}
|- 
| &lt;!--Description--&gt;Oppo 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{yes|untested}}
|- 
| &lt;!--Description--&gt;Samsung Galaxy 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{yes|untested}}
|- 
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| Opinion 
|-
|- 
| &lt;!--Description--&gt;iPhone
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|- 
| &lt;!--Description--&gt;Microsoft winPhone
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|}


===USB &amp;rarr; ethernet lan adaptor===

*2002 playstation 2 usb1.1 era - a little support but very old and slow 
*2006 wii asix era - a little support but very much miss than hit 
*2026 usb0: or eth0: of CDC Ethernet protocol (cdcether) with Ethernet Control Model (ECM) and [https://www.usb.org/document-library/class-definitions-communication-devices-12 others like Wireless Mobile Communication Devices WMC] and later CDC EEM (Ethernet Emulation Model) and NCM (Network Control Model) are USB Communication Device Class (CDC) protocols packing more Ethernet traffic over every USB bundle. For CDC Ethernet - NCM is better than EEM is better than ECM 


* USB1.1 Up to 010 meg broadband (1.25MBytes/s) - ADM8511, DM9601 poor speeds 
* USB2.0 Up to 400 meg broadband (60MBytes/s) - MCS7830, AX88772 a little especially the 2010 apple version but buy many as very very poor odds of working one 
* USB3.0 Over 400 meg broadband (60+MBytes/s) - not supported at the moment 


SANA (Standard Amiga Network Architecture) to usb 

ADMtek Infineon ADM8511 Pegasus II (USB 1.1 and 10Mbit/s - Sony PlayStation 2 network adapter) 
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;5%&quot; |Product ID
! width=&quot;5%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| 3Com 3c460b 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2001 }}
|-
| Abocom UFE1000 / Abocom DSB650TX
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Accton USB320-EC / Accton SpeedStream Ethernet
| 0x083a
| 0x0320
| &lt;!--Revision--&gt;
| {{unk|2002 }}
|-
| AEI USB Fast Ethernet / Allied Telesyn AT-USB100 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2002 }}
|-
| ATEN UC-110T
| 0x0557
| 0x4000
|
| {{unk|2001 }}
|-
| BAFO USB To Ethernet Adapter BF-310
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2001 }}
|-
| Belkin F5D5050 v1 1101 
| 0x050D
| 
| &lt;!--Revision--&gt;
| {{maybe|2002 sometimes works from old amiga.org post which is now removed}}
|-
| Belkin F5D5050 v2 2101
| 0x050D
| 0x0121
| &lt;!--Revision--&gt;
| {{no|2006 does not works}} 
|-
| Belkin F5U122-PC
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Billionton USB-100 / Billionton USBLP-100
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Billionton USBEL-100 / Billionton USBE-100
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Compex LinkPort/UE202A
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| D-Link DSB-H3ETX
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| D-Link DSB-650 / D-Link DSB-650TX / D-Link DSB-650TX-PNA
| 0x2001
| 0x4000
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| D-Link DU-E10 / D-Link DU-E100
| 0x2001
| 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Edimax USB Ethernet Adapter EU-4201 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Elsa AG MicroLink USB2 Lan Ethernet adapter
| 0x05cc
| 0x3000
| &lt;!--Revision--&gt;1.01
| &lt;!--Opinion--&gt;{{unk| }}
|-
| GetNet
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| GIGABYTE GN-BR402W Wireless Router
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Goodway Fellowes USB UE-120 REV:V1 UE120 ADMTek 1011594 HO2419741 
| &lt;!--Vendor ID--&gt;0x07a6
| &lt;!--Product ID--&gt;0x0986
| &lt;!--Revision--&gt;0001
| &lt;!--Opinion--&gt;{{maybe|2001 USB Specification 1.1 compliant}} 
|-
| GWC Tech USB Ethernet Adapter
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Hawking UF100
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| HP HN210E / I/O DATA USB ETTX / Kingston KNU101TX
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Jinco USB Ethernet Adapter 10/100 Base-T UE-110
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Kouwell USB to Ethernet 588A
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Linksys USB10T / TA / TX
| 0x066b
| 0x2202
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|untested - possible peg1/peg2}}
|-
| Linksys (Cisco) USB100TX / H1
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Logitec LAN-TX/U1 H2
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| [http://www.mayflash.com/psps2/ps2024/ps2024.htm Mayflash PS2024] Playstation2 compatible clone of Proxim/Farallon NetLine?
| 0x07a6
| 0x8511
| &lt;!--Revision--&gt;1.01
| &lt;!--Opinion--&gt;{{maybe|works with DHCP router option on old 32bit distros but not on newer 64bit, best to go asixeth apple 2010 but buy many of them as poor success rate i.e. a lottery}}
|-
| Netgear FA101
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Philips CPWUE01/00 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Planet UE-9500 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| PlayStation 2 SCPH-10000 50000 models 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Proxim (formerly Farallon) NetLine USB PN796-650
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Siemens SpeedStream USB
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| SOHOware NUB100 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| SMC EZNET-USB 2202USB/ETH / SMC 2206USB/ETH
| 0x0707
| 0x0100 0x0200 0x0201
| &lt;!--Revision--&gt;
| {{unk|untested but should work very well }}
|-
| Surecom EP-1427X 100/10M
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Target USB to 10/100M Fast Ethernet Converter
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Trendnet TU-ET100C
| 0x07a6
| 0x8511 
| &lt;!--Revision--&gt;0x0
| {{yes| sometimes works well, very stable}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Opinion 
|-
| &lt;!--Description--&gt;Digitus USB NIC DN-3016-A 
| 0x07a6
| 0x8513
| 1.01
| {{unk|untested new chipset }}
|-
| Digitus lanusb ADM8515
| 0x07a6
| 0x8515
| 1.01
| {{unk|untested because new chipset }}
|-
| VE285 usblan ADMtek 8515 
| 0x07a6
| 0x8515
| 1.01
| {{no|not working as new chipset }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
|}


Davicom DM9601 eth (USB 1.1 and up to 10Mbit/s) 
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| Davicom USB-100 see clone below 
| 0x0a46
| 0x9601
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2001 }}
|-
| [http://wiki.maemo.org/USB_to_ethernet_networking chinese translucent transparent crystal blue] but variants are also found in clear, white and black. Just over 6&amp;nbsp;cm long. 
| 0x0a46
| 0x9601
| 0x0
| {{yes|2002 success can be sporadic so technically okay, but lacking in reliability. Out of 4 tested by me, only 2 worked. One case cracked open. }}
|-
| Corega FEther USB-TXC
| 0x07aa
| 0x9601
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Dynamode USB-NIC-1427-100
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Hirose USB-100
| 0x0a47
| 0x9601
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| KY-RS9600
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{yes|[http://www.amiga.org/forums/showpost.php?p=585358&amp;postcount=12 works] }}
|-
| ShanTou ST268 USB NIC
| 0x0a46
| 0x0268
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| ZT6688 USB NIC 
| 0x0a46
| 0x6688
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;ICS Advent DM9601 USB 2.0 10/100M Ethenet Adaptor JP1081B 
| &lt;!--Vendor ID--&gt;0x0FE6
| &lt;!--Product ID--&gt;0x9700
| &lt;!--Revision--&gt;0101
| &lt;!--Opinion--&gt;{{No|not working 32bit and 64bit - USB 1.1 10M ethernet}} 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|-
|}


MosChip MCS7830 (USB 2)
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| Digitus DN-10050
| 0x9710
| 0x7830
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2004 }}
|-
| Edimax [http://www.edimax.co.uk/images/Image/datasheet/USB/EU-4206/EU-4206.pdf EU-4206]
|
| 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2005 }}
|-
| Speed Dragon 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| STLabs 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| StarTech Compact USB2105S [http://www.kustompcs.co.uk/acatalog/info_6790.html USB2106S]
| 0x9710
| 0x7830
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2007 }}
|-
| Sunrich Technologies [http://www.st-lab.com/admin/upfile/UploadFile/manual/manual(u-250).zip U-250]
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2006 }}
|-
| Syba 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| Opinion 
|-
| &lt;!--Description--&gt;MCS 7832 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|2008 }} 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|-
|}


* USB2 [https://www.asix.com.tw/en/product/USBEthernet Asix Ethernet] AX88178A, AX88772C, AX88772B, AX88772A (wii), AX88172A 
* USB3 AX88179A, AX88179  

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| AirLink101 AGIGAUSB 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2009  AX88172}}
|-
| ATEN UC210T 
| 0x0557
| 0x2009
| 0x
| &lt;!--Opinion--&gt;{{unk| AX88172}}
|-
| &lt;!--Description--&gt;Billionton Systems USB2AR
| &lt;!--Vendor ID--&gt;0x08dd
| &lt;!--Product ID--&gt;0x90ff
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| }}
|-
| &lt;!--Description--&gt;Buffalo LUA-U2-KTX
| &lt;!--Vendor ID--&gt;0x0411
| &lt;!--Product ID--&gt;0x003d
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| }}
|-
| &lt;!--Description--&gt;corega FEther USB2-TX
| &lt;!--Vendor ID--&gt;0x07aa
| &lt;!--Product ID--&gt;0x0017
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no| }}
|-
| D-Link DUB-E100 up to rev A4
| 0x2001
| 0x1a00
| 
| &lt;!--Opinion--&gt;{{No| }}
|-
| &lt;!--Description--&gt;D-Link DUB-E100 rev B1 onwards 
| 0x07d1 or 0x2001 
| 0x3c05
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{Maybe|AX88172 works on Deneb with [http://amigax.com/2010/02/21/usb-ethernet-speed-test-amigaos-4-0-classic/ Amiga OS4 Classic] and [http://www.a1k.org/forum/showthread.php?t=11432 on a1k] }}
|-
| &lt;!--Description--&gt;goodway corp USB gwusb2e
| &lt;!--Vendor ID--&gt;0x1631
| &lt;!--Product ID--&gt;0x6200
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Hawking UF200 
| 0x07b8
| 0x420a 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;[Linksys USB200M] 
| 0x077b
| 0x2226
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{yes|[http://www.amiga.org/forums/showpost.php?p=585601&amp;postcount=20 works] }}
|-
| &lt;!--Description--&gt;Netgear FA120 
| 0x0846 
| 0x1040
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested 2002 10/100 Rev.B1&quot; is silkscreened on the board of the device populating this entry (S/N: FA12254CB100409, date code 0508). This device may be manuf. by [http://www.cameo.com.tw/ Cameo] &quot;AX88172 L&quot;, &quot;F05040157&quot;, and &quot;ED3&quot; Chip1 ASIX AX88172  Chip2 Realtek RTL8201BL}}
|-
| &lt;!--Description--&gt;Intellinet
| 0x0b95 
| 0x1720
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;JVC MP-PRX1 Port Replicator
| &lt;!--Vendor ID--&gt;0x04f1
| &lt;!--Product ID--&gt;0x3008
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;ST Lab USB Ethernet
| &lt;!--Vendor ID--&gt;0x0b95 
| &lt;!--Product ID--&gt;0x1720
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Sitecom LN-029 &quot;USB 2.0 10/100 Ethernet adapter&quot;
| &lt;!--Vendor ID--&gt;0x6189
| &lt;!--Product ID--&gt;0x182d
| &lt;!--Revision--&gt;0
| &lt;!--Opinion--&gt;{{No| }}
|-
| &lt;!--Description--&gt;Surecom EP-1427X-2
| &lt;!--Vendor ID--&gt;0x1189
| &lt;!--Product ID--&gt;0x0893
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| }}
|-
| &lt;!--Description--&gt;TrendNet TU2-ET100 v2
| 0x07b8
| 0x420a 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{Maybe|version 2}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| Opinion 
|-
| &lt;!--Description--&gt;A-LINK NA1GU 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| 88772}}
|-
| &lt;!--Description--&gt;AirLink101 ASOHOUSB Wii 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;AirLive EtherWe-1000U 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;APPLE AX88772 Model No. A1277 MC704LL/A P/N 825-7098-A 
| &lt;!--Vendor ID--&gt;0x05ac 
| &lt;!--Product ID--&gt;0x1402
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|2008  usb2, }}
|-
| &lt;!--Description--&gt;APPLE Model No. A1277 (MB442Z/A 0885909217434) MC704ZM/A PN 825-7579-A 
| &lt;!--Vendor ID--&gt;0x05ac 
| &lt;!--Product ID--&gt;0x1402
| &lt;!--Revision--&gt; 
| &lt;!--Opinion--&gt;{{Maybe|2010 model, usb2 and controller AX88772 where prehaps 1in3 units working with owb - really poor odds i.e. a lottery, could be situation where various ethernet phy chipsets are used - press Use in network prefs after Save initial setup typing in usbasixeth.device, }}
|-
| &lt;!--Description--&gt;ASIX AX88772 bulbous casing 
| &lt;!--Vendor ID--&gt;0x0b95
| &lt;!--Product ID--&gt;0x7720 
| &lt;!--Revision--&gt;0x0
| &lt;!--Opinion--&gt;{{maybe|2008 works on 32bit and 64bit though setup can take a few attempts but may have issues with phy ethernet chip changing,  }}
|-
| &lt;!--Description--&gt;Datel Wii Lan Adapter DUS0204 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2007 }}
|-
| &lt;!--Description--&gt;EdiMax EU-4207 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2008 }}
|-
| &lt;!--Description--&gt;Goodway HE2230 Maplin ASIX 88772 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2008 }}
|-
| &lt;!--Description--&gt;Intec LAN G5626 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2008 }}
|-
| &lt;!--Description--&gt;LevelOne USB-0202
| 0x0b95
| &lt;!--Product ID--&gt;0x07720
| &lt;!--Revision--&gt;0x
| &lt;!--Opinion--&gt;{{unk|2008 }}
|-
| &lt;!--Description--&gt;LevelOne USB-0301
| 0x0b95
| &lt;!--Product ID--&gt;0x07720
| &lt;!--Revision--&gt;0x
| &lt;!--Opinion--&gt;{{unk|2009 }}
|-
| &lt;!--Description--&gt;Linksys USB200M Rev 2
| &lt;!--Vendor ID--&gt;0x13b1
| &lt;!--Product ID--&gt;0x0018
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{maybe|2008 sparsely randomly working AX88772 or with &quot;Sana-II Meter Tool 37.11&quot; network monitoring program, showing continuous &quot;Bad Packet&quot; errors which could means &quot;CRC&quot; errors}}
|-
| &lt;!--Description--&gt;Linksys USB300M 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{maybe|2009 AX88772  }}
|-
| &lt;!--Description--&gt;Mayflash W001 or clones Lupo/PEGA S-Wii-0680 light gray rectangular with third of one top 45 degree angled slope
| &lt;!--Vendor ID--&gt;0x0b95
| &lt;!--Product ID--&gt;0x7720 
| &lt;!--Revision--&gt;0x0
| &lt;!--Opinion--&gt;{{unk| may have randomly changed phy ethernet chips, }}
|-
| &lt;!--Description--&gt;Max Value MVF00446 ASIN B006EG568A 
| &lt;!--Vendor ID--&gt;0x0b95
| &lt;!--Product ID--&gt;0x7720 
| &lt;!--Revision--&gt;0x0
| &lt;!--Opinion--&gt;{{Maybe|Trident prefs recognises as AX88772 sometimes works on 32bit and 64bit}} 
|-
| &lt;!--Description--&gt;NEWLink N14050 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;NEWLink Wii-ETH USB2.0
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Nintendo Wii LAN Adaptor 2110566 and clones 
| &lt;!--Vendor ID--&gt;0x0b95
| &lt;!--Product ID--&gt;0x07720
| &lt;!--Revision--&gt;0x
| &lt;!--Opinion--&gt;{{Maybe|Poseidon recognises as AX88772 with usbasixeth.device sometimes works seems different ethernet phy chips can be matched affecting compatibility}} 
|-
| &lt;!--Description--&gt;Nyko Wii Net Connect 87024
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{yes|[http://www.amiga.org/forums/showpost.php?p=585624&amp;postcount=22 works] }}
|-
| &lt;!--Description--&gt;0Q0 cable ethernet
| &lt;!--Vendor ID--&gt;0x1557
| &lt;!--Product ID--&gt;0x7720
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Plugable USB2-E100 (2009/2010) Bulbous housing 
| &lt;!--Vendor ID--&gt;0x0b95
| &lt;!--Product ID--&gt;0x7720 
| &lt;!--Revision--&gt;0x0
| &lt;!--Opinion--&gt;{{Maybe|Trident prefs recognises it as ax88772A and typing in usbasixeth.device sometimes works}}
|-
| &lt;!--Description--&gt;Sabrent KINAMAX 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;SpeedLink SL-3401-SGY 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;TrendNet TU2-ET100 v3
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;UGreen 20254 USB2 to 10/100 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| AX88772}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| Opinion 
|-
| &lt;!--Description--&gt;Afunta Apple-style White USB2.0 I/O Crest SY-ADA24005 ASIX Electronics Corp. AX88772A Fast Ethernet Adapter 
| &lt;!--Vendor ID--&gt;0x0b95
| &lt;!--Product ID--&gt;0x772a
| &lt;!--Revision--&gt;0x
| &lt;!--Opinion--&gt;{{no|usbasixeth.device accepted by network prefs but does not work}}
|-
| &lt;!--Description--&gt;Amazon Basics USB 2.0 AX88772A
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Digitus DN-10050-1
| &lt;!--Vendor ID--&gt;0x0b95
| &lt;!--Product ID--&gt;0x772a
| &lt;!--Revision--&gt;0x0 
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Edimax EU-4230  
| &lt;!--Vendor ID--&gt;0x0b95
| &lt;!--Product ID--&gt;0x772a
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Sabrent KINAMAX NT-USB20 AX88772A 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| Opinion 
|-
| &lt;!--Description--&gt; AX88772B USB 2.0 to 10/100M 
| &lt;!--Vendor ID--&gt;0x0B95
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2010  }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;0x0B95
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;EdiMax EU-4208 
| &lt;!--Vendor ID--&gt;0x0B95
| &lt;!--Product ID--&gt;0x772b
| &lt;!--Revision--&gt;0x
| &lt;!--Opinion--&gt;{{No|Detected but not working}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;0x0B95
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;StarTech USB2100 ASIX AX88772C 
| &lt;!--Vendor ID--&gt;0x0B95
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;0x0B95
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;[https://www.asix.com.tw/en/product/USBEthernet/High-Speed_USB_Ethernet/AX88772D AX88772D]
| &lt;!--Vendor ID--&gt;0x0B95
| &lt;!--Product ID--&gt;0x1790
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2011 }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;0x0B95
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;[https://www.asix.com.tw/en/product/USBEthernet/High-Speed_USB_Ethernet/AX88772E AX88772E]
| &lt;!--Vendor ID--&gt;0x0B95
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2012 }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;0x0B95
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| Opinion 
|-
| &lt;!--Description--&gt;AX88178 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|2004 }} 
|-
| &lt;!--Description--&gt;Plugable USB2-E1000 i.e. USB 2.0 to Gigabit Ethernet 10/100/1000 LAN 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2011 ASIX AX88178 Controller and Realtek RTL8211CL PHY}}
|-
| &lt;!--Description--&gt;AX88178A USB 2.0 to 10/100/1000M Gigabit Ethernet controller 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|2005 }} 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|-
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| Opinion 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;AmazonBasics USB3.0 adapter [https://github.com/nothingstopsme/AX88179_178A_Linux_Driver AX88179] 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Cable Matters SuperSpeed USB 3.0 RJ45 adapter 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Hori Nintendo Switch 1 USB3 ethernet AX88179 
| &lt;!--Vendor ID--&gt;0x0b95
| &lt;!--Product ID--&gt;0x1790
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|2017 AX88179 not binding to asixeth.class }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Plugable USB3-E1000  
| &lt;!--Vendor ID--&gt;0x0b95
| &lt;!--Product ID--&gt;0x1790
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|2020 ASIX AX88179 not binding to class, USB 3.2 Gen1 to Gigabit Ethernet controller with integrated 10/100/1000Mbps Gigabit Ethernet PHY}}  
|-
| &lt;!--Description--&gt;Plugable AX88179 = [https://plugable.com/products/usb3-e1000-deal USB3-E1000] before mid-2023 or USB3-E1000; AX88179A = USBC-E1000 after mid-2023
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2022  controller is AX88179 phy is ??, }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;StarTech USB31000SPTW ax88179 
| &lt;!--Vendor ID--&gt;0x0b95
| &lt;!--Product ID--&gt;0x1790
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no| AX88179 not binding to asixeth.class, }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;StarTech USB31000NDS AX88179 USB-A
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;StarTech US1GC301AU AX88179 USB-c
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;StarTech US1GC30B2 AX88179A USB-c
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;StarTech USB32000SPT AX88179A USB-c Rev 1 (AX88179) Rev 2 (AX88179A) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;USB32000SPT the Lot code sticker will have a bar code accompanied by a 10 digit number. The 5th and 6th digits of this lot code number would signify the revision. (Ex. xxxx02xxxx which would indicate rev. 2)
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;SYBA SY-ADA24029 Gigabit AX88179 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| }} may depend on the PHY chip connected to the controller chipset
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;TP-Link UE306 AX88179 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;TeckNet® Orico UL677G 10/100 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;TeckNet® UL688G USB 3.0 10/100/1000 Base-T Ethernet port 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;AX88179 178A 
|-
| &lt;!--Description--&gt;Tecknet UL699G 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;TrendNet TU2-ET100 v6 
| &lt;!--Vendor ID--&gt;0x07b8
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|no support }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;uGreen 50922 USB3-A to 100/1000 dark grey rounded barrels 
| &lt;!--Vendor ID--&gt;0x0b95
| &lt;!--Product ID--&gt;0x
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no| ax88179 not binding to asixeth.class, }}
|-
| &lt;!--Description--&gt;UGreen USB3-C to 100/1000 
| &lt;!--Vendor ID--&gt;0x0b95
| &lt;!--Product ID--&gt;0x1790
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;uGreen CR111 20256 usb3 a black plastic 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| AX88179}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| Opinion 
|-
| &lt;!--Description--&gt;  AX88179A 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Plugable USB3-E1000 USBC-E1000 after mid-2023 i.e. AX88179A 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;StarTech USB31000SPTB 
| &lt;!--Vendor ID--&gt;0x0b95
| &lt;!--Product ID--&gt;0x1790
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|  AX88179A USB-A, }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| Opinion 
|-
| &lt;!--Description--&gt;  AX88179B
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|}


==USB  &amp;rarr; SerialPort Converter==

*2002 some support for early revisions of PL2303 
*2005 Prolific PL2303H PL-2303X and Pl-2303HX (same usb ids as pl2303) no support 
*2025 FTDI 232R [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1135&amp;highlight=232r&amp;rowstart=20 work in progress] 
*2026 CDC-ACM i.e. Serial port over USB standard 

serialpl2303.class make sure you specify serialpl2303.device or Echo &quot;Test&quot; &gt;SER1: 

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| ATEN UC-232A 
| 0x0557 
| 0x2008 
| Full 0x0300
| {{N/A|untested}}
|- 
| IOGear GUC232A 
| 0x0557  
| 0x2008 
| Full 0x0110
| {{N/A|untested}}
|- 
| Alcatel 
| 0x11f7 
| 0x02df 
|
| {{N/A|untested}}
|- 
| BAFO BF-810 
| 0x067B  
| 0x2303 
| 0x0
| {{N/A|untested}}
|- 
| Belkin F5U103 
| 0x
| 0x
| 0x0
| {{N/A|untested}}
|- 
| Davibe SP611 
| 0x067B 
| 0x2303 
| 0x0 
| {{N/A|untested}}
|- 
| Dcu10 
| 0x0731
| 0x0528
| 
| {{N/A|untested}}
|- 
| Elcom 
| 0x056e
| 0x5003
| 
| {{N/A|untested}}
|- 
| IOData 
| 0x04bb 
| 0x0a03 
| 0x0
| {{N/A|untested}}
|- 
| Itegno 
| 0x0eba
| 0x1080
| 
| {{N/A|untested}}
|- 
| Nokia CA42 
| 
| 
| 
| {{N/A|untested}}
|- 
| Radioshack 
| 0x1453
| 0x4026
| 
| {{N/A|untested}}
|- 
| Ratoc 
| 0x0584
| 0xb000
| 
| {{N/A|untested}}
|- 
| Samsung 
| 0x04e8
| 0x8001
|
| {{N/A|untested}}
|- 
| Siemens DCA-510 
| 0x067B 
| 0x2303 
| 0x0 
| {{N/A|untested}}
|- 
| Sitecom CN104
| 0x6189
| 0x2068
|
| {{N/A|untested}}
|- 
| Sitecom CN116 
| 0x6189
| 0x2068
|
| {{N/A|untested}}
|- 
| Some Cut Ma620 
| 0x0df7
| 0x0620
| 
| {{N/A|untested}}
|- 
| Speed Dragon Multimedia MS3303H 
| 
| 
| 
| {{N/A|untested}}
|- 
| Syntech 
| 
| 
| 
| {{N/A|untested}}
|- 
| &lt;!--Description--&gt;Tripp 
| 0x2478
| 0x2008
| 
| {{N/A|untested}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| Opinion 
|-
| &lt;!--Description--&gt;Airlink101 AC-USBS
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver }}
|-
| &lt;!--Description--&gt;Belkin F5U103v
| 0x067B  
| 0x2303 
| 0x0
| {{no|no driver }}
|- 
| Dynamode U232-P9
| 0x067B
| 0x2303
| 300
| {{no| no driver [http://koti.mbnet.fi/lonnberg/pl2303x.html linux patch] and using lsusb -v -d 067b:2303 gave bMaxPacketSize as 64 - pl2303x }}
|- 
| Konig CABLE-146/2 USB to RS232 
| 0x067b
| 0x2303
| 400
| {{no|no driver }}
|-
| MANHATTAN 205146 USB to Serial Converter
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver }}
|- 
| Sabrent SBT-USC1M
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver }}
|-
| &lt;!--Description--&gt;Trendnet TU-59
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver }}
|-
| &lt;!--Description--&gt;Unbranded black case and lead USB 232 Converter
| &lt;!--Vendor ID--&gt;0x067B
| &lt;!--Product ID--&gt;0x2303
| &lt;!--Revision--&gt;0300
| &lt;!--Opinion--&gt;{{No| }}
|-
|}


[http://www.ftdichip.com/index.html Future Technology Devices International Ltd FTDI]-FT232R.class [https://ftdichip.com/software-examples/code-examples/c-builder/ FTProg src], [http://rtr.ca/ft232r/ ft232r src], [https://ftdichip.com/wp-content/uploads/2020/08/DS_FT232R.pdf FT232R datasheet], [], 
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;0x0403
| &lt;!--Product ID--&gt;0x6001 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}} [https://www.youtube.com/watch?v=1GE-gKgHxZI beware of cheap clones fake with s/n A50285BI SN]
|-
| &lt;!--Description--&gt;Lynx Astro FTDI 
| &lt;!--Vendor ID--&gt;0x0403
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}} FT232R 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}}
|-
| &lt;!--Description--&gt;Sabrent CB-FTDI
| &lt;!--Vendor ID--&gt;0x0403
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| {{no|no driver TTL-232R cables use FTDI's [http://n1mm.hamdocs.com/tiki-index.php?page=USB+Interface+Devices FT232RQ ic device] }}
|-
| &lt;!--Description--&gt;Startech.com 1 Port FTDI USB to Serial RS232 DB9M Adapter Cable with COM Retention ICUSB2321F 
| &lt;!--Vendor ID--&gt;0x0403
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}} FT232RL Chipset
|-
| &lt;!--Description--&gt;StarTech.com 2 Port FTDI USB to Serial RS232 Adapter Cable ICUSB2322F
| &lt;!--Vendor ID--&gt;0x0403
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}} FTDI FT2232D Chipset
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| Opinion 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}} FT232RL is the SSOP-28 and the FT232RQ is the QFN-32 package option 
|}


[https://www.onetransistor.eu/2017/08/ch341a-mini-programmer-schematic.html ch341a.class] 

*I2C EEPROMS (3.3V and 5V) compatible and also SPI FLASH memories (3.3V devices) making sure 1.8V is covered  
*each having their own [https://winraid.level1techs.com/t/guide-how-to-use-a-ch341a-spi-programmer-flasher-with-pictures/33041 4x2 connection blocks] using [https://github.com/flashrom/flashrom flashrom] 

 sudo flashrom --programmer ch341a_spi -r backup.bin
 sudo flashrom --programmer ch341a_spi -w &lt;new bios name&gt;

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;Jiangsu QinHeng Ltd CH341A emulate UART communication, standard parallel port, memory parallel port and synchronous serial (I2C, SPI) 
| &lt;!--Vendor ID--&gt;0x1A86
| &lt;!--Product ID--&gt;0x5512
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}}
|-
| &lt;!--Description--&gt;QinHeng USB2.0-Serial HL-340 
| &lt;!--Vendor ID--&gt;0x1A86
| &lt;!--Product ID--&gt;0x7523
| &lt;!--Revision--&gt;0252
| &lt;!--Opinion--&gt;{{no|no driver}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}}
|}


==simplemidi.class and CAMD==

Currently support includes 

* simplemidi.class SimpleMidi maps some keyboard keys to corresponding computer keys as used by music trackers to emulate a musical keyboard 
* camdusbmidi.class follows the rules of the m68k implementation of Commodore's CAMD midi specification and usb class compliant 

for 

* usb host like a computer, pi, etc 
* usb device controllers - keyboards, drum machines, djay turntables, grooveboxes, etc 
* interfaces - cables or boxes which convert usb to 5pin DIN plug midi 


What is needed is a fully class-compliant '''brand name''' USB MIDI keyboard, especially manufactured in the last 15 years are best 

*Arturia
*Novation
*M-Audio
*Akai

Plugging this in one of your USB ports, the camd.library will make the keyboard's MIDI IN/OUT ports available in the system. 

Then select the keyboard's MIDI IN port (known as a &quot;cluster&quot; in CAMD) for input, and the software instrument's cluster as output 


ShowCluster (shows midi ports available in and out)

MidiWatch (usually port usbmidi.in.0 less often usbmidi.out.0) (Ctrl-C to end output stream) 
 usbmidi.in.0 Message on channel 01, NoteOn  90  39  08  00
 usbmidi.in.0 Message on channel 01, NoteOff 80  39  00  00

MidiThru (forwards messages from one port to another)
 run &gt;nil: c:midithru usbmidi.out.0 usbmidi.out.2 

MidiSendC (sends a middle C to a specific port)


Midi Controller + Sound Module (together aka as a synth) -&gt; Audio Output 


The difference between midi and midi over USB is that in old school Midi the transmitter transmits whenever it wants and the receiver always has to be prepared to receive data. Easy to do at the rate of a 1990's modem speed these days.

USB over midi.. turns midi into a polled protocol.. So the USB host (typically the computer) has to ask &quot;do you have anything for me&quot; before the remote will send. If the USB host gets busy doing other things or there is a lot of things on the USB bus to get polled, you can get delays.

For its age midi is still a great protocol for music

* [https://www.usb.org/sites/default/files/midi10.pdf USBIF's &quot;USB Device Class Definition for MIDI Devices&quot; document, version 1.0 from Nov 1, 1999]
* [https://www.usb.org/sites/default/files/USB%20MIDI%20v2_0.pdf MIDI v2.0 from 2020 which AROS still needs, adds support for MIDI 2.0, MIDI-CI, and Universal MIDI Packet] 

Nearly all synthesizers now use the 16 MIDI channels available on a MIDI bus in one instrument alone, requiring multiple MIDI busses in a typical setup with more than
one MIDI instrument. In addition, by handling multiple &quot;virtual&quot; cables, USB offers a solution to go beyond MIDI's 16-channel limit. 

MIDI data is transferred over USB using 32-bit USB-MIDI Event Packets. These packets provide an efficient method to transfer multiple MIDI streams with fixed length messages. The 32-bit USB-MIDI Event Packet allows multiple &quot;virtual MIDI cables&quot; routed over the same USB endpoint. This approach minimizes the number of required endpoints. It also makes parsing MIDI events easier by packetizing the separate bytes of a MIDI event into one parsed USB-MIDI event. 


{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;25%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;5%&quot; |Product ID
! width=&quot;5%&quot; |Revision 
! width=&quot;15%&quot; |CAMD
! width=&quot;30%&quot; |Opinion
|-
| &lt;!--Description--&gt;Computer 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;
| &lt;!--Opinion--&gt;{{Yes|which acts as USB midi host to get all usb devices talking together}} 
|-
| &lt;!--Description--&gt;Hobbytronics usb host standalone 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;bomebox 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;[https://neuma.studio/rpi-as-midi-host/ raspberry pi] with several midi interface(s) and linux scripting 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Kenton MIDI USB Host mk3
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|}


{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;25%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;5%&quot; |Product ID
! width=&quot;5%&quot; |Revision 
! width=&quot;15%&quot; |CAMD
! width=&quot;30%&quot; |Opinion
|-
| &lt;!--Description--&gt;Acorn Instruments Masterkey 49 device 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2018 untested usb powered 5V regulated - similar keybed to keystation 49es but unplug then re-plug the USB cable while it is powered the device might reconnect 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{maybe| }}
| &lt;!--Opinion--&gt; midi keyboard controller 
|-
| &lt;!--Description--&gt;Akai SynthStation 25 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2010 - sticky rubber keys - usb 
|-
| &lt;!--Description--&gt;Akai MPK Mini Laptop Production Keyboard 
| &lt;!--Vendor ID--&gt;0x09e8
| &lt;!--Product ID--&gt;0x007c
| &lt;!--Revision--&gt;0100
| &lt;!--CAMD--&gt;{{Yes|detected and camd usb to use, not tested with apps}}
| &lt;!--Opinion--&gt;2010 25 mini key self powered by mini USB lead - sustain port - no top left corner joystick - tested icaros 2.3 -  
|-
| &lt;!--Description--&gt;Akai LPK25 LPK37 LPK49 Laptop Production Keyboard
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested }}
| &lt;!--Opinion--&gt;2012 untested velocity sensitive mini keys with synth action - weak mini USB port - latency issues -  
|-
| &lt;!--Description--&gt;Akai Professional APC Key 25 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2012 
|-
| &lt;!--Description--&gt;Akai MPK49 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| untested}}
| &lt;!--Opinion--&gt;2012 untested 49 key 49-key full-sized, semi-weighted keyboard with aftertouch - 
|-
| &lt;!--Description--&gt;AKAI Max25 MAX49 control keyboard
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested }} 
| &lt;!--Opinion--&gt;2014 usb compliant 
|-
| &lt;!--Description--&gt;Akai Professional MPK249 MPK261 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}} 
| &lt;!--Opinion--&gt;2015 USB2 USB-b - full keys semi-weighted aftertouch - midi in out - sustain and peddle port 
|-
| &lt;!--Description--&gt;Akai Professional Advance 49
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2016 
|-
| &lt;!--Description--&gt;Akai MPK Mini MKII MK2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| untested}}
| &lt;!--Opinion--&gt;2017 untested USB2 USB-b midi connection only - 4 way thumb joystick top left - 25 tiny keys - velocity drum pads - plastic build quality - 
|-
| &lt;!--Description--&gt;AKAI Professional APC Key 25 MK2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| driver}}
| &lt;!--Opinion--&gt;2017 
|-
| &lt;!--Description--&gt;Akai MPK Mini Play
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2021 untested USB2 USB-b midi connection only - synth basic samples - class compliant? - small led display top centre - 25 mini keys - press and hold the &quot;Prog Select&quot; button then use the &quot;Program&quot; knob to assign a MIDI channel - 
|-
| &lt;!--Description--&gt;Akai MPK Mini 3 MKIII MK3 
| &lt;!--Vendor ID--&gt;0x09E8
| &lt;!--Product ID--&gt;0x1049 
| &lt;!--Revision--&gt;0200
| &lt;!--CAMD--&gt;{{Yes|detected audio class and bindings with camdusbmidi.class -  - midi in out untested - }}
| &lt;!--Opinion--&gt;2021 USB2 USB-b midi controller connection no 5pin legacy - small led display top centre - 25 mini keys goofy uneven feel of the akai keyboards - press and hold the &quot;Prog Select&quot; button and press pad 1 to 8 to assign a MIDI channel - tested on AROS One 2.4 usb
|-
| &lt;!--Description--&gt;Akai Force / MPC One 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{Maybe| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Akai Pro MPK Mini Plus 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{Maybe| }}
| &lt;!--Opinion--&gt;2023 untested 37 mini keys - class compliant device - usb-b bus powered only with 5pin midi in and out - Shift and Global for Midi Ch - 
|-
| &lt;!--Description--&gt;Akai Pro Ableton Push Mk 1 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Akai Professional MPC Key 37 49 61 midi controller 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| untested}}
| &lt;!--Opinion--&gt;2023 untested USB2 usb-b
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| CAMD
| Opinion 
|-
| &lt;!--Description--&gt;Alesis Photon PH-25 X25 Midi &amp; USB keyboard/synth
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2005 midi keyboard controller  
|-
| &lt;!--Description--&gt;Alesis Q25 Q49 Q61 Q88 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{Maybe| }}
| &lt;!--Opinion--&gt;2014 untested 
|-
| &lt;!--Description--&gt;Alesis Coda Pro Portable 88-Key Digital Piano USB MIDI Keyboard
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2015 
|-
| &lt;!--Description--&gt;Alesis V25 V49 V61 midi controller 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| untested}}
| &lt;!--Opinion--&gt;2017 
|-
| &lt;!--Description--&gt;Alesis V Mini 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{Maybe| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Alesis VI49 VI61 midi controller 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{Maybe| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Alesis VX49 VX61 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2016 1 5-pin MIDI input, 1 5-pin MIDI output, 1 USB port,
|-
| &lt;!--Description--&gt;Alesis Q25 Q49 Q61 Mk2 MKII 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2018 
|-
| &lt;!--Description--&gt;Alesis Recital 88 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2020 
|-
| &lt;!--Description--&gt;Alesis V25 V49 V61 MK2 MKII 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2022
|-
| &lt;!--Description--&gt;Alesis Qmini portable 32-key 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2023 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;audiothingies MicroMonsta 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2016 untested synth - 
|-
| &lt;!--Description--&gt;audiothingies MicroMonsta 2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2019  synth - 
|-
| &lt;!--Description--&gt;Arturia Analog Experience “The Player” USB MIDI Master Keyboard Model APE25
| &lt;!--Vendor ID--&gt;0x1C75
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2010 usb-b bus powered - 
|-
| &lt;!--Description--&gt;Arturia MiniLab Mk1
| &lt;!--Vendor ID--&gt;0x1C75
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2013 maybe class complaint 
|-
| &lt;!--Description--&gt;Arturia MiniLab MkII Mk2
| &lt;!--Vendor ID--&gt;0x1C75
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2016 maybe class complaint 
|-
| &lt;!--Description--&gt;Arturia Keystep 32 
| &lt;!--Vendor ID--&gt;0x1C75
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{Maybe| }}
| &lt;!--Opinion--&gt;2016 untested 32 mini keys  usb compliant 
|-
| &lt;!--Description--&gt;Arturia KeyLab 61 88 
| &lt;!--Vendor ID--&gt;0x1C75
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{Maybe| }}
| &lt;!--Opinion--&gt;2017 untested hammer-action Fatar keybed - reset Press and hold Oct + and Oct – buttons then insert the USB cable - 
|-
| &lt;!--Description--&gt;Arturia MiniLab mkII
| &lt;!--Vendor ID--&gt;0x1C75
| &lt;!--Product ID--&gt;0x2209 
| &lt;!--Revision--&gt;0100
| &lt;!--CAMD--&gt;{{Yes|detected audio class and bindings with camdusbmidi.class -  - midi in out untested - }}
| &lt;!--Opinion--&gt;2017 USB2 usb-b bus power - metal base heavier than most - Shift and press a key to select the MIDI Channel - To reset to original factory, unplug the USB cable, hold down the Oct- and Oct + buttons, plug the USB cable back in and continue to hold the buttons until the pads turn white - need software to change parameters like velocity sensitive assistance - 
|-
| &lt;!--Description--&gt;Arturia KeyLab MK2 MKII 61 88 
| &lt;!--Vendor ID--&gt;0x1C75
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested }}
| &lt;!--Opinion--&gt;2017 untested hammer-action Fatar keybed 
|-
| &lt;!--Description--&gt;Arturia MicroFreak
| &lt;!--Vendor ID--&gt;0x1C75
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2019 hybrid digital/analog synthesis, 
|-
| &lt;!--Description--&gt;[https://www.youtube.com/watch?v=PeYIAfn3UMs Arturia Minilab 3] [https://www.youtube.com/shorts/chj1WgMupGw ] [https://www.youtube.com/shorts/FMVdfhzg1Dw ]
| &lt;!--Vendor ID--&gt;0x1C75
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| untested}}
| &lt;!--Opinion--&gt;2020 untested usb-c bus powered - 25 mini keys semi - 
|-
| &lt;!--Description--&gt;Arturia Keystep Pro 
| &lt;!--Vendor ID--&gt;0x1C75
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2020 
|-
| &lt;!--Description--&gt;Arturia MiniLab 3 Mk3
| &lt;!--Vendor ID--&gt;0x1C75
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2022 maybe class complaint 
|-
| &lt;!--Description--&gt;Arturia MiniFreak
| &lt;!--Vendor ID--&gt;0x1C75
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2022 
|-
| &lt;!--Description--&gt;Arturia KeyLab Essential 49 61 88 mk3 
| &lt;!--Vendor ID--&gt;0x1C75
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2023 untested usb-c and 1 midi out - lack of aftertouch - 
|-
| &lt;!--Description--&gt;Arturia AstroLab 
| &lt;!--Vendor ID--&gt;0x1C75
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2024 
|-
| &lt;!--Description--&gt;Arturia KeyLab MK3 MKIII 61 88 
| &lt;!--Vendor ID--&gt;0x1C75
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2025 untested hammer-action Fatar keybed 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Behringer UMX61
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{maybe|untested}}
| &lt;!--Opinion--&gt;2007 
|-
| &lt;!--Description--&gt;Behringer U-Control UMX490 UMX610 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2010 
|-
| &lt;!--Description--&gt;Behringer U-Control 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Behringer Swing 32-Key
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Behringer MOTOR 49 - 49-Key USB/MIDI Master Controller Keyboard
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;
|-
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| CAMD
| Opinion 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt; midi keyboard controller 
|-
| &lt;!--Description--&gt;Creative EMU Xboard 25 E-MU X-Board 49 61 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No|untested}}
| &lt;!--Opinion--&gt;2008 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;CME M-Key Mkey 49 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2008 stops sending MIDI on a regular basis. The simplest &quot;fix&quot; is to flip it off and on via the power switch at the back
|-
| &lt;!--Description--&gt;CME Ukey U-Key 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2009 
|-
| &lt;!--Description--&gt;CME Xkey 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2014 low-profile aluminium  full size pressure sensitive with polyphonic aftertouch but keys make too much noise and that they can be too sensitive to velocity - low power draw 25ma 
|-
| &lt;!--Description--&gt;CME M-Key 49 V2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2014 simplified version of the U-key Mobiltone 
|-
| &lt;!--Description--&gt;CME XKEY AIR 37
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2019
|-
| &lt;!--Description--&gt;cme xkey 37 le
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2020 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{ | }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Donner Spaceline DMK-25 Donnerdeal Rantion 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Donner DMK25 PRO 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;  25 mini velocity keys with limited aftertouch - usb-c powered - 8 drum pads - 3.5mm &quot;midi out&quot; socket - 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{ | }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Elektron Digitakt 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2015 expensive later midi usb class compliant with since 1.5 Update
|-
| &lt;!--Description--&gt;Elecktron Digitone 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Elektron Digitone Keys 37-key Digital FM Synthesizer
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2018 expensive 
|-
| &lt;!--Description--&gt;Elektron Analog Four MKII
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Elektron Octatrak MKII
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{ | }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;ESI keycontrol 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;ESI keycontrol 49+ 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;ESI keycontrol 25xt
| &lt;!--Vendor ID--&gt;0x2702 
| &lt;!--Product ID--&gt;0x2702
| &lt;!--Revision--&gt;0100
| &lt;!--CAMD--&gt;{{Yes|detected and usb driver working}}
| &lt;!--Opinion--&gt;2011 bus powered or 12v 0.5a dc in - metal base so heavy - midi out 5pin - sustain pedal port - modulation slider - rubber coated knobs becomes sticky - 
|-
| &lt;!--Description--&gt;ESI keycontrol 49xt 61xt 88xt 
| &lt;!--Vendor ID--&gt;0x2702
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;0100
| &lt;!--CAMD--&gt;{{Yes|detected}}
| &lt;!--Opinion--&gt;2011 12v 0.5a center pin +ve external psu required - USB i/o and 1 legacy 5pin out - full sized keys - heavy aluminium case keyboard metal base - 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{maybe| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Evolution MK-125 MK-149
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;2000 9v 
|-
| &lt;!--Description--&gt;Evolution MK-225C MK-249C 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;2003 9v 
|-
| &lt;!--Description--&gt;Evolution USB/Midi Controller MK-425C MK-449C MK-461C 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No|25, 49, 61 keys -  }}
| &lt;!--Opinion--&gt;2006  9V or 12V - 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{maybe| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt; midi keyboard controller 
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| CAMD
| Opinion 
|-
| &lt;!--Description--&gt;IK Multimedia iRig Keys Pro
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2014 37 full keys 
|-
| &lt;!--Description--&gt;IK Multimedia iRig Keys Pro Mobile
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2014 25 or 37 mini keys 
|-
| &lt;!--Description--&gt;IK Multimedia iRig Keys 2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2020 mini velocity keys no aftertouch - 
|-
| &lt;!--Description--&gt;IK Multimedia iRig Keys 2 PRO 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2020 full velocity keys no aftertouch - 
|-
| &lt;!--Description--&gt;IK Multimedia iRig Keys 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{maybe| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Kawai VPC 1 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt; weighted keys - heavy build - 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Keith McMillen Instruments K-Board
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt; omni class compliant to all channels? each keypad makes them velocity, pressure, and location sensitive but  not really suited for piano playing 
|-
| &lt;!--Description--&gt;Keith McMillen  BopPad
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt; omni class compliant to all channels? 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{maybe| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Korg NanoKontrol 1
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;mini usb
|-
| &lt;!--Description--&gt;Korg Prophecy 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;KORG microKONTROL 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{no| }}
| &lt;!--Opinion--&gt;2010
|-
| &lt;!--Description--&gt;Korg microKEY 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| untested}}
| &lt;!--Opinion--&gt;2011 velocity-sensitive Natural Touch keys but  joystick is an alternative to the common pitch/modulation wheel design - power draw - 
|-
| &lt;!--Description--&gt;Korg nanoKey nanoPad 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2011 
|-
| &lt;!--Description--&gt;Korg Taktile 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Korg microKEY2 25 37 49 61 USB
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|2015 untested}}
| &lt;!--Opinion--&gt;2015 USB powered - semi weighted - 
|-
| &lt;!--Description--&gt;Korg MiniList 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Korg MinKey nanoPad nanoPad 2
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Korg Nautilus 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2024 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{maybe| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt; midi keyboard controller 
|-
| &lt;!--Description--&gt;Kurzweil PC3 7 series - Artis 7 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}} 
| &lt;!--Opinion--&gt;fatar TP-8 semi-weighted action  
|-
| &lt;!--Description--&gt;Kurzweil PC1
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Kurzweil PC3 A8
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{maybe| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Line 6 Mobile keys 25
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;2006 
|-
| &lt;!--Description--&gt;Line 6 POD Studio KB37 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;2006 
|-
| &lt;!--Description--&gt;Line 6 Tone Port KB37 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;2007 
|-
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| CAMD
| Opinion 
|-
| &lt;!--Description--&gt;Midiman (later M-Audio) Oxygen8 Ozone Ozonic 25 32 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{no|not class compliant - untested 5pin legacy }}
| &lt;!--Opinion--&gt;2002 2004 - 25 full keys - slider/fader to left of lcd display - 
|-
| &lt;!--Description--&gt;m-audio oxygen keystation (61 key) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{no| }}
| &lt;!--Opinion--&gt;2004 
|-
| &lt;!--Description--&gt;M-Audio eKeys 37 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{no| }}
| &lt;!--Opinion--&gt;2005 
|-
| &lt;!--Description--&gt;M-Audio Axiom 25, 49, 61
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;2006 bus powered and 12v psu - if sliders/faders are on right - legacy midi 5pin - chunky unit -
|-
| &lt;!--Description--&gt;M-Audio Oxygen 8v2, 49, 61 (silver) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{no| }}
| &lt;!--Opinion--&gt;2006 full size velocity sensitive 12v psu - sending random pitchbend info - 
|-
| &lt;!--Description--&gt;M-Audio Keystation 37e 49e, 61e MK1 MKI 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2006 - ok key action - 
|-
| &lt;!--Description--&gt;M-Audio Keystation 37es 49se 61es, 88es MK1 MKI 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2008 - 
|-
| &lt;!--Description--&gt;M-Audio Oxygen 25/49/61/88 (blue) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2008 [https://m-audio.com/products/view/oxygen-25-legacy advised Class-compliant and GM/GM2/XG SysEx messages] with full size velocity sensitive 12v psu - sending random pitchbend info - 
|-
| &lt;!--Description--&gt;M-Audio Axiom 25, 49, 61 (2nd Gen) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2010 semi-weighted mini keys - bus powered and 9v psu for 25/49 and 12v for 61 - if sliders/faders are on left - legacy midi 5pin - chunky unit - 
|-
| &lt;!--Description--&gt;M-Audio Axiom Pro 25, 49, 61 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2011 poor construction 
|-
| &lt;!--Description--&gt;MAudio Axiom AIR 25 M-Audio Axiom Air Mini 32
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2012 
|-
| &lt;!--Description--&gt;M-Audio Oxygen 25 III (3rd Gen) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2012 untested - usb only - rubber keys sticky - 
|-
| &lt;!--Description--&gt;MAudio Keyrig 49 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;M-Audio Keystation Mini 32 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2012 - mini usb - plays a few notes and then stops responding randomly - try plugging it into port 1 or 2 on your pc - 
|-
| &lt;!--Description--&gt;M-Audio Keystation 49 MK2 II
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2012 USB port and class compliant
|-
| &lt;!--Description--&gt;M-Audio Keystation 61 MK3 MKIII MIDI keyboard
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2015 usb compliant untested 
|-
| &lt;!--Description--&gt;M-Audio Oxygen 25 IV
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| untested}}
| &lt;!--Opinion--&gt;2016  choice 
|-
| &lt;!--Description--&gt;M-Audio CTRL-49
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2017 
|-
| &lt;!--Description--&gt;M-Audio ProKeys 88, 88sx 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;M-Audio Keystation Mini 32 MK3 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2019 mini usb - some power or incompatibility issue with the native USB ports of the laptop, plugged in a passive USB 2.0 HUB (not USB 3.0, not powered)
|-
| &lt;!--Description--&gt;[https://www.youtube.com/watch?v=3328SvuJsLw M-Audio Oxygen25 MKV]
| &lt;!--Vendor ID--&gt;0x0763
| &lt;!--Product ID--&gt;0x0001
| &lt;!--Revision--&gt;0023
| &lt;!--CAMD--&gt;{{Yes|detected audio class and bindings with camdusbmidi.class  - midi in out untested}}
| &lt;!--Opinion--&gt;2020 25 full size semi keys - USB2 usb-b but no 5pin classic plugs - channel select SHIFT button and CHANNEL on keybed - plastic build - holding down both the Octave + and - for factory reset -  more limited in what you can do with it than IV 4th one - tested on AROS One 2.4 usb
|-
| &lt;!--Description--&gt;M-Audio Oxygen Pro 25 49 61 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2022 untested semi full keys 
|-
| &lt;!--Description--&gt;M-Audio Oxygen Pro Mini 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2023 untested - 32 smaller keys - not endless encoders - usb only - 
|-
| &lt;!--Description--&gt;M-Audio Hammer 88 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Moog 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Moog Minitaur 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;M-VAVE SMK-25mini 25key MIDI Control Keyboard Y6I0 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Native Instruments NI Primus A25 JamMate 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{no| }}
| &lt;!--Opinion--&gt;2008 not compliant, 
|-
| &lt;!--Description--&gt;Native Instruments Maschine MK1 MKI
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;2009 not compliant uses snd-usb-caiaq module, 
|-
| &lt;!--Description--&gt;Native Instruments Komplete Kontrol S88 S61 S49 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2012 - weighted keys - 
|-
| &lt;!--Description--&gt;Native Instruments Maschine MK2 MKII 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2013 maybe compliant, 
|-
| &lt;!--Description--&gt;Native Instruments Maschine Micro Mikro MK2 MKII
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2014 maybe? 
|-
| &lt;!--Description--&gt;NI Komplete Kontrol S49 S61 S88 MkII MK2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2017 all MK2 MK3 power up the keyboard using USB, it will set the keyboards MIDI port to computer MIDI only without any option to set it to use the MIDI DIN, meaning you cannot connect the keyboard to hardware and power from USB, you MUST power with the power adapter and physically unplug from any USB connection - 
|-
| &lt;!--Description--&gt;Native Instruments Komplete Kontrol A25 A49 A61 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2018 maybe compliant,  
|-
| &lt;!--Description--&gt;[https://github.com/sikorak666/maschine-mikro-mk3-driver Native Instruments Maschine Micro Mikro Plus MK3 MKIII]
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2019 
|-
| &lt;!--Description--&gt;Native Instruments Komplete Kontrol M32 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2019 untested 32 smaller keys - no drum pads - USB only - 
|-
| &lt;!--Description--&gt;NI Komplete Kontrol S49 S61 S88 MkIII MK3 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2023 
|-
| &lt;!--Description--&gt;NI 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2025 
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| CAMD
| Opinion 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt; midi keyboard controller 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Neusonik iBoard 4
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Nektar Impact LX25+ LX49+ LX61+ LX88+ SE 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2017 budget full-size velocity-sensitive synth-action keyboard - 
|-
| &lt;!--Description--&gt;Nektar Impact GX49
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt; USB port - 
|-
| &lt;!--Description--&gt;Nektar Panorama P4 P6 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  USB &amp; USB Micro B, 5-pin MIDI out, 2 x TRS inputs with 49 semi-weighted, velocity sensitive with aftertouch
|-
| &lt;!--Description--&gt;Nektar SE25 SE49
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt; mini keys - micro usb bus powered - velocity and sustain button 
|-
| &lt;!--Description--&gt;Nektar Panorama P6 61 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Nektar Panorama T6 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Nord Stage 3 midi controller 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt; sysex 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Novation ReMote 25 49 61 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;2003 lhs XY touchpad and the joystick -
|-
| &lt;!--Description--&gt;Novation LaunchKey 25 49 61 88 Mk1 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{no| }}
| &lt;!--Opinion--&gt;2005 not USB class compliant 
|-
| &lt;!--Description--&gt;Novation 49 61 SL 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;2006 semi-weighted Fatar TP-8 or TP-9 keybed
|-
| &lt;!--Description--&gt;Novation ReMote 25SL 49SL 61SL soft label 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;2006 - two long top liquid-crystal display LCD strips - XY touchpad and the joystick - 
|-
| &lt;!--Description--&gt;Novation ReMOTE 25LE 
| &lt;!--Vendor ID--&gt;0x1235
| &lt;!--Product ID--&gt;0x0004
| &lt;!--Revision--&gt;0001
| &lt;!--CAMD--&gt;{{Yes|detected, usb driver in devs/midi for camd to use}}
| &lt;!--Opinion--&gt;2007 USB-b powered, 9v center pin positive or 6 MN1500 AA batteries - X/Y touchpad and the combined pitch and modulation joystick - no aftertouch but can use both the legacy MIDI OUT and USB port simultaneously 
|-
| &lt;!--Description--&gt;Novation Nocturn 49 61 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{Unk| }} 
| &lt;!--Opinion--&gt;2008 untested sending random pitchbend info
|-
| &lt;!--Description--&gt;Novation 49 61 SL MkII
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2009 semi-weighted Fatar TP-8 or TP-9 keybed 
|-
| &lt;!--Description--&gt;Novation MiniNova 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2013 
|-
| &lt;!--Description--&gt;Novation Impulse 25 49 61 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2012 velocity aftertouch‑sensitive semi-weighted keyboards and eight backlit pads -  USB, 5-pin MIDI out - 
|-
| &lt;!--Description--&gt;Novation Circuit Tracks / Rhythm 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2015 untested 
|-
| &lt;!--Description--&gt;Novation LaunchKey 25 49 61 88 MK2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2015 USB class compliant - full keys - 
|-
| &lt;!--Description--&gt;Novation Launchpad Mini MK2 MKII
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2016 untested 8x8 buttons with 16 backlit
|-
| &lt;!--Description--&gt;Novation LaunchKey Mini MK2 MKII 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2018 untested - 25 soft mini keys - 2 rotary wheels lhs - 
|-
| &lt;!--Description--&gt;Novation LaunchKey 25 37 49 61 88 MK3 MKIII 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2020 USB class compliant choice - full keys - 
|-
| &lt;!--Description--&gt;Novation LaunchKey Mini MK3
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2023 untested - 25 soft mini keys - 2 sliders lhs -  
|-
| &lt;!--Description--&gt;Novation 61SL Mk3
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt; midi keyboard controller 
|-
| &lt;!--Description--&gt;Nymphes Dreadbox 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt; 6 voice analog synth
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| CAMD
| Opinion 
|-
| &lt;!--Description--&gt;Oberheim MC 2000 EX 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2015 88 keys fully weighted - very heavy - 
|-
| &lt;!--Description--&gt;PreSonus ATOM SQ Hybrid MIDI Keyboard/Pad
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;[https://polyend.com/tracker/ Polyend Tracker]
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Roland ED PC-300
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;2002 USB MIDI keyboard controller 49-key
|-
| &lt;!--Description--&gt;Roland EDIROL PCR-M30 PCR-M50 PCR-M80 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;2005 
|-
| &lt;!--Description--&gt;Roland Edirol PCR-30 PCR-50 PCR-80
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;2007 untested 32 key - 
|-
| &lt;!--Description--&gt;Roland PC-50 PC-80
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;2007 
|-
| &lt;!--Description--&gt;Roland PCR-500 PCR-800
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2008 61 velocity-sensitive keys with aftertouch 
|-
| &lt;!--Description--&gt;Roland A-88 a-49
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2013 USB port - weighted keys velocity no aftertouch - class compliant with press FUNCTION so it is lit. Press the key labelled &quot;ADV.&quot;, Press the &quot;+&quot; button so it is lit - 
|-
| &lt;!--Description--&gt;Roland PC-200 mkII
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2014 some had fatar keys 
|-
| &lt;!--Description--&gt;Roland MC-707 Groovebox
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2015 
|-
| &lt;!--Description--&gt;Roland MC-101 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2015 untested 
|-
| &lt;!--Description--&gt;Roland A-500 A500Pro
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2018 
|-
| &lt;!--Description--&gt;Roland A-300 A300Pro
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2018 
|-
| &lt;!--Description--&gt;Roland JUNO DS, FA, Fantom, JUPITER X / Xm 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2019 (be sure that USB driver is set to &quot;Generic&quot; - requires device rebooting) 
|-
| &lt;!--Description--&gt;Roland A-88 a-49 MKii MK2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2020 expensive with USB-c port - hammer-action keyboard weighted keys - Class-compliant if  USB-C enables bus power - MIDI 2.0 later - 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;ROLI Seaboard RISE 25 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt; midi keyboard controller 
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| CAMD
| Opinion 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt; midi keyboard controller 
|-
| &lt;!--Description--&gt;Samson Graphite 49 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Samson Carbon 49 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Sequential TAKE 5 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Studiologic VMK-161 and VMK-161 Plus Organ version 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }} 
| &lt;!--Opinion--&gt;TP-8O action is the unweighted, organ-style waterfall keybed - usb midi in out - 9v psu - 
|-
| &lt;!--Description--&gt;Studiologic SL990XP midi controller 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Studiologic VMK176 Plus
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }} 
| &lt;!--Opinion--&gt;USB and midi connectivity
|-
| &lt;!--Description--&gt;Studiologic SL880 midi controller 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Studiologic SL73 SL88 Studio midi controller 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt; hammer-action Fatar TP semi-weighted keys 
|-
| &lt;!--Description--&gt;Studiologic Numa Organ 2
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt; 73 key TP-8O action is the unweighted, organ-style waterfall keybed used in nearly all clonewheels 
|-
| &lt;!--Description--&gt;Studiologic Numacompact 2/2x, Numa X Piano
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;SubZero CommandKey49 CommandKey25 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;SubZero SZ-MiniCommand Mini-Command USB 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;SubZero SPC61 MIDI Controller
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt; bus powered - 5 octave 
|-
| &lt;!--Description--&gt;SubZero ControlKey49S 49 Key Slim MIDI Controller Keyboard
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{maybe| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Synido TempoKey K25
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2023 25 mini keys - usb-c powered 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{maybe| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Winterbloom Sol 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{maybe| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Worlde Panda 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt; midi keyboard controller 
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| CAMD
| Opinion 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Yamaha KX8 KX49 KX61 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;2008 not compliant 
|-
| &lt;!--Description--&gt;Yamaha CMC-PD
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;2010 
|-
| &lt;!--Description--&gt;Yamaha 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2011 not class compliant 
|-
| &lt;!--Description--&gt;Yamaha P45B P-45 Digital Piano 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;2011 not compliant 
|-
| &lt;!--Description--&gt;Yamaha P-115 midi controller  
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2016 untested weighted keys - USB midi port 
|-
| &lt;!--Description--&gt;Yamaha MX49 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2020 should compliant untested 
|-
| &lt;!--Description--&gt;Yamaha Montage, CP73/88, YC, MODX
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  midi keyboard controller 
|-
| &lt;!--Description--&gt;Yamaha PSR-E353, PSR-E443
PSR-S670, PSR-S770, PSR-S970, PSR-A3000, TYROS-5
NP-12, NP-32
DGX-650, DGX-660
P-105, P-115, P-255
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Yamaha MX49 II V2 Black Blue 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2023 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  midi keyboard controller 
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| CAMD
| Opinion 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;DJM V10
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt; dj 
|-
| &lt;!--Description--&gt;Native Instruments Kontrol DJ Pro midi controller 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt; detected but untested 
|-
| &lt;!--Description--&gt;Numark Mixtrack Pro II USB DJ Controller Djay 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;older generation pioneer DDJ-SX2 dj 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|}


{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;20%&quot; | Description 
! width=&quot;10%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;10%&quot; |CAMD
! width=&quot;30%&quot; |Opinion
|-
| &lt;!--Description--&gt;Alyseum AL-22 AL22c  
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;Alyseum AL-88 Schneidersladen AL88c 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;Alyseum U3-88c Midi Interface
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt; no CopperLan support Midi network using a UTP Ethernet patch cable) 
|-
| &lt;!--Description--&gt;Behringer BCF2000 midi interface 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;[http://www.behringer.com/EN/home.aspx Behringer] BCR2000 1in 2out
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Behringer B-CONTROL DEEJAY BCD3000 DJ Mixer 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Behringer UMD404 UMD202 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;Creative EMU 0404/USB midi interface 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{no| }}
| &lt;!--Opinion--&gt;2006 
|-
| &lt;!--Description--&gt;DigiDesign / Focusrite Command 8 Control Surface
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;2005 supports MIDI continuous controller (CC) and note data. SysEx dumping and loading is also supported  
|-
| &lt;!--Description--&gt;Digidesign Digi 002
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;2006   firewire only 
|-
| &lt;!--Description--&gt;Digidesign Digi 003
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;2009   firewire only 
|-
| &lt;!--Description--&gt;emagic m4 2x4 AMT8 Unitor 8 Mk2  8x8 
| &lt;!--Vendor ID--&gt;0x00d0
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;0x010 0x0103
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;2000 offers MTS (Midi Time Stamping) - 12v 2a psu centre pos - usb mini with rs232 and rs422 serial ports - 16 channels (8-in / 8-out), this rack-mountable unit - 
|-
| &lt;!--Description--&gt;Evolution U-Control UC-16 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| detected}}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Focusrite Saffire 6 USB 1.1
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Guillemot Maxi Studio ISIS Vintage Sound Card MIDI Audio Interface 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No|dedicated driver}}
| &lt;!--Opinion--&gt;1998 
|-
| &lt;!--Description--&gt;[http://www.ucapps.de/mbhp_usb.html MidiBox] Hardware Platform USB Module
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{no| }}
| &lt;!--Opinion--&gt;2001 
|-
| &lt;!--Description--&gt;Mackie Control Universal Pro XT with One Two Extenders 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{no| }}
| &lt;!--Opinion--&gt;2008 not compliant, 
|-
| &lt;!--Description--&gt;M-Audio Audiophile USB
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;2003 not compliant, 
|-
| &lt;!--Description--&gt;M-Audio Midisport UNO old version 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;2004 not compliant, 
|-
| &lt;!--Description--&gt;M-Audio MidiMan 1x1 midi interface 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;2004  [http://sourceforge.net/projects/linux-hotplug/ firmware update]
|-
| &lt;!--Description--&gt;M-Audio Midisport 2x2 yellowy green blue, green or silver chassis plastic box 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No|MIDISPORT 2x2 or 4x4 interfaces from previous production series (blue, green or silver chassis) are not class-compliant}}
| &lt;!--Opinion--&gt;2004 
|-
| &lt;!--Description--&gt;MAudio Audiosport Quattro USB 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No|dedicated driver}}
| &lt;!--Opinion--&gt;2004 not usb compliant as [http://usb-midi-fw.sourceforge.net/ firmware required and that is buggy], 
|-
| &lt;!--Description--&gt;M-Audio UC-33
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{no| }}
| &lt;!--Opinion--&gt;2004 not compliant, 
|-
| &lt;!--Description--&gt;M-Audio Midisport 1x1 2x2 4x4 Anniversary Edition, black box 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2010 maybe class compliant, 
|-
| &lt;!--Description--&gt;Mooer Steep II Multi-Platform USB Audio Interface 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;[http://www.amiga.org/forums/showthread.php?t=52920 Mark of the Unicorn Motu Fastlane] 2x2
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No|[http://www.amiga.org/forums/showpost.php?p=560852&amp;postcount=8 not working on OS4]}} 
| &lt;!--Opinion--&gt; not class compliant, 
|-
| &lt;!--Description--&gt;Motu Micro Lite 1x1 and MOTU microlite 5x5 USB 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No|dedicated driver}}
| &lt;!--Opinion--&gt; good unit but poor just plug in support and not class compliant - USB2 usb-b - 
|-
| &lt;!--Description--&gt;Motu MIDI Express 128 8x8
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No|dedicated driver}}
| &lt;!--Opinion--&gt;poor support serial port only - offers MTS (Midi Time Stamping) A serial port based MIDI interface or a USB interface without MTS will have a MIDI slop of up to 2ms on record and playback. MTS provides accuracy for record and playback to around .3ms - five times more accurate than serial or non-MTS.&quot; 
|-
| &lt;!--Description--&gt;MOTU.com MIDI Express XT 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No|dedicated driver}}
| &lt;!--Opinion--&gt;2008 for many USB should have octocoupled connection to reduce groundloop humm, usually the timing is off 
|-
| &lt;!--Description--&gt;MOTU MIDI Timepiece AV 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No|dedicated driver}}
| &lt;!--Opinion--&gt; not class compliant is one of the best multi-port MIDI interfaces ever made as USB model connects to the computer as an 8x16 interface
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Native Instruments GmbH Audio 8 DJ, 4 DJ, 2 DJ
| &lt;!--Vendor ID--&gt;0x17CC
| &lt;!--Product ID--&gt;0x
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{no|needs dedicated driver}}
| &lt;!--Opinion--&gt;2006 not class compliant, 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;Qcon 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;Roland Edirol UA-100 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No|did not match to camdusbmidi.class USB audio midi with onboard DSP}}
| &lt;!--Opinion--&gt;1998 
|-
| &lt;!--Description--&gt;Roland Corp Edirol UM-2 
| &lt;!--Vendor ID--&gt;0x0582
| &lt;!--Product ID--&gt;0x0005
| &lt;!--Revision--&gt;0200
| &lt;!--CAMD--&gt;{{no|is not bound via camdusbmidi.class }}
| &lt;!--Opinion--&gt;1999 not bound to any midi class - 2x2 - tested Aros One USb 2.4 
|-
| &lt;!--Description--&gt;Roland Edirol UA-100G 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No|detected but not working}} 
| &lt;!--Opinion--&gt;1999 USB audio midi with onboard DSP 
|-
| &lt;!--Description--&gt;Roland Edirol UM-880 8x8 midi interface 
| &lt;!--Vendor ID--&gt;0x0582
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No|detected but not working}} 
| &lt;!--Opinion--&gt;2000 under poseidon but could work with run &gt;nil: c:midithru out.0 &quot;EDIROL UM-880.out.2&quot;
|-
| &lt;!--Description--&gt;Roland Edirol UM-1 blue plastic 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{Unk| bound??? via camdusbmidi.class - untested midi in out}}
| &lt;!--Opinion--&gt;2000 UM-1 -  1-in/1-out (16 channels) 
|-
| &lt;!--Description--&gt;Roland Edirol UM-1S
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No|not working}} 
| &lt;!--Opinion--&gt;2000 1-in/1-out (16 channels)
|-
| &lt;!--Description--&gt;Roland Edirol UM-2E
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No|not working}} 
| &lt;!--Opinion--&gt;2000 
|-
| &lt;!--Description--&gt;Roland Edirol UM550
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;2001 
|-
| &lt;!--Description--&gt;Roland Edirol UM-1X midi interface 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No|do not have the Advanced Driver Switch on them}}
| &lt;!--Opinion--&gt;2001 
|-
| &lt;!--Description--&gt;Roland Edirol UM-1SX
| &lt;!--Vendor ID--&gt;0x0582
| &lt;!--Product ID--&gt;0x0052
| &lt;!--Revision--&gt;0200
| &lt;!--CAMD--&gt;{{No|do not have the Advanced Driver Switch on them}}
| &lt;!--Opinion--&gt;2003 
|-
| &lt;!--Description--&gt;Roland Edirol Cakewalk UM-2C - 2x2
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;2003 
|-
| &lt;!--Description--&gt;Roland Edirol Cakewalk UM-1G 1x1
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;2004 
|-
| &lt;!--Description--&gt;Roland Edirol Cakewalk UM-2G 2x2
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;2004 
|-
| &lt;!--Description--&gt;[https://github.com/spotify/linux/blob/master/sound/usb/usbquirks.h Roland Edirol UA20 UA-20] 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No|not working}} 
| &lt;!--Opinion--&gt;2004 
|-
| &lt;!--Description--&gt;Roland UM-1EX 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;2005
|-
| &lt;!--Description--&gt;Roland Edirol UM-2EX 2x2
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{no| }}
| &lt;!--Opinion--&gt;2005  adds a second MIDI OUT
|-
| &lt;!--Description--&gt;Roland Cakewalk UM-3G - 3x3
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;2006 
|-
| &lt;!--Description--&gt;Roland Cakewalk ua-25excw 1x1 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No|detected but not working}} 
| &lt;!--Opinion--&gt;2009 not class compliant mode 
|-
| &lt;!--Description--&gt;[https://alsa.opensrc.org/Edirol_UA-25EX Roland Edirol UA55 UA-55 Cakewalk UA25 EX] 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No|detected but not working}} 
| &lt;!--Opinion--&gt;2011 not usb compliant, 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;Sonuus B2M Bass MIDI Interface
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;Sonuus G2M
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;Steinberg CMC Series 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;Subzero SZ-MB44 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;Swisssonic MIDI1x1
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt;2012 AmigaOS there is no output at midichannel one and two but if play a midi file there is only output on some channels and if pressed stop the prog freezes or the whole system crashes
|-
| &lt;!--Description--&gt;Teac Tascam US-428 US-422 midi interface 
| &lt;!--Vendor ID--&gt;0x0644
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt; 2000 not compatible 
|-
| &lt;!--Description--&gt;Teac Tascam [http://web.archive.org/web/*/http://www.tascam.com/Products/US-224.html US-224]
| &lt;!--Vendor ID--&gt;0x1604
| &lt;!--Product ID--&gt;0x8004
| &lt;!--Revision--&gt;0100
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt; 2002 does not bind to any class
|-
| &lt;!--Description--&gt;Teac Corp Tascam US-1x2
| &lt;!--Vendor ID--&gt;0x0644
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }} 
| &lt;!--Opinion--&gt;2002 
|-
| &lt;!--Description--&gt;Teac Tascam US-122 MKII midi interface 
| &lt;!--Vendor ID--&gt;0x0644
| &lt;!--Product ID--&gt;0x8021
| &lt;!--Revision--&gt;0100
| &lt;!--CAMD--&gt;{{No|not detected / binding to camdusbmidi.class on AROS 2.4 usb }} 
| &lt;!--Opinion--&gt;2004 detected but not working 2-in/2-out USB two XLR microphone preamps with phantom power for condenser microphones 
|-
| &lt;!--Description--&gt;Teac Tascam US-200 US-400 US-600 US-800 US-1200 US-1800 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No|no driver}}
| &lt;!--Opinion--&gt;2010 may not be totally usb compliant 
|-
| &lt;!--Description--&gt;Yamaha UX-16
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No|no driver}}
| &lt;!--Opinion--&gt;2010 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| CAMD
| Opinion 
|-
| &lt;!--Description--&gt;Akai EIE and Pro version midi interface 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2011 dc 6v power - 3 USB hubs, midi in out , 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;Alesis I/O2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{no| }}
| &lt;!--Opinion--&gt;2007 powered USB hub required, not compliant 
|-
| &lt;!--Description--&gt;Alesis IO2 Express 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2010 usb compliant?
|-
| &lt;!--Description--&gt;Alesis IO4 Express 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2010 
|-
| &lt;!--Description--&gt;Behringer XTouch 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt; psu needed 
|-
| &lt;!--Description--&gt;Behringer X-Touch Compact
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2014 maybe usb compliant?
|-
| &lt;!--Description--&gt;Behringer X-Touch Mini
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2014 maybe usb compliant?,  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;Behringer U-Phoria UMD404HD UMD202HD 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2019 maybe class compliant - volume low, 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;CME U2 MIDI Pro 1x1 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt; current model 
|-
| Creative EMU XMIDI 1X1
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2008 early versions with sysex checksum errors 
|-
| &lt;!--Description--&gt;Creative E-MU Xmidi 1x1 Tab (V3) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2010 tab version class compliant but report that when transferring 'System Exclusive' messages (SysEx) the unit could not handle the highest data rate leading to data corruption 
|-
| Creative EMU XMIDI 2x2
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2008 sysex errors 
|-
| &lt;!--Description--&gt;Digidesign Mbox 2 Mini now Avid 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{no| }}
| &lt;!--Opinion--&gt;2005 USB powered but not compliant 
|-
| &lt;!--Description--&gt;Digidesign Mbox II Pro 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{no| }}
| &lt;!--Opinion--&gt;2006 USB powered but not compliant 
|-
| &lt;!--Description--&gt;Engl Z7 MIDI Interface (E660/E610/E360/E930)
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt; guitar?
|-
| &lt;!--Description--&gt;Elektron TurboMidi TM-1 1in 1out
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;ESI MidiTerminal M4U 4x4 midi interface 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;supposedly class compliant - USB bus powered - 
|-
| &lt;!--Description--&gt;ESI MidiTerminal M8U 8x8
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;ESI MidiTerminal M4U XL 4x4
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt; ploytec chipset 
|-
| &lt;!--Description--&gt;ESI MidiTerminal M8U XL 8x8
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt; no hardware routing e.g. x on input 5 to synth y on output 7 - ploytec chipset 
|-
| &lt;!--Description--&gt;ESI MidiMate 1x1
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt; supposedly class compliant - USB bus powered 
|-
| &lt;!--Description--&gt;ESI MidiMate II 2
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;ESI ROM I/O
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2005 romio version 
|-
| &lt;!--Description--&gt;ESI M4U XT
| &lt;!--Vendor ID--&gt;0x2573
| &lt;!--Product ID--&gt;0x0002
| &lt;!--Revision--&gt;0100
| &lt;!--CAMD--&gt;{{Maybe|is bound via camdusbmidi.class AROS One 2.4  - untested midi in out}}
| &lt;!--Opinion--&gt;2010  - 
|-
| &lt;!--Description--&gt;ESI M8U XT 8in 8out
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2010 discontinued 2018 
|-
| &lt;!--Description--&gt;ESI M8UEX USB3.0
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2018 current model 
|-
| &lt;!--Description--&gt;ESI M4U eX
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2018 current model 
|-
| &lt;!--Description--&gt;ESI MidiMate eX midi interface 1x1 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2016 current model, well liked and might class compliant?? 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;icon midiport 2x2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;iCON CubeMi 3 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt; class compliant? 
|-
| &lt;!--Description--&gt;iConnectivity 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;iConnectivity mio 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2010 class compliant but reported issues with sending System Exclusive (SysEx) MIDI messages and MIDI signals getting cut off 
|-
| &lt;!--Description--&gt; iConnectMidi interface 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2010 
|-
| &lt;!--Description--&gt;iCM2 iCM4 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2012 
|-
| &lt;!--Description--&gt;iConnectivity iConnectMIDI4+ L
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2014 class compliant?? 
|-
| &lt;!--Description--&gt;iConnectivity MioXL 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;IK Multimedia iRig MIDI 2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt; class compliant 
|-
| &lt;!--Description--&gt;iRig Pro 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;Kenton 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;Kenton Electronics pro solo mk2 midi to cv converter
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;Kenton Midi Thru-25 5 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;Keytech MT18E 8 Way Midi Thru box 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt; 9 to 12v psu required 
|-
| &lt;!--Description--&gt;MidiPlus Midi 2x2 midi interface 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;MidiPlus Midi 4x4 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt; supposedly class compliant - USB bus powered 
|-
| &lt;!--Description--&gt;MidiTech MIT-00151 Midiface 4x4
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;MidiTech Midiface 4x4 8x8 16x16 thru merge 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;Miditech Midilink mini 1x1 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;M-Audio Midisport UNO only if box is labeled Class Compliant and latest MIDISPORT 1x1 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;M-Audio Fast Track Ultra (6 in 6 out) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2008 not usb compliant, - 
|-
| &lt;!--Description--&gt;M-Audio Midiman Midisport 2x2 Anniversary Edition [https://gearspace.com/board/electronic-music-instruments-and-electronic-music-production/1133862-why-there-hardly-any-midi-interfaces.html not stable enough] 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2009 USB2 usb-b - does not need firmware and supposedly plug and play - 
|-
| &lt;!--Description--&gt;M-Audio Midisport 4x4 Anniversary Edition
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt; rumored does not need firmware - supposedly plug and play -  issues with its firmware for some and lacks configurable routing
|-
| &lt;!--Description--&gt;Maudio Fast Track Ultra 8R 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;Native Instruments Komplete Audio 6 Mk1
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2011 maybe usb compliant but bus powered, 
|-
| &lt;!--Description--&gt;Nektar Midiflex 4
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|untested}}
| &lt;!--Opinion--&gt;2015 class compliant and usb-b powered - used as a 1 in / 3 out, 2 in / 2 out or 4 out 5pin sockets - 
|-
| &lt;!--Description--&gt;Neusonik IM-One 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;Peavey Xport
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt; guitars only 
|-
| &lt;!--Description--&gt;Roland UM-ONE UM-1 mk2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2010 USB class compliant if switch to TAB for class compliant mode rather than the COMPUTER mode 
|-
| &lt;!--Description--&gt;Squarp Hermid 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;Steinberg Midex 8x8 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt; class compliant?  supporting MIDI Time Stamping protocol
|-
| &lt;!--Description--&gt;Swissonic MidiConnect 2
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;Tapco LiNK.midi USB 4x4 (Loud technologies) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{no|dedicated driver}}
| &lt;!--Opinion--&gt;2005 
|-
| &lt;!--Description--&gt;Teac Corp Tascam US-2x2
| &lt;!--Vendor ID--&gt;0x0644
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{no| }}
| &lt;!--Opinion--&gt; 2014 5v dc power, midi out in, 
|-
| &lt;!--Description--&gt;Teac Corp Tascam US-4x4
| &lt;!--Vendor ID--&gt;0x0644
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt; 
|-
| &lt;!--Description--&gt;Teac Tascam US-16x08 US-20x20
| &lt;!--Vendor ID--&gt;0x0644
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No| }}
| &lt;!--Opinion--&gt; 
|-
| &lt;!--Description--&gt;Zoom U-24
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  midi to 5pin interface 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  midi to 5pin interface 
|-
| &lt;!--Description--&gt;Unbranded cable 
| 0x552d
| 0x4348
| F110 
| &lt;!--CAMD--&gt;{{Maybe|detected but no usb driver in devs/midi for camd to use}}
| &lt;!--Opinion--&gt;detected but not working the USB-MIDI conversion functionality of the cheapo USB MIDI &quot;cable&quot; interface is simply lacking, possibly being incapable of handling MIDI strings longer than 3 bytes long SysEx strings (e.g. SysEx dumps) - tested in Icaros 2.3 - 
|-
| &lt;!--Description--&gt;USB2.0-MIDI Unbranded cable with clear braided underneath leads 
| &lt;!--Vendor ID--&gt;0x1A86
| &lt;!--Product ID--&gt;0x752D 
| &lt;!--Revision--&gt;0254 
| &lt;!--CAMD--&gt;{{Maybe|detected binding to camdusbmidi.class but untested midi in / out}}
| &lt;!--Opinion--&gt;untested but better to get a branded version - tested AROS One 2.4 usb
|-
| &lt;!--Description--&gt;LogiLink USB to Midi In-Out 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk|}}
| &lt;!--Opinion--&gt;untested cheap cable version but issues with latency on other systems 
|-
| &lt;!--Description--&gt; gm5 USB midi chip  DIY option only
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;Doremidi LEKATO MIDI USB C Interface 1x1 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;Thomann Midi USB 1x1
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;   Prodipe made 
|-
| &lt;!--Description--&gt;Prodipe MIDI 1i/1o 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  usb to 5pin midi interface 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|}


Classic 5pin DIN controllers for above interfaces 
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;20%&quot; | Description 
! width=&quot;10%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;10%&quot; |CAMD
! width=&quot;30%&quot; |Opinion
|-
| &lt;!--Description--&gt;Akai s5000 s6000
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  midi digital samplers 
|-
| &lt;!--Description--&gt;Akai AX80 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Casio CZ-5000 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Casio CZ-3000 CZ-1000 CZ-101 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Cheetah MS6 midi controller 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{No|untested}}
| &lt;!--Opinion--&gt;2000 multi-timbral, six-voice (twelve-oscillator), analogue synthesiser module is loaded with CEM 3396s 
|-
| &lt;!--Description--&gt;Ensoniq ESQ1
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Integra 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Korg Wavestation Ex A/D SR 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;1986 ex has piano and drum sounds 
|-
| &lt;!--Description--&gt;Korg DW-8000 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Korg DW-6000 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Korg Poly 800 MK1 Poly-800ii 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  all plastic and can run on batteries - 49 keys non-velocity dco synt analogue filter 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Roland D-50
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;
| &lt;!--Opinion--&gt;{{N/A|1987 untested greater concern would be moisture and wear}}
|-
| &lt;!--Description--&gt;Roland A50 (76) A80 (88) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;
| &lt;!--Opinion--&gt;{{N/A|1989 untested}}
|-
| &lt;!--Description--&gt;ROLAND JUNO-D
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Roland Juno 106 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;80s kx73 or kx88 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Roland ED PC-160A PC-180A 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}} legacy DIN5 MIDI port only - 6 AA batteries or 9v psu - One regular source of failure for me were emty batteries (even with red control light still active). Another source was a bad MIDI cable - unplug then re-plug the USB cable while it is powered the device might reconnect 
|-
| &lt;!--Description--&gt;Roland M1 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Roland S-550 S-760 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt; digital samplers kontakt replaced these? 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Yamaha DX7 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;1983 12bit 
|-
| &lt;!--Description--&gt;Yamaha DX7S DX72IID DX7IIFD 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;1987 16bit versions 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--CAMD--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
|}


The MIDI standard was published in August 1983. The inventors, Kakehashi and Smith finally received a Technical Grammy Award in 2013 for their work. 

The MIDI files that contained just the note data, velocity and timing meant you could transfer an entire studio session from one place to another on one floppy disk and it could control all the synths and drum samplers. Pass-thru meant that one computer could run an entire bands worth of instruments. 

It's bulletproof too. MIDI never goes wrong, it's always a bug in software that causes any issue - you can absolutely rely on it to go gigging with, take your synths, controllers and computers and not crash an entire gig at your 100,000 person venue. 

The MIDI hardware specification is very simple (voltage, polarity, screening, protection and a fast enough opto-isolator), it assumes that the data it sends and receives between MIDI devices is to the MIDI data standard and just passes it on. The microprocessor in the hardware does all the work.

The minimum for a computer/MIDI interface is that it meets the MIDI hardware specification. It is attached to the computer bus and handles the electrical conversions required. To meet the MIDI hardware specification, to be class compliant as a USB device all it has to do is report itself properly when plugged in.

The other half of the equation is the MIDI data standard, and for a computer MIDI interface the main issue is the speed of data transmission. The bus speed of the computer is faster than the speed of the MIDI standard so it can generate and send MIDI data faster than a MIDI device can receive it. The MIDI standards have nothing to say on that bottleneck at all. MIDI was designed to be very simple and very open, it just defines a standard for the messages and leaves it up to manufacturers to implement them in the way they want. That's what makes it so powerful a tool, and also what makes it so confusing and frustrating at times.

For midi, the hardware/software combination at various connection points handles the translation to/from midi (or other protocols). Drivers would be needed for midi, including clock and SysEx signal (actually claiming to handle ALL midi quirks transparently

All the important MIDI data types can be sent (CC, NRPN, RPN, MMC, Note On/Off, program change)

There is no official way to solve the data bottleneck. Early software sequencers and librarians tried to solve it by having an option to buffer SYSEX data in software and transmit it at the MIDI data rate. The downside is that hogs the bus and can hit computer performance. Interface manufacturers would add a hardware buffer which would take all the MIDI data from the PC bus and feed it into the MIDI at the slower data rate, but that added cost and created timing issues.

Things have moved on since then, but the principles remain the same. You can buffer in the hardware or in software, whether that is in the application or the interface driver. SYSEX will work perfectly well with that budget cable if your software handles the buffering. And while the cables with hardware buffers make SYSEX easier, they still have potential problems because of the limitations of the MIDI data rate. Your MIDI clock doesn't like being interrupted with a big program dump 

The serial / parallel ports were a direct connection, so faster. Now, everything in the computer is virtual and the only thing connected to the hardware is the kernel, hence everything is by default bottlenecked and jittery, regardless of which connection. So by the time the interface gets the information it's already too late. 

Ethernet network cable to transport MIDI over large distances, connect 2 MIDI In and 2 MIDI Out ports to patch, remap, filter and merge MIDI flows on a fine channel basis for tight MIDI throughput, latency and jitter 

Possibilities for DAWs of the future including a kind of sync reference for timing reference which an interface could sync to, hence all the timings then would be locked between the grid on the DAW screen and the MIDI info. 

Preemptible, low latency and accuracy are essential for good communication.  

One of the first things you need to do, is make sure your MIDI software sets the interface to the same MIDI channel as your keyboard (usually 1) 


Do you want to send just your master keyboard to other synths or to be able to use any keyboard with any synth?

1st option is relatively simple. Just need to send midi from your master keyboard into a midi splitter that redistributes the signal onto your synths. Each synth will be set up to receive midi on a specific channel so the only challenge is to find a way to select to which channel you are sending midi. Some master keyboards can do that although not many that have a dedicated knob or switch on the panel and most require a bit of menu diving. Could use a midi box that offers channel selection but usually this is not very workflow friendly. The software route would require using the mouse. 

2nd option is a bit more complex but superior workflow by sending midi messages into a merge box, from there into a hardware sequencer that allows to select midi channel, then on to a midi interface that distributes the signal to the synths. 

Master keyboard MIDI-in to computer. External hardware sampler MIDI-out from computer. Audio-out from sampler to audio-in on computer/device. 


Blue Ribbon Soundworks Bars &amp; Pipes Professional (1993/4) 

GM (1984), GS (1987), XG level 1-3 (1994-1997), GM level 2 (1999) 	

GM GM1 imposes several requirements beyond the MIDI 1.0 specification. While MIDI 1.0 by itself provides a communication protocol which ensures that different instruments can interoperate at a fundamental level e.g sound modules. GM goes further in two ways. First, GM requires that all compliant MIDI instruments meet a certain minimal set of features, such as being able to play at least 24 notes simultaneously (polyphony). Second, GM attaches specific interpretations to many parameters and control messages which were left unspecified in the MIDI 1.0 specification. A minimum of 128 MIDI Program Numbers (conforming to the GM 1 Instrument Patch Map) and 47 percussion sounds (conforming to the GM 1 Percussion Key Map). Support for controller number 1, 7, 10, 11, 64, 100, 101, 121 and 123; support for channel pressure and pitch bend controllers. 

General MIDI Level 2 or GM2 is a specification for synthesizers which defines several requirements beyond the MIDI standard and is based on General MIDI (GM) and Roland GS extensions. It was adopted in 1999 by the MIDI Manufacturers Association (MMA).

* Number of Notes: 32 simultaneous notes
* MIDI Channels: 16
* Simultaneous Melodic Instruments – up to 16 (all Channels)
* Simultaneous Percussion Kits – up to 2 (Channel 10/11)

Program and bank change events
General MIDI 2 compatible synthesizers access all of the 256 instruments by setting cc#0 (Bank Select MSB) to 121 and using cc#32 (Bank Select LSB) to select the variation bank before a Program Change. Variation bank 0 contains the full GM (General MIDI 1) sound set. Variations using other bank numbers are new to General MIDI 2, and correspond to variation sounds introduced in Roland GS. 


[https://www.youtube.com/watch?v=CluuHrr7HG4 Major WWHWWWH, Minor WHWWHWW scale], [https://www.youtube.com/watch?v=Jjm7Ti-iwz0 Chords], 


==usb audio==

USB audio has recently made available for Aros, there are many standards introduced over the years. Much is still untested. 

*Introduced 2000 and from 2014 USB Audio 1 UAC1 16bit 44.1kHz
*Introduced 2006 and from 2014 USB Audio 2 [https://www.usb.org/document-library/usb-device-class-definition-audio-devices-release-20-errata-and-ecn-through-april UAC2] 24bit 192kHz
*Introduced 2016 and from 2024 USB Audio 3 [https://www.usb.org/documents UAC3] 32bit 384kHz 

USB group decided to rewrite the audio standard, so [https://os4depot.net/?function=showfile&amp;file=audio/record/usbaudio2.lha UAC2] and [https://archive.fosdem.org/2019/schedule/event/linux_and_usb_audio_class_3/attachments/slides/3345/export/events/attachments/linux_and_usb_audio_class_3/slides/3345/Linux_and_USB_Audio_Class_3___FOSDEM_2019.pdf UAC3]. They added clock selection and control, timing domains and others. Part of the changes included changing many of the descriptors that an audio device uses to describe itself to the machine. 

PsdErrorlog/PsdDevlister? The AHI driver generated only supports mono/stereo at any bit rates between 8 and 32 bit per sample, but not multichannel modes and only rates up to 65KHz (because AHI uses a 16-bit word for frequencies). If the soundcard does not offer such a PCM 8-32 bit mode at frequencies lower than 65 KHz, there's nothing much that can be done about it on the computer side other than revising and expanding the AHI standard. Most cheap USB soundcards do though. 

AHI does not support six channel playback. It only supports mono, stereo and multichannel (8 channels). Due to the multichannel mode not being used by any application so far, the usbaudio.class does not support multichannel playback, especially not &quot;upchannelling&quot; stereo to six or more channels. If this USB device does not support a two channel mode, you can't use it under AHI.

Untested but most likely to work, at least 2 mic inputs (low impedance) &amp; instruments (high impedance) and made in the last 10 years 
*[https://www.youtube.com/watch?v=gMuA-2FbJxE Entry level &lt;100Euro]   BOMGE U202, Behringer UMC, Presonus Studio, 
*[ Next tier &lt;200Euro]   Audient iD, Solid SSL2 and SSL2+, Lewitt, Focusrite Scarlett, Arturia MiniFuse, 
*[ Prosumer &lt;300Euro]   Focusrite Clarett+, 
*[ Professional &lt;500Euro]   RME Babyface, 
*[ Studio &gt;500Euros]    

Bands should need 4 or more mic inputs 

[http://forum.xda-developers.com/showthread.php?p=38364030 XDA Forum thread],

&lt;pre&gt;
                                            &lt;- Computer 
                                            &lt;- Mobile Phone / Tablet (OTG)
                                            &lt;- Digital Cameras 
                            &lt;- Video        &lt;- Webcams 

Base Computer &lt;-&gt; OBS like  &lt;- Audio Mixer  &lt;- Microphone(s) 

                            -&gt; Internet     -&gt; Youtube &amp; Chat 

&lt;/pre&gt;

USB AUDIO CARDS - UAC Compliant 
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;20%&quot; |Description 
! width=&quot;10%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;10%&quot; |Playback
! width=&quot;10%&quot; |Records 
! width=&quot;30%&quot; |Opinion
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Antelope Galaxy 64 Synergy Core
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no| }}
| &lt;!--Records--&gt;{{no| }}
| &lt;!--Opinion--&gt; not compliant so does not wotk with Aros and a high-end 64-channel AD/DA converter HDX, Dante connectivity and a Thunderbolt Audio interface 
|-
| &lt;!--Description--&gt;Antelope Galaxy 32 Synergy Core
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no| }}
| &lt;!--Records--&gt;{{no| }}
| &lt;!--Opinion--&gt; not be compliant so does not wotk with Aros as Antelope Audio does not provide official drivers, control software, or an Antelope Launcher 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Arturia Mini Fuse 1
| &lt;!--Vendor ID--&gt;0x1C75
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2021 maybe usb compliant, okay pre amp 1 combi input, cirrus logic cs4272 ad converter, 
|-
| &lt;!--Description--&gt;Arturia MiniFuse 2
| &lt;!--Vendor ID--&gt;0x1C75
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2021 maybe usb compliant usb-c with usb2.0, okay pre amps with good dynamic range 110dB, cirrus logic cs4272 ad converter, two combi inputs for mic, line or guitar, 
|-
| &lt;!--Description--&gt;Arturia MiniFuse 4 
| &lt;!--Vendor ID--&gt;0x1C75
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2022 maybe usb compliant, okay 110dB dynamic range, -129dB EIN, 
|-
| &lt;!--Description--&gt;Arturia AudioFuse 16Rig 
| &lt;!--Vendor ID--&gt;0x1C75
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2023 maybe usb compliant, good 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Audient iD44 mk1 mki 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2018 maybe usb compliant, good, 
|-
| &lt;!--Description--&gt;Audient evo4 EVO8 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2020 maybe usb compliant, 
|-
| &lt;!--Description--&gt;Audient iD4 mk2 mkII
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2022 maybe usb compliant, 
|-
| &lt;!--Description--&gt;Audient id14 mk2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2022 maybe usb compliant, good, 
|-
| &lt;!--Description--&gt;Audient iD24 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2023 maybe usb compliant and usb-c bus powered, good, , 0-in/14-out audio interface with ADAT expandability, balanced inserts
|-
| &lt;!--Description--&gt;Audient iD44 Mk2 Mkii 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2022 maybe usb compliant, good, 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Behringer U-PHORIA UMC22 
| &lt;!--Vendor ID--&gt;0x1397
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2014 maybe usb compliant, okay, midas pre-amps
|-
| &lt;!--Description--&gt;Behringer U-PHORIA UMC202HD 
| &lt;!--Vendor ID--&gt;0x1397
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2014 maybe usb compliant, okay, midas pre-amps ein -129 dBu, 24bit ADC, 
|-
| &lt;!--Description--&gt;Behringer U-PHORIA UMC404HD 
| &lt;!--Vendor ID--&gt;0x1397
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2014 maybe usb compliant, okay, midas pre-amps, 24bit adc, 
|-
| &lt;!--Description--&gt;Behringer U-PHORIA UMC204HD 192 Empower Tribe 
| &lt;!--Vendor ID--&gt;0x1397
| &lt;!--Product ID--&gt;0x0508
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2015 maybe usb compliant, okay, midas pre-amps
|-
| &lt;!--Description--&gt;Behringer UMC1820 
| &lt;!--Vendor ID--&gt;0x1397
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2016, bus complaint?, okay midas pre amps, adc, 
|-
| &lt;!--Description--&gt;Behringer U-PHORIA UM2 
| &lt;!--Vendor ID--&gt;0x1397
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2018 maybe usb compliant, poor zenyx pre-amps with high noise floor, plastic build no rf shielding, latency issues, 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Focusrite Saffire 6 USB 1.1
| &lt;!--Vendor ID--&gt;0x1235
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2008 maybe usb compliant, , , midi, strictly NEC USB 2.0, 
|-
| &lt;!--Description--&gt;Focusrite Scarlett 8i6 Gen 1 MOSC0001 
| &lt;!--Vendor ID--&gt;0x1235
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2011 maybe usb compliant, but 
|-
| &lt;!--Description--&gt;Focusrite Scarlett 2i2 Gen 1 MOSC0003 
*TP1 - 3.3V, tested ok
*TP2 - U4 control signal, 3.3V present at all time.
*TP4 - Ground
*TP6 - 48V, tested ok
*TP7 - Ground
*TP8 - Ground
| &lt;!--Vendor ID--&gt;0x1235
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2011 usually avoid early Gen 1, 
|-
| &lt;!--Description--&gt;[https://khronscave.blogspot.com/2021/08/75-focusrite-scarlett-2i4-1st-gen.html Focusrite Scarlet 2i4 Gen 1 (slide toggles) MOSC0004] 
*TP1 - 3.3V, tested 3.22v
*TP2 - U4 control signal, 3.3V present 
*TP4 - Ground
*TP6 - measure 47.72v 
* AKM 4384ET (VDD 5v)
* Cirrus Logic CS4272-CZZ (VA 4.94v/ VD 3.2v/ VL 3.2v)
* all four HC4066 (VCC 4.96v)
* XMOS XS1-L01A-TQ128-C5 (all VDD 1.08v/ all VVDIO 3.23v/ PPLAVDD 0.99v/ PCU-VDDIO 3.23v)
2i4S
*TP1 seems to be 0V
*TP2 should be 5V
*TP3 should be 
*TP6 should be 48V
*TP8 should be 3.3V
| &lt;!--Vendor ID--&gt;0x1235
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2011 maybe usb compliant, pre amps JRC NJM2122 and NJM4565, [https://statics.cirrus.com/pubs/proDatasheet/CS4272_F1.pdf CS4272 adc], [https://pdf.datasheet.live/e5e5fd1c/akm.com/AK4384.pdf AK4384 output pair], Xmos XS1-L8A-64-TQ128 processor and firmware in Winbond 25X40CL 4Mbit, an SMSC Microchip USB3343 interface and a Microchip PL611 clock generator - two Intersil / Renesas ISL97519A for the phantom power rail, two OnSemi NCP1521B for the 3.3V (digital) and 1V (Xmos core) rails - 
|-
| &lt;!--Description--&gt;Focusrite iTrack Solo USB Audio Interface
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2012 maybe usb compliant, 
|-
| &lt;!--Description--&gt;Focusrite Scarlett 18i20 1st Gen MOSC00
| &lt;!--Vendor ID--&gt;0x1235
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2013 maybe usb compliant, , Cirrus CS4272, 
|-
| &lt;!--Description--&gt;[http://wiki.linuxaudio.org/wiki/current_audio_gear Focusrite ] Scarlett 4i4 Gen  MOSC00
| &lt;!--Vendor ID--&gt;0x1235
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt; maybe usb compliant, , Cirrus CS4272, 
|-
| &lt;!--Description--&gt;Focusrite Scarlett 6i6 Gen1 MOSC00
| &lt;!--Vendor ID--&gt;0x1235
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2013 maybe usb compliant, , , 12v psu, the headphone outs mirror the outs on the back panel, so that's six independent outs. 4 independent analog output paths, plus two over spdif, 
|-
| &lt;!--Description--&gt;[https://khronscave.blogspot.com/2019/03/38-focusrite-scarlett-18i8-gen1-teardown.html Focusrite Scarlett 18i8 1st Gen MOSC0008]
| &lt;!--Vendor ID--&gt;0x1235
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2013 maybe usb compliant, JRC NJM4565 provide most of the opamps, pair of JRC NJM2122's for inputs 1 and 2, [http://www.mouser.com/ds/2/76/cs4272_f1-43250.pdf Cirrus CS4272], 12v 1a +central psu to a pair of National Semiconductor LM2672 for 3.3V rail and the +6.9V rail, Xmos XS1–L16A–128 dual-row QFN package, firmware a Winbond 25X40C 4Mbit SPI Flash and an SMSC USB3343 interface chip, the two headphone outs are completely independent so 6 independent analog output paths, plus two over spdif, 
|-
| &lt;!--Description--&gt;Focusrite Clarett+ 8Pre 
| &lt;!--Vendor ID--&gt;0x1235
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2015 great, expensive, maybe usb compliant?  
|-
| &lt;!--Description--&gt;Focusrite Scarlett 2i2 Gen 2 (slide toggles) MOSC0006 
*TP6 should be 48V
| &lt;!--Vendor ID--&gt;0x1235
| &lt;!--Product ID--&gt;0x8202
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2016 maybe usb compliant, USB-b bus powered, good preamps ein equivalent input noise -128 dBu, 24-bit 192kHz CS4272 as well as an additional AKM AK4384ET for the second stereo output pair, 4 screws under bottom rubber,  
|-
| &lt;!--Description--&gt;[https://khronscave.blogspot.com/2021/07/focusrite-scarlett-2i4-2nd-gen-teardown.html Focusrite Scarlett 2i4 Gen 2 (slide toggles) MOSC0014]
*TP6 should be 48V
| &lt;!--Vendor ID--&gt;0x1235
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2016 maybe usb compliant, USB-b bus powered, good preamps NJM2122's, NJM4565's and CMOS switches (HEF4053 and HEF4066), CS4272 and a AKM AK4384ET, Xmos XU208-256-TQ64-C10 with firmware stored in a Macronix MX25L8006E 8Mbit flash memory, clocking by a Cirrus Logic CS2100, an MP1542 boost converter creates +6V and -6V rails, powering the opamps and the rest of the analog circuitry, 
|-
| &lt;!--Description--&gt;Focusrite Scarlett 6i6 Gen2 MOSC0016
| &lt;!--Vendor ID--&gt;0x1235
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2016 maybe usb compliant, 12v psu, 
|-
| &lt;!--Description--&gt;Focusrite Scarlett Solo 2nd Gen MOSC0019
| &lt;!--Vendor ID--&gt;0x1235
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2016 maybe usb compliant, 
|-
| &lt;!--Description--&gt;[https://khronscave.blogspot.com/2024/03/focusrite-scarlett-18i8-gen2-teardown.html Focusrite Scarlett 18i8 2nd Gen MOSC00]
| &lt;!--Vendor ID--&gt;0x1235
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2016 maybe usb compliant, 12v psu, 
|-
| &lt;!--Description--&gt;Focusrite Red 16Line 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2017 may not be compliant as Focusrite provides no drivers - 64-in/64-out Pro Tools - dual Thunderbolt 3 audio interface with ultra-low latency A-D/D-A conversion - Red Evolution mic preamps
|-
| &lt;!--Description--&gt;Focusrite Scarlett Solo 3rd Gen MOSC0024
| &lt;!--Vendor ID--&gt;0x1235
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2019 maybe usb compliant usb-c but usb2, preamps, ad/dc 24bit 192kHz, most Focusrite gen3 interfaces have encrypted processors, 
|-
| &lt;!--Description--&gt;Focusrite Scarlett 18i6 Gen3 MOSC00
| &lt;!--Vendor ID--&gt;0x1235
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2019 maybe usb compliant, USB2 class compliant device, but with custom mixer interface
|-
| &lt;!--Description--&gt;Focusrite Scarlett 2i2 Gen 3 (push in switches) MOSC00
| &lt;!--Vendor ID--&gt;0x1235
| &lt;!--Product ID--&gt;0x8210
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2019 maybe usb compliant, USB-c bus powered, good preamps ein equivalent input noise -128 dBu, 24-bit 192kHz Cirrus Logic xfr002c and cs4272 chips, 
|-
| &lt;!--Description--&gt;Focusrite Scarlett 18i20 3rd gen MOSC00
| &lt;!--Vendor ID--&gt;0x1235
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2019 maybe usb compliant, 
|-
| &lt;!--Description--&gt;Focusrite Scarlett 18i8 3rd Gen MOSC00
| &lt;!--Vendor ID--&gt;0x1235
| &lt;!--Product ID--&gt;0x8214
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2019 maybe usb compliant, , , no screws under the rubber pads on the bottom, 12v psu, 
|-
| &lt;!--Description--&gt;Focusrite Scarlett Solo Studio Mk3 USB Audio Interface MOSC0030 
| &lt;!--Vendor ID--&gt;0x1235
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2020
|-
| &lt;!--Description--&gt;Focusrite Scarlett 2i2 4th Gen USB 
| &lt;!--Vendor ID--&gt;0x1235
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2024 maybe usb compliant, 
|-
| &lt;!--Description--&gt;Focusrite Scarlett 4i4 4th Gen USB 
| &lt;!--Vendor ID--&gt;0x1235
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2024 maybe usb compliant, 
|-
| &lt;!--Description--&gt;Focusrite Scarlett Studio 4th Gen USB 
| &lt;!--Vendor ID--&gt;0x1235
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2024 maybe usb compliant, 
|-
| &lt;!--Description--&gt;Focusrite Scarlett Solo 4th Gen MOSC00
| &lt;!--Vendor ID--&gt;0x1235
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt; maybe usb compliant, 
|-
| &lt;!--Description--&gt;Focusrite Scarlett 18i20 4th Gen MOSC00
| &lt;!--Vendor ID--&gt;0x1235
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2024 maybe usb compliant, 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;FractalAudio FM9 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2018 
|-
| &lt;!--Description--&gt;Fractal Audio AM4 platform 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2023 not working 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Lewitt Connect 6 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt; maybe usb compliant, 
|-
| &lt;!--Description--&gt;Lewitt 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Mooer Steep II Multi-Platform USB Audio Interface 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Motu UltraLite AVB
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt; usb not compliant? 
|-
| &lt;!--Description--&gt;MOTU M2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt; maybe not usb compliant?, usb-c, good pre amps, ad/dc, 
|-
| &lt;!--Description--&gt;MOTU M4 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt; maybe not usb compliant, okay, 
|-
| &lt;!--Description--&gt;MOTU U2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  maybe not usb compliant, good but latest had hardware revision 
|-
| &lt;!--Description--&gt;MOTU UltraLite-mk3
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2010 not usb compliant, great 
|-
| &lt;!--Description--&gt;MOTU UltraLite-mk5
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2020 not usb compliant, great 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Nuemann MT48 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt; usb audio compliant, great pre-amps 
|-
| &lt;!--Description--&gt;Neumann MT48 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;neuralDSP Quad Cortex QC platform 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2024 cc compliant but plugins not working 
|-
| &lt;!--Description--&gt;NeuralDSP QC Lite 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2024 cc complaint 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Neve Genesys Black G16 G32 G64
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt; not compliant - very good very expensive 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Presonus AudioBox USB 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2008 maybe not usb compliant, usb1.1 usb-b bus powered, okay pre-amps, 24bit ADC 48Khz max, 
|-
| &lt;!--Description--&gt;Presonus Audiobox 1818VSL 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2011 maybe not usb compliant, 
|-
| &lt;!--Description--&gt;Presonus AudioBox 44VSL
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2011 may not be usb compliant, 12v psu, 
|-
| &lt;!--Description--&gt;PreSonus AudioBox 22VSL
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2011 maybe not usb compliant, 
|-
| &lt;!--Description--&gt;|PreSonus Studio 2|4 2x2
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt; maybe usb compliant, usb-b, 
|-
| &lt;!--Description--&gt;|PreSonus Studio 2|6 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2017 maybe usb compliant, 
|-
| &lt;!--Description--&gt;|PreSonus Studio 6|8 USB Audio Interface
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2017 maybe compliant, needs ext psu, 
|-
| &lt;!--Description--&gt;PreSonus Studio 24c 2x2
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2019 maybe usb compliant, usb-c, good, adc, 
|-
| &lt;!--Description--&gt;PreSonus Studio 26c 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2019 maybe usb compliant, usb-c, 
|-
| &lt;!--Description--&gt;PreSonus® Studio 68c
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2019 maybe usb compliant, usb-c, 
|-
| &lt;!--Description--&gt;PreSonus AudioBox USB 96 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2020 maybe usb compliant, high preamp noise, 
|-
| &lt;!--Description--&gt;Presonus Quantum ES2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2022 maybe usb compliant, okay, 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Prism 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Prism Lyra 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2013 maybe not usb compliant, great 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Platane UP1 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2024 maybe usb compliant usb- UAC2 asynchronous protocol, 64dB Low-noise Mic amplifier, 32Bit High End ADC and DAC, 16dBu High-power ti headphone amplifier
|-
| &lt;!--Description--&gt;Platane UP2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2024 maybe usb compliant, 
|-
| &lt;!--Description--&gt;Platane 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;RME Babyface/UC/UFX
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2010 maybe not usb compliant, good 
|-
| &lt;!--Description--&gt;RME Fireface UCX
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2012 might be able to put into class compliant cc although a firewire device, pre amps, adc,  
|-
| &lt;!--Description--&gt;RME Babyface Pro FS  
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2019 maybe not usb compliant, good 
|-
| &lt;!--Description--&gt;RME Fireface UCX II
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2021 might be class compliant usb-b, pre amps, adc,  
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Solid State Logic SSL2 SSL2+ Mk1 1st Gen 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2020 maybe usb compliant, good, adc, 
|-
| &lt;!--Description--&gt;Solid State Logic SSL12 SSL18 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2022 maybe usb compliant, bus powered, good pre-amps, up to 32-bit 192kHz AD/DA converters, 12-in 8-out, 
|-
| &lt;!--Description--&gt;Solid State Logic SSL2 SSL2+ MkII 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2024 maybe usb compliant, good pre amps ein -130 dBu, ad/dc, okay latency, 
|-
| &lt;!--Description--&gt;Solid State Logic 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt; maybe usb compliant, 
|-
| &lt;!--Description--&gt; 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;  
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Topping E1x2
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2023 maybe usb compliant, good 
|-
| &lt;!--Description--&gt;Topping Pro E2x2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2023 maybe usb compliant, good 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;UAD UA Apollo 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2012 maybe not usb compliant, 
|-
| &lt;!--Description--&gt;UA apollo 2nd Gen twin X (Duo/Quad), X4, X6, X8, X8P, and X16
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2015 bus compliant?, usb-
|-
| &lt;!--Description--&gt;UA apollo twin x quad 3rd Gen 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2018 bus compliant?, usb-
|-
| &lt;!--Description--&gt;Universal Audio Volt 1
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2021 maybe usb compliant, good, 
|-
| &lt;!--Description--&gt;|Universal Audio Volt 276 2|76 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2021 maybe usb compliant, good, 
|-
| &lt;!--Description--&gt;Universal Audio Volt 2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2022 maybe usb compliant, good, 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| Playback
| Records 
| Opinion 
|-
| &lt;!--Description--&gt;Akai EIE Pro AI01 Electromusic Interface Expander - 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2011 maybe not usb compliant, 4-in/4-out USB 2.0 audio interface with a built-in USB hub and MIDI I/O, up to 24-bit/96kHz 
|-
| &lt;!--Description--&gt;Akai EIE Pro AI02 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt; maybe not usb compliant, 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;|Alesis io2 io|2, io14 io|14, io26 io|26 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no| }}
| &lt;!--Records--&gt;{{no| }}
| &lt;!--Opinion--&gt;2006 bus powered but not usb compliant, okay pre-amps, 2, 4 or 8 mics respectively, 
|-
| &lt;!--Description--&gt;Alesis iO2 Express 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no| }}
| &lt;!--Records--&gt;{{no| }}
| &lt;!--Opinion--&gt;2010  not usb compliant, poor pre-amps, 
|-
| &lt;!--Description--&gt;Alesis Core 1 USB Audio Interface 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2014 maybe cc, mini usb, poor latency, 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Apogee Duet 1 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no| }}
| &lt;!--Records--&gt;{{no| }}
| &lt;!--Opinion--&gt;2009 firewire only, not usb compliant micro-usb with most features, , ,  two‑channel two‑in, two‑out, 
|-
| &lt;!--Description--&gt;Apogee Ensemble 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no| }}
| &lt;!--Records--&gt;{{no| }}
| &lt;!--Opinion--&gt;2009 firewire, not usb compliant micro-usb with most features, , ,  two‑channel 
|-
| &lt;!--Description--&gt;Apogee One USB 1st Gen 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2010 maybe not usb compliant micro-usb for basic features, , , single‑channel up to 48kHz
|-
| &lt;!--Description--&gt;Apogee One USB 2nd Gen 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2013 maybe usb compliant usb- and maybe aa batteries, 
|-
| &lt;!--Description--&gt;Apogee Duet 2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2022 maybe usb compliant usb-c with most features, , , 
|-
| &lt;!--Description--&gt;Apogee One USB 3rd Gen 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2016 maybe usb compliant, 
|-
| &lt;!--Description--&gt;Apogee Ensemble Thunderbolt 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2020 maybe not usb compliant micro-usb with most features, , ,  two‑channel 
|-
| &lt;!--Description--&gt;Apogee Boom 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2022 maybe usb compliant usb-c, , , 
|-
| &lt;!--Description--&gt;Apogee Duet 3 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2022 maybe usb compliant usb-c with most features, , , 
|-
| &lt;!--Description--&gt;Apogee 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;ART PRO Audio Usb Mix 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2016 maybe usb compliant bus powered, 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Avid Digidesign Mbox 1 USB Audio 
| &lt;!--Vendor ID--&gt;0x0dba
| &lt;!--Product ID--&gt;01000
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no| }}
| &lt;!--Records--&gt;{{no| }}
| &lt;!--Opinion--&gt;2002 mbox original was usb1 and not a usb class compliant device, and had the much hated &quot;focusrite designed&quot; mic preamps, light blue front plate and the sticky out feet 
|-
| &lt;!--Description--&gt;Avid Digidesign Mbox 2 USB Audio 
| &lt;!--Vendor ID--&gt;0x0dba
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no| }}
| &lt;!--Records--&gt;{{no| }}
| &lt;!--Opinion--&gt;2005 midi not usb compliant 
|-
| &lt;!--Description--&gt;Avid Digidesign Mbox 2 Pro USB Audio 
| &lt;!--Vendor ID--&gt;0x0dba
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no| }}
| &lt;!--Records--&gt;{{no| }}
| &lt;!--Opinion--&gt;2006 not usb compliant 
|-
| &lt;!--Description--&gt;Avid Digidesign Mbox 2 Mini USB Audio 
| &lt;!--Vendor ID--&gt;0x0dba
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no| }}
| &lt;!--Records--&gt;{{no| }}
| &lt;!--Opinion--&gt;2007 not usb compliant 
|-
| &lt;!--Description--&gt;Avid Digidesign Mbox 2 Micro USB Audio 
| &lt;!--Vendor ID--&gt;0x0dba
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no| }}
| &lt;!--Records--&gt;{{no| }}
| &lt;!--Opinion--&gt;2009 not usb compliant 
|-
| &lt;!--Description--&gt;AVID MBox 3rd gen Mini or Standard but Pro is Firewire 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2010 maybe usb compliant, 
|-
| &lt;!--Description--&gt;behringer u-control uca202 
| &lt;!--Vendor ID--&gt;0x8bb
| &lt;!--Product ID--&gt;0x2902
| &lt;!--Revision--&gt;1.00
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2008 maybe usb compliant, draws a lot of power - dac ti burr-brown - no microphone pre-amp - 
|-
| &lt;!--Description--&gt;Behringer U-CONTROL UCA 222 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2009 maybe usb compliant,  - no microphone pre-amp - 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Black Lion Audio 2x2 evolution 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2021 maybe usb compliant but , okay with 109dB range - poor noise floor, 24-bit 192kHz Cirrus Logic CS4272, average latency, 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Bomge 11s 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2021 
|-
| &lt;!--Description--&gt;Bomge 22s 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2021 
|-
| &lt;!--Description--&gt;Bomge BMG22 USB Audio Interface 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2021 usb-c, 24bit 192kHz but only use much lower, may have to spend time cleaning up some of the noise, high latency, 
|-
| &lt;!--Description--&gt;Bomge U202 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2022 usb-c, 32bit 192kHz but only use much lower, may have to spend time cleaning up some of the noise, high latency, 
|-
| &lt;!--Description--&gt;Bomge U204 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2022 usb-c, 32bit 192kHz but only use much lower , may have to spend time cleaning up some of the noise, high latency, 
|-
| &lt;!--Description--&gt;Bomge Mini 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2024 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;TI Burr-Brown PCM2702E PCM2704 PCM2704C Muse Audio Mini USB DAC board 
| &lt;!--Vendor ID--&gt;0x08bb 
| &lt;!--Product ID--&gt;0x2704
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt; maybe usb compliant, no mic input - goodish quality
|-
| &lt;!--Description--&gt;TI Burr-Brown PCM2900 PCM2902 PCM2906 USB DAC board 
| &lt;!--Vendor ID--&gt;0x08bb
| &lt;!--Product ID--&gt;0x2900
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt; maybe usb compliant, no mic input - goodish quality 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Depusheng MD22 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2022 usb-b powered, 24bit 192kHz though is 96kHz, 
|-
| &lt;!--Description--&gt;Depusheng USB Audio 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2023 usb-b powered, 24bit 192kHz though is 96kHz, 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;|Emagic emi 2|6 em2|6 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2002 not uac 
|-
| &lt;!--Description--&gt;|Emagic emi 6|2m 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2005 not uac 
|-
| &lt;!--Description--&gt;|Emagic emi 6|2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2005 not uac 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Ego Systems, Inc. in Korea (ESI) joining with RIDI GmbH 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2006 maybe not usb compliant, 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;esi Mixvibes U46 Mk II USB audio 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no| }}
| &lt;!--Records--&gt;{{no| }}
| &lt;!--Opinion--&gt;2007 not usb compliant, usb-b powered, 
|-
| &lt;!--Description--&gt;ESI ESU22
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2008 maybe not usb compliant, 
|-
| &lt;!--Description--&gt;esi U24XL 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2008 maybe usb compliant, usb-b powered, 24 bits, 2 analogue inputs and outputs with 6.3 mm jack connection, Output L can be used as a headphone output, S / PDIF digital input - 
|-
| &lt;!--Description--&gt;esi U46XL 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2008 maybe usb compliant, usb-b powered, 
|-
| &lt;!--Description--&gt;ESI Originals, Inc ESIO MAYA22USB 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2013 maybe usb compliant, usb-b powered, 1 xlr, 
|-
| &lt;!--Description--&gt;ESI MAYA44USB+ 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2013 maybe usb compliant, usb-b powered,  xlr, 
|-
| &lt;!--Description--&gt;ESI Originals, Inc ESIO MARA22XTU 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2014 maybe usb compliant, usb-b powered, 1 xlr, 
|-
| &lt;!--Description--&gt;ESI U22XT
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2016 usb class compliant
|-
| &lt;!--Description--&gt;ESI Gigaport Ex
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2020 usb compliant?, usb-c usb3.1, , , 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;iConnectivity iConnectAUDIO2+ icaudio-02 USB audio interface
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;{{unk|2016 }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;LexiconPro - Omega 8x4x2 (USB-1.1)
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no| }}
| &lt;!--Records--&gt;{{no| }}
| &lt;!--Opinion--&gt;2003 not usb complaint 
|-
| &lt;!--Description--&gt;Lexicon Alpha 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no| }}
| &lt;!--Records--&gt;{{no| }}
| &lt;!--Opinion--&gt;2006 not usb compliant, 
|-
| &lt;!--Description--&gt;Lexicon Lambda
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2006 may not be compliant, 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Line 6 Toneport UX1 and Tone Port UX2
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2004  not usb compliant, 
|-
| &lt;!--Description--&gt;Line 6 TonePort UX8 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2005 maybe not class compliant, 
|-
| &lt;!--Description--&gt;Line 6 POD Studio UX1 UX2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2006  not usb compliant, 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Lokchonk UX22 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;[https://www.youtube.com/watch?v=ljSiNmudMm0 Lokchonk UX44HD] 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2023 usb-b , , , 2in 2out only, average latency, 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Mackie Onyx Artist 1·2
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2006 maybe not usb compliant, usb-b powered, 
|-
| &lt;!--Description--&gt;Mackie Onyx Producer 2X2 USB Audio Interface 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2008 maybe usb compliant, usb-b midi 
|-
| &lt;!--Description--&gt;Mackie Onyx Blackjack
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2011 USB powered but maybe not usb compliant, Two Onyx Preamps, 2-in, 2-out which are combo Neutrik-type connectors to handle XLR, instrument or line level 
|-
| &lt;!--Description--&gt;Mackie 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2011 maybe usb compliant, , , 
|-
| &lt;!--Description--&gt;Media Assistance USB-One
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no| }}
| &lt;!--Records--&gt;{{no| }}
| &lt;!--Opinion--&gt;2009 not uac cc comliant, 
|-
| &lt;!--Description--&gt;M-Audio Fast Track USB 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2004 maybe not usb compliant, - guitar 
|-
| &lt;!--Description--&gt;M-Audio Fast Track Ultra (6 in 6 out) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2008 maybe usb cc providing 24-bit/96kHz audio capabilities but requires manual configuration of the mixer settings 
|-
| &lt;!--Description--&gt;M-Audio M-Track 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2008 usb compliant?, okay - guitar and vocal mainly 
|-
| &lt;!--Description--&gt;[https://htyp.org/M-Audio/Fast_Track_Ultra/Linux M-Audio FastTrack Ultra] and Ultra 8R 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2010 maybe usb compliant, low round-trip latency, okay octane pre amps, adc, 
|-
| &lt;!--Description--&gt;M-Audio M-Track 2x2M
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2016 usb compliant? usb-c - okay pre-amps, , 
|-
| &lt;!--Description--&gt;M-Audio M-Track (MkII) 2x2
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2016 usb compliant? usb-c - okay pre amps, , 
|-
| &lt;!--Description--&gt;M-Audio M-Track Solo 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2021 usb compliant? - okay but issues, MJN4580C opamps (lower gain 55 dB at volume 9-10), ti PCM2900C ADC 16bit means there is a hard noise floor at -96 dB, plastic build no rf shielding, 
|-
| &lt;!--Description--&gt;M-Audio M-Track DUO 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2021 usb compliant? - okay but issues, MJN4580C opamps (lower gain 55 dB at volume 9-10), ti PCM2900C ADC 16bit means there is a hard noise floor at -96 dB, plastic build no rf sheild, 
|-
| &lt;!--Description--&gt;M-Audio Air
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt; maybe usb compliant, okay 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;NI AK1 
| &lt;!--Vendor ID--&gt;0x17CC
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2008 maybe usb compliant, 
|-
| &lt;!--Description--&gt;[https://www.pogo.org.uk/~mark/linuxdj/ Native Instruments Traktor Audio 8 DJ], [ Traktor Audio 4 DJ], [ Traktor Audio 2 DJ], 
| &lt;!--Vendor ID--&gt;0x17cc
| &lt;!--Product ID--&gt;0x1978, 0x0839, 0x041C 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no| }}
| &lt;!--Records--&gt;{{no| }}
| &lt;!--Opinion--&gt;2009 not usb compliant uses snd-usb-caiaq module, [https://mixxx.discourse.group/t/problems-with-native-instruments-audio-8-dj-on-linux/14719/2 Audio 8 device has 4 subunits which are not recognized correctly], Cirrus Logic DACs spec'd at 24-bit/96KHz over a USB2, 
|-
| &lt;!--Description--&gt;NI Komplete Audio 6 Mk1 
| &lt;!--Vendor ID--&gt;0x17CC
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2011 maybe usb compliant, pre amps, 24bit 96kHz adc, ocassional dropouts, plastic build top with metal around 3/4, 
|-
| &lt;!--Description--&gt;Native Instruments NI Komplete Audio 1 and 2 USB 
| &lt;!--Vendor ID--&gt;0x17CC
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2019 maybe usb compliant, good pre amp ein -129.5 dBu, ad/dc, 
|-
| &lt;!--Description--&gt;[https://support.native-instruments.com/hc/en-us/articles/360014683497-Apple-Silicon-Compatibility-News Native Instruments Komplete Audio 6 Mk2] 
| &lt;!--Vendor ID--&gt;0x17CC
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2019 maybe usb compliant, pre amps, 24bit 192kHz adc, black aluminum glass build, 
|-
| &lt;!--Description--&gt;[ Native Instruments Traktor Pro] 
| &lt;!--Vendor ID--&gt;0x17cc
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2023 maybe usb compliant 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Novation AudioHub 2x4 NOVHUB01 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2008 maybe usb compliant, usb-b powered, no xlr, focusrite sounds inside, 
|-
| &lt;!--Description--&gt;Novation AudioHub 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt; maybe usb compliant, 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Prodipe Studio 22 Pro
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt; maybe not usb compliant, 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Schiit HEL 1 USB Audio Interface 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2019
|-
| &lt;!--Description--&gt;Schiit HEL 2 USB Audio Interface 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2021 gaming headsets mostly 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Roland Edirol UA-3 Audio Capture
| &lt;!--Vendor ID--&gt;0x0582
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;1998 maybe not usb compliant, 
|-
| &lt;!--Description--&gt;Roland Edirol UA-30 Audio Capture
| &lt;!--Vendor ID--&gt;0x0582
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no|no driver}}
| &lt;!--Records--&gt;{{no|no driver}}
| &lt;!--Opinion--&gt;1999 not usb compliant, 
|-
| &lt;!--Description--&gt;Roland Edirol UA1A UA-1D Audio Capture
| &lt;!--Vendor ID--&gt;0x0582
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no|no driver}}
| &lt;!--Records--&gt;{{no|no driver}}
| &lt;!--Opinion--&gt;2000 not usb compliant, 
|-
| &lt;!--Description--&gt;Roland Edirol UA-5 Audio Capture (Roland)
| &lt;!--Vendor ID--&gt;0x0582
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no|no driver}}
| &lt;!--Records--&gt;{{no|no driver}}
| &lt;!--Opinion--&gt;2000 not usb compliant, 
|-
| &lt;!--Description--&gt;Roland Edirol UA-1000 Audio Capture
| &lt;!--Vendor ID--&gt;0x0582
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no|no driver}}
| &lt;!--Records--&gt;{{no|no driver}}
| &lt;!--Opinion--&gt;2004 not usb compliant, 
|-
| &lt;!--Description--&gt;Roland Edirol UA-1EX, Cakewalk UA-1G  
| &lt;!--Vendor ID--&gt;0x0582
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no|no driver}}
| &lt;!--Records--&gt;{{no|no driver}}
| &lt;!--Opinion--&gt;2005 not usb compliant driver also supports ASIO (Steinberg Audio Stream I/O Interface), noisy 
|-
| &lt;!--Description--&gt;Roland Duo Capture UA-11 
| &lt;!--Vendor ID--&gt;0x0582
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no|no driver}}
| &lt;!--Records--&gt;{{no|no driver}}
| &lt;!--Opinion--&gt;2006 not usb compliant, 
|-
| &lt;!--Description--&gt;Roland QUAD-CAPTURE Analog 2x2 Digital 2x2 USB 2.0 4in/4out
| &lt;!--Vendor ID--&gt;0x0582
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no|no driver}}
| &lt;!--Records--&gt;{{no|no driver}}
| &lt;!--Opinion--&gt;2005 not usb compliant, usb-b powered 
|-
| &lt;!--Description--&gt;[https://wiki.debian.org/DebianEdu/Documentation/Manuals/Rosegarden/Setup Roland Edirol UA-101 and UA-1000 (Clemens Ladisch driver)]
| &lt;!--Vendor ID--&gt;0x0582
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no| }}
| &lt;!--Records--&gt;{{no| }}
| &lt;!--Opinion--&gt;2006 not usb compliant, 
|-
| &lt;!--Description--&gt;[https://github.com/mmueller-kaffeeschluerfercom/UA-25-Firmware-Modification Roland Edirol ua-25]
| &lt;!--Vendor ID--&gt;0x0582
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2007 maybe usb compliant 16bit 44.1kHz sampling without MIDI but not USB class complient when in Advanced mode for 24bit or midi 
|-
| &lt;!--Description--&gt;Edirol by Roland USB AudioCapture UA-25EX 
| &lt;!--Vendor ID--&gt;0x0582
| &lt;!--Product ID--&gt;0x00e6, 0x00e7
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2008 maybe usb compliant if ADVANCED DRIVER switched to OFF might play and record at 44.1kHz and 16-bit samples 
|-
| &lt;!--Description--&gt;Roland Audio Interface V-Studio 20 VS-20 Cakewalk
| &lt;!--Vendor ID--&gt;0x0582
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no| }}
| &lt;!--Records--&gt;{{no| }}
| &lt;!--Opinion--&gt;2010 maybe not usb compliant, usb-b powered, 1 xlr, 
|-
| &lt;!--Description--&gt;Roland Edirol UA55 UA-55 Quad Cakewalk 
| &lt;!--Vendor ID--&gt;0x0582
| &lt;!--Product ID--&gt;0x012f
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no| }}
| &lt;!--Records--&gt;{{no| }}
| &lt;!--Opinion--&gt;2011 not USB class compliant, 
|-
| &lt;!--Description--&gt;Roland DUO-CAPTURE EX UA-22 USB Audio
| &lt;!--Vendor ID--&gt;0x0582
| &lt;!--Product ID--&gt;0x0159
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2013 maybe usb compliant but not be used with a USB 3.0 port that is not compatible with USB 2.0 specification, vs pre amps, adc, three AA batteries in base, or an AC adapter psb-1u 9V 2A - 
|-
| &lt;!--Description--&gt;Roland Rubix series Roland Rubix22 USB 2.0 Audio Interface
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2017 maybe usb compliant, 
|-
| &lt;!--Description--&gt;Roland Rubix series Roland Rubix24 USB 2.0 Audio Interface
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2017 maybe usb compliant, 
|-
| &lt;!--Description--&gt;Roland 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt; maybe usb compliant 
|-
| &lt;!--Description--&gt;Steinberg MI2, Steinberg MI4
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no| }}
| &lt;!--Records--&gt;{{no| }}
| &lt;!--Opinion--&gt;2004 not usb compliant, 
|-
| &lt;!--Description--&gt;Steinberg (2004 Yamaha buys) MIDI interface hardware including the CC like CC121 CC-121 and CI1 CI2 series.
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no|no driver}}
| &lt;!--Records--&gt;{{no|no driver}}
| &lt;!--Opinion--&gt;2008 not usb compliant, 
|-
| &lt;!--Description--&gt;Steinberg UR12 UR22
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2013 maybe not usb compliant, poor pre-amps, 
|-
| &lt;!--Description--&gt;Steinberg UR44 usb audio interface
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2014 maybe not usb compliant, poor pre-amps, 
|-
| &lt;!--Description--&gt;Steinberg UR242 audio interface
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2015 maybe usb compliant, usb powered or 5v psu, okay pre-amps, 
|-
| &lt;!--Description--&gt;Steinberg UR22mkII 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2018 maybe usb compliant, okay pre-amps ein -123 dBu, ad/dc, 
|-
| &lt;!--Description--&gt;Steinberg UR-RT 2 USB Audio Interface 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2018 maybe usb compliant, usb2.0 usb-b, pre-amps, ad/dc, 
|-
| &lt;!--Description--&gt;Steinberg UR44C (USB3) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2019 maybe usb compliant, 
|-
| &lt;!--Description--&gt;Steinberg URX22C UR22C  
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2021 maybe usb compliant, preamps okay but little noisy, ad/dc. 
|-
| &lt;!--Description--&gt;Steinberg UR22 MkIII UR series
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2024 maybe usb compliant usb-c, okay pre-amps, adc, 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Tapco LiNK.USB 2x2 (Loud technologies WA, USA) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no| }}
| &lt;!--Records--&gt;{{no| }}
| &lt;!--Opinion--&gt;2005 maybe not compliant, usb-b, poor pre-amps hum, latency issues, 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;[https://git.alsa-project.org/?p=alsa-tools.git;a=blob;f=usx2yloader/README;hb=3843634ef0310a952b256bcb6a4ddd0ad4ebe396 Teac Tascam US-422 US-428 US2XYloader] 
| &lt;!--Vendor ID--&gt;0x0644
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no|no driver}}
| &lt;!--Records--&gt;{{no|no driver}}
| &lt;!--Opinion--&gt;2000 not usb compliant, 
|-
| &lt;!--Description--&gt;Tascam US-122 US-224 
| &lt;!--Vendor ID--&gt;0x0644
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no|no driver}}
| &lt;!--Records--&gt;{{no|no driver}}
| &lt;!--Opinion--&gt;2003 not usb compliant, needing firmware usx2yloader/us122fw.ihx for audio sound card - Tascam US-122 and US-122L are not the same - 
|-
| &lt;!--Description--&gt;Tascam US-122L 
| &lt;!--Vendor ID--&gt;0x0644
| &lt;!--Product ID--&gt;0x800e
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no|no driver}}
| &lt;!--Records--&gt;{{no|no driver}}
| &lt;!--Opinion--&gt;2006 not usb compliant, obsolete needs tascam_loader.ihx and us122fw.ihx firmware loaded each time unless automated 
|-
| &lt;!--Description--&gt;Tascam US122 US-122 Mk2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no|no driver}}
| &lt;!--Records--&gt;{{no|no driver}}
| &lt;!--Opinion--&gt;2004 not usb compliant although USB2 downgrade so using USB1.1 UHCI, tascam units suffer from high round-trip latency as do most typical USB units
|-
| &lt;!--Description--&gt;Tascam US144 US-144 Mk2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no|no driver}}
| &lt;!--Records--&gt;{{no|no driver}}
| &lt;!--Opinion--&gt;2004 maybe usb compliant although USB2 downgrade so using USB1.1 UHCI, tascam units suffer from high round-trip latency as do most typical USB units
|-
| &lt;!--Description--&gt;Teac TASCAM US-200 USB 2.0 Audio / MIDI Interface 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no|no driver}}
| &lt;!--Records--&gt;{{no|no driver}}
| &lt;!--Opinion--&gt;2011 maybe not usb compliant, 
|-
| &lt;!--Description--&gt;Teac US-366 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no|no driver}}
| &lt;!--Records--&gt;{{no|no driver}}
| &lt;!--Opinion--&gt;2011 maybe not usb compliant, 
|-
| &lt;!--Description--&gt;Teac TASCAM US-600 USB 2.0 Audio / MIDI Interface 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no|no driver}}
| &lt;!--Records--&gt;{{no|no driver}}
| &lt;!--Opinion--&gt;2011 maybe not usb compliant, 
|-
| &lt;!--Description--&gt;Teac TASCAM US-800 USB 2.0 Audio / MIDI Interface 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no|no driver}}
| &lt;!--Records--&gt;{{no|no driver}}
| &lt;!--Opinion--&gt;2011 may not be totally usb compliant 
|-
| &lt;!--Description--&gt;Teac Tascam iU2
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{no| }}
| &lt;!--Records--&gt;{{no| }}
| &lt;!--Opinion--&gt;2012 maybe not usb compliant, 
|-
| &lt;!--Description--&gt;Teac Corp Tascam US-2x2
| &lt;!--Vendor ID--&gt;0x0644
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2014 usb compliant?, 5v dc power, midi out in, 
|-
| &lt;!--Description--&gt;Teac Corp Tascam US-4x4
| &lt;!--Vendor ID--&gt;0x0644
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt; usb compliant?, 
|-
| &lt;!--Description--&gt;Teac Tascam US-16x08 US-20x20
| &lt;!--Vendor ID--&gt;0x0644
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt; 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;teyun q12 Q-12, q22 Q-22 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt; maybe usb compliant - unknown pre amp, unknown ad/dc, 
|-
| &lt;!--Description--&gt;Teyun q26 Q-26, q24 Q-24 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt; maybe usb compliant - unknown pre amp, unknown ad/dc, 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Yamaha UW500
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2000 not class compliant, 
|-
| &lt;!--Description--&gt;Yamaha Audiogram 3 USB Digital Audio Interface 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2012 maybe usb compliant, okay pre amp, 16bit 44kHz adc no advanced features without dedicated asio driver, 1 xlr, 1 instrument, 
|-
| &lt;!--Description--&gt;Yamaha Audiogram 6 USB Digital Audio Interface 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2013 maybe usb compliant, okay, 2 xlr, 2 instrument, 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Zoom UAC-232 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt; maybe not usb compliant, okay, 
|-
| &lt;!--Description--&gt;Zoom UAC
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt; maybe not usb compliant, okay, 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| Playback
| Records 
| Opinion 
|-
| &lt;!--Description--&gt;[http://www.arcam.co.uk/products,rseries,usb-dacs,rPAC.htm Arcam rPac] 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Audioquest Dragonfly 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Audioengine D1 Premium 24-bit DAC 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Beresford TC-7520 (Burr Brown PCM 1716) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Beresford TC-7520 + Burson Buffer + MK3 JKSPDIF
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;[http://epiphany-acoustics.co.uk/products-page/dacs/e-dac-24bit-miniature-usb-dac/ Epiphany E-DAC 24bit] ES9023 DAC chip 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Firestone Audio FUBAR II Mk2
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Firestone Audio iLoveTW 24Bit USB DAC
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;FiiO D5 ta2020 chip amp 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;FiiO E07K Andes 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;FiiO E17 Alpen 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;GoVibe Magnum 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;GoVibe Martini-U 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;GoVibe Vulcan 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Halide Design DAC HD (Wolfson WM8716) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;HRT Steamer II USB DAC 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;John Kenny JKDAC uses a 24-bit/192&amp;nbsp;kHz Sabre ES9022 DAC or better JKDAC32 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt; iBasso D12  
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Leckerton UHA-6S MKII  
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;MyST 1866 PortaDAC 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Objective DAC ODAC+O2  
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Rega DAC (Wolfson WM8742) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| Playback
| Records 
| Opinion 
|-
| &lt;!--Description--&gt;[http://www.henryaudio.com/open-source.php Henry Audio USB DAC 128 also known as QNKTC AB-1.2 open source DAC] 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Henry Audio mkII 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;AKM4430 DAC chip comes from Asahi Kasai 
|-
| &lt;!--Description--&gt;DevilSound USB DAC 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Zoom U series
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;KingRex UD-01 SE (Burr-Brown PCM 2702E) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;SuperPro 24/192 USB DAC (24bit 192&amp;nbsp;kHz, CS-4398 D/A chip) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| Playback
| Records 
| Opinion 
|-
| CMedia CM108 7.1ch emulation I2S in and out
| 0x1926
| 0x0003
| 0x0100
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| [http://www.lindy.co.uk/usb-2-audio-adapter/42961.html Lindy USB 2.0] (Chipset CM108)
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| Speed-Link SL-8850-SBK Vigo ([http://mightyohm.com/forum/viewtopic.php?p=1036#p1030 CMedia CM108])
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| Dynamode USB SOUNDCARD 2.0 
| &lt;!--Vendor ID--&gt;0x0003
| &lt;!--Product ID--&gt;0x1130
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| Dynamode Virtual 7.1 USB-SOUND7 (C-Media )
| 0x0d8c
| 0x000c 0x000e
| 1.00
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Generic White box with very little red led and white USB lead (CMedia )
| &lt;!--Vendor ID--&gt;0x0d8c
| &lt;!--Product ID--&gt; 0c000e
| &lt;!--Revision--&gt;1.00
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| Playback
| Records 
| Opinion 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| CM109 CiT SC-U119 5.1 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| Playback
| Records 
| Opinion 
|-
| CMedia CM1197.1ch I2C MCU port Penguin 
| 0x0D8C
| 0x0000
| 0x010
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| Playback
| Records 
| Opinion 
|-
| &lt;!--Description--&gt;Sweex 7.1 Startech External USB, WMA Blue metal box SYBA SD-AUD20040, Sabrent USB-SND8, Sewell Vantec NBA-200U (C-Media CM6206 CM106 like) 
| &lt;!--Vendor ID--&gt;0x0d8c
| &lt;!--Product ID--&gt;0x0102
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;50/50 if the item is detected but does not work 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Creative Labs SoundBlaster X-fi 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Creative X-Fi Go 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Creative X-Fi 5.1
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Creative Sound Blaster Play! USB sound adapter (SB1140) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt; working with [http://www.amiga.org/forums/showpost.php?p=646431&amp;postcount=15 Deneb on OS3] 
|-
| &lt;!--Description--&gt;Asus Xonar U1 (ASUS UA100 USB Audio Chip) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Asus Xonar U3 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| Playback
| Records 
| Opinion 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Griffin iMic 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;M-Audio Transit
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Icemat Siberia (steel series) (Cmedia chipset) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;JMTek HY554, ZyXEL NSA-220, Logilink (Tenx Technology TP6911 and SSS-1623 headphone set) 
| 0x0C76 0x1130
| 0x1605 0x1607  0xf211
| 0x
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt; reports on other OS not good 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Plantronics &quot;DSP Adapter-01&quot; (or &quot;USB Adapter-02&quot;) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Rocksmith Real Tone Cable 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;RSA Intruder Predator 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;StarTech ICUSBAUDIO7
| &lt;!--Vendor ID--&gt;0x0d8c
| &lt;!--Product ID--&gt;0x000c
| &lt;!--Revision--&gt;1.00
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Stoner Acoustics UD100 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Teac UDH01-B  
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Terratec Aureon 5.1 USB
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Terratec Aureon 5.1 USB MKII
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;TerraTec Electronic GmbH Aureon Dual USB
| 0x0ccd
| 0x0077 
| &lt;!--Product ID--&gt; 
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Terratec Phase26
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Trust 510 EX 5.1
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Logitech A-5572A USB 2.0  to 3.5mm jacks Virtual 7.1 Surround Sound Adapter or accessory of Logitech Clearchat pro USB or Logitech USB Headset H530 
| &lt;!--Vendor ID--&gt;0x0003 
| &lt;!--Product ID--&gt;0x046D
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Trumix TM-10 USB Audio Interface 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;2024  maybe cc 
|-
| &lt;!--Description--&gt;Trumix TM-12 USB-C 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;2024 maybe cc usb compliant, 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Turtle Beach Audio Advantage Amigo Micro II USB Sound Card &amp; Headset Adapter 
| &lt;!--Vendor ID--&gt;0x10F5
| &lt;!--Product ID--&gt;0x0211
| &lt;!--Revision--&gt;0100
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;Vantec NBA-100U 7.1 Channel 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt;{{unk| }}
| &lt;!--Records--&gt;{{unk| }}
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Playback--&gt; 
| &lt;!--Records--&gt;
| &lt;!--Opinion--&gt;
|}

 Companies including Access, Alesis, Allen&amp;Heath, American Audio, CME, ESI, Infrasonic, Lexicon, Numark, Presonus, Reloop, SIMS, Sound Devices, Steinberg, Swissonic, Tascam, Terrasoniq, Terratec, Yamaha and Yellowtec decided to license and bundle this driver. So fully functional custom drivers are available for Access Virus TI, Access Virus TI snow, Alesis Multimix 8 USB2.0, Alesis Multimix 16 USB2.0, Allen&amp;Heath XONE:2D, Allen&amp;Heath XONE:3D, Allen&amp;Heath XONE:4D, Allen&amp;Heath XONE:DX, Allen&amp;Heath XONE:DB4, American Audio Versa Port, CME XCORPIO, ESI ESU1808, ESI Gigaport AG / DG, ESI Maya 44 USB, Infrasonic Amon, Lexicon I-ONIX U22, Lexicon I-ONIX U42S, Lexicon I-ONIX U82S, Mindprint DI-MOD USB, Numark DJ IO, Numark NS6, Numark NS7, Numark Omni Control, Numark V7, Presonus Audiobox USB, Reloop Digital Jockey, SIMS Primus, Sound Devices USB pre, Steinberg MI2, Steinberg MI4, Swissonic Easy USB, Tascam M-164UF, Tascam US-122L, Tascam US-144, Tascam US-Tascam US-144mkII 122mkII, Tascam US-200, Tascam US-600, Tascam US-1641, Tascam US-1800, Tascam US-2000, Terratec Area 61, Terrasoniq Phase X64, Terratec Phase 26 USB, Yamaha UW10, Yamaha UW500, Yellowtec PUC2 and many others.

Well, those companies are using the same driver framework because all of those interfaces use the same microprocessor/firmware architecture to communicate with the USB bus. Just like almost all FireWire audio interfaces use the same TC Dice or BridgeCo chipsets. Usually it does not make sense for companies to develop their own USB1.1/USB2/FW framework for a product they are going to sell for &lt;$500.

However, that isn't the end of the story. The companies who develop audio interfaces implement different features into their devices and must update the driver and firmware to accommodate those features. That is where things can go wrong. Sometimes there is miss-communication about how things are coded, sometimes the developer who started a project leaves without transferring his knowledge to his successor, etc. You have to keep in mind that there are no &quot;big&quot; computer audio companies. Even the companies that seem big in the scale of the market, probably have fewer employees than you'd think.

A very well made interface that is designed from scratch from the ground up would be a very expensive device, regardless of whether it's USB, FW, PCIe or whatever.

Round-trip latency is the sum of the following:
&lt;pre&gt;
    ASIO input buffer
    ASIO output buffer
    A/D D/A converter latency
    The driver's hidden safety buffer
&lt;/pre&gt;
At a 64-sample ASIO buffer size/44.1k, Tascam units yield ~18ms total round-trip latency.

Typical USB audio interfaces use a large hidden safety buffer.
This helps ensure glitch-free playback... even under less than ideal circumstances. But... this comes at the expense of much higher round-trip latency. Short of doubling the sample-rate, there's no means of mitigating the higher round-trip latency.
If you have no plans of ever monitoring in realtime thru software based EFX/processing (ie: playing/monitoring DI bass thru an AmpSim plugin as you're playing), then this may not matter to you.
If you want the ability this play/monitor in realtime thru software based EFX/processing, make sure to get an audio interface that yields low round-trip latency.

As a point of reference the best PCI/e audio interfaces yield about 5ms total round-trip latency at a 64-sample ASIO buffer size/44.1k
The best Firewire and USB units yield 5.5-5.6ms total round-trip latency at those same settings.
Typical USB and Firewire units (that use a large hidden safety buffer) yield 12-18ms total round-trip latency at those same settings.

Anything above ~6ms starts to feel sluggish.
Anything above ~10ms feels like playing thru molasses.


USB Microphones 
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;C-Media Electronics, Inc. CM108 Audio Controller Mic
| &lt;!--Vendor ID--&gt;0x0d8c
| &lt;!--Product ID--&gt;0x013c 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Elgato WaveMic 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Elgato Wave:1
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2019 no driver }}
|-
| &lt;!--Description--&gt;Elgato Wave:3
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2019 no driver lightweight }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;hyperx solocast 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2018 no driver}}
|-
| &lt;!--Description--&gt;hyperx quadcast 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2018 no driver}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Sennheiser CC510 USB 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| Opinion 
|-
| &lt;!--Description--&gt;Alesis USB-Mic microphone podcasting kit 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Audio-Technica AT2020 (AT202) AT4040
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Audio-Technica AT2035 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Behringer B1 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Blue Microphones Snowball 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Blue Microphones Snowball iCE
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| cardioid only }}
|-
| &lt;!--Description--&gt;Blue Microphones Yeti 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|can pick up a lot of background noise but not sure if right mode used }}
|-
| &lt;!--Description--&gt;Blue Microphones Yeti Pro 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| can pick up a lot of background noise but not sure if right mode used }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;MXL 2001A/600 Studio Microphone Pack / MXL 2003A Studio Condenser
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Microsoft LifeChat LX-3000 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Namtai SingStar(TM) PS2 SCEH-0001 USBMIC 
| &lt;!--Vendor ID--&gt;0x1415
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;0.01
| &lt;!--Opinion--&gt;{{unk| mono microphones }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Neumann MT48 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Razer Seiren X 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Razer Seiren Mini USB Condenser Microphone 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Rockband USB Mic 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Rode NT1A VideoMic Pro 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Rode Podcaster 2 USB 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| RODECaster Pro usb audio compatible}}
|-
| &lt;!--Description--&gt;Rode NT1A NT2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|  NT2 better }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Roland R-07
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Samson Go Mic - Portable USB Microphone for Recording 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| mini usb r.h.s. and clip on the bottom left hand side}}
|-
| &lt;!--Description--&gt;Samson Go Mic Clip On USB Microphone 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| switch to choose between Cardiod, Omni and -10&amp;nbsp;dB modes, a 3.5mm headphone socket and a USB socket}}
|-
| &lt;!--Description--&gt;Samson C01U  
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| cardoid only}}
|-
| &lt;!--Description--&gt;Samson C03U 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Shure MV7 USB Podcast Microphone 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Shure MV7+ XLR &amp; USB-C dynamic microphone 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| Opinion 
|-
| &lt;!--Description--&gt;SONY PCM-D50 handy 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| one mini usb 5V, }}
|-
| &lt;!--Description--&gt;Sony PCM-M10 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| one mini usb out 5V, }}
|-
| &lt;!--Description--&gt;SONY 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| one mini usb out, }}
|-
| &lt;!--Description--&gt;SONY 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| one mini usb out, }}
|-
| &lt;!--Description--&gt;TASCAM DR-1 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2008, one mini usb out, lithium battery}}
|-
| &lt;!--Description--&gt;Tascam DR-07 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2009, one mini usb out, aa battery}}
|-
| &lt;!--Description--&gt;Tascam DR05 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2011, one mini usb port for file transfer and charging the AA batteries }}
|-
| &lt;!--Description--&gt;Tascam DR-40
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2011  mini usb aa battery }}
|-
| &lt;!--Description--&gt;Tascam DR-07mkII
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2012 , one mini usb out, }}
|-
| &lt;!--Description--&gt;Tascam DR-05X 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2019 , one micro usb out, }}
|-
| &lt;!--Description--&gt;Tascam DR-07X 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2019 , one micro usb out, }}
|-
| &lt;!--Description--&gt;Tascam DR-40X
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2019 , one micro usb 3 aa battery }}
|-
| &lt;!--Description--&gt;Tascam DR-05XP 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 , one usb-c , }}
|-
| &lt;!--Description--&gt;Tascam DR-07XP 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 , one usb-c , }}
|-
| &lt;!--Description--&gt;Tascam DR-40XP
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 , one usb-c, }}
|-
| &lt;!--Description--&gt;Tascam DR-100mkIII 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| , usb , }}
|-
| &lt;!--Description--&gt;Tascam 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| , usb , }}
|-
| &lt;!--Description--&gt;Zoom H4 
| &lt;!--Vendor ID--&gt;0x1686
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2006 no driver, mini usb 5V }}
|-
| &lt;!--Description--&gt;Zoom H2 
| &lt;!--Vendor ID--&gt;0x1686
| &lt;!--Product ID--&gt;0x0095
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2007 no driver, mini usb 5V audio i/f USB Card and USB Audio; press the Record button when USB Audio is displayed. Press Record again to choose the default }}
|-
| &lt;!--Description--&gt;Zoom H4n 
| &lt;!--Vendor ID--&gt;0x1686
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2009 no driver, mini usb 5V }}
|-
| &lt;!--Description--&gt;Zoom H1 
| &lt;!--Vendor ID--&gt;0x1686
| &lt;!--Product ID--&gt;0x0120
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2010 no driver, mini usb 5V and display will alternate between USB Card and USB Audio; press the Record button when USB Audio is displayed. Press Record again to choose the default }}
|-
| &lt;!--Description--&gt;Zoom H2n 
| &lt;!--Vendor ID--&gt;0x1686
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2011 no driver, mini usb 5V audio i/f press the Record. Press Record again to choose the default }}
|-
| &lt;!--Description--&gt;Zoom H4n PRO 
| &lt;!--Vendor ID--&gt;0x1686
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2011 no driver, mini usb 5V }}
|-
| &lt;!--Description--&gt;Zoom H6 
| &lt;!--Vendor ID--&gt;0x1686
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2013 untested, 2xlr, 5v mini usb, }}
|-
| &lt;!--Description--&gt;Zoom H5 
| &lt;!--Vendor ID--&gt;0x1686
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2014 no driver, 5v mini usb, 2 xlr, }}
|-
| &lt;!--Description--&gt;Zoom H1n-vp handy 
| &lt;!--Vendor ID--&gt;0x1686
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2018 no driver, mini usb 5V }}
|-
| &lt;!--Description--&gt;Zoom H6studio 
| &lt;!--Vendor ID--&gt;0x1686
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 untested}}
|-
| &lt;!--Description--&gt;Zoom 
| &lt;!--Vendor ID--&gt;0x1686
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|no driver}}
|-
| &lt;!--Description--&gt;Zoom Q3
| &lt;!--Vendor ID--&gt;0x1686
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2008 untested usb a cord, no hdmi, 480p}}
|-
| &lt;!--Description--&gt;Zoom Q3HD Handy Video Recorder 
| &lt;!--Vendor ID--&gt;0x1686
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2010 untested, built in usb-a cord, mini hdmi, 1 hour on 2 AA batteries, H.264 movies 480p }}
|-
| &lt;!--Description--&gt;Zoom Q2HD Handy 
| &lt;!--Vendor ID--&gt;0x1686
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2012 untested, up 720p but no stablisation, mini usb cord, 1 hour on 2 AA batteries}}
|-
| &lt;!--Description--&gt;Zoom Q4
| &lt;!--Vendor ID--&gt;0x1686
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2014 untested, li-ion battery}}
|-
| &lt;!--Description--&gt;Zoom Q4N 
| &lt;!--Vendor ID--&gt;0x1686
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2015 untested, li-ion battery}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| Opinion 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Audio Technica ATR4697-USB Boundary Microphone
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;CAD Audio CAD USB Condenser Boundary Microphone 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;MXL AC-44 Boundary Conferencing Mic 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Samson Audio SAUB1 Boundary Microphone (USB)
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|}


USB Speakers 
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Focal XS 2.1 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
|}


USB Headset Wired/Wireless 
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| Logitech Vantage Wired (came free with PS2 Socom3)
| 
| 
| 
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Logitech G330 
| 
| 
| 
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Logitech Premium USB Stereo Headset 350
| 
| 
| 
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Plantronics DSP-300 
| 
| 
| 
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Plantronics GameCom 777
| 
| 
| 
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| Opinion 
|-
| &lt;!--Description--&gt;Wireless
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Logitech G-930 Wireless
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| [http://www.makeuseof.com/tag/set-usb-wireless-earphones/ Plantronics Audio 995 Wireless RF] 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| Sennheiser  Wireless
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
|}


[https://www.youtube.com/watch?v=Be1e0QPIPK0 Mixers]

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;ALESIS MULTIMIX 4 CHANNEL USB MIXER
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Alesis - MultiMix 8 USB FX (USB 1.0)
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;2010 usb compliant?, up to 16-bit/48kHz, 18v 500mA - 
|-
| &lt;!--Description--&gt;Alesis - MultiMix 8 USB 2.0 FX (USB 2.0)
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;2012 usb compliant?, up to 16-bit/48kHz, 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Allen&amp;Heath MixWiz16
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; maybe not usb compliant, 
|-
| &lt;!--Description--&gt;Allen and Heath ZED Power 1000 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no usb 8 xlr, usb-b out, }}
|-
| &lt;!--Description--&gt;Allen &amp; Heath ZEDi-10
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; maybe not usb compliant, 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Behringer XENYX 302USB 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| 5-Input Mixer/Audio Interface - 1 xlr - }}
|-
| &lt;!--Description--&gt;Behringer Xenyx Q502USB Mixer 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|no driver}} Behringer 2*18.5V 250ma psu - 1 xlr - phanton power - 
|-
| &lt;!--Description--&gt;Behringer Xenyx Q802USB 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}} Behringer 2*18.5V 250ma psu - 2 xlr - phanton power - 
|-
| &lt;!--Description--&gt;BEHRINGER XENYX 1204USB 8-Channel 2-Bus Mixer USB/Audio Interface Studio/Live
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}} iec kettle psu lead - can develop constant background hiss over time 
|-
| &lt;!--Description--&gt;Behringer XENYX X1222USB
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver - 12-Channel Analog Mixer with USB Interface and Effects}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}}
|-
| &lt;!--Description--&gt;Depusheng HT-7 HT7USB 7 Channel Audio Mixer
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|2023 cheap no driver, USB MP3 player to work, format your USB stick Fat32 as a Logical drive - not primary}}
|-
| &lt;!--Description--&gt;Depusheng XT7 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|2025 cheap no driver}}
|-
| &lt;!--Description--&gt;Depusheng DT8 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|2025 cheap no driver}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}}
|-
| &lt;!--Description--&gt;Spirit soundcraft Folio FX8 with Lexicon Effects Processor
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}} unusual power connector - [https://github.com/lack/soundcraft-utils usb routing] -  
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}}
|-
| &lt;!--Description--&gt;Weymic Professional F7 7-Channel 2-Bus Mixer 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|2022 no driver, cheap mixer with 3pin ac input (introduces noise) and 1 usb-a port}}
|-
| &lt;!--Description--&gt;Weymic Professional F7-Pro 7-Channel 2-Bus Mixer 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|2022 no driver}}
|-
| &lt;!--Description--&gt;Weymic A80 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|2024 no driver}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}}
|-
| &lt;!--Description--&gt;Yamaha 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}}
|-
|}


Mixer no hardware usb 

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no usb}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no usb}}
|-
| &lt;!--Description--&gt;ALTO Lynx MIX82FX Audio Mixer
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no usb}}
|-
| &lt;!--Description--&gt;Alto L16 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no usb}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no usb}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no usb}}
|-
| &lt;!--Description--&gt;Behringer MXUL5 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no usb}}
|-
| &lt;!--Description--&gt;Behringer MX602A 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no usb}}
|-
| &lt;!--Description--&gt;Behringer Eurorack UB502
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no usb 17.5V 3pin psu needed}}
|-
| &lt;!--Description--&gt;Behringer Eurorack UB802 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no usb 2 xlr,}}
|-
| &lt;!--Description--&gt;Behringer Eurorack UB1002 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no usb 2 xlr,}}
|-
| &lt;!--Description--&gt;Behringer Eurorack UB1202 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no usb 4 xlr, }}
|-
| &lt;!--Description--&gt;Behringer Eurorack UB1602 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no usb}}
|-
| &lt;!--Description--&gt;Behringer RX1602 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no usb}}
|-
| &lt;!--Description--&gt;Behringer 802 XENYX 8-Input 2-Bus Mixer Small Format Mixer
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}} Behringer 18.5V ???ma psu - 2 xlr - phanton power - 
|-
| &lt;!--Description--&gt;Behringer Xenyx 502 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no usb}}
|-
| &lt;!--Description--&gt;Behringer Xenyx 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no usb}}
|-
| &lt;!--Description--&gt;Behringer 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no usb}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no hardware usb connection}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no usb}}
|-
| &lt;!--Description--&gt;IMG stage Line MMX-122 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no usb, 4 xlr, iec cable}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no hardware usb connection}}
|-
| &lt;!--Description--&gt;Mackie 802VLZ4 Mackie 802-VLZ4
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no usb , psu}}
|-
| &lt;!--Description--&gt;Mackie 1202-VLZ Pro
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no usb, mains iec}}
|-
| &lt;!--Description--&gt;Mackie Mix5 Mixer 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no usb}} 18v 300mA psu - 5 Channel - 
|-
| &lt;!--Description--&gt;Mackie Mix8 Mixer 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no usb}} 9v x2 600mA psu - 
|-
| &lt;!--Description--&gt;Mackie MIX12FX
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no usb, 4 xlr, 9v 500mA x2 psu, }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no hardware usb connection}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no usb}}
|-
| &lt;!--Description--&gt;[https://www.soundcraft.com/en/product_documents/en/owners_manual Soundcraft] Spirit Folio F1 Fader 100 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}} 16 Channel Mixer - 
|-
| &lt;!--Description--&gt;Soundcraft EPM6 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no hardware usb connection}}
|-
| &lt;!--Description--&gt;Soundcraft EPM8 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no hardware usb connection}}
|-
| &lt;!--Description--&gt;Harman Soundcraft EPM 12 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}} iec kettle power lead - 
|-
| &lt;!--Description--&gt;Soundcraft EPM 16
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}}
|-
| &lt;!--Description--&gt;Soundcraft Notepad 8FX
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no hardware usb connection}}
|-
| &lt;!--Description--&gt;Soundcraft Notepad UI12
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; connect via wifi 
|-
| &lt;!--Description--&gt;Soundcraft Notepad UI16
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt; connect via wifi 
|-
| &lt;!--Description--&gt;Soundcraft Notepad 124FX 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no hardware usb connection, 14.8V x2 3 pin psu}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no hardware usb connection}}
|-
| &lt;!--Description--&gt;t.mix xmix 1402fx mp usb
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no hardware usb connection, mains iec, }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no hardware usb connection}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no hardware usb connection}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no hardware usb connection}}
|-
|}


==Webcameras==

A USB camera has two dedicated chips: a controller or bridge and an image sensor.

There was no Commodore support for video interfaces. The only commercial, now discontinued application that defined some sort of standard was VHI Studio by iospirit.

===OLD standards===

See [http://www.e3b.de/usb/main_supported_e.html support pages] and [http://www.e3b.de/usb/main_faq_e.html here] and some [http://webcam-osx.sourceforge.net/cameras/index.php?orderBy=status further compatibility]


Pencam STV680
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| AIPTEK stv680 
| 0x0553 
| 0x0202 
| 
| {{N/A|untested}}
|-
| Konica e-mini 
| 0x04c8 
| 0x0722 
|
| {{N/A|untested }}
|-
| DigitalDream l'espion XS 
| 0x1183 
| 0x0001 
|
| {{N/A|untested}}
|-
| [http://reviews.cnet.com/webcams/creative-webcam-go/1707-6502_7-1446174.html Creative WebCam Go mini] 
| 0x041e 
| 0x4007 
|
| {{N/A|untested}}
|-
|}


SonixcamTool (Sonix webcams and derivates)

'''Note [http://amigadev.free.fr/sonix/ some] Sonix Webcams with a Sonix SN9C1xx controller ''and'' a pas106b or tas5110c1b sensor support bulk mode which works even with pciusb.device!'''
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| Macally IceCam II
| 0x0c45
| 0x05d8
| 
| {{N/A|untested}}
|-
| Sweex MiniCam 100K 
| 0x0c45 
| 0x6005 
| 
| {{N/A|untested - sensor tas5110c1b}}
|-
| Macally IceCam Portable 
| 0x0c45
| 0x6007
| 
| {{N/A|untested - sensor tas5110d}}
|-
| Sweex 100K 
| 0x0c45 
| 0x6009 
| 0x0101
| {{yes|bulk works - sensor pas106b}}
|-
| [http://www.epinions.com/pr-Chicony_TwinkleCam_Webcam/display_~full_specs Chicony Twinkle DC-2110A] 
| 0x0c45
| 0x600d
| 
| {{no|no}}
|-
| Unknown
| 0x0c45
| 0x601e
| 
| {{no|no}}
|-
| USB PC Camera (SN9C102)
| 0x0c45 
| 0x6028
| 
| {{no|no - sn9c10x + pas202b}}
|-
| Trust SpaceC@m 120 and 150
| 0x0c45 
| 0x6029
| 
| {{N/A|untested - sensor pas106a}}
|-
| HiRes Webcam Live
| 0x0c45 
| 0x602c
| 
| {{no|no - sensor ov7630}}
|-
| [http://www.sweex.com/en/assortiment/sound-vision/webcams/JA000020 Sweex USB Webcam 300K]
| 0x0c45
| 0x608f
| 
| {{no|no - sensor ov7630}}
|-
| Speedlink Sphere Webcam SL-6820, 350K
| 0x0c45
| 0x613c
| 0x0101
| {{N/A|untested - sensor HV7131R}}
|-
| WB-3250P
| 0x0c45
| 0x613e
| 
| {{no|no - sensor ov7630}}
|-
| Unknown
| 0x0c45 
| 0x6207
| 
| {{no|no}}
|}

&lt;pre&gt;
micromaxx USB Camera 	STM 	1363 	514 	works 	---
USB Tower 	Lego 	1684 	1 	works 	need NCQ
Trust Spycam 100plus 	STM 	1363 	514 	works
&lt;/pre&gt;


ov51x.class - no driver
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| D-Link VGA Webcam (640x480) 
| 0x05a9
| 0x8519
| 
| {{no|no driver}}
|-
| Sony PS2 EyeToy Logitech/Logicool Black (ov519) SCEH-0004 
| 0x054c
| 0x0154
| 
| {{no|no driver}}
|-
| Sony PS2 EyeToy Namtai Silver (ov519) SLEH-00031 SLEH-00030
| 0x054c
| 0x0155
| 
| {{no|no driver}}
|-
|}


===UVC.class - [https://www.usb.org/document-library/video-class-v15-document-set USB Device Class Definition for Video Devices or USB Video Class]===

 AROS does not supported as still needs an uvc.class which might create a virtual UVC.VHI or an expanded streaming device driver for use by AROS apps 

*2003 UVC 1.0 baseline streaming of uncompressed YUV422, MJPEG, and compressed MPEG-2 TS, DV 
*2005 [http://www.cajunbot.com/wiki/images/8/85/USB_Video_Class_1.1.pdf UVC 1.1] baseline HD 720p streams formats, usb2 support, 
*2012 [https://www.usb.org/document-library/video-class-v15-document-set UVC 1.5] added usb3 devices and compressed h.264 and VP8 formats 
*2019 the market is filled with UVC Compliant USB HDMI Capture


*Aros needs to read the camera’s class-specific Video Control (VC) unit and terminal descriptors.
*Identifies the devices as UVC-compatible and links it to the native UVC class driver, so no separate driver installation is required.
*Aros and camera determine the appropriate streaming settings, including format, resolution, and frame rate.
*Once set, video data moves from the image sensor to the onboard ISP, then through the USB controller and into the host system for viewing, analysis, or recording 
*More advanced functions, such as HDR, ROI, and hardware trigger support, can be managed 


{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;Acasis 4K30 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|}}
|-
| &lt;!--Description--&gt;Acasis 4K60 HD VS009
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|4k 60hz ok for chat streams}}
|-
| &lt;!--Description--&gt;Acasis 4K60 HDMI HDR Game Live Video Capture
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| for chat streams }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;AJA U-tap HDMI 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|}}
|-
| &lt;!--Description--&gt;ASUS TUF CU4K30 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;ATEN CAMLIVE HDMI to USB-C UVC Video Capture adapter UC3020 HDMI (F) TO USB-C M 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2019 possibly UVC and UAC standard support allows up to 1080P @ 60}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Avermedia Live Streamer Cap 4K - BU113 
| &lt;!--Vendor ID--&gt;0x07ca
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2021 uvc usb3}}  
|-
| &lt;!--Description--&gt;AVerMedia GC515 video capturing device 
| &lt;!--Vendor ID--&gt;0x07ca
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2021 USB 3.2 Gen 1 (3.1 Gen 1)}}
|-
| &lt;!--Description--&gt;AVerMedia Live Gamer Ultra GC553
| &lt;!--Vendor ID--&gt;0x07ca
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2021 usb3 powered by Type C USB cable and 4K HDMI cable}}
|-
| &lt;!--Description--&gt;AVerMedia Live Gamer Ultra S GC553PROW 302AGC553DL2 
| &lt;!--Vendor ID--&gt;0x07ca
| &lt;!--Product ID--&gt;0x1553
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2021 powered by good quality type C USB3 cable and 4K HDMI 2.0 cable}}
|-
| &lt;!--Description--&gt;AVermedia Live Gamer Mini GC311 302AGC311DG9 
| &lt;!--Vendor ID--&gt;0x07ca
| &lt;!--Product ID--&gt;0x1311
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2021 uvc compliant up to 1080p 60fps capture and supports internal hardware H.264 encoding - if flashing blue light try another '''quality''' micro usb cable - }}
|-
| &lt;!--Description--&gt;AVerMedia Ez Recorder 330 (ER330) 
| &lt;!--Vendor ID--&gt;0x07ca
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2021 designed to work independently and is generally not compatible as a plug-and-play UVC capture card }}
|-
| &lt;!--Description--&gt;AVerMedia Live Gamer extreme3 GC551G2 (LGX3) 
| &lt;!--Vendor ID--&gt;0x07ca
| &lt;!--Product ID--&gt;0x3551
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2022 uvc compliant for intensive gaming streams, some vrr but no hdr with maximum recording resolution of 4K30/1080p60 from fully wired usb3 compatible cable - passing through 4K60/1080p120 Game Capture video capturing device HDMI}}
|-
| &lt;!--Description--&gt;AVerMedia Live Gamer Ultra Pro GC553Pro 
| &lt;!--Vendor ID--&gt;0x07ca
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2024 usb3 }}
|-
| &lt;!--Description--&gt;AVerMedia Live Gamer Ultra 2.1 GC553G2 61GC553G20BV video capturing device 
| &lt;!--Vendor ID--&gt;0x07ca
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 USB 3.2 Gen 1 (3.1 Gen 1)}}
|-
| &lt;!--Description--&gt;AVerMedia GC575
| &lt;!--Vendor ID--&gt;0x07ca
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 usb3 powered by Type C USB cable and 4K HDMI cable}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;AVMatrix 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;ClonerAlliance Flint 4KP Plus 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;DIGITNOW U600 video capture card 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2022 uvc uac  }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Epiphan AV.io HD
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Epiphan AV.io 4K 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Elgato Cam Link 4K 
| &lt;!--Vendor ID--&gt;0x0FD9
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2018 uvc }}
|-
| &lt;!--Description--&gt;[https://github.com/elgatosf/capture-device-support Elgato HD60 S+]
| &lt;!--Vendor ID--&gt;0x0FD9
| &lt;!--Product ID--&gt;0x006C, 0x006E
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2019 4K 30FPS capture, 1080p 60FPS uvc}} 
|-
| &lt;!--Description--&gt;Elgato HD60 X 
| &lt;!--Vendor ID--&gt;0x0FD9
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2022 uvc }}
|-
| &lt;!--Description--&gt;Elgato Cam Link 4K HDMI video capture card 
| &lt;!--Vendor ID--&gt;0x0FD9
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 uvc compliant but can have usb disconnects}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;EVGA XR1 USB 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2021 USB 3.0 device with 1080/60 capture and 4K/60 passthrough}}
|-
| &lt;!--Description--&gt;EVGA XR1 lite USB 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2022 USB 3.0 device }}
|-
| &lt;!--Description--&gt;EVGA XR1 Pro USB 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2021 USB 3.0 device with 1080/60 capture and 4K/60 passthrough}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;EZcap Game Link Raw - ezcap321 usb3.1 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2022 2160p30, 1080p120 and 1440p60 HDMI input and pass-through. - 1080p120, 2160p30 and 1440p60 recording. - Latency less than 50ms uvc}} 
|-
| &lt;!--Description--&gt;EZCap GameDock Ultra 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2022 record at 4K30, 1440p60, and 1080p120}}
|-
| &lt;!--Description--&gt;EZcap 360 Game Capture Extreme 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2023 USB 3.0, 4K 60FPS passthru and 1080p 240FPS}}
|-
| &lt;!--Description--&gt;EZCAP 364 GameDock Extreme 2.1
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2024 }} 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Genki ShadowCast 1 &amp; 2, the Pro version 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;HAUPPAUGE HD PVR Pro 60 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2021  4K in/Out 1080P 60fps Capture and Streaming PC Connected and Stand Alone }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;INOGENI 4K2USB3 2830 3826 HDMI 4K to USB 3.0 UHD 1080p Video Capture Card 
| &lt;!--Vendor ID--&gt;0x2997
| &lt;!--Product ID--&gt;0x0004
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2019 uvc compliant made in Canada - usb3-b socket and 1 hdmi 1080p from 23.98 up to 60p, 4K@30 fps maybe - }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Kondor Blue 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Nanjing Magewell Electronics Co ltd USB 3.0 XI100DUSB-HDMI Pro Capture 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2013 }}
|-
| &lt;!--Description--&gt;Magewell USB3.0 Silver HDMI Full HD Video Capture Device 1080p 32011 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2013 usb audio extract HDMI embedded audio output via headphones}}
|-
| &lt;!--Description--&gt;Magewell USB capture HDMI PLUS 2K 32040 320400000
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2014 captures video up to 1920×1200, 1920×1080 or 2048×1080 at 60 fps over an HDMI capture from devices such as game consoles in up to DCI 4Kp60 4:2:0 input resolution, and it automatically upscales/downscales the signal to 2K for recording or streaming}} 
|-
| &lt;!--Description--&gt;Magewell USB capture HDMI Gen2 32060 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2015 1080p gets hot, 165M HDMI receiver, max input 2048x1080 60fps 4:4:4, RGB/YUV 4:4:4 8/10/12-bit, YUY 4:2:2 12-bit, up to 8-channel 24-bit HDMI-embedded audio at 192kHz, HDMI 1.4a, output from 480p to 1080p, YUY2/UYVY/RGB24/RGB32 support video cropping, up/down scaling, de-interlacing, aspect ratio conversion, color format conversion, frame rate conversion, flip and mirror, up to 2-channel IEC60958 audio streams, 5V 0.5A 2.5W, }}
|-
| &lt;!--Description--&gt;Magewell USB Capture 4K Plus 32090 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2022 limited by the bandwidth of USB 3.0, the maximum frame rate can only reach 30 fps when capturing}}
|-
| &lt;!--Description--&gt;Magewell USB Capture 4K PRO
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2024 }}
|-
| &lt;!--Description--&gt;Magewell Pro Convert IP to USB 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|Captures one network eth NDI® High Bandwidth, NDI® HX2, NDI® HX3 sources or H.264/H.265 video source into software at resolutions up to 1080p60}}
|-
| &lt;!--Description--&gt;Magewell USB Fusion 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|versatile USB video capture device that allows users to switch between two HDMI inputs and one USB webcam input for live presentations}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;ROLAND UVC-01 USB Video Capture
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2020  }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Sunplus Innovation Technology Inc. MiraBox HSV321 ARX321 Video Capture device 
| &lt;!--Vendor ID--&gt;ox1bcf
| &lt;!--Product ID--&gt;0x2c99
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2022 uvc uac  }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;UGREEN CM716 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| uvc uac but disable HDCP on your source device (PS4/PS5, Xbox) }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;VisionTek UVC HD60 Capture Card
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
|}


{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;Acer Aspire Crystal Eye AOA110 AOA150 0.3M 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|2008 webcam }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|}}
|-
| &lt;!--Description--&gt;AVerMedia Live Streamer CAM 313 (PW313) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|2019 uvc 1080p/30 webcam}}
|-
| &lt;!--Description--&gt;AVerMedia Live Streamer DUO 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|2021 uvc 1080p/60 webcam}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|}}
|-
| &lt;!--Description--&gt;[http://reviews.cnet.co.uk/webcams/creative-live-cam-optia-af-review-49294183/ Creative Live Cam Optia AF] 2.0M
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| {{no|2008 }}
|-
| &lt;!--Description--&gt;DSLR macro extensions + a cheap 50mm E-Series lens + some PVC tubing and a negative holder 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{yes| if uvc camera chosen}}
|-
| &lt;!--Description--&gt;DSLR scanning using a macro lens, for the adapter, for a 3d printed negative holder) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{yes| if uvc camera used }}
|-
| &lt;!--Description--&gt;Logitech C270 
| &lt;!--Vendor ID--&gt;0x046d
| &lt;!--Product ID--&gt;0x0825
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|720p }}
|-
| &lt;!--Description--&gt;Logitech C910 C920 HD Pro 5Megapixels 720p 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|Output mjpg 1080p}} 
|-
| &lt;!--Description--&gt;Logitech C920s c922 HD Pro 5Megapixels 1080p 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|Output mjpg 1080p}} 
|-
| &lt;!--Description--&gt;Logitech 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|}}
|-
| &lt;!--Description--&gt;Logitech Brio 100 300 500 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|}} 1080p 
|-
| &lt;!--Description--&gt;Logitech MX Brio 4k 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|4k}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|}}
|-
| &lt;!--Description--&gt;Microsoft's LifeCam HD-3000 HD-5000 
| &lt;!--Vendor ID--&gt;0x045e
| &lt;!--Product ID--&gt; 0x0779
| &lt;!--Revision--&gt;1.06
| &lt;!--Opinion--&gt;{{no|}}
|-
| &lt;!--Description--&gt;Microsoft LifeCam Cinema 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|}}
|-
| &lt;!--Description--&gt;Microsoft LifeCam Studio 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|}} sony imx179 1080p 
|-
| &lt;!--Description--&gt;Pi 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|}} 1/2.8” Sony IMX291 image sensor, it's a 2MP, UVC-compliant, ultra-wide-angle, low light, high-speed USB 2.0 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|}} OV5648 
|-
| &lt;!--Description--&gt;razer kiyo 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|}} 4 megapixel sensor 1080p 30fps 720p 60fps - 12 led ring light adjustable 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|}}
|-
| &lt;!--Description--&gt;TeckNet C068 1.3mpixel HTD USB2.0 Camera Vimicro Z-Star Corp 
| &lt;!--Vendor ID--&gt;0x0AC8
| &lt;!--Product ID--&gt; 0x3420 
| &lt;!--Revision--&gt;0x01FA
| &lt;!--Opinion--&gt;{{no|}}
|-
| &lt;!--Description--&gt;[https://github.com/wltechblog/thingino-installers/tree/main/wyze-cam-4 Wyze Cam V4] [https://www.youtube.com/watch?v=H0QLiC9QoQU firmware]
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no| verified with os04d10 sensor (i2c 0x3c) but not GC4653 (i2c 0x29)}}
|-
| &lt;!--Description--&gt;YEALINK(XIAMEN) NETWORK UVC50 is compatible with the UVC 1.1 protocol CP960-UVC50 and CP960-UVC80 kits PTZ, CP960-UVC30 Kit is UVC 1.5 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|}}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID 
| Product ID
| Revision 
| Opinion 
|-
| &lt;!--Description--&gt;Amcrest ProHD 1080P WiFi Wireless IP Security Camera - 1080P (1920TVL), [https://www.ispyconnect.com/man.aspx%3Fn%3DAmcrest IP2M-841] nvr 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|}} h264/rtsp, motion detection, features Sony image sensor and Ambarella processor - rtsp://[username]:[password]@[IPaddress]:[port]/cam/realmonitor?channel=[channel]&amp;subtype=[stream] - [username] - username to login to the DVR or NVR, [password] - password, [IPaddress] - IP address of the device. If you are not on the same local network, this should be the external IP address of the device's network, [port] - port number, [channel] - channel number of the stream, [stream] - view the Main or Sub stream. (main stream is 0, sub stream is 1) , eg. rtsp://admin:admin@192.108.1.108:80/cam/realmonitor?channel=1&amp;subtype=1 - utilizing RTSP ( rtsp://user:pass@ipcam1 )  
|-
| &lt;!--Description--&gt;Axis all modern ones 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|}} RTSP/RTP + H264/mjpeg or MJPEG over HTTP
|-
| &lt;!--Description--&gt;PTZ 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|}}
|-
| &lt;!--Description--&gt;DLink DCS-5222 5222L network camera 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|}} camera streams H.264 over RTP controlled by RTSP 
|-
| &lt;!--Description--&gt;Dlink DCS900 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|}}
|-
| &lt;!--Description--&gt;Sony 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|}}
|-
| &lt;!--Description--&gt;Wansview 1080p [http://marc.merlins.org/perso/linuxha/post_2013-11-10_Reviewing-IP-Webcams-for-Linux-and-Zoneminder_Dlink-DCS900_-Ubnt-Aircam_-Foscam-FI8904W-FI8910W_-FFI9820W_-FI9821W_-Wansview-NCB541W_-and-Zavio-F3210.html#NCM625GA NCM625GA] IP Camera WiFi Wireless IP Security Camera , Full HD Plug n Play Home Surveillance / Baby Monitor 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|}} RTSP/RTP + H264/mjpeg - play its HD stream without problem with vlc rtsp://ip/live/ch0 and getting  jpegs http://ipaddr/mjpeg/snap.cgi?chn=0 - methods involve transcoding h.264 video from the camera into jpeg's, which is cpu intensive - able to pull images manually, using http://username:password@ip/mjpeg/snap.cgi - 
|-
| &lt;!--Description--&gt;Wansview NCB541W
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|}}
|-
|}


{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| not uvc}}
|-
| &lt;!--Description--&gt;Avermedia Game Capture HD C281 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|2011 standalone h.264 recording of up to component cable not hdmi but not uvc}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Avermedia GL310 Live Gamer Portable (LGP Lite)
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|2014 not working usb2 and USB Lite no uvc}} 
|-
| &lt;!--Description--&gt;Avermedia AVerMedia Live Gamer Portable ([https://github.com/Trouffman/octv_gears_lgp Model C875])  
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|2014 usb2 no uvc}}   
|-
| &lt;!--Description--&gt;AVerMedia LGX Live Gamer extreme GC550
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|2015 but [https://github.com/ChrisAJS/lgx2userspace driver]}}
|-
| &lt;!--Description--&gt;AVerMedia LGX2 Live Gamer extreme2 gc550 plus gc551 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|2017 but [https://github.com/ChrisAJS/lgx2userspace driver]}}
|-
| &lt;!--Description--&gt;Avermedia ExtremeCap UVC - BU110 
| &lt;!--Vendor ID--&gt;0x07ca
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|2017 maybe not uvc and uac}}
|-
| &lt;!--Description--&gt;AVerMedia Live Gamer Portable 2 Plus GC513 Micro-USB Capture Box LGP2 Plus
| &lt;!--Vendor ID--&gt;0x07ca
| &lt;!--Product ID--&gt;0x1513
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|2017 powered by a standard Micro-USB cable, video capture output up to 1080p60 capture to hdmi in, standalone sd card recording on exFAT or FAT32 of .MOV, 2160p pass-through hdmi out to tv - no vrr - [https://www.avermedia.com/uk/support/download#ans_part firmware latest 2.1.7.13, 2.1.7.14], SN74AVC8T245 8bit, DRV604 stereo, iTE IT6663FN hdmi 2.0 splitter, TLV320DAC3101 DAC, CS42L73 audio codec, CDCE913 PLL clock, W29N01HVSINA nand bios, I-Catch V35MA SOC CPU 32bit MIPS24K, ADV7480 hdmi mhl, }}
|-
| &lt;!--Description--&gt;AVerMedia Live Gamer 4K LG4K GC573 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|2018 not uvc but [https://github.com/derrod/lg4k-linux drivers here], }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| not uvc }}
|-
| &lt;!--Description--&gt;Blackmagic intensity Extreme Capture Card
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|2011 not uvc }}
|-
| &lt;!--Description--&gt;BlackMagic Intensity Pro 4k 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|2015 }}
|-
| &lt;!--Description--&gt;Elgato Video Capture (1VC108601000)
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| not uvc }}
|-
| &lt;!--Description--&gt;Elgato Game Capture 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| not uvc, mini usb}}
|-
| &lt;!--Description--&gt;Elgato Game Capture HD60 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| not uvc, }}
|-
| &lt;!--Description--&gt;Elgato Game Capture HD GCHD 2GC309901000 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| not uvc https://github.com/tolga9009/elgato-gchd needs firmware mb86h57_h58_idle.bin and mb86h57_h58_enc_h.bin - mini usb}}
|-
| &lt;!--Description--&gt;Elgato HD60S Elgato Game Capture 4K60 S+ Video Capture 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|non uvc, }}
|-
| &lt;!--Description--&gt;August EZCap.tv model 116 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| }} poor audio recording 
|-
| &lt;!--Description--&gt;E-SDS Diamond Maplin 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| not uvc }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| not uvc }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| not uvc }}
|-
| &lt;!--Description--&gt;Hauppauge 1212 HD PVR 
| &lt;!--Vendor ID--&gt;0x2040
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| }} analog and component only - PlayStation (.m2ts), AVCHD (ts), or XBox(.mp4) recording formats - switched the component output from the default YPbPr to RGB. 
|-
| &lt;!--Description--&gt;Hauppauge 1431 1445 HD PVR Gaming Edition HDMI Capture 
| &lt;!--Vendor ID--&gt;0x2040
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|2014 not working, can get warm}}  
|-
| &lt;!--Description--&gt;Hauppauge HD Rocket 
| &lt;!--Vendor ID--&gt;0x2040
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| not uvc}}
|-
| &lt;!--Description--&gt;Hauppauge HD-PVR2 (model 145210 Rev E4) 
| &lt;!--Vendor ID--&gt;0x2040
| &lt;!--Product ID--&gt;0xE502
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| not uvc }}
|-
| &lt;!--Description--&gt;Hauppauge 1480 1482 HD PVR 2 GE Gaming Edition HDMI Capture green LED - 1498 1503 1504 Plus version with Mac support 
| &lt;!--Vendor ID--&gt;0x2040 
| &lt;!--Product ID--&gt;0xe514 0xe524
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| can get warm - [https://ez.analog.com/video/w/documents/581/adv7482-design-support-files ADV7482] [https://patchwork.kernel.org/patch/9201075/ video chip] with Magnum DXT H.264 encoder blob, IDR keyframe generation poor - best for model 157210 and not 157221 and Game Edition Plus (model 157320) 2040:E505 E505-00-00AF1234 [http://www.hauppauge.com/site/support/linux.html#tabs-3 ]}} 
* HDMI: 1920x1080p50/60, 1920x1080i50/60, 1280x720p50/60, 720x480i, 720x576i, 640x480p60.
* Component: 1920x1080p50/60, 1920x1080i50/60*, 1280x720p50/60, 720x480p60, 720x480i, 720x576i.
* Composite: 720x480i and 720x576i 
* Audio Inputs : HDMI PCM and RCA support with Adjustable Bitrate Quality 2 Channel AAC/AC3 audio codec 
|-
| &lt;!--Description--&gt;Hauppauge 1512 HD PVR 2 PC blue LED with optical in input on the back 
| &lt;!--Vendor ID--&gt;0x2040
| &lt;!--Product ID--&gt;0xe525
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| }} can get quite warm - IR Blaster added - 
|-
| &lt;!--Description--&gt;Hauppauge Colossus2 E585-00-00AF4321 
| &lt;!--Vendor ID--&gt;0x2040
| &lt;!--Product ID--&gt;0xe585
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| not uvc}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| not uvc }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| not uvc }}
|-
| &lt;!--Description--&gt;Ion SLIDES2PC 35mm Portable Slide &amp; Film Scanner 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| not uvc }}
|-
| &lt;!--Description--&gt;Ion Pics 2 PC 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| not uvc }}
|-
| &lt;!--Description--&gt;ION PowerScan USB film and slide scanner
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|2011 not uvc }}
|-
| &lt;!--Description--&gt;Koolertron Sunny 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| not uvc }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| not uvc }}
|-
| &lt;!--Description--&gt;FilmScan35 35mm Film Negative Scanner 1304 marks spencer 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| not uvc }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| not uvc }}
|-
| &lt;!--Description--&gt;U3 HD Capture 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| not uvc }}
|-
| &lt;!--Description--&gt;[https://github.com/openrazer/openrazer Razer Ripsaw HD] Game Capture (RZ20-01780100)
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|2017 not uvc put in usb2 slot and use video BGR3 (Emulated) and OpenRazer drivers }}
|-
| &lt;!--Description--&gt;Razer Ripsaw HD USB HDMI Capture Card 
| &lt;!--Vendor ID--&gt;0x1532
| &lt;!--Product ID--&gt;0x0d01
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|2018 not uvc compliant}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| not uvc }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| not uvc }}
|-
| &lt;!--Description--&gt;Silvercrest 35mm Photo Slide Scanner 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| not uvc but not great quality}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| not uvc }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| not uvc }}
|-
| &lt;!--Description--&gt;Z-Star Microelectronics Corp. Traveler TV 6500 SF Dia-scanner
| &lt;!--Vendor ID--&gt;0x0ac8
| &lt;!--Product ID--&gt;0x3370
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|2010 not uvc and poor scans}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| not uvc }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| not uvc }}
|-
|}


=== WebAR + WebVR = WebXR Headset ===

 AROS needs an usb based uvc.class to vhi like type driver for virtual display 

The primary engineering challenge of VR is motion sickness caused by a mismatch of visual and inner ear information, which is extremely well established as causing people to throw up in a wide range of contexts outside of VR. The experiences that make some people sick are low framerate. Foveated rendering doesn't solve vergence accommodation. Your eye will still be focused at infinity regardless of where you are looking, you'll just have the illusion that the foreground or background are out of focus. Eye tracking plus dynamic lenses (perhaps liquid lenses) or real light fields are necessary. 

First start with apps that have simple static features at first, then advance to dioramasa and teleportation options for 10, 20 minutes and then gradually upgrade over a timespan of four weeks to train your brain. Avoid smooth motion stuff like rollercoaster or mountain heights until much later. Even with this preparation, VR makes 40% of people seasick nausea. If so, you may be able to use VR glasses just to watch videos and some slow moving apps [https://www.emuvr.net/ emuVR] instead.

*2014-2019 1st Gen, low resolution, 
*2020-2025 2nd Gen, higher resolution, 
*2026-

Most hardware typically has a 1-3 year retail lifespan with 1-3 years of updates after. Really need &quot;right&quot; tethered PCVR rather than wireless. 
The advantage to being tethered to a PC is processing power. Any standalone headset is going to be running purely off of batteries.

VR and AR are known as XR

Technology will get immersed enough so not making people sick. Higher resolution, faster frame rates, and [https://github.com/opentrack/opentrack better tracking]. 
Eventually, hyper reality brings VR, AR and MR digital layers together as a less chaotic, optic tracking with no delay, agents understanding, experiences with objects 

3Dgs 4Dgs gassian splats bullet time slice photo snaps .ply for WebXR 

[https://lvra.gitlab.io/docs/hardware/ ], 

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Big Screen Beyond 1 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2023 pcvr 2560 x 2560, fixed IPD,  }}
|-
| &lt;!--Description--&gt;bigscreen Beyond 2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 pcvr oled 5120 x 2560 @75Hz 2688x2688 @90Hz over pancake lenses, 116 FOV, virtual screens, custom facial plate from iphone app, streamvr 2.0 basestations and controllers not included, no passthrough, 107g-196g, }}
|-
| &lt;!--Description--&gt;bigscreen Beyond 2e 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2026 pcvr oled 5120 x 2560 total up to 90Hz pancake lens 116 FOV adjustable IPD app needed for adjustment, eye tracking, custom face mask cushion, streamvr 2.0 basestations and controllers not included, seperate head strap and speaker modules extra costs, 110g-300g }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Dpvr P1 Pro 4k Ultra Vr Headset 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2024 wireless snapdragon, }}
|-
| &lt;!--Description--&gt;DPVR P2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025  }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Play for Dream MR 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 android modular 3840x3552 uoled per eye 90Hz or qled mura issues, Arm snapdragon XR2+ Gen 2, eye tracking and 11 cameras 7 sensors 22 ir leds 14ms latency and foveated rendering, 1.5hrs battery, }}
|-
| &lt;!--Description--&gt;Play for Dream GravityXR 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2026 ultralight head gear gx100 3w }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }} 
|-
| &lt;!--Description--&gt;[https://lvra.gitlab.io/docs/community/ Valve Index HMD] 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2019 tethered PC VR headset 1440 x 1600 120Hz, 108° and 104° FOV, fresnel lenses, SteamVR2 compatible tracking ir basestations, controllers aka Knuckles, dp 1.2 and usb3 cable proprietary cable end, no battery, }}
|-
| &lt;!--Description--&gt;Valve Steam Frame (Valve Deckard / Valve’s Index 2) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2026 - 2160 x 2160 up to 144Hz pancake lens, 108° and 96° FOV, wifi 6 fovelated streaming, Qualcomm Snapdragon 8 Gen 3 with [https://github.com/FEX-Emu/FEX fex] arm-to-x86 x64 translation layer, }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Sony PSVR2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|2023 PCVR with adapter, two, one for each eye, 2000 x 2040 resolution OLED panels from 90Hz 120Hz refresh rates,  fresnel lenses, 116° and 102° FOV, sony proprietary headset cable end, needs additional comfort options, }}
|-
| &lt;!--Description--&gt;VisionPro
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Opinion 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Goertek glasses 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;HTC Vive ?
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| 2016 2x 1080x1200 needs external power supply, }} 
|-
| &lt;!--Description--&gt;HTC Vive Original 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2016 108° and 96° FOV}}
|-
| &lt;!--Description--&gt;HTC Vive Pro 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2016 , uvc, at least 2 powered steamvr basestations so 3 to 5 wall warts in total, proprietary cable end, }}
|-
| &lt;!--Description--&gt;HTC Vive Pro 2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2017 dual 1440x1600 oled displays, 116° and 100° FOV - steamvr 2.0 basestation 2 for 5m2 area 4 for 10m2 - steamvr 2.0 joypads - low latency wireless later - type USB-c headphone adapter required, [https://github.com/CertainLach/VivePro2-Linux-Driver Rust on Linux] with [https://github.com/santeri3700/vive-pro-2-on-linux Shell], proprietary cable end, }} 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Lynx R1 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2023 android Qualcomm Snapdragon XR2 Gen 1, }}
|-
| &lt;!--Description--&gt;Lynx R2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|2026 company liquidated, 2 x 2312x2160 110 FOV pancake lenses, LynxOS android Qualcomm Snapdragon XR2 Gen, openxr 1.1, }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Oculus Rift prototype development kit [https://www.virtual-boy.com/forums/t/the-oculus-rift-dk1-thread/ DK1] with [https://www.youtube.com/watch?v=X_T4DJyy2Bo wired razer hydra controllers]
| &lt;!--Vendor ID--&gt;0x2833
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|2013 pcvr LCD 1280 × 800 resolution 640 × 800 per eye up to 110° FOV, and 3DoF rotational tracking via a 1000Hz 9-axis IMU (Accelerometer, gyroscope, and magnetometer), no positional optical tracking either inside-out or outside-in, 380g, nausea issues, , }}
|-
| &lt;!--Description--&gt;Oculus Rift prototype development kit [https://github.com/facebookarchive/RiftDK2/tree/master DK2], [https://www.ifixit.com/Teardown/Oculus+Rift+Development+Kit+2+Teardown/27613 ifixit teardown] 
| &lt;!--Vendor ID--&gt;0x2833
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|2014 pcvr, 5.7&quot; Super AMOLED display with a resolution of 960 x 1080 per eye 100° field of view, 1 usb Positional Tracker DK2 camera, lots of wires}}
|-
| &lt;!--Description--&gt;Facebook [https://github.com/thaytan/OpenHMD/tree/rift-kalman-filter Oculus Rift CV1] [https://noraisin.net/diary/?m=202201 some Linux support] [] [https://github.com/OpenHMD/OpenHMD/issues/330 AMD usb issues] [https://github.com/OpenHMD/OpenHMD/wiki/Xorg ] [https://github.com/Doc-Ok/OculusRiftCV1Camera Live Video] [https://www.youtube.com/@thaytan Youtube] [https://github.com/Fredrum/riftOnLinux Pi] [https://github.com/OhioIon/riftDriverPi ], but not quite there with the [https://www.youtube.com/watch?v=DSsCN6HFkWc consumer CV1], [https://forum.dcs.world/topic/142259-cv1-not-working-in-dcs/#comment-2878168 orange led could be HDMI Signal is not within HDMI Spec and might be Overclocked or usb3 not getting enough power frustrating],  
| &lt;!--Vendor ID--&gt;0x2833
| &lt;!--Product ID--&gt;0x3031, 0x2031, 0x0031 and 0x0211 for 3p-a basestations lighthouses, 0x045e 0x02e6 for xbox wireless adapter 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|2016 powered run from your PC maybe uvc via wired dual PenTile OLED 2160x1200 (1080x1200 per eye) @ exactly 90Hz but screen door effect (space between pixels), 87 FOV, IPD from 58mm to 72mm, good 3D audio and okay mic, constellation headset 6DOF (3-axis rotational tracking + 3-axis positional tracking) with up to 3 usb infrared basestation (1 in front and 2 behind pointing upwards) on usb3 and usb2 to your PC but the tracking can be fragile so set it up on a weekly basis, wired only HDMI 1.3, USB 3.0 bus powered with proprietary plug in headset, 470g 1lb front heavy, 2 robust 1st Gen touch controllers with external sensors i.e. outside-in - 1 aa alkaline over rechargable battery each , press occulus and B buttons for 2 secs to connect, headset traps air so gets very warm inside and random disconnects due to twisting action on the top of the headset and/or cables, t4 torx screws }} 
|-
| &lt;!--Description--&gt;Facebook Occulus Go 32Gb 
| &lt;!--Vendor ID--&gt;0x2833
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|2018 discontinued 2020 android based, 1280x1440 per eye 60Hz LCD, not gaming, no inside-out and limited self tracking, }} 
|-
| &lt;!--Description--&gt;Facebook Oculus Rift S [https://noraisin.net/diary/?m=202201 some Linux support] 
| &lt;!--Vendor ID--&gt;0x2833
| &lt;!--Product ID--&gt;0x0051 headset (cdc, audio, tracking data), 0x2052 usb hub, 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|2019 PCVR wired dual LCD 1080 by 1200, 88 horizontal FOV, display port (fibre optic strands) and annoying USB3 copper cables (power, audio and other data) but proprietary port in the headset, cameras on the headset (&quot;inside-out&quot;) tracking so no base stations, non removeable head band and cushions and ipd hard to set, requires specific fragile Rift S/Quest1 2nd Gen Touch controllers which has a ring of translucent plastic with leds inside - t5 torx to disassemble for sticks drifting}} 
|-
| &lt;!--Description--&gt;Facebook Occulus Quest 1 
*032Gb
*064Gb
| &lt;!--Vendor ID--&gt;0x2833
| &lt;!--Product ID--&gt;0x0183 (single adb boot), 0x0
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|2019 android standalone wireless, 1440 x 1600 72Hz oled, front heavy though, play area 2m x 2m or bigger, low clocked Qualcomm Snapdragon 835 (MSM8998) (4x Kryo 280 Gold cores ARM Cortex-A73) + (4x Kryo 280 Silver A53), 2 to 3 hrs play time, 575g, 2nd Gen touch controllers, }}
|-
| &lt;!--Description--&gt;Meta Oculus Quest 2 KW49CM aka Codename Del Mar [https://www.meta.com/en-gb/help/quest/967070027432609/ fragile 3rd Gen Touch controllers] [https://www.youtube.com/watch?v=Cgejky8ZeoM internal battery] and selling over 20 million, more than all other quest headsets combined 
*064Gb 
*128Gb (110Gb free) 
*256Gb 
Setup continuous wifi, create Meta Oculus account, [https://developers.meta.com/horizon/ verify dev account, click on My apps], [ create Organization -&gt; My Organization Groupings], [https://www.youtube.com/watch?v=QPInS5xxF-0 finally, meta quest mobile app to switch on adb], 
| &lt;!--Vendor ID--&gt;0x2833
| &lt;!--Product ID--&gt;0x5010 (), 0x0083 (massstorage), 0x0086 (), 0x0186 (adb and xrsp [https://github.com/shinyquagsire23/xrsp_tests tests]), 0x0090 (composite adb), 0x0081 (), 
| &lt;!--Revision--&gt;0419
| &lt;!--Opinion--&gt;{{unk|2021 android stand alone, lcd 1832x1920 per-eye 90Hz refresh rate, 97 FOV, fresnel lenses, 6DOF (degrees of freedom), 58-63-68 IPD settings, low clocked Arm snapdragon xr2 gen 1 apps with Meta Link cable USB-C usb3.2 pcvr maybe, b/w but no color passthrough, 6 t2 torx and 5 ph00 screws in headset (long bit), discontinued December 31, 2024, feature updates until December 2026, critical bug fixes and security updates until December 2027, 470g, Oculus + B button on right controller (move) and Menu + Y button on left controller (click) for about 3 seconds, 10W 5v 2a, RTL8153 chipset usb support, 
*V60 unable to 
*V77 pcvr issues 
*V79 unable to }}
|-
| &lt;!--Description--&gt;Facebook Occulus Quest Pro aka Codename Seacliffe 
| &lt;!--Vendor ID--&gt;0x2833
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|2022 android standalone wireless 1440 x 1600 72Hz oled, 106° and 96° FOV mini lcd local dimming, pancake lenses, limited eye tracking, play area 2m x 2m or bigger, higher clocked snapdragon xr2 gen 1 arm cpu Arm apps, 1 to 2 hrs play time, new pro controllers with 3 cameras each, battery at rear, wireless charging, color passthrough, 9V 3A or 5V 3A, 
*v77 capped wifi }}
|-
| &lt;!--Description--&gt;Meta Oculus Quest 3 aka Codename Eureka [ Air Light ALVR] or [ WiVRn] with fragile touch plus q3 controllers 
*128Gb
*512Gb
streaming from PC with [https://github.com/alvr-org/Monado-ALVR ALVR], runtime of [https://monado.freedesktop.org/ Monado steamvr alternative openxr openVR], with Envision GUI, 
| &lt;!--Vendor ID--&gt;0x2833
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2023 standalone, pancake lenses on lcd 2064 x 2208 res panel per eye 1200ppi - 104° and 96° FOV - up to 120Hz, Arm snapdragon xr2 gen 2 apps,  foveated rendering, Meta Link cable USB-C 3.2, headstrap clamshell or halo style, speaker arms fragile, color passthrough, 510g, 18W 9v 2A or 15W 5V 3A, 
*v74 ok }}
*v76 pcvr issues }}
|-
| &lt;!--Description--&gt;Meta Quest 3S aka Codename Ventura 
*128Gb
*256Gb
| &lt;!--Vendor ID--&gt;0x2833
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2024 Arm snapdragon xr2 gen 2 cpu, lcd 1832 x 1920 fresnel lenses, 97 FOV, headphone arms fragile, better air flow, no promixity sensor inside, Meta Link cable USB-C 3.2, passthrough, }}
|-
| &lt;!--Description--&gt;Meta Boba 3 
| &lt;!--Vendor ID--&gt;0x2833
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2027 ultra-wide 180° x 120° FOV, snapdragon XR2 G2,  }}
|-
| &lt;!--Description--&gt;Meta Tiramisu 
| &lt;!--Vendor ID--&gt;0x2833
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2027  µOLED displays with 90 pixels per degree,  }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Pimax 5K Super Plus 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2019 }}
|-
| &lt;!--Description--&gt;Pimax 8K
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2020  }}
|-
| &lt;!--Description--&gt;Pimax 8K-X 8KX 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2021  }}
|-
| &lt;!--Description--&gt;Pimax Crystal Light 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 tethered to PC with 2160 x 2160 4k 120Hz, 115° and 96° FOV, inside-out tracking, no battery, display port cable, variable qc and customer service, }}
|-
| &lt;!--Description--&gt;Pimax Crystal Super 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 tethered to PC with 3640 x 3640 4k 90hz, 116°+ and 100° FOV,  eye tracking, inside-out tracking, no battery, display port cable, }}
|-
| &lt;!--Description--&gt;Pimax Dream Air with Lighthouse(s)  
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2026 tethered 3840 by 3552 @90Hz micro oled with pancake lens, 100 HFOV 96 VFOV but FOV IPD changes in app, link box for headset 2 split y cables, removable face gasket, 290g, steamVR2 bases and controllers, eye tracking, }}
|-
| &lt;!--Description--&gt;Pimax Dream Air SLAM 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2026  Simultaneous Localization and Mapping (SLAM) tracking inside-out so no base stations,  }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;[https://somniumspace.com/ Somnium VR One VR1] [https://portal.vrgineers.com/user-guide/software/ open source] VR headset
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 pcvr 2880 x 2880 per eye @90 @120Hz, 125° horizontal 100° vertical FOV, 2 x SteamVR 2.0 bases, passthrough, 900g }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Varjo Aero VR-1 Headset 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2022 psu needed, 2 x Mini LED binocular of 150 nits, 2880x2720 per, 90Hz, FOV 102° horizontal, 73° vertical, 720g with headstrap, 2 x SteamVR 2.0 basestations, no speakers/mic, hdmi and usb3.0}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Varjo Aero XR-3 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Varjo Aero XR-4 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Opinion 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Camelo La Melaza Music Shield 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|2026 no usb only bluetooth ,  }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;InAir 2 elite suite 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 ar  nits 46FOV , , 4h battery life, 80g, }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Oakley Vanguard 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;RayNeo Air 3s 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 AR 100in 46FOV 650nits, usb-c 79g  }}
|-
| &lt;!--Description--&gt;RayNeo Air 3S Pro 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 AR 135in virtual display 46FOV 1200nits, usb-c 80g }}
|-
| &lt;!--Description--&gt;RayNeo Air 4 Pro 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2026 AR oled vision 4000 processing, HDR10, 47 FOV }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Rokid Max 2
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 ar 147in 50 FOV 650nits, usb-c back left, 76g, }}
|-
| &lt;!--Description--&gt;Rokid AI Spatial with Station 2 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 AR 600nits 147in 50FOV  75g, }}
|-
| &lt;!--Description--&gt;Rokid 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| ar ai smart glass}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Viture Pro 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 135in 46 FOV 1000nits, magnetic connector, 77g, }}
|-
| &lt;!--Description--&gt;VITURE XR Luma 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 ar 147in 1200p 50 FOV, }}
|-
| &lt;!--Description--&gt;Viture Luma Pro 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 152in 52 FOV 1000nits 1200p, 3dof, , 79g, }}
|-
| &lt;!--Description--&gt;Viture Luma Ultra 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 in  FOV, 2 cameras, 3dof 6dof,  }}
|-
| &lt;!--Description--&gt;[https://github.com/wheaney/XRLinuxDriver Viture Luma Pro] 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Viture Beast 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 ar 1250nits 58FOV 174in, magnetic,  88g,  }}
|-
| &lt;!--Description--&gt;VITURE Beast X Glasses models (Immersive 3D Moonlight) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2026 based 2D to 3D conversion with support DP Alt Mode (DisplayPort over USB-C), 1200p, 3df tracking, practic lenses 58deg POV, }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Xreal One 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 ar 600nits, 50FOV, 3dof, usb-c 84g,  }}
|-
| &lt;!--Description--&gt;XReal One Pro 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 ar 700nits 57FOV 171in, usb-c, x1 3dof, }}
|-
| &lt;!--Description--&gt;Nreal now Xreal Air 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 , micro-oled 1080p, audio, virtual uvc ar displays, }}
|-
| &lt;!--Description--&gt;Nreal now Xreal Real3D 1S 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2026 AI based 2D to 3D conversion 57 FOV, , virtual uvc ar displays not vr, }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Xiami XR 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Xtal 8k
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Opinion 
|-
| &lt;!--Description--&gt;Apple Vision Pro 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|2022 tethered AR mixed reality glasses,   3300ppi, 800g, }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Google XR 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;HTC Vive Focus 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2018 standalone }}
|-
| &lt;!--Description--&gt;HTC Vive Focus Plus 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2018 android with 2 1440 x 1600 75Hz amoled, inside-out, durable motion controllers, Vive port,  }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;HTC Vive Pro EYE 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|2019 dual-OLED displays 2880 x 1600 combined resolution), SteamVR 2.0 tracking, foveated rendering, Tobii, it enables gaze-based menu navigation with avatar eye contact, proprietary cables, }}
|-
| &lt;!--Description--&gt;HTC Vibe Cosmos 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|2018  poor tracking and lifespan on controllers,  }}
|-
| &lt;!--Description--&gt;HTC Vibe Cosmos Elite 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|2020 1440x1700 per eye resolution, 90 Hz refresh rate, 6 DoF tracking, 2880 x 1700 combined pixel resolution, 97° FoV, two controllers and two base stations. Lighthouse tracking, }}
|-
| &lt;!--Description--&gt;HTC Vive Focus Vision Wired 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No| }}
|-
| &lt;!--Description--&gt;HTC Vive Focus 3 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2021 per-eye resolution of 2448×2448 at 90 Hz, a 120-degree field of view, Qualcomm Snapdragon XR2 Gen 1,  }}
|-
| &lt;!--Description--&gt;HTC Vive XR Elite VR Headset Deluxe Pack 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|2022 snapdragon xr2 gen 1, }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Pico Goblin 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2017 android based, 2.5K 1280x1440 per eye @70Hz, 92° FoV, and 3DoF (three degrees of freedom) tracking (Orientation tracking only—yaw, pitch, roll), single controller, snapdragon 820, ipd adjustment 54-71 mm, 600g,  }}
|-
| &lt;!--Description--&gt;ByteDance Pico G2 4K
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2020 android standalone VR headset, 3840 x 2160 (4K) LCD screen, Snapdragon 835 processor, 3DoF so rotational movement (looking around, pointing) rather than positional movement (walking, leaning), does not support hand or eye tracking, 800g }}
|-
| &lt;!--Description--&gt;ByteDance Pico NEO 2 EYE
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2020 6DoF 360g snapdragon 845 display 4k 75Hz tracking inside-out - magnetic field for controllers - pico software on android 8 - eye tracking }}
|-
| &lt;!--Description--&gt;ByteDance Pico Neo 3 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2022 Snapdragon XR2 Gen, 4K 3664 x 1920 90Hz lcd, battery at rear, displayport, Pico apparently emulates Oculus controllers, }}
|-
| &lt;!--Description--&gt;ByteDance Pico Neo 3 Pro 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2022 }}
|-
| &lt;!--Description--&gt;ByteDance Pico Neo 3 Link 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2022 }}
|-
| &lt;!--Description--&gt;ByteDance Pico 4 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2023 2160x2160 panel per eye 75Hz 90Hz 105 FOV, Arm snapdragon xr gen 1, }}
|-
| &lt;!--Description--&gt;ByteDance Pico 4 ultra 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2023 2160 x 2160 @90 105 FOV, snapdragon XR2 G2, streaming from PC with alvr, wireless streaming from PC with WiVRn, Pico apparently emulates Oculus controllers, not plug and play, }}
|-
| &lt;!--Description--&gt;ByteDance Pico 5 aka Project Swan aka Vision Pro Competitor 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2026 micro-oled BOE 3840 x 3840 4000ppi per eye, MLA pancake lenses, custom pico arm cpu, pico os 6 android, eye and hand tracking, 300g,  }}
|-
| &lt;!--Description--&gt;ByteDance Pico  
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Samsung Galaxy XR VR 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 3552 x 3840 @60-90 109 FOV , Arm snapdragon XR2+ Gen 2, }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Shiftall MeganeX 8K 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2024 android  }}
|-
| &lt;!--Description--&gt;[https://en.shiftall.net/products/meganex8k MeganeX Superlight 8K] 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 android (3552 x 3840 pixels) into pixel count yields 27.27MP 10-bit HDR-compatible 4K resolution micro OLED panels @90Hz, pancake lenses 94 FOV, SteamVR™ tracking, 180g, 5V 2A, }}
|-
| &lt;!--Description--&gt;[https://en.shiftall.net/products/meganex8kmk2 MeganeX 8K Mk2 MkII] [https://github.com/sboys3/CustomHeadsetOpenVR community] 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2026 pcvr linux, 4K per eye (1.35inch micro OLED 3552x3840 10 bit HDR) 27MP @90Hz 75Hz 72Hz pancake, upto 108 hor 100 vert FOV, usb-c and dp cables to breakout box, 5V 2.1A, 200g}}
|-
| &lt;!--Description--&gt;Shiftall 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2026 }}
|-
| &lt;!--Description--&gt;Shiftall 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Opinion 
|-
| &lt;!--Description--&gt;Acer Windows(TM) MR AH101 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2018 Dual 2.89” LCD panels 2880 x 1440 combined (1440 x 1440 per eye) Up to 90Hz (HDMI 2.0), or 60Hz (HDMI 1.4), Field of View FOV 95, Tracking Inside-out, lots of light leak, }} 
|-
| &lt;!--Description--&gt;Acer H7001 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2017 wmr 1440 x 1440 per-eye resolution @90Hz refresh rate, and 100-degree field of view FOV, inside-out tracking with front-mounted cameras so no external sensors, flip-up visor design but has a &quot;screen door effect,&quot; subpar foam padding, win10 to win11 24H2,  }}
|-
| &lt;!--Description--&gt;Dell Visor Mixed Reality VRP100 VR118
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2017 2x 1440x1440 a bit of nose light leak }}
|-
| &lt;!--Description--&gt;Fujitsu 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2017 cheap and lots of light leak }}
|-
| &lt;!--Description--&gt;[https://github.com/HadesVR HadesVR] with [https://github.com/ManoloMancelli/Persephone-Classic-Controller Persephone Controller]
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;[https://www.youtube.com/watch?v=HFaVjB1uNOM Persephone 3 Pro DiY 6Dof SteamVR Headset], 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;HP Reverb G1 VR1000 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2019 WMR 2160 x 2160 @90Hz, 115 FOV, , hp proprietary headset cable end, 2 camera tracking but poor and controllers can be unresponsive, 500g front heavy, flight sims rather than gaming,  }}
|-
| &lt;!--Description--&gt;HP 1440p Spatial Computing 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2019 dim display }}
|-
| &lt;!--Description--&gt;[https://forums.x-plane.org/forums/topic/294764-vr-in-linux-without-steam/ HP Reverb G2] WMR VR3000 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2020 2 2160 x 2160 90Hz, needs Windows10 or Win 11 24H2, 4 camera tracking, controllers can be unresponsive, hp proprietary headset cable end, , }} 
|-
| &lt;!--Description--&gt;HP 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Mirage Solo is a Standalone VR headset
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2018 Qualcomm Snapdragon 835, 1280x1440 per eye resolution, 75 Hz refresh rate, }}
|-
| &lt;!--Description--&gt;Lenovo Explorer VR2511N (G0A2) VR windows mixed reality (WMR) 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2018 LCD 2.89&quot; 1440 x 1440 per eye @90Hz, 6 DOF position tracking, 400g, }}
|-
| &lt;!--Description--&gt;[https://github.com/relativty/relativty open source relativty] 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Samsung MHD Odyssey XE800ZAA WMR 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2018 9V 500mA oled screens 2x 1440x1600 with usb3 and hdmi cables but bluetooth dongle required }}
|-
| &lt;!--Description--&gt;Samsung MHD Odyssey+ Plus WMR 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2019 dual 3.5-inch AMOLED displays 2880 x 1600 total @90Hz, 6DOF inside-out tracking with usb3 and hdmi cables but bluetooth dongle required, use only win10 or win11 24H2,  }}
|-
| &lt;!--Description--&gt;Sony PSVR 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|2016 2x 1080x960 up to 120Hz, lots of cables and computation brick, sony camera needed for tracking, ps4 or move controllers, }} 
|-
| &lt;!--Description--&gt;Virtuality 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|1992 , , Amiga 3000 with TI chips, }}
|-
| &lt;!--Description--&gt;Virtuix Omni 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2013 VR treadmill changed course to commercial VR and pivotted back again 2020, }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Opinion 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
|}


=== HDMI CEC transmitter and receiver ===

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
|}


=== TV Remote Control MCE IR transmitter and receiver ===

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Compro K100 K300
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|need extra software support}}
|-
| &lt;!--Description--&gt;Elitegroup Computer Systems
| &lt;!--Vendor ID--&gt;0x1019
| &lt;!--Product ID--&gt;0x0f38
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;GMYLE MCE 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{Maybe|acts as usb-hid with limited keyboard like controls }}
|-
| &lt;!--Description--&gt;Hauppauge WinTV-PVR kit
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|untested}}
|-
| &lt;!--Description--&gt;Logitech Harmony 300 i300 600 650 800 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|need extra software support}}
|-
| &lt;!--Description--&gt;Microsoft MCE Commander 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|2005 need extra software support}}
|-
| &lt;!--Description--&gt;Microsoft 1039 rev 1
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|2005 home top of square shape direction keys}}
|-
| &lt;!--Description--&gt;Microsoft 1039 rev 2
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|2006 home under circle spaced direction keys}}
|-
| &lt;!--Description--&gt;Microsoft 1069 SMK Manufacturing, Inc
| &lt;!--Vendor ID--&gt;0x0609
| &lt;!--Product ID--&gt;0x0334 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|2007 untested}}
|-
| &lt;!--Description--&gt;Philips RC1974506/00 
| &lt;!--Vendor ID--&gt;0x0471
| &lt;!--Product ID--&gt;0x0815
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|untested}}
|-
| &lt;!--Description--&gt;Sony RM-MCE10E PC REMOTE CONTROL VGN-AR21M VGX-XL100 VGN-AR21B/AR21S 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Sony RM-MCE20E PC REMOTE CONTROL
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Sony RM-MCE30E PC REMOTE CONTROL VGN-AW21XY VGX-TP3E VGX-TP3G 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Sony RM-MCE50E PC REMOTE CONTROL VGC-LA2R 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Opinion 
|-
| &lt;!--Description--&gt;TSDX-IR14 USB MCE Media Center External Infrared IR Receiver
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;chipsets support CIR (consumer IR) Winbond W83977F/AF, SMC IrCC 2.0 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|technical reasons it's not possible to use USB IrDA dongles}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| &lt;!--Description--&gt;Zotac RC2604323/01G Zbox Media Remote Control with IR USB Receiver OVU710
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
|}


{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;Anycubic Cobra 2 Max 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Bambu Labs A1 Mini 3D printer 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{No|2019 EMS proprietary slicer app and cloud use, eSUN}}
|-
| &lt;!--Description--&gt;Bambu Labs X1 Carbon 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2022  }}
|-
| &lt;!--Description--&gt;Bambu Labs X2D 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025  }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Creality K1
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Creality K2
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Creality 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Elegoo 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Lulzbot 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Prusa 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt; 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt; 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Qidi 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Snapmaker U1 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk|2025 tool changer  }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;Sovol SV08 Max
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| open source voron model, }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Opinion 
|-
| &lt;!--Description--&gt;desktop pick and place machines AFARCO PNP running OpenPnP for Desktop SMT 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|}


==ethwrap.class - Host Data Link &quot;Cable Bridge&quot; for data transfer==

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| Advance USBNET (eTEK design)
| 0x0525
| 0x9901
| 
| {{N/A|untested}}
|-
| ALi Uli M5632 (chip)
| 
| 
| 
| {{N/A|untested}}
|-
| Aten (Ali Corporation) UN201
| 0x0402
| 0x5632
| 
| {{maybe|force binding from rawwarp to ethwrap}}
|-
| Belkin (eTek design see below)
| 0x050d
| 0x0004
| 
| {{N/A|untested}}
|-
| Digitus DN-3004 - USB Host Link
| 
| 
| 
| {{yes|works}}
|-
| EPSON USB client
| 0x0525
| 0x2888
| 
| {{N/A|untested}}
|-
| eTEK
| 0x056c
| 0x8100
| 
| {{N/A|untested}}
|-
| KC-190
| 0x050f
| 0x0190
| 
| {{N/A|untested}}
|-
| GeneSys GL620USB
| 
| 
| 
| {{no|no driver the half-duplex GL620USB is NOT supported, products using it include the Inland Pro USB Quick Link}}
|-
| GeneSys GL620USB-A
| 
| 
| 
| {{N/A|untested}}
|-
| Laplink Gold (uses NetChip 1080)
| 
| 
| 
| {{N/A|untested}}
|-
| Prolific 2301/2302 (Jaton USB ConNET) (BAFO DirectLinq) 
| 0x067b
| 0x0000 and 0x0001
| 0x0004
| {{maybe|detected but untested}}
|-
| Xircom PGUNET (uses AnchorChips 2720)
| 0x0547
| 0x2727
| 
| {{N/A|untested}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
|}

==cdcacm.class - USB modem==

The CDC ACM driver exposes the USB modem as a virtual serial modem or a virtual COM port to the operating system. The driver enables sending both data and AT commands, either through ACM (separating data and AT commands over different channels) or through Serial Emulation (passing the AT commands as is and as part of the data stream).

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| Alcatel OT-I650 
| 0x1bbb
| 0x0003
| 
| {{N/A|untested}}
|-
| Acatel Dymamode/Dynamite
| 0x06b9
| 0xa5a5
| 
| {{N/A|untested Zyxel Prestige 630-13 - untested PROLiNK Hurricane 8000 external link }}
|-
| AnyData ADU-100A ADU-E100A ADU-E100D ADU-E100H D10
| 0x16d5
| 0x6501
| 
| {{N/A|untested}}
|-
| AnyData ADU-310
| 0x16d5
| 0x650
| 
| {{N/A|untested}}
|-
| AnyData ADU-500A ADU-510A ADU-510L ADU-520A
| 0x16d5
| 0x6502
| 
| {{N/A|untested}}
|-
| AnyData ADU-610 ADU-620
| 0x16d5
| 0x650
| 
| {{N/A|untested}}
|-
| BT On-Air USB MODEM 
| 0x079b
| 0x000f
| 
| {{N/A|untested}}
|-
| Conexant USB MODEM CX93010 
| 0x0572
| 0x1321
| 
| {{N/A|untested}}
|-
| Conexant USB MODEM RD02-D400 
| 0x0572
| 0x1324
| 
| {{N/A|untested}}
|-
| Conexant Chipset 
| 0x06ea
| 0x0002
| 
| {{N/A|untested AUS N367 Roadster II 56 USB (Model AM5050R3) - untested }}
|-
| [http://accessrunner.sourceforge.net/ Conexant AccessRunner]
| 0x0586
| 0x330a
| 
| {{N/A|untested }}
|-
| Creative Modem Blaster USB DE5670
| 0x1690
| 0x0101
| 
| {{N/A|untested}}
|-
| FIREFLY, MediaTek Inc
| 0x0e8d
| 0x0003
| 
| {{N/A|untested}}
|-
| Huawei E122
| 0x12d1
| 0x1446
| 
| {{yes|works}} [http://aros-exec.org/modules/newbb/viewtopic.php?post_id=49126#forumpost49126]
|-
| Huawei E160, E160E, E160G
| 0x12d1
| 0x1003
| 
|{{yes|works}} [http://aros-exec.org/modules/newbb/viewtopic.php?post_id=51888#forumpost51888] (Chipset: Qualcomm MSM6246)
|-
| Huawei E169 also known as Vodafone K3715 and Huawei K3715 
| 0x12d1
| 0x1001
| 
|{{yes|works}} [http://aros-exec.org/modules/newbb/viewtopic.php?topic_id=4941&amp;forum=4&amp;post_id=44683#forumpost44683] (Chipset: Qualcomm MSM7200)
|-
| Huawei E220 &quot;Vodafone EasyBox II&quot; &quot;T-Mobile wnw Box Micro&quot; also known as Huawei K3565 
| 0x12d1
| 0x1003
|
| {{yes|works, see E169 above (Chipset: Qualcomm MSM6280)}}
|-
| Huawei E1750
| 0x12d1
| 0x1001
| 
| {{N/A|untested (Chipset: Qualcomm MSM6290)}}
|-
| Huawei E170, E172, E176 
| 0x12d1
| 0x1003
| 
| {{N/A|untested (Chipset: Qualcomm MSM7200)}}
|-
| Huawei E180
| 0x12d1  
| 0x1406
| 
| {{yes|Works (Chipset: Qualcomm MSM7200)}}
|-
| KYOCERA AH-K3001V 
| 0x0482
| 0x0203
| 
| {{N/A|untested}}
|-
| LG CU515
| 
| 
| 
| {{N/A|untested}}
|-
| MediaTek Inc GPS 
| 0x0e8d
| 0x3329
| 
| {{N/A|untested}}
|-
| Metricom GS Modem 
| 0x0870
| 0x0001
| 
| {{N/A|untested}}
|-
| Motorola MOTOMAGX phones 
| 0x22b8
| 0x6425
| 
| {{N/A|untested}}
|-
| Motorola Q Phone 
| 0x22b8
| 0x7000
| 
| {{N/A|untested}}
|-
| Hummingbird huc56s (Conexant) 
| 0x0572
| 0x1329
| 
| {{N/A|untested}}
|-
| Netcomm Roadster II 128 ISDN
| 
| 
| 
| {{N/A|untested}}
|-
| Nokia n70 N95 HSDPA
| 
| 
| 
| {{yes|works - see [http://aros-exec.org/modules/newbb/viewtopic.php?start=0&amp;topic_id=4415&amp;viewmode=flat&amp;order=ASC here]}}
|-
| OGO
| 0x045E
| 0x0079
| 0090
| {{no|no driver}}
|-
| Olitec ADSL Modem V2 
| 0x08e3
| 0x0100 / 0x0102
| 
| {{N/A|untested}}
|-
| &lt;!--Description--&gt;Onda PT502HS 
| &lt;!--Vendor ID--&gt;0x19D2
| &lt;!--Product ID--&gt;0x0001
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
| Radicom V92HU-E2
| 
| 
| 
| {{N/A|untested}}
|-
| &lt;!--Description--&gt;Samsung i8510 Innov8 Symbian smartphone
| 0x04e8
| 0x6651
| &lt;!--Revision--&gt;
| {{yes|works}} [http://aros-exec.org/modules/newbb/viewtopic.php?start=0&amp;topic_id=5552&amp;viewmode=flat&amp;order=ASC&amp;type=&amp;mode=0] 
|-
| Samsung Tocco Lite (aka GT-S5230)
| 0x04e8
| 0x6795
| &lt;!--Revision--&gt;
| {{yes|works}} [http://aros-exec.org/modules/newbb/viewtopic.php?start=0&amp;topic_id=5552&amp;viewmode=flat&amp;order=ASC&amp;type=&amp;mode=0] 
|-
| Shiro / Aztech USB MODEM UM-3100 
| 0x0572
| 0x1328
| 
| {{N/A|untested}}
|-
| ZyDAS 56K USB MODEM 
| 0x0ace
| 0x1602
| 
| {{N/A|untested}}
|-
| ZyDAS 56K USB MODEM 
| 0x0ace
| 0x1608
| 
| {{N/A|untested}}
|-
| ZyDAS 56K USB MODEM - new version 
| 0x0ace
| 0x1611
| 
| {{N/A|untested}}
|-
| Zoom Telephonics Model 3095F USB MODEM 
| 0x0803
| 0x3095
| 
| {{N/A|untested}}
|-
| Ugobe Pleo
| 0x6962
| 0x0100
| 0x0100
| {{Yes|Works}}
|}


==Misc==

palmpda.class - no [http://aminet.net/package/util/libs/PdaLinkPoseidon pdalink.library and tools] in AROS 

 Palm PDA (discontinued) synchronisation requires a port of pdalink.library and its tools through virtual usbpalm.device.

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| Palm IIIx (OS3.1) serial rs-232 only
| 
| 
| 
| {{no|no }}
|-
| Palm IIIc (OS3.5)
| 
| 
| 
| {{no|no }}
|-
| Palm V
| 
| 
| 
| {{no|no }}
|-
| Palm m100
| 
| 
| 
| {{no|no }}
|-
| Palm m125 first USB - last with aaa batteries
| 
| 
| 
| {{no|no }}
|-
| Palm m500 (OS4)
| 
| 
| 
| {{no|no }}
|-
| Tungsten T (OS5) first arm cpu 
| 0x
| 0x
| 0x
| {{no|no }}
|-
| Zire 31 (OS 5.28) color arm-based
| 
| 
| 
| {{no|no }}
|-
| [[:w:Handspring (company)|Handspring Visor]] – USB support out of box
|
|
|
| {{no|no }}
|-
| Handspring Treo 600 – last one for [[:w:Handspring (company)|Handspring]] 
| 
| 
| 
| {{no|no }}
|-
| Treo 700w
| 
| 
| 
| {{no|no }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}}
|-
|}


bluetooth.class - needs Bluetooth (Viking King Harald &quot;Bluetooth&quot; Gormsson (Old Norse: Haraldr Blátǫnn Gormsson; Danish: Harald Blåtand Gormsen) stack to work (not written due to licensing fees to use the symbol merging the Younger Futhark runes for H (ᚼ) and B (ᛒ), representing Harald's initials)
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}}
|-
|}


ccid.class - Chip/Smart Card Interface Devices (not implemented)
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;cyberJack RFID basis
| &lt;!--Vendor ID--&gt;0x0C4B
| &lt;!--Product ID--&gt;0x9102
| &lt;!--Revision--&gt;0001
| &lt;!--Opinion--&gt;{{no|no driver}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{no|no driver}}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{N/A|untested}}
|-
|}


dfu.class - DFU firmware upgrade
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| &lt;!--Description--&gt;iPhone 3, 4, 5, 5c 
| &lt;!--Vendor ID--&gt;0x05ac
| &lt;!--Product ID--&gt;0x1290 0x1292 0x1294
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| 32bit use with caution could cause damage}}
|-
| &lt;!--Description--&gt;iPhone 5s, 6, 7, 8, X 
| &lt;!--Vendor ID--&gt;0x05ac
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| 64bit use with caution could cause damage}}
|-
| &lt;!--Description--&gt;M-Audio/Midiman USB audio
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt;
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Description
| Vendor ID
| Product ID
| Revision
| Opinion 
|-
| &lt;!--Description--&gt;iPad 1, iPad 2 A1395 A1430, iPad 3, ipad mini A1432, iPad A1458 4th Gen (MD512LL/A),  
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;2008-2013 32bit A4, A5 up to Apple A6X, iOS 1 to 10, 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|-
| &lt;!--Description--&gt;iPad Air (1st generation) A1474, A1475, A1476, 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;2014-2015 [https://github.com/AsahiLinux 64bit], A7, iOS 11 up to 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;2015 64bit A8, A8X, 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;2016 64bit A9, A9X, 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;2017 64bit A10, A10X, 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;2018 64bit A11 
|-
| &lt;!--Description--&gt;iPad Air 3rd Gen A2153, A2123, A2154, iPad Mini 5th Gen, 
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;2019 64bit A12 
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;{{unk| }}
|-
|}


RocketTool (USB Rocket Launchers - Toy missile launchers)
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;3px&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| Original Launcher and StrikerII (includes laser)
| 0x1130
| 0x0202
| 
| {{yes|works }}
|-
| Dream Cheeky USB Missile Launcher or USB Cirus Cannon
| 0x1941
| 0x8021
| 
| {{no|no driver }}
|-
| Dream Cheeky USB Webcam Missile Launcher
| 0x1941
|
| 
| {{no|no driver }}
|-
| Rocket Baby
| 0x0a81
| 0x0701
| 
| {{no|no driver }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|}


DRadioTool (FM Radios - USB radio devices D-Link/Gemtek)
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;5%&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| D-Link DSB-R100 USB 
| 0x04b4
| 0x1002
| 0x0410
| {{yes|works }}
|-
| [http://www.neoseeker.com/forums/383/t257009-link-usb-dru-r100-radio/ GemTek USB FM Radio 21]
| 0x04b4
| 0x1002
| 
| {{N/A|untested }}
|-
| &lt;!--Description--&gt;
| &lt;!--Vendor ID--&gt;
| &lt;!--Product ID--&gt; 
| &lt;!--Revision--&gt;
| &lt;!--Opinion--&gt;
|}


UproarTool (Valencia MPX mp3 player and others)
{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;30%&quot; | Description 
! width=&quot;3px&quot; |Vendor ID
! width=&quot;10%&quot; |Product ID
! width=&quot;10%&quot; |Revision 
! width=&quot;50%&quot; |Opinion
|-
| Korean D Square Valencia MPX-Player
| 0x04e8
| various
| 
| {{N/A|untested }}
|-
|}


{{BookCat}}</text>
      <sha1>jlbs6ltd4ti6p98lelils878f3e7t1d</sha1>
    </revision>
  </page>
  <page>
    <title>Template:Quality/color</title>
    <ns>10</ns>
    <id>229054</id>
    <revision>
      <id>4676724</id>
      <parentid>3495253</parentid>
      <timestamp>2026-10-18T10:22:21Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <origin>4676724</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="484" sha1="mxgox483fokmj1lannp5y616zj59nur" xml:space="preserve">&lt;includeonly&gt;{{#tag:nowiki|{{#switch:{{lc:{{{1|}}}}}
 | fb           = #6699ff
 | a            = #66ffff
 | b            = #b2ff66
 | c            = #ffff66
 | start        = #ffaa66
 | stub         = #ff9393
 | category|cat = #abb0c9
 | shelf        = #e6d9ff
 | subject      = #e6d9ff
 | template     = #fbceb1
 | nb           = #bfbfbf
 | project      = #98FF98
 | unassessed   = transparent
 | #default     = transparent}}}}&lt;/includeonly&gt;&lt;noinclude&gt;
{{documentation}}
&lt;/noinclude&gt;</text>
      <sha1>mxgox483fokmj1lannp5y616zj59nur</sha1>
    </revision>
    <revision>
      <id>4676725</id>
      <parentid>4676724</parentid>
      <timestamp>2026-10-18T10:23:42Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Doesn't work as intended.</comment>
      <origin>4676725</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="468" sha1="2yl51bqx3qg9o81ldy6n2hy8v268bre" xml:space="preserve">&lt;includeonly&gt;{{#switch:{{lc:{{{1|}}}}}
 | fb           = #6699ff
 | a            = #66ffff
 | b            = #b2ff66
 | c            = #ffff66
 | start        = #ffaa66
 | stub         = #ff9393
 | category|cat = #abb0c9
 | shelf        = #e6d9ff
 | subject      = #e6d9ff
 | template     = #fbceb1
 | nb           = #bfbfbf
 | project      = #98FF98
 | unassessed   = transparent
 | #default     = transparent}}&lt;/includeonly&gt;&lt;noinclude&gt;
{{documentation}}
&lt;/noinclude&gt;</text>
      <sha1>2yl51bqx3qg9o81ldy6n2hy8v268bre</sha1>
    </revision>
    <revision>
      <id>4676726</id>
      <parentid>4676725</parentid>
      <timestamp>2026-10-18T10:24:04Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <origin>4676726</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="485" sha1="ojt6fhmzd866wpn58z1p563bw2ilcwt" xml:space="preserve">&lt;includeonly&gt;&lt;nowiki&gt;{{#switch:{{lc:{{{1|}}}}}
 | fb           = #6699ff
 | a            = #66ffff
 | b            = #b2ff66
 | c            = #ffff66
 | start        = #ffaa66
 | stub         = #ff9393
 | category|cat = #abb0c9
 | shelf        = #e6d9ff
 | subject      = #e6d9ff
 | template     = #fbceb1
 | nb           = #bfbfbf
 | project      = #98FF98
 | unassessed   = transparent
 | #default     = transparent}}&lt;/nowiki&gt;&lt;/includeonly&gt;&lt;noinclude&gt;
{{documentation}}
&lt;/noinclude&gt;</text>
      <sha1>ojt6fhmzd866wpn58z1p563bw2ilcwt</sha1>
    </revision>
    <revision>
      <id>4676727</id>
      <parentid>4676726</parentid>
      <timestamp>2026-10-18T10:25:33Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Undid 3 revisions from [[Special:Diff/4676724|4676724]] until [[Special:Diff/4676726|4676726]]</comment>
      <origin>4676727</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="459" sha1="euhgltc27emmvr6bqkzaw1f2slft6um" xml:space="preserve">&lt;includeonly&gt;{{#tag:nowiki|{{#switch:{{lc:{{{1|}}}}}|fb           = #6699ff
|a            = #66ffff
|b            = #b2ff66
|c            = #ffff66
|start        = #ffaa66
|stub         = #ff9393
|category|cat = #abb0c9
|shelf        = #e6d9ff
|subject      = #e6d9ff
|template     = #fbceb1
| nb           = #bfbfbf
| project      = #98FF98
| unassessed   = transparent
| #default     = transparent}}}}&lt;/includeonly&gt;&lt;noinclude&gt;
{{documentation}}
&lt;/noinclude&gt;</text>
      <sha1>euhgltc27emmvr6bqkzaw1f2slft6um</sha1>
    </revision>
    <revision>
      <id>4676728</id>
      <parentid>4676727</parentid>
      <timestamp>2026-10-18T10:26:52Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Flatten template</comment>
      <origin>4676728</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="435" sha1="9ibrxl9ul8n4iju5tnih9egoazjiqvu" xml:space="preserve">&lt;includeonly&gt;{{#tag:nowiki|{{#switch:{{lc:{{{1|}}}}}|fb= #6699ff|a            = #66ffff|b            = #b2ff66|c            = #ffff66|start        = #ffaa66|stub         = #ff9393|category|cat = #abb0c9|shelf        = #e6d9ff|subject      = #e6d9ff|template     = #fbceb1| nb           = #bfbfbf| project      = #98FF98| unassessed   = transparent| #default     = transparent}}}}&lt;/includeonly&gt;&lt;noinclude&gt;
{{documentation}}
&lt;/noinclude&gt;</text>
      <sha1>9ibrxl9ul8n4iju5tnih9egoazjiqvu</sha1>
    </revision>
  </page>
  <page>
    <title>Aros/User/Applications</title>
    <ns>0</ns>
    <id>237399</id>
    <revision>
      <id>4676721</id>
      <parentid>4676332</parentid>
      <timestamp>2026-10-18T10:04:22Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4676721</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="243694" sha1="ahi8mofl9enomynn9ghw9rolz9g0nu3" xml:space="preserve">
==Introduction==


[[#Graphical Image Editing Art]]
[[#Office Application]]
[[#Audio]]

[[#Misc Application]]
[[#Games &amp; Emulation]]

[[#Application Guides]]

[[#top|...to the top]]


[[#top|...to the top]]

Most apps can be opened on the Workbench (aka publicscreen pubscreen) which is the default display option but can offer a custom one set to your configurations (aka custom screen mode promotion). These custom ones tend to stack so the possible use of A-M/A-N method of switching between full screens and the ability to pull down screens as well 

If you are interested in creating or porting new software, see [http://en.wikibooks.org/wiki/Aros/Developer/Docs here]

{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Internet Applications 
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1 (68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;Web Online Browser [], 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=network/browser Amelinium], Odyssey 2.0, [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1175&amp;highlight=odyssey&amp;rowstart=100 Odyssey 3.0], [], 
|&lt;!--Amiga OS--&gt;[https://juen.in/ Amelinium], [https://blog.alb42.de/programs/amifox/ amifox] with [https://github.com/alb42/wrp wrp server], IBrowse*, [https://github.com/zapek/Voyager Voyager], [https://github.com/amigazen/aweb3/ AWeb 3.6 src], [https://github.com/matjam/aweb AWeb Src], [http://aminet.net/package/comm/www/NetSurf-m68k-sources Netsurf], [], 
|&lt;!--AmigaOS4--&gt;[ Odyssey OWB], [ Timberwolf (Firefox port 2011)], [http://amigaworld.net/modules/newbb/viewtopic.php?forum=32&amp;topic_id=32847 OWB-mui], [http://strohmayer.org/owb/ OWB-Reaction], IBrowse*, [http://os4depot.net/index.php?function=showfile&amp;file=network/browser/aweb.lha AWeb], Voyager, [http://www.os4depot.net/index.php?function=browse&amp;cat=network/browser Netsurf], 
|&lt;!--MorphOS--&gt;Wayfarer, [http://fabportnawak.free.fr/owb/ Odyssey OWB], [ Netsurf], IBrowse*, AWeb, [], 
|-
|&lt;!--Sub Menu--&gt;Downloading videos and/or audio [https://github.com/yt-dlp/yt-dlp yt-dlp], [https://clipgrab.org/ clipgrab],  
|&lt;!--AROS--&gt;[], [https://blog.alb42.de/amitube/ Amitube], 
|&lt;!--Amiga OS--&gt;[https://blog.alb42.de/amitube/ Amitube], [ smtube], 
|&lt;!--AmigaOS4--&gt;[https://blog.alb42.de/amitube/ Amitube], getVideo, 
|&lt;!--MorphOS--&gt;[ ytsearch], [https://blog.alb42.de/amitube/ Amitube], [ getVideo], Tubexx 
|-
|&lt;!--Sub Menu--&gt;E-mailing SMTP POP3 IMAP based 
|&lt;!--AROS--&gt;Emailinium, [http://archives.arosworld.org/index.php?function=browse&amp;cat=network/email SimpleMail], [http://sourceforge.net/projects/simplemail/files/ src], [https://github.com/jens-maus/yam YAM] 
|&lt;!--Amiga OS--&gt;Emailinium, [http://sourceforge.net/projects/simplemail/files/ SimpleMail], [https://github.com/jens-maus/yam YAM]
|&lt;!--AmigaOS4--&gt;SimpleMail, YAM, 
|&lt;!--MorphOS--&gt; SimpleMail, YAM, 
|-
|&lt;!--Sub Menu--&gt;Internet Chat IRC, ICB, 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=network/chat WookieChat], [https://sourceforge.net/projects/wookiechat/ Wookiechat src], [http://archives.arosworld.org/index.php?function=browse&amp;cat=network/chat AiRcOS], Jabberwocky, 
|&lt;!--Amiga OS--&gt;[https://github.com/charabaruk/WookieChat Wookiechat], AmIRC 
|&lt;!--AmigaOS4--&gt;Wookiechat 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=5 Wookiechat], [ AmIRC], 
|-
|&lt;!--Sub Menu--&gt;Instant Messaging IM like [https://github.com/BlitterStudio/amidon Hollywood lang based Mastodon client], BlueSky AT protocol, Facebook(TM), Twitter X (TM), Bitlbee IRC Gateway and others 
|&lt;!--AROS--&gt;[https://github.com/kaffeine1/telegram-amiga telegram-amiga], [http://archives.arosworld.org/index.php?function=browse&amp;cat=network/chat jabberwocky], 
|&lt;!--Amiga OS--&gt;[http://amitwitter.sourceforge.net/ AmiTwitter], CLIMM, SabreMSN, [https://sourceforge.net/projects/ajabberwocky/ jabberwocky], 
|&lt;!--AmigaOS4--&gt;[http://amitwitter.sourceforge.net/ AmiTwitter], SabreMSN,
|&lt;!--MorphOS--&gt;[http://amitwitter.sourceforge.net/ AmiTwitter], [http://morphos.lukysoft.cz/en/vypis.php?kat=5 PolyglotNG], SabreMSN,
|-
|&lt;!--Sub Menu--&gt;Torrents 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=network/p2p ArTorr], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;CTorrent, Transmission 
|&lt;!--MorphOS--&gt;MLDonkey, Beehive, [http://morphos.lukysoft.cz/en/vypis.php?kat=5 Transmission], CTorrent, 
|-
|&lt;!--Sub Menu--&gt;FTP 
|&lt;!--AROS--&gt;[https://github.com/BlitterStudio/dopus5 Dopus5 Magellan], MarranoFTP, [https://aminet.net/package/comm/tcp/wput-0.3.4c.i386-aros wput i386 c src]
|&lt;!--Amiga OS--&gt;[https://github.com/BlitterStudio/dopus5 Dopus5 Magellan], [http://aminet.net/package/comm/tcp/AmiFTP AmiFTP], AmiTradeCenter, ncFTP, [https://aminet.net/package/comm/tcp/sana2-tftpclient sana2 tftpclient c src]
|&lt;!--AmigaOS4--&gt;[https://github.com/BlitterStudio/dopus5 Dopus5 Magellan], 
|&lt;!--MorphOS--&gt;[https://github.com/BlitterStudio/dopus5 Dopus5 Magellan], [http://morphos.lukysoft.cz/en/vypis.php?kat=5 Pftp], [http://aminet.net/package/comm/tcp/AmiFTP-1.935-OS4 AmiFTP], 
|-
|&lt;!--Sub Menu--&gt;WYSIWYG Web Site Editor
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Internet Radio Streaming Audio [http://www.gnu.org/software/gnump3d/ gnump3d], [http://www.icecast.org/ Icecast2] Server (Broadcast) and Client (Listen), [ mpd], [http://darkice.sourceforge.net/ DarkIce], [http://www.dyne.org/software/muse/ Muse], 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=audio/misc], Mplayer (Icecast Client only), 
|&lt;!--Amiga OS--&gt;[https://github.com/sandlbn/TuneFinder TuneFinder C Src], [https://github.com/sandlbn/TuneFinderMUI TuneFinderMUI], [http://amigazeux.net/anr/ AmiNetRadio], [https://github.com/boingball/MintAMP MintAMP], [], 
|&lt;!--AmigaOS4--&gt;[http://www.tunenet.co.uk/ Tunenet], 
|&lt;!--MorphOS--&gt;Mplayer, AmiNetRadio, 
|-
|&lt;!--Sub Menu--&gt;VoIP (Voice over IP) with SIP Client (Session Initiation Protocol) or Asterisk IAX2 Clients Softphone (skype like) 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;AmiPhone with Speak Freely, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Weather Forecast 
|&lt;!--AROS--&gt;[http://sourceforge.net/projects/zunetools/files/ WeatherBar], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/workbench AWeather], []
|&lt;!--Amiga OS--&gt;[http://amigazeux.net/wetter/ Wetter], [https://github.com/emartisoft/AmiWeatherForecasts AmiWeatherForecasts src], 
|&lt;!--AmigaOS4--&gt;[http://os4depot.net/?function=showfile&amp;file=utility/workbench/flipclock.lha FlipClock], 
|&lt;!--MorphOS--&gt;[http://amigazeux.net/wetter/ Wetter], 
|-
|&lt;!--Sub Menu--&gt;Street Road Maps Route Planning GPS Tracking  
|&lt;!--AROS--&gt;[https://blog.alb42.de/programs/muimapparium/ MuiMapparium] [https://build.alb42.de/ Build of MuiMapp versions], 
|&lt;!--Amiga OS--&gt;AmiAtlas*, UKRoutePlus*, [http://blog.alb42.de/ AmOSM], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[http://blog.alb42.de/programs/mapparium/ Mapparium], 
|-
|&lt;!--Sub Menu--&gt;Clock and Date setting from the internet by network time protocol (NTP) [https://www.timeanddate.com/worldclock/ World Clock], [http://www.time.gov/ old standard NIST Internet Time Servers], 
|&lt;!--AROS--&gt;[https://github.com/bohunamiga/PiNTP PiNTP], [https://archives.arosworld.org/?function=showfile&amp;file=utility/workbench/amitimekeeper.i386-aros.lha amitimekeeper with c src], [http://archives.arosworld.org/index.php?function=browse&amp;cat=network/misc ntpsync], [], 
|&lt;!--Amiga OS--&gt;ntpsync, [http://aminet.net/package/util/cdity/AmiTimeKeeper amitimekeeper], [http://aminet.net/comm/misc/netclock netclock], [https://aminet.net/package/comm/net/sntp sntp], [http://aminet.net/package/util/time/ScreenTime ScreenTime], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Newsgroups
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;[http://newscoaster.sourceforge.net/ Newscoaster], [https://github.com/jens-maus/newsrog NewsRog], [ WorldNews], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;RSS 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;[https://github.com/Team-Boingo/AmiRSS AmiRSS src]
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;AI
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;[https://github.com/murinsel/AmigaAI Claude], [https://github.com/geekychris/amiga_mcp AI on host machine], [], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;BBS
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.


==Graphical Image Editing Art==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Image Editing
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1(68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;Pixel Raster Artwork [https://github.com/LibreSprite/LibreSprite LibreSprite based on GPL aseprite], [https://github.com/abetusk/hsvhero hsvhero], [], 
|&lt;!--AROS--&gt;[https://sourceforge.net/projects/zunetools/files/ZunePaint/ ZunePaint], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/edit LunaPaint], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/edit GrafX2], [ LodePaint needs OpenGL], 
|&lt;!--Amiga OS--&gt;[http://www.amigaforever.com/classic/download.html PPaint], GrafX2, [https://github.com/grovdata/Amiga_Sources/blob/master/software.md DeluxePaint], [http://www.amiforce.de/perfectpaint/perfectpaint.php PerfectPaint], Zoetrope, Brilliance2*, 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=graphics/edit LodePaint], GrafX2, 
|&lt;!--MorphOS--&gt;Sketch, Pixel*, GrafX2, [http://morphos.lukysoft.cz/en/vypis.php?kat=3 LunaPaint]
|-
|&lt;!--Sub Menu--&gt;Image viewing 
|&lt;!--AROS--&gt;[http://sourceforge.net/projects/zunetools/files/ ZuneView], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/viewer LookHere], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/viewer LoView], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/viewer PicShow] , [http://amigaworld.net/modules/newbb/viewtopic.php?mode=viewtopic&amp;topic_id=31400&amp;forum=32&amp;start=80&amp;viewmode=flat&amp;order=0#583458 Picture Album], 
|&lt;!--Amiga OS--&gt;PicShow, PicView, Photoalbum,
|&lt;!--AmigaOS4--&gt;WarpView, PicShow, flPhoto, Thumbs, [http://amigaworld.net/modules/newbb/viewtopic.php?mode=viewtopic&amp;topic_id=31400&amp;forum=32&amp;start=80&amp;viewmode=flat&amp;order=0#583458 Picture Album], 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=3 ShowGirls], [http://amigaworld.net/modules/newbb/viewtopic.php?mode=viewtopic&amp;topic_id=31400&amp;forum=32&amp;start=80&amp;viewmode=flat&amp;order=0#583458 Picture Album]
|-
|&lt;!--Sub Menu--&gt;Photography retouching / Image Manipulation like Photoshop(tm)  
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/edit RNOEffects], 
|&lt;!--Amiga OS--&gt;[ Tecsoft Video Paint aka TVPaint], Photogenics*, ArtEffect*, ImageFX*, XiPaint, fxPaint, ImageMasterRT, Opalpaint, 
|&lt;!--AmigaOS4--&gt;WarpView, flPhoto, [http://www.os4depot.net/index.php?function=browse&amp;cat=graphics/edit Photocrop]
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=3 ShowGirls], ImageFX*, 
|-
|&lt;!--Sub Menu--&gt;Manage RAW picture folder galleries like Darktable, RAWtherapy, etc 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Graphic Format Converter - ICC profile support sRGB, Adobe RGB, XYZ and linear RGB 
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;GraphicsConverter, ImageStudio, [http://www.coplabs.org/artpro.html ArtPro]
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Thumbnail Generator [], 
|&lt;!--AROS--&gt;[http://sourceforge.net/projects/zunetools/files/ ZuneView], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/shell Thumbnail Generator]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Icon Editor
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/iconedit Archives], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/workbench Icon Toolbox], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=graphics/iconedit IconEditor]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;2D Pixel Art Animation 
|&lt;!--AROS--&gt;Lunapaint
|&lt;!--Amiga OS--&gt;PPaint, AnimatED, Scala*, GoldDisk MovieSetter*, Walt Disney's Animation Studio*, ProDAD*, [https://github.com/historicalsource/DeluxePaint DeluxePaint src], Brilliance
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=3 Titler] 
|-
|&lt;!--Sub Menu--&gt;2D SVG based MovieSetter type 
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;MovieSetter*, Fantavision*
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Morphing 
|&lt;!--AROS--&gt;[ GLMorph]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;2D Cad (qcad-&gt;LibreCAD, etc.) 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;Xcad, MaxonCAD
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;3D Cad like FreeCad, BRL-CAD, OpenSCAD, AvoCADo, etc. using dxf, obj (vertices), blend, 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;XCad3d*, DynaCADD*, [https://aminet.net/package/gfx/3d/Cycas178_EN Cycas]*, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;3D Model Rendering of glft (json) gbl (png jpg), usdz (USD files with materials, textures, and animations), FBX Filmbox is a proprietary Autodesk format, 
|&lt;!--AROS--&gt;POV-Ray
|&lt;!--Amiga OS--&gt;[http://www.discreetfx.com./amigaproducts.html CINEMA 4D]*, POV-Ray, Lightwave3D*, Real3D*, Caligari24*, Reflections/Monzoom*, [https://github.com/privatosan/RayStorm Raystorm src], Tornado 3D, [https://github.com/AlphaPixel/Eric-Graham-1987-Juggler-Raytracer-1.0 Eric-Graham-1987-Juggler-Raytracer-1.0]
|&lt;!--AmigaOS4--&gt;Blender, POV-Ray, Yafray
|&lt;!--MorphOS--&gt;Blender, POV-Ray, Yafray
|-
|&lt;!--Sub Menu--&gt;3D Format Converter [], [], 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/?function=showfile&amp;file=graphics/convert/ 3doc.i386-aros], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=showfile&amp;file=graphics/convert/ivcon.lha IVCon]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Screen grabbing display 
|&lt;!--AROS--&gt;[ Screengrabber], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/misc snapit], [http://archives.arosworld.org/index.php?function=browse&amp;cat=video/record screen recorder], []
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Grab graphics music from apps [https://github.com/Malvineous/ripper6 ripper6], [],
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Manage metadata of images [https://github.com/exiv2/exiv2 exiv2], [ EXIF/IPTC/XMP metadata manipulation], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.

[[#top|...to the top]]

==Office Application==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Office
!width:10%;|AROS (x86)
!width:10%;|[http://en.wikipedia.org/wiki/Amiga_software Commodore-Amiga OS 3.1] (68k)
!width:10%;|[http://en.wikipedia.org/wiki/AmigaOS_4 Hyperion OS4] (PPC)
!width:10%;|[http://en.wikipedia.org/wiki/MorphOS MorphOS] (PPC)
|-
|&lt;!--Sub Menu--&gt;Office Suite 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;[ Softwood Final Office], [ Wordworth Office], [ Digita Office],  [ The Works!], [ Europress Mini Office], [], [ Papyrus Office Demo], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[ Papyrus Office], 
|-
|&lt;!--Sub Menu--&gt;Word-processing 
|&lt;!--AROS--&gt;[https://finalwriter.godaddysites.com/ Final Writer 7*], [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1995&amp;rowstart=20&amp;pid=12668#post_12668 Slovo], [https://github.com/sodero/MUI-Vim/releases MUI-Vim], [https://archives.arosworld.org/index.php?function=browse&amp;cat=office/wordprocessing Cinnamon Writer], [], 
|&lt;!--AmigaOS--&gt;[ Softwood FinalCopy II*], Haage AmigaWriter*, Digita WordWorth*, Softwood FinalWriter*, Micro-Systems Excellence 3*, Arnor Protext, Rashumon, [ InterWord], [ KindWords], [WordPerfect], [ New Horizons Flow], [ CygnusEd Pro], [ Micro-systems Scribble], 
|&lt;!--AmigaOS4--&gt;AbiWord, [ CinnamonWriter], 
|&lt;!--MorphOS--&gt;[ Cinnamon Writer], [http://www.meta-morphos.org/viewtopic.php?topic=1246&amp;forum=53 scriba], [http://morphos.lukysoft.cz/en/index.php Papyrus Office], 
|-
|&lt;!--Sub Menu--&gt;Spreadsheets 
|&lt;!--AROS--&gt;[https://blog.alb42.de/programs/leu/ Leu], [https://archives.arosworld.org/index.php?function=browse&amp;cat=office/spreadsheet ], 
|&lt;!--AmigaOS--&gt;[https://aminet.net/package/biz/spread/ignition-src Ignition Src 1.3], [MaxiPlan 500 Plus], [OXXI Plan/IT v2.0 Speadsheet], [ Superplan], [ Creative Developments TurboCalc], [ ProCalc], [ InterSpread], [Digita DGCalc], [ Gold Disk Advantage], [ Micro-systems Analyze!]
|&lt;!--AmigaOS4--&gt;Gnumeric, [https://ignition-amiga.sourceforge.net/ Ignition], 
|&lt;!--MorphOS--&gt;[ ignition], [http://morphos.lukysoft.cz/en/vypis.php Papyrus Office], 
|-
|&lt;!--Sub Menu--&gt;Presentations
|&lt;!--AROS--&gt;[http://www.hollywoood-mal.com/ Hollywood]*, 
|&lt;!--Amiga OS--&gt;[http://www.hollywoood-mal.com/ Hollywood]*, [https://github.com/evaneykelen/mediapoint-amiga MediaPoint C and asm], PointRider, Scala*, 
|&lt;!--Amiga OS4--&gt;[http://www.hollywoood-mal.com/ Hollywood]*, PointRider 
|&lt;!--MorphOS--&gt;[http://www.hollywoood-mal.com/ Hollywood]*, PointRider
|-
|&lt;!--Sub Menu--&gt;Databases 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=office/database BeeBase], 
|&lt;!--Amiga OS--&gt;Precision Superbase 4 Pro*, Arnor Prodata*, [https://sourceforge.net/projects/beebase/ BeeBase], Datastore, FinalData*, AmigaBase, Fiasco, Twist2*, [Digita DGBase], [], 
|&lt;!--AmigaOS4--&gt;BeeBase, SQLite, 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=6 BeeBase], 
|-
|&lt;!--Sub Menu--&gt;PDF Viewing, editing and digital signatures 
|&lt;!--AROS--&gt;[https://github.com/tomaszstaniak/aros-foliopdf folio version of mupdf], [http://sourceforge.net/projects/arospdf/ ArosPDF via splash xpdf], [https://github.com/wattoc/AROS-vpdf vpdf], 
|&lt;!--Amiga OS--&gt;APDF 
|&lt;!--AmigaOS4--&gt;AmiPDF 
|&lt;!--MorphOS--&gt;APDF, vPDF, 
|-
|&lt;!--Sub Menu--&gt;Note Taking markdown support like Obsidian like, joplin, OneNote, EverNotes, xournalpp, etc 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;[http://aminet.net/package/text/edit/Kickdown c src with reaction gui], [], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Study and analyse, collect, organize, annotate, cite, and share
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;PIM Personal Information Manager - Day Diary Planner Calendar App Filofax like 
|&lt;!--AROS--&gt;[ ], [ ], [ ], 
|&lt;!--Amiga OS--&gt;Digita Organiser*, On The Ball, Everyday Organiser, [ Contact Manager], 
|&lt;!--AmigaOS4--&gt;AOrganiser, 
|&lt;!--MorphOS--&gt;[http://polymere.free.fr/orga_en.html PolyOrga], 
|-
|&lt;!--Sub Menu--&gt;Accounting
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=office/misc ETB], LoanCalc, [ ], [ ], [ ], 
|[ Digita Home Accounts2], Accountant, Small Business Accounts, Account Master, [ Amigabok], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Project Management Research 
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;SuperGantt, SuperPlan, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Desktop 
|&lt;!--AROS--&gt;Wanderer, Scalos, Workbook, DOpus5, 
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[https://github.com/zapek/Ambient Ambient Src]
|-
|&lt;!--Sub Menu--&gt;System Wide Search 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=utility/filetool Finder], [], [], 
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;System Wide Dictionary - multilingual [http://sourceforge.net/projects/babiloo/ Babiloo], [http://code.google.com/p/stardict-3/ StarDict], 
|&lt;!--AROS--&gt;[ ],  
|&lt;!--AmigaOS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;System wide Thesaurus - multi lingual
|&lt;!--AROS--&gt;[ ], 
|Kuma K-Roget*, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Sticky Desktop Notes (post it type) 
|&lt;!--AROS--&gt;[http://aminet.net/package/util/wb/amimemos.i386-aros AmiMemos], [https://aminet.net/package/util/wb/amimemos.src-aros AmiMemos Src], [], 
|&lt;!--Amiga OS--&gt;[http://aminet.net/package/util/wb/StickIt-2.00 StickIt v2], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;DTP Desktop Publishing 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/edit RNOPublisher], 
|&lt;!--Amiga OS--&gt;[http://pagestream.org/ Pagestream]*, Professional Pro Page*, Saxon Publisher, Pagesetter, PenPal, 
|&lt;!--AmigaOS4--&gt;[http://pagestream.org/ Pagestream]* 
|&lt;!--MorphOS--&gt;[http://pagestream.org/ Pagestream]* 
|-
|&lt;!--Sub Menu--&gt;Printing 
|&lt;!--AROS--&gt;Postscript 3 laser printers, [https://github.com/bohunamiga/MintPRINT MintPRINT AirPrint IPP], [ Ghostscript], [], 
|&lt;!--Amiga OS--&gt;[https://github.com/boingball/MintPRINT MintPRINT IPP], [https://github.com/Andiweli/AmiAirprint AmiAirprint], [http://www.irseesoft.de/tp_what.htm TurboPrint]*, [ GutenPrint], [https://aminet.net/package/comm/tcp/NetPrinter NetPrinter LPR], [], [], 
|&lt;!--AmigaOS4--&gt;(some native drivers), 
|&lt;!--MorphOS--&gt;early TurboPrint included, [https://aminet.net/package/comm/tcp/NetPrinter NetPrinter LPR], 
|-
|&lt;!--Sub Menu--&gt;Scanning 
|&lt;!--AROS--&gt;[ SCANdal], [], 
|&lt;!--Amiga OS--&gt;FxScan*, ScanQuix*, [https://github.com/boingball/MintSCAN MintSCAN], 
|&lt;!--AmigaOS4--&gt;SCANdal (Sane)
|&lt;!--MorphOS--&gt;SCANdal
|-
|&lt;!--Sub Menu--&gt;OCR
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/convert gOCR] 
|&lt;!--AmigaOS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[http://morphos-files.net/categories/office/text Tesseract] 
|-
|&lt;!--Sub Menu--&gt;Text Editing
|&lt;!--AROS--&gt;Jano Editor (already installed as Editor), [http://archives.arosworld.org/index.php?function=browse&amp;cat=development/edit EdiSyn], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/text/edit Annotate], [https://archives.arosworld.org/index.php?function=browse&amp;cat=development/edit Vim], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/text/edit FrexxEd] [https://github.com/vidarh/FrexxEd src], [ NoWinEd], 
|&lt;!--Amiga OS--&gt;[https://aminet.net/package/text/edit/TurboText20 TurboText20 ttx], Annotate, MicroGoldED/CubicIDE*, CygnusED*, Protext*, NoWinED, 
|&lt;!--AmigaOS4--&gt;Notepad, Annotate, CygnusED*, NoWinED, 
|&lt;!--MorphOS--&gt;MorphOS ED, NoWinED, GoldED/CubicIDE*, CygnusED*, Annotate, 
|-
|&lt;!--Sub Menu--&gt;Office Fonts [http://sourceforge.net/projects/fontforge/files/fontforge-source/ Font Designer] 
|&lt;!--AROS--&gt;[ ], [ ], 
|&lt;!--Amiga OS--&gt;TypeSmith*, SaxonScript (GetFont Adobe Type 1), 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Drawing Vector
|&lt;!--AROS--&gt;[http://sourceforge.net/projects/amifig/ ZuneFIG previously AmiFIG], [https://github.com/serk118/designworks-aros designworks aros 64bit]
|&lt;!--Amiga OS--&gt;Drawstudio*, ProVector*, ArtExpression*, Professional Draw*, AmiFIG, MetaView, [https://gitlab.com/amigasourcecodepreservation/designworks Design Works Src], [], 
|&lt;!--AmigaOS4--&gt;MindSpace, [http://www.os4depot.net/index.php?function=browse&amp;cat=graphics/edit amifig], 
|&lt;!--MorphOS--&gt;SteamDraw, [http://aminet.net/package/gfx/edit/amifig amiFIG], 
|-
|&lt;!--Sub Menu--&gt;video conferencing (jitsi) 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;source code hosting
|&lt;!--AROS--&gt;Gitlab, 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Remote Desktop (server)
|&lt;!--AROS--&gt;[http://sourceforge.net/projects/zunetools/files/VNC_Server ArosVNCServer], 
|&lt;!--Amiga OS--&gt;[http://s.guillard.free.fr/AmiVNC/AmiVNC.htm AmiVNC], [http://dspach.free.fr/amiga/avnc/index.html AVNC]
|&lt;!--AmigaOS4--&gt;[http://s.guillard.free.fr/AmiVNC/AmiVNC.htm AmiVNC] 
|MorphVNC, vncserver
|-
|&lt;!--Sub Menu--&gt;Remote Desktop (client) login and connect to another machine 
|&lt;!--AROS--&gt;[https://sourceforge.net/projects/zunetools/files/VNC_Client/ ArosVNC], [http://archives.arosworld.org/index.php?function=browse&amp;cat=network/misc rdesktop], 
|&lt;!--Amiga OS--&gt;[http://twinvnc.free.fr/index.php?menu=01&amp;lang=eng TwinVNC], [http://dspach.free.fr/amiga/vva/index.html VVA], [http://www.hd-zone.com/ RDesktop]
|&lt;!--AmigaOS4--&gt;[http://twinvnc.free.fr/index.php?menu=01&amp;lang=eng TwinVNC], [http://www.hd-zone.com/ RDesktop]
|[http://twinvnc.free.fr/index.php?menu=01&amp;lang=eng TwinVNC], [http://www.hd-zone.com/ RDesktop]
|-
|&lt;!--Sub Menu--&gt;notifications 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;Ranchero 
|&lt;!--AmigaOS4--&gt;Ringhio 
|&lt;!--MorphOS--&gt;MagicBeacon 
|-
|&lt;!--Sub Menu--&gt;Biometric facial logins and fingerprint security features 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Fido U2F (Universal 2nd Factor) and later FIDO2 (W3C WebAuthn with CTAP2) key authorization like Yubico YubiKey, etc 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.

[[#top|...to the top]]

==Audio==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Audio
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1(68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;Playing playback Audio like MP3, [https://github.com/chrg127/gmplayer NSF], [https://github.com/kode54/lazyusf miniusf .usflib] [https://gitlab.com/kode54/psflib with pfslib], [], [], etc 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=video/play Mplayer], [ HarmonyPlayer hp], [http://www.a500.org/downloads/audio/index.xhtml playcdda] CDs, [ WildMidi Player], [https://bszili.morphos.me/ UADE mod player], [], [ RNOTunes], [ mp3Player], [], 
|&lt;!--Amiga OS--&gt;AmiNetRadio, AmigaAmp, playOGG, [https://codeberg.org/tygre/amimodradio amimodradio]
|&lt;!--AmigaOS4--&gt;TuneNet, SimplePlay, AmigaAmp, TKPlayer
|AmiNetRadio, Mplayer, Kaya, AmigaAmp
|-
|&lt;!--Sub Menu--&gt;Editing Audio 
|&lt;!--AROS--&gt;[ Audio Evolution 4] 
|&lt;!--Amiga OS--&gt;[https://sourceforge.net/projects/hd-rec/ HD-Rec Src], [http://www.sonicpulse.de/eng/news.html SoundFX], [ Samplitude], 
|&lt;!--AmigaOS4--&gt;[https://sourceforge.net/projects/hd-rec/ HD-Rec], AmiSoundED, [http://os4depot.net/?function=showfile&amp;file=audio/record/audioevolution4.lha Audio Evolution 4] 
|[http://www.hd-rec.de/HD-Rec/index.php?site=home HD-Rec], 
|-
|&lt;!--Sub Menu--&gt;Editing Tracker Music
|&lt;!--AROS--&gt;[https://github.com/hitchhikr/protrekkr Protrekkr], [ Schism Tracker], [http://archives.arosworld.org/index.php?function=browse&amp;cat=audio/tracker MilkyTracker], [http://www.hivelytracker.com/ HivelyTracker], [ Radium in AROS already],  [http://www.a500.org/downloads/development/index.xhtml libMikMod], 
|&lt;!--Amiga OS--&gt;MilkyTracker, HivelyTracker, DigiBooster, Octamed SoundStudio, [https://github.com/elindstrom/soundtracker soundtracker], 
|&lt;!--AmigaOS4--&gt;MilkyTracker, HivelyTracker, GoatTracker
|MilkyTracker, GoatTracker, DigiBooster, 
|-
|&lt;!--Sub Menu--&gt;Editing Music [], [https://github.com/kmatheussen/camd CAMD] and/or staves and musical notes on manuscript [https://github.com/ratchov/midish midish] midi sequencer 
|&lt;!--AROS--&gt;[http://bnp.hansfaust.de/ Bars and Pipes], [], [], 
|&lt;!--Amiga OS--&gt;[http://bnp.hansfaust.de/ Bars'n'Pipes], MusicX* David &quot;Talin&quot; Joiner &amp; Craig Weeks (for Notator-X), Deluxe Music Construction Set DMCS2*, [https://github.com/timoinutilis/midi-sequencer-amigaos Horny c Src] [https://github.com/kas1e/midi-sequencer-amigaos/tree/master/HornyGCC HornyGCC OS4 src] [https://github.com/capehill/midi-sequencer-amigaos Horny OS4 fork src] [https://www.amigans.net/modules/newbb/viewtopic.php?start=0&amp;topic_id=8143&amp;order=ASC&amp;status=&amp;mode=0 OS4 thread], HD-Rec, [https://aminet.net/package/mus/midi/dominatorV1_51 Dominator], [https://github.com/royaltm/Amiga-midiIn Amiga-midiIn], [ Aegis Sonix 2.0]
|&lt;!--AmigaOS4--&gt;[https://sourceforge.net/p/hd-rec/code/HEAD/tree/ HD-Rec Src], Rockbeat, [http://bnp.hansfaust.de/download.html Bars'n'Pipes], [https://github.com/gooofy/freeaction Horny OS4 src fork], Audio Evolution 4, 
|&lt;!--MorphOS--&gt;Bars'n'Pipes, 
|-
|&lt;!--Sub Menu--&gt;Sound Sampling 
|&lt;!--AROS--&gt;[ Advanced AHI Recorder all], [https://archives.arosworld.org/index.php?function=browse&amp;cat=audio/record Audio Evolution 4], [http://www.imica.net/SitePortalPage.aspx?siteid=1&amp;did=162 Quick Record], [https://archives.arosworld.org/index.php?function=browse&amp;cat=audio/misc SOX to get AIFF 16bit files], [https://github.com/aros-development-team/AROS/tree/master/workbench/tools/AHIRecord AHIRecord], 
|&lt;!--Amiga OS--&gt;[https://aminet.net/package/mus/edit/AudioEvolution3_src Audio Evolution 3 c src], [ Samplitude]*, Audiomaster IV*, 
|&lt;!--AmigaOS4--&gt;[https://github.com/timoinutilis/phonolith-amigaos phonolith c src], HD-Rec, Audio Evolution 4,
|&lt;!--MorphOS--&gt;[https://sourceforge.net/p/hd-rec/code/HEAD/tree/ HD-Rec Src], Audio Evolution 4,
|-
|&lt;!--Sub Menu--&gt;Audio Processing like easyeffects so having limiter, compressor, convolver, equalizer and auto volume and many other plugins 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Live Looping or Audio Misc - Groovebox like
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;CD/DVD burn
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=utility IsoTools], [https://code.google.com/p/amiga-fryingpan/ FryingPan], 
|&lt;!--Amiga OS--&gt;FryingPan, [ MakeCD], 
|&lt;!--AmigaOS4--&gt;FryingPan, AmiDVD, 
|&lt;!--MorphOS--&gt;[http://www.amiga.org/forums/printthread.php?t=58736 FryingPan], Jalopeano, 
|-
|&lt;!--Sub Menu--&gt;CD/DVD audio rip
|&lt;!--AROS--&gt;Lame, [http://www.imica.net/SitePortalPage.aspx?siteid=1&amp;cfid=0&amp;did=167 Quick CDrip],
|&lt;!--Amiga OS--&gt;Lame,  
|&lt;!--AmigaOS4--&gt;Lame, 
|&lt;!--MorphOS--&gt;Lame,  
|-
|&lt;!--Sub Menu--&gt;MP3 v1 and v2 Tagger
|&lt;!--AROS--&gt;id3ren (v1), [http://archives.arosworld.org/index.php?function=browse&amp;cat=audio/edit mp3info], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|
|-
|&lt;!--Sub Menu--&gt;Audio Convert
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=audio/misc Sox], [], 
|&lt;!--Amiga OS--&gt;[http://aminet.net/package/mus/misc/SoundBox SoundBox], [http://aminet.net/package/mus/misc/SoundBoxKey SoundBox Key], [http://aminet.net/package/mus/edit/SampleE SampleE], sox 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;DJ mixing jamming 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;[https://github.com/djh0ffman/PT1210 Hoffman PT1210 DJ tracker], [], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Radio Automation Software [http://www.rivendellaudio.org/ Rivendell], [http://code.campware.org/projects/livesupport/report/3 Campware LiveSupport], [http://www.sourcefabric.org/en/airtime/ SourceFabric AirTime], [http://www.ohloh.net/p/mediabox404 MediaBox404], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Speakers Audio Sonos Mains AC networked wired controlled 
*2005 ZP100 with ZP80 
*2008 Zoneplayer ZP120 (multi-room wireless amp)  ZP90 receiver only with CR100 controller, 
*2009 ZonePlayer S5, 
*2010 BR100 wireless Bridge (no support),   
*2011 Play:3
*2013 Bridge (no support), Play:1,  
*2016 Arc,   Play:1,   
*Beam (Gen 2),   Playbar,  Ray,   Era 100,   Era 300,   Roam,   Move 2,   
*Sub (Gen 3),   Sub Mini,  Five,  Amp  S2 
|&lt;!--AROS--&gt;SonosController 
|&lt;!--Amiga OS--&gt;SonosController
|&lt;!--AmigaOS4--&gt;SonosController
|&lt;!--MorphOS--&gt;SonosController
|-
|&lt;!--Sub Menu--&gt;Smart Speakers 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.

[[#top|...to the top]]

==Video Creativity and Production==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Video
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1(68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;Playing Video 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=video/play Mplayer], [ VAMP], [http://www.a500.org/downloads/video/index.xhtml CDXL player], [http://www.a500.org/downloads/video/index.xhtml IffAnimPlay], [], 
|&lt;!--Amiga OS--&gt;Frogger*, AMP2, MPlayer, RiVA*, MooViD*, 
|&lt;!--AmigaOS4--&gt;DvPlayer, MPlayer 
|&lt;!--MorphOS--&gt;MPlayer, Frogger, AMP2, VLC 
|-
|&lt;!--Sub Menu--&gt;Streaming Video and game streaming like OBS studio, Parsec, [https://github.com/lizardbyte/sunshine sunshine], [https://github.com/moonlight-stream/moonlight-qt moonlight], etc 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Playing DVD 
|&lt;!--AROS--&gt;[http://a-mc.biz/ AMC]*, Mplayer 
|&lt;!--Amiga OS--&gt;AMP2, Frogger 
|&lt;!--AmigaOS4--&gt;[http://a-mc.biz/ AMC]*, DvPlayer*, AMP2,  
|&lt;!--MorphOS--&gt;Mplayer 
|-
|&lt;!--Sub Menu--&gt;Screen Recording
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=video/record Screenrecorder], [ ], [ ], [ ], [ ], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;Screenrecorder, 
|-
|&lt;!--Sub Menu--&gt;Create Edit Individual Video - Amiga like OSs have no pro NLE 
|&lt;!--AROS--&gt;[ Mencoder], [ Quick Videos], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/edit AVIbuild], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/misc FrameBuild], FFMPEG, 
|&lt;!--Amiga OS--&gt;[ MainConcept Mainactor Broadcast*], [http://en.wikipedia.org/wiki/Video_Toaster Video Toaster*] with [https://discreetfx.com/openvideotoaster.html some c src], MacroSystem MovieShop 4.3*, proDAD Adorage*, [ IOSpirit VHI studio]*, [Gold Disk ShowMaker], [], 
|&lt;!--AmigaOS4--&gt;FFMpeg/GUI 
|&lt;!--MorphOS--&gt;Blender, Mencoder, FFmpeg
|-
|&lt;!--Sub Menu--&gt;Subtitle editor 
|&lt;!--AROS--&gt;[https://aminet.net/package/text/edit/Slarti_Arosx86ABIv0 Slarti_Arosx86ABIv0], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;IP-based video production workflows with High Dynamic Range (HDR), 10-bit color collaborative NDI, 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Blogging like Lemmy or kbin
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;VR face recognition for Vtubers 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;VR chatting Live2D models with Cubism type editor or [https://github.com/AyagamiDev/ayagami ayagami] like with zipped moc3 with model metadata (model3, cdi3) 
&lt;pre&gt;
Model data (cmo3)
Basic motions (can3)
Background image (png)
Set of files for embedding (runtime folder)
• Model data (moc3)
• Motion data (motion3.json)
• Model settings file (model3.json)
• Physics settings file (physics3.json)
• Display auxiliary file (cdi3.json)
&lt;/pre&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;VR chatting chatters .VRML models - standardized 3D file format for VR avatars 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;V-tubers V-tubing like Vseeface with Openseeface tracker or Vpuppr (virtual puppet project) for online live 2d / 3d art models rigging rigged LIV 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.

[[#top|...to the top]]


==Misc Application==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Misc Application
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1 (68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;File Management 
|&lt;!--AROS--&gt;DOpus4, [https://github.com/BlitterStudio/dopus5 DOpus Magellan aka DOpus 5], [ Scalos], [ FileMaster], 
|&lt;!--Amiga OS--&gt;DOpus2, DOpus 4, [https://github.com/BlitterStudio/dopus5 Dopus5 Magellan], ClassAction, FileMaster, DirWork 2*, [https://github.com/RudolphRiedel/DiskMaster2 DiskMaster2 src], 
|&lt;!--AmigaOS4--&gt;DOpus4, [https://github.com/BlitterStudio/dopus5 Dopus5 Magellan], Filer, AmiDisk 
|&lt;!--MorphOS--&gt;DOpus4, [https://github.com/BlitterStudio/dopus5 Dopus5 Magellan], 
|-
|&lt;!--Sub Menu--&gt;Package Application Installer 
|&lt;!--AROS--&gt;[https://github.com/tomaszstaniak?tab=repositories Pkg manager], [https://aros-pkg.azurewebsites.net/search?arch=x86_64 Pkg], [ InstallerNG], 
|&lt;!--Amiga OS--&gt;InstallerNG, Grunch, 
|&lt;!--AmigaOS4--&gt;Jack
|&lt;!--MorphOS--&gt;Jack 
|-
|&lt;!--Sub Menu--&gt;Compression archiver [https://github.com/FS-make-simple/paq9a paq9a], [], 
|&lt;!--AROS--&gt;XAD system is a toolkit designed for handling various file and disk archiver
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[https://aminet.net/package/util/pack/decrunchmania_os4 Crunchmania CrM2 depacker], 
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Binary Hexadecimal Editor 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=development/edit Zaphod], [],
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Filesystem Partition Editor formatter Disk Management
|&lt;!--AROS--&gt;[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1440&amp;highlight=partition&amp;pid=8821#post_8821 QuickPart], [ HDToolBox]
|&lt;!--Amiga OS--&gt;[https://github.com/stefanskotte/hdpart hdpart], [https://github.com/ChuckyGang/AmiPart AmiPart], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Filesystem Repair and backups 
|&lt;!--AROS--&gt;ArSFSDoctor, 
|&lt;!--Amiga OS--&gt;[https://aminet.net/package/disk/bakup/quarterback_src Quarterback Tools C and asm src], [ ], [ ], [ ], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;System Disk check, integrity and history [https://github.com/smartmontools/smartmontools smart tools], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;[], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;File Verification / Repair 
|&lt;!--AROS--&gt;[https://arosarchives.os4depot.net/index.php?function=browse&amp;cat=utility md5sum], [https://arosarchives.os4depot.net/index.php?function=browse&amp;cat=utility/filetool asum], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/filetool workpar2] (PAR2),  [http://zakalwe.fi/~shd/foss/cksfv/files/ compile cksfv from website], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;Par2, 
|-
|&lt;!--Sub Menu--&gt;Multiple File renaming
|&lt;!--AROS--&gt;DOpus 4 or 5, 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Anti Virus
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;VChecker, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Random Wallpaper Desktop changer [ DOpus5], [ Scalos],  
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Alarm Clock, Timer, Stopwatch, Countdown 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/workbench DClock], [http://aminet.net/util/time/AlarmClockAROS.lha AlarmClock], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Edge snap window tool 
|&lt;!--AROS--&gt;[https://github.com/kaffeine1/edgesnap edgesnap]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}


==Misc Application 2==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Misc Application
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1(68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;C/C++ IDE Integrated Development 
|&lt;!--AROS--&gt;[https://sourceforge.net/projects/aidea/ AIDEa], [ Murks], [],  
|&lt;!--Amiga OS--&gt;[http://devplex.awardspace.biz/cubic/index.html Cubic IDE]*, [ StormC], [https://github.com/jens-maus/amide amide], [], 
|&lt;!--AmigaOS4--&gt;CodeBench , [https://gitlab.com/boemann/codecraft CodeCraft], 
|&lt;!--MorphOS--&gt;[http://devplex.awardspace.biz/cubic/index.html Cubic IDE]*, 
|-
|&lt;!--Sub Menu--&gt;C/C++ Text Editors 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/text/edit FrexxEd], [https://github.com/vidarh/FrexxEd FrexxEd src], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/text/edit Annotate] with [https://www.onyxsoft.se/files/annotate_src.lha src], 
|&lt;!--Amiga OS--&gt;[ Protext], [ CED], [], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[https://www.onyxsoft.se/annotate.html Annotate], 
|-
|&lt;!--Sub Menu--&gt;Repository
|&lt;!--AROS--&gt;[ Git]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;Git
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;BASIC Computer Language 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=development/language Basic4SDL], [ Ace Basic], [ X-AMOS], [SDLBasic], [ Alvyn], 
|&lt;!--Amiga OS--&gt;[http://www.amiforce.de/main.php Amiblitz 3] with [https://github.com/AmiBlitz/AmiBlitz3 Asm src], [http://amos.condor.serverpro3.com/AmosProManual/contents/c1.html Amos Pro] with [https://github.com/AmiDARK/AmosProfessionalUnity-Official-Releases Asm src], [http://aminet.net/package/dev/basic/ace24dist ACE Basic], [https://github.com/gooofy/aqb aqb], [], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;sdlBasic
|-
|&lt;!--Sub Menu--&gt;Computer Languages Translation [https://tetracorp.github.io/guide/reverse-engineering-amiga.html], [https://amigasourcecodepreservation.gitlab.io/amiga-assembler-insider-guide/], [https://github.com/kermitfrog/Amiga-Re-Engineering Rust, Ghidra and FS-UAE], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;[https://bitbucket.org/rhinoid/convert68000toc/src/main/ convert m68k seka asm-one to c], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Gui Creators
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=development/guitool MuiBuilder], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[ MuiBuilder],  
|-
|&lt;!--Sub Menu--&gt;Catalog .cd .ct Custom App Language Editors 
|&lt;!--AROS--&gt;FlexCat, [https://archives.arosworld.org/index.php?function=browse&amp;cat=utility Flexcat GUI], [], 
|&lt;!--Amiga OS--&gt;[http://www.geit.de/deu_simplecat.html SimpleCat], FlexCat
|&lt;!--AmigaOS4--&gt;[http://aminet.net/package/dev/misc/simplecat SimpleCat], FlexCat
|&lt;!--MorphOS--&gt;[http://www.geit.de/deu_simplecat.html SimpleCat], FlexCat
|-
|&lt;!--Sub Menu--&gt;Cross Development 
|&lt;!--AROS--&gt;[], [], 
|&lt;!--Amiga OS--&gt;[https://github.com/geekychris/amiga_mcp amiga_mcp], [https://github.com/mbergmann-sh/AmigaED4-IDE AmigaED4-IDE], [https://lemonspawn.com/turbo-rascal-syntax-error-expected-but-begin/ Turbo Rascal], [], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.


==Misc Application 3==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Misc Application
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1(68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;System 
|&lt;!--AROS--&gt;[ SysExplorer], [ SysMon], [ Scout], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Terminals Shells CLIs 
|&lt;!--AROS--&gt;[https://github.com/tomaszstaniak/limpet limpet], [], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;OSK On Screen Keyboard
|&lt;!--AROS--&gt;[], 
|&lt;!--Amiga OS--&gt;[https://aminet.net/util/wb/OSK.lha OSK]
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Screen Magnifier Magnifying Glass Magnification 
|&lt;!--AROS--&gt;[http://www.onyxsoft.se/files/zoomit.lha ZoomIT], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Comic Book CBR CBZ format reader viewer 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/viewer comics], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/viewer comicon], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Ebook Reader 
|&lt;!--AROS--&gt;[https://blog.alb42.de/programs/#legadon Legadon EPUB],[]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Ebook Converter 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Text to Speech tts [https://github.com/JonathanFly/bark-installer Bark], [], 
|&lt;!--AROS--&gt;[ Echo &quot; &quot; &gt;SPEAK:A1 inbuilt], [http://archives.arosworld.org/index.php?function=browse&amp;cat=audio/misc flite], 
|&lt;!--Amiga OS--&gt;[http://www.text2speech.com translator], [https://github.com/sidick/narrator.wyoming narrator.wyoming], [], 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=search&amp;tool=simple FLite]
|&lt;!--MorphOS--&gt;[http://se.aminet.net/pub/aminet/mus/misc/ FLite]
|-
|&lt;!--Sub Menu--&gt;Speech Voice Recognition Dictation - [http://sourceforge.net/projects/cmusphinx/files/ CMU Sphinx], [http://julius.sourceforge.jp/en_index.php?q=en/index.html Julius], [http://www.isip.piconepress.com/projects/speech/index.html ISIP], 
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Speech Voice Changer [], [], [], [], 
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Screen Display Blanker screensaver 
|&lt;!--AROS--&gt;Blanker Commodity (built in), [https://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/screenblanker GarshneBlanker], [http://sourceforge.net/projects/gblanker/ GBlanker Src], [], 
|&lt;!--Amiga OS--&gt;MultiCX, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;ModernArt Blanker, 
|-
|&lt;!--Sub Menu--&gt;Fortune Cookie Quotes Sayings 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/misc AFortune], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}


==Misc Application 4==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Misc Application
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1(68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;Fractals mandelbrot, etc 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/misc], 
|&lt;!--Amiga OS--&gt;ZoneXplorer, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Landscape Rendering 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/raytrace WCS World Construction Set], 
|&lt;!--Amiga OS--&gt;[ Vista Pro], [http://en.wikipedia.org/wiki/World_Construction_Set World Construction Set]
|&lt;!--AmigaOS4--&gt;[ WCS World Construction Set],
|&lt;!--MorphOS--&gt;[ WCS World Construction Set],
|-
|&lt;!--Sub Menu--&gt;Astronomy [https://sourceforge.net/projects/skychart/ skychart freepascal], [], [], 
|&lt;!--AROS--&gt;[ Digital Almanac (ABIv0 only)], 
|&lt;!--Amiga OS--&gt;[http://aminet.net/search?query=planetarium Aminet search], [http://aminet.net/misc/sci/DA3V56ISO.zip Digital Almanac], [https://aminet.net/package/misc/sci/da3sourceV58 Src c V58], [ Galileo renamed to Distant Suns]*, [], 
|&lt;!--AmigaOS4--&gt;[http://sourceforge.net/projects/digital-almanac/ Digital Almanac], Distant Suns*, [http://www.digitaluniverse.org.uk/ Digital Universe]*,
|&lt;!--MorphOS--&gt;[http://www.aminet.net/misc/sci/da3.lha Digital Almanac], [http://www.aminet.net/package/misc/sci/da3-mos-src Src c V56], 
|-
|&lt;!--Sub Menu--&gt;Astrology [https://sourceforge.net/projects/skylendar/ skylendar], [https://github.com/CruiserOne/Astrolog Astrolog], [https://www.astrolog.org/astrolog/astfile.htm Astrology alt site], [https://saravali.github.io/download.html Maitreya], [https://github.com/alamahant/Asteria Asteria], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Genealogy History Family Tree Ancestry Records (FreeBMD, FreeREG, and FreeCEN file formats or GEDCOM GenTree)
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; [ Origins], [ Your Family Tree], [ ], [ ], [ ], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Languages 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;Fun School, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Mathematics ([http://www-fourier.ujf-grenoble.fr/~parisse/install_en.html Xcas], etc.), 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/scientific mathX] 
|&lt;!--Amiga OS--&gt;Maple V, mathX, Fun School, GCSE Maths, [ ], [ ], [ ], 
|&lt;!--AmigaOS4--&gt;Yacas 
|&lt;!--MorphOS--&gt;Yacas 
|-
|&lt;!--Sub Menu--&gt;Maths Graph Function Plotting
|&lt;!--AROS--&gt;[https://blog.alb42.de/programs/#MUIPlot MUIPlot], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;App Utility Launcher Dock toolbar  
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/docky BoingBar], [], 
|&lt;!--Amiga OS--&gt;[https://github.com/adkennan/DockBot Dockbot],
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;3D Printer [https://github.com/OrcaSlicer/OrcaSlicer OrcaSlicer]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;CNC control with laser and vinyl cutting 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;PCB design
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;[ ], [ ], [ ], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Digital Signage
|&lt;!--AROS--&gt;Hollywood, Hollywood Designer 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;HAM radio, amateur radio, packet radio,  [], [], [], [https://cemaxecuter.com/ Dragon OS], [https://github.com/km4ack/73Linux with 73 link update], [https://www.youtube.com/watch?v=YAL5KNePRSg video for], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;[https://github.com/punktniklas/NiKom NiKom], [https://www.amigarealm.com/amiga/amicomms/comm4.htm Comm4], [https://www.amigarealm.com/archives/comms/aarug/ TNC Terminal Node Controller with packets over serial connections on Yaesu or Woxum handheld], [https://aminet.net/comm/misc AmiCom], [ with 7Plus file encoder/decoder], [ mksstv], [ RTTYam], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;modern smart home network like Home Assistant Automation Yellow, Green, Mosquitto, EMQX,  
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;[https://github.com/evil4dmin/ami2ha HA], [https://github.com/sidick/midge mtqq.lib], [https://aminet.net/package/comm/tcp/AmiHomeassist-0.7 AmiHomeassist], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Teaching classroom learning training [https://github.com/moodle/moodle moodle], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.


==Games &amp; Emulation==

Some emulators/games require OpenGL to function and to adjust ahi prefs channels, frequency and unit0 and unit1 and 
[http://aros.sourceforge.net/documentation/users/shell/changetaskpri.php changetaskpri -1]

Rom patching  https://www.marcrobledo.com/RomPatcher.js/ https://www.romhacking.net/patch/ (ips, ups, bps, etc) and this other site supports the latter formats https://hack64.net/tools/patcher.php 

Free public domain roms for use with emulators can be found [http://www.pdroms.de/ here] as most of the rest are covered by copyright rules. If you like to read about old games see [http://retrogamingtimes.com/ here] and [http://www.armchairarcade.com/neo/ here] and a [http://www.vintagecomputing.com/ blog] about old computers. Possibly some of the [http://www.answers.com/topic/list-of-best-selling-computer-and-video-games best selling] of all time. [http://en.wikipedia.org/wiki/List_of_computer_system_emulators Wiki] with emulated systems list.

[https://archive.gamehistory.org/ Archive of VGHF], [https://library.gamehistory.org/ Video Game History Foundation Library search]


{|  class=&quot;wikitable sortable&quot; 
|- 
!width:10%;|Games [http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer Emulation]
!width:10%;|AROS(x86)
!width:10%;|AmigaOS3(68k)
!width:10%;|AmigaOS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;Games Emulation Amstrad CPC 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer], [ Caprice32 (OpenGL &amp; pure SDL)], [ Arnold], [https://retroshowcase.gr/cpcbox-master/], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://os4depot.net/index.php?function=browse&amp;cat=emulation/computer]
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=2], 
|-
|&lt;!--Sub Menu--&gt;Games Emulation Apple2 and 2GS
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Arcade 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem Mame], [ SI Emu (ABIv0 only)], 
|&lt;!--Amiga OS--&gt;Mame, 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem xmame], amiarcadia, 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=2 Mame], 
|-
|&lt;!--Sub Menu--&gt;Games Emulation Atari 2600 [], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem Stella], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Atari 5200 [https://github.com/wavemotion-dave/A5200DS A5200DS], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Atari 7800
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Atari 400 800 130XL [https://github.com/wavemotion-dave/A8DS A8DS], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer Atari800], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Atari Lynx
|&lt;!--AROS--&gt;[http://myfreefilehosting.com/f/6366e11bdf_1.93MB Handy (ABIv0 only)], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Atari Jaguar
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Bandai Wonderswan 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation BBC Micro and Acorn Electron [http://beehttps://bem-unix.bbcmicro.com/download.html BeebEm], [http://b-em.bbcmicro.com/ B-Em], [http://elkulator.acornelectron.co.uk/ Elkulator], [http://electrem.emuunlim.com/ ElectrEm], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Dragon 32 and Tandy CoCo [http://www.6809.org.uk/xroar/ xroar], [], 
|&lt;!--AROS--&gt;[], [], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Commodore C16 Plus4
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Commodore C64
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer Vice (ABIv0 only)], [], 
|&lt;!--Amiga OS--&gt;Frodo, 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem viceplus], 
|&lt;!--MorphOS--&gt;Vice, 
|-
|&lt;!--Sub Menu--&gt;Games Emulation Commodore Amiga
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer Janus UAE], Emumiga, 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://os4depot.net/index.php?function=browse&amp;cat=emulation/computer UAE], 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=2 UAE], 
|-
|&lt;!--Sub Menu--&gt;Games Emulation Japanese MSX MSX2 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Mattel Intelivision
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Mattel Colecovision and Adam
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Milton Bradley (MB) Vectrex [ Vectrex OpenGL], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation PICO8 Pico-8 fantasy video game console [https://github.com/egordorichev/pemsa-sdl/ pemsa-sdl], [https://github.com/jtothebell/fake-08 fake-08], [https://github.com/Epicpkmn11/fake-08/tree/wip fake-08 fork], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Nintendo Gameboy
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem vba no sound], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem vba]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Nintendo NES
|&lt;!--AROS--&gt;[ EmiNES], [http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem Fceu], [https://github.com/takahirox/nes-js?tab=readme-ov-file nes-js], [https://github.com/bfirsh/jsnes jsnes], [https://github.com/angelo-wf/NesJs NesJs], 
|&lt;!--Amiga OS--&gt;AmiNES, [http://www.dridus.com/~nyef/darcnes/ darcNES], 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem amines]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Nintendo SNES
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem Zsnes], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem warpsnes]
|&lt;!--MorphOS--&gt;[http://fabportnawak.free.fr/snes/ Snes9x], 
|-
|&lt;!--Sub Menu--&gt;Games Emulation Nintendo N64 
*HLE and plugins [ mupen64], [https://github.com/ares-emulator/ares ares], [https://github.com/N64Recomp/N64Recomp N64Recomp], [https://github.com/rt64/rt64 rt64], [https://github.com/simple64/simple64 Simple64], 
*LLE [], 
|&lt;!--AROS--&gt;[http://code.google.com/p/mupen64plus/ Mupen64+],
|&lt;!--Amiga OS--&gt;[http://code.google.com/p/mupen64plus/ Mupen64+], [http://aminet.net/package/misc/emu/tr-981125_src TR64], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[ Nintendo Gamecube Wii]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[ Nintendo Wii U]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[https://github.com/yuzu-emu Nintendo Switch]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation NEC PC Engine 
|&lt;!--AROS--&gt;[], [], [https://github.com/yhzmr442/jspce js-pce], 
|[http://www.hugo.fr.fm/ Hugo], [http://mednafen.sourceforge.net/ Mednafen], 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem tgemu]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sega Master System (SMS)
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem Dega], [http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem sms], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem osmose]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sega Genesis/Megadrive
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem gp no sound], [http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem DGen], 
|&lt;!--Amiga OS--&gt;[http://code.google.com/p/genplus-gx/ Genplus], 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem genesisplus]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sega Saturn 
*HLE [https://mednafen.github.io/ mednafen], [http://yabause.org/ yabause], [], 
*LLE [], [], 
|&lt;!--AROS--&gt;?
|&lt;!--Amiga OS--&gt;[http://yabause.org/ Yabause], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sega Dreamcast 
*HLE [https://github.com/flyinghead/flycast  flycast], [https://code.google.com/archive/p/nulldc/downloads NullDC], 
*LLE [], [], 
|&lt;!--AROS--&gt;?
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sinclair ZX80 and ZX81 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer], [], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sinclair Spectrum 
|[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer Fuse (crackly sound)], [http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer SimCoupe], [ FBZX slow], [https://jsspeccy.zxdemo.org/ jsspeccy], [http://torinak.com/qaop/games qaop], 
|&lt;!--Amiga OS--&gt;[http://www.zophar.net/sinclair.html Speculator], [http://www.worldofspectrum.org/x128/index.html X128], 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/computer]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sinclair QL
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer], [], 
|&lt;!--Amiga OS--&gt;[http://aminet.net/package/misc/emu/QDOS4amiga1 QDOS4amiga]
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation SNK NeoGeo Pocket
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem gngeo], NeoPop, 
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sony PlayStation
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem FPSE], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem FPSE]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[ Sony PS2]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[ Sony PS3]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[https://vita3k.org/ Sony Vita]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[https://github.com/shadps4-emu/shadPS4 PS4]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation [http://en.wikipedia.org/wiki/Tangerine_Computer_Systems Tangerine] Oric and Atmos 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer Oricutron]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem Oricutron]
|&lt;!--MorphOS--&gt;[http://aminet.net/package/misc/emu/oricutron Oricutron]
|-
|&lt;!--Sub Menu--&gt;Games Emulation TI 99/4 99/4A [https://github.com/wavemotion-dave/DS994a DS994a], [], [https://js99er.net/#/ js99er], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer], 
|&lt;!--Amiga OS--&gt;[http://aminet.net/package/misc/emu/TI4Amiga TI4Amiga], [http://aminet.net/package/misc/emu/TI4Amiga_src TI4Amiga src in c], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation HP 38G 40GS 48 49G/50G Graphing Calculators
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation TI 58 83 84 85 86 - 89 92 Graphing Calculators
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games emulation Ms-Dos Dosbox type 
|&lt;!--AROS--&gt;[https://github.com/tomaszstaniak/aros-boxerapp Boxer]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|}

{|  class=&quot;wikitable sortable&quot; 
|- 
!width:10%;|Games [https://www.rockpapershotgun.com/ General]
!width:10%;|AROS(x86)
!width:10%;|AmigaOS3(68k)
!width:10%;|AmigaOS4(PPC)
!width:10%;|MorphOS(PPC)
|- style=&quot;background:lightgrey;{{text default color}}; text-align:center; font-weight:bold;&quot;
| Games [https://www.trackawesomelist.com/michelpereira/awesome-open-source-games/ Open Source and others] || AROS || Amiga OS || Amiga OS4 || Morphos 
|-
|&lt;!--Sub Menu--&gt;Games Action like [https://github.com/opentomb/OpenTomb opentomb], [https://github.com/LostArtefacts/TRX TRX formerly Tomb1Main], [https://github.com/TombEngine TombEngine], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/action Thrust], [https://github.com/fragglet/sdl-sopwith sdl sopwith], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/action], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/action BOH], [], 
|&lt;!--Amiga OS--&gt;[https://github.com/BSzili/OpenLara/tree/amiga/src source of openlara SDL2], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Adventure like [http://dotg.sourceforge.net/ DMJ], [https://github.com/kromenak/gengine Gabriel Knight 3], [http://www.sarien.net/ Sierra Sarien], [https://github.com/klembot/twinejs twine js], [https://github.com/QSPFoundation/qspgui Quest Soft Player QSP], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/adventure dmagnetic], [https://archives.arosworld.org/?function=browse&amp;cat=emulation/misc ScummVM], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/roleplaying frotz infocom], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Board like [https://github.com/aperture-software/colditz-escape escape from colditz], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/board], [http://amigan.1emu.net/releases Africa]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Cards 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=game/card], [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1443&amp;rowstart=180&amp;pid=12934#post_12934 Balatro], 
|&lt;!--AmigaOS--&gt;[http://home.arcor.de/amigasolitaire/e/welcome.html Reko], [https://github.com/samskivert/beschei-en beschei Src], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Misc [https://github.com/michelpereira/awesome-open-source-games Awesome open], [https://github.com/bobeff/open-source-games General Open Source], [https://github.com/SAT-R/sa2 Sonic Advance 2], [https://github.com/velorek1/cwordle Wordle type], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/misc], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games FPS like [https://aminet.net/package/game/shoot/D1X_Rebirth_AGA Descent D1X src], [https://github.com/DescentDevelopers/Descent3 Descent 3], [https://github.com/Fewnity/Counter-Strike-Nintendo-DS Counter-Strike-Nintendo-DS], [https://github.com/Aleph-One-Marathon/alephone Bungie Marathon 1994], [https://zdoom.org/downloads UzDoom opengl 3.3], [https://github.com/ZDoom/gzdoom gzdoom opengl 3+], [https://zdoom.org/downloads LZDoom opengl 2.1], [https://github.com/OpenXRay/xray-16 S.T.A.L.K.E.R Xray], [https://staniks.github.io/articles/serious-engine-networking-analysis/ Serious Sam] [https://github.com/Croteam-official/Serious-Engine Serious Engine 1]
|&lt;!--AROS--&gt;Doom, Quake, [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Quake 3 Arena (OpenGL)], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Cube (OpenGL)], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Assault Cube (OpenGL)], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Cube 2 Sauerbraten (OpenGL)], [http://fodquake.net/test/ FodQuake QuakeWorld], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Duke Nukem 3D], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Darkplaces Nexuiz Xonotic], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Doom 3 SDL (OpenGL)], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Hexenworld and Hexen 2], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Aliens vs Predator Gold 2000 avp (openGL)], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Odamex (openGL doom)], [https://archives.arosworld.org/?function=showfile&amp;file=game/fps/ zgloom], [], [https://archives.arosworld.org/?function=showfile&amp;file=game/fps/ ab3dhd], [], 
|&lt;!--Amiga OS--&gt;Doom, Quake, AB3D, Fears, Breathless, Gloom, 
|&lt;!--AmigaOS4--&gt;Doom, Quake, 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=12 Doom], Quake, Quake 3 Arena, 
|-
|&lt;!--Sub Menu--&gt;Games MMORG like 
|&lt;!--AROS--&gt;[ Eternal Lands (OpenGL)],
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Platform like 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/platform], [ Maze of Galious], [ Gish]*(openGL), [ Mega Mario], [https://archives.arosworld.org/?function=showfile&amp;file=game/platform/ thextech SMBX], [http://www.gianas-return.de/ Giana's Return], [http://www.sqrxz.de/ Sqrxz], [www.sqrxz2.de/ Sqrxz 2], [http://www.sqrxz.de/sqrxz-3/ Sqrxz 3], [http://www.sqrxz.de/sqrxz-4/ Sqrxz 4], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/platform Cave Story], [https://bszili.morphos.me/ Frogatto], [https://bszili.morphos.me/ OpenJazz], [https://archives.arosworld.org/?function=showfile&amp;file=game/platform/ pekkakana2], [ Aquaria], [https://archives.arosworld.org/?function=showfile&amp;file=game/platform/ sonic CD], [], 
|&lt;!--Amiga OS--&gt;[ Giana Sisters], [], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Puzzle [https://github.com/mariopartyrd/marioparty4/tree/port Party], [https://github.com/mdodis/OpenSolomonsKey OpenSolomonsKey], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/puzzle], [ Cubosphere (OpenGL)], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/puzzle Candy Crisis], [http://bszili.morphos.me/ TailTale], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Racing [ Trigger Rally], [ VDrift], [http://www.ultimatestunts.nl/index.php?page=2&amp;lang=en Ultimate Stunts], [http://maniadrive.raydium.org/ Mania Drive], [https://github.com/plowteam/donut Simpsons Hit and Run], [], 
|&lt;!--AROS--&gt;[ Super Tux Kart (OpenGL)], [http://www.dusabledanslherbe.eu/AROSPage/F1Spirit.30.html F1 Spirit (OpenGL)], [http://bszili.morphos.me/index.html MultiRacer], [https://bszili.morphos.me/ Speed Dreams], [https://archives.arosworld.org/?function=showfile&amp;file=game/driving/dethrace-0.10.1.x86_64-aros-v11.zip Carmageddon dethrace 64bit], [http://maniadrive.raydium.org/index.php?downloads=yes maniadrive like trackmania], 
|&lt;!--AmigaOS--&gt;
|&lt;!--AmigaOS4--&gt;[http://bszili.morphos.me/index.html Speed Dreams], 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=12], [http://bszili.morphos.me/index.html TORCS], 
|-
|&lt;!--Sub Menu--&gt;Games 1st first person DRPG [https://wiki.rpg.net/index.php/Open_Game_Systems Misc], [https://github.com/OpenEnroth/OpenEnroth OpenEnroth MM], []
|&lt;!--AROS--&gt;[https://github.com/BSzili/aros-stuff Arx Libertatis], [http://www.playfuljs.com/a-first-person-engine-in-265-lines/ js raycaster], [https://github.com/Dorthu/es6-crpg webgl], [https://github.com/sonountaleban/AmiShockolate System Shock], [], [], 
|&lt;!--AmigaOS--&gt;Phantasie, Faery Tale, Dungeon Master, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games 3rd third person action CRPG  [https://sourceforge.net/projects/sumwars/ Summoning Wars], [https://www.solarus-games.org/ Solarus], [https://wiki.rpg.net/index.php/Open_Game_Systems Misc], [https://github.com/alexbatalov/fallout1-ce fallout ce], [https://github.com/rwengine/openrw gta3], [https://github.com/gta-reversed/gta-reversed gta3 sa], [https://github.com/mrxenginner/reVC gta3 vc revc], [https://github.com/jakobharder/burntime/tree/main Burntime], 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/?function=showfile&amp;file=game/strategy/ fheroes2 homm2], [https://archives.arosworld.org/?function=showfile&amp;file=game/roleplaying/ breakhack], [https://archives.arosworld.org/?function=showfile&amp;file=game/roleplaying/ devilutionx diablo 1 hellfire], [https://archives.arosworld.org/?function=showfile&amp;file=game/roleplaying/ fallout 1], [https://archives.arosworld.org/?function=showfile&amp;file=game/strategy/ stratagus], [https://archives.arosworld.org/?function=showfile&amp;file=game/strategy/ hostile-takeover], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games isometric RPG [https://sourceforge.net/projects/sumwars/ Summoning Wars], [https://www.solarus-games.org/ Solarus], [https://wiki.rpg.net/index.php/Open_Game_Systems Misc], [https://github.com/topics/dungeon?l=javascript Dungeon], [], [https://github.com/clintbellanger/heroine-dusk JS Dusk], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/roleplaying nethack], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/roleplaying GemRB], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games card based RPG [https://github.com/open-duelyst/duelyst Duelyst], [], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games turn based tactics RPG [], [], [], [], [], [], 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=game/strategy UFO AI], [http://play.freeciv.org/ FreeCiv], [https://juen.in Aveterna online civ], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Strategy [http://rtsgus.org/ RTSgus], [http://stargus.sourceforge.net/ Stargus], [https://github.com/KD-lab-Open-Source/Perimeter Perimeter], [https://matty77.itch.io/conflict-3049 conflict-3049], [https://github.com/ZeroK-RTS/Zero-K Zero-K multi player rts lua], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/strategy MegaGlest (OpenGL)], [https://archives.arosworld.org/?function=showfile&amp;file=game/strategy/ signus], [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1443&amp;rowstart=140&amp;pid=12446#post_12446 Wargus warcraft 2 setup], 
|&lt;!--Amiga OS--&gt;[https://aminet.net/package/game/strat/OpenDUNE_RTG OpenDUNE_RTG src]
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=12]
|-
|&lt;!--Sub Menu--&gt;Games Rhythm, Beat, Step [], [], [https://clonehero.net/ clonehero], [https://github.com/MatteoGodzilla/Dj-Engine Dj-Engine], 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=game/misc Frets on Fire], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Shoot Em Ups [http://www.mhgames.org/oldies/formido/ Formido], [http://code.google.com/p/violetland/ Violetland], 
||&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=game/action Open Tyrian], [http://www.parallelrealities.co.uk/projects/starfighter.php Starfighter], [ Alien Blaster], [https://github.com/OpenFodder/openfodder OpenFodder], [https://archives.arosworld.org/?function=showfile&amp;file=game/action/ tbftss The Battle for the Solar System: the Pandora War]
|&lt;!--AmigaOS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.parallelrealities.co.uk/projects/starfighter.php Starfighter], [ The Battle for the Solar System: the Pandora War]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Simulations [http://scp.indiegames.us/ Freespace 2], [http://www.heptargon.de/gl-117/gl-117.html GL117], [http://code.google.com/p/corsix-th/ Theme Hospital], [http://code.google.com/p/freerct/ Rollercoaster Tycoon], [http://hedgewars.org/ Hedgewars], [https://github.com/raceintospace/raceintospace raceintospace], [https://github.com/Return-To-The-Roots RTTR Settlers 2], [https://github.com/OoliteProject/oolite oolite elite], [https://github.com/fesh0r/newkind newkind elite], [https://github.com/bohemiainteractive/cwr Arma Cold War Src], [https://github.com/endless-sky/endless-sky endless-sky], [https://github.com/pioneerspacesim/pioneer pioneer space command], 
|&lt;!--AROS--&gt;[https://github.com/tomaszstaniak/aros-micropolis micropolis]
|&lt;!--Amiga OS--&gt;SimCity, SimAnt, Sim Hospital, Theme Park, [https://github.com/angree/openttd_amiga_68k openttd amiga_68k], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=12]
|-
|&lt;!--Sub Menu--&gt;Games Life Sim [https://github.com/ACreTeam/forest Animal Crossing], [ ], [], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Horror [https://github.com/Mikompilation/MikuPan Fatal Frame], [ ], [], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Sandbox Voxel Open World Exploration [https://github.com/ClassiCube/ Classicube],[http://www.michaelfogleman.com/craft/ Craft], [https://github.com/tothpaul/DelphiCraft DelphiCraft],[https://www.minetest.net/ Luanti formerly Minetest], [ infiniminer], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Battle Royale [https://bruh.io/ Play.Bruh.io], [https://www.coolmathgames.com/0-copter Copter Royale], [https://surviv.io/ Surviv.io], [https://nuggetroyale.io/#Ketchup Nugget Royale], [https://miniroyale2.io/ Miniroyale2.io], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Tower Defense [https://chriscourses.github.io/tower-defense/ HTML5], [https://github.com/SBardak/Tower-Defense-Game TD C++], [https://github.com/bdoms/love_defense LUA and LOVE], [https://github.com/HyOsori/Osori-WebGame HTML5], [https://github.com/PascalCorpsman/ConfigTD ConfigTD Pascal], [https://github.com/GloriousEggroll/wine-ge-custom Wine], []
|&lt;!--AROS--&gt;[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1443&amp;rowstart=180&amp;pid=12871#post_12871 Plants vs Zombies PvZ], 
|&lt;!--Amiga OS--&gt;[https://github.com/boingball/miggy-tower-defense miggy-tower-defense], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Visual Novel Engines [https://github.com/diane1f0cd/VisualNovelTemplate Visual Novel Template], [https://github.com/Kirilllive/tuesday-js Tuesday JS], [https://github.com/tejasnayak25/vnsutra vnsutra], [https://github.com/weetabix-su/renpsp-dev RenPSP], [https://github.com/Galladite27/ONScripter-EN ONScripter-EN], [https://github.com/NathanGuilhot/VNES-Raylib https://github.com/NathanGuilhot/VNES VNES in Raylib], [https://www.renpy.org/latest.html renpy ren'py python based], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Virtual Reality VR [https://gitlab.com/madsbuvi/openmw openmw vr], [https://github.com/Team-Beef-Studios/BeefRaiderXR BeefRaiderXR], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Virtual Table Top VTT [ Roll20], [https://www.owlbear.rodeo/ owlbear rodeo], [], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Computer assisted TableTop TTRPG OSR [https://www.rpgsolo.com/play.php RPGSolo], [https://github.com/fpsvogel/solo-ttrpgs Solo TTRPG], [], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games 2D 3D Engines [https://github.com/fegennari/3DWorld 3DWorld], [https://github.com/GarageGames/Torque3D Torque3D], [https://github.com/gameplay3d/GamePlay GamePlay 3D],  [https://www.babylonjs.com/ BabylonJS ], [ Godot], [ Ogre], [ Crystal Space], [https://github.com/JacobHess03/ Dragon-Quest like], [https://github.com/bjornbytes/lovr Lua LOVE for 2D LOVR for 3D], [], 
|&lt;!--AROS--&gt;[https://www.arkhamdev.net/wiki.htm?id=agx Arkham Development antiryadgx 8.9 lts with register], [], 
|&lt;!--Amiga OS--&gt;[https://github.com/alpyre/Sevgi_Engine Sevgi Engine], [], [], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games C based game frameworks [https://github.com/orangeduck/Corange Corange], [https://github.com/scottcgi/Mojoc Mojoc], [https://orx-project.org/ Orx], [https://github.com/ioquake/ioq3 Quake 3], [https://www.mapeditor.org/ Tiled], [https://www.raylib.com/ 2d Raylib], [https://github.com/Rabios/awesome-raylib other raylib], [https://github.com/MrFrenik/gunslinger Gunslinger], [https://o3de.org/ o3d], [http://archives.aros-exec.org/index.php?function=browse&amp;cat=development/library GLFW], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=development/library Raylib 5], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games RPGMaker MV/MZ-compatible projects [https://github.com/Psychronic-Games/RPGReactor RPGReactor js],
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Virtual Pinball [https://github.com/vpinball/vpinball vpinball], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games unpack unarc [], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|}


==Application Guides==

[[#top|...to the top]]

===Web Browser===

OWB is now at version 2.0 (which got an engine refresh, from July 2015 to February 2019) and 3.0.

This latest version has a good support for many/most web sites, even YouTube web page now works. [https://www.bilibili.tv/en/search untested] 

This improved compatibility comes at the expense of higher RAM usage (now 1GB RAM is the absolute minimum). 

Also, keep in mind that the lack of a JIT (Just-In-Time) JS compiler on the 32 bit version, makes the web surfing a bit slow. 

Only the 64 bit version of OWB 2.0 will have JIT enabled, thus benefitting of more speed. There are tooltypes that can be added to the icon to provide further features JIT, MSE etc 


Certificates from [https://curl.se/docs/caextract.html ca certs], 


DNS tracking blocking with [https://easylist.to/easylist/easylist.txt easylist.txt] in PROGDIR:Conf before starting browser with enabled AdBlock [https://github.com/easylist/easylist/tree/master easylist], [https://gitlab.com/eyeo anti abp], [https://firebog.net/ big blocklist], [https://github.com/StevenBlack/hosts Steves], [], [], 

This can be enabled with OWB Odyssey with Windows -&gt; Content Blocking and Windows -&gt; Messages and enter 

 https://www.youtube.com/api/stats/ads*
 https://www.youtube.com/pagead/adview*
 https://www.youtube.com#@##player-ads*

into your custom filters 


Element blocker browser extension might be needed for [https://github.com/easylist/easylist/wiki/Youtube-Issues youtube], [ mid roll], [ pre roll], [ ],  


OWB speed is much better when running from RAM Disk, the best way is to add the below into your S:User-Startup which copies OWB drawer from Extras:Internet/OWB to RAM Disk: 

So add this :
&lt;pre&gt;
copy Extras:Internet/OWB Ram:OWB/ ALL CLONE &gt;NIL:
copy Extras:Internet/OWB.info Ram: &gt;NIL:
&lt;/pre&gt;
Open RAM Disk and open OWB drawer and double click on OWB icon so that the above icon tooltypes are activated 

Problems are that the copy time is long (around 20 seconds added in the background), but we can make it faster if we delete useless files from the OWB drawer (docs, …)
If you don’t copy the drawer back onto the HD, you won’t save your cache, cookies, passwords… So you need a script for it.

 copy Extras:Internet/Amelinium/#? Ram:Amelinium/ ALL CLONE &gt;NIL: 

Error messages 

SSL error &quot;cant verify with ca-certificates&quot;, check bios clock time date is correct 

Error 6, try checking networking prefs settings and Save / Use preferences again or a '''few times''' otherwise the network chipset may not be compatible with Aros 


[https://www.google.com/search?q=%s&amp;udm=14 Google search without AI overview] 
[ DuckDuckGo]
[ Ecosia]
[ Qwant]
[ Swisscows]
[ Mojeek]
[ Brave Search]
[ PreSearch]
[ Startpage] 


===E-mail===

 Emailinium is now available for IMAP and POP3 based accounts 

YAM does not support SSL and most mail providers now switched to encrypted SMTP/POP3 connections


====SimpleMail====

SimpleMail supports IMAP and appears to work with GMail, but it's never been reliable enough, it can crash with large mailboxes.

Please read more on this [http://www.freelists.org/list/simplemail-usr User list]


 GMail

Be sure to activate the pop3 usage in your gmail account setup / configuration first.

pop3: 
pop.gmail.com
Use SSL: Yes
Port: 995

smtp:
smtp.gmail.com (with authentication)
Use Authentication: Yes
Use SSL: Yes
Port: 465 or 587


 Hotmail/MSN/outlook/Microsoft Mail mid-2017, all outlook.com accounts will be migrated to Office 365 / Exchange

Most users are currently on POP which does not allow showing folders and many other features (technical limitations of POP3). With Microsoft IMAP you will get folders, sync read/unread, and show flags. You still won't get push though, as Microsoft has not turned on the IMAP Idle command as at Sept 2013.

If you want to try it, you need to first remove (you can't edit) your pop account (long-press the account on the accounts screen, delete account). Then set it up this way:

1. Email/Password
2. Manual
3. IMAP
4.

* Incoming: imap-mail.outlook.com, port 993, SSL/TLS should be checked
* Outgoing: smtp-mail.outlook.com, port 587, SSL/TLS should be checked
* POP server name pop-mail.outlook.com, port 995, POP encryption method SSL

 Yahoo  Mail

On April 24, 2002 Yahoo ceased to offer POP access to its free mail service. Introducing instead a yearly payment feature, allowing users POP3 and IMAP server support, along with such benefits as larger file attachment sizes and no adverts.

Sorry to see Yahoo leaving its users to cough up for the privilege of accessing their mail. Understandable, when competing against rivals such as Gmail and Hotmail who hold a large majority of users and were hacked in 2014 as well.


Incoming Mail (IMAP) Server

* Server - imap.mail.yahoo.com
* Port - 993
* Requires SSL - Yes

Outgoing Mail (SMTP) Server

* Server - smtp.mail.yahoo.com
* Port - 465 or 587
* Requires SSL - Yes
* Requires authentication - Yes

Your login info

* Email address - Your full email address (name@domain.com)
* Password - Your account's password
* Requires authentication - Yes


Note that you need to enable “Web &amp; POP Access” in your Yahoo Mail account to send and receive Yahoo Mail messages through any other email program.

You will have to enable “Allow your Yahoo Mail to be POPed” under “POP and Forwarding”, to send and receive Yahoo mails through any other email client.

Cannot be done since 2002 unless the customer pays Yahoo a subscription subs fee to have access to SMTP and POP3

* Set the POP server for incoming mails as pop.mail.yahoo.com. You will have to enable “SSL” and use 995 for Port.
* “Account Name or Login Name” – Your Yahoo Mail ID i.e. your email address without the domain “@yahoo.com”.
* “Email Address” – Your Yahoo Mail address i.e. your email address including the domain “@yahoo.com”. E.g. myname@yahoo.com
* “Password” – Your Yahoo Mail password.

Yahoo! Mail Plus users may have to set POP server as plus.pop.mail.yahoo.com and SMTP server as plus.smtp.mail.yahoo.com.

* Set the SMTP server for outgoing mails as smtp.mail.yahoo.com. You will also have to make sure that “SSL” is enabled and use 465 for port. you must also enable “authentication” for this to work.


====YAM Yet Another Mailer====

 YAM does not support SSL and most mail providers have now switched to encrypted SMTP/POP3 connections

This email client is POP3 only if the SSL library is available [http://www.freelists.org/list/yam YAM Freelists]

One of the downsides of using a POP3 mailer unfortunately - you have to set an option not to delete the mail if you want it left on the server. IMAP keeps all the emails on the server.

Possible issues

Sending mail issues is probably a matter of using your ISP's SMTP server, though it could also be an SSL issue.


getting a &quot;Couldn't initialise TLSv1 / SSL error

Use of on-line e-mail accounts with this email client is not possible as it lacks the OpenSSL AmiSSl v3 compatible library

 GMail 
Incoming Mail (POP3) Server - requires SSL: pop.gmail.com
Use SSL: Yes
Port: 995

Outgoing Mail (SMTP) Server - requires TLS: smtp.gmail.com (use authentication)
Use Authentication: Yes
Use STARTTLS: Yes (some clients call this SSL)
Port: 465 or 587

Account Name: your Gmail username (including '@gmail.com')
Email Address: your full Gmail email address (username@gmail.com)
Password: your Gmail password

Anyway, the SMTP is pop.gmail.com port 465 and it uses SSLLv3 Authentication. The POP3 settings are for the same server (pop.gmail.com), only on port 995 instead.


 Outlook.com access

&lt;pre &gt;
Outlook.com SMTP server address: smtp.live.com
Outlook.com SMTP user name: Your full Outlook.com email address (not an alias)
Outlook.com SMTP password: Your Outlook.com password
Outlook.com SMTP port: 587
Outlook.com SMTP TLS/SSL encryption required: yes 
&lt;/pre &gt;


 Yahoo  Mail

&lt;pre &gt;
“POP3 Server” – Set the POP server for incoming mails as pop.mail.yahoo.com. You will have to enable “SSL” and use 995 for Port.
“SMTP Server” – Set the SMTP server for outgoing mails as smtp.mail.yahoo.com. You will also have to make sure that “SSL” is enabled and use 465 for port. you must also enable “authentication” for this to work.
“Account Name or Login Name” – Your Yahoo Mail ID i.e. your email address without the domain “@yahoo.com”.
“Email Address” – Your Yahoo Mail address i.e. your email address including the domain “@yahoo.com”. E.g. myname@yahoo.com
“Password” – Your Yahoo Mail password.
&lt;/pre &gt;

Yahoo! Mail Plus users may have to set POP server as plus.pop.mail.yahoo.com and SMTP server as plus.smtp.mail.yahoo.com.

Note that you need to enable “Web &amp; POP Access” in your Yahoo Mail account to send and receive Yahoo Mail messages through any other email program.

You will have to enable “Allow your Yahoo Mail to be POPed” under “POP and Forwarding”, to send and receive Yahoo mails through any other email client.

Cannot be done since 2002 unless the customer pays Yahoo a monthly fee to have access to SMTP and POP3


 Microsoft Outlook Express Mail 

1. Get the files to your PC.
By whatever method get the files off your Amiga onto your PC. In the YAM folder you have a number of different folders, one for each of your folders in YAM. Inside that is a file usually some numbers such as 332423.283. YAM created a new file for every single email you received.

2. Open up a brand new Outlook Express. Just configure the account to use 127.0.0.1 as mail servers. It doesn't really matter. You will need to manually create any subfolders you used in YAM.

3. You will need to do a mass rename on all your email files from YAM. Just add a .eml to the end of it. Amazing how PCs still rely mostly on the file name so it knows what sort of file it is rather than just looking at it! There are a number of multiple renamers online to download and free too.

4. Go into each of your folders, inbox, sent items etc. And do a select all then drag the files into Outlook Express (to the relevant folder obviously) Amazingly the file format that YAM used is very compatible with .eml standard and viola your emails appear. With correct dates and working attachments.

5. If you want your email into Microsoft Outlook. Open that up and create a new profile and a new blank PST file. Then go into File Import and choose to import from Outlook Express. And the mail will go into there. And viola.. you have your old email from your Amiga in a more modern day format.


===FTP===

Magellan has a great FTP module. It allows transferring files from/to a FTP server over the Internet or the local network and, even if FTP is perceived as a &quot;thing of the past&quot;, its usability is all inside the client. The FTP thing has a nice side effect too, since every Icaros machine can be a FTP server as well, and our files can be easily transferred from an Icaros machine to another with a little configuration effort.

First of all, we need to know the 'server' IP address. Server is the Icaros machine with the file we are about to download on another Icaros machine, that we're going to call 'client'. To do that, move on the server machine and 1) run Prefs/Services to be sure &quot;FTP file transfer&quot; is enabled (if not, enable it and restart Icaros); 2) run a shell and enter this command:

ifconfig -a

Make a note of the IP address for the network interface used by the local area network. For cabled devices, it usually is net0:. Now go on the client machine and run Magellan:

Perform these actions: 1) click on FTP; 2) click on ADDRESS BOOK; 3) click on &quot;New&quot;. 
You can now add a new entry for your Icaros server machine:

1) Choose a name for your server, in order to spot it immediately in the address book. Enter the IP address you got before.

2) click on Custom Options:


1) go to Miscellaneous in the left menu;

2) Ensure &quot;Passive Transfers&quot; is NOT selected;

3) click on Use. We need to deactivate Passive Transfers because YAFS, the FTP server included in Icaros, only allows active transfers at the current stage. Now, we can finally connect to our new file source:


1) Look into the address book for the newly introduced server, be sure that name and IP address are right, and

2) click on Connect. A new lister with server's &quot;MyWorkspace&quot; contents will appear. You can now transfer files over the network choosing a destination among your local (client's) volumes.

Can be adapted to any FTP client on any platform of your choice, just be sure your client allows Active Transfers as well.


===IRC Internet Relay Chat===

Jabberwocky is ideal for one-to-one social media communication, use IRC if you require one to many. 

Just type a message in ''lowercase''' letters and it will be posted to all in the [ AROS irc channel]. Please do not use UPPER CASE as it is a sign of SHOUTING which is annoying.

Other things to type in - replace &lt;message&gt; with a line of text and &lt;nick&gt; with a person's name

&lt;pre&gt;
/help

/list

/who
/whois &lt;nick&gt;

/msg &lt;nick&gt; &lt;message&gt;

/query &lt;nick&gt; 
&lt;message&gt;s
/query

/away &lt;message&gt;
/away

/quit &lt;going away message&gt; 
&lt;/pre&gt;


[http://irchelp.org/irchelp/new2irc.html#smiley Intro guide here]. IRC Primer can be found here in [http://www.irchelp.org/irchelp/ircprimer.html html], [http://www.irchelp.org/irchelp/text/ircprimer.txt TXT], [http://www.kei.com/irc/IRCprimer1.1.ps PostScript].


Issue the command /me &lt;text&gt; where &lt;text&gt; is the text that should follow your nickname.
Example: /me slaps ajk around a bit with a large trout

/nick &lt;newNick&gt;

/nickserv register &lt;password&gt; &lt;email address&gt;

/ns instead of /nickserv, while others might need /msg nickserv

/nickserv identify &lt;password&gt;

Alternatives:
/ns identify &lt;password&gt;
/msg nickserv identify &lt;password&gt;


==== IRC WookieChat ====

WookieChat is the most complete internet client for communication across the IRC Network. WookieChat allows you to swap ideas and communicate in real-time, you can also exchange Files, Documents, Images and everything else using the application's DCC capabilities.


add smilies drawer/directory

 run wookiechat from the shell and set stack to 1000000 e.g. wookiechat stack 1000000

select a server / server window

* nickname 
* user name 
* real name - optional

Once you configure the client with your preferred screen name, you'll want to find a channel to talk in.


servers

* New Server - click on this to add / add extra - change details in section below this click box 
* New Group
* Delete Entry
* Connect to server
* connect in new tab
* perform on connect

Change details

* Servername - change text in this box to one of the below Server: 
* Port number - no need to change
* Server password
* Channel - add #channel from below 
* auto join - can click this 
* nick registration password,

Click Connect to server button above


&lt;pre&gt;
Server: irc.freenode.net
Channel: #aros
&lt;/pre&gt;

irc://irc.freenode.net/aros

&lt;pre&gt;
Server: chat.amigaworld.net 
Channel: #amigaworld or #amigans 
&lt;/pre&gt;

&lt;pre&gt;
On Sunday evenings USA time usually starting around 3PM EDT (1900 UTC)
Server:irc.superhosts.net
Channel #team*amiga  
&lt;/pre&gt;

&lt;pre&gt;
BitlBee and Minbif are IRCd-like gateways to multiple IM networks
Server: im.bitlbee.org 
Port 6667 
Seems to be most useful on WookieChat as you can be connected to several servers at once. One for Bitlbee and any messages that might come through that. One for your normal IRC chat server. 
&lt;/pre&gt;

[http://www.bitlbee.org/main.php/servers.html Other servers],

&lt;pre&gt;
#Amiga.org - irc.synirc.net eu.synirc.net dissonance.nl.eu.synirc.net (IPv6: 2002:5511:1356:0:216:17ff:fe84:68a) 
twilight.de.eu.synirc.net zero.dk.eu.synirc.net us.synirc.net avarice.az.us.synirc.net envy.il.us.synirc.net harpy.mi.us.synirc.net 
liberty.nj.us.synirc.net snowball.mo.us.synirc.net - Ports 6660-6669 7001 (SSL)
&lt;/pre&gt;

&lt;pre&gt;
Multiple server support
&quot;Perform on connect&quot; scripts and channel auto-joins
Automatic Nickserv login
Tabs for channels and private conversations
CTCP PING, TIME, VERSION, SOUND
Incoming and Outgoing DCC SEND file transfers
Colours for different events
Logging and automatic reloading of logs
mIRC colour code filters
Configurable timestamps
GUI for changing channel modes easily
Configurable highlight keywords
URL Grabber window
Optional outgoing swear word filter
Event sounds for tabs opening, highlighted words, and private messages
DCC CHAT support
Doubleclickable URL's
Support for multiple languages using LOCALE
Clone detection
Auto reconnection to Servers upon disconnection
Command aliases
Chat display can be toggled between AmIRC and mIRC style
Counter for Unread messages
Graphical nicklist and graphical smileys with a popup chooser
&lt;/pre&gt;


====IRC Aircos ====

Double click on Aircos icon in Extras:Networking/Apps/Aircos. It has been set up with a guest account for trial purposes. Though ideally, choose a nickname and password for frequent use of irc. 


====IRC and XMPP Jabberwocky====
 Servers are setup and close down at random 
You sign up to a server that someone else has setup and access chat services through them. 

The two ways to access chat from jabberwocky
&lt;pre &gt;
Jabberwocky -&gt; Server -&gt; XMPP -&gt; open and ad-free 
Jabberwocky -&gt; Server -&gt; Transports (Gateways) -&gt; Proprietary closed systems 
&lt;/pre &gt;

The Jabber.org service connects with all IM services that use XMPP, the open standard for instant messaging and presence over the Internet. The services we connect with include Google Talk (closed), Live Journal Talk, Nimbuzz, Ovi, and thousands more. However, you can not connect from Jabber.org to proprietary services like AIM, ICQ, MSN, Skype, or Yahoo because they don’t yet use XMPP components (XEP-0114) '''but''' you can use Jabber.com's servers and IM gateways (MSN, ICQ, Yahoo etc.) instead.

The best way to use jabberwocky is in conjunction with a public jabber server with '''transports''' to your favorite services, like gtalk, Facebook, yahoo, ICQ, AIM, etc.


You have to register with one of the servers, [https://list.jabber.at/ this list] or [http://www.jabberes.org/servers/ another list], [http://xmpp.net/ this security XMPP list],

Unfortunately jabberwocky can only connect to one server at a time so it is best to check what services each server offers. If you set it up with separate Facebook and google talk accounts, for example, sometimes you'll only get one or the other.

Jabberwocky open a window where the Jabber server part is typed in as well as your Nickname and Password.

Jabber ID (JID) identifies you to the server and other users.

Once registered the next step is to goto Jabberwocky's &quot;Windows&quot; menu and select the &quot;Agents&quot; option. The &quot;Agents List&quot; window will open.

Roster (contacts list)

[http://search.wensley.org.uk/ Chatrooms] (MUC) are available

File Transfer - can send and receive files through the Jabber service but not with other services like IRC, ICQ, AIM or Yahoo. All you need is an installed webbrowser and OpenURL.

Clickable URLs - The message window uses Mailtext.mcc and you can set a URL action in the MUI mailtext prefs like SYS:Utils/OpenURL %s NEWWIN.

There is no consistent Skype like (H.323 VoIP) video conferencing available over Jabber. The move from xmpp to Jingle should help but no support on any amiga-like systems at the moment. [http://aminet.net/package/dev/src/AmiPhoneSrc192 AmiPhone] and [http://www.lysator.liu.se/%28frame,faq,nobg,useframes%29/ahi/v4-site/ Speak Freely] was an early attempt voice only contact. SIP and Asterisk are other PBX options.


 Facebook

If you're using the XMPP transport provided by Facebook themselves, chat.facebook.com, it looks like they're now requiring SSL transport. This means jabberwocky method below will no longer work. The best thing to do is to create an ID on a public jabber server which has a Facebook gateway.

&lt;pre &gt;
1. launch jabberwocky
2. if the login window doesn't appear on launch, select 'account' from the jabberwocky menu
3. your jabber ID will be user@chat.facebook.com where user is your user ID
4. your password is your normal facebook password
5. to save this for next time, click the popup gadget next to the ID field

6. click the 'add' button
7. click the 'close' button
8. click the 'connect' button
&lt;/pre &gt;

you're done. you can also click the 'save as default account' button if you want. jabberwocky configured to auto-connect when launching the program, but you can configure as you like. there is amigaguide documentation included with jabberwocky.

[http://amigaworld.net/modules/newbb/viewtopic.php?topic_id=37085&amp;forum=32 Read more here]

for Facebook users, you can log-in directly to Facebook with jabberwocky. just sign in as @chat.facebook.com with your Facebook password as the password


 Twitter

For a few years, there has been added a twitter transport. Servers include [http://jabber.hot-chilli.net/ jabber.hot-chili.net],  and .

An [http://jabber.hot-chilli.net/tag/how-tos/ How-to]

:Read [http://jabber.hot-chilli.net/2010/05/09/twitter-transport-working/ more]

 Instagram 

no support at the moment best to use a web browser based client

 ICQ

The new version (beta) of StriCQ uses a newer ICQ protocol. Most of the ICQ Jabber Transports still use an older ICQ protocol. You can only talk one-way to StriCQ using the older Transports. Only the newer ICQv7 Transport lets you talk both ways to StriCQ. Look at the server lists in the first section to check.

Register on a Jabber server, e.g. this one works: http://www.jabber.de/
Then login into Jabberwocky with the following login data e.g. xxx@jabber.de / Password: xxx Now add your ICQ account under the window-&gt;Agents-&gt;&quot;Register&quot;. Now Jabberwocky connects via the Jabber.de server with your ICQ account.

 Yahoo Messenger

although yahoo! does not use xmpp protocol, you should be able to use the transport methods to gain access and post your replies

 MSN

early months of 2013 Microsoft will ditch MSN Messenger client and force everyone to use Skype...but MSN protocol and servers will keep working as usual for quite a long time....

Occasionally the Messenger servers have been experiencing problems signing in.  You may need to sign in at www.outlook.com and then try again.  It may also take multiple tries to sign in.  (This also affects you if you’re using Skype.)

You have to check each servers' Agents List to see what transports (MSN protocol, ICQ protocol, etc.) are supported or use the list address' provided in the section above. Then register with each transport (IRC, MSN, ICQ, etc.) to which you need access. After registering you can Connect to start chatting.

msn.jabber.com/registered should appear in the window.

From this [http://tech.dir.groups.yahoo.com/group/amiga-jabberwocky/message/1378 JW group] guide which  helps with this process in a clear, step by step procedure.

1. Sign up on MSN's site for a passport account. This typically involves getting a Hotmail address.

2. Log on to the Jabber server of your choice and do the following:

* Select the &quot;Windows/Agents&quot; menu option in Jabberwocky.
* Select the MSN Agent from the list presented by the server.
* Click the Register button to open a new window asking for:
**Username = passort account email address, typically your hotmail address.
**Nick = Screen name to be shown to anyone you add to your buddy list.
**Password = Password for your passport account/hotmail address.
* Click the Register button at the bottom of the new window.

3. If all goes well, you will see the MSN Gateway added to your buddy list. If not, repeat part 2 on another server. Some servers may show MSN in their list of available agents, but have not updated their software for the latest protocols used by MSN.

4. Once you are registered, you can now add people to your buddy list. Note that you need to include the '''msn.''' ahead of the servername so that it knows what gateway agent to use. Some servers may use a slight variation and require '''msg.gate.''' before the server name, so try both to see what works.

If my friend's msn was amiga@hotmail.co.uk and my jabber server was @jabber.meta.net.nz..
then amiga'''%'''hotmail.com@'''msn.'''jabber.meta.net.nz

or another the trick to import MSN contacts is that you don't type the hotmail URL but the passport URL... e.g. Instead of: goodvibe%hotmail.com@msn.jabber.com  You type: goodvibe%passport.com@msn.jabber.com 
And the thing about importing contacts I'm afraid you'll have to do it by hand, one at the time...

 Google Talk

any XMPP server will work, but you have to add your contacts manually. a google talk user is typically either @gmail.com or @talk.google.com. a true gtalk transport is nice because it brings your contacts to you and (can) also support file transfers to/from google talk users.

implement Jingle a set of extensions to the IETF's Extensible Messaging and Presence Protocol (XMPP)

support ended early 2014 as Google moved to Google+ Hangouts which uses it own proprietary format


===Video Player MPlayer===

Many of the menu features (such as doubling) do not work with the current version of mplayer but using

4:3
 mplayer -vf scale=800:600 file.avi

16:9
 mplayer -vf scale=854:480 file.avi

if you want gui use;
 mplayer -gui 1 &lt;other params&gt; file.avi

&lt;pre &gt;
stack 1000000

; using AspireOS 1.xx 
; copy FROM SYS:Extras/Multimedia/MPlayer/ TO RAM:MPlayer ALL CLONE &gt; Nil:

; using Icaros Desktop 1.x 
; copy FROM SYS:Tools/MPlayer/ TO RAM:MPlayer ALL CLONE &gt; Nil:

; using Icaros Desktop 2.x 
; copy FROM SYS:Utilities/MPlayer/ TO RAM:MPlayer ALL CLONE &gt; Nil:

cd RAM:MPlayer
run MPlayer -gui &gt; Nil:
;run MPlayer -gui -ao ahi_dev -playlist http://www.radio-paralax.de/listen.pls &gt; Nil: 
&lt;/pre &gt;

$ mplayer rtsp://127.0.0.1:554/sample_300kbit.mp4


MPlayer supports multicast streaming, and rtp/rtsp protocols (it might require [http://www.live555.com/openRTSP/ live555 library] to work with some streams). But you might have to build it where it's disabled. Also, multicast won't work with some AmiTCP-likes. MIAMI supported it, though.

AROS supports IPv4 (old but works) and this includes the needed address space for RTP.

If you mean multicast via RTP - mplayer handles it. You can even force UDP over TCP

-rtsp-stream-over-tcp

If the rtsp Real Time Streaming Protocol  server needs authentification:

-user -passwd


MPlayer - Menu - Open Playlist and load already downloaded .pls or .m3u file - auto starts around 4 percent cache

MPlayer - Menu - Open Stream and copy one of the .pls lines below into space allowed, press OK and press play button on main gui interface


Old 8bit 16bit remixes chip tune game music 
 
http://www.radio-paralax.de/listen.pls 

http://scenesat.com/

http://www.shoutcast.com/radio/Amiga

http://www.theoldcomputer.com/retro_radio/RetroRadio_Main.htm

http://www.kohina.com/

http://www.remix64.com/

http://retrogamer.net/forum/

http://retroasylum.podomatic.com/rss2.xml

http://retrogamesquad.com/

http://www.retronauts.com/

http://monsterfeet.com/noquarter/

http://www.retrogamingradio.com/

http://www.radiofeeds.co.uk/mp3.asp


[[#top|...to the top]]

====ZunePaint==== 

simplified typical workflow

* importing and organizing and photo management
* making global and regional local correction(s) - recalculation is necessary after each adjustment as it is not in real-time 
* exporting your images in the best format available with the preservation of metadata


Whilst achieving 80% of a great photo with just a filter, the remaining 20% comes from a manual fine-tuning of specific image attributes.


For photojournalism, documentary, and event coverage, minimal touching is recommended. Stick to Camera Raw for such shots, and limit changes to level adjustment, sharpness, noise reduction, and white balance correction.

For fashion or portrait shoots, a large amount of adjustment is allowed and usually ends up far from the original. Skin smoothing, blemish removal, eye touch-ups, etc. are common.  Might alter the background a bit to emphasize the subject.

Product photography usually requires a lot of sharpening, spot removal, and focus stacking.

For landscape shots, best results are achieved by doing the maximum amount of preparation before/while taking the shot. No amount of processing can match timing, proper lighting, correct gear, optimal settings, etc. Excessive post-processing might give you a dramatic shot but best avoided in the long term.


* White Balance - Left Amiga or F12 and K and under &quot;Misc color effects&quot; tab with a pull down for White Balance - color temperature also known as AKA tint (movies) or tones (painting) - warm temp raise red reduce green blue - cool raise blue lower red green 
* Exposure - exposure compensation, highlight/shadow recovery
* Noise Reduction - during RAW development or using external software
* Lens Corrections - distortion, vignetting, chromatic aberrations
* Detail - capture sharpening and local contrast enhancement
* Contrast - black point, levels (sliders) and curves tools (F12 and K) 
* Framing - straighten () and crop (F12 and F) 
* Refinements - color adjustments and selective enhancements - Left Amiga or F12 and K for RGB and YUV histogram tabs - 
* Resizing - enlarge for a print or downsize for the web or email (F12 and D) 
* Output Sharpening - customized for your subject matter and print/screen size


White Balance - F12 and K

scan your image for a shade which was meant to be white (neutral with each RGB value being equal) like paper or plastic which is in the same light as the subject of the picture. Use the dropper tool to select this color, similar colours will shift and you will have selected the perfect white balance for your part of the image - for the whole picture make sure RAZ or CLR button at the bottom is pressed before applying to the image above.


Exposure correction

F12 and K - YUV Y luminosity - RGB extra red tint - move red curve slightly down and move blue green curves slightly up

Workflows in practice

* Undo - Right AROS key or F12 and Z 
* Redo - Right AROS key or F12 and R

First flatten your image (if necessary) and then do a rotation until the picture looks level. 
* Crop the picture. Click the selection button and drag a box over the area of the picture you want to keep. Press the crop button and the rest of the photo will be gone. 
* Adjust your saturation, exposure, hue levels, etc., (right AROS Key and K for color correction) until you are happy with the photo. Make sure you zoom in all of the way to 100% and look the photo over, zoom back out and move around. Look for obvious problems with the picture. 
* After coloring and exposure do a sharpen (Right AROS key and E for Convolution and select drop down option needed), e.g. set the matrix to 5x5 (roughly equivalent Amount to 60%) and set the Radius to 1.0. Click OK.


And save your picture


Implemented or would like to see for simplification and ease of use

basic filters (presets) like black and white, monochrome, edge detection (sobel), motion/gaussian blur, 
* negative, sepiatone, retro vintage, night vision, colour tint, color gradient, color temperature, glows, fire, lightning, lens flare, emboss, filmic, pixelate mezzotint, antialias, etc.

adjust / cosmetic tools such as crop, 
* reshaping tools, straighten, smear, smooth, perspective, liquify, bloat, pucker, push pixels in any direction, dispersion, transform like warp, blending with soft light, page-curl, whirl, ripple, fisheye, neon,  etc. 
* red eye fixing, blemish remover, skin smoothing, teeth whitener, make eyes look brighter, desaturate,

effects like oil paint, cartoon, pencil sketch, charcoal, noise/matrix like sharpen/unsharpen, (right AROS key with A for Artistic effects) 
* blend two image, gradient blend, masking blend, explode, implode, custom collage, surreal painting, comic book style, needlepoint, stained glass, watercolor, mosaic, stencil/outline, crayon, chalk, etc.

borders such as 
* dropshadow, rounded, blurred, color tint, picture frame, film strip polaroid, bevelled edge, etc.

brushes e.g.
* frost, smoke, etc.

and manual control of

fix lens issues including vignetting (darkening), color fringing and barrel distortion, and chromatic and geometric aberration -  lens and body profiles

perspective correction

levels - directly modify the levels of the tone-values of an image, by using sliders for highlights, midtones and shadows

curves -  Color Adjustment and Brightness/Contrast

color balance

one single color transparent (alpha channel (color information/selections) for masking and/or blending ) for backgrounds, etc.

Threshold indicates how much other colors will be considered mixture of the removed color and non-removed colors

decompose layer into a set of layers with each holding a different type of pattern that is visible within the image

any selection using any selecting tools like lasso tool, marquee tool etc. the selection will temporarily be save to alpha 
If you create your image without transparency then the Alpha channel is not present, but you can add later.

File formats like .psd (Photoshop file has layers, masks etc.  contains edited sensor data. The original sensor data is no longer available) .xcf .raw .hdr

Image Picture Formats
* low dynamic range (JPEG, PNG, TIFF 8-bit), 16-bit (PPM, TIFF), typically as a 16-bit TIFF in either ProPhoto or AdobeRGB colorspace -  TIFF files are also fairly universal – although, if they contain proprietary data, such as Photoshop Adjustment Layers or Smart Filters, then they can only be opened by Photoshop making them proprietary.
* linear high dynamic range (HDR) images (PFM, [http://www.openexr.com/ ILM .EXR], jpg, [http://aminet.net/util/dtype cr2] (canon tiff based), hdr, NEF, CRW, ARW, MRW, ORF, RAF (Fuji), PEF, DCR, SRF, ERF, DNG files are RAW converted to an Adobe proprietary format - a container that can embed the raw file as well as the information needed to open it) 
An old version of [http://archives.aros-exec.org/index.php?function=browse&amp;cat=graphics/convert dcraw]

There is no single RAW file format. Each camera manufacturer has one or more unique RAW formats. RAW files contain the brightness levels data captured by the camera sensor. This data cannot be modified. A second smaller file, separate XML file, or within a database with instructions for the RAW processor to change exposure, saturation etc. The extra data can be changed but the original sensor data is still there. RAW is technically least compatible.

A raw file is high-bit (usually 12 or 14 bits of information) but a camera-generated TIFF file will be usually converted by the camera (compressed, downsampled) to 8 bits. The raw file has no embedded color balance or color space, but the TIFF has both. These three things (smaller bit depth, embedded color balance, and embedded color space) make it so that the TIFF will lose quality more quickly with image adjustments than the raw file. The camera-generated TIFF image is much more like a camera processed JPEG than a raw file. A strong advantage goes to the raw file. The power of RAW files, such as the ability to set any color temperature non-destructively and will contain more tonal values.

The principle of preserving the maximum amount of information to as late as possible in the process. The final conversion - which will always effectively represent a &quot;downsampling&quot; - should prevent as much loss as possible.

Once you save it as TIFF, you throw away some of that data irretrievably. When saving in the lossy JPEG format, you get tremendous file size savings, but you've irreversibly thrown away a lot of image data. As long as you have the RAW file, original or otherwise, you have access to all of the image data as captured.

Keyboard equivalence with Photoshop(tm) would help 

File
PHOTOSHOP	SHORTCUT	GIMP
New	Ctrl+n	New
Open	Ctrl+o	Open
Close	Ctrl+w	Close
Save	Ctrl+s	Save
Save as	Shift+Ctrl+s	Save as
Revert	F12	Revert
Print	Ctrl+p	Print
Exit	Ctrl+q	Quit
 
Edit
PHOTOSHOP	SHORTCUT	GIMP
Undo/Redo (1 level)	Ctrl+z	Undo (Redo is Shift+Ctrl+z)
Cut	Ctrl+x	Cut
Copy	Ctrl+c	Copy
Paste	Ctrl+v	Paste
Paste Into	Shift+Ctrl+v	Paste Into
Fill with FG color	Alt+Backspace	Fill with FG color
Fill with BG color	Control+Backspace	Fill with BG color
 
Image/Colors
PHOTOSHOP	SHORTCUT	GIMP
Levels	Ctrl+l	Levels
Auto Contrast	Shift+Ctrl+Alt+l	Stretch Contrast (same?)
Curves	Ctrl+m	Curves
Color Balance	Ctrl+b	Color Balance
Hue/Saturation	Ctrl+u	Hue-Saturation
Desaturate	Shift+Ctrl+u	Desaturate
Invert	Ctrl+i	Invert
Default Colors	d	Default Colors
Switch Colors	x	Switch Colors
 
Layer
PHOTOSHOP	SHORTCUT	GIMP
New Layer	Shift+Ctrl+n	New Layer
Layer via Copy	Ctrl+j	Duplicate Layer
Bring (layer) to Front	Shift+Ctrl+]	Layer to Top
Send (layer) to Back	Shift+Ctrl+[	Layer to Bottom
Bring (layer) Forward	Ctrl+]	Raise Layer
Send (layer) Backward	Ctrl+[	Lower Layer
Select Top Layer	Shift+Alt+]	Select Top Layer
Select Bottom Layer	Shift+Alt+[	Select Bottom Layer
Select One Layer Forward	Alt+]	Select Previous Layer
Select One Layer Backward	Alt+[	Select Next Layer
Merge Down	Ctrl+e	Merge Down
Merge Visible	Shift+Ctrl+e	Merge Visible
Preserve Transparency	/	Keep Transparency
Cycle Modes Forwards	Shift+=	Next Layer Mode
Cycle Modes Backwards	Shift+-	Previous Layer Mode
 
Select
PHOTOSHOP	SHORTCUT	GIMP
Select All	Ctrl+a	Select All
Deselect	Ctrl+d	Select None
Inverse	Shift+Ctrl+i	Invert
Feather	Ctrl+Alt+d	Feather
 
View
PHOTOSHOP	SHORTCUT	GIMP
Zoom In	Ctrl+=	Zoom In
Zoom Out	Ctrl+-	Zoom Out
Fit on Screen	Ctrl+0	Zoom to Fit Window
Actual Pixels	Ctrl+Alt+0	Zoom 1:1
Show/Hide Extras	Ctrl+h	Toggle Show Selection (close enough?)
Show/Hide Guides	Ctrl+'	Toggle Show Guides
Show/Hide Grid	Ctrl+Alt+'	Toggle Show Grid
Show/Hide Rulers	Ctrl+r	Toggle Show Rulers
Snap	Ctrl+;	Snap to Guides
Scroll View Up	Page Up	Scroll Page Up
Scroll View Down	Page Down	Scroll Page Down
Scroll View Left	Ctrl+Page Up	Scroll Page Left
Scroll View Right	Ctrl+Page Down	Scroll Page Right
 
Window/Dialogs
PHOTOSHOP	SHORTCUT	GIMP
?	F5	Tools Dialog
Color Tab	F6	Colors Dialog
Layers Tab	F7	Layers Dialog
Info Tab	F8	Image Information
 
Tools
PHOTOSHOP	SHORTCUT	GIMP
Rectangular Marquee Tool	m	Rect Select Tool
Elliptical Marquee Tool	Shift+m	Ellipse Select Tool
 	*This is a toggle between 'Elliptical Marquee Tool' and 'Rectangular Marquee Tool' in Photoshop	 
Move Tool	v	Move Tool
Lasso Tool	l	Free Select Tool
Magic Wand Tool	w	Fuzzy Select Tool
Crop Tool	c	Crop &amp; Resize Tool
Airbrush Tool	j	Airbrush Tool
Paintbrush Tool	b	Paintbrush Tool
Clone Stamp Tool	s	Clone Stamp Tool
Eraser Tool	e	Eraser Tool
Gradient Tool	g	Blend Tool
Paint Bucket Tool	Shift+g	Bucket Fill Tool
 	*This is a toggle between 'Paint Bucket Tool' and 'Gradient Tool' in Photoshop	 
Blur Tool	r	Convolve Tool
Dodge Tool	o	DodgeBurn Tool
Type Tool	t	Text Tool
Pen Tool	p	Bezier Select Tool
Eye Dropper Tool	i	Color Picker Tool
Zoom Tool	z	Magnify Tool
Previous Brush	,	Previous Brush
Next Brush	.	Next Brush
First Brush	Shift+&lt;	First Brush
Last Brush	Shift+&gt;	Last Brush
Decrease Brush Size	[	Decrease Brush Size
Increase Brush Size	]	Increase Brush Size
Decrease Brush Hardness	{	Decrease Brush Hardness
Increase Brush Hardness	}	Increase Brush Hardness
 
Help
PHOTOSHOP	SHORTCUT	GIMP
Help	F1	Help
Context Help	Shift+F1	Context Help
 
Misc.
PHOTOSHOP	SHORTCUT	GIMP
Last Filter	Ctrl+f	Repeat Last Filter
?	Shift+Ctrl+f	Reshow Last Filter
Preferences	Ctrl+k	Preferences
Liquify	Shift+Ctrl+x	IWarp (close enough?)
Toggle Quick Mask	q	Toggle Quick Mask


Spotlights - triangle of white opaque shape

Cutting out and/or replacing unwanted background or features - select large areas with the selection option like the Magic Wand tool (aka Color Range) or the Lasso (quick and fast) with feather 2 to soften edge or the pen tool which adds points/lines/Bézier curves (better control but slower), hold down the shift button as you click to add extra points/areas of the subject matter to remove. Increase the tolerance to cover more areas. To subtract from your selection hold down alt as you're clicking. 
* Layer masks are a better way of working than Erase they clip (black hides/hidden white visible/reveal). Clone Stamp can be simulated by   and brushes for other areas. 
* Leave the fine details like hair, fur, etc. to later with lasso and the shift key to draw a line all the way around your subject. Gradient Mapping - Inverse - Mask. i.e. Refine your selected image with edge detection and using the radius and edge options / adjuster (increase/decrease contrast) so that you will capture more fine detail from the background allowing easier removal. 
Remove fringe/halo

saving image as png rather than jpg/jpeg to keep transparency background intact.


Implemented [http://colorizer.org/ colour model representations] [http://paulbourke.net/texture_colour/colourspace/ Mathematical approach] - Photo stills are spatially 2d (h and w), but are colorimetrically 3d (r g and b, or H L S, or Y U V etc.) as well. 
* RGB - split cubed mapped color model for photos and computer graphics hardware using the light spectrum (adding and subtracting) 
* YUV - Y-Lightness U-blue/yellow V-red/cyan (similar to YPbPr and YCbCr) used in the PAL, NTSC, and SECAM composite digital TV color [http://crewofone.com/2012/chroma-subsampling-and-transcoding/#comment-7299 video]


Histograms

White balanced (neutral) if the spike happens in the same place in each channel of the RGB graphs. If not, you're not balanced. 
If you have sky you'll see the blue channel further off to the right.

RGB is best one to change colours. These elements RGB is a 3-channel format containing data for Red, Green, and Blue in your photo scale between 0 and 255. The area in a picture that appears to be brighter/whiter contains more red color as compared to the area which is relatively darker. Similarly in the green channel the area that appears to be darker contains less amount of green color as compared to the area that appears to be brighter.  Similarly in the blue channel the area appears to be darker contains less amount of blue color as compared to the area that appears to be brighter. Brightness luminance histogram also matches the green histogram more than any other color - human eye interprets green better e.g. RGB rough ratio 15/55/30%

RGBA (RGB+A, A means alpha channel) .  The alpha channel is used for &quot;alpha compositing&quot;, which can mostly be associated as &quot;opacity&quot;.  AROS deals in RGB with two digits for every color (red, green, blue), in ARGB you have two additional hex digits for the alpha channel.

The shadows are represented by the left third of the graph.  The highlights are represented by the right third.  And the midtones are, of course, in the middle.  The higher the black peaks in the graph, the more pixels are concentrated in that tonal range (total black area). 
By moving the black endpoint, which identifies the shadows (darkness) and a white light endpoint (brightness) up and down either sides of the graph, colors are adjusted based on these points. 
By dragging the central one, can increased the midtones and control the contrast, raise shadows levels, clip or softly eliminate unsafe levels, alter gamma, etc... in a way that is much more precise and creative .


RGB Curves

* Move left endpoint (black point) up or right endpoint (white point) up brightens 
* Move left endpoint down or right endpoint down darkens

Color Curves

* Dragging up on the Red Curve increases the intensity of the reds in the image but 
* Dragging down on the Red Curve decreases the intensity of the reds and thus increases the apparent intensity of its complimentary color, cyan. Green’s complimentary color is magenta, and blue’s is yellow.
&lt;pre&gt;
 Red &lt;-&gt; Cyan
 Green &lt;-&gt;Magenta
 Blue &lt;-&gt;Yellow 
&lt;/pre&gt;

YUV Best option to analyse and pull out statistical elements of any picture (i.e.  separate luminance data from color data). The line in Y luma tone box represents the brightness of the image with the point in the bottom left been black, and the point in the top right as white.  A low-contrast image has a concentrated clump of values nearer to the center of the graph. By comparison, a high-contrast image has a wider distribution of values across the entire width of the Histogram.   A histogram that is skewed to the right would indicate a picture that is a bit overexposed because most of the color data is on the lighter side (increase exposure with higher value F), while a histogram with the curve on the left shows a picture that is underexposed. This is good information to have when using post-processing software because it shows you not only where the color data exists for a given picture, but also where any data has been clipped (extremes on edges of either side): that is, it does not exist and, therefore, cannot be edited.  By dragging the endpoints of the line and as well as the central one, can increased the dark/shadows, midtones and light/bright parts and control the contrast, raise shadows levels, clip or softly eliminate unsafe levels, alter gamma, etc... in a way that is much more precise and creative .

The U and V chroma parts show color difference components of the image. It’s useful for checking whether or not the overall chroma is too high, and also whether it’s being limited too much
Can be used to create a negative image but also 
With U (Cb), the higher value you are, the more you're on the blue primary color. If you go to the low values then you're on blue complementary color, i.e. yellow.
With V (Cr), this is the same principle but with Red and Cyan.
e.g. If you push U full blue and V full red, you get magenta. If you push U full yellow and V full Cyan then you get green.

YUV simultaneously adds to one side of the color equation while subtracting from the other.  
using YUV to do color correction can be very problematic because each curve alters the result of each other: the mutual influence between U and V often makes things tricky. You may also be careful in what you do to avoid the raise of noise (which happens very easily). Best results are obtained with little adjustments

sunset that looks uninspiring and needs some color pop especially for the rays over the hill, a subtle contrast raise while setting luma values back to the legal range without hard clipping.


====Lunapaint====

Pixel based drawing app with onion-skin animation function

 Blocking, Shading, Coloring, adding detail 

&lt;pre&gt;
b BRUSH
e ERASER

alt eyedropper 
v layer tool 

z ZOOM / MAGNIFY &lt; &gt; n 
spc panning 
m  marque 
q lasso 
w same color selection / region 
&lt;/pre&gt;

&lt;pre&gt;
, LM RM
v 
V
f  filter 
F 
.  size 

p 
,  pick color 
[] last / next color 
&lt;/pre&gt;


There is not much missing in Lunapaint to be as good as FlipBook and then you have to take into account that Flipbook is considered to be amongst the best and easiest to use animation software out there. Ok to be honest Flipbook has some nice features that require more heavy work but those aren't so much needed right away, things like camera effects, sound, smart fill, export to different movie file formats etc.

Tried Flipbook with my tablet and compared it to Luna. The feeling is the same when sketching. LunaPaint is very responsive/fluent to draw with. Just as Flipbook is, and that responsiveness is something its users have mentioned as one of the positive sides of said software.

 author was learning MUI. Some parts just have to be rewritten with proper MUI classes before new features can be added.

* add [Frame Add] / [Frame Del]
* whole animation feature is impossible to use. If you draw 2 color maybe but if you start coloring your cells then you get in trouble
* pickup the entire image as a brush, not just a selection ? And consequently remove the brush from memory when one doesn't need it anymore. can pick up a brush and put it onto a new image but cropping isn't possible, nor to load/save brushes.
* Undo is something I longed for ages in Lunapaint.
* to import into the current layer, other types of images (e.g. JPEG) besides RAW64.
* implement graphic tablet features support


**GENERAL DRAWING**

Miss it very much:
UNDO
ERASER
COLORPICKER - has to show on palette too which color got picked.
BACKGROUND COLOR -Possibility to select from &quot;New project screen&quot;

Miss it somewhat:
ICON for UNDO
ICON for ERASER
ICON for CLEAR SCREEN ( What can I say? I start over from scratch very often )
BRUSH - possibility to cut out as brush not just copy off image to brush

**ANIMATING**

Miss it very much:
NUMBER OF CELLS - Possibity to change total no. of cells during project
ANIM BRUSH - Possibility to pick up a selected part of cells into an animbrush

Miss it somewhat:
ADD/REMOVE FRAMES: Add/remove single frame

In general LunaPaint is really well done and it feels like a new DeluxePaint version. It works with my tablet. Sure there's much missing of course but things can always be added over time. So there is great potential in LunaPaint that's for sure. Animations could be made in it and maybe put together in QuickVideo, saving in .gif or .mng etc some day.


LAYERS
-Layers names don't get saved globally in animation frames
-Layers order don't change globally in an animation (perhaps as default?).

EXPORTING IMAGES
-Exporting frames to JPG/PNG gives problems with colors. (wrong colors. See my animatiopn --&gt; My robot was blue now it's &quot;gold&quot; ) I think this only happens if you have layers.
-Trying to flatten the layers before export doesn't work if you have animation frames only the one you have visible will flatten properly all other frames are destroyed. (Only one of the layers are visible on them)
-Exporting images filenames should be for example e.g. file0001, file0002...file0010 instead as of now file1, file2...file10

LOAD/SAVE (Preferences)
-Make a setting for the default &quot;Work&quot; folder.

* Destroyed colors if exported image/frame has layers 
* mystic color cycling of the selected color while stepping frames back/forth (annoying)

&lt;pre&gt;
Deluxe Paint II enhanced key shortcuts 
    NOTE: @ denotes the ALT key

    [Technique]

    F1  - Paint
    F2  - Single Colour
    F3  - Replace
    F4  - Smear
    F5  - Shade
    F6  - Cycle
    F7  - Smooth
     M  - Colour Cycle

    [Brush]

     B  - Restore
     O  - Outline
     h  - Halve brush size
     H  - Double brush size
     x  - Flip brush on X axis
     X  - Double brush size on X axis only
     y  - Flip on Y 
     Y  - Double on Y
     z  - Rotate brush 90 degrees
     Z  - Stretch

    [Stencil]

     `  - Stencil On

    [Miscellaneous]

    F9  - Info Bar
    F10 - Selection Bar
    @o  - Co-Ordinates
    @a  - Anti-alias
    @r  - Colourise
    @t  - Translucent
    TAB - Colour Cycle

    [Picture]

     L  - Load
     S  - Save
     j  - Page to Spare(Flip)
     J  - Page to Spare(Copy)
     V  - View Page
     Q  - Quit

    [General Keys]

     m  - Magnify
     &lt;  - Zoom In
     &gt;  - Zoom Out
     [  - Palette Colour Up
     ]  - Palette Colour Down
     (  - Palette Colour Left
     )  - Palette Colour Right
     ,  - Eye Dropper
     .  - Pixel / Brush Toggle
     /  - Symmetry
     |  - Co-Ordinates
    INS - Perspective Control
    +/- - Brush Size (Fine Control)
     w  - Unfilled Polygon
     W  - Filled Polygon
     e  - Unfilled Ellipse
     E  - Filled Ellipse
     r  - Unfilled Rectangle
     R  - Filled Rectangle
     t  - Type/text tool
     a  - Select Font
    u/U - Undo
     d  - Brush
     D  - Filled Non-Uniform Polygon
    f/F - Fill Options
    g/G - Grid
    h/H - Brush Size (Coarse Control)
     K  - Clear
     c  - Unfilled Circle
     C  - Filled Circle
     v  - Line
     b  - Scissor Select and Toggle
     B  - Brush
    {,} - Toggle between two background colours
&lt;/pre&gt;

====Lodepaint====

Pixel based painting artwork app

====Grafx2====

Pixel based painting artwork app aesprite like 

[https://www.youtube.com/watch?v=59Y6OTzNrhk aesprite workflow keys and tablet use], [], 


====Vector Graphics ZuneFIG====

Vector Image Editing of files .svg .ps .eps


*Objects - raise lower rotate flip aligning snapping 
*Path - unify subtract intersect exclude divide 
*Colour - fill stroke 
*Stroke - size 
*Brushes - 
*Layers - 
*Effects - gaussian bevels glows shadows 
*Text    - 
*Transform - 


 AmiFIG ([http://epb.lbl.gov/xfig/frm_introduction.html xfig manual]) 

[[File:MyScreen.png|thumb|left|alt=Showing all Windows open in AmiFIG.|All windows available to AmiFIG.]]

for drawing simple to intermediate vector graphic images for scientific and technical uses and for illustration purposes for those with talent

;Menu options
* Load - fig format but import(s) SVG
* Save - fig format but export(s) eps, ps, pdf, svg and png
* PAN = Ctrl + Arrow keys 
* Deselect all points

There is no selected object until you apply the tool, and the selected object is not highlighted.

;Metrics - to set up page and styles - first window to open on new drawings

;Tools - Drawing Primitives - set Attributes window first before clicking any Tools button(s) 
* Shapes - circles, ellipses, arcs, splines, boxes,  polygon 
* Lines - polylines
* Text &quot;T&quot; button 
* Photos - bitmaps
* Compound - Glue, Break, Scale 
* POINTs - Move, Add, Remove 
* Objects - Move, Copy, Delete, Mirror, Rotate, Paste 
use right mouse button to stop extra lines, shapes being formed and the left mouse to select/deselect tools button(s)
* Rotate - moves in 90 degree turns centered on clicked POINT of a polygon or square

;Attributes which provide change(s) to the above primitives 
* Color
* Line Width
* Line Style
* arrowheads

;Modes 
Choose from freehand, charts, figures, magnet, etc.

;Library - allows .fig clip-art to be stored 
* compound tools to add .fig(s) together

;FIG 3.2 [http://epb.lbl.gov/xfig/fig-format.html Format] as produced by xfig version 3.2.5 
&lt;pre&gt;
Landscape
Center
Inches
Letter 
100.00
Single
-2
1200 2
4 0 0 50 -1 0 12 0.0000 4 135 1050 1050 2475 This is a test.01
&lt;/pre&gt;

# change the text alignment within the textbox. I can choose left, center, or right aligned by either changing the integer in the second column from 0 (left) to 1 or 2 (center, or right). 
# The third integer in the row specifies fontcolor. For instance, 0 is black, but blue is 1 and Green3 is 13.
# The sixth integer in the bottom row specifies fontface. 0 is Times-Roman, but 16 is Helvetica (a MATLAB default).
# The seventh number is fontsize. 12 represents a 12pt fontsize. Changing the fontsize of an item really is as easy as changing that number to 20.
# The next number is the counter-clockwise angle of the text. Notice that I have changed the angle to .7854 (pi/4 rounded to four digits=45 degrees).
# twelfth number is the position according to the standard “x-axis” in Xfig units from the left. Note that 1200 Xfig units is equivalent to once inch.
# thirteenth number is the “y-position” from the top using the same unit convention as before.

* The nested text string is what you entered into the textbox.
* The “01″ present at the end of that line in the .fig file is the closing tag. For instance, a change to \100 appends a @ symbol at the end of the period of that sentence.

; Just to note there are no layers, no 3d functions, no shading, no transparency, no animation


[[#top|...to the top]]

===Audio===


# AHI uses linear panning/balance, which means that in the center, you will get -6dB. If an app uses panning, this is what you will get. Note that apps like Audio Evolution need panning, so they will have this problem.

# When using AHI Hifi modes, mixing is done in 32-bit and sent as 32-bit data to the driver. The Envy24HT driver uses that to output at 24-bit (always).

# For the Envy24/Envy24HT, I've made 16-bit and 24-bit inputs (called Line-in 16-bit, Line-in 24-bit etc.). There is unfortunately no app that can handle 24-bit recording.


====Music Mods====

Digital module (mods) trackers are music creation software using samples and sometimes soundfonts, audio plugins (VST, AU or RTAS), MIDI.

Generally, MODs are similar to MIDI in that they contain note on/off and other sequence messages that control the mod player. Unlike (most) midi files, however, they also contain sound samples that the sequence information actually plays. MOD files can have many channels (classic amiga mods have 4, corresponding to the inbuilt sound channels), but unlike MIDI, each channel can typically play only one note at once. However, since that note might be a sample of a chord, a drumloop or other complex sound, this is not as limiting as it sounds.

Like MIDI, notes will play indefinitely if they're not instructed to end. Most trackers record this information automatically if you play your music in live. If you're using manual note entry, you can enter a note-off command with a keyboard shortcut - usually Caps Lock.

In fact when considering file size MOD is not always the best option. Even a dummy song wastes few kilobytes for nothing when a simple SID tune could be few hundreds bytes and not bigger than 64kB. AHX is another small format, AHX tunes are never larger than 64kB excluding comments.

[https://www.youtube.com/watch?v=rXXsZfwgil Protrekkr] (previously aka [w:Juan_Antonio_Arguelles_Rius|NoiseTrekkr])

If Protrekkr does not start, please check if the Unit 0 has been setup in the AHI prefs and still not, go to the directory utilities/protrekkr and double click on the Protrekkr icon

*Sample
*Note - Effect 
*Track (column) - Pattern - Order

It all starts with the Sample which is used to create Note(s) in a Track (column of a tracker) 
The Note can be changed with an Effect.  A Track of Note(s) can be collected into a Pattern (section of a song) and these can be given Order to create the whole song.

Patience (notes have to be entered one at a time) or playing the bassline on a midi controller (faster - see midi section above).  Best approach is to wait until a melody popped into your head.

*Up-tempo means the track should be reasonably fast, but not super-fast. 
*Groovy and funky imply the track should have some sort of &quot;swing&quot; feel, with plenty of syncopation or off beat emphasis and a recognizable, melodic bass line. 
*Sweet and happy mean upbeat melodies, a major key and avoiding harsh sounds.
*Moody - minor key

First, create a quick bass sound, which is basically a sine wave, but can be hand drawn for a little more variance. It could also work for the melody part, too.

This is usually a bass guitar or some kind of synthesizer bass. The bass line is often forgotten by inexperienced composers, but it plays an important role in a musical piece. Together with the rhythm section the bass line forms the groove of a song. It's the glue between the rhythm section and the melodic layer of a song.

The drums are just pink noise samples, played at different frequencies to get a slightly different sound for the kick, snare, and hihats.

Instruments that fall into the rhythm category are bass drums, snares, hi-hats, toms, cymbals, congas, tambourines, shakers, etc. Any percussive instrument can be used to form part of the rhythm section.

The lead is the instrument that plays the main melody, on top of the chords. There are many instruments that can play a lead section, like a guitar, a piano, a saxophone or a flute. The list is almost endless. There is a lot of overlap with instruments that play chords. Often in one piece an instrument serves both roles. The lead melody is often played at a higher pitch than the chords.

Listened back to what was produced so far, and a counter-melody can be imagined, which can be added with a triangle wave.

To give the ends of phrases some life, you can add a solo part with a crunchy synth. By hitting random notes in the key of G, then edited a few of them.

For the climax of the song, filled out the texture with a gentle high-pitch pad… …and a grungy bass synth.


The arrow at A points at the pattern order list. As you see, the patterns don't have to be in numerical order. This song starts with pattern &quot;00&quot;, then pattern &quot;02&quot;, then &quot;03&quot;, then &quot;01&quot;, etcetera. Patterns may be repeated throughout a song.

The B arrow points at the song title. Below it are the global BPM and speed parameters. These determine the tempo of the song, unless the tempo is altered through effect commands during the song.

The C arrow points at the list of instruments. An instrument may consist of multiple samples. Which sample will be played depends on the note. This can be set in the Instrument Editing screen. Most instruments will consist of just one sample, though. The sample list for the selected instrument can be found under arrow D.

Here's a part of the main editing screen. This is where you put in actual notes. Up to 32 channels can be used, meaning 32 sounds can play simultaneously. The first six channels of pattern &quot;03&quot; at order &quot;02&quot; are shown here. The arrow at A points at the row number. The B arrow points at the note to play, in this case a C4. The column pointed at by the C arrow tells us which instrument is associated with that note, in this case instrument #1 &quot;Kick&quot;.

The column at D is used (mainly) for volume commands. In this case it is left empty which means the instrument should play at its default volume. You can see the volume column being used in channel #6.

The E column tells us which effect to use and any parameters for that effect. In this case it holds the &quot;F&quot; effect, which is a tempo command. The &quot;04&quot; means it should play at tempo 4 (a smaller number means faster).

Base pattern

When I create a new track I start with what I call the base pattern. It is worthwhile to spend some time polishing it as a lot of the ideas in the base pattern will be copied and used in other patterns. At least, that's how I work. Every musician will have his own way of working. In &quot;Wild Bunnies&quot; the base pattern is pattern &quot;03&quot; at order &quot;02&quot;.

In the section about selecting samples I talked about the four different categories of instruments: drums, bass, chords and leads. That's also how I usually go about making the base pattern. I start by making a drum pattern, then add a bass line, place some chords and top it off with a lead. This forms the base pattern from which the rest of the song will grow.


Drums

Here's a screenshot of the first four rows of the base pattern. I usually reserve the first four channels or so for the drum instruments. Right away there are a couple of tricks shown here. In the first channel the kick, or bass drum, plays some notes. Note the alternating F04 and F02 commands. The &quot;F&quot; command alters the tempo of the song and by quickly alternating the tempo; the song will get some kind of &quot;swing&quot; feel.

In the second channel the closed hi-hat plays a fairly simple pattern. Further down in the channel, not shown here, some open hi-hat notes are added for a bit of variation.

In the third and fourth channel the snare sample plays. The &quot;8&quot; command is for panning. One note is panned hard to the left and the other hard to the right. One sample is played a semitone lower than the other. This results in a cool flanging effect. It makes the snare stand out a little more in the mix.


Bass line

There are two different instruments used for the bass line. Instrument #6 is a pretty standard synthesized bass sound. Instrument #A sounds a bit like a slap bass when used with a quick fade out. By using two different instruments the bass line sounds a bit more ”human”. The volume command is used to cut off the notes. However, it is never set to zero. Setting the volume to a very small value will result in a reverb-like effect. This makes the song sound more &quot;live&quot;.

The bass line hints at the chords that will be played and the key the song will be in. In this case the key of the song is D-major, a positive and happy key.


Chords

The D major chords that are being played here are chords stabs; short sounds with a quick decay (fade out). Two different instruments (#8 and #9) are used to form the chords. These instruments are quite similar, but have a slightly different sound, panning and volume decay. Again, the reason for this is to make the sound more human. The volume command is used on some chords to simulate a delay, to achieve more of a live feel. The chords are placed off-beat making for a funky rhythm.


Lead

Finally the lead melody is added. The other instruments are invaluable in holding the track together, but the lead melody is usually what catches people's attention.

A lot of notes and commands are used here, but it looks more complex than it is. A stepwise ascending melody plays in channel 13. Channel 14 and 15 copy this melody, but play it a few rows later at a lower volume. This creates an echo effect. A bit of panning is used on the notes to create some stereo depth. Like with the bass line, instead of cutting off notes the volume is set to low values for a reverb effect. The &quot;461&quot; effect adds a little vibrato to the note, which sounds nice on sustained notes.

Those paying close attention may notice the instrument used here for the lead melody is the same as the one used for the bass line (#6 &quot;Square&quot;), except played two or three octaves higher. This instrument is a looped square wave sample. Each type of wave has its own quirks, but the square wave (shown below) is a really versatile wave form.

Song structure

Good, catchy songs are often carefully structured into sections, some of which are repeated throughout the song with small variations.

A typical pop-song structure is: Intro - Verse - Chorus - Verse - Chorus - Bridge - Chorus.

Other single sectional song structures are

&lt;pre&gt;
Strophic or AAA Song Form - oldest story telling with refrain (often title of the song) repeated in every verse section melody 
AABA Song Form - early popular, jazz and gospel fading during the 1960s 
AB or Verse/Chorus Song Form - songwriting format of choice for modern popular music since the 1960s 
Verse/Chorus/Bridge Song Form
ABAB Song Form
ABAC Song Form
ABCD Song Form
AAB 12-Bar Song Form - three four-bar lines or sub-sections 
8-Bar Song Form
16-Bar Song Form
Hybrid / Compound Song Forms
&lt;/pre&gt;

The most common building blocks are:

#INTRODUCTION(INTRO)
#VERSE
#REFRAIN
#PRE-CHORUS / RISE / CLIMB
#CHORUS
#BRIDGE
#MIDDLE EIGHT
#SOLO / INSTRUMENTAL BREAK
#COLLISION
#CODA / OUTRO
#AD LIB (OFTEN IN CODA / OUTRO)

The chorus usually has more energy than the verse and often has a memorable melody line. As the chorus is repeated the most often during the song, it will be the part that people will remember.

The bridge often marks a change of direction in the song. It is not uncommon to change keys in the bridge, or at least to use a different chord sequence. The bridge is used to build up tension towards the big finale, the last repetition of chorus.


 Playing

RCTRL:                           Play song from row 0.

LSHIFT + RCTRL:                  Play song from current row.

RALT:                            Play pattern from row 0.

LSHIFT + RALT:                   Play pattern from current row.

Left mouse on '&gt;':               Play song from row 0.

Right mouse on '&gt;':              Play song from current row.

Left mouse on '|&gt;':              Play pattern from row 0.

Right mouse on '|&gt;':             Play pattern from current row.

Left mouse on 'Edit/Record':     Edit mode on/off.

Right mouse on 'Edit/Record':    Record mode on/off.


 Editing 


LSHIFT + ESCAPE:                 Switch large patterns view on/off

TAB:                    Go to next track

LSHIFT + TAB:                    Go to prev. track

LCTRL + TAB:                    Go to next note in track

LCTRL + LSHIFT + TAB:           Go to prev. note in track

SPACE:                           Toggle Edit mode On &amp; Off

(Also stop if the song is being played)

SHIFT SPACE:                     Toggle Record mode On &amp; Off

(Wait for a key note to be pressed

or a midi in message to be received)

DOWN ARROW:                      1 Line down

UP ARROW:                        1 Line up

LEFT ARROW:                      1 Row left

RIGHT ARROW:                     1 Row right

PREV. PAGE:                      16 Arrows Up

NEXT PAGE:                       16 Arrows Down

HOME / END:                      Top left / Bottom right of pattern

LCTRL + HOME / END:              First / last track

F5, F6, F7, F8, F9:              Jump to 0, 1/4, 2/4, 3/4, 4/4 lines of the patterns

+ - (Numeric keypad):           Next / Previous pattern

LCTRL + LEFT / RIGHT:           Next / Previous pattern

LCTRL + LALT + LEFT / RIGHT:    Next / Previous position

LALT + LEFT / RIGHT:           Next / Previous instrument

LSHIFT + M:                      Toggle mute state of the current channel

LCTRL + LSHIFT + M:             Solo the current track / Unmute all

LSHIFT + F1 to F11:              Select a tab/panel

LCTRL + 1 to 4:                 Select a copy buffer


 Tracking 

1st and 2nd keys rows:           Upper octave row

3rd and 4th keys rows:           Lower octave row

RSHIFT:                          Insert a note off

/ and * (Numeric keypad)

or F1 F2:                        -1 or +1 octave

INSERT / BACKSPACE:              Insert or Delete a line in current track

or current selected block.

LSHIFT + INSERT / BACKSPACE:     Insert or Delete a line in current pattern

DELETE (NOT BACKSPACE):          Empty a column or a selected block.


 Blocks

(Blocks can also be selected with the mouse by holding the right button and scrolling the pattern with the mouse wheel).


LCTRL + A:          Select entire current track

LCTRL + LSHIFT + A: Select entire current pattern

LALT + A:          Select entire column note in a track

LALT + LSHIFT + A: Select all notes of a track

LCTRL + X:          Cut the selected block and copy it into the block-buffer

LCTRL + C:          Copy the selected block into the block-buffer

LCTRL + V:          Paste the data from the block buffer into the pattern

LCTRL + I:          Interpolate selected data from the first to the last row of a selection

LSHIFT + ARROWS

PREV. PAGE

NEXT PAGE: Select a block

LCTRL + R:          Randomize the select columns of a selection, works similar to CTRL + I (interpolating them)

LCTRL + U:          Transpose the note of a selection to 1 seminote higher

LCTRL + D:          Transpose the note of a selection to 1 seminote lower

LCTRL + LSHIFT + U: Transpose the note of a selection to 1 seminote higher (only for the current instrument)

LCTRL + LSHIFT + D: Transpose the note of a selection to 1 seminote lower  (only for the current instrument)

LCTRL + H:          Transpose the note of a selection to 1 octave higher

LCTRL + L:          Transpose the note of a selection to 1 octave lower

LCTRL + LSHIFT + H: Transpose the note of a selection to 1 octave higher (only for the current instrument)

LCTRL + LSHIFT + L: Transpose the note of a selection to 1 octave lower (only for the current instrument)

LCTRL + W:          Save the current selection into a file


 Misc 


LALT + ENTER:     Switch between full screen / windowed mode

LALT + F4:        Exit program (Windows only)

LCTRL + S:         Save current module

LSHIFT + S:         Switch top right panel to synths list

LSHIFT + I:         Switch top right panel to instruments list


&lt;pre&gt;
C-x   xh xx xx hhhh             Volume 
B-x   xh xx xx hhhh             Jump to 
A#x  xh xx xx hhhh hhhh   Slide 
F-x    xh xx xx hhhh            Tempo 
D-x   xh xx xx hhhh             Pattern Break 
G#x  xh xx xx hhhh
&lt;/pre&gt;

h Hex 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13

d Dec 01 02 03 04 05 06 07 08 09 10  11 12 13 14 15 16 17 18 19

The Set Volume command: C. Input a note, then move the cursor to the effects command column and type a C. Play the pattern, and you shouldn't be able to hear the note you placed the C by. This is because the effect parameters are 00. Change the two zeros to a 40(Hex)/64(Dec), depending on what your tracker uses. Play back the pattern again, and the note should come in at full volume.

The Position Jump command next. This is just a B followed by the position in the playing list that you want to jump to. One thing to remember is that the playing list always starts at 0, not 1. This command is usually in Hex.

Onto the volume slide command: A. This is slightly more complex (much more if you're using a newer tracker, if you want to achieve the results here, then set slides to Amiga, not linear), due to the fact it depends on the secondary tempo. For now set a secondary tempo of 06 (you can play around later), load a long or looped sample and input a note or two. A few rows after a note type in the effect command A. For the parameters use 0F. Play back the pattern, and you should notice that when the effect kicks in, the sample drops to a very low volume very quickly. Change the effect parameters to F0, and use a low volume command on the note. Play back the pattern, and when the slide kicks in the volume of the note should increase very quickly.
This because each part of the effect parameters for command A does a different thing. The first number slides the volume up, and the second slides it down. It's not recommended that you use both a volume up and volume down at the same time, due to the fact the tracker only looks for the first number that isn't set to 0. If you specify parameters of 8F, the tracker will see the 8, ignore the F, and slide the volume up. Using a slide up and down at same time just makes you look stupid. Don't do it...

The Set Tempo command: F, is pretty easy to understand. You simply specify the BPM (in Hex) that you want to change to. One important thing to note is that values of lower than 20 (Hex) sets the secondary tempo rather than the primary.

Another useful command is the Pattern Break: D. This will stop the playing of the current pattern and skip to the next one in the playing list. By using parameters of more than 00 you can also specify which line to begin playing from.

Command 3 is Portamento to Note. This slides the currently playing note to another note, at a specified speed. The slide then stops when it reaches the desired note. 
&lt;pre&gt;
   C-2 1 000 - Starts the note playing
   ---      000
   C-3    330 - Starts the slide to C-3 at a speed of 30.
   ---     300 - Continues the slide
   ---     300 - Continues the slide
&lt;/pre&gt;
Once the parameters have been set, the command can be input again without any parameters, and it'll still perform the same function unless you change the parameters. This memory function allows certain commands to function correctly, such as command 5, which is the Portamento to Note and Volume Slide command. Once command 3 has been set up command 5 will simply take the parameters from that and perform a Portamento to Note. Any parameters set up for command 5 itself simply perform a Volume Slide identical to command A at the same time as the Portamento to Note.

This memory function will only operate in the same channel where the original parameters were set up.
There are various other commands which perform two functions at once. They will be described as we come across them.

C-3  04  ..  ..  09  00 ---&gt; C-3  04  ..  ..  09  00

C-3  04  ..  ..  09  00 ---&gt; C-3  04  ..  ..  09  02

C-3  04  ..  ..  09  00 ---&gt; C-3  04  ..  ..  09  05

C-3  04  ..  ..  09  00 ---&gt; C-3  04  ..  ..  09  08

C-3  04  ..  ..  09  00 ---&gt; C-3  04  ..  ..  09  0A

C-3  04  ..  ..  09  00 ---&gt; C-3  04  ..  ..  09  0D

C-3  04  ..  ..  09  10 ---&gt; C-3  04  ..  ..  09  10

(You can also switch on the Slider Rec to On, and perform parameter-live-recording, such as cutoff transitions, resonance or panning tweaking, etc..)  Note: this command only works for volume/panning and fx datas columns.


The next command we'll look at is the Portamento up/down: 1 and 2. Command 1 slides the pitch up at a specified speed, and 2 slides it down. This command works in a similar way to the volume slide, in that it is dependent on the secondary tempo. Both these commands have a memory dependent on each other, if you set the slide to a speed of 3 with the 1 command, a 2 command with no parameters will use the speed of 3 from the 1 command, and vice versa.

Command 4 is Vibrato. Vibrato is basically rapid changes in pitch, just try it, and you'll see what I mean. Parameters are in the format of xy, where x is the speed of the slide, and y is the depth of the slide. One important point to remember is to keep your vibratos subtle and natural so a depth of 3 or less and a reasonably fast speed, around 8, is usually used. Setting the depth too high can make the part sound out of tune from the rest.
Following on from command 4 is command 6. This is the Vibrato and Volume Slide command, and it has a memory like command 5, which you already know how to use.

Command 7 is Tremolo. This is similar to vibrato. Rather than changing the pitch it slides the volume. The effect parameters are in exactly the same format.   vibrato effect (0x1dxy) x = speed y = depth (can't be used if arpeggio (0x1b) is turned on) 

&lt;pre&gt;
 C-7 00 .. .. 1B37 &lt;-  Turn Arpeggio effect on
  --- .. .. .. 0000
  --- .. .. .. 0000
  --- .. .. .. 0000
  --- .. .. .. 1B38 &lt;- Change datas
  --- .. .. .. 0000
  --- .. .. .. 0000
  --- .. .. .. 0000
  --- .. .. .. 1B00 &lt;- Turn it off
&lt;/pre&gt;

Command 9 is Sample Offset. This starts the playback of the sample from a different place than the start. The effect parameters specify the sample offset, but only very roughly. Say you have a sample which is 8765(Hex) bytes long, and you wanted it to play from position 4321(Hex). The effect parameter could only be as accurate as the 43 part, and it would ignore the 21.

Command B is the Playing List/Order Jump command. The parameters specify the position in the Playing List/Order to jump to. When used in conjunction with command D you can specify the position and the line to play from.

Command E is pretty complex, as it is used for a lot of different things, depending on what the first parameter is. Let's take a trip through each effect in order.
Command E0 controls the hardware filter on an Amiga, which, as a low pass filter, cuts off the highest frequencies being played back. There are very few players and trackers on other system that simulate this function, not that you should need to use it. The second parameter, if set to 1, turns on the filter. If set to 0, the filter gets turned off.

Commands E1/E2 are Fine Portamento Up/Down. Exactly the same functions as commands 1/2, except that they only slide the pitch by a very small amount. These commands have a memory the same as 1/2 as well.

Command E3 sets the Glissando control. If parameters are set to 1 then when using command 3, any sliding will only use the notes in between the original note and the note being slid to. This produces a somewhat jumpier slide than usual. The best way to understand is to try it out for yourself. Produce a slow slide with command 3, listen to it, and then try using E31.

Command E4 is the Set Vibrato Waveform control. This command controls how the vibrato command slides the pitch. Parameters are 0 - Sine, 1 - Ramp Down (Saw), 2 - Square. By adding 4 to the parameters, the waveform will not be restarted when a new note is played e.g. 5 - Sine without restart.

Command E5 sets the Fine Tune of the instrument being played, but only for the particular note being played. It will override the default Fine Tune for the instrument. The parameters range from 0 to F, with 0 being -8 and F being +8 Fine Tune. A parameter of 8 gives no Fine Tune. If you're using a newer tracker that supports more than -8 to +8 e.g. -128 to +128, these parameters will give a rough Fine Tune, accurate to the nearest 16.

Command E6 is the Jump Loop command. You mark the beginning of the part of a pattern that you want to loop with E60, and then specify with E6x the end of the loop, where x is the number of times you want it to loop.

Command E7 is the Set Tremolo Waveform control. This has exactly the same parameters as command E4, except that it works for Tremolo rather than Vibrato.

Command E9 is for Retriggering the note quickly. The parameter specifies the interval between the retrigs. Use a value of less than the current secondary tempo, or else the note will not get retrigged.

Command EA/B are for Fine Volume Slide Up/Down. Much the same as the normal Volume Slides, except that these are easier to control since they don't depend on the secondary tempo. The parameters specify the amount to slide by e.g. if you have a sample playing at a volume of 08 (Hex) then the effect EA1 will slide this volume to 09 (Hex). A subsequent effect of EB4 would slide this volume down to 05 (Hex).

Command EC is the Note Cut. This sets the volume of the currently playing note to 0 at a specified tick. The parameters should be lower than the secondary tempo or else the effect won't work.

Command ED is the Note Delay. This should be used at the same time as a note is to be played, and the parameters will specify the number of ticks to delay playing the note. Again, keep the parameters lower than the secondary tempo, or the note won't get played!

Command EE is the Pattern Delay. This delays the pattern for the amount of time it would take to play a certain number of rows. The parameters specify how many rows to delay for.

Command EF is the Funk Repeat command. Set the sample loop to 0-1000. When EFx is used, the loop will be moved to 1000- 2000, then to 2000-3000 etc. After 9000-10000 the loop is set back to 0- 1000. The speed of the loop &quot;movement&quot; is defined by x. E is two times as slow as F, D is three times as slow as F etc. EF0 will turn the Funk Repeat off and reset the loop (to 0-1000).

effects 0x41 and 0x42 to control the volumes of the 2 303 units

There is a dedicated panel for synth parameter editing with coherent sections (osc, filter modulation, routing, so on) the interface is much nicer, much better to navigate with customizable colors, the reverb is now customizable (10 delay lines), It accepts newer types of Waves (higher bit rates, at least 24). Has a replay routine.

It's pretty much your basic VA synth. The problem isn't with the sampler being to high it's the synth is tuned two octaves too low, but if you want your samples tuned down just set the base note down 2 octaves (in the instrument panel).

so the synth is basically divided into 3 sections from left to right: oscillators/envelopes, then filter and LFO's, and in the right column you have mod routings and global settings.

for the oscillator section you have two normal oscillators (sine, saw, square, noise), the second of which is tunable, the first one tunes with the key pressed. Attached to OSC 1 is a sub-oscillator, which is a sawtooth wave tuned one octave down. The phase modulation controls the point in the duty cycle at which the oscillator starts. The ADSR envelope sliders (grouped with oscs) are for modulation envelope 1 and 2 respectively. you can use the synth as a sampler by choosing the instrument at the top.

In the filter column, the filter settings are: 1 = lowpass, 2 = highpass, 3 = off. cutoff and resonance. For the LFOs they are LFO 1 and LFO 2, the ADSR sliders in those are for the LFO itself.

For the modulation routings you have ENV 1, LFO 1 for the first slider and ENV 2, LFO 2 for the second, you can cycle through the individual routings there, and you can route each modulation source to multiple destinations of course, which is another big plus for this synth. Finally the glide time is for portamento and master volume, well, the master volume... it can go quite loud.

The sequencer is changed too, It's more like the one in AXS if you've used that, where you can mute tracks to re-use patterns with variation.


&lt;pre&gt;
Support for the following modules formats:
669 (Composer 669, Unis 669), 
AMF (DSMI Advanced Module Format), 
AMF (ASYLUM Music Format V1.0), 
APUN (APlayer), DSM (DSIK internal format), 
FAR (Farandole Composer), 
GDM (General DigiMusic), 
IT (Impulse Tracker), 
IMF (Imago Orpheus), 
MOD (15 and 31 instruments), 
MED (OctaMED), 
MTM (MultiTracker Module editor), 
OKT (Amiga Oktalyzer), 
S3M (Scream Tracker 3), 
STM (Scream Tracker), 
STX (Scream Tracker Music Interface Kit), 
ULT (UltraTracker), 
UNI (MikMod), 
XM (FastTracker 2),
Mid (midi format via timidity)
&lt;/pre&gt;


Possible plugin options include [http://lv2plug.in/ LV2],


====Midi - Musical Instrument Digital Interface====

A midi file typically contains music that plays on up to 16 channels (as per the midi standard), but many notes can simultaneously play on each channel (depending on the limit of the midi hardware playing it).

'''Timidity'''

Although usually already installed, you can uncompress the [http://www.libsdl.org/projects/SDL_mixer/ timidity.tar.gz (14MB)] into a suitable drawer like below's SYS:Extras/Audio/ 
 assign timidity: SYS:Extras/Audio/timidity
added to SYSːs/User-Startup

'''WildMidi playback'''


'''Audio Evolution 4 (2003) 4.0.23 (from 2012)'''


*Sync Menu    - CAMD Receive, Send checked 
*Options Menu - MIDI Machine Control - Midi Bar Display - Select CAMD MIDI in / out - Midi Remote Setup 


MCB Master Control Bus 
*Sending a MIDI start-command and a Song Position Pointer, you can synchronize audio with an external MIDI sequencer (like B&amp;P). 
*B&amp;P Receive, start AE, add AudioEvolution.ptool in Bars&amp;Pipes track, press play / record in AE then press play in Pipes 
*CAMD Receive, receive MIDI start or continue commands via camd.library sync to AE 


*MIDI Machine Control
*Midi Bar Display 
*Select CAMD MIDI in / out
*Midi Remote Setup - open requester for external MIDI controllers to control app mixer and transport controls cc remotely 
 Channel   - mixer(vol, pan, mute, solo), eq, aux, fx, 
 Subgroup  - Volume, Mute, Solo 
 Transport - Start, End, Play, Stop, Record, Rewind, Forward 
 Misc      - Master vol., Bank Down, Bank up 


&lt;pre&gt;
q        - quit 

First 3 already opened when AE started 
F1       - timeline window
F2       - mixer 
F3       - control 
F4       - subgroups 
F5       - aux returns 
F6       - sample list 

i        - Load sample to use 

space    - start/stop play 
b        - reset time 0:00


s        - split mode 
r        - open recording window 
a        - automation edit mode with p panning, m mute and v volume 


[ / ]    - zoom in / out 
:        - previous track
*        - next track 

x c v f  - cut copy paste cross-fade 
g        - snap grid 


&lt;/pre&gt;


 '''[http://bnp.hansfaust.de/ Bars n Pipes sequencer]'''

 BarsnPipes debug ... in shell 

Menu (right mouse)  
*Song        - Songs load and save in .song format but option here to load/save Midi_Files .mid in FORMAT0 or FORMAT1 
*Track       - 
*Edit        -
*Tool        - 
*Timing      - SMTPE Synchronizing 
*Windows     - 
*Preferences - Multiple MIDI-in option 

Windows (some of these are usually already opened when Bars n Pipes starts up for the first time) 
*Workflow -&gt; Tracks, .... Song Construction, Time-line Scoring, Media Madness, Mix Maestro, 
*Control  -&gt; Transport (or mini one), Windows (which collects all the Windows icons together-shortcut), .... Toolbox, Accessories, Metronome, 

Once you have your windows placed on the screen that suits your workflow, Song -&gt; Save as Default will save the positions, colors, icons, etc as you'd like them 

If you need a particular setup of Tracks, Tools, Tempos etc, you save them all as a new song you can load each time 

Right mouse menu -&gt; Preferences -&gt; Environment... -&gt; ScreenMode  - Linkages for Synch (to Slave) usbmidi.out.0 and Send (Master) usbmidi.in.0 - Clock MTC 


'''Tracks'''

#Double-click on B&amp;P's icon. B&amp;P will then open with an empty Song. You can also double-click on a song icon to open a song in B&amp;P.
#Choose a track. The B&amp;P screen will contain a Tracks Window with a number of tracks shown as pipelines (Track 1, Track 2, etc...). To choose a track, simply click on the gray box to show an arrow-icon to highlight it. This icon show whether a track is chosen or not. To the right of the arrow-icon, you can see the icon for the midi-input. If you double-click on this icon you can change the MIDI-in setup.
#Choose Record for the track. To the right of the MIDI-input channel icon you can see a pipe. This leads to another clickable icon with that shows either P, R or M. This stands for Play, Record or Merge. To change the icon, simply click on it. If you choose P, this track can only play the track (you can't record anything). If you choose R, you can record what you play and it overwrites old stuff in the track. If you choose M, you merge new records with old stuff in the track. Choose R now to be able to make a record.
#Chose MIDI-channel. On the most right part of the track you can see an icon with a number in it. This is the MIDI-channel selector. Here you must choose a MIDI-channel that is available on your synthesizer/keyboard. If you choose General MIDI channel 10, most synthesizer will play drum sounds. To the left of this icon is the MIDI-output icon. Double-click on this icon to change the MIDI-output configuration.
#Start recording. The next step is to start recording. You must then find the control buttons (they look like buttons on a CD-player). To be able to make a record. you must click on the R icon. You can simply now press the play button (after you have pressed the R button) and play something on you keyboard. To playback your composition, press the Play button on the control panel.
#Edit track. To edit a track, you simply double click in the middle part of a track. You will then get a new window containing the track, where you can change what you have recorded using tools provided. Take also a look in the drop-down menus for more features.


Videos to help understand [https://www.youtube.com/watch?v=A6gVTX-9900 small intro], [https://www.youtube.com/watch?v=abq_rUTiSA4&amp;t=3s Overview], [https://www.youtube.com/watch?v=ixOVutKsYQo Workplace Setup CC PC Sysex], [https://www.youtube.com/watch?v=dDnJLYPaZTs Import Song], [https://www.youtube.com/watch?v=BC3kkzPLkv4 Tempo Mapping], [https://www.youtube.com/watch?v=sd23kqMYPDs ptool Arpeggi-8], [https://www.youtube.com/watch?v=LDJq-YxgwQg  PlayMidi Song], [https://www.youtube.com/watch?v=DY9Pu5P9TaU Amiga Midi], [https://www.youtube.com/watch?v=abq_rUTiSA4 Learning Amiga bars and Pipes], 

Groups like [https://groups.io/g/barsnpipes/topics this] could help 


'''Tracks window'''

* blue &quot;1 2 3 4 5 6 7 8 Group&quot; and transport tape deck VCR-type controls
* Flags 
* [http://theproblem.alco-rhythm.com/org/bp.html Track 1, Track2, to Track 16, on each Track there are many options that can be activated] 

Each Track has a 

*Left LHS  - Click in grey box to select what Track to work on, Midi-In ptool icon should be here (5pin plug icon), and many more from the Toolbox on the Input Pipeline 
*Middle    - (P, R, M) Play, Record, Merge/Multi before the sequencer line and a blue/red/yellow (Thru Mute Play) Tap 
*Right RHS - Output pipeline, can have icons placed uopn it with the final ptool icon(s) being the 5pin icon symbol for Midi-OUT 

Clogged pipelines may need Esc pressed several times 


'''Toolbox (tools affect the chosen pipeline)'''

After opening the Toolbox window you can add extra Tools (.ptool) for the pipelines like keyboard(virtual), midimonitor, quick patch, transpose, triad, (un)quantize, feedback in/out, velocity etc
 right mouse -&gt; Toolbox menu option -&gt; Install Tool... and navigate to Tool drawer (folder) and select requried .ptool 

Accompany B tool to get some sort of rythmic accompaniment, Rythm Section and Groove Quantize are examples of other tools that make use of rythms
[https://aminet.net/search?query=bars Bars &amp; Pipes pattern format .ptrn] for drawer (folder). Load from the Menu as Track or Group 


'''Accessories (affect the whole app)''' 

Accessories -&gt; Install... and goto the Accessories drawer for .paccess like adding ARexx scripting support 


'''Song Construction'''
&lt;pre&gt;
F1  Pencil
F2  Magic Wand
F3  Hand 
F4  Duplicator 
F5  Eraser 
F6  Toolpad 
F7  Bounding box 
F8  Lock to A-B-A 

A-B-A strip, section, edit flags, white boxes, 

&lt;/pre&gt;


Bars&amp;Pipes Professional offers three track formats; basic song tracks, linear tracks — which don't loop — and finally real‑time tracks. The difference between them is that both song and linear tracks respond to tempo changes, while real‑time tracks use absolute timing, always trigger at the same instant regardless of tempo alterations 

'''Tempo Map'''

F1  Pencil
F2  Magic Wand
F3  Hand 
F4  Eraser 
F5  Curve 
F6  Toolpad 


Compositions

Lyrics, Key, Rhythm, Time Signature 

'''Master Parameters'''

Key, Scale/Mode

'''Track Parameters'''

Dynamics 


'''Time-line Scoring'''


'''Media Madness'''


'''Mix Maestro'''


*ACCESSORIES         Allows the importation of other packages and additional modules 
*CLIPBOARD           Full cut, copy and paste operations, enabling user‑definable clips to be shared between tracks.
*INFORMATION         A complete rundown on the state of the current production and your machine.
*MASTER PARAMETERS   Enables global definition of time signatures, lyrics, scales, chords, dynamics and rhythm changes.
*MEDIA MADNESS       A complete multimedia sequencer which allows samples, stills, animation, etc 
*METRONOME           Tempo feedback via MIDI, internal Amiga audio and colour cycling — all three can be mixed and matched as required.
*MIX MAESTRO         Completely automated mixdown with control for both volume and pan. All fader alterations are memorised by the software 
*RECORD ACTIVATION   Complete specification of the data to be recorded/merged. Allows overdubbing of pitch‑bend, program changes, modulation etc
*SET FLAGS           Numeric positioning of location and edit flags in either SMPTE or musical time 
*SONG CONSTRUCTION   Large‑scale cut and paste of individual measures, verses or chorus, by means of bounding box and drag‑n‑drop mouse selections
*TEMPO MAP           Tempo change using a variety of linear and non‑linear transition curves 
*TEMPO PALETTE       Instant tempo changes courtesy of four user‑definable settings.
*TIMELINE SCORING    Sequencing of a selection of songs over a defined period — ideal for planning an entire set for a live performance.
*TOOLBOX             Selection screen for the hundreds of signal‑processing tools available 
*TRACKS              Opens the main track window to enable recording, editing and the use of tools.
*TRANSPORT           Main playback control window, which also provides access to user‑ defined flags, loop and punch‑in record modes.


Bars and Pipes Pro 2.5 is using internal 4-Byte IDs, to check which kind of data are currently processed.
Especially in all its files the IDs play an important role. The IDs are stored into the file in the same order they are laid out in the memory.

In a Bars 'N' Pipes file (no matter which kind) the ID &quot;NAME&quot; (saved as its ANSI-values) is stored on a big endian system (68k-computer) as &quot;NAME&quot;. On a little endian system (x86 PC computer) as &quot;EMAN&quot;.  The target is to make the AROS-BnP compatible to songs, which were stored on a 68k computer (AMIGA).

If possible, setting MIDI channels for Local Control for your keyboard 

http://www.fromwithin.com/liquidmidi/archive.shtml


MIDI files are essentially a stream of event data. An event can be many things, but typically &quot;note on&quot;, &quot;note off&quot;, &quot;program change&quot;, &quot;controller change&quot;, or messages that instruct a MIDI compatible synth how to play a given bit of music.

* Channel     - 1 to 16 -
* Messages    - PC presets, CC effects like delays, reverbs,  etc 
* Sequencing  - MIDI instruments, Drums, Sound design, 
* Recording   - 
* GUI         - Piano roll or Tracker, Staves and Notes 

MIDI events/messages like step entry e.g. Note On, Note Off 

MIDI events/messages like PB, PC, CC, Mono and Poly After-Touch, Sysex, etc 

MIDI sync - Midi Clocks (SPS Measures), Midi Time Code (h, m, s and frames) SMPTE 

Individual track editing with audition edits so easier to test any changes. Possible to stop track playback, mix clips from the right edit flag and scroll the display using arrow keys. 

Step entry, to extend a selected note hit the space bar and the note grows accordingly. Ability to cancel mouse‑driven edits by simply clicking the right mouse button — at which point everything snaps back into its original form. Lyrics can now be put in with syllable dividers, even across an entire measure or section. Autoranging when you open a edit window, the notes are automatically displayed — working from the lowest upwards. 

Flag editing, shift‑click on a flag immediately open the bounds window, ready for numeric input. Ability to cancel edits using the right‑hand mouse button, plus much improved Bounding Box operations.

Icons other than the BarsnPipes icon -&gt; PUBSCREEN=BarsnPipes (cannot choose modes higher than 8bit 256 colors)

Preferences -&gt; Menu in Tracks window - Send MIDI defaults OFF 

Prefs -&gt; Environment -&gt; screenmode (saved to BarsnPipes.prefs binary file) 

Customization -&gt; pics in gui drawer (folder) - 


Can save as .song files and .mid General Midi 

SMF is a “Standard Midi File”  ([http://www.music.mcgill.ca/~ich/classes/mumt306/StandardMIDIfileformat.html SMF0, SMF1 and SMF2]), [https://github.com/stump/libsmf libsmf], [https://github.com/markc/midicomp MIDIcomp], [https://github.com/MajicDesigns/MD_MIDIFile C++ src], [], [https://github.com/newdigate/midi-smf-reader Midi player], 

* SMF0        All MIDI data is stored in one track only, separated exclusively by the MIDI channel.
* SMF1        The MIDI data is stored in separate tracks/channels.
* SMF2 (rarely used) The MIDI data is stored in separate tracks, which are additionally wrapped in containers, so it's possible to have e.g. several tracks using the same MIDI channels.


Would it be possible to enrich Bars N’Pipes with software synth and sample support along with audio recording and mastering tools like in the named MAC or PC music sequencers?
On the classic AMIGA-OS this is not possible because of missing CPU-power. The hardware of the classic AMIGA is not further developed. So we must say (unfortunately) that those dreams can’t become reality

BarsnPipes is best used with external MIDI-equipment. This can be a keyboard or synthesizer with MIDI-connectors. 

&lt;pre&gt;
MIDI can control 16 channels 
There are USB-MIDI-Interfaces on the market with 16 independent MIDI-lines (multi-port), which can handle 16 MIDI devices independently – 16×16 = 256 independent MIDI-channels or instruments 
handle up to 16 different USB-MIDI-Interfaces (multi-device). That is: 16X16X16 = 4096 independent MIDI-channels – theoretically 
&lt;/pre&gt;

&lt;pre&gt;
Librarian MIDI SYStem EXplorer (sysex) - PatchEditor and used to be supplied as a separate program like PatchMeister but currently not at present 
It should support MIDI.library (PD), BlueRibbon.library (B&amp;P), TriplePlayPlus, and CAMD.library (DeluxeMusic) and 
MIDI information from a device's user manual and configure a custom interface to access parameters for all MIDI products connected to the system 
Supports ALL MIDI events and the Patch/Librarian data is stored in MIDI standard format 
Annette M.Crowling, Missing Link Software, Inc.
&lt;/pre&gt;


Composers
&lt;pre&gt;
[https://x.com/hirasawa/status/1403686519899054086 Susumu Hirasawa] 

&lt;/pre&gt;


&lt;pre&gt;
1988 Todor Fay and his wife Melissa Jordan Gray, who founded the Blue Ribbon Inc
1992 Bars&amp;Pipes Pro published 
November 2000, Todor Fay announcement to release the sourcecode of Bars&amp;Pipes Pro 2.5c beta
end of May 2001, the source of the main program and the sources of some tools and accessories were in a complete and compileable state 
end of October 2009 stop further development of BarsnPipes New for now on all supported systems and made freeware 
2013 Alfred Faust diagnosed with incureable illness, called „Myastenia gravis“ (weak muscles) 
&lt;/pre&gt;


 Protrekkr

How to use Midi In/Out in Protrekkr ?

First of all, midi in &amp; out capabilities of this program are rather limited.

# Go to Misc. Setup section and select a midi in or out device to use (ptk only supports one device at a time).
# Go to instrument section, and select a MIDI PRG (the default is N/A, which means no midi program selected).
# Go to track section and here you can assign a midi channel to each track of ptk.
# Play notes :]. Note off works. F'x' note cut command also works too, and note-volume command (speed) is supported.

Also, you can change midicontrollers in the tracker, using '90' in the panning row:

&lt;pre&gt;
    C-3 02 .. .. 0000....


    --- .. .. 90 xxyy.... &lt;&lt; This will set the value 
    --- .. .. .. 0000....    of the controller n.'xx' to 'yy' (both in hex)
    --- .. .. .. 0000....
&lt;/pre&gt;

So &quot;--- .. .. 90 2040....&quot; will set the controller number $20(32) to $40(64).

You will need the midi implementation table of your gear to know what you can change with midi controller messages.

 N.B. Not all MIDI devices are created equal!

Although the MIDI specification defines a large range of MIDI messages of various kinds, not every MIDI device is required to work in exactly the same way and respond to all the available messages and ways of working. For example, we don't expect a wind synthesiser to work in the same way as a home keyboard.

Some devices, the older ones perhaps, are only able to respond to a single channel. With some of those devices that channel can be altered from the default of 1 (probably) to another channel of the 16 possible.

Other devices, for instance monophonic synthesisers, are capable of producing just one note at a time, on one MIDI channel. Others can produce many notes spread across many channels.

Further devices can respond to, and transmit, &quot;breath controller&quot; data (MIDI controller number 2 (CC#2)) others may respond to the reception of CC#2 but not be able to create and to send it.

A controller keyboard may be capable of sending &quot;expression pedal&quot; data, but another device may not be capable of responding to that message.

Some devices just have the basic GM sound set. The &quot;voice&quot; or &quot;instrument&quot; is selected using a &quot;Program Change&quot; message on its own.

Other devices have a greater selection of voices, usually arranged in &quot;banks&quot;, and the choice of instrument is made by responding to &quot;Bank Select MSB&quot; (MIDI controller 0 (CC#0)), others use &quot;Bank Select LSB&quot; (MIDI controller number 32 (CC#32)), yet others use both MSB and LSB sent one after the other, all followed by the Program Change message. The detailed information about all the different voices will usually be available in a published MIDI Data List.


 MIDI Implementation Chart

But in the User Manual there is sometimes a summary of how the device works, in terms of MIDI, in the chart at the back of the manual, the MIDI Implementation Chart.

If you require two devices to work together you can compare the two implementation charts to see if they are &quot;compatible&quot;. In order to do this we will need to interpret that chart.

The chart is divided into four columns headed &quot;Function&quot;, &quot;Transmitted&quot; (or &quot;Tx&quot;), &quot;Received&quot; (or &quot;Rx&quot;), or more correctly &quot;Recognised&quot;, and finally, &quot;Remarks&quot;.

&lt;pre&gt;
The left hand column defines which MIDI functions are being described.
The 2nd column defines what the device in question is capable of transmitting to another device.
The 3rd column defines what the device is capable of responding to.
The 4th column is for explanations of the values contained within these previous two columns.
&lt;/pre&gt;

There should then be twelve sections, with possibly a thirteenth containing extra &quot;Notes&quot;. Finally there should be an explanation of the four MIDI &quot;modes&quot; and what the &quot;X&quot; and the &quot;O&quot; mean.
&lt;pre&gt;
Mode 1: Omni On, Poly; 
Mode 2: Omni On, Mono; 
Mode 3: Omni Off, Poly; 
Mode 4: Omni Off, Mono.
&lt;/pre&gt;
O means &quot;yes&quot; (implemented), X means &quot;no&quot; (not implemented).

Sometimes you will find a row of asterisks &quot;**************&quot;, these seem to indicate that the data is not applicable in this case. Seen in the transmitted field only (unless you've seen otherwise).

Lastly you may find against some entries an asterisk followed by a number e.g. *1, these will refer you to further information, often on a following page, giving more detail.

Basic Channel
But the very first set of boxes will tell us the &quot;Basic Channel(s)&quot; that the device sends or receives on. 
&quot;Default&quot; is what happens when the device is first turned on, &quot;changed&quot; is what a switch of some kind may allow the device to be set to. 
For many devices e.g. a GM sound module or a home keyboard, this would be 1-16 for both. That is it can handle sending and receiving on all MIDI channels.

On other devices, for example a synthesiser, it may by default only work on channel 1. But the keyboard could be &quot;split&quot; with the lower notes e.g. on channel 2. If the synth has an arppegiator, this may be able to be set to transmit and or receive on yet another channel.
So we might see the default as &quot;1&quot; but the changed as &quot;1-16&quot;.

Modes.
We need to understand Omni On and Off, and Mono and Poly, then we can decipher the four modes.

But first we need to understand that any of these four Mode messages can be sent to any MIDI channel. They don't necessarily apply to the whole device.

If we send an &quot;Omni On&quot; message (CC#125) to a MIDI channel of a device, we are, in effect, asking it to respond to e.g. a Note On / Off message pair, received on any of the sixteen channels. Sound strange? Read it again. Still strange? It certainly is. We normally want a MIDI channel to respond only to Note On / Off messages sent on that channel, not any other. In other words, &quot;Omni Off&quot;.

So &quot;Omni Off&quot; (CC#124) tells a channel of our MIDI device to respond only to messages sent on that MIDI channel.

&quot;Poly&quot; (CC#127) is for e.g. a channel of a polyphonic sound module, or a home keyboard, to be able to respond to many simultaneous Note On / Off message pairs at once and produce musical chords.

&quot;Mono&quot; (CC#126) allows us to set a channel to respond as if it were e.g. a flute or a trumpet, playing just one note at a time. If the device is capable of it, then the overlapping of notes will produce legato playing, that is the attack portion of the second note of two overlapping notes will be removed resulting in a &quot;smoother&quot; transition.

So a channel with a piano voice assigned to it will have Omni Off, Poly On (Mode 3), a channel with a saxophone voice assigned could be Omni Off, Mono On (Mode 4).

We call these combinations the four modes, 1 to 4, as defined above. 
Most modern devices will have their channels set to Mode 3 (Omni Off, Poly) but be switchable, on a per channel basis, to Mode 4 (Omni Off, Mono).

This second section of data will include first its default value i.e. upon device switch on. Then what Mode messages are acceptable, or X if none.

Finally, in the &quot;Altered&quot; field, how a Mode message that can't be implemented will be interpreted. Usually there will just be a row of asterisks effectively meaning nothing will be done if you try to switch to an unimplemented mode.

Note Number
&lt;pre&gt;
The next row will tell us which MIDI notes the device can send or receive, normally 0-127.
The second line, &quot;True Voice&quot; has the following in the MIDI specification: 
&quot;Range of received note numbers falling within the range of true notes produced by the instrument.&quot;
My interpretation is that, for instance, a MIDI piano may be capable of sending all MIDI notes (0 to 127) by transposition, but only responding to the 88 notes (21 to 108) of a real piano. 
&lt;/pre&gt;

Velocity
This will tell us whether the device we're looking at will handle note velocity, and what range from 1-127, or maybe just 64, it transmits or will recognise. So usually &quot;O&quot; plus a range or &quot;X&quot; for not implemented.

After touch
This may have one or two lines two it.
If a one liner the either &quot;O&quot; or &quot;X&quot;, yes or no.
If a two liner then it may include &quot;Keys&quot; or &quot;Poly&quot; and &quot;Channel&quot;.
This will show whether the device will respond to Polyphonic after touch or channel after touch or neither.

Pitch Bend
Again &quot;O&quot; for implemented, &quot;X&quot; for not implemented.
(Many stage pianos will have no pitch bend capability.)
It may also, in the notes section, state whether it will respond to the full 14 bits, or not, as usually encoded by the pitch bend wheel.

Control Change
This is likely to be the largest section of the chart.
It will list all those controllers, starting from CC#0, Bank Select MSB, which the device is capable of sending, and those that it will respond to using &quot;O&quot; or &quot;X&quot; respectively.
You will, almost certainly, get some further explanation of functionality in the remarks column, or in more detail elsewhere in the documentation.

Of course you will need to know what all the various controller numbers do. Lots of the official technical specifications can be found at the [www.midi.org/techspecs/ MMA], with the table of messages and control change [www.midi.org/techspecs/midimessages.php message numbers]

Program Change
Again &quot;O&quot; or &quot;X&quot; in the Transmitted or Recognised column to indicate whether or not the feature is implemented. In addition a range of numbers is shown, typically 0-127, to show what is available.
True # (number): &quot;The range of the program change numbers which correspond to the actual number of patches selected.&quot;

System Exclusive
Used to indicate whether or not the device can send or recognise System Exclusive messages. A short description is often given in the Remarks field followed by a detailed explanation elsewhere in the documentation.

System Common - These include the following:
&lt;pre&gt;
MIDI Time Code Quarter Frame messages (device synchronisation).
Song Position Pointer
Song Select
Tune Request
&lt;/pre&gt;
The section will indicate whether or not the device can send or respond to any of these messages.

System Real Time
These include the following:
&lt;pre&gt;
Timing Clock - often just written as &quot;Clock&quot;
Start
Stop
Continue
&lt;/pre&gt;
These three are usually just referred to as &quot;Commands&quot; and listed.
Again the section will indicate which, if any, of these messages the device can send or respond to.
&lt;pre&gt;
Aux. Messages
Again &quot;O&quot; or &quot;X&quot; for implemented or not.
Aux. = Auxiliary.
Active Sense = Active Sensing.
&lt;/pre&gt;
Often with an explanation of the action of the device.

Notes
The &quot;Notes&quot; section can contain any additional comments to clarify the particular implementation.

Some of the explanations have been drawn directly from the MMA MIDI 1.0 Detailed Specification.
And the detailed explanation of some of the functions will be found there, or in the General MIDI System Level 1 or General MIDI System Level 2 documents also published by the MMA.


 OFFICIAL MIDI SPECIFICATIONS

SUMMARY OF MIDI MESSAGES
Table 1 - Summary of MIDI Messages

The following table lists the major MIDI messages in numerical (binary) order (adapted from &quot;MIDI by the Numbers&quot; by D. Valenti, Electronic Musician 2/88, and updated by the MIDI Manufacturers Association.). This table is intended as an overview of MIDI, and is by no means complete.

WARNING! Details about implementing these messages can dramatically impact compatibility with other products. We strongly recommend consulting the official MIDI Specifications for additional information.

MIDI 1.0 Specification

Message Summary Channel Voice Messages [nnnn = 0-15 (MIDI Channel Number 1-16)]

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot;  |Status D7----D0 
! width=&quot;10%&quot;  |Data Byte(s) D7----D0 
! width=&quot;20%&quot;  |Description
|-
|&lt;!--Status--&gt;1000nnnn || &lt;!--Data--&gt;0kkkkkkk 0vvvvvvv || &lt;!--Description--&gt;Note Off event. 
This message is sent when a note is released (ended). (kkkkkkk) is the key (note) number. (vvvvvvv) is the velocity.
|-
|&lt;!--Status--&gt;1001nnnn || &lt;!--Data--&gt;0kkkkkkk 0vvvvvvv || &lt;!--Description--&gt;Note On event. 
This message is sent when a note is depressed (start). (kkkkkkk) is the key (note) number. (vvvvvvv) is the velocity.
|-
|&lt;!--Status--&gt;1010nnnn || &lt;!--Data--&gt;0kkkkkkk 0vvvvvvv || &lt;!--Description--&gt;Polyphonic Key Pressure (Aftertouch). 
This message is most often sent by pressing down on the key after it &quot;bottoms out&quot;. (kkkkkkk) is the key (note) number. (vvvvvvv) is the pressure value.
|-
|&lt;!--Status--&gt;1011nnnn || &lt;!--Data--&gt;0ccccccc 0vvvvvvv || &lt;!--Description--&gt;Control Change. 
This message is sent when a controller value changes. Controllers include devices such as pedals and levers. Controller numbers 120-127 are reserved as &quot;Channel Mode Messages&quot; (below). (ccccccc) is the controller number (0-119). (vvvvvvv) is the controller value (0-127).
|-
|&lt;!--Status--&gt;1100nnnn || &lt;!--Data--&gt;0ppppppp || &lt;!--Description--&gt;Program Change. This message sent when the patch number changes. (ppppppp) is the new program number.
|-
|&lt;!--Status--&gt;1101nnnn || &lt;!--Data--&gt;0vvvvvvv || &lt;!--Description--&gt;Channel Pressure (After-touch). This message is most often sent by pressing down on the key after it &quot;bottoms out&quot;. This message is different from polyphonic after-touch. Use this message to send the single greatest pressure value (of all the current depressed keys). (vvvvvvv) is the pressure value.
|-
|&lt;!--Status--&gt;1110nnnn || &lt;!--Data--&gt;0lllllll 0mmmmmmm || &lt;!--Description--&gt;Pitch Bend Change. This message is sent to indicate a change in the pitch bender (wheel or lever, typically). The pitch bender is measured by a fourteen bit value. Center (no pitch change) is 2000H. Sensitivity is a function of the receiver, but may be set using RPN 0. (lllllll) are the least significant 7 bits. (mmmmmmm) are the most significant 7 bits.
|}

Channel Mode Messages (See also Control Change, above)

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot;  |Status D7----D0 
! width=&quot;10%&quot;  |Data Byte(s) D7----D0 
! width=&quot;20%&quot;  |Description
|-
|&lt;!--Status--&gt;1011nnnn || &lt;!--Data--&gt;0ccccccc 0vvvvvvv || &lt;!--Description--&gt;Channel Mode Messages. 
This the same code as the Control Change (above), but implements Mode control and special message by using reserved controller numbers 120-127. The commands are:
*All Sound Off. When All Sound Off is received all oscillators will turn off, and their volume envelopes are set to zero as soon as possible c = 120, v = 0: All Sound Off
*Reset All Controllers. When Reset All Controllers is received, all controller values are reset to their default values. (See specific Recommended Practices for defaults) c = 121, v = x: Value must only be zero unless otherwise allowed in a specific Recommended Practice.
*Local Control. When Local Control is Off, all devices on a given channel will respond only to data received over MIDI. Played data, etc. will be ignored. Local Control On restores the functions of the normal controllers. 
c = 122, v = 0: Local Control Off
c = 122, v = 127: Local Control On
* All Notes Off. When an All Notes Off is received, all oscillators will turn off. 
c = 123, v = 0: All Notes Off (See text for description of actual mode commands.)
c = 124, v = 0: Omni Mode Off 
c = 125, v = 0: Omni Mode On 
c = 126, v = M: Mono Mode On (Poly Off) where M is the number of channels (Omni Off) or 0 (Omni On) 
c = 127, v = 0: Poly Mode On (Mono Off) (Note: These four messages also cause All Notes Off)
|}

System Common Messages

System Messages (0xF0)

The final status nybble is a “catch all” for data that doesn’t fit the other statuses. They all use the most significant nybble (4bits) of 0xF, with the least significant nybble indicating the specific category.

The messages are denoted when the MSB of the second nybble is 1. When that bit is a 0, the messages fall into two other subcategories.

System Common

If the MSB of the second second nybble (4 bits) is not set, this indicates a System Common message. Most of these are messages that include some additional data bytes.

System Common Messages
Type Status Byte   Number of Data Bytes      Usage 
&lt;pre&gt;
Time Code Quarter Frame	0xF1	1	Indicates timing using absolute time code, primarily for synthronization with video playback systems. A single location requires eight messages to send the location in an encoded hours:minutes:seconds:frames format*.
Song Position	0xF2	2	Instructs a sequencer to jump to a new position in the song. The data bytes form a 14-bit value that expresses the location as the number of sixteenth notes from the start of the song.
Song Select	0xF3	1	Instructs a sequencer to select a new song. The data byte indicates the song.
Undefined	0xF4	0	
Undefined	0xF5	0	
Tune Request	0xF6	0	Requests that the receiver retunes itself**.
&lt;/pre&gt;
*MIDI Time Code (MTC) is significantly complex. Please see the MIDI Specification
**While modern digital instruments are good at staying in tune, older analog synthesizers were prone to tuning drift. Some analog synthesizers had an automatic tuning operation that could be initiated with this command.


System Exclusive

If you’ve been keeping track, you’ll notice there are two status bytes not yet defined: 0xf0 and 0xf7. These are used by the System Exclusive message, often abbreviated at SysEx. SysEx provides a path to send arbitrary data over a MIDI connection. There is a group of predefined messages for complex data, like fine grained control of MIDI Time code machinery. SysEx is also used to send manufacturer defined data, such as patches, or even firmware updates.

System Exclusive messages are longer than other MIDI messages, and can be any length. The messages are of the following format:

0xF0, 0xID, 0xdd, ...... 0xF7
The message is bookended with distinct bytes.

It opens with the Start Of Exclusive (SOX) data byte, 0xF0.
The next one to three bytes after the start are an identifier.
Values from 0x01 to 0x7C are one-byte vendor IDs, assigned to manufacturers who were involved with MIDI at the beginning.
If the ID is 0x00, it’s a three-byte vendor ID - the next two bytes of the message are the value.
&lt;pre&gt;
ID 0x7D is a placeholder for non-commercial entities.
ID 0x7E indicates a predefined Non-realtime SysEx message.
ID 0x7F indicates a predefined Realtime SysEx message.
&lt;/pre&gt;
After the ID is the data payload, sent as a stream of bytes.
The transfer concludes with the End of Exclusive (EOX) byte, 0xF7.
The payload data must follow the guidelines for MIDI data bytes – the MSB must not be set, so only 7 bits per byte are actually usable. If the MSB is set, it falls into three possible scenarios.

An End of Exclusive byte marks the ordinary termination of the SysEx transfer.
System Real Time messages may occur within the transfer without interrupting it. The recipient should handle them independently of the SysEx transfer.
Other status bytes implicitly terminate the SysEx transfer and signal the start of new messages.
 Some inexpensive USB-to-MIDI interfaces aren’t capable of handling messages longer than four bytes.

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot;  |Status D7----D0 
! width=&quot;10%&quot;  |Data Byte(s) D7----D0 
! width=&quot;20%&quot;  |Description
|-
|&lt;!--Status--&gt;11110000 || &lt;!--Data--&gt;0iiiiiii [0iiiiiii 0iiiiiii]  0ddddddd  --- --- 0ddddddd 11110111 || &lt;!--Description--&gt;System Exclusive. 
This message type allows manufacturers to create their own messages (such as bulk dumps, patch parameters, and other non-spec data) and provides a mechanism for creating additional MIDI Specification messages. The Manufacturer's ID code (assigned by MMA or AMEI) is either 1 byte (0iiiiiii) or 3 bytes (0iiiiiii 0iiiiiii 0iiiiiii). Two of the 1 Byte IDs are reserved for extensions called Universal Exclusive Messages, which are not manufacturer-specific. If a device recognizes the ID code as its own (or as a supported Universal message) it will listen to the rest of the message (0ddddddd). Otherwise, the message will be ignored. (Note: Only Real-Time messages may be interleaved with a System Exclusive.)
|-
|&lt;!--Status--&gt;11110001 || &lt;!--Data--&gt;0nnndddd || &lt;!--Description--&gt;MIDI Time Code Quarter Frame.
nnn = Message Type
dddd = Values
|-
|&lt;!--Status--&gt;11110010 || &lt;!--Data--&gt;0lllllll 0mmmmmmm || &lt;!--Description--&gt;Song Position Pointer. 
This is an internal 14 bit register that holds the number of MIDI beats (1 beat= six MIDI clocks) since the start of the song. l is the LSB, m the MSB.
|-
|&lt;!--Status--&gt;11110011 || &lt;!--Data--&gt;0sssssss || &lt;!--Description--&gt;Song Select. 
The Song Select specifies which sequence or song is to be played.
|-
|&lt;!--Status--&gt;11110100 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Undefined. (Reserved)
|-
|&lt;!--Status--&gt;11110101 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Undefined. (Reserved)
|-
|&lt;!--Status--&gt;11110110 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Tune Request. Upon receiving a Tune Request, all analog synthesizers should tune their oscillators.
|-
|&lt;!--Status--&gt;11110111 || &lt;!--Data--&gt; || &lt;!--Description--&gt;End of Exclusive. Used to terminate a System Exclusive dump. 
|}


System Real-Time Messages

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot;  |Status D7----D0 
! width=&quot;10%&quot;  |Data Byte(s) D7----D0 
! width=&quot;20%&quot;  |Description
|-
|&lt;!--Status--&gt;11111000 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Timing Clock. Sent 24 times per quarter note when synchronization is required.
|-
|&lt;!--Status--&gt;11111001 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Undefined. (Reserved)
|-
|&lt;!--Status--&gt;11111010 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Start. Start the current sequence playing. (This message will be followed with Timing Clocks).
|-
|&lt;!--Status--&gt;11111011 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Continue. Continue at the point the sequence was Stopped.
|-
|&lt;!--Status--&gt;11111100 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Stop. Stop the current sequence.
|-
|&lt;!--Status--&gt;11111101 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Undefined. (Reserved)
|-
|&lt;!--Status--&gt;11111110 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Active Sensing. This message is intended to be sent repeatedly to tell the receiver that a connection is alive. Use of this message is optional. When initially received, the receiver will expect to receive another Active Sensing message each 300ms (max), and if it does not then it will assume that the connection has been terminated. At termination, the receiver will turn off all voices and return to normal (non- active sensing) operation. 
|-
|&lt;!--Status--&gt;11111111 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Reset. Reset all receivers in the system to power-up status. This should be used sparingly, preferably under manual control. In particular, it should not be sent on power-up.
|}


Advanced Messages

Polyphonic Pressure (0xA0) and Channel Pressure (0xD0)

Some MIDI controllers include a feature known as Aftertouch. While a key is being held down, the player can press harder on the key. The controller measures this, and converts it into MIDI messages.

Aftertouch comes in two flavors, with two different status messages.

The first flavor is polyphonic aftertouch, where every key on the controller is capable of sending its own independent pressure information. The messages are of the following format:
&lt;pre&gt;
0xnc, 0xkk, 0xpp
n is the status (0xA)
c is the channel nybble
kk is the key number (0 to 127)
pp is the pressure value (0 to 127)
&lt;/pre&gt;
Polyphonic aftertouch is an uncommon feature, usually found on premium quality instruments, because every key requires a separate pressure sensor, plus the circuitry to read them all.

Much more commonly found is channel aftertouch. Instead of needing a discrete sensor per key, it uses a single, larger sensor to measure pressure on all of the keys as a group. The messages omit the key number, leaving a two-byte format
&lt;pre&gt;
0xnc, 0xpp
n is the status (0xD)
c is the channel number
pp is the pressure value (0 to 127)
&lt;/pre&gt;

Pitch Bend (0xE0)

Many keyboards have a wheel or lever towards the left of the keys for pitch bend control. This control is usually spring-loaded, so it snaps back to the center of its range when released. This allows for both upward and downward bends.

Pitch Bend Wheel

The wheel sends pitch bend messages, of the format
&lt;pre&gt;
0xnc, 0xLL, 0xMM
n is the status (0xE)
c is the channel number
LL is the 7 least-significant bits of the value
MM is the 7 most-significant bits of the value
&lt;/pre&gt;
You’ll notice that the bender data is actually 14 bits long, transmitted as two 7-bit data bytes. This means that the recipient needs to reassemble those bytes using binary manipulation. 14 bits results in an overall range of 214, or 0 to 16,383. Because it defaults to the center of the range, the default value for the bender is halfway through that range, at 8192 (0x2000).

Control Change (0xB0)

In addition to pitch bend, MIDI has provisions for a wider range of expressive controls, sometimes known as continuous controllers, often abbreviated CC. These are transmitted by the remaining knobs and sliders on the keyboard controller shown below.


Continuous Controllers

These controls send the following message format:
&lt;pre&gt;
0xnc, 0xcc, 0xvv
n is the status (0xB)
c is the MIDI channel
cc is the controller number (0-127)
vv is the controller value (0-127)
&lt;/pre&gt;

Typically, the wheel next to the bender sends controller number one, assigned to modulation (or vibrato) depth. It is implemented by most instruments.

The remaining controller number assignments are another point of confusion. The MIDI specification was revised in version 2.0 to assign uses for many of the controllers. However, this implementation is not universal, and there are ranges of unassigned controllers.

On many modern MIDI devices, the controllers are assignable. On the controller keyboard shown in the photos, the various controls can be configured to transmit different controller numbers. Controller numbers can be mapped to particular parameters. Virtual synthesizers frequently allow the user to assign CCs to the on-screen controls. This is very flexible, but it might require configuration on both ends of the link and completely bypasses the assignments in the standard.


Program Change (0xC0)

Most synthesizers have patch storage memory, and can be told to change patches using the following command:
&lt;pre&gt;
0xnc, 0xpp
n is the status (0xc)
c is the channel
pp is the patch number (0-127)
&lt;/pre&gt;
This allows for 128 sounds to be selected, but modern instruments contain many more than 128 patches. Controller #0 is used as an additional layer of addressing, interpreted as a “bank select” command. Selecting a sound on such an instrument might involve two messages: a bank select controller message, then a program change.

Audio &amp; Midi are not synchronized, what I can do ?
Buy a commercial software package but there is a nasty trick to synchronize both. It's a bit hardcore but works for me:

 Simply put one line down to all midi notes on your pattern (use Insert key)
 and go to 'Misc. Setup', adjust the latency and just search a value
 that will make sound sync both audio/midi.

The stock Sin/Saw/Pulse and Rnd waveforms are too simple/common, is there a way to use something more complex/rich ?
You have to ability to redirect the waveforms of the instruments through the synth pipe by selecting the &quot;wav&quot; option for the oscillator you're using for this synth instrument, samples can be used as wavetables to replace the stock signals.


Sound banks like soundfont (sf2) or Kontakt2 are not supported at the moment


====DAW Audio Evolution 4====

Audio Evolution 4 gives you unsurpassed power for digital audio recording and editing on the Amiga. The latest release focusses on time-saving non-linear and non-destructive editing, as seen on other platforms. Besides editing, Audio Evolution 4 offers a wide range of realtime effects, including compression, noise gate, delays, reverb, chorus and 3-band EQ.

Whether you put them as inserts on a channel or use them as auxillaries, the effect parameters are realtime adjustable and can be fully automated. Together with all other mixing parameters, they can even be controlled remotely, using more ergonomic MIDI hardware.

Non-linear editing on the time line, including cut, copy, paste, move, split, trim and crossfade actions

The number of tracks per project(s) is unlimited .... AHI limits you to recording only two at a time. i.e. not on 8 track sound cards like the Juli@ or Phase 88.

sample file import is limited to 16bit AIFF (not AIFC, important distinction as some files from other sources can be AIFC with aiff file extension). and 16bit WAV (pcm only)


Most apps use the Music Unit only but a few apps also use Unit (0-3) instead or as well. 
* Set up AHI prefs so that microphone is available. (Input option near the bottom)


stereo++ allows the audio piece to be placed anywhere and the left-right adjusted to sound positionally right

hifi best for music playback if driver supports this option


Load 16bit .aif .aiff only sample(s) to use not AIFC which can have the same ending. AIFF stands for Audio Interchange File Format 

 sox recital.wav recital.aiff

 sox recital.wav −b 16 recital.aiff channels 1 rate 16k fade 3 norm
 sox input.wav        output.aiff bass −b 16 rate 48k

performs the same format translation, but also applies four effects (down-mix to one channel, sample rate change, fade-in, nomalize), and stores the result at a bit-depth of 16.

 rec −c 2 radio.aiff trim 0 30:00

records half an hour of stereo audio 

 play existing-file.wav


24bit PCM WAV or AIFF do not work 

*No stream format handling. So no way to pass on an AC3 encoded stream unmodified to the digital outputs through AHI.
*No master volume handling. Each application has to set its own volume. So each driver implements its own custom driver-mixer interface for handling master volumes, mute and preamps.
*Only one output stream. So all input gets mixed into one output.
*No automatic handling of output direction based on connected cables.
*No monitor input selection. Only monitor volume control. 


select the correct input (Don't mistake enabled sound for the correct input.)
The monitor will feedback audio to the lineout and hp out no matter if you have selected the correct input to the ADC. The monitor will provide sound for any valid input. This will result in free mixing when recording from the monitor input instead of mic/line because the monitor itself will provide the hardware mixing for you. Be aware that MIC inputs will give two channel mono. Only Linein will give real stereo.

Now for the not working part. Attempt to record from linein in the AE4 record window, the right channel is noise and the left channel is distorted. Even with the recommended HIFI 16bit Stereo++ mode at 48kHz.


Channels

Monitor

Gain

Inout

Output

Advanced settings - Debugging via serial port


* Options -&gt; Soundcard In/Out
* Options -&gt; SampleRate
* Options -&gt; Preferences

F6 for Sample File List

Setting a grid is easy as is measuring the BPM by marking a section of the sample. Is your kick drum track &quot;not in time&quot; ? If so, you're stumped in AE4 as it has no fancy variable time signatures and definitely no 'track this dodgy rhythm' function like software of the nature of Logic has. So if your drum beat is freeform you will need to work in freeform mode. (Real music is free form anyway).

If the drum *is* accurate and you are just having trouble measuring the time, I usually measure over a range of bars and set the number of beats in range to say 16 as this is more accurate, Then you will need to shift the drum track to match your grid *before* applying the grid. (probably an iterative process as when the grid is active samples snap to it, and when inactive you cannot see it).

AE4 does have ARexx but the functions are more for adding samples at set offsets and starting playback / recording.


These are the usual features found in DAWs...

* Recording digital audio, midi sequencer and mixer 
* virtual VST instruments and plug-ins 
* automation, group channels, MIDI channels, FX sends and returns, audio and MIDI editors and music notation editor


* different track views 
* mixer and track layout (but not the same as below) 
* traditional two windows (track and mixer)


Mixing - mixdown

Could not figure out how to select what part I wanted to send to the aux, set it to echo and return. Pretty much the whole echo effect. Or any effect.

Take look at page17 of the manual.

When you open the EQ / Aux send popup window you will see 4 sends. Now from the menu choose the windows menu.

Menus-&gt;Windows-&gt; Aux Returns Window

or press F5

You will see a small window with 4 volume controls and an effects button for each. Click a button and add an effects to that aux channel, then set it up as desired (note the reverb effect has a special AUX setting that improves its use with the aux channel, not compulsory but highly useful). You set the amount of 'return' on the main mix in the Aux Return window, and the amount sent from each main mixer channel in the popup for that channel. Again the aux sends are &quot;prefade&quot; so the volume faders on each channel do not affect them.


Tracking


Effects - fade in

To add some echoes to some vocals, tried to add an effect on a track but did not come out. This is made more complicated as I wanted to mute a vocal but then make it echo at the muting point. Want to have one word of a vocal heard and then echoed off. But when the track is mute the echo is cancelled out.

To correctly understand what is happening here you need to study the figure at the bottom of page 15 on the manual. You will see from that that the effects are applied 'prefade' So the automation you applied will naturally mute the entire signal.

There would be a number of ways to achieve the goal,

You have three real time effects slots, one for smoothing like so

Sample -&gt; Amplify -&gt; Delay

Then automate the gain of the amplify block so that it effectively mutes the sample just before the delay at the appropriate moment, the echo effect should then be heard.

Getting the effects in the right order will require experimentation as they can only be added top down and it's not obvious which order they are applied to the signal, but there only two possibilities, so it wont take long to find out.

Using MUTE can cause clicks to the Amplify can be used to mute more smoothly so that's a secondary advantage.

Signal Processing -


Overdub

[[#top|...to the top]]

===Office===

====Spreadsheet Leu====

Support for some xlsx, and ods functions 


====Spreadsheet Ignition====

; Needs ABIv1 to be completed before more can be done

File formats supported 
* ascii #?.txt and #?.csv (single sheets with data only). 
* igs and TurboCalc(WIP) #?.tc for all sheets with data, formats and formulas.

There is '''no''' support for xls, xlsx, ods or uos ([http://en.wikipedia.org/wiki/Uniform_Office_Format Uniform Unified Office Format]) at the moment.

* Always use Esc key after editing Spreadsheet cells.
* copy/paste seems to copy the first instance only so go to Edit -&gt; Clipboard to manage the list of remembered actions. 
* Right mouse click on row (1 or 2 or 3) or column header (a or b or c)  to access optimal height or width of the row or column respectively 
* Edit -&gt; Insert -&gt; Row  seems to clear the spreadsheet or clears the rows after the inserted row until undo restores as it should be...

Change Sheet name by  Object -&gt; Sheet -&gt; Properties

Click in the cell which will contain the result, and click '''down arrow button''' to the right of the formula box at the bottom of the spreadsheet and choose the function required from the list provided. Then click on the start cell and click on the bottom right corner, a '''very''' small blob, which allows stretching a bounding box (thick grey outlines) across many cells This grey bounding box can be used to '''copy a formula''' to other cells.

Object -&gt; Cell -&gt; Properties to change cell format - Currency only covers DM and not $, Euro, Renminbi, Yen or Pound etc. 
Shift key and arrow keys selects a range of cells, so that '''formatting can be done to all highlighted cells'''. 
View -&gt; Overview then select ALL with one click (in empty cell in the top left hand corner of the sheet).

Default mode is relative cell referencing e.g. a1+a2 but absolute e.g. $a$1+$a$2 can be entered.

* #sheet-name to '''absolute''' reference another sheet-name cell unless reference() function used.

;Graphs

use shift key and arrow keys to select a bunch of cells to be graph'ed making sure that x axes represents and y axes represents

* value() - 0 value, 1 percent, 2 date, 3 time, 4 unit ...


;Dates 
* Excel starts a running count from the 1st Jan 1900 and Ignition starts from 1st Jan 1AD '''(maybe this needs to change)'''
Set formatting Object -&gt; Cell -&gt; Properties and put date in days


;Time 
Set formatting Object -&gt; Cell -&gt; Properties and put time in seconds taken


;Database (to be done by someone else)

type - standard, reference (bezug), search criterion (suchkriterium), 
* select a bunch of cells and Object -&gt; Database -&gt; Define to set Datenbank (database) and Felder (fields not sure how?) 
* Neu (new) or loschen (delete) to add/remove database headings e.g. Personal, Start Date, Finish Date (one per row?)
* Object -&gt; Database -&gt; Index to add fields (felder) like Surname, First Name, Employee ID, etc. to ?

Filtering done with dbfilter(), dbproduct() and dbposition().

Activities with dbsum(), dbaverage(), dbmin() and dbmax().

Table sorting -


;Scripts (Arexx)

;Excel(TM) to Ignition - commas ''',''' replaced by semi-colons ''';''' to separate values within functions 
*SUM(), 
*AVERAGE(), MAX(), MIN(), INT(), PRODUCT(), MEDIAN(), VAR() becomes Variance(), Percentile(),
*IF(), AND, OR, NOT 
*LEFT(), RIGHT(), MID() becomes MIDDLE(), LEN() becomes LENGTH(), 
*LOWER() becomes LOWERCASE(), UPPER() becomes UPPERCASE(),
* DATE(yyyy,mm,dd) becomes COMPUTEDATE(dd;mm;yyyy), 
*TODAY(), DAY(),WEEK(), MONTH(),=YEAR(TODAY()), 
*EOMONTH() becomes MONTHLENGTH(), 
*NOW() should be date and time becomes time only, SECOND(), MINUTE(), HOUR(),
*DBSUM() becomes DSUM(),


;Missing and possibly useful features/functions needed for ignition to have better support of Excel files 
There is no Merge and Join Text over many cells, no protect and/or freeze row or columns or books but can LOCK sheets, no define bunch of cells as a name, Macros (Arexx?), conditional formatting, no Solver, no Goal Seek, no Format Painter, no AutoFill, no AutoSum function button, no pivot tables, (30 argument limit applies to Excel)

*HLOOKUP(), VLOOKUP(), [http://production-scheduling.com/excel-index-function-most-useful/ INDEX(), MATCH()], CHOOSE(), TEXT(), 
*TRIM(), FIND(), SUBSTITUTE(), CONCATENATE() or &amp;, PROPER(), REPT(), 
*[https://acingexcel.com/excel-sumproduct-function/ SUMPRODUCT()], ROUND(), ROUNDUP(), *ROUNDDOWN(), COUNT(), COUNTA(), SUMIF(), COUNTIF(), COUNTBLANK(), TRUNC(), 
*PMT(), PV(), FV(), POWER(), SQRT(), MODE(), TRUE, FALSE, 
*MODE(), LARGE(), SMALL(), RANK(), STDEV(), 
*DCOUNT(), DCOUNTA(), WEEKDAY(),


;Excel Keyboard [http://dmcritchie.mvps.org/excel/shortx2k.htm shortcuts needed to aid usability in Ignition] 
&lt;pre&gt;
Ctrl Z - Undo

Ctrl D - Fill Down
Ctrl R - Fill right

Ctrl F - Find
Ctrl H - Replace

Ctrl 1 - Formatting of Cells
CTRL SHIFT ~ Apply General Formatting ie a number 
Ctrl ; - Todays Date 

F2 - Edit cell
F4 - toggle cell absolute / relative cell references

&lt;/pre&gt;


====Document Scanning - Scandal====

Scanner usually needs to be connected via a USB port and not via a hub or extension lead.

Check in Trident Prefs -&gt; Devices that the USB Scanner is not bound to anything (e.g. Bindings None)
If not found then reboot the computer and recheck.

Start Scandal, choose Settings from Menu strip at top of screen and in Scanner Driver choose the ?#.device of the scanner (e.g. epson2.device).

The next two boxes - leave empty as they are for morphos SCSI use only
 or put ata.device (use the selection option in bigger box below) and Unit as 0 this is needed for gt68xx

* gt68xx - no editing needed in s/gt68xx.conf but needs a firmware file that corresponds to the scanner [http://www.meier-geinitz.de/sane/gt68xx-backend/ gt68xx firmwares] in sys:s/gt68xx.
* epson2 - Need to edit the file epson2.conf in sys/s that corresponds to the scanner being used

'''Save''' the settings but do not press the Use button (aros freezes)

Back to the Picture Scan window and the right-hand sections.

Click on the '''Information''' tab and press Connect button and the scanner should now be detected.

Go next to the '''Scanner''' tab next to Information Tab should have Color, Black and White, etc. and dpi settings now. Selecting an option Color, B/W etc. can cause dpi settings corruption (especially if the settings are in one line) so set '''dpi first'''. Make sure if Preview is set or not.

In the '''Scan''' Tab, press Scan and the scanner will do its duty. 
Be aware that nothing is saved to disk yet.

In the Save tab, change format JPEG, PNG or IFF DEEP. Tick incremental and base filename if necessary and then click the Save button. The image will now be saved to permanent storage.


The driver ignores a device if it is already bond to another USB class, rejects it from being usable. However, open Trident prefs, select your device and use the right mouse button to open. Select &quot;NONE&quot; to prevent poseidon from touching the device. Now save settings. It should always work now.

[[#top|...to the top]]

===Emulators===

==== Amiberry ====


==== Amiga Emu - Janus UAE ====

With Amibridge, AROS attempts to make the UAE emulator seem embedded within but it still is acting as an app 

There is no dynarec m68k for each hardware that Aros supports or direct patching of motorola calls to AROS hardware accelerated ones unless the emulator has that included 

Try starting Janus with a priority of -1 like this little script:
&lt;pre&gt;
cd sys:system/AmiBridge/emulator
changetaskpri -1
run janus-uae -f my_uaerc.config &gt;nil:
cd sys:prefs
endcli
&lt;/pre&gt;
This stops Janus hogging all the CPU time.


===Miscellaneous===

====Screensaver Blanker====

Most blankers on the amiga (i.e. aros) run as commodities (they are in the tools/commodities drawer). Double click on blanker.

Control is with an app called Exchange, which you need to run first (double click on app) or  run QUIET sys:tools/commodities/Exchange &gt;NIL: but subsequently can use (Cntrl Alt h).

Icon tool types (may be broken) or command line options 
&lt;pre&gt;
seconds=number 
&lt;/pre&gt;

Once the timing is right then add the following to s:icaros-sequence or s:user-startup

e.g. for 5 minutes

 run QUIET sys:tools/commodities/Blanker seconds=300 &gt;NIL:


*[http://archives.aros-exec.org/index.php?function=showfile&amp;file=graphics/screenblanker/gblanker.i386-aros.zip Garshneblanker] can make Aros unstable or slow. Certain blankers crashes in Icaros 2.0.x like Dragon, Executor.


*[ Acuario AROS version], the aquarium screen saver.

Startup: extras:acuariofv-aros/acuario

Kill: c:break name=extras:acuariofv-aros/acuario

Managed to start Acuario by the Executor blanker.

&lt;pre&gt;
cx_priority=
cx_popkey=    ie CX_POPKEY=&quot;Shift F1&quot; 
cx_popup=Yes or No

&lt;/pre&gt;


&lt;pre&gt;
 Qualifier String    Input Event Class
   ----------------    -----------------
    &quot;lshift&quot;           IEQUALIFIER_LSHIFT
    &quot;rshift&quot;           IEQUALIFIER_RSHIFT
    &quot;capslock&quot;         IEQUALIFIER_CAPSLOCK
    &quot;control&quot;          IEQUALIFIER_CONTROL
    &quot;lalt&quot;             IEQUALIFIER_LALT
    &quot;ralt&quot;             IEQUALIFIER_RALT
    &quot;lcommand&quot;         IEQUALIFIER_LCOMMAND
    &quot;rcommand&quot;         IEQUALIFIER_RCOMMAND
    &quot;numericpad&quot;       IEQUALIFIER_NUMERICPAD
    &quot;repeat&quot;           IEQUALIFIER_REPEAT
    &quot;midbutton&quot;        IEQUALIFIER_MIDBUTTON
    &quot;rbutton&quot;          IEQUALIFIER_RBUTTON
    &quot;leftbutton&quot;       IEQUALIFIER_LEFTBUTTON
    &quot;relativemouse&quot;    IEQUALIFIER_RELATIVEMOUSE
&lt;/pre&gt;


&lt;pre&gt;
    Synonym     Synonym
    String     Identifier
    -------    ----------
    &quot;shift&quot;    IXSYM_SHIFT    /* look for either shift key */
    &quot;caps&quot;     IXSYM_CAPS     /* look for either shift key or capslock */
    &quot;alt&quot;      IXSYM_ALT      /* look for either alt key */

Highmap is one of the following strings:
    &quot;space&quot;, &quot;backspace&quot;, &quot;tab&quot;, &quot;enter&quot;, &quot;return&quot;, &quot;esc&quot;, &quot;del&quot;,
    &quot;up&quot;, &quot;down&quot;, &quot;right&quot;, &quot;left&quot;, &quot;f1&quot;, &quot;f2&quot;, &quot;f3&quot;, &quot;f4&quot;, &quot;f5&quot;,
    &quot;f6&quot;, &quot;f7&quot;, &quot;f8&quot;, &quot;f9&quot;, &quot;f10&quot;, &quot;help&quot;.


&lt;/pre&gt;


[[#top|...to the top]]

==== World Construction Set WCS (Version 2.031) ====

WCS is a fractal landscape software such as Scenery Animator, Vista Pro and Panorama. Open sourced February 2022, World Construction Set [https://3dnature.com/downloads/legacy-software/ legally and for free] and [https://github.com/AlphaPixel/3DNature c source]. 

Announced August 1994 this version dates from April 1996 developed by Gary R. Huber and Chris &quot;Xenon&quot; Hanson&quot; from Questar 

&lt;pre&gt;
Assign &quot;WCSProjects:&quot; &quot;Volume:Dir/Dir/WCSProjects&quot; 
Assign &quot;WCSFrames:&quot;   &quot;Volume:Dir/Dir/WCSFrames&quot; 
&lt;/pre&gt;

&lt;pre&gt;
Load projects .proj by accessing pull down menu Project -&gt; Open then click on CanyonSunset.proj
OK to changing .par file and enlarge Status Log window to show what is happening 
Render by pull down menu Modules -&gt; Render with End equal 1 not 300 then click bottom middle button Render 
&lt;/pre&gt;

[https://www.youtube.com/watch?v=CxQDmf1ZWG0 Youtube walkthrough of above], [], [], 

Also try working with the already built file ColoDemo - Then open with the drop-down menu: Project/Open, then WCSProject:ColoDemo.proj
Which allows you to use altimetric DEM files already included and Loading scene parameters from ColoDemo.par
Once this is done, save everything with a new name to start working exclusively on your project. 
Then drop-down menu and select Save As (&quot;NewName&quot;.proj name), then drop-down menu to open parameter and select Save All ( .par name)


After launching the software, there is a the Module Control Panel composed of five icons. 
It is a dock type shortcut of the first few functions of the drop-down menu 

*Database   - Load (#?.proj), Append, Create, Edit, Save, Dir List (of WCSProject drawer), 
*Data Ops   - Extract / Convert Interp DEM, Import DLG, DXF, WDB and export LW map 3d formats  
*Map View   - Database file Loader leading to Map View Control with option to the Database Editor 
*Parameters - Editor for Motion, Color, Ecosystem, Clouds, Waves, management of altimeter files DEM, sclock settings etc 
*Render     - rendering terrain 

These are more in the pull down menu but not in the dock 
*Motion Editor
*Color Editor
*Ecosys Editor 


Simple minimal workflow 
*Load database (1st icon - 1st)
*Set parameters and save .par file (4th icon)
*Render scene (5th icon) 

[https://www.youtube.com/watch?v=ZbTwwR2qcc4 Youtube], [], 

&lt;pre&gt;
.proj new project name which creates a drawer of additional files 

.binary array, ascii array .xyz , z buffer, DTED .dt0, vista 1990s dem, iff  conversion 
.Obj with .elev, .frd with .hdr maps, - digital elevation model (DEM) is a 3D representation of elevation data in various formats 
USGS 7.5MinDEM, 

.par 


&lt;/pre&gt;


Since for the time being no project is loaded, a query window indicates a procedural error when clicking on the rendering icon (right end of the bar). The menu is quite traditional; it varies according to the activity of the windows. To display any altimetric file in the &quot;Mapview&quot; (third icon of the panel), There are three possibilities:

* Loading of a demonstration project.
* The import of a DEM file, followed by texturing and packaging from the &quot;Database-Editor&quot; and the &quot;Color-Editor&quot;.
* The creation of an altimetric file in WCS format, then texturing.


The altimeter file editing (display in the menu) is only made possible if the &quot;Mapview&quot; window is active.

The software is made up of many windows and won't be able to describe them all. Know that &quot;Color-Editor&quot; and the &quot;Data-Editor&quot; comprise sufficient functions for obtaining an almost real rendering quality. You have the possibility of inserting vector objects in the &quot;Data-Editor&quot; (creation of roads, railways, etc.) 


The Map View (MapView) window

*Database - Objects and Topos
*View     - Align, Center, Zoom, Pan, Move 
*Draw     - Maps and distance 
*Object   - Find, highlight, add points, conform topo, duplicate 
*Motion   - Camera, Focus, path, elevation 
*Windows  - DEM designer, Cloud (.cld) and wave (.wve) editor, 


You will notice that by selecting this window and simply moving the pointer to various points on the map you will see latitude and longitude values ​​change, along with the height.
Drop-down menu and Modules, then select MapView and change the width of the window with the map to arrange it in the best way on the screen. With the Auto button the center. Window that then displays the contents of my DEM file, in this case the Grand Canyon. MapView allows you to observe the shape of the landscape from above
 

ZOOM button

Press the Zoom button and then with the pointer position on a point on the map, press the left mouse button and then move to the opposite corner to circumscribe the chosen area and press the left mouse button again, then we will see the enlarged area selected on the map.
Would add that there is a box next to the Zoom button that allows the direct insertion of a value which, the larger it is, the smaller the magnification and the smaller the value, the stronger the magnification. At each numerical change you will need to press the DRAW button to update the view.

PAN button

Under Zoom you will find the PAN button which allows you to move the map at will in all directions by the amount you want. This is done by drawing a line in one direction, then press PAN and point to an area on the map with the pointer and press the left mouse button. At this point, leave it and move the pointer in one direction by drawing a line and press the left mouse button again to trigger the movement of the map on the screen (origin and end points). Do some experiments and then use the Auto button immediately below to recenter everything.
There are parameters such as TOPO, VEC to be left checked and immediately below one that allows different views of the map with the Style command (Single, Multi, Surface, Emboss, Slope, Contour), each with its own particularities to highlight different details.

Now you have the first basics to manage your project visually on the map. Close the MapView window and go further...


Let's start working on ECOSYSTEMS
If we select Emboss from the MapView Style command we will have a clear idea of ​​how the landscape appears, realizing that it is a predominantly desert region of our planet. Therefore we will begin to act on any vegetation present and the appearance of the landscape.
With WCS we will begin to break down the elements of the landscape by assigning defined characteristics. It will be necessary to determine the classes of the ecosystem (Class) with parameters of Elevation Line (maximum altitude), Relative Elevation (arrangement on basins or convexities with respectively positive or negative parameters), Min Slope and Max Slope (slope). WCS offers the possibility of making ecosystems coexist on the same terrain with the UnderEco function, by setting a Density value.


Ecosys Ecosystem Editor

Let's open it from Modules, then Ecosys Editor. In the left pane you will find the list of ecosystems referring to the files present in our project. It will be necessary to clean up that box to leave only the Water and Snow landscapes and a few other predefined ones. We can do this by selecting the items and pressing the Remove button (be careful not for all elements the button is activated, therefore they cannot all be eliminated).
Once this is done we can start adding new ecosystems. Scroll through the various Unused and as soon as the Name item at the top is activated allowing you to write, type the name of your ecosystem, adding the necessary parameters.
&lt;pre&gt;
Ecosystem1: Name: RockBase Class: Rock Density: 80 MinSlope: 15 UnderEco: Terrain
Ecosystem2: Name: RockIncl Clss: Rock Density: 80 MinSlope: 30 UnderEco: Terrain
Ecosystem3: Name: Grass Class Low Veg Density: 50 Height: 1 Elev Line : 1500 Rel El Eff: 5
Max Slope: 10 – Min Slope: 0 UnderEco: Terrain
Ecosistema4: Name: Shrubs Class: Low Veg Density: 40 Height: 8 Elev Line: 3000
Rel El Eff: -2 Max Slope: 20 Min Slope : 5 UnderEco: Terrain
Ecosistema5: Name: Terrain Class: Ground Density: 100 UnderEco: Terrain
&lt;/pre&gt;

Now we need to identify an intermediate ecosystem that guarantees a smooth transition between all, therefore we select as Understory Ecosystem the one called Terrain in all ecosystems, except Snow and Water .
Now we need to 'emerge' the Colorado River in the Canyon and we can do this by raising the sea level to 900 (Sea Level) in the Ecosystem called Water.
Please note that the order of the ecosystem list gives priority to those that come after. So our list must have the following order: Water, Snow, Shrubs, RockIncl, RockBase, Terrain. It is possible to carry out all movements with the Swap button at the bottom. To put order you can also press Short List. Press Keep to confirm all the work done so far with Ecosystem Editor.
Remember every now and then to save both the Project 'Modules/Save' and 'Parameter/Save All'

EcoModels are made up of .etp .fgp .iff8 for each model 


Color Editor

Now it's time to define the colors of our scene and we can do this by going to Modules and then Color Editor. In the list we focus on our ecosystems, created first.
Let's go to the bottom of the list and select the first white space, assigning the name 'empty1', with a color we like and then we will find this element again in other environments... It could serve as an example for other situations!
So we move to 'grass' which already exists and assign the following colors: R 60 G 70 B50
&lt;pre&gt;
'shrubs': R 60 G 80 B 30
'RockIncl' R 110 G 65 B 60
'RockBase' R 110 G 80 B 80
' Terrain' R 150 G 30 B 30
&lt;pre&gt;
Now we can work on pre-existing colors
&lt;pre&gt;
'SunLight' R 150 G 130 B 130
'Haze and Fog' R 190 G 170 B 170
'Horizon' R 209 G 185 B 190
'Zenith' R 140 G 150 B 200
'Water' R 90 G 125 B 170
&lt;/pre&gt;

Ambient R 0 G 0 B 0

So don't forget to close Color Editor by pressing Keep.
Go once again to Ecosystem Editor and assign the corresponding color to each environment by selecting it using the Ecosystem Color button. Press it several times until the correct one appears. Then save the project and parameters again, as done previously.


Motion Editor

Now it's time to take care of the framing, so let's go to Modules and then to Motion Editor. An extremely feature-rich window will open. Following is the list of parameters regarding the Camera, position and other characteristics:
&lt;pre&gt;
-Camera Altitude: 7.0
-Camera Latitude: 36.075
-Camera Longitude: 112.133
-Focus Attitude: -2.0
-Focus Latitude: 36.275
-Focus Longitude: 112.386
-Camera : 512 → rendering window
-Camera Y: 384 → rendering window
-View Arc: 80 → View width in degrees
-Sun Longitude: 172
-Sun Latitude: -0.9
-Haze Start: 3.8
-Haze Range: 78, 5
&lt;/pre&gt;
As soon as the values ​​shown in the relevant sliders have been modified, we will be ready to open the CamView window to observe the wireframe preview. Let's not consider all the controls that will appear.
Well from the Motion Editor if you have selected Camera Altitude and open the CamView panel, you can change the height of the camera by holding down the right mouse button and moving the mouse up and down. To update the view, press the Terrain button in the adjacent window. As soon as you are convinced of the position, confirm again with Keep. You can carry out the same work with the other functions of the camera, such as Focus Altitude...
Let's now see the next positioning step on the Camera map, but let's leave the CamView preview window open while we go to Modules to open the window at the same time MapView. We will thus be able to take advantage of the view from the other together with a subjective one.


From the MapView window, select with the left mouse button and while it is pressed, move the Camera as desired. To update the subjective preview, always click on Terrain.
While with the same procedure you can intervene on the direction of the camera lens, by selecting the cross and with the left button pressed you can choose the desired view. So with the pressure of Terrain I update the Preview. Possibly can enlarge or reduce the Map View using the Zoom button, for greater precision.
Also write that the circle around the cameras indicates the beginning of the haze, there are two types (haze and fog) linked to the altitude. Would also add that the camera height is editable through the Motion Editor panel.


The sun

Let's see that changing the position of the sun from the Motion Editor. Press the SUN button at the bottom right and set the time and the date. Longitude and latitude are automatically obtained by the program. Always open the View Arc command from the Motion Editor panel, an item present in the Parameter List box.

Once again confirm everything with Keep and then save again.


Animation

The animation part is not left-back and also occupies a window. The settings possibilities are enormous. A time line with dragging functions (&quot;slide&quot;, &quot;drag&quot;...) comparable to that of LightWave completes this window. 


A small window is available for positioning the stars as a function of a date, in order to vary the seasons and their various events (and yes...).

At the bottom of the &quot;Motion-Editor&quot;, a &quot;cam-view&quot; function will give you access to a control panel. Different preview modes are possible. The rendering is also accessible through a window. No less than nine pages compose it. At this level, you will be able to determine the backup name of your images (&quot;path&quot;), the type of texture to be calculated, the resolution of the images, activate or deactivate functions such as the depth buffer (&quot;zbuffer&quot;), the blur, the background image, etc.


Once all these parameters have been set, all you have to do is click on the &quot;Render&quot; button.

For rendering go to Modules and then Render. Select the resolution, then under IMA select the name of the image. Move to FRA and indicate the level of fractal detail which of 4 is quite good. Then Keep to confirm and then reopen the window, pressing Render you will see the result. The image will be opened with any viewing program.


Strengths:

* Multi-window.
* Quality of rendering.
* Accuracy.
* Opening, preview and rendering on CyberGraphX screen.
* Extract / Convert Interp DEM, Import DLG, DXF, WDB and export LW map 3d formats 
* The &quot;zbuffer&quot; function.

Weaknesses:

* No OpenGL management 
* Calculation time.
* No network computing tool.


====Writing CD / DVD - Frying Pan====

Can be backup DVDs (4GB ISO size limit due to use of FileInfoBlock), create audio cds from mp3's, and put .iso files on discs

If using for the first time - click Drive button and Device set to ata.device and unit to 0 (zero)

Click Tracks Button - Drive 1 - Create New Disc or Import Existing Disc Image (iso bin/cue etc.) - Session File open cue file

If you're making a data cd, with files and drawers from your hard drive, you should be using the ISO Builder.. which is the MUI page on the left. (&quot;Data/Audio Tracks&quot; is on the right).

You should use the &quot;Data/Audio tracks&quot; page if you want to create music cds with AIFF/WAV/MP3 files, or if you download an .iso file, and you want to put it on a cd.

Click WRITE Button - set write speed - click on long Write button

Examples

Easiest way would be to burn a DATA CD, simply go to &quot;Tracks&quot; page &quot;ISO Builder&quot; and &quot;ADD&quot; everything you need to burn.

On the &quot;Write&quot; page i have &quot;Masterize Disc (DAO)&quot;, &quot;Close Disc&quot; and &quot;Eject after Write&quot; set.

One must not &quot;Blank disc before write&quot; if one uses a CDR


AUDIO CD from MP3's are as easy but tricky to deal with. FP only understands one MP3 format, Layer II, everything else will just create empty tracks

Burning bootable CD's works only with .iso files. Go to &quot;Tracks&quot; page and &quot;Data/Audio Tracks&quot; and add the .iso


====odf====

Every ODF file is a collection of several subdocuments within a package (ZIP file), each of which stores part of the complete document.

* content.xml – Document content and automatic styles used in the content.
* styles.xml – Styles used in the document content and automatic styles used in the styles themselves.
* meta.xml – Document meta information, such as the author or the time of the last save action.
* settings.xml – Application-specific settings, such as the window size or printer information.


To read document follow these steps:

* Extracting .ods file.
* Getting content.xml file (which contains sheets data).
* Creating XmlDocument object from content.xml file.
* Creating DataSet (that represent Spreadsheet file).
* With XmlDocument select “table:table” elements, and then create adequate DataTables.
* Parse child’s of “table:table” element and fill DataTables with those data.
* At the end, return DataSet and show it in application’s interface.


To write document follow these steps:

* Extracting template.ods file (.ods file that we use as template).
* Getting content.xml file.
* Creating XmlDocument object from content.xml file.
* Erasing all “table:table” elements from the content.xml file.
* Reading data from our DataSet and composing adequate “table:table” elements.
* Adding “table:table” elements to content.xml file.
* Zipping that file as new .ods file.

XLS file format

The XLS file format contains streams, substreams, and records.

These sheet substreams include worksheets, macro sheets, chart sheets, dialog sheets, and VBA module sheets. 
All the records in an XLS document start with a 2-byte unsigned integer to specify Record Type (rt), and another for Count of Bytes (cb). A record cannot exceed 8224 bytes. If larger than the rest is stored in one or more continue records.

* Workbook stream 
**Globals substream
***BoundSheet8 record - info for Worksheet substream i.e. name, location, type, and visibility. (4bytes the lbPlyPos FilePointer, specifies the position in the Workbook stream where the sheet substream starts) 
**Worksheet substream (sheet) - Cell Table - Row record - Cells (2byte=row 2byte=column 2byte=XF format)
***Blank cell record
***RK cell record 32-bit number. 
***BoolErr cell record (2-byte Bes structure that may be either a Boolean value or an error code)
***Number cell record (64-bit floating-point number)
***LabelSst cell record (4-byte integer that specifies a string in the Shared Strings Table (SST). Specifically, the integer corresponds to the array index in the RGB field of the SST)
***Formula cell record (FormulaValue structure in the 8 bytes that follow the cell structure. The next 6 bytes can be ignored, and the rest of the record is a CellParsedFormula structure that contains the formula itself)
***MulBlank record (first 2 bytes give the row, and the next 2 bytes give the column that the series of blanks starts at. Next, a variable length array of cell structures follows to store formatting information, and the last 2 bytes show what column the series of blanks ends on)
***MulRK record 
***Shared String Table (SST) contains all of the string values in the workbook.

ACCRINT(), ACCRINTM(), AMORDEGRC(), AMORLINC(), 
COUPDAYBS(), COUPDAYS(), COUPDAYSNC(), COUPNCD(), COUPNUM(), COUPPCD(), 
CUMIPMT(), CUMPRINC(), 
DB(), DDB(), DISC(), 
DOLLARDE(), DOLLARFR(), 
DURATION(), EFFECT(), FV(), FVSCHEDULE(), 
INTRATE(), IPMT(), IRR(), ISPMT(), MDURATION(), MIRR(), NOMINAL(), NPER(), NPV(), 
ODDFPRICE(), ODDFYIELD(), ODDLPRICE(), ODDLYIELD(), 
PMT(), PPMT(), PRICE(), PRICEDISC(), PRICEMAT(), PV(), RATE(), 
RECEIVED(), SLN(), SYD(), TBILLEQ(), TBILLPRICE(), TBILLYIELD(), 
VDB(), XIRR(), XNPV(), YIELD(), YIELDDISC(), YIELDMAT(),


&lt;pre&gt;
&lt;/pre&gt;


&lt;pre&gt;
&lt;/pre&gt;

&lt;pre&gt;
&lt;/pre&gt;

{{BookCat}}</text>
      <sha1>ahi8mofl9enomynn9ghw9rolz9g0nu3</sha1>
    </revision>
  </page>
  <page>
    <title>JPEG - Idea and Practice/Foreword</title>
    <ns>0</ns>
    <id>246147</id>
    <revision>
      <id>4676582</id>
      <parentid>4654125</parentid>
      <timestamp>2026-10-18T02:35:22Z</timestamp>
      <contributor>
        <username>Acrions</username>
        <id>3509296</id>
      </contributor>
      <comment>himself -&gt; themselves</comment>
      <origin>4676582</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3884" sha1="cqne5jmomgakasxrmzd7e5zt6u57gm7" xml:space="preserve">
&lt;gallery widths=160px heights=216px class=&quot;center&quot;&gt;
File:Juliasetsdkjpegforeword1.jpg|Drawing perfect but file compressed too much
File:Juliasetsdkjpegforeword2.jpg|
File:Juliasetsdkjpegforeword3.jpg|File perfect but drawing incomplete
&lt;/gallery&gt;


When the era of digital pictures began, a serious problem arose: 

* A digital picture took up a great deal of storage space.

At that time computer memory was more expensive than it is now.  The memory requirements were a very significant problem. Moreover, the electronic transmission of data was slow. A method had to be found by which the data could be compressed.  The compression method could lose some information.  It could be acceptable to introduce small changes in colour values if the overall impression of the picture were preserved.  Sadly the solution to this problem is not, as one might hope, a nice piece of mathematical work in the classical sense.  It involves experiments with the ability of the human eye to discern colour nuances compared with light intensity.  Strange tables appear in the procedure. 

The '''JPEG method''' was a result of collaboration. JPEG stands for &quot;Joint Photographic Expert Group&quot;.  The expert group was organized in 1986 and in 1992 issued a standard for their new image file format, JPEG.  Since that time this format has been the most commonly used format for storing and transmitting  photos. 

The JPEG method is not difficult to understand. However, it ''is'' difficult to acquire knowledge about the method, mainly because it is not a fixed and final procedure but rather a principle.  The number of articles that try to explain the method is immense.  They often contain misunderstandings strongly suggesting the author themselves has not made, or closely studied, a program that can produce a file or draw the picture from a file. 

Hence this Wiki book.

==Parts One and Two ==

This Wiki book is divided into two parts.  Each is accompanied by programs.  These are closely described and used to make illustrations and experiments.

* '''Part one''' explains the idea.  We have altered the method a little so that it is easier to understand.  Our alterations allow us to introduce variables in order to make interesting experiments. Our method is rather simple. Naturally, it does not compress as efficiently as the real JPEG method, but it is still surprisingly good. It can compress a file so that the data take up about 7 per cent of the original data of the picture. When you have read ''part one'', you will have a good understanding of the principle of the JPEG method.  If it was merely this you were looking for, you will not become very much wiser by reading ''part two''.

* '''Part two''' is based on two articles: 
:# The official document (from 1992) where the method is described in full and recommended as international standard; 
:# The document (also from 1992) specifying the standard for the implementation of the method which has become the most commonly used - almost all JPEG pictures you will meet are in accordance with this implementation. 

We explain all the things necessary for making a program that can produce efficiently compressed JPEG files.  We provide a program that can draw the pictures of the most commonly used JPEG file types. We have also made a program that can show all the most relevant information in the header part of a JPEG file. Some experience with this program can help you to understand the arrangement of a JPEG file.  You can use this information (copy it or use it as guidelines), if you want to make your own JPEG compressor - for instance as a component of a program that can make computer graphics.

==About the Pictures==

All the pictures in this book were made with the program in ''part two'' - also those in ''part one'', since the files made with the demonstration program are not true JPEG files.

{{BookCat}}</text>
      <sha1>cqne5jmomgakasxrmzd7e5zt6u57gm7</sha1>
    </revision>
  </page>
  <page>
    <title>Chess/Arranging The Board</title>
    <ns>0</ns>
    <id>273011</id>
    <revision>
      <id>4676689</id>
      <parentid>4658175</parentid>
      <timestamp>2026-10-18T05:19:20Z</timestamp>
      <contributor>
        <username>Mast303</username>
        <id>3416213</id>
      </contributor>
      <origin>4676689</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1558" sha1="p7std59co5lgp22hzmu2uy312u0vyye" xml:space="preserve">{{Chess diagram|tright
|
|rd|nd|bd|qd|kd|bd|nd|rd
|pd|pd|pd|pd|pd|pd|pd|pd
|  |  |  |  |  |  |  |  
|  |  |  |  |  |  |  |  
|  |  |  |  |  |  |  |  
|  |  |  |  |  |  |  |  
|pl|pl|pl|pl|pl|pl|pl|pl
|rl|nl|bl|ql|kl|bl|nl|rl
|Initial position of the chessboard
}}

Before starting the game, it's very important to arrange the board and the pieces correctly.

The rows are called ''ranks'', and the vertical squares are called ''files''.

Your chess board is an 8×8 board. Place the board in such a manner that the bottom right hand corner on your side is white (&quot;White on the right&quot;). On that white square, place the Rook and place the other Rook on the bottom left corner. Next to the Rooks, place the Knights, followed by the Bishops.

Wrong placement of the Queens is a common mistake. While arranging these pieces, make sure that the black Queen goes on a black square and the white Queen goes on a white square (&quot;Queen on her own color&quot;). The King then goes on the square next to the Queen. It is very important that you place these two pieces properly. Any game found to be set up incorrectly, i.e., King on its own color, will result in the game being voided and a restart called using the same colors.

If the board contains the file letters and rank numbers, remember that the Queen is placed on the d-file (&quot;d for Dame&quot;), and that White starts on the first rank.

Fill the next rank with your eight pawns and repeat for both colours. You're ready to play!
{{-}}
{{BookCat}}
&lt;noinclude&gt;{{Chess/Navigation|Introduction|Playing The Game}}&lt;/noinclude&gt;</text>
      <sha1>p7std59co5lgp22hzmu2uy312u0vyye</sha1>
    </revision>
  </page>
  <page>
    <title>Aros/Platforms/Arm Raspberry Pi support</title>
    <ns>0</ns>
    <id>286123</id>
    <revision>
      <id>4676517</id>
      <parentid>4676376</parentid>
      <timestamp>2026-10-17T13:28:40Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4676517</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="106179" sha1="7igeidlgme4syt2ppo7e3iw0l7tjmck" xml:space="preserve">{{ArosNav}}

[[#Native]]

[[#Hosted]]

[[#Build]]

[[#Hardware]]

[[#References]]

[[#Future]]


==Introduction==


[[File:Scalos00.png|thumb|Scalos on Aros Pi3b]]

Aros aims to cover Pi 3 to 5 512Mb+ RAM 


Options to boot from using a good power source to prevent the yellow lightning symbol. 
*With Pi3b+ the max you can get is 5.1V 2.5A with micro usb.
*With Pi4 5.1V 3A with usb-c 
*With Pi5 5.1V 5A, the amps went ever upwards, even to 5.1V 9A with usb-c 


* Pi500+ keyboard wedge - working but not much tested esp [https://github.com/aros-development-team/AROS/commit/48e9c8edcca4b5c1e1fe0b1123f2129f624af67b power button] 
* Pi500 wedge with up to date bootloader via PiOS - working but not much testing esp [https://github.com/aros-development-team/AROS/commit/48e9c8edcca4b5c1e1fe0b1123f2129f624af67b power button] 
* Pi 5  - Quad A76 64bit ARMv8 and RP1 &quot;southbridge&quot; with VideoCore 7 D0 (rev1.1) - untested 
* Pi 5  - Quad A76 64bit ARMv8 and RP1 &quot;southbridge&quot; with VideoCore 7 Pre-D0 C1 (Rev1.0) - untested 
* Pi400 RPI-400 keyboard wedge - resolution changing and audio from micro hdmi0 (near 40pin) and micro hdmi1 (near usb-c psu) - Fn F10 0x5e power on and off works or held down for over 7 seconds auto shutdown - keyboard ok - wifi and lan ethernet testing - 
* Pi 4  - Quad A72 64bit ARMv8 with VideoCore 6 
* Pi 3  - Quad A53 [https://www.raspberrypi.com/documentation/computers/processors.html 64 bit] ARMv8 with VideoCore 4 with '''fan''' to prevent overheating cpu 82C+ throttling 
* Pi02W - Quad A53 64bit - boots but [https://forums.raspberrypi.com/viewtopic.php?p=2387984#p2387984 usb not working but did in the past], 


* Pi 2 - Quad 32bit ARMv6 with VideoCore 4 - mostly not 64bit compatible 
* Pi Model B+ 32bit ARMv6 with VideoCore 4 - not 64bit compatible 
* Pi Model A and B 32bit ARMv6 with VideoCore 4 - not 64bit compatible 


===Native===

* 2013-03 Kalamatee starts work
* 2015-04 Work continues with mschulz on the kernel and Kalamatee (NicJA) on gpio and usb
* 2018 [https://www.patreon.com/posts/i-owe-you-some-20956961 mschulz resume adding BE big endian support], [https://www.patreon.com/michal_schulz/posts Big endian on Pi]  
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bsek latest commits for pi 3b, 4 and 5 64bit] 
* 2026 [https://github.com/aros-development-team/AROS/commits?author=metaneutrons latest commits for Pi5]
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bitplane latest commits for ARM]


====64bit====

'''Download''' A [https://archive.org/details/piAROS Pi Distribution (Distro) has started] and the contents copied to fat32 8GB+ microSD card (there will be drawers/folders - boot c Classes Demos Developer Devs Extras etc only showing). The SD can be plugged in to the Pi. And power on. [https://pi.amiga.icu/ Repository]

'''Not recommended''' but [https://aros.sourceforge.io/nightly1.html RaspberryPi 3, 3+, 4 and 5 64bit ArmV8 nightly builds] [https://sourceforge.net/projects/aros/files/ and alternative site and nightly2] which is a test version of '''very few''' apps with both raspi-aarch64-system and raspi-aarch64-contrib can be unbz2'd to a SD or SSD as appropriate. 

64bit build works well on a single core LE little endian. Multicore [https://github.com/aros-development-team/AROS/commit/1df0747c2bda3523a43029725a709b1f377d84ec may follow]. Any issues booting could be down to the SD card so please use another SD to see if it is resolved. Remember Aros Arm uses FAT32 and Aros can detect issues with this format very acutely (once fault found, FAT 0x0FFFFFF7 bad cluster so no files written after that, no repair). Please report your experiences in the [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2138&amp;pid=15057#post_15057 Aros forum thread], [https://forums.raspberrypi.com/viewforum.php?f=179 Raspberry Pi Aros Dev and User forums], [https://forums.raspberrypi.com/viewtopic.php?p=2387984#p2387984 previous Raspberry Pi forum thread]. Any bugs or issues can be [https://github.com/aros-development-team/AROS/issues described here to fix] 


*Pi500+   untested usb3 booting or nvme ssd 
*Pi500    untested usb3 booting 
*Pi5      untested usb3 booting 
*Pi400    boots with '''USB3''' port based sata3 ssd 
*Pi4      untested (may need eeprom update from PiOS or Pi SD Imager) 
*Pi 3 B+  is pre-configured for USB sata3 boot - untested 
*Pi 3 B   may need [https://www.youtube.com/watch?v=ubnwvxF3Klc PiOS to set OTP to boot from usb - do so at your own risk] - if OTP set to usb, boot works but slower than SD card 

Speed write wise (top faster) 
&lt;pre&gt;
*NVME Pi5 untested    &gt;1000MB/sec  or faster if matched correctly 
*Sata3 ssd              500MB/sec
*SD        V90           90MB/sec  4K maybe 8K 
*SD        V60           60MB/sec  1080p 
*SD     U3 V30           30MB/sec  720p 
*SD C10 U1 V10 A1 A2     10MB/sec  minimum should be used now 
*SD C06                   6MB/sec  
*SD C04                   4MB/sec 
&lt;/pre&gt;


As a homage to the past, Aros shows a reduced number of icons but this can be changed by left mouse click in the window and then right click down to Window -&gt; View -&gt; All files

Windows can be manipulated by the top (moving) and the bottom right corner (resizing) only. 

Zune like MUI gui interface, has a unique quirk in that after changing a setting in a text box, you may sometimes need to press Enter/Return before clicking OK, Save, etc 


Double left mouse click on most picture (Developer/Debug/Tests/Datatypes), audio and video files are supported, via datatypes, by the multiview application. 
Esc escape key usually closes open windows even the desktop 

In Prefs/Appearance some decorative theming elements need work. There is a few Mason icons in /Prefs/Presets/Icons/Mason/ and the ever present default Gorilla - Icon exchange in works 

For more intensive graphics applications, you may need to edit config.txt in the root folder and change 128M to 256M to adjust more memory to graphics usage 

If your cursor should '''appear''' to vanish, fear not it is still there. Please head to the top of the screen i.e. the title bar, hold down the left click mouse and drag the screen down a little and the cursor will appear again. Then you can drag the screen up again. 


Like most amiga like OSs the audio and networking need to be setup manually 

Audio AHI prefs - Mode settings tab - needs both Music unit and Unit 0 set to RPiHDMI:16 bit stereo++  or RPiPWM:16 bit stereo++ at 44100Hz. Press '''Save or Use''' button after each choice 


For wireless, please use the Wifi prefs and already selected device bwfm.device. Press Scan and double right click on the router and enter password. You may need to setup after every power off
*if asking for password again - press cancel and go to Network Prefs, Wireless Networks tab and highlight the router line and hit the remove button and press the cancel button. Retry with Wifi prefs again 
*...waiting for an address - Disconnect and try Connect 
Until, Connected to &lt;router&gt; - 192.168.x.x 


For lan ethernet port, please use Network prefs and the following hardware is 
*lan9514    Pi3b Pi2 not supported at the moment 
*lan7515    Pi3b+ type into Device  usblan78xx.device as net0:  remove other device(s) 
*bcmgenet   Pi4 Pi400 choose for Device bcmgenet.device 
*cdnsgem    Pi5 Pi500 Pi500+ RP1 i/o for cadencegem 
 (network prefs may forget random information when rebooted) 


Summary
&lt;pre&gt;
*3b    ethernet not supported, usb ethernet not working but wifi prefs setup works 
*3b+   wifi working and ethernet works 
*4     untested 
*400   wifi and ethernet untested 
*5     wifi and ethernet untested
*500   wifi and ethernet untested
*500+  wifi works 
&lt;/pre&gt;


Type in 'aarch64' in the [https://archives.arosworld.org/index.php?function=search&amp;tool=simple search box] and you will see available software packages / apps. apkg can be used to inspect and install applications. 

[http://archives.arosworld.org/index.php?function=browse&amp;cat=network/browser amelinium web browser (JS 1.6 ES9 ECMASCript 2018)] is available with an [https://eab.abime.net/showthread.php?t=122494&amp;page=80 eab thread] reminiscent of [https://github.com/zapek/Voyager Voyager] and to a lesser extent [https://github.com/amigazen/aweb3/ Aweb JavaScript 1.5 (ECMAScript 3)] as css and javascript websites can be slow to load or resolve (no JIT) and nothing from facebook, reddit etc. 

Press Cancel at screenmode selector or -wb argument to get windowed version. You could use the Shift + Del shortcut or mouse wheel should work to delete all text at once. Html5test gives 189 (1.29), 300 (1.31), 311 (1.33) out of 555, some bigger Amiga like browsers are around 370+ but it does less better. 

You may have to delete the cache (Menu -&gt; Page -&gt; Delete cache) to fully retest big Amelinium updates or free up space. 
Be aware [https://pianetaamiga.it/en/reportage-pianeta-amiga-2026/ some site pages] can use up hundreds of MBs of cache very quickly 

 DNS lookup failed...  close browser and reboot and setup wifi again - repeat until it works again 

 youtube video and audio - js button for javascript must be on/shaded -  Settings -&gt; Soundoutput - AHI 
Any restriction to lower resolutions is due to [https://docs.invidious.io/faq/#q-where-are-the-360p480p1080p-quality-options bandwidth]. Either CPU/GPU, internet speed and/or video quality. Pi3 can expect 480p (wifi) to 720p (ethernet). Pi4 expect (wifi)  (ethernet). 

Telegram https://t.me/s/channel_name for public messages from vamped_amiga chatamigagames demoscenecracktros 

*art local js apps like dpaint.js 


There is normally no Bluetooth support for most amiga like OSs but Aros has one [https://github.com/aros-development-team/AROS/commit/6942cbfbf66426d21963a7fcd8aba6aff611a9e0 work in progress] [https://github.com/RPi-Distro/bluez-firmware/tree/pios/trixie/debian/firmware/broadcom firmware] 

*Bluetooth 4.1 BCM43430A1.hcd Pi3B, Pi3A, Zero 2W 
*Bluetooth 4.2 BCM4345C0.hcd  Pi3B+, Pi4 
*Bluetooth 5.0 BCM4345C5.hcd  Pi4B rev, CM4 and maybe Pi5 and CM5 

&lt;pre&gt;
*bthid    keyboard mouse support 
*btserial serial 
*btpan    short range wireless connecting devices 
&lt;/pre&gt;


Only the Pi5 has a RTC real time clock, the other Pis will need to use ntp services [https://github.com/aros-development-team/AROS/commit/29cd4116330dc7f692d90757eacc59fb3f31ae70 sntp] with time.cloudflare.com pool.ntp.org or Cloudflare 162.159.200.1, 162.159.200.123, 2606:4700:f1::1, 2606:4700:f1::123 or [https://github.com/bohunamiga/PiNTP PiNTP -s goodtime.ijs.si or ntp1.ptb.de] to get the date and time from the internet. Can use date in a shell e.g.  date 24-Dec-2026 23:59:59  but this will need to be done again after every reset/power off. Maybe [https://github.com/aros-development-team/AROS/commit/28674a157bc56175aa668e7b62dca6fa740578dc ds3231 rtc with dtoverlay=i2c-rtc,ds3231 in config.txt] 


It helps to have all usb devices already plugged in before power on to detect at the moment. Even then some usb devices will freeze the mouse cursor and the only resolution is to remove the offending usb device and reinsert. Sometimes, the reinsert leads to the mouse cursor vanishing, it is still there and responds to left mouse clicks, top of the screen and pull down the screen. 

USB classes support from Prefs/Trident is still work in process 
*usbaudio working on usb3 port (blue) on pi4, 400 but not working (no rt isochronous) on usb2otg (white or black) for pi3b, zero 2w 
*[https://aminet.net/package/mus/midi/camd camdusbmidi] detects midi devices without a preferences file (Prefs/Env-Archive/sys/midi.prefs) as [https://www.youtube.com/watch?v=RBxHkwy4Nrw auto setup now] possibly with [https://github.com/metaneutrons/mt32-pi metaneutrons mt32-pi] [https://github.com/rtzor/mt32-pi mt32-pi fork] [https://github.com/ahmadexp/mt32-pi fork] [https://github.com/gmcn42/mt32-pi-control control of] [https://github.com/dwhinham/mt32-pi mt32-pi pi3+]. Alternative of [https://homspace.nl/samplerbox/ SamplerBox]. 

Will need developer clang gcc tools to look at 64bit ports of [https://archives.arosworld.org/?function=showfile&amp;file=driver/audio/usbmidi.i386-aros.lha usbmidi], [https://aminet.net/package/mus/midi/CAMD_Toolkit CAMD_Toolkit], [https://aminet.net/package/mus/midi/camdtools camdtools], [https://github.com/cnvogelg/amiditools amiditools], [https://github.com/timoinutilis/midi-sequencer-amigaos horny src], [https://aminet.net/package/mus/midi/horny-base horny-base], [http://bnp.hansfaust.de/index.html BnP], [https://arosarchives.os4depot.net/?function=showfile&amp;file=audio/misc/timidity.lha timidity], 


Regarding 680x0 emulation, there are several options (not implemented yet) that could be considered 
*[https://github.com/aros-development-team/AROS/blob/6722a0ae9e03fe5d26e32703360bd2059e0864cc/rom/m68kemu/README.md?plain=1#L424 m68kemu.library] for some Amiga productivity where the cpu is emulated and the system calls are redirected to Aros ones
*[https://github.com/BlitterStudio/amiberry amiberry] (winuae) for everything else like games 
*[https://github.com/jonx/AROS/tree/aarch64-darwin-graft/arch/all-darwin/libs/emu68k emu68k] 
*[https://scriptedamigaemulator.net/ Scripted Amiga] with [https://github.com/naTmeg/ScriptedAmigaEmulator ScriptedAmigaEmulator] or older [https://github.com/gbraad-amiga/ScriptedAmigaEmulator2 ScriptedAmigaEmulator2] 
 Hopefully getting Pi3 up to 25Mhz 68040 (non JIT) and 50Mhz 68040 (JIT) 
 Pi4 maybe getting up to 50Mhz 68040 (no JIT) and 100Mhz 68040 (JIT) 


[https://pinout.xyz/ GPIO 40 pins] [https://learn.sparkfun.com/tutorials/raspberry-gpio/gpio-pinout pinout] 

Some exceptions:

*Physical pins 27, 28 (GPIO0, 1) are an internal I2C bus and should not be used
*The other I2C on pins 3, 5 (GPIO 2, 3) can be used generally, but be aware they have permanent pull-up resistors to 3.3V
*For MIDI use USB but there are dedicated UART pins 8, 10 (GPIO 14, 15).

With a HAT it's more awkward -- you need to know which pins are used by the HAT and avoid them. Hopefully this will be documented.

Remember all GPIOs are 3.3V (not 5V tolerant), floating/noisy inputs can cause odd behavior, and that shorting the power supplies can cause instant death of the Pi.

In the shell (Cntrl + C to end) 

 GPIO PIN/A/N,SET/N,GET/S,MODE/K,PULL/K

Controls and queries hardware GPIO pins via gpio.resource which is stored in the rom or Devs/ '''please test''' 

*PIN   -- (Required) Target GPIO pin number (e.g. 12).
*SET   -- Set pin output value to 0 (LOW) or 1 (HIGH).
*GET   -- Read and print current digital input level (0 or 1).
*MODE  -- Configure pin mode: IN (Input), OUT (Output), ALT (Alternate).
*PULL  -- Configure pull resistor: NONE, UP, DOWN.

EXAMPLES
&lt;pre&gt;
GPIO 12 MODE OUT
GPIO 12 SET 1
GPIO 12 GET
GPIO 13 PULL UP
&lt;/pre&gt;


[https://gpiozero.readthedocs.io/en/stable/installing.html Current] [https://gpiozero.readthedocs.io/en/v1.2.0/api_boards.html old support for gpiozero is unknown at present] [https://energenie4u.co.uk/res/pdfs/ENER314%20UM.pdf and associated 433MHz equipment] [ USA X10 security and lights via USB] [ OpenHab with Shelly Smart Plug connected over Wi-Fi, controlled by MQTT or HTTP] 


Printing only with Postscript but [https://github.com/bohunamiga/MintPRINT one] of [https://github.com/boingball/MintPRINT two] [https://github.com/Andiweli/AmiAirPrint/tree/main AirPrint] IPP has been attempted with [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2061&amp;pid=13954#post_13954 discussion] 


Youtube 

[], [], [https://www.youtube.com/watch?v=X4fmWAIv7FE Aros native on Pi3b], 

[], [], [https://www.youtube.com/watch?v=TSxlYb1eQWU Installed on Pi3b+], 

[], [], [https://www.youtube.com/watch?v=NFF1H3jCoz8 testing Aros native on Pi400], 

[], [], [https://www.youtube.com/watch?v=nIVx7mh1E1Q&amp;pp=ygUHYXJvcyBwadIHCQkTDAGHKiGM7w%3D%3D Aros on Thumb 2 based 32bit-ish ARM STM32H743 board], 


[https://www.youtube.com/watch?v=zQM4CD64xDE&amp;t=612s&amp;pp=ugUEEgJlbg%3D%3D Performance under Linux] but on Aros... 

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot; |Pi
! width=&quot;10%&quot; |Single Core 2D
! width=&quot;10%&quot; |Single Core 3D
! width=&quot;10%&quot; |Single Core 3D
! width=&quot;10%&quot; |SMP 2D
! width=&quot;10%&quot; |SMP 3D
! width=&quot;10%&quot; |SMP 3D 
! width=&quot;35%&quot; |Comments
|-
| &lt;!--Pi--&gt;Pi3 
| &lt;!--Single Core 2D--&gt;
| &lt;!--Single Core 3D--&gt;
| &lt;!--Single Core 3D--&gt;
| &lt;!--SMP 2D--&gt;
| &lt;!--SMP 3D--&gt;
| &lt;!--SMP 3D--&gt;
| &lt;!--Comments--&gt;
|-
|}


==== 32bit ====

For the Pi1 Pi2 Pi2B the status of AROS native ARMv6 for 32bit RasPi was OK. System booting, USB working (although with some issues but plans to fix them). 32bit native [http://www.aros.org/nightly1.html ARMv6 32bit nightlys] raspi-armhf-system raspi-armhf-contrib unbz2'd to fat32 microSD 


===Hosted===


AArch64 CPU backend for AROS, a Cocoa/Metal display, clipboard / host-volume / CoreAudio / BSD-sockets bridges, GPU 2D via gpufx.library, a 68k→AArch64 JIT (run68k), and a full Rust std port. On [https://www.jkn.me/blog/macaros-aros-on-apple-silicon/ latest Apple Silicon] [https://github.com/jonx/Macaros early buggy alpha version of hosted Aros .dmg on MacOS12+]. Please use [https://github.com/jonx/Macaros/issues MACAros github] for issues, features etc and possibly [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2030&amp;pid=13910#post_13910 here] 


[http://www.aros.org/snapshots1.html old linux and android hosted 32bit] 


==== Hosted ====

=====64bit=====

[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80&amp;pid=13667#post_13667 Ubuntu Linux PC hosted Pi compiler build] 

[https://github.com/BlitterStudio/aros-compiler-docker Docker based cross compiler for various Aros systems], 

[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80 From the Aros Raspberry pi 3 64bit thread] 
Instructions on building 64-bit Raspberry Pi AROS and cross-compiler from sources.

You will need:
- Ubuntu 24.04 or 26.04
- qemu-system-aarch64 installed
- Internet connection
- rpi-scripts.tar.gz downloaded (https://axrt.org/download/aros/rpi/rpi-scripts.tar.gz)

1) Install prerequisites:

sudo apt install git gcc g++ make gawk bison flex bzip2 netpbm autoconf automake libc6-dev liblzo2-dev libpng-dev gcc-multilib byacc python3-mako cmake yasm curl nasm

2) Clone sources

cd &lt;project-directory&gt;
git clone https://github.com/aros-development-team/AROS.git --recurse-submodules

3) Extract rpi-scripts.tar.gz. Copy all files into your project directory so that you have:

AROS (the directory with cloned sources)
fix-dotdot.py
rebuild.sh
recreate-sdcard.sh
run-qemu.sh
update-sdcard.sh

4) Run ./rebuild.sh. Select option 1) toolchain-core-aarch64

This will execute process of building a cross-compiler. During this process packages will be downloaded from Internet. This process can take up to 2 hours. If there are some missing dependencies, install them with 'sudo apt install' and restart this step.

5) Run ./rebuild.sh again. Select option 2) core-raspi-aarch64

This will build system files for 64-bit Raspberry Pi AROS. This process can take around an hour.

6) Run ./recreate-sdcard.sh

This will create an sdcard.img file with contents of previous step.

7) Run ./run-qemu.sh

This will start QEMU with SD card image and ROM images. It will boot into AROS.


=====32bit=====

Ubuntu VM approach to compiling [http://lallafa.de/blog/2013/06/building-aros-hosted-for-raspbian/ Linux hosted AROS June 04, 2013]

 ../AROS/configure --target=linux-armhf  --enable-includes=/usr/arm-linux-gnueabihf/include --x-includes=/usr/arm-linux-gnueabihf/include --x-libraries=/usr/arm-linux-gnueabihf/lib

arm-elf- is symbol-linked to arm-linux-gnueabi- (arm-linux-gnueabi- is more correct in this case, because it's going to be compiling the ARM AROSBootstrap for ARM Linux)

*armel - many of the &quot;android&quot; machines require since the entire OS is made for soft float VFP. 
*armfp - Efika MX target, Raspberry PI, EfikaMX, Pandora and virtually everything (VFP)

Keep in mind it's possible to start hardfp AROS hosted on softfp system, though, as long as no calls between AROS and host require floating point parameters. NOTE: hardfloat objects *cannot* be linked with softfloat objects - they have a different ABI.

Just keep in mind the arm nightly build machine is quite complex beast. It needs the x86_64 host compiler to compile AROS tools. The arm version is built every night using gcc-4.6.2 crosscompiler (built together with AROS) and successfully builds armel and armhf linux hosted targets.

*needs an AROS code compiler for ARM target 
*as well as unix compiler for ARM linux host (would be best to have both softfp and armhf, we have softfp only now) with full set of libraries and includes.

with—disable-crosstools  $AROS_CC  is always a wrapper around $KERNEL_CC  ?  If  so,  this  is  wrong for some ports. This can break Darwin, Windows and Android port. 
Yes,  Android  port  will  build.  And  even  work. But it's not good because  the  port  will  not  be ABI-compatible with other ARM ports. Android's ABI is different from GNUEABI. For example:

&lt;pre&gt;
enum test {foo, bar};
enum test testvar;
&lt;/pre&gt;

sizeof(testvar)  will  be  equal  to sizeof(int) in GNUEABI (Linux and AROS)  and  sizeof(short)  on  Android. This affects linking objects from static linklibs, for example.

Previously everything worked because $AROS_CC was a wrapper on top of $HOST_CC. And a real crosscompiler was used on non-ELF hosts.

Android is the same. $KERNEL_CC is incompatible with AROS.

compiler=kernel  is  appropriate _ONLY FOR CODE WHICH RUNS ON HOST OS_ (or  barebone  hardware,  if  we  talk  about  native).  This includes bootstraps,  their  linklibs, and host-side dynamic libraries (Windows makes extensive use of them because of architectural considerations.

No single AROS object should be compiled with this setting. $KERNEL_CC is really compatible with AROS *ONLY IN LINUX-HOSTED* and no more. On other systems (Darwin, Windows,  Android) this is not true any more, and compiler=kernel is never going to work.

If  you  want  to  compile your AROS module against host OS includes, append  the  following  to  USER_INCLUDES  (or  USER_CFLAGS,  this  is effectively the same):

 -isystem $(GENINCDIR) $(KERNEL_INCLUDES)

$(KERNEL_INCLUDES) expands to:

 -isystem  &lt;your_os_includes&gt;  -isystem  &lt;host_OS_gcc_private_includes&gt;
 -nostdinc

This makes AROS compiler adhering to host OS APIs.

If you want some preprocessor symbols based on what your host OS actually is, add something like -DHOST_OS_$(AROS_HOST_ARCH).

Why is there $(GENINCDIR) at all? Because host OS has its own libc includes, which would conflict with AROS ones. And the host OS libc is not binary-compatible with AROS one.

Why doesn't Windows-hosted port use $(KERNEL_INCLUDES) ? Because WinAPI includes conflict with AROS ones in fundamental typedefs, like WORD, BYTE and BOOL. It's almost impossible to deal with this in any other way than rewriting WinAPI definitions using AROS types.

Building under centos 6.3 (i386) currently, and AROS creates the toolchain itself. haven't yet committed the necessary changes but &quot;./configure --target=raspi-armhf&quot; is enough to start, then &quot;make arosboot-raspi&quot; will generate arosraspi.img (containing the bootstrap, kernel.resource, and exec.library) as well as arosraspi.rom (containing all the other essentials components such as dos, graphics etc).  It will also copy over a config.txt file to make the raspi bootstrap code load the correct kernel, and a cmdline.txt that enables exec debug output.

*armel = typically Debian 6, Ubuntu Maverick, Android, 
*armhf = typically Debian 7, Debian 8, Ubuntu Precise,

Cross-compiling Ubuntu ARM softfp 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armel' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armel] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armel.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabi libx11-dev:armel libsdl-dev:armel
&lt;/pre&gt;

&lt;pre&gt;
 ./configure --target=linux-arm --x-includes=/usr/include \
             --enable-includes=/usr/arm-linux-gnueabi/include
&lt;/pre&gt;

Cross-compiling Ubuntu ARM hard-float 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armhf' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armhf] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armhf.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabihf libx11-dev:armhf libsdl-dev:armhf
&lt;/pre&gt;

&lt;pre&gt;
    ./configure --target=linux-armhf --x-includes=/usr/include \
                --enable-includes=/usr/arm-linux-gnueabihf/include
&lt;/pre&gt;

Now, the AROS build is configured properly and all you need to do is:

 make


==Build==

===64bit===

[https://github.com/aros-development-team/AROS/blob/7016ce28bfdb754182edb16011c98faaf5413c29/arch/aarch64-raspi/boot/mmakefile.src#L180 boot makefile] 


===32bit===


# download/checkout the source someplace, e.g. /build/AROS-Src/
# make a directory to store external sources AROS downloads, e.g. /build/Ports
# make a build directory, e.g. /build/aros-raspi-armhf
# cd into the build dir, configure, and then run make -:

&lt;pre&gt;
&gt;cd /build/aros-raspi-armhf
&gt;/build/AROS-Src/configure --target=raspberrypi-armhf --with-serial-debug --enable-ccache --with-portssources=/build/Ports
&gt;make
&gt;make arosboot-raspi
&lt;/pre&gt;

then copy the files from /build/aros-raspi-armhf/bin/raspi-armhf/AROS/ onto an sdcard, and download/copy the Raspi firmware files onto it.

You should then be able to boot the sdcard on your RasPi.

The current W.I.P tree to svn. it can be built as follows ..
&lt;pre&gt;
./configure --target=raspi-armhf
make arosboot-raspi
&lt;/pre&gt;

That will generate arosraspi.img, arosraspi.rom and config.txt in bin/raspi-arm/AROS - so either copy just those files to a fat formatted SD card (with the firmware files on), or copy the whole contents of the AROS folder.

NB - if you have a Linux/other install, backup the existing config.txt first

arosraspi.img contains the bootstrap (which has very basic mailbox code, framebuffer/gpio init, and console &quot;emulation&quot; via code pinched from our libbootconsole), kernel.resource, and exec.library

arosraspi.rom contains all the other components needed to boot AROS.

The config.txt file will tell the RasPI bootstrap to load the arosraspi kernel and ramdisk (rom).

the bootstrap has minimal mailbox code, planning on adding either a resource or library that driver/app code will use to access it (likewise for GPIO)


Help building AROS hosted on Linux ARM

Was looking a way to use more my Handheld ARM based called Pyra (Dragonbox Pyra) an ARM (Omap5 cpu with 4GB ram) linux based machine (Debian Buster v10 with kernel 5.6.19 adapted) and have a try to compile the latest Aros sources by Deadwood directly on this device.
Compilation stops after build libpopupmenu.a and trying to build libatomic have this error:

&lt;pre&gt;
    Configuring build in bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic
    configure: WARNING: unrecognized options: --disable-nls, --without-x
    checking for --enable-version-specific-runtime-libs... no
    checking for --enable-generated-files-in-srcdir... no
    checking build system type... arm-unknown-linux-gnu
    checking host system type... arm-unknown-aros
    checking target system type... arm-unknown-aros
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for arm-aros-strip... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-strip
    checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
    checking for gawk... no
    checking for mawk... mawk
    checking whether make sets $(MAKE)... yes
    checking whether make supports nested variables... yes
    checking for arm-aros-gcc... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-gcc
    checking whether the C compiler works... no
    configure: error: in /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic':
    configure: error: C compiler cannot create executables
    See config.log' for more details
    make[2]: *** [mmakefile:4489: /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic/.configured] Error 77
    [MMAKE] make --no-print-directory TOP=/media/farox/pyra2/arosbuilds/toolchain-core-armhf-build SRCDIR=/media/farox/pyra2/arosbuilds/AROS CURDIR=tools/crosstools/gnu TARGET=tools-crosstools-gcc-libatomic-configure -s --file=mmakefile tools-crosstools-gcc-libatomic-configure failed: 512
    [MMAKE] Error: Error while running make in tools/crosstools/gnu: No such file or directory
    make[1]: *** [Makefile:361: linklibs-libatomic] Error 10
    make: *** [Makefile:183: crosstools] Error 2
&lt;/pre&gt;


looking at config.log on arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic

found that arosbuilds/toolchain-core-armhf/arm-aros-ld: cannot find -laeabi
so do make linklibs-aeabi-arm-quick
and the missing lib was built.

now the next stop is at
fatal error: bits/libc-header-start.h: No such file or directory
and
fatal error: sys/cdefs.h: No such file or directory
in many places so after checking that have this missing include files i have noted that my include path is a bit different, standard searching path is /usr/arm-linux-gnueabihf but in my system is /usr/include/arm-linux-gnueabihf
so if i add my path to some mmakefiles compilation goes on....but is a better way to add this path to avoid every mmakefiles to be changed?

fixed with adding
-I/usr/include/arm-linux-gnueabihf
to where is missing on mmakefiles like
USER_INCLUDES := -isystem $(GENINCDIR) -I/usr/include/arm-linux-gnueabihf $(KERNEL_INCLUDES)

P.s. I have changed many mmakefiles and have at least compiled (after many hours) the toolchain doing make every time in arosbuilds/toolchain-core-armhf-build (also have to disable making tests under cplusplus but don't remember the directory ...) but ask an help to have an automated way to correctly build without modify mmakefiles.


Last time built armhf target was around 2 years ago. At that point built is via cross-compilation from linux (ubuntu 22.04) using linux armhf crosscompiler (this can explain the path differences you are experiencing) as well as using AROS gcc cross-compiler in version 6.5.0 (build with option 21) in rebuild.sh). Since then AROS GCC has been updated to 10.5.0 and don't believe anyone tried to build the armhf target again.

My suggestion would be to downgrade GCC to 6.5.0 (via editing AROS/config/gcc_def file) and try to first build using cross-compilation from x86_64 linux. Once that works, you will have a &quot;template&quot; to compare to native compilation under arm linux.


Thanks for your suggestion...but think the toolchain with GCC 10.5.0 is compilable if i found a way to pass the path of my system to the script that build (option 21 on rebuild).
The other only changes are (but don't know where to modify...) is to add the build of libaeabi and disable the building of some tests under cplusplus that use exceptions and is not supported under ARM. try to crosscompile with my Linux amd64 PC.

For paths look into core-linux-armhf/bin/linux-armhf/gen/config/target.cfg. A number of build-wide variable is set there containing paths to local build system. These variables and the target.cfg file are generated by AROS ./configure script.

Thanks compilation now go forward...changed target.cfg under &quot;toolchain-core-armhf-build/bin/linux-arm/gen/config&quot; and do make on &quot;toolchain-core-armhf-build&quot; dir.

Need to find where to enable build libaeabi.a so can build the entire toolchain with option 21 of rebuild.sh


Found something that looks like libeabi in AROS/arm-all/arm-aeabi/mmakefile.src. Try adding a third line there:

#MM- linklibs-armhd : libklibs-aeabi-arm

Don't remember needing this library. Possibly the 6.5.0 GCC somehow does this while 10.5.0 is missing this.

Try adding this line (and the variant &quot;linklibs-armhf&quot; instead of hd) but it did not solve the automatic building of the missing lib. I must do &quot;linklibs-aeabi-arm-quick&quot;.
Anyway after have build the aeabi lib i succefully built the toolchain (after many hours...). Smile

To test I restarted from selecting option 21 (on rebuild.sh) but after many hours i get the same error of the kernel includes not found...maybe i need to modify the configure script for my case.

With the toolchain built i try to build the core-linux-armhf (DEBUG) (option 22) but after a while it stopped with
&quot;cannot find -laeabi &quot; so i made it built manually...and now i can continue compiling...i'll let you know if all goes ok.


== Hardware ==

===64bit===


====BCM2712====

With the Pi5 

Broadcom VideoCore 7 vc7 is an integrated GPU with 12 cores and up to 800 MHz clock. VideoCore VII is capable of OpenGL ES 3.1 and Vulkan 1.2. The driver support for the Raspberry Pi continues to build upon the [https://lore.kernel.org/dri-devel/20230928114532.167854-1-itoral@igalia.com/ open-source V3D driver] stack within [https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450 Mesa] hopefully be merged for Mesa 23.3. x265 HEVC accelerated untested, x264/h.264 and VP9 cpu only. 

*Raspberry Pi M.2 HAT+ Expansion Board 
*Geekworm X1001 PCIe to M.2 Key-M NVMe
*Geekworm X1003 PCIe to M.2 HAT NVMe SSD PIP Board for Raspberry Pi 5 
*Pineboards Pi Hut HatDrive! M.2 HAT 2024/V4 
*Hat+ Gen2 Gen3 Nvme
*GeeekPi 52Pi N04 for Raspberry Pi 5 NVME M.2
*


*2024 RPI AI HAT    - Hailo  20TOPs  no LLMs 
*2026 RPI AI HAT+ 2 - Hailo  40TOPs  slightly better? 


[https://www.raspberrypi.com/documentation/accessories/camera.html Cameras for Pi]
*Raspberry Pi camera module, the V3 with Sony IMX708 back-illuminated CMOS 12 Megapixel sensor
*Raspberry Pi Camera Module V2 – 8MP Sony IMX219 Sensor
*Raspberry Pi camera Rev 1.3, 5MP 1080P OV5647 image/video module, 2592 x 1944 pixels


====BCM2711====

With the Pi4 an ARM a72 cpu is about x3 times the size of an a53 in the Pi3 

the 2711b line used more power when idle, compared to the 2711c 

*2018 Raspberry Pi PoE HAT Power Over Ethernet Hat - design issues 
*2020 Raspberry Pi PoE+ HAT Power Over Ethernet Hat Pi3b+ Pi4 only - better design 
*Waveshare PoE HAT (B) with cooling fan for Raspberry Pi 3B+/4B 802.3af PoE 

*[https://github.com/axizo-pi/V3DLib vc6 V3D 4.2] is derived from [https://docs.broadcom.com/doc/12358545 vc4], but it is [https://docs.mesa3d.org/drivers/v3d.html significantly different] 
The QPU pipeline stays mostly the same, you still have an add ALU and a multiply ALU and it can issue two ALU OPs per cycle. There is still 4 SIMD lanes, interleaved over 4 cycles.
The instruction encoding for the QPUs is different, but the core instructions are the same.

Instructions for packed 8 bit int math has been dropped, along with most of the pack modes.
Instructions for packed 16bit float math has been added (2 floats at in a single operation)
With vc5/vc6, you write two packed 16f value to the tilebuffer (or four writes of 32f, if you are using the rgba32f framebuffer). And there is a handy vfpack operation which allows you to pack two f32s into a single 32bit value in a single instruction. You can vfpack directly into the tile buffer register.

the multiply ALU can now fadd, so you can issue two fadds per instruction. the add ALU has gained a bunch of new instructions 

the A and B register files have been merged. You still only get an A read and a B read per instruction, but they read from one big register file (which means the underlying memory block has gone from two sets of &quot;one read port, one write port&quot; to one &quot;two read ports, one write port&quot; block)

The theoretical max FLOPs per QPU remains the same at two per cycle, other than the bump from 400mhz to 500mhx but it looks like a lot of effort has been put putting those theoretical FLOPs to better use. 
*vc4 could run one or two threads per QPU. When you ran in two thread mode, the available register file halfed to 32 registers.
*vc5 added a four thread per QPU mode, with 16 registers per thread.
*vc6 doubled the size of the register file. You could now use all 64 threads in two thread mode and 32 registers in for thread mode. Single thread mode was removed, you always have at least two threads.

With the threading improvements, the QPUs should spent much less time idle waiting NOPs for memory requests. Most of the design changes have gone to improving the fixed function hardware around the QPUs. A fixed function blend unit has been added, which should reduce load on the QPUs when doing alpha blending. hope software blending is still possible 

The tile buffer can now store upto 4 render targets (up to 128bits per pixel, so if you are using 4 32bit render targets, you can't have a depth buffer)

A MMU, allowing a much simpler/faster kernel driver.

Many more texture formats, framebuffer formats.

h264/x264 as Pi3 

All the features needed for opengl es 3.0 

H.265 / HEVC decoder is a HEVCv2 Main 4:4:4 10 design supporting bitstreams up to profile 5.1
HEVC hardware decode supports 4kp60, 10-bit. Audio output is pretty much unchanged, but the HDMI audio channels now support 8x192kHz bitrates 

Each ALU typically have 2 floating point operators, and as you pointed out in a earlier post videocore 6 is no exception, with both a multiply and additive floating point operator. Thus theoretical GFLOPs are calculated with both operators in mind. That is what the 2 in my formula represents, and is common across any modern programmable shader, whether you calculate Nvidia, AMD, Intel, Boardcom or any other company's GPUs. Total ALUs * 2 * GHz clock = GFLOPs, In the case of Raspberry Pi 3, it's 24 ALUs * 2 operators * 0.4GHz = 19.2GFLOPs
If the Videocore 6 does indeed only have 16 ALUs (16 * 2 * 0.5GHz), you'd have only 16GFLOPs but they are better utilised 

Possible maximum performance 
&lt;pre&gt;
VideoCore IV @ 250MHz: 250 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 24 Gflop/s
VideoCore IV @ 300MHz: 300 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 28.8 Gflop/s
VideoCore VI @ 500MHz: 500 [MHz] x 2 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 32 Gflop/s
&lt;/pre&gt;

Faster LPDDR4 memory.


====BCM2837==== 

With the Pi3 
* Broadcom BCM43438 chip provides 2.4&amp;nbsp;GHz 802.11n wireless LAN, Bluetooth Low Energy, and Bluetooth 4.1 Classic radio support, 3B+ [https://github.com/aros-development-team/AROS/commit/afa5bc0bb17d5dd06bcfdbac00853a3799ca8d76 LAN7515] 

The overclock ability has diminished with each chip version as the energy usage has increased. BCM2837 is one of the warmest yet and benefits from active fan cooling if all four cpu cores are in use for a short while. Video playback maybe affected due to the lack of custom support in the GPU with Aros. 5 V / 2.4 or 2.5 amp power supply recommended if all four cpu cores are running, else throttling (cpu slowdown) might occur. 

[https://github.com/hermanhermitage/videocoreiv/wiki/VideoCore-IV-Programmers-Manual Dual VDP] and scalable QPU in [https://docs.mesa3d.org/drivers/vc4.html VC4] and x.264/h.264 accelerated untested only and VP9 on cpu or neon help 


ARMv8-A has [https://developer.arm.com/documentation/102412/0100/Privilege-and-Exception-levels privilege levels] where userspace typically runs at ‘EL0’, the kernel at ‘EL1’ or ‘EL2’ and the firmware at the highest level ‘EL3’. 


===32bit===

=== Core Kernel ===


====BCM2708(family)====
which includes the [http://elinux.org/RPi_Hardware BCM2835] (ARM1176JZF-S 700&amp;nbsp;MHz CPU + VideoCore IV GPU + up to 1GB RAM)

*Framebuffer (fb) using mailbox 
*IRQ scheduler, etc 
*Arasan based SD Card controller 
*Synopsis DesignWare USB 2.0 OTG controller [http://networkdirection.net/index.php?option=com_content&amp;view=article&amp;id=106:rasperry-pi-usb-controller&amp;catid=45:raspberry-pi&amp;Itemid=54 Unofficial DOCS pdf],  [dwc_otg.c FreeBSD], [], [https://www.riscosopen.org/viewer/view/mixed/RiscOS/Sources/HWSupport/USB/Controllers/DWCDriver/ RiscOS USB Driver], [https://www.riscosopen.org/forum/forums/5/topics/878 RiscOS USB Discussion], [https://www.riscosopen.org/forum/forums/11/topics/1893 Other USB RiscOS], [http://plan9.bell-labs.com/plan9/index.html Plan9 Miller's usb] http://plan9.bell-labs.com/sources/contrib/miller/, [https://github.com/Chadderz121/csud CSUD driver], 
*[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf SMSC 9512] USB LAN/Hub chip 
*CMOS RAM 
*VCHIQ port which sends messages to the GPU e.g. for mouse, keyboard, audio on HDMI, etc 
*Audio Driver 
*Serial Peripheral Interface Bus (SPI) 
*[http://www.susa.net/wordpress/2012/06/raspberry-pi-pcf8563-real-time-clock-rtc/ I2C registers]
*I2S 
*Universal Asynchronous Receiver Transmitter (UART) 
*[http://elinux.org/RPi_BCM2835_GPIOs GPIOs] and [http://www.adafruit.com/blog/2012/08/17/broadcom-bcm2835-peripheral-memory-map-and-gpio-alternate-use-chart-piday-raspberrypi-raspberry_pi/ Alternative view of GPIO]

BCM2836 
* For Pi B+, PI 2 and Pi 3 SMSC LAN9514 chip adding 10/100 Ethernet connectivity and four USB channels to the board

*[http://www.andrewscheller.co.uk/rpi_pcb_modules.html PCB], [http://elinux.org/RPi_Low-level_peripherals Low level features],


 Implemented so far... 

# Modify the configure system so that it correctly builds for the arm hardware float raspi target.
# Implemented the bootstrap to load the aros modules and prepare the arm to jump into them. Reworked the x86 console support so that parts can be stolen for raspi to use since t has no basic functionality to output to the display.
# Implemented a kernel.resource to prepare the raspi for running aros and provide the low level api calls to expose available resources and allow exec, etc function.
# Implemented serial debug support
# Implemented the exec (and kernel) functionality required to make multitasking work (and interrupts, exceptions, syscalls, etc)
# Implemented a timer.device to utilise the hardware timers.
# Implemented a very basic gfx driver to expose the hardware's framebuffer.
# Implemented an SD-Card driver for AROS which presently only supports the raspi's chipset but can easily be modified to support all sd-card hardware and media.
# Fixed the fat filesystem support in AROS so that it can boot on RasPi's normal SD-Card setup. The &quot;rom&quot; image files needed use a different filename than the default linux, etc images so can be easily installed without harming the existing files - you only need to change the loaded images in the config file to get aros to boot.
# Updated the build scripts to automatically download the necessary raspi firmware files and wrap it all up so that you can simply extract the archive to a fat formatted sdcard and boot it on the raspi without having to get anything else.
# fix everything in contrib and ports to build for raspi (needs proper testing/fixes but allows every component to actually compile at least, including owb) + numerous other fixes to get things working on arm/raspi ..


Improvements...

# Implement a USB chipset driver &quot;OR&quot; finish the existing one [https://github.com/aros-development-team/AROS/commit/c07d13c724f944674be5db54fc6a71ee72a01809 usb otg] - the current code is mostly a skeleton that should initialise the chipset and then needs relevant code to support the different transfer types. It also has the &quot;virtual&quot; hub code in place to represent the raspi's USB port (from poseidons p.o.v) 
# Implement a driver for the USB NIC (a few weeks - depends on USB above) 
# Write an [https://github.com/aros-development-team/AROS/commit/d55d0f74d20b769bbb8c8d386e5c1d7a9154f05a audio driver] (a few weeks - independent of USB) and [https://github.com/aros-development-team/AROS/commit/e93a4c245f27a87c9c4c1d39206694b39059998a HDMI]
# fix syscall bug in the current raspi kernel code
# Graphics depend on having a decent &quot;bcmdma.resource&quot; implemented as to use the cpu's dma engine. The sd card driver needs to use it for transfers to/from the controller - and the gfx system needs to use it for &quot;blitting&quot;. 
# [https://github.com/aros-development-team/AROS/commit/4019d84e4975d4dad987a12d57fe108f5ac048e6 Improve the gfx driver], [ vc4gfx HIDD] add [http://dri.freedesktop.org/wiki/VC4/ Gallium3D support] 
# [https://github.com/aros-development-team/AROS/commit/b13905b3e8e45b089f520b44692c81affddd066f Improve] the [https://github.com/aros-development-team/AROS/commit/3a876755c070f5c73c4f53c7f4d35b4f923088b9 sdcard] device driver  - which is also pretty basic but should work with most cards, rework it to also support pci, etc. sd card interfaces on x86 
# The current code using very rudimentary access to the gpio interface - so that should be implemented as some resource for other components to access, as-well as the i2c interface exposed over the gpio interface. that should have a hidd class implemented which uses the gpio resource to communicate.


 Boot up typical for most other OSs before the open sourcing of many binary blobs from 2017 onwards 

On power-up, the rpi [http://www.open.com.au/mikem/bcm2835/ BCM 2835] [https://github.com/hermanhermitage/videocoreiv VideoCore4] GPU, not the ARM CPU, is in control, and the SD card slot is the only peripheral device with power. The firmware burned into the BCM2835's VideoCoreIV GPU PROM requires a DOS-style partition table; a FAT-formatted first partition; and the freely redistributable but closed sourced Broadcom files “bootcode.bin” and “start.elf” in that partition.

The boot sequence carries out several pre-boot tasks

*On powering of the rpi, the GPU reads and executes bootcode.bin, which then loads start.elf 
*The GPU loads the “start.elf” file, eventually, into the L2 cache and then executes it
*configures the memory split for the CPU and GPU
*reads and parses “config.txt” from the same partition on the SD card and applies the settings (like a PC’s BIOS settings)
*loads the “kernel.img” file, again from the same partition
*activates the CPU to begin executing the loaded kernel image

The CPU/GPU memory split is hard-coded into start.elf, so Broadcom provides three start.elf images, to give 32M, 64M, or 128M to the GPU for multimedia performance, and the remainder to the CPU.

RPi uses [https://github.com/raspberrypi/firmware some closed source loaders] and at some point it loads a binary blob named &quot;kernel.img&quot; at 0x8000, at that point there would be a rudimentary Aros alive. If one wants to use the SD-card then there would have to be a driver for the interface and a fat filesystem handler (SD-card has to be formatted to fat filesystem)

Boot code and kernel are now linked together and made into that binary blob, just for starters. Raspberry Pi uses [http://kernelnomicon.org/?p=133 u-boot] and [http://kernelnomicon.org/?p=138 UBoot] as bootloader, there's already some code in the Efika MX port for that. UBoot is a native bootloader and not just for the raspberry pi, it loads after start.elf.

You can find Efika MX port from arch implementations, some hacking is needed for the mmakefile.src'es as iit dates back to before the Aros crosstool era or else you get some weird errors while building. You also need to code the bootstrap and serial handling.

At the moment it seems that a fastest route for the native build would be to make one binary blob without using the package system. Raspberry's memory layout is pretty simple and if the implemented u-boot doesn't support loading other modules 

&lt;pre&gt;
?          - alias for 'help'
mtest      - simple RAM test
autoscr    - run script from memory
base       - print or set address offset
bbm        - BBM sub-system
bdinfo     - print Board Info structure
boot       - boot default, i.e., run 'bootcmd'
bootd      - boot default, i.e., run 'bootcmd'
bootm      - boot application image from memory
bootp      - boot image via network using BootP/TFTP protocol
cmp        - memory compare
coninfo    - print console devices and information
cp         - memory copy
crc32      - checksum calculation
echo       - echo args to console
fatinfo    - print information about filesystem
fatload    - load binary file from a dos filesystem
fatls      - list files in a directory (default /)
go         - start application at address 'addr'
help       - print online help
iminfo     - print header information for application image
itest      - return true/false on integer compare
jade       -
loadb      - load binary file over serial line (kermit mode)
loads      - load S-Record file over serial line
loady      - load binary file over serial line (ymodem mode)
loop       - infinite loop on address range
md         - memory display
mm         - memory modify (auto-incrementing)
mtest      - simple RAM test
mw         - memory write (fill)
nfs        - boot image via network using NFS protocol
nm         - memory modify (constant address)
pci        - list and access PCI Configuration Space
ping       - send ICMP ECHO_REQUEST to network host
printenv   - print environment variables
rarpboot   - boot image via network using RARP/TFTP protocol
reset      - Perform RESET of the CPU
run        - run commands in an environment variable
saveenv    - save environment variables to persistent storage
saves      - save S-Record file over serial line
setenv     - set environment variables
sleep      - delay execution for some time
tftpboot   - boot image via network using TFTP protocol
USB        - USB sub-system
usbboot    - boot from USB device
version    - print monitor version
&lt;/pre&gt;


And there is one more thing about modular ports. In order to actually implement this, your bootstrapping environment should provide the ability to load several files. On PC this is provided by GRUB2. on CHRP you can read filesystem via OpenFirmware, and Sam's Parthenope relies on modified u-boot. If your bootstrap allows to load only a single file, then you stuck with monolithic kickstart. By the way...  u-boot allows not only to boot up a single uImage or zImage, it also allows to write client programs AFAIK. With this approach, you actually can write modular bootstrap for ARM AROS using unmodified u-boot.

Most used [http://www.compulab.co.il/workspace/mediawiki/index.php5/U-Boot_quick_reference uboot options] are fatls usb 0:1,

the reason behind INTB_KERNEL is to allow use of the standard Exec function AddIntServer() to add interrupt handlers for
hardware drivers etc. AmigaOS never used it for abstract hardware drivers. AmigaOS  routed  only  raw  hardware IRQs there. Their assignment was hardcoded. As well as number of them. Actually on AmigaOS every bus has its own interrupt subsystem. For example PCI bus. PCI interrupts on Amiga are routed to a single exec interrupt.  1:1 relationship between CPU  and hardware interrupts is present only on PC.

IMHO we miss things like AddInterrupt/RemInterrupt methods on our PCI subsystem's device class.  PCI bus class should map these methods to whatever is appropriate. This is how it is done on AmigaOS and friends. When these are implemented, raw kernel.resource API will be needed only for several PC-specific drivers with hardwired resources. Exec IRQs are real IRQs only on Amiga hardware. On other machines they can be emulated where appropriate (VBlank is a good example). kernel.resource is meant  to be different, its IRQs are hardware-agnostic, they are plain &quot;Hardware IRQ number X, whatever this means&quot;. They are low-level actually, and meaningful only in the context of a particular system.

Was that not the transition from irq.hidd to kernel.resource? No.  A long time ago there was another hacky bit named INTB_TIMERTICK. It was &quot;abstract timer interrupt&quot;, used by timer.device. It was the same as VBlank, but with larger frequency. I removed it, because kernel.resource API was a cleaner way to access this interrupt. Furthermore, there can be more than one timer in the system. Thinking about bringing back timer HIDD definitions again. hpet.resource is a bad idea.

Can someone please enlighten me a little on how the scheduler is meant to work?
 
Poseidon.library creates its &quot;Poseidon Event Task&quot; during RTF_COLDSTART -&gt; then calls Wait(), and ends up in limbo because wait disables interrupts (used for the scheduler heartbeat), and basically waits forever because the sigbit is never set, since krnSwitch doesn't switch the task unless TF_SWITCH is set, and no codepath run during this seems to set it?? TF_SWITCH does not disable/enable switching. This flag just enables to run user-supplied hook when the task is being switched away. It is completely safe to call Wait() in Disable()d state. Doing this actually temporarily breaks this state. IDNestCnt gets remembered in struct Task, then next task is selected, and its IDNestCnt is restored in sysbase (see kernel_scheduler.c). If there are no other tasks, then your cpu_Dispatch() should enable interrupts on the CPU and enter idle mode. See x86 implementation for good example.

You miss what happens next...
 1. KrnSwitch() saves context of your task, saves IDNestCnt (core_Switch() and cpu_Switch()), then drops into cpu_Dispatch().
 2. cpu_Dispatch() calls core_Dispatch. Then two cases are possible:
 2a. There is a READY task. It is picked up, its IDNestCnt is restored in SysBase, then cpu_Dispatch() needs to restore registers and exit. The next task is run.
 2b. There are no READY tasks. core_Dispatch() returns NULL. In this case your cpu_Dispatch() should enter idle loop. It should just enable interrupts on the CPU and put it on halt. This allows it to process hardware interrupts. Eventually some of your interrupt handlers wakes up your task and puts it into READY list.

My heartbeat interrupt has been slowed atm to help debugging - but it never actually gets a chance to fire because of the Wait() disabling interrupts. Perhaps you have forgotten to enable interrupts in your idle loop.

There is a change in the format of AROS executables. Until now we were using Elf RELocable files which are usually used as intermediate object files. We had them for various reasons, one of them was how AROS files were built in the past. That days we had no real aros cross compiler and the option to embed relocation data in unix executables (or in executable files in general) was rather new and not every linux/unix system had it. Therefore we have decided to use intermediate files. Although it was somehow working (and it is still working :-)), it has some drawbacks. Therefore decided to introduce real Elf EXEC types, in first turn implemented on ARM target with option to expand in future to all other AROS architectures.

The first patch was pretty easy and appeared to work somehow. It generated nice executables with embedded relocation info. Not only that, it also removed all global symbols adjusting relocation data to be relative to the beginning of the sections. That move reduced number of symbols in each executable significantly (depending on the file between 20 and 80% of all symbols could be removed). The only symbols that stayed in the file are local ones - due to the nature of the patch wasn't able to remove them since we have not seen them in the symbol hash table.

The patch didn't worked though. The files were relocated, AROS kernel loaded, but it crashed very early. What happened? Well, the nature of ARM relocations happened :)

Most of the relocation data on all machines is rather simple. Relocation can be absolute or pc-relative, sometimes the offset has to be bit shifted. On ARM v7 there is another one. There, when one wants to load an address of function/variable into register a combination of two instructions can be used: movw and movt. The first one loads immediate into lower 16 bits of a register while clearing upper 16 bits. The second one loads immediate into upper 16 bits without touching lower halfword. Loading of a pointer into a register looks like this:

        movw r0, #:lower16:label

        movt   r0, #:upper16:label

In this case there are two relocations - one for lower halfword and another for upper. If an overflow of lower 16 bits occurs during relocation process, the upper one should be updated as well. Unfortunately with current patch and with typical ARM executables there is not enough information to perform the calculations.

There are two options - the first one would be to give up and go back to &quot;fake&quot; executables, another one would be to change from REL to RELA relocation info. The latter contains an addend, extra data which can be used to perform all the relocation calculations I need.

Decided for the second option. The patch is already in the works. There is another function for the binutils' bfd backend to perform the final relocation. There can decide what to do with every reloc info, modify data and eventually strip some symbols. An advantage is - at this stage of the linking process have also full access to all local symbols so can change all relocations section relative and eventually strip all symbols from the files. 


 GPU 

VCore developed by Alphamosaic Ltd and now owned by Broadcom. Most of start.elf runs on the GPU.   Placing ALL the userland GPU code in the videocore.hidd isn't going to be a terribly big problem because the code they published is nothing more than a shim that sends data straight to the GPU to execute.

The good news about this is that we only need to write our HIDD using the OpenVG API.   The shim is relatively small codewise and lives in the ARM memory (the actual OpenVG code itself lives in the GPU RAM area and its loaded from start.elf).   That's also the bad news.  Our driver has to translate AROS video calls to OpenVG calls, for most tasks it should be easy, for some, not so much.  It's still probably less difficult and less work, than controlling the GPU directly.

The other good news is that anything done through OpenVG happens on the GPU, its truly accelerated.   It also has some nice font functions, meaning we can lead into an accelerated text mode later.

Basically, AROS resets or locks up when it tries to use AROS_ATOMIC_INC or DEC.  If I comment out the byte/word operations in the header files and use non-atomic operations, the code works as expected.
 
have read that the L1 cache needs to be enabled to use LDREX and co (which I also read is only meant to be used on multi processor systems with shared memory) - however I am certain this is correctly enabled.

If you are using LREX or STREX, you should have L1 cache enabled, at least on the ARM CPU I work with at work.

L1 cache is enabled by enabling the MMU *AND* setting the C and I bits in the CPU - the C bit is ignored, and the I bit only covers the 16 byte instruction pipeline if the MMU is not enabled.

Can you verify that your assembly is generating LDREX/STREX? From the behavior, it almost sounds like its generating the default Semaphore locked atomics.
 Impossible. There are no semaphore-locked atomics. There are Disable()/Enable()-based ones instead. And there's a special #define AROS_NO_ATOMIC_OPERATIONS in this case, which tweaks Disable()/Enable() implementations not to recurse forever.
 I have tested this on ARMv5 which does not have ldrex/strex, it works fine. On those ARMs there's no way to have real atomics. On other OSes (like Linux) this is done by introducing things like atomic_t, which appears to be a complex structure, holding the value together with accompanying spinlock (implemented using swp).

    #warning &quot;TODO: lookup optimal mmu table settings for raspi memory&quot;
        /* Set up an identity-mapping for all 4GB */
        for(x = 0; x &lt; 4096; x ++)
        {
            pagetable[x] = x&lt;&lt;20 | (0x40002|0x80000|0x010000|0x00C00|0x04);
        }

Shouldn't there be a second loop that sets the 'C' bit in the descriptor for the RAM pages?

Currently, you have TEX=0, C=0, B=1 for all pages (Shared Device).

You should have TEX=0, C=1, B=0 for RAM (Write-Through, Cached)

    So ..
     
     pagetable[x] = x&lt;&lt;20 | 2;

     
    should be enough?

No, for RAM you need to change the '| 0x40' to '| 0x80'

tell dosboot the correct defaults to use

Please don't do this. This bootconfig.c is a deprecated legacy thing. I wanted it to go away completely with time. Instead,  display  drivers  should auto-install themselves during own initialization phase. I. e. detect hardware=&gt;instantiate itself. This   should   make  things way simpler. With this approach you only need  to add the driver into KS image to get the device autobooted. No hardcoded stuff. 
Currently  VESA  and  VGA drivers do this, look there for examples. never rewrote ATI driver because i don't have any test system for it.

they defined a smaller AROSCPUContext than the ExceptionContext - yet reference it as ExceptionContext in other places, and since it hasn't allocated enough storage for ExceptionContext, are corrupting memory/the structure (since the elements that are there don't map 1 to 1 with the exception context).

AFAIK, AROS has been moving in a different direction to this in recent years. It is the job of graphics HIDDs to allocate bitmaps etc. so that they have the most suitable characteristics, including allocating them from GPU RAM where possible. The concept of chip RAM is only for legacy code, and most if not all non-68k platforms should have all system RAM
marked as chip.

BTW, is the video processing code you mention CPU code or GPU code?

Also, IIRC we have support for &quot;external memory allocators&quot;. Perhaps that's what we need for the allocation of GPU RAM through the mailbox.

All hosted and x86 native ports should use proper context formats.

trying to clarify if the vblank handler has to have run by this point to prevent this deadlock. Actually, no. Unless you have installed VBlank handler which should wake up at some point. Without VBlank there will be no quantum count. Consequently, there will be no forced preemption. But the rest will work, and multitasking will be cooperative (switch happens only when current task voluntarily gives up the CPU). Does it depend on the vblank having run before this point? and if yes what does that mean on systems where it might be able to run enough code (e.g. get to this point) before the vblank interrupt has triggered? What is it waiting for? It could wait for timer, in this case you need timer.device working. VBlank is currently needed for exec's quantum counter. In current native ports we have only a single timer, which is served by timer.device. VBlank is simulated by timer.device also. If your machine has two timers, then you can use one of them for VBlank, and another for timer.device, this will simplify things down. VBlank needs to be 50 Hz for historical reasons, many programs use it as cheap timer. I am periodically thinking about making some abstract mechanism to be able to change quantum source (and untie it from 50 Hz), but have no time to come up with something good. Additionally i started disliking timer.device hardcoded design when PC has got many timers (old 8253, APIC, HPET).
Currently i think there should be some low-level entity representing tick source. timer.device should just select the most appropriate source for its units.
The BCM2835 has 4 GPU based timer sources - 2 are used by the GPU, so im using Timer3 for our heartbeat and the remaining one will be free to the system. There is also the less capable ARM timer but that is dependent on the CPU frequency. Very good. You won't need any emulation. Set the heartbeat to 50 Hz and drive VBlank from it. Use other timer for MicroHZ.

Can you use the 'econsole.hook' I make for debugging the Sam460 via the serial port?
It provides a before-anything-else shell prompt on the serial port.  You can then do 'NewCLI' to test your graphics, or use any DOS command in shellcommands.resource.

You should just be able to add econsole.hook to your module list, and use 'econsole' in your bootargs.

So long as you have a working Exec/RawMayGetChar and Exec/RawPutChar, it should work.

Also make sure to add shell.resource and shellcommands.resource for this.

That should have done it.

If you set &quot;#define DEBUG 1&quot; in  arch/all-native/econsole/econsole.c, do you get any additional serial output?

have added it to the build and added econsole to the command line - and can see the bootloader picks up on the emergency bootconsole tag, but I still only get the insert bootable media display?

Im assuming it exposes a fake filesystem that tricks aros into booting?
The contents of which are: ECON:AROS.boot

Way to handle the scheduling code? The implementations I had been following were causing problems, due to cascading interrupts which I cant handle properly in the asm stubs just now (when they break disable etc.) - since it means detecting the interrupted codes cpu mode and getting the correct sp/lr for it, and that's just too tedious for arm.
 
To work around this ive added a system idle task which does nothing - and when the scheduling code has no task to run switches this in and lets it run, thereby allowing the interrupts etc to resume until something does need to happen.
 
Also, by adding accounting code to cpu_Switch() and cpu_Dispatch(), it should allow the system to log idle time correctly (as well as running tasks).
 
have thought of also adding an additional task that never runs, solely to record time spent in IRQ handlers, but I digress..

was under the impression that kernel.resource should *never* be used outside of exec.library. This is a wrong impression.
Michal started designing it because portable nature of AROS does not fit well into exec's API with all its assumptions. So, he started the new, hardware-agnostic kernel API from scratch. Yes, exec sits on top of it in places. But kernel always meant to be open thing. Otherwise it would not exist. 
it wasn't meant to be just used willy nilly by user code - but by lower system components (e.g. exec) so that they could be implemented in a more generic fashion, and the kernel resource itself hide the systems quirks.

Adding new things there perfectly keeps up with our decision to minimize AROS-specific intervention into APIs which can clash with MorphOS or Amiga OS4 extensions. We want at least source-level compatibility there. Binary compatibility on PPC would be extremely cool, but at the other hand we have no maintainer for this, as well as their ABIs splintering. 
It depends on what exactly is being implemented - there's no reason we should have everything crammed into kernel.resource if it doesn't need to be (i.e. if its better suited as a separate component/subsystem in its own right)

The _LE versions are for when you have endian swapping taking place.  If the graphics are the same endian as the CPU, no swapping should occur.  I ran into a similar terminology problem in SDL with a friend insisting that his Radeon 7000 on his PC was big-endian.  It is not, it just uses the same endianness for the graphics card and the CPU so no swapping was necessary.  They were both little-endian.
The _LE versions are because the PixFmts refer to the bitmap data being in big endian format in memory, for which the normal version would need to do endianness conversion before applying the shifts/masks. on this platform it is in _LE in memory also so we don't need the conversion hence using the _LE version of the call). would use _LE (if it's really little endian 16 bit mode).

 
What is the bare minimum needed to implement a framebuffer based gfx driver, with our software handling the rest?

Have tried with just a gfx class that only expose new/dispose/newbitmap - and having an onscreenbitmap used only for the framebuffer itself (with all other bitmaps being chunkybm, and the framebuffer's superclass also being chunkybm), but that alone isn't enough it seems?
You can use workbench/hidds/sm502/ as your example - it is as simple as I could make it.
So, AROS creates the framebuffer bitmap (verified this) -&gt; so surely it should be capable of then rendeing into it? I don't actually create the framebuffer &quot;bitmap object&quot; myself - only as a result of being asked to. The code I currently have on SVN seems to create the framebuffers bitmap object fine, but then crashes in intuitions DisplayDriver callback.  In particular it crashes performing the getattr on the system default pointer. don't expose MEMF_CHIP in an allocatable form so AllocSpriteData was failing (and other code later doesn't check if the values are valid == illegal memory accesses) 

So far have -:

vc_init: queries the gpus memory, and sets up a fake memory handler for it, then adds the bootmode driver and returns saying all is well
vc_gfxhidd:New: sets up some fake syncmodes to test with and creates the real gfx object.
vc_gfxhidd:NewBitmap: checks if its a framebuffer and uses the onbitmap class or uses the chunkybm class otherwise
vc_onbitmap:New; creates a chunkybm object and then pushes the real framebuffer address into it as the buffer,

vc4 had v8adds, v8subs, v8muld, v8min and v8max which operated on four 8bit uint values packed into a 32bit register. Multiplication was in the range 0.0 to 1.0 and addition/subtraction saturated. There were also a range unpacking/packing modes that allowed you to pack and unpack 8bit values into 32bit registers. 

RasPi has to speak to the &quot;operating system&quot; which runs on the GPU itself and request/free memory - it cant directly manage it itself, and so the managed functions were used to wrap these calls.

The Arm and GPU share memory space. The framebuffer is shared. The Arm can write a pixel and it will appear on the screen (through GPU hardware) without flushing/copying being required.

The GPU can composite multiple FB's in real time - so you have a number of surfaces defined which are rotated etc and  composited in real time to the output. Copying can map from the address space of the Arm to the flat space of the GPU which takes some code, but I don't think whole buffers are copied.

The DMA hardware can also access the whole memory space and can perform 2D fills and blits (no blending). This is documented in the peripheral spec posted. The DMA is just an Arm accessible peripheral and can be set up with low latency (e.g. microseconds).
must use a 0xc0000000-based bus address to access SDRAM, yet non-DMA access should go via a 0x0-based bus address. 
For 2D dma, set TDMODE, and the spec says &quot;interpret the TXFR_LEN register as YLENGTH number of transfers each of XLENGTH, and add the strides to the address after each transfer.&quot; so set STRIDE to pitch of the image, the width is XLENGTH and height is YLENGTH. You would fill by not setting the SRC_INC and point source to your fill data.

The DMA cannot see the ARM's L1 cache, so you would map the framebuffer with ioremap_nocache. Depending on where the source data comes from, it may need an L1 cache flush. The DMA can see the L2 cache. Use 0xC0000000 bus addresses when L2 is disabled and 0x40000000 bus addresses when L2 is enabled. (actually just call virt_to_bus and you'll get the right address out).

openGLES/openVG has high latency. Writing to framebuffer then reading it back is very inefficient (e.g. milliseconds). If you can drive it a unidirectional way, just streaming commands at then that is efficient. openVG is not implemented on top of openGLES - it uses the same hardware but as a first class interface

To improve the Gfx driver, we will need a DMA resource implemented so can use to perform DMA operations. The Gfx driver will need this to perform blits.


Actually MEMF_CHIP has to present, for historical reasons.
This has been never fully agreed upon, but in ports i wrote i exposed the whole memory as MEMF_CHIP. The idea behind this is that CHIP is originally the memory where graphics and sound data can be put. On non-Amiga platforms there are no restrictions on this, so the whole memory is CHIP.
Yes, many old software can misbehave with CHIP memory size larger than 2MB. But this actually applies only to m68k AROS which is going to run m68k binaries. In other cases it's quite logical to fix the program when porting.

As to original question: yes, it's enough to have a framebuffer bitmap (one with aoHidd_BitMap_FrameBuffer set to TRUE) and PutPixel routine. It framebuffer can be served by chunky bitmap class, then you can simply create chunky bitmap with your own buffer (see how VESA driver does this). Chunky PutPixel is already there.

struggling to determine what is the correct pixfmt to use for the 24/16/15 bit gfx modes on the RasPi.  AFAIK it uses RGB565, for 16bit but im unsure what shifts etc should go with it? suffice to say Im getting the wrong colors so far lol.

&lt;pre&gt;
redmask: 0x0000F800
greenmask: 0x000007E0
bluemask: 0x0000001F
alphamask: 0

redshift: 16
greenshift: 21
blueshift: 27
alphashift: 0
&lt;/pre&gt;

It should likely be vHidd_StdPixFmt_RGB16_LE

This stuff is a bit confusing.  The &quot;names&quot; of the stdpixfmts are based on the layout in memory,
ignoring endianess. So for example:

ARGB32: will be 0xAA 0xRR 0xGG 0xBB in memory on both big endian and little endian machines.

The shifts and masks OTOH are based on pixel access (ULONG in this case), so differ depending
on whether you run on big endian machine or little endian machine (that's why there's stdpixfmt_le.h and
stdpixfmt_be.h in rom/hidds/graphics/).

With the 16 bit pixel format it's even more confusing, as for example it's impossible on little endian machine
to describe RGB16 with shifts/masks alone. That's why there's vHidd_PixFmt_SwapPixelBytes_Flag.
(RGB16 == RRRRRGGG GGGBBBBB in memory, and for pixel (WORD) access on little endian machine it needs to
be accessed as GGGBBBBBRRRRRGGGG).

The shifts btw indicate how much to shift the component to the left (!) so that it is moved to the highest bit (31).

The aHidd_PixFmt_StdPixFmt you specify will be ignored most of the time, because when the pixelfmt is registered,
the gfx hidd checks if there's an identical pixfmt (shifts/masks/etc., but ignoring pixfmt-&gt;stdpixfmt) already in the system,
and if so, it uses the already existing one and does not create a new one.

In theory it would be better if gfx drivers could simply/only specify a StdPixFmt without all the shifts/masks stuff when the
gfx driver uses pixfmt which matches one of the stdpixfmts exactly. Another possibility would be for gfx drivers to use
HIDD_Gfx_GetPIxFmt(stdpixfmt_gfx_driver_wants_to_use) and then peek shifts/masks from it and fill out a pixfmt
tag list based on that.
15bit very blue/green: Try to pass same shifts/masks/etc. as in 16 bit pixfmt (maybe you think it's using 15 bit R5G5B5
(or swapped) but it's actually still using 16 bit R5G6B5 (or swapped).
 aHidd_PixFmt_StdPixFmt you pass is mostly ignored. It's the shift/masks/etc. that count.
But I would still pass the correct one (_LE) == whatever rom/hidds/graphics/stdpixfmts_??.h uses
in the entry where you have looked up shifts/masks/etc.

Use the shifts/masks/etc. from the entry in stdpixfmt_le.h (if you are running on little endian machine) or stdpixfmt_be.h (if you
are running on little endian machine) that matches the pixfmt that its meant to be.

0xAA,0xRR,0xGG,0xBB on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_BGRA32)

0xAA,0xRR,0xGG,0xBB on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_BGRA32)

it feels like AROS trashes the alpha component, otherwise it should be 8A8R8G8B.

read on the subject suggest its in 1x5r5g5b (x is ignored) to keep 16bit alignment .
 
Suggests to me that wrong shift/mask are being applied - however going by the 16bit versions it all looks correct to me so I am really confused as to what is happening.

The output image looks to have too much green/blue, and very weak red.


 Kickstart 

The  idea  is  to minimize amount of archirecture-specific modules to make the user's  life  easier.  So,  the kickstart was split into 'base' (which  does  not  contain anything machine-specific) and 'BSP' (Board Support Package) which contains all hardware-specific stuff. This  way,  for  example, distribution makers can save up space on CD and  make  CDs with multiple platform support. Different configuration would load the same base with different BSP's.

Next  there  was some part which is entirely missing on hosted. These are   filesystems.  Hosted  ports  do  not need them to boot up, so on hosted   they  are  left  out.  At  the  other  hand,  they  are  also architecture-agnostic.  So  i put them into 'FS' package (standing for 'filesystem').


 USB 

Poseidon  is  one  more  big part. I made it into separate package in order to allow users to omit it if they don't need it (for example, to run  on retro PCs without USB). Personally i have one. Again, Poseidon is  hardware-agnostic (well, there are USB drivers but HCIs are pretty standard).

AFAIK its HCI 1.0 compliant but not familiar enough with poseidons drivers, nor USB, to just hack away at the existing code.  Perhaps once i'm more familiar with the workings I can merge in the changes needed to get it operating but for now I will focus on getting it running.  Also our drivers have known issues so perhaps a fresh set of eyes might shed some light on what is going wrong.

Another interesting question is whether Poseidon can operate on device side. Is it flexible enough? How similar is being a USB host and USB device? think it will need a bit of work on Poseidon's side.  Until then I will force the driver into Host/Master mode in the init code, but leave open device etc to configure the chipset for either's use - and look at trying to add support for working in Device/Slave mode &amp; switching modes once it's up and running.

Actually USBROMStartup is some kind of kludge. Can there be any alternative? Could device drivers be self-installing, like our HIDDs? This would get rid of need to list them in USBRomStartup.

* Model A and B limited to 150 mA per port. 
* Model B+ and Pi 2 introduced configurable 600 mA to 1.2 A support over all ports - anything above that requires a powered USB hub.

Implementing the hardware driver that Poseidon uses to interact with the USB components.

Have code in place to (try) and initialise the USB chipset, and configure host/device mode operation (though AFAICT Poseidon doesn't support device mode). Started to get the &quot;virtual&quot; root hub written for the single USB port so that Poseidon should at least list it correctly in the GUI - and try to interact with it to find peripherals.


The BCM2835 uses a soft IP block from Synopsys’ DesignWare library (DWC), specifically the block is called dwc_usb_2_0_hs_otg_subsystem-ahb_se (“USB 2.0 Hi-Speed OTG Controller Subsystem w/AHB Interface SE”).

There is no public documentation for this, and pretty much zero chance of anyone getting hold of it even with NDA. However, there's a Linux driver written by Synopsys ([https://github.com/raspberrypi/linux dwc_usb]). Specifically directories [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_common_port] and [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_otg].

The Synopsys code is actually under a fairly permissive licence – it's not GPL, it's similar to BSD (’don't sue us if it breaks’ is pretty much the only clause). So this should not be a barrier to porting the code.

The code is really well written, with a nice partition between the work done by the driver (dwc_otg, which is fairly involved, given the host does more work than a conventional EHCI driver), and the interface to Linux (dwc_common_port).

Probably only need provision of relevant changes to dwc_common_port. Other things to consider....

* Provision of necessary headers to get it to compile
* Provision of necessary functions (main issues are wait queues, threads, work queues, tasklets, timers, spinlocks and mutexes (multithreading) )
* Interfacing between USB stack and the driver. dwc_otg/dwc_otg_hcd_linux.c looks like the place to start.

the Linux bits of the headers are only required for the dwc_common_port library. dwc_common_port includes a variety of crypto functions which are not used – it appears to also be used for ultrawideband (UWB) and wireless USB (WUSB) drivers where crypto will be an issue, but it isn't going to be for plain wired USB.

Every USB driver acts as an USB hub as well in order to let Poseidon control the state of USB ports. The code there was reading status of the only USB port in Raspberry's CPU but when changing the status it erroneously deleted some of the status bits, including the port enable one. It was so because those bits in the status register are of a type Read/WriteToClear. It means, if one does not want to change their value from 1 back to 0, one has to actually write the 0 value. Very practical thing e.g. in interrupt handlers, where one reads the interrupt status register to learn what was the interrupt reason, and writes it back to the same register in order to clear the interrupts. 

After fixing that code it turned out that the communication was still unsuccessful. Apparently the USB device was not understanding the host for some reason. That should not happen since the request sent was one of the standard ones implemented by virtually anything with an USB connector, assumed that Poseidon clears the data caches before forwarding the work to the USB drivers but that's the responsibility of the driver itself. 

The USB device responded and acknowledged the transmission! But why were all the request sent after address change failing with timeout? They should not. Once again, address set is supported just by anything. Tried to contact the device at address 0 once again and there it was, still responding properly. The enlightenment came. The bus address for DMA transmissions was, as it is in many bare metal USB implementations, just the pure memory address of the buffer as seen by the ARM cpu. Have &quot;prefixed&quot; it with the real location of uncached RAM and booted AROS once again. 


Trident saw this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

and this:

    Product     : Vendor: Vdr=0424/PID=EC00
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 255
    SubClass  : 0
    DevProto  : 1
    VendorID  : 1060
    ProductID : 60416
    DevVers   : 0200

and even this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

What are these things? The first one is USB hub built in the Raspberry. Thanks to this one the Pi machines (with exception of Pi0 and computing modules) have more than just one single USB port. The second one is the network chip in raspberry, the third one is my USB SD card reader which have just connected to see what happens. AROS tried, of course, to boot from it ;)

So, the first step towards working USB is done. The control transfers are working as you can see above. Next step is to implement bulk and interrupt transfers, having the basics in place. Finally some error handling will be added and USB for Pi will be as complete as the PC version. 

[http://www.raspyfi.com/raspberry-pi-usb-audio-fix/ Issue with USB Audio]


 Audio 

The Pi 4B is the only Pi that can output HD Audio as an HD Audio passthrough bitstream, and it does it over HDMI. It's possible to use the two HDMI output for separate HDMI video and HDMI audio outputs to allow UHD HDR video and HD Audio with non-UHD HDR compatible AVRs. 

The Pi3B+ and earlier will decode to PCM 5.1/7.1 and output over HDMI.  HDMI is the only interconnect that has a standard for carrying Dolby True HD, DTS HD MA etc. as a bitstream - you can't carry it as a bitstream on any other interface.

Pi3 and Pi4 audio jack output derived from 12bit pulse width modulation is relatively poor. For better, choose USB Audio or I2C versions. 

[https://github.com/raspberrypi/linux/tree/rpi-patches/sound/arm audio] and its [https://github.com/raspberrypi/firmware/issues/2 very high speed message passing interface type of thing VCHI] 

The Model B+ added an additional voltage regulator for the audio output and an additional output driver to drive low-resistance loads like headphones. However it is still using pulse-width modulation (PWM), which has a major impact on sound quality

the old Raspberry Pi used a linear voltage regulator to provide the 3.3V to many of the components on the board while the new one uses a switching regulator. Both can perform reasonably well. However switch mode power supplies often show higher noise figures

Analogue audio

Audio over HDMI rev 1.3 &amp; 1.4


 Ethernet 

10/100 BaseT Ethernet RJ45 socket


 GPIO 

GPIO shouldn't be too bad but bear in mind it is already accessed in places so they would need to allocate pins etc through it (e.g. sdcard to flicker the activity light, serial debug to output data on the GPIO pins)

Probably a resource rather than a device...

Started an i2c driver that will need to allocate GPIO pins. Feel free to work on it if you are interested ;p


 GPU graphics with 2D and 3D acceleration 

Sadly none yet for 32bit but for 64bit... 


 Miscellanous

hdmi issues

Setting the hdmi_force_hotplug=1 makes sure the Pi believes the monitor/TV is really there.

You might also need to set config_hdmi_boost=4 or even higher (up to 9) if your display needs a stronger signal.

If the display is a computer monitor or newer tv, use hdmi_group=1 (auto HDMI use) and if it is an older TV, try hdmi_group=2 (for DMT formats, i.e. for PC monitors) then you HAVE to &quot;set hdmi_drive = 2 to enable HDMI output as this forces HDMI mode rather than DVI mode

Do not set hdmi_safe=1 as that overrides many of the previous options.

Using a shorter or better quality HDMI cable might help. Make sure your Pi's power supply delivers 1 A and not 500 mA.
If you see a problem with the red colour - either absent, or interference - then try a boost

composite video

changing the RCA cable, then the composite port worked out of the box

Boot it as you are doing, without HDMI. If you now plug in the HDMI, do you get the image? In other words, does the Pi think HDMI is connected even when it isn't?

Rename all the files in the first partion of the card except bootcode.bin, start.elf and fixup.dat  What's the result?

Put back config.txt What's the result?

for PAL mode   sdtv_mode=2

dmi_ignore_hotplug Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached
hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected

&lt;pre&gt;
# NOOBS Auto-generated Settings:
#hdmi_force_hotplug=1
#config_hdmi_boost=4
#overscan_left=24
#overscan_right=24
#overscan_top=16
#overscan_bottom=16
#disable_overscan=0
start_x=1
gpu_mem=128
&lt;/pre&gt;

tvservice -c &quot;PAL 4:3&quot;

&lt;pre&gt;
/opt/vc/bin/tvservice -s   or tvservice -s 
state: HPD high|HDMI mode|HDCP off|composite off (0x12001a), 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m CEA
Group CEA has 1 modes:
(native) mode 16: 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m DMT
Group DMT has 0 modes:
&lt;/pre&gt;

sudo amixer cset numid=3 1

forces the audio to the headphone jack, even with the HDMI video output plugged in

config.txt

the hdmi_ignore_edid_audio=1 option sems relevant as it should tell ALSA that the only available audio is analog, no matter what the display says

There are several different ways that these 4 pole (ring) composite analog cables can be wired up, so some work great in some applications and can be a waste of time in others.

What is needed for the Raspberry Pi B+ and above, which like many camcorders needs the ring contact next to the base contact to be the ground.


The wiring for the 4 pole are:

TIP (LEFT AUDIO CHANNEL)

RING 1 (RIGHT AUDIO CHANNEL)

RING 2 (GROUND/EARTH)

RING 3 BASE/SLEEVE (VIDEO) YELLOW

Most Apple based Players and the Microsoft Zune (TM) are wired this way.

Most analogue camcorders are wired this way as well, where the ground in on Ring 2 will work with the Pi although you may need to swap your Video plug with the Right Audio plug.

Nearly all other MP3 players are not wired this way, the ground is on another ring ie the wrong one.


External devices

* Camera Module Omnivision ov5647 Sunny 5MP (NoIR version) V1.3 - NoIR at 850&amp;nbsp;nm, peak at 880&amp;nbsp;nm and trails off at 940&amp;nbsp;nm wavelengths 
* Camera V2 Sony IMX219 V2.1 8mpixel 8MP 8megapixel - 3280 x 2464 pixels - video at 1080p30, 720p60 and 640x480p90 - wider field of view, 62 vs 54 degrees horizontally - 
* Branded WIFI usb BCM43143 dongle

N.B.  dreaded error after changing cameras (stupidly without turning off the power first) and lasted through several power cycles.  It can be a bad 15-pin FFC ribbon cable, when swapped, camera(s) and the Pi itself are working OK. It can be an instance of a cold solder joint on the CSI connector on the pi board.  the camera can be detected (that's done via I2C) but may still not be able to receive image data (done via CSI-2) if something is broken. CSI-2 is uni-directional. Control is generally done via I2C. 
The CSI-2 receiver always writes to memory, not direct to the ISP. That's the way the Broadcom architecture works as it allows multipass processing easily. GPU memory is accessible from the ARM. Processing using the QPU graphics processors may be possible.  currently the only supported sensor is OV5647 and IMX219.  The linux drivers are all in the firmware blob, else you'd  be looking at at least a man-month of work in a fully fledged imaging lab to do a decent tuning of the camera modules' ISP parameters. 
Static electricity maybe an issue for the camera module and slightly less for the pi board.


== References ==


===Good sites to visit===

*[https://github.com/raspberrypi/firmware/tree/master/ Raspberry Pi Firmware build] 
*[https://www.raspberrypi.com/documentation/computers/software-sources.html Documentation] 
*[https://rpilocator.com/ RPiLocator] 


Linux only
*[https://github.com/raspberrypi/linux Raspberry Pi Linux Build] 
*[https://dietpi.com/ DietPi] 
*[http://www.tinycorelinux.net/ports.html piCore]
*[https://wiki.alpinelinux.org/wiki/Raspberry_Pi Alpine Linux] 
*[https://github.com/armbian/build Armbian] 


*[ FydeOS]
*[ TwisterOS based on ChromiumOS] 
*[https://note.com/jamesmondo/n/nc76e31402be8?hl=en BSD] 


*[https://www.raspberrypi.com/software/operating-systems/ PiOS Lite] and then [https://hstwb.firstrealize.com/ HST] 
*[ PiMiga for pi4 and pi5] 
*[ amibian for pi2 and pi3] 
*[ retropie pi1 and 2] 


Other alternative lighter smaller than Pi OS 
*[https://aros.sourceforge.io/nightly1.html Aros 64bit ARMV8 single core] 
*[https://www.riscosopen.org/wiki/documentation/show/Welcome%20to%20RISC%20OS%20Pi RiscOS on Pi3 and Pi4]
*[https://github.com/michalsc/Emu68 ARM based realtime JIT 68k for amiga computers] 
*[https://github.com/JJDSNT/bellatrix/releases/ Alternative use of Emu68 on Pi3b] 
*[https://github.com/stevereaver/uaos uaOS with Emu68k] 
*[https://github.com/aros-development-team/AROS/commit/f80a268607dfae81b2db94755ab4e4d31ccb72d6 m68kemu library reference] 
*[ HaikuOS]
*[https://github.com/raspberrypi/noobs NOOBS] os loader with successor [https://github.com/procount/pinn PINN] 
*[https://github.com/maxnet/berryboot berryboot]

*[https://github.com/brianwiddas/pi-baremetal Bare Metal Access on Pi 32bit] 


Testing procedure is put sd card in, connect board to board if necessary, plug in hdmi and then power nothing else is done especially CSI DSI etc 

[https://www.raspberrypi.com/documentation/computers/compute-module.html CM5] has the same 55mm x 40mm 2x100pin connectors form factor as the CM4 but [https://www.epdtonthenet.net/article/214508/Key-Considerations-When-Migrating-from-Raspberry-Pi-CM4-to-CM5.aspx some pins and other small things] have changed. Will need the [https://raspipcb.com/tech-blog/raspberry-pi-cm4-vs-cm5-difference-in-booting-from-sd-card/ right IO board to suit] 

*Green [ Raspberry Pi Compute Module 5 IO Board REV2 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1967]] - untested 
*Green [ RPi Compute Module 5 IO board REV1 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1751]] - untested 
*Black SupTronics Geekbord X1500 CM5 IO Carrier Board - untested
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*[https://sipeed.com/nanocluster Sipeed NanoCluster] - untested up to 7 CM5 
*Green BentoIO CMX0 - untested 
*Box EDATec ED-CLAWBOX - untested 
*Home Assistant Yellow - Kit with PoE with Raspberry Pi Compute Module 5 - untested 
*Blue [https://www.waveshare.com/wiki/CM5_PoE_BASE_A Waveshare CM5-PoE-BASE-A] - untested 
*Box  Waveshare [ CM5-POE-BOX-A] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-B Waveshare CM5-IO-BASE-B] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-A Waveshare CM5-IO-BASE-A] - untested 
*Blue Waveshare [https://www.waveshare.com/wiki/CM5-NANO-B CM5-NANO-B] - untested 


*[https://carboncomputers.us/products/pi-flux piFlux]
*[https://carboncomputers.us/products/ Zitaotech Hackberry] CM5 lite only - 
*Portable [https://www.waveshare.com/pocketterm35.htm Waveshare PocketTerm35] with Pi4B or Pi5 - untested 
*Box [https://www.clockworkpi.com/uconsole ClockworkPi uConsole][https://www.youtube.com/watch?v=EtI_bAahbR8 CM4 into an adapter or CM3 into so-dimm - Cyberdeck] - untested 


*Green RPi [https://datasheets.raspberrypi.com/cm4io/CM4IO-KiCAD.zip Compute Module 4] [https://datasheets.raspberrypi.com/cm4io/cm4io-datasheet.pdf IO board] V1.4 [https://datasheets.raspberrypi.com/cm4io/CM4IOUSB3-KiCAD.zip USB3] [https://datasheets.raspberrypi.com/cm4io/cm4iousb3-appnote.pdf CM4ISO] [https://datasheets.raspberrypi.com/cm4/cm4-datasheet.pdf Dual100pin] (2020) aka Development Platform Board - untested 
*Purple Pi Hut Cytron CM4 Maker Board - untested 
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*[ KubeSail PiBox mini 2] 
*Home Assistant Yellow with Raspberry Pi Compute Module 4 - untested 
*[ Turing Pi V2] - untested CM4 with 260-pin SO-DIMM socket adapters and/or nvidia jetson nanos - untested 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-C Waveshare CM4-IO-BASE-C] - untested but binary blobs Rev01 Rev02 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-B Waveshare CM4-IO-BASE-B] - untested but binary blobs 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-A Waveshare CM4-IO-BASE-A] - untested but binary blobs 
*Blue [https://www.waveshare.com/wiki/CM4-NANO-B Waveshare CM4-NANO] - untested but usb and audio turned off or rerouted 
*Black [ Seeed Studio with BigTreeTech BTT pad 7] - bin blobs? 


CM3 has a 200 pin sodimm ddr2 connector form factor but not electrically SC0028, SC0029 
*Blue [https://wiki.geekworm.com/CM_IO_Board Geekworm RPi Compute Module IO Board] [https://github.com/geekworm-com/cm-io-board CSI DSI] with CM3 in ddr2 slot underside - '''works''' if SW1 on but CM3+ '''does not''' 
*Green [https://cdn-shop.adafruit.com/product-files/3442/CMIO_schematic.pdf RPi V3 IO board CM3IO] and CM3 Lite - untested 
*Green [https://turingpi.com/ turingpi v1 cluster] - untested up to 7 cm3 7xlan9514 12V discontinued, 3 x Pi4 homelab maybe better 
*Blue [https://www.waveshare.com/wiki/Compute_Module_PoE_Board Waveshare Compute Module PoE Board] and CM3 lite (if not lite, write files to internal eMMC fat32) '''AVOID''' bin blobs 
*Blue [https://www.waveshare.com/compute-module-io-board-plus.htm Waveshare Compute Module IO Board Plus] [https://www.waveshare.com/wiki/Compute_Module_IO_Board_Plus wiki] [https://forums.raspberrypi.com/viewtopic.php?t=235695 pin settings] with CM3+ Lite - '''AVOID''' binary blob 


*[ Pi02w on Geekworm SupTronics X305 Raspberry Pi Zero IO Baseboard] - untested 
*[ Spotpear Pi Zero 2w to Pi3b format-ish] - untested 


*[ pi-top v4] box has 128x64 oled display, micro hdmi, 19Whr battery with pi4 and 15V PD 36W min needed 
*[ pi-top v3] three green pieces, heatsink covers most of the base tray, pi-top hub mk1 lhs and Pi1B Pi2b Pi3b rhs secured from below, black rounded strip with pi-top above keyboard, 13.3&quot; HD 1366 x 768 display, small touchpad, 
*[ pi-top Model 2.0] pi-top on bottom bezel of 14-inch green laptop, large trackpad, keyboard slide down to reveal main system hub on slide rails moved to the right, Raspberry Pi3b screws down, hub slides in, 18V 2.5A 45W charger brick, battery 11.1V 3500mAh 38.85Wh and storage PiTopOS 
*[ Pi-Top CEED Raspberry Pi Modular Educational Desktop with RPI3] monitor 
*[https://www.indiegogo.com/en/projects/jesselozano/pi-top-a-raspberry-pi-laptop-you-build-yourself Pi-Top v1] wedge laptop with RPi2 


&lt;pre&gt;
2008 Trustees collected for Foundation
2009 Pi Foundation charity status gained 
2010 
2011 First Raspberry prototypes 
2012 First boards go on sale at CPC and RS. The Model A and B 700 MHz Arm11 - February 29th BCM 2835
2012 First million sold - more than the 10,000 original planned and anticipated 
2013 First Alpha Experimental builds of AROS Native for the 32bit Pi 
2013 Pi Trading launched making grants available, providing in house educational resources and Pi Academy for teacher training 
2013 Over two million sold 
2014 Over three million sold 
2014 Pi 1 Model B+ introduced that moved composite video to audio jack and same half gig of memory 
2014 Pi Model A+ v1.1 no ethernet and 1 usb - a little smaller - 
2015 Over four million first gen pis sold  
2015 Pi Zero 1.2 BCM2835 first production revision released with no camera port 
2016 Pi0 1.3 released with camera csi connector 
2017 Pi Zero W v1.1 1GHz Pi0W, single-core 32bit CPU BCM2835 released with Cypress CYW43438 wireless 
2020 Raspberry Pi Pico SC0919 with RP2040 32-bit 2Core ARM Cortex-M0+ up to 133 MHz - 264KB of SRAM and 2MB of on-board QSPI Flash - 
2024 Raspberry Pi Pico 2 with RP2350 2Core 32bit Arm Cortex-M33 and 2core open-hardware [https://github.com/wren6991/hazard3 Hazard3 RISC-V] 

2015 Pi 2 Model B v1.1 BCM2836 900/600 MHz ARM Cortex-A7 Armv7 quad 32bit, 32bit VideoCore IV GPU - 1Gb RAM - 5V 2A micro usb - SMSC LAN9514 chip - 
2015 Over a million pi2s sold 


2015 Raspberry Pi 2 Model B version 1.2 Pi2bv1.2, aka Pi2B2 has armv8 BCM2837 underclocked to 900Mhz without wifi/bluetooth module 
2016 Pi 3 Model B - Broadcom BCM2837 SOC four 64bit ARMv8 Cortex-A53 1.2GHz 32bit 1080p VideoCore IV GPU - 1Gb DDR2 - bluetooth 4.1, Cypress CYW43438 wireless 802.11n - 4 x USB2.0 ports - 5.1V 2.5A - SMSC LAN9514 chip 
2016 PIs total over 10 million worldwide 
2017 Compute Module 3 CM3 with BCM2837B0 armv8 Quad 64-bit - small 67.6mm x 31mm board which fits DDR2 SODIMM connector but not electrically compatible which plugs into needed IO board - beware of the I2C protocol issue 
     1Gb LPDDR2 RAM - Lite or 4Gb Emmc storage 
2017 12 million pis sold in total 
2018 Pi 3 Model B+ - 4c A53 BCM2837B0 1.4Ghz - 1Gb, wireless 802.11ac, gigabit ethernet (300Mbit/s) and bluetooth 4.2 - power over ethernet - 4 x USB2.0 ports - Microchip LAN7515 chip 
2019 Over 15 million sold 
2019 Pi 3 Model A+ with BCM2837b0 Cortex-A53 64-bit SoC @ 1.4 GHz with 512Mb LPDDR2, 1 usb2, 1 hdmi, 1 micro usb 5V 2A - no ethernet - 
2019 Raspberry Pi Compute Module 3+ CM3+ - Broadcom BCM2837B0 1.2Ghz, Cortex-A53 (ARMv8) 64-bit SoC on DDR2 SODIMM mechanically compatible only factor - IO board required 
     1Gb DDR2 and 8GB, 16GB, 32GB or a Lite variant without eMMC 
2021 Pi zero 2 (w or no W) RP3A0 quad 1GHz Cortex-A53 64bit BCM2710A1 512mB SDRam 
2025 edaTEC CM0 ED-CM0NANA with additional dev board with quad 1Ghz A53 with 512Mb Raysan RAM, 2 USB2 and 10/100 ethernet - pico castellated edge
 

2019 Pi 4 Model B v1.1 RPI4B - BCM2711B0T quad 64bit A72 1.5GHz, 4K VideoCore VI, AC wifi, Bluetooth 5.0, GbE Broadcom BCM54213PE (PHY ID 0x600d84a2), 2 micro hdmi decode up to 4K, USB-C 5.1V 3A power, 2xVLI VL805 USB 3, 2xUSB 2.0, 2GB 9LDWW D9WHZ or 4GB 9FDWW D9WHV, 8GB 0AA47 D9ZCL ddr4 ram 
2020 Silent Pi 4 v1.2 upgrade with more USB-c psu support 
2020 PI400 BCM2711C0T 1.8GHz 4Gb DDR4 inside keyboard, 5.1V 5A 27W usb-c psu, 2 micro hdmi, external ide style 40pin gpio, no audio port - 
2020 Raspberry Pi Compute Module 4 BCM2711B0T on new 55mm x 40mm 2x100 pin form factor with extra breakout IO board 
     CM4101000 1Gb RAM Lite SOM 
     CM4102000 2GB RAM Lite 
     CM4104000 4GB RAM Lite 
     CM4004008-4GB-RAM 8GB-EMMC SOM System on Modules 
     CM4104032 4GB RAM 32GB emmc 
     CM4108000 8GB RAM Lite 
     CM4008016 8GB RAM 16Gb eMMc
2021 Raspberry Pi SC0763 Compute Module 4S CM4S with ddr2 sodimm pinouts but not electrically the same with suitable IO board extra cost - 
     CM4S01000 1GB RAM Lite
     CM4S01008 1GB RAM 8GB eMMC Flash
     CM4S02000 2GB RAM Lite
     CM4S04000 4GB RAM Lite
     CM4S04016 4GB RAM 16Gb KLMAG1JETD-B041 
     CM4S08000 8GB RAM Lite 
2021 Pi 4 v1.4 BCM2711B1 upgraded power regulator, to deal with 8gig of ram being more power hungry 
2021-48 Raspberry Pi 4 model B v1.5 2GB 


2023 Pi 5 v1.0 BCM2712 Quad A76 @2.4Ghz - VideoCore VII - no audio socket - dual 4k from mini hdmi - fan connector - 5.1V 5A psu 
2024 Pi 5 2GB DDR4 version uses BCM2712D0 
2024 Pi-500 with 8Gb LPDDR5 and membrane keyboard 
2024 Pi 5 v1.1 
2024 Raspberry Pi Compute Module 5 CM5 BCM2712 55mm x 40mm form factor with additional IO board 
     CM5004000 04GB RAM 0GB eMMC Lite
     CM5008000 08GB RAM 0GB eMMC Lite
     CM5016000 16GB RAM 0GB eMMC Lite
2025 Pi-500+ with 256GB NVMe storage, 16GB LPDDR4 RAM, and Gateron KS-33 Low Profile Blue mechanical keyboard switches 
2025 Pi5 1GB DDR4 announced 


2022 PiOS linux goes 64bit 
2024 Pi Trading IPO stockmarket stock exchange listing 


2026 April and May Aros 64bit fixed, added AHI audio, VC4 gfx started, usb functions added to rom  
2026 June and July Aros 64bit usb2otg started, dma.resource, sdio.resource, bwfm.device wifi added 
2026 Late July daily 64bit Pi3 LE little endian builds start 
2026 August Pi 4, 400, 5 and 500 DTBs added, expanding existing support and wifi for Pi4 and Pi5 
2026 August Pi5 HAT+ nvme and HDMI, AHI RPiI2S added, Pi4 HVS5 video scaler started, 
2026 
2027 


2028 Pi 6 
&lt;/pre&gt;


The vcgencmd can be used to inspect and dump the current system configuration. 
vcgencmd runs on top of VCHIQ as an RPC. The mailbox interface is an alternate but much simpler RPC. 
VCHIQ is a bridge (queue) between the CPU and the GPU so they can communicate with the firmware. 

Loads of [https://github.com/6by9/rpi3-gpiovirtbuf/blob/master/rpi3-gpiovirtbuf.c mailbox] which uses the GPIO control calls. [https://github.com/raspberrypi/firmware/wiki/Mailboxes may also be of interest] 

A fair number of vcgencmd examples (search for vc_vchi_gencmd_init). [https://www.raspberrypi.org/forums/viewtopic.php?t=229203#p1406112 sends the relevant vcgencmd commands] to update the scaling kernel, but the [https://github.com/raspberrypi/userland/blob/master/host_applications/linux/apps/gencmd/gencmd.c command] is just a text string. Parsing and execution of the instructions is performed by the VideoCore firmware. 

The Raspberry Pi runs two separate operating systems: Linux/Aros on the ARM, and a threedx RTOS called vcos running on the Videocore 4 VPU: vcos is commonly called &quot;the firmware&quot;. Vcos is tasked with performing certain system services, for example running the display and audio outputs. The VCHI driver provides an interface to allow drivers to talk to vcos. 


Doubtful, on any [https://www.web3d.org/ Web3d] [https://developer.mozilla.org/en-US/docs/Web/API/WebGL_API WebGL] or [https://github.com/immersive-web/webxr WebXR] [https://developer.mozilla.org/en-US/docs/Web/API/WebXR_Device_API Device API] [https://developer.mozilla.org/en-US/docs/Web/API/XRInputSource XRInputSource] support. Hopefully, never/limited support features like location, peer-to-peer, invasive web apps, unwarranted storage, payments, proprietary video streaming etc 

*spreadsheet [https://git.sheetjs.com/sheetjs/sheetjs sheetjs] [https://github.com/mleibman/SlickGrid SlickGrid] [https://github.com/6pac/SlickGrid SlickGrid] [https://github.com/jspreadsheet/ce jspreadsheet ce] [https://github.com/dream-num/Luckysheet Luckysheet] [https://github.com/ruilisi/fortune-sheet fortune-sheet] [https://github.com/dream-num/univer/ univer]  probably without xlsx support 
*presentations [https://github.com/impress/impress.js/ impress.js simplified] [https://github.com/bwlewis/slides slides] [https://zenomt.github.io/mdslides/ github markdown slides] [https://github.com/Patternslib/slides Patternslib slides markdown] probably without pptx support 
*weather [https://github.com/kaushalsahu07/weather weather], [https://github.com/Himanshu3412/Weather-Forecast Weather Forecast],  


==Future==


[https://github.com/ARMSX2/ARMSX2 Arm pi of pcsx2] 


[https://tube.cadence.moe/ Cloudtube], [https://github.com/TeamPiped/documentation/blob/main/content/docs/public-instances/index.md TeamPiped], [], [], [], 

[https://hyperpipe.codeberg.page/ hyperpipe], [https://ytify.pp.ua/ ytify], [], [], 

[ ytdl], [https://github.com/golddominik893/liberatube liberatube]

[https://git.lolcat.ca/lolcat/4get 4get], [https://github.com/hnhx/librex librex], [], [], 


{{BookCat}}</text>
      <sha1>7igeidlgme4syt2ppo7e3iw0l7tjmck</sha1>
    </revision>
    <revision>
      <id>4676518</id>
      <parentid>4676517</parentid>
      <timestamp>2026-10-17T13:31:49Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4676518</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="106179" sha1="jrkb3xa0vkkdbksjd47u6p1p6g49g7s" xml:space="preserve">{{ArosNav}}

[[#Native]]

[[#Hosted]]

[[#Build]]

[[#Hardware]]

[[#References]]

[[#Future]]


==Introduction==


[[File:Scalos00.png|thumb|Scalos on Aros Pi3b]]

Aros aims to cover Pi 3 to 5 512Mb+ RAM 


Options to boot from using a good power source to prevent the yellow lightning symbol. 
*With Pi3b+ the max you can get is 5.1V 2.5A with micro usb.
*With Pi4 5.1V 3A with usb-c 
*With Pi5 5.1V 5A, the amps went ever upwards, even to 5.1V 9A with usb-c 


* Pi500+ keyboard wedge - working but not much tested esp [https://github.com/aros-development-team/AROS/commit/48e9c8edcca4b5c1e1fe0b1123f2129f624af67b power button] 
* Pi500 wedge with up to date bootloader via PiOS - working but not much testing esp [https://github.com/aros-development-team/AROS/commit/48e9c8edcca4b5c1e1fe0b1123f2129f624af67b power button] 
* Pi 5  - Quad A76 64bit ARMv8 and RP1 &quot;southbridge&quot; with VideoCore 7 D0 (rev1.1) - untested 
* Pi 5  - Quad A76 64bit ARMv8 and RP1 &quot;southbridge&quot; with VideoCore 7 Pre-D0 C1 (Rev1.0) - untested 
* Pi400 RPI-400 keyboard wedge - resolution changing and audio from micro hdmi0 (near 40pin) and micro hdmi1 (near usb-c psu) - Fn F10 0x5e power on and off works or held down for over 7 seconds auto shutdown - keyboard ok - wifi and lan ethernet testing - 
* Pi 4  - Quad A72 64bit ARMv8 with VideoCore 6 
* Pi 3  - Quad A53 [https://www.raspberrypi.com/documentation/computers/processors.html 64 bit] ARMv8 with VideoCore 4 with '''fan''' to prevent overheating cpu 82C+ throttling 
* Pi02W - Quad A53 64bit - boots but [https://forums.raspberrypi.com/viewtopic.php?p=2387984#p2387984 usb not working but did in the past], 


* Pi 2 - Quad 32bit ARMv6 with VideoCore 4 - mostly not 64bit compatible 
* Pi Model B+ 32bit ARMv6 with VideoCore 4 - not 64bit compatible 
* Pi Model A and B 32bit ARMv6 with VideoCore 4 - not 64bit compatible 


===Native===

* 2013-03 Kalamatee starts work
* 2015-04 Work continues with mschulz on the kernel and Kalamatee (NicJA) on gpio and usb
* 2018 [https://www.patreon.com/posts/i-owe-you-some-20956961 mschulz resume adding BE big endian support], [https://www.patreon.com/michal_schulz/posts Big endian on Pi]  
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bsek latest commits for pi 3b, 4 and 5 64bit] 
* 2026 [https://github.com/aros-development-team/AROS/commits?author=metaneutrons latest commits for Pi5]
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bitplane latest commits for ARM]


====64bit====

'''Download''' A [https://archive.org/details/piAROS Pi Distribution (Distro) has started] and the contents copied to fat32 8GB+ microSD card (there will be drawers/folders - boot c Classes Demos Developer Devs Extras etc only showing). The SD can be plugged in to the Pi. And power on. [https://pi.amiga.icu/ Repository]

'''Not recommended''' but [https://aros.sourceforge.io/nightly1.html RaspberryPi 3, 3+, 4 and 5 64bit ArmV8 nightly builds] [https://sourceforge.net/projects/aros/files/ and alternative site and nightly2] which is a test version of '''very few''' apps with both raspi-aarch64-system and raspi-aarch64-contrib can be unbz2'd to a SD or SSD as appropriate. 

64bit build works well on a single core LE little endian. Multicore [https://github.com/aros-development-team/AROS/commit/1df0747c2bda3523a43029725a709b1f377d84ec may follow]. Any issues booting could be down to the SD card so please use another SD to see if it is resolved. Remember Aros Arm uses FAT32 and Aros can detect issues with this format very acutely (once fault found, FAT 0x0FFFFFF7 bad cluster so no files written after that, no repair). Please report your experiences in the [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2138&amp;pid=15057#post_15057 Aros forum thread], [https://forums.raspberrypi.com/viewforum.php?f=179 Raspberry Pi Aros Dev and User forums], [https://forums.raspberrypi.com/viewtopic.php?p=2387984#p2387984 previous Raspberry Pi forum thread]. Any bugs or issues can be [https://github.com/aros-development-team/AROS/issues described here to fix] 


*Pi500+   untested usb3 booting or nvme ssd 
*Pi500    untested usb3 booting 
*Pi5      untested usb3 booting 
*Pi400    boots with '''USB3''' port based sata3 ssd 
*Pi4      untested (may need eeprom update from PiOS or Pi SD Imager) 
*Pi 3 B+  is pre-configured for USB sata3 boot - untested 
*Pi 3 B   may need [https://www.youtube.com/watch?v=ubnwvxF3Klc PiOS to set OTP to boot from usb - do so at your own risk] - if OTP set to usb, boot works but slower than SD card 

Speed write wise (top faster) 
&lt;pre&gt;
*NVME Pi5 untested    &gt;1000MB/sec  or faster if matched correctly 
*Sata3 ssd              500MB/sec
*SD        V90           90MB/sec  4K maybe 8K 
*SD        V60           60MB/sec  1080p 
*SD     U3 V30           30MB/sec  720p 
*SD C10 U1 V10 A1 A2     10MB/sec  minimum should be used now 
*SD C06                   6MB/sec  
*SD C04                   4MB/sec 
&lt;/pre&gt;


As a homage to the past, Aros shows a reduced number of icons but this can be changed by left mouse click in the window and then right click down to Window -&gt; View -&gt; All files

Windows can be manipulated by the top (moving) and the bottom right corner (resizing) only. 

Zune like MUI gui interface, has a unique quirk in that after changing a setting in a text box, you may sometimes need to press Enter/Return before clicking OK, Save, etc 


Double left mouse click on most picture (Developer/Debug/Tests/Datatypes), audio and video files are supported, via datatypes, by the multiview application. 
Esc escape key usually closes open windows even the desktop 

In Prefs/Appearance some decorative theming elements need work. There is a few Mason icons in /Prefs/Presets/Icons/Mason/ and the ever present default Gorilla - Icon exchange in works 

For more intensive graphics applications, you may need to edit config.txt in the root folder and change 128M to 256M to adjust more memory to graphics usage 

If your cursor should '''appear''' to vanish, fear not it is still there. Please head to the top of the screen i.e. the title bar, hold down the left click mouse and drag the screen down a little and the cursor will appear again. Then you can drag the screen up again. 


Like most amiga like OSs the audio and networking need to be setup manually 

Audio AHI prefs - Mode settings tab - needs both Music unit and Unit 0 set to RPiHDMI:16 bit stereo++  or RPiPWM:16 bit stereo++ at 44100Hz. Press '''Save or Use''' button after each choice 


For wireless, please use the Wifi prefs and already selected device bwfm.device. Press Scan and double right click on the router and enter password. You may need to setup after every power off
*if asking for password again - press cancel and go to Network Prefs, Wireless Networks tab and highlight the router line and hit the remove button and press the cancel button. Retry with Wifi prefs again 
*...waiting for an address - Disconnect and try Connect 
Until, Connected to &lt;router&gt; - 192.168.x.x 


For lan ethernet port, please use Network prefs and the following hardware is 
*lan9514    Pi3b Pi2 not supported at the moment 
*lan7515    Pi3b+ type into Device  usblan78xx.device as net0:  remove other device(s) 
*bcmgenet   Pi4 Pi400 choose for Device bcmgenet.device 
*cdnsgem    Pi5 Pi500 Pi500+ RP1 i/o for cadencegem 
 (network prefs may forget random information when rebooted) 


Summary
&lt;pre&gt;
*3b    ethernet not supported, usb ethernet not working but wifi prefs setup works 
*3b+   wifi working and ethernet works 
*4     untested 
*400   wifi and ethernet untested 
*5     wifi and ethernet untested
*500   wifi and ethernet untested
*500+  wifi works 
&lt;/pre&gt;


Type in 'aarch64' in the [https://archives.arosworld.org/index.php?function=search&amp;tool=simple search box] and you will see available software packages / apps. apkg can be used to inspect and install applications. 

[http://archives.arosworld.org/index.php?function=browse&amp;cat=network/browser amelinium web browser (JS 1.6 ES9 ECMASCript 2018)] is available with an [https://eab.abime.net/showthread.php?t=122494&amp;page=80 eab thread] reminiscent of [https://github.com/zapek/Voyager Voyager] and to a lesser extent [https://github.com/amigazen/aweb3/ Aweb JavaScript 1.5 (ECMAScript 3)] as css and javascript websites can be slow to load or resolve (no JIT) and nothing from facebook, reddit etc. 

Press Cancel at screenmode selector or -wb argument to get windowed version. You could use the Shift + Del shortcut or mouse wheel should work to delete all text at once. Html5test gives 189 (1.29), 300 (1.31), 301 (1.39) out of 555, some bigger Amiga like browsers are around 370+ but it does less better. 

You may have to delete the cache (Menu -&gt; Page -&gt; Delete cache) to fully retest big Amelinium updates or free up space. 
Be aware [https://pianetaamiga.it/en/reportage-pianeta-amiga-2026/ some site pages] can use up hundreds of MBs of cache very quickly 

 DNS lookup failed...  close browser and reboot and setup wifi again - repeat until it works again 

 youtube video and audio - js button for javascript must be on/shaded -  Settings -&gt; Soundoutput - AHI 
Any restriction to lower resolutions is due to [https://docs.invidious.io/faq/#q-where-are-the-360p480p1080p-quality-options bandwidth]. Either CPU/GPU, internet speed and/or video quality. Pi3 can expect 480p (wifi) to 720p (ethernet). Pi4 expect (wifi)  (ethernet). 

Telegram https://t.me/s/channel_name for public messages from vamped_amiga chatamigagames demoscenecracktros 

*art local js apps like dpaint.js 


There is normally no Bluetooth support for most amiga like OSs but Aros has one [https://github.com/aros-development-team/AROS/commit/6942cbfbf66426d21963a7fcd8aba6aff611a9e0 work in progress] [https://github.com/RPi-Distro/bluez-firmware/tree/pios/trixie/debian/firmware/broadcom firmware] 

*Bluetooth 4.1 BCM43430A1.hcd Pi3B, Pi3A, Zero 2W 
*Bluetooth 4.2 BCM4345C0.hcd  Pi3B+, Pi4 
*Bluetooth 5.0 BCM4345C5.hcd  Pi4B rev, CM4 and maybe Pi5 and CM5 

&lt;pre&gt;
*bthid    keyboard mouse support 
*btserial serial 
*btpan    short range wireless connecting devices 
&lt;/pre&gt;


Only the Pi5 has a RTC real time clock, the other Pis will need to use ntp services [https://github.com/aros-development-team/AROS/commit/29cd4116330dc7f692d90757eacc59fb3f31ae70 sntp] with time.cloudflare.com pool.ntp.org or Cloudflare 162.159.200.1, 162.159.200.123, 2606:4700:f1::1, 2606:4700:f1::123 or [https://github.com/bohunamiga/PiNTP PiNTP -s goodtime.ijs.si or ntp1.ptb.de] to get the date and time from the internet. Can use date in a shell e.g.  date 24-Dec-2026 23:59:59  but this will need to be done again after every reset/power off. Maybe [https://github.com/aros-development-team/AROS/commit/28674a157bc56175aa668e7b62dca6fa740578dc ds3231 rtc with dtoverlay=i2c-rtc,ds3231 in config.txt] 


It helps to have all usb devices already plugged in before power on to detect at the moment. Even then some usb devices will freeze the mouse cursor and the only resolution is to remove the offending usb device and reinsert. Sometimes, the reinsert leads to the mouse cursor vanishing, it is still there and responds to left mouse clicks, top of the screen and pull down the screen. 

USB classes support from Prefs/Trident is still work in process 
*usbaudio working on usb3 port (blue) on pi4, 400 but not working (no rt isochronous) on usb2otg (white or black) for pi3b, zero 2w 
*[https://aminet.net/package/mus/midi/camd camdusbmidi] detects midi devices without a preferences file (Prefs/Env-Archive/sys/midi.prefs) as [https://www.youtube.com/watch?v=RBxHkwy4Nrw auto setup now] possibly with [https://github.com/metaneutrons/mt32-pi metaneutrons mt32-pi] [https://github.com/rtzor/mt32-pi mt32-pi fork] [https://github.com/ahmadexp/mt32-pi fork] [https://github.com/gmcn42/mt32-pi-control control of] [https://github.com/dwhinham/mt32-pi mt32-pi pi3+]. Alternative of [https://homspace.nl/samplerbox/ SamplerBox]. 

Will need developer clang gcc tools to look at 64bit ports of [https://archives.arosworld.org/?function=showfile&amp;file=driver/audio/usbmidi.i386-aros.lha usbmidi], [https://aminet.net/package/mus/midi/CAMD_Toolkit CAMD_Toolkit], [https://aminet.net/package/mus/midi/camdtools camdtools], [https://github.com/cnvogelg/amiditools amiditools], [https://github.com/timoinutilis/midi-sequencer-amigaos horny src], [https://aminet.net/package/mus/midi/horny-base horny-base], [http://bnp.hansfaust.de/index.html BnP], [https://arosarchives.os4depot.net/?function=showfile&amp;file=audio/misc/timidity.lha timidity], 


Regarding 680x0 emulation, there are several options (not implemented yet) that could be considered 
*[https://github.com/aros-development-team/AROS/blob/6722a0ae9e03fe5d26e32703360bd2059e0864cc/rom/m68kemu/README.md?plain=1#L424 m68kemu.library] for some Amiga productivity where the cpu is emulated and the system calls are redirected to Aros ones
*[https://github.com/BlitterStudio/amiberry amiberry] (winuae) for everything else like games 
*[https://github.com/jonx/AROS/tree/aarch64-darwin-graft/arch/all-darwin/libs/emu68k emu68k] 
*[https://scriptedamigaemulator.net/ Scripted Amiga] with [https://github.com/naTmeg/ScriptedAmigaEmulator ScriptedAmigaEmulator] or older [https://github.com/gbraad-amiga/ScriptedAmigaEmulator2 ScriptedAmigaEmulator2] 
 Hopefully getting Pi3 up to 25Mhz 68040 (non JIT) and 50Mhz 68040 (JIT) 
 Pi4 maybe getting up to 50Mhz 68040 (no JIT) and 100Mhz 68040 (JIT) 


[https://pinout.xyz/ GPIO 40 pins] [https://learn.sparkfun.com/tutorials/raspberry-gpio/gpio-pinout pinout] 

Some exceptions:

*Physical pins 27, 28 (GPIO0, 1) are an internal I2C bus and should not be used
*The other I2C on pins 3, 5 (GPIO 2, 3) can be used generally, but be aware they have permanent pull-up resistors to 3.3V
*For MIDI use USB but there are dedicated UART pins 8, 10 (GPIO 14, 15).

With a HAT it's more awkward -- you need to know which pins are used by the HAT and avoid them. Hopefully this will be documented.

Remember all GPIOs are 3.3V (not 5V tolerant), floating/noisy inputs can cause odd behavior, and that shorting the power supplies can cause instant death of the Pi.

In the shell (Cntrl + C to end) 

 GPIO PIN/A/N,SET/N,GET/S,MODE/K,PULL/K

Controls and queries hardware GPIO pins via gpio.resource which is stored in the rom or Devs/ '''please test''' 

*PIN   -- (Required) Target GPIO pin number (e.g. 12).
*SET   -- Set pin output value to 0 (LOW) or 1 (HIGH).
*GET   -- Read and print current digital input level (0 or 1).
*MODE  -- Configure pin mode: IN (Input), OUT (Output), ALT (Alternate).
*PULL  -- Configure pull resistor: NONE, UP, DOWN.

EXAMPLES
&lt;pre&gt;
GPIO 12 MODE OUT
GPIO 12 SET 1
GPIO 12 GET
GPIO 13 PULL UP
&lt;/pre&gt;


[https://gpiozero.readthedocs.io/en/stable/installing.html Current] [https://gpiozero.readthedocs.io/en/v1.2.0/api_boards.html old support for gpiozero is unknown at present] [https://energenie4u.co.uk/res/pdfs/ENER314%20UM.pdf and associated 433MHz equipment] [ USA X10 security and lights via USB] [ OpenHab with Shelly Smart Plug connected over Wi-Fi, controlled by MQTT or HTTP] 


Printing only with Postscript but [https://github.com/bohunamiga/MintPRINT one] of [https://github.com/boingball/MintPRINT two] [https://github.com/Andiweli/AmiAirPrint/tree/main AirPrint] IPP has been attempted with [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2061&amp;pid=13954#post_13954 discussion] 


Youtube 

[], [], [https://www.youtube.com/watch?v=X4fmWAIv7FE Aros native on Pi3b], 

[], [], [https://www.youtube.com/watch?v=TSxlYb1eQWU Installed on Pi3b+], 

[], [], [https://www.youtube.com/watch?v=NFF1H3jCoz8 testing Aros native on Pi400], 

[], [], [https://www.youtube.com/watch?v=nIVx7mh1E1Q&amp;pp=ygUHYXJvcyBwadIHCQkTDAGHKiGM7w%3D%3D Aros on Thumb 2 based 32bit-ish ARM STM32H743 board], 


[https://www.youtube.com/watch?v=zQM4CD64xDE&amp;t=612s&amp;pp=ugUEEgJlbg%3D%3D Performance under Linux] but on Aros... 

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot; |Pi
! width=&quot;10%&quot; |Single Core 2D
! width=&quot;10%&quot; |Single Core 3D
! width=&quot;10%&quot; |Single Core 3D
! width=&quot;10%&quot; |SMP 2D
! width=&quot;10%&quot; |SMP 3D
! width=&quot;10%&quot; |SMP 3D 
! width=&quot;35%&quot; |Comments
|-
| &lt;!--Pi--&gt;Pi3 
| &lt;!--Single Core 2D--&gt;
| &lt;!--Single Core 3D--&gt;
| &lt;!--Single Core 3D--&gt;
| &lt;!--SMP 2D--&gt;
| &lt;!--SMP 3D--&gt;
| &lt;!--SMP 3D--&gt;
| &lt;!--Comments--&gt;
|-
|}


==== 32bit ====

For the Pi1 Pi2 Pi2B the status of AROS native ARMv6 for 32bit RasPi was OK. System booting, USB working (although with some issues but plans to fix them). 32bit native [http://www.aros.org/nightly1.html ARMv6 32bit nightlys] raspi-armhf-system raspi-armhf-contrib unbz2'd to fat32 microSD 


===Hosted===


AArch64 CPU backend for AROS, a Cocoa/Metal display, clipboard / host-volume / CoreAudio / BSD-sockets bridges, GPU 2D via gpufx.library, a 68k→AArch64 JIT (run68k), and a full Rust std port. On [https://www.jkn.me/blog/macaros-aros-on-apple-silicon/ latest Apple Silicon] [https://github.com/jonx/Macaros early buggy alpha version of hosted Aros .dmg on MacOS12+]. Please use [https://github.com/jonx/Macaros/issues MACAros github] for issues, features etc and possibly [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2030&amp;pid=13910#post_13910 here] 


[http://www.aros.org/snapshots1.html old linux and android hosted 32bit] 


==== Hosted ====

=====64bit=====

[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80&amp;pid=13667#post_13667 Ubuntu Linux PC hosted Pi compiler build] 

[https://github.com/BlitterStudio/aros-compiler-docker Docker based cross compiler for various Aros systems], 

[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80 From the Aros Raspberry pi 3 64bit thread] 
Instructions on building 64-bit Raspberry Pi AROS and cross-compiler from sources.

You will need:
- Ubuntu 24.04 or 26.04
- qemu-system-aarch64 installed
- Internet connection
- rpi-scripts.tar.gz downloaded (https://axrt.org/download/aros/rpi/rpi-scripts.tar.gz)

1) Install prerequisites:

sudo apt install git gcc g++ make gawk bison flex bzip2 netpbm autoconf automake libc6-dev liblzo2-dev libpng-dev gcc-multilib byacc python3-mako cmake yasm curl nasm

2) Clone sources

cd &lt;project-directory&gt;
git clone https://github.com/aros-development-team/AROS.git --recurse-submodules

3) Extract rpi-scripts.tar.gz. Copy all files into your project directory so that you have:

AROS (the directory with cloned sources)
fix-dotdot.py
rebuild.sh
recreate-sdcard.sh
run-qemu.sh
update-sdcard.sh

4) Run ./rebuild.sh. Select option 1) toolchain-core-aarch64

This will execute process of building a cross-compiler. During this process packages will be downloaded from Internet. This process can take up to 2 hours. If there are some missing dependencies, install them with 'sudo apt install' and restart this step.

5) Run ./rebuild.sh again. Select option 2) core-raspi-aarch64

This will build system files for 64-bit Raspberry Pi AROS. This process can take around an hour.

6) Run ./recreate-sdcard.sh

This will create an sdcard.img file with contents of previous step.

7) Run ./run-qemu.sh

This will start QEMU with SD card image and ROM images. It will boot into AROS.


=====32bit=====

Ubuntu VM approach to compiling [http://lallafa.de/blog/2013/06/building-aros-hosted-for-raspbian/ Linux hosted AROS June 04, 2013]

 ../AROS/configure --target=linux-armhf  --enable-includes=/usr/arm-linux-gnueabihf/include --x-includes=/usr/arm-linux-gnueabihf/include --x-libraries=/usr/arm-linux-gnueabihf/lib

arm-elf- is symbol-linked to arm-linux-gnueabi- (arm-linux-gnueabi- is more correct in this case, because it's going to be compiling the ARM AROSBootstrap for ARM Linux)

*armel - many of the &quot;android&quot; machines require since the entire OS is made for soft float VFP. 
*armfp - Efika MX target, Raspberry PI, EfikaMX, Pandora and virtually everything (VFP)

Keep in mind it's possible to start hardfp AROS hosted on softfp system, though, as long as no calls between AROS and host require floating point parameters. NOTE: hardfloat objects *cannot* be linked with softfloat objects - they have a different ABI.

Just keep in mind the arm nightly build machine is quite complex beast. It needs the x86_64 host compiler to compile AROS tools. The arm version is built every night using gcc-4.6.2 crosscompiler (built together with AROS) and successfully builds armel and armhf linux hosted targets.

*needs an AROS code compiler for ARM target 
*as well as unix compiler for ARM linux host (would be best to have both softfp and armhf, we have softfp only now) with full set of libraries and includes.

with—disable-crosstools  $AROS_CC  is always a wrapper around $KERNEL_CC  ?  If  so,  this  is  wrong for some ports. This can break Darwin, Windows and Android port. 
Yes,  Android  port  will  build.  And  even  work. But it's not good because  the  port  will  not  be ABI-compatible with other ARM ports. Android's ABI is different from GNUEABI. For example:

&lt;pre&gt;
enum test {foo, bar};
enum test testvar;
&lt;/pre&gt;

sizeof(testvar)  will  be  equal  to sizeof(int) in GNUEABI (Linux and AROS)  and  sizeof(short)  on  Android. This affects linking objects from static linklibs, for example.

Previously everything worked because $AROS_CC was a wrapper on top of $HOST_CC. And a real crosscompiler was used on non-ELF hosts.

Android is the same. $KERNEL_CC is incompatible with AROS.

compiler=kernel  is  appropriate _ONLY FOR CODE WHICH RUNS ON HOST OS_ (or  barebone  hardware,  if  we  talk  about  native).  This includes bootstraps,  their  linklibs, and host-side dynamic libraries (Windows makes extensive use of them because of architectural considerations.

No single AROS object should be compiled with this setting. $KERNEL_CC is really compatible with AROS *ONLY IN LINUX-HOSTED* and no more. On other systems (Darwin, Windows,  Android) this is not true any more, and compiler=kernel is never going to work.

If  you  want  to  compile your AROS module against host OS includes, append  the  following  to  USER_INCLUDES  (or  USER_CFLAGS,  this  is effectively the same):

 -isystem $(GENINCDIR) $(KERNEL_INCLUDES)

$(KERNEL_INCLUDES) expands to:

 -isystem  &lt;your_os_includes&gt;  -isystem  &lt;host_OS_gcc_private_includes&gt;
 -nostdinc

This makes AROS compiler adhering to host OS APIs.

If you want some preprocessor symbols based on what your host OS actually is, add something like -DHOST_OS_$(AROS_HOST_ARCH).

Why is there $(GENINCDIR) at all? Because host OS has its own libc includes, which would conflict with AROS ones. And the host OS libc is not binary-compatible with AROS one.

Why doesn't Windows-hosted port use $(KERNEL_INCLUDES) ? Because WinAPI includes conflict with AROS ones in fundamental typedefs, like WORD, BYTE and BOOL. It's almost impossible to deal with this in any other way than rewriting WinAPI definitions using AROS types.

Building under centos 6.3 (i386) currently, and AROS creates the toolchain itself. haven't yet committed the necessary changes but &quot;./configure --target=raspi-armhf&quot; is enough to start, then &quot;make arosboot-raspi&quot; will generate arosraspi.img (containing the bootstrap, kernel.resource, and exec.library) as well as arosraspi.rom (containing all the other essentials components such as dos, graphics etc).  It will also copy over a config.txt file to make the raspi bootstrap code load the correct kernel, and a cmdline.txt that enables exec debug output.

*armel = typically Debian 6, Ubuntu Maverick, Android, 
*armhf = typically Debian 7, Debian 8, Ubuntu Precise,

Cross-compiling Ubuntu ARM softfp 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armel' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armel] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armel.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabi libx11-dev:armel libsdl-dev:armel
&lt;/pre&gt;

&lt;pre&gt;
 ./configure --target=linux-arm --x-includes=/usr/include \
             --enable-includes=/usr/arm-linux-gnueabi/include
&lt;/pre&gt;

Cross-compiling Ubuntu ARM hard-float 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armhf' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armhf] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armhf.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabihf libx11-dev:armhf libsdl-dev:armhf
&lt;/pre&gt;

&lt;pre&gt;
    ./configure --target=linux-armhf --x-includes=/usr/include \
                --enable-includes=/usr/arm-linux-gnueabihf/include
&lt;/pre&gt;

Now, the AROS build is configured properly and all you need to do is:

 make


==Build==

===64bit===

[https://github.com/aros-development-team/AROS/blob/7016ce28bfdb754182edb16011c98faaf5413c29/arch/aarch64-raspi/boot/mmakefile.src#L180 boot makefile] 


===32bit===


# download/checkout the source someplace, e.g. /build/AROS-Src/
# make a directory to store external sources AROS downloads, e.g. /build/Ports
# make a build directory, e.g. /build/aros-raspi-armhf
# cd into the build dir, configure, and then run make -:

&lt;pre&gt;
&gt;cd /build/aros-raspi-armhf
&gt;/build/AROS-Src/configure --target=raspberrypi-armhf --with-serial-debug --enable-ccache --with-portssources=/build/Ports
&gt;make
&gt;make arosboot-raspi
&lt;/pre&gt;

then copy the files from /build/aros-raspi-armhf/bin/raspi-armhf/AROS/ onto an sdcard, and download/copy the Raspi firmware files onto it.

You should then be able to boot the sdcard on your RasPi.

The current W.I.P tree to svn. it can be built as follows ..
&lt;pre&gt;
./configure --target=raspi-armhf
make arosboot-raspi
&lt;/pre&gt;

That will generate arosraspi.img, arosraspi.rom and config.txt in bin/raspi-arm/AROS - so either copy just those files to a fat formatted SD card (with the firmware files on), or copy the whole contents of the AROS folder.

NB - if you have a Linux/other install, backup the existing config.txt first

arosraspi.img contains the bootstrap (which has very basic mailbox code, framebuffer/gpio init, and console &quot;emulation&quot; via code pinched from our libbootconsole), kernel.resource, and exec.library

arosraspi.rom contains all the other components needed to boot AROS.

The config.txt file will tell the RasPI bootstrap to load the arosraspi kernel and ramdisk (rom).

the bootstrap has minimal mailbox code, planning on adding either a resource or library that driver/app code will use to access it (likewise for GPIO)


Help building AROS hosted on Linux ARM

Was looking a way to use more my Handheld ARM based called Pyra (Dragonbox Pyra) an ARM (Omap5 cpu with 4GB ram) linux based machine (Debian Buster v10 with kernel 5.6.19 adapted) and have a try to compile the latest Aros sources by Deadwood directly on this device.
Compilation stops after build libpopupmenu.a and trying to build libatomic have this error:

&lt;pre&gt;
    Configuring build in bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic
    configure: WARNING: unrecognized options: --disable-nls, --without-x
    checking for --enable-version-specific-runtime-libs... no
    checking for --enable-generated-files-in-srcdir... no
    checking build system type... arm-unknown-linux-gnu
    checking host system type... arm-unknown-aros
    checking target system type... arm-unknown-aros
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for arm-aros-strip... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-strip
    checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
    checking for gawk... no
    checking for mawk... mawk
    checking whether make sets $(MAKE)... yes
    checking whether make supports nested variables... yes
    checking for arm-aros-gcc... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-gcc
    checking whether the C compiler works... no
    configure: error: in /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic':
    configure: error: C compiler cannot create executables
    See config.log' for more details
    make[2]: *** [mmakefile:4489: /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic/.configured] Error 77
    [MMAKE] make --no-print-directory TOP=/media/farox/pyra2/arosbuilds/toolchain-core-armhf-build SRCDIR=/media/farox/pyra2/arosbuilds/AROS CURDIR=tools/crosstools/gnu TARGET=tools-crosstools-gcc-libatomic-configure -s --file=mmakefile tools-crosstools-gcc-libatomic-configure failed: 512
    [MMAKE] Error: Error while running make in tools/crosstools/gnu: No such file or directory
    make[1]: *** [Makefile:361: linklibs-libatomic] Error 10
    make: *** [Makefile:183: crosstools] Error 2
&lt;/pre&gt;


looking at config.log on arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic

found that arosbuilds/toolchain-core-armhf/arm-aros-ld: cannot find -laeabi
so do make linklibs-aeabi-arm-quick
and the missing lib was built.

now the next stop is at
fatal error: bits/libc-header-start.h: No such file or directory
and
fatal error: sys/cdefs.h: No such file or directory
in many places so after checking that have this missing include files i have noted that my include path is a bit different, standard searching path is /usr/arm-linux-gnueabihf but in my system is /usr/include/arm-linux-gnueabihf
so if i add my path to some mmakefiles compilation goes on....but is a better way to add this path to avoid every mmakefiles to be changed?

fixed with adding
-I/usr/include/arm-linux-gnueabihf
to where is missing on mmakefiles like
USER_INCLUDES := -isystem $(GENINCDIR) -I/usr/include/arm-linux-gnueabihf $(KERNEL_INCLUDES)

P.s. I have changed many mmakefiles and have at least compiled (after many hours) the toolchain doing make every time in arosbuilds/toolchain-core-armhf-build (also have to disable making tests under cplusplus but don't remember the directory ...) but ask an help to have an automated way to correctly build without modify mmakefiles.


Last time built armhf target was around 2 years ago. At that point built is via cross-compilation from linux (ubuntu 22.04) using linux armhf crosscompiler (this can explain the path differences you are experiencing) as well as using AROS gcc cross-compiler in version 6.5.0 (build with option 21) in rebuild.sh). Since then AROS GCC has been updated to 10.5.0 and don't believe anyone tried to build the armhf target again.

My suggestion would be to downgrade GCC to 6.5.0 (via editing AROS/config/gcc_def file) and try to first build using cross-compilation from x86_64 linux. Once that works, you will have a &quot;template&quot; to compare to native compilation under arm linux.


Thanks for your suggestion...but think the toolchain with GCC 10.5.0 is compilable if i found a way to pass the path of my system to the script that build (option 21 on rebuild).
The other only changes are (but don't know where to modify...) is to add the build of libaeabi and disable the building of some tests under cplusplus that use exceptions and is not supported under ARM. try to crosscompile with my Linux amd64 PC.

For paths look into core-linux-armhf/bin/linux-armhf/gen/config/target.cfg. A number of build-wide variable is set there containing paths to local build system. These variables and the target.cfg file are generated by AROS ./configure script.

Thanks compilation now go forward...changed target.cfg under &quot;toolchain-core-armhf-build/bin/linux-arm/gen/config&quot; and do make on &quot;toolchain-core-armhf-build&quot; dir.

Need to find where to enable build libaeabi.a so can build the entire toolchain with option 21 of rebuild.sh


Found something that looks like libeabi in AROS/arm-all/arm-aeabi/mmakefile.src. Try adding a third line there:

#MM- linklibs-armhd : libklibs-aeabi-arm

Don't remember needing this library. Possibly the 6.5.0 GCC somehow does this while 10.5.0 is missing this.

Try adding this line (and the variant &quot;linklibs-armhf&quot; instead of hd) but it did not solve the automatic building of the missing lib. I must do &quot;linklibs-aeabi-arm-quick&quot;.
Anyway after have build the aeabi lib i succefully built the toolchain (after many hours...). Smile

To test I restarted from selecting option 21 (on rebuild.sh) but after many hours i get the same error of the kernel includes not found...maybe i need to modify the configure script for my case.

With the toolchain built i try to build the core-linux-armhf (DEBUG) (option 22) but after a while it stopped with
&quot;cannot find -laeabi &quot; so i made it built manually...and now i can continue compiling...i'll let you know if all goes ok.


== Hardware ==

===64bit===


====BCM2712====

With the Pi5 

Broadcom VideoCore 7 vc7 is an integrated GPU with 12 cores and up to 800 MHz clock. VideoCore VII is capable of OpenGL ES 3.1 and Vulkan 1.2. The driver support for the Raspberry Pi continues to build upon the [https://lore.kernel.org/dri-devel/20230928114532.167854-1-itoral@igalia.com/ open-source V3D driver] stack within [https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450 Mesa] hopefully be merged for Mesa 23.3. x265 HEVC accelerated untested, x264/h.264 and VP9 cpu only. 

*Raspberry Pi M.2 HAT+ Expansion Board 
*Geekworm X1001 PCIe to M.2 Key-M NVMe
*Geekworm X1003 PCIe to M.2 HAT NVMe SSD PIP Board for Raspberry Pi 5 
*Pineboards Pi Hut HatDrive! M.2 HAT 2024/V4 
*Hat+ Gen2 Gen3 Nvme
*GeeekPi 52Pi N04 for Raspberry Pi 5 NVME M.2
*


*2024 RPI AI HAT    - Hailo  20TOPs  no LLMs 
*2026 RPI AI HAT+ 2 - Hailo  40TOPs  slightly better? 


[https://www.raspberrypi.com/documentation/accessories/camera.html Cameras for Pi]
*Raspberry Pi camera module, the V3 with Sony IMX708 back-illuminated CMOS 12 Megapixel sensor
*Raspberry Pi Camera Module V2 – 8MP Sony IMX219 Sensor
*Raspberry Pi camera Rev 1.3, 5MP 1080P OV5647 image/video module, 2592 x 1944 pixels


====BCM2711====

With the Pi4 an ARM a72 cpu is about x3 times the size of an a53 in the Pi3 

the 2711b line used more power when idle, compared to the 2711c 

*2018 Raspberry Pi PoE HAT Power Over Ethernet Hat - design issues 
*2020 Raspberry Pi PoE+ HAT Power Over Ethernet Hat Pi3b+ Pi4 only - better design 
*Waveshare PoE HAT (B) with cooling fan for Raspberry Pi 3B+/4B 802.3af PoE 

*[https://github.com/axizo-pi/V3DLib vc6 V3D 4.2] is derived from [https://docs.broadcom.com/doc/12358545 vc4], but it is [https://docs.mesa3d.org/drivers/v3d.html significantly different] 
The QPU pipeline stays mostly the same, you still have an add ALU and a multiply ALU and it can issue two ALU OPs per cycle. There is still 4 SIMD lanes, interleaved over 4 cycles.
The instruction encoding for the QPUs is different, but the core instructions are the same.

Instructions for packed 8 bit int math has been dropped, along with most of the pack modes.
Instructions for packed 16bit float math has been added (2 floats at in a single operation)
With vc5/vc6, you write two packed 16f value to the tilebuffer (or four writes of 32f, if you are using the rgba32f framebuffer). And there is a handy vfpack operation which allows you to pack two f32s into a single 32bit value in a single instruction. You can vfpack directly into the tile buffer register.

the multiply ALU can now fadd, so you can issue two fadds per instruction. the add ALU has gained a bunch of new instructions 

the A and B register files have been merged. You still only get an A read and a B read per instruction, but they read from one big register file (which means the underlying memory block has gone from two sets of &quot;one read port, one write port&quot; to one &quot;two read ports, one write port&quot; block)

The theoretical max FLOPs per QPU remains the same at two per cycle, other than the bump from 400mhz to 500mhx but it looks like a lot of effort has been put putting those theoretical FLOPs to better use. 
*vc4 could run one or two threads per QPU. When you ran in two thread mode, the available register file halfed to 32 registers.
*vc5 added a four thread per QPU mode, with 16 registers per thread.
*vc6 doubled the size of the register file. You could now use all 64 threads in two thread mode and 32 registers in for thread mode. Single thread mode was removed, you always have at least two threads.

With the threading improvements, the QPUs should spent much less time idle waiting NOPs for memory requests. Most of the design changes have gone to improving the fixed function hardware around the QPUs. A fixed function blend unit has been added, which should reduce load on the QPUs when doing alpha blending. hope software blending is still possible 

The tile buffer can now store upto 4 render targets (up to 128bits per pixel, so if you are using 4 32bit render targets, you can't have a depth buffer)

A MMU, allowing a much simpler/faster kernel driver.

Many more texture formats, framebuffer formats.

h264/x264 as Pi3 

All the features needed for opengl es 3.0 

H.265 / HEVC decoder is a HEVCv2 Main 4:4:4 10 design supporting bitstreams up to profile 5.1
HEVC hardware decode supports 4kp60, 10-bit. Audio output is pretty much unchanged, but the HDMI audio channels now support 8x192kHz bitrates 

Each ALU typically have 2 floating point operators, and as you pointed out in a earlier post videocore 6 is no exception, with both a multiply and additive floating point operator. Thus theoretical GFLOPs are calculated with both operators in mind. That is what the 2 in my formula represents, and is common across any modern programmable shader, whether you calculate Nvidia, AMD, Intel, Boardcom or any other company's GPUs. Total ALUs * 2 * GHz clock = GFLOPs, In the case of Raspberry Pi 3, it's 24 ALUs * 2 operators * 0.4GHz = 19.2GFLOPs
If the Videocore 6 does indeed only have 16 ALUs (16 * 2 * 0.5GHz), you'd have only 16GFLOPs but they are better utilised 

Possible maximum performance 
&lt;pre&gt;
VideoCore IV @ 250MHz: 250 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 24 Gflop/s
VideoCore IV @ 300MHz: 300 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 28.8 Gflop/s
VideoCore VI @ 500MHz: 500 [MHz] x 2 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 32 Gflop/s
&lt;/pre&gt;

Faster LPDDR4 memory.


====BCM2837==== 

With the Pi3 
* Broadcom BCM43438 chip provides 2.4&amp;nbsp;GHz 802.11n wireless LAN, Bluetooth Low Energy, and Bluetooth 4.1 Classic radio support, 3B+ [https://github.com/aros-development-team/AROS/commit/afa5bc0bb17d5dd06bcfdbac00853a3799ca8d76 LAN7515] 

The overclock ability has diminished with each chip version as the energy usage has increased. BCM2837 is one of the warmest yet and benefits from active fan cooling if all four cpu cores are in use for a short while. Video playback maybe affected due to the lack of custom support in the GPU with Aros. 5 V / 2.4 or 2.5 amp power supply recommended if all four cpu cores are running, else throttling (cpu slowdown) might occur. 

[https://github.com/hermanhermitage/videocoreiv/wiki/VideoCore-IV-Programmers-Manual Dual VDP] and scalable QPU in [https://docs.mesa3d.org/drivers/vc4.html VC4] and x.264/h.264 accelerated untested only and VP9 on cpu or neon help 


ARMv8-A has [https://developer.arm.com/documentation/102412/0100/Privilege-and-Exception-levels privilege levels] where userspace typically runs at ‘EL0’, the kernel at ‘EL1’ or ‘EL2’ and the firmware at the highest level ‘EL3’. 


===32bit===

=== Core Kernel ===


====BCM2708(family)====
which includes the [http://elinux.org/RPi_Hardware BCM2835] (ARM1176JZF-S 700&amp;nbsp;MHz CPU + VideoCore IV GPU + up to 1GB RAM)

*Framebuffer (fb) using mailbox 
*IRQ scheduler, etc 
*Arasan based SD Card controller 
*Synopsis DesignWare USB 2.0 OTG controller [http://networkdirection.net/index.php?option=com_content&amp;view=article&amp;id=106:rasperry-pi-usb-controller&amp;catid=45:raspberry-pi&amp;Itemid=54 Unofficial DOCS pdf],  [dwc_otg.c FreeBSD], [], [https://www.riscosopen.org/viewer/view/mixed/RiscOS/Sources/HWSupport/USB/Controllers/DWCDriver/ RiscOS USB Driver], [https://www.riscosopen.org/forum/forums/5/topics/878 RiscOS USB Discussion], [https://www.riscosopen.org/forum/forums/11/topics/1893 Other USB RiscOS], [http://plan9.bell-labs.com/plan9/index.html Plan9 Miller's usb] http://plan9.bell-labs.com/sources/contrib/miller/, [https://github.com/Chadderz121/csud CSUD driver], 
*[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf SMSC 9512] USB LAN/Hub chip 
*CMOS RAM 
*VCHIQ port which sends messages to the GPU e.g. for mouse, keyboard, audio on HDMI, etc 
*Audio Driver 
*Serial Peripheral Interface Bus (SPI) 
*[http://www.susa.net/wordpress/2012/06/raspberry-pi-pcf8563-real-time-clock-rtc/ I2C registers]
*I2S 
*Universal Asynchronous Receiver Transmitter (UART) 
*[http://elinux.org/RPi_BCM2835_GPIOs GPIOs] and [http://www.adafruit.com/blog/2012/08/17/broadcom-bcm2835-peripheral-memory-map-and-gpio-alternate-use-chart-piday-raspberrypi-raspberry_pi/ Alternative view of GPIO]

BCM2836 
* For Pi B+, PI 2 and Pi 3 SMSC LAN9514 chip adding 10/100 Ethernet connectivity and four USB channels to the board

*[http://www.andrewscheller.co.uk/rpi_pcb_modules.html PCB], [http://elinux.org/RPi_Low-level_peripherals Low level features],


 Implemented so far... 

# Modify the configure system so that it correctly builds for the arm hardware float raspi target.
# Implemented the bootstrap to load the aros modules and prepare the arm to jump into them. Reworked the x86 console support so that parts can be stolen for raspi to use since t has no basic functionality to output to the display.
# Implemented a kernel.resource to prepare the raspi for running aros and provide the low level api calls to expose available resources and allow exec, etc function.
# Implemented serial debug support
# Implemented the exec (and kernel) functionality required to make multitasking work (and interrupts, exceptions, syscalls, etc)
# Implemented a timer.device to utilise the hardware timers.
# Implemented a very basic gfx driver to expose the hardware's framebuffer.
# Implemented an SD-Card driver for AROS which presently only supports the raspi's chipset but can easily be modified to support all sd-card hardware and media.
# Fixed the fat filesystem support in AROS so that it can boot on RasPi's normal SD-Card setup. The &quot;rom&quot; image files needed use a different filename than the default linux, etc images so can be easily installed without harming the existing files - you only need to change the loaded images in the config file to get aros to boot.
# Updated the build scripts to automatically download the necessary raspi firmware files and wrap it all up so that you can simply extract the archive to a fat formatted sdcard and boot it on the raspi without having to get anything else.
# fix everything in contrib and ports to build for raspi (needs proper testing/fixes but allows every component to actually compile at least, including owb) + numerous other fixes to get things working on arm/raspi ..


Improvements...

# Implement a USB chipset driver &quot;OR&quot; finish the existing one [https://github.com/aros-development-team/AROS/commit/c07d13c724f944674be5db54fc6a71ee72a01809 usb otg] - the current code is mostly a skeleton that should initialise the chipset and then needs relevant code to support the different transfer types. It also has the &quot;virtual&quot; hub code in place to represent the raspi's USB port (from poseidons p.o.v) 
# Implement a driver for the USB NIC (a few weeks - depends on USB above) 
# Write an [https://github.com/aros-development-team/AROS/commit/d55d0f74d20b769bbb8c8d386e5c1d7a9154f05a audio driver] (a few weeks - independent of USB) and [https://github.com/aros-development-team/AROS/commit/e93a4c245f27a87c9c4c1d39206694b39059998a HDMI]
# fix syscall bug in the current raspi kernel code
# Graphics depend on having a decent &quot;bcmdma.resource&quot; implemented as to use the cpu's dma engine. The sd card driver needs to use it for transfers to/from the controller - and the gfx system needs to use it for &quot;blitting&quot;. 
# [https://github.com/aros-development-team/AROS/commit/4019d84e4975d4dad987a12d57fe108f5ac048e6 Improve the gfx driver], [ vc4gfx HIDD] add [http://dri.freedesktop.org/wiki/VC4/ Gallium3D support] 
# [https://github.com/aros-development-team/AROS/commit/b13905b3e8e45b089f520b44692c81affddd066f Improve] the [https://github.com/aros-development-team/AROS/commit/3a876755c070f5c73c4f53c7f4d35b4f923088b9 sdcard] device driver  - which is also pretty basic but should work with most cards, rework it to also support pci, etc. sd card interfaces on x86 
# The current code using very rudimentary access to the gpio interface - so that should be implemented as some resource for other components to access, as-well as the i2c interface exposed over the gpio interface. that should have a hidd class implemented which uses the gpio resource to communicate.


 Boot up typical for most other OSs before the open sourcing of many binary blobs from 2017 onwards 

On power-up, the rpi [http://www.open.com.au/mikem/bcm2835/ BCM 2835] [https://github.com/hermanhermitage/videocoreiv VideoCore4] GPU, not the ARM CPU, is in control, and the SD card slot is the only peripheral device with power. The firmware burned into the BCM2835's VideoCoreIV GPU PROM requires a DOS-style partition table; a FAT-formatted first partition; and the freely redistributable but closed sourced Broadcom files “bootcode.bin” and “start.elf” in that partition.

The boot sequence carries out several pre-boot tasks

*On powering of the rpi, the GPU reads and executes bootcode.bin, which then loads start.elf 
*The GPU loads the “start.elf” file, eventually, into the L2 cache and then executes it
*configures the memory split for the CPU and GPU
*reads and parses “config.txt” from the same partition on the SD card and applies the settings (like a PC’s BIOS settings)
*loads the “kernel.img” file, again from the same partition
*activates the CPU to begin executing the loaded kernel image

The CPU/GPU memory split is hard-coded into start.elf, so Broadcom provides three start.elf images, to give 32M, 64M, or 128M to the GPU for multimedia performance, and the remainder to the CPU.

RPi uses [https://github.com/raspberrypi/firmware some closed source loaders] and at some point it loads a binary blob named &quot;kernel.img&quot; at 0x8000, at that point there would be a rudimentary Aros alive. If one wants to use the SD-card then there would have to be a driver for the interface and a fat filesystem handler (SD-card has to be formatted to fat filesystem)

Boot code and kernel are now linked together and made into that binary blob, just for starters. Raspberry Pi uses [http://kernelnomicon.org/?p=133 u-boot] and [http://kernelnomicon.org/?p=138 UBoot] as bootloader, there's already some code in the Efika MX port for that. UBoot is a native bootloader and not just for the raspberry pi, it loads after start.elf.

You can find Efika MX port from arch implementations, some hacking is needed for the mmakefile.src'es as iit dates back to before the Aros crosstool era or else you get some weird errors while building. You also need to code the bootstrap and serial handling.

At the moment it seems that a fastest route for the native build would be to make one binary blob without using the package system. Raspberry's memory layout is pretty simple and if the implemented u-boot doesn't support loading other modules 

&lt;pre&gt;
?          - alias for 'help'
mtest      - simple RAM test
autoscr    - run script from memory
base       - print or set address offset
bbm        - BBM sub-system
bdinfo     - print Board Info structure
boot       - boot default, i.e., run 'bootcmd'
bootd      - boot default, i.e., run 'bootcmd'
bootm      - boot application image from memory
bootp      - boot image via network using BootP/TFTP protocol
cmp        - memory compare
coninfo    - print console devices and information
cp         - memory copy
crc32      - checksum calculation
echo       - echo args to console
fatinfo    - print information about filesystem
fatload    - load binary file from a dos filesystem
fatls      - list files in a directory (default /)
go         - start application at address 'addr'
help       - print online help
iminfo     - print header information for application image
itest      - return true/false on integer compare
jade       -
loadb      - load binary file over serial line (kermit mode)
loads      - load S-Record file over serial line
loady      - load binary file over serial line (ymodem mode)
loop       - infinite loop on address range
md         - memory display
mm         - memory modify (auto-incrementing)
mtest      - simple RAM test
mw         - memory write (fill)
nfs        - boot image via network using NFS protocol
nm         - memory modify (constant address)
pci        - list and access PCI Configuration Space
ping       - send ICMP ECHO_REQUEST to network host
printenv   - print environment variables
rarpboot   - boot image via network using RARP/TFTP protocol
reset      - Perform RESET of the CPU
run        - run commands in an environment variable
saveenv    - save environment variables to persistent storage
saves      - save S-Record file over serial line
setenv     - set environment variables
sleep      - delay execution for some time
tftpboot   - boot image via network using TFTP protocol
USB        - USB sub-system
usbboot    - boot from USB device
version    - print monitor version
&lt;/pre&gt;


And there is one more thing about modular ports. In order to actually implement this, your bootstrapping environment should provide the ability to load several files. On PC this is provided by GRUB2. on CHRP you can read filesystem via OpenFirmware, and Sam's Parthenope relies on modified u-boot. If your bootstrap allows to load only a single file, then you stuck with monolithic kickstart. By the way...  u-boot allows not only to boot up a single uImage or zImage, it also allows to write client programs AFAIK. With this approach, you actually can write modular bootstrap for ARM AROS using unmodified u-boot.

Most used [http://www.compulab.co.il/workspace/mediawiki/index.php5/U-Boot_quick_reference uboot options] are fatls usb 0:1,

the reason behind INTB_KERNEL is to allow use of the standard Exec function AddIntServer() to add interrupt handlers for
hardware drivers etc. AmigaOS never used it for abstract hardware drivers. AmigaOS  routed  only  raw  hardware IRQs there. Their assignment was hardcoded. As well as number of them. Actually on AmigaOS every bus has its own interrupt subsystem. For example PCI bus. PCI interrupts on Amiga are routed to a single exec interrupt.  1:1 relationship between CPU  and hardware interrupts is present only on PC.

IMHO we miss things like AddInterrupt/RemInterrupt methods on our PCI subsystem's device class.  PCI bus class should map these methods to whatever is appropriate. This is how it is done on AmigaOS and friends. When these are implemented, raw kernel.resource API will be needed only for several PC-specific drivers with hardwired resources. Exec IRQs are real IRQs only on Amiga hardware. On other machines they can be emulated where appropriate (VBlank is a good example). kernel.resource is meant  to be different, its IRQs are hardware-agnostic, they are plain &quot;Hardware IRQ number X, whatever this means&quot;. They are low-level actually, and meaningful only in the context of a particular system.

Was that not the transition from irq.hidd to kernel.resource? No.  A long time ago there was another hacky bit named INTB_TIMERTICK. It was &quot;abstract timer interrupt&quot;, used by timer.device. It was the same as VBlank, but with larger frequency. I removed it, because kernel.resource API was a cleaner way to access this interrupt. Furthermore, there can be more than one timer in the system. Thinking about bringing back timer HIDD definitions again. hpet.resource is a bad idea.

Can someone please enlighten me a little on how the scheduler is meant to work?
 
Poseidon.library creates its &quot;Poseidon Event Task&quot; during RTF_COLDSTART -&gt; then calls Wait(), and ends up in limbo because wait disables interrupts (used for the scheduler heartbeat), and basically waits forever because the sigbit is never set, since krnSwitch doesn't switch the task unless TF_SWITCH is set, and no codepath run during this seems to set it?? TF_SWITCH does not disable/enable switching. This flag just enables to run user-supplied hook when the task is being switched away. It is completely safe to call Wait() in Disable()d state. Doing this actually temporarily breaks this state. IDNestCnt gets remembered in struct Task, then next task is selected, and its IDNestCnt is restored in sysbase (see kernel_scheduler.c). If there are no other tasks, then your cpu_Dispatch() should enable interrupts on the CPU and enter idle mode. See x86 implementation for good example.

You miss what happens next...
 1. KrnSwitch() saves context of your task, saves IDNestCnt (core_Switch() and cpu_Switch()), then drops into cpu_Dispatch().
 2. cpu_Dispatch() calls core_Dispatch. Then two cases are possible:
 2a. There is a READY task. It is picked up, its IDNestCnt is restored in SysBase, then cpu_Dispatch() needs to restore registers and exit. The next task is run.
 2b. There are no READY tasks. core_Dispatch() returns NULL. In this case your cpu_Dispatch() should enter idle loop. It should just enable interrupts on the CPU and put it on halt. This allows it to process hardware interrupts. Eventually some of your interrupt handlers wakes up your task and puts it into READY list.

My heartbeat interrupt has been slowed atm to help debugging - but it never actually gets a chance to fire because of the Wait() disabling interrupts. Perhaps you have forgotten to enable interrupts in your idle loop.

There is a change in the format of AROS executables. Until now we were using Elf RELocable files which are usually used as intermediate object files. We had them for various reasons, one of them was how AROS files were built in the past. That days we had no real aros cross compiler and the option to embed relocation data in unix executables (or in executable files in general) was rather new and not every linux/unix system had it. Therefore we have decided to use intermediate files. Although it was somehow working (and it is still working :-)), it has some drawbacks. Therefore decided to introduce real Elf EXEC types, in first turn implemented on ARM target with option to expand in future to all other AROS architectures.

The first patch was pretty easy and appeared to work somehow. It generated nice executables with embedded relocation info. Not only that, it also removed all global symbols adjusting relocation data to be relative to the beginning of the sections. That move reduced number of symbols in each executable significantly (depending on the file between 20 and 80% of all symbols could be removed). The only symbols that stayed in the file are local ones - due to the nature of the patch wasn't able to remove them since we have not seen them in the symbol hash table.

The patch didn't worked though. The files were relocated, AROS kernel loaded, but it crashed very early. What happened? Well, the nature of ARM relocations happened :)

Most of the relocation data on all machines is rather simple. Relocation can be absolute or pc-relative, sometimes the offset has to be bit shifted. On ARM v7 there is another one. There, when one wants to load an address of function/variable into register a combination of two instructions can be used: movw and movt. The first one loads immediate into lower 16 bits of a register while clearing upper 16 bits. The second one loads immediate into upper 16 bits without touching lower halfword. Loading of a pointer into a register looks like this:

        movw r0, #:lower16:label

        movt   r0, #:upper16:label

In this case there are two relocations - one for lower halfword and another for upper. If an overflow of lower 16 bits occurs during relocation process, the upper one should be updated as well. Unfortunately with current patch and with typical ARM executables there is not enough information to perform the calculations.

There are two options - the first one would be to give up and go back to &quot;fake&quot; executables, another one would be to change from REL to RELA relocation info. The latter contains an addend, extra data which can be used to perform all the relocation calculations I need.

Decided for the second option. The patch is already in the works. There is another function for the binutils' bfd backend to perform the final relocation. There can decide what to do with every reloc info, modify data and eventually strip some symbols. An advantage is - at this stage of the linking process have also full access to all local symbols so can change all relocations section relative and eventually strip all symbols from the files. 


 GPU 

VCore developed by Alphamosaic Ltd and now owned by Broadcom. Most of start.elf runs on the GPU.   Placing ALL the userland GPU code in the videocore.hidd isn't going to be a terribly big problem because the code they published is nothing more than a shim that sends data straight to the GPU to execute.

The good news about this is that we only need to write our HIDD using the OpenVG API.   The shim is relatively small codewise and lives in the ARM memory (the actual OpenVG code itself lives in the GPU RAM area and its loaded from start.elf).   That's also the bad news.  Our driver has to translate AROS video calls to OpenVG calls, for most tasks it should be easy, for some, not so much.  It's still probably less difficult and less work, than controlling the GPU directly.

The other good news is that anything done through OpenVG happens on the GPU, its truly accelerated.   It also has some nice font functions, meaning we can lead into an accelerated text mode later.

Basically, AROS resets or locks up when it tries to use AROS_ATOMIC_INC or DEC.  If I comment out the byte/word operations in the header files and use non-atomic operations, the code works as expected.
 
have read that the L1 cache needs to be enabled to use LDREX and co (which I also read is only meant to be used on multi processor systems with shared memory) - however I am certain this is correctly enabled.

If you are using LREX or STREX, you should have L1 cache enabled, at least on the ARM CPU I work with at work.

L1 cache is enabled by enabling the MMU *AND* setting the C and I bits in the CPU - the C bit is ignored, and the I bit only covers the 16 byte instruction pipeline if the MMU is not enabled.

Can you verify that your assembly is generating LDREX/STREX? From the behavior, it almost sounds like its generating the default Semaphore locked atomics.
 Impossible. There are no semaphore-locked atomics. There are Disable()/Enable()-based ones instead. And there's a special #define AROS_NO_ATOMIC_OPERATIONS in this case, which tweaks Disable()/Enable() implementations not to recurse forever.
 I have tested this on ARMv5 which does not have ldrex/strex, it works fine. On those ARMs there's no way to have real atomics. On other OSes (like Linux) this is done by introducing things like atomic_t, which appears to be a complex structure, holding the value together with accompanying spinlock (implemented using swp).

    #warning &quot;TODO: lookup optimal mmu table settings for raspi memory&quot;
        /* Set up an identity-mapping for all 4GB */
        for(x = 0; x &lt; 4096; x ++)
        {
            pagetable[x] = x&lt;&lt;20 | (0x40002|0x80000|0x010000|0x00C00|0x04);
        }

Shouldn't there be a second loop that sets the 'C' bit in the descriptor for the RAM pages?

Currently, you have TEX=0, C=0, B=1 for all pages (Shared Device).

You should have TEX=0, C=1, B=0 for RAM (Write-Through, Cached)

    So ..
     
     pagetable[x] = x&lt;&lt;20 | 2;

     
    should be enough?

No, for RAM you need to change the '| 0x40' to '| 0x80'

tell dosboot the correct defaults to use

Please don't do this. This bootconfig.c is a deprecated legacy thing. I wanted it to go away completely with time. Instead,  display  drivers  should auto-install themselves during own initialization phase. I. e. detect hardware=&gt;instantiate itself. This   should   make  things way simpler. With this approach you only need  to add the driver into KS image to get the device autobooted. No hardcoded stuff. 
Currently  VESA  and  VGA drivers do this, look there for examples. never rewrote ATI driver because i don't have any test system for it.

they defined a smaller AROSCPUContext than the ExceptionContext - yet reference it as ExceptionContext in other places, and since it hasn't allocated enough storage for ExceptionContext, are corrupting memory/the structure (since the elements that are there don't map 1 to 1 with the exception context).

AFAIK, AROS has been moving in a different direction to this in recent years. It is the job of graphics HIDDs to allocate bitmaps etc. so that they have the most suitable characteristics, including allocating them from GPU RAM where possible. The concept of chip RAM is only for legacy code, and most if not all non-68k platforms should have all system RAM
marked as chip.

BTW, is the video processing code you mention CPU code or GPU code?

Also, IIRC we have support for &quot;external memory allocators&quot;. Perhaps that's what we need for the allocation of GPU RAM through the mailbox.

All hosted and x86 native ports should use proper context formats.

trying to clarify if the vblank handler has to have run by this point to prevent this deadlock. Actually, no. Unless you have installed VBlank handler which should wake up at some point. Without VBlank there will be no quantum count. Consequently, there will be no forced preemption. But the rest will work, and multitasking will be cooperative (switch happens only when current task voluntarily gives up the CPU). Does it depend on the vblank having run before this point? and if yes what does that mean on systems where it might be able to run enough code (e.g. get to this point) before the vblank interrupt has triggered? What is it waiting for? It could wait for timer, in this case you need timer.device working. VBlank is currently needed for exec's quantum counter. In current native ports we have only a single timer, which is served by timer.device. VBlank is simulated by timer.device also. If your machine has two timers, then you can use one of them for VBlank, and another for timer.device, this will simplify things down. VBlank needs to be 50 Hz for historical reasons, many programs use it as cheap timer. I am periodically thinking about making some abstract mechanism to be able to change quantum source (and untie it from 50 Hz), but have no time to come up with something good. Additionally i started disliking timer.device hardcoded design when PC has got many timers (old 8253, APIC, HPET).
Currently i think there should be some low-level entity representing tick source. timer.device should just select the most appropriate source for its units.
The BCM2835 has 4 GPU based timer sources - 2 are used by the GPU, so im using Timer3 for our heartbeat and the remaining one will be free to the system. There is also the less capable ARM timer but that is dependent on the CPU frequency. Very good. You won't need any emulation. Set the heartbeat to 50 Hz and drive VBlank from it. Use other timer for MicroHZ.

Can you use the 'econsole.hook' I make for debugging the Sam460 via the serial port?
It provides a before-anything-else shell prompt on the serial port.  You can then do 'NewCLI' to test your graphics, or use any DOS command in shellcommands.resource.

You should just be able to add econsole.hook to your module list, and use 'econsole' in your bootargs.

So long as you have a working Exec/RawMayGetChar and Exec/RawPutChar, it should work.

Also make sure to add shell.resource and shellcommands.resource for this.

That should have done it.

If you set &quot;#define DEBUG 1&quot; in  arch/all-native/econsole/econsole.c, do you get any additional serial output?

have added it to the build and added econsole to the command line - and can see the bootloader picks up on the emergency bootconsole tag, but I still only get the insert bootable media display?

Im assuming it exposes a fake filesystem that tricks aros into booting?
The contents of which are: ECON:AROS.boot

Way to handle the scheduling code? The implementations I had been following were causing problems, due to cascading interrupts which I cant handle properly in the asm stubs just now (when they break disable etc.) - since it means detecting the interrupted codes cpu mode and getting the correct sp/lr for it, and that's just too tedious for arm.
 
To work around this ive added a system idle task which does nothing - and when the scheduling code has no task to run switches this in and lets it run, thereby allowing the interrupts etc to resume until something does need to happen.
 
Also, by adding accounting code to cpu_Switch() and cpu_Dispatch(), it should allow the system to log idle time correctly (as well as running tasks).
 
have thought of also adding an additional task that never runs, solely to record time spent in IRQ handlers, but I digress..

was under the impression that kernel.resource should *never* be used outside of exec.library. This is a wrong impression.
Michal started designing it because portable nature of AROS does not fit well into exec's API with all its assumptions. So, he started the new, hardware-agnostic kernel API from scratch. Yes, exec sits on top of it in places. But kernel always meant to be open thing. Otherwise it would not exist. 
it wasn't meant to be just used willy nilly by user code - but by lower system components (e.g. exec) so that they could be implemented in a more generic fashion, and the kernel resource itself hide the systems quirks.

Adding new things there perfectly keeps up with our decision to minimize AROS-specific intervention into APIs which can clash with MorphOS or Amiga OS4 extensions. We want at least source-level compatibility there. Binary compatibility on PPC would be extremely cool, but at the other hand we have no maintainer for this, as well as their ABIs splintering. 
It depends on what exactly is being implemented - there's no reason we should have everything crammed into kernel.resource if it doesn't need to be (i.e. if its better suited as a separate component/subsystem in its own right)

The _LE versions are for when you have endian swapping taking place.  If the graphics are the same endian as the CPU, no swapping should occur.  I ran into a similar terminology problem in SDL with a friend insisting that his Radeon 7000 on his PC was big-endian.  It is not, it just uses the same endianness for the graphics card and the CPU so no swapping was necessary.  They were both little-endian.
The _LE versions are because the PixFmts refer to the bitmap data being in big endian format in memory, for which the normal version would need to do endianness conversion before applying the shifts/masks. on this platform it is in _LE in memory also so we don't need the conversion hence using the _LE version of the call). would use _LE (if it's really little endian 16 bit mode).

 
What is the bare minimum needed to implement a framebuffer based gfx driver, with our software handling the rest?

Have tried with just a gfx class that only expose new/dispose/newbitmap - and having an onscreenbitmap used only for the framebuffer itself (with all other bitmaps being chunkybm, and the framebuffer's superclass also being chunkybm), but that alone isn't enough it seems?
You can use workbench/hidds/sm502/ as your example - it is as simple as I could make it.
So, AROS creates the framebuffer bitmap (verified this) -&gt; so surely it should be capable of then rendeing into it? I don't actually create the framebuffer &quot;bitmap object&quot; myself - only as a result of being asked to. The code I currently have on SVN seems to create the framebuffers bitmap object fine, but then crashes in intuitions DisplayDriver callback.  In particular it crashes performing the getattr on the system default pointer. don't expose MEMF_CHIP in an allocatable form so AllocSpriteData was failing (and other code later doesn't check if the values are valid == illegal memory accesses) 

So far have -:

vc_init: queries the gpus memory, and sets up a fake memory handler for it, then adds the bootmode driver and returns saying all is well
vc_gfxhidd:New: sets up some fake syncmodes to test with and creates the real gfx object.
vc_gfxhidd:NewBitmap: checks if its a framebuffer and uses the onbitmap class or uses the chunkybm class otherwise
vc_onbitmap:New; creates a chunkybm object and then pushes the real framebuffer address into it as the buffer,

vc4 had v8adds, v8subs, v8muld, v8min and v8max which operated on four 8bit uint values packed into a 32bit register. Multiplication was in the range 0.0 to 1.0 and addition/subtraction saturated. There were also a range unpacking/packing modes that allowed you to pack and unpack 8bit values into 32bit registers. 

RasPi has to speak to the &quot;operating system&quot; which runs on the GPU itself and request/free memory - it cant directly manage it itself, and so the managed functions were used to wrap these calls.

The Arm and GPU share memory space. The framebuffer is shared. The Arm can write a pixel and it will appear on the screen (through GPU hardware) without flushing/copying being required.

The GPU can composite multiple FB's in real time - so you have a number of surfaces defined which are rotated etc and  composited in real time to the output. Copying can map from the address space of the Arm to the flat space of the GPU which takes some code, but I don't think whole buffers are copied.

The DMA hardware can also access the whole memory space and can perform 2D fills and blits (no blending). This is documented in the peripheral spec posted. The DMA is just an Arm accessible peripheral and can be set up with low latency (e.g. microseconds).
must use a 0xc0000000-based bus address to access SDRAM, yet non-DMA access should go via a 0x0-based bus address. 
For 2D dma, set TDMODE, and the spec says &quot;interpret the TXFR_LEN register as YLENGTH number of transfers each of XLENGTH, and add the strides to the address after each transfer.&quot; so set STRIDE to pitch of the image, the width is XLENGTH and height is YLENGTH. You would fill by not setting the SRC_INC and point source to your fill data.

The DMA cannot see the ARM's L1 cache, so you would map the framebuffer with ioremap_nocache. Depending on where the source data comes from, it may need an L1 cache flush. The DMA can see the L2 cache. Use 0xC0000000 bus addresses when L2 is disabled and 0x40000000 bus addresses when L2 is enabled. (actually just call virt_to_bus and you'll get the right address out).

openGLES/openVG has high latency. Writing to framebuffer then reading it back is very inefficient (e.g. milliseconds). If you can drive it a unidirectional way, just streaming commands at then that is efficient. openVG is not implemented on top of openGLES - it uses the same hardware but as a first class interface

To improve the Gfx driver, we will need a DMA resource implemented so can use to perform DMA operations. The Gfx driver will need this to perform blits.


Actually MEMF_CHIP has to present, for historical reasons.
This has been never fully agreed upon, but in ports i wrote i exposed the whole memory as MEMF_CHIP. The idea behind this is that CHIP is originally the memory where graphics and sound data can be put. On non-Amiga platforms there are no restrictions on this, so the whole memory is CHIP.
Yes, many old software can misbehave with CHIP memory size larger than 2MB. But this actually applies only to m68k AROS which is going to run m68k binaries. In other cases it's quite logical to fix the program when porting.

As to original question: yes, it's enough to have a framebuffer bitmap (one with aoHidd_BitMap_FrameBuffer set to TRUE) and PutPixel routine. It framebuffer can be served by chunky bitmap class, then you can simply create chunky bitmap with your own buffer (see how VESA driver does this). Chunky PutPixel is already there.

struggling to determine what is the correct pixfmt to use for the 24/16/15 bit gfx modes on the RasPi.  AFAIK it uses RGB565, for 16bit but im unsure what shifts etc should go with it? suffice to say Im getting the wrong colors so far lol.

&lt;pre&gt;
redmask: 0x0000F800
greenmask: 0x000007E0
bluemask: 0x0000001F
alphamask: 0

redshift: 16
greenshift: 21
blueshift: 27
alphashift: 0
&lt;/pre&gt;

It should likely be vHidd_StdPixFmt_RGB16_LE

This stuff is a bit confusing.  The &quot;names&quot; of the stdpixfmts are based on the layout in memory,
ignoring endianess. So for example:

ARGB32: will be 0xAA 0xRR 0xGG 0xBB in memory on both big endian and little endian machines.

The shifts and masks OTOH are based on pixel access (ULONG in this case), so differ depending
on whether you run on big endian machine or little endian machine (that's why there's stdpixfmt_le.h and
stdpixfmt_be.h in rom/hidds/graphics/).

With the 16 bit pixel format it's even more confusing, as for example it's impossible on little endian machine
to describe RGB16 with shifts/masks alone. That's why there's vHidd_PixFmt_SwapPixelBytes_Flag.
(RGB16 == RRRRRGGG GGGBBBBB in memory, and for pixel (WORD) access on little endian machine it needs to
be accessed as GGGBBBBBRRRRRGGGG).

The shifts btw indicate how much to shift the component to the left (!) so that it is moved to the highest bit (31).

The aHidd_PixFmt_StdPixFmt you specify will be ignored most of the time, because when the pixelfmt is registered,
the gfx hidd checks if there's an identical pixfmt (shifts/masks/etc., but ignoring pixfmt-&gt;stdpixfmt) already in the system,
and if so, it uses the already existing one and does not create a new one.

In theory it would be better if gfx drivers could simply/only specify a StdPixFmt without all the shifts/masks stuff when the
gfx driver uses pixfmt which matches one of the stdpixfmts exactly. Another possibility would be for gfx drivers to use
HIDD_Gfx_GetPIxFmt(stdpixfmt_gfx_driver_wants_to_use) and then peek shifts/masks from it and fill out a pixfmt
tag list based on that.
15bit very blue/green: Try to pass same shifts/masks/etc. as in 16 bit pixfmt (maybe you think it's using 15 bit R5G5B5
(or swapped) but it's actually still using 16 bit R5G6B5 (or swapped).
 aHidd_PixFmt_StdPixFmt you pass is mostly ignored. It's the shift/masks/etc. that count.
But I would still pass the correct one (_LE) == whatever rom/hidds/graphics/stdpixfmts_??.h uses
in the entry where you have looked up shifts/masks/etc.

Use the shifts/masks/etc. from the entry in stdpixfmt_le.h (if you are running on little endian machine) or stdpixfmt_be.h (if you
are running on little endian machine) that matches the pixfmt that its meant to be.

0xAA,0xRR,0xGG,0xBB on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_BGRA32)

0xAA,0xRR,0xGG,0xBB on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_BGRA32)

it feels like AROS trashes the alpha component, otherwise it should be 8A8R8G8B.

read on the subject suggest its in 1x5r5g5b (x is ignored) to keep 16bit alignment .
 
Suggests to me that wrong shift/mask are being applied - however going by the 16bit versions it all looks correct to me so I am really confused as to what is happening.

The output image looks to have too much green/blue, and very weak red.


 Kickstart 

The  idea  is  to minimize amount of archirecture-specific modules to make the user's  life  easier.  So,  the kickstart was split into 'base' (which  does  not  contain anything machine-specific) and 'BSP' (Board Support Package) which contains all hardware-specific stuff. This  way,  for  example, distribution makers can save up space on CD and  make  CDs with multiple platform support. Different configuration would load the same base with different BSP's.

Next  there  was some part which is entirely missing on hosted. These are   filesystems.  Hosted  ports  do  not need them to boot up, so on hosted   they  are  left  out.  At  the  other  hand,  they  are  also architecture-agnostic.  So  i put them into 'FS' package (standing for 'filesystem').


 USB 

Poseidon  is  one  more  big part. I made it into separate package in order to allow users to omit it if they don't need it (for example, to run  on retro PCs without USB). Personally i have one. Again, Poseidon is  hardware-agnostic (well, there are USB drivers but HCIs are pretty standard).

AFAIK its HCI 1.0 compliant but not familiar enough with poseidons drivers, nor USB, to just hack away at the existing code.  Perhaps once i'm more familiar with the workings I can merge in the changes needed to get it operating but for now I will focus on getting it running.  Also our drivers have known issues so perhaps a fresh set of eyes might shed some light on what is going wrong.

Another interesting question is whether Poseidon can operate on device side. Is it flexible enough? How similar is being a USB host and USB device? think it will need a bit of work on Poseidon's side.  Until then I will force the driver into Host/Master mode in the init code, but leave open device etc to configure the chipset for either's use - and look at trying to add support for working in Device/Slave mode &amp; switching modes once it's up and running.

Actually USBROMStartup is some kind of kludge. Can there be any alternative? Could device drivers be self-installing, like our HIDDs? This would get rid of need to list them in USBRomStartup.

* Model A and B limited to 150 mA per port. 
* Model B+ and Pi 2 introduced configurable 600 mA to 1.2 A support over all ports - anything above that requires a powered USB hub.

Implementing the hardware driver that Poseidon uses to interact with the USB components.

Have code in place to (try) and initialise the USB chipset, and configure host/device mode operation (though AFAICT Poseidon doesn't support device mode). Started to get the &quot;virtual&quot; root hub written for the single USB port so that Poseidon should at least list it correctly in the GUI - and try to interact with it to find peripherals.


The BCM2835 uses a soft IP block from Synopsys’ DesignWare library (DWC), specifically the block is called dwc_usb_2_0_hs_otg_subsystem-ahb_se (“USB 2.0 Hi-Speed OTG Controller Subsystem w/AHB Interface SE”).

There is no public documentation for this, and pretty much zero chance of anyone getting hold of it even with NDA. However, there's a Linux driver written by Synopsys ([https://github.com/raspberrypi/linux dwc_usb]). Specifically directories [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_common_port] and [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_otg].

The Synopsys code is actually under a fairly permissive licence – it's not GPL, it's similar to BSD (’don't sue us if it breaks’ is pretty much the only clause). So this should not be a barrier to porting the code.

The code is really well written, with a nice partition between the work done by the driver (dwc_otg, which is fairly involved, given the host does more work than a conventional EHCI driver), and the interface to Linux (dwc_common_port).

Probably only need provision of relevant changes to dwc_common_port. Other things to consider....

* Provision of necessary headers to get it to compile
* Provision of necessary functions (main issues are wait queues, threads, work queues, tasklets, timers, spinlocks and mutexes (multithreading) )
* Interfacing between USB stack and the driver. dwc_otg/dwc_otg_hcd_linux.c looks like the place to start.

the Linux bits of the headers are only required for the dwc_common_port library. dwc_common_port includes a variety of crypto functions which are not used – it appears to also be used for ultrawideband (UWB) and wireless USB (WUSB) drivers where crypto will be an issue, but it isn't going to be for plain wired USB.

Every USB driver acts as an USB hub as well in order to let Poseidon control the state of USB ports. The code there was reading status of the only USB port in Raspberry's CPU but when changing the status it erroneously deleted some of the status bits, including the port enable one. It was so because those bits in the status register are of a type Read/WriteToClear. It means, if one does not want to change their value from 1 back to 0, one has to actually write the 0 value. Very practical thing e.g. in interrupt handlers, where one reads the interrupt status register to learn what was the interrupt reason, and writes it back to the same register in order to clear the interrupts. 

After fixing that code it turned out that the communication was still unsuccessful. Apparently the USB device was not understanding the host for some reason. That should not happen since the request sent was one of the standard ones implemented by virtually anything with an USB connector, assumed that Poseidon clears the data caches before forwarding the work to the USB drivers but that's the responsibility of the driver itself. 

The USB device responded and acknowledged the transmission! But why were all the request sent after address change failing with timeout? They should not. Once again, address set is supported just by anything. Tried to contact the device at address 0 once again and there it was, still responding properly. The enlightenment came. The bus address for DMA transmissions was, as it is in many bare metal USB implementations, just the pure memory address of the buffer as seen by the ARM cpu. Have &quot;prefixed&quot; it with the real location of uncached RAM and booted AROS once again. 


Trident saw this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

and this:

    Product     : Vendor: Vdr=0424/PID=EC00
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 255
    SubClass  : 0
    DevProto  : 1
    VendorID  : 1060
    ProductID : 60416
    DevVers   : 0200

and even this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

What are these things? The first one is USB hub built in the Raspberry. Thanks to this one the Pi machines (with exception of Pi0 and computing modules) have more than just one single USB port. The second one is the network chip in raspberry, the third one is my USB SD card reader which have just connected to see what happens. AROS tried, of course, to boot from it ;)

So, the first step towards working USB is done. The control transfers are working as you can see above. Next step is to implement bulk and interrupt transfers, having the basics in place. Finally some error handling will be added and USB for Pi will be as complete as the PC version. 

[http://www.raspyfi.com/raspberry-pi-usb-audio-fix/ Issue with USB Audio]


 Audio 

The Pi 4B is the only Pi that can output HD Audio as an HD Audio passthrough bitstream, and it does it over HDMI. It's possible to use the two HDMI output for separate HDMI video and HDMI audio outputs to allow UHD HDR video and HD Audio with non-UHD HDR compatible AVRs. 

The Pi3B+ and earlier will decode to PCM 5.1/7.1 and output over HDMI.  HDMI is the only interconnect that has a standard for carrying Dolby True HD, DTS HD MA etc. as a bitstream - you can't carry it as a bitstream on any other interface.

Pi3 and Pi4 audio jack output derived from 12bit pulse width modulation is relatively poor. For better, choose USB Audio or I2C versions. 

[https://github.com/raspberrypi/linux/tree/rpi-patches/sound/arm audio] and its [https://github.com/raspberrypi/firmware/issues/2 very high speed message passing interface type of thing VCHI] 

The Model B+ added an additional voltage regulator for the audio output and an additional output driver to drive low-resistance loads like headphones. However it is still using pulse-width modulation (PWM), which has a major impact on sound quality

the old Raspberry Pi used a linear voltage regulator to provide the 3.3V to many of the components on the board while the new one uses a switching regulator. Both can perform reasonably well. However switch mode power supplies often show higher noise figures

Analogue audio

Audio over HDMI rev 1.3 &amp; 1.4


 Ethernet 

10/100 BaseT Ethernet RJ45 socket


 GPIO 

GPIO shouldn't be too bad but bear in mind it is already accessed in places so they would need to allocate pins etc through it (e.g. sdcard to flicker the activity light, serial debug to output data on the GPIO pins)

Probably a resource rather than a device...

Started an i2c driver that will need to allocate GPIO pins. Feel free to work on it if you are interested ;p


 GPU graphics with 2D and 3D acceleration 

Sadly none yet for 32bit but for 64bit... 


 Miscellanous

hdmi issues

Setting the hdmi_force_hotplug=1 makes sure the Pi believes the monitor/TV is really there.

You might also need to set config_hdmi_boost=4 or even higher (up to 9) if your display needs a stronger signal.

If the display is a computer monitor or newer tv, use hdmi_group=1 (auto HDMI use) and if it is an older TV, try hdmi_group=2 (for DMT formats, i.e. for PC monitors) then you HAVE to &quot;set hdmi_drive = 2 to enable HDMI output as this forces HDMI mode rather than DVI mode

Do not set hdmi_safe=1 as that overrides many of the previous options.

Using a shorter or better quality HDMI cable might help. Make sure your Pi's power supply delivers 1 A and not 500 mA.
If you see a problem with the red colour - either absent, or interference - then try a boost

composite video

changing the RCA cable, then the composite port worked out of the box

Boot it as you are doing, without HDMI. If you now plug in the HDMI, do you get the image? In other words, does the Pi think HDMI is connected even when it isn't?

Rename all the files in the first partion of the card except bootcode.bin, start.elf and fixup.dat  What's the result?

Put back config.txt What's the result?

for PAL mode   sdtv_mode=2

dmi_ignore_hotplug Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached
hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected

&lt;pre&gt;
# NOOBS Auto-generated Settings:
#hdmi_force_hotplug=1
#config_hdmi_boost=4
#overscan_left=24
#overscan_right=24
#overscan_top=16
#overscan_bottom=16
#disable_overscan=0
start_x=1
gpu_mem=128
&lt;/pre&gt;

tvservice -c &quot;PAL 4:3&quot;

&lt;pre&gt;
/opt/vc/bin/tvservice -s   or tvservice -s 
state: HPD high|HDMI mode|HDCP off|composite off (0x12001a), 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m CEA
Group CEA has 1 modes:
(native) mode 16: 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m DMT
Group DMT has 0 modes:
&lt;/pre&gt;

sudo amixer cset numid=3 1

forces the audio to the headphone jack, even with the HDMI video output plugged in

config.txt

the hdmi_ignore_edid_audio=1 option sems relevant as it should tell ALSA that the only available audio is analog, no matter what the display says

There are several different ways that these 4 pole (ring) composite analog cables can be wired up, so some work great in some applications and can be a waste of time in others.

What is needed for the Raspberry Pi B+ and above, which like many camcorders needs the ring contact next to the base contact to be the ground.


The wiring for the 4 pole are:

TIP (LEFT AUDIO CHANNEL)

RING 1 (RIGHT AUDIO CHANNEL)

RING 2 (GROUND/EARTH)

RING 3 BASE/SLEEVE (VIDEO) YELLOW

Most Apple based Players and the Microsoft Zune (TM) are wired this way.

Most analogue camcorders are wired this way as well, where the ground in on Ring 2 will work with the Pi although you may need to swap your Video plug with the Right Audio plug.

Nearly all other MP3 players are not wired this way, the ground is on another ring ie the wrong one.


External devices

* Camera Module Omnivision ov5647 Sunny 5MP (NoIR version) V1.3 - NoIR at 850&amp;nbsp;nm, peak at 880&amp;nbsp;nm and trails off at 940&amp;nbsp;nm wavelengths 
* Camera V2 Sony IMX219 V2.1 8mpixel 8MP 8megapixel - 3280 x 2464 pixels - video at 1080p30, 720p60 and 640x480p90 - wider field of view, 62 vs 54 degrees horizontally - 
* Branded WIFI usb BCM43143 dongle

N.B.  dreaded error after changing cameras (stupidly without turning off the power first) and lasted through several power cycles.  It can be a bad 15-pin FFC ribbon cable, when swapped, camera(s) and the Pi itself are working OK. It can be an instance of a cold solder joint on the CSI connector on the pi board.  the camera can be detected (that's done via I2C) but may still not be able to receive image data (done via CSI-2) if something is broken. CSI-2 is uni-directional. Control is generally done via I2C. 
The CSI-2 receiver always writes to memory, not direct to the ISP. That's the way the Broadcom architecture works as it allows multipass processing easily. GPU memory is accessible from the ARM. Processing using the QPU graphics processors may be possible.  currently the only supported sensor is OV5647 and IMX219.  The linux drivers are all in the firmware blob, else you'd  be looking at at least a man-month of work in a fully fledged imaging lab to do a decent tuning of the camera modules' ISP parameters. 
Static electricity maybe an issue for the camera module and slightly less for the pi board.


== References ==


===Good sites to visit===

*[https://github.com/raspberrypi/firmware/tree/master/ Raspberry Pi Firmware build] 
*[https://www.raspberrypi.com/documentation/computers/software-sources.html Documentation] 
*[https://rpilocator.com/ RPiLocator] 


Linux only
*[https://github.com/raspberrypi/linux Raspberry Pi Linux Build] 
*[https://dietpi.com/ DietPi] 
*[http://www.tinycorelinux.net/ports.html piCore]
*[https://wiki.alpinelinux.org/wiki/Raspberry_Pi Alpine Linux] 
*[https://github.com/armbian/build Armbian] 


*[ FydeOS]
*[ TwisterOS based on ChromiumOS] 
*[https://note.com/jamesmondo/n/nc76e31402be8?hl=en BSD] 


*[https://www.raspberrypi.com/software/operating-systems/ PiOS Lite] and then [https://hstwb.firstrealize.com/ HST] 
*[ PiMiga for pi4 and pi5] 
*[ amibian for pi2 and pi3] 
*[ retropie pi1 and 2] 


Other alternative lighter smaller than Pi OS 
*[https://aros.sourceforge.io/nightly1.html Aros 64bit ARMV8 single core] 
*[https://www.riscosopen.org/wiki/documentation/show/Welcome%20to%20RISC%20OS%20Pi RiscOS on Pi3 and Pi4]
*[https://github.com/michalsc/Emu68 ARM based realtime JIT 68k for amiga computers] 
*[https://github.com/JJDSNT/bellatrix/releases/ Alternative use of Emu68 on Pi3b] 
*[https://github.com/stevereaver/uaos uaOS with Emu68k] 
*[https://github.com/aros-development-team/AROS/commit/f80a268607dfae81b2db94755ab4e4d31ccb72d6 m68kemu library reference] 
*[ HaikuOS]
*[https://github.com/raspberrypi/noobs NOOBS] os loader with successor [https://github.com/procount/pinn PINN] 
*[https://github.com/maxnet/berryboot berryboot]

*[https://github.com/brianwiddas/pi-baremetal Bare Metal Access on Pi 32bit] 


Testing procedure is put sd card in, connect board to board if necessary, plug in hdmi and then power nothing else is done especially CSI DSI etc 

[https://www.raspberrypi.com/documentation/computers/compute-module.html CM5] has the same 55mm x 40mm 2x100pin connectors form factor as the CM4 but [https://www.epdtonthenet.net/article/214508/Key-Considerations-When-Migrating-from-Raspberry-Pi-CM4-to-CM5.aspx some pins and other small things] have changed. Will need the [https://raspipcb.com/tech-blog/raspberry-pi-cm4-vs-cm5-difference-in-booting-from-sd-card/ right IO board to suit] 

*Green [ Raspberry Pi Compute Module 5 IO Board REV2 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1967]] - untested 
*Green [ RPi Compute Module 5 IO board REV1 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1751]] - untested 
*Black SupTronics Geekbord X1500 CM5 IO Carrier Board - untested
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*[https://sipeed.com/nanocluster Sipeed NanoCluster] - untested up to 7 CM5 
*Green BentoIO CMX0 - untested 
*Box EDATec ED-CLAWBOX - untested 
*Home Assistant Yellow - Kit with PoE with Raspberry Pi Compute Module 5 - untested 
*Blue [https://www.waveshare.com/wiki/CM5_PoE_BASE_A Waveshare CM5-PoE-BASE-A] - untested 
*Box  Waveshare [ CM5-POE-BOX-A] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-B Waveshare CM5-IO-BASE-B] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-A Waveshare CM5-IO-BASE-A] - untested 
*Blue Waveshare [https://www.waveshare.com/wiki/CM5-NANO-B CM5-NANO-B] - untested 


*[https://carboncomputers.us/products/pi-flux piFlux]
*[https://carboncomputers.us/products/ Zitaotech Hackberry] CM5 lite only - 
*Portable [https://www.waveshare.com/pocketterm35.htm Waveshare PocketTerm35] with Pi4B or Pi5 - untested 
*Box [https://www.clockworkpi.com/uconsole ClockworkPi uConsole][https://www.youtube.com/watch?v=EtI_bAahbR8 CM4 into an adapter or CM3 into so-dimm - Cyberdeck] - untested 


*Green RPi [https://datasheets.raspberrypi.com/cm4io/CM4IO-KiCAD.zip Compute Module 4] [https://datasheets.raspberrypi.com/cm4io/cm4io-datasheet.pdf IO board] V1.4 [https://datasheets.raspberrypi.com/cm4io/CM4IOUSB3-KiCAD.zip USB3] [https://datasheets.raspberrypi.com/cm4io/cm4iousb3-appnote.pdf CM4ISO] [https://datasheets.raspberrypi.com/cm4/cm4-datasheet.pdf Dual100pin] (2020) aka Development Platform Board - untested 
*Purple Pi Hut Cytron CM4 Maker Board - untested 
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*[ KubeSail PiBox mini 2] 
*Home Assistant Yellow with Raspberry Pi Compute Module 4 - untested 
*[ Turing Pi V2] - untested CM4 with 260-pin SO-DIMM socket adapters and/or nvidia jetson nanos - untested 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-C Waveshare CM4-IO-BASE-C] - untested but binary blobs Rev01 Rev02 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-B Waveshare CM4-IO-BASE-B] - untested but binary blobs 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-A Waveshare CM4-IO-BASE-A] - untested but binary blobs 
*Blue [https://www.waveshare.com/wiki/CM4-NANO-B Waveshare CM4-NANO] - untested but usb and audio turned off or rerouted 
*Black [ Seeed Studio with BigTreeTech BTT pad 7] - bin blobs? 


CM3 has a 200 pin sodimm ddr2 connector form factor but not electrically SC0028, SC0029 
*Blue [https://wiki.geekworm.com/CM_IO_Board Geekworm RPi Compute Module IO Board] [https://github.com/geekworm-com/cm-io-board CSI DSI] with CM3 in ddr2 slot underside - '''works''' if SW1 on but CM3+ '''does not''' 
*Green [https://cdn-shop.adafruit.com/product-files/3442/CMIO_schematic.pdf RPi V3 IO board CM3IO] and CM3 Lite - untested 
*Green [https://turingpi.com/ turingpi v1 cluster] - untested up to 7 cm3 7xlan9514 12V discontinued, 3 x Pi4 homelab maybe better 
*Blue [https://www.waveshare.com/wiki/Compute_Module_PoE_Board Waveshare Compute Module PoE Board] and CM3 lite (if not lite, write files to internal eMMC fat32) '''AVOID''' bin blobs 
*Blue [https://www.waveshare.com/compute-module-io-board-plus.htm Waveshare Compute Module IO Board Plus] [https://www.waveshare.com/wiki/Compute_Module_IO_Board_Plus wiki] [https://forums.raspberrypi.com/viewtopic.php?t=235695 pin settings] with CM3+ Lite - '''AVOID''' binary blob 


*[ Pi02w on Geekworm SupTronics X305 Raspberry Pi Zero IO Baseboard] - untested 
*[ Spotpear Pi Zero 2w to Pi3b format-ish] - untested 


*[ pi-top v4] box has 128x64 oled display, micro hdmi, 19Whr battery with pi4 and 15V PD 36W min needed 
*[ pi-top v3] three green pieces, heatsink covers most of the base tray, pi-top hub mk1 lhs and Pi1B Pi2b Pi3b rhs secured from below, black rounded strip with pi-top above keyboard, 13.3&quot; HD 1366 x 768 display, small touchpad, 
*[ pi-top Model 2.0] pi-top on bottom bezel of 14-inch green laptop, large trackpad, keyboard slide down to reveal main system hub on slide rails moved to the right, Raspberry Pi3b screws down, hub slides in, 18V 2.5A 45W charger brick, battery 11.1V 3500mAh 38.85Wh and storage PiTopOS 
*[ Pi-Top CEED Raspberry Pi Modular Educational Desktop with RPI3] monitor 
*[https://www.indiegogo.com/en/projects/jesselozano/pi-top-a-raspberry-pi-laptop-you-build-yourself Pi-Top v1] wedge laptop with RPi2 


&lt;pre&gt;
2008 Trustees collected for Foundation
2009 Pi Foundation charity status gained 
2010 
2011 First Raspberry prototypes 
2012 First boards go on sale at CPC and RS. The Model A and B 700 MHz Arm11 - February 29th BCM 2835
2012 First million sold - more than the 10,000 original planned and anticipated 
2013 First Alpha Experimental builds of AROS Native for the 32bit Pi 
2013 Pi Trading launched making grants available, providing in house educational resources and Pi Academy for teacher training 
2013 Over two million sold 
2014 Over three million sold 
2014 Pi 1 Model B+ introduced that moved composite video to audio jack and same half gig of memory 
2014 Pi Model A+ v1.1 no ethernet and 1 usb - a little smaller - 
2015 Over four million first gen pis sold  
2015 Pi Zero 1.2 BCM2835 first production revision released with no camera port 
2016 Pi0 1.3 released with camera csi connector 
2017 Pi Zero W v1.1 1GHz Pi0W, single-core 32bit CPU BCM2835 released with Cypress CYW43438 wireless 
2020 Raspberry Pi Pico SC0919 with RP2040 32-bit 2Core ARM Cortex-M0+ up to 133 MHz - 264KB of SRAM and 2MB of on-board QSPI Flash - 
2024 Raspberry Pi Pico 2 with RP2350 2Core 32bit Arm Cortex-M33 and 2core open-hardware [https://github.com/wren6991/hazard3 Hazard3 RISC-V] 

2015 Pi 2 Model B v1.1 BCM2836 900/600 MHz ARM Cortex-A7 Armv7 quad 32bit, 32bit VideoCore IV GPU - 1Gb RAM - 5V 2A micro usb - SMSC LAN9514 chip - 
2015 Over a million pi2s sold 


2015 Raspberry Pi 2 Model B version 1.2 Pi2bv1.2, aka Pi2B2 has armv8 BCM2837 underclocked to 900Mhz without wifi/bluetooth module 
2016 Pi 3 Model B - Broadcom BCM2837 SOC four 64bit ARMv8 Cortex-A53 1.2GHz 32bit 1080p VideoCore IV GPU - 1Gb DDR2 - bluetooth 4.1, Cypress CYW43438 wireless 802.11n - 4 x USB2.0 ports - 5.1V 2.5A - SMSC LAN9514 chip 
2016 PIs total over 10 million worldwide 
2017 Compute Module 3 CM3 with BCM2837B0 armv8 Quad 64-bit - small 67.6mm x 31mm board which fits DDR2 SODIMM connector but not electrically compatible which plugs into needed IO board - beware of the I2C protocol issue 
     1Gb LPDDR2 RAM - Lite or 4Gb Emmc storage 
2017 12 million pis sold in total 
2018 Pi 3 Model B+ - 4c A53 BCM2837B0 1.4Ghz - 1Gb, wireless 802.11ac, gigabit ethernet (300Mbit/s) and bluetooth 4.2 - power over ethernet - 4 x USB2.0 ports - Microchip LAN7515 chip 
2019 Over 15 million sold 
2019 Pi 3 Model A+ with BCM2837b0 Cortex-A53 64-bit SoC @ 1.4 GHz with 512Mb LPDDR2, 1 usb2, 1 hdmi, 1 micro usb 5V 2A - no ethernet - 
2019 Raspberry Pi Compute Module 3+ CM3+ - Broadcom BCM2837B0 1.2Ghz, Cortex-A53 (ARMv8) 64-bit SoC on DDR2 SODIMM mechanically compatible only factor - IO board required 
     1Gb DDR2 and 8GB, 16GB, 32GB or a Lite variant without eMMC 
2021 Pi zero 2 (w or no W) RP3A0 quad 1GHz Cortex-A53 64bit BCM2710A1 512mB SDRam 
2025 edaTEC CM0 ED-CM0NANA with additional dev board with quad 1Ghz A53 with 512Mb Raysan RAM, 2 USB2 and 10/100 ethernet - pico castellated edge
 

2019 Pi 4 Model B v1.1 RPI4B - BCM2711B0T quad 64bit A72 1.5GHz, 4K VideoCore VI, AC wifi, Bluetooth 5.0, GbE Broadcom BCM54213PE (PHY ID 0x600d84a2), 2 micro hdmi decode up to 4K, USB-C 5.1V 3A power, 2xVLI VL805 USB 3, 2xUSB 2.0, 2GB 9LDWW D9WHZ or 4GB 9FDWW D9WHV, 8GB 0AA47 D9ZCL ddr4 ram 
2020 Silent Pi 4 v1.2 upgrade with more USB-c psu support 
2020 PI400 BCM2711C0T 1.8GHz 4Gb DDR4 inside keyboard, 5.1V 5A 27W usb-c psu, 2 micro hdmi, external ide style 40pin gpio, no audio port - 
2020 Raspberry Pi Compute Module 4 BCM2711B0T on new 55mm x 40mm 2x100 pin form factor with extra breakout IO board 
     CM4101000 1Gb RAM Lite SOM 
     CM4102000 2GB RAM Lite 
     CM4104000 4GB RAM Lite 
     CM4004008-4GB-RAM 8GB-EMMC SOM System on Modules 
     CM4104032 4GB RAM 32GB emmc 
     CM4108000 8GB RAM Lite 
     CM4008016 8GB RAM 16Gb eMMc
2021 Raspberry Pi SC0763 Compute Module 4S CM4S with ddr2 sodimm pinouts but not electrically the same with suitable IO board extra cost - 
     CM4S01000 1GB RAM Lite
     CM4S01008 1GB RAM 8GB eMMC Flash
     CM4S02000 2GB RAM Lite
     CM4S04000 4GB RAM Lite
     CM4S04016 4GB RAM 16Gb KLMAG1JETD-B041 
     CM4S08000 8GB RAM Lite 
2021 Pi 4 v1.4 BCM2711B1 upgraded power regulator, to deal with 8gig of ram being more power hungry 
2021-48 Raspberry Pi 4 model B v1.5 2GB 


2023 Pi 5 v1.0 BCM2712 Quad A76 @2.4Ghz - VideoCore VII - no audio socket - dual 4k from mini hdmi - fan connector - 5.1V 5A psu 
2024 Pi 5 2GB DDR4 version uses BCM2712D0 
2024 Pi-500 with 8Gb LPDDR5 and membrane keyboard 
2024 Pi 5 v1.1 
2024 Raspberry Pi Compute Module 5 CM5 BCM2712 55mm x 40mm form factor with additional IO board 
     CM5004000 04GB RAM 0GB eMMC Lite
     CM5008000 08GB RAM 0GB eMMC Lite
     CM5016000 16GB RAM 0GB eMMC Lite
2025 Pi-500+ with 256GB NVMe storage, 16GB LPDDR4 RAM, and Gateron KS-33 Low Profile Blue mechanical keyboard switches 
2025 Pi5 1GB DDR4 announced 


2022 PiOS linux goes 64bit 
2024 Pi Trading IPO stockmarket stock exchange listing 


2026 April and May Aros 64bit fixed, added AHI audio, VC4 gfx started, usb functions added to rom  
2026 June and July Aros 64bit usb2otg started, dma.resource, sdio.resource, bwfm.device wifi added 
2026 Late July daily 64bit Pi3 LE little endian builds start 
2026 August Pi 4, 400, 5 and 500 DTBs added, expanding existing support and wifi for Pi4 and Pi5 
2026 August Pi5 HAT+ nvme and HDMI, AHI RPiI2S added, Pi4 HVS5 video scaler started, 
2026 
2027 


2028 Pi 6 
&lt;/pre&gt;


The vcgencmd can be used to inspect and dump the current system configuration. 
vcgencmd runs on top of VCHIQ as an RPC. The mailbox interface is an alternate but much simpler RPC. 
VCHIQ is a bridge (queue) between the CPU and the GPU so they can communicate with the firmware. 

Loads of [https://github.com/6by9/rpi3-gpiovirtbuf/blob/master/rpi3-gpiovirtbuf.c mailbox] which uses the GPIO control calls. [https://github.com/raspberrypi/firmware/wiki/Mailboxes may also be of interest] 

A fair number of vcgencmd examples (search for vc_vchi_gencmd_init). [https://www.raspberrypi.org/forums/viewtopic.php?t=229203#p1406112 sends the relevant vcgencmd commands] to update the scaling kernel, but the [https://github.com/raspberrypi/userland/blob/master/host_applications/linux/apps/gencmd/gencmd.c command] is just a text string. Parsing and execution of the instructions is performed by the VideoCore firmware. 

The Raspberry Pi runs two separate operating systems: Linux/Aros on the ARM, and a threedx RTOS called vcos running on the Videocore 4 VPU: vcos is commonly called &quot;the firmware&quot;. Vcos is tasked with performing certain system services, for example running the display and audio outputs. The VCHI driver provides an interface to allow drivers to talk to vcos. 


Doubtful, on any [https://www.web3d.org/ Web3d] [https://developer.mozilla.org/en-US/docs/Web/API/WebGL_API WebGL] or [https://github.com/immersive-web/webxr WebXR] [https://developer.mozilla.org/en-US/docs/Web/API/WebXR_Device_API Device API] [https://developer.mozilla.org/en-US/docs/Web/API/XRInputSource XRInputSource] support. Hopefully, never/limited support features like location, peer-to-peer, invasive web apps, unwarranted storage, payments, proprietary video streaming etc 

*spreadsheet [https://git.sheetjs.com/sheetjs/sheetjs sheetjs] [https://github.com/mleibman/SlickGrid SlickGrid] [https://github.com/6pac/SlickGrid SlickGrid] [https://github.com/jspreadsheet/ce jspreadsheet ce] [https://github.com/dream-num/Luckysheet Luckysheet] [https://github.com/ruilisi/fortune-sheet fortune-sheet] [https://github.com/dream-num/univer/ univer]  probably without xlsx support 
*presentations [https://github.com/impress/impress.js/ impress.js simplified] [https://github.com/bwlewis/slides slides] [https://zenomt.github.io/mdslides/ github markdown slides] [https://github.com/Patternslib/slides Patternslib slides markdown] probably without pptx support 
*weather [https://github.com/kaushalsahu07/weather weather], [https://github.com/Himanshu3412/Weather-Forecast Weather Forecast],  


==Future==


[https://github.com/ARMSX2/ARMSX2 Arm pi of pcsx2] 


[https://tube.cadence.moe/ Cloudtube], [https://github.com/TeamPiped/documentation/blob/main/content/docs/public-instances/index.md TeamPiped], [], [], [], 

[https://hyperpipe.codeberg.page/ hyperpipe], [https://ytify.pp.ua/ ytify], [], [], 

[ ytdl], [https://github.com/golddominik893/liberatube liberatube]

[https://git.lolcat.ca/lolcat/4get 4get], [https://github.com/hnhx/librex librex], [], [], 


{{BookCat}}</text>
      <sha1>jrkb3xa0vkkdbksjd47u6p1p6g49g7s</sha1>
    </revision>
    <revision>
      <id>4676520</id>
      <parentid>4676518</parentid>
      <timestamp>2026-10-17T13:39:13Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4676520</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="106192" sha1="9acvq1hbhwjzi6rpuy2tcz7h8oyh6id" xml:space="preserve">{{ArosNav}}

[[#Native]]

[[#Hosted]]

[[#Build]]

[[#Hardware]]

[[#References]]

[[#Future]]


==Introduction==


[[File:Scalos00.png|thumb|Scalos on Aros Pi3b]]

Aros aims to cover Pi 3 to 5 512Mb+ RAM 


Options to boot from using a good power source to prevent the yellow lightning symbol. 
*With Pi3b+ the max you can get is 5.1V 2.5A with micro usb.
*With Pi4 5.1V 3A with usb-c 
*With Pi5 5.1V 5A, the amps went ever upwards, even to 5.1V 9A with usb-c 


* Pi500+ keyboard wedge - working but not much tested esp [https://github.com/aros-development-team/AROS/commit/48e9c8edcca4b5c1e1fe0b1123f2129f624af67b power button] 
* Pi500 wedge with up to date bootloader via PiOS - working but not much testing esp [https://github.com/aros-development-team/AROS/commit/48e9c8edcca4b5c1e1fe0b1123f2129f624af67b power button] 
* Pi 5  - Quad A76 64bit ARMv8 and RP1 &quot;southbridge&quot; with VideoCore 7 D0 (rev1.1) - untested 
* Pi 5  - Quad A76 64bit ARMv8 and RP1 &quot;southbridge&quot; with VideoCore 7 Pre-D0 C1 (Rev1.0) - untested 
* Pi400 RPI-400 keyboard wedge - resolution changing and audio from micro hdmi0 (near 40pin) and micro hdmi1 (near usb-c psu) - Fn F10 0x5e power on and off works or held down for over 7 seconds auto shutdown - keyboard ok - wifi and lan ethernet testing - 
* Pi 4  - Quad A72 64bit ARMv8 with VideoCore 6 
* Pi 3  - Quad A53 [https://www.raspberrypi.com/documentation/computers/processors.html 64 bit] ARMv8 with VideoCore 4 with '''fan''' to prevent overheating cpu 82C+ throttling 
* Pi02W - Quad A53 64bit - boots but [https://forums.raspberrypi.com/viewtopic.php?p=2387984#p2387984 usb not working but did in the past], 


* Pi 2 - Quad 32bit ARMv6 with VideoCore 4 - mostly not 64bit compatible 
* Pi Model B+ 32bit ARMv6 with VideoCore 4 - not 64bit compatible 
* Pi Model A and B 32bit ARMv6 with VideoCore 4 - not 64bit compatible 


===Native===

* 2013-03 Kalamatee starts work
* 2015-04 Work continues with mschulz on the kernel and Kalamatee (NicJA) on gpio and usb
* 2018 [https://www.patreon.com/posts/i-owe-you-some-20956961 mschulz resume adding BE big endian support], [https://www.patreon.com/michal_schulz/posts Big endian on Pi]  
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bsek latest commits for pi 3b, 4 and 5 64bit] 
* 2026 [https://github.com/aros-development-team/AROS/commits?author=metaneutrons latest commits for Pi5]
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bitplane latest commits for ARM]


====64bit====

'''Download''' A [https://archive.org/details/piAROS Pi Distribution (Distro) has started] and the contents copied to fat32 8GB+ microSD card (there will be drawers/folders - boot c Classes Demos Developer Devs Extras etc only showing). The SD can be plugged in to the Pi. And power on. [https://pi.amiga.icu/ Repository]

'''Not recommended''' but [https://aros.sourceforge.io/nightly1.html RaspberryPi 3, 3+, 4 and 5 64bit ArmV8 nightly builds] [https://sourceforge.net/projects/aros/files/ and alternative site and nightly2] which is a test version of '''very few''' apps with both raspi-aarch64-system and raspi-aarch64-contrib can be unbz2'd to a SD or SSD as appropriate. 

64bit build works well on a single core LE little endian. Multicore [https://github.com/aros-development-team/AROS/commit/1df0747c2bda3523a43029725a709b1f377d84ec may follow]. Any issues booting could be down to the SD card so please use another SD to see if it is resolved. Remember Aros Arm uses FAT32 and Aros can detect issues with this format very acutely (once fault found, FAT 0x0FFFFFF7 bad cluster so no files written after that, no repair). Please report your experiences in the [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2138&amp;pid=15057#post_15057 Aros forum thread], [https://forums.raspberrypi.com/viewforum.php?f=179 Raspberry Pi Aros Dev and User forums], [https://forums.raspberrypi.com/viewtopic.php?p=2387984#p2387984 previous Raspberry Pi forum thread]. Any bugs or issues can be [https://github.com/aros-development-team/AROS/issues described here to fix] 


*Pi500+   untested usb3 booting or nvme ssd 
*Pi500    untested usb3 booting 
*Pi5      untested usb3 booting 
*Pi400    boots with '''USB3''' port based sata3 ssd 
*Pi4      untested (may need eeprom update from PiOS or Pi SD Imager) 
*Pi 3 B+  is pre-configured for USB sata3 boot - untested 
*Pi 3 B   may need [https://www.youtube.com/watch?v=ubnwvxF3Klc PiOS to set OTP to boot from usb - do so at your own risk] - if OTP set to usb, boot works but slower than SD card 

Speed write wise (top faster) 
&lt;pre&gt;
*NVME Pi5 untested    &gt;1000MB/sec  or faster if matched correctly 
*Sata3 ssd              500MB/sec
*SD        V90           90MB/sec  4K maybe 8K 
*SD        V60           60MB/sec  1080p 
*SD     U3 V30           30MB/sec  720p 
*SD C10 U1 V10 A1 A2     10MB/sec  minimum should be used now 
*SD C06                   6MB/sec  
*SD C04                   4MB/sec 
&lt;/pre&gt;


As a homage to the past, Aros shows a reduced number of icons but this can be changed by left mouse click in the window and then right click down to Window -&gt; View -&gt; All files

Windows can be manipulated by the top (moving) and the bottom right corner (resizing) only. 

Zune like MUI gui interface, has a unique quirk in that after changing a setting in a text box, you may sometimes need to press Enter/Return before clicking OK, Save, etc 


Double left mouse click on most picture (Developer/Debug/Tests/Datatypes), audio and video files are supported, via datatypes, by the multiview application. 
Esc escape key usually closes open windows even the desktop 

In Prefs/Appearance some decorative theming elements need work. There is a few Mason icons in /Prefs/Presets/Icons/Mason/ and the ever present default Gorilla - Icon exchange in works 

For more intensive graphics applications, you may need to edit config.txt in the root folder and change 128M to 256M to adjust more memory to graphics usage 

If your cursor should '''appear''' to vanish, fear not it is still there. Please head to the top of the screen i.e. the title bar, hold down the left click mouse and drag the screen down a little and the cursor will appear again. Then you can drag the screen up again. 


Like most amiga like OSs the audio and networking need to be setup manually 

Audio AHI prefs - Mode settings tab - needs both Music unit and Unit 0 set to RPiHDMI:16 bit stereo++  or RPiPWM:16 bit stereo++ at 44100Hz. Press '''Save or Use''' button after each choice 


For wireless, please use the Wifi prefs and already selected device bwfm.device. Press Scan and double right click on the router and enter password. You may need to setup after every power off
*if asking for password again - press cancel and go to Network Prefs, Wireless Networks tab and highlight the router line and hit the remove button and press the cancel button. Retry with Wifi prefs again 
*...waiting for an address - Disconnect and try Connect 
Until, Connected to &lt;router&gt; - 192.168.x.x 


For lan ethernet port, please use Network prefs and the following hardware is 
*lan9514    Pi3b Pi2 not supported at the moment 
*lan7515    Pi3b+ type into Device  usblan78xx.device as net0:  remove other device(s) 
*bcmgenet   Pi4 Pi400 choose for Device bcmgenet.device 
*cdnsgem    Pi5 Pi500 Pi500+ RP1 i/o for cadencegem 
 (network prefs may forget random information when rebooted) 


Summary
&lt;pre&gt;
*3b    ethernet not supported, usb ethernet not working but wifi prefs setup works 
*3b+   wifi working and ethernet works 
*4     untested 
*400   wifi and ethernet untested 
*5     wifi and ethernet untested
*500   wifi and ethernet untested
*500+  wifi works 
&lt;/pre&gt;


Type in 'aarch64' in the [https://archives.arosworld.org/index.php?function=search&amp;tool=simple search box] and you will see available software packages / apps. apkg can be used to inspect and install applications. 

[http://archives.arosworld.org/index.php?function=browse&amp;cat=network/browser amelinium web browser (JS 1.6 ES9 ECMASCript 2018)] is available with an [https://eab.abime.net/showthread.php?t=122494&amp;page=80 eab thread] reminiscent of [https://github.com/zapek/Voyager Voyager] and to a lesser extent [https://github.com/amigazen/aweb3/ Aweb JavaScript 1.5 (ECMAScript 3)] as css and javascript websites can be slow to load or resolve (no JIT) and nothing from facebook, reddit etc. 

Press Cancel at screenmode selector or -wb argument to get windowed version. You could use the Shift + Del shortcut or mouse wheel should work to delete all text at once. Html5test gives 189 (1.29), 300 (1.31), 301 (1.39) out of 555, some bigger Amiga like browsers are around 370+ but it does less better. 

You may have to delete the cache (Menu -&gt; Page -&gt; Delete cache) to fully retest big Amelinium updates or free up space. 
Be aware [https://pianetaamiga.it/en/reportage-pianeta-amiga-2026/ some site pages] can use up hundreds of MBs of cache very quickly 

 DNS lookup failed...  close browser and reboot and setup wifi again - repeat until it works again 

 youtube video and audio - js button for javascript must be on/shaded -  Settings -&gt; Soundoutput - AHI 
Any restriction to lower resolutions is due to [https://docs.invidious.io/faq/#q-where-are-the-360p480p1080p-quality-options bandwidth]. Either CPU/GPU, internet speed and/or video quality. Pi3 can expect 480p (wifi) to 720p (ethernet). Pi4 expect (wifi)  (ethernet). 

Telegram https://t.me/s/channel_name for public messages from vamped_amiga chatamigagames demoscenecracktros 

*art local js apps like dpaint.js 


There is normally no Bluetooth support for most amiga like OSs but Aros has one [https://github.com/aros-development-team/AROS/commit/6942cbfbf66426d21963a7fcd8aba6aff611a9e0 work in progress] [https://github.com/RPi-Distro/bluez-firmware/tree/pios/trixie/debian/firmware/broadcom firmware] 

*Bluetooth 4.1 BCM43430A1.hcd Pi3B, Pi3A, Zero 2W 
*Bluetooth 4.2 BCM4345C0.hcd  Pi3B+, Pi4 
*Bluetooth 5.0 BCM4345C5.hcd  Pi4B rev, CM4 and maybe Pi5 and CM5 

&lt;pre&gt;
*bthid    keyboard mouse support 
*btserial serial 
*btpan    short range wireless connecting devices 
&lt;/pre&gt;


Only the Pi5 has a RTC real time clock, the other Pis will need to use ntp services [https://github.com/aros-development-team/AROS/commit/29cd4116330dc7f692d90757eacc59fb3f31ae70 sntp] with time.cloudflare.com pool.ntp.org or Cloudflare 162.159.200.1, 162.159.200.123, 2606:4700:f1::1, 2606:4700:f1::123 or [https://github.com/bohunamiga/PiNTP PiNTP -s goodtime.ijs.si or ntp1.ptb.de] to get the date and time from the internet. Can use date in a shell e.g.  date 24-Dec-2026 23:59:59  but this will need to be done again after every reset/power off. Maybe [https://github.com/aros-development-team/AROS/commit/28674a157bc56175aa668e7b62dca6fa740578dc ds3231 rtc with dtoverlay=i2c-rtc,ds3231 in config.txt] 


It helps to have all usb devices already plugged in before power on to detect at the moment. Even then some usb devices will freeze the mouse cursor and the only resolution is to remove the offending usb device and reinsert. Sometimes, the reinsert leads to the mouse cursor vanishing, it is still there and responds to left mouse clicks, top of the screen and pull down the screen. 

USB classes support from Prefs/Trident is still work in process 
*usbaudio working on usb3 port (blue) on pi4, 400 but not working (no rt isochronous) on usb2otg (white or black) for pi3b, zero 2w 
*[https://aminet.net/package/mus/midi/camd camdusbmidi] detects midi devices without a preferences file (Prefs/Env-Archive/sys/midi.prefs) as [https://www.youtube.com/watch?v=RBxHkwy4Nrw auto setup now] possibly with [https://github.com/metaneutrons/mt32-pi metaneutrons mt32-pi] [https://github.com/rtzor/mt32-pi mt32-pi fork] [https://github.com/ahmadexp/mt32-pi fork] [https://github.com/gmcn42/mt32-pi-control control of] [https://github.com/dwhinham/mt32-pi mt32-pi pi3+]. Alternative of [https://homspace.nl/samplerbox/ SamplerBox]. 

Will need developer clang gcc tools to look at 64bit ports of [https://archives.arosworld.org/?function=showfile&amp;file=driver/audio/usbmidi.i386-aros.lha usbmidi], [https://aminet.net/package/mus/midi/CAMD_Toolkit CAMD_Toolkit], [https://aminet.net/package/mus/midi/camdtools camdtools], [https://github.com/cnvogelg/amiditools amiditools], [https://github.com/timoinutilis/midi-sequencer-amigaos horny src], [https://aminet.net/package/mus/midi/horny-base horny-base], [http://bnp.hansfaust.de/index.html BnP], [https://arosarchives.os4depot.net/?function=showfile&amp;file=audio/misc/timidity.lha timidity], 


Regarding 680x0 emulation, there are several options (not implemented yet) that could be considered 
*[https://github.com/aros-development-team/AROS/blob/6722a0ae9e03fe5d26e32703360bd2059e0864cc/rom/m68kemu/README.md?plain=1#L424 m68kemu.library] for some Amiga productivity where the cpu is emulated and the system calls are redirected to Aros ones
*[https://github.com/BlitterStudio/amiberry amiberry] (winuae) for everything else like games 
*[https://github.com/jonx/AROS/tree/aarch64-darwin-graft/arch/all-darwin/libs/emu68k emu68k] 
*[https://scriptedamigaemulator.net/ Scripted Amiga] with [https://github.com/naTmeg/ScriptedAmigaEmulator ScriptedAmigaEmulator] or older [https://github.com/gbraad-amiga/ScriptedAmigaEmulator2 ScriptedAmigaEmulator2] 
 Hopefully getting Pi3 up to 25Mhz 68040 (non JIT) and 50Mhz 68040 (JIT) 
 Pi4 maybe getting up to 50Mhz 68040 (no JIT) and 100Mhz 68040 (JIT) 


[https://pinout.xyz/ GPIO 40 pins] [https://learn.sparkfun.com/tutorials/raspberry-gpio/gpio-pinout pinout] 

Some exceptions:

*Physical pins 27, 28 (GPIO0, 1) are an internal I2C bus and should not be used
*The other I2C on pins 3, 5 (GPIO 2, 3) can be used generally, but be aware they have permanent pull-up resistors to 3.3V
*For MIDI use USB but there are dedicated UART pins 8, 10 (GPIO 14, 15).

With a HAT it's more awkward -- you need to know which pins are used by the HAT and avoid them. Hopefully this will be documented.

Remember all GPIOs are 3.3V (not 5V tolerant), floating/noisy inputs can cause odd behavior, and that shorting the power supplies can cause instant death of the Pi.

In the shell (Cntrl + C to end) 

 GPIO PIN/A/N,SET/N,GET/S,MODE/K,PULL/K

Controls and queries hardware GPIO pins via gpio.resource which is stored in the rom or Devs/ '''please test''' 

*PIN   -- (Required) Target GPIO pin number (e.g. 12).
*SET   -- Set pin output value to 0 (LOW) or 1 (HIGH).
*GET   -- Read and print current digital input level (0 or 1).
*MODE  -- Configure pin mode: IN (Input), OUT (Output), ALT (Alternate).
*PULL  -- Configure pull resistor: NONE, UP, DOWN.

EXAMPLES
&lt;pre&gt;
GPIO 12 MODE OUT
GPIO 12 SET 1
GPIO 12 GET
GPIO 13 PULL UP
&lt;/pre&gt;


[https://gpiozero.readthedocs.io/en/stable/installing.html Current] [https://gpiozero.readthedocs.io/en/v1.2.0/api_boards.html old support for gpiozero is unknown at present] [https://energenie4u.co.uk/res/pdfs/ENER314%20UM.pdf and associated 433MHz equipment] [ USA X10 security and lights via USB] [ OpenHab with Shelly Smart Plug connected over Wi-Fi, controlled by MQTT or HTTP] 


Printing only with Postscript but [https://github.com/bohunamiga/MintPRINT one] of [https://github.com/boingball/MintPRINT two] [https://github.com/Andiweli/AmiAirPrint/tree/main AirPrint] IPP has been attempted with [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2061&amp;pid=13954#post_13954 discussion] 


Youtube 

[], [], [https://www.youtube.com/watch?v=X4fmWAIv7FE Aros native on Pi3b], 

[], [], [https://www.youtube.com/watch?v=TSxlYb1eQWU Installed on Pi3b+], 

[], [], [https://www.youtube.com/watch?v=NFF1H3jCoz8 testing Aros native on Pi400], 

[], [], [https://www.youtube.com/watch?v=nIVx7mh1E1Q&amp;pp=ygUHYXJvcyBwadIHCQkTDAGHKiGM7w%3D%3D Aros on Thumb 2 based 32bit-ish ARM STM32H743 board], 


[https://www.youtube.com/watch?v=zQM4CD64xDE&amp;t=612s&amp;pp=ugUEEgJlbg%3D%3D Performance under Linux] but on Aros... 

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot; |Pi
! width=&quot;10%&quot; |Single Core 2D
! width=&quot;10%&quot; |Single Core 3D
! width=&quot;10%&quot; |Single Core 3D
! width=&quot;10%&quot; |SMP 2D
! width=&quot;10%&quot; |SMP 3D
! width=&quot;10%&quot; |SMP 3D 
! width=&quot;35%&quot; |Comments
|-
| &lt;!--Pi--&gt;Pi3 
| &lt;!--Single Core 2D--&gt;
| &lt;!--Single Core 3D--&gt;
| &lt;!--Single Core 3D--&gt;
| &lt;!--SMP 2D--&gt;
| &lt;!--SMP 3D--&gt;
| &lt;!--SMP 3D--&gt;
| &lt;!--Comments--&gt;
|-
|}


==== 32bit ====

For the Pi1 Pi2 Pi2B the status of AROS native ARMv6 for 32bit RasPi was OK. System booting, USB working (although with some issues but plans to fix them). 32bit native [http://www.aros.org/nightly1.html ARMv6 32bit nightlys] raspi-armhf-system raspi-armhf-contrib unbz2'd to fat32 microSD 


===Hosted===


AArch64 CPU backend for AROS, a Cocoa/Metal display, clipboard / host-volume / CoreAudio / BSD-sockets bridges, GPU 2D via gpufx.library, a 68k→AArch64 JIT (run68k), and a full Rust std port. On [https://www.jkn.me/blog/macaros-aros-on-apple-silicon/ latest Apple Silicon] [https://github.com/jonx/Macaros early buggy alpha version of hosted Aros .dmg on MacOS12+]. Please use [https://github.com/jonx/Macaros/issues MACAros github] for issues, features etc and possibly [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2030&amp;pid=13910#post_13910 here] 


[http://www.aros.org/snapshots1.html old linux and android hosted 32bit] 


==== Hosted ====

=====64bit=====

[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80&amp;pid=13667#post_13667 Ubuntu Linux PC hosted Pi compiler build] 

[https://github.com/BlitterStudio/aros-compiler-docker Docker based cross compiler for various Aros systems], 

[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80 From the Aros Raspberry pi 3 64bit thread] 
Instructions on building 64-bit Raspberry Pi AROS and cross-compiler from sources.

You will need:
- Ubuntu 24.04 or 26.04
- qemu-system-aarch64 installed
- Internet connection
- rpi-scripts.tar.gz downloaded (https://axrt.org/download/aros/rpi/rpi-scripts.tar.gz)

1) Install prerequisites:

sudo apt install git gcc g++ make gawk bison flex bzip2 netpbm autoconf automake libc6-dev liblzo2-dev libpng-dev gcc-multilib byacc python3-mako cmake yasm curl nasm

2) Clone sources

cd &lt;project-directory&gt;
git clone https://github.com/aros-development-team/AROS.git --recurse-submodules

3) Extract rpi-scripts.tar.gz. Copy all files into your project directory so that you have:

AROS (the directory with cloned sources)
fix-dotdot.py
rebuild.sh
recreate-sdcard.sh
run-qemu.sh
update-sdcard.sh

4) Run ./rebuild.sh. Select option 1) toolchain-core-aarch64

This will execute process of building a cross-compiler. During this process packages will be downloaded from Internet. This process can take up to 2 hours. If there are some missing dependencies, install them with 'sudo apt install' and restart this step.

5) Run ./rebuild.sh again. Select option 2) core-raspi-aarch64

This will build system files for 64-bit Raspberry Pi AROS. This process can take around an hour.

6) Run ./recreate-sdcard.sh

This will create an sdcard.img file with contents of previous step.

7) Run ./run-qemu.sh

This will start QEMU with SD card image and ROM images. It will boot into AROS.


=====32bit=====

Ubuntu VM approach to compiling [http://lallafa.de/blog/2013/06/building-aros-hosted-for-raspbian/ Linux hosted AROS June 04, 2013]

 ../AROS/configure --target=linux-armhf  --enable-includes=/usr/arm-linux-gnueabihf/include --x-includes=/usr/arm-linux-gnueabihf/include --x-libraries=/usr/arm-linux-gnueabihf/lib

arm-elf- is symbol-linked to arm-linux-gnueabi- (arm-linux-gnueabi- is more correct in this case, because it's going to be compiling the ARM AROSBootstrap for ARM Linux)

*armel - many of the &quot;android&quot; machines require since the entire OS is made for soft float VFP. 
*armfp - Efika MX target, Raspberry PI, EfikaMX, Pandora and virtually everything (VFP)

Keep in mind it's possible to start hardfp AROS hosted on softfp system, though, as long as no calls between AROS and host require floating point parameters. NOTE: hardfloat objects *cannot* be linked with softfloat objects - they have a different ABI.

Just keep in mind the arm nightly build machine is quite complex beast. It needs the x86_64 host compiler to compile AROS tools. The arm version is built every night using gcc-4.6.2 crosscompiler (built together with AROS) and successfully builds armel and armhf linux hosted targets.

*needs an AROS code compiler for ARM target 
*as well as unix compiler for ARM linux host (would be best to have both softfp and armhf, we have softfp only now) with full set of libraries and includes.

with—disable-crosstools  $AROS_CC  is always a wrapper around $KERNEL_CC  ?  If  so,  this  is  wrong for some ports. This can break Darwin, Windows and Android port. 
Yes,  Android  port  will  build.  And  even  work. But it's not good because  the  port  will  not  be ABI-compatible with other ARM ports. Android's ABI is different from GNUEABI. For example:

&lt;pre&gt;
enum test {foo, bar};
enum test testvar;
&lt;/pre&gt;

sizeof(testvar)  will  be  equal  to sizeof(int) in GNUEABI (Linux and AROS)  and  sizeof(short)  on  Android. This affects linking objects from static linklibs, for example.

Previously everything worked because $AROS_CC was a wrapper on top of $HOST_CC. And a real crosscompiler was used on non-ELF hosts.

Android is the same. $KERNEL_CC is incompatible with AROS.

compiler=kernel  is  appropriate _ONLY FOR CODE WHICH RUNS ON HOST OS_ (or  barebone  hardware,  if  we  talk  about  native).  This includes bootstraps,  their  linklibs, and host-side dynamic libraries (Windows makes extensive use of them because of architectural considerations.

No single AROS object should be compiled with this setting. $KERNEL_CC is really compatible with AROS *ONLY IN LINUX-HOSTED* and no more. On other systems (Darwin, Windows,  Android) this is not true any more, and compiler=kernel is never going to work.

If  you  want  to  compile your AROS module against host OS includes, append  the  following  to  USER_INCLUDES  (or  USER_CFLAGS,  this  is effectively the same):

 -isystem $(GENINCDIR) $(KERNEL_INCLUDES)

$(KERNEL_INCLUDES) expands to:

 -isystem  &lt;your_os_includes&gt;  -isystem  &lt;host_OS_gcc_private_includes&gt;
 -nostdinc

This makes AROS compiler adhering to host OS APIs.

If you want some preprocessor symbols based on what your host OS actually is, add something like -DHOST_OS_$(AROS_HOST_ARCH).

Why is there $(GENINCDIR) at all? Because host OS has its own libc includes, which would conflict with AROS ones. And the host OS libc is not binary-compatible with AROS one.

Why doesn't Windows-hosted port use $(KERNEL_INCLUDES) ? Because WinAPI includes conflict with AROS ones in fundamental typedefs, like WORD, BYTE and BOOL. It's almost impossible to deal with this in any other way than rewriting WinAPI definitions using AROS types.

Building under centos 6.3 (i386) currently, and AROS creates the toolchain itself. haven't yet committed the necessary changes but &quot;./configure --target=raspi-armhf&quot; is enough to start, then &quot;make arosboot-raspi&quot; will generate arosraspi.img (containing the bootstrap, kernel.resource, and exec.library) as well as arosraspi.rom (containing all the other essentials components such as dos, graphics etc).  It will also copy over a config.txt file to make the raspi bootstrap code load the correct kernel, and a cmdline.txt that enables exec debug output.

*armel = typically Debian 6, Ubuntu Maverick, Android, 
*armhf = typically Debian 7, Debian 8, Ubuntu Precise,

Cross-compiling Ubuntu ARM softfp 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armel' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armel] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armel.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabi libx11-dev:armel libsdl-dev:armel
&lt;/pre&gt;

&lt;pre&gt;
 ./configure --target=linux-arm --x-includes=/usr/include \
             --enable-includes=/usr/arm-linux-gnueabi/include
&lt;/pre&gt;

Cross-compiling Ubuntu ARM hard-float 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armhf' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armhf] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armhf.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabihf libx11-dev:armhf libsdl-dev:armhf
&lt;/pre&gt;

&lt;pre&gt;
    ./configure --target=linux-armhf --x-includes=/usr/include \
                --enable-includes=/usr/arm-linux-gnueabihf/include
&lt;/pre&gt;

Now, the AROS build is configured properly and all you need to do is:

 make


==Build==

===64bit===

[https://github.com/aros-development-team/AROS/blob/7016ce28bfdb754182edb16011c98faaf5413c29/arch/aarch64-raspi/boot/mmakefile.src#L180 boot makefile] 


===32bit===


# download/checkout the source someplace, e.g. /build/AROS-Src/
# make a directory to store external sources AROS downloads, e.g. /build/Ports
# make a build directory, e.g. /build/aros-raspi-armhf
# cd into the build dir, configure, and then run make -:

&lt;pre&gt;
&gt;cd /build/aros-raspi-armhf
&gt;/build/AROS-Src/configure --target=raspberrypi-armhf --with-serial-debug --enable-ccache --with-portssources=/build/Ports
&gt;make
&gt;make arosboot-raspi
&lt;/pre&gt;

then copy the files from /build/aros-raspi-armhf/bin/raspi-armhf/AROS/ onto an sdcard, and download/copy the Raspi firmware files onto it.

You should then be able to boot the sdcard on your RasPi.

The current W.I.P tree to svn. it can be built as follows ..
&lt;pre&gt;
./configure --target=raspi-armhf
make arosboot-raspi
&lt;/pre&gt;

That will generate arosraspi.img, arosraspi.rom and config.txt in bin/raspi-arm/AROS - so either copy just those files to a fat formatted SD card (with the firmware files on), or copy the whole contents of the AROS folder.

NB - if you have a Linux/other install, backup the existing config.txt first

arosraspi.img contains the bootstrap (which has very basic mailbox code, framebuffer/gpio init, and console &quot;emulation&quot; via code pinched from our libbootconsole), kernel.resource, and exec.library

arosraspi.rom contains all the other components needed to boot AROS.

The config.txt file will tell the RasPI bootstrap to load the arosraspi kernel and ramdisk (rom).

the bootstrap has minimal mailbox code, planning on adding either a resource or library that driver/app code will use to access it (likewise for GPIO)


Help building AROS hosted on Linux ARM

Was looking a way to use more my Handheld ARM based called Pyra (Dragonbox Pyra) an ARM (Omap5 cpu with 4GB ram) linux based machine (Debian Buster v10 with kernel 5.6.19 adapted) and have a try to compile the latest Aros sources by Deadwood directly on this device.
Compilation stops after build libpopupmenu.a and trying to build libatomic have this error:

&lt;pre&gt;
    Configuring build in bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic
    configure: WARNING: unrecognized options: --disable-nls, --without-x
    checking for --enable-version-specific-runtime-libs... no
    checking for --enable-generated-files-in-srcdir... no
    checking build system type... arm-unknown-linux-gnu
    checking host system type... arm-unknown-aros
    checking target system type... arm-unknown-aros
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for arm-aros-strip... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-strip
    checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
    checking for gawk... no
    checking for mawk... mawk
    checking whether make sets $(MAKE)... yes
    checking whether make supports nested variables... yes
    checking for arm-aros-gcc... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-gcc
    checking whether the C compiler works... no
    configure: error: in /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic':
    configure: error: C compiler cannot create executables
    See config.log' for more details
    make[2]: *** [mmakefile:4489: /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic/.configured] Error 77
    [MMAKE] make --no-print-directory TOP=/media/farox/pyra2/arosbuilds/toolchain-core-armhf-build SRCDIR=/media/farox/pyra2/arosbuilds/AROS CURDIR=tools/crosstools/gnu TARGET=tools-crosstools-gcc-libatomic-configure -s --file=mmakefile tools-crosstools-gcc-libatomic-configure failed: 512
    [MMAKE] Error: Error while running make in tools/crosstools/gnu: No such file or directory
    make[1]: *** [Makefile:361: linklibs-libatomic] Error 10
    make: *** [Makefile:183: crosstools] Error 2
&lt;/pre&gt;


looking at config.log on arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic

found that arosbuilds/toolchain-core-armhf/arm-aros-ld: cannot find -laeabi
so do make linklibs-aeabi-arm-quick
and the missing lib was built.

now the next stop is at
fatal error: bits/libc-header-start.h: No such file or directory
and
fatal error: sys/cdefs.h: No such file or directory
in many places so after checking that have this missing include files i have noted that my include path is a bit different, standard searching path is /usr/arm-linux-gnueabihf but in my system is /usr/include/arm-linux-gnueabihf
so if i add my path to some mmakefiles compilation goes on....but is a better way to add this path to avoid every mmakefiles to be changed?

fixed with adding
-I/usr/include/arm-linux-gnueabihf
to where is missing on mmakefiles like
USER_INCLUDES := -isystem $(GENINCDIR) -I/usr/include/arm-linux-gnueabihf $(KERNEL_INCLUDES)

P.s. I have changed many mmakefiles and have at least compiled (after many hours) the toolchain doing make every time in arosbuilds/toolchain-core-armhf-build (also have to disable making tests under cplusplus but don't remember the directory ...) but ask an help to have an automated way to correctly build without modify mmakefiles.


Last time built armhf target was around 2 years ago. At that point built is via cross-compilation from linux (ubuntu 22.04) using linux armhf crosscompiler (this can explain the path differences you are experiencing) as well as using AROS gcc cross-compiler in version 6.5.0 (build with option 21) in rebuild.sh). Since then AROS GCC has been updated to 10.5.0 and don't believe anyone tried to build the armhf target again.

My suggestion would be to downgrade GCC to 6.5.0 (via editing AROS/config/gcc_def file) and try to first build using cross-compilation from x86_64 linux. Once that works, you will have a &quot;template&quot; to compare to native compilation under arm linux.


Thanks for your suggestion...but think the toolchain with GCC 10.5.0 is compilable if i found a way to pass the path of my system to the script that build (option 21 on rebuild).
The other only changes are (but don't know where to modify...) is to add the build of libaeabi and disable the building of some tests under cplusplus that use exceptions and is not supported under ARM. try to crosscompile with my Linux amd64 PC.

For paths look into core-linux-armhf/bin/linux-armhf/gen/config/target.cfg. A number of build-wide variable is set there containing paths to local build system. These variables and the target.cfg file are generated by AROS ./configure script.

Thanks compilation now go forward...changed target.cfg under &quot;toolchain-core-armhf-build/bin/linux-arm/gen/config&quot; and do make on &quot;toolchain-core-armhf-build&quot; dir.

Need to find where to enable build libaeabi.a so can build the entire toolchain with option 21 of rebuild.sh


Found something that looks like libeabi in AROS/arm-all/arm-aeabi/mmakefile.src. Try adding a third line there:

#MM- linklibs-armhd : libklibs-aeabi-arm

Don't remember needing this library. Possibly the 6.5.0 GCC somehow does this while 10.5.0 is missing this.

Try adding this line (and the variant &quot;linklibs-armhf&quot; instead of hd) but it did not solve the automatic building of the missing lib. I must do &quot;linklibs-aeabi-arm-quick&quot;.
Anyway after have build the aeabi lib i succefully built the toolchain (after many hours...). Smile

To test I restarted from selecting option 21 (on rebuild.sh) but after many hours i get the same error of the kernel includes not found...maybe i need to modify the configure script for my case.

With the toolchain built i try to build the core-linux-armhf (DEBUG) (option 22) but after a while it stopped with
&quot;cannot find -laeabi &quot; so i made it built manually...and now i can continue compiling...i'll let you know if all goes ok.


== Hardware ==

===64bit===


====BCM2712====

With the Pi5 

Broadcom VideoCore 7 vc7 is an integrated GPU with 12 cores and up to 800 MHz clock. VideoCore VII is capable of OpenGL ES 3.1 and Vulkan 1.2. The driver support for the Raspberry Pi continues to build upon the [https://lore.kernel.org/dri-devel/20230928114532.167854-1-itoral@igalia.com/ open-source V3D driver] stack within [https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450 Mesa] hopefully be merged for Mesa 23.3. x265 HEVC accelerated untested, x264/h.264 and VP9 cpu only. 

*Raspberry Pi M.2 HAT+ Expansion Board 
*Geekworm X1001 PCIe to M.2 Key-M NVMe
*Geekworm X1003 PCIe to M.2 HAT NVMe SSD PIP Board for Raspberry Pi 5 
*Pineboards Pi Hut HatDrive! M.2 HAT 2024/V4 
*Hat+ Gen2 Gen3 Nvme
*GeeekPi 52Pi N04 for Raspberry Pi 5 NVME M.2
*


*2024 RPI AI HAT    - Hailo  20TOPs  no LLMs 
*2026 RPI AI HAT+ 2 - Hailo  40TOPs  slightly better? 


[https://www.raspberrypi.com/documentation/accessories/camera.html Cameras for Pi]
*Raspberry Pi camera module, the V3 with Sony IMX708 back-illuminated CMOS 12 Megapixel sensor
*Raspberry Pi Camera Module V2 – 8MP Sony IMX219 Sensor
*Raspberry Pi camera Rev 1.3, 5MP 1080P OV5647 image/video module, 2592 x 1944 pixels


====BCM2711====

With the Pi4 an ARM a72 cpu is about x3 times the size of an a53 in the Pi3 

the 2711b line used more power when idle, compared to the 2711c 

*2018 Raspberry Pi PoE HAT Power Over Ethernet Hat - design issues 
*2020 Raspberry Pi PoE+ HAT Power Over Ethernet Hat Pi3b+ Pi4 only - better design 
*Waveshare PoE HAT (B) with cooling fan for Raspberry Pi 3B+/4B 802.3af PoE 

*[https://github.com/axizo-pi/V3DLib vc6 V3D 4.2] is derived from [https://docs.broadcom.com/doc/12358545 vc4], but it is [https://docs.mesa3d.org/drivers/v3d.html significantly different] 
The QPU pipeline stays mostly the same, you still have an add ALU and a multiply ALU and it can issue two ALU OPs per cycle. There is still 4 SIMD lanes, interleaved over 4 cycles.
The instruction encoding for the QPUs is different, but the core instructions are the same.

Instructions for packed 8 bit int math has been dropped, along with most of the pack modes.
Instructions for packed 16bit float math has been added (2 floats at in a single operation)
With vc5/vc6, you write two packed 16f value to the tilebuffer (or four writes of 32f, if you are using the rgba32f framebuffer). And there is a handy vfpack operation which allows you to pack two f32s into a single 32bit value in a single instruction. You can vfpack directly into the tile buffer register.

the multiply ALU can now fadd, so you can issue two fadds per instruction. the add ALU has gained a bunch of new instructions 

the A and B register files have been merged. You still only get an A read and a B read per instruction, but they read from one big register file (which means the underlying memory block has gone from two sets of &quot;one read port, one write port&quot; to one &quot;two read ports, one write port&quot; block)

The theoretical max FLOPs per QPU remains the same at two per cycle, other than the bump from 400mhz to 500mhx but it looks like a lot of effort has been put putting those theoretical FLOPs to better use. 
*vc4 could run one or two threads per QPU. When you ran in two thread mode, the available register file halfed to 32 registers.
*vc5 added a four thread per QPU mode, with 16 registers per thread.
*vc6 doubled the size of the register file. You could now use all 64 threads in two thread mode and 32 registers in for thread mode. Single thread mode was removed, you always have at least two threads.

With the threading improvements, the QPUs should spent much less time idle waiting NOPs for memory requests. Most of the design changes have gone to improving the fixed function hardware around the QPUs. A fixed function blend unit has been added, which should reduce load on the QPUs when doing alpha blending. hope software blending is still possible 

The tile buffer can now store upto 4 render targets (up to 128bits per pixel, so if you are using 4 32bit render targets, you can't have a depth buffer)

A MMU, allowing a much simpler/faster kernel driver.

Many more texture formats, framebuffer formats.

h264/x264 as Pi3 

All the features needed for opengl es 3.0 

H.265 / HEVC decoder is a HEVCv2 Main 4:4:4 10 design supporting bitstreams up to profile 5.1
HEVC hardware decode supports 4kp60, 10-bit. Audio output is pretty much unchanged, but the HDMI audio channels now support 8x192kHz bitrates 

Each ALU typically have 2 floating point operators, and as you pointed out in a earlier post videocore 6 is no exception, with both a multiply and additive floating point operator. Thus theoretical GFLOPs are calculated with both operators in mind. That is what the 2 in my formula represents, and is common across any modern programmable shader, whether you calculate Nvidia, AMD, Intel, Boardcom or any other company's GPUs. Total ALUs * 2 * GHz clock = GFLOPs, In the case of Raspberry Pi 3, it's 24 ALUs * 2 operators * 0.4GHz = 19.2GFLOPs
If the Videocore 6 does indeed only have 16 ALUs (16 * 2 * 0.5GHz), you'd have only 16GFLOPs but they are better utilised 

Possible maximum performance 
&lt;pre&gt;
VideoCore IV @ 250MHz: 250 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 24 Gflop/s
VideoCore IV @ 300MHz: 300 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 28.8 Gflop/s
VideoCore VI @ 500MHz: 500 [MHz] x 2 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 32 Gflop/s
&lt;/pre&gt;

Faster LPDDR4 memory.


====BCM2837==== 

With the Pi3 
* Broadcom BCM43438 chip provides 2.4&amp;nbsp;GHz 802.11n wireless LAN, Bluetooth Low Energy, and Bluetooth 4.1 Classic radio support, 3B+ [https://github.com/aros-development-team/AROS/commit/afa5bc0bb17d5dd06bcfdbac00853a3799ca8d76 LAN7515] 

The overclock ability has diminished with each chip version as the energy usage has increased. BCM2837 is one of the warmest yet and benefits from active fan cooling if all four cpu cores are in use for a short while. Video playback maybe affected due to the lack of custom support in the GPU with Aros. 5 V / 2.4 or 2.5 amp power supply recommended if all four cpu cores are running, else throttling (cpu slowdown) might occur. 

[https://github.com/hermanhermitage/videocoreiv/wiki/VideoCore-IV-Programmers-Manual Dual VDP] and scalable QPU in [https://docs.mesa3d.org/drivers/vc4.html VC4] and x.264/h.264 accelerated untested only and VP9 on cpu or neon help 


ARMv8-A has [https://developer.arm.com/documentation/102412/0100/Privilege-and-Exception-levels privilege levels] where userspace typically runs at ‘EL0’, the kernel at ‘EL1’ or ‘EL2’ and the firmware at the highest level ‘EL3’. 


===32bit===

=== Core Kernel ===


====BCM2708(family)====
which includes the [http://elinux.org/RPi_Hardware BCM2835] (ARM1176JZF-S 700&amp;nbsp;MHz CPU + VideoCore IV GPU + up to 1GB RAM)

*Framebuffer (fb) using mailbox 
*IRQ scheduler, etc 
*Arasan based SD Card controller 
*Synopsis DesignWare USB 2.0 OTG controller [http://networkdirection.net/index.php?option=com_content&amp;view=article&amp;id=106:rasperry-pi-usb-controller&amp;catid=45:raspberry-pi&amp;Itemid=54 Unofficial DOCS pdf],  [dwc_otg.c FreeBSD], [], [https://www.riscosopen.org/viewer/view/mixed/RiscOS/Sources/HWSupport/USB/Controllers/DWCDriver/ RiscOS USB Driver], [https://www.riscosopen.org/forum/forums/5/topics/878 RiscOS USB Discussion], [https://www.riscosopen.org/forum/forums/11/topics/1893 Other USB RiscOS], [http://plan9.bell-labs.com/plan9/index.html Plan9 Miller's usb] http://plan9.bell-labs.com/sources/contrib/miller/, [https://github.com/Chadderz121/csud CSUD driver], 
*[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf SMSC 9512] USB LAN/Hub chip 
*CMOS RAM 
*VCHIQ port which sends messages to the GPU e.g. for mouse, keyboard, audio on HDMI, etc 
*Audio Driver 
*Serial Peripheral Interface Bus (SPI) 
*[http://www.susa.net/wordpress/2012/06/raspberry-pi-pcf8563-real-time-clock-rtc/ I2C registers]
*I2S 
*Universal Asynchronous Receiver Transmitter (UART) 
*[http://elinux.org/RPi_BCM2835_GPIOs GPIOs] and [http://www.adafruit.com/blog/2012/08/17/broadcom-bcm2835-peripheral-memory-map-and-gpio-alternate-use-chart-piday-raspberrypi-raspberry_pi/ Alternative view of GPIO]

BCM2836 
* For Pi B+, PI 2 and Pi 3 SMSC LAN9514 chip adding 10/100 Ethernet connectivity and four USB channels to the board

*[http://www.andrewscheller.co.uk/rpi_pcb_modules.html PCB], [http://elinux.org/RPi_Low-level_peripherals Low level features],


 Implemented so far... 

# Modify the configure system so that it correctly builds for the arm hardware float raspi target.
# Implemented the bootstrap to load the aros modules and prepare the arm to jump into them. Reworked the x86 console support so that parts can be stolen for raspi to use since t has no basic functionality to output to the display.
# Implemented a kernel.resource to prepare the raspi for running aros and provide the low level api calls to expose available resources and allow exec, etc function.
# Implemented serial debug support
# Implemented the exec (and kernel) functionality required to make multitasking work (and interrupts, exceptions, syscalls, etc)
# Implemented a timer.device to utilise the hardware timers.
# Implemented a very basic gfx driver to expose the hardware's framebuffer.
# Implemented an SD-Card driver for AROS which presently only supports the raspi's chipset but can easily be modified to support all sd-card hardware and media.
# Fixed the fat filesystem support in AROS so that it can boot on RasPi's normal SD-Card setup. The &quot;rom&quot; image files needed use a different filename than the default linux, etc images so can be easily installed without harming the existing files - you only need to change the loaded images in the config file to get aros to boot.
# Updated the build scripts to automatically download the necessary raspi firmware files and wrap it all up so that you can simply extract the archive to a fat formatted sdcard and boot it on the raspi without having to get anything else.
# fix everything in contrib and ports to build for raspi (needs proper testing/fixes but allows every component to actually compile at least, including owb) + numerous other fixes to get things working on arm/raspi ..


Improvements...

# Implement a USB chipset driver &quot;OR&quot; finish the existing one [https://github.com/aros-development-team/AROS/commit/c07d13c724f944674be5db54fc6a71ee72a01809 usb otg] - the current code is mostly a skeleton that should initialise the chipset and then needs relevant code to support the different transfer types. It also has the &quot;virtual&quot; hub code in place to represent the raspi's USB port (from poseidons p.o.v) 
# Implement a driver for the USB NIC (a few weeks - depends on USB above) 
# Write an [https://github.com/aros-development-team/AROS/commit/d55d0f74d20b769bbb8c8d386e5c1d7a9154f05a audio driver] (a few weeks - independent of USB) and [https://github.com/aros-development-team/AROS/commit/e93a4c245f27a87c9c4c1d39206694b39059998a HDMI]
# fix syscall bug in the current raspi kernel code
# Graphics depend on having a decent &quot;bcmdma.resource&quot; implemented as to use the cpu's dma engine. The sd card driver needs to use it for transfers to/from the controller - and the gfx system needs to use it for &quot;blitting&quot;. 
# [https://github.com/aros-development-team/AROS/commit/4019d84e4975d4dad987a12d57fe108f5ac048e6 Improve the gfx driver], [ vc4gfx HIDD] add [http://dri.freedesktop.org/wiki/VC4/ Gallium3D support] 
# [https://github.com/aros-development-team/AROS/commit/b13905b3e8e45b089f520b44692c81affddd066f Improve] the [https://github.com/aros-development-team/AROS/commit/3a876755c070f5c73c4f53c7f4d35b4f923088b9 sdcard] device driver  - which is also pretty basic but should work with most cards, rework it to also support pci, etc. sd card interfaces on x86 
# The current code using very rudimentary access to the gpio interface - so that should be implemented as some resource for other components to access, as-well as the i2c interface exposed over the gpio interface. that should have a hidd class implemented which uses the gpio resource to communicate.


 Boot up typical for most other OSs before the open sourcing of many binary blobs from 2017 onwards 

On power-up, the rpi [http://www.open.com.au/mikem/bcm2835/ BCM 2835] [https://github.com/hermanhermitage/videocoreiv VideoCore4] GPU, not the ARM CPU, is in control, and the SD card slot is the only peripheral device with power. The firmware burned into the BCM2835's VideoCoreIV GPU PROM requires a DOS-style partition table; a FAT-formatted first partition; and the freely redistributable but closed sourced Broadcom files “bootcode.bin” and “start.elf” in that partition.

The boot sequence carries out several pre-boot tasks

*On powering of the rpi, the GPU reads and executes bootcode.bin, which then loads start.elf 
*The GPU loads the “start.elf” file, eventually, into the L2 cache and then executes it
*configures the memory split for the CPU and GPU
*reads and parses “config.txt” from the same partition on the SD card and applies the settings (like a PC’s BIOS settings)
*loads the “kernel.img” file, again from the same partition
*activates the CPU to begin executing the loaded kernel image

The CPU/GPU memory split is hard-coded into start.elf, so Broadcom provides three start.elf images, to give 32M, 64M, or 128M to the GPU for multimedia performance, and the remainder to the CPU.

RPi uses [https://github.com/raspberrypi/firmware some closed source loaders] and at some point it loads a binary blob named &quot;kernel.img&quot; at 0x8000, at that point there would be a rudimentary Aros alive. If one wants to use the SD-card then there would have to be a driver for the interface and a fat filesystem handler (SD-card has to be formatted to fat filesystem)

Boot code and kernel are now linked together and made into that binary blob, just for starters. Raspberry Pi uses [http://kernelnomicon.org/?p=133 u-boot] and [http://kernelnomicon.org/?p=138 UBoot] as bootloader, there's already some code in the Efika MX port for that. UBoot is a native bootloader and not just for the raspberry pi, it loads after start.elf.

You can find Efika MX port from arch implementations, some hacking is needed for the mmakefile.src'es as iit dates back to before the Aros crosstool era or else you get some weird errors while building. You also need to code the bootstrap and serial handling.

At the moment it seems that a fastest route for the native build would be to make one binary blob without using the package system. Raspberry's memory layout is pretty simple and if the implemented u-boot doesn't support loading other modules 

&lt;pre&gt;
?          - alias for 'help'
mtest      - simple RAM test
autoscr    - run script from memory
base       - print or set address offset
bbm        - BBM sub-system
bdinfo     - print Board Info structure
boot       - boot default, i.e., run 'bootcmd'
bootd      - boot default, i.e., run 'bootcmd'
bootm      - boot application image from memory
bootp      - boot image via network using BootP/TFTP protocol
cmp        - memory compare
coninfo    - print console devices and information
cp         - memory copy
crc32      - checksum calculation
echo       - echo args to console
fatinfo    - print information about filesystem
fatload    - load binary file from a dos filesystem
fatls      - list files in a directory (default /)
go         - start application at address 'addr'
help       - print online help
iminfo     - print header information for application image
itest      - return true/false on integer compare
jade       -
loadb      - load binary file over serial line (kermit mode)
loads      - load S-Record file over serial line
loady      - load binary file over serial line (ymodem mode)
loop       - infinite loop on address range
md         - memory display
mm         - memory modify (auto-incrementing)
mtest      - simple RAM test
mw         - memory write (fill)
nfs        - boot image via network using NFS protocol
nm         - memory modify (constant address)
pci        - list and access PCI Configuration Space
ping       - send ICMP ECHO_REQUEST to network host
printenv   - print environment variables
rarpboot   - boot image via network using RARP/TFTP protocol
reset      - Perform RESET of the CPU
run        - run commands in an environment variable
saveenv    - save environment variables to persistent storage
saves      - save S-Record file over serial line
setenv     - set environment variables
sleep      - delay execution for some time
tftpboot   - boot image via network using TFTP protocol
USB        - USB sub-system
usbboot    - boot from USB device
version    - print monitor version
&lt;/pre&gt;


And there is one more thing about modular ports. In order to actually implement this, your bootstrapping environment should provide the ability to load several files. On PC this is provided by GRUB2. on CHRP you can read filesystem via OpenFirmware, and Sam's Parthenope relies on modified u-boot. If your bootstrap allows to load only a single file, then you stuck with monolithic kickstart. By the way...  u-boot allows not only to boot up a single uImage or zImage, it also allows to write client programs AFAIK. With this approach, you actually can write modular bootstrap for ARM AROS using unmodified u-boot.

Most used [http://www.compulab.co.il/workspace/mediawiki/index.php5/U-Boot_quick_reference uboot options] are fatls usb 0:1,

the reason behind INTB_KERNEL is to allow use of the standard Exec function AddIntServer() to add interrupt handlers for
hardware drivers etc. AmigaOS never used it for abstract hardware drivers. AmigaOS  routed  only  raw  hardware IRQs there. Their assignment was hardcoded. As well as number of them. Actually on AmigaOS every bus has its own interrupt subsystem. For example PCI bus. PCI interrupts on Amiga are routed to a single exec interrupt.  1:1 relationship between CPU  and hardware interrupts is present only on PC.

IMHO we miss things like AddInterrupt/RemInterrupt methods on our PCI subsystem's device class.  PCI bus class should map these methods to whatever is appropriate. This is how it is done on AmigaOS and friends. When these are implemented, raw kernel.resource API will be needed only for several PC-specific drivers with hardwired resources. Exec IRQs are real IRQs only on Amiga hardware. On other machines they can be emulated where appropriate (VBlank is a good example). kernel.resource is meant  to be different, its IRQs are hardware-agnostic, they are plain &quot;Hardware IRQ number X, whatever this means&quot;. They are low-level actually, and meaningful only in the context of a particular system.

Was that not the transition from irq.hidd to kernel.resource? No.  A long time ago there was another hacky bit named INTB_TIMERTICK. It was &quot;abstract timer interrupt&quot;, used by timer.device. It was the same as VBlank, but with larger frequency. I removed it, because kernel.resource API was a cleaner way to access this interrupt. Furthermore, there can be more than one timer in the system. Thinking about bringing back timer HIDD definitions again. hpet.resource is a bad idea.

Can someone please enlighten me a little on how the scheduler is meant to work?
 
Poseidon.library creates its &quot;Poseidon Event Task&quot; during RTF_COLDSTART -&gt; then calls Wait(), and ends up in limbo because wait disables interrupts (used for the scheduler heartbeat), and basically waits forever because the sigbit is never set, since krnSwitch doesn't switch the task unless TF_SWITCH is set, and no codepath run during this seems to set it?? TF_SWITCH does not disable/enable switching. This flag just enables to run user-supplied hook when the task is being switched away. It is completely safe to call Wait() in Disable()d state. Doing this actually temporarily breaks this state. IDNestCnt gets remembered in struct Task, then next task is selected, and its IDNestCnt is restored in sysbase (see kernel_scheduler.c). If there are no other tasks, then your cpu_Dispatch() should enable interrupts on the CPU and enter idle mode. See x86 implementation for good example.

You miss what happens next...
 1. KrnSwitch() saves context of your task, saves IDNestCnt (core_Switch() and cpu_Switch()), then drops into cpu_Dispatch().
 2. cpu_Dispatch() calls core_Dispatch. Then two cases are possible:
 2a. There is a READY task. It is picked up, its IDNestCnt is restored in SysBase, then cpu_Dispatch() needs to restore registers and exit. The next task is run.
 2b. There are no READY tasks. core_Dispatch() returns NULL. In this case your cpu_Dispatch() should enter idle loop. It should just enable interrupts on the CPU and put it on halt. This allows it to process hardware interrupts. Eventually some of your interrupt handlers wakes up your task and puts it into READY list.

My heartbeat interrupt has been slowed atm to help debugging - but it never actually gets a chance to fire because of the Wait() disabling interrupts. Perhaps you have forgotten to enable interrupts in your idle loop.

There is a change in the format of AROS executables. Until now we were using Elf RELocable files which are usually used as intermediate object files. We had them for various reasons, one of them was how AROS files were built in the past. That days we had no real aros cross compiler and the option to embed relocation data in unix executables (or in executable files in general) was rather new and not every linux/unix system had it. Therefore we have decided to use intermediate files. Although it was somehow working (and it is still working :-)), it has some drawbacks. Therefore decided to introduce real Elf EXEC types, in first turn implemented on ARM target with option to expand in future to all other AROS architectures.

The first patch was pretty easy and appeared to work somehow. It generated nice executables with embedded relocation info. Not only that, it also removed all global symbols adjusting relocation data to be relative to the beginning of the sections. That move reduced number of symbols in each executable significantly (depending on the file between 20 and 80% of all symbols could be removed). The only symbols that stayed in the file are local ones - due to the nature of the patch wasn't able to remove them since we have not seen them in the symbol hash table.

The patch didn't worked though. The files were relocated, AROS kernel loaded, but it crashed very early. What happened? Well, the nature of ARM relocations happened :)

Most of the relocation data on all machines is rather simple. Relocation can be absolute or pc-relative, sometimes the offset has to be bit shifted. On ARM v7 there is another one. There, when one wants to load an address of function/variable into register a combination of two instructions can be used: movw and movt. The first one loads immediate into lower 16 bits of a register while clearing upper 16 bits. The second one loads immediate into upper 16 bits without touching lower halfword. Loading of a pointer into a register looks like this:

        movw r0, #:lower16:label

        movt   r0, #:upper16:label

In this case there are two relocations - one for lower halfword and another for upper. If an overflow of lower 16 bits occurs during relocation process, the upper one should be updated as well. Unfortunately with current patch and with typical ARM executables there is not enough information to perform the calculations.

There are two options - the first one would be to give up and go back to &quot;fake&quot; executables, another one would be to change from REL to RELA relocation info. The latter contains an addend, extra data which can be used to perform all the relocation calculations I need.

Decided for the second option. The patch is already in the works. There is another function for the binutils' bfd backend to perform the final relocation. There can decide what to do with every reloc info, modify data and eventually strip some symbols. An advantage is - at this stage of the linking process have also full access to all local symbols so can change all relocations section relative and eventually strip all symbols from the files. 


 GPU 

VCore developed by Alphamosaic Ltd and now owned by Broadcom. Most of start.elf runs on the GPU.   Placing ALL the userland GPU code in the videocore.hidd isn't going to be a terribly big problem because the code they published is nothing more than a shim that sends data straight to the GPU to execute.

The good news about this is that we only need to write our HIDD using the OpenVG API.   The shim is relatively small codewise and lives in the ARM memory (the actual OpenVG code itself lives in the GPU RAM area and its loaded from start.elf).   That's also the bad news.  Our driver has to translate AROS video calls to OpenVG calls, for most tasks it should be easy, for some, not so much.  It's still probably less difficult and less work, than controlling the GPU directly.

The other good news is that anything done through OpenVG happens on the GPU, its truly accelerated.   It also has some nice font functions, meaning we can lead into an accelerated text mode later.

Basically, AROS resets or locks up when it tries to use AROS_ATOMIC_INC or DEC.  If I comment out the byte/word operations in the header files and use non-atomic operations, the code works as expected.
 
have read that the L1 cache needs to be enabled to use LDREX and co (which I also read is only meant to be used on multi processor systems with shared memory) - however I am certain this is correctly enabled.

If you are using LREX or STREX, you should have L1 cache enabled, at least on the ARM CPU I work with at work.

L1 cache is enabled by enabling the MMU *AND* setting the C and I bits in the CPU - the C bit is ignored, and the I bit only covers the 16 byte instruction pipeline if the MMU is not enabled.

Can you verify that your assembly is generating LDREX/STREX? From the behavior, it almost sounds like its generating the default Semaphore locked atomics.
 Impossible. There are no semaphore-locked atomics. There are Disable()/Enable()-based ones instead. And there's a special #define AROS_NO_ATOMIC_OPERATIONS in this case, which tweaks Disable()/Enable() implementations not to recurse forever.
 I have tested this on ARMv5 which does not have ldrex/strex, it works fine. On those ARMs there's no way to have real atomics. On other OSes (like Linux) this is done by introducing things like atomic_t, which appears to be a complex structure, holding the value together with accompanying spinlock (implemented using swp).

    #warning &quot;TODO: lookup optimal mmu table settings for raspi memory&quot;
        /* Set up an identity-mapping for all 4GB */
        for(x = 0; x &lt; 4096; x ++)
        {
            pagetable[x] = x&lt;&lt;20 | (0x40002|0x80000|0x010000|0x00C00|0x04);
        }

Shouldn't there be a second loop that sets the 'C' bit in the descriptor for the RAM pages?

Currently, you have TEX=0, C=0, B=1 for all pages (Shared Device).

You should have TEX=0, C=1, B=0 for RAM (Write-Through, Cached)

    So ..
     
     pagetable[x] = x&lt;&lt;20 | 2;

     
    should be enough?

No, for RAM you need to change the '| 0x40' to '| 0x80'

tell dosboot the correct defaults to use

Please don't do this. This bootconfig.c is a deprecated legacy thing. I wanted it to go away completely with time. Instead,  display  drivers  should auto-install themselves during own initialization phase. I. e. detect hardware=&gt;instantiate itself. This   should   make  things way simpler. With this approach you only need  to add the driver into KS image to get the device autobooted. No hardcoded stuff. 
Currently  VESA  and  VGA drivers do this, look there for examples. never rewrote ATI driver because i don't have any test system for it.

they defined a smaller AROSCPUContext than the ExceptionContext - yet reference it as ExceptionContext in other places, and since it hasn't allocated enough storage for ExceptionContext, are corrupting memory/the structure (since the elements that are there don't map 1 to 1 with the exception context).

AFAIK, AROS has been moving in a different direction to this in recent years. It is the job of graphics HIDDs to allocate bitmaps etc. so that they have the most suitable characteristics, including allocating them from GPU RAM where possible. The concept of chip RAM is only for legacy code, and most if not all non-68k platforms should have all system RAM
marked as chip.

BTW, is the video processing code you mention CPU code or GPU code?

Also, IIRC we have support for &quot;external memory allocators&quot;. Perhaps that's what we need for the allocation of GPU RAM through the mailbox.

All hosted and x86 native ports should use proper context formats.

trying to clarify if the vblank handler has to have run by this point to prevent this deadlock. Actually, no. Unless you have installed VBlank handler which should wake up at some point. Without VBlank there will be no quantum count. Consequently, there will be no forced preemption. But the rest will work, and multitasking will be cooperative (switch happens only when current task voluntarily gives up the CPU). Does it depend on the vblank having run before this point? and if yes what does that mean on systems where it might be able to run enough code (e.g. get to this point) before the vblank interrupt has triggered? What is it waiting for? It could wait for timer, in this case you need timer.device working. VBlank is currently needed for exec's quantum counter. In current native ports we have only a single timer, which is served by timer.device. VBlank is simulated by timer.device also. If your machine has two timers, then you can use one of them for VBlank, and another for timer.device, this will simplify things down. VBlank needs to be 50 Hz for historical reasons, many programs use it as cheap timer. I am periodically thinking about making some abstract mechanism to be able to change quantum source (and untie it from 50 Hz), but have no time to come up with something good. Additionally i started disliking timer.device hardcoded design when PC has got many timers (old 8253, APIC, HPET).
Currently i think there should be some low-level entity representing tick source. timer.device should just select the most appropriate source for its units.
The BCM2835 has 4 GPU based timer sources - 2 are used by the GPU, so im using Timer3 for our heartbeat and the remaining one will be free to the system. There is also the less capable ARM timer but that is dependent on the CPU frequency. Very good. You won't need any emulation. Set the heartbeat to 50 Hz and drive VBlank from it. Use other timer for MicroHZ.

Can you use the 'econsole.hook' I make for debugging the Sam460 via the serial port?
It provides a before-anything-else shell prompt on the serial port.  You can then do 'NewCLI' to test your graphics, or use any DOS command in shellcommands.resource.

You should just be able to add econsole.hook to your module list, and use 'econsole' in your bootargs.

So long as you have a working Exec/RawMayGetChar and Exec/RawPutChar, it should work.

Also make sure to add shell.resource and shellcommands.resource for this.

That should have done it.

If you set &quot;#define DEBUG 1&quot; in  arch/all-native/econsole/econsole.c, do you get any additional serial output?

have added it to the build and added econsole to the command line - and can see the bootloader picks up on the emergency bootconsole tag, but I still only get the insert bootable media display?

Im assuming it exposes a fake filesystem that tricks aros into booting?
The contents of which are: ECON:AROS.boot

Way to handle the scheduling code? The implementations I had been following were causing problems, due to cascading interrupts which I cant handle properly in the asm stubs just now (when they break disable etc.) - since it means detecting the interrupted codes cpu mode and getting the correct sp/lr for it, and that's just too tedious for arm.
 
To work around this ive added a system idle task which does nothing - and when the scheduling code has no task to run switches this in and lets it run, thereby allowing the interrupts etc to resume until something does need to happen.
 
Also, by adding accounting code to cpu_Switch() and cpu_Dispatch(), it should allow the system to log idle time correctly (as well as running tasks).
 
have thought of also adding an additional task that never runs, solely to record time spent in IRQ handlers, but I digress..

was under the impression that kernel.resource should *never* be used outside of exec.library. This is a wrong impression.
Michal started designing it because portable nature of AROS does not fit well into exec's API with all its assumptions. So, he started the new, hardware-agnostic kernel API from scratch. Yes, exec sits on top of it in places. But kernel always meant to be open thing. Otherwise it would not exist. 
it wasn't meant to be just used willy nilly by user code - but by lower system components (e.g. exec) so that they could be implemented in a more generic fashion, and the kernel resource itself hide the systems quirks.

Adding new things there perfectly keeps up with our decision to minimize AROS-specific intervention into APIs which can clash with MorphOS or Amiga OS4 extensions. We want at least source-level compatibility there. Binary compatibility on PPC would be extremely cool, but at the other hand we have no maintainer for this, as well as their ABIs splintering. 
It depends on what exactly is being implemented - there's no reason we should have everything crammed into kernel.resource if it doesn't need to be (i.e. if its better suited as a separate component/subsystem in its own right)

The _LE versions are for when you have endian swapping taking place.  If the graphics are the same endian as the CPU, no swapping should occur.  I ran into a similar terminology problem in SDL with a friend insisting that his Radeon 7000 on his PC was big-endian.  It is not, it just uses the same endianness for the graphics card and the CPU so no swapping was necessary.  They were both little-endian.
The _LE versions are because the PixFmts refer to the bitmap data being in big endian format in memory, for which the normal version would need to do endianness conversion before applying the shifts/masks. on this platform it is in _LE in memory also so we don't need the conversion hence using the _LE version of the call). would use _LE (if it's really little endian 16 bit mode).

 
What is the bare minimum needed to implement a framebuffer based gfx driver, with our software handling the rest?

Have tried with just a gfx class that only expose new/dispose/newbitmap - and having an onscreenbitmap used only for the framebuffer itself (with all other bitmaps being chunkybm, and the framebuffer's superclass also being chunkybm), but that alone isn't enough it seems?
You can use workbench/hidds/sm502/ as your example - it is as simple as I could make it.
So, AROS creates the framebuffer bitmap (verified this) -&gt; so surely it should be capable of then rendeing into it? I don't actually create the framebuffer &quot;bitmap object&quot; myself - only as a result of being asked to. The code I currently have on SVN seems to create the framebuffers bitmap object fine, but then crashes in intuitions DisplayDriver callback.  In particular it crashes performing the getattr on the system default pointer. don't expose MEMF_CHIP in an allocatable form so AllocSpriteData was failing (and other code later doesn't check if the values are valid == illegal memory accesses) 

So far have -:

vc_init: queries the gpus memory, and sets up a fake memory handler for it, then adds the bootmode driver and returns saying all is well
vc_gfxhidd:New: sets up some fake syncmodes to test with and creates the real gfx object.
vc_gfxhidd:NewBitmap: checks if its a framebuffer and uses the onbitmap class or uses the chunkybm class otherwise
vc_onbitmap:New; creates a chunkybm object and then pushes the real framebuffer address into it as the buffer,

vc4 had v8adds, v8subs, v8muld, v8min and v8max which operated on four 8bit uint values packed into a 32bit register. Multiplication was in the range 0.0 to 1.0 and addition/subtraction saturated. There were also a range unpacking/packing modes that allowed you to pack and unpack 8bit values into 32bit registers. 

RasPi has to speak to the &quot;operating system&quot; which runs on the GPU itself and request/free memory - it cant directly manage it itself, and so the managed functions were used to wrap these calls.

The Arm and GPU share memory space. The framebuffer is shared. The Arm can write a pixel and it will appear on the screen (through GPU hardware) without flushing/copying being required.

The GPU can composite multiple FB's in real time - so you have a number of surfaces defined which are rotated etc and  composited in real time to the output. Copying can map from the address space of the Arm to the flat space of the GPU which takes some code, but I don't think whole buffers are copied.

The DMA hardware can also access the whole memory space and can perform 2D fills and blits (no blending). This is documented in the peripheral spec posted. The DMA is just an Arm accessible peripheral and can be set up with low latency (e.g. microseconds).
must use a 0xc0000000-based bus address to access SDRAM, yet non-DMA access should go via a 0x0-based bus address. 
For 2D dma, set TDMODE, and the spec says &quot;interpret the TXFR_LEN register as YLENGTH number of transfers each of XLENGTH, and add the strides to the address after each transfer.&quot; so set STRIDE to pitch of the image, the width is XLENGTH and height is YLENGTH. You would fill by not setting the SRC_INC and point source to your fill data.

The DMA cannot see the ARM's L1 cache, so you would map the framebuffer with ioremap_nocache. Depending on where the source data comes from, it may need an L1 cache flush. The DMA can see the L2 cache. Use 0xC0000000 bus addresses when L2 is disabled and 0x40000000 bus addresses when L2 is enabled. (actually just call virt_to_bus and you'll get the right address out).

openGLES/openVG has high latency. Writing to framebuffer then reading it back is very inefficient (e.g. milliseconds). If you can drive it a unidirectional way, just streaming commands at then that is efficient. openVG is not implemented on top of openGLES - it uses the same hardware but as a first class interface

To improve the Gfx driver, we will need a DMA resource implemented so can use to perform DMA operations. The Gfx driver will need this to perform blits.


Actually MEMF_CHIP has to present, for historical reasons.
This has been never fully agreed upon, but in ports i wrote i exposed the whole memory as MEMF_CHIP. The idea behind this is that CHIP is originally the memory where graphics and sound data can be put. On non-Amiga platforms there are no restrictions on this, so the whole memory is CHIP.
Yes, many old software can misbehave with CHIP memory size larger than 2MB. But this actually applies only to m68k AROS which is going to run m68k binaries. In other cases it's quite logical to fix the program when porting.

As to original question: yes, it's enough to have a framebuffer bitmap (one with aoHidd_BitMap_FrameBuffer set to TRUE) and PutPixel routine. It framebuffer can be served by chunky bitmap class, then you can simply create chunky bitmap with your own buffer (see how VESA driver does this). Chunky PutPixel is already there.

struggling to determine what is the correct pixfmt to use for the 24/16/15 bit gfx modes on the RasPi.  AFAIK it uses RGB565, for 16bit but im unsure what shifts etc should go with it? suffice to say Im getting the wrong colors so far lol.

&lt;pre&gt;
redmask: 0x0000F800
greenmask: 0x000007E0
bluemask: 0x0000001F
alphamask: 0

redshift: 16
greenshift: 21
blueshift: 27
alphashift: 0
&lt;/pre&gt;

It should likely be vHidd_StdPixFmt_RGB16_LE

This stuff is a bit confusing.  The &quot;names&quot; of the stdpixfmts are based on the layout in memory,
ignoring endianess. So for example:

ARGB32: will be 0xAA 0xRR 0xGG 0xBB in memory on both big endian and little endian machines.

The shifts and masks OTOH are based on pixel access (ULONG in this case), so differ depending
on whether you run on big endian machine or little endian machine (that's why there's stdpixfmt_le.h and
stdpixfmt_be.h in rom/hidds/graphics/).

With the 16 bit pixel format it's even more confusing, as for example it's impossible on little endian machine
to describe RGB16 with shifts/masks alone. That's why there's vHidd_PixFmt_SwapPixelBytes_Flag.
(RGB16 == RRRRRGGG GGGBBBBB in memory, and for pixel (WORD) access on little endian machine it needs to
be accessed as GGGBBBBBRRRRRGGGG).

The shifts btw indicate how much to shift the component to the left (!) so that it is moved to the highest bit (31).

The aHidd_PixFmt_StdPixFmt you specify will be ignored most of the time, because when the pixelfmt is registered,
the gfx hidd checks if there's an identical pixfmt (shifts/masks/etc., but ignoring pixfmt-&gt;stdpixfmt) already in the system,
and if so, it uses the already existing one and does not create a new one.

In theory it would be better if gfx drivers could simply/only specify a StdPixFmt without all the shifts/masks stuff when the
gfx driver uses pixfmt which matches one of the stdpixfmts exactly. Another possibility would be for gfx drivers to use
HIDD_Gfx_GetPIxFmt(stdpixfmt_gfx_driver_wants_to_use) and then peek shifts/masks from it and fill out a pixfmt
tag list based on that.
15bit very blue/green: Try to pass same shifts/masks/etc. as in 16 bit pixfmt (maybe you think it's using 15 bit R5G5B5
(or swapped) but it's actually still using 16 bit R5G6B5 (or swapped).
 aHidd_PixFmt_StdPixFmt you pass is mostly ignored. It's the shift/masks/etc. that count.
But I would still pass the correct one (_LE) == whatever rom/hidds/graphics/stdpixfmts_??.h uses
in the entry where you have looked up shifts/masks/etc.

Use the shifts/masks/etc. from the entry in stdpixfmt_le.h (if you are running on little endian machine) or stdpixfmt_be.h (if you
are running on little endian machine) that matches the pixfmt that its meant to be.

0xAA,0xRR,0xGG,0xBB on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_BGRA32)

0xAA,0xRR,0xGG,0xBB on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_BGRA32)

it feels like AROS trashes the alpha component, otherwise it should be 8A8R8G8B.

read on the subject suggest its in 1x5r5g5b (x is ignored) to keep 16bit alignment .
 
Suggests to me that wrong shift/mask are being applied - however going by the 16bit versions it all looks correct to me so I am really confused as to what is happening.

The output image looks to have too much green/blue, and very weak red.


 Kickstart 

The  idea  is  to minimize amount of archirecture-specific modules to make the user's  life  easier.  So,  the kickstart was split into 'base' (which  does  not  contain anything machine-specific) and 'BSP' (Board Support Package) which contains all hardware-specific stuff. This  way,  for  example, distribution makers can save up space on CD and  make  CDs with multiple platform support. Different configuration would load the same base with different BSP's.

Next  there  was some part which is entirely missing on hosted. These are   filesystems.  Hosted  ports  do  not need them to boot up, so on hosted   they  are  left  out.  At  the  other  hand,  they  are  also architecture-agnostic.  So  i put them into 'FS' package (standing for 'filesystem').


 USB 

Poseidon  is  one  more  big part. I made it into separate package in order to allow users to omit it if they don't need it (for example, to run  on retro PCs without USB). Personally i have one. Again, Poseidon is  hardware-agnostic (well, there are USB drivers but HCIs are pretty standard).

AFAIK its HCI 1.0 compliant but not familiar enough with poseidons drivers, nor USB, to just hack away at the existing code.  Perhaps once i'm more familiar with the workings I can merge in the changes needed to get it operating but for now I will focus on getting it running.  Also our drivers have known issues so perhaps a fresh set of eyes might shed some light on what is going wrong.

Another interesting question is whether Poseidon can operate on device side. Is it flexible enough? How similar is being a USB host and USB device? think it will need a bit of work on Poseidon's side.  Until then I will force the driver into Host/Master mode in the init code, but leave open device etc to configure the chipset for either's use - and look at trying to add support for working in Device/Slave mode &amp; switching modes once it's up and running.

Actually USBROMStartup is some kind of kludge. Can there be any alternative? Could device drivers be self-installing, like our HIDDs? This would get rid of need to list them in USBRomStartup.

* Model A and B limited to 150 mA per port. 
* Model B+ and Pi 2 introduced configurable 600 mA to 1.2 A support over all ports - anything above that requires a powered USB hub.

Implementing the hardware driver that Poseidon uses to interact with the USB components.

Have code in place to (try) and initialise the USB chipset, and configure host/device mode operation (though AFAICT Poseidon doesn't support device mode). Started to get the &quot;virtual&quot; root hub written for the single USB port so that Poseidon should at least list it correctly in the GUI - and try to interact with it to find peripherals.


The BCM2835 uses a soft IP block from Synopsys’ DesignWare library (DWC), specifically the block is called dwc_usb_2_0_hs_otg_subsystem-ahb_se (“USB 2.0 Hi-Speed OTG Controller Subsystem w/AHB Interface SE”).

There is no public documentation for this, and pretty much zero chance of anyone getting hold of it even with NDA. However, there's a Linux driver written by Synopsys ([https://github.com/raspberrypi/linux dwc_usb]). Specifically directories [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_common_port] and [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_otg].

The Synopsys code is actually under a fairly permissive licence – it's not GPL, it's similar to BSD (’don't sue us if it breaks’ is pretty much the only clause). So this should not be a barrier to porting the code.

The code is really well written, with a nice partition between the work done by the driver (dwc_otg, which is fairly involved, given the host does more work than a conventional EHCI driver), and the interface to Linux (dwc_common_port).

Probably only need provision of relevant changes to dwc_common_port. Other things to consider....

* Provision of necessary headers to get it to compile
* Provision of necessary functions (main issues are wait queues, threads, work queues, tasklets, timers, spinlocks and mutexes (multithreading) )
* Interfacing between USB stack and the driver. dwc_otg/dwc_otg_hcd_linux.c looks like the place to start.

the Linux bits of the headers are only required for the dwc_common_port library. dwc_common_port includes a variety of crypto functions which are not used – it appears to also be used for ultrawideband (UWB) and wireless USB (WUSB) drivers where crypto will be an issue, but it isn't going to be for plain wired USB.

Every USB driver acts as an USB hub as well in order to let Poseidon control the state of USB ports. The code there was reading status of the only USB port in Raspberry's CPU but when changing the status it erroneously deleted some of the status bits, including the port enable one. It was so because those bits in the status register are of a type Read/WriteToClear. It means, if one does not want to change their value from 1 back to 0, one has to actually write the 0 value. Very practical thing e.g. in interrupt handlers, where one reads the interrupt status register to learn what was the interrupt reason, and writes it back to the same register in order to clear the interrupts. 

After fixing that code it turned out that the communication was still unsuccessful. Apparently the USB device was not understanding the host for some reason. That should not happen since the request sent was one of the standard ones implemented by virtually anything with an USB connector, assumed that Poseidon clears the data caches before forwarding the work to the USB drivers but that's the responsibility of the driver itself. 

The USB device responded and acknowledged the transmission! But why were all the request sent after address change failing with timeout? They should not. Once again, address set is supported just by anything. Tried to contact the device at address 0 once again and there it was, still responding properly. The enlightenment came. The bus address for DMA transmissions was, as it is in many bare metal USB implementations, just the pure memory address of the buffer as seen by the ARM cpu. Have &quot;prefixed&quot; it with the real location of uncached RAM and booted AROS once again. 


Trident saw this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

and this:

    Product     : Vendor: Vdr=0424/PID=EC00
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 255
    SubClass  : 0
    DevProto  : 1
    VendorID  : 1060
    ProductID : 60416
    DevVers   : 0200

and even this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

What are these things? The first one is USB hub built in the Raspberry. Thanks to this one the Pi machines (with exception of Pi0 and computing modules) have more than just one single USB port. The second one is the network chip in raspberry, the third one is my USB SD card reader which have just connected to see what happens. AROS tried, of course, to boot from it ;)

So, the first step towards working USB is done. The control transfers are working as you can see above. Next step is to implement bulk and interrupt transfers, having the basics in place. Finally some error handling will be added and USB for Pi will be as complete as the PC version. 

[http://www.raspyfi.com/raspberry-pi-usb-audio-fix/ Issue with USB Audio]


 Audio 

The Pi 4B is the only Pi that can output HD Audio as an HD Audio passthrough bitstream, and it does it over HDMI. It's possible to use the two HDMI output for separate HDMI video and HDMI audio outputs to allow UHD HDR video and HD Audio with non-UHD HDR compatible AVRs. 

The Pi3B+ and earlier will decode to PCM 5.1/7.1 and output over HDMI.  HDMI is the only interconnect that has a standard for carrying Dolby True HD, DTS HD MA etc. as a bitstream - you can't carry it as a bitstream on any other interface.

Pi3 and Pi4 audio jack output derived from 12bit pulse width modulation is relatively poor. For better, choose USB Audio or I2C versions. 

[https://github.com/raspberrypi/linux/tree/rpi-patches/sound/arm audio] and its [https://github.com/raspberrypi/firmware/issues/2 very high speed message passing interface type of thing VCHI] 

The Model B+ added an additional voltage regulator for the audio output and an additional output driver to drive low-resistance loads like headphones. However it is still using pulse-width modulation (PWM), which has a major impact on sound quality

the old Raspberry Pi used a linear voltage regulator to provide the 3.3V to many of the components on the board while the new one uses a switching regulator. Both can perform reasonably well. However switch mode power supplies often show higher noise figures

Analogue audio

Audio over HDMI rev 1.3 &amp; 1.4


 Ethernet 

10/100 BaseT Ethernet RJ45 socket


 GPIO 

GPIO shouldn't be too bad but bear in mind it is already accessed in places so they would need to allocate pins etc through it (e.g. sdcard to flicker the activity light, serial debug to output data on the GPIO pins)

Probably a resource rather than a device...

Started an i2c driver that will need to allocate GPIO pins. Feel free to work on it if you are interested ;p


 GPU graphics with 2D and 3D acceleration 

Sadly none yet for 32bit but for 64bit... 


 Miscellanous

hdmi issues

Setting the hdmi_force_hotplug=1 makes sure the Pi believes the monitor/TV is really there.

You might also need to set config_hdmi_boost=4 or even higher (up to 9) if your display needs a stronger signal.

If the display is a computer monitor or newer tv, use hdmi_group=1 (auto HDMI use) and if it is an older TV, try hdmi_group=2 (for DMT formats, i.e. for PC monitors) then you HAVE to &quot;set hdmi_drive = 2 to enable HDMI output as this forces HDMI mode rather than DVI mode

Do not set hdmi_safe=1 as that overrides many of the previous options.

Using a shorter or better quality HDMI cable might help. Make sure your Pi's power supply delivers 1 A and not 500 mA.
If you see a problem with the red colour - either absent, or interference - then try a boost

composite video

changing the RCA cable, then the composite port worked out of the box

Boot it as you are doing, without HDMI. If you now plug in the HDMI, do you get the image? In other words, does the Pi think HDMI is connected even when it isn't?

Rename all the files in the first partion of the card except bootcode.bin, start.elf and fixup.dat  What's the result?

Put back config.txt What's the result?

for PAL mode   sdtv_mode=2

dmi_ignore_hotplug Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached
hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected

&lt;pre&gt;
# NOOBS Auto-generated Settings:
#hdmi_force_hotplug=1
#config_hdmi_boost=4
#overscan_left=24
#overscan_right=24
#overscan_top=16
#overscan_bottom=16
#disable_overscan=0
start_x=1
gpu_mem=128
&lt;/pre&gt;

tvservice -c &quot;PAL 4:3&quot;

&lt;pre&gt;
/opt/vc/bin/tvservice -s   or tvservice -s 
state: HPD high|HDMI mode|HDCP off|composite off (0x12001a), 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m CEA
Group CEA has 1 modes:
(native) mode 16: 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m DMT
Group DMT has 0 modes:
&lt;/pre&gt;

sudo amixer cset numid=3 1

forces the audio to the headphone jack, even with the HDMI video output plugged in

config.txt

the hdmi_ignore_edid_audio=1 option sems relevant as it should tell ALSA that the only available audio is analog, no matter what the display says

There are several different ways that these 4 pole (ring) composite analog cables can be wired up, so some work great in some applications and can be a waste of time in others.

What is needed for the Raspberry Pi B+ and above, which like many camcorders needs the ring contact next to the base contact to be the ground.


The wiring for the 4 pole are:

TIP (LEFT AUDIO CHANNEL)

RING 1 (RIGHT AUDIO CHANNEL)

RING 2 (GROUND/EARTH)

RING 3 BASE/SLEEVE (VIDEO) YELLOW

Most Apple based Players and the Microsoft Zune (TM) are wired this way.

Most analogue camcorders are wired this way as well, where the ground in on Ring 2 will work with the Pi although you may need to swap your Video plug with the Right Audio plug.

Nearly all other MP3 players are not wired this way, the ground is on another ring ie the wrong one.


External devices

* Camera Module Omnivision ov5647 Sunny 5MP (NoIR version) V1.3 - NoIR at 850&amp;nbsp;nm, peak at 880&amp;nbsp;nm and trails off at 940&amp;nbsp;nm wavelengths 
* Camera V2 Sony IMX219 V2.1 8mpixel 8MP 8megapixel - 3280 x 2464 pixels - video at 1080p30, 720p60 and 640x480p90 - wider field of view, 62 vs 54 degrees horizontally - 
* Branded WIFI usb BCM43143 dongle

N.B.  dreaded error after changing cameras (stupidly without turning off the power first) and lasted through several power cycles.  It can be a bad 15-pin FFC ribbon cable, when swapped, camera(s) and the Pi itself are working OK. It can be an instance of a cold solder joint on the CSI connector on the pi board.  the camera can be detected (that's done via I2C) but may still not be able to receive image data (done via CSI-2) if something is broken. CSI-2 is uni-directional. Control is generally done via I2C. 
The CSI-2 receiver always writes to memory, not direct to the ISP. That's the way the Broadcom architecture works as it allows multipass processing easily. GPU memory is accessible from the ARM. Processing using the QPU graphics processors may be possible.  currently the only supported sensor is OV5647 and IMX219.  The linux drivers are all in the firmware blob, else you'd  be looking at at least a man-month of work in a fully fledged imaging lab to do a decent tuning of the camera modules' ISP parameters. 
Static electricity maybe an issue for the camera module and slightly less for the pi board.


== References ==


===Good sites to visit===

*[https://github.com/raspberrypi/firmware/tree/master/ Raspberry Pi Firmware build] 
*[https://www.raspberrypi.com/documentation/computers/software-sources.html Documentation] 
*[https://rpilocator.com/ RPiLocator] 


Linux only
*[https://github.com/raspberrypi/linux Raspberry Pi Linux Build] 
*[https://dietpi.com/ DietPi] 
*[http://www.tinycorelinux.net/ports.html piCore]
*[https://wiki.alpinelinux.org/wiki/Raspberry_Pi Alpine Linux] 
*[https://github.com/armbian/build Armbian] 


*[ FydeOS]
*[ TwisterOS based on ChromiumOS] 
*[https://note.com/jamesmondo/n/nc76e31402be8?hl=en BSD] 


*[https://www.raspberrypi.com/software/operating-systems/ PiOS Lite] and then [https://hstwb.firstrealize.com/ HST] 
*[ PiMiga for pi4 and pi5] 
*[ amibian for pi2 and pi3] 
*[ retropie pi1 and 2] 


Other alternative lighter smaller than Pi OS 
*[https://aros.sourceforge.io/nightly1.html Aros 64bit ARMV8 single core] 
*[https://www.riscosopen.org/wiki/documentation/show/Welcome%20to%20RISC%20OS%20Pi RiscOS on Pi3 and Pi4]
*[https://github.com/michalsc/Emu68 ARM based realtime JIT 68k for amiga computers] 
*[https://github.com/JJDSNT/bellatrix/releases/ Alternative use of Emu68 on Pi3b] 
*[https://github.com/stevereaver/uaos uaOS with Emu68k] 
*[https://github.com/aros-development-team/AROS/commit/f80a268607dfae81b2db94755ab4e4d31ccb72d6 m68kemu library reference] 
*[ HaikuOS]
*[https://github.com/raspberrypi/noobs NOOBS] os loader with successor [https://github.com/procount/pinn PINN] 
*[https://github.com/maxnet/berryboot berryboot]

*[https://github.com/brianwiddas/pi-baremetal Bare Metal Access on Pi 32bit] 


Testing procedure is put sd card in, connect board to board if necessary, plug in hdmi and then power nothing else is done especially CSI DSI etc 

[https://www.raspberrypi.com/documentation/computers/compute-module.html CM5] has the same 55mm x 40mm 2x100pin connectors form factor as the CM4 but [https://www.epdtonthenet.net/article/214508/Key-Considerations-When-Migrating-from-Raspberry-Pi-CM4-to-CM5.aspx some pins and other small things] have changed. Will need the [https://raspipcb.com/tech-blog/raspberry-pi-cm4-vs-cm5-difference-in-booting-from-sd-card/ right IO board to suit] 

*Green [ Raspberry Pi Compute Module 5 IO Board REV2 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1967]] - untested 
*Green [ RPi Compute Module 5 IO board REV1 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1751]] - untested 
*Black SupTronics Geekbord X1500 CM5 IO Carrier Board - untested
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*[https://sipeed.com/nanocluster Sipeed NanoCluster] - untested up to 7 CM5 
*Green BentoIO CMX0 - untested 
*Box EDATec ED-CLAWBOX - untested 
*Home Assistant Yellow - Kit with PoE with Raspberry Pi Compute Module 5 - untested 
*Blue [https://www.waveshare.com/wiki/CM5_PoE_BASE_A Waveshare CM5-PoE-BASE-A] - untested 
*Box  Waveshare [ CM5-POE-BOX-A] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-B Waveshare CM5-IO-BASE-B] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-A Waveshare CM5-IO-BASE-A] - untested 
*Blue Waveshare [https://www.waveshare.com/wiki/CM5-NANO-B CM5-NANO-B] - untested 


*[https://carboncomputers.us/products/pi-flux piFlux]
*[https://carboncomputers.us/products/ Zitaotech Hackberry] CM5 lite only - 
*Portable [https://www.waveshare.com/pocketterm35.htm Waveshare PocketTerm35] with Pi4B or Pi5 - untested 
*Box [https://www.clockworkpi.com/uconsole ClockworkPi uConsole][https://www.youtube.com/watch?v=EtI_bAahbR8 CM4 into an adapter or CM3 into so-dimm - Cyberdeck] - untested 


*Green RPi [https://datasheets.raspberrypi.com/cm4io/CM4IO-KiCAD.zip Compute Module 4] [https://datasheets.raspberrypi.com/cm4io/cm4io-datasheet.pdf IO board] V1.4 [https://datasheets.raspberrypi.com/cm4io/CM4IOUSB3-KiCAD.zip USB3] [https://datasheets.raspberrypi.com/cm4io/cm4iousb3-appnote.pdf CM4ISO] [https://datasheets.raspberrypi.com/cm4/cm4-datasheet.pdf Dual100pin] (2020) aka Development Platform Board - untested 
*Purple Pi Hut Cytron CM4 Maker Board - untested 
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*[ KubeSail PiBox mini 2] 
*Home Assistant Yellow with Raspberry Pi Compute Module 4 - untested 
*[ Turing Pi V2] - untested CM4 with 260-pin SO-DIMM socket adapters and/or nvidia jetson nanos - untested 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-C Waveshare CM4-IO-BASE-C] - untested but binary blobs Rev01 Rev02 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-B Waveshare CM4-IO-BASE-B] - untested but binary blobs 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-A Waveshare CM4-IO-BASE-A] - untested but binary blobs 
*Blue [https://www.waveshare.com/wiki/CM4-NANO-B Waveshare CM4-NANO] - untested but usb and audio turned off or rerouted 
*Black [ Seeed Studio with BigTreeTech BTT pad 7] - bin blobs? 


CM3 has a 200 pin sodimm ddr2 connector form factor but not electrically SC0028, SC0029 
*Blue [https://wiki.geekworm.com/CM_IO_Board Geekworm RPi Compute Module IO Board] [https://github.com/geekworm-com/cm-io-board CSI DSI] with CM3 in ddr2 slot underside - '''works''' if SW1 on but CM3+ '''does not''' 
*Green [https://cdn-shop.adafruit.com/product-files/3442/CMIO_schematic.pdf RPi V3 IO board CM3IO] and CM3 Lite - untested 
*Green [https://turingpi.com/ turingpi v1 cluster] - untested up to 7 cm3 7xlan9514 12V discontinued, 3 x Pi4 homelab maybe better 
*Blue [https://www.waveshare.com/wiki/Compute_Module_PoE_Board Waveshare Compute Module PoE Board] and CM3 lite (if not lite, write files to internal eMMC fat32) '''AVOID''' bin blobs 
*Blue [https://www.waveshare.com/compute-module-io-board-plus.htm Waveshare Compute Module IO Board Plus] [https://www.waveshare.com/wiki/Compute_Module_IO_Board_Plus wiki] [https://forums.raspberrypi.com/viewtopic.php?t=235695 pin settings] with CM3+ Lite - '''AVOID''' binary blob 


*[ Pi02w on Geekworm SupTronics X305 Raspberry Pi Zero IO Baseboard] - untested 
*[ Spotpear Pi Zero 2w to Pi3b format-ish] - untested 


*[ pi-top v4] box has 128x64 oled display, micro hdmi, 19Whr battery with pi4 and 15V PD 36W min needed 
*[ pi-top v3] three green pieces, heatsink covers most of the base tray, pi-top hub mk1 lhs and Pi1B Pi2b Pi3b rhs secured from below, black rounded strip with pi-top above keyboard, 13.3&quot; HD 1366 x 768 display, small touchpad, 
*[ pi-top Model 2.0] pi-top on bottom bezel of 14-inch green laptop, large trackpad, keyboard slide down to reveal main system hub on slide rails moved to the right, Raspberry Pi3b screws down, hub slides in, 18V 2.5A 45W charger brick, battery 11.1V 3500mAh 38.85Wh and storage PiTopOS 
*[ Pi-Top CEED Raspberry Pi Modular Educational Desktop with RPI3] monitor 
*[https://www.indiegogo.com/en/projects/jesselozano/pi-top-a-raspberry-pi-laptop-you-build-yourself Pi-Top v1] wedge laptop with RPi2 


&lt;pre&gt;
2008 Trustees collected for Foundation
2009 Pi Foundation charity status gained 
2010 
2011 First Raspberry prototypes 
2012 First boards go on sale at CPC and RS. The Model A and B 700 MHz Arm11 - February 29th BCM 2835
2012 First million sold - more than the 10,000 original planned and anticipated 
2013 First Alpha Experimental builds of AROS Native for the 32bit Pi 
2013 Pi Trading launched making grants available, providing in house educational resources and Pi Academy for teacher training 
2013 Over two million sold 
2014 Over three million sold 
2014 Pi 1 Model B+ introduced that moved composite video to audio jack and same half gig of memory 
2014 Pi Model A+ v1.1 no ethernet and 1 usb - a little smaller - 
2015 Over four million first gen pis sold  
2015 Pi Zero 1.2 BCM2835 first production revision released with no camera port 
2016 Pi0 1.3 released with camera csi connector 
2017 Pi Zero W v1.1 1GHz Pi0W, single-core 32bit CPU BCM2835 released with Cypress CYW43438 wireless 
2020 Raspberry Pi Pico SC0919 with RP2040 32-bit 2Core ARM Cortex-M0+ up to 133 MHz - 264KB of SRAM and 2MB of on-board QSPI Flash - 
2024 Raspberry Pi Pico 2 with RP2350 2Core 32bit Arm Cortex-M33 and 2core open-hardware [https://github.com/wren6991/hazard3 Hazard3 RISC-V] 

2015 Pi 2 Model B v1.1 BCM2836 900/600 MHz ARM Cortex-A7 Armv7 quad 32bit, 32bit VideoCore IV GPU - 1Gb RAM - 5V 2A micro usb - SMSC LAN9514 chip - 
2015 Over a million pi2s sold 


2015 Raspberry Pi 2 Model B version 1.2 Pi2bv1.2, aka Pi2B2 has armv8 BCM2837 underclocked to 900Mhz without wifi/bluetooth module 
2016 Pi 3 Model B - Broadcom BCM2837 SOC four 64bit ARMv8 Cortex-A53 1.2GHz 32bit 1080p VideoCore IV GPU - 1Gb DDR2 - bluetooth 4.1, Cypress CYW43438 wireless 802.11n - 4 x USB2.0 ports - 5.1V 2.5A - SMSC LAN9514 chip 
2016 PIs total over 10 million worldwide 
2017 Compute Module 3 CM3 with BCM2837B0 armv8 Quad 64-bit - small 67.6mm x 31mm board which fits DDR2 SODIMM connector but not electrically compatible which plugs into needed IO board - beware of the I2C protocol issue 
     1Gb LPDDR2 RAM - Lite or 4Gb Emmc storage 
2017 12 million pis sold in total 
2018 Pi 3 Model B+ - 4c A53 BCM2837B0 1.4Ghz - 1Gb, wireless 802.11ac, gigabit ethernet (300Mbit/s) and bluetooth 4.2 - power over ethernet - 4 x USB2.0 ports - Microchip LAN7515 chip 
2019 Over 15 million sold 
2019 Pi 3 Model A+ with BCM2837b0 Cortex-A53 64-bit SoC @ 1.4 GHz with 512Mb LPDDR2, 1 usb2, 1 hdmi, 1 micro usb 5V 2A - no ethernet - 
2019 Raspberry Pi Compute Module 3+ CM3+ - Broadcom BCM2837B0 1.2Ghz, Cortex-A53 (ARMv8) 64-bit SoC on DDR2 SODIMM mechanically compatible only factor - IO board required 
     1Gb DDR2 and 8GB, 16GB, 32GB or a Lite variant without eMMC 
2021 Pi zero 2 (w or no W) RP3A0 quad 1GHz Cortex-A53 64bit BCM2710A1 512mB SDRam 
2025 edaTEC CM0 ED-CM0NANA with additional dev board with quad 1Ghz A53 with 512Mb Raysan RAM, 2 USB2 and 10/100 ethernet - pico castellated edge
 

2019 Pi 4 Model B v1.1 RPI4B - BCM2711B0T quad 64bit A72 1.5GHz, 4K VideoCore VI, AC wifi, Bluetooth 5.0, GbE Broadcom BCM54213PE (PHY ID 0x600d84a2), 2 micro hdmi decode up to 4K, USB-C 5.1V 3A power, 2xVLI VL805 USB 3, 2xUSB 2.0, 2GB 9LDWW D9WHZ or 4GB 9FDWW D9WHV, 8GB 0AA47 D9ZCL ddr4 ram 
2020 Silent Pi 4 v1.2 upgrade with more USB-c psu support 
2020 PI400 BCM2711C0T 1.8GHz 4Gb DDR4 inside keyboard, 5.1V 5A 27W usb-c psu, 2 micro hdmi, external ide style 40pin gpio, no audio port - 
2020 Raspberry Pi Compute Module 4 BCM2711B0T on new 55mm x 40mm 2x100 pin form factor with extra breakout IO board 
     CM4101000 1Gb RAM Lite SOM 
     CM4102000 2GB RAM Lite 
     CM4104000 4GB RAM Lite 
     CM4004008-4GB-RAM 8GB-EMMC SOM System on Modules 
     CM4104032 4GB RAM 32GB emmc 
     CM4108000 8GB RAM Lite 
     CM4008016 8GB RAM 16Gb eMMc
2021 Raspberry Pi SC0763 Compute Module 4S CM4S with ddr2 sodimm pinouts but not electrically the same with suitable IO board extra cost - 
     CM4S01000 1GB RAM Lite
     CM4S01008 1GB RAM 8GB eMMC Flash
     CM4S02000 2GB RAM Lite
     CM4S04000 4GB RAM Lite
     CM4S04016 4GB RAM 16Gb KLMAG1JETD-B041 
     CM4S08000 8GB RAM Lite 
2021 Pi 4 v1.4 BCM2711B1 upgraded power regulator, to deal with 8gig of ram being more power hungry 
2021-48 Raspberry Pi 4 model B v1.5 2GB 


2023 Pi 5 v1.0 BCM2712 Quad A76 @2.4Ghz - VideoCore VII - no audio socket - dual 4k from mini hdmi - fan connector - 5.1V 5A psu 
2024 Pi 5 2GB DDR4 version uses BCM2712D0 
2024 Pi-500 with 8Gb LPDDR5 and membrane keyboard 
2024 Pi 5 v1.1 
2024 Raspberry Pi Compute Module 5 CM5 BCM2712 55mm x 40mm form factor with additional IO board 
     CM5004000 04GB RAM 0GB eMMC Lite
     CM5008000 08GB RAM 0GB eMMC Lite
     CM5016000 16GB RAM 0GB eMMC Lite
2025 Pi-500+ with 256GB NVMe storage, 16GB LPDDR4 RAM, and Gateron KS-33 Low Profile Blue mechanical keyboard switches 
2025 Pi5 1GB DDR4 announced 


2022 PiOS linux goes 64bit 
2024 Pi Trading IPO stockmarket stock exchange listing 


2026 April and May Aros 64bit fixed, added AHI audio, VC4 gfx started, usb functions added to rom  
2026 June and July Aros 64bit usb2otg started, dma.resource, sdio.resource, bwfm.device wifi added 
2026 Late July daily 64bit Pi3 LE little endian builds start 
2026 August Pi 4, 400, 5 and 500 DTBs added, expanding existing support and wifi for Pi4 and Pi5 
2026 August Pi5 HAT+ nvme and HDMI, AHI RPiI2S added, Pi4 HVS5 video scaler started, 
2026 
2027 


2028 Pi 6 
&lt;/pre&gt;


The vcgencmd can be used to inspect and dump the current system configuration. 
vcgencmd runs on top of VCHIQ as an RPC. The mailbox interface is an alternate but much simpler RPC. 
VCHIQ is a bridge (queue) between the CPU and the GPU so they can communicate with the firmware. 

Loads of [https://github.com/6by9/rpi3-gpiovirtbuf/blob/master/rpi3-gpiovirtbuf.c mailbox] which uses the GPIO control calls. [https://github.com/raspberrypi/firmware/wiki/Mailboxes may also be of interest] 

A fair number of vcgencmd examples (search for vc_vchi_gencmd_init). [https://www.raspberrypi.org/forums/viewtopic.php?t=229203#p1406112 sends the relevant vcgencmd commands] to update the scaling kernel, but the [https://github.com/raspberrypi/userland/blob/master/host_applications/linux/apps/gencmd/gencmd.c command] is just a text string. Parsing and execution of the instructions is performed by the VideoCore firmware. 

The Raspberry Pi runs two separate operating systems: Linux/Aros on the ARM, and a threedx RTOS called vcos running on the Videocore 4 VPU: vcos is commonly called &quot;the firmware&quot;. Vcos is tasked with performing certain system services, for example running the display and audio outputs. The VCHI driver provides an interface to allow drivers to talk to vcos. 


Doubtful, on any [https://www.web3d.org/ Web3d] [https://developer.mozilla.org/en-US/docs/Web/API/WebGL_API WebGL] or [https://github.com/immersive-web/webxr WebXR] [https://developer.mozilla.org/en-US/docs/Web/API/WebXR_Device_API Device API] [https://developer.mozilla.org/en-US/docs/Web/API/XRInputSource XRInputSource] support. Hopefully, never/limited support features like location, peer-to-peer, invasive web apps, unwarranted storage, payments, proprietary video streaming etc 

*spreadsheet [https://git.sheetjs.com/sheetjs/sheetjs sheetjs] [https://github.com/mleibman/SlickGrid SlickGrid] [https://github.com/6pac/SlickGrid SlickGrid] [https://github.com/jspreadsheet/ce jspreadsheet ce] [https://github.com/dream-num/Luckysheet Luckysheet] [https://github.com/ruilisi/fortune-sheet fortune-sheet] [https://github.com/dream-num/univer/ univer]  probably without xlsx support 
*presentations [https://github.com/impress/impress.js/ impress.js simplified] [https://github.com/bwlewis/slides slides] [https://zenomt.github.io/mdslides/ github markdown slides] [https://github.com/Patternslib/slides Patternslib slides markdown] probably without pptx support 
*weather [https://github.com/Himanshu3412/Weather-Forecast Weather Forecast], [https://github.com/kaushalsahu07/weather weather needs API key], 


==Future==


[https://github.com/ARMSX2/ARMSX2 Arm pi of pcsx2] 


[https://tube.cadence.moe/ Cloudtube], [https://github.com/TeamPiped/documentation/blob/main/content/docs/public-instances/index.md TeamPiped], [], [], [], 

[https://hyperpipe.codeberg.page/ hyperpipe], [https://ytify.pp.ua/ ytify], [], [], 

[ ytdl], [https://github.com/golddominik893/liberatube liberatube]

[https://git.lolcat.ca/lolcat/4get 4get], [https://github.com/hnhx/librex librex], [], [], 


{{BookCat}}</text>
      <sha1>9acvq1hbhwjzi6rpuy2tcz7h8oyh6id</sha1>
    </revision>
    <revision>
      <id>4676529</id>
      <parentid>4676520</parentid>
      <timestamp>2026-10-17T14:19:52Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4676529</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="106204" sha1="dsj76bann5p0pkjm4lpw37z5gr6svjd" xml:space="preserve">{{ArosNav}}

[[#Native]]

[[#Hosted]]

[[#Build]]

[[#Hardware]]

[[#References]]

[[#Future]]


==Introduction==


[[File:Scalos00.png|thumb|Scalos on Aros Pi3b]]

Aros aims to cover Pi 3 to 5 512Mb+ RAM 


Options to boot from using a good power source to prevent the yellow lightning symbol. 
*With Pi3b+ the max you can get is 5.1V 2.5A with micro usb.
*With Pi4 5.1V 3A with usb-c 
*With Pi5 5.1V 5A, the amps went ever upwards, even to 5.1V 9A with usb-c 


* Pi500+ keyboard wedge - working but not much tested esp [https://github.com/aros-development-team/AROS/commit/48e9c8edcca4b5c1e1fe0b1123f2129f624af67b power button] 
* Pi500 wedge with up to date bootloader via PiOS - working but not much testing esp [https://github.com/aros-development-team/AROS/commit/48e9c8edcca4b5c1e1fe0b1123f2129f624af67b power button] 
* Pi 5  - Quad A76 64bit ARMv8 and RP1 &quot;southbridge&quot; with VideoCore 7 D0 (rev1.1) - untested 
* Pi 5  - Quad A76 64bit ARMv8 and RP1 &quot;southbridge&quot; with VideoCore 7 Pre-D0 C1 (Rev1.0) - untested 
* Pi400 RPI-400 keyboard wedge - resolution changing and audio from micro hdmi0 (near 40pin) and micro hdmi1 (near usb-c psu) - Fn F10 0x5e power on and off works or held down for over 7 seconds auto shutdown - keyboard ok - wifi and lan ethernet testing - 
* Pi 4  - Quad A72 64bit ARMv8 with VideoCore 6 
* Pi 3  - Quad A53 [https://www.raspberrypi.com/documentation/computers/processors.html 64 bit] ARMv8 with VideoCore 4 with '''fan''' to prevent overheating cpu 82C+ throttling 
* Pi02W - Quad A53 64bit - boots but [https://forums.raspberrypi.com/viewtopic.php?p=2387984#p2387984 usb not working but did in the past], 


* Pi 2 - Quad 32bit ARMv6 with VideoCore 4 - mostly not 64bit compatible 
* Pi Model B+ 32bit ARMv6 with VideoCore 4 - not 64bit compatible 
* Pi Model A and B 32bit ARMv6 with VideoCore 4 - not 64bit compatible 


===Native===

* 2013-03 Kalamatee starts work
* 2015-04 Work continues with mschulz on the kernel and Kalamatee (NicJA) on gpio and usb
* 2018 [https://www.patreon.com/posts/i-owe-you-some-20956961 mschulz resume adding BE big endian support], [https://www.patreon.com/michal_schulz/posts Big endian on Pi]  
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bsek latest commits for pi 3b, 4 and 5 64bit] 
* 2026 [https://github.com/aros-development-team/AROS/commits?author=metaneutrons latest commits for Pi5]
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bitplane latest commits for ARM]


====64bit====

'''Download''' A [https://archive.org/details/piAROS Pi Distribution (Distro) has started] and the contents copied to fat32 8GB+ microSD card (there will be drawers/folders - boot c Classes Demos Developer Devs Extras etc only showing). The SD can be plugged in to the Pi. And power on. [https://pi.amiga.icu/ Repository]

'''Not recommended''' but [https://aros.sourceforge.io/nightly1.html RaspberryPi 3, 3+, 4 and 5 64bit ArmV8 nightly builds] [https://sourceforge.net/projects/aros/files/ and alternative site and nightly2] which is a test version of '''very few''' apps with both raspi-aarch64-system and raspi-aarch64-contrib can be unbz2'd to a SD or SSD as appropriate. 

64bit build works well on a single core LE little endian. Multicore [https://github.com/aros-development-team/AROS/commit/1df0747c2bda3523a43029725a709b1f377d84ec may follow]. Any issues booting could be down to the SD card so please use another SD to see if it is resolved. Remember Aros Arm uses FAT32 and Aros can detect issues with this format very acutely (once fault found, FAT 0x0FFFFFF7 bad cluster so no files written after that, no repair). Please report your experiences in the [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2138&amp;pid=15057#post_15057 Aros forum thread], [https://forums.raspberrypi.com/viewforum.php?f=179 Raspberry Pi Aros Dev and User forums], [https://forums.raspberrypi.com/viewtopic.php?p=2387984#p2387984 previous Raspberry Pi forum thread]. Any bugs or issues can be [https://github.com/aros-development-team/AROS/issues described here to fix] 


*Pi500+   untested usb3 booting or nvme ssd 
*Pi500    untested usb3 booting 
*Pi5      untested usb3 booting 
*Pi400    boots with '''USB3''' port based sata3 ssd 
*Pi4      untested (may need eeprom update from PiOS or Pi SD Imager) 
*Pi 3 B+  is pre-configured for USB sata3 boot - untested 
*Pi 3 B   may need [https://www.youtube.com/watch?v=ubnwvxF3Klc PiOS to set OTP to boot from usb - do so at your own risk] - if OTP set to usb, boot works but slower than SD card 

Speed write wise (top faster) 
&lt;pre&gt;
*NVME Pi5 untested    &gt;1000MB/sec  or faster if matched correctly 
*Sata3 ssd              500MB/sec
*SD        V90           90MB/sec  4K maybe 8K 
*SD        V60           60MB/sec  1080p 
*SD     U3 V30           30MB/sec  720p 
*SD C10 U1 V10 A1 A2     10MB/sec  minimum should be used now 
*SD C06                   6MB/sec  
*SD C04                   4MB/sec 
&lt;/pre&gt;


As a homage to the past, Aros shows a reduced number of icons but this can be changed by left mouse click in the window and then right click down to Window -&gt; View -&gt; All files

Windows can be manipulated by the top (moving) and the bottom right corner (resizing) only. 

Zune like MUI gui interface, has a unique quirk in that after changing a setting in a text box, you may sometimes need to press Enter/Return before clicking OK, Save, etc 


Double left mouse click on most picture (Developer/Debug/Tests/Datatypes), audio and video files are supported, via datatypes, by the multiview application. 
Esc escape key usually closes open windows even the desktop 

In Prefs/Appearance some decorative theming elements need work. There is a few Mason icons in /Prefs/Presets/Icons/Mason/ and the ever present default Gorilla - Icon exchange in works 

For more intensive graphics applications, you may need to edit config.txt in the root folder and change 128M to 256M to adjust more memory to graphics usage 

If your cursor should '''appear''' to vanish, fear not it is still there. Please head to the top of the screen i.e. the title bar, hold down the left click mouse and drag the screen down a little and the cursor will appear again. Then you can drag the screen up again. 


Like most amiga like OSs the audio and networking need to be setup manually 

Audio AHI prefs - Mode settings tab - needs both Music unit and Unit 0 set to RPiHDMI:16 bit stereo++  or RPiPWM:16 bit stereo++ at 44100Hz. Press '''Save or Use''' button after each choice 


For wireless, please use the Wifi prefs and already selected device bwfm.device. Press Scan and double right click on the router and enter password. You may need to setup after every power off
*if asking for password again - press cancel and go to Network Prefs, Wireless Networks tab and highlight the router line and hit the remove button and press the cancel button. Retry with Wifi prefs again 
*...waiting for an address - Disconnect and try Connect 
Until, Connected to &lt;router&gt; - 192.168.x.x 


For lan ethernet port, please use Network prefs and the following hardware is 
*lan9514    Pi3b Pi2 not supported at the moment 
*lan7515    Pi3b+ type into Device  usblan78xx.device as net0:  remove other device(s) 
*bcmgenet   Pi4 Pi400 choose for Device bcmgenet.device 
*cdnsgem    Pi5 Pi500 Pi500+ RP1 i/o for cadencegem 
 (network prefs may forget random information when rebooted) 


Summary
&lt;pre&gt;
*3b    ethernet not supported, usb ethernet not working but wifi prefs setup works 
*3b+   wifi working and ethernet works 
*4     untested 
*400   wifi and ethernet untested 
*5     wifi and ethernet untested
*500   wifi and ethernet untested
*500+  wifi works 
&lt;/pre&gt;


Type in 'aarch64' in the [https://archives.arosworld.org/index.php?function=search&amp;tool=simple search box] and you will see available software packages / apps. apkg can be used to inspect and install applications. 

[http://archives.arosworld.org/index.php?function=browse&amp;cat=network/browser amelinium web browser (JS 1.6 ES9 ECMASCript 2018)] is available with an [https://eab.abime.net/showthread.php?t=122494&amp;page=80 eab thread] reminiscent of [https://github.com/zapek/Voyager Voyager] and to a lesser extent [https://github.com/amigazen/aweb3/ Aweb JavaScript 1.5 (ECMAScript 3)] as css and javascript websites can be slow to load or resolve (no JIT) and nothing from facebook, reddit etc. 

Press Cancel at screenmode selector or -wb argument to get windowed version. You could use the Shift + Del shortcut or mouse wheel should work to delete all text at once. Html5test gives 189 (1.29), 300 (1.31), 301 (1.39) out of 555, some bigger Amiga like browsers are around 370+ but it does less better. 

You may have to delete the cache (Menu -&gt; Page -&gt; Delete cache) to fully retest big Amelinium updates or free up space. 
Be aware [https://pianetaamiga.it/en/reportage-pianeta-amiga-2026/ some site pages] can use up hundreds of MBs of cache very quickly 

 DNS lookup failed...  close browser and reboot and setup wifi again - repeat until it works again 

 youtube video and audio - js button for javascript must be on/shaded -  Settings -&gt; Soundoutput - AHI 
Any restriction to lower resolutions is due to [https://docs.invidious.io/faq/#q-where-are-the-360p480p1080p-quality-options bandwidth]. Either CPU/GPU, internet speed and/or video quality. Pi3 can expect 480p (wifi) to 720p (ethernet). Pi4 expect (wifi)  (ethernet). 

Telegram https://t.me/s/channel_name for public messages from vamped_amiga chatamigagames demoscenecracktros 

*art local js apps like dpaint.js 


There is normally no Bluetooth support for most amiga like OSs but Aros has one [https://github.com/aros-development-team/AROS/commit/6942cbfbf66426d21963a7fcd8aba6aff611a9e0 work in progress] [https://github.com/RPi-Distro/bluez-firmware/tree/pios/trixie/debian/firmware/broadcom firmware] 

*Bluetooth 4.1 BCM43430A1.hcd Pi3B, Pi3A, Zero 2W 
*Bluetooth 4.2 BCM4345C0.hcd  Pi3B+, Pi4 
*Bluetooth 5.0 BCM4345C5.hcd  Pi4B rev, CM4 and maybe Pi5 and CM5 

&lt;pre&gt;
*bthid    keyboard mouse support 
*btserial serial 
*btpan    short range wireless connecting devices 
&lt;/pre&gt;


Only the Pi5 has a RTC real time clock, the other Pis will need to use ntp services [https://github.com/aros-development-team/AROS/commit/29cd4116330dc7f692d90757eacc59fb3f31ae70 sntp] with time.cloudflare.com pool.ntp.org or Cloudflare 162.159.200.1, 162.159.200.123, 2606:4700:f1::1, 2606:4700:f1::123 or [https://github.com/bohunamiga/PiNTP PiNTP -s goodtime.ijs.si or ntp1.ptb.de] to get the date and time from the internet. Can use date in a shell e.g.  date 24-Dec-2026 23:59:59  but this will need to be done again after every reset/power off. Maybe [https://github.com/aros-development-team/AROS/commit/28674a157bc56175aa668e7b62dca6fa740578dc ds3231 rtc with dtoverlay=i2c-rtc,ds3231 in config.txt] 


It helps to have all usb devices already plugged in before power on to detect at the moment. Even then some usb devices will freeze the mouse cursor and the only resolution is to remove the offending usb device and reinsert. Sometimes, the reinsert leads to the mouse cursor vanishing, it is still there and responds to left mouse clicks, top of the screen and pull down the screen. 

USB classes support from Prefs/Trident is still work in process 
*usbaudio working on usb3 port (blue) on pi4, 400 but not working (no rt isochronous) on usb2otg (white or black) for pi3b, zero 2w 
*[https://aminet.net/package/mus/midi/camd camdusbmidi] detects midi devices without a preferences file (Prefs/Env-Archive/sys/midi.prefs) as [https://www.youtube.com/watch?v=RBxHkwy4Nrw auto setup now] possibly with [https://github.com/metaneutrons/mt32-pi metaneutrons mt32-pi] [https://github.com/rtzor/mt32-pi mt32-pi fork] [https://github.com/ahmadexp/mt32-pi fork] [https://github.com/gmcn42/mt32-pi-control control of] [https://github.com/dwhinham/mt32-pi mt32-pi pi3+]. Alternative of [https://homspace.nl/samplerbox/ SamplerBox]. 

Will need developer clang gcc tools to look at 64bit ports of [https://archives.arosworld.org/?function=showfile&amp;file=driver/audio/usbmidi.i386-aros.lha usbmidi], [https://aminet.net/package/mus/midi/CAMD_Toolkit CAMD_Toolkit], [https://aminet.net/package/mus/midi/camdtools camdtools], [https://github.com/cnvogelg/amiditools amiditools], [https://github.com/timoinutilis/midi-sequencer-amigaos horny src], [https://aminet.net/package/mus/midi/horny-base horny-base], [http://bnp.hansfaust.de/index.html BnP], [https://arosarchives.os4depot.net/?function=showfile&amp;file=audio/misc/timidity.lha timidity], 


Regarding 680x0 emulation, there are several options (not implemented yet) that could be considered 
*[https://github.com/aros-development-team/AROS/blob/6722a0ae9e03fe5d26e32703360bd2059e0864cc/rom/m68kemu/README.md?plain=1#L424 m68kemu.library] for some Amiga productivity where the cpu is emulated and the system calls are redirected to Aros ones
*[https://github.com/BlitterStudio/amiberry amiberry] (winuae) for everything else like games 
*[https://github.com/jonx/AROS/tree/aarch64-darwin-graft/arch/all-darwin/libs/emu68k emu68k] 
*[https://scriptedamigaemulator.net/ Scripted Amiga] with [https://github.com/naTmeg/ScriptedAmigaEmulator ScriptedAmigaEmulator] or older [https://github.com/gbraad-amiga/ScriptedAmigaEmulator2 ScriptedAmigaEmulator2] 
 Hopefully getting Pi3 up to 25Mhz 68040 (non JIT) and 50Mhz 68040 (JIT) 
 Pi4 maybe getting up to 50Mhz 68040 (no JIT) and 100Mhz 68040 (JIT) 


[https://pinout.xyz/ GPIO 40 pins] [https://learn.sparkfun.com/tutorials/raspberry-gpio/gpio-pinout pinout] 

Some exceptions:

*Physical pins 27, 28 (GPIO0, 1) are an internal I2C bus and should not be used
*The other I2C on pins 3, 5 (GPIO 2, 3) can be used generally, but be aware they have permanent pull-up resistors to 3.3V
*For MIDI use USB but there are dedicated UART pins 8, 10 (GPIO 14, 15).

With a HAT it's more awkward -- you need to know which pins are used by the HAT and avoid them. Hopefully this will be documented.

Remember all GPIOs are 3.3V (not 5V tolerant), floating/noisy inputs can cause odd behavior, and that shorting the power supplies can cause instant death of the Pi.

In the shell (Cntrl + C to end) 

 GPIO PIN/A/N,SET/N,GET/S,MODE/K,PULL/K

Controls and queries hardware GPIO pins via gpio.resource which is stored in the rom or Devs/ '''please test''' 

*PIN   -- (Required) Target GPIO pin number (e.g. 12).
*SET   -- Set pin output value to 0 (LOW) or 1 (HIGH).
*GET   -- Read and print current digital input level (0 or 1).
*MODE  -- Configure pin mode: IN (Input), OUT (Output), ALT (Alternate).
*PULL  -- Configure pull resistor: NONE, UP, DOWN.

EXAMPLES
&lt;pre&gt;
GPIO 12 MODE OUT
GPIO 12 SET 1
GPIO 12 GET
GPIO 13 PULL UP
&lt;/pre&gt;


[https://gpiozero.readthedocs.io/en/stable/installing.html Current] [https://gpiozero.readthedocs.io/en/v1.2.0/api_boards.html old support for gpiozero is unknown at present] [https://energenie4u.co.uk/res/pdfs/ENER314%20UM.pdf and associated 433MHz equipment] [ USA X10 security and lights via USB] [ OpenHab with Shelly Smart Plug connected over Wi-Fi, controlled by MQTT or HTTP] 


Printing only with Postscript but [https://github.com/bohunamiga/MintPRINT one] of [https://github.com/boingball/MintPRINT two] [https://github.com/Andiweli/AmiAirPrint/tree/main AirPrint] IPP has been attempted with [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2061&amp;pid=13954#post_13954 discussion] 


Youtube 

[], [], [https://www.youtube.com/watch?v=X4fmWAIv7FE Aros native on Pi3b], 

[], [], [https://www.youtube.com/watch?v=TSxlYb1eQWU Installed on Pi3b+], 

[], [], [https://www.youtube.com/watch?v=NFF1H3jCoz8 testing Aros native on Pi400], 

[], [], [https://www.youtube.com/watch?v=nIVx7mh1E1Q&amp;pp=ygUHYXJvcyBwadIHCQkTDAGHKiGM7w%3D%3D Aros on Thumb 2 based 32bit-ish ARM STM32H743 board], 


[https://www.youtube.com/watch?v=zQM4CD64xDE&amp;t=612s&amp;pp=ugUEEgJlbg%3D%3D Performance under Linux] but on Aros... 

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot; |Pi
! width=&quot;10%&quot; |Single Core 2D
! width=&quot;10%&quot; |Single Core 3D
! width=&quot;10%&quot; |Single Core 3D
! width=&quot;10%&quot; |SMP 2D
! width=&quot;10%&quot; |SMP 3D
! width=&quot;10%&quot; |SMP 3D 
! width=&quot;35%&quot; |Comments
|-
| &lt;!--Pi--&gt;Pi3 
| &lt;!--Single Core 2D--&gt;
| &lt;!--Single Core 3D--&gt;
| &lt;!--Single Core 3D--&gt;
| &lt;!--SMP 2D--&gt;
| &lt;!--SMP 3D--&gt;
| &lt;!--SMP 3D--&gt;
| &lt;!--Comments--&gt;
|-
|}


==== 32bit ====

For the Pi1 Pi2 Pi2B the status of AROS native ARMv6 for 32bit RasPi was OK. System booting, USB working (although with some issues but plans to fix them). 32bit native [http://www.aros.org/nightly1.html ARMv6 32bit nightlys] raspi-armhf-system raspi-armhf-contrib unbz2'd to fat32 microSD 


===Hosted===


AArch64 CPU backend for AROS, a Cocoa/Metal display, clipboard / host-volume / CoreAudio / BSD-sockets bridges, GPU 2D via gpufx.library, a 68k→AArch64 JIT (run68k), and a full Rust std port. On [https://www.jkn.me/blog/macaros-aros-on-apple-silicon/ latest Apple Silicon] [https://github.com/jonx/Macaros early buggy alpha version of hosted Aros .dmg on MacOS12+]. Please use [https://github.com/jonx/Macaros/issues MACAros github] for issues, features etc and possibly [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2030&amp;pid=13910#post_13910 here] 


[http://www.aros.org/snapshots1.html old linux and android hosted 32bit] 


==== Hosted ====

=====64bit=====

[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80&amp;pid=13667#post_13667 Ubuntu Linux PC hosted Pi compiler build] 

[https://github.com/BlitterStudio/aros-compiler-docker Docker based cross compiler for various Aros systems], 

[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80 From the Aros Raspberry pi 3 64bit thread] 
Instructions on building 64-bit Raspberry Pi AROS and cross-compiler from sources.

You will need:
- Ubuntu 24.04 or 26.04
- qemu-system-aarch64 installed
- Internet connection
- rpi-scripts.tar.gz downloaded (https://axrt.org/download/aros/rpi/rpi-scripts.tar.gz)

1) Install prerequisites:

sudo apt install git gcc g++ make gawk bison flex bzip2 netpbm autoconf automake libc6-dev liblzo2-dev libpng-dev gcc-multilib byacc python3-mako cmake yasm curl nasm

2) Clone sources

cd &lt;project-directory&gt;
git clone https://github.com/aros-development-team/AROS.git --recurse-submodules

3) Extract rpi-scripts.tar.gz. Copy all files into your project directory so that you have:

AROS (the directory with cloned sources)
fix-dotdot.py
rebuild.sh
recreate-sdcard.sh
run-qemu.sh
update-sdcard.sh

4) Run ./rebuild.sh. Select option 1) toolchain-core-aarch64

This will execute process of building a cross-compiler. During this process packages will be downloaded from Internet. This process can take up to 2 hours. If there are some missing dependencies, install them with 'sudo apt install' and restart this step.

5) Run ./rebuild.sh again. Select option 2) core-raspi-aarch64

This will build system files for 64-bit Raspberry Pi AROS. This process can take around an hour.

6) Run ./recreate-sdcard.sh

This will create an sdcard.img file with contents of previous step.

7) Run ./run-qemu.sh

This will start QEMU with SD card image and ROM images. It will boot into AROS.


=====32bit=====

Ubuntu VM approach to compiling [http://lallafa.de/blog/2013/06/building-aros-hosted-for-raspbian/ Linux hosted AROS June 04, 2013]

 ../AROS/configure --target=linux-armhf  --enable-includes=/usr/arm-linux-gnueabihf/include --x-includes=/usr/arm-linux-gnueabihf/include --x-libraries=/usr/arm-linux-gnueabihf/lib

arm-elf- is symbol-linked to arm-linux-gnueabi- (arm-linux-gnueabi- is more correct in this case, because it's going to be compiling the ARM AROSBootstrap for ARM Linux)

*armel - many of the &quot;android&quot; machines require since the entire OS is made for soft float VFP. 
*armfp - Efika MX target, Raspberry PI, EfikaMX, Pandora and virtually everything (VFP)

Keep in mind it's possible to start hardfp AROS hosted on softfp system, though, as long as no calls between AROS and host require floating point parameters. NOTE: hardfloat objects *cannot* be linked with softfloat objects - they have a different ABI.

Just keep in mind the arm nightly build machine is quite complex beast. It needs the x86_64 host compiler to compile AROS tools. The arm version is built every night using gcc-4.6.2 crosscompiler (built together with AROS) and successfully builds armel and armhf linux hosted targets.

*needs an AROS code compiler for ARM target 
*as well as unix compiler for ARM linux host (would be best to have both softfp and armhf, we have softfp only now) with full set of libraries and includes.

with—disable-crosstools  $AROS_CC  is always a wrapper around $KERNEL_CC  ?  If  so,  this  is  wrong for some ports. This can break Darwin, Windows and Android port. 
Yes,  Android  port  will  build.  And  even  work. But it's not good because  the  port  will  not  be ABI-compatible with other ARM ports. Android's ABI is different from GNUEABI. For example:

&lt;pre&gt;
enum test {foo, bar};
enum test testvar;
&lt;/pre&gt;

sizeof(testvar)  will  be  equal  to sizeof(int) in GNUEABI (Linux and AROS)  and  sizeof(short)  on  Android. This affects linking objects from static linklibs, for example.

Previously everything worked because $AROS_CC was a wrapper on top of $HOST_CC. And a real crosscompiler was used on non-ELF hosts.

Android is the same. $KERNEL_CC is incompatible with AROS.

compiler=kernel  is  appropriate _ONLY FOR CODE WHICH RUNS ON HOST OS_ (or  barebone  hardware,  if  we  talk  about  native).  This includes bootstraps,  their  linklibs, and host-side dynamic libraries (Windows makes extensive use of them because of architectural considerations.

No single AROS object should be compiled with this setting. $KERNEL_CC is really compatible with AROS *ONLY IN LINUX-HOSTED* and no more. On other systems (Darwin, Windows,  Android) this is not true any more, and compiler=kernel is never going to work.

If  you  want  to  compile your AROS module against host OS includes, append  the  following  to  USER_INCLUDES  (or  USER_CFLAGS,  this  is effectively the same):

 -isystem $(GENINCDIR) $(KERNEL_INCLUDES)

$(KERNEL_INCLUDES) expands to:

 -isystem  &lt;your_os_includes&gt;  -isystem  &lt;host_OS_gcc_private_includes&gt;
 -nostdinc

This makes AROS compiler adhering to host OS APIs.

If you want some preprocessor symbols based on what your host OS actually is, add something like -DHOST_OS_$(AROS_HOST_ARCH).

Why is there $(GENINCDIR) at all? Because host OS has its own libc includes, which would conflict with AROS ones. And the host OS libc is not binary-compatible with AROS one.

Why doesn't Windows-hosted port use $(KERNEL_INCLUDES) ? Because WinAPI includes conflict with AROS ones in fundamental typedefs, like WORD, BYTE and BOOL. It's almost impossible to deal with this in any other way than rewriting WinAPI definitions using AROS types.

Building under centos 6.3 (i386) currently, and AROS creates the toolchain itself. haven't yet committed the necessary changes but &quot;./configure --target=raspi-armhf&quot; is enough to start, then &quot;make arosboot-raspi&quot; will generate arosraspi.img (containing the bootstrap, kernel.resource, and exec.library) as well as arosraspi.rom (containing all the other essentials components such as dos, graphics etc).  It will also copy over a config.txt file to make the raspi bootstrap code load the correct kernel, and a cmdline.txt that enables exec debug output.

*armel = typically Debian 6, Ubuntu Maverick, Android, 
*armhf = typically Debian 7, Debian 8, Ubuntu Precise,

Cross-compiling Ubuntu ARM softfp 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armel' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armel] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armel.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabi libx11-dev:armel libsdl-dev:armel
&lt;/pre&gt;

&lt;pre&gt;
 ./configure --target=linux-arm --x-includes=/usr/include \
             --enable-includes=/usr/arm-linux-gnueabi/include
&lt;/pre&gt;

Cross-compiling Ubuntu ARM hard-float 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armhf' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armhf] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armhf.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabihf libx11-dev:armhf libsdl-dev:armhf
&lt;/pre&gt;

&lt;pre&gt;
    ./configure --target=linux-armhf --x-includes=/usr/include \
                --enable-includes=/usr/arm-linux-gnueabihf/include
&lt;/pre&gt;

Now, the AROS build is configured properly and all you need to do is:

 make


==Build==

===64bit===

[https://github.com/aros-development-team/AROS/blob/7016ce28bfdb754182edb16011c98faaf5413c29/arch/aarch64-raspi/boot/mmakefile.src#L180 boot makefile] 


===32bit===


# download/checkout the source someplace, e.g. /build/AROS-Src/
# make a directory to store external sources AROS downloads, e.g. /build/Ports
# make a build directory, e.g. /build/aros-raspi-armhf
# cd into the build dir, configure, and then run make -:

&lt;pre&gt;
&gt;cd /build/aros-raspi-armhf
&gt;/build/AROS-Src/configure --target=raspberrypi-armhf --with-serial-debug --enable-ccache --with-portssources=/build/Ports
&gt;make
&gt;make arosboot-raspi
&lt;/pre&gt;

then copy the files from /build/aros-raspi-armhf/bin/raspi-armhf/AROS/ onto an sdcard, and download/copy the Raspi firmware files onto it.

You should then be able to boot the sdcard on your RasPi.

The current W.I.P tree to svn. it can be built as follows ..
&lt;pre&gt;
./configure --target=raspi-armhf
make arosboot-raspi
&lt;/pre&gt;

That will generate arosraspi.img, arosraspi.rom and config.txt in bin/raspi-arm/AROS - so either copy just those files to a fat formatted SD card (with the firmware files on), or copy the whole contents of the AROS folder.

NB - if you have a Linux/other install, backup the existing config.txt first

arosraspi.img contains the bootstrap (which has very basic mailbox code, framebuffer/gpio init, and console &quot;emulation&quot; via code pinched from our libbootconsole), kernel.resource, and exec.library

arosraspi.rom contains all the other components needed to boot AROS.

The config.txt file will tell the RasPI bootstrap to load the arosraspi kernel and ramdisk (rom).

the bootstrap has minimal mailbox code, planning on adding either a resource or library that driver/app code will use to access it (likewise for GPIO)


Help building AROS hosted on Linux ARM

Was looking a way to use more my Handheld ARM based called Pyra (Dragonbox Pyra) an ARM (Omap5 cpu with 4GB ram) linux based machine (Debian Buster v10 with kernel 5.6.19 adapted) and have a try to compile the latest Aros sources by Deadwood directly on this device.
Compilation stops after build libpopupmenu.a and trying to build libatomic have this error:

&lt;pre&gt;
    Configuring build in bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic
    configure: WARNING: unrecognized options: --disable-nls, --without-x
    checking for --enable-version-specific-runtime-libs... no
    checking for --enable-generated-files-in-srcdir... no
    checking build system type... arm-unknown-linux-gnu
    checking host system type... arm-unknown-aros
    checking target system type... arm-unknown-aros
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for arm-aros-strip... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-strip
    checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
    checking for gawk... no
    checking for mawk... mawk
    checking whether make sets $(MAKE)... yes
    checking whether make supports nested variables... yes
    checking for arm-aros-gcc... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-gcc
    checking whether the C compiler works... no
    configure: error: in /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic':
    configure: error: C compiler cannot create executables
    See config.log' for more details
    make[2]: *** [mmakefile:4489: /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic/.configured] Error 77
    [MMAKE] make --no-print-directory TOP=/media/farox/pyra2/arosbuilds/toolchain-core-armhf-build SRCDIR=/media/farox/pyra2/arosbuilds/AROS CURDIR=tools/crosstools/gnu TARGET=tools-crosstools-gcc-libatomic-configure -s --file=mmakefile tools-crosstools-gcc-libatomic-configure failed: 512
    [MMAKE] Error: Error while running make in tools/crosstools/gnu: No such file or directory
    make[1]: *** [Makefile:361: linklibs-libatomic] Error 10
    make: *** [Makefile:183: crosstools] Error 2
&lt;/pre&gt;


looking at config.log on arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic

found that arosbuilds/toolchain-core-armhf/arm-aros-ld: cannot find -laeabi
so do make linklibs-aeabi-arm-quick
and the missing lib was built.

now the next stop is at
fatal error: bits/libc-header-start.h: No such file or directory
and
fatal error: sys/cdefs.h: No such file or directory
in many places so after checking that have this missing include files i have noted that my include path is a bit different, standard searching path is /usr/arm-linux-gnueabihf but in my system is /usr/include/arm-linux-gnueabihf
so if i add my path to some mmakefiles compilation goes on....but is a better way to add this path to avoid every mmakefiles to be changed?

fixed with adding
-I/usr/include/arm-linux-gnueabihf
to where is missing on mmakefiles like
USER_INCLUDES := -isystem $(GENINCDIR) -I/usr/include/arm-linux-gnueabihf $(KERNEL_INCLUDES)

P.s. I have changed many mmakefiles and have at least compiled (after many hours) the toolchain doing make every time in arosbuilds/toolchain-core-armhf-build (also have to disable making tests under cplusplus but don't remember the directory ...) but ask an help to have an automated way to correctly build without modify mmakefiles.


Last time built armhf target was around 2 years ago. At that point built is via cross-compilation from linux (ubuntu 22.04) using linux armhf crosscompiler (this can explain the path differences you are experiencing) as well as using AROS gcc cross-compiler in version 6.5.0 (build with option 21) in rebuild.sh). Since then AROS GCC has been updated to 10.5.0 and don't believe anyone tried to build the armhf target again.

My suggestion would be to downgrade GCC to 6.5.0 (via editing AROS/config/gcc_def file) and try to first build using cross-compilation from x86_64 linux. Once that works, you will have a &quot;template&quot; to compare to native compilation under arm linux.


Thanks for your suggestion...but think the toolchain with GCC 10.5.0 is compilable if i found a way to pass the path of my system to the script that build (option 21 on rebuild).
The other only changes are (but don't know where to modify...) is to add the build of libaeabi and disable the building of some tests under cplusplus that use exceptions and is not supported under ARM. try to crosscompile with my Linux amd64 PC.

For paths look into core-linux-armhf/bin/linux-armhf/gen/config/target.cfg. A number of build-wide variable is set there containing paths to local build system. These variables and the target.cfg file are generated by AROS ./configure script.

Thanks compilation now go forward...changed target.cfg under &quot;toolchain-core-armhf-build/bin/linux-arm/gen/config&quot; and do make on &quot;toolchain-core-armhf-build&quot; dir.

Need to find where to enable build libaeabi.a so can build the entire toolchain with option 21 of rebuild.sh


Found something that looks like libeabi in AROS/arm-all/arm-aeabi/mmakefile.src. Try adding a third line there:

#MM- linklibs-armhd : libklibs-aeabi-arm

Don't remember needing this library. Possibly the 6.5.0 GCC somehow does this while 10.5.0 is missing this.

Try adding this line (and the variant &quot;linklibs-armhf&quot; instead of hd) but it did not solve the automatic building of the missing lib. I must do &quot;linklibs-aeabi-arm-quick&quot;.
Anyway after have build the aeabi lib i succefully built the toolchain (after many hours...). Smile

To test I restarted from selecting option 21 (on rebuild.sh) but after many hours i get the same error of the kernel includes not found...maybe i need to modify the configure script for my case.

With the toolchain built i try to build the core-linux-armhf (DEBUG) (option 22) but after a while it stopped with
&quot;cannot find -laeabi &quot; so i made it built manually...and now i can continue compiling...i'll let you know if all goes ok.


== Hardware ==

===64bit===


====BCM2712====

With the Pi5 

Broadcom VideoCore 7 vc7 is an integrated GPU with 12 cores and up to 800 MHz clock. VideoCore VII is capable of OpenGL ES 3.1 and Vulkan 1.2. The driver support for the Raspberry Pi continues to build upon the [https://lore.kernel.org/dri-devel/20230928114532.167854-1-itoral@igalia.com/ open-source V3D driver] stack within [https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450 Mesa] hopefully be merged for Mesa 23.3. x265 HEVC accelerated untested, x264/h.264 and VP9 cpu only. 

*Raspberry Pi M.2 HAT+ Expansion Board 
*Geekworm X1001 PCIe to M.2 Key-M NVMe
*Geekworm X1003 PCIe to M.2 HAT NVMe SSD PIP Board for Raspberry Pi 5 
*Pineboards Pi Hut HatDrive! M.2 HAT 2024/V4 
*Hat+ Gen2 Gen3 Nvme
*GeeekPi 52Pi N04 for Raspberry Pi 5 NVME M.2
*


*2024 RPI AI HAT    - Hailo  20TOPs  no LLMs 
*2026 RPI AI HAT+ 2 - Hailo  40TOPs  slightly better? 


[https://www.raspberrypi.com/documentation/accessories/camera.html Cameras for Pi]
*Raspberry Pi camera module, the V3 with Sony IMX708 back-illuminated CMOS 12 Megapixel sensor
*Raspberry Pi Camera Module V2 – 8MP Sony IMX219 Sensor
*Raspberry Pi camera Rev 1.3, 5MP 1080P OV5647 image/video module, 2592 x 1944 pixels


====BCM2711====

With the Pi4 an ARM a72 cpu is about x3 times the size of an a53 in the Pi3 

the 2711b line used more power when idle, compared to the 2711c 

*2018 Raspberry Pi PoE HAT Power Over Ethernet Hat - design issues 
*2020 Raspberry Pi PoE+ HAT Power Over Ethernet Hat Pi3b+ Pi4 only - better design 
*Waveshare PoE HAT (B) with cooling fan for Raspberry Pi 3B+/4B 802.3af PoE 

*[https://github.com/axizo-pi/V3DLib vc6 V3D 4.2] is derived from [https://docs.broadcom.com/doc/12358545 vc4], but it is [https://docs.mesa3d.org/drivers/v3d.html significantly different] 
The QPU pipeline stays mostly the same, you still have an add ALU and a multiply ALU and it can issue two ALU OPs per cycle. There is still 4 SIMD lanes, interleaved over 4 cycles.
The instruction encoding for the QPUs is different, but the core instructions are the same.

Instructions for packed 8 bit int math has been dropped, along with most of the pack modes.
Instructions for packed 16bit float math has been added (2 floats at in a single operation)
With vc5/vc6, you write two packed 16f value to the tilebuffer (or four writes of 32f, if you are using the rgba32f framebuffer). And there is a handy vfpack operation which allows you to pack two f32s into a single 32bit value in a single instruction. You can vfpack directly into the tile buffer register.

the multiply ALU can now fadd, so you can issue two fadds per instruction. the add ALU has gained a bunch of new instructions 

the A and B register files have been merged. You still only get an A read and a B read per instruction, but they read from one big register file (which means the underlying memory block has gone from two sets of &quot;one read port, one write port&quot; to one &quot;two read ports, one write port&quot; block)

The theoretical max FLOPs per QPU remains the same at two per cycle, other than the bump from 400mhz to 500mhx but it looks like a lot of effort has been put putting those theoretical FLOPs to better use. 
*vc4 could run one or two threads per QPU. When you ran in two thread mode, the available register file halfed to 32 registers.
*vc5 added a four thread per QPU mode, with 16 registers per thread.
*vc6 doubled the size of the register file. You could now use all 64 threads in two thread mode and 32 registers in for thread mode. Single thread mode was removed, you always have at least two threads.

With the threading improvements, the QPUs should spent much less time idle waiting NOPs for memory requests. Most of the design changes have gone to improving the fixed function hardware around the QPUs. A fixed function blend unit has been added, which should reduce load on the QPUs when doing alpha blending. hope software blending is still possible 

The tile buffer can now store upto 4 render targets (up to 128bits per pixel, so if you are using 4 32bit render targets, you can't have a depth buffer)

A MMU, allowing a much simpler/faster kernel driver.

Many more texture formats, framebuffer formats.

h264/x264 as Pi3 

All the features needed for opengl es 3.0 

H.265 / HEVC decoder is a HEVCv2 Main 4:4:4 10 design supporting bitstreams up to profile 5.1
HEVC hardware decode supports 4kp60, 10-bit. Audio output is pretty much unchanged, but the HDMI audio channels now support 8x192kHz bitrates 

Each ALU typically have 2 floating point operators, and as you pointed out in a earlier post videocore 6 is no exception, with both a multiply and additive floating point operator. Thus theoretical GFLOPs are calculated with both operators in mind. That is what the 2 in my formula represents, and is common across any modern programmable shader, whether you calculate Nvidia, AMD, Intel, Boardcom or any other company's GPUs. Total ALUs * 2 * GHz clock = GFLOPs, In the case of Raspberry Pi 3, it's 24 ALUs * 2 operators * 0.4GHz = 19.2GFLOPs
If the Videocore 6 does indeed only have 16 ALUs (16 * 2 * 0.5GHz), you'd have only 16GFLOPs but they are better utilised 

Possible maximum performance 
&lt;pre&gt;
VideoCore IV @ 250MHz: 250 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 24 Gflop/s
VideoCore IV @ 300MHz: 300 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 28.8 Gflop/s
VideoCore VI @ 500MHz: 500 [MHz] x 2 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 32 Gflop/s
&lt;/pre&gt;

Faster LPDDR4 memory.


====BCM2837==== 

With the Pi3 
* Broadcom BCM43438 chip provides 2.4&amp;nbsp;GHz 802.11n wireless LAN, Bluetooth Low Energy, and Bluetooth 4.1 Classic radio support, 3B+ [https://github.com/aros-development-team/AROS/commit/afa5bc0bb17d5dd06bcfdbac00853a3799ca8d76 LAN7515] 

The overclock ability has diminished with each chip version as the energy usage has increased. BCM2837 is one of the warmest yet and benefits from active fan cooling if all four cpu cores are in use for a short while. Video playback maybe affected due to the lack of custom support in the GPU with Aros. 5 V / 2.4 or 2.5 amp power supply recommended if all four cpu cores are running, else throttling (cpu slowdown) might occur. 

[https://github.com/hermanhermitage/videocoreiv/wiki/VideoCore-IV-Programmers-Manual Dual VDP] and scalable QPU in [https://docs.mesa3d.org/drivers/vc4.html VC4] and x.264/h.264 accelerated untested only and VP9 on cpu or neon help 


ARMv8-A has [https://developer.arm.com/documentation/102412/0100/Privilege-and-Exception-levels privilege levels] where userspace typically runs at ‘EL0’, the kernel at ‘EL1’ or ‘EL2’ and the firmware at the highest level ‘EL3’. 


===32bit===

=== Core Kernel ===


====BCM2708(family)====
which includes the [http://elinux.org/RPi_Hardware BCM2835] (ARM1176JZF-S 700&amp;nbsp;MHz CPU + VideoCore IV GPU + up to 1GB RAM)

*Framebuffer (fb) using mailbox 
*IRQ scheduler, etc 
*Arasan based SD Card controller 
*Synopsis DesignWare USB 2.0 OTG controller [http://networkdirection.net/index.php?option=com_content&amp;view=article&amp;id=106:rasperry-pi-usb-controller&amp;catid=45:raspberry-pi&amp;Itemid=54 Unofficial DOCS pdf],  [dwc_otg.c FreeBSD], [], [https://www.riscosopen.org/viewer/view/mixed/RiscOS/Sources/HWSupport/USB/Controllers/DWCDriver/ RiscOS USB Driver], [https://www.riscosopen.org/forum/forums/5/topics/878 RiscOS USB Discussion], [https://www.riscosopen.org/forum/forums/11/topics/1893 Other USB RiscOS], [http://plan9.bell-labs.com/plan9/index.html Plan9 Miller's usb] http://plan9.bell-labs.com/sources/contrib/miller/, [https://github.com/Chadderz121/csud CSUD driver], 
*[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf SMSC 9512] USB LAN/Hub chip 
*CMOS RAM 
*VCHIQ port which sends messages to the GPU e.g. for mouse, keyboard, audio on HDMI, etc 
*Audio Driver 
*Serial Peripheral Interface Bus (SPI) 
*[http://www.susa.net/wordpress/2012/06/raspberry-pi-pcf8563-real-time-clock-rtc/ I2C registers]
*I2S 
*Universal Asynchronous Receiver Transmitter (UART) 
*[http://elinux.org/RPi_BCM2835_GPIOs GPIOs] and [http://www.adafruit.com/blog/2012/08/17/broadcom-bcm2835-peripheral-memory-map-and-gpio-alternate-use-chart-piday-raspberrypi-raspberry_pi/ Alternative view of GPIO]

BCM2836 
* For Pi B+, PI 2 and Pi 3 SMSC LAN9514 chip adding 10/100 Ethernet connectivity and four USB channels to the board

*[http://www.andrewscheller.co.uk/rpi_pcb_modules.html PCB], [http://elinux.org/RPi_Low-level_peripherals Low level features],


 Implemented so far... 

# Modify the configure system so that it correctly builds for the arm hardware float raspi target.
# Implemented the bootstrap to load the aros modules and prepare the arm to jump into them. Reworked the x86 console support so that parts can be stolen for raspi to use since t has no basic functionality to output to the display.
# Implemented a kernel.resource to prepare the raspi for running aros and provide the low level api calls to expose available resources and allow exec, etc function.
# Implemented serial debug support
# Implemented the exec (and kernel) functionality required to make multitasking work (and interrupts, exceptions, syscalls, etc)
# Implemented a timer.device to utilise the hardware timers.
# Implemented a very basic gfx driver to expose the hardware's framebuffer.
# Implemented an SD-Card driver for AROS which presently only supports the raspi's chipset but can easily be modified to support all sd-card hardware and media.
# Fixed the fat filesystem support in AROS so that it can boot on RasPi's normal SD-Card setup. The &quot;rom&quot; image files needed use a different filename than the default linux, etc images so can be easily installed without harming the existing files - you only need to change the loaded images in the config file to get aros to boot.
# Updated the build scripts to automatically download the necessary raspi firmware files and wrap it all up so that you can simply extract the archive to a fat formatted sdcard and boot it on the raspi without having to get anything else.
# fix everything in contrib and ports to build for raspi (needs proper testing/fixes but allows every component to actually compile at least, including owb) + numerous other fixes to get things working on arm/raspi ..


Improvements...

# Implement a USB chipset driver &quot;OR&quot; finish the existing one [https://github.com/aros-development-team/AROS/commit/c07d13c724f944674be5db54fc6a71ee72a01809 usb otg] - the current code is mostly a skeleton that should initialise the chipset and then needs relevant code to support the different transfer types. It also has the &quot;virtual&quot; hub code in place to represent the raspi's USB port (from poseidons p.o.v) 
# Implement a driver for the USB NIC (a few weeks - depends on USB above) 
# Write an [https://github.com/aros-development-team/AROS/commit/d55d0f74d20b769bbb8c8d386e5c1d7a9154f05a audio driver] (a few weeks - independent of USB) and [https://github.com/aros-development-team/AROS/commit/e93a4c245f27a87c9c4c1d39206694b39059998a HDMI]
# fix syscall bug in the current raspi kernel code
# Graphics depend on having a decent &quot;bcmdma.resource&quot; implemented as to use the cpu's dma engine. The sd card driver needs to use it for transfers to/from the controller - and the gfx system needs to use it for &quot;blitting&quot;. 
# [https://github.com/aros-development-team/AROS/commit/4019d84e4975d4dad987a12d57fe108f5ac048e6 Improve the gfx driver], [ vc4gfx HIDD] add [http://dri.freedesktop.org/wiki/VC4/ Gallium3D support] 
# [https://github.com/aros-development-team/AROS/commit/b13905b3e8e45b089f520b44692c81affddd066f Improve] the [https://github.com/aros-development-team/AROS/commit/3a876755c070f5c73c4f53c7f4d35b4f923088b9 sdcard] device driver  - which is also pretty basic but should work with most cards, rework it to also support pci, etc. sd card interfaces on x86 
# The current code using very rudimentary access to the gpio interface - so that should be implemented as some resource for other components to access, as-well as the i2c interface exposed over the gpio interface. that should have a hidd class implemented which uses the gpio resource to communicate.


 Boot up typical for most other OSs before the open sourcing of many binary blobs from 2017 onwards 

On power-up, the rpi [http://www.open.com.au/mikem/bcm2835/ BCM 2835] [https://github.com/hermanhermitage/videocoreiv VideoCore4] GPU, not the ARM CPU, is in control, and the SD card slot is the only peripheral device with power. The firmware burned into the BCM2835's VideoCoreIV GPU PROM requires a DOS-style partition table; a FAT-formatted first partition; and the freely redistributable but closed sourced Broadcom files “bootcode.bin” and “start.elf” in that partition.

The boot sequence carries out several pre-boot tasks

*On powering of the rpi, the GPU reads and executes bootcode.bin, which then loads start.elf 
*The GPU loads the “start.elf” file, eventually, into the L2 cache and then executes it
*configures the memory split for the CPU and GPU
*reads and parses “config.txt” from the same partition on the SD card and applies the settings (like a PC’s BIOS settings)
*loads the “kernel.img” file, again from the same partition
*activates the CPU to begin executing the loaded kernel image

The CPU/GPU memory split is hard-coded into start.elf, so Broadcom provides three start.elf images, to give 32M, 64M, or 128M to the GPU for multimedia performance, and the remainder to the CPU.

RPi uses [https://github.com/raspberrypi/firmware some closed source loaders] and at some point it loads a binary blob named &quot;kernel.img&quot; at 0x8000, at that point there would be a rudimentary Aros alive. If one wants to use the SD-card then there would have to be a driver for the interface and a fat filesystem handler (SD-card has to be formatted to fat filesystem)

Boot code and kernel are now linked together and made into that binary blob, just for starters. Raspberry Pi uses [http://kernelnomicon.org/?p=133 u-boot] and [http://kernelnomicon.org/?p=138 UBoot] as bootloader, there's already some code in the Efika MX port for that. UBoot is a native bootloader and not just for the raspberry pi, it loads after start.elf.

You can find Efika MX port from arch implementations, some hacking is needed for the mmakefile.src'es as iit dates back to before the Aros crosstool era or else you get some weird errors while building. You also need to code the bootstrap and serial handling.

At the moment it seems that a fastest route for the native build would be to make one binary blob without using the package system. Raspberry's memory layout is pretty simple and if the implemented u-boot doesn't support loading other modules 

&lt;pre&gt;
?          - alias for 'help'
mtest      - simple RAM test
autoscr    - run script from memory
base       - print or set address offset
bbm        - BBM sub-system
bdinfo     - print Board Info structure
boot       - boot default, i.e., run 'bootcmd'
bootd      - boot default, i.e., run 'bootcmd'
bootm      - boot application image from memory
bootp      - boot image via network using BootP/TFTP protocol
cmp        - memory compare
coninfo    - print console devices and information
cp         - memory copy
crc32      - checksum calculation
echo       - echo args to console
fatinfo    - print information about filesystem
fatload    - load binary file from a dos filesystem
fatls      - list files in a directory (default /)
go         - start application at address 'addr'
help       - print online help
iminfo     - print header information for application image
itest      - return true/false on integer compare
jade       -
loadb      - load binary file over serial line (kermit mode)
loads      - load S-Record file over serial line
loady      - load binary file over serial line (ymodem mode)
loop       - infinite loop on address range
md         - memory display
mm         - memory modify (auto-incrementing)
mtest      - simple RAM test
mw         - memory write (fill)
nfs        - boot image via network using NFS protocol
nm         - memory modify (constant address)
pci        - list and access PCI Configuration Space
ping       - send ICMP ECHO_REQUEST to network host
printenv   - print environment variables
rarpboot   - boot image via network using RARP/TFTP protocol
reset      - Perform RESET of the CPU
run        - run commands in an environment variable
saveenv    - save environment variables to persistent storage
saves      - save S-Record file over serial line
setenv     - set environment variables
sleep      - delay execution for some time
tftpboot   - boot image via network using TFTP protocol
USB        - USB sub-system
usbboot    - boot from USB device
version    - print monitor version
&lt;/pre&gt;


And there is one more thing about modular ports. In order to actually implement this, your bootstrapping environment should provide the ability to load several files. On PC this is provided by GRUB2. on CHRP you can read filesystem via OpenFirmware, and Sam's Parthenope relies on modified u-boot. If your bootstrap allows to load only a single file, then you stuck with monolithic kickstart. By the way...  u-boot allows not only to boot up a single uImage or zImage, it also allows to write client programs AFAIK. With this approach, you actually can write modular bootstrap for ARM AROS using unmodified u-boot.

Most used [http://www.compulab.co.il/workspace/mediawiki/index.php5/U-Boot_quick_reference uboot options] are fatls usb 0:1,

the reason behind INTB_KERNEL is to allow use of the standard Exec function AddIntServer() to add interrupt handlers for
hardware drivers etc. AmigaOS never used it for abstract hardware drivers. AmigaOS  routed  only  raw  hardware IRQs there. Their assignment was hardcoded. As well as number of them. Actually on AmigaOS every bus has its own interrupt subsystem. For example PCI bus. PCI interrupts on Amiga are routed to a single exec interrupt.  1:1 relationship between CPU  and hardware interrupts is present only on PC.

IMHO we miss things like AddInterrupt/RemInterrupt methods on our PCI subsystem's device class.  PCI bus class should map these methods to whatever is appropriate. This is how it is done on AmigaOS and friends. When these are implemented, raw kernel.resource API will be needed only for several PC-specific drivers with hardwired resources. Exec IRQs are real IRQs only on Amiga hardware. On other machines they can be emulated where appropriate (VBlank is a good example). kernel.resource is meant  to be different, its IRQs are hardware-agnostic, they are plain &quot;Hardware IRQ number X, whatever this means&quot;. They are low-level actually, and meaningful only in the context of a particular system.

Was that not the transition from irq.hidd to kernel.resource? No.  A long time ago there was another hacky bit named INTB_TIMERTICK. It was &quot;abstract timer interrupt&quot;, used by timer.device. It was the same as VBlank, but with larger frequency. I removed it, because kernel.resource API was a cleaner way to access this interrupt. Furthermore, there can be more than one timer in the system. Thinking about bringing back timer HIDD definitions again. hpet.resource is a bad idea.

Can someone please enlighten me a little on how the scheduler is meant to work?
 
Poseidon.library creates its &quot;Poseidon Event Task&quot; during RTF_COLDSTART -&gt; then calls Wait(), and ends up in limbo because wait disables interrupts (used for the scheduler heartbeat), and basically waits forever because the sigbit is never set, since krnSwitch doesn't switch the task unless TF_SWITCH is set, and no codepath run during this seems to set it?? TF_SWITCH does not disable/enable switching. This flag just enables to run user-supplied hook when the task is being switched away. It is completely safe to call Wait() in Disable()d state. Doing this actually temporarily breaks this state. IDNestCnt gets remembered in struct Task, then next task is selected, and its IDNestCnt is restored in sysbase (see kernel_scheduler.c). If there are no other tasks, then your cpu_Dispatch() should enable interrupts on the CPU and enter idle mode. See x86 implementation for good example.

You miss what happens next...
 1. KrnSwitch() saves context of your task, saves IDNestCnt (core_Switch() and cpu_Switch()), then drops into cpu_Dispatch().
 2. cpu_Dispatch() calls core_Dispatch. Then two cases are possible:
 2a. There is a READY task. It is picked up, its IDNestCnt is restored in SysBase, then cpu_Dispatch() needs to restore registers and exit. The next task is run.
 2b. There are no READY tasks. core_Dispatch() returns NULL. In this case your cpu_Dispatch() should enter idle loop. It should just enable interrupts on the CPU and put it on halt. This allows it to process hardware interrupts. Eventually some of your interrupt handlers wakes up your task and puts it into READY list.

My heartbeat interrupt has been slowed atm to help debugging - but it never actually gets a chance to fire because of the Wait() disabling interrupts. Perhaps you have forgotten to enable interrupts in your idle loop.

There is a change in the format of AROS executables. Until now we were using Elf RELocable files which are usually used as intermediate object files. We had them for various reasons, one of them was how AROS files were built in the past. That days we had no real aros cross compiler and the option to embed relocation data in unix executables (or in executable files in general) was rather new and not every linux/unix system had it. Therefore we have decided to use intermediate files. Although it was somehow working (and it is still working :-)), it has some drawbacks. Therefore decided to introduce real Elf EXEC types, in first turn implemented on ARM target with option to expand in future to all other AROS architectures.

The first patch was pretty easy and appeared to work somehow. It generated nice executables with embedded relocation info. Not only that, it also removed all global symbols adjusting relocation data to be relative to the beginning of the sections. That move reduced number of symbols in each executable significantly (depending on the file between 20 and 80% of all symbols could be removed). The only symbols that stayed in the file are local ones - due to the nature of the patch wasn't able to remove them since we have not seen them in the symbol hash table.

The patch didn't worked though. The files were relocated, AROS kernel loaded, but it crashed very early. What happened? Well, the nature of ARM relocations happened :)

Most of the relocation data on all machines is rather simple. Relocation can be absolute or pc-relative, sometimes the offset has to be bit shifted. On ARM v7 there is another one. There, when one wants to load an address of function/variable into register a combination of two instructions can be used: movw and movt. The first one loads immediate into lower 16 bits of a register while clearing upper 16 bits. The second one loads immediate into upper 16 bits without touching lower halfword. Loading of a pointer into a register looks like this:

        movw r0, #:lower16:label

        movt   r0, #:upper16:label

In this case there are two relocations - one for lower halfword and another for upper. If an overflow of lower 16 bits occurs during relocation process, the upper one should be updated as well. Unfortunately with current patch and with typical ARM executables there is not enough information to perform the calculations.

There are two options - the first one would be to give up and go back to &quot;fake&quot; executables, another one would be to change from REL to RELA relocation info. The latter contains an addend, extra data which can be used to perform all the relocation calculations I need.

Decided for the second option. The patch is already in the works. There is another function for the binutils' bfd backend to perform the final relocation. There can decide what to do with every reloc info, modify data and eventually strip some symbols. An advantage is - at this stage of the linking process have also full access to all local symbols so can change all relocations section relative and eventually strip all symbols from the files. 


 GPU 

VCore developed by Alphamosaic Ltd and now owned by Broadcom. Most of start.elf runs on the GPU.   Placing ALL the userland GPU code in the videocore.hidd isn't going to be a terribly big problem because the code they published is nothing more than a shim that sends data straight to the GPU to execute.

The good news about this is that we only need to write our HIDD using the OpenVG API.   The shim is relatively small codewise and lives in the ARM memory (the actual OpenVG code itself lives in the GPU RAM area and its loaded from start.elf).   That's also the bad news.  Our driver has to translate AROS video calls to OpenVG calls, for most tasks it should be easy, for some, not so much.  It's still probably less difficult and less work, than controlling the GPU directly.

The other good news is that anything done through OpenVG happens on the GPU, its truly accelerated.   It also has some nice font functions, meaning we can lead into an accelerated text mode later.

Basically, AROS resets or locks up when it tries to use AROS_ATOMIC_INC or DEC.  If I comment out the byte/word operations in the header files and use non-atomic operations, the code works as expected.
 
have read that the L1 cache needs to be enabled to use LDREX and co (which I also read is only meant to be used on multi processor systems with shared memory) - however I am certain this is correctly enabled.

If you are using LREX or STREX, you should have L1 cache enabled, at least on the ARM CPU I work with at work.

L1 cache is enabled by enabling the MMU *AND* setting the C and I bits in the CPU - the C bit is ignored, and the I bit only covers the 16 byte instruction pipeline if the MMU is not enabled.

Can you verify that your assembly is generating LDREX/STREX? From the behavior, it almost sounds like its generating the default Semaphore locked atomics.
 Impossible. There are no semaphore-locked atomics. There are Disable()/Enable()-based ones instead. And there's a special #define AROS_NO_ATOMIC_OPERATIONS in this case, which tweaks Disable()/Enable() implementations not to recurse forever.
 I have tested this on ARMv5 which does not have ldrex/strex, it works fine. On those ARMs there's no way to have real atomics. On other OSes (like Linux) this is done by introducing things like atomic_t, which appears to be a complex structure, holding the value together with accompanying spinlock (implemented using swp).

    #warning &quot;TODO: lookup optimal mmu table settings for raspi memory&quot;
        /* Set up an identity-mapping for all 4GB */
        for(x = 0; x &lt; 4096; x ++)
        {
            pagetable[x] = x&lt;&lt;20 | (0x40002|0x80000|0x010000|0x00C00|0x04);
        }

Shouldn't there be a second loop that sets the 'C' bit in the descriptor for the RAM pages?

Currently, you have TEX=0, C=0, B=1 for all pages (Shared Device).

You should have TEX=0, C=1, B=0 for RAM (Write-Through, Cached)

    So ..
     
     pagetable[x] = x&lt;&lt;20 | 2;

     
    should be enough?

No, for RAM you need to change the '| 0x40' to '| 0x80'

tell dosboot the correct defaults to use

Please don't do this. This bootconfig.c is a deprecated legacy thing. I wanted it to go away completely with time. Instead,  display  drivers  should auto-install themselves during own initialization phase. I. e. detect hardware=&gt;instantiate itself. This   should   make  things way simpler. With this approach you only need  to add the driver into KS image to get the device autobooted. No hardcoded stuff. 
Currently  VESA  and  VGA drivers do this, look there for examples. never rewrote ATI driver because i don't have any test system for it.

they defined a smaller AROSCPUContext than the ExceptionContext - yet reference it as ExceptionContext in other places, and since it hasn't allocated enough storage for ExceptionContext, are corrupting memory/the structure (since the elements that are there don't map 1 to 1 with the exception context).

AFAIK, AROS has been moving in a different direction to this in recent years. It is the job of graphics HIDDs to allocate bitmaps etc. so that they have the most suitable characteristics, including allocating them from GPU RAM where possible. The concept of chip RAM is only for legacy code, and most if not all non-68k platforms should have all system RAM
marked as chip.

BTW, is the video processing code you mention CPU code or GPU code?

Also, IIRC we have support for &quot;external memory allocators&quot;. Perhaps that's what we need for the allocation of GPU RAM through the mailbox.

All hosted and x86 native ports should use proper context formats.

trying to clarify if the vblank handler has to have run by this point to prevent this deadlock. Actually, no. Unless you have installed VBlank handler which should wake up at some point. Without VBlank there will be no quantum count. Consequently, there will be no forced preemption. But the rest will work, and multitasking will be cooperative (switch happens only when current task voluntarily gives up the CPU). Does it depend on the vblank having run before this point? and if yes what does that mean on systems where it might be able to run enough code (e.g. get to this point) before the vblank interrupt has triggered? What is it waiting for? It could wait for timer, in this case you need timer.device working. VBlank is currently needed for exec's quantum counter. In current native ports we have only a single timer, which is served by timer.device. VBlank is simulated by timer.device also. If your machine has two timers, then you can use one of them for VBlank, and another for timer.device, this will simplify things down. VBlank needs to be 50 Hz for historical reasons, many programs use it as cheap timer. I am periodically thinking about making some abstract mechanism to be able to change quantum source (and untie it from 50 Hz), but have no time to come up with something good. Additionally i started disliking timer.device hardcoded design when PC has got many timers (old 8253, APIC, HPET).
Currently i think there should be some low-level entity representing tick source. timer.device should just select the most appropriate source for its units.
The BCM2835 has 4 GPU based timer sources - 2 are used by the GPU, so im using Timer3 for our heartbeat and the remaining one will be free to the system. There is also the less capable ARM timer but that is dependent on the CPU frequency. Very good. You won't need any emulation. Set the heartbeat to 50 Hz and drive VBlank from it. Use other timer for MicroHZ.

Can you use the 'econsole.hook' I make for debugging the Sam460 via the serial port?
It provides a before-anything-else shell prompt on the serial port.  You can then do 'NewCLI' to test your graphics, or use any DOS command in shellcommands.resource.

You should just be able to add econsole.hook to your module list, and use 'econsole' in your bootargs.

So long as you have a working Exec/RawMayGetChar and Exec/RawPutChar, it should work.

Also make sure to add shell.resource and shellcommands.resource for this.

That should have done it.

If you set &quot;#define DEBUG 1&quot; in  arch/all-native/econsole/econsole.c, do you get any additional serial output?

have added it to the build and added econsole to the command line - and can see the bootloader picks up on the emergency bootconsole tag, but I still only get the insert bootable media display?

Im assuming it exposes a fake filesystem that tricks aros into booting?
The contents of which are: ECON:AROS.boot

Way to handle the scheduling code? The implementations I had been following were causing problems, due to cascading interrupts which I cant handle properly in the asm stubs just now (when they break disable etc.) - since it means detecting the interrupted codes cpu mode and getting the correct sp/lr for it, and that's just too tedious for arm.
 
To work around this ive added a system idle task which does nothing - and when the scheduling code has no task to run switches this in and lets it run, thereby allowing the interrupts etc to resume until something does need to happen.
 
Also, by adding accounting code to cpu_Switch() and cpu_Dispatch(), it should allow the system to log idle time correctly (as well as running tasks).
 
have thought of also adding an additional task that never runs, solely to record time spent in IRQ handlers, but I digress..

was under the impression that kernel.resource should *never* be used outside of exec.library. This is a wrong impression.
Michal started designing it because portable nature of AROS does not fit well into exec's API with all its assumptions. So, he started the new, hardware-agnostic kernel API from scratch. Yes, exec sits on top of it in places. But kernel always meant to be open thing. Otherwise it would not exist. 
it wasn't meant to be just used willy nilly by user code - but by lower system components (e.g. exec) so that they could be implemented in a more generic fashion, and the kernel resource itself hide the systems quirks.

Adding new things there perfectly keeps up with our decision to minimize AROS-specific intervention into APIs which can clash with MorphOS or Amiga OS4 extensions. We want at least source-level compatibility there. Binary compatibility on PPC would be extremely cool, but at the other hand we have no maintainer for this, as well as their ABIs splintering. 
It depends on what exactly is being implemented - there's no reason we should have everything crammed into kernel.resource if it doesn't need to be (i.e. if its better suited as a separate component/subsystem in its own right)

The _LE versions are for when you have endian swapping taking place.  If the graphics are the same endian as the CPU, no swapping should occur.  I ran into a similar terminology problem in SDL with a friend insisting that his Radeon 7000 on his PC was big-endian.  It is not, it just uses the same endianness for the graphics card and the CPU so no swapping was necessary.  They were both little-endian.
The _LE versions are because the PixFmts refer to the bitmap data being in big endian format in memory, for which the normal version would need to do endianness conversion before applying the shifts/masks. on this platform it is in _LE in memory also so we don't need the conversion hence using the _LE version of the call). would use _LE (if it's really little endian 16 bit mode).

 
What is the bare minimum needed to implement a framebuffer based gfx driver, with our software handling the rest?

Have tried with just a gfx class that only expose new/dispose/newbitmap - and having an onscreenbitmap used only for the framebuffer itself (with all other bitmaps being chunkybm, and the framebuffer's superclass also being chunkybm), but that alone isn't enough it seems?
You can use workbench/hidds/sm502/ as your example - it is as simple as I could make it.
So, AROS creates the framebuffer bitmap (verified this) -&gt; so surely it should be capable of then rendeing into it? I don't actually create the framebuffer &quot;bitmap object&quot; myself - only as a result of being asked to. The code I currently have on SVN seems to create the framebuffers bitmap object fine, but then crashes in intuitions DisplayDriver callback.  In particular it crashes performing the getattr on the system default pointer. don't expose MEMF_CHIP in an allocatable form so AllocSpriteData was failing (and other code later doesn't check if the values are valid == illegal memory accesses) 

So far have -:

vc_init: queries the gpus memory, and sets up a fake memory handler for it, then adds the bootmode driver and returns saying all is well
vc_gfxhidd:New: sets up some fake syncmodes to test with and creates the real gfx object.
vc_gfxhidd:NewBitmap: checks if its a framebuffer and uses the onbitmap class or uses the chunkybm class otherwise
vc_onbitmap:New; creates a chunkybm object and then pushes the real framebuffer address into it as the buffer,

vc4 had v8adds, v8subs, v8muld, v8min and v8max which operated on four 8bit uint values packed into a 32bit register. Multiplication was in the range 0.0 to 1.0 and addition/subtraction saturated. There were also a range unpacking/packing modes that allowed you to pack and unpack 8bit values into 32bit registers. 

RasPi has to speak to the &quot;operating system&quot; which runs on the GPU itself and request/free memory - it cant directly manage it itself, and so the managed functions were used to wrap these calls.

The Arm and GPU share memory space. The framebuffer is shared. The Arm can write a pixel and it will appear on the screen (through GPU hardware) without flushing/copying being required.

The GPU can composite multiple FB's in real time - so you have a number of surfaces defined which are rotated etc and  composited in real time to the output. Copying can map from the address space of the Arm to the flat space of the GPU which takes some code, but I don't think whole buffers are copied.

The DMA hardware can also access the whole memory space and can perform 2D fills and blits (no blending). This is documented in the peripheral spec posted. The DMA is just an Arm accessible peripheral and can be set up with low latency (e.g. microseconds).
must use a 0xc0000000-based bus address to access SDRAM, yet non-DMA access should go via a 0x0-based bus address. 
For 2D dma, set TDMODE, and the spec says &quot;interpret the TXFR_LEN register as YLENGTH number of transfers each of XLENGTH, and add the strides to the address after each transfer.&quot; so set STRIDE to pitch of the image, the width is XLENGTH and height is YLENGTH. You would fill by not setting the SRC_INC and point source to your fill data.

The DMA cannot see the ARM's L1 cache, so you would map the framebuffer with ioremap_nocache. Depending on where the source data comes from, it may need an L1 cache flush. The DMA can see the L2 cache. Use 0xC0000000 bus addresses when L2 is disabled and 0x40000000 bus addresses when L2 is enabled. (actually just call virt_to_bus and you'll get the right address out).

openGLES/openVG has high latency. Writing to framebuffer then reading it back is very inefficient (e.g. milliseconds). If you can drive it a unidirectional way, just streaming commands at then that is efficient. openVG is not implemented on top of openGLES - it uses the same hardware but as a first class interface

To improve the Gfx driver, we will need a DMA resource implemented so can use to perform DMA operations. The Gfx driver will need this to perform blits.


Actually MEMF_CHIP has to present, for historical reasons.
This has been never fully agreed upon, but in ports i wrote i exposed the whole memory as MEMF_CHIP. The idea behind this is that CHIP is originally the memory where graphics and sound data can be put. On non-Amiga platforms there are no restrictions on this, so the whole memory is CHIP.
Yes, many old software can misbehave with CHIP memory size larger than 2MB. But this actually applies only to m68k AROS which is going to run m68k binaries. In other cases it's quite logical to fix the program when porting.

As to original question: yes, it's enough to have a framebuffer bitmap (one with aoHidd_BitMap_FrameBuffer set to TRUE) and PutPixel routine. It framebuffer can be served by chunky bitmap class, then you can simply create chunky bitmap with your own buffer (see how VESA driver does this). Chunky PutPixel is already there.

struggling to determine what is the correct pixfmt to use for the 24/16/15 bit gfx modes on the RasPi.  AFAIK it uses RGB565, for 16bit but im unsure what shifts etc should go with it? suffice to say Im getting the wrong colors so far lol.

&lt;pre&gt;
redmask: 0x0000F800
greenmask: 0x000007E0
bluemask: 0x0000001F
alphamask: 0

redshift: 16
greenshift: 21
blueshift: 27
alphashift: 0
&lt;/pre&gt;

It should likely be vHidd_StdPixFmt_RGB16_LE

This stuff is a bit confusing.  The &quot;names&quot; of the stdpixfmts are based on the layout in memory,
ignoring endianess. So for example:

ARGB32: will be 0xAA 0xRR 0xGG 0xBB in memory on both big endian and little endian machines.

The shifts and masks OTOH are based on pixel access (ULONG in this case), so differ depending
on whether you run on big endian machine or little endian machine (that's why there's stdpixfmt_le.h and
stdpixfmt_be.h in rom/hidds/graphics/).

With the 16 bit pixel format it's even more confusing, as for example it's impossible on little endian machine
to describe RGB16 with shifts/masks alone. That's why there's vHidd_PixFmt_SwapPixelBytes_Flag.
(RGB16 == RRRRRGGG GGGBBBBB in memory, and for pixel (WORD) access on little endian machine it needs to
be accessed as GGGBBBBBRRRRRGGGG).

The shifts btw indicate how much to shift the component to the left (!) so that it is moved to the highest bit (31).

The aHidd_PixFmt_StdPixFmt you specify will be ignored most of the time, because when the pixelfmt is registered,
the gfx hidd checks if there's an identical pixfmt (shifts/masks/etc., but ignoring pixfmt-&gt;stdpixfmt) already in the system,
and if so, it uses the already existing one and does not create a new one.

In theory it would be better if gfx drivers could simply/only specify a StdPixFmt without all the shifts/masks stuff when the
gfx driver uses pixfmt which matches one of the stdpixfmts exactly. Another possibility would be for gfx drivers to use
HIDD_Gfx_GetPIxFmt(stdpixfmt_gfx_driver_wants_to_use) and then peek shifts/masks from it and fill out a pixfmt
tag list based on that.
15bit very blue/green: Try to pass same shifts/masks/etc. as in 16 bit pixfmt (maybe you think it's using 15 bit R5G5B5
(or swapped) but it's actually still using 16 bit R5G6B5 (or swapped).
 aHidd_PixFmt_StdPixFmt you pass is mostly ignored. It's the shift/masks/etc. that count.
But I would still pass the correct one (_LE) == whatever rom/hidds/graphics/stdpixfmts_??.h uses
in the entry where you have looked up shifts/masks/etc.

Use the shifts/masks/etc. from the entry in stdpixfmt_le.h (if you are running on little endian machine) or stdpixfmt_be.h (if you
are running on little endian machine) that matches the pixfmt that its meant to be.

0xAA,0xRR,0xGG,0xBB on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_BGRA32)

0xAA,0xRR,0xGG,0xBB on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_BGRA32)

it feels like AROS trashes the alpha component, otherwise it should be 8A8R8G8B.

read on the subject suggest its in 1x5r5g5b (x is ignored) to keep 16bit alignment .
 
Suggests to me that wrong shift/mask are being applied - however going by the 16bit versions it all looks correct to me so I am really confused as to what is happening.

The output image looks to have too much green/blue, and very weak red.


 Kickstart 

The  idea  is  to minimize amount of archirecture-specific modules to make the user's  life  easier.  So,  the kickstart was split into 'base' (which  does  not  contain anything machine-specific) and 'BSP' (Board Support Package) which contains all hardware-specific stuff. This  way,  for  example, distribution makers can save up space on CD and  make  CDs with multiple platform support. Different configuration would load the same base with different BSP's.

Next  there  was some part which is entirely missing on hosted. These are   filesystems.  Hosted  ports  do  not need them to boot up, so on hosted   they  are  left  out.  At  the  other  hand,  they  are  also architecture-agnostic.  So  i put them into 'FS' package (standing for 'filesystem').


 USB 

Poseidon  is  one  more  big part. I made it into separate package in order to allow users to omit it if they don't need it (for example, to run  on retro PCs without USB). Personally i have one. Again, Poseidon is  hardware-agnostic (well, there are USB drivers but HCIs are pretty standard).

AFAIK its HCI 1.0 compliant but not familiar enough with poseidons drivers, nor USB, to just hack away at the existing code.  Perhaps once i'm more familiar with the workings I can merge in the changes needed to get it operating but for now I will focus on getting it running.  Also our drivers have known issues so perhaps a fresh set of eyes might shed some light on what is going wrong.

Another interesting question is whether Poseidon can operate on device side. Is it flexible enough? How similar is being a USB host and USB device? think it will need a bit of work on Poseidon's side.  Until then I will force the driver into Host/Master mode in the init code, but leave open device etc to configure the chipset for either's use - and look at trying to add support for working in Device/Slave mode &amp; switching modes once it's up and running.

Actually USBROMStartup is some kind of kludge. Can there be any alternative? Could device drivers be self-installing, like our HIDDs? This would get rid of need to list them in USBRomStartup.

* Model A and B limited to 150 mA per port. 
* Model B+ and Pi 2 introduced configurable 600 mA to 1.2 A support over all ports - anything above that requires a powered USB hub.

Implementing the hardware driver that Poseidon uses to interact with the USB components.

Have code in place to (try) and initialise the USB chipset, and configure host/device mode operation (though AFAICT Poseidon doesn't support device mode). Started to get the &quot;virtual&quot; root hub written for the single USB port so that Poseidon should at least list it correctly in the GUI - and try to interact with it to find peripherals.


The BCM2835 uses a soft IP block from Synopsys’ DesignWare library (DWC), specifically the block is called dwc_usb_2_0_hs_otg_subsystem-ahb_se (“USB 2.0 Hi-Speed OTG Controller Subsystem w/AHB Interface SE”).

There is no public documentation for this, and pretty much zero chance of anyone getting hold of it even with NDA. However, there's a Linux driver written by Synopsys ([https://github.com/raspberrypi/linux dwc_usb]). Specifically directories [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_common_port] and [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_otg].

The Synopsys code is actually under a fairly permissive licence – it's not GPL, it's similar to BSD (’don't sue us if it breaks’ is pretty much the only clause). So this should not be a barrier to porting the code.

The code is really well written, with a nice partition between the work done by the driver (dwc_otg, which is fairly involved, given the host does more work than a conventional EHCI driver), and the interface to Linux (dwc_common_port).

Probably only need provision of relevant changes to dwc_common_port. Other things to consider....

* Provision of necessary headers to get it to compile
* Provision of necessary functions (main issues are wait queues, threads, work queues, tasklets, timers, spinlocks and mutexes (multithreading) )
* Interfacing between USB stack and the driver. dwc_otg/dwc_otg_hcd_linux.c looks like the place to start.

the Linux bits of the headers are only required for the dwc_common_port library. dwc_common_port includes a variety of crypto functions which are not used – it appears to also be used for ultrawideband (UWB) and wireless USB (WUSB) drivers where crypto will be an issue, but it isn't going to be for plain wired USB.

Every USB driver acts as an USB hub as well in order to let Poseidon control the state of USB ports. The code there was reading status of the only USB port in Raspberry's CPU but when changing the status it erroneously deleted some of the status bits, including the port enable one. It was so because those bits in the status register are of a type Read/WriteToClear. It means, if one does not want to change their value from 1 back to 0, one has to actually write the 0 value. Very practical thing e.g. in interrupt handlers, where one reads the interrupt status register to learn what was the interrupt reason, and writes it back to the same register in order to clear the interrupts. 

After fixing that code it turned out that the communication was still unsuccessful. Apparently the USB device was not understanding the host for some reason. That should not happen since the request sent was one of the standard ones implemented by virtually anything with an USB connector, assumed that Poseidon clears the data caches before forwarding the work to the USB drivers but that's the responsibility of the driver itself. 

The USB device responded and acknowledged the transmission! But why were all the request sent after address change failing with timeout? They should not. Once again, address set is supported just by anything. Tried to contact the device at address 0 once again and there it was, still responding properly. The enlightenment came. The bus address for DMA transmissions was, as it is in many bare metal USB implementations, just the pure memory address of the buffer as seen by the ARM cpu. Have &quot;prefixed&quot; it with the real location of uncached RAM and booted AROS once again. 


Trident saw this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

and this:

    Product     : Vendor: Vdr=0424/PID=EC00
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 255
    SubClass  : 0
    DevProto  : 1
    VendorID  : 1060
    ProductID : 60416
    DevVers   : 0200

and even this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

What are these things? The first one is USB hub built in the Raspberry. Thanks to this one the Pi machines (with exception of Pi0 and computing modules) have more than just one single USB port. The second one is the network chip in raspberry, the third one is my USB SD card reader which have just connected to see what happens. AROS tried, of course, to boot from it ;)

So, the first step towards working USB is done. The control transfers are working as you can see above. Next step is to implement bulk and interrupt transfers, having the basics in place. Finally some error handling will be added and USB for Pi will be as complete as the PC version. 

[http://www.raspyfi.com/raspberry-pi-usb-audio-fix/ Issue with USB Audio]


 Audio 

The Pi 4B is the only Pi that can output HD Audio as an HD Audio passthrough bitstream, and it does it over HDMI. It's possible to use the two HDMI output for separate HDMI video and HDMI audio outputs to allow UHD HDR video and HD Audio with non-UHD HDR compatible AVRs. 

The Pi3B+ and earlier will decode to PCM 5.1/7.1 and output over HDMI.  HDMI is the only interconnect that has a standard for carrying Dolby True HD, DTS HD MA etc. as a bitstream - you can't carry it as a bitstream on any other interface.

Pi3 and Pi4 audio jack output derived from 12bit pulse width modulation is relatively poor. For better, choose USB Audio or I2C versions. 

[https://github.com/raspberrypi/linux/tree/rpi-patches/sound/arm audio] and its [https://github.com/raspberrypi/firmware/issues/2 very high speed message passing interface type of thing VCHI] 

The Model B+ added an additional voltage regulator for the audio output and an additional output driver to drive low-resistance loads like headphones. However it is still using pulse-width modulation (PWM), which has a major impact on sound quality

the old Raspberry Pi used a linear voltage regulator to provide the 3.3V to many of the components on the board while the new one uses a switching regulator. Both can perform reasonably well. However switch mode power supplies often show higher noise figures

Analogue audio

Audio over HDMI rev 1.3 &amp; 1.4


 Ethernet 

10/100 BaseT Ethernet RJ45 socket


 GPIO 

GPIO shouldn't be too bad but bear in mind it is already accessed in places so they would need to allocate pins etc through it (e.g. sdcard to flicker the activity light, serial debug to output data on the GPIO pins)

Probably a resource rather than a device...

Started an i2c driver that will need to allocate GPIO pins. Feel free to work on it if you are interested ;p


 GPU graphics with 2D and 3D acceleration 

Sadly none yet for 32bit but for 64bit... 


 Miscellanous

hdmi issues

Setting the hdmi_force_hotplug=1 makes sure the Pi believes the monitor/TV is really there.

You might also need to set config_hdmi_boost=4 or even higher (up to 9) if your display needs a stronger signal.

If the display is a computer monitor or newer tv, use hdmi_group=1 (auto HDMI use) and if it is an older TV, try hdmi_group=2 (for DMT formats, i.e. for PC monitors) then you HAVE to &quot;set hdmi_drive = 2 to enable HDMI output as this forces HDMI mode rather than DVI mode

Do not set hdmi_safe=1 as that overrides many of the previous options.

Using a shorter or better quality HDMI cable might help. Make sure your Pi's power supply delivers 1 A and not 500 mA.
If you see a problem with the red colour - either absent, or interference - then try a boost

composite video

changing the RCA cable, then the composite port worked out of the box

Boot it as you are doing, without HDMI. If you now plug in the HDMI, do you get the image? In other words, does the Pi think HDMI is connected even when it isn't?

Rename all the files in the first partion of the card except bootcode.bin, start.elf and fixup.dat  What's the result?

Put back config.txt What's the result?

for PAL mode   sdtv_mode=2

dmi_ignore_hotplug Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached
hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected

&lt;pre&gt;
# NOOBS Auto-generated Settings:
#hdmi_force_hotplug=1
#config_hdmi_boost=4
#overscan_left=24
#overscan_right=24
#overscan_top=16
#overscan_bottom=16
#disable_overscan=0
start_x=1
gpu_mem=128
&lt;/pre&gt;

tvservice -c &quot;PAL 4:3&quot;

&lt;pre&gt;
/opt/vc/bin/tvservice -s   or tvservice -s 
state: HPD high|HDMI mode|HDCP off|composite off (0x12001a), 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m CEA
Group CEA has 1 modes:
(native) mode 16: 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m DMT
Group DMT has 0 modes:
&lt;/pre&gt;

sudo amixer cset numid=3 1

forces the audio to the headphone jack, even with the HDMI video output plugged in

config.txt

the hdmi_ignore_edid_audio=1 option sems relevant as it should tell ALSA that the only available audio is analog, no matter what the display says

There are several different ways that these 4 pole (ring) composite analog cables can be wired up, so some work great in some applications and can be a waste of time in others.

What is needed for the Raspberry Pi B+ and above, which like many camcorders needs the ring contact next to the base contact to be the ground.


The wiring for the 4 pole are:

TIP (LEFT AUDIO CHANNEL)

RING 1 (RIGHT AUDIO CHANNEL)

RING 2 (GROUND/EARTH)

RING 3 BASE/SLEEVE (VIDEO) YELLOW

Most Apple based Players and the Microsoft Zune (TM) are wired this way.

Most analogue camcorders are wired this way as well, where the ground in on Ring 2 will work with the Pi although you may need to swap your Video plug with the Right Audio plug.

Nearly all other MP3 players are not wired this way, the ground is on another ring ie the wrong one.


External devices

* Camera Module Omnivision ov5647 Sunny 5MP (NoIR version) V1.3 - NoIR at 850&amp;nbsp;nm, peak at 880&amp;nbsp;nm and trails off at 940&amp;nbsp;nm wavelengths 
* Camera V2 Sony IMX219 V2.1 8mpixel 8MP 8megapixel - 3280 x 2464 pixels - video at 1080p30, 720p60 and 640x480p90 - wider field of view, 62 vs 54 degrees horizontally - 
* Branded WIFI usb BCM43143 dongle

N.B.  dreaded error after changing cameras (stupidly without turning off the power first) and lasted through several power cycles.  It can be a bad 15-pin FFC ribbon cable, when swapped, camera(s) and the Pi itself are working OK. It can be an instance of a cold solder joint on the CSI connector on the pi board.  the camera can be detected (that's done via I2C) but may still not be able to receive image data (done via CSI-2) if something is broken. CSI-2 is uni-directional. Control is generally done via I2C. 
The CSI-2 receiver always writes to memory, not direct to the ISP. That's the way the Broadcom architecture works as it allows multipass processing easily. GPU memory is accessible from the ARM. Processing using the QPU graphics processors may be possible.  currently the only supported sensor is OV5647 and IMX219.  The linux drivers are all in the firmware blob, else you'd  be looking at at least a man-month of work in a fully fledged imaging lab to do a decent tuning of the camera modules' ISP parameters. 
Static electricity maybe an issue for the camera module and slightly less for the pi board.


== References ==


===Good sites to visit===

*[https://github.com/raspberrypi/firmware/tree/master/ Raspberry Pi Firmware build] 
*[https://www.raspberrypi.com/documentation/computers/software-sources.html Documentation] 
*[https://rpilocator.com/ RPiLocator] 


Linux only
*[https://github.com/raspberrypi/linux Raspberry Pi Linux Build] 
*[https://dietpi.com/ DietPi] 
*[http://www.tinycorelinux.net/ports.html piCore]
*[https://wiki.alpinelinux.org/wiki/Raspberry_Pi Alpine Linux] 
*[https://github.com/armbian/build Armbian] 


*[ FydeOS]
*[ TwisterOS based on ChromiumOS] 
*[https://note.com/jamesmondo/n/nc76e31402be8?hl=en BSD] 


*[https://www.raspberrypi.com/software/operating-systems/ PiOS Lite] and then [https://hstwb.firstrealize.com/ HST] 
*[ PiMiga for pi4 and pi5] 
*[ amibian for pi2 and pi3] 
*[ retropie pi1 and 2] 


Other alternative lighter smaller than Pi OS 
*[https://aros.sourceforge.io/nightly1.html Aros 64bit ARMV8 single core] 
*[https://www.riscosopen.org/wiki/documentation/show/Welcome%20to%20RISC%20OS%20Pi RiscOS on Pi3 and Pi4]
*[https://github.com/michalsc/Emu68 ARM based realtime JIT 68k for amiga computers] 
*[https://github.com/JJDSNT/bellatrix/releases/ Alternative use of Emu68 on Pi3b] 
*[https://github.com/stevereaver/uaos uaOS with Emu68k] 
*[https://github.com/aros-development-team/AROS/commit/f80a268607dfae81b2db94755ab4e4d31ccb72d6 m68kemu library reference] 
*[ HaikuOS]
*[https://github.com/raspberrypi/noobs NOOBS] os loader with successor [https://github.com/procount/pinn PINN] 
*[https://github.com/maxnet/berryboot berryboot]

*[https://github.com/brianwiddas/pi-baremetal Bare Metal Access on Pi 32bit] 


Testing procedure is put sd card in, connect board to board if necessary, plug in hdmi and then power nothing else is done especially CSI DSI etc 

[https://www.raspberrypi.com/documentation/computers/compute-module.html CM5] has the same 55mm x 40mm 2x100pin connectors form factor as the CM4 but [https://www.epdtonthenet.net/article/214508/Key-Considerations-When-Migrating-from-Raspberry-Pi-CM4-to-CM5.aspx some pins and other small things] have changed. Will need the [https://raspipcb.com/tech-blog/raspberry-pi-cm4-vs-cm5-difference-in-booting-from-sd-card/ right IO board to suit] 

*Green [ Raspberry Pi Compute Module 5 IO Board REV2 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1967]] - untested 
*Green [ RPi Compute Module 5 IO board REV1 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1751]] - untested 
*Black SupTronics Geekbord X1500 CM5 IO Carrier Board - untested
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*[https://sipeed.com/nanocluster Sipeed NanoCluster] - untested up to 7 CM5 
*Green BentoIO CMX0 - untested 
*Box EDATec ED-CLAWBOX - untested 
*Home Assistant Yellow - Kit with PoE with Raspberry Pi Compute Module 5 - untested 
*Blue [https://www.waveshare.com/wiki/CM5_PoE_BASE_A Waveshare CM5-PoE-BASE-A] - untested 
*Box  Waveshare [ CM5-POE-BOX-A] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-B Waveshare CM5-IO-BASE-B] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-A Waveshare CM5-IO-BASE-A] - untested 
*Blue Waveshare [https://www.waveshare.com/wiki/CM5-NANO-B CM5-NANO-B] - untested 


*[https://carboncomputers.us/products/pi-flux piFlux]
*[https://carboncomputers.us/products/ Zitaotech Hackberry] CM5 lite only - 
*Portable [https://www.waveshare.com/pocketterm35.htm Waveshare PocketTerm35] with Pi4B or Pi5 - untested 
*Box [https://www.clockworkpi.com/uconsole ClockworkPi uConsole][https://www.youtube.com/watch?v=EtI_bAahbR8 CM4 into an adapter or CM3 into so-dimm - Cyberdeck] - untested 


*Green RPi [https://datasheets.raspberrypi.com/cm4io/CM4IO-KiCAD.zip Compute Module 4] [https://datasheets.raspberrypi.com/cm4io/cm4io-datasheet.pdf IO board] V1.4 [https://datasheets.raspberrypi.com/cm4io/CM4IOUSB3-KiCAD.zip USB3] [https://datasheets.raspberrypi.com/cm4io/cm4iousb3-appnote.pdf CM4ISO] [https://datasheets.raspberrypi.com/cm4/cm4-datasheet.pdf Dual100pin] (2020) aka Development Platform Board - untested 
*Purple Pi Hut Cytron CM4 Maker Board - untested 
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*[ KubeSail PiBox mini 2] 
*Home Assistant Yellow with Raspberry Pi Compute Module 4 - untested 
*[ Turing Pi V2] - untested CM4 with 260-pin SO-DIMM socket adapters and/or nvidia jetson nanos - untested 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-C Waveshare CM4-IO-BASE-C] - untested but binary blobs Rev01 Rev02 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-B Waveshare CM4-IO-BASE-B] - untested but binary blobs 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-A Waveshare CM4-IO-BASE-A] - untested but binary blobs 
*Blue [https://www.waveshare.com/wiki/CM4-NANO-B Waveshare CM4-NANO] - untested but usb and audio turned off or rerouted 
*Black [ Seeed Studio with BigTreeTech BTT pad 7] - bin blobs? 


CM3 has a 200 pin sodimm ddr2 connector form factor but not electrically SC0028, SC0029 
*Blue [https://wiki.geekworm.com/CM_IO_Board Geekworm RPi Compute Module IO Board] [https://github.com/geekworm-com/cm-io-board CSI DSI] with CM3 in ddr2 slot underside - '''works''' if SW1 on but CM3+ '''does not''' 
*Green [https://cdn-shop.adafruit.com/product-files/3442/CMIO_schematic.pdf RPi V3 IO board CM3IO] and CM3 Lite - untested 
*Green [https://turingpi.com/ turingpi v1 cluster] - untested up to 7 cm3 7xlan9514 12V discontinued, 3 x Pi4 homelab maybe better 
*Blue [https://www.waveshare.com/wiki/Compute_Module_PoE_Board Waveshare Compute Module PoE Board] and CM3 lite (if not lite, write files to internal eMMC fat32) '''AVOID''' bin blobs 
*Blue [https://www.waveshare.com/compute-module-io-board-plus.htm Waveshare Compute Module IO Board Plus] [https://www.waveshare.com/wiki/Compute_Module_IO_Board_Plus wiki] [https://forums.raspberrypi.com/viewtopic.php?t=235695 pin settings] with CM3+ Lite - '''AVOID''' binary blob 


*[ Pi02w on Geekworm SupTronics X305 Raspberry Pi Zero IO Baseboard] - untested 
*[ Spotpear Pi Zero 2w to Pi3b format-ish] - untested 


*[ pi-top v4] box has 128x64 oled display, micro hdmi, 19Whr battery with pi4 and 15V PD 36W min needed 
*[ pi-top v3] three green pieces, heatsink covers most of the base tray, pi-top hub mk1 lhs and Pi1B Pi2b Pi3b rhs secured from below, black rounded strip with pi-top above keyboard, 13.3&quot; HD 1366 x 768 display, small touchpad, 
*[ pi-top Model 2.0] pi-top on bottom bezel of 14-inch green laptop, large trackpad, keyboard slide down to reveal main system hub on slide rails moved to the right, Raspberry Pi3b screws down, hub slides in, 18V 2.5A 45W charger brick, battery 11.1V 3500mAh 38.85Wh and storage PiTopOS 
*[ Pi-Top CEED Raspberry Pi Modular Educational Desktop with RPI3] monitor 
*[https://www.indiegogo.com/en/projects/jesselozano/pi-top-a-raspberry-pi-laptop-you-build-yourself Pi-Top v1] wedge laptop with RPi2 


&lt;pre&gt;
2008 Trustees collected for Foundation
2009 Pi Foundation charity status gained 
2010 
2011 First Raspberry prototypes 
2012 First boards go on sale at CPC and RS. The Model A and B 700 MHz Arm11 - February 29th BCM 2835
2012 First million sold - more than the 10,000 original planned and anticipated 
2013 First Alpha Experimental builds of AROS Native for the 32bit Pi 
2013 Pi Trading launched making grants available, providing in house educational resources and Pi Academy for teacher training 
2013 Over two million sold 
2014 Over three million sold 
2014 Pi 1 Model B+ introduced that moved composite video to audio jack and same half gig of memory 
2014 Pi Model A+ v1.1 no ethernet and 1 usb - a little smaller - 
2015 Over four million first gen pis sold  
2015 Pi Zero 1.2 BCM2835 first production revision released with no camera port 
2016 Pi0 1.3 released with camera csi connector 
2017 Pi Zero W v1.1 1GHz Pi0W, single-core 32bit CPU BCM2835 released with Cypress CYW43438 wireless 
2020 Raspberry Pi Pico SC0919 with RP2040 32-bit 2Core ARM Cortex-M0+ up to 133 MHz - 264KB of SRAM and 2MB of on-board QSPI Flash - 
2024 Raspberry Pi Pico 2 with RP2350 2Core 32bit Arm Cortex-M33 and 2core open-hardware [https://github.com/wren6991/hazard3 Hazard3 RISC-V] 

2015 Pi 2 Model B v1.1 BCM2836 900/600 MHz ARM Cortex-A7 Armv7 quad 32bit, 32bit VideoCore IV GPU - 1Gb RAM - 5V 2A micro usb - SMSC LAN9514 chip - 
2015 Over a million pi2s sold 


2015 Raspberry Pi 2 Model B version 1.2 Pi2bv1.2, aka Pi2B2 has armv8 BCM2837 underclocked to 900Mhz without wifi/bluetooth module 
2016 Pi 3 Model B - Broadcom BCM2837 SOC four 64bit ARMv8 Cortex-A53 1.2GHz 32bit 1080p VideoCore IV GPU - 1Gb DDR2 - bluetooth 4.1, Cypress CYW43438 wireless 802.11n - 4 x USB2.0 ports - 5.1V 2.5A - SMSC LAN9514 chip 
2016 PIs total over 10 million worldwide 
2017 Compute Module 3 CM3 with BCM2837B0 armv8 Quad 64-bit - small 67.6mm x 31mm board which fits DDR2 SODIMM connector but not electrically compatible which plugs into needed IO board - beware of the I2C protocol issue 
     1Gb LPDDR2 RAM - Lite or 4Gb Emmc storage 
2017 12 million pis sold in total 
2018 Pi 3 Model B+ - 4c A53 BCM2837B0 1.4Ghz - 1Gb, wireless 802.11ac, gigabit ethernet (300Mbit/s) and bluetooth 4.2 - power over ethernet - 4 x USB2.0 ports - Microchip LAN7515 chip 
2019 Over 15 million sold 
2019 Pi 3 Model A+ with BCM2837b0 Cortex-A53 64-bit SoC @ 1.4 GHz with 512Mb LPDDR2, 1 usb2, 1 hdmi, 1 micro usb 5V 2A - no ethernet - 
2019 Raspberry Pi Compute Module 3+ CM3+ - Broadcom BCM2837B0 1.2Ghz, Cortex-A53 (ARMv8) 64-bit SoC on DDR2 SODIMM mechanically compatible only factor - IO board required 
     1Gb DDR2 and 8GB, 16GB, 32GB or a Lite variant without eMMC 
2021 Pi zero 2 (w or no W) RP3A0 quad 1GHz Cortex-A53 64bit BCM2710A1 512mB SDRam 
2025 edaTEC CM0 ED-CM0NANA with additional dev board with quad 1Ghz A53 with 512Mb Raysan RAM, 2 USB2 and 10/100 ethernet - pico castellated edge
 

2019 Pi 4 Model B v1.1 RPI4B - BCM2711B0T quad 64bit A72 1.5GHz, 4K VideoCore VI, AC wifi, Bluetooth 5.0, GbE Broadcom BCM54213PE (PHY ID 0x600d84a2), 2 micro hdmi decode up to 4K, USB-C 5.1V 3A power, 2xVLI VL805 USB 3, 2xUSB 2.0, 2GB 9LDWW D9WHZ or 4GB 9FDWW D9WHV, 8GB 0AA47 D9ZCL ddr4 ram 
2020 Silent Pi 4 v1.2 upgrade with more USB-c psu support 
2020 PI400 BCM2711C0T 1.8GHz 4Gb DDR4 inside keyboard, 5.1V 5A 27W usb-c psu, 2 micro hdmi, external ide style 40pin gpio, no audio port - 
2020 Raspberry Pi Compute Module 4 BCM2711B0T on new 55mm x 40mm 2x100 pin form factor with extra breakout IO board 
     CM4101000 1Gb RAM Lite SOM 
     CM4102000 2GB RAM Lite 
     CM4104000 4GB RAM Lite 
     CM4004008-4GB-RAM 8GB-EMMC SOM System on Modules 
     CM4104032 4GB RAM 32GB emmc 
     CM4108000 8GB RAM Lite 
     CM4008016 8GB RAM 16Gb eMMc
2021 Raspberry Pi SC0763 Compute Module 4S CM4S with ddr2 sodimm pinouts but not electrically the same with suitable IO board extra cost - 
     CM4S01000 1GB RAM Lite
     CM4S01008 1GB RAM 8GB eMMC Flash
     CM4S02000 2GB RAM Lite
     CM4S04000 4GB RAM Lite
     CM4S04016 4GB RAM 16Gb KLMAG1JETD-B041 
     CM4S08000 8GB RAM Lite 
2021 Pi 4 v1.4 BCM2711B1 upgraded power regulator, to deal with 8gig of ram being more power hungry 
2021-48 Raspberry Pi 4 model B v1.5 2GB 


2023 Pi 5 v1.0 BCM2712 Quad A76 @2.4Ghz - VideoCore VII - no audio socket - dual 4k from mini hdmi - fan connector - 5.1V 5A psu 
2024 Pi 5 2GB DDR4 version uses BCM2712D0 
2024 Pi-500 with 8Gb LPDDR5 and membrane keyboard 
2024 Pi 5 v1.1 
2024 Raspberry Pi Compute Module 5 CM5 BCM2712 55mm x 40mm form factor with additional IO board 
     CM5004000 04GB RAM 0GB eMMC Lite
     CM5008000 08GB RAM 0GB eMMC Lite
     CM5016000 16GB RAM 0GB eMMC Lite
2025 Pi-500+ with 256GB NVMe storage, 16GB LPDDR4 RAM, and Gateron KS-33 Low Profile Blue mechanical keyboard switches 
2025 Pi5 1GB DDR4 announced 


2022 PiOS linux goes 64bit 
2024 Pi Trading IPO stockmarket stock exchange listing 


2026 April and May Aros 64bit fixed, added AHI audio, VC4 gfx started, usb functions added to rom  
2026 June and July Aros 64bit usb2otg started, dma.resource, sdio.resource, bwfm.device wifi added 
2026 Late July daily 64bit Pi3 LE little endian builds start 
2026 August Pi 4, 400, 5 and 500 DTBs added, expanding existing support and wifi for Pi4 and Pi5 
2026 August Pi5 HAT+ nvme and HDMI, AHI RPiI2S added, Pi4 HVS5 video scaler started, 
2026 
2027 


2028 Pi 6 
&lt;/pre&gt;


The vcgencmd can be used to inspect and dump the current system configuration. 
vcgencmd runs on top of VCHIQ as an RPC. The mailbox interface is an alternate but much simpler RPC. 
VCHIQ is a bridge (queue) between the CPU and the GPU so they can communicate with the firmware. 

Loads of [https://github.com/6by9/rpi3-gpiovirtbuf/blob/master/rpi3-gpiovirtbuf.c mailbox] which uses the GPIO control calls. [https://github.com/raspberrypi/firmware/wiki/Mailboxes may also be of interest] 

A fair number of vcgencmd examples (search for vc_vchi_gencmd_init). [https://www.raspberrypi.org/forums/viewtopic.php?t=229203#p1406112 sends the relevant vcgencmd commands] to update the scaling kernel, but the [https://github.com/raspberrypi/userland/blob/master/host_applications/linux/apps/gencmd/gencmd.c command] is just a text string. Parsing and execution of the instructions is performed by the VideoCore firmware. 

The Raspberry Pi runs two separate operating systems: Linux/Aros on the ARM, and a threedx RTOS called vcos running on the Videocore 4 VPU: vcos is commonly called &quot;the firmware&quot;. Vcos is tasked with performing certain system services, for example running the display and audio outputs. The VCHI driver provides an interface to allow drivers to talk to vcos. 


Doubtful, on any [https://www.web3d.org/ Web3d] [https://developer.mozilla.org/en-US/docs/Web/API/WebGL_API WebGL] or [https://github.com/immersive-web/webxr WebXR] [https://developer.mozilla.org/en-US/docs/Web/API/WebXR_Device_API Device API] [https://developer.mozilla.org/en-US/docs/Web/API/XRInputSource XRInputSource] support. Hopefully, never/limited support features like location, peer-to-peer, invasive web apps, unwarranted storage, payments, proprietary video streaming etc 

*spreadsheet [https://git.sheetjs.com/sheetjs/sheetjs sheetjs] [https://github.com/mleibman/SlickGrid SlickGrid] [https://github.com/6pac/SlickGrid SlickGrid] [https://github.com/jspreadsheet/ce jspreadsheet ce] [https://github.com/dream-num/Luckysheet Luckysheet] [https://github.com/ruilisi/fortune-sheet fortune-sheet] probably without xlsx support 
*presentations [https://github.com/impress/impress.js/ impress.js simplified] [https://github.com/bwlewis/slides slides] [https://zenomt.github.io/mdslides/ github markdown slides] [https://github.com/Patternslib/slides Patternslib slides markdown] probably without pptx support 
*ai office [https://github.com/dream-num/univer/ univer], 
*weather [https://github.com/Himanshu3412/Weather-Forecast Weather Forecast], [https://github.com/kaushalsahu07/weather weather needs API key], 


==Future==


[https://github.com/ARMSX2/ARMSX2 Arm pi of pcsx2] 


[https://tube.cadence.moe/ Cloudtube], [https://github.com/TeamPiped/documentation/blob/main/content/docs/public-instances/index.md TeamPiped], [], [], [], 

[https://hyperpipe.codeberg.page/ hyperpipe], [https://ytify.pp.ua/ ytify], [], [], 

[ ytdl], [https://github.com/golddominik893/liberatube liberatube]

[https://git.lolcat.ca/lolcat/4get 4get], [https://github.com/hnhx/librex librex], [], [], 


{{BookCat}}</text>
      <sha1>dsj76bann5p0pkjm4lpw37z5gr6svjd</sha1>
    </revision>
    <revision>
      <id>4676534</id>
      <parentid>4676529</parentid>
      <timestamp>2026-10-17T14:33:19Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4676534</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="106204" sha1="9px4g6wrk3uiy5ys4xxnt78zwxu3gj3" xml:space="preserve">{{ArosNav}}

[[#Native]]

[[#Hosted]]

[[#Build]]

[[#Hardware]]

[[#References]]

[[#Future]]


==Introduction==


[[File:Scalos00.png|thumb|Scalos on Aros Pi3b]]

Aros aims to cover Pi 3 to 5 512Mb+ RAM 


Options to boot from using a good power source to prevent the yellow lightning symbol. 
*With Pi3b+ the max you can get is 5.1V 2.5A with micro usb.
*With Pi4 5.1V 3A with usb-c 
*With Pi5 5.1V 5A, the amps went ever upwards, even to 5.1V 9A with usb-c 


* Pi500+ keyboard wedge - working but not much tested esp [https://github.com/aros-development-team/AROS/commit/48e9c8edcca4b5c1e1fe0b1123f2129f624af67b power button] 
* Pi500 wedge with up to date bootloader via PiOS - working but not much testing esp [https://github.com/aros-development-team/AROS/commit/48e9c8edcca4b5c1e1fe0b1123f2129f624af67b power button] 
* Pi 5  - Quad A76 64bit ARMv8 and RP1 &quot;southbridge&quot; with VideoCore 7 D0 (rev1.1) - untested 
* Pi 5  - Quad A76 64bit ARMv8 and RP1 &quot;southbridge&quot; with VideoCore 7 Pre-D0 C1 (Rev1.0) - untested 
* Pi400 RPI-400 keyboard wedge - resolution changing and audio from micro hdmi0 (near 40pin) and micro hdmi1 (near usb-c psu) - Fn F10 0x5e power on and off works or held down for over 7 seconds auto shutdown - keyboard ok - wifi and lan ethernet testing - 
* Pi 4  - Quad A72 64bit ARMv8 with VideoCore 6 
* Pi 3  - Quad A53 [https://www.raspberrypi.com/documentation/computers/processors.html 64 bit] ARMv8 with VideoCore 4 with '''fan''' to prevent overheating cpu 82C+ throttling 
* Pi02W - Quad A53 64bit - boots but [https://forums.raspberrypi.com/viewtopic.php?p=2387984#p2387984 usb not working but did in the past], 


* Pi 2 - Quad 32bit ARMv6 with VideoCore 4 - mostly not 64bit compatible 
* Pi Model B+ 32bit ARMv6 with VideoCore 4 - not 64bit compatible 
* Pi Model A and B 32bit ARMv6 with VideoCore 4 - not 64bit compatible 


===Native===

* 2013-03 Kalamatee starts work
* 2015-04 Work continues with mschulz on the kernel and Kalamatee (NicJA) on gpio and usb
* 2018 [https://www.patreon.com/posts/i-owe-you-some-20956961 mschulz resume adding BE big endian support], [https://www.patreon.com/michal_schulz/posts Big endian on Pi]  
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bsek latest commits for pi 3b, 4 and 5 64bit] 
* 2026 [https://github.com/aros-development-team/AROS/commits?author=metaneutrons latest commits for Pi5]
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bitplane latest commits for ARM]


====64bit====

'''Download''' A [https://archive.org/details/piAROS Pi Distribution (Distro) has started] and the contents copied to fat32 8GB+ microSD card (there will be drawers/folders - boot c Classes Demos Developer Devs Extras etc only showing). The SD can be plugged in to the Pi. And power on. [https://pi.amiga.icu/ Repository]

'''Not recommended''' but [https://aros.sourceforge.io/nightly1.html RaspberryPi 3, 3+, 4 and 5 64bit ArmV8 nightly builds] [https://sourceforge.net/projects/aros/files/ and alternative site and nightly2] which is a test version of '''very few''' apps with both raspi-aarch64-system and raspi-aarch64-contrib can be unbz2'd to a SD or SSD as appropriate. 

64bit build works well on a single core LE little endian. Multicore [https://github.com/aros-development-team/AROS/commit/1df0747c2bda3523a43029725a709b1f377d84ec may follow]. Any issues booting could be down to the SD card so please use another SD to see if it is resolved. Remember Aros Arm uses FAT32 and Aros can detect issues with this format very acutely (once fault found, FAT 0x0FFFFFF7 bad cluster so no files written after that, no repair). Please report your experiences in the [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2138&amp;pid=15057#post_15057 Aros forum thread], [https://forums.raspberrypi.com/viewforum.php?f=179 Raspberry Pi Aros Dev and User forums], [https://forums.raspberrypi.com/viewtopic.php?p=2387984#p2387984 previous Raspberry Pi forum thread]. Any bugs or issues can be [https://github.com/aros-development-team/AROS/issues described here to fix] 


*Pi500+   untested usb3 booting or nvme ssd 
*Pi500    untested usb3 booting 
*Pi5      untested usb3 booting 
*Pi400    boots with '''USB3''' port based sata3 ssd 
*Pi4      untested (may need eeprom update from PiOS or Pi SD Imager) 
*Pi 3 B+  is pre-configured for USB sata3 boot - untested 
*Pi 3 B   may need [https://www.youtube.com/watch?v=ubnwvxF3Klc PiOS to set OTP to boot from usb - do so at your own risk] - if OTP set to usb, boot works but slower than SD card 

Speed write wise (top faster) 
&lt;pre&gt;
*NVME Pi5 untested    &gt;1000MB/sec  or faster if matched correctly 
*Sata3 ssd              500MB/sec
*SD        V90           90MB/sec  4K maybe 8K 
*SD        V60           60MB/sec  1080p 
*SD     U3 V30           30MB/sec  720p 
*SD C10 U1 V10 A1 A2     10MB/sec  minimum should be used now 
*SD C06                   6MB/sec  
*SD C04                   4MB/sec 
&lt;/pre&gt;


As a homage to the past, Aros shows a reduced number of icons but this can be changed by left mouse click in the window and then right click down to Window -&gt; View -&gt; All files

Windows can be manipulated by the top (moving) and the bottom right corner (resizing) only. 

Zune like MUI gui interface, has a unique quirk in that after changing a setting in a text box, you may sometimes need to press Enter/Return before clicking OK, Save, etc 


Double left mouse click on most picture (Developer/Debug/Tests/Datatypes), audio and video files are supported, via datatypes, by the multiview application. 
Esc escape key usually closes open windows even the desktop 

In Prefs/Appearance some decorative theming elements need work. There is a few Mason icons in /Prefs/Presets/Icons/Mason/ and the ever present default Gorilla - Icon exchange in works 

For more intensive graphics applications, you may need to edit config.txt in the root folder and change 128M to 256M to adjust more memory to graphics usage 

If your cursor should '''appear''' to vanish, fear not it is still there. Please head to the top of the screen i.e. the title bar, hold down the left click mouse and drag the screen down a little and the cursor will appear again. Then you can drag the screen up again. 


Like most amiga like OSs the audio and networking need to be setup manually 

Audio AHI prefs - Mode settings tab - needs both Music unit and Unit 0 set to RPiHDMI:16 bit stereo++  or RPiPWM:16 bit stereo++ at 44100Hz. Press '''Save or Use''' button after each choice 


For wireless, please use the Wifi prefs and already selected device bwfm.device. Press Scan and double right click on the router and enter password. You may need to setup after every power off
*if asking for password again - press cancel and go to Network Prefs, Wireless Networks tab and highlight the router line and hit the remove button and press the cancel button. Retry with Wifi prefs again 
*...waiting for an address - Disconnect and try Connect 
Until, Connected to &lt;router&gt; - 192.168.x.x 


For lan ethernet port, please use Network prefs and the following hardware is 
*lan9514    Pi3b Pi2 not supported at the moment 
*lan7515    Pi3b+ type into Device  usblan78xx.device as net0:  remove other device(s) 
*bcmgenet   Pi4 Pi400 choose for Device bcmgenet.device 
*cdnsgem    Pi5 Pi500 Pi500+ RP1 i/o for cadencegem 
 (network prefs may forget random information when rebooted) 


Summary
&lt;pre&gt;
*3b    ethernet not supported, usb ethernet not working but wifi prefs setup works 
*3b+   wifi working and ethernet works 
*4     untested 
*400   wifi and ethernet untested 
*5     wifi and ethernet untested
*500   wifi and ethernet untested
*500+  wifi works 
&lt;/pre&gt;


Type in 'aarch64' in the [https://archives.arosworld.org/index.php?function=search&amp;tool=simple search box] and you will see available software packages / apps. apkg can be used to inspect and install applications. 

[http://archives.arosworld.org/index.php?function=browse&amp;cat=network/browser amelinium web browser (JS 1.6 ES9 ECMASCript 2018)] is available with an [https://eab.abime.net/showthread.php?t=122494&amp;page=80 eab thread] reminiscent of [https://github.com/zapek/Voyager Voyager] and to a lesser extent [https://github.com/amigazen/aweb3/ Aweb JavaScript 1.5 (ECMAScript 3)] as css and javascript websites can be slow to load or resolve (no JIT) and nothing from facebook, reddit etc. 

Press Cancel at screenmode selector or -wb argument to get windowed version. You could use the Shift + Del shortcut or mouse wheel should work to delete all text at once. Html5test gives 189 (1.29), 300 (1.31), 301 (1.39) out of 555, some bigger Amiga like browsers are around 370+ but it does less better. 

You may have to delete the cache (Menu -&gt; Page -&gt; Delete cache) to fully retest big Amelinium updates or free up space. 
Be aware [https://pianetaamiga.it/en/reportage-pianeta-amiga-2026/ some site pages] can use up hundreds of MBs of cache very quickly 

 DNS lookup failed...  close browser and reboot and setup wifi again - repeat until it works again 

 youtube video and audio - js button for javascript must be on/shaded -  Settings -&gt; Soundoutput - AHI 
Any restriction to lower resolutions is due to [https://docs.invidious.io/faq/#q-where-are-the-360p480p1080p-quality-options bandwidth]. Either CPU/GPU, internet speed and/or video quality. Pi3 can expect 480p (wifi) to 720p (ethernet). Pi4 expect (wifi)  (ethernet). 

Telegram https://t.me/s/channel_name for public messages from vamped_amiga chatamigagames demoscenecracktros 

*art local js apps like dpaint.js 


There is normally no Bluetooth support for most amiga like OSs but Aros has one [https://github.com/aros-development-team/AROS/commit/6942cbfbf66426d21963a7fcd8aba6aff611a9e0 work in progress] [https://github.com/RPi-Distro/bluez-firmware/tree/pios/trixie/debian/firmware/broadcom firmware] 

*Bluetooth 4.1 BCM43430A1.hcd Pi3B, Pi3A, Zero 2W 
*Bluetooth 4.2 BCM4345C0.hcd  Pi3B+, Pi4 
*Bluetooth 5.0 BCM4345C5.hcd  Pi4B rev, CM4 and maybe Pi5 and CM5 

&lt;pre&gt;
*bthid    keyboard mouse support 
*btserial serial 
*btpan    short range wireless connecting devices 
&lt;/pre&gt;


Only the Pi5 has a RTC real time clock, the other Pis will need to use ntp services [https://github.com/aros-development-team/AROS/commit/29cd4116330dc7f692d90757eacc59fb3f31ae70 sntp] with time.cloudflare.com pool.ntp.org or Cloudflare 162.159.200.1, 162.159.200.123, 2606:4700:f1::1, 2606:4700:f1::123 or [https://github.com/bohunamiga/PiNTP PiNTP -s goodtime.ijs.si or ntp1.ptb.de] to get the date and time from the internet. Can use date in a shell e.g.  date 24-Dec-2026 23:59:59  but this will need to be done again after every reset/power off. Maybe [https://github.com/aros-development-team/AROS/commit/28674a157bc56175aa668e7b62dca6fa740578dc ds3231 rtc with dtoverlay=i2c-rtc,ds3231 in config.txt] 


It helps to have all usb devices already plugged in before power on to detect at the moment. Even then some usb devices will freeze the mouse cursor and the only resolution is to remove the offending usb device and reinsert. Sometimes, the reinsert leads to the mouse cursor vanishing, it is still there and responds to left mouse clicks, top of the screen and pull down the screen. 

USB classes support from Prefs/Trident is still work in process 
*usbaudio working on usb3 port (blue) on pi4, 400 but not working (no rt isochronous) on usb2otg (white or black) for pi3b, zero 2w 
*[https://aminet.net/package/mus/midi/camd camdusbmidi] detects midi devices without a preferences file (Prefs/Env-Archive/sys/midi.prefs) as [https://www.youtube.com/watch?v=RBxHkwy4Nrw auto setup now] possibly with [https://github.com/metaneutrons/mt32-pi metaneutrons mt32-pi] [https://github.com/rtzor/mt32-pi mt32-pi fork] [https://github.com/ahmadexp/mt32-pi fork] [https://github.com/gmcn42/mt32-pi-control control of] [https://github.com/dwhinham/mt32-pi mt32-pi pi3+]. Alternative of [https://homspace.nl/samplerbox/ SamplerBox]. 

Will need developer clang gcc tools to look at 64bit ports of [https://archives.arosworld.org/?function=showfile&amp;file=driver/audio/usbmidi.i386-aros.lha usbmidi], [https://aminet.net/package/mus/midi/CAMD_Toolkit CAMD_Toolkit], [https://aminet.net/package/mus/midi/camdtools camdtools], [https://github.com/cnvogelg/amiditools amiditools], [https://github.com/timoinutilis/midi-sequencer-amigaos horny src], [https://aminet.net/package/mus/midi/horny-base horny-base], [http://bnp.hansfaust.de/index.html BnP], [https://arosarchives.os4depot.net/?function=showfile&amp;file=audio/misc/timidity.lha timidity], 


Regarding 680x0 emulation, there are several options (not implemented yet) that could be considered 
*[https://github.com/aros-development-team/AROS/blob/6722a0ae9e03fe5d26e32703360bd2059e0864cc/rom/m68kemu/README.md?plain=1#L424 m68kemu.library] for some Amiga productivity where the cpu is emulated and the system calls are redirected to Aros ones
*[https://github.com/BlitterStudio/amiberry amiberry] (winuae) for everything else like games 
*[https://github.com/jonx/AROS/tree/aarch64-darwin-graft/arch/all-darwin/libs/emu68k emu68k] 
*[https://scriptedamigaemulator.net/ Scripted Amiga] with [https://github.com/naTmeg/ScriptedAmigaEmulator ScriptedAmigaEmulator] or older [https://github.com/gbraad-amiga/ScriptedAmigaEmulator2 ScriptedAmigaEmulator2] 
 Hopefully getting Pi3 up to 25Mhz 68040 (non JIT) and 50Mhz 68040 (JIT) 
 Pi4 maybe getting up to 50Mhz 68040 (no JIT) and 100Mhz 68040 (JIT) 


[https://pinout.xyz/ GPIO 40 pins] [https://learn.sparkfun.com/tutorials/raspberry-gpio/gpio-pinout pinout] 

Some exceptions:

*Physical pins 27, 28 (GPIO0, 1) are an internal I2C bus and should not be used
*The other I2C on pins 3, 5 (GPIO 2, 3) can be used generally, but be aware they have permanent pull-up resistors to 3.3V
*For MIDI use USB but there are dedicated UART pins 8, 10 (GPIO 14, 15).

With a HAT it's more awkward -- you need to know which pins are used by the HAT and avoid them. Hopefully this will be documented.

Remember all GPIOs are 3.3V (not 5V tolerant), floating/noisy inputs can cause odd behavior, and that shorting the power supplies can cause instant death of the Pi.

In the shell (Cntrl + C to end) 

 GPIO PIN/A/N,SET/N,GET/S,MODE/K,PULL/K

Controls and queries hardware GPIO pins via gpio.resource which is stored in the rom or Devs/ '''please test''' 

*PIN   -- (Required) Target GPIO pin number (e.g. 12).
*SET   -- Set pin output value to 0 (LOW) or 1 (HIGH).
*GET   -- Read and print current digital input level (0 or 1).
*MODE  -- Configure pin mode: IN (Input), OUT (Output), ALT (Alternate).
*PULL  -- Configure pull resistor: NONE, UP, DOWN.

EXAMPLES
&lt;pre&gt;
GPIO 12 MODE OUT
GPIO 12 SET 1
GPIO 12 GET
GPIO 13 PULL UP
&lt;/pre&gt;


[https://gpiozero.readthedocs.io/en/stable/installing.html Current] [https://gpiozero.readthedocs.io/en/v1.2.0/api_boards.html old support for gpiozero is unknown at present] [https://energenie4u.co.uk/res/pdfs/ENER314%20UM.pdf and associated 433MHz equipment] [ USA X10 security and lights via USB] [ OpenHab with Shelly Smart Plug connected over Wi-Fi, controlled by MQTT or HTTP] 


Printing only with Postscript but [https://github.com/bohunamiga/MintPRINT one] of [https://github.com/boingball/MintPRINT two] [https://github.com/Andiweli/AmiAirPrint/tree/main AirPrint] IPP has been attempted with [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2061&amp;pid=13954#post_13954 discussion] 


Youtube 

[], [], [https://www.youtube.com/watch?v=X4fmWAIv7FE Aros native on Pi3b], 

[], [], [https://www.youtube.com/watch?v=TSxlYb1eQWU Installed on Pi3b+], 

[], [], [https://www.youtube.com/watch?v=NFF1H3jCoz8 testing Aros native on Pi400], 

[], [], [https://www.youtube.com/watch?v=nIVx7mh1E1Q&amp;pp=ygUHYXJvcyBwadIHCQkTDAGHKiGM7w%3D%3D Aros on Thumb 2 based 32bit-ish ARM STM32H743 board], 


[https://www.youtube.com/watch?v=zQM4CD64xDE&amp;t=612s&amp;pp=ugUEEgJlbg%3D%3D Performance under Linux] but on Aros... 

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot; |Pi
! width=&quot;10%&quot; |Single Core 2D
! width=&quot;10%&quot; |Single Core 3D
! width=&quot;10%&quot; |Single Core 3D
! width=&quot;10%&quot; |SMP 2D
! width=&quot;10%&quot; |SMP 3D
! width=&quot;10%&quot; |SMP 3D 
! width=&quot;35%&quot; |Comments
|-
| &lt;!--Pi--&gt;Pi3 
| &lt;!--Single Core 2D--&gt;
| &lt;!--Single Core 3D--&gt;
| &lt;!--Single Core 3D--&gt;
| &lt;!--SMP 2D--&gt;
| &lt;!--SMP 3D--&gt;
| &lt;!--SMP 3D--&gt;
| &lt;!--Comments--&gt;
|-
|}


==== 32bit ====

For the Pi1 Pi2 Pi2B the status of AROS native ARMv6 for 32bit RasPi was OK. System booting, USB working (although with some issues but plans to fix them). 32bit native [http://www.aros.org/nightly1.html ARMv6 32bit nightlys] raspi-armhf-system raspi-armhf-contrib unbz2'd to fat32 microSD 


===Hosted===


AArch64 CPU backend for AROS, a Cocoa/Metal display, clipboard / host-volume / CoreAudio / BSD-sockets bridges, GPU 2D via gpufx.library, a 68k→AArch64 JIT (run68k), and a full Rust std port. On [https://www.jkn.me/blog/macaros-aros-on-apple-silicon/ latest Apple Silicon] [https://github.com/jonx/Macaros early buggy alpha version of hosted Aros .dmg on MacOS12+]. Please use [https://github.com/jonx/Macaros/issues MACAros github] for issues, features etc and possibly [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2030&amp;pid=13910#post_13910 here] 


[http://www.aros.org/snapshots1.html old linux and android hosted 32bit] 


==== Hosted ====

=====64bit=====

[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80&amp;pid=13667#post_13667 Ubuntu Linux PC hosted Pi compiler build] 

[https://github.com/BlitterStudio/aros-compiler-docker Docker based cross compiler for various Aros systems], 

[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80 From the Aros Raspberry pi 3 64bit thread] 
Instructions on building 64-bit Raspberry Pi AROS and cross-compiler from sources.

You will need:
- Ubuntu 24.04 or 26.04
- qemu-system-aarch64 installed
- Internet connection
- rpi-scripts.tar.gz downloaded (https://axrt.org/download/aros/rpi/rpi-scripts.tar.gz)

1) Install prerequisites:

sudo apt install git gcc g++ make gawk bison flex bzip2 netpbm autoconf automake libc6-dev liblzo2-dev libpng-dev gcc-multilib byacc python3-mako cmake yasm curl nasm

2) Clone sources

cd &lt;project-directory&gt;
git clone https://github.com/aros-development-team/AROS.git --recurse-submodules

3) Extract rpi-scripts.tar.gz. Copy all files into your project directory so that you have:

AROS (the directory with cloned sources)
fix-dotdot.py
rebuild.sh
recreate-sdcard.sh
run-qemu.sh
update-sdcard.sh

4) Run ./rebuild.sh. Select option 1) toolchain-core-aarch64

This will execute process of building a cross-compiler. During this process packages will be downloaded from Internet. This process can take up to 2 hours. If there are some missing dependencies, install them with 'sudo apt install' and restart this step.

5) Run ./rebuild.sh again. Select option 2) core-raspi-aarch64

This will build system files for 64-bit Raspberry Pi AROS. This process can take around an hour.

6) Run ./recreate-sdcard.sh

This will create an sdcard.img file with contents of previous step.

7) Run ./run-qemu.sh

This will start QEMU with SD card image and ROM images. It will boot into AROS.


=====32bit=====

Ubuntu VM approach to compiling [http://lallafa.de/blog/2013/06/building-aros-hosted-for-raspbian/ Linux hosted AROS June 04, 2013]

 ../AROS/configure --target=linux-armhf  --enable-includes=/usr/arm-linux-gnueabihf/include --x-includes=/usr/arm-linux-gnueabihf/include --x-libraries=/usr/arm-linux-gnueabihf/lib

arm-elf- is symbol-linked to arm-linux-gnueabi- (arm-linux-gnueabi- is more correct in this case, because it's going to be compiling the ARM AROSBootstrap for ARM Linux)

*armel - many of the &quot;android&quot; machines require since the entire OS is made for soft float VFP. 
*armfp - Efika MX target, Raspberry PI, EfikaMX, Pandora and virtually everything (VFP)

Keep in mind it's possible to start hardfp AROS hosted on softfp system, though, as long as no calls between AROS and host require floating point parameters. NOTE: hardfloat objects *cannot* be linked with softfloat objects - they have a different ABI.

Just keep in mind the arm nightly build machine is quite complex beast. It needs the x86_64 host compiler to compile AROS tools. The arm version is built every night using gcc-4.6.2 crosscompiler (built together with AROS) and successfully builds armel and armhf linux hosted targets.

*needs an AROS code compiler for ARM target 
*as well as unix compiler for ARM linux host (would be best to have both softfp and armhf, we have softfp only now) with full set of libraries and includes.

with—disable-crosstools  $AROS_CC  is always a wrapper around $KERNEL_CC  ?  If  so,  this  is  wrong for some ports. This can break Darwin, Windows and Android port. 
Yes,  Android  port  will  build.  And  even  work. But it's not good because  the  port  will  not  be ABI-compatible with other ARM ports. Android's ABI is different from GNUEABI. For example:

&lt;pre&gt;
enum test {foo, bar};
enum test testvar;
&lt;/pre&gt;

sizeof(testvar)  will  be  equal  to sizeof(int) in GNUEABI (Linux and AROS)  and  sizeof(short)  on  Android. This affects linking objects from static linklibs, for example.

Previously everything worked because $AROS_CC was a wrapper on top of $HOST_CC. And a real crosscompiler was used on non-ELF hosts.

Android is the same. $KERNEL_CC is incompatible with AROS.

compiler=kernel  is  appropriate _ONLY FOR CODE WHICH RUNS ON HOST OS_ (or  barebone  hardware,  if  we  talk  about  native).  This includes bootstraps,  their  linklibs, and host-side dynamic libraries (Windows makes extensive use of them because of architectural considerations.

No single AROS object should be compiled with this setting. $KERNEL_CC is really compatible with AROS *ONLY IN LINUX-HOSTED* and no more. On other systems (Darwin, Windows,  Android) this is not true any more, and compiler=kernel is never going to work.

If  you  want  to  compile your AROS module against host OS includes, append  the  following  to  USER_INCLUDES  (or  USER_CFLAGS,  this  is effectively the same):

 -isystem $(GENINCDIR) $(KERNEL_INCLUDES)

$(KERNEL_INCLUDES) expands to:

 -isystem  &lt;your_os_includes&gt;  -isystem  &lt;host_OS_gcc_private_includes&gt;
 -nostdinc

This makes AROS compiler adhering to host OS APIs.

If you want some preprocessor symbols based on what your host OS actually is, add something like -DHOST_OS_$(AROS_HOST_ARCH).

Why is there $(GENINCDIR) at all? Because host OS has its own libc includes, which would conflict with AROS ones. And the host OS libc is not binary-compatible with AROS one.

Why doesn't Windows-hosted port use $(KERNEL_INCLUDES) ? Because WinAPI includes conflict with AROS ones in fundamental typedefs, like WORD, BYTE and BOOL. It's almost impossible to deal with this in any other way than rewriting WinAPI definitions using AROS types.

Building under centos 6.3 (i386) currently, and AROS creates the toolchain itself. haven't yet committed the necessary changes but &quot;./configure --target=raspi-armhf&quot; is enough to start, then &quot;make arosboot-raspi&quot; will generate arosraspi.img (containing the bootstrap, kernel.resource, and exec.library) as well as arosraspi.rom (containing all the other essentials components such as dos, graphics etc).  It will also copy over a config.txt file to make the raspi bootstrap code load the correct kernel, and a cmdline.txt that enables exec debug output.

*armel = typically Debian 6, Ubuntu Maverick, Android, 
*armhf = typically Debian 7, Debian 8, Ubuntu Precise,

Cross-compiling Ubuntu ARM softfp 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armel' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armel] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armel.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabi libx11-dev:armel libsdl-dev:armel
&lt;/pre&gt;

&lt;pre&gt;
 ./configure --target=linux-arm --x-includes=/usr/include \
             --enable-includes=/usr/arm-linux-gnueabi/include
&lt;/pre&gt;

Cross-compiling Ubuntu ARM hard-float 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armhf' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armhf] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armhf.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabihf libx11-dev:armhf libsdl-dev:armhf
&lt;/pre&gt;

&lt;pre&gt;
    ./configure --target=linux-armhf --x-includes=/usr/include \
                --enable-includes=/usr/arm-linux-gnueabihf/include
&lt;/pre&gt;

Now, the AROS build is configured properly and all you need to do is:

 make


==Build==

===64bit===

[https://github.com/aros-development-team/AROS/blob/7016ce28bfdb754182edb16011c98faaf5413c29/arch/aarch64-raspi/boot/mmakefile.src#L180 boot makefile] 


===32bit===


# download/checkout the source someplace, e.g. /build/AROS-Src/
# make a directory to store external sources AROS downloads, e.g. /build/Ports
# make a build directory, e.g. /build/aros-raspi-armhf
# cd into the build dir, configure, and then run make -:

&lt;pre&gt;
&gt;cd /build/aros-raspi-armhf
&gt;/build/AROS-Src/configure --target=raspberrypi-armhf --with-serial-debug --enable-ccache --with-portssources=/build/Ports
&gt;make
&gt;make arosboot-raspi
&lt;/pre&gt;

then copy the files from /build/aros-raspi-armhf/bin/raspi-armhf/AROS/ onto an sdcard, and download/copy the Raspi firmware files onto it.

You should then be able to boot the sdcard on your RasPi.

The current W.I.P tree to svn. it can be built as follows ..
&lt;pre&gt;
./configure --target=raspi-armhf
make arosboot-raspi
&lt;/pre&gt;

That will generate arosraspi.img, arosraspi.rom and config.txt in bin/raspi-arm/AROS - so either copy just those files to a fat formatted SD card (with the firmware files on), or copy the whole contents of the AROS folder.

NB - if you have a Linux/other install, backup the existing config.txt first

arosraspi.img contains the bootstrap (which has very basic mailbox code, framebuffer/gpio init, and console &quot;emulation&quot; via code pinched from our libbootconsole), kernel.resource, and exec.library

arosraspi.rom contains all the other components needed to boot AROS.

The config.txt file will tell the RasPI bootstrap to load the arosraspi kernel and ramdisk (rom).

the bootstrap has minimal mailbox code, planning on adding either a resource or library that driver/app code will use to access it (likewise for GPIO)


Help building AROS hosted on Linux ARM

Was looking a way to use more my Handheld ARM based called Pyra (Dragonbox Pyra) an ARM (Omap5 cpu with 4GB ram) linux based machine (Debian Buster v10 with kernel 5.6.19 adapted) and have a try to compile the latest Aros sources by Deadwood directly on this device.
Compilation stops after build libpopupmenu.a and trying to build libatomic have this error:

&lt;pre&gt;
    Configuring build in bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic
    configure: WARNING: unrecognized options: --disable-nls, --without-x
    checking for --enable-version-specific-runtime-libs... no
    checking for --enable-generated-files-in-srcdir... no
    checking build system type... arm-unknown-linux-gnu
    checking host system type... arm-unknown-aros
    checking target system type... arm-unknown-aros
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for arm-aros-strip... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-strip
    checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
    checking for gawk... no
    checking for mawk... mawk
    checking whether make sets $(MAKE)... yes
    checking whether make supports nested variables... yes
    checking for arm-aros-gcc... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-gcc
    checking whether the C compiler works... no
    configure: error: in /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic':
    configure: error: C compiler cannot create executables
    See config.log' for more details
    make[2]: *** [mmakefile:4489: /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic/.configured] Error 77
    [MMAKE] make --no-print-directory TOP=/media/farox/pyra2/arosbuilds/toolchain-core-armhf-build SRCDIR=/media/farox/pyra2/arosbuilds/AROS CURDIR=tools/crosstools/gnu TARGET=tools-crosstools-gcc-libatomic-configure -s --file=mmakefile tools-crosstools-gcc-libatomic-configure failed: 512
    [MMAKE] Error: Error while running make in tools/crosstools/gnu: No such file or directory
    make[1]: *** [Makefile:361: linklibs-libatomic] Error 10
    make: *** [Makefile:183: crosstools] Error 2
&lt;/pre&gt;


looking at config.log on arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic

found that arosbuilds/toolchain-core-armhf/arm-aros-ld: cannot find -laeabi
so do make linklibs-aeabi-arm-quick
and the missing lib was built.

now the next stop is at
fatal error: bits/libc-header-start.h: No such file or directory
and
fatal error: sys/cdefs.h: No such file or directory
in many places so after checking that have this missing include files i have noted that my include path is a bit different, standard searching path is /usr/arm-linux-gnueabihf but in my system is /usr/include/arm-linux-gnueabihf
so if i add my path to some mmakefiles compilation goes on....but is a better way to add this path to avoid every mmakefiles to be changed?

fixed with adding
-I/usr/include/arm-linux-gnueabihf
to where is missing on mmakefiles like
USER_INCLUDES := -isystem $(GENINCDIR) -I/usr/include/arm-linux-gnueabihf $(KERNEL_INCLUDES)

P.s. I have changed many mmakefiles and have at least compiled (after many hours) the toolchain doing make every time in arosbuilds/toolchain-core-armhf-build (also have to disable making tests under cplusplus but don't remember the directory ...) but ask an help to have an automated way to correctly build without modify mmakefiles.


Last time built armhf target was around 2 years ago. At that point built is via cross-compilation from linux (ubuntu 22.04) using linux armhf crosscompiler (this can explain the path differences you are experiencing) as well as using AROS gcc cross-compiler in version 6.5.0 (build with option 21) in rebuild.sh). Since then AROS GCC has been updated to 10.5.0 and don't believe anyone tried to build the armhf target again.

My suggestion would be to downgrade GCC to 6.5.0 (via editing AROS/config/gcc_def file) and try to first build using cross-compilation from x86_64 linux. Once that works, you will have a &quot;template&quot; to compare to native compilation under arm linux.


Thanks for your suggestion...but think the toolchain with GCC 10.5.0 is compilable if i found a way to pass the path of my system to the script that build (option 21 on rebuild).
The other only changes are (but don't know where to modify...) is to add the build of libaeabi and disable the building of some tests under cplusplus that use exceptions and is not supported under ARM. try to crosscompile with my Linux amd64 PC.

For paths look into core-linux-armhf/bin/linux-armhf/gen/config/target.cfg. A number of build-wide variable is set there containing paths to local build system. These variables and the target.cfg file are generated by AROS ./configure script.

Thanks compilation now go forward...changed target.cfg under &quot;toolchain-core-armhf-build/bin/linux-arm/gen/config&quot; and do make on &quot;toolchain-core-armhf-build&quot; dir.

Need to find where to enable build libaeabi.a so can build the entire toolchain with option 21 of rebuild.sh


Found something that looks like libeabi in AROS/arm-all/arm-aeabi/mmakefile.src. Try adding a third line there:

#MM- linklibs-armhd : libklibs-aeabi-arm

Don't remember needing this library. Possibly the 6.5.0 GCC somehow does this while 10.5.0 is missing this.

Try adding this line (and the variant &quot;linklibs-armhf&quot; instead of hd) but it did not solve the automatic building of the missing lib. I must do &quot;linklibs-aeabi-arm-quick&quot;.
Anyway after have build the aeabi lib i succefully built the toolchain (after many hours...). Smile

To test I restarted from selecting option 21 (on rebuild.sh) but after many hours i get the same error of the kernel includes not found...maybe i need to modify the configure script for my case.

With the toolchain built i try to build the core-linux-armhf (DEBUG) (option 22) but after a while it stopped with
&quot;cannot find -laeabi &quot; so i made it built manually...and now i can continue compiling...i'll let you know if all goes ok.


== Hardware ==

===64bit===


====BCM2712====

With the Pi5 

Broadcom VideoCore 7 vc7 is an integrated GPU with 12 cores and up to 800 MHz clock. VideoCore VII is capable of OpenGL ES 3.1 and Vulkan 1.2. The driver support for the Raspberry Pi continues to build upon the [https://lore.kernel.org/dri-devel/20230928114532.167854-1-itoral@igalia.com/ open-source V3D driver] stack within [https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450 Mesa] hopefully be merged for Mesa 23.3. x265 HEVC accelerated untested, x264/h.264 and VP9 cpu only. 

*Raspberry Pi M.2 HAT+ Expansion Board 
*Geekworm X1001 PCIe to M.2 Key-M NVMe
*Geekworm X1003 PCIe to M.2 HAT NVMe SSD PIP Board for Raspberry Pi 5 
*Pineboards Pi Hut HatDrive! M.2 HAT 2024/V4 
*Hat+ Gen2 Gen3 Nvme
*GeeekPi 52Pi N04 for Raspberry Pi 5 NVME M.2
*


*2024 RPI AI HAT    - Hailo  20TOPs  no LLMs 
*2026 RPI AI HAT+ 2 - Hailo  40TOPs  slightly better? 


[https://www.raspberrypi.com/documentation/accessories/camera.html Cameras for Pi]
*Raspberry Pi camera module, the V3 with Sony IMX708 back-illuminated CMOS 12 Megapixel sensor
*Raspberry Pi Camera Module V2 – 8MP Sony IMX219 Sensor
*Raspberry Pi camera Rev 1.3, 5MP 1080P OV5647 image/video module, 2592 x 1944 pixels


====BCM2711====

With the Pi4 an ARM a72 cpu is about x3 times the size of an a53 in the Pi3 

the 2711b line used more power when idle, compared to the 2711c 

*2018 Raspberry Pi PoE HAT Power Over Ethernet Hat - design issues 
*2020 Raspberry Pi PoE+ HAT Power Over Ethernet Hat Pi3b+ Pi4 only - better design 
*Waveshare PoE HAT (B) with cooling fan for Raspberry Pi 3B+/4B 802.3af PoE 

*[https://github.com/axizo-pi/V3DLib vc6 V3D 4.2] is derived from [https://docs.broadcom.com/doc/12358545 vc4], but it is [https://docs.mesa3d.org/drivers/v3d.html significantly different] 
The QPU pipeline stays mostly the same, you still have an add ALU and a multiply ALU and it can issue two ALU OPs per cycle. There is still 4 SIMD lanes, interleaved over 4 cycles.
The instruction encoding for the QPUs is different, but the core instructions are the same.

Instructions for packed 8 bit int math has been dropped, along with most of the pack modes.
Instructions for packed 16bit float math has been added (2 floats at in a single operation)
With vc5/vc6, you write two packed 16f value to the tilebuffer (or four writes of 32f, if you are using the rgba32f framebuffer). And there is a handy vfpack operation which allows you to pack two f32s into a single 32bit value in a single instruction. You can vfpack directly into the tile buffer register.

the multiply ALU can now fadd, so you can issue two fadds per instruction. the add ALU has gained a bunch of new instructions 

the A and B register files have been merged. You still only get an A read and a B read per instruction, but they read from one big register file (which means the underlying memory block has gone from two sets of &quot;one read port, one write port&quot; to one &quot;two read ports, one write port&quot; block)

The theoretical max FLOPs per QPU remains the same at two per cycle, other than the bump from 400mhz to 500mhx but it looks like a lot of effort has been put putting those theoretical FLOPs to better use. 
*vc4 could run one or two threads per QPU. When you ran in two thread mode, the available register file halfed to 32 registers.
*vc5 added a four thread per QPU mode, with 16 registers per thread.
*vc6 doubled the size of the register file. You could now use all 64 threads in two thread mode and 32 registers in for thread mode. Single thread mode was removed, you always have at least two threads.

With the threading improvements, the QPUs should spent much less time idle waiting NOPs for memory requests. Most of the design changes have gone to improving the fixed function hardware around the QPUs. A fixed function blend unit has been added, which should reduce load on the QPUs when doing alpha blending. hope software blending is still possible 

The tile buffer can now store upto 4 render targets (up to 128bits per pixel, so if you are using 4 32bit render targets, you can't have a depth buffer)

A MMU, allowing a much simpler/faster kernel driver.

Many more texture formats, framebuffer formats.

h264/x264 as Pi3 

All the features needed for opengl es 3.0 

H.265 / HEVC decoder is a HEVCv2 Main 4:4:4 10 design supporting bitstreams up to profile 5.1
HEVC hardware decode supports 4kp60, 10-bit. Audio output is pretty much unchanged, but the HDMI audio channels now support 8x192kHz bitrates 

Each ALU typically have 2 floating point operators, and as you pointed out in a earlier post videocore 6 is no exception, with both a multiply and additive floating point operator. Thus theoretical GFLOPs are calculated with both operators in mind. That is what the 2 in my formula represents, and is common across any modern programmable shader, whether you calculate Nvidia, AMD, Intel, Boardcom or any other company's GPUs. Total ALUs * 2 * GHz clock = GFLOPs, In the case of Raspberry Pi 3, it's 24 ALUs * 2 operators * 0.4GHz = 19.2GFLOPs
If the Videocore 6 does indeed only have 16 ALUs (16 * 2 * 0.5GHz), you'd have only 16GFLOPs but they are better utilised 

Possible maximum performance 
&lt;pre&gt;
VideoCore IV @ 250MHz: 250 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 24 Gflop/s
VideoCore IV @ 300MHz: 300 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 28.8 Gflop/s
VideoCore VI @ 500MHz: 500 [MHz] x 2 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 32 Gflop/s
&lt;/pre&gt;

Faster LPDDR4 memory.


====BCM2837==== 

With the Pi3 
* Broadcom BCM43438 chip provides 2.4&amp;nbsp;GHz 802.11n wireless LAN, Bluetooth Low Energy, and Bluetooth 4.1 Classic radio support, 3B+ [https://github.com/aros-development-team/AROS/commit/afa5bc0bb17d5dd06bcfdbac00853a3799ca8d76 LAN7515] 

The overclock ability has diminished with each chip version as the energy usage has increased. BCM2837 is one of the warmest yet and benefits from active fan cooling if all four cpu cores are in use for a short while. Video playback maybe affected due to the lack of custom support in the GPU with Aros. 5 V / 2.4 or 2.5 amp power supply recommended if all four cpu cores are running, else throttling (cpu slowdown) might occur. 

[https://github.com/hermanhermitage/videocoreiv/wiki/VideoCore-IV-Programmers-Manual Dual VDP] and scalable QPU in [https://docs.mesa3d.org/drivers/vc4.html VC4] and x.264/h.264 accelerated untested only and VP9 on cpu or neon help 


ARMv8-A has [https://developer.arm.com/documentation/102412/0100/Privilege-and-Exception-levels privilege levels] where userspace typically runs at ‘EL0’, the kernel at ‘EL1’ or ‘EL2’ and the firmware at the highest level ‘EL3’. 


===32bit===

=== Core Kernel ===


====BCM2708(family)====
which includes the [http://elinux.org/RPi_Hardware BCM2835] (ARM1176JZF-S 700&amp;nbsp;MHz CPU + VideoCore IV GPU + up to 1GB RAM)

*Framebuffer (fb) using mailbox 
*IRQ scheduler, etc 
*Arasan based SD Card controller 
*Synopsis DesignWare USB 2.0 OTG controller [http://networkdirection.net/index.php?option=com_content&amp;view=article&amp;id=106:rasperry-pi-usb-controller&amp;catid=45:raspberry-pi&amp;Itemid=54 Unofficial DOCS pdf],  [dwc_otg.c FreeBSD], [], [https://www.riscosopen.org/viewer/view/mixed/RiscOS/Sources/HWSupport/USB/Controllers/DWCDriver/ RiscOS USB Driver], [https://www.riscosopen.org/forum/forums/5/topics/878 RiscOS USB Discussion], [https://www.riscosopen.org/forum/forums/11/topics/1893 Other USB RiscOS], [http://plan9.bell-labs.com/plan9/index.html Plan9 Miller's usb] http://plan9.bell-labs.com/sources/contrib/miller/, [https://github.com/Chadderz121/csud CSUD driver], 
*[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf SMSC 9512] USB LAN/Hub chip 
*CMOS RAM 
*VCHIQ port which sends messages to the GPU e.g. for mouse, keyboard, audio on HDMI, etc 
*Audio Driver 
*Serial Peripheral Interface Bus (SPI) 
*[http://www.susa.net/wordpress/2012/06/raspberry-pi-pcf8563-real-time-clock-rtc/ I2C registers]
*I2S 
*Universal Asynchronous Receiver Transmitter (UART) 
*[http://elinux.org/RPi_BCM2835_GPIOs GPIOs] and [http://www.adafruit.com/blog/2012/08/17/broadcom-bcm2835-peripheral-memory-map-and-gpio-alternate-use-chart-piday-raspberrypi-raspberry_pi/ Alternative view of GPIO]

BCM2836 
* For Pi B+, PI 2 and Pi 3 SMSC LAN9514 chip adding 10/100 Ethernet connectivity and four USB channels to the board

*[http://www.andrewscheller.co.uk/rpi_pcb_modules.html PCB], [http://elinux.org/RPi_Low-level_peripherals Low level features],


 Implemented so far... 

# Modify the configure system so that it correctly builds for the arm hardware float raspi target.
# Implemented the bootstrap to load the aros modules and prepare the arm to jump into them. Reworked the x86 console support so that parts can be stolen for raspi to use since t has no basic functionality to output to the display.
# Implemented a kernel.resource to prepare the raspi for running aros and provide the low level api calls to expose available resources and allow exec, etc function.
# Implemented serial debug support
# Implemented the exec (and kernel) functionality required to make multitasking work (and interrupts, exceptions, syscalls, etc)
# Implemented a timer.device to utilise the hardware timers.
# Implemented a very basic gfx driver to expose the hardware's framebuffer.
# Implemented an SD-Card driver for AROS which presently only supports the raspi's chipset but can easily be modified to support all sd-card hardware and media.
# Fixed the fat filesystem support in AROS so that it can boot on RasPi's normal SD-Card setup. The &quot;rom&quot; image files needed use a different filename than the default linux, etc images so can be easily installed without harming the existing files - you only need to change the loaded images in the config file to get aros to boot.
# Updated the build scripts to automatically download the necessary raspi firmware files and wrap it all up so that you can simply extract the archive to a fat formatted sdcard and boot it on the raspi without having to get anything else.
# fix everything in contrib and ports to build for raspi (needs proper testing/fixes but allows every component to actually compile at least, including owb) + numerous other fixes to get things working on arm/raspi ..


Improvements...

# Implement a USB chipset driver &quot;OR&quot; finish the existing one [https://github.com/aros-development-team/AROS/commit/c07d13c724f944674be5db54fc6a71ee72a01809 usb otg] - the current code is mostly a skeleton that should initialise the chipset and then needs relevant code to support the different transfer types. It also has the &quot;virtual&quot; hub code in place to represent the raspi's USB port (from poseidons p.o.v) 
# Implement a driver for the USB NIC (a few weeks - depends on USB above) 
# Write an [https://github.com/aros-development-team/AROS/commit/d55d0f74d20b769bbb8c8d386e5c1d7a9154f05a audio driver] (a few weeks - independent of USB) and [https://github.com/aros-development-team/AROS/commit/e93a4c245f27a87c9c4c1d39206694b39059998a HDMI]
# fix syscall bug in the current raspi kernel code
# Graphics depend on having a decent &quot;bcmdma.resource&quot; implemented as to use the cpu's dma engine. The sd card driver needs to use it for transfers to/from the controller - and the gfx system needs to use it for &quot;blitting&quot;. 
# [https://github.com/aros-development-team/AROS/commit/4019d84e4975d4dad987a12d57fe108f5ac048e6 Improve the gfx driver], [ vc4gfx HIDD] add [http://dri.freedesktop.org/wiki/VC4/ Gallium3D support] 
# [https://github.com/aros-development-team/AROS/commit/b13905b3e8e45b089f520b44692c81affddd066f Improve] the [https://github.com/aros-development-team/AROS/commit/3a876755c070f5c73c4f53c7f4d35b4f923088b9 sdcard] device driver  - which is also pretty basic but should work with most cards, rework it to also support pci, etc. sd card interfaces on x86 
# The current code using very rudimentary access to the gpio interface - so that should be implemented as some resource for other components to access, as-well as the i2c interface exposed over the gpio interface. that should have a hidd class implemented which uses the gpio resource to communicate.


 Boot up typical for most other OSs before the open sourcing of many binary blobs from 2017 onwards 

On power-up, the rpi [http://www.open.com.au/mikem/bcm2835/ BCM 2835] [https://github.com/hermanhermitage/videocoreiv VideoCore4] GPU, not the ARM CPU, is in control, and the SD card slot is the only peripheral device with power. The firmware burned into the BCM2835's VideoCoreIV GPU PROM requires a DOS-style partition table; a FAT-formatted first partition; and the freely redistributable but closed sourced Broadcom files “bootcode.bin” and “start.elf” in that partition.

The boot sequence carries out several pre-boot tasks

*On powering of the rpi, the GPU reads and executes bootcode.bin, which then loads start.elf 
*The GPU loads the “start.elf” file, eventually, into the L2 cache and then executes it
*configures the memory split for the CPU and GPU
*reads and parses “config.txt” from the same partition on the SD card and applies the settings (like a PC’s BIOS settings)
*loads the “kernel.img” file, again from the same partition
*activates the CPU to begin executing the loaded kernel image

The CPU/GPU memory split is hard-coded into start.elf, so Broadcom provides three start.elf images, to give 32M, 64M, or 128M to the GPU for multimedia performance, and the remainder to the CPU.

RPi uses [https://github.com/raspberrypi/firmware some closed source loaders] and at some point it loads a binary blob named &quot;kernel.img&quot; at 0x8000, at that point there would be a rudimentary Aros alive. If one wants to use the SD-card then there would have to be a driver for the interface and a fat filesystem handler (SD-card has to be formatted to fat filesystem)

Boot code and kernel are now linked together and made into that binary blob, just for starters. Raspberry Pi uses [http://kernelnomicon.org/?p=133 u-boot] and [http://kernelnomicon.org/?p=138 UBoot] as bootloader, there's already some code in the Efika MX port for that. UBoot is a native bootloader and not just for the raspberry pi, it loads after start.elf.

You can find Efika MX port from arch implementations, some hacking is needed for the mmakefile.src'es as iit dates back to before the Aros crosstool era or else you get some weird errors while building. You also need to code the bootstrap and serial handling.

At the moment it seems that a fastest route for the native build would be to make one binary blob without using the package system. Raspberry's memory layout is pretty simple and if the implemented u-boot doesn't support loading other modules 

&lt;pre&gt;
?          - alias for 'help'
mtest      - simple RAM test
autoscr    - run script from memory
base       - print or set address offset
bbm        - BBM sub-system
bdinfo     - print Board Info structure
boot       - boot default, i.e., run 'bootcmd'
bootd      - boot default, i.e., run 'bootcmd'
bootm      - boot application image from memory
bootp      - boot image via network using BootP/TFTP protocol
cmp        - memory compare
coninfo    - print console devices and information
cp         - memory copy
crc32      - checksum calculation
echo       - echo args to console
fatinfo    - print information about filesystem
fatload    - load binary file from a dos filesystem
fatls      - list files in a directory (default /)
go         - start application at address 'addr'
help       - print online help
iminfo     - print header information for application image
itest      - return true/false on integer compare
jade       -
loadb      - load binary file over serial line (kermit mode)
loads      - load S-Record file over serial line
loady      - load binary file over serial line (ymodem mode)
loop       - infinite loop on address range
md         - memory display
mm         - memory modify (auto-incrementing)
mtest      - simple RAM test
mw         - memory write (fill)
nfs        - boot image via network using NFS protocol
nm         - memory modify (constant address)
pci        - list and access PCI Configuration Space
ping       - send ICMP ECHO_REQUEST to network host
printenv   - print environment variables
rarpboot   - boot image via network using RARP/TFTP protocol
reset      - Perform RESET of the CPU
run        - run commands in an environment variable
saveenv    - save environment variables to persistent storage
saves      - save S-Record file over serial line
setenv     - set environment variables
sleep      - delay execution for some time
tftpboot   - boot image via network using TFTP protocol
USB        - USB sub-system
usbboot    - boot from USB device
version    - print monitor version
&lt;/pre&gt;


And there is one more thing about modular ports. In order to actually implement this, your bootstrapping environment should provide the ability to load several files. On PC this is provided by GRUB2. on CHRP you can read filesystem via OpenFirmware, and Sam's Parthenope relies on modified u-boot. If your bootstrap allows to load only a single file, then you stuck with monolithic kickstart. By the way...  u-boot allows not only to boot up a single uImage or zImage, it also allows to write client programs AFAIK. With this approach, you actually can write modular bootstrap for ARM AROS using unmodified u-boot.

Most used [http://www.compulab.co.il/workspace/mediawiki/index.php5/U-Boot_quick_reference uboot options] are fatls usb 0:1,

the reason behind INTB_KERNEL is to allow use of the standard Exec function AddIntServer() to add interrupt handlers for
hardware drivers etc. AmigaOS never used it for abstract hardware drivers. AmigaOS  routed  only  raw  hardware IRQs there. Their assignment was hardcoded. As well as number of them. Actually on AmigaOS every bus has its own interrupt subsystem. For example PCI bus. PCI interrupts on Amiga are routed to a single exec interrupt.  1:1 relationship between CPU  and hardware interrupts is present only on PC.

IMHO we miss things like AddInterrupt/RemInterrupt methods on our PCI subsystem's device class.  PCI bus class should map these methods to whatever is appropriate. This is how it is done on AmigaOS and friends. When these are implemented, raw kernel.resource API will be needed only for several PC-specific drivers with hardwired resources. Exec IRQs are real IRQs only on Amiga hardware. On other machines they can be emulated where appropriate (VBlank is a good example). kernel.resource is meant  to be different, its IRQs are hardware-agnostic, they are plain &quot;Hardware IRQ number X, whatever this means&quot;. They are low-level actually, and meaningful only in the context of a particular system.

Was that not the transition from irq.hidd to kernel.resource? No.  A long time ago there was another hacky bit named INTB_TIMERTICK. It was &quot;abstract timer interrupt&quot;, used by timer.device. It was the same as VBlank, but with larger frequency. I removed it, because kernel.resource API was a cleaner way to access this interrupt. Furthermore, there can be more than one timer in the system. Thinking about bringing back timer HIDD definitions again. hpet.resource is a bad idea.

Can someone please enlighten me a little on how the scheduler is meant to work?
 
Poseidon.library creates its &quot;Poseidon Event Task&quot; during RTF_COLDSTART -&gt; then calls Wait(), and ends up in limbo because wait disables interrupts (used for the scheduler heartbeat), and basically waits forever because the sigbit is never set, since krnSwitch doesn't switch the task unless TF_SWITCH is set, and no codepath run during this seems to set it?? TF_SWITCH does not disable/enable switching. This flag just enables to run user-supplied hook when the task is being switched away. It is completely safe to call Wait() in Disable()d state. Doing this actually temporarily breaks this state. IDNestCnt gets remembered in struct Task, then next task is selected, and its IDNestCnt is restored in sysbase (see kernel_scheduler.c). If there are no other tasks, then your cpu_Dispatch() should enable interrupts on the CPU and enter idle mode. See x86 implementation for good example.

You miss what happens next...
 1. KrnSwitch() saves context of your task, saves IDNestCnt (core_Switch() and cpu_Switch()), then drops into cpu_Dispatch().
 2. cpu_Dispatch() calls core_Dispatch. Then two cases are possible:
 2a. There is a READY task. It is picked up, its IDNestCnt is restored in SysBase, then cpu_Dispatch() needs to restore registers and exit. The next task is run.
 2b. There are no READY tasks. core_Dispatch() returns NULL. In this case your cpu_Dispatch() should enter idle loop. It should just enable interrupts on the CPU and put it on halt. This allows it to process hardware interrupts. Eventually some of your interrupt handlers wakes up your task and puts it into READY list.

My heartbeat interrupt has been slowed atm to help debugging - but it never actually gets a chance to fire because of the Wait() disabling interrupts. Perhaps you have forgotten to enable interrupts in your idle loop.

There is a change in the format of AROS executables. Until now we were using Elf RELocable files which are usually used as intermediate object files. We had them for various reasons, one of them was how AROS files were built in the past. That days we had no real aros cross compiler and the option to embed relocation data in unix executables (or in executable files in general) was rather new and not every linux/unix system had it. Therefore we have decided to use intermediate files. Although it was somehow working (and it is still working :-)), it has some drawbacks. Therefore decided to introduce real Elf EXEC types, in first turn implemented on ARM target with option to expand in future to all other AROS architectures.

The first patch was pretty easy and appeared to work somehow. It generated nice executables with embedded relocation info. Not only that, it also removed all global symbols adjusting relocation data to be relative to the beginning of the sections. That move reduced number of symbols in each executable significantly (depending on the file between 20 and 80% of all symbols could be removed). The only symbols that stayed in the file are local ones - due to the nature of the patch wasn't able to remove them since we have not seen them in the symbol hash table.

The patch didn't worked though. The files were relocated, AROS kernel loaded, but it crashed very early. What happened? Well, the nature of ARM relocations happened :)

Most of the relocation data on all machines is rather simple. Relocation can be absolute or pc-relative, sometimes the offset has to be bit shifted. On ARM v7 there is another one. There, when one wants to load an address of function/variable into register a combination of two instructions can be used: movw and movt. The first one loads immediate into lower 16 bits of a register while clearing upper 16 bits. The second one loads immediate into upper 16 bits without touching lower halfword. Loading of a pointer into a register looks like this:

        movw r0, #:lower16:label

        movt   r0, #:upper16:label

In this case there are two relocations - one for lower halfword and another for upper. If an overflow of lower 16 bits occurs during relocation process, the upper one should be updated as well. Unfortunately with current patch and with typical ARM executables there is not enough information to perform the calculations.

There are two options - the first one would be to give up and go back to &quot;fake&quot; executables, another one would be to change from REL to RELA relocation info. The latter contains an addend, extra data which can be used to perform all the relocation calculations I need.

Decided for the second option. The patch is already in the works. There is another function for the binutils' bfd backend to perform the final relocation. There can decide what to do with every reloc info, modify data and eventually strip some symbols. An advantage is - at this stage of the linking process have also full access to all local symbols so can change all relocations section relative and eventually strip all symbols from the files. 


 GPU 

VCore developed by Alphamosaic Ltd and now owned by Broadcom. Most of start.elf runs on the GPU.   Placing ALL the userland GPU code in the videocore.hidd isn't going to be a terribly big problem because the code they published is nothing more than a shim that sends data straight to the GPU to execute.

The good news about this is that we only need to write our HIDD using the OpenVG API.   The shim is relatively small codewise and lives in the ARM memory (the actual OpenVG code itself lives in the GPU RAM area and its loaded from start.elf).   That's also the bad news.  Our driver has to translate AROS video calls to OpenVG calls, for most tasks it should be easy, for some, not so much.  It's still probably less difficult and less work, than controlling the GPU directly.

The other good news is that anything done through OpenVG happens on the GPU, its truly accelerated.   It also has some nice font functions, meaning we can lead into an accelerated text mode later.

Basically, AROS resets or locks up when it tries to use AROS_ATOMIC_INC or DEC.  If I comment out the byte/word operations in the header files and use non-atomic operations, the code works as expected.
 
have read that the L1 cache needs to be enabled to use LDREX and co (which I also read is only meant to be used on multi processor systems with shared memory) - however I am certain this is correctly enabled.

If you are using LREX or STREX, you should have L1 cache enabled, at least on the ARM CPU I work with at work.

L1 cache is enabled by enabling the MMU *AND* setting the C and I bits in the CPU - the C bit is ignored, and the I bit only covers the 16 byte instruction pipeline if the MMU is not enabled.

Can you verify that your assembly is generating LDREX/STREX? From the behavior, it almost sounds like its generating the default Semaphore locked atomics.
 Impossible. There are no semaphore-locked atomics. There are Disable()/Enable()-based ones instead. And there's a special #define AROS_NO_ATOMIC_OPERATIONS in this case, which tweaks Disable()/Enable() implementations not to recurse forever.
 I have tested this on ARMv5 which does not have ldrex/strex, it works fine. On those ARMs there's no way to have real atomics. On other OSes (like Linux) this is done by introducing things like atomic_t, which appears to be a complex structure, holding the value together with accompanying spinlock (implemented using swp).

    #warning &quot;TODO: lookup optimal mmu table settings for raspi memory&quot;
        /* Set up an identity-mapping for all 4GB */
        for(x = 0; x &lt; 4096; x ++)
        {
            pagetable[x] = x&lt;&lt;20 | (0x40002|0x80000|0x010000|0x00C00|0x04);
        }

Shouldn't there be a second loop that sets the 'C' bit in the descriptor for the RAM pages?

Currently, you have TEX=0, C=0, B=1 for all pages (Shared Device).

You should have TEX=0, C=1, B=0 for RAM (Write-Through, Cached)

    So ..
     
     pagetable[x] = x&lt;&lt;20 | 2;

     
    should be enough?

No, for RAM you need to change the '| 0x40' to '| 0x80'

tell dosboot the correct defaults to use

Please don't do this. This bootconfig.c is a deprecated legacy thing. I wanted it to go away completely with time. Instead,  display  drivers  should auto-install themselves during own initialization phase. I. e. detect hardware=&gt;instantiate itself. This   should   make  things way simpler. With this approach you only need  to add the driver into KS image to get the device autobooted. No hardcoded stuff. 
Currently  VESA  and  VGA drivers do this, look there for examples. never rewrote ATI driver because i don't have any test system for it.

they defined a smaller AROSCPUContext than the ExceptionContext - yet reference it as ExceptionContext in other places, and since it hasn't allocated enough storage for ExceptionContext, are corrupting memory/the structure (since the elements that are there don't map 1 to 1 with the exception context).

AFAIK, AROS has been moving in a different direction to this in recent years. It is the job of graphics HIDDs to allocate bitmaps etc. so that they have the most suitable characteristics, including allocating them from GPU RAM where possible. The concept of chip RAM is only for legacy code, and most if not all non-68k platforms should have all system RAM
marked as chip.

BTW, is the video processing code you mention CPU code or GPU code?

Also, IIRC we have support for &quot;external memory allocators&quot;. Perhaps that's what we need for the allocation of GPU RAM through the mailbox.

All hosted and x86 native ports should use proper context formats.

trying to clarify if the vblank handler has to have run by this point to prevent this deadlock. Actually, no. Unless you have installed VBlank handler which should wake up at some point. Without VBlank there will be no quantum count. Consequently, there will be no forced preemption. But the rest will work, and multitasking will be cooperative (switch happens only when current task voluntarily gives up the CPU). Does it depend on the vblank having run before this point? and if yes what does that mean on systems where it might be able to run enough code (e.g. get to this point) before the vblank interrupt has triggered? What is it waiting for? It could wait for timer, in this case you need timer.device working. VBlank is currently needed for exec's quantum counter. In current native ports we have only a single timer, which is served by timer.device. VBlank is simulated by timer.device also. If your machine has two timers, then you can use one of them for VBlank, and another for timer.device, this will simplify things down. VBlank needs to be 50 Hz for historical reasons, many programs use it as cheap timer. I am periodically thinking about making some abstract mechanism to be able to change quantum source (and untie it from 50 Hz), but have no time to come up with something good. Additionally i started disliking timer.device hardcoded design when PC has got many timers (old 8253, APIC, HPET).
Currently i think there should be some low-level entity representing tick source. timer.device should just select the most appropriate source for its units.
The BCM2835 has 4 GPU based timer sources - 2 are used by the GPU, so im using Timer3 for our heartbeat and the remaining one will be free to the system. There is also the less capable ARM timer but that is dependent on the CPU frequency. Very good. You won't need any emulation. Set the heartbeat to 50 Hz and drive VBlank from it. Use other timer for MicroHZ.

Can you use the 'econsole.hook' I make for debugging the Sam460 via the serial port?
It provides a before-anything-else shell prompt on the serial port.  You can then do 'NewCLI' to test your graphics, or use any DOS command in shellcommands.resource.

You should just be able to add econsole.hook to your module list, and use 'econsole' in your bootargs.

So long as you have a working Exec/RawMayGetChar and Exec/RawPutChar, it should work.

Also make sure to add shell.resource and shellcommands.resource for this.

That should have done it.

If you set &quot;#define DEBUG 1&quot; in  arch/all-native/econsole/econsole.c, do you get any additional serial output?

have added it to the build and added econsole to the command line - and can see the bootloader picks up on the emergency bootconsole tag, but I still only get the insert bootable media display?

Im assuming it exposes a fake filesystem that tricks aros into booting?
The contents of which are: ECON:AROS.boot

Way to handle the scheduling code? The implementations I had been following were causing problems, due to cascading interrupts which I cant handle properly in the asm stubs just now (when they break disable etc.) - since it means detecting the interrupted codes cpu mode and getting the correct sp/lr for it, and that's just too tedious for arm.
 
To work around this ive added a system idle task which does nothing - and when the scheduling code has no task to run switches this in and lets it run, thereby allowing the interrupts etc to resume until something does need to happen.
 
Also, by adding accounting code to cpu_Switch() and cpu_Dispatch(), it should allow the system to log idle time correctly (as well as running tasks).
 
have thought of also adding an additional task that never runs, solely to record time spent in IRQ handlers, but I digress..

was under the impression that kernel.resource should *never* be used outside of exec.library. This is a wrong impression.
Michal started designing it because portable nature of AROS does not fit well into exec's API with all its assumptions. So, he started the new, hardware-agnostic kernel API from scratch. Yes, exec sits on top of it in places. But kernel always meant to be open thing. Otherwise it would not exist. 
it wasn't meant to be just used willy nilly by user code - but by lower system components (e.g. exec) so that they could be implemented in a more generic fashion, and the kernel resource itself hide the systems quirks.

Adding new things there perfectly keeps up with our decision to minimize AROS-specific intervention into APIs which can clash with MorphOS or Amiga OS4 extensions. We want at least source-level compatibility there. Binary compatibility on PPC would be extremely cool, but at the other hand we have no maintainer for this, as well as their ABIs splintering. 
It depends on what exactly is being implemented - there's no reason we should have everything crammed into kernel.resource if it doesn't need to be (i.e. if its better suited as a separate component/subsystem in its own right)

The _LE versions are for when you have endian swapping taking place.  If the graphics are the same endian as the CPU, no swapping should occur.  I ran into a similar terminology problem in SDL with a friend insisting that his Radeon 7000 on his PC was big-endian.  It is not, it just uses the same endianness for the graphics card and the CPU so no swapping was necessary.  They were both little-endian.
The _LE versions are because the PixFmts refer to the bitmap data being in big endian format in memory, for which the normal version would need to do endianness conversion before applying the shifts/masks. on this platform it is in _LE in memory also so we don't need the conversion hence using the _LE version of the call). would use _LE (if it's really little endian 16 bit mode).

 
What is the bare minimum needed to implement a framebuffer based gfx driver, with our software handling the rest?

Have tried with just a gfx class that only expose new/dispose/newbitmap - and having an onscreenbitmap used only for the framebuffer itself (with all other bitmaps being chunkybm, and the framebuffer's superclass also being chunkybm), but that alone isn't enough it seems?
You can use workbench/hidds/sm502/ as your example - it is as simple as I could make it.
So, AROS creates the framebuffer bitmap (verified this) -&gt; so surely it should be capable of then rendeing into it? I don't actually create the framebuffer &quot;bitmap object&quot; myself - only as a result of being asked to. The code I currently have on SVN seems to create the framebuffers bitmap object fine, but then crashes in intuitions DisplayDriver callback.  In particular it crashes performing the getattr on the system default pointer. don't expose MEMF_CHIP in an allocatable form so AllocSpriteData was failing (and other code later doesn't check if the values are valid == illegal memory accesses) 

So far have -:

vc_init: queries the gpus memory, and sets up a fake memory handler for it, then adds the bootmode driver and returns saying all is well
vc_gfxhidd:New: sets up some fake syncmodes to test with and creates the real gfx object.
vc_gfxhidd:NewBitmap: checks if its a framebuffer and uses the onbitmap class or uses the chunkybm class otherwise
vc_onbitmap:New; creates a chunkybm object and then pushes the real framebuffer address into it as the buffer,

vc4 had v8adds, v8subs, v8muld, v8min and v8max which operated on four 8bit uint values packed into a 32bit register. Multiplication was in the range 0.0 to 1.0 and addition/subtraction saturated. There were also a range unpacking/packing modes that allowed you to pack and unpack 8bit values into 32bit registers. 

RasPi has to speak to the &quot;operating system&quot; which runs on the GPU itself and request/free memory - it cant directly manage it itself, and so the managed functions were used to wrap these calls.

The Arm and GPU share memory space. The framebuffer is shared. The Arm can write a pixel and it will appear on the screen (through GPU hardware) without flushing/copying being required.

The GPU can composite multiple FB's in real time - so you have a number of surfaces defined which are rotated etc and  composited in real time to the output. Copying can map from the address space of the Arm to the flat space of the GPU which takes some code, but I don't think whole buffers are copied.

The DMA hardware can also access the whole memory space and can perform 2D fills and blits (no blending). This is documented in the peripheral spec posted. The DMA is just an Arm accessible peripheral and can be set up with low latency (e.g. microseconds).
must use a 0xc0000000-based bus address to access SDRAM, yet non-DMA access should go via a 0x0-based bus address. 
For 2D dma, set TDMODE, and the spec says &quot;interpret the TXFR_LEN register as YLENGTH number of transfers each of XLENGTH, and add the strides to the address after each transfer.&quot; so set STRIDE to pitch of the image, the width is XLENGTH and height is YLENGTH. You would fill by not setting the SRC_INC and point source to your fill data.

The DMA cannot see the ARM's L1 cache, so you would map the framebuffer with ioremap_nocache. Depending on where the source data comes from, it may need an L1 cache flush. The DMA can see the L2 cache. Use 0xC0000000 bus addresses when L2 is disabled and 0x40000000 bus addresses when L2 is enabled. (actually just call virt_to_bus and you'll get the right address out).

openGLES/openVG has high latency. Writing to framebuffer then reading it back is very inefficient (e.g. milliseconds). If you can drive it a unidirectional way, just streaming commands at then that is efficient. openVG is not implemented on top of openGLES - it uses the same hardware but as a first class interface

To improve the Gfx driver, we will need a DMA resource implemented so can use to perform DMA operations. The Gfx driver will need this to perform blits.


Actually MEMF_CHIP has to present, for historical reasons.
This has been never fully agreed upon, but in ports i wrote i exposed the whole memory as MEMF_CHIP. The idea behind this is that CHIP is originally the memory where graphics and sound data can be put. On non-Amiga platforms there are no restrictions on this, so the whole memory is CHIP.
Yes, many old software can misbehave with CHIP memory size larger than 2MB. But this actually applies only to m68k AROS which is going to run m68k binaries. In other cases it's quite logical to fix the program when porting.

As to original question: yes, it's enough to have a framebuffer bitmap (one with aoHidd_BitMap_FrameBuffer set to TRUE) and PutPixel routine. It framebuffer can be served by chunky bitmap class, then you can simply create chunky bitmap with your own buffer (see how VESA driver does this). Chunky PutPixel is already there.

struggling to determine what is the correct pixfmt to use for the 24/16/15 bit gfx modes on the RasPi.  AFAIK it uses RGB565, for 16bit but im unsure what shifts etc should go with it? suffice to say Im getting the wrong colors so far lol.

&lt;pre&gt;
redmask: 0x0000F800
greenmask: 0x000007E0
bluemask: 0x0000001F
alphamask: 0

redshift: 16
greenshift: 21
blueshift: 27
alphashift: 0
&lt;/pre&gt;

It should likely be vHidd_StdPixFmt_RGB16_LE

This stuff is a bit confusing.  The &quot;names&quot; of the stdpixfmts are based on the layout in memory,
ignoring endianess. So for example:

ARGB32: will be 0xAA 0xRR 0xGG 0xBB in memory on both big endian and little endian machines.

The shifts and masks OTOH are based on pixel access (ULONG in this case), so differ depending
on whether you run on big endian machine or little endian machine (that's why there's stdpixfmt_le.h and
stdpixfmt_be.h in rom/hidds/graphics/).

With the 16 bit pixel format it's even more confusing, as for example it's impossible on little endian machine
to describe RGB16 with shifts/masks alone. That's why there's vHidd_PixFmt_SwapPixelBytes_Flag.
(RGB16 == RRRRRGGG GGGBBBBB in memory, and for pixel (WORD) access on little endian machine it needs to
be accessed as GGGBBBBBRRRRRGGGG).

The shifts btw indicate how much to shift the component to the left (!) so that it is moved to the highest bit (31).

The aHidd_PixFmt_StdPixFmt you specify will be ignored most of the time, because when the pixelfmt is registered,
the gfx hidd checks if there's an identical pixfmt (shifts/masks/etc., but ignoring pixfmt-&gt;stdpixfmt) already in the system,
and if so, it uses the already existing one and does not create a new one.

In theory it would be better if gfx drivers could simply/only specify a StdPixFmt without all the shifts/masks stuff when the
gfx driver uses pixfmt which matches one of the stdpixfmts exactly. Another possibility would be for gfx drivers to use
HIDD_Gfx_GetPIxFmt(stdpixfmt_gfx_driver_wants_to_use) and then peek shifts/masks from it and fill out a pixfmt
tag list based on that.
15bit very blue/green: Try to pass same shifts/masks/etc. as in 16 bit pixfmt (maybe you think it's using 15 bit R5G5B5
(or swapped) but it's actually still using 16 bit R5G6B5 (or swapped).
 aHidd_PixFmt_StdPixFmt you pass is mostly ignored. It's the shift/masks/etc. that count.
But I would still pass the correct one (_LE) == whatever rom/hidds/graphics/stdpixfmts_??.h uses
in the entry where you have looked up shifts/masks/etc.

Use the shifts/masks/etc. from the entry in stdpixfmt_le.h (if you are running on little endian machine) or stdpixfmt_be.h (if you
are running on little endian machine) that matches the pixfmt that its meant to be.

0xAA,0xRR,0xGG,0xBB on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_BGRA32)

0xAA,0xRR,0xGG,0xBB on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_BGRA32)

it feels like AROS trashes the alpha component, otherwise it should be 8A8R8G8B.

read on the subject suggest its in 1x5r5g5b (x is ignored) to keep 16bit alignment .
 
Suggests to me that wrong shift/mask are being applied - however going by the 16bit versions it all looks correct to me so I am really confused as to what is happening.

The output image looks to have too much green/blue, and very weak red.


 Kickstart 

The  idea  is  to minimize amount of archirecture-specific modules to make the user's  life  easier.  So,  the kickstart was split into 'base' (which  does  not  contain anything machine-specific) and 'BSP' (Board Support Package) which contains all hardware-specific stuff. This  way,  for  example, distribution makers can save up space on CD and  make  CDs with multiple platform support. Different configuration would load the same base with different BSP's.

Next  there  was some part which is entirely missing on hosted. These are   filesystems.  Hosted  ports  do  not need them to boot up, so on hosted   they  are  left  out.  At  the  other  hand,  they  are  also architecture-agnostic.  So  i put them into 'FS' package (standing for 'filesystem').


 USB 

Poseidon  is  one  more  big part. I made it into separate package in order to allow users to omit it if they don't need it (for example, to run  on retro PCs without USB). Personally i have one. Again, Poseidon is  hardware-agnostic (well, there are USB drivers but HCIs are pretty standard).

AFAIK its HCI 1.0 compliant but not familiar enough with poseidons drivers, nor USB, to just hack away at the existing code.  Perhaps once i'm more familiar with the workings I can merge in the changes needed to get it operating but for now I will focus on getting it running.  Also our drivers have known issues so perhaps a fresh set of eyes might shed some light on what is going wrong.

Another interesting question is whether Poseidon can operate on device side. Is it flexible enough? How similar is being a USB host and USB device? think it will need a bit of work on Poseidon's side.  Until then I will force the driver into Host/Master mode in the init code, but leave open device etc to configure the chipset for either's use - and look at trying to add support for working in Device/Slave mode &amp; switching modes once it's up and running.

Actually USBROMStartup is some kind of kludge. Can there be any alternative? Could device drivers be self-installing, like our HIDDs? This would get rid of need to list them in USBRomStartup.

* Model A and B limited to 150 mA per port. 
* Model B+ and Pi 2 introduced configurable 600 mA to 1.2 A support over all ports - anything above that requires a powered USB hub.

Implementing the hardware driver that Poseidon uses to interact with the USB components.

Have code in place to (try) and initialise the USB chipset, and configure host/device mode operation (though AFAICT Poseidon doesn't support device mode). Started to get the &quot;virtual&quot; root hub written for the single USB port so that Poseidon should at least list it correctly in the GUI - and try to interact with it to find peripherals.


The BCM2835 uses a soft IP block from Synopsys’ DesignWare library (DWC), specifically the block is called dwc_usb_2_0_hs_otg_subsystem-ahb_se (“USB 2.0 Hi-Speed OTG Controller Subsystem w/AHB Interface SE”).

There is no public documentation for this, and pretty much zero chance of anyone getting hold of it even with NDA. However, there's a Linux driver written by Synopsys ([https://github.com/raspberrypi/linux dwc_usb]). Specifically directories [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_common_port] and [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_otg].

The Synopsys code is actually under a fairly permissive licence – it's not GPL, it's similar to BSD (’don't sue us if it breaks’ is pretty much the only clause). So this should not be a barrier to porting the code.

The code is really well written, with a nice partition between the work done by the driver (dwc_otg, which is fairly involved, given the host does more work than a conventional EHCI driver), and the interface to Linux (dwc_common_port).

Probably only need provision of relevant changes to dwc_common_port. Other things to consider....

* Provision of necessary headers to get it to compile
* Provision of necessary functions (main issues are wait queues, threads, work queues, tasklets, timers, spinlocks and mutexes (multithreading) )
* Interfacing between USB stack and the driver. dwc_otg/dwc_otg_hcd_linux.c looks like the place to start.

the Linux bits of the headers are only required for the dwc_common_port library. dwc_common_port includes a variety of crypto functions which are not used – it appears to also be used for ultrawideband (UWB) and wireless USB (WUSB) drivers where crypto will be an issue, but it isn't going to be for plain wired USB.

Every USB driver acts as an USB hub as well in order to let Poseidon control the state of USB ports. The code there was reading status of the only USB port in Raspberry's CPU but when changing the status it erroneously deleted some of the status bits, including the port enable one. It was so because those bits in the status register are of a type Read/WriteToClear. It means, if one does not want to change their value from 1 back to 0, one has to actually write the 0 value. Very practical thing e.g. in interrupt handlers, where one reads the interrupt status register to learn what was the interrupt reason, and writes it back to the same register in order to clear the interrupts. 

After fixing that code it turned out that the communication was still unsuccessful. Apparently the USB device was not understanding the host for some reason. That should not happen since the request sent was one of the standard ones implemented by virtually anything with an USB connector, assumed that Poseidon clears the data caches before forwarding the work to the USB drivers but that's the responsibility of the driver itself. 

The USB device responded and acknowledged the transmission! But why were all the request sent after address change failing with timeout? They should not. Once again, address set is supported just by anything. Tried to contact the device at address 0 once again and there it was, still responding properly. The enlightenment came. The bus address for DMA transmissions was, as it is in many bare metal USB implementations, just the pure memory address of the buffer as seen by the ARM cpu. Have &quot;prefixed&quot; it with the real location of uncached RAM and booted AROS once again. 


Trident saw this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

and this:

    Product     : Vendor: Vdr=0424/PID=EC00
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 255
    SubClass  : 0
    DevProto  : 1
    VendorID  : 1060
    ProductID : 60416
    DevVers   : 0200

and even this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

What are these things? The first one is USB hub built in the Raspberry. Thanks to this one the Pi machines (with exception of Pi0 and computing modules) have more than just one single USB port. The second one is the network chip in raspberry, the third one is my USB SD card reader which have just connected to see what happens. AROS tried, of course, to boot from it ;)

So, the first step towards working USB is done. The control transfers are working as you can see above. Next step is to implement bulk and interrupt transfers, having the basics in place. Finally some error handling will be added and USB for Pi will be as complete as the PC version. 

[http://www.raspyfi.com/raspberry-pi-usb-audio-fix/ Issue with USB Audio]


 Audio 

The Pi 4B is the only Pi that can output HD Audio as an HD Audio passthrough bitstream, and it does it over HDMI. It's possible to use the two HDMI output for separate HDMI video and HDMI audio outputs to allow UHD HDR video and HD Audio with non-UHD HDR compatible AVRs. 

The Pi3B+ and earlier will decode to PCM 5.1/7.1 and output over HDMI.  HDMI is the only interconnect that has a standard for carrying Dolby True HD, DTS HD MA etc. as a bitstream - you can't carry it as a bitstream on any other interface.

Pi3 and Pi4 audio jack output derived from 12bit pulse width modulation is relatively poor. For better, choose USB Audio or I2C versions. 

[https://github.com/raspberrypi/linux/tree/rpi-patches/sound/arm audio] and its [https://github.com/raspberrypi/firmware/issues/2 very high speed message passing interface type of thing VCHI] 

The Model B+ added an additional voltage regulator for the audio output and an additional output driver to drive low-resistance loads like headphones. However it is still using pulse-width modulation (PWM), which has a major impact on sound quality

the old Raspberry Pi used a linear voltage regulator to provide the 3.3V to many of the components on the board while the new one uses a switching regulator. Both can perform reasonably well. However switch mode power supplies often show higher noise figures

Analogue audio

Audio over HDMI rev 1.3 &amp; 1.4


 Ethernet 

10/100 BaseT Ethernet RJ45 socket


 GPIO 

GPIO shouldn't be too bad but bear in mind it is already accessed in places so they would need to allocate pins etc through it (e.g. sdcard to flicker the activity light, serial debug to output data on the GPIO pins)

Probably a resource rather than a device...

Started an i2c driver that will need to allocate GPIO pins. Feel free to work on it if you are interested ;p


 GPU graphics with 2D and 3D acceleration 

Sadly none yet for 32bit but for 64bit... 


 Miscellanous

hdmi issues

Setting the hdmi_force_hotplug=1 makes sure the Pi believes the monitor/TV is really there.

You might also need to set config_hdmi_boost=4 or even higher (up to 9) if your display needs a stronger signal.

If the display is a computer monitor or newer tv, use hdmi_group=1 (auto HDMI use) and if it is an older TV, try hdmi_group=2 (for DMT formats, i.e. for PC monitors) then you HAVE to &quot;set hdmi_drive = 2 to enable HDMI output as this forces HDMI mode rather than DVI mode

Do not set hdmi_safe=1 as that overrides many of the previous options.

Using a shorter or better quality HDMI cable might help. Make sure your Pi's power supply delivers 1 A and not 500 mA.
If you see a problem with the red colour - either absent, or interference - then try a boost

composite video

changing the RCA cable, then the composite port worked out of the box

Boot it as you are doing, without HDMI. If you now plug in the HDMI, do you get the image? In other words, does the Pi think HDMI is connected even when it isn't?

Rename all the files in the first partion of the card except bootcode.bin, start.elf and fixup.dat  What's the result?

Put back config.txt What's the result?

for PAL mode   sdtv_mode=2

dmi_ignore_hotplug Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached
hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected

&lt;pre&gt;
# NOOBS Auto-generated Settings:
#hdmi_force_hotplug=1
#config_hdmi_boost=4
#overscan_left=24
#overscan_right=24
#overscan_top=16
#overscan_bottom=16
#disable_overscan=0
start_x=1
gpu_mem=128
&lt;/pre&gt;

tvservice -c &quot;PAL 4:3&quot;

&lt;pre&gt;
/opt/vc/bin/tvservice -s   or tvservice -s 
state: HPD high|HDMI mode|HDCP off|composite off (0x12001a), 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m CEA
Group CEA has 1 modes:
(native) mode 16: 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m DMT
Group DMT has 0 modes:
&lt;/pre&gt;

sudo amixer cset numid=3 1

forces the audio to the headphone jack, even with the HDMI video output plugged in

config.txt

the hdmi_ignore_edid_audio=1 option sems relevant as it should tell ALSA that the only available audio is analog, no matter what the display says

There are several different ways that these 4 pole (ring) composite analog cables can be wired up, so some work great in some applications and can be a waste of time in others.

What is needed for the Raspberry Pi B+ and above, which like many camcorders needs the ring contact next to the base contact to be the ground.


The wiring for the 4 pole are:

TIP (LEFT AUDIO CHANNEL)

RING 1 (RIGHT AUDIO CHANNEL)

RING 2 (GROUND/EARTH)

RING 3 BASE/SLEEVE (VIDEO) YELLOW

Most Apple based Players and the Microsoft Zune (TM) are wired this way.

Most analogue camcorders are wired this way as well, where the ground in on Ring 2 will work with the Pi although you may need to swap your Video plug with the Right Audio plug.

Nearly all other MP3 players are not wired this way, the ground is on another ring ie the wrong one.


External devices

* Camera Module Omnivision ov5647 Sunny 5MP (NoIR version) V1.3 - NoIR at 850&amp;nbsp;nm, peak at 880&amp;nbsp;nm and trails off at 940&amp;nbsp;nm wavelengths 
* Camera V2 Sony IMX219 V2.1 8mpixel 8MP 8megapixel - 3280 x 2464 pixels - video at 1080p30, 720p60 and 640x480p90 - wider field of view, 62 vs 54 degrees horizontally - 
* Branded WIFI usb BCM43143 dongle

N.B.  dreaded error after changing cameras (stupidly without turning off the power first) and lasted through several power cycles.  It can be a bad 15-pin FFC ribbon cable, when swapped, camera(s) and the Pi itself are working OK. It can be an instance of a cold solder joint on the CSI connector on the pi board.  the camera can be detected (that's done via I2C) but may still not be able to receive image data (done via CSI-2) if something is broken. CSI-2 is uni-directional. Control is generally done via I2C. 
The CSI-2 receiver always writes to memory, not direct to the ISP. That's the way the Broadcom architecture works as it allows multipass processing easily. GPU memory is accessible from the ARM. Processing using the QPU graphics processors may be possible.  currently the only supported sensor is OV5647 and IMX219.  The linux drivers are all in the firmware blob, else you'd  be looking at at least a man-month of work in a fully fledged imaging lab to do a decent tuning of the camera modules' ISP parameters. 
Static electricity maybe an issue for the camera module and slightly less for the pi board.


== References ==


===Good sites to visit===

*[https://github.com/raspberrypi/firmware/tree/master/ Raspberry Pi Firmware build] 
*[https://www.raspberrypi.com/documentation/computers/software-sources.html Documentation] 
*[https://rpilocator.com/ RPiLocator] 


Linux only
*[https://github.com/raspberrypi/linux Raspberry Pi Linux Build] 
*[https://dietpi.com/ DietPi] 
*[http://www.tinycorelinux.net/ports.html piCore]
*[https://wiki.alpinelinux.org/wiki/Raspberry_Pi Alpine Linux] 
*[https://github.com/armbian/build Armbian] 


*[ FydeOS]
*[ TwisterOS based on ChromiumOS] 
*[https://note.com/jamesmondo/n/nc76e31402be8?hl=en BSD] 


*[https://www.raspberrypi.com/software/operating-systems/ PiOS Lite] and then [https://hstwb.firstrealize.com/ HST] 
*[ PiMiga for pi4 and pi5] 
*[ amibian for pi2 and pi3] 
*[ retropie pi1 and 2] 


Other alternative lighter smaller than Pi OS 
*[https://aros.sourceforge.io/nightly1.html Aros 64bit ARMV8 single core] 
*[https://www.riscosopen.org/wiki/documentation/show/Welcome%20to%20RISC%20OS%20Pi RiscOS on Pi3 and Pi4]
*[https://github.com/michalsc/Emu68 ARM based realtime JIT 68k for amiga computers] 
*[https://github.com/JJDSNT/bellatrix/releases/ Alternative use of Emu68 on Pi3b] 
*[https://github.com/stevereaver/uaos uaOS with Emu68k] 
*[https://github.com/aros-development-team/AROS/commit/f80a268607dfae81b2db94755ab4e4d31ccb72d6 m68kemu library reference] 
*[ HaikuOS]
*[https://github.com/raspberrypi/noobs NOOBS] os loader with successor [https://github.com/procount/pinn PINN] 
*[https://github.com/maxnet/berryboot berryboot]

*[https://github.com/brianwiddas/pi-baremetal Bare Metal Access on Pi 32bit] 


Testing procedure is put sd card in, connect board to board if necessary, plug in hdmi and then power nothing else is done especially CSI DSI etc 

[https://www.raspberrypi.com/documentation/computers/compute-module.html CM5] has the same 55mm x 40mm 2x100pin connectors form factor as the CM4 but [https://www.epdtonthenet.net/article/214508/Key-Considerations-When-Migrating-from-Raspberry-Pi-CM4-to-CM5.aspx some pins and other small things] have changed. Will need the [https://raspipcb.com/tech-blog/raspberry-pi-cm4-vs-cm5-difference-in-booting-from-sd-card/ right IO board to suit] 

*Green [ Raspberry Pi Compute Module 5 IO Board REV2 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1967]] - untested 
*Green [ RPi Compute Module 5 IO board REV1 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1751]] - untested 
*Black SupTronics Geekbord X1500 CM5 IO Carrier Board - untested
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*[https://sipeed.com/nanocluster Sipeed NanoCluster] - untested up to 7 CM5 
*Green BentoIO CMX0 - untested 
*Box EDATec ED-CLAWBOX - untested 
*Home Assistant Yellow - Kit with PoE with Raspberry Pi Compute Module 5 - untested 
*Blue [https://www.waveshare.com/wiki/CM5_PoE_BASE_A Waveshare CM5-PoE-BASE-A] - untested 
*Box  Waveshare [ CM5-POE-BOX-A] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-B Waveshare CM5-IO-BASE-B] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-A Waveshare CM5-IO-BASE-A] - untested 
*Blue Waveshare [https://www.waveshare.com/wiki/CM5-NANO-B CM5-NANO-B] - untested 


*[https://carboncomputers.us/products/pi-flux piFlux]
*[https://carboncomputers.us/products/ Zitaotech Hackberry] CM5 lite only - 
*Portable [https://www.waveshare.com/pocketterm35.htm Waveshare PocketTerm35] with Pi4B or Pi5 - untested 
*Box [https://www.clockworkpi.com/uconsole ClockworkPi uConsole][https://www.youtube.com/watch?v=EtI_bAahbR8 CM4 into an adapter or CM3 into so-dimm - Cyberdeck] - untested 


*Green RPi [https://datasheets.raspberrypi.com/cm4io/CM4IO-KiCAD.zip Compute Module 4] [https://datasheets.raspberrypi.com/cm4io/cm4io-datasheet.pdf IO board] V1.4 [https://datasheets.raspberrypi.com/cm4io/CM4IOUSB3-KiCAD.zip USB3] [https://datasheets.raspberrypi.com/cm4io/cm4iousb3-appnote.pdf CM4ISO] [https://datasheets.raspberrypi.com/cm4/cm4-datasheet.pdf Dual100pin] (2020) aka Development Platform Board - untested 
*Purple Pi Hut Cytron CM4 Maker Board - untested 
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*[ KubeSail PiBox mini 2] 
*Home Assistant Yellow with Raspberry Pi Compute Module 4 - untested 
*[ Turing Pi V2] - untested CM4 with 260-pin SO-DIMM socket adapters and/or nvidia jetson nanos - untested 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-C Waveshare CM4-IO-BASE-C] - untested but binary blobs Rev01 Rev02 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-B Waveshare CM4-IO-BASE-B] - untested but binary blobs 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-A Waveshare CM4-IO-BASE-A] - untested but binary blobs 
*Blue [https://www.waveshare.com/wiki/CM4-NANO-B Waveshare CM4-NANO] - untested but usb and audio turned off or rerouted 
*Black [ Seeed Studio with BigTreeTech BTT pad 7] - bin blobs? 


CM3 has a 200 pin sodimm ddr2 connector form factor but not electrically SC0028, SC0029 
*Blue [https://wiki.geekworm.com/CM_IO_Board Geekworm RPi Compute Module IO Board] [https://github.com/geekworm-com/cm-io-board CSI DSI] with CM3 in ddr2 slot underside - '''works''' if SW1 on but CM3+ '''does not''' 
*Green [https://cdn-shop.adafruit.com/product-files/3442/CMIO_schematic.pdf RPi V3 IO board CM3IO] and CM3 Lite - untested 
*Green [https://turingpi.com/ turingpi v1 cluster] - untested up to 7 cm3 7xlan9514 12V discontinued, 3 x Pi4 homelab maybe better 
*Blue [https://www.waveshare.com/wiki/Compute_Module_PoE_Board Waveshare Compute Module PoE Board] and CM3 lite (if not lite, write files to internal eMMC fat32) '''AVOID''' bin blobs 
*Blue [https://www.waveshare.com/compute-module-io-board-plus.htm Waveshare Compute Module IO Board Plus] [https://www.waveshare.com/wiki/Compute_Module_IO_Board_Plus wiki] [https://forums.raspberrypi.com/viewtopic.php?t=235695 pin settings] with CM3+ Lite - '''AVOID''' binary blob 


*[ Pi02w on Geekworm SupTronics X305 Raspberry Pi Zero IO Baseboard] - untested 
*[ Spotpear Pi Zero 2w to Pi3b format-ish] - untested 


*[ pi-top v4] box has 128x64 oled display, micro hdmi, 19Whr battery with pi4 and 15V PD 36W min needed 
*[ pi-top v3] three green pieces, heatsink covers most of the base tray, pi-top hub mk1 lhs and Pi1B Pi2b Pi3b rhs secured from below, black rounded strip with pi-top above keyboard, 13.3&quot; HD 1366 x 768 display, small touchpad, 
*[ pi-top Model 2.0] pi-top on bottom bezel of 14-inch green laptop, large trackpad, keyboard slide down to reveal main system hub on slide rails moved to the right, Raspberry Pi3b screws down, hub slides in, 18V 2.5A 45W charger brick, battery 11.1V 3500mAh 38.85Wh and storage PiTopOS 
*[ Pi-Top CEED Raspberry Pi Modular Educational Desktop with RPI3] monitor 
*[https://www.indiegogo.com/en/projects/jesselozano/pi-top-a-raspberry-pi-laptop-you-build-yourself Pi-Top v1] wedge laptop with RPi2 


&lt;pre&gt;
2008 Trustees collected for Foundation
2009 Pi Foundation charity status gained 
2010 
2011 First Raspberry prototypes 
2012 First boards go on sale at CPC and RS. The Model A and B 700 MHz Arm11 - February 29th BCM 2835
2012 First million sold - more than the 10,000 original planned and anticipated 
2013 First Alpha Experimental builds of AROS Native for the 32bit Pi 
2013 Pi Trading launched making grants available, providing in house educational resources and Pi Academy for teacher training 
2013 Over two million sold 
2014 Over three million sold 
2014 Pi 1 Model B+ introduced that moved composite video to audio jack and same half gig of memory 
2014 Pi Model A+ v1.1 no ethernet and 1 usb - a little smaller - 
2015 Over four million first gen pis sold  
2015 Pi Zero 1.2 BCM2835 first production revision released with no camera port 
2016 Pi0 1.3 released with camera csi connector 
2017 Pi Zero W v1.1 1GHz Pi0W, single-core 32bit CPU BCM2835 released with Cypress CYW43438 wireless 
2020 Raspberry Pi Pico SC0919 with RP2040 32-bit 2Core ARM Cortex-M0+ up to 133 MHz - 264KB of SRAM and 2MB of on-board QSPI Flash - 
2024 Raspberry Pi Pico 2 with RP2350 2Core 32bit Arm Cortex-M33 and 2core open-hardware [https://github.com/wren6991/hazard3 Hazard3 RISC-V] 

2015 Pi 2 Model B v1.1 BCM2836 900/600 MHz ARM Cortex-A7 Armv7 quad 32bit, 32bit VideoCore IV GPU - 1Gb RAM - 5V 2A micro usb - SMSC LAN9514 chip - 
2015 Over a million pi2s sold 


2015 Raspberry Pi 2 Model B version 1.2 Pi2bv1.2, aka Pi2B2 has armv8 BCM2837 underclocked to 900Mhz without wifi/bluetooth module 
2016 Pi 3 Model B - Broadcom BCM2837 SOC four 64bit ARMv8 Cortex-A53 1.2GHz 32bit 1080p VideoCore IV GPU - 1Gb DDR2 - bluetooth 4.1, Cypress CYW43438 wireless 802.11n - 4 x USB2.0 ports - 5.1V 2.5A - SMSC LAN9514 chip 
2016 PIs total over 10 million worldwide 
2017 Compute Module 3 CM3 with BCM2837B0 armv8 Quad 64-bit - small 67.6mm x 31mm board which fits DDR2 SODIMM connector but not electrically compatible which plugs into needed IO board - beware of the I2C protocol issue 
     1Gb LPDDR2 RAM - Lite or 4Gb Emmc storage 
2017 12 million pis sold in total 
2018 Pi 3 Model B+ - 4c A53 BCM2837B0 1.4Ghz - 1Gb, wireless 802.11ac, gigabit ethernet (300Mbit/s) and bluetooth 4.2 - power over ethernet - 4 x USB2.0 ports - Microchip LAN7515 chip 
2019 Over 15 million sold 
2019 Pi 3 Model A+ with BCM2837b0 Cortex-A53 64-bit SoC @ 1.4 GHz with 512Mb LPDDR2, 1 usb2, 1 hdmi, 1 micro usb 5V 2A - no ethernet - 
2019 Raspberry Pi Compute Module 3+ CM3+ - Broadcom BCM2837B0 1.2Ghz, Cortex-A53 (ARMv8) 64-bit SoC on DDR2 SODIMM mechanically compatible only factor - IO board required 
     1Gb DDR2 and 8GB, 16GB, 32GB or a Lite variant without eMMC 
2021 Pi zero 2 (w or no W) RP3A0 quad 1GHz Cortex-A53 64bit BCM2710A1 512mB SDRam 
2025 edaTEC CM0 ED-CM0NANA with additional dev board with quad 1Ghz A53 with 512Mb Raysan RAM, 2 USB2 and 10/100 ethernet - pico castellated edge
 

2019 Pi 4 Model B v1.1 RPI4B - BCM2711B0T quad 64bit A72 1.5GHz, 4K VideoCore VI, AC wifi, Bluetooth 5.0, GbE Broadcom BCM54213PE (PHY ID 0x600d84a2), 2 micro hdmi decode up to 4K, USB-C 5.1V 3A power, 2xVLI VL805 USB 3, 2xUSB 2.0, 2GB 9LDWW D9WHZ or 4GB 9FDWW D9WHV, 8GB 0AA47 D9ZCL ddr4 ram 
2020 Silent Pi 4 v1.2 upgrade with more USB-c psu support 
2020 PI400 BCM2711C0T 1.8GHz 4Gb DDR4 inside keyboard, 5.1V 5A 27W usb-c psu, 2 micro hdmi, external ide style 40pin gpio, no audio port - 
2020 Raspberry Pi Compute Module 4 BCM2711B0T on new 55mm x 40mm 2x100 pin form factor with extra breakout IO board 
     CM4101000 1Gb RAM Lite SOM 
     CM4102000 2GB RAM Lite 
     CM4104000 4GB RAM Lite 
     CM4004008-4GB-RAM 8GB-EMMC SOM System on Modules 
     CM4104032 4GB RAM 32GB emmc 
     CM4108000 8GB RAM Lite 
     CM4008016 8GB RAM 16Gb eMMc
2021 Raspberry Pi SC0763 Compute Module 4S CM4S with ddr2 sodimm pinouts but not electrically the same with suitable IO board extra cost - 
     CM4S01000 1GB RAM Lite
     CM4S01008 1GB RAM 8GB eMMC Flash
     CM4S02000 2GB RAM Lite
     CM4S04000 4GB RAM Lite
     CM4S04016 4GB RAM 16Gb KLMAG1JETD-B041 
     CM4S08000 8GB RAM Lite 
2021 Pi 4 v1.4 BCM2711B1 upgraded power regulator, to deal with 8gig of ram being more power hungry 
2021-48 Raspberry Pi 4 model B v1.5 2GB 


2023 Pi 5 v1.0 BCM2712 Quad A76 @2.4Ghz - VideoCore VII - no audio socket - dual 4k from mini hdmi - fan connector - 5.1V 5A psu 
2024 Pi 5 2GB DDR4 version uses BCM2712D0 
2024 Pi-500 with 8Gb LPDDR5 and membrane keyboard 
2024 Pi 5 v1.1 
2024 Raspberry Pi Compute Module 5 CM5 BCM2712 55mm x 40mm form factor with additional IO board 
     CM5004000 04GB RAM 0GB eMMC Lite
     CM5008000 08GB RAM 0GB eMMC Lite
     CM5016000 16GB RAM 0GB eMMC Lite
2025 Pi-500+ with 256GB NVMe storage, 16GB LPDDR4 RAM, and Gateron KS-33 Low Profile Blue mechanical keyboard switches 
2025 Pi5 1GB DDR4 announced 


2022 PiOS linux goes 64bit 
2024 Pi Trading IPO stockmarket stock exchange listing 


2026 April and May Aros 64bit fixed, added AHI audio, VC4 gfx started, usb functions added to rom  
2026 June and July Aros 64bit usb2otg started, dma.resource, sdio.resource, bwfm.device wifi added 
2026 Late July daily 64bit Pi3 LE little endian builds start 
2026 August Pi 4, 400, 5 and 500 DTBs added, expanding existing support and wifi for Pi4 and Pi5 
2026 August Pi5 HAT+ nvme and HDMI, AHI RPiI2S added, Pi4 HVS5 video scaler started, 
2026 
2027 


2028 Pi 6 
&lt;/pre&gt;


The vcgencmd can be used to inspect and dump the current system configuration. 
vcgencmd runs on top of VCHIQ as an RPC. The mailbox interface is an alternate but much simpler RPC. 
VCHIQ is a bridge (queue) between the CPU and the GPU so they can communicate with the firmware. 

Loads of [https://github.com/6by9/rpi3-gpiovirtbuf/blob/master/rpi3-gpiovirtbuf.c mailbox] which uses the GPIO control calls. [https://github.com/raspberrypi/firmware/wiki/Mailboxes may also be of interest] 

A fair number of vcgencmd examples (search for vc_vchi_gencmd_init). [https://www.raspberrypi.org/forums/viewtopic.php?t=229203#p1406112 sends the relevant vcgencmd commands] to update the scaling kernel, but the [https://github.com/raspberrypi/userland/blob/master/host_applications/linux/apps/gencmd/gencmd.c command] is just a text string. Parsing and execution of the instructions is performed by the VideoCore firmware. 

The Raspberry Pi runs two separate operating systems: Linux/Aros on the ARM, and a threedx RTOS called vcos running on the Videocore 4 VPU: vcos is commonly called &quot;the firmware&quot;. Vcos is tasked with performing certain system services, for example running the display and audio outputs. The VCHI driver provides an interface to allow drivers to talk to vcos. 


Doubtful, on any [https://www.web3d.org/ Web3d] [https://developer.mozilla.org/en-US/docs/Web/API/WebGL_API WebGL] or [https://github.com/immersive-web/webxr WebXR] [https://developer.mozilla.org/en-US/docs/Web/API/WebXR_Device_API Device API] [https://developer.mozilla.org/en-US/docs/Web/API/XRInputSource XRInputSource] support. Hopefully, never/limited support features like location, peer-to-peer, invasive web apps, unwarranted storage, payments, proprietary video streaming etc 

*spreadsheet [https://git.sheetjs.com/sheetjs/sheetjs sheetjs] [https://github.com/mleibman/SlickGrid SlickGrid] [https://github.com/6pac/SlickGrid SlickGrid] [https://github.com/jspreadsheet/ce jspreadsheet ce] probably without xlsx support 
*presentations [https://github.com/impress/impress.js/ impress.js simplified] [https://github.com/bwlewis/slides slides] [https://zenomt.github.io/mdslides/ github markdown slides] [https://github.com/Patternslib/slides Patternslib slides markdown] probably without pptx support 
*ai office [https://github.com/dream-num/univer/ univer], [https://github.com/dream-num/Luckysheet Luckysheet] [https://github.com/ruilisi/fortune-sheet fortune-sheet] 
*weather [https://github.com/Himanshu3412/Weather-Forecast Weather Forecast], [https://github.com/kaushalsahu07/weather weather needs API key], 


==Future==


[https://github.com/ARMSX2/ARMSX2 Arm pi of pcsx2] 


[https://tube.cadence.moe/ Cloudtube], [https://github.com/TeamPiped/documentation/blob/main/content/docs/public-instances/index.md TeamPiped], [], [], [], 

[https://hyperpipe.codeberg.page/ hyperpipe], [https://ytify.pp.ua/ ytify], [], [], 

[ ytdl], [https://github.com/golddominik893/liberatube liberatube]

[https://git.lolcat.ca/lolcat/4get 4get], [https://github.com/hnhx/librex librex], [], [], 


{{BookCat}}</text>
      <sha1>9px4g6wrk3uiy5ys4xxnt78zwxu3gj3</sha1>
    </revision>
    <revision>
      <id>4676557</id>
      <parentid>4676534</parentid>
      <timestamp>2026-10-17T15:33:28Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4676557</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="106226" sha1="1kon26txpe12gejpr7c8b564049wmlh" xml:space="preserve">{{ArosNav}}

[[#Native]]

[[#Hosted]]

[[#Build]]

[[#Hardware]]

[[#References]]

[[#Future]]


==Introduction==


[[File:Scalos00.png|thumb|Scalos on Aros Pi3b]]

Aros aims to cover Pi 3 to 5 512Mb+ RAM 


Options to boot from using a good power source to prevent the yellow lightning symbol. 
*With Pi3b+ the max you can get is 5.1V 2.5A with micro usb.
*With Pi4 5.1V 3A with usb-c 
*With Pi5 5.1V 5A, the amps went ever upwards, even to 5.1V 9A with usb-c 


* Pi500+ keyboard wedge - working but not much tested esp [https://github.com/aros-development-team/AROS/commit/48e9c8edcca4b5c1e1fe0b1123f2129f624af67b power button] 
* Pi500 wedge with up to date bootloader via PiOS - working but not much testing esp [https://github.com/aros-development-team/AROS/commit/48e9c8edcca4b5c1e1fe0b1123f2129f624af67b power button] 
* Pi 5  - Quad A76 64bit ARMv8 and RP1 &quot;southbridge&quot; with VideoCore 7 D0 (rev1.1) - untested 
* Pi 5  - Quad A76 64bit ARMv8 and RP1 &quot;southbridge&quot; with VideoCore 7 Pre-D0 C1 (Rev1.0) - untested 
* Pi400 RPI-400 keyboard wedge - resolution changing and audio from micro hdmi0 (near 40pin) and micro hdmi1 (near usb-c psu) - Fn F10 0x5e power on and off works or held down for over 7 seconds auto shutdown - keyboard ok - wifi and lan ethernet testing - 
* Pi 4  - Quad A72 64bit ARMv8 with VideoCore 6 
* Pi 3  - Quad A53 [https://www.raspberrypi.com/documentation/computers/processors.html 64 bit] ARMv8 with VideoCore 4 with '''fan''' to prevent overheating cpu 82C+ throttling 
* Pi02W - Quad A53 64bit - boots but [https://forums.raspberrypi.com/viewtopic.php?p=2387984#p2387984 usb not working but did in the past], 


* Pi 2 - Quad 32bit ARMv6 with VideoCore 4 - mostly not 64bit compatible 
* Pi Model B+ 32bit ARMv6 with VideoCore 4 - not 64bit compatible 
* Pi Model A and B 32bit ARMv6 with VideoCore 4 - not 64bit compatible 


===Native===

* 2013-03 Kalamatee starts work
* 2015-04 Work continues with mschulz on the kernel and Kalamatee (NicJA) on gpio and usb
* 2018 [https://www.patreon.com/posts/i-owe-you-some-20956961 mschulz resume adding BE big endian support], [https://www.patreon.com/michal_schulz/posts Big endian on Pi]  
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bsek latest commits for pi 3b, 4 and 5 64bit] 
* 2026 [https://github.com/aros-development-team/AROS/commits?author=metaneutrons latest commits for Pi5]
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bitplane latest commits for ARM]


====64bit====

'''Download''' A [https://archive.org/details/piAROS Pi Distribution (Distro) has started] and the contents copied to fat32 8GB+ microSD card (there will be drawers/folders - boot c Classes Demos Developer Devs Extras etc only showing). The SD can be plugged in to the Pi. And power on. [https://pi.amiga.icu/ Repository]

'''Not recommended''' but [https://aros.sourceforge.io/nightly1.html RaspberryPi 3, 3+, 4 and 5 64bit ArmV8 nightly builds] [https://sourceforge.net/projects/aros/files/ and alternative site and nightly2] which is a test version of '''very few''' apps with both raspi-aarch64-system and raspi-aarch64-contrib can be unbz2'd to a SD or SSD as appropriate. 

64bit build works well on a single core LE little endian. Multicore [https://github.com/aros-development-team/AROS/commit/1df0747c2bda3523a43029725a709b1f377d84ec may follow]. Any issues booting could be down to the SD card so please use another SD to see if it is resolved. Remember Aros Arm uses FAT32 and Aros can detect issues with this format very acutely (once fault found, FAT 0x0FFFFFF7 bad cluster so no files written after that, no repair). Please report your experiences in the [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2138&amp;pid=15057#post_15057 Aros forum thread], [https://forums.raspberrypi.com/viewforum.php?f=179 Raspberry Pi Aros Dev and User forums], [https://forums.raspberrypi.com/viewtopic.php?p=2387984#p2387984 previous Raspberry Pi forum thread]. Any bugs or issues can be [https://github.com/aros-development-team/AROS/issues described here to fix] 


*Pi500+   untested usb3 booting or nvme ssd 
*Pi500    untested usb3 booting 
*Pi5      untested usb3 booting 
*Pi400    boots with '''USB3''' port based sata3 ssd 
*Pi4      untested (may need eeprom update from PiOS or Pi SD Imager) 
*Pi 3 B+  is pre-configured for USB sata3 boot - untested 
*Pi 3 B   may need [https://www.youtube.com/watch?v=ubnwvxF3Klc PiOS to set OTP to boot from usb - do so at your own risk] - if OTP set to usb, boot works but slower than SD card 

Speed write wise (top faster) 
&lt;pre&gt;
*NVME Pi5 untested    &gt;1000MB/sec  or faster if matched correctly 
*Sata3 ssd              500MB/sec
*SD        V90           90MB/sec  4K maybe 8K 
*SD        V60           60MB/sec  1080p 
*SD     U3 V30           30MB/sec  720p 
*SD C10 U1 V10 A1 A2     10MB/sec  minimum should be used now 
*SD C06                   6MB/sec  
*SD C04                   4MB/sec 
&lt;/pre&gt;


As a homage to the past, Aros shows a reduced number of icons but this can be changed by left mouse click in the window and then right click down to Window -&gt; View -&gt; All files

Windows can be manipulated by the top (moving) and the bottom right corner (resizing) only. 

Zune like MUI gui interface, has a unique quirk in that after changing a setting in a text box, you may sometimes need to press Enter/Return before clicking OK, Save, etc 


Double left mouse click on most picture (Developer/Debug/Tests/Datatypes), audio and video files are supported, via datatypes, by the multiview application. 
Esc escape key usually closes open windows even the desktop 

In Prefs/Appearance some decorative theming elements need work. There is a few Mason icons in /Prefs/Presets/Icons/Mason/ and the ever present default Gorilla - Icon exchange in works 

For more intensive graphics applications, you may need to edit config.txt in the root folder and change 128M to 256M to adjust more memory to graphics usage 

If your cursor should '''appear''' to vanish, fear not it is still there. Please head to the top of the screen i.e. the title bar, hold down the left click mouse and drag the screen down a little and the cursor will appear again. Then you can drag the screen up again. 


Like most amiga like OSs the audio and networking need to be setup manually 

Audio AHI prefs - Mode settings tab - needs both Music unit and Unit 0 set to RPiHDMI:16 bit stereo++  or RPiPWM:16 bit stereo++ at 44100Hz. Press '''Save or Use''' button after each choice 


For wireless, please use the Wifi prefs and already selected device bwfm.device. Press Scan and double right click on the router and enter password. You may need to setup after every power off
*if asking for password again - press cancel and go to Network Prefs, Wireless Networks tab and highlight the router line and hit the remove button and press the cancel button. Retry with Wifi prefs again 
*...waiting for an address - Disconnect and try Connect 
Until, Connected to &lt;router&gt; - 192.168.x.x 


For lan ethernet port, please use Network prefs and the following hardware is 
*lan9514    Pi3b Pi2 not supported at the moment 
*lan7515    Pi3b+ type into Device  usblan78xx.device as net0:  remove other device(s) 
*bcmgenet   Pi4 Pi400 choose for Device bcmgenet.device 
*cdnsgem    Pi5 Pi500 Pi500+ RP1 i/o for cadencegem 
 (network prefs may forget random information when rebooted) 


Summary
&lt;pre&gt;
*3b    ethernet not supported, usb ethernet not working but wifi prefs setup works 
*3b+   wifi working and ethernet works 
*4     untested 
*400   wifi and ethernet untested 
*5     wifi and ethernet untested
*500   wifi and ethernet untested
*500+  wifi works 
&lt;/pre&gt;


Type in 'aarch64' in the [https://archives.arosworld.org/index.php?function=search&amp;tool=simple search box] and you will see available software packages / apps. apkg can be used to inspect and install applications. 

[http://archives.arosworld.org/index.php?function=browse&amp;cat=network/browser amelinium web browser (JS 1.6 ES9 ECMASCript 2018)] is available with an [https://eab.abime.net/showthread.php?t=122494&amp;page=80 eab thread] reminiscent of [https://github.com/zapek/Voyager Voyager] and to a lesser extent [https://github.com/amigazen/aweb3/ Aweb JavaScript 1.5 (ECMAScript 3)] as css and javascript websites can be slow to load or resolve (no JIT) and nothing from facebook, reddit etc. 

Press Cancel at screenmode selector or -wb argument to get windowed version. You could use the Shift + Del shortcut or mouse wheel should work to delete all text at once. Html5test gives 189 (1.29), 300 (1.31), 301 (1.39) out of 555, some bigger Amiga like browsers are around 370+ but it does less better. 

You may have to delete the cache (Menu -&gt; Page -&gt; Delete cache) to fully retest big Amelinium updates or free up space. 
Be aware [https://pianetaamiga.it/en/reportage-pianeta-amiga-2026/ some site pages] can use up hundreds of MBs of cache very quickly 

 DNS lookup failed...  close browser and reboot and setup wifi again - repeat until it works again 

 youtube video and audio - js button for javascript must be on/shaded -  Settings -&gt; Soundoutput - AHI 
Any restriction to lower resolutions is due to [https://docs.invidious.io/faq/#q-where-are-the-360p480p1080p-quality-options bandwidth]. Either CPU/GPU, internet speed and/or video quality. Pi3 can expect 480p (wifi) to 720p (ethernet). Pi4 expect (wifi)  (ethernet). 

Telegram https://t.me/s/channel_name for public messages from vamped_amiga chatamigagames demoscenecracktros 

*art local js apps like dpaint.js 


There is normally no Bluetooth support for most amiga like OSs but Aros has one [https://github.com/aros-development-team/AROS/commit/6942cbfbf66426d21963a7fcd8aba6aff611a9e0 work in progress] [https://github.com/RPi-Distro/bluez-firmware/tree/pios/trixie/debian/firmware/broadcom firmware] 

*Bluetooth 4.1 BCM43430A1.hcd Pi3B, Pi3A, Zero 2W 
*Bluetooth 4.2 BCM4345C0.hcd  Pi3B+, Pi4 
*Bluetooth 5.0 BCM4345C5.hcd  Pi4B rev, CM4 and maybe Pi5 and CM5 

&lt;pre&gt;
*bthid    keyboard mouse support 
*btserial serial 
*btpan    short range wireless connecting devices 
&lt;/pre&gt;


Only the Pi5 has a RTC real time clock, the other Pis will need to use ntp services [https://github.com/aros-development-team/AROS/commit/29cd4116330dc7f692d90757eacc59fb3f31ae70 sntp] with time.cloudflare.com pool.ntp.org or Cloudflare 162.159.200.1, 162.159.200.123, 2606:4700:f1::1, 2606:4700:f1::123 or [https://github.com/bohunamiga/PiNTP PiNTP -s goodtime.ijs.si or ntp1.ptb.de] to get the date and time from the internet. Can use date in a shell e.g.  date 24-Dec-2026 23:59:59  but this will need to be done again after every reset/power off. Maybe [https://github.com/aros-development-team/AROS/commit/28674a157bc56175aa668e7b62dca6fa740578dc ds3231 rtc with dtoverlay=i2c-rtc,ds3231 in config.txt] 


It helps to have all usb devices already plugged in before power on to detect at the moment. Even then some usb devices will freeze the mouse cursor and the only resolution is to remove the offending usb device and reinsert. Sometimes, the reinsert leads to the mouse cursor vanishing, it is still there and responds to left mouse clicks, top of the screen and pull down the screen. 

USB classes support from Prefs/Trident is still work in process 
*usbaudio working on usb3 port (blue) on pi4, 400 but not working (no rt isochronous) on usb2otg (white or black) for pi3b, zero 2w 
*[https://aminet.net/package/mus/midi/camd camdusbmidi] detects midi devices without a preferences file (Prefs/Env-Archive/sys/midi.prefs) as [https://www.youtube.com/watch?v=RBxHkwy4Nrw auto setup now] possibly with [https://github.com/metaneutrons/mt32-pi metaneutrons mt32-pi] [https://github.com/rtzor/mt32-pi mt32-pi fork] [https://github.com/ahmadexp/mt32-pi fork] [https://github.com/gmcn42/mt32-pi-control control of] [https://github.com/dwhinham/mt32-pi mt32-pi pi3+]. Alternative of [https://homspace.nl/samplerbox/ SamplerBox]. 

Will need developer clang gcc tools to look at 64bit ports of [https://archives.arosworld.org/?function=showfile&amp;file=driver/audio/usbmidi.i386-aros.lha usbmidi], [https://aminet.net/package/mus/midi/CAMD_Toolkit CAMD_Toolkit], [https://aminet.net/package/mus/midi/camdtools camdtools], [https://github.com/cnvogelg/amiditools amiditools], [https://github.com/timoinutilis/midi-sequencer-amigaos horny src], [https://aminet.net/package/mus/midi/horny-base horny-base], [http://bnp.hansfaust.de/index.html BnP], [https://arosarchives.os4depot.net/?function=showfile&amp;file=audio/misc/timidity.lha timidity], 


Regarding 680x0 emulation, there are several options (not implemented yet) that could be considered 
*[https://github.com/aros-development-team/AROS/blob/6722a0ae9e03fe5d26e32703360bd2059e0864cc/rom/m68kemu/README.md?plain=1#L424 m68kemu.library] for some Amiga productivity where the cpu is emulated and the system calls are redirected to Aros ones
*[https://github.com/BlitterStudio/amiberry amiberry] (winuae) for everything else like games 
*[https://github.com/jonx/AROS/tree/aarch64-darwin-graft/arch/all-darwin/libs/emu68k emu68k] 
*[https://scriptedamigaemulator.net/ Scripted Amiga] with [https://github.com/naTmeg/ScriptedAmigaEmulator ScriptedAmigaEmulator] or older [https://github.com/gbraad-amiga/ScriptedAmigaEmulator2 ScriptedAmigaEmulator2] 
 Hopefully getting Pi3 up to 25Mhz 68040 (non JIT) and 50Mhz 68040 (JIT) 
 Pi4 maybe getting up to 50Mhz 68040 (no JIT) and 100Mhz 68040 (JIT) 


[https://pinout.xyz/ GPIO 40 pins] [https://learn.sparkfun.com/tutorials/raspberry-gpio/gpio-pinout pinout] 

Some exceptions:

*Physical pins 27, 28 (GPIO0, 1) are an internal I2C bus and should not be used
*The other I2C on pins 3, 5 (GPIO 2, 3) can be used generally, but be aware they have permanent pull-up resistors to 3.3V
*For MIDI use USB but there are dedicated UART pins 8, 10 (GPIO 14, 15).

With a HAT it's more awkward -- you need to know which pins are used by the HAT and avoid them. Hopefully this will be documented.

Remember all GPIOs are 3.3V (not 5V tolerant), floating/noisy inputs can cause odd behavior, and that shorting the power supplies can cause instant death of the Pi.

In the shell (Cntrl + C to end) 

 GPIO PIN/A/N,SET/N,GET/S,MODE/K,PULL/K

Controls and queries hardware GPIO pins via gpio.resource which is stored in the rom or Devs/ '''please test''' 

*PIN   -- (Required) Target GPIO pin number (e.g. 12).
*SET   -- Set pin output value to 0 (LOW) or 1 (HIGH).
*GET   -- Read and print current digital input level (0 or 1).
*MODE  -- Configure pin mode: IN (Input), OUT (Output), ALT (Alternate).
*PULL  -- Configure pull resistor: NONE, UP, DOWN.

EXAMPLES
&lt;pre&gt;
GPIO 12 MODE OUT
GPIO 12 SET 1
GPIO 12 GET
GPIO 13 PULL UP
&lt;/pre&gt;


[https://gpiozero.readthedocs.io/en/stable/installing.html Current] [https://gpiozero.readthedocs.io/en/v1.2.0/api_boards.html old support for gpiozero is unknown at present] [https://energenie4u.co.uk/res/pdfs/ENER314%20UM.pdf and associated 433MHz equipment] [ USA X10 security and lights via USB] [ OpenHab with Shelly Smart Plug connected over Wi-Fi, controlled by MQTT or HTTP] 


Printing only with Postscript but [https://github.com/bohunamiga/MintPRINT one] of [https://github.com/boingball/MintPRINT two] [https://github.com/Andiweli/AmiAirPrint/tree/main AirPrint] IPP has been attempted with [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2061&amp;pid=13954#post_13954 discussion] 


Youtube 

[], [], [https://www.youtube.com/watch?v=X4fmWAIv7FE Aros native on Pi3b], 

[], [], [https://www.youtube.com/watch?v=TSxlYb1eQWU Installed on Pi3b+], 

[], [], [https://www.youtube.com/watch?v=NFF1H3jCoz8 testing Aros native on Pi400], 

[], [], [https://www.youtube.com/watch?v=nIVx7mh1E1Q&amp;pp=ygUHYXJvcyBwadIHCQkTDAGHKiGM7w%3D%3D Aros on Thumb 2 based 32bit-ish ARM STM32H743 board], 


[https://www.youtube.com/watch?v=zQM4CD64xDE&amp;t=612s&amp;pp=ugUEEgJlbg%3D%3D Performance under Linux] but on Aros... 

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot; |Pi
! width=&quot;10%&quot; |Single Core 2D
! width=&quot;10%&quot; |Single Core 3D
! width=&quot;10%&quot; |Single Core 3D
! width=&quot;10%&quot; |SMP 2D
! width=&quot;10%&quot; |SMP 3D
! width=&quot;10%&quot; |SMP 3D 
! width=&quot;35%&quot; |Comments
|-
| &lt;!--Pi--&gt;Pi3 
| &lt;!--Single Core 2D--&gt;
| &lt;!--Single Core 3D--&gt;
| &lt;!--Single Core 3D--&gt;
| &lt;!--SMP 2D--&gt;
| &lt;!--SMP 3D--&gt;
| &lt;!--SMP 3D--&gt;
| &lt;!--Comments--&gt;
|-
|}


==== 32bit ====

For the Pi1 Pi2 Pi2B the status of AROS native ARMv6 for 32bit RasPi was OK. System booting, USB working (although with some issues but plans to fix them). 32bit native [http://www.aros.org/nightly1.html ARMv6 32bit nightlys] raspi-armhf-system raspi-armhf-contrib unbz2'd to fat32 microSD 


===Hosted===


AArch64 CPU backend for AROS, a Cocoa/Metal display, clipboard / host-volume / CoreAudio / BSD-sockets bridges, GPU 2D via gpufx.library, a 68k→AArch64 JIT (run68k), and a full Rust std port. On [https://www.jkn.me/blog/macaros-aros-on-apple-silicon/ latest Apple Silicon] [https://github.com/jonx/Macaros early buggy alpha version of hosted Aros .dmg on MacOS12+]. Please use [https://github.com/jonx/Macaros/issues MACAros github] for issues, features etc and possibly [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2030&amp;pid=13910#post_13910 here] 


[http://www.aros.org/snapshots1.html old linux and android hosted 32bit] 


==== Hosted ====

=====64bit=====

[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80&amp;pid=13667#post_13667 Ubuntu Linux PC hosted Pi compiler build] 

[https://github.com/BlitterStudio/aros-compiler-docker Docker based cross compiler for various Aros systems], 

[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80 From the Aros Raspberry pi 3 64bit thread] 
Instructions on building 64-bit Raspberry Pi AROS and cross-compiler from sources.

You will need:
- Ubuntu 24.04 or 26.04
- qemu-system-aarch64 installed
- Internet connection
- rpi-scripts.tar.gz downloaded (https://axrt.org/download/aros/rpi/rpi-scripts.tar.gz)

1) Install prerequisites:

sudo apt install git gcc g++ make gawk bison flex bzip2 netpbm autoconf automake libc6-dev liblzo2-dev libpng-dev gcc-multilib byacc python3-mako cmake yasm curl nasm

2) Clone sources

cd &lt;project-directory&gt;
git clone https://github.com/aros-development-team/AROS.git --recurse-submodules

3) Extract rpi-scripts.tar.gz. Copy all files into your project directory so that you have:

AROS (the directory with cloned sources)
fix-dotdot.py
rebuild.sh
recreate-sdcard.sh
run-qemu.sh
update-sdcard.sh

4) Run ./rebuild.sh. Select option 1) toolchain-core-aarch64

This will execute process of building a cross-compiler. During this process packages will be downloaded from Internet. This process can take up to 2 hours. If there are some missing dependencies, install them with 'sudo apt install' and restart this step.

5) Run ./rebuild.sh again. Select option 2) core-raspi-aarch64

This will build system files for 64-bit Raspberry Pi AROS. This process can take around an hour.

6) Run ./recreate-sdcard.sh

This will create an sdcard.img file with contents of previous step.

7) Run ./run-qemu.sh

This will start QEMU with SD card image and ROM images. It will boot into AROS.


=====32bit=====

Ubuntu VM approach to compiling [http://lallafa.de/blog/2013/06/building-aros-hosted-for-raspbian/ Linux hosted AROS June 04, 2013]

 ../AROS/configure --target=linux-armhf  --enable-includes=/usr/arm-linux-gnueabihf/include --x-includes=/usr/arm-linux-gnueabihf/include --x-libraries=/usr/arm-linux-gnueabihf/lib

arm-elf- is symbol-linked to arm-linux-gnueabi- (arm-linux-gnueabi- is more correct in this case, because it's going to be compiling the ARM AROSBootstrap for ARM Linux)

*armel - many of the &quot;android&quot; machines require since the entire OS is made for soft float VFP. 
*armfp - Efika MX target, Raspberry PI, EfikaMX, Pandora and virtually everything (VFP)

Keep in mind it's possible to start hardfp AROS hosted on softfp system, though, as long as no calls between AROS and host require floating point parameters. NOTE: hardfloat objects *cannot* be linked with softfloat objects - they have a different ABI.

Just keep in mind the arm nightly build machine is quite complex beast. It needs the x86_64 host compiler to compile AROS tools. The arm version is built every night using gcc-4.6.2 crosscompiler (built together with AROS) and successfully builds armel and armhf linux hosted targets.

*needs an AROS code compiler for ARM target 
*as well as unix compiler for ARM linux host (would be best to have both softfp and armhf, we have softfp only now) with full set of libraries and includes.

with—disable-crosstools  $AROS_CC  is always a wrapper around $KERNEL_CC  ?  If  so,  this  is  wrong for some ports. This can break Darwin, Windows and Android port. 
Yes,  Android  port  will  build.  And  even  work. But it's not good because  the  port  will  not  be ABI-compatible with other ARM ports. Android's ABI is different from GNUEABI. For example:

&lt;pre&gt;
enum test {foo, bar};
enum test testvar;
&lt;/pre&gt;

sizeof(testvar)  will  be  equal  to sizeof(int) in GNUEABI (Linux and AROS)  and  sizeof(short)  on  Android. This affects linking objects from static linklibs, for example.

Previously everything worked because $AROS_CC was a wrapper on top of $HOST_CC. And a real crosscompiler was used on non-ELF hosts.

Android is the same. $KERNEL_CC is incompatible with AROS.

compiler=kernel  is  appropriate _ONLY FOR CODE WHICH RUNS ON HOST OS_ (or  barebone  hardware,  if  we  talk  about  native).  This includes bootstraps,  their  linklibs, and host-side dynamic libraries (Windows makes extensive use of them because of architectural considerations.

No single AROS object should be compiled with this setting. $KERNEL_CC is really compatible with AROS *ONLY IN LINUX-HOSTED* and no more. On other systems (Darwin, Windows,  Android) this is not true any more, and compiler=kernel is never going to work.

If  you  want  to  compile your AROS module against host OS includes, append  the  following  to  USER_INCLUDES  (or  USER_CFLAGS,  this  is effectively the same):

 -isystem $(GENINCDIR) $(KERNEL_INCLUDES)

$(KERNEL_INCLUDES) expands to:

 -isystem  &lt;your_os_includes&gt;  -isystem  &lt;host_OS_gcc_private_includes&gt;
 -nostdinc

This makes AROS compiler adhering to host OS APIs.

If you want some preprocessor symbols based on what your host OS actually is, add something like -DHOST_OS_$(AROS_HOST_ARCH).

Why is there $(GENINCDIR) at all? Because host OS has its own libc includes, which would conflict with AROS ones. And the host OS libc is not binary-compatible with AROS one.

Why doesn't Windows-hosted port use $(KERNEL_INCLUDES) ? Because WinAPI includes conflict with AROS ones in fundamental typedefs, like WORD, BYTE and BOOL. It's almost impossible to deal with this in any other way than rewriting WinAPI definitions using AROS types.

Building under centos 6.3 (i386) currently, and AROS creates the toolchain itself. haven't yet committed the necessary changes but &quot;./configure --target=raspi-armhf&quot; is enough to start, then &quot;make arosboot-raspi&quot; will generate arosraspi.img (containing the bootstrap, kernel.resource, and exec.library) as well as arosraspi.rom (containing all the other essentials components such as dos, graphics etc).  It will also copy over a config.txt file to make the raspi bootstrap code load the correct kernel, and a cmdline.txt that enables exec debug output.

*armel = typically Debian 6, Ubuntu Maverick, Android, 
*armhf = typically Debian 7, Debian 8, Ubuntu Precise,

Cross-compiling Ubuntu ARM softfp 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armel' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armel] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armel.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabi libx11-dev:armel libsdl-dev:armel
&lt;/pre&gt;

&lt;pre&gt;
 ./configure --target=linux-arm --x-includes=/usr/include \
             --enable-includes=/usr/arm-linux-gnueabi/include
&lt;/pre&gt;

Cross-compiling Ubuntu ARM hard-float 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armhf' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armhf] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armhf.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabihf libx11-dev:armhf libsdl-dev:armhf
&lt;/pre&gt;

&lt;pre&gt;
    ./configure --target=linux-armhf --x-includes=/usr/include \
                --enable-includes=/usr/arm-linux-gnueabihf/include
&lt;/pre&gt;

Now, the AROS build is configured properly and all you need to do is:

 make


==Build==

===64bit===

[https://github.com/aros-development-team/AROS/blob/7016ce28bfdb754182edb16011c98faaf5413c29/arch/aarch64-raspi/boot/mmakefile.src#L180 boot makefile] 


===32bit===


# download/checkout the source someplace, e.g. /build/AROS-Src/
# make a directory to store external sources AROS downloads, e.g. /build/Ports
# make a build directory, e.g. /build/aros-raspi-armhf
# cd into the build dir, configure, and then run make -:

&lt;pre&gt;
&gt;cd /build/aros-raspi-armhf
&gt;/build/AROS-Src/configure --target=raspberrypi-armhf --with-serial-debug --enable-ccache --with-portssources=/build/Ports
&gt;make
&gt;make arosboot-raspi
&lt;/pre&gt;

then copy the files from /build/aros-raspi-armhf/bin/raspi-armhf/AROS/ onto an sdcard, and download/copy the Raspi firmware files onto it.

You should then be able to boot the sdcard on your RasPi.

The current W.I.P tree to svn. it can be built as follows ..
&lt;pre&gt;
./configure --target=raspi-armhf
make arosboot-raspi
&lt;/pre&gt;

That will generate arosraspi.img, arosraspi.rom and config.txt in bin/raspi-arm/AROS - so either copy just those files to a fat formatted SD card (with the firmware files on), or copy the whole contents of the AROS folder.

NB - if you have a Linux/other install, backup the existing config.txt first

arosraspi.img contains the bootstrap (which has very basic mailbox code, framebuffer/gpio init, and console &quot;emulation&quot; via code pinched from our libbootconsole), kernel.resource, and exec.library

arosraspi.rom contains all the other components needed to boot AROS.

The config.txt file will tell the RasPI bootstrap to load the arosraspi kernel and ramdisk (rom).

the bootstrap has minimal mailbox code, planning on adding either a resource or library that driver/app code will use to access it (likewise for GPIO)


Help building AROS hosted on Linux ARM

Was looking a way to use more my Handheld ARM based called Pyra (Dragonbox Pyra) an ARM (Omap5 cpu with 4GB ram) linux based machine (Debian Buster v10 with kernel 5.6.19 adapted) and have a try to compile the latest Aros sources by Deadwood directly on this device.
Compilation stops after build libpopupmenu.a and trying to build libatomic have this error:

&lt;pre&gt;
    Configuring build in bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic
    configure: WARNING: unrecognized options: --disable-nls, --without-x
    checking for --enable-version-specific-runtime-libs... no
    checking for --enable-generated-files-in-srcdir... no
    checking build system type... arm-unknown-linux-gnu
    checking host system type... arm-unknown-aros
    checking target system type... arm-unknown-aros
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for arm-aros-strip... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-strip
    checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
    checking for gawk... no
    checking for mawk... mawk
    checking whether make sets $(MAKE)... yes
    checking whether make supports nested variables... yes
    checking for arm-aros-gcc... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-gcc
    checking whether the C compiler works... no
    configure: error: in /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic':
    configure: error: C compiler cannot create executables
    See config.log' for more details
    make[2]: *** [mmakefile:4489: /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic/.configured] Error 77
    [MMAKE] make --no-print-directory TOP=/media/farox/pyra2/arosbuilds/toolchain-core-armhf-build SRCDIR=/media/farox/pyra2/arosbuilds/AROS CURDIR=tools/crosstools/gnu TARGET=tools-crosstools-gcc-libatomic-configure -s --file=mmakefile tools-crosstools-gcc-libatomic-configure failed: 512
    [MMAKE] Error: Error while running make in tools/crosstools/gnu: No such file or directory
    make[1]: *** [Makefile:361: linklibs-libatomic] Error 10
    make: *** [Makefile:183: crosstools] Error 2
&lt;/pre&gt;


looking at config.log on arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic

found that arosbuilds/toolchain-core-armhf/arm-aros-ld: cannot find -laeabi
so do make linklibs-aeabi-arm-quick
and the missing lib was built.

now the next stop is at
fatal error: bits/libc-header-start.h: No such file or directory
and
fatal error: sys/cdefs.h: No such file or directory
in many places so after checking that have this missing include files i have noted that my include path is a bit different, standard searching path is /usr/arm-linux-gnueabihf but in my system is /usr/include/arm-linux-gnueabihf
so if i add my path to some mmakefiles compilation goes on....but is a better way to add this path to avoid every mmakefiles to be changed?

fixed with adding
-I/usr/include/arm-linux-gnueabihf
to where is missing on mmakefiles like
USER_INCLUDES := -isystem $(GENINCDIR) -I/usr/include/arm-linux-gnueabihf $(KERNEL_INCLUDES)

P.s. I have changed many mmakefiles and have at least compiled (after many hours) the toolchain doing make every time in arosbuilds/toolchain-core-armhf-build (also have to disable making tests under cplusplus but don't remember the directory ...) but ask an help to have an automated way to correctly build without modify mmakefiles.


Last time built armhf target was around 2 years ago. At that point built is via cross-compilation from linux (ubuntu 22.04) using linux armhf crosscompiler (this can explain the path differences you are experiencing) as well as using AROS gcc cross-compiler in version 6.5.0 (build with option 21) in rebuild.sh). Since then AROS GCC has been updated to 10.5.0 and don't believe anyone tried to build the armhf target again.

My suggestion would be to downgrade GCC to 6.5.0 (via editing AROS/config/gcc_def file) and try to first build using cross-compilation from x86_64 linux. Once that works, you will have a &quot;template&quot; to compare to native compilation under arm linux.


Thanks for your suggestion...but think the toolchain with GCC 10.5.0 is compilable if i found a way to pass the path of my system to the script that build (option 21 on rebuild).
The other only changes are (but don't know where to modify...) is to add the build of libaeabi and disable the building of some tests under cplusplus that use exceptions and is not supported under ARM. try to crosscompile with my Linux amd64 PC.

For paths look into core-linux-armhf/bin/linux-armhf/gen/config/target.cfg. A number of build-wide variable is set there containing paths to local build system. These variables and the target.cfg file are generated by AROS ./configure script.

Thanks compilation now go forward...changed target.cfg under &quot;toolchain-core-armhf-build/bin/linux-arm/gen/config&quot; and do make on &quot;toolchain-core-armhf-build&quot; dir.

Need to find where to enable build libaeabi.a so can build the entire toolchain with option 21 of rebuild.sh


Found something that looks like libeabi in AROS/arm-all/arm-aeabi/mmakefile.src. Try adding a third line there:

#MM- linklibs-armhd : libklibs-aeabi-arm

Don't remember needing this library. Possibly the 6.5.0 GCC somehow does this while 10.5.0 is missing this.

Try adding this line (and the variant &quot;linklibs-armhf&quot; instead of hd) but it did not solve the automatic building of the missing lib. I must do &quot;linklibs-aeabi-arm-quick&quot;.
Anyway after have build the aeabi lib i succefully built the toolchain (after many hours...). Smile

To test I restarted from selecting option 21 (on rebuild.sh) but after many hours i get the same error of the kernel includes not found...maybe i need to modify the configure script for my case.

With the toolchain built i try to build the core-linux-armhf (DEBUG) (option 22) but after a while it stopped with
&quot;cannot find -laeabi &quot; so i made it built manually...and now i can continue compiling...i'll let you know if all goes ok.


== Hardware ==

===64bit===


====BCM2712====

With the Pi5 

Broadcom VideoCore 7 vc7 is an integrated GPU with 12 cores and up to 800 MHz clock. VideoCore VII is capable of OpenGL ES 3.1 and Vulkan 1.2. The driver support for the Raspberry Pi continues to build upon the [https://lore.kernel.org/dri-devel/20230928114532.167854-1-itoral@igalia.com/ open-source V3D driver] stack within [https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450 Mesa] hopefully be merged for Mesa 23.3. x265 HEVC accelerated untested, x264/h.264 and VP9 cpu only. 

*Raspberry Pi M.2 HAT+ Expansion Board 
*Geekworm X1001 PCIe to M.2 Key-M NVMe
*Geekworm X1003 PCIe to M.2 HAT NVMe SSD PIP Board for Raspberry Pi 5 
*Pineboards Pi Hut HatDrive! M.2 HAT 2024/V4 
*Hat+ Gen2 Gen3 Nvme
*GeeekPi 52Pi N04 for Raspberry Pi 5 NVME M.2
*


*2024 RPI AI HAT    - Hailo  20TOPs  no LLMs 
*2026 RPI AI HAT+ 2 - Hailo  40TOPs  slightly better? 


[https://www.raspberrypi.com/documentation/accessories/camera.html Cameras for Pi]
*Raspberry Pi camera module, the V3 with Sony IMX708 back-illuminated CMOS 12 Megapixel sensor
*Raspberry Pi Camera Module V2 – 8MP Sony IMX219 Sensor
*Raspberry Pi camera Rev 1.3, 5MP 1080P OV5647 image/video module, 2592 x 1944 pixels


====BCM2711====

With the Pi4 an ARM a72 cpu is about x3 times the size of an a53 in the Pi3 

the 2711b line used more power when idle, compared to the 2711c 

*2018 Raspberry Pi PoE HAT Power Over Ethernet Hat - design issues 
*2020 Raspberry Pi PoE+ HAT Power Over Ethernet Hat Pi3b+ Pi4 only - better design 
*Waveshare PoE HAT (B) with cooling fan for Raspberry Pi 3B+/4B 802.3af PoE 

*[https://github.com/axizo-pi/V3DLib vc6 V3D 4.2] is derived from [https://docs.broadcom.com/doc/12358545 vc4], but it is [https://docs.mesa3d.org/drivers/v3d.html significantly different] 
The QPU pipeline stays mostly the same, you still have an add ALU and a multiply ALU and it can issue two ALU OPs per cycle. There is still 4 SIMD lanes, interleaved over 4 cycles.
The instruction encoding for the QPUs is different, but the core instructions are the same.

Instructions for packed 8 bit int math has been dropped, along with most of the pack modes.
Instructions for packed 16bit float math has been added (2 floats at in a single operation)
With vc5/vc6, you write two packed 16f value to the tilebuffer (or four writes of 32f, if you are using the rgba32f framebuffer). And there is a handy vfpack operation which allows you to pack two f32s into a single 32bit value in a single instruction. You can vfpack directly into the tile buffer register.

the multiply ALU can now fadd, so you can issue two fadds per instruction. the add ALU has gained a bunch of new instructions 

the A and B register files have been merged. You still only get an A read and a B read per instruction, but they read from one big register file (which means the underlying memory block has gone from two sets of &quot;one read port, one write port&quot; to one &quot;two read ports, one write port&quot; block)

The theoretical max FLOPs per QPU remains the same at two per cycle, other than the bump from 400mhz to 500mhx but it looks like a lot of effort has been put putting those theoretical FLOPs to better use. 
*vc4 could run one or two threads per QPU. When you ran in two thread mode, the available register file halfed to 32 registers.
*vc5 added a four thread per QPU mode, with 16 registers per thread.
*vc6 doubled the size of the register file. You could now use all 64 threads in two thread mode and 32 registers in for thread mode. Single thread mode was removed, you always have at least two threads.

With the threading improvements, the QPUs should spent much less time idle waiting NOPs for memory requests. Most of the design changes have gone to improving the fixed function hardware around the QPUs. A fixed function blend unit has been added, which should reduce load on the QPUs when doing alpha blending. hope software blending is still possible 

The tile buffer can now store upto 4 render targets (up to 128bits per pixel, so if you are using 4 32bit render targets, you can't have a depth buffer)

A MMU, allowing a much simpler/faster kernel driver.

Many more texture formats, framebuffer formats.

h264/x264 as Pi3 

All the features needed for opengl es 3.0 

H.265 / HEVC decoder is a HEVCv2 Main 4:4:4 10 design supporting bitstreams up to profile 5.1
HEVC hardware decode supports 4kp60, 10-bit. Audio output is pretty much unchanged, but the HDMI audio channels now support 8x192kHz bitrates 

Each ALU typically have 2 floating point operators, and as you pointed out in a earlier post videocore 6 is no exception, with both a multiply and additive floating point operator. Thus theoretical GFLOPs are calculated with both operators in mind. That is what the 2 in my formula represents, and is common across any modern programmable shader, whether you calculate Nvidia, AMD, Intel, Boardcom or any other company's GPUs. Total ALUs * 2 * GHz clock = GFLOPs, In the case of Raspberry Pi 3, it's 24 ALUs * 2 operators * 0.4GHz = 19.2GFLOPs
If the Videocore 6 does indeed only have 16 ALUs (16 * 2 * 0.5GHz), you'd have only 16GFLOPs but they are better utilised 

Possible maximum performance 
&lt;pre&gt;
VideoCore IV @ 250MHz: 250 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 24 Gflop/s
VideoCore IV @ 300MHz: 300 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 28.8 Gflop/s
VideoCore VI @ 500MHz: 500 [MHz] x 2 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 32 Gflop/s
&lt;/pre&gt;

Faster LPDDR4 memory.


====BCM2837==== 

With the Pi3 
* Broadcom BCM43438 chip provides 2.4&amp;nbsp;GHz 802.11n wireless LAN, Bluetooth Low Energy, and Bluetooth 4.1 Classic radio support, 3B+ [https://github.com/aros-development-team/AROS/commit/afa5bc0bb17d5dd06bcfdbac00853a3799ca8d76 LAN7515] 

The overclock ability has diminished with each chip version as the energy usage has increased. BCM2837 is one of the warmest yet and benefits from active fan cooling if all four cpu cores are in use for a short while. Video playback maybe affected due to the lack of custom support in the GPU with Aros. 5 V / 2.4 or 2.5 amp power supply recommended if all four cpu cores are running, else throttling (cpu slowdown) might occur. 

[https://github.com/hermanhermitage/videocoreiv/wiki/VideoCore-IV-Programmers-Manual Dual VDP] and scalable QPU in [https://docs.mesa3d.org/drivers/vc4.html VC4] and x.264/h.264 accelerated untested only and VP9 on cpu or neon help 


ARMv8-A has [https://developer.arm.com/documentation/102412/0100/Privilege-and-Exception-levels privilege levels] where userspace typically runs at ‘EL0’, the kernel at ‘EL1’ or ‘EL2’ and the firmware at the highest level ‘EL3’. 


===32bit===

=== Core Kernel ===


====BCM2708(family)====
which includes the [http://elinux.org/RPi_Hardware BCM2835] (ARM1176JZF-S 700&amp;nbsp;MHz CPU + VideoCore IV GPU + up to 1GB RAM)

*Framebuffer (fb) using mailbox 
*IRQ scheduler, etc 
*Arasan based SD Card controller 
*Synopsis DesignWare USB 2.0 OTG controller [http://networkdirection.net/index.php?option=com_content&amp;view=article&amp;id=106:rasperry-pi-usb-controller&amp;catid=45:raspberry-pi&amp;Itemid=54 Unofficial DOCS pdf],  [dwc_otg.c FreeBSD], [], [https://www.riscosopen.org/viewer/view/mixed/RiscOS/Sources/HWSupport/USB/Controllers/DWCDriver/ RiscOS USB Driver], [https://www.riscosopen.org/forum/forums/5/topics/878 RiscOS USB Discussion], [https://www.riscosopen.org/forum/forums/11/topics/1893 Other USB RiscOS], [http://plan9.bell-labs.com/plan9/index.html Plan9 Miller's usb] http://plan9.bell-labs.com/sources/contrib/miller/, [https://github.com/Chadderz121/csud CSUD driver], 
*[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf SMSC 9512] USB LAN/Hub chip 
*CMOS RAM 
*VCHIQ port which sends messages to the GPU e.g. for mouse, keyboard, audio on HDMI, etc 
*Audio Driver 
*Serial Peripheral Interface Bus (SPI) 
*[http://www.susa.net/wordpress/2012/06/raspberry-pi-pcf8563-real-time-clock-rtc/ I2C registers]
*I2S 
*Universal Asynchronous Receiver Transmitter (UART) 
*[http://elinux.org/RPi_BCM2835_GPIOs GPIOs] and [http://www.adafruit.com/blog/2012/08/17/broadcom-bcm2835-peripheral-memory-map-and-gpio-alternate-use-chart-piday-raspberrypi-raspberry_pi/ Alternative view of GPIO]

BCM2836 
* For Pi B+, PI 2 and Pi 3 SMSC LAN9514 chip adding 10/100 Ethernet connectivity and four USB channels to the board

*[http://www.andrewscheller.co.uk/rpi_pcb_modules.html PCB], [http://elinux.org/RPi_Low-level_peripherals Low level features],


 Implemented so far... 

# Modify the configure system so that it correctly builds for the arm hardware float raspi target.
# Implemented the bootstrap to load the aros modules and prepare the arm to jump into them. Reworked the x86 console support so that parts can be stolen for raspi to use since t has no basic functionality to output to the display.
# Implemented a kernel.resource to prepare the raspi for running aros and provide the low level api calls to expose available resources and allow exec, etc function.
# Implemented serial debug support
# Implemented the exec (and kernel) functionality required to make multitasking work (and interrupts, exceptions, syscalls, etc)
# Implemented a timer.device to utilise the hardware timers.
# Implemented a very basic gfx driver to expose the hardware's framebuffer.
# Implemented an SD-Card driver for AROS which presently only supports the raspi's chipset but can easily be modified to support all sd-card hardware and media.
# Fixed the fat filesystem support in AROS so that it can boot on RasPi's normal SD-Card setup. The &quot;rom&quot; image files needed use a different filename than the default linux, etc images so can be easily installed without harming the existing files - you only need to change the loaded images in the config file to get aros to boot.
# Updated the build scripts to automatically download the necessary raspi firmware files and wrap it all up so that you can simply extract the archive to a fat formatted sdcard and boot it on the raspi without having to get anything else.
# fix everything in contrib and ports to build for raspi (needs proper testing/fixes but allows every component to actually compile at least, including owb) + numerous other fixes to get things working on arm/raspi ..


Improvements...

# Implement a USB chipset driver &quot;OR&quot; finish the existing one [https://github.com/aros-development-team/AROS/commit/c07d13c724f944674be5db54fc6a71ee72a01809 usb otg] - the current code is mostly a skeleton that should initialise the chipset and then needs relevant code to support the different transfer types. It also has the &quot;virtual&quot; hub code in place to represent the raspi's USB port (from poseidons p.o.v) 
# Implement a driver for the USB NIC (a few weeks - depends on USB above) 
# Write an [https://github.com/aros-development-team/AROS/commit/d55d0f74d20b769bbb8c8d386e5c1d7a9154f05a audio driver] (a few weeks - independent of USB) and [https://github.com/aros-development-team/AROS/commit/e93a4c245f27a87c9c4c1d39206694b39059998a HDMI]
# fix syscall bug in the current raspi kernel code
# Graphics depend on having a decent &quot;bcmdma.resource&quot; implemented as to use the cpu's dma engine. The sd card driver needs to use it for transfers to/from the controller - and the gfx system needs to use it for &quot;blitting&quot;. 
# [https://github.com/aros-development-team/AROS/commit/4019d84e4975d4dad987a12d57fe108f5ac048e6 Improve the gfx driver], [ vc4gfx HIDD] add [http://dri.freedesktop.org/wiki/VC4/ Gallium3D support] 
# [https://github.com/aros-development-team/AROS/commit/b13905b3e8e45b089f520b44692c81affddd066f Improve] the [https://github.com/aros-development-team/AROS/commit/3a876755c070f5c73c4f53c7f4d35b4f923088b9 sdcard] device driver  - which is also pretty basic but should work with most cards, rework it to also support pci, etc. sd card interfaces on x86 
# The current code using very rudimentary access to the gpio interface - so that should be implemented as some resource for other components to access, as-well as the i2c interface exposed over the gpio interface. that should have a hidd class implemented which uses the gpio resource to communicate.


 Boot up typical for most other OSs before the open sourcing of many binary blobs from 2017 onwards 

On power-up, the rpi [http://www.open.com.au/mikem/bcm2835/ BCM 2835] [https://github.com/hermanhermitage/videocoreiv VideoCore4] GPU, not the ARM CPU, is in control, and the SD card slot is the only peripheral device with power. The firmware burned into the BCM2835's VideoCoreIV GPU PROM requires a DOS-style partition table; a FAT-formatted first partition; and the freely redistributable but closed sourced Broadcom files “bootcode.bin” and “start.elf” in that partition.

The boot sequence carries out several pre-boot tasks

*On powering of the rpi, the GPU reads and executes bootcode.bin, which then loads start.elf 
*The GPU loads the “start.elf” file, eventually, into the L2 cache and then executes it
*configures the memory split for the CPU and GPU
*reads and parses “config.txt” from the same partition on the SD card and applies the settings (like a PC’s BIOS settings)
*loads the “kernel.img” file, again from the same partition
*activates the CPU to begin executing the loaded kernel image

The CPU/GPU memory split is hard-coded into start.elf, so Broadcom provides three start.elf images, to give 32M, 64M, or 128M to the GPU for multimedia performance, and the remainder to the CPU.

RPi uses [https://github.com/raspberrypi/firmware some closed source loaders] and at some point it loads a binary blob named &quot;kernel.img&quot; at 0x8000, at that point there would be a rudimentary Aros alive. If one wants to use the SD-card then there would have to be a driver for the interface and a fat filesystem handler (SD-card has to be formatted to fat filesystem)

Boot code and kernel are now linked together and made into that binary blob, just for starters. Raspberry Pi uses [http://kernelnomicon.org/?p=133 u-boot] and [http://kernelnomicon.org/?p=138 UBoot] as bootloader, there's already some code in the Efika MX port for that. UBoot is a native bootloader and not just for the raspberry pi, it loads after start.elf.

You can find Efika MX port from arch implementations, some hacking is needed for the mmakefile.src'es as iit dates back to before the Aros crosstool era or else you get some weird errors while building. You also need to code the bootstrap and serial handling.

At the moment it seems that a fastest route for the native build would be to make one binary blob without using the package system. Raspberry's memory layout is pretty simple and if the implemented u-boot doesn't support loading other modules 

&lt;pre&gt;
?          - alias for 'help'
mtest      - simple RAM test
autoscr    - run script from memory
base       - print or set address offset
bbm        - BBM sub-system
bdinfo     - print Board Info structure
boot       - boot default, i.e., run 'bootcmd'
bootd      - boot default, i.e., run 'bootcmd'
bootm      - boot application image from memory
bootp      - boot image via network using BootP/TFTP protocol
cmp        - memory compare
coninfo    - print console devices and information
cp         - memory copy
crc32      - checksum calculation
echo       - echo args to console
fatinfo    - print information about filesystem
fatload    - load binary file from a dos filesystem
fatls      - list files in a directory (default /)
go         - start application at address 'addr'
help       - print online help
iminfo     - print header information for application image
itest      - return true/false on integer compare
jade       -
loadb      - load binary file over serial line (kermit mode)
loads      - load S-Record file over serial line
loady      - load binary file over serial line (ymodem mode)
loop       - infinite loop on address range
md         - memory display
mm         - memory modify (auto-incrementing)
mtest      - simple RAM test
mw         - memory write (fill)
nfs        - boot image via network using NFS protocol
nm         - memory modify (constant address)
pci        - list and access PCI Configuration Space
ping       - send ICMP ECHO_REQUEST to network host
printenv   - print environment variables
rarpboot   - boot image via network using RARP/TFTP protocol
reset      - Perform RESET of the CPU
run        - run commands in an environment variable
saveenv    - save environment variables to persistent storage
saves      - save S-Record file over serial line
setenv     - set environment variables
sleep      - delay execution for some time
tftpboot   - boot image via network using TFTP protocol
USB        - USB sub-system
usbboot    - boot from USB device
version    - print monitor version
&lt;/pre&gt;


And there is one more thing about modular ports. In order to actually implement this, your bootstrapping environment should provide the ability to load several files. On PC this is provided by GRUB2. on CHRP you can read filesystem via OpenFirmware, and Sam's Parthenope relies on modified u-boot. If your bootstrap allows to load only a single file, then you stuck with monolithic kickstart. By the way...  u-boot allows not only to boot up a single uImage or zImage, it also allows to write client programs AFAIK. With this approach, you actually can write modular bootstrap for ARM AROS using unmodified u-boot.

Most used [http://www.compulab.co.il/workspace/mediawiki/index.php5/U-Boot_quick_reference uboot options] are fatls usb 0:1,

the reason behind INTB_KERNEL is to allow use of the standard Exec function AddIntServer() to add interrupt handlers for
hardware drivers etc. AmigaOS never used it for abstract hardware drivers. AmigaOS  routed  only  raw  hardware IRQs there. Their assignment was hardcoded. As well as number of them. Actually on AmigaOS every bus has its own interrupt subsystem. For example PCI bus. PCI interrupts on Amiga are routed to a single exec interrupt.  1:1 relationship between CPU  and hardware interrupts is present only on PC.

IMHO we miss things like AddInterrupt/RemInterrupt methods on our PCI subsystem's device class.  PCI bus class should map these methods to whatever is appropriate. This is how it is done on AmigaOS and friends. When these are implemented, raw kernel.resource API will be needed only for several PC-specific drivers with hardwired resources. Exec IRQs are real IRQs only on Amiga hardware. On other machines they can be emulated where appropriate (VBlank is a good example). kernel.resource is meant  to be different, its IRQs are hardware-agnostic, they are plain &quot;Hardware IRQ number X, whatever this means&quot;. They are low-level actually, and meaningful only in the context of a particular system.

Was that not the transition from irq.hidd to kernel.resource? No.  A long time ago there was another hacky bit named INTB_TIMERTICK. It was &quot;abstract timer interrupt&quot;, used by timer.device. It was the same as VBlank, but with larger frequency. I removed it, because kernel.resource API was a cleaner way to access this interrupt. Furthermore, there can be more than one timer in the system. Thinking about bringing back timer HIDD definitions again. hpet.resource is a bad idea.

Can someone please enlighten me a little on how the scheduler is meant to work?
 
Poseidon.library creates its &quot;Poseidon Event Task&quot; during RTF_COLDSTART -&gt; then calls Wait(), and ends up in limbo because wait disables interrupts (used for the scheduler heartbeat), and basically waits forever because the sigbit is never set, since krnSwitch doesn't switch the task unless TF_SWITCH is set, and no codepath run during this seems to set it?? TF_SWITCH does not disable/enable switching. This flag just enables to run user-supplied hook when the task is being switched away. It is completely safe to call Wait() in Disable()d state. Doing this actually temporarily breaks this state. IDNestCnt gets remembered in struct Task, then next task is selected, and its IDNestCnt is restored in sysbase (see kernel_scheduler.c). If there are no other tasks, then your cpu_Dispatch() should enable interrupts on the CPU and enter idle mode. See x86 implementation for good example.

You miss what happens next...
 1. KrnSwitch() saves context of your task, saves IDNestCnt (core_Switch() and cpu_Switch()), then drops into cpu_Dispatch().
 2. cpu_Dispatch() calls core_Dispatch. Then two cases are possible:
 2a. There is a READY task. It is picked up, its IDNestCnt is restored in SysBase, then cpu_Dispatch() needs to restore registers and exit. The next task is run.
 2b. There are no READY tasks. core_Dispatch() returns NULL. In this case your cpu_Dispatch() should enter idle loop. It should just enable interrupts on the CPU and put it on halt. This allows it to process hardware interrupts. Eventually some of your interrupt handlers wakes up your task and puts it into READY list.

My heartbeat interrupt has been slowed atm to help debugging - but it never actually gets a chance to fire because of the Wait() disabling interrupts. Perhaps you have forgotten to enable interrupts in your idle loop.

There is a change in the format of AROS executables. Until now we were using Elf RELocable files which are usually used as intermediate object files. We had them for various reasons, one of them was how AROS files were built in the past. That days we had no real aros cross compiler and the option to embed relocation data in unix executables (or in executable files in general) was rather new and not every linux/unix system had it. Therefore we have decided to use intermediate files. Although it was somehow working (and it is still working :-)), it has some drawbacks. Therefore decided to introduce real Elf EXEC types, in first turn implemented on ARM target with option to expand in future to all other AROS architectures.

The first patch was pretty easy and appeared to work somehow. It generated nice executables with embedded relocation info. Not only that, it also removed all global symbols adjusting relocation data to be relative to the beginning of the sections. That move reduced number of symbols in each executable significantly (depending on the file between 20 and 80% of all symbols could be removed). The only symbols that stayed in the file are local ones - due to the nature of the patch wasn't able to remove them since we have not seen them in the symbol hash table.

The patch didn't worked though. The files were relocated, AROS kernel loaded, but it crashed very early. What happened? Well, the nature of ARM relocations happened :)

Most of the relocation data on all machines is rather simple. Relocation can be absolute or pc-relative, sometimes the offset has to be bit shifted. On ARM v7 there is another one. There, when one wants to load an address of function/variable into register a combination of two instructions can be used: movw and movt. The first one loads immediate into lower 16 bits of a register while clearing upper 16 bits. The second one loads immediate into upper 16 bits without touching lower halfword. Loading of a pointer into a register looks like this:

        movw r0, #:lower16:label

        movt   r0, #:upper16:label

In this case there are two relocations - one for lower halfword and another for upper. If an overflow of lower 16 bits occurs during relocation process, the upper one should be updated as well. Unfortunately with current patch and with typical ARM executables there is not enough information to perform the calculations.

There are two options - the first one would be to give up and go back to &quot;fake&quot; executables, another one would be to change from REL to RELA relocation info. The latter contains an addend, extra data which can be used to perform all the relocation calculations I need.

Decided for the second option. The patch is already in the works. There is another function for the binutils' bfd backend to perform the final relocation. There can decide what to do with every reloc info, modify data and eventually strip some symbols. An advantage is - at this stage of the linking process have also full access to all local symbols so can change all relocations section relative and eventually strip all symbols from the files. 


 GPU 

VCore developed by Alphamosaic Ltd and now owned by Broadcom. Most of start.elf runs on the GPU.   Placing ALL the userland GPU code in the videocore.hidd isn't going to be a terribly big problem because the code they published is nothing more than a shim that sends data straight to the GPU to execute.

The good news about this is that we only need to write our HIDD using the OpenVG API.   The shim is relatively small codewise and lives in the ARM memory (the actual OpenVG code itself lives in the GPU RAM area and its loaded from start.elf).   That's also the bad news.  Our driver has to translate AROS video calls to OpenVG calls, for most tasks it should be easy, for some, not so much.  It's still probably less difficult and less work, than controlling the GPU directly.

The other good news is that anything done through OpenVG happens on the GPU, its truly accelerated.   It also has some nice font functions, meaning we can lead into an accelerated text mode later.

Basically, AROS resets or locks up when it tries to use AROS_ATOMIC_INC or DEC.  If I comment out the byte/word operations in the header files and use non-atomic operations, the code works as expected.
 
have read that the L1 cache needs to be enabled to use LDREX and co (which I also read is only meant to be used on multi processor systems with shared memory) - however I am certain this is correctly enabled.

If you are using LREX or STREX, you should have L1 cache enabled, at least on the ARM CPU I work with at work.

L1 cache is enabled by enabling the MMU *AND* setting the C and I bits in the CPU - the C bit is ignored, and the I bit only covers the 16 byte instruction pipeline if the MMU is not enabled.

Can you verify that your assembly is generating LDREX/STREX? From the behavior, it almost sounds like its generating the default Semaphore locked atomics.
 Impossible. There are no semaphore-locked atomics. There are Disable()/Enable()-based ones instead. And there's a special #define AROS_NO_ATOMIC_OPERATIONS in this case, which tweaks Disable()/Enable() implementations not to recurse forever.
 I have tested this on ARMv5 which does not have ldrex/strex, it works fine. On those ARMs there's no way to have real atomics. On other OSes (like Linux) this is done by introducing things like atomic_t, which appears to be a complex structure, holding the value together with accompanying spinlock (implemented using swp).

    #warning &quot;TODO: lookup optimal mmu table settings for raspi memory&quot;
        /* Set up an identity-mapping for all 4GB */
        for(x = 0; x &lt; 4096; x ++)
        {
            pagetable[x] = x&lt;&lt;20 | (0x40002|0x80000|0x010000|0x00C00|0x04);
        }

Shouldn't there be a second loop that sets the 'C' bit in the descriptor for the RAM pages?

Currently, you have TEX=0, C=0, B=1 for all pages (Shared Device).

You should have TEX=0, C=1, B=0 for RAM (Write-Through, Cached)

    So ..
     
     pagetable[x] = x&lt;&lt;20 | 2;

     
    should be enough?

No, for RAM you need to change the '| 0x40' to '| 0x80'

tell dosboot the correct defaults to use

Please don't do this. This bootconfig.c is a deprecated legacy thing. I wanted it to go away completely with time. Instead,  display  drivers  should auto-install themselves during own initialization phase. I. e. detect hardware=&gt;instantiate itself. This   should   make  things way simpler. With this approach you only need  to add the driver into KS image to get the device autobooted. No hardcoded stuff. 
Currently  VESA  and  VGA drivers do this, look there for examples. never rewrote ATI driver because i don't have any test system for it.

they defined a smaller AROSCPUContext than the ExceptionContext - yet reference it as ExceptionContext in other places, and since it hasn't allocated enough storage for ExceptionContext, are corrupting memory/the structure (since the elements that are there don't map 1 to 1 with the exception context).

AFAIK, AROS has been moving in a different direction to this in recent years. It is the job of graphics HIDDs to allocate bitmaps etc. so that they have the most suitable characteristics, including allocating them from GPU RAM where possible. The concept of chip RAM is only for legacy code, and most if not all non-68k platforms should have all system RAM
marked as chip.

BTW, is the video processing code you mention CPU code or GPU code?

Also, IIRC we have support for &quot;external memory allocators&quot;. Perhaps that's what we need for the allocation of GPU RAM through the mailbox.

All hosted and x86 native ports should use proper context formats.

trying to clarify if the vblank handler has to have run by this point to prevent this deadlock. Actually, no. Unless you have installed VBlank handler which should wake up at some point. Without VBlank there will be no quantum count. Consequently, there will be no forced preemption. But the rest will work, and multitasking will be cooperative (switch happens only when current task voluntarily gives up the CPU). Does it depend on the vblank having run before this point? and if yes what does that mean on systems where it might be able to run enough code (e.g. get to this point) before the vblank interrupt has triggered? What is it waiting for? It could wait for timer, in this case you need timer.device working. VBlank is currently needed for exec's quantum counter. In current native ports we have only a single timer, which is served by timer.device. VBlank is simulated by timer.device also. If your machine has two timers, then you can use one of them for VBlank, and another for timer.device, this will simplify things down. VBlank needs to be 50 Hz for historical reasons, many programs use it as cheap timer. I am periodically thinking about making some abstract mechanism to be able to change quantum source (and untie it from 50 Hz), but have no time to come up with something good. Additionally i started disliking timer.device hardcoded design when PC has got many timers (old 8253, APIC, HPET).
Currently i think there should be some low-level entity representing tick source. timer.device should just select the most appropriate source for its units.
The BCM2835 has 4 GPU based timer sources - 2 are used by the GPU, so im using Timer3 for our heartbeat and the remaining one will be free to the system. There is also the less capable ARM timer but that is dependent on the CPU frequency. Very good. You won't need any emulation. Set the heartbeat to 50 Hz and drive VBlank from it. Use other timer for MicroHZ.

Can you use the 'econsole.hook' I make for debugging the Sam460 via the serial port?
It provides a before-anything-else shell prompt on the serial port.  You can then do 'NewCLI' to test your graphics, or use any DOS command in shellcommands.resource.

You should just be able to add econsole.hook to your module list, and use 'econsole' in your bootargs.

So long as you have a working Exec/RawMayGetChar and Exec/RawPutChar, it should work.

Also make sure to add shell.resource and shellcommands.resource for this.

That should have done it.

If you set &quot;#define DEBUG 1&quot; in  arch/all-native/econsole/econsole.c, do you get any additional serial output?

have added it to the build and added econsole to the command line - and can see the bootloader picks up on the emergency bootconsole tag, but I still only get the insert bootable media display?

Im assuming it exposes a fake filesystem that tricks aros into booting?
The contents of which are: ECON:AROS.boot

Way to handle the scheduling code? The implementations I had been following were causing problems, due to cascading interrupts which I cant handle properly in the asm stubs just now (when they break disable etc.) - since it means detecting the interrupted codes cpu mode and getting the correct sp/lr for it, and that's just too tedious for arm.
 
To work around this ive added a system idle task which does nothing - and when the scheduling code has no task to run switches this in and lets it run, thereby allowing the interrupts etc to resume until something does need to happen.
 
Also, by adding accounting code to cpu_Switch() and cpu_Dispatch(), it should allow the system to log idle time correctly (as well as running tasks).
 
have thought of also adding an additional task that never runs, solely to record time spent in IRQ handlers, but I digress..

was under the impression that kernel.resource should *never* be used outside of exec.library. This is a wrong impression.
Michal started designing it because portable nature of AROS does not fit well into exec's API with all its assumptions. So, he started the new, hardware-agnostic kernel API from scratch. Yes, exec sits on top of it in places. But kernel always meant to be open thing. Otherwise it would not exist. 
it wasn't meant to be just used willy nilly by user code - but by lower system components (e.g. exec) so that they could be implemented in a more generic fashion, and the kernel resource itself hide the systems quirks.

Adding new things there perfectly keeps up with our decision to minimize AROS-specific intervention into APIs which can clash with MorphOS or Amiga OS4 extensions. We want at least source-level compatibility there. Binary compatibility on PPC would be extremely cool, but at the other hand we have no maintainer for this, as well as their ABIs splintering. 
It depends on what exactly is being implemented - there's no reason we should have everything crammed into kernel.resource if it doesn't need to be (i.e. if its better suited as a separate component/subsystem in its own right)

The _LE versions are for when you have endian swapping taking place.  If the graphics are the same endian as the CPU, no swapping should occur.  I ran into a similar terminology problem in SDL with a friend insisting that his Radeon 7000 on his PC was big-endian.  It is not, it just uses the same endianness for the graphics card and the CPU so no swapping was necessary.  They were both little-endian.
The _LE versions are because the PixFmts refer to the bitmap data being in big endian format in memory, for which the normal version would need to do endianness conversion before applying the shifts/masks. on this platform it is in _LE in memory also so we don't need the conversion hence using the _LE version of the call). would use _LE (if it's really little endian 16 bit mode).

 
What is the bare minimum needed to implement a framebuffer based gfx driver, with our software handling the rest?

Have tried with just a gfx class that only expose new/dispose/newbitmap - and having an onscreenbitmap used only for the framebuffer itself (with all other bitmaps being chunkybm, and the framebuffer's superclass also being chunkybm), but that alone isn't enough it seems?
You can use workbench/hidds/sm502/ as your example - it is as simple as I could make it.
So, AROS creates the framebuffer bitmap (verified this) -&gt; so surely it should be capable of then rendeing into it? I don't actually create the framebuffer &quot;bitmap object&quot; myself - only as a result of being asked to. The code I currently have on SVN seems to create the framebuffers bitmap object fine, but then crashes in intuitions DisplayDriver callback.  In particular it crashes performing the getattr on the system default pointer. don't expose MEMF_CHIP in an allocatable form so AllocSpriteData was failing (and other code later doesn't check if the values are valid == illegal memory accesses) 

So far have -:

vc_init: queries the gpus memory, and sets up a fake memory handler for it, then adds the bootmode driver and returns saying all is well
vc_gfxhidd:New: sets up some fake syncmodes to test with and creates the real gfx object.
vc_gfxhidd:NewBitmap: checks if its a framebuffer and uses the onbitmap class or uses the chunkybm class otherwise
vc_onbitmap:New; creates a chunkybm object and then pushes the real framebuffer address into it as the buffer,

vc4 had v8adds, v8subs, v8muld, v8min and v8max which operated on four 8bit uint values packed into a 32bit register. Multiplication was in the range 0.0 to 1.0 and addition/subtraction saturated. There were also a range unpacking/packing modes that allowed you to pack and unpack 8bit values into 32bit registers. 

RasPi has to speak to the &quot;operating system&quot; which runs on the GPU itself and request/free memory - it cant directly manage it itself, and so the managed functions were used to wrap these calls.

The Arm and GPU share memory space. The framebuffer is shared. The Arm can write a pixel and it will appear on the screen (through GPU hardware) without flushing/copying being required.

The GPU can composite multiple FB's in real time - so you have a number of surfaces defined which are rotated etc and  composited in real time to the output. Copying can map from the address space of the Arm to the flat space of the GPU which takes some code, but I don't think whole buffers are copied.

The DMA hardware can also access the whole memory space and can perform 2D fills and blits (no blending). This is documented in the peripheral spec posted. The DMA is just an Arm accessible peripheral and can be set up with low latency (e.g. microseconds).
must use a 0xc0000000-based bus address to access SDRAM, yet non-DMA access should go via a 0x0-based bus address. 
For 2D dma, set TDMODE, and the spec says &quot;interpret the TXFR_LEN register as YLENGTH number of transfers each of XLENGTH, and add the strides to the address after each transfer.&quot; so set STRIDE to pitch of the image, the width is XLENGTH and height is YLENGTH. You would fill by not setting the SRC_INC and point source to your fill data.

The DMA cannot see the ARM's L1 cache, so you would map the framebuffer with ioremap_nocache. Depending on where the source data comes from, it may need an L1 cache flush. The DMA can see the L2 cache. Use 0xC0000000 bus addresses when L2 is disabled and 0x40000000 bus addresses when L2 is enabled. (actually just call virt_to_bus and you'll get the right address out).

openGLES/openVG has high latency. Writing to framebuffer then reading it back is very inefficient (e.g. milliseconds). If you can drive it a unidirectional way, just streaming commands at then that is efficient. openVG is not implemented on top of openGLES - it uses the same hardware but as a first class interface

To improve the Gfx driver, we will need a DMA resource implemented so can use to perform DMA operations. The Gfx driver will need this to perform blits.


Actually MEMF_CHIP has to present, for historical reasons.
This has been never fully agreed upon, but in ports i wrote i exposed the whole memory as MEMF_CHIP. The idea behind this is that CHIP is originally the memory where graphics and sound data can be put. On non-Amiga platforms there are no restrictions on this, so the whole memory is CHIP.
Yes, many old software can misbehave with CHIP memory size larger than 2MB. But this actually applies only to m68k AROS which is going to run m68k binaries. In other cases it's quite logical to fix the program when porting.

As to original question: yes, it's enough to have a framebuffer bitmap (one with aoHidd_BitMap_FrameBuffer set to TRUE) and PutPixel routine. It framebuffer can be served by chunky bitmap class, then you can simply create chunky bitmap with your own buffer (see how VESA driver does this). Chunky PutPixel is already there.

struggling to determine what is the correct pixfmt to use for the 24/16/15 bit gfx modes on the RasPi.  AFAIK it uses RGB565, for 16bit but im unsure what shifts etc should go with it? suffice to say Im getting the wrong colors so far lol.

&lt;pre&gt;
redmask: 0x0000F800
greenmask: 0x000007E0
bluemask: 0x0000001F
alphamask: 0

redshift: 16
greenshift: 21
blueshift: 27
alphashift: 0
&lt;/pre&gt;

It should likely be vHidd_StdPixFmt_RGB16_LE

This stuff is a bit confusing.  The &quot;names&quot; of the stdpixfmts are based on the layout in memory,
ignoring endianess. So for example:

ARGB32: will be 0xAA 0xRR 0xGG 0xBB in memory on both big endian and little endian machines.

The shifts and masks OTOH are based on pixel access (ULONG in this case), so differ depending
on whether you run on big endian machine or little endian machine (that's why there's stdpixfmt_le.h and
stdpixfmt_be.h in rom/hidds/graphics/).

With the 16 bit pixel format it's even more confusing, as for example it's impossible on little endian machine
to describe RGB16 with shifts/masks alone. That's why there's vHidd_PixFmt_SwapPixelBytes_Flag.
(RGB16 == RRRRRGGG GGGBBBBB in memory, and for pixel (WORD) access on little endian machine it needs to
be accessed as GGGBBBBBRRRRRGGGG).

The shifts btw indicate how much to shift the component to the left (!) so that it is moved to the highest bit (31).

The aHidd_PixFmt_StdPixFmt you specify will be ignored most of the time, because when the pixelfmt is registered,
the gfx hidd checks if there's an identical pixfmt (shifts/masks/etc., but ignoring pixfmt-&gt;stdpixfmt) already in the system,
and if so, it uses the already existing one and does not create a new one.

In theory it would be better if gfx drivers could simply/only specify a StdPixFmt without all the shifts/masks stuff when the
gfx driver uses pixfmt which matches one of the stdpixfmts exactly. Another possibility would be for gfx drivers to use
HIDD_Gfx_GetPIxFmt(stdpixfmt_gfx_driver_wants_to_use) and then peek shifts/masks from it and fill out a pixfmt
tag list based on that.
15bit very blue/green: Try to pass same shifts/masks/etc. as in 16 bit pixfmt (maybe you think it's using 15 bit R5G5B5
(or swapped) but it's actually still using 16 bit R5G6B5 (or swapped).
 aHidd_PixFmt_StdPixFmt you pass is mostly ignored. It's the shift/masks/etc. that count.
But I would still pass the correct one (_LE) == whatever rom/hidds/graphics/stdpixfmts_??.h uses
in the entry where you have looked up shifts/masks/etc.

Use the shifts/masks/etc. from the entry in stdpixfmt_le.h (if you are running on little endian machine) or stdpixfmt_be.h (if you
are running on little endian machine) that matches the pixfmt that its meant to be.

0xAA,0xRR,0xGG,0xBB on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_BGRA32)

0xAA,0xRR,0xGG,0xBB on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_BGRA32)

it feels like AROS trashes the alpha component, otherwise it should be 8A8R8G8B.

read on the subject suggest its in 1x5r5g5b (x is ignored) to keep 16bit alignment .
 
Suggests to me that wrong shift/mask are being applied - however going by the 16bit versions it all looks correct to me so I am really confused as to what is happening.

The output image looks to have too much green/blue, and very weak red.


 Kickstart 

The  idea  is  to minimize amount of archirecture-specific modules to make the user's  life  easier.  So,  the kickstart was split into 'base' (which  does  not  contain anything machine-specific) and 'BSP' (Board Support Package) which contains all hardware-specific stuff. This  way,  for  example, distribution makers can save up space on CD and  make  CDs with multiple platform support. Different configuration would load the same base with different BSP's.

Next  there  was some part which is entirely missing on hosted. These are   filesystems.  Hosted  ports  do  not need them to boot up, so on hosted   they  are  left  out.  At  the  other  hand,  they  are  also architecture-agnostic.  So  i put them into 'FS' package (standing for 'filesystem').


 USB 

Poseidon  is  one  more  big part. I made it into separate package in order to allow users to omit it if they don't need it (for example, to run  on retro PCs without USB). Personally i have one. Again, Poseidon is  hardware-agnostic (well, there are USB drivers but HCIs are pretty standard).

AFAIK its HCI 1.0 compliant but not familiar enough with poseidons drivers, nor USB, to just hack away at the existing code.  Perhaps once i'm more familiar with the workings I can merge in the changes needed to get it operating but for now I will focus on getting it running.  Also our drivers have known issues so perhaps a fresh set of eyes might shed some light on what is going wrong.

Another interesting question is whether Poseidon can operate on device side. Is it flexible enough? How similar is being a USB host and USB device? think it will need a bit of work on Poseidon's side.  Until then I will force the driver into Host/Master mode in the init code, but leave open device etc to configure the chipset for either's use - and look at trying to add support for working in Device/Slave mode &amp; switching modes once it's up and running.

Actually USBROMStartup is some kind of kludge. Can there be any alternative? Could device drivers be self-installing, like our HIDDs? This would get rid of need to list them in USBRomStartup.

* Model A and B limited to 150 mA per port. 
* Model B+ and Pi 2 introduced configurable 600 mA to 1.2 A support over all ports - anything above that requires a powered USB hub.

Implementing the hardware driver that Poseidon uses to interact with the USB components.

Have code in place to (try) and initialise the USB chipset, and configure host/device mode operation (though AFAICT Poseidon doesn't support device mode). Started to get the &quot;virtual&quot; root hub written for the single USB port so that Poseidon should at least list it correctly in the GUI - and try to interact with it to find peripherals.


The BCM2835 uses a soft IP block from Synopsys’ DesignWare library (DWC), specifically the block is called dwc_usb_2_0_hs_otg_subsystem-ahb_se (“USB 2.0 Hi-Speed OTG Controller Subsystem w/AHB Interface SE”).

There is no public documentation for this, and pretty much zero chance of anyone getting hold of it even with NDA. However, there's a Linux driver written by Synopsys ([https://github.com/raspberrypi/linux dwc_usb]). Specifically directories [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_common_port] and [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_otg].

The Synopsys code is actually under a fairly permissive licence – it's not GPL, it's similar to BSD (’don't sue us if it breaks’ is pretty much the only clause). So this should not be a barrier to porting the code.

The code is really well written, with a nice partition between the work done by the driver (dwc_otg, which is fairly involved, given the host does more work than a conventional EHCI driver), and the interface to Linux (dwc_common_port).

Probably only need provision of relevant changes to dwc_common_port. Other things to consider....

* Provision of necessary headers to get it to compile
* Provision of necessary functions (main issues are wait queues, threads, work queues, tasklets, timers, spinlocks and mutexes (multithreading) )
* Interfacing between USB stack and the driver. dwc_otg/dwc_otg_hcd_linux.c looks like the place to start.

the Linux bits of the headers are only required for the dwc_common_port library. dwc_common_port includes a variety of crypto functions which are not used – it appears to also be used for ultrawideband (UWB) and wireless USB (WUSB) drivers where crypto will be an issue, but it isn't going to be for plain wired USB.

Every USB driver acts as an USB hub as well in order to let Poseidon control the state of USB ports. The code there was reading status of the only USB port in Raspberry's CPU but when changing the status it erroneously deleted some of the status bits, including the port enable one. It was so because those bits in the status register are of a type Read/WriteToClear. It means, if one does not want to change their value from 1 back to 0, one has to actually write the 0 value. Very practical thing e.g. in interrupt handlers, where one reads the interrupt status register to learn what was the interrupt reason, and writes it back to the same register in order to clear the interrupts. 

After fixing that code it turned out that the communication was still unsuccessful. Apparently the USB device was not understanding the host for some reason. That should not happen since the request sent was one of the standard ones implemented by virtually anything with an USB connector, assumed that Poseidon clears the data caches before forwarding the work to the USB drivers but that's the responsibility of the driver itself. 

The USB device responded and acknowledged the transmission! But why were all the request sent after address change failing with timeout? They should not. Once again, address set is supported just by anything. Tried to contact the device at address 0 once again and there it was, still responding properly. The enlightenment came. The bus address for DMA transmissions was, as it is in many bare metal USB implementations, just the pure memory address of the buffer as seen by the ARM cpu. Have &quot;prefixed&quot; it with the real location of uncached RAM and booted AROS once again. 


Trident saw this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

and this:

    Product     : Vendor: Vdr=0424/PID=EC00
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 255
    SubClass  : 0
    DevProto  : 1
    VendorID  : 1060
    ProductID : 60416
    DevVers   : 0200

and even this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

What are these things? The first one is USB hub built in the Raspberry. Thanks to this one the Pi machines (with exception of Pi0 and computing modules) have more than just one single USB port. The second one is the network chip in raspberry, the third one is my USB SD card reader which have just connected to see what happens. AROS tried, of course, to boot from it ;)

So, the first step towards working USB is done. The control transfers are working as you can see above. Next step is to implement bulk and interrupt transfers, having the basics in place. Finally some error handling will be added and USB for Pi will be as complete as the PC version. 

[http://www.raspyfi.com/raspberry-pi-usb-audio-fix/ Issue with USB Audio]


 Audio 

The Pi 4B is the only Pi that can output HD Audio as an HD Audio passthrough bitstream, and it does it over HDMI. It's possible to use the two HDMI output for separate HDMI video and HDMI audio outputs to allow UHD HDR video and HD Audio with non-UHD HDR compatible AVRs. 

The Pi3B+ and earlier will decode to PCM 5.1/7.1 and output over HDMI.  HDMI is the only interconnect that has a standard for carrying Dolby True HD, DTS HD MA etc. as a bitstream - you can't carry it as a bitstream on any other interface.

Pi3 and Pi4 audio jack output derived from 12bit pulse width modulation is relatively poor. For better, choose USB Audio or I2C versions. 

[https://github.com/raspberrypi/linux/tree/rpi-patches/sound/arm audio] and its [https://github.com/raspberrypi/firmware/issues/2 very high speed message passing interface type of thing VCHI] 

The Model B+ added an additional voltage regulator for the audio output and an additional output driver to drive low-resistance loads like headphones. However it is still using pulse-width modulation (PWM), which has a major impact on sound quality

the old Raspberry Pi used a linear voltage regulator to provide the 3.3V to many of the components on the board while the new one uses a switching regulator. Both can perform reasonably well. However switch mode power supplies often show higher noise figures

Analogue audio

Audio over HDMI rev 1.3 &amp; 1.4


 Ethernet 

10/100 BaseT Ethernet RJ45 socket


 GPIO 

GPIO shouldn't be too bad but bear in mind it is already accessed in places so they would need to allocate pins etc through it (e.g. sdcard to flicker the activity light, serial debug to output data on the GPIO pins)

Probably a resource rather than a device...

Started an i2c driver that will need to allocate GPIO pins. Feel free to work on it if you are interested ;p


 GPU graphics with 2D and 3D acceleration 

Sadly none yet for 32bit but for 64bit... 


 Miscellanous

hdmi issues

Setting the hdmi_force_hotplug=1 makes sure the Pi believes the monitor/TV is really there.

You might also need to set config_hdmi_boost=4 or even higher (up to 9) if your display needs a stronger signal.

If the display is a computer monitor or newer tv, use hdmi_group=1 (auto HDMI use) and if it is an older TV, try hdmi_group=2 (for DMT formats, i.e. for PC monitors) then you HAVE to &quot;set hdmi_drive = 2 to enable HDMI output as this forces HDMI mode rather than DVI mode

Do not set hdmi_safe=1 as that overrides many of the previous options.

Using a shorter or better quality HDMI cable might help. Make sure your Pi's power supply delivers 1 A and not 500 mA.
If you see a problem with the red colour - either absent, or interference - then try a boost

composite video

changing the RCA cable, then the composite port worked out of the box

Boot it as you are doing, without HDMI. If you now plug in the HDMI, do you get the image? In other words, does the Pi think HDMI is connected even when it isn't?

Rename all the files in the first partion of the card except bootcode.bin, start.elf and fixup.dat  What's the result?

Put back config.txt What's the result?

for PAL mode   sdtv_mode=2

dmi_ignore_hotplug Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached
hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected

&lt;pre&gt;
# NOOBS Auto-generated Settings:
#hdmi_force_hotplug=1
#config_hdmi_boost=4
#overscan_left=24
#overscan_right=24
#overscan_top=16
#overscan_bottom=16
#disable_overscan=0
start_x=1
gpu_mem=128
&lt;/pre&gt;

tvservice -c &quot;PAL 4:3&quot;

&lt;pre&gt;
/opt/vc/bin/tvservice -s   or tvservice -s 
state: HPD high|HDMI mode|HDCP off|composite off (0x12001a), 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m CEA
Group CEA has 1 modes:
(native) mode 16: 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m DMT
Group DMT has 0 modes:
&lt;/pre&gt;

sudo amixer cset numid=3 1

forces the audio to the headphone jack, even with the HDMI video output plugged in

config.txt

the hdmi_ignore_edid_audio=1 option sems relevant as it should tell ALSA that the only available audio is analog, no matter what the display says

There are several different ways that these 4 pole (ring) composite analog cables can be wired up, so some work great in some applications and can be a waste of time in others.

What is needed for the Raspberry Pi B+ and above, which like many camcorders needs the ring contact next to the base contact to be the ground.


The wiring for the 4 pole are:

TIP (LEFT AUDIO CHANNEL)

RING 1 (RIGHT AUDIO CHANNEL)

RING 2 (GROUND/EARTH)

RING 3 BASE/SLEEVE (VIDEO) YELLOW

Most Apple based Players and the Microsoft Zune (TM) are wired this way.

Most analogue camcorders are wired this way as well, where the ground in on Ring 2 will work with the Pi although you may need to swap your Video plug with the Right Audio plug.

Nearly all other MP3 players are not wired this way, the ground is on another ring ie the wrong one.


External devices

* Camera Module Omnivision ov5647 Sunny 5MP (NoIR version) V1.3 - NoIR at 850&amp;nbsp;nm, peak at 880&amp;nbsp;nm and trails off at 940&amp;nbsp;nm wavelengths 
* Camera V2 Sony IMX219 V2.1 8mpixel 8MP 8megapixel - 3280 x 2464 pixels - video at 1080p30, 720p60 and 640x480p90 - wider field of view, 62 vs 54 degrees horizontally - 
* Branded WIFI usb BCM43143 dongle

N.B.  dreaded error after changing cameras (stupidly without turning off the power first) and lasted through several power cycles.  It can be a bad 15-pin FFC ribbon cable, when swapped, camera(s) and the Pi itself are working OK. It can be an instance of a cold solder joint on the CSI connector on the pi board.  the camera can be detected (that's done via I2C) but may still not be able to receive image data (done via CSI-2) if something is broken. CSI-2 is uni-directional. Control is generally done via I2C. 
The CSI-2 receiver always writes to memory, not direct to the ISP. That's the way the Broadcom architecture works as it allows multipass processing easily. GPU memory is accessible from the ARM. Processing using the QPU graphics processors may be possible.  currently the only supported sensor is OV5647 and IMX219.  The linux drivers are all in the firmware blob, else you'd  be looking at at least a man-month of work in a fully fledged imaging lab to do a decent tuning of the camera modules' ISP parameters. 
Static electricity maybe an issue for the camera module and slightly less for the pi board.


== References ==


===Good sites to visit===

*[https://github.com/raspberrypi/firmware/tree/master/ Raspberry Pi Firmware build] 
*[https://www.raspberrypi.com/documentation/computers/software-sources.html Documentation] 
*[https://rpilocator.com/ RPiLocator] 


Linux only
*[https://github.com/raspberrypi/linux Raspberry Pi Linux Build] 
*[https://dietpi.com/ DietPi] 
*[http://www.tinycorelinux.net/ports.html piCore]
*[https://wiki.alpinelinux.org/wiki/Raspberry_Pi Alpine Linux] 
*[https://github.com/armbian/build Armbian] 


*[ FydeOS]
*[ TwisterOS based on ChromiumOS] 
*[https://note.com/jamesmondo/n/nc76e31402be8?hl=en BSD] 


*[https://www.raspberrypi.com/software/operating-systems/ PiOS Lite] and then [https://hstwb.firstrealize.com/ HST] 
*[ PiMiga for pi4 and pi5] 
*[ amibian for pi2 and pi3] 
*[ retropie pi1 and 2] 


Other alternative lighter smaller than Pi OS 
*[https://aros.sourceforge.io/nightly1.html Aros 64bit ARMV8 single core] 
*[https://www.riscosopen.org/wiki/documentation/show/Welcome%20to%20RISC%20OS%20Pi RiscOS on Pi3 and Pi4]
*[https://github.com/michalsc/Emu68 ARM based realtime JIT 68k for amiga computers] 
*[https://github.com/JJDSNT/bellatrix/releases/ Alternative use of Emu68 on Pi3b] 
*[https://github.com/stevereaver/uaos uaOS with Emu68k] 
*[https://github.com/aros-development-team/AROS/commit/f80a268607dfae81b2db94755ab4e4d31ccb72d6 m68kemu library reference] 
*[ HaikuOS]
*[https://github.com/raspberrypi/noobs NOOBS] os loader with successor [https://github.com/procount/pinn PINN] 
*[https://github.com/maxnet/berryboot berryboot]

*[https://github.com/brianwiddas/pi-baremetal Bare Metal Access on Pi 32bit] 


Testing procedure is put sd card in, connect board to board if necessary, plug in hdmi and then power nothing else is done especially CSI DSI etc 

[https://www.raspberrypi.com/documentation/computers/compute-module.html CM5] has the same 55mm x 40mm 2x100pin connectors form factor as the CM4 but [https://www.epdtonthenet.net/article/214508/Key-Considerations-When-Migrating-from-Raspberry-Pi-CM4-to-CM5.aspx some pins and other small things] have changed. Will need the [https://raspipcb.com/tech-blog/raspberry-pi-cm4-vs-cm5-difference-in-booting-from-sd-card/ right IO board to suit] 

*Green [ Raspberry Pi Compute Module 5 IO Board REV2 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1967]] - untested 
*Green [ RPi Compute Module 5 IO board REV1 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1751]] - untested 
*Black SupTronics Geekbord X1500 CM5 IO Carrier Board - untested
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*[https://sipeed.com/nanocluster Sipeed NanoCluster] - untested up to 7 CM5 
*Green BentoIO CMX0 - untested 
*Box EDATec ED-CLAWBOX - untested 
*Home Assistant Yellow - Kit with PoE with Raspberry Pi Compute Module 5 - untested 
*Blue [https://www.waveshare.com/wiki/CM5_PoE_BASE_A Waveshare CM5-PoE-BASE-A] - untested 
*Box  Waveshare [ CM5-POE-BOX-A] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-B Waveshare CM5-IO-BASE-B] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-A Waveshare CM5-IO-BASE-A] - untested 
*Blue Waveshare [https://www.waveshare.com/wiki/CM5-NANO-B CM5-NANO-B] - untested 


*[https://carboncomputers.us/products/pi-flux piFlux]
*[https://carboncomputers.us/products/ Zitaotech Hackberry] CM5 lite only - 
*Portable [https://www.waveshare.com/pocketterm35.htm Waveshare PocketTerm35] with Pi4B or Pi5 - untested 
*Box [https://www.clockworkpi.com/uconsole ClockworkPi uConsole][https://www.youtube.com/watch?v=EtI_bAahbR8 CM4 into an adapter or CM3 into so-dimm - Cyberdeck] - untested 


*Green RPi [https://datasheets.raspberrypi.com/cm4io/CM4IO-KiCAD.zip Compute Module 4] [https://datasheets.raspberrypi.com/cm4io/cm4io-datasheet.pdf IO board] V1.4 [https://datasheets.raspberrypi.com/cm4io/CM4IOUSB3-KiCAD.zip USB3] [https://datasheets.raspberrypi.com/cm4io/cm4iousb3-appnote.pdf CM4ISO] [https://datasheets.raspberrypi.com/cm4/cm4-datasheet.pdf Dual100pin] (2020) aka Development Platform Board - untested 
*Purple Pi Hut Cytron CM4 Maker Board - untested 
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*[ KubeSail PiBox mini 2] 
*Home Assistant Yellow with Raspberry Pi Compute Module 4 - untested 
*[ Turing Pi V2] - untested CM4 with 260-pin SO-DIMM socket adapters and/or nvidia jetson nanos - untested 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-C Waveshare CM4-IO-BASE-C] - untested but binary blobs Rev01 Rev02 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-B Waveshare CM4-IO-BASE-B] - untested but binary blobs 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-A Waveshare CM4-IO-BASE-A] - untested but binary blobs 
*Blue [https://www.waveshare.com/wiki/CM4-NANO-B Waveshare CM4-NANO] - untested but usb and audio turned off or rerouted 
*Black [ Seeed Studio with BigTreeTech BTT pad 7] - bin blobs? 


CM3 has a 200 pin sodimm ddr2 connector form factor but not electrically SC0028, SC0029 
*Blue [https://wiki.geekworm.com/CM_IO_Board Geekworm RPi Compute Module IO Board] [https://github.com/geekworm-com/cm-io-board CSI DSI] with CM3 in ddr2 slot underside - '''works''' if SW1 on but CM3+ '''does not''' 
*Green [https://cdn-shop.adafruit.com/product-files/3442/CMIO_schematic.pdf RPi V3 IO board CM3IO] and CM3 Lite - untested 
*Green [https://turingpi.com/ turingpi v1 cluster] - untested up to 7 cm3 7xlan9514 12V discontinued, 3 x Pi4 homelab maybe better 
*Blue [https://www.waveshare.com/wiki/Compute_Module_PoE_Board Waveshare Compute Module PoE Board] and CM3 lite (if not lite, write files to internal eMMC fat32) '''AVOID''' bin blobs 
*Blue [https://www.waveshare.com/compute-module-io-board-plus.htm Waveshare Compute Module IO Board Plus] [https://www.waveshare.com/wiki/Compute_Module_IO_Board_Plus wiki] [https://forums.raspberrypi.com/viewtopic.php?t=235695 pin settings] with CM3+ Lite - '''AVOID''' binary blob 


*[ Pi02w on Geekworm SupTronics X305 Raspberry Pi Zero IO Baseboard] - untested 
*[ Spotpear Pi Zero 2w to Pi3b format-ish] - untested 


*[ pi-top v4] box has 128x64 oled display, micro hdmi, 19Whr battery with pi4 and 15V PD 36W min needed 
*[ pi-top v3] three green pieces, heatsink covers most of the base tray, pi-top hub mk1 lhs and Pi1B Pi2b Pi3b rhs secured from below, black rounded strip with pi-top above keyboard, 13.3&quot; HD 1366 x 768 display, small touchpad, 
*[ pi-top Model 2.0] pi-top on bottom bezel of 14-inch green laptop, large trackpad, keyboard slide down to reveal main system hub on slide rails moved to the right, Raspberry Pi3b screws down, hub slides in, 18V 2.5A 45W charger brick, battery 11.1V 3500mAh 38.85Wh and storage PiTopOS 
*[ Pi-Top CEED Raspberry Pi Modular Educational Desktop with RPI3] monitor 
*[https://www.indiegogo.com/en/projects/jesselozano/pi-top-a-raspberry-pi-laptop-you-build-yourself Pi-Top v1] wedge laptop with RPi2 


&lt;pre&gt;
2008 Trustees collected for Foundation
2009 Pi Foundation charity status gained 
2010 
2011 First Raspberry prototypes 
2012 First boards go on sale at CPC and RS. The Model A and B 700 MHz Arm11 - February 29th BCM 2835
2012 First million sold - more than the 10,000 original planned and anticipated 
2013 First Alpha Experimental builds of AROS Native for the 32bit Pi 
2013 Pi Trading launched making grants available, providing in house educational resources and Pi Academy for teacher training 
2013 Over two million sold 
2014 Over three million sold 
2014 Pi 1 Model B+ introduced that moved composite video to audio jack and same half gig of memory 
2014 Pi Model A+ v1.1 no ethernet and 1 usb - a little smaller - 
2015 Over four million first gen pis sold  
2015 Pi Zero 1.2 BCM2835 first production revision released with no camera port 
2016 Pi0 1.3 released with camera csi connector 
2017 Pi Zero W v1.1 1GHz Pi0W, single-core 32bit CPU BCM2835 released with Cypress CYW43438 wireless 
2020 Raspberry Pi Pico SC0919 with RP2040 32-bit 2Core ARM Cortex-M0+ up to 133 MHz - 264KB of SRAM and 2MB of on-board QSPI Flash - 
2024 Raspberry Pi Pico 2 with RP2350 2Core 32bit Arm Cortex-M33 and 2core open-hardware [https://github.com/wren6991/hazard3 Hazard3 RISC-V] 

2015 Pi 2 Model B v1.1 BCM2836 900/600 MHz ARM Cortex-A7 Armv7 quad 32bit, 32bit VideoCore IV GPU - 1Gb RAM - 5V 2A micro usb - SMSC LAN9514 chip - 
2015 Over a million pi2s sold 


2015 Raspberry Pi 2 Model B version 1.2 Pi2bv1.2, aka Pi2B2 has armv8 BCM2837 underclocked to 900Mhz without wifi/bluetooth module 
2016 Pi 3 Model B - Broadcom BCM2837 SOC four 64bit ARMv8 Cortex-A53 1.2GHz 32bit 1080p VideoCore IV GPU - 1Gb DDR2 - bluetooth 4.1, Cypress CYW43438 wireless 802.11n - 4 x USB2.0 ports - 5.1V 2.5A - SMSC LAN9514 chip 
2016 PIs total over 10 million worldwide 
2017 Compute Module 3 CM3 with BCM2837B0 armv8 Quad 64-bit - small 67.6mm x 31mm board which fits DDR2 SODIMM connector but not electrically compatible which plugs into needed IO board - beware of the I2C protocol issue 
     1Gb LPDDR2 RAM - Lite or 4Gb Emmc storage 
2017 12 million pis sold in total 
2018 Pi 3 Model B+ - 4c A53 BCM2837B0 1.4Ghz - 1Gb, wireless 802.11ac, gigabit ethernet (300Mbit/s) and bluetooth 4.2 - power over ethernet - 4 x USB2.0 ports - Microchip LAN7515 chip 
2019 Over 15 million sold 
2019 Pi 3 Model A+ with BCM2837b0 Cortex-A53 64-bit SoC @ 1.4 GHz with 512Mb LPDDR2, 1 usb2, 1 hdmi, 1 micro usb 5V 2A - no ethernet - 
2019 Raspberry Pi Compute Module 3+ CM3+ - Broadcom BCM2837B0 1.2Ghz, Cortex-A53 (ARMv8) 64-bit SoC on DDR2 SODIMM mechanically compatible only factor - IO board required 
     1Gb DDR2 and 8GB, 16GB, 32GB or a Lite variant without eMMC 
2021 Pi zero 2 (w or no W) RP3A0 quad 1GHz Cortex-A53 64bit BCM2710A1 512mB SDRam 
2025 edaTEC CM0 ED-CM0NANA with additional dev board with quad 1Ghz A53 with 512Mb Raysan RAM, 2 USB2 and 10/100 ethernet - pico castellated edge
 

2019 Pi 4 Model B v1.1 RPI4B - BCM2711B0T quad 64bit A72 1.5GHz, 4K VideoCore VI, AC wifi, Bluetooth 5.0, GbE Broadcom BCM54213PE (PHY ID 0x600d84a2), 2 micro hdmi decode up to 4K, USB-C 5.1V 3A power, 2xVLI VL805 USB 3, 2xUSB 2.0, 2GB 9LDWW D9WHZ or 4GB 9FDWW D9WHV, 8GB 0AA47 D9ZCL ddr4 ram 
2020 Silent Pi 4 v1.2 upgrade with more USB-c psu support 
2020 PI400 BCM2711C0T 1.8GHz 4Gb DDR4 inside keyboard, 5.1V 5A 27W usb-c psu, 2 micro hdmi, external ide style 40pin gpio, no audio port - 
2020 Raspberry Pi Compute Module 4 BCM2711B0T on new 55mm x 40mm 2x100 pin form factor with extra breakout IO board 
     CM4101000 1Gb RAM Lite SOM 
     CM4102000 2GB RAM Lite 
     CM4104000 4GB RAM Lite 
     CM4004008-4GB-RAM 8GB-EMMC SOM System on Modules 
     CM4104032 4GB RAM 32GB emmc 
     CM4108000 8GB RAM Lite 
     CM4008016 8GB RAM 16Gb eMMc
2021 Raspberry Pi SC0763 Compute Module 4S CM4S with ddr2 sodimm pinouts but not electrically the same with suitable IO board extra cost - 
     CM4S01000 1GB RAM Lite
     CM4S01008 1GB RAM 8GB eMMC Flash
     CM4S02000 2GB RAM Lite
     CM4S04000 4GB RAM Lite
     CM4S04016 4GB RAM 16Gb KLMAG1JETD-B041 
     CM4S08000 8GB RAM Lite 
2021 Pi 4 v1.4 BCM2711B1 upgraded power regulator, to deal with 8gig of ram being more power hungry 
2021-48 Raspberry Pi 4 model B v1.5 2GB 


2023 Pi 5 v1.0 BCM2712 Quad A76 @2.4Ghz - VideoCore VII - no audio socket - dual 4k from mini hdmi - fan connector - 5.1V 5A psu 
2024 Pi 5 2GB DDR4 version uses BCM2712D0 
2024 Pi-500 with 8Gb LPDDR5 and membrane keyboard 
2024 Pi 5 v1.1 
2024 Raspberry Pi Compute Module 5 CM5 BCM2712 55mm x 40mm form factor with additional IO board 
     CM5004000 04GB RAM 0GB eMMC Lite
     CM5008000 08GB RAM 0GB eMMC Lite
     CM5016000 16GB RAM 0GB eMMC Lite
2025 Pi-500+ with 256GB NVMe storage, 16GB LPDDR4 RAM, and Gateron KS-33 Low Profile Blue mechanical keyboard switches 
2025 Pi5 1GB DDR4 announced 


2022 PiOS linux goes 64bit 
2024 Pi Trading IPO stockmarket stock exchange listing 


2026 April and May Aros 64bit fixed, added AHI audio, VC4 gfx started, usb functions added to rom  
2026 June and July Aros 64bit usb2otg started, dma.resource, sdio.resource, bwfm.device wifi added 
2026 Late July daily 64bit Pi3 LE little endian builds start 
2026 August Pi 4, 400, 5 and 500 DTBs added, expanding existing support and wifi for Pi4 and Pi5 
2026 August Pi5 HAT+ nvme and HDMI, AHI RPiI2S added, Pi4 HVS5 video scaler started, 
2026 
2027 


2028 Pi 6 
&lt;/pre&gt;


The vcgencmd can be used to inspect and dump the current system configuration. 
vcgencmd runs on top of VCHIQ as an RPC. The mailbox interface is an alternate but much simpler RPC. 
VCHIQ is a bridge (queue) between the CPU and the GPU so they can communicate with the firmware. 

Loads of [https://github.com/6by9/rpi3-gpiovirtbuf/blob/master/rpi3-gpiovirtbuf.c mailbox] which uses the GPIO control calls. [https://github.com/raspberrypi/firmware/wiki/Mailboxes may also be of interest] 

A fair number of vcgencmd examples (search for vc_vchi_gencmd_init). [https://www.raspberrypi.org/forums/viewtopic.php?t=229203#p1406112 sends the relevant vcgencmd commands] to update the scaling kernel, but the [https://github.com/raspberrypi/userland/blob/master/host_applications/linux/apps/gencmd/gencmd.c command] is just a text string. Parsing and execution of the instructions is performed by the VideoCore firmware. 

The Raspberry Pi runs two separate operating systems: Linux/Aros on the ARM, and a threedx RTOS called vcos running on the Videocore 4 VPU: vcos is commonly called &quot;the firmware&quot;. Vcos is tasked with performing certain system services, for example running the display and audio outputs. The VCHI driver provides an interface to allow drivers to talk to vcos. 


Doubtful, on any [https://www.web3d.org/ Web3d] [https://developer.mozilla.org/en-US/docs/Web/API/WebGL_API WebGL] or [https://github.com/immersive-web/webxr WebXR] [https://developer.mozilla.org/en-US/docs/Web/API/WebXR_Device_API Device API] [https://developer.mozilla.org/en-US/docs/Web/API/XRInputSource XRInputSource] support. Hopefully, never/limited support features like location, peer-to-peer, invasive web apps, unwarranted storage, payments, proprietary video streaming etc 

*spreadsheet [https://git.sheetjs.com/sheetjs/sheetjs sheetjs] [https://github.com/mleibman/SlickGrid SlickGrid javascript] [https://github.com/6pac/SlickGrid SlickGrid typescript] [https://github.com/jspreadsheet/ce jspreadsheet ce] probably without xlsx support 
*presentations [https://github.com/impress/impress.js/ impress.js simplified] [https://github.com/bwlewis/slides slides] [https://zenomt.github.io/mdslides/ github markdown slides] [https://github.com/Patternslib/slides Patternslib slides markdown] probably without pptx support 
*ai office [https://github.com/dream-num/univer/ univer], [https://github.com/dream-num/Luckysheet Luckysheet] [https://github.com/ruilisi/fortune-sheet fortune-sheet] 
*weather [https://github.com/Himanshu3412/Weather-Forecast Weather Forecast], [https://github.com/kaushalsahu07/weather weather needs API key], 


==Future==


[https://github.com/ARMSX2/ARMSX2 Arm pi of pcsx2] 


[https://tube.cadence.moe/ Cloudtube], [https://github.com/TeamPiped/documentation/blob/main/content/docs/public-instances/index.md TeamPiped], [], [], [], 

[https://hyperpipe.codeberg.page/ hyperpipe], [https://ytify.pp.ua/ ytify], [], [], 

[ ytdl], [https://github.com/golddominik893/liberatube liberatube]

[https://git.lolcat.ca/lolcat/4get 4get], [https://github.com/hnhx/librex librex], [], [], 


{{BookCat}}</text>
      <sha1>1kon26txpe12gejpr7c8b564049wmlh</sha1>
    </revision>
    <revision>
      <id>4676729</id>
      <parentid>4676557</parentid>
      <timestamp>2026-10-18T10:38:49Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4676729</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="106239" sha1="lbfe5op6lapohxn3x8vgtav7wk2n380" xml:space="preserve">{{ArosNav}}

[[#Native]]

[[#Hosted]]

[[#Build]]

[[#Hardware]]

[[#References]]

[[#Future]]


==Introduction==


[[File:Scalos00.png|thumb|Scalos on Aros Pi3b]]

Aros aims to cover Pi 3 to 5 512Mb+ RAM 


Options to boot from using a good power source to prevent the yellow lightning symbol. 
*With Pi3b+ the max you can get is 5.1V 2.5A with micro usb.
*With Pi4 5.1V 3A with usb-c 
*With Pi5 5.1V 5A, the amps went ever upwards, even to 5.1V 9A with usb-c 


* Pi500+ keyboard wedge - working but not much tested esp [https://github.com/aros-development-team/AROS/commit/48e9c8edcca4b5c1e1fe0b1123f2129f624af67b power button] 
* Pi500 wedge with up to date bootloader via PiOS - working but not much testing esp [https://github.com/aros-development-team/AROS/commit/48e9c8edcca4b5c1e1fe0b1123f2129f624af67b power button] 
* Pi 5  - Quad A76 64bit ARMv8 and RP1 &quot;southbridge&quot; with VideoCore 7 D0 (rev1.1) - untested 
* Pi 5  - Quad A76 64bit ARMv8 and RP1 &quot;southbridge&quot; with VideoCore 7 Pre-D0 C1 (Rev1.0) - untested 
* Pi400 RPI-400 keyboard wedge - resolution changing and audio from micro hdmi0 (near 40pin) and micro hdmi1 (near usb-c psu) - Fn F10 0x5e power on and off works or held down for over 7 seconds auto shutdown - keyboard ok - wifi and lan ethernet testing - 
* Pi 4  - Quad A72 64bit ARMv8 with VideoCore 6 
* Pi 3  - Quad A53 [https://www.raspberrypi.com/documentation/computers/processors.html 64 bit] ARMv8 with VideoCore 4 with '''fan''' to prevent overheating cpu 82C+ throttling 
* Pi02W - Quad A53 64bit - boots but [https://forums.raspberrypi.com/viewtopic.php?p=2387984#p2387984 usb not working but did in the past], 


* Pi 2 - Quad 32bit ARMv6 with VideoCore 4 - mostly not 64bit compatible 
* Pi Model B+ 32bit ARMv6 with VideoCore 4 - not 64bit compatible 
* Pi Model A and B 32bit ARMv6 with VideoCore 4 - not 64bit compatible 


===Native===

* 2013-03 Kalamatee starts work
* 2015-04 Work continues with mschulz on the kernel and Kalamatee (NicJA) on gpio and usb
* 2018 [https://www.patreon.com/posts/i-owe-you-some-20956961 mschulz resume adding BE big endian support], [https://www.patreon.com/michal_schulz/posts Big endian on Pi]  
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bsek latest commits for pi 3b, 4 and 5 64bit] 
* 2026 [https://github.com/aros-development-team/AROS/commits?author=metaneutrons latest commits for Pi5]
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bitplane latest commits for ARM]


====64bit====

'''Download''' A [https://archive.org/details/piAROS Pi Distribution (Distro) has started] and the contents copied to fat32 8GB+ microSD card (there will be drawers/folders - boot c Classes Demos Developer Devs Extras etc only showing). The SD can be plugged in to the Pi. And power on. [https://pi.amiga.icu/ Repository]

'''Not recommended''' but [https://aros.sourceforge.io/nightly1.html RaspberryPi 3, 3+, 4 and 5 64bit ArmV8 nightly builds] [https://sourceforge.net/projects/aros/files/ and alternative site and nightly2] which is a test version of '''very few''' apps with both raspi-aarch64-system and raspi-aarch64-contrib can be unbz2'd to a SD or SSD as appropriate. 

64bit build works well on a single core LE little endian. Multicore [https://github.com/aros-development-team/AROS/commit/1df0747c2bda3523a43029725a709b1f377d84ec may follow]. Any issues booting could be down to the SD card so please use another SD to see if it is resolved. Remember Aros Arm uses FAT32 and Aros can detect issues with this format very acutely (once fault found, FAT 0x0FFFFFF7 bad cluster so no files written after that, no repair). Please report your experiences in the [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2138&amp;pid=15057#post_15057 Aros forum thread], [https://forums.raspberrypi.com/viewforum.php?f=179 Raspberry Pi Aros Dev and User forums], [https://forums.raspberrypi.com/viewtopic.php?p=2387984#p2387984 previous Raspberry Pi forum thread]. Any bugs or issues can be [https://github.com/aros-development-team/AROS/issues described here to fix] 


*Pi500+   untested usb3 booting or nvme ssd 
*Pi500    untested usb3 booting 
*Pi5      untested usb3 booting 
*Pi400    boots with '''USB3''' port based sata3 ssd 
*Pi4      untested (may need eeprom update from PiOS or Pi SD Imager) 
*Pi 3 B+  is pre-configured for USB sata3 boot - untested 
*Pi 3 B   may need [https://www.youtube.com/watch?v=ubnwvxF3Klc PiOS to set OTP to boot from usb - do so at your own risk] - if OTP set to usb, boot works but slower than SD card 

Speed write wise (top faster) 
&lt;pre&gt;
*NVME Pi5 untested    &gt;1000MB/sec  or faster if matched correctly 
*Sata3 ssd              500MB/sec
*SD        V90           90MB/sec  4K maybe 8K 
*SD        V60           60MB/sec  1080p 
*SD     U3 V30           30MB/sec  720p 
*SD C10 U1 V10 A1 A2     10MB/sec  minimum should be used now 
*SD C06                   6MB/sec  
*SD C04                   4MB/sec 
&lt;/pre&gt;


As a homage to the past, Aros shows a reduced number of icons but this can be changed by left mouse click in the window and then right click down to Window -&gt; View -&gt; All files

Windows can be manipulated by the top (moving) and the bottom right corner (resizing) only. 

Zune like MUI gui interface, has a unique quirk in that after changing a setting in a text box, you may sometimes need to press Enter/Return before clicking OK, Save, etc 


Double left mouse click on most picture (Developer/Debug/Tests/Datatypes), audio and video files are supported, via datatypes, by the multiview application. 
Esc escape key usually closes open windows even the desktop 

In Prefs/Appearance some decorative theming elements need work. There is a few Mason icons in /Prefs/Presets/Icons/Mason/ and the ever present default Gorilla - Icon exchange in works 

For more intensive graphics applications, you may need to edit config.txt in the root folder and change 128M to 256M to adjust more memory to graphics usage 

If your cursor should '''appear''' to vanish, fear not it is still there. Please head to the top of the screen i.e. the title bar, hold down the left click mouse and drag the screen down a little and the cursor will appear again. Then you can drag the screen up again. 


Like most amiga like OSs the audio and networking need to be setup manually 

Audio AHI prefs - Mode settings tab - needs both Music unit and Unit 0 set to RPiHDMI:16 bit stereo++  or RPiPWM:16 bit stereo++ at 44100Hz. Press '''Save or Use''' button after each choice 


For wireless, please use the Wifi prefs and already selected device bwfm.device. Press Scan and double right click on the router and enter password. You may need to setup after every power off
*if asking for password again - press cancel and go to Network Prefs, Wireless Networks tab and highlight the router line and hit the remove button and press the cancel button. Retry with Wifi prefs again 
*...waiting for an address - Disconnect and try Connect 
Until, Connected to &lt;router&gt; - 192.168.x.x 


For lan ethernet port, please use Network prefs and the following hardware is 
*lan9514    Pi3b Pi2 not supported at the moment 
*lan7515    Pi3b+ type into Device  usblan78xx.device as net0:  remove other device(s) 
*bcmgenet   Pi4 Pi400 choose for Device bcmgenet.device 
*cdnsgem    Pi5 Pi500 Pi500+ RP1 i/o for cadencegem 
 (network prefs may forget random information when rebooted) 


Summary
&lt;pre&gt;
*3b    ethernet not supported, usb ethernet not working but wifi prefs setup works 
*3b+   wifi working and ethernet works 
*4     untested 
*400   wifi and ethernet untested 
*5     wifi and ethernet untested
*500   wifi and ethernet untested
*500+  wifi works 
&lt;/pre&gt;


Type in 'aarch64' in the [https://archives.arosworld.org/index.php?function=search&amp;tool=simple search box] and you will see available software packages / apps. apkg can be used to inspect and install applications. 

[http://archives.arosworld.org/index.php?function=browse&amp;cat=network/browser amelinium web browser (JS 1.6 ES9 ECMASCript 2018)] is available with an [https://eab.abime.net/showthread.php?t=122494&amp;page=80 eab thread] reminiscent of [https://github.com/zapek/Voyager Voyager] and to a lesser extent [https://github.com/amigazen/aweb3/ Aweb JavaScript 1.5 (ECMAScript 3)] as css and javascript websites can be slow to load or resolve (no JIT) and nothing from facebook, reddit etc. 

Press Cancel at screenmode selector or -wb argument to get windowed version. You could use the Shift + Del shortcut or mouse wheel should work to delete all text at once. Html5test gives 189 (1.29), 300 (1.31), 301 (1.39) out of 555, some bigger Amiga like browsers are around 370+ but it does less better. 

You may have to delete the cache (Menu -&gt; Page -&gt; Delete cache) to fully retest big Amelinium updates or free up space. 
Be aware [https://pianetaamiga.it/en/reportage-pianeta-amiga-2026/ some site pages] can use up hundreds of MBs of cache very quickly 

 DNS lookup failed...  close browser and reboot and setup wifi again - repeat until it works again 

 youtube video and audio - js button for javascript must be on/shaded -  Settings -&gt; Soundoutput - AHI 
Any restriction to lower resolutions is due to [https://docs.invidious.io/faq/#q-where-are-the-360p480p1080p-quality-options bandwidth]. Either CPU/GPU, internet speed and/or video quality. Pi3 can expect up to 480p (wifi) and up to 720p (ethernet). Pi4 expect (wifi)  (ethernet). 

Telegram https://t.me/s/channel_name for public messages from vamped_amiga chatamigagames demoscenecracktros 

*art local js apps like dpaint.js 


There is normally no Bluetooth support for most amiga like OSs but Aros has one [https://github.com/aros-development-team/AROS/commit/6942cbfbf66426d21963a7fcd8aba6aff611a9e0 work in progress] [https://github.com/RPi-Distro/bluez-firmware/tree/pios/trixie/debian/firmware/broadcom firmware] 

*Bluetooth 4.1 BCM43430A1.hcd Pi3B, Pi3A, Zero 2W 
*Bluetooth 4.2 BCM4345C0.hcd  Pi3B+, Pi4 
*Bluetooth 5.0 BCM4345C5.hcd  Pi4B rev, CM4 and maybe Pi5 and CM5 

&lt;pre&gt;
*bthid    keyboard mouse support 
*btserial serial 
*btpan    short range wireless connecting devices 
&lt;/pre&gt;


Only the Pi5 has a RTC real time clock, the other Pis will need to use ntp services [https://github.com/aros-development-team/AROS/commit/29cd4116330dc7f692d90757eacc59fb3f31ae70 sntp] with time.cloudflare.com pool.ntp.org or Cloudflare 162.159.200.1, 162.159.200.123, 2606:4700:f1::1, 2606:4700:f1::123 or [https://github.com/bohunamiga/PiNTP PiNTP -s goodtime.ijs.si or ntp1.ptb.de] to get the date and time from the internet. Can use date in a shell e.g.  date 24-Dec-2026 23:59:59  but this will need to be done again after every reset/power off. Maybe [https://github.com/aros-development-team/AROS/commit/28674a157bc56175aa668e7b62dca6fa740578dc ds3231 rtc with dtoverlay=i2c-rtc,ds3231 in config.txt] 


It helps to have all usb devices already plugged in before power on to detect at the moment. Even then some usb devices will freeze the mouse cursor and the only resolution is to remove the offending usb device and reinsert. Sometimes, the reinsert leads to the mouse cursor vanishing, it is still there and responds to left mouse clicks, top of the screen and pull down the screen. 

USB classes support from Prefs/Trident is still work in process 
*usbaudio working on usb3 port (blue) on pi4, 400 but not working (no rt isochronous) on usb2otg (white or black) for pi3b, zero 2w 
*[https://aminet.net/package/mus/midi/camd camdusbmidi] detects midi devices without a preferences file (Prefs/Env-Archive/sys/midi.prefs) as [https://www.youtube.com/watch?v=RBxHkwy4Nrw auto setup now] possibly with [https://github.com/metaneutrons/mt32-pi metaneutrons mt32-pi] [https://github.com/rtzor/mt32-pi mt32-pi fork] [https://github.com/ahmadexp/mt32-pi fork] [https://github.com/gmcn42/mt32-pi-control control of] [https://github.com/dwhinham/mt32-pi mt32-pi pi3+]. Alternative of [https://homspace.nl/samplerbox/ SamplerBox]. 

Will need developer clang gcc tools to look at 64bit ports of [https://archives.arosworld.org/?function=showfile&amp;file=driver/audio/usbmidi.i386-aros.lha usbmidi], [https://aminet.net/package/mus/midi/CAMD_Toolkit CAMD_Toolkit], [https://aminet.net/package/mus/midi/camdtools camdtools], [https://github.com/cnvogelg/amiditools amiditools], [https://github.com/timoinutilis/midi-sequencer-amigaos horny src], [https://aminet.net/package/mus/midi/horny-base horny-base], [http://bnp.hansfaust.de/index.html BnP], [https://arosarchives.os4depot.net/?function=showfile&amp;file=audio/misc/timidity.lha timidity], 


Regarding 680x0 emulation, there are several options (not implemented yet) that could be considered 
*[https://github.com/aros-development-team/AROS/blob/6722a0ae9e03fe5d26e32703360bd2059e0864cc/rom/m68kemu/README.md?plain=1#L424 m68kemu.library] for some Amiga productivity where the cpu is emulated and the system calls are redirected to Aros ones
*[https://github.com/BlitterStudio/amiberry amiberry] (winuae) for everything else like games 
*[https://github.com/jonx/AROS/tree/aarch64-darwin-graft/arch/all-darwin/libs/emu68k emu68k] 
*[https://scriptedamigaemulator.net/ Scripted Amiga] with [https://github.com/naTmeg/ScriptedAmigaEmulator ScriptedAmigaEmulator] or older [https://github.com/gbraad-amiga/ScriptedAmigaEmulator2 ScriptedAmigaEmulator2] 
 Hopefully getting Pi3 up to 25Mhz 68040 (non JIT) and 50Mhz 68040 (JIT) 
 Pi4 maybe getting up to 50Mhz 68040 (no JIT) and 100Mhz 68040 (JIT) 


[https://pinout.xyz/ GPIO 40 pins] [https://learn.sparkfun.com/tutorials/raspberry-gpio/gpio-pinout pinout] 

Some exceptions:

*Physical pins 27, 28 (GPIO0, 1) are an internal I2C bus and should not be used
*The other I2C on pins 3, 5 (GPIO 2, 3) can be used generally, but be aware they have permanent pull-up resistors to 3.3V
*For MIDI use USB but there are dedicated UART pins 8, 10 (GPIO 14, 15).

With a HAT it's more awkward -- you need to know which pins are used by the HAT and avoid them. Hopefully this will be documented.

Remember all GPIOs are 3.3V (not 5V tolerant), floating/noisy inputs can cause odd behavior, and that shorting the power supplies can cause instant death of the Pi.

In the shell (Cntrl + C to end) 

 GPIO PIN/A/N,SET/N,GET/S,MODE/K,PULL/K

Controls and queries hardware GPIO pins via gpio.resource which is stored in the rom or Devs/ '''please test''' 

*PIN   -- (Required) Target GPIO pin number (e.g. 12).
*SET   -- Set pin output value to 0 (LOW) or 1 (HIGH).
*GET   -- Read and print current digital input level (0 or 1).
*MODE  -- Configure pin mode: IN (Input), OUT (Output), ALT (Alternate).
*PULL  -- Configure pull resistor: NONE, UP, DOWN.

EXAMPLES
&lt;pre&gt;
GPIO 12 MODE OUT
GPIO 12 SET 1
GPIO 12 GET
GPIO 13 PULL UP
&lt;/pre&gt;


[https://gpiozero.readthedocs.io/en/stable/installing.html Current] [https://gpiozero.readthedocs.io/en/v1.2.0/api_boards.html old support for gpiozero is unknown at present] [https://energenie4u.co.uk/res/pdfs/ENER314%20UM.pdf and associated 433MHz equipment] [ USA X10 security and lights via USB] [ OpenHab with Shelly Smart Plug connected over Wi-Fi, controlled by MQTT or HTTP] 


Printing only with Postscript but [https://github.com/bohunamiga/MintPRINT one] of [https://github.com/boingball/MintPRINT two] [https://github.com/Andiweli/AmiAirPrint/tree/main AirPrint] IPP has been attempted with [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2061&amp;pid=13954#post_13954 discussion] 


Youtube 

[], [], [https://www.youtube.com/watch?v=X4fmWAIv7FE Aros native on Pi3b], 

[], [], [https://www.youtube.com/watch?v=TSxlYb1eQWU Installed on Pi3b+], 

[], [], [https://www.youtube.com/watch?v=NFF1H3jCoz8 testing Aros native on Pi400], 

[], [], [https://www.youtube.com/watch?v=nIVx7mh1E1Q&amp;pp=ygUHYXJvcyBwadIHCQkTDAGHKiGM7w%3D%3D Aros on Thumb 2 based 32bit-ish ARM STM32H743 board], 


[https://www.youtube.com/watch?v=zQM4CD64xDE&amp;t=612s&amp;pp=ugUEEgJlbg%3D%3D Performance under Linux] but on Aros... 

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot; |Pi
! width=&quot;10%&quot; |Single Core 2D
! width=&quot;10%&quot; |Single Core 3D
! width=&quot;10%&quot; |Single Core 3D
! width=&quot;10%&quot; |SMP 2D
! width=&quot;10%&quot; |SMP 3D
! width=&quot;10%&quot; |SMP 3D 
! width=&quot;35%&quot; |Comments
|-
| &lt;!--Pi--&gt;Pi3 
| &lt;!--Single Core 2D--&gt;
| &lt;!--Single Core 3D--&gt;
| &lt;!--Single Core 3D--&gt;
| &lt;!--SMP 2D--&gt;
| &lt;!--SMP 3D--&gt;
| &lt;!--SMP 3D--&gt;
| &lt;!--Comments--&gt;
|-
|}


==== 32bit ====

For the Pi1 Pi2 Pi2B the status of AROS native ARMv6 for 32bit RasPi was OK. System booting, USB working (although with some issues but plans to fix them). 32bit native [http://www.aros.org/nightly1.html ARMv6 32bit nightlys] raspi-armhf-system raspi-armhf-contrib unbz2'd to fat32 microSD 


===Hosted===


AArch64 CPU backend for AROS, a Cocoa/Metal display, clipboard / host-volume / CoreAudio / BSD-sockets bridges, GPU 2D via gpufx.library, a 68k→AArch64 JIT (run68k), and a full Rust std port. On [https://www.jkn.me/blog/macaros-aros-on-apple-silicon/ latest Apple Silicon] [https://github.com/jonx/Macaros early buggy alpha version of hosted Aros .dmg on MacOS12+]. Please use [https://github.com/jonx/Macaros/issues MACAros github] for issues, features etc and possibly [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2030&amp;pid=13910#post_13910 here] 


[http://www.aros.org/snapshots1.html old linux and android hosted 32bit] 


==== Hosted ====

=====64bit=====

[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80&amp;pid=13667#post_13667 Ubuntu Linux PC hosted Pi compiler build] 

[https://github.com/BlitterStudio/aros-compiler-docker Docker based cross compiler for various Aros systems], 

[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80 From the Aros Raspberry pi 3 64bit thread] 
Instructions on building 64-bit Raspberry Pi AROS and cross-compiler from sources.

You will need:
- Ubuntu 24.04 or 26.04
- qemu-system-aarch64 installed
- Internet connection
- rpi-scripts.tar.gz downloaded (https://axrt.org/download/aros/rpi/rpi-scripts.tar.gz)

1) Install prerequisites:

sudo apt install git gcc g++ make gawk bison flex bzip2 netpbm autoconf automake libc6-dev liblzo2-dev libpng-dev gcc-multilib byacc python3-mako cmake yasm curl nasm

2) Clone sources

cd &lt;project-directory&gt;
git clone https://github.com/aros-development-team/AROS.git --recurse-submodules

3) Extract rpi-scripts.tar.gz. Copy all files into your project directory so that you have:

AROS (the directory with cloned sources)
fix-dotdot.py
rebuild.sh
recreate-sdcard.sh
run-qemu.sh
update-sdcard.sh

4) Run ./rebuild.sh. Select option 1) toolchain-core-aarch64

This will execute process of building a cross-compiler. During this process packages will be downloaded from Internet. This process can take up to 2 hours. If there are some missing dependencies, install them with 'sudo apt install' and restart this step.

5) Run ./rebuild.sh again. Select option 2) core-raspi-aarch64

This will build system files for 64-bit Raspberry Pi AROS. This process can take around an hour.

6) Run ./recreate-sdcard.sh

This will create an sdcard.img file with contents of previous step.

7) Run ./run-qemu.sh

This will start QEMU with SD card image and ROM images. It will boot into AROS.


=====32bit=====

Ubuntu VM approach to compiling [http://lallafa.de/blog/2013/06/building-aros-hosted-for-raspbian/ Linux hosted AROS June 04, 2013]

 ../AROS/configure --target=linux-armhf  --enable-includes=/usr/arm-linux-gnueabihf/include --x-includes=/usr/arm-linux-gnueabihf/include --x-libraries=/usr/arm-linux-gnueabihf/lib

arm-elf- is symbol-linked to arm-linux-gnueabi- (arm-linux-gnueabi- is more correct in this case, because it's going to be compiling the ARM AROSBootstrap for ARM Linux)

*armel - many of the &quot;android&quot; machines require since the entire OS is made for soft float VFP. 
*armfp - Efika MX target, Raspberry PI, EfikaMX, Pandora and virtually everything (VFP)

Keep in mind it's possible to start hardfp AROS hosted on softfp system, though, as long as no calls between AROS and host require floating point parameters. NOTE: hardfloat objects *cannot* be linked with softfloat objects - they have a different ABI.

Just keep in mind the arm nightly build machine is quite complex beast. It needs the x86_64 host compiler to compile AROS tools. The arm version is built every night using gcc-4.6.2 crosscompiler (built together with AROS) and successfully builds armel and armhf linux hosted targets.

*needs an AROS code compiler for ARM target 
*as well as unix compiler for ARM linux host (would be best to have both softfp and armhf, we have softfp only now) with full set of libraries and includes.

with—disable-crosstools  $AROS_CC  is always a wrapper around $KERNEL_CC  ?  If  so,  this  is  wrong for some ports. This can break Darwin, Windows and Android port. 
Yes,  Android  port  will  build.  And  even  work. But it's not good because  the  port  will  not  be ABI-compatible with other ARM ports. Android's ABI is different from GNUEABI. For example:

&lt;pre&gt;
enum test {foo, bar};
enum test testvar;
&lt;/pre&gt;

sizeof(testvar)  will  be  equal  to sizeof(int) in GNUEABI (Linux and AROS)  and  sizeof(short)  on  Android. This affects linking objects from static linklibs, for example.

Previously everything worked because $AROS_CC was a wrapper on top of $HOST_CC. And a real crosscompiler was used on non-ELF hosts.

Android is the same. $KERNEL_CC is incompatible with AROS.

compiler=kernel  is  appropriate _ONLY FOR CODE WHICH RUNS ON HOST OS_ (or  barebone  hardware,  if  we  talk  about  native).  This includes bootstraps,  their  linklibs, and host-side dynamic libraries (Windows makes extensive use of them because of architectural considerations.

No single AROS object should be compiled with this setting. $KERNEL_CC is really compatible with AROS *ONLY IN LINUX-HOSTED* and no more. On other systems (Darwin, Windows,  Android) this is not true any more, and compiler=kernel is never going to work.

If  you  want  to  compile your AROS module against host OS includes, append  the  following  to  USER_INCLUDES  (or  USER_CFLAGS,  this  is effectively the same):

 -isystem $(GENINCDIR) $(KERNEL_INCLUDES)

$(KERNEL_INCLUDES) expands to:

 -isystem  &lt;your_os_includes&gt;  -isystem  &lt;host_OS_gcc_private_includes&gt;
 -nostdinc

This makes AROS compiler adhering to host OS APIs.

If you want some preprocessor symbols based on what your host OS actually is, add something like -DHOST_OS_$(AROS_HOST_ARCH).

Why is there $(GENINCDIR) at all? Because host OS has its own libc includes, which would conflict with AROS ones. And the host OS libc is not binary-compatible with AROS one.

Why doesn't Windows-hosted port use $(KERNEL_INCLUDES) ? Because WinAPI includes conflict with AROS ones in fundamental typedefs, like WORD, BYTE and BOOL. It's almost impossible to deal with this in any other way than rewriting WinAPI definitions using AROS types.

Building under centos 6.3 (i386) currently, and AROS creates the toolchain itself. haven't yet committed the necessary changes but &quot;./configure --target=raspi-armhf&quot; is enough to start, then &quot;make arosboot-raspi&quot; will generate arosraspi.img (containing the bootstrap, kernel.resource, and exec.library) as well as arosraspi.rom (containing all the other essentials components such as dos, graphics etc).  It will also copy over a config.txt file to make the raspi bootstrap code load the correct kernel, and a cmdline.txt that enables exec debug output.

*armel = typically Debian 6, Ubuntu Maverick, Android, 
*armhf = typically Debian 7, Debian 8, Ubuntu Precise,

Cross-compiling Ubuntu ARM softfp 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armel' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armel] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armel.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabi libx11-dev:armel libsdl-dev:armel
&lt;/pre&gt;

&lt;pre&gt;
 ./configure --target=linux-arm --x-includes=/usr/include \
             --enable-includes=/usr/arm-linux-gnueabi/include
&lt;/pre&gt;

Cross-compiling Ubuntu ARM hard-float 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armhf' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armhf] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armhf.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabihf libx11-dev:armhf libsdl-dev:armhf
&lt;/pre&gt;

&lt;pre&gt;
    ./configure --target=linux-armhf --x-includes=/usr/include \
                --enable-includes=/usr/arm-linux-gnueabihf/include
&lt;/pre&gt;

Now, the AROS build is configured properly and all you need to do is:

 make


==Build==

===64bit===

[https://github.com/aros-development-team/AROS/blob/7016ce28bfdb754182edb16011c98faaf5413c29/arch/aarch64-raspi/boot/mmakefile.src#L180 boot makefile] 


===32bit===


# download/checkout the source someplace, e.g. /build/AROS-Src/
# make a directory to store external sources AROS downloads, e.g. /build/Ports
# make a build directory, e.g. /build/aros-raspi-armhf
# cd into the build dir, configure, and then run make -:

&lt;pre&gt;
&gt;cd /build/aros-raspi-armhf
&gt;/build/AROS-Src/configure --target=raspberrypi-armhf --with-serial-debug --enable-ccache --with-portssources=/build/Ports
&gt;make
&gt;make arosboot-raspi
&lt;/pre&gt;

then copy the files from /build/aros-raspi-armhf/bin/raspi-armhf/AROS/ onto an sdcard, and download/copy the Raspi firmware files onto it.

You should then be able to boot the sdcard on your RasPi.

The current W.I.P tree to svn. it can be built as follows ..
&lt;pre&gt;
./configure --target=raspi-armhf
make arosboot-raspi
&lt;/pre&gt;

That will generate arosraspi.img, arosraspi.rom and config.txt in bin/raspi-arm/AROS - so either copy just those files to a fat formatted SD card (with the firmware files on), or copy the whole contents of the AROS folder.

NB - if you have a Linux/other install, backup the existing config.txt first

arosraspi.img contains the bootstrap (which has very basic mailbox code, framebuffer/gpio init, and console &quot;emulation&quot; via code pinched from our libbootconsole), kernel.resource, and exec.library

arosraspi.rom contains all the other components needed to boot AROS.

The config.txt file will tell the RasPI bootstrap to load the arosraspi kernel and ramdisk (rom).

the bootstrap has minimal mailbox code, planning on adding either a resource or library that driver/app code will use to access it (likewise for GPIO)


Help building AROS hosted on Linux ARM

Was looking a way to use more my Handheld ARM based called Pyra (Dragonbox Pyra) an ARM (Omap5 cpu with 4GB ram) linux based machine (Debian Buster v10 with kernel 5.6.19 adapted) and have a try to compile the latest Aros sources by Deadwood directly on this device.
Compilation stops after build libpopupmenu.a and trying to build libatomic have this error:

&lt;pre&gt;
    Configuring build in bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic
    configure: WARNING: unrecognized options: --disable-nls, --without-x
    checking for --enable-version-specific-runtime-libs... no
    checking for --enable-generated-files-in-srcdir... no
    checking build system type... arm-unknown-linux-gnu
    checking host system type... arm-unknown-aros
    checking target system type... arm-unknown-aros
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for arm-aros-strip... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-strip
    checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
    checking for gawk... no
    checking for mawk... mawk
    checking whether make sets $(MAKE)... yes
    checking whether make supports nested variables... yes
    checking for arm-aros-gcc... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-gcc
    checking whether the C compiler works... no
    configure: error: in /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic':
    configure: error: C compiler cannot create executables
    See config.log' for more details
    make[2]: *** [mmakefile:4489: /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic/.configured] Error 77
    [MMAKE] make --no-print-directory TOP=/media/farox/pyra2/arosbuilds/toolchain-core-armhf-build SRCDIR=/media/farox/pyra2/arosbuilds/AROS CURDIR=tools/crosstools/gnu TARGET=tools-crosstools-gcc-libatomic-configure -s --file=mmakefile tools-crosstools-gcc-libatomic-configure failed: 512
    [MMAKE] Error: Error while running make in tools/crosstools/gnu: No such file or directory
    make[1]: *** [Makefile:361: linklibs-libatomic] Error 10
    make: *** [Makefile:183: crosstools] Error 2
&lt;/pre&gt;


looking at config.log on arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic

found that arosbuilds/toolchain-core-armhf/arm-aros-ld: cannot find -laeabi
so do make linklibs-aeabi-arm-quick
and the missing lib was built.

now the next stop is at
fatal error: bits/libc-header-start.h: No such file or directory
and
fatal error: sys/cdefs.h: No such file or directory
in many places so after checking that have this missing include files i have noted that my include path is a bit different, standard searching path is /usr/arm-linux-gnueabihf but in my system is /usr/include/arm-linux-gnueabihf
so if i add my path to some mmakefiles compilation goes on....but is a better way to add this path to avoid every mmakefiles to be changed?

fixed with adding
-I/usr/include/arm-linux-gnueabihf
to where is missing on mmakefiles like
USER_INCLUDES := -isystem $(GENINCDIR) -I/usr/include/arm-linux-gnueabihf $(KERNEL_INCLUDES)

P.s. I have changed many mmakefiles and have at least compiled (after many hours) the toolchain doing make every time in arosbuilds/toolchain-core-armhf-build (also have to disable making tests under cplusplus but don't remember the directory ...) but ask an help to have an automated way to correctly build without modify mmakefiles.


Last time built armhf target was around 2 years ago. At that point built is via cross-compilation from linux (ubuntu 22.04) using linux armhf crosscompiler (this can explain the path differences you are experiencing) as well as using AROS gcc cross-compiler in version 6.5.0 (build with option 21) in rebuild.sh). Since then AROS GCC has been updated to 10.5.0 and don't believe anyone tried to build the armhf target again.

My suggestion would be to downgrade GCC to 6.5.0 (via editing AROS/config/gcc_def file) and try to first build using cross-compilation from x86_64 linux. Once that works, you will have a &quot;template&quot; to compare to native compilation under arm linux.


Thanks for your suggestion...but think the toolchain with GCC 10.5.0 is compilable if i found a way to pass the path of my system to the script that build (option 21 on rebuild).
The other only changes are (but don't know where to modify...) is to add the build of libaeabi and disable the building of some tests under cplusplus that use exceptions and is not supported under ARM. try to crosscompile with my Linux amd64 PC.

For paths look into core-linux-armhf/bin/linux-armhf/gen/config/target.cfg. A number of build-wide variable is set there containing paths to local build system. These variables and the target.cfg file are generated by AROS ./configure script.

Thanks compilation now go forward...changed target.cfg under &quot;toolchain-core-armhf-build/bin/linux-arm/gen/config&quot; and do make on &quot;toolchain-core-armhf-build&quot; dir.

Need to find where to enable build libaeabi.a so can build the entire toolchain with option 21 of rebuild.sh


Found something that looks like libeabi in AROS/arm-all/arm-aeabi/mmakefile.src. Try adding a third line there:

#MM- linklibs-armhd : libklibs-aeabi-arm

Don't remember needing this library. Possibly the 6.5.0 GCC somehow does this while 10.5.0 is missing this.

Try adding this line (and the variant &quot;linklibs-armhf&quot; instead of hd) but it did not solve the automatic building of the missing lib. I must do &quot;linklibs-aeabi-arm-quick&quot;.
Anyway after have build the aeabi lib i succefully built the toolchain (after many hours...). Smile

To test I restarted from selecting option 21 (on rebuild.sh) but after many hours i get the same error of the kernel includes not found...maybe i need to modify the configure script for my case.

With the toolchain built i try to build the core-linux-armhf (DEBUG) (option 22) but after a while it stopped with
&quot;cannot find -laeabi &quot; so i made it built manually...and now i can continue compiling...i'll let you know if all goes ok.


== Hardware ==

===64bit===


====BCM2712====

With the Pi5 

Broadcom VideoCore 7 vc7 is an integrated GPU with 12 cores and up to 800 MHz clock. VideoCore VII is capable of OpenGL ES 3.1 and Vulkan 1.2. The driver support for the Raspberry Pi continues to build upon the [https://lore.kernel.org/dri-devel/20230928114532.167854-1-itoral@igalia.com/ open-source V3D driver] stack within [https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450 Mesa] hopefully be merged for Mesa 23.3. x265 HEVC accelerated untested, x264/h.264 and VP9 cpu only. 

*Raspberry Pi M.2 HAT+ Expansion Board 
*Geekworm X1001 PCIe to M.2 Key-M NVMe
*Geekworm X1003 PCIe to M.2 HAT NVMe SSD PIP Board for Raspberry Pi 5 
*Pineboards Pi Hut HatDrive! M.2 HAT 2024/V4 
*Hat+ Gen2 Gen3 Nvme
*GeeekPi 52Pi N04 for Raspberry Pi 5 NVME M.2
*


*2024 RPI AI HAT    - Hailo  20TOPs  no LLMs 
*2026 RPI AI HAT+ 2 - Hailo  40TOPs  slightly better? 


[https://www.raspberrypi.com/documentation/accessories/camera.html Cameras for Pi]
*Raspberry Pi camera module, the V3 with Sony IMX708 back-illuminated CMOS 12 Megapixel sensor
*Raspberry Pi Camera Module V2 – 8MP Sony IMX219 Sensor
*Raspberry Pi camera Rev 1.3, 5MP 1080P OV5647 image/video module, 2592 x 1944 pixels


====BCM2711====

With the Pi4 an ARM a72 cpu is about x3 times the size of an a53 in the Pi3 

the 2711b line used more power when idle, compared to the 2711c 

*2018 Raspberry Pi PoE HAT Power Over Ethernet Hat - design issues 
*2020 Raspberry Pi PoE+ HAT Power Over Ethernet Hat Pi3b+ Pi4 only - better design 
*Waveshare PoE HAT (B) with cooling fan for Raspberry Pi 3B+/4B 802.3af PoE 

*[https://github.com/axizo-pi/V3DLib vc6 V3D 4.2] is derived from [https://docs.broadcom.com/doc/12358545 vc4], but it is [https://docs.mesa3d.org/drivers/v3d.html significantly different] 
The QPU pipeline stays mostly the same, you still have an add ALU and a multiply ALU and it can issue two ALU OPs per cycle. There is still 4 SIMD lanes, interleaved over 4 cycles.
The instruction encoding for the QPUs is different, but the core instructions are the same.

Instructions for packed 8 bit int math has been dropped, along with most of the pack modes.
Instructions for packed 16bit float math has been added (2 floats at in a single operation)
With vc5/vc6, you write two packed 16f value to the tilebuffer (or four writes of 32f, if you are using the rgba32f framebuffer). And there is a handy vfpack operation which allows you to pack two f32s into a single 32bit value in a single instruction. You can vfpack directly into the tile buffer register.

the multiply ALU can now fadd, so you can issue two fadds per instruction. the add ALU has gained a bunch of new instructions 

the A and B register files have been merged. You still only get an A read and a B read per instruction, but they read from one big register file (which means the underlying memory block has gone from two sets of &quot;one read port, one write port&quot; to one &quot;two read ports, one write port&quot; block)

The theoretical max FLOPs per QPU remains the same at two per cycle, other than the bump from 400mhz to 500mhx but it looks like a lot of effort has been put putting those theoretical FLOPs to better use. 
*vc4 could run one or two threads per QPU. When you ran in two thread mode, the available register file halfed to 32 registers.
*vc5 added a four thread per QPU mode, with 16 registers per thread.
*vc6 doubled the size of the register file. You could now use all 64 threads in two thread mode and 32 registers in for thread mode. Single thread mode was removed, you always have at least two threads.

With the threading improvements, the QPUs should spent much less time idle waiting NOPs for memory requests. Most of the design changes have gone to improving the fixed function hardware around the QPUs. A fixed function blend unit has been added, which should reduce load on the QPUs when doing alpha blending. hope software blending is still possible 

The tile buffer can now store upto 4 render targets (up to 128bits per pixel, so if you are using 4 32bit render targets, you can't have a depth buffer)

A MMU, allowing a much simpler/faster kernel driver.

Many more texture formats, framebuffer formats.

h264/x264 as Pi3 

All the features needed for opengl es 3.0 

H.265 / HEVC decoder is a HEVCv2 Main 4:4:4 10 design supporting bitstreams up to profile 5.1
HEVC hardware decode supports 4kp60, 10-bit. Audio output is pretty much unchanged, but the HDMI audio channels now support 8x192kHz bitrates 

Each ALU typically have 2 floating point operators, and as you pointed out in a earlier post videocore 6 is no exception, with both a multiply and additive floating point operator. Thus theoretical GFLOPs are calculated with both operators in mind. That is what the 2 in my formula represents, and is common across any modern programmable shader, whether you calculate Nvidia, AMD, Intel, Boardcom or any other company's GPUs. Total ALUs * 2 * GHz clock = GFLOPs, In the case of Raspberry Pi 3, it's 24 ALUs * 2 operators * 0.4GHz = 19.2GFLOPs
If the Videocore 6 does indeed only have 16 ALUs (16 * 2 * 0.5GHz), you'd have only 16GFLOPs but they are better utilised 

Possible maximum performance 
&lt;pre&gt;
VideoCore IV @ 250MHz: 250 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 24 Gflop/s
VideoCore IV @ 300MHz: 300 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 28.8 Gflop/s
VideoCore VI @ 500MHz: 500 [MHz] x 2 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 32 Gflop/s
&lt;/pre&gt;

Faster LPDDR4 memory.


====BCM2837==== 

With the Pi3 
* Broadcom BCM43438 chip provides 2.4&amp;nbsp;GHz 802.11n wireless LAN, Bluetooth Low Energy, and Bluetooth 4.1 Classic radio support, 3B+ [https://github.com/aros-development-team/AROS/commit/afa5bc0bb17d5dd06bcfdbac00853a3799ca8d76 LAN7515] 

The overclock ability has diminished with each chip version as the energy usage has increased. BCM2837 is one of the warmest yet and benefits from active fan cooling if all four cpu cores are in use for a short while. Video playback maybe affected due to the lack of custom support in the GPU with Aros. 5 V / 2.4 or 2.5 amp power supply recommended if all four cpu cores are running, else throttling (cpu slowdown) might occur. 

[https://github.com/hermanhermitage/videocoreiv/wiki/VideoCore-IV-Programmers-Manual Dual VDP] and scalable QPU in [https://docs.mesa3d.org/drivers/vc4.html VC4] and x.264/h.264 accelerated untested only and VP9 on cpu or neon help 


ARMv8-A has [https://developer.arm.com/documentation/102412/0100/Privilege-and-Exception-levels privilege levels] where userspace typically runs at ‘EL0’, the kernel at ‘EL1’ or ‘EL2’ and the firmware at the highest level ‘EL3’. 


===32bit===

=== Core Kernel ===


====BCM2708(family)====
which includes the [http://elinux.org/RPi_Hardware BCM2835] (ARM1176JZF-S 700&amp;nbsp;MHz CPU + VideoCore IV GPU + up to 1GB RAM)

*Framebuffer (fb) using mailbox 
*IRQ scheduler, etc 
*Arasan based SD Card controller 
*Synopsis DesignWare USB 2.0 OTG controller [http://networkdirection.net/index.php?option=com_content&amp;view=article&amp;id=106:rasperry-pi-usb-controller&amp;catid=45:raspberry-pi&amp;Itemid=54 Unofficial DOCS pdf],  [dwc_otg.c FreeBSD], [], [https://www.riscosopen.org/viewer/view/mixed/RiscOS/Sources/HWSupport/USB/Controllers/DWCDriver/ RiscOS USB Driver], [https://www.riscosopen.org/forum/forums/5/topics/878 RiscOS USB Discussion], [https://www.riscosopen.org/forum/forums/11/topics/1893 Other USB RiscOS], [http://plan9.bell-labs.com/plan9/index.html Plan9 Miller's usb] http://plan9.bell-labs.com/sources/contrib/miller/, [https://github.com/Chadderz121/csud CSUD driver], 
*[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf SMSC 9512] USB LAN/Hub chip 
*CMOS RAM 
*VCHIQ port which sends messages to the GPU e.g. for mouse, keyboard, audio on HDMI, etc 
*Audio Driver 
*Serial Peripheral Interface Bus (SPI) 
*[http://www.susa.net/wordpress/2012/06/raspberry-pi-pcf8563-real-time-clock-rtc/ I2C registers]
*I2S 
*Universal Asynchronous Receiver Transmitter (UART) 
*[http://elinux.org/RPi_BCM2835_GPIOs GPIOs] and [http://www.adafruit.com/blog/2012/08/17/broadcom-bcm2835-peripheral-memory-map-and-gpio-alternate-use-chart-piday-raspberrypi-raspberry_pi/ Alternative view of GPIO]

BCM2836 
* For Pi B+, PI 2 and Pi 3 SMSC LAN9514 chip adding 10/100 Ethernet connectivity and four USB channels to the board

*[http://www.andrewscheller.co.uk/rpi_pcb_modules.html PCB], [http://elinux.org/RPi_Low-level_peripherals Low level features],


 Implemented so far... 

# Modify the configure system so that it correctly builds for the arm hardware float raspi target.
# Implemented the bootstrap to load the aros modules and prepare the arm to jump into them. Reworked the x86 console support so that parts can be stolen for raspi to use since t has no basic functionality to output to the display.
# Implemented a kernel.resource to prepare the raspi for running aros and provide the low level api calls to expose available resources and allow exec, etc function.
# Implemented serial debug support
# Implemented the exec (and kernel) functionality required to make multitasking work (and interrupts, exceptions, syscalls, etc)
# Implemented a timer.device to utilise the hardware timers.
# Implemented a very basic gfx driver to expose the hardware's framebuffer.
# Implemented an SD-Card driver for AROS which presently only supports the raspi's chipset but can easily be modified to support all sd-card hardware and media.
# Fixed the fat filesystem support in AROS so that it can boot on RasPi's normal SD-Card setup. The &quot;rom&quot; image files needed use a different filename than the default linux, etc images so can be easily installed without harming the existing files - you only need to change the loaded images in the config file to get aros to boot.
# Updated the build scripts to automatically download the necessary raspi firmware files and wrap it all up so that you can simply extract the archive to a fat formatted sdcard and boot it on the raspi without having to get anything else.
# fix everything in contrib and ports to build for raspi (needs proper testing/fixes but allows every component to actually compile at least, including owb) + numerous other fixes to get things working on arm/raspi ..


Improvements...

# Implement a USB chipset driver &quot;OR&quot; finish the existing one [https://github.com/aros-development-team/AROS/commit/c07d13c724f944674be5db54fc6a71ee72a01809 usb otg] - the current code is mostly a skeleton that should initialise the chipset and then needs relevant code to support the different transfer types. It also has the &quot;virtual&quot; hub code in place to represent the raspi's USB port (from poseidons p.o.v) 
# Implement a driver for the USB NIC (a few weeks - depends on USB above) 
# Write an [https://github.com/aros-development-team/AROS/commit/d55d0f74d20b769bbb8c8d386e5c1d7a9154f05a audio driver] (a few weeks - independent of USB) and [https://github.com/aros-development-team/AROS/commit/e93a4c245f27a87c9c4c1d39206694b39059998a HDMI]
# fix syscall bug in the current raspi kernel code
# Graphics depend on having a decent &quot;bcmdma.resource&quot; implemented as to use the cpu's dma engine. The sd card driver needs to use it for transfers to/from the controller - and the gfx system needs to use it for &quot;blitting&quot;. 
# [https://github.com/aros-development-team/AROS/commit/4019d84e4975d4dad987a12d57fe108f5ac048e6 Improve the gfx driver], [ vc4gfx HIDD] add [http://dri.freedesktop.org/wiki/VC4/ Gallium3D support] 
# [https://github.com/aros-development-team/AROS/commit/b13905b3e8e45b089f520b44692c81affddd066f Improve] the [https://github.com/aros-development-team/AROS/commit/3a876755c070f5c73c4f53c7f4d35b4f923088b9 sdcard] device driver  - which is also pretty basic but should work with most cards, rework it to also support pci, etc. sd card interfaces on x86 
# The current code using very rudimentary access to the gpio interface - so that should be implemented as some resource for other components to access, as-well as the i2c interface exposed over the gpio interface. that should have a hidd class implemented which uses the gpio resource to communicate.


 Boot up typical for most other OSs before the open sourcing of many binary blobs from 2017 onwards 

On power-up, the rpi [http://www.open.com.au/mikem/bcm2835/ BCM 2835] [https://github.com/hermanhermitage/videocoreiv VideoCore4] GPU, not the ARM CPU, is in control, and the SD card slot is the only peripheral device with power. The firmware burned into the BCM2835's VideoCoreIV GPU PROM requires a DOS-style partition table; a FAT-formatted first partition; and the freely redistributable but closed sourced Broadcom files “bootcode.bin” and “start.elf” in that partition.

The boot sequence carries out several pre-boot tasks

*On powering of the rpi, the GPU reads and executes bootcode.bin, which then loads start.elf 
*The GPU loads the “start.elf” file, eventually, into the L2 cache and then executes it
*configures the memory split for the CPU and GPU
*reads and parses “config.txt” from the same partition on the SD card and applies the settings (like a PC’s BIOS settings)
*loads the “kernel.img” file, again from the same partition
*activates the CPU to begin executing the loaded kernel image

The CPU/GPU memory split is hard-coded into start.elf, so Broadcom provides three start.elf images, to give 32M, 64M, or 128M to the GPU for multimedia performance, and the remainder to the CPU.

RPi uses [https://github.com/raspberrypi/firmware some closed source loaders] and at some point it loads a binary blob named &quot;kernel.img&quot; at 0x8000, at that point there would be a rudimentary Aros alive. If one wants to use the SD-card then there would have to be a driver for the interface and a fat filesystem handler (SD-card has to be formatted to fat filesystem)

Boot code and kernel are now linked together and made into that binary blob, just for starters. Raspberry Pi uses [http://kernelnomicon.org/?p=133 u-boot] and [http://kernelnomicon.org/?p=138 UBoot] as bootloader, there's already some code in the Efika MX port for that. UBoot is a native bootloader and not just for the raspberry pi, it loads after start.elf.

You can find Efika MX port from arch implementations, some hacking is needed for the mmakefile.src'es as iit dates back to before the Aros crosstool era or else you get some weird errors while building. You also need to code the bootstrap and serial handling.

At the moment it seems that a fastest route for the native build would be to make one binary blob without using the package system. Raspberry's memory layout is pretty simple and if the implemented u-boot doesn't support loading other modules 

&lt;pre&gt;
?          - alias for 'help'
mtest      - simple RAM test
autoscr    - run script from memory
base       - print or set address offset
bbm        - BBM sub-system
bdinfo     - print Board Info structure
boot       - boot default, i.e., run 'bootcmd'
bootd      - boot default, i.e., run 'bootcmd'
bootm      - boot application image from memory
bootp      - boot image via network using BootP/TFTP protocol
cmp        - memory compare
coninfo    - print console devices and information
cp         - memory copy
crc32      - checksum calculation
echo       - echo args to console
fatinfo    - print information about filesystem
fatload    - load binary file from a dos filesystem
fatls      - list files in a directory (default /)
go         - start application at address 'addr'
help       - print online help
iminfo     - print header information for application image
itest      - return true/false on integer compare
jade       -
loadb      - load binary file over serial line (kermit mode)
loads      - load S-Record file over serial line
loady      - load binary file over serial line (ymodem mode)
loop       - infinite loop on address range
md         - memory display
mm         - memory modify (auto-incrementing)
mtest      - simple RAM test
mw         - memory write (fill)
nfs        - boot image via network using NFS protocol
nm         - memory modify (constant address)
pci        - list and access PCI Configuration Space
ping       - send ICMP ECHO_REQUEST to network host
printenv   - print environment variables
rarpboot   - boot image via network using RARP/TFTP protocol
reset      - Perform RESET of the CPU
run        - run commands in an environment variable
saveenv    - save environment variables to persistent storage
saves      - save S-Record file over serial line
setenv     - set environment variables
sleep      - delay execution for some time
tftpboot   - boot image via network using TFTP protocol
USB        - USB sub-system
usbboot    - boot from USB device
version    - print monitor version
&lt;/pre&gt;


And there is one more thing about modular ports. In order to actually implement this, your bootstrapping environment should provide the ability to load several files. On PC this is provided by GRUB2. on CHRP you can read filesystem via OpenFirmware, and Sam's Parthenope relies on modified u-boot. If your bootstrap allows to load only a single file, then you stuck with monolithic kickstart. By the way...  u-boot allows not only to boot up a single uImage or zImage, it also allows to write client programs AFAIK. With this approach, you actually can write modular bootstrap for ARM AROS using unmodified u-boot.

Most used [http://www.compulab.co.il/workspace/mediawiki/index.php5/U-Boot_quick_reference uboot options] are fatls usb 0:1,

the reason behind INTB_KERNEL is to allow use of the standard Exec function AddIntServer() to add interrupt handlers for
hardware drivers etc. AmigaOS never used it for abstract hardware drivers. AmigaOS  routed  only  raw  hardware IRQs there. Their assignment was hardcoded. As well as number of them. Actually on AmigaOS every bus has its own interrupt subsystem. For example PCI bus. PCI interrupts on Amiga are routed to a single exec interrupt.  1:1 relationship between CPU  and hardware interrupts is present only on PC.

IMHO we miss things like AddInterrupt/RemInterrupt methods on our PCI subsystem's device class.  PCI bus class should map these methods to whatever is appropriate. This is how it is done on AmigaOS and friends. When these are implemented, raw kernel.resource API will be needed only for several PC-specific drivers with hardwired resources. Exec IRQs are real IRQs only on Amiga hardware. On other machines they can be emulated where appropriate (VBlank is a good example). kernel.resource is meant  to be different, its IRQs are hardware-agnostic, they are plain &quot;Hardware IRQ number X, whatever this means&quot;. They are low-level actually, and meaningful only in the context of a particular system.

Was that not the transition from irq.hidd to kernel.resource? No.  A long time ago there was another hacky bit named INTB_TIMERTICK. It was &quot;abstract timer interrupt&quot;, used by timer.device. It was the same as VBlank, but with larger frequency. I removed it, because kernel.resource API was a cleaner way to access this interrupt. Furthermore, there can be more than one timer in the system. Thinking about bringing back timer HIDD definitions again. hpet.resource is a bad idea.

Can someone please enlighten me a little on how the scheduler is meant to work?
 
Poseidon.library creates its &quot;Poseidon Event Task&quot; during RTF_COLDSTART -&gt; then calls Wait(), and ends up in limbo because wait disables interrupts (used for the scheduler heartbeat), and basically waits forever because the sigbit is never set, since krnSwitch doesn't switch the task unless TF_SWITCH is set, and no codepath run during this seems to set it?? TF_SWITCH does not disable/enable switching. This flag just enables to run user-supplied hook when the task is being switched away. It is completely safe to call Wait() in Disable()d state. Doing this actually temporarily breaks this state. IDNestCnt gets remembered in struct Task, then next task is selected, and its IDNestCnt is restored in sysbase (see kernel_scheduler.c). If there are no other tasks, then your cpu_Dispatch() should enable interrupts on the CPU and enter idle mode. See x86 implementation for good example.

You miss what happens next...
 1. KrnSwitch() saves context of your task, saves IDNestCnt (core_Switch() and cpu_Switch()), then drops into cpu_Dispatch().
 2. cpu_Dispatch() calls core_Dispatch. Then two cases are possible:
 2a. There is a READY task. It is picked up, its IDNestCnt is restored in SysBase, then cpu_Dispatch() needs to restore registers and exit. The next task is run.
 2b. There are no READY tasks. core_Dispatch() returns NULL. In this case your cpu_Dispatch() should enter idle loop. It should just enable interrupts on the CPU and put it on halt. This allows it to process hardware interrupts. Eventually some of your interrupt handlers wakes up your task and puts it into READY list.

My heartbeat interrupt has been slowed atm to help debugging - but it never actually gets a chance to fire because of the Wait() disabling interrupts. Perhaps you have forgotten to enable interrupts in your idle loop.

There is a change in the format of AROS executables. Until now we were using Elf RELocable files which are usually used as intermediate object files. We had them for various reasons, one of them was how AROS files were built in the past. That days we had no real aros cross compiler and the option to embed relocation data in unix executables (or in executable files in general) was rather new and not every linux/unix system had it. Therefore we have decided to use intermediate files. Although it was somehow working (and it is still working :-)), it has some drawbacks. Therefore decided to introduce real Elf EXEC types, in first turn implemented on ARM target with option to expand in future to all other AROS architectures.

The first patch was pretty easy and appeared to work somehow. It generated nice executables with embedded relocation info. Not only that, it also removed all global symbols adjusting relocation data to be relative to the beginning of the sections. That move reduced number of symbols in each executable significantly (depending on the file between 20 and 80% of all symbols could be removed). The only symbols that stayed in the file are local ones - due to the nature of the patch wasn't able to remove them since we have not seen them in the symbol hash table.

The patch didn't worked though. The files were relocated, AROS kernel loaded, but it crashed very early. What happened? Well, the nature of ARM relocations happened :)

Most of the relocation data on all machines is rather simple. Relocation can be absolute or pc-relative, sometimes the offset has to be bit shifted. On ARM v7 there is another one. There, when one wants to load an address of function/variable into register a combination of two instructions can be used: movw and movt. The first one loads immediate into lower 16 bits of a register while clearing upper 16 bits. The second one loads immediate into upper 16 bits without touching lower halfword. Loading of a pointer into a register looks like this:

        movw r0, #:lower16:label

        movt   r0, #:upper16:label

In this case there are two relocations - one for lower halfword and another for upper. If an overflow of lower 16 bits occurs during relocation process, the upper one should be updated as well. Unfortunately with current patch and with typical ARM executables there is not enough information to perform the calculations.

There are two options - the first one would be to give up and go back to &quot;fake&quot; executables, another one would be to change from REL to RELA relocation info. The latter contains an addend, extra data which can be used to perform all the relocation calculations I need.

Decided for the second option. The patch is already in the works. There is another function for the binutils' bfd backend to perform the final relocation. There can decide what to do with every reloc info, modify data and eventually strip some symbols. An advantage is - at this stage of the linking process have also full access to all local symbols so can change all relocations section relative and eventually strip all symbols from the files. 


 GPU 

VCore developed by Alphamosaic Ltd and now owned by Broadcom. Most of start.elf runs on the GPU.   Placing ALL the userland GPU code in the videocore.hidd isn't going to be a terribly big problem because the code they published is nothing more than a shim that sends data straight to the GPU to execute.

The good news about this is that we only need to write our HIDD using the OpenVG API.   The shim is relatively small codewise and lives in the ARM memory (the actual OpenVG code itself lives in the GPU RAM area and its loaded from start.elf).   That's also the bad news.  Our driver has to translate AROS video calls to OpenVG calls, for most tasks it should be easy, for some, not so much.  It's still probably less difficult and less work, than controlling the GPU directly.

The other good news is that anything done through OpenVG happens on the GPU, its truly accelerated.   It also has some nice font functions, meaning we can lead into an accelerated text mode later.

Basically, AROS resets or locks up when it tries to use AROS_ATOMIC_INC or DEC.  If I comment out the byte/word operations in the header files and use non-atomic operations, the code works as expected.
 
have read that the L1 cache needs to be enabled to use LDREX and co (which I also read is only meant to be used on multi processor systems with shared memory) - however I am certain this is correctly enabled.

If you are using LREX or STREX, you should have L1 cache enabled, at least on the ARM CPU I work with at work.

L1 cache is enabled by enabling the MMU *AND* setting the C and I bits in the CPU - the C bit is ignored, and the I bit only covers the 16 byte instruction pipeline if the MMU is not enabled.

Can you verify that your assembly is generating LDREX/STREX? From the behavior, it almost sounds like its generating the default Semaphore locked atomics.
 Impossible. There are no semaphore-locked atomics. There are Disable()/Enable()-based ones instead. And there's a special #define AROS_NO_ATOMIC_OPERATIONS in this case, which tweaks Disable()/Enable() implementations not to recurse forever.
 I have tested this on ARMv5 which does not have ldrex/strex, it works fine. On those ARMs there's no way to have real atomics. On other OSes (like Linux) this is done by introducing things like atomic_t, which appears to be a complex structure, holding the value together with accompanying spinlock (implemented using swp).

    #warning &quot;TODO: lookup optimal mmu table settings for raspi memory&quot;
        /* Set up an identity-mapping for all 4GB */
        for(x = 0; x &lt; 4096; x ++)
        {
            pagetable[x] = x&lt;&lt;20 | (0x40002|0x80000|0x010000|0x00C00|0x04);
        }

Shouldn't there be a second loop that sets the 'C' bit in the descriptor for the RAM pages?

Currently, you have TEX=0, C=0, B=1 for all pages (Shared Device).

You should have TEX=0, C=1, B=0 for RAM (Write-Through, Cached)

    So ..
     
     pagetable[x] = x&lt;&lt;20 | 2;

     
    should be enough?

No, for RAM you need to change the '| 0x40' to '| 0x80'

tell dosboot the correct defaults to use

Please don't do this. This bootconfig.c is a deprecated legacy thing. I wanted it to go away completely with time. Instead,  display  drivers  should auto-install themselves during own initialization phase. I. e. detect hardware=&gt;instantiate itself. This   should   make  things way simpler. With this approach you only need  to add the driver into KS image to get the device autobooted. No hardcoded stuff. 
Currently  VESA  and  VGA drivers do this, look there for examples. never rewrote ATI driver because i don't have any test system for it.

they defined a smaller AROSCPUContext than the ExceptionContext - yet reference it as ExceptionContext in other places, and since it hasn't allocated enough storage for ExceptionContext, are corrupting memory/the structure (since the elements that are there don't map 1 to 1 with the exception context).

AFAIK, AROS has been moving in a different direction to this in recent years. It is the job of graphics HIDDs to allocate bitmaps etc. so that they have the most suitable characteristics, including allocating them from GPU RAM where possible. The concept of chip RAM is only for legacy code, and most if not all non-68k platforms should have all system RAM
marked as chip.

BTW, is the video processing code you mention CPU code or GPU code?

Also, IIRC we have support for &quot;external memory allocators&quot;. Perhaps that's what we need for the allocation of GPU RAM through the mailbox.

All hosted and x86 native ports should use proper context formats.

trying to clarify if the vblank handler has to have run by this point to prevent this deadlock. Actually, no. Unless you have installed VBlank handler which should wake up at some point. Without VBlank there will be no quantum count. Consequently, there will be no forced preemption. But the rest will work, and multitasking will be cooperative (switch happens only when current task voluntarily gives up the CPU). Does it depend on the vblank having run before this point? and if yes what does that mean on systems where it might be able to run enough code (e.g. get to this point) before the vblank interrupt has triggered? What is it waiting for? It could wait for timer, in this case you need timer.device working. VBlank is currently needed for exec's quantum counter. In current native ports we have only a single timer, which is served by timer.device. VBlank is simulated by timer.device also. If your machine has two timers, then you can use one of them for VBlank, and another for timer.device, this will simplify things down. VBlank needs to be 50 Hz for historical reasons, many programs use it as cheap timer. I am periodically thinking about making some abstract mechanism to be able to change quantum source (and untie it from 50 Hz), but have no time to come up with something good. Additionally i started disliking timer.device hardcoded design when PC has got many timers (old 8253, APIC, HPET).
Currently i think there should be some low-level entity representing tick source. timer.device should just select the most appropriate source for its units.
The BCM2835 has 4 GPU based timer sources - 2 are used by the GPU, so im using Timer3 for our heartbeat and the remaining one will be free to the system. There is also the less capable ARM timer but that is dependent on the CPU frequency. Very good. You won't need any emulation. Set the heartbeat to 50 Hz and drive VBlank from it. Use other timer for MicroHZ.

Can you use the 'econsole.hook' I make for debugging the Sam460 via the serial port?
It provides a before-anything-else shell prompt on the serial port.  You can then do 'NewCLI' to test your graphics, or use any DOS command in shellcommands.resource.

You should just be able to add econsole.hook to your module list, and use 'econsole' in your bootargs.

So long as you have a working Exec/RawMayGetChar and Exec/RawPutChar, it should work.

Also make sure to add shell.resource and shellcommands.resource for this.

That should have done it.

If you set &quot;#define DEBUG 1&quot; in  arch/all-native/econsole/econsole.c, do you get any additional serial output?

have added it to the build and added econsole to the command line - and can see the bootloader picks up on the emergency bootconsole tag, but I still only get the insert bootable media display?

Im assuming it exposes a fake filesystem that tricks aros into booting?
The contents of which are: ECON:AROS.boot

Way to handle the scheduling code? The implementations I had been following were causing problems, due to cascading interrupts which I cant handle properly in the asm stubs just now (when they break disable etc.) - since it means detecting the interrupted codes cpu mode and getting the correct sp/lr for it, and that's just too tedious for arm.
 
To work around this ive added a system idle task which does nothing - and when the scheduling code has no task to run switches this in and lets it run, thereby allowing the interrupts etc to resume until something does need to happen.
 
Also, by adding accounting code to cpu_Switch() and cpu_Dispatch(), it should allow the system to log idle time correctly (as well as running tasks).
 
have thought of also adding an additional task that never runs, solely to record time spent in IRQ handlers, but I digress..

was under the impression that kernel.resource should *never* be used outside of exec.library. This is a wrong impression.
Michal started designing it because portable nature of AROS does not fit well into exec's API with all its assumptions. So, he started the new, hardware-agnostic kernel API from scratch. Yes, exec sits on top of it in places. But kernel always meant to be open thing. Otherwise it would not exist. 
it wasn't meant to be just used willy nilly by user code - but by lower system components (e.g. exec) so that they could be implemented in a more generic fashion, and the kernel resource itself hide the systems quirks.

Adding new things there perfectly keeps up with our decision to minimize AROS-specific intervention into APIs which can clash with MorphOS or Amiga OS4 extensions. We want at least source-level compatibility there. Binary compatibility on PPC would be extremely cool, but at the other hand we have no maintainer for this, as well as their ABIs splintering. 
It depends on what exactly is being implemented - there's no reason we should have everything crammed into kernel.resource if it doesn't need to be (i.e. if its better suited as a separate component/subsystem in its own right)

The _LE versions are for when you have endian swapping taking place.  If the graphics are the same endian as the CPU, no swapping should occur.  I ran into a similar terminology problem in SDL with a friend insisting that his Radeon 7000 on his PC was big-endian.  It is not, it just uses the same endianness for the graphics card and the CPU so no swapping was necessary.  They were both little-endian.
The _LE versions are because the PixFmts refer to the bitmap data being in big endian format in memory, for which the normal version would need to do endianness conversion before applying the shifts/masks. on this platform it is in _LE in memory also so we don't need the conversion hence using the _LE version of the call). would use _LE (if it's really little endian 16 bit mode).

 
What is the bare minimum needed to implement a framebuffer based gfx driver, with our software handling the rest?

Have tried with just a gfx class that only expose new/dispose/newbitmap - and having an onscreenbitmap used only for the framebuffer itself (with all other bitmaps being chunkybm, and the framebuffer's superclass also being chunkybm), but that alone isn't enough it seems?
You can use workbench/hidds/sm502/ as your example - it is as simple as I could make it.
So, AROS creates the framebuffer bitmap (verified this) -&gt; so surely it should be capable of then rendeing into it? I don't actually create the framebuffer &quot;bitmap object&quot; myself - only as a result of being asked to. The code I currently have on SVN seems to create the framebuffers bitmap object fine, but then crashes in intuitions DisplayDriver callback.  In particular it crashes performing the getattr on the system default pointer. don't expose MEMF_CHIP in an allocatable form so AllocSpriteData was failing (and other code later doesn't check if the values are valid == illegal memory accesses) 

So far have -:

vc_init: queries the gpus memory, and sets up a fake memory handler for it, then adds the bootmode driver and returns saying all is well
vc_gfxhidd:New: sets up some fake syncmodes to test with and creates the real gfx object.
vc_gfxhidd:NewBitmap: checks if its a framebuffer and uses the onbitmap class or uses the chunkybm class otherwise
vc_onbitmap:New; creates a chunkybm object and then pushes the real framebuffer address into it as the buffer,

vc4 had v8adds, v8subs, v8muld, v8min and v8max which operated on four 8bit uint values packed into a 32bit register. Multiplication was in the range 0.0 to 1.0 and addition/subtraction saturated. There were also a range unpacking/packing modes that allowed you to pack and unpack 8bit values into 32bit registers. 

RasPi has to speak to the &quot;operating system&quot; which runs on the GPU itself and request/free memory - it cant directly manage it itself, and so the managed functions were used to wrap these calls.

The Arm and GPU share memory space. The framebuffer is shared. The Arm can write a pixel and it will appear on the screen (through GPU hardware) without flushing/copying being required.

The GPU can composite multiple FB's in real time - so you have a number of surfaces defined which are rotated etc and  composited in real time to the output. Copying can map from the address space of the Arm to the flat space of the GPU which takes some code, but I don't think whole buffers are copied.

The DMA hardware can also access the whole memory space and can perform 2D fills and blits (no blending). This is documented in the peripheral spec posted. The DMA is just an Arm accessible peripheral and can be set up with low latency (e.g. microseconds).
must use a 0xc0000000-based bus address to access SDRAM, yet non-DMA access should go via a 0x0-based bus address. 
For 2D dma, set TDMODE, and the spec says &quot;interpret the TXFR_LEN register as YLENGTH number of transfers each of XLENGTH, and add the strides to the address after each transfer.&quot; so set STRIDE to pitch of the image, the width is XLENGTH and height is YLENGTH. You would fill by not setting the SRC_INC and point source to your fill data.

The DMA cannot see the ARM's L1 cache, so you would map the framebuffer with ioremap_nocache. Depending on where the source data comes from, it may need an L1 cache flush. The DMA can see the L2 cache. Use 0xC0000000 bus addresses when L2 is disabled and 0x40000000 bus addresses when L2 is enabled. (actually just call virt_to_bus and you'll get the right address out).

openGLES/openVG has high latency. Writing to framebuffer then reading it back is very inefficient (e.g. milliseconds). If you can drive it a unidirectional way, just streaming commands at then that is efficient. openVG is not implemented on top of openGLES - it uses the same hardware but as a first class interface

To improve the Gfx driver, we will need a DMA resource implemented so can use to perform DMA operations. The Gfx driver will need this to perform blits.


Actually MEMF_CHIP has to present, for historical reasons.
This has been never fully agreed upon, but in ports i wrote i exposed the whole memory as MEMF_CHIP. The idea behind this is that CHIP is originally the memory where graphics and sound data can be put. On non-Amiga platforms there are no restrictions on this, so the whole memory is CHIP.
Yes, many old software can misbehave with CHIP memory size larger than 2MB. But this actually applies only to m68k AROS which is going to run m68k binaries. In other cases it's quite logical to fix the program when porting.

As to original question: yes, it's enough to have a framebuffer bitmap (one with aoHidd_BitMap_FrameBuffer set to TRUE) and PutPixel routine. It framebuffer can be served by chunky bitmap class, then you can simply create chunky bitmap with your own buffer (see how VESA driver does this). Chunky PutPixel is already there.

struggling to determine what is the correct pixfmt to use for the 24/16/15 bit gfx modes on the RasPi.  AFAIK it uses RGB565, for 16bit but im unsure what shifts etc should go with it? suffice to say Im getting the wrong colors so far lol.

&lt;pre&gt;
redmask: 0x0000F800
greenmask: 0x000007E0
bluemask: 0x0000001F
alphamask: 0

redshift: 16
greenshift: 21
blueshift: 27
alphashift: 0
&lt;/pre&gt;

It should likely be vHidd_StdPixFmt_RGB16_LE

This stuff is a bit confusing.  The &quot;names&quot; of the stdpixfmts are based on the layout in memory,
ignoring endianess. So for example:

ARGB32: will be 0xAA 0xRR 0xGG 0xBB in memory on both big endian and little endian machines.

The shifts and masks OTOH are based on pixel access (ULONG in this case), so differ depending
on whether you run on big endian machine or little endian machine (that's why there's stdpixfmt_le.h and
stdpixfmt_be.h in rom/hidds/graphics/).

With the 16 bit pixel format it's even more confusing, as for example it's impossible on little endian machine
to describe RGB16 with shifts/masks alone. That's why there's vHidd_PixFmt_SwapPixelBytes_Flag.
(RGB16 == RRRRRGGG GGGBBBBB in memory, and for pixel (WORD) access on little endian machine it needs to
be accessed as GGGBBBBBRRRRRGGGG).

The shifts btw indicate how much to shift the component to the left (!) so that it is moved to the highest bit (31).

The aHidd_PixFmt_StdPixFmt you specify will be ignored most of the time, because when the pixelfmt is registered,
the gfx hidd checks if there's an identical pixfmt (shifts/masks/etc., but ignoring pixfmt-&gt;stdpixfmt) already in the system,
and if so, it uses the already existing one and does not create a new one.

In theory it would be better if gfx drivers could simply/only specify a StdPixFmt without all the shifts/masks stuff when the
gfx driver uses pixfmt which matches one of the stdpixfmts exactly. Another possibility would be for gfx drivers to use
HIDD_Gfx_GetPIxFmt(stdpixfmt_gfx_driver_wants_to_use) and then peek shifts/masks from it and fill out a pixfmt
tag list based on that.
15bit very blue/green: Try to pass same shifts/masks/etc. as in 16 bit pixfmt (maybe you think it's using 15 bit R5G5B5
(or swapped) but it's actually still using 16 bit R5G6B5 (or swapped).
 aHidd_PixFmt_StdPixFmt you pass is mostly ignored. It's the shift/masks/etc. that count.
But I would still pass the correct one (_LE) == whatever rom/hidds/graphics/stdpixfmts_??.h uses
in the entry where you have looked up shifts/masks/etc.

Use the shifts/masks/etc. from the entry in stdpixfmt_le.h (if you are running on little endian machine) or stdpixfmt_be.h (if you
are running on little endian machine) that matches the pixfmt that its meant to be.

0xAA,0xRR,0xGG,0xBB on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_BGRA32)

0xAA,0xRR,0xGG,0xBB on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_BGRA32)

it feels like AROS trashes the alpha component, otherwise it should be 8A8R8G8B.

read on the subject suggest its in 1x5r5g5b (x is ignored) to keep 16bit alignment .
 
Suggests to me that wrong shift/mask are being applied - however going by the 16bit versions it all looks correct to me so I am really confused as to what is happening.

The output image looks to have too much green/blue, and very weak red.


 Kickstart 

The  idea  is  to minimize amount of archirecture-specific modules to make the user's  life  easier.  So,  the kickstart was split into 'base' (which  does  not  contain anything machine-specific) and 'BSP' (Board Support Package) which contains all hardware-specific stuff. This  way,  for  example, distribution makers can save up space on CD and  make  CDs with multiple platform support. Different configuration would load the same base with different BSP's.

Next  there  was some part which is entirely missing on hosted. These are   filesystems.  Hosted  ports  do  not need them to boot up, so on hosted   they  are  left  out.  At  the  other  hand,  they  are  also architecture-agnostic.  So  i put them into 'FS' package (standing for 'filesystem').


 USB 

Poseidon  is  one  more  big part. I made it into separate package in order to allow users to omit it if they don't need it (for example, to run  on retro PCs without USB). Personally i have one. Again, Poseidon is  hardware-agnostic (well, there are USB drivers but HCIs are pretty standard).

AFAIK its HCI 1.0 compliant but not familiar enough with poseidons drivers, nor USB, to just hack away at the existing code.  Perhaps once i'm more familiar with the workings I can merge in the changes needed to get it operating but for now I will focus on getting it running.  Also our drivers have known issues so perhaps a fresh set of eyes might shed some light on what is going wrong.

Another interesting question is whether Poseidon can operate on device side. Is it flexible enough? How similar is being a USB host and USB device? think it will need a bit of work on Poseidon's side.  Until then I will force the driver into Host/Master mode in the init code, but leave open device etc to configure the chipset for either's use - and look at trying to add support for working in Device/Slave mode &amp; switching modes once it's up and running.

Actually USBROMStartup is some kind of kludge. Can there be any alternative? Could device drivers be self-installing, like our HIDDs? This would get rid of need to list them in USBRomStartup.

* Model A and B limited to 150 mA per port. 
* Model B+ and Pi 2 introduced configurable 600 mA to 1.2 A support over all ports - anything above that requires a powered USB hub.

Implementing the hardware driver that Poseidon uses to interact with the USB components.

Have code in place to (try) and initialise the USB chipset, and configure host/device mode operation (though AFAICT Poseidon doesn't support device mode). Started to get the &quot;virtual&quot; root hub written for the single USB port so that Poseidon should at least list it correctly in the GUI - and try to interact with it to find peripherals.


The BCM2835 uses a soft IP block from Synopsys’ DesignWare library (DWC), specifically the block is called dwc_usb_2_0_hs_otg_subsystem-ahb_se (“USB 2.0 Hi-Speed OTG Controller Subsystem w/AHB Interface SE”).

There is no public documentation for this, and pretty much zero chance of anyone getting hold of it even with NDA. However, there's a Linux driver written by Synopsys ([https://github.com/raspberrypi/linux dwc_usb]). Specifically directories [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_common_port] and [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_otg].

The Synopsys code is actually under a fairly permissive licence – it's not GPL, it's similar to BSD (’don't sue us if it breaks’ is pretty much the only clause). So this should not be a barrier to porting the code.

The code is really well written, with a nice partition between the work done by the driver (dwc_otg, which is fairly involved, given the host does more work than a conventional EHCI driver), and the interface to Linux (dwc_common_port).

Probably only need provision of relevant changes to dwc_common_port. Other things to consider....

* Provision of necessary headers to get it to compile
* Provision of necessary functions (main issues are wait queues, threads, work queues, tasklets, timers, spinlocks and mutexes (multithreading) )
* Interfacing between USB stack and the driver. dwc_otg/dwc_otg_hcd_linux.c looks like the place to start.

the Linux bits of the headers are only required for the dwc_common_port library. dwc_common_port includes a variety of crypto functions which are not used – it appears to also be used for ultrawideband (UWB) and wireless USB (WUSB) drivers where crypto will be an issue, but it isn't going to be for plain wired USB.

Every USB driver acts as an USB hub as well in order to let Poseidon control the state of USB ports. The code there was reading status of the only USB port in Raspberry's CPU but when changing the status it erroneously deleted some of the status bits, including the port enable one. It was so because those bits in the status register are of a type Read/WriteToClear. It means, if one does not want to change their value from 1 back to 0, one has to actually write the 0 value. Very practical thing e.g. in interrupt handlers, where one reads the interrupt status register to learn what was the interrupt reason, and writes it back to the same register in order to clear the interrupts. 

After fixing that code it turned out that the communication was still unsuccessful. Apparently the USB device was not understanding the host for some reason. That should not happen since the request sent was one of the standard ones implemented by virtually anything with an USB connector, assumed that Poseidon clears the data caches before forwarding the work to the USB drivers but that's the responsibility of the driver itself. 

The USB device responded and acknowledged the transmission! But why were all the request sent after address change failing with timeout? They should not. Once again, address set is supported just by anything. Tried to contact the device at address 0 once again and there it was, still responding properly. The enlightenment came. The bus address for DMA transmissions was, as it is in many bare metal USB implementations, just the pure memory address of the buffer as seen by the ARM cpu. Have &quot;prefixed&quot; it with the real location of uncached RAM and booted AROS once again. 


Trident saw this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

and this:

    Product     : Vendor: Vdr=0424/PID=EC00
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 255
    SubClass  : 0
    DevProto  : 1
    VendorID  : 1060
    ProductID : 60416
    DevVers   : 0200

and even this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

What are these things? The first one is USB hub built in the Raspberry. Thanks to this one the Pi machines (with exception of Pi0 and computing modules) have more than just one single USB port. The second one is the network chip in raspberry, the third one is my USB SD card reader which have just connected to see what happens. AROS tried, of course, to boot from it ;)

So, the first step towards working USB is done. The control transfers are working as you can see above. Next step is to implement bulk and interrupt transfers, having the basics in place. Finally some error handling will be added and USB for Pi will be as complete as the PC version. 

[http://www.raspyfi.com/raspberry-pi-usb-audio-fix/ Issue with USB Audio]


 Audio 

The Pi 4B is the only Pi that can output HD Audio as an HD Audio passthrough bitstream, and it does it over HDMI. It's possible to use the two HDMI output for separate HDMI video and HDMI audio outputs to allow UHD HDR video and HD Audio with non-UHD HDR compatible AVRs. 

The Pi3B+ and earlier will decode to PCM 5.1/7.1 and output over HDMI.  HDMI is the only interconnect that has a standard for carrying Dolby True HD, DTS HD MA etc. as a bitstream - you can't carry it as a bitstream on any other interface.

Pi3 and Pi4 audio jack output derived from 12bit pulse width modulation is relatively poor. For better, choose USB Audio or I2C versions. 

[https://github.com/raspberrypi/linux/tree/rpi-patches/sound/arm audio] and its [https://github.com/raspberrypi/firmware/issues/2 very high speed message passing interface type of thing VCHI] 

The Model B+ added an additional voltage regulator for the audio output and an additional output driver to drive low-resistance loads like headphones. However it is still using pulse-width modulation (PWM), which has a major impact on sound quality

the old Raspberry Pi used a linear voltage regulator to provide the 3.3V to many of the components on the board while the new one uses a switching regulator. Both can perform reasonably well. However switch mode power supplies often show higher noise figures

Analogue audio

Audio over HDMI rev 1.3 &amp; 1.4


 Ethernet 

10/100 BaseT Ethernet RJ45 socket


 GPIO 

GPIO shouldn't be too bad but bear in mind it is already accessed in places so they would need to allocate pins etc through it (e.g. sdcard to flicker the activity light, serial debug to output data on the GPIO pins)

Probably a resource rather than a device...

Started an i2c driver that will need to allocate GPIO pins. Feel free to work on it if you are interested ;p


 GPU graphics with 2D and 3D acceleration 

Sadly none yet for 32bit but for 64bit... 


 Miscellanous

hdmi issues

Setting the hdmi_force_hotplug=1 makes sure the Pi believes the monitor/TV is really there.

You might also need to set config_hdmi_boost=4 or even higher (up to 9) if your display needs a stronger signal.

If the display is a computer monitor or newer tv, use hdmi_group=1 (auto HDMI use) and if it is an older TV, try hdmi_group=2 (for DMT formats, i.e. for PC monitors) then you HAVE to &quot;set hdmi_drive = 2 to enable HDMI output as this forces HDMI mode rather than DVI mode

Do not set hdmi_safe=1 as that overrides many of the previous options.

Using a shorter or better quality HDMI cable might help. Make sure your Pi's power supply delivers 1 A and not 500 mA.
If you see a problem with the red colour - either absent, or interference - then try a boost

composite video

changing the RCA cable, then the composite port worked out of the box

Boot it as you are doing, without HDMI. If you now plug in the HDMI, do you get the image? In other words, does the Pi think HDMI is connected even when it isn't?

Rename all the files in the first partion of the card except bootcode.bin, start.elf and fixup.dat  What's the result?

Put back config.txt What's the result?

for PAL mode   sdtv_mode=2

dmi_ignore_hotplug Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached
hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected

&lt;pre&gt;
# NOOBS Auto-generated Settings:
#hdmi_force_hotplug=1
#config_hdmi_boost=4
#overscan_left=24
#overscan_right=24
#overscan_top=16
#overscan_bottom=16
#disable_overscan=0
start_x=1
gpu_mem=128
&lt;/pre&gt;

tvservice -c &quot;PAL 4:3&quot;

&lt;pre&gt;
/opt/vc/bin/tvservice -s   or tvservice -s 
state: HPD high|HDMI mode|HDCP off|composite off (0x12001a), 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m CEA
Group CEA has 1 modes:
(native) mode 16: 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m DMT
Group DMT has 0 modes:
&lt;/pre&gt;

sudo amixer cset numid=3 1

forces the audio to the headphone jack, even with the HDMI video output plugged in

config.txt

the hdmi_ignore_edid_audio=1 option sems relevant as it should tell ALSA that the only available audio is analog, no matter what the display says

There are several different ways that these 4 pole (ring) composite analog cables can be wired up, so some work great in some applications and can be a waste of time in others.

What is needed for the Raspberry Pi B+ and above, which like many camcorders needs the ring contact next to the base contact to be the ground.


The wiring for the 4 pole are:

TIP (LEFT AUDIO CHANNEL)

RING 1 (RIGHT AUDIO CHANNEL)

RING 2 (GROUND/EARTH)

RING 3 BASE/SLEEVE (VIDEO) YELLOW

Most Apple based Players and the Microsoft Zune (TM) are wired this way.

Most analogue camcorders are wired this way as well, where the ground in on Ring 2 will work with the Pi although you may need to swap your Video plug with the Right Audio plug.

Nearly all other MP3 players are not wired this way, the ground is on another ring ie the wrong one.


External devices

* Camera Module Omnivision ov5647 Sunny 5MP (NoIR version) V1.3 - NoIR at 850&amp;nbsp;nm, peak at 880&amp;nbsp;nm and trails off at 940&amp;nbsp;nm wavelengths 
* Camera V2 Sony IMX219 V2.1 8mpixel 8MP 8megapixel - 3280 x 2464 pixels - video at 1080p30, 720p60 and 640x480p90 - wider field of view, 62 vs 54 degrees horizontally - 
* Branded WIFI usb BCM43143 dongle

N.B.  dreaded error after changing cameras (stupidly without turning off the power first) and lasted through several power cycles.  It can be a bad 15-pin FFC ribbon cable, when swapped, camera(s) and the Pi itself are working OK. It can be an instance of a cold solder joint on the CSI connector on the pi board.  the camera can be detected (that's done via I2C) but may still not be able to receive image data (done via CSI-2) if something is broken. CSI-2 is uni-directional. Control is generally done via I2C. 
The CSI-2 receiver always writes to memory, not direct to the ISP. That's the way the Broadcom architecture works as it allows multipass processing easily. GPU memory is accessible from the ARM. Processing using the QPU graphics processors may be possible.  currently the only supported sensor is OV5647 and IMX219.  The linux drivers are all in the firmware blob, else you'd  be looking at at least a man-month of work in a fully fledged imaging lab to do a decent tuning of the camera modules' ISP parameters. 
Static electricity maybe an issue for the camera module and slightly less for the pi board.


== References ==


===Good sites to visit===

*[https://github.com/raspberrypi/firmware/tree/master/ Raspberry Pi Firmware build] 
*[https://www.raspberrypi.com/documentation/computers/software-sources.html Documentation] 
*[https://rpilocator.com/ RPiLocator] 


Linux only
*[https://github.com/raspberrypi/linux Raspberry Pi Linux Build] 
*[https://dietpi.com/ DietPi] 
*[http://www.tinycorelinux.net/ports.html piCore]
*[https://wiki.alpinelinux.org/wiki/Raspberry_Pi Alpine Linux] 
*[https://github.com/armbian/build Armbian] 


*[ FydeOS]
*[ TwisterOS based on ChromiumOS] 
*[https://note.com/jamesmondo/n/nc76e31402be8?hl=en BSD] 


*[https://www.raspberrypi.com/software/operating-systems/ PiOS Lite] and then [https://hstwb.firstrealize.com/ HST] 
*[ PiMiga for pi4 and pi5] 
*[ amibian for pi2 and pi3] 
*[ retropie pi1 and 2] 


Other alternative lighter smaller than Pi OS 
*[https://aros.sourceforge.io/nightly1.html Aros 64bit ARMV8 single core] 
*[https://www.riscosopen.org/wiki/documentation/show/Welcome%20to%20RISC%20OS%20Pi RiscOS on Pi3 and Pi4]
*[https://github.com/michalsc/Emu68 ARM based realtime JIT 68k for amiga computers] 
*[https://github.com/JJDSNT/bellatrix/releases/ Alternative use of Emu68 on Pi3b] 
*[https://github.com/stevereaver/uaos uaOS with Emu68k] 
*[https://github.com/aros-development-team/AROS/commit/f80a268607dfae81b2db94755ab4e4d31ccb72d6 m68kemu library reference] 
*[ HaikuOS]
*[https://github.com/raspberrypi/noobs NOOBS] os loader with successor [https://github.com/procount/pinn PINN] 
*[https://github.com/maxnet/berryboot berryboot]

*[https://github.com/brianwiddas/pi-baremetal Bare Metal Access on Pi 32bit] 


Testing procedure is put sd card in, connect board to board if necessary, plug in hdmi and then power nothing else is done especially CSI DSI etc 

[https://www.raspberrypi.com/documentation/computers/compute-module.html CM5] has the same 55mm x 40mm 2x100pin connectors form factor as the CM4 but [https://www.epdtonthenet.net/article/214508/Key-Considerations-When-Migrating-from-Raspberry-Pi-CM4-to-CM5.aspx some pins and other small things] have changed. Will need the [https://raspipcb.com/tech-blog/raspberry-pi-cm4-vs-cm5-difference-in-booting-from-sd-card/ right IO board to suit] 

*Green [ Raspberry Pi Compute Module 5 IO Board REV2 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1967]] - untested 
*Green [ RPi Compute Module 5 IO board REV1 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1751]] - untested 
*Black SupTronics Geekbord X1500 CM5 IO Carrier Board - untested
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*[https://sipeed.com/nanocluster Sipeed NanoCluster] - untested up to 7 CM5 
*Green BentoIO CMX0 - untested 
*Box EDATec ED-CLAWBOX - untested 
*Home Assistant Yellow - Kit with PoE with Raspberry Pi Compute Module 5 - untested 
*Blue [https://www.waveshare.com/wiki/CM5_PoE_BASE_A Waveshare CM5-PoE-BASE-A] - untested 
*Box  Waveshare [ CM5-POE-BOX-A] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-B Waveshare CM5-IO-BASE-B] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-A Waveshare CM5-IO-BASE-A] - untested 
*Blue Waveshare [https://www.waveshare.com/wiki/CM5-NANO-B CM5-NANO-B] - untested 


*[https://carboncomputers.us/products/pi-flux piFlux]
*[https://carboncomputers.us/products/ Zitaotech Hackberry] CM5 lite only - 
*Portable [https://www.waveshare.com/pocketterm35.htm Waveshare PocketTerm35] with Pi4B or Pi5 - untested 
*Box [https://www.clockworkpi.com/uconsole ClockworkPi uConsole][https://www.youtube.com/watch?v=EtI_bAahbR8 CM4 into an adapter or CM3 into so-dimm - Cyberdeck] - untested 


*Green RPi [https://datasheets.raspberrypi.com/cm4io/CM4IO-KiCAD.zip Compute Module 4] [https://datasheets.raspberrypi.com/cm4io/cm4io-datasheet.pdf IO board] V1.4 [https://datasheets.raspberrypi.com/cm4io/CM4IOUSB3-KiCAD.zip USB3] [https://datasheets.raspberrypi.com/cm4io/cm4iousb3-appnote.pdf CM4ISO] [https://datasheets.raspberrypi.com/cm4/cm4-datasheet.pdf Dual100pin] (2020) aka Development Platform Board - untested 
*Purple Pi Hut Cytron CM4 Maker Board - untested 
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*[ KubeSail PiBox mini 2] 
*Home Assistant Yellow with Raspberry Pi Compute Module 4 - untested 
*[ Turing Pi V2] - untested CM4 with 260-pin SO-DIMM socket adapters and/or nvidia jetson nanos - untested 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-C Waveshare CM4-IO-BASE-C] - untested but binary blobs Rev01 Rev02 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-B Waveshare CM4-IO-BASE-B] - untested but binary blobs 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-A Waveshare CM4-IO-BASE-A] - untested but binary blobs 
*Blue [https://www.waveshare.com/wiki/CM4-NANO-B Waveshare CM4-NANO] - untested but usb and audio turned off or rerouted 
*Black [ Seeed Studio with BigTreeTech BTT pad 7] - bin blobs? 


CM3 has a 200 pin sodimm ddr2 connector form factor but not electrically SC0028, SC0029 
*Blue [https://wiki.geekworm.com/CM_IO_Board Geekworm RPi Compute Module IO Board] [https://github.com/geekworm-com/cm-io-board CSI DSI] with CM3 in ddr2 slot underside - '''works''' if SW1 on but CM3+ '''does not''' 
*Green [https://cdn-shop.adafruit.com/product-files/3442/CMIO_schematic.pdf RPi V3 IO board CM3IO] and CM3 Lite - untested 
*Green [https://turingpi.com/ turingpi v1 cluster] - untested up to 7 cm3 7xlan9514 12V discontinued, 3 x Pi4 homelab maybe better 
*Blue [https://www.waveshare.com/wiki/Compute_Module_PoE_Board Waveshare Compute Module PoE Board] and CM3 lite (if not lite, write files to internal eMMC fat32) '''AVOID''' bin blobs 
*Blue [https://www.waveshare.com/compute-module-io-board-plus.htm Waveshare Compute Module IO Board Plus] [https://www.waveshare.com/wiki/Compute_Module_IO_Board_Plus wiki] [https://forums.raspberrypi.com/viewtopic.php?t=235695 pin settings] with CM3+ Lite - '''AVOID''' binary blob 


*[ Pi02w on Geekworm SupTronics X305 Raspberry Pi Zero IO Baseboard] - untested 
*[ Spotpear Pi Zero 2w to Pi3b format-ish] - untested 


*[ pi-top v4] box has 128x64 oled display, micro hdmi, 19Whr battery with pi4 and 15V PD 36W min needed 
*[ pi-top v3] three green pieces, heatsink covers most of the base tray, pi-top hub mk1 lhs and Pi1B Pi2b Pi3b rhs secured from below, black rounded strip with pi-top above keyboard, 13.3&quot; HD 1366 x 768 display, small touchpad, 
*[ pi-top Model 2.0] pi-top on bottom bezel of 14-inch green laptop, large trackpad, keyboard slide down to reveal main system hub on slide rails moved to the right, Raspberry Pi3b screws down, hub slides in, 18V 2.5A 45W charger brick, battery 11.1V 3500mAh 38.85Wh and storage PiTopOS 
*[ Pi-Top CEED Raspberry Pi Modular Educational Desktop with RPI3] monitor 
*[https://www.indiegogo.com/en/projects/jesselozano/pi-top-a-raspberry-pi-laptop-you-build-yourself Pi-Top v1] wedge laptop with RPi2 


&lt;pre&gt;
2008 Trustees collected for Foundation
2009 Pi Foundation charity status gained 
2010 
2011 First Raspberry prototypes 
2012 First boards go on sale at CPC and RS. The Model A and B 700 MHz Arm11 - February 29th BCM 2835
2012 First million sold - more than the 10,000 original planned and anticipated 
2013 First Alpha Experimental builds of AROS Native for the 32bit Pi 
2013 Pi Trading launched making grants available, providing in house educational resources and Pi Academy for teacher training 
2013 Over two million sold 
2014 Over three million sold 
2014 Pi 1 Model B+ introduced that moved composite video to audio jack and same half gig of memory 
2014 Pi Model A+ v1.1 no ethernet and 1 usb - a little smaller - 
2015 Over four million first gen pis sold  
2015 Pi Zero 1.2 BCM2835 first production revision released with no camera port 
2016 Pi0 1.3 released with camera csi connector 
2017 Pi Zero W v1.1 1GHz Pi0W, single-core 32bit CPU BCM2835 released with Cypress CYW43438 wireless 
2020 Raspberry Pi Pico SC0919 with RP2040 32-bit 2Core ARM Cortex-M0+ up to 133 MHz - 264KB of SRAM and 2MB of on-board QSPI Flash - 
2024 Raspberry Pi Pico 2 with RP2350 2Core 32bit Arm Cortex-M33 and 2core open-hardware [https://github.com/wren6991/hazard3 Hazard3 RISC-V] 

2015 Pi 2 Model B v1.1 BCM2836 900/600 MHz ARM Cortex-A7 Armv7 quad 32bit, 32bit VideoCore IV GPU - 1Gb RAM - 5V 2A micro usb - SMSC LAN9514 chip - 
2015 Over a million pi2s sold 


2015 Raspberry Pi 2 Model B version 1.2 Pi2bv1.2, aka Pi2B2 has armv8 BCM2837 underclocked to 900Mhz without wifi/bluetooth module 
2016 Pi 3 Model B - Broadcom BCM2837 SOC four 64bit ARMv8 Cortex-A53 1.2GHz 32bit 1080p VideoCore IV GPU - 1Gb DDR2 - bluetooth 4.1, Cypress CYW43438 wireless 802.11n - 4 x USB2.0 ports - 5.1V 2.5A - SMSC LAN9514 chip 
2016 PIs total over 10 million worldwide 
2017 Compute Module 3 CM3 with BCM2837B0 armv8 Quad 64-bit - small 67.6mm x 31mm board which fits DDR2 SODIMM connector but not electrically compatible which plugs into needed IO board - beware of the I2C protocol issue 
     1Gb LPDDR2 RAM - Lite or 4Gb Emmc storage 
2017 12 million pis sold in total 
2018 Pi 3 Model B+ - 4c A53 BCM2837B0 1.4Ghz - 1Gb, wireless 802.11ac, gigabit ethernet (300Mbit/s) and bluetooth 4.2 - power over ethernet - 4 x USB2.0 ports - Microchip LAN7515 chip 
2019 Over 15 million sold 
2019 Pi 3 Model A+ with BCM2837b0 Cortex-A53 64-bit SoC @ 1.4 GHz with 512Mb LPDDR2, 1 usb2, 1 hdmi, 1 micro usb 5V 2A - no ethernet - 
2019 Raspberry Pi Compute Module 3+ CM3+ - Broadcom BCM2837B0 1.2Ghz, Cortex-A53 (ARMv8) 64-bit SoC on DDR2 SODIMM mechanically compatible only factor - IO board required 
     1Gb DDR2 and 8GB, 16GB, 32GB or a Lite variant without eMMC 
2021 Pi zero 2 (w or no W) RP3A0 quad 1GHz Cortex-A53 64bit BCM2710A1 512mB SDRam 
2025 edaTEC CM0 ED-CM0NANA with additional dev board with quad 1Ghz A53 with 512Mb Raysan RAM, 2 USB2 and 10/100 ethernet - pico castellated edge
 

2019 Pi 4 Model B v1.1 RPI4B - BCM2711B0T quad 64bit A72 1.5GHz, 4K VideoCore VI, AC wifi, Bluetooth 5.0, GbE Broadcom BCM54213PE (PHY ID 0x600d84a2), 2 micro hdmi decode up to 4K, USB-C 5.1V 3A power, 2xVLI VL805 USB 3, 2xUSB 2.0, 2GB 9LDWW D9WHZ or 4GB 9FDWW D9WHV, 8GB 0AA47 D9ZCL ddr4 ram 
2020 Silent Pi 4 v1.2 upgrade with more USB-c psu support 
2020 PI400 BCM2711C0T 1.8GHz 4Gb DDR4 inside keyboard, 5.1V 5A 27W usb-c psu, 2 micro hdmi, external ide style 40pin gpio, no audio port - 
2020 Raspberry Pi Compute Module 4 BCM2711B0T on new 55mm x 40mm 2x100 pin form factor with extra breakout IO board 
     CM4101000 1Gb RAM Lite SOM 
     CM4102000 2GB RAM Lite 
     CM4104000 4GB RAM Lite 
     CM4004008-4GB-RAM 8GB-EMMC SOM System on Modules 
     CM4104032 4GB RAM 32GB emmc 
     CM4108000 8GB RAM Lite 
     CM4008016 8GB RAM 16Gb eMMc
2021 Raspberry Pi SC0763 Compute Module 4S CM4S with ddr2 sodimm pinouts but not electrically the same with suitable IO board extra cost - 
     CM4S01000 1GB RAM Lite
     CM4S01008 1GB RAM 8GB eMMC Flash
     CM4S02000 2GB RAM Lite
     CM4S04000 4GB RAM Lite
     CM4S04016 4GB RAM 16Gb KLMAG1JETD-B041 
     CM4S08000 8GB RAM Lite 
2021 Pi 4 v1.4 BCM2711B1 upgraded power regulator, to deal with 8gig of ram being more power hungry 
2021-48 Raspberry Pi 4 model B v1.5 2GB 


2023 Pi 5 v1.0 BCM2712 Quad A76 @2.4Ghz - VideoCore VII - no audio socket - dual 4k from mini hdmi - fan connector - 5.1V 5A psu 
2024 Pi 5 2GB DDR4 version uses BCM2712D0 
2024 Pi-500 with 8Gb LPDDR5 and membrane keyboard 
2024 Pi 5 v1.1 
2024 Raspberry Pi Compute Module 5 CM5 BCM2712 55mm x 40mm form factor with additional IO board 
     CM5004000 04GB RAM 0GB eMMC Lite
     CM5008000 08GB RAM 0GB eMMC Lite
     CM5016000 16GB RAM 0GB eMMC Lite
2025 Pi-500+ with 256GB NVMe storage, 16GB LPDDR4 RAM, and Gateron KS-33 Low Profile Blue mechanical keyboard switches 
2025 Pi5 1GB DDR4 announced 


2022 PiOS linux goes 64bit 
2024 Pi Trading IPO stockmarket stock exchange listing 


2026 April and May Aros 64bit fixed, added AHI audio, VC4 gfx started, usb functions added to rom  
2026 June and July Aros 64bit usb2otg started, dma.resource, sdio.resource, bwfm.device wifi added 
2026 Late July daily 64bit Pi3 LE little endian builds start 
2026 August Pi 4, 400, 5 and 500 DTBs added, expanding existing support and wifi for Pi4 and Pi5 
2026 August Pi5 HAT+ nvme and HDMI, AHI RPiI2S added, Pi4 HVS5 video scaler started, 
2026 
2027 


2028 Pi 6 
&lt;/pre&gt;


The vcgencmd can be used to inspect and dump the current system configuration. 
vcgencmd runs on top of VCHIQ as an RPC. The mailbox interface is an alternate but much simpler RPC. 
VCHIQ is a bridge (queue) between the CPU and the GPU so they can communicate with the firmware. 

Loads of [https://github.com/6by9/rpi3-gpiovirtbuf/blob/master/rpi3-gpiovirtbuf.c mailbox] which uses the GPIO control calls. [https://github.com/raspberrypi/firmware/wiki/Mailboxes may also be of interest] 

A fair number of vcgencmd examples (search for vc_vchi_gencmd_init). [https://www.raspberrypi.org/forums/viewtopic.php?t=229203#p1406112 sends the relevant vcgencmd commands] to update the scaling kernel, but the [https://github.com/raspberrypi/userland/blob/master/host_applications/linux/apps/gencmd/gencmd.c command] is just a text string. Parsing and execution of the instructions is performed by the VideoCore firmware. 

The Raspberry Pi runs two separate operating systems: Linux/Aros on the ARM, and a threedx RTOS called vcos running on the Videocore 4 VPU: vcos is commonly called &quot;the firmware&quot;. Vcos is tasked with performing certain system services, for example running the display and audio outputs. The VCHI driver provides an interface to allow drivers to talk to vcos. 


Doubtful, on any [https://www.web3d.org/ Web3d] [https://developer.mozilla.org/en-US/docs/Web/API/WebGL_API WebGL] or [https://github.com/immersive-web/webxr WebXR] [https://developer.mozilla.org/en-US/docs/Web/API/WebXR_Device_API Device API] [https://developer.mozilla.org/en-US/docs/Web/API/XRInputSource XRInputSource] support. Hopefully, never/limited support features like location, peer-to-peer, invasive web apps, unwarranted storage, payments, proprietary video streaming etc 

*spreadsheet [https://git.sheetjs.com/sheetjs/sheetjs sheetjs] [https://github.com/mleibman/SlickGrid SlickGrid javascript] [https://github.com/6pac/SlickGrid SlickGrid typescript] [https://github.com/jspreadsheet/ce jspreadsheet ce] probably without xlsx support 
*presentations [https://github.com/impress/impress.js/ impress.js simplified] [https://github.com/bwlewis/slides slides] [https://zenomt.github.io/mdslides/ github markdown slides] [https://github.com/Patternslib/slides Patternslib slides markdown] probably without pptx support 
*ai office [https://github.com/dream-num/univer/ univer], [https://github.com/dream-num/Luckysheet Luckysheet] [https://github.com/ruilisi/fortune-sheet fortune-sheet] 
*weather [https://github.com/Himanshu3412/Weather-Forecast Weather Forecast], [https://github.com/kaushalsahu07/weather weather needs API key], 


==Future==


[https://github.com/ARMSX2/ARMSX2 Arm pi of pcsx2] 


[https://tube.cadence.moe/ Cloudtube], [https://github.com/TeamPiped/documentation/blob/main/content/docs/public-instances/index.md TeamPiped], [], [], [], 

[https://hyperpipe.codeberg.page/ hyperpipe], [https://ytify.pp.ua/ ytify], [], [], 

[ ytdl], [https://github.com/golddominik893/liberatube liberatube]

[https://git.lolcat.ca/lolcat/4get 4get], [https://github.com/hnhx/librex librex], [], [], 


{{BookCat}}</text>
      <sha1>lbfe5op6lapohxn3x8vgtav7wk2n380</sha1>
    </revision>
  </page>
  <page>
    <title>Seed Factories/Introduction</title>
    <ns>0</ns>
    <id>288346</id>
    <revision>
      <id>4676730</id>
      <parentid>4676492</parentid>
      <timestamp>2026-10-18T10:44:22Z</timestamp>
      <contributor>
        <username>Danielravennest</username>
        <id>13526</id>
      </contributor>
      <minor />
      <comment>/* 5.0- Design Examples */  Update to end</comment>
      <origin>4676730</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="32992" sha1="lxy5yq67yzrlwdkafm63ux83vkde2qd" xml:space="preserve">{{DISPLAYTITLE:&lt;span style=&quot;display:block;text-align:left;font-size:100%;background:#d0f0f0;line-height:2.5em; font-family:'Georgia', serif;&quot;&gt;Chapter 1.0 - Introduction&lt;/span&gt;}}


&lt;div class=&quot;nonumtoc&quot;&gt;{{TOCright}}&lt;/div&gt;

&lt;div style=&quot;font-size:125%; font-family:'Georgia', serif;&quot;&gt;
&amp;emsp;In engineering, a '''[[w:System|System]]''' is a group of related elements that act by rules to form a whole.  Systems are  distinct entities with boundaries, surrounded by their environment.  They are defined for purposes like understanding, analysis, design, and improvement. Systems can include people, and any other kinds of elements. 

&amp;emsp;Systems have characteristics of interest, such as quality of life, size, emissions, and output rate.  Their change in a desired direction is considered an improvement.  Self-improvement is when the change is produced by internal action of the system.  It has occurred throughout history in many ways, such the as evolution of life, and the development of civilization.

&amp;emsp;Through history, large-scale systems like cities have grown, and made major improvements to themselves.  But intentional design for growth and self-improvement has been rare.  Designing from the start to avoid side effects like environmental damage and pollution is even rarer.  We think future changes to existing systems, and newly made ones, should include such design features.  So these volumes are mostly future-oriented, describing types of projects that haven't been done before, and for which few people have experience with.  This is in comparison to mature fields like  '''[[w:Civil_engineering|Civil Engineering]]''', where there are many past examples of construction projects, and many people with skills and experience in developing them.  However the new features are in addition to the knowledge and experience from more mature fields, not a replacement.


==&lt;span style=&quot;font-size:x-large; font-family:'Georgia', serif;&quot;&gt;1.0 - Volume Overview&lt;/span&gt;==
&amp;emsp;

&amp;emsp;Note that both volumes in this set are incomplete works-in-progress.  They present work we have done so far, but are far from finished.  Longer chapters are divided into numbered pages, and pages divided into sections and subsections for easier cross-reference.

&amp;emsp;In this volume we consider self-improvement generally, and a particular example called a '''Seed Factory'''.  This is a system that includes a starter set of equipment intentionally designed to improve by a repeating process:  

&amp;emsp;Part of the factory's capacity is used to make more or better equipment for the factory itself.  The remaining capacity is used to make useful products, like any other factory.  The fraction used for self-improvement can vary over time, according to whatever goals the factory operators choose.  The added equipment increases the ability to make the next round of equipment and further improve.  Output capacity increases as you add more equipment.  So if a significant fraction of output is devoted to improvement then total capacity can grow exponentially.  This idea matters because civilization faces a number of large-scale problems which can only be addressed by large-scale solutions.  Exponentially growing systems can provide the necessary scale.

&amp;emsp;This Chapter (1.0) introduces some of the problems, how the systems engineering method can be used to develop solutions, and some examples of self-improving designs we will detail later.

&amp;emsp;'''[https://en.wikibooks.org/wiki/Seed_Factories/History Chapter 2]''' discusses the history of self-improvement in nature and in human civilization, and how those led to the problems we face.  We then look at self-improvement as an idea.  It is closely related to other ideas like progress and economic development.  More recently, ideas like self-replicating systems, and technologies like computers and automation, have led to the concept of a seed factory as an instance of self-improvement.  It is still a fairly new approach, so Chapter 2 finishes with what we don't know about it yet, and areas for further research and development.

&amp;emsp;If new systems are going to address current problems, and not create new ones as a result, they need to be carefully planned and designed before building and operating them.  Engineering is already a well-developed field, so we will not cover all of what already exists.  Instead, the next two chapters cover what is new in our approach from a technical engineering standpoint.  Note that small and simple projects and systems with minimal side effects don't need much planning and design.  There are existing tools, machines, supplies, plans, instructions, and people with experience to carry them out.

&amp;emsp;'''[https://en.wikibooks.org/wiki/Seed_Factories/Basics Chapter 3]''' presents new design elements to include in the design process.  This includes the current state of the seed factory idea, the pieces which make it up, and a reference architecture for system designs.

&amp;emsp;'''[https://en.wikibooks.org/wiki/Seed_Factories/Design Chapter 4]''' discusses the design process itself.  A constantly growing and improving system is complicated.  So we apply the &quot;systems engineering&quot; approach which was developed to handle such complex projects.  A complete system includes more than just factory equipment, but if it is intended to grow and self-improve it will use a number of production processes and equipment types.  So we provide a reference list of many of the available options as inputs to the design process.

&amp;emsp;'''Chapters 5 through 8''' are a series of design examples for use on Earth.  The series is linked by the fact that one example can grow into or produce starter sets for later ones.  The examples are intended to show how a design is developed, and also serve as a reference for building and operating them.  

&amp;emsp;The last chapter (9.0) of this volume is a set of notes that are too new or don't fit into the main discussion.  It also serves as part of our project database. 
 

&amp;emsp;Space beyond Earth is of interest because of larger available resources and the potential to reduce or even reverse unwanted side effects on Earth. The environments and distances of regions in space are typically more extreme and larger compared to those on Earth.  In addition, objects in space are all in fairly fast motion relative to Earth and each other compared to motions on Earth.  So a second '''[https://en.wikibooks.org/wiki/Space_Transport_and_Engineering_Methods Volume II]''' addresses these differences.  It begins with the relevant science and engineering methods that apply to space projects.  We then continue the series of design examples for various space regions.  For each region we summarize local conditions and available resources.  These will affect how systems are designed for each.

&amp;emsp;Space projects are presented in general order of distance from Earth and in difficulty from easier to harder.  Since the first set of people and equipment must come from Earth, this is the approximate order projects in each region would get started.  Also later and more difficult regions will be able get support both from Earth and previously developed regions.

 
==&lt;span style=&quot;font-size:x-large; font-family:'Georgia', serif;&quot;&gt;2.0 - Some Problems Facing Civilization&lt;/span&gt;==
&amp;emsp;

&amp;emsp;These are engineering-oriented books.  Engineering in general involves applying knowledge towards useful ends, such as satisfying people's needs, solving problems, or making life better.  If seed factories are to be more than just an interesting idea, they should be developed with such useful purposes in mind.  Here we identify some current and future problems facing civilization.  This is by no means a complete list.  Rather, they are problems we think worth solving, and could be addressed by technical solutions.  The ideas and methods in these books can then be applied with these problems in mind.


:'''Insufficient Development'''


&amp;emsp;Many places where people live have less of the artifacts and systems of civilization, and the benefits they bring, relative to intensely developed areas like large high-income cities.  Even in the most developed areas it would be difficult to find people perfectly satisfied with their current situation.  They can usually list a number of things they would like to improve, if only they had more time, money, or other resources.  There is no shortage of desire for improvements.  What is lacking are the means to make them happen.  This is particularly true in difficult or hostile environments, where the extra work required has left them nearly or entirely undeveloped.

&amp;emsp;In addition to uneven development, even the most developed areas have an uneven distribution of resources.  Those who have the least lead a precarious existence, where any adverse event can seriously degrade their lives.  So in addition to general development, we would like to enable backup systems, reserves, and other buffers against adversity.


:'''A Deteriorating Environment'''


&amp;emsp;A healthy environment is necessary for us to live on Earth.  But side effects of our current civilization have led to changes for the worse.  Probably the most pressing environmental problem is excess carbon dioxide (CO&lt;sub&gt;2&lt;/sub&gt;) leading to climate change.  Others include deforestation, desertification, species extinction, and various kinds of pollution, like airborne particulates and micro-plastics.  In the future we would like to minimize, eliminate, or reverse these side effects and the changes for the worse they have caused.


:'''Technological Unemployment'''


&amp;emsp;Recent centuries have seen accelerating replacement of manual labor with powered equipment.  This produced a shift from farming, which used to be people's main activity, to manufacturing and services.  Continued improvements have reduced manufacturing labor, to where services are now the dominant activity in developed areas.  Since about the mid-20th century, technologies like automation, robotics, software, and artificial intelligence have enabled &quot;Smart Tools&quot;.  These have an increasing ability to work on their own, replacing much of the remaining labor.  

&amp;emsp;Our modern economic system is based on people trading their specialized labor for money, then trading money for the other things they need and want.  If most labor can be replaced by smarter tools, we get the problem of technological unemployment.  The unemployed can no longer buy what they need, and the still-employed lose them as customers.  The system of trading work for money and then money for other goods breaks down.

&amp;emsp;This is not yet a severe problem. Through history, people displaced from one kind of work have found something else to do, and the changes were slow enough that young people could start in the new fields while older people aged out the old ones.  But the recent advances in smart tools threaten to displace many jobs in fields like transportation, distribution, and retail in a short period of time.  The displaced workers may not be able to find new jobs in other fields.  It is worth thinking about how to deal with this potential problem ''before'' it becomes severe and we are faced with mass unemployment.


==&lt;span style=&quot;font-size:x-large; font-family:'Georgia', serif;&quot;&gt;3.0 - How to Tackle These Problems?&lt;/span&gt;==
&amp;emsp;

&amp;emsp;Our civilization, and the parts that make it up, are very complex systems.  A method called '''Systems Engineering''' was developed in the 20th century to deal with such systems.  We propose to use it to address the problems noted above.  The systems approach starts by defining the unmet needs which one or more systems are intended to satisfy.  For existing systems this is in terms of what changes are needed.  Identifying what is wanted comes before any consideration of designs or solutions.  Having the answer in mind before stating the problem prematurely limits considering all the options.  Goals should also not be limited by what is thought to be possible now.  Partly meeting the goals, and identifying what research or improvements are needed for the rest is better than limiting our goals and going no further.

&amp;emsp;We identified some problems in a general way above.  For the systems approach we need to specify what we want more exactly.  That way we can measure how well proposed designs or solutions meet the goals, which ones are better or worse, and in what direction to make improvements.  We will start specifying wants here, and continue the systems process in later sections.  Since civilization already exists, these statements are in terms of changes.  The goal statements (in bold face) are followed by some explanations.


:'''(1) Bring less-developed parts of civilization up to [TBD] level of satisfaction with their situation, given sufficient information about their options.  Increase satisfaction in more developed areas by [TBD] and provide means to deal with adverse events.''' - TBD means &quot;to be determined&quot;.  We haven't defined how to measure satisfaction levels yet.  We know we want some kind of measure for it, so we use [TBD] as a marker for later work to fill in.  Significant numbers of people lack education and information on what is possible, and therefore can't know what they would want if they had that knowledge.  Supplying them with that knowledge so they can choose is part of the goal.  Satisfaction with the current state of things is not enough if something bad happens, so we also want to be able to handle adversity.

:'''(2) Reverse human-caused environmental problems by [TBD] percent while minimizing side effects.  To the extent possible, also minimize natural risks.''' - All human activities have side effects, so we can never entirely eliminate them. The goal is then to minimize them, and make them less harmful.  The natural world also presents many hazards, like hurricanes and earthquakes.  We can't eliminate these hazards either, but we can minimize the damage they cause.

:'''(3) Avoid or minimize future problems, such as technological unemployment.''' - Permanently displaced workers due to automation is one problem we already identified.  There may be others we want to deal with ahead of time.  Part of the goal is to identify them.


==&lt;span style=&quot;font-size:x-large; font-family:'Georgia', serif;&quot;&gt;4.0 - Systems and the Systems Engineering Method&lt;/span&gt;==
&amp;emsp;

&amp;emsp;A &quot;System&quot; is any collection of elements which interact with each other and the outside world, and performs some identifiable function or transformation.  For example, a computer system such as a desktop personal computer or smartphone allows you to read this document on Wikibooks.  It contains elements like a power supply, semiconductor chips, and software that work together.  It interacts with you as the reader, and the Internet to access this page.  If you were editing this page, you would be transforming it from one version to the next.

&amp;emsp;We define systems to help with understanding, analysis, design, and improvement, and to help meet intended goals.  Every system has a boundary.  This is a mental construct rather than a wall or a fence.  It separates the system from what is outside the system.  In general the parts of a system are related in some way, and perform an identifiable function.  Sometimes system boundaries are natural and obvious, such as an airplane vs everything outside the airplane.  Other times system boundaries and their contents are arbitrary and in multiple pieces and places.  Defining them can still be helpful in working on a project.

&amp;emsp;A wide variety of things can cross the system boundary, and thus enter or leave the system.  For example, a factory system can take in raw materials and power as inputs, and deliver finished products and various kinds of wastes as outputs.  The physical sciences tell us matter and energy can't spontaneously appear or disappear, only change form.  So mathematically, the change in the contents of a system equals the flows entering the system minus the flows leaving.

&amp;emsp;Systems can be any shape or size, and can contain other, smaller, systems.  Smaller systems within a larger one are called '''Subsystems''', which can in turn contain even smaller subsystems, to any level of depth.  The human mind can't comprehend the entirety of a large complex system.  So a key method in systems engineering is to break up large systems into smaller subsystems and sub-sub-systems, until they are small enough and simple enough to understand, design, build, etc.  The flows at every level must still equal the change in subsystem contents, so straightforward bookkeeping can ensure nothing has been forgotten or lost in the total system.

&amp;emsp;Having identified problems and set goals, the next step is starting to identify potential solutions that can meet them.  At the start, we don't know what the best approach will be.  So typically multiple candidates will be proposed or formulated.  Over time, most of these will be weeded out and optimized, until one or a few best options remain.  Research and testing may be needed before the final choices are made.  The details of the process are more fully covered in '''[https://en.wikibooks.org/wiki/Seed_Factories/Design Chapter 4.0 Design Process]'''.

&amp;emsp;The premise of these two volumes is that seed factories and self-improving systems can be part of the solutions to the problems noted above.  That needs to be proven, though, and not just assumed.  The examples we present and analyze will help to do that, but they need to be put to actual use and shown to work as expected.

&amp;emsp;Self-improvement is a design feature.  It is not a complete solution by itself.  System designs must also include and build on past experience in fields like '''[[w:Industrial_technology|Industrial Technology]]''', other '''[[w:Engineering|Engineering]]''' fields, and other parts of our accumulated human knowledge.  Those other subjects will be referenced and included where appropriate.

==&lt;span style=&quot;font-size:x-large; font-family:'Georgia', serif;&quot;&gt;5.0- Design Examples&lt;/span&gt;==
&amp;emsp;

&amp;emsp;Chapters 5 through 8 describe four types of self-improving production systems.  Each is intended to help solve the problems and meet the goals noted above. How they do this is by using particular approaches and features in their design.

&amp;emsp;The first problem is that of insufficient development in terms of modern artifacts and systems.  In principle this can be resolved by producing and delivering the needed items.  But that presents several secondary problems.  People in low-income areas may lack funds to pay for such things.  Even if they were donated, they may not have the skills and experience to operate and maintain them.  A solution to both secondary problems is to bootstrap their own production from seed factory starter sets and their own labor.  They will need less funds to build the factories if they self-build them, and they can then make the other finished products they want.  The experience gained in building the factories and making the products will then enable them to operate and maintain them later.

&amp;emsp;In more developed areas, there are still widespread shortages of time, money, or resources to make improvements and increase satisfaction.  Our approach to this is self-improving systems with a high level of smart tools.  Starter sets take less money, smart tools take less time to operate, and the production systems can produce their own energy and obtain material resources.  Due to the higher level of complexity and skills needed, these systems would likely be developed as cooperative projects involving many people.

&amp;emsp;The second problem is risk from environmental damage and natural events.  A start towards solving it is education about these risks and what can be done to reduce them.  New systems can be designed to incorporate renewable energy, avoid or recycle wastes, reduce pollution, and maintain natural habitats.  These design features would be included in both finished products and the production systems that make them.

&amp;emsp;The third gosl is addressing future problems before they become urgent.  An early task is to identify what those problems might be, besides technological unemployment that we already identified.  Then the systems approach would be used to identify solutions or preventive measures, and incorporate them into system designs.  The unemployment problem could be addressed by production systems of the types in our examples.  Their owner-builders receive a share of their output directly, regardless of how automated the systems are, or how much labor is needed for their operation.  In other words, the production systems work for their owners, so the owners don't have to, or as much.

&amp;emsp;The four examples in chapters 5 through 8 form a linked series of projects.  One way to move through the series is by evolution.  Enough improvements and growth can turn one example into the next.  Another way is by setting up new seed factories for a later example.  The various parts for new seed factories can be made by matured previous ones.  A later example could also be started fresh by supplying equipment from elsewhere, or by some mixture of internal and outside sources.  However they are started, the experience from earlier projects and their growth paths can be applied to later ones.  

&amp;emsp;The example systems are:  


* '''[[Seed_Factories/Concept|Personal Production]] (Chapter 5)'''


&amp;emsp;This example has the goal of making a range of basic products for a local community of owner/operators, such as food, building materials, and utilities.  It is personal in the sense that products are made for their own use and for others in their community.  It is not like a personal computer in having just one owner.  It begins with a network of people interested in working together and conventional workshop tools.  At first, production is at hobby and home-use scale.  This keeps early costs within reach.  To this they gradually add a starter set of seed machines.  The combined collection is partly used to make more equipment, alongside the basic products.

&amp;emsp;Later equipment is scaled in size to increase output, and more diverse to increase product range.  The equipment eventually becomes too large for individuals to house, and too expensive for them to afford individually.  The wider product range also becomes too complex for one person to have all the skills needed.  The solution is building or acquiring larger and more dedicated production spaces, and have multiple owners with different skills who work together to make what is needed.  

&amp;emsp;There are two approaches to working together: distributed and centralized.  In the distributed approach, each person owns one or a few pieces of equipment.  A production request is then distributed as needed to the people and their equipment, who do their parts to make the product.  In this approach, ways are needed to settle up the resources and costs in meeting each other's needs.  In the centralized approach, the equipment is in one or a few larger places, with shared ownership.  A mixed approach is also possible, part distributed and part centralized.  

&amp;emsp;As production grows beyond personal needs, the network can start to operate like a commercial workshop, building items for outside customers in addition to the local community.  At the hobby and home-use scale, participation is mostly part-time, and the owners' main support is from conventional work.  As production grows to commercial levels, some of the people can transition to full-time self-employment and have a large part of their physical needs supplied from within the network.


* '''[[Seed_Factories/WWF|The &quot;Makernet&quot;]] (Chapter 6)'''


&amp;emsp;We define a '''Location''' as an area small enough that people can easily travel to work in person, and exchange products with each other.  An example would be a US metropolitan area.  In the Personal Production example, one location can then contain multiple home and dedicated sites where work is done.  Since modern communications are worldwide, the network of people working together and exchanging items does not have to be restricted to a single location.  So our second example extends the distributed approach to multiple locations in different parts of the world.  

&amp;emsp;Individual production sites are then network nodes that communicate by means such as personal contact and the Internet.  We call it a &quot;Makernet&quot; because the network collectively makes things.  Owner-operators and customers can communicate with each other by any available method, including electronically.  Smart production machines can also communicate with each other directly, or be controlled by people and software remotely.  

&amp;emsp;Shipping physical items long distances involves significant cost, energy, and time.  Therefore makernet production will tend to be concentrated on items with higher value to mass ratios.  At the high end of value to mass, electronic design files for new machines and products have no mass, and can be sent anywhere at low cost.  They are well suited for a worldwide network.  At the low end, crushed stone for construction is heavy and cheap.  Shipping will tend to be limited to a single location near the quarry rather than moving rocks long distances.  

&amp;emsp;In a well-developed makernet, a customer may submit a product order to the network through a website.  Production requests are then routed to various network nodes, who supply the materials, fabricate parts, and do other necessary steps.  As each step is completed, payment is routed to the node.  Eventually the finished item is delivered to the customer.  Production nodes can contain any number of machines and processes.  Since new machines can collectively be made by already existing nodes, a single seed factory starter set can in theory extend the network everywhere over time.  

&amp;emsp;For node operators, modern communications allows people to work remotely from the actual equipment.  This has potential advantages in commuting cost and flexibility of work hours and place.  The Personal Production example is a local community at a single location.  So much of the interaction can be in person or by voice.  The Makernet approach emphasizes software and networking, with people doing things at times of their choosing, rather than on a work schedule in a conventional factory.  New starter sets would tend to be optimized for size and mass, so they can be shipped farther at reasonable cost.


* '''[[Seed_Factories/Industrial|Industrial Production]] (Chapter 7)'''


&amp;emsp;The goal of this example is large-scale production of more specialized products, much like conventional factories.  It begins with smaller-scale commercial networks like the previous examples, or starter sets specifically designed to grow to industrial scale.  In either case, growth by self-expansion should be a less expensive way to reach the desired production capacity.  In one version, the starter sets are mobile, and are used like construction equipment.  They are brought to a new industrial site and start making parts and equipment.  Once the new factory reaches sufficient capacity, the seed factory components move on to the next project.  In another version, a commercial-scale network grows in place to the larger industrial scale.  

&amp;emsp;Individual industrial sites grow towards scale and efficiency rather than diversity of outputs.  This is partly because it gets harder to fit all the large equipment and operations in one place.  Starter sets and small-scale production favor flexibility in what they can make, at the expense of being less efficient.  At industrial scales, the individual machines can be optimized for their specific tasks.  They are then easier to automate because they each do fewer different things.  

&amp;emsp;Industrial-scale sites can still operate as a network, and make things for each other as needed.  However, the larger scale output goes well beyond the original owner's needs, or even the general needs of a given location  They can then sell products directly to a wider market.  They can also sell production shares to people who otherwise don't participate in site operations.  Production shares entitle people to a share of the products made, either without further payment, or just to cover inputs like raw materials.  An example of this would be a large-scale automated farm, whose shareholders then get a portion of the food produced.  Industrial-scale sites can use conventional factory financing via capital markets if internal funding is not sufficient.


* '''[[Seed_Factories/Remote|Remote and Difficult Locations]] (Chapter 8)'''


&amp;emsp;This book's last example is production in remote locations, or where environment conditions are difficult or extreme.  In such locations, the benefit of self-expanding systems is not having to bring all the infrastructure with you.  Instead, you bring a starter set and produce most of the rest locally.  Examples of remote and difficult locations on Earth include deserts, polar regions, and the ocean surface.  More extreme locations include high altitudes, ice caps, deep underground, or underwater.  Current civilization mostly occupies a thin layer within 30 meters of about 13% of the Earth's surface.  This is only 1.2 parts per million of the total Earth.  Extending available locations horizontally to the remaining area, and vertically beyond the first few meters would vastly increase living and working space and resources.  The key to this is affordability, which self-expanding systems can help provide.  

&amp;emsp;The more difficult and remote the location, the higher the cost of transporting equipment there, and the more incentive there is to use a small starter set and build locally.  High levels of automation and productivity can make it possible to live and work in such locations by providing the infrastructure and resources needed.  Remote controlled operation allows building up capacity without necessarily living there.  For example, the Sahara Desert may be a great place to make solar panels, because of abundant sunlight and sand as inputs.  But people may not want to live there full time.  Working remotely can allow that choice.  Conversely, if technology enables living in a remote location, it might be desirable for some people.  Since other people don't live there, land would be cheap.  It might be scenic or have other features people would prefer.


* '''Space (Volume II)'''


&amp;emsp;The most remote and difficult places are regions in space beyond the Earth.  Synchronous orbits, where many satellites operate, are twice as far as any two points on Earth can be, and the farthest known Solar System orbits extend ten million times farther than that.  The space environment has a number of difficult or hostile conditions for people and other living things.  This includes lack of breathable atmosphere and water, high radiation levels, and low gravity.  On the other hand, space contains large amounts of untapped energy and material resources.  If seed factories and self-expanding production can help make these resources accessible, the potential gain for civilization is enormous.  

&amp;emsp;Since the conditions are so different, and involve different engineering specialties and designs, we reserve discussion of their examples to a second volume on '''[https://en.wikibooks.org/wiki/Space_Transport_and_Engineering_Methods Space Systems Engineering]'''.  The examples for space are linked to the previous ones for Earth in a couple of ways.  First, industrial and in some cases remote and difficult locations are needed make and operate transportation to reach space.  Second, the first seed factories to use in space must be designed and built down here, and some of their operation can be remotely controlled from Earth.


*'''[[Seed_Factories/Notes|Conceptual Design Notes]] (Chapter 9)'''


&amp;emsp;The final part of this volume is a collection of material that is (a) too new or not organized enough for the main text, or (b) is too detailed and would interrupt the flow of the discussion.  The ideas we present in these books are a work in progress, so the final part also serves as a kind of &quot;engineer's notebook&quot; to record that work.  In the past, such notebooks were on bound paper or pages in file folders.  Larger sketches and drawings were kept flat in drawers or rolled up.  Only a few people could access them and collaborate.  The modern approach is a shared electronic database where everyone has access to the full contents.  Our work is open-source and we encourage collaboration.  So the notes in Chapter 9 form part of our database.  Material that is not suited to the Wikimedia format will be stored elsewhere and linked from that section, and from other parts of both volumes.
&lt;/div&gt;

{{BookCat}}</text>
      <sha1>lxy5yq67yzrlwdkafm63ux83vkde2qd</sha1>
    </revision>
  </page>
  <page>
    <title>Seed Factories/History</title>
    <ns>0</ns>
    <id>288454</id>
    <revision>
      <id>4676731</id>
      <parentid>4207728</parentid>
      <timestamp>2026-10-18T10:51:52Z</timestamp>
      <contributor>
        <username>Danielravennest</username>
        <id>13526</id>
      </contributor>
      <origin>4676731</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="73769" sha1="02bbbeo0g3nz79klhyxgeemqku0iwma" xml:space="preserve">{{DISPLAYTITLE:&lt;span style=&quot;display:block;text-align:left;font-size:100%;background:#d0f0f0;line-height:2.5em; font-family:'Georgia', serif;&quot;&gt;Chapter 2.0 - History and Concept Development&lt;/span&gt;}}


&lt;div style=&quot;font-size:125%; font-family:'Georgia', serif;&quot;&gt;

&lt;div class=&quot;nonumtoc&quot;&gt;{{TOCright}}&lt;/div&gt;


&amp;emsp;In Chapter 1.0 (Introduction) we identified three large-scale problems: insufficient development, a deteriorating environment, and technological unemployment.  All three are unintentional side effects of how civilization evolved in the past, and may develop in the near future.  

&amp;emsp;The growth of modern civilization is still incomplete and unevenly distributed.  This results in the first problem, of insufficient development.  We've made poor choices in the past due to lack of knowledge and incentives built into the economic system.  These are negatively affecting the environment, the second problem.  A lack of foresight combined with how our economic system works may lead to the third problem, of large-scale unemployment. 

&amp;emsp;Before trying to find solutions, we should first understand the history and processes which brought us to where we are.  So the first part of this chapter covers processes like expansion, growth, and self-improvement in nature, before people evolved.  Then we look at how people have tried to satisfy their needs and make their lives better.  More specifically, technology has a long history in human culture.  We take a look at that history, leading up to modern technology.  In addition to improving our lives, technology brought unsuspected and undesirable side effects, resulting in the current state of civilization.  

&amp;emsp;'''[[Seed_Factories/SelfImprovement|Chapter 2.1: Self-Improvement and Seed Factories]]''' explores self-improvement as an idea, and its relation to ideas like progress and economic development.  The second half of the 20th century took the idea of machine self-replication from theory and philosophy to design and engineering.  Technologies like computers and automation developed quickly in this period, making replication a real possibility.  The original idea was a machine system copying itself without help, by making and assembling copies of all its own parts.  Doing this with physical systems is still beyond our reach.  Electronic information, on the other hand, is easily copied, and automated software can do this without people involved.

&amp;emsp;We have updated the original idea of fully automated self-replication to an evolving system.  It begins with a smaller and simpler seed factory that grows towards higher levels of automation and replication.  The changes to the idea are fairly new and not yet completely worked out.  '''[[Seed_Factories/Technology|Chapter 2.2: Further Research and Development]]''' considers open questions and what isn't yet known about it.  An evolving factory system will also make use of other, more developed, areas of knowledge and experience.  So we also look at their current state-of-the-art.  Lastly, we look at related projects, and topics for future research and development needed to make use of the seed factory approach.
  

==&lt;span style=&quot;font-size:x-large; font-family:'Georgia', serif;&quot;&gt;1.0 - Natural Processes&lt;/span&gt;==
&amp;emsp;

&amp;emsp;Expansion, growth, replication, and tool use are processes which predate civilization, and even modern humans as a species able to think about them.  People have always exploited these processes in the past, knowingly or not, and continue to do so today.  A short review of their history is in order for a couple of reasons.  The first is to understand how modern civilization arrived at its current state.  The other is to identify processes and methods we can use.  We can combine them in new ways, adapt them to meet our needs, and use them to help solve our pressing problems.

&amp;emsp;The natural world doesn't consider internal changes as &quot;better&quot; or &quot;worse&quot;.  Those are labels that people apply based on our needs, desires, and opinions.  We need at least some physical space and objects like food and shelter to keep living.  Beyond the bare necessities, most of us strongly desire additional or higher quality things to make our lives better.

&amp;emsp;So we describe natural changes as improvements when they enable more of the necessities and desirable extras, or make them easier to get.  An example would be the end of the last '''[[w:Ice_age#Glacials_and_interglacials|Glacial Period]]''' about 20,000 years ago, bringing warmer temperatures and freeing fertile land from ice cover.  When nature does it without our help we call it self-improvement.  The natural world has changed for the better, from our standpoint, based on what we know from '''[[w:Astronomy|Astronomy]]''' and '''[[w:Biology|Biology]]'''.


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;1.1 - Astronomy&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;

&amp;emsp;Expansion as a process appears to be as old as the Universe itself.  Red-shifts in the spectra of galaxies, supernova brightness and light curves, and the '''[[w:Cosmic_microwave_background_radiation|Cosmic Microwave Background]]''' radiation imply that '''[[w:Metric_expansion_of_space|space itself is expanding]]'''.  This seems to be the combined effect of strong repulsive forces from '''[[w:Inflation_(cosmology)|Cosmic Inflation]]''' during the '''[[w:Big_Bang|Big Bang]]''' ~13.8 billion years ago, and '''[[w:Dark_energy|Dark Energy]]''', which continues to accelerate the expansion.  If the inflation theory of cosmology is correct, the growth of large scale structures, now hundreds of millions of light years in size, can be traced to microscopic quantum fluctuations during the inflationary era and acoustic waves that occurred somewhat later.

&amp;emsp;Stars, planets, and galaxies grow by '''[[w:Accretion_(astrophysics)|Accretion]]''', the addition of more matter to what is already there.  Since the force of gravity is proportional to mass, the ability to attract more matter grows as more mass is collected.  This leads to '''[[w:Exponential_growth|Exponential Growth]]''', until all the nearby matter is consumed.  Any growth process which is proportional to the current size leads to exponential increases over time. We will see many examples of this in the course of these volumes.  

&amp;emsp;Stars replicate in a limited sense.  They are born with different masses, and their energy output increases much faster than mass.  This is known as the '''[[w:Mass–luminosity_relation|Mass-Luminosity Relation]]'''.  So the larger stars use up their fuel much more quickly, despite starting with more.  As these stars reach the end of their life, they emit large amounts of gas or explode.  The shock waves from these processes can create high density areas in molecular clouds.  These denser areas can collapse to form a new generation of stars.  Our own Sun is thought to be a third generation star whose formation was triggered by a supernova explosion of a nearby older star.

&amp;emsp;The early Universe after the Big Bang consisted of hydrogen and helium, and nearly no other elements. '''[[w:Stellar_nucleosynthesis|Nucleosynthesis]]''', the process by which stars shine, also builds heavier elements.  There are some additional processes which convert one element to another.  We need heavier elements to make the kind planet we live on and the parts of our bodies.  So the evolution of generations of stars producing such elements is considered an improvement.  

&amp;emsp;Planets grow by an exponential process from smaller bodies.  A growing '''[[w:Protoplanet|Protoplanet]]''' has a stronger gravitational field, so it can attract nearby gas, dust, and other small bodies to itself.  As it gets larger, it's gravity can also change the orbits of other bodies.  This causes collisions, with the larger bodies tending to keep more of the combined mass.  Debris from collisions continues to collect by attraction and more collisions.  Eventually most of the available mass is (1) gathered into planets and moons, (2) thrown into the parent star, (3) ejected from the stellar system, or (4) not ejected, but thrown far enough outwards that further collisions are rare.  

&amp;emsp;Once formed, planets continue to affect each other's orbits by gravity, and the parent star supplies energy to keep them warm according to their distance.  The star's output can vary with time, and it can emit other things besides light.  Internally, a planet can generate heat by various means, and that heat can drive geological processes.  So a planet's environment can get better or worse with time in quite complicated ways.

&amp;emsp;'''[[w:Galaxy_formation_and_evolution|Galaxies]]''' formed and continue to evolve by a similar growth and evolution processes.  Random processes produced regions in the early Universe that were denser than others.  They tended to attract other nearby matter to form clouds.  The clouds in turn attracted each other, forming larger and larger structures like galaxies and clusters of galaxies.  Our own Milky Way galaxy is still consuming smaller ones, as evidenced by leftover streams of gas and stars.  The Andromeda galaxy and ours are predicted '''[[w:Andromeda–Milky_Way_collision|to collide]]''' in about 4.5 billion years.  The larger the distances, the longer these growth processes take, so they are incomplete in the Universe today.  

&amp;emsp;Galaxies evolve internally as gas and dust are turned into generations of stars and back again, central black holes grow, and the stars redistribute their positions gravitationally.  By late 2022 we have discovered over 5000 '''[http://exoplanet.eu/ Exoplanets]''' - planets around other stars.  So we now know the evolution of our Galaxy has resulted in many planets besides the ones around the Sun.  

&amp;emsp;We consider the evolution of the Universe from the Big Bang until now to be an improvement.  It has provided the physical space, heavier elements, and the Earth and Sun that have allowed us to evolve and continue to live.  We expect conditions on Earth to deteriorate as the Sun gets brighter and the Earth hotter.  Left to itself, life as we know it on Earth will become impossible in 0.6-1.0 billion years.

&amp;emsp;It is not yet clear how often and for how long conditions suitable for life happen elsewhere.  We also don't know if planetary, stellar, and galactic processes could be artificially used to increase or extend such conditions.  But in the mean time, in our current civilization, we can incorporate the ideas of expansion, replication, and exponential growth into our efforts.


[[File:DNA_replication_en.svg|thumb|right|691x336px|Figure 2.0-1 - Proteins, most of whose names end in -ase, separating DNA strands and assembling new complementary ones, which results in two complete copies.]]  

===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;1.2 - Biology&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;

&amp;emsp;'''[[w:Evolutionary_history_of_life|Living Things]]''' on Earth have grown and reproduced for 3-4 billion years (GY).  As a percentage of the age of the planet, life started soon after the surface cooled enough and frequent large asteroid impacts ended about 3.8 GY ago.  Life as we know it requires water and '''[[w:Organic_compound|Organic Compounds]]'''.  These were either included in the planet's original formation, or delivered afterwards by impacts of comets and asteroids.

&amp;emsp;Growth and reproduction are two of the defining features of '''[[w:Life#Biology|Life]]'''.  Another defining feature of life is '''[[w:Metabolism|Metabolism]]''', the use of available energy to convert ingested materials into parts of the organism.  Some of the new parts are for self-maintenance, and some are for growth.  At some point in its life cycle the organism has grown enough to make copies by division at the cellular level.  Small organisms like '''[[w:Bacteria|Bacteria]]''' and some '''[[w:Algae|Algae]]''' consist of a single cell which divides repeatedly.  Large organisms like whales and trees consist of many cells.  They individually divide, become specialized for different tasks, and are grouped into larger structures.  Organisms can also incorporate non-living matter, like the mineral parts of bones and shells, or the bark of trees.  

&amp;emsp;The replication of a large organism involves partitioning one or a small number of cells into an '''[[w:Embryo|Embryo]]''' or '''[[w:Seed|Seed]]''', a smaller and simpler entity than the mature organism.  This entity contains all the information to build the mature organism, mainly in the form of long double-chain polymer molecules known as '''[[w:DNA|DNA]]''' (Deoxyribonucleic Acid), often after mixing genetic data from two parents.  The sequence of DNA units directs the construction of various '''[[w:Protein|Proteins]]''', which in turn perform a variety of functions necessary for life.  One of these functions is separating the two strands of DNA molecules, and assembling complementary units to make a matching second strand for each (Figure 2.0-1).  When a cell divides, each copy then contains a full set of instructions so it can continue to live.  

&amp;emsp;Biological seeds usually contain the plant embryo, which does the actual growing, a supply of nutrients to support the initial growth, and a protective coating. The nutrient supply supports the embryo until photosynthesis and uptake through roots can take over. Animal embryos develop within eggs - containers with a nutrient supply, or are carried internally and supplied by the mother until birth.  The initial seed or embryo cells divide and specialize until they become a mature copy of the parent organism.  Specialization during the life of one organism, and other short-term changes are affected by '''[[w:Epigenetics|Epigenetic]]''' processes.  Humans, being large organisms, grow and replicate in this way, both at the cellular and whole organism level.  The process of growth from an embryo or seed is at least 400 million years old. 
   
&amp;emsp;Self-reproducing organisms have DNA sequences 0.1 to 670,000 million units in length.  Changes to the sequences happen for a variety of reasons.  The the changes cause differences in how well the modified organisms live and die in their environment.  Different survival and reproduction have produced all the various '''[[s:Species|Species]]''' that exist now, and have existed in the long history of our planet.

&amp;emsp;There are several scales at which these changes can happen: at the individual '''[[w:Nucleotide|Nucleotide]]''' unit level, to longer segments of DNA, and by wholesale reshuffling in '''[[w:Sexual_reproduction|Sexual Reproduction]]'''.  Until very recently, DNA changes were unplanned and undirected, so the evolution of species was random and slow.  For example human DNA varies by 0.1% between individuals in the ~10,000 generations since our modern form evolved.  We vary by 1.2% in the 7 million years since we diverged from our nearest living relatives.  We can distinguish between long-term information such as coded in DNA, and shorter-term information such as '''[[w:Epigenetics|Epigenetics]]''' and individual memories, which are outside of DNA changes.  

&amp;emsp;Most of the energy for life ultimately comes from the Sun.   Waste products and dead organisms are recycled by other organisms, or accumulate as sediments, which are converted to rock formations by geologic processes.  Over very long periods of time, the rocks can again become available as raw materials for life.  Communities of living things, together with the non-living surroundings they interact with, form linked '''[[w:Ecosystem|Ecosystems]]'''.  These are dynamic entities through which energy and materials flow, often in cycles with feedback loops.
  
&amp;emsp;All living things interact with their surroundings by ingesting food, rejecting wastes, and using local energy sources to sustain themselves.  Many species also modify their surroundings by building non-living constructs outside their bodies, such as '''[[w:Nest|Nests]]''', '''[[w:Burrow|Burrows]]''', and '''[[w:Beaver_dam|Dams]]'''.  Once built, these structures can perform functions like shelter from the environment or protection from predators.  The non-living objects don't need constant biological activity to sustain them.

&amp;emsp;People also interact with and modify our surroundings, build non-living objects, and participate in ecosystems with other living things.  We depend on the self-expansion and replication abilities of other living things to supply food and other products we need and use.
 
&amp;emsp;We can apply ideas from biology, such as specialization during growth, replication via a smaller and simpler starter entity (i.e. a seed), and replication of information into our designs.  We can also incorporate the ideas of energy and material sources, recycling, and ecosystems of related elements.  Since many features from biology can be included into artificial self-improving and replicating systems, we can consider them forms of '''[[w:Artificial_life|Artificial Life]]'''.


==&lt;span style=&quot;font-size:x-large; font-family:'Georgia', serif;&quot;&gt;2.0 - Technology and Culture&lt;/span&gt;==
&amp;emsp;

&amp;emsp;The natural processes of expansion and replication started billions of years before the roughly 300,000 year history of '''[[w:Human|Modern Humans]]'''.  As living beings we continue to participate in these processes, and they continue to operate in nature.  What makes us distinct is our creation of technology and culture.  In a broad sense, '''[[w:Technology|Technology]]''' includes the knowledge and skills needed to make things, but also putting that knowledge to practical use for all the tools, artifacts, and products we make.  A tool like a hammer is a technical artifact, but knowing how to make and use hammers is a part of technical knowledge.  Humans also produce '''[[w:Culture|Culture]]''' - entities that persist beyond the death of individual people.  Both technology and culture involve growth and replication processes.  We can better meet our needs by intentionally using these processes in the systems we build.


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;2.1 - Recent Evolution and Early Tools&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;
  
&amp;emsp;Some animals actively '''[[w:Tool_use_by_animals|Use Tools]]''', objects which are not permanent parts of their bodies.  Tools let them perform tasks more effectively than their bodies can alone.  Most animal tool-use is passed genetically or arises spontaneously.  They lack a knowledge component, so we don't call them technology.  Knowledge is learned, saved, and passed on to others.  We don't know exactly when the first technologies arose that were passed on this way.  Before that, tools were invented each time, then lost when that individual died.

&amp;emsp;Many of our relatives among the '''[[w:Primate|Primates]]''' have been observed using simple tools such as sticks and leaves to gather food.  Some groups of wild chimpanzees use tools to chop large fruit into smaller pieces so they can be eaten.  Neighboring groups do not do this, suggesting knowledge is being learned or passed on within the group that does.  So this would count as a very early technology.  

&amp;emsp;Our early human ancestors also made this kind of transition from spontaneous to learned tool-use at some point millions of years ago.  This was likely among the '''[[w:Hominidae|Hominid]]''' (Great Apes) family of primates to which we belong, but an earlier species now extinct and distinctly different from us.

&amp;emsp;It is hard to pin down exactly when and how the '''[[w:History_of_technology|History of Technology]]''' began.  The oldest activities that might be classed as technology are foraging and nest building by hand.  Other species of Great Apes do this, and likely our ancestors millions of years ago did too.  However, the remains of meals and nests are biological, and perish over such long periods.  

&amp;emsp;Beyond using the body, we can speculate about using sticks and unmodified rocks to knock down fruit or kill prey. But wood decays, and while stones can last, they don't leave evidence of their use.  The ones which were used as tools, like chimpanzees are observed doing today, are indistinguishable from all the other stones which were not.

&amp;emsp;Stones modified by flaking or worn from chopping and cutting are the earliest surviving evidence of technology.  We know the technology was being passed on, because of the persistence of particular techniques and their geographic spread over time.  If they were spontaneous inventions, which were then lost when the inventor died, the timing and distribution would be more random.  

&amp;emsp;'''[[w:Recent_African_origin_of_modern_humans|People Today]]''' appear to be the last surviving species or subspecies of the genus '''[[w:Homo|Homo]]''', although DNA analysis indicates some interbreeding with extinct relatives.  We emerged in anatomically modern form about 0.2-0.3 million years (MY) ago.  This is long after the appearance of early technologies like stone tools (3.3 MY), controlled fire (0.5 - 1.5 MY), and using them for preparing and cooking food (0.5 to possibly 2 MY).  So our evolution to modern form happened in parallel with early technology, and it may have contributed to that evolution.

&amp;emsp;Compared to other tool-users, modern humans seem to be unique in several ways.  These include (1) the number of different objects we make, and their complexity, (2) significant transfer of knowledge from person to person, and indirectly by way of lasting records, (3) extensive use of tools to make other tools, and (4) creating tools which can carry out tasks to some degree on their own.  These features have combined to produce accelerating growth and an increasingly complex society.


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;2.2 - Technology Accumulation and Acceleration&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;  

&amp;emsp;The key advantage technology has given us over genetic evolution is the speed at which it can accumulate and spread.  It helped our ancestors evolve to modern form, out-compete our relatives, and build a civilization which dominates the planet.  We are even at the point of artificially modifying biology, doing so much faster than natural changes happen.

&amp;emsp;Tool marks on fossilized bones and shaped stone tools date back about 3-4 MY, which starts a period we call the '''[[w:Stone_Age|Stone Age]]'''.  These signs show toolmaking was intentional.  Their spread across Africa and Eurasia, similarity, persistence over time, and gradual improvement shows knowledge was being passed on.  This makes them the first identifiable class of technology, if not the first to develop.  Stone tools are harder and sharper than our body parts, and replaceable when broken, but limited by the muscle power we can supply.  

&amp;emsp;The next great advance was '''[[w:Control_of_fire_by_early_humans|Harnessing Fire]]'''.  This increased usable energy, and allowed transforming materials in ways not possible using only stone tools.  Fires occur naturally, so it is hard to identify when we first learned to use it and pass on the knowledge.  Evidence from caves containing human fossils, hearths, and the remains of fires indicate the technology had been mastered no later than 0.5 MY ago, but possibly starting a million years earlier.  Aside from the immediate uses for warmth and discouraging predators, fire led to cooking.  Various cooking methods increase available calories, reduce toxicity and pathogens, and preserve some foods for later use.  Stone tools, fire, and cooking gave us a survival advantage. It also allowed us to evolve to modern form, with larger brains that need more energy.

&amp;emsp;Since reaching our current form, modern humans have developed technology and culture at an accelerating pace.  This includes clothing, language, ceramics, domesticated species, and many others.  There is a strong positive feedback loop that causes this acceleration.  Improved tools gave early humans a survival advantage.  Their numbers multiplied and they spread geographically.  Assuming a constant rate of inventiveness at a given point in our evolution, more people means more inventions.  New locations with a greater variety of living conditions encouraged new solutions to the problems they faced.  For example, cold climates led to a need for clothing.  New inventions, once made, could then spread elsewhere and be further modified, increasing our survival advantage.  

&amp;emsp;On top of this feedback loop was the gradual increase in the size and energy use of our brains.  This increased our inventiveness over the last three million years, but it also allowed for larger social groups.  Modern humans form groups of about 150 people, compared to about 40 for our distant ancestors.  Larger groups allowed for specialization of skills and therefore becoming more expert in each, further increasing our survival and numbers.  Specialized skills encouraged developing specialized tools for each task.  For example, axes and the many varieties of chisels and saws all cut a material by concentrating forces at a narrow edge.  But their sizes and shapes have evolved according to the specific materials and needs of the work.  Specialized tools were an improvement over the previous generic ones.  They also improved survival and increased population, adding to the feedback loop.

&amp;emsp;'''[[w:Agriculture|Agriculture]]''' is the part of technology concerned with purposely growing other living things.  It began in multiple places between 23,000 and 12,000 years ago, during and after the last Ice Age maximum.  

&amp;emsp;That living things can grow and make copies of themselves from seeds or by giving birth was probably always evident to people. Understanding the detailed mechanisms only started a few hundred years ago, including replication of DNA, division of cells, and all the supporting bioprocesses.  But long before understanding the details, people knew seeds grew into full sized plants, which in turn produced more seeds, and animals gave birth to small copies of themselves which grew to full size.  This is known as a '''[[w:Biological_life_cycle|Biological Life Cycle]]'''.

&amp;emsp;Because each plant generally produces many seeds, their number can grow exponentially until they are limited by competition or available resources.  So any natural landscape which can support them tends to be covered in plants.  Total oceanic '''[[w:Primary_production|Primary Production]]''' approximately equals that on land, but is more thinly distributed because the water absorbs sunlight before it can be used.  It also consists of more microscopic organisms on a relative basis due to lack of solid anchorage in deep waters.

&amp;emsp;Once people learned to exploit the supply of nutrients, in particular plants and animals, and started raising them intentionally, the natural ability of living things to grow exponentially increased the human food supply dramatically.  In turn, human population also grew exponentially.  More people means more inventions, including better ways to pass on knowledge.  So knowledge and culture have also grown at an accelerating rate.


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;2.3 - Knowledge Transfer&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;

&amp;emsp;DNA encodes genetic information, and is passed from generation to generation.  But it doesn't change at all, or very little, in the life of an individual.  It can slowly change through mutation, and by shuffling parts during replication.  The organisms better adapted to their environment by such changes have a survival advantage, and become more common.  But it may take many generations for an improvement to spread through a population.  In contrast, learning is a process which allows variable information to accumulate within the life of a single organism.

&amp;emsp;The ability to learn has evolved in many forms throughout the animal kingdom ('''[https://doi.org/10.1017/S1464793103006225  Moore, 2004]''').  That evolution was at the same slow pace of other genetics, but once learning is possible, information could accumulate faster.  For most species, the learning is lost when the individual dies and must be done anew each generation.  Knowledge transfer is more efficient since the organism doesn't have to repeat all the trial and error in accumulating knowledge.  Instead it receives useful information previously learned by others, and has the opportunity to improve on it and pass the improvements to the next generation.  

&amp;emsp;Early knowledge transfer used methods like observation and imitation, with later additions like gestures and pantomime to focus attention.  These transfer methods didn't require special tools.  Language and memory techniques are technologies that allowed larger amounts of knowledge to be stored and transferred, over longer time periods.  They need training, but still did not need external tools.  Art and writing further increased the quantity, persistence, and accuracy of knowledge transfer, and began to store the knowledge separately from people.  These techniques now required tools like pigments and chisels to put the information on durable media like stone.  Our ability to store, transfer, and copy knowledge has only improved with time, with more and more advanced tools to do it with.

&amp;emsp;Pictorial art, such as cave paintings and figurines, didn't require specialized knowledge to understand because they were similar to the originals they represented.  Pictorial symbols were more abstract and required some learning to understand.  Finally, abstract symbols like numbers and alphabets required the most learning to use, but could represent ideas and new things which didn't yet exist.  Along with increasing abstraction, our storage media have evolved from marked stone to clay, papyrus, printed paper, and the rapidly changing electronic methods.


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;2.4 - Sequential Toolmaking and Specialization&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;

&amp;emsp;Parts of the body are the universal first tools, but they are grown rather than made, and their variety is fixed by genetics.  For a given species, body parts have a fixed repertoire of actions they can perform.  For example, human elbows are limited to less than 180 degrees in bending.  Body parts are also limited in terms of strength, size, durability, and other features.  You can use your fist as a hammer, but only for certain light tasks without injury.  Many animals use natural objects, like rocks and twigs, as tools to pound or poke.  Fewer will modify natural objects to suit a task.  Humans, and our recent relatives, seem to be the only species who first make one tool, then use that to make another, which we call &quot;sequential toolmaking&quot;. 

&amp;emsp;  '''[[w:Hammerstone|Hammerstones]]''' are natural round stones used to shape other stones, or to crush, pound, or grind other materials.  They are found, rather than made.  The oldest identifiable made tools are split and flaked stones from Kenya that are 3.3 million years old.  They were not used to make more tools.  If they wore out or broke, you needed to start fresh with new rocks.  The skills and knowledge, however, could be copied by observation and imitation, even if language did not exist yet.  Later in our history, the original stone tools started to be used to make secondary tools.

&amp;emsp;A '''[[w:Hand_axe|Hand axe]]''' may be shaped by a hammerstone.  If the axe is then used to cut and shape a '''[[w:Digging_stick|Digging Stick]]''', which in turn is used to pry up edible roots, that is a sequence of two tools, both of which are made.  Sequential toolmaking requires enough memory and planning to accomplish the whole series.  The knowledge and production may be among several people, but they all have to exist within a given society.  Hand axes and scrapers made from split rocks can be used to cut and peel branches, which can then be used as handles for axes.  A tool with more than one part and made from different materials is a step up in complexity.  Complex tools can be more efficient.  In this case the handle increases leverage and allows more splitting force.   

&amp;emsp;The earliest cycle of tools to make more tools of the same kind may be using digging sticks and hammerstones to excavate and flake stones, which in turn can cut and sharpen more digging sticks.  Over time, hand tools such as these were used to make better tools and artifacts, a process which still continues today.  Modern humans have developed by far the most complex sequences of tools used to make other tools.  This includes loops which lead back to earlier and simpler tools.


&amp;emsp;'''Specialization''' - As our social groups got larger, their members developed specialized skills.  One of these skills was making tools for others to use.  Specialized groups of toolmakers, such as blacksmiths, were able to copy their own tools, plus make tools for other people.  We can make a distinction between the toolmakers and nearly everyone else - who use tools made by others.  Specialized toolmakers persist as a significant segment of industry, since modern civilization can't function without all the tools they make.  This includes making better tools than the ones we already have, a process we expect to continue in the future.  Modern society is filled with tools, from kitchen utensils to smartphones.  But the vast selection tools and machines found throughout civilization can all trace their existence to the self-making toolmakers.

&amp;emsp;Early blacksmiths could copy tools for themselves and others, but their work was not mechanized and certainly not automated.  Animal, water, and wind power later augmented human muscles, and increased total production.  More recently steam and electrical power further improved production rates.  As the scale of production and the knowledge involved grew, toolmakers also became specialized.  Specialties like mining, steel mills, foundries, and machinery builders still retain the collective ability to make more tools and machines of the type they themselves use.  So as a group they are still able to copy their own tools, plus make tools and machines for others.


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;2.5 - Self-Operating Tools&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;

&amp;emsp;'''Energy''' - Tools require energy to perform their function.  At first, all work was performed entirely by human muscle, which in turn gets its energy from food.  The first outside energy source was probably fire, for tasks like cooking, firing pottery, and smelting copper.  Once animals were domesticated we could add their muscles to ours.

&amp;emsp;'''[[w:Mechanization|Mechanization]]''' refers to the replacement of muscle power with devices using other power sources.  Boats using wind power and mills using water power are early examples.  They have been used since ancient times in particular cultures and for particular tasks, but many tasks were still performed by muscles.  Replacing muscle power only became widespread since the '''[[w:Industrial_Revolution|Industrial Revolution]]''', starting around 1760.  Coal and sometimes wood were used to make steam, whose pressure could drive mechanical devices.  More recent engines use combustion gases to directly produce motion.  Electricity from a variety of energy sources has allowed distributing power to whatever devices need it.  Motors can convert this power to motion at the point of use.


&amp;emsp;'''Self-Operation''' - For three million years our tools were passive, not doing anything unless people used them.  A fire can continue to burn for a time once started, but requires frequent attention for safety and additional fuel.  '''[[w:Domestication|Domesticated]]''' species may be considered the first self-operating tools.  They are improvements over acquiring food in the wild, and agriculture is an important technology, so they fit within a broad definition of tools.  Since they are living things, hunting dogs can chase prey, livestock can forage, and cultivated plants can grow, all without constant human attention or work.  

&amp;emsp;Domestication of living things started about 15-30,000 years ago.  It wasn't until about 7,500 years ago, with the development of sail power, that non-living tools could start to perform active functions to some degree on their own.  Wind provided an external energy source to move the sail, and the boat it was attached to.  As long as the wind is steady, the boat can continue to move without constant attention by people.  This differs from rowing or paddling, which need constant action.  

&amp;emsp;Simple tools, like a hammer, need a person's constant attention and muscle power to operate.  More complex ones, like an electric drill, replace some or all of the muscle power, but still need our full attention and guidance.  A '''[[w:Mill_(grinding)|Mill]]''' powered by wind or water may not need constant attention to keep turning and grinding, though it still needs labor for other tasks.  It is therefore partially self-operating.  


&amp;emsp;'''Smart Tools''' - Where mechanization replaces muscles, technologies like '''[[w:Automation|Automation]]''', '''[[w:Robotics|Robotics]]''', '''[[w:Software|Software]]''' and '''[[w:Artificial_intelligence|Artificial Intelligence]]''' (AI) can also replace the senses, and decision-making of people.  We call devices which use such technologies '''Smart Tools'''.  They make possible mechanical, electrical, electronic, and information systems which can function to a greater degree on their own.  This reduces the need for constant human attention and intervention for work tasks.  Therefore more can get done relative to the time people spend on it.

&amp;emsp;By the mid-20th century, electronics had developed to the point they could be programmed and used as sensors.  The field of '''[[w:Control_theory|Control Theory]]''' had developed enough to design self-operating systems that used these electronic devices.  Automation, robotics, and software started to develop on a large scale from that time.  AI took until the late 20th century to develop enough for practical applications, and is now being widely deployed.

&amp;emsp;If our tools no longer need our strength, attention, guidance, or control, the need for our labor is reduced or eliminated.  In theory, a set of sufficiently smart tools could be given instructions, then then proceed to build everything else we need and want with little effort on our part.  This includes making copies of itself.  In practice, we don't yet have tools that smart.  The ones we do have, though, are increasingly able to work on their own and need less help from us.  Smart tools are the latest in a long series of '''[[w:Productivity_improving_technologies|Productivity Improving Technologies]]'''.  Like new sources of energy and mechanization, they will lead to a better quality of life, but in the process can disrupt economic systems based on trading labor for other goods and services.


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;2.6 - Cultural Elements&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;

&amp;emsp;Culture can be described as things that persist in society beyond the life of any given person.  It includes both non-material elements and '''[[w:Material_culture|Material Culture]]'''.  Non-material culture includes things like patterns and knowledge.  For example, an early '''[[w:Hunter-gatherer|Hunter-Gatherer]]''' band could persist as a pattern for a much longer time than any member lived.  Language and how to use it is knowledge that can be passed down through many generations orally, without ever being written down.  Material culture, like tools and cities can, if maintained, also last well past the life of any individual.  The life span of an artifact, however, does not determine if it is cultural.  The important feature is whether it exists independent of human biology.  For example, a fast food soft drink cup may only be used for a few minutes, or sit on a shelf for years, but our internal biology does not affect these lifetimes.

&amp;emsp;All kinds of cultural elements can exhibit growth and replication.  A hunter-gatherer band can grow to the point it divides into two bands.  A language can grow by the addition of new words, and by new people adopting it.  New languages can form when people live far enough from each other that they rarely communicate.  Shifts in vocabulary and usage then lead to enough changes that there are two distinct languages instead of one.

&amp;emsp;Widespread distribution of media like books and video have tended to stabilize language content, and worldwide communications means nobody is too far away any more to interact.  Although the trend is now for small languages to disappear in favor of the more common ones, the remaining languages continue to grow by adding new words and speakers.  Cities can grow horizontally in area and vertically above and below ground level.  Historically they multiplied by intentionally setting up colonies, or grew around a local feature by attracting settlers.  No two cities are the same, but they may share many similar components.

&amp;emsp;The oldest elements of culture that showed growth and replication predate modern humans.  They include '''[[w:Band_society|Band Society]]''', and early types of technology in the form of hunting, foraging, and tool-making skills.  Species of the genus '''[[w:Homo|Homo]]''', to which we belong, expanded repeatedly across the world over the past few million years.  Successful social groups therefore presumably divided when their population became larger than a given area could support.

&amp;emsp;Skills could grow by accumulation of details and technique and by specialization.  Each person has a limited memory and time to learn.  So specialization allows more total skills to be passed on.  Cultural replication included making new copies of tools from raw materials, but not generally using an existing tool to copy itself.  Instead, a collection of tools was brought to bear on making copies of its members.


==&lt;span style=&quot;font-size:x-large; font-family:'Georgia', serif;&quot;&gt;3.0 - Industry and Economics&lt;/span&gt;==
&amp;emsp;

[[File:Five_Myr_Climate_Change.svg|thumb|right|640x233px|Figure 2.0-2 - Quaternary glaciation temperature variations.]]

&amp;emsp;The last 2.8 million years are known as the '''[[w:Quaternary_glaciation|Quaternary Glaciation]]''', during which ice sheets have expanded over parts of the world's land areas. There was both a drop in the long-term average temperature, and increasingly large temperature cycles of 41,000 and then 100,000 years (Figure 2.0-2).  The Antarctic ice sheet persisted even in the warm periods, and variable amounts of other ice sheets grew during the cold periods.  Our ancestors evolved during the Quaternary, and our modern form developed during the last few thermal cycles, 200-300 thousand years ago.

&amp;emsp;For reasons that are not entirely clear, after the most recent warming 18-12,000 years ago, there was a dramatic change in our technology, culture, and population.  In a relatively short period we went from hunter/gatherer bands to space travel, developing agriculture, cities, and large accumulations of knowledge.  Work has become very specialized, and trade using money as an intermediary is now world-wide.  These changes also brought new kinds problems and side effects, including the ones identified in the Introduction (Chapter 1.0).


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;3.1 - Economics&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;

&amp;emsp;Before developing tools and technology, our ancestors survived the same way as other animals.  They were part of biological ecosystems, and obtained their food mainly from other living things.  Both primates and their food sources were self-reproducing, and self-expanding to the point of filling their ecological niches.  Goods and services, and therefore trade, were limited in scope, consisting of highly local things like sharing food and grooming.  Studies of living primates indicate they have a sense of fairness and reciprocity, so our ancestors likely did too.  These behaviors enhanced group survival, but they also underlie modern trade.


&amp;emsp;'''Early Trade''' - By the start of the '''[[w:Neolithic|Neolithic]]''', around 12,000 years ago, modern humans had developed a number of technologies and tool types.  These included an assortment of stone tools, fire, cooking, clothing, the first domesticated species (dogs), and ceramics.  Prior to the development of agriculture, societies were more mobile, because they had to follow or go to where the food was.  This limited the amount of tools and other artifacts they could accumulate to the level of seasonal camps.  Whatever they could not carry to the next location had to be left behind and made anew, or if durable enough, stored in caches for later return.  

&amp;emsp;People at that time were anatomically modern.  Their social groups could range up to around 150 members, so could specialize in different tasks.  Specialization involves trade in goods and services from other specialists.  The mobility of hunter-gatherer cultures meant they also encountered other groups in the course of their seasonal movements.  This encouraged trade in specialties between the groups, in their members, and in items and materials which came from more distant places.

&amp;emsp;The '''[[w:Neolithic_Revolution|Neolithic Revolution]]''' marks the transition from hunter-gatherer to agriculture and fixed settlements as a way of life.  This happened multiple times in separate locations around the world.  Domestication of plants and livestock increased their quality as food sources.  Intentional planting and care of herds greatly increased the food supply relative to the natural state.  The increased quality and quantity of food allowed for large increases in population density.  

&amp;emsp;Raising plants and animals was an investment of labor with a delayed return.  The need to protect that work led to less mobile populations.  Fixed settlements enabled managing crops, storing food reserves, protecting people and their animals from the elements and natural and human predators.  People continued replicating themselves and their food supply through biology, and copying their tools and artifacts through technology.  Individual settlements gradually expanded, and their numbers increased by starting new settlements in in different places.


&amp;emsp;'''Economic Evolution''' - The increased work that went into agriculture led to property rights as a way to secure that work.  You owned what you put work into making or improving.  Other people weren't allowed to take it because in effect it was taking the part of your life that went into it.  Various ways to protect property developed over time, such as laws and customs, or walls and gates.  

&amp;emsp;Improved food production produced a surplus.  This allowed more people to engage in other crafts and services.  One of the new specialties was trading items made by others, i.e. merchants.  The amount of goods a merchant can handle isn't limited in the same way a farmer is limited in the area of crops they can grow.  The work involved in making a trade can be much less than the work to make the items being traded.  Trades only happen when both parties see an advantage in it.  So dedicated traders can accumulate large total gains.  Ownership passes when goods are traded.  So individual traders can accumulate ownership of many goods, more than they can handle themselves.  They can then hire as many people as needed to do the physical work, trading a share of their gains for the work.  

&amp;emsp;One type of property is land, either in the natural state, or has had work put into it like a farm.  As populations grew, new areas were occupied, initially by mobile bands.  The food from that area was necessary to live, so as a group they protected it from incursion by others.  By virtue of the protection work they considered it &quot;their land&quot;, to be passed down to later generations.  As property rights developed with agriculture, specific pieces of land were claimed by families and individuals and passed down.   

&amp;emsp;Large areas of land could be accumulated by peaceful methods like trade and inheritance.  Another method is taking it using force and violence.  The takers could then use slaves or tenants to work the land for them.  They took a share of the products by threats or force (pillage), or by imposing rules and customs to make it habitual (taxation).  As with merchants, hirelings like soldiers and tax collectors could multiply the gains in return for a share in them.  Concentrated ownership, whether through peaceful or violent methods, made possible much larger inequalities than those based on individual abilities.

[[File:World_population_growth_(log-log_scale).png|thumb|right|800x480px|Figure 2.0-3 - World population over time.]] 

&amp;emsp;The development of property rights, increased division of labor, organized trade, accumulation of wealth, and taxation all came out of the Neolithic Revolution.  They produced an economic system with recognizable elements that persist to this day.  Agriculture also induced a huge increase in population (Figure 2.0-3).  The graph shows population history on a logarithmic scale, to better show the dramatic changes in both speed and numbers.  Each labeled division on the axes is a factor of ten in time before the year 2000 (horizontal) and total population in millions(vertical).

&amp;emsp;Population before agriculture was a few million.  By the time iron production became widespread, about 1000 BC, it had grown to about 50 million, and by the time of Classical Greece to 150 million.  The much larger population led to more rapid improvements in technology, including in economic systems.  The general trend of population growth and accelerated change has continued to the present day, with occasional setbacks.  


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;a&gt;&lt;u&gt;3.2 - Modern Economies&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;

&amp;emsp;The work people do in modern economies, and how they do it, is highly specialized.  The US Bureau of Labor Statistics tracks over a thousand '''[https://www.bls.gov/oes/current/oes_nat.htm Detailed Occupations]''', each of which are further specialized.  For example, farm workers in crops are listed as one occupation type, but vegetables, fruits, and field crops all use different skills and equipment.  The US Census Bureau tracks over a thousand different industries in their '''[https://www.census.gov/naics/ Statistics System]''', all of which use different tools and skills to produce different goods and services.  Specialization is efficient, but people and industries must then trade for all the things they don't make or do themselves. 

&amp;emsp;Modern economies are also based on a mixture of voluntary trade and action, and involuntary use of force, actual or implied.  To the extent people find the functions of government useful, and are willing to pay for them, they are funded voluntarily.  There are always people who would contribute less if not forced to, so that portion is involuntary.  When the dominant mode of trade and action is voluntary, we call it a '''[[w:Market_(economics)|Market]]''' economy.  When that economy also includes large proportions of capital accumulation, wage labor, and trade using money, we call it '''[[w:Capitalism|Capitalism]]'''.  

&amp;emsp;Modern economies typically include a capitalist sector, smaller-scale individual trade, plus a variable-sized government sector whose control varies from autocratic to extensive public choice and direction.  Trade is now interconnected on a world-wide scale, so there are no truly isolated economies any more.  There are many local variations in the relative sizes of government, capitalist, and individual sectors, in the extent of physical and social development, and in the local environments and resources which underlie the economic activity.

&amp;emsp;In terms of total activity, the modern world economy is mostly based on large-scale capitalism.  By large-scale, we mean large amounts of capital controlled by a smaller number of people and organizations.  They employ larger numbers of people for their specialized labor, and pay them wages in return.  For example, in the US, only about 10% of workers do so for themselves rather than others.  The capitalists keep a share of the revenues as profits.  

&amp;emsp;The majority of people, both wage-earners and capital owners, then use the money they obtain as an intermediate good to trade for the other goods and services they need and want.  The goods and services in turn are mainly produced by the capital owners and their organizations, forming a complete trading system.  Governments operate in a similar way - employing people and paying them wages.  The difference is their capital is publicly owned rather than private.

&amp;emsp;A system where most people work for wages is a relatively recent historical development.  For example, in the United States (US) the majority of workers were agricultural until 1880, and primarily worked for themselves (see Table 2 in '''[https://www.nber.org/chapters/c1567.pdf Output, Employment, &amp; Productivity in the United States, Brady, NBER, 1966]''').


==&lt;span style=&quot;font-size:x-large; font-family:'Georgia', serif;&quot;&gt;4.0 - Economic Problems and Approaches&lt;/span&gt;==
&amp;emsp;

&amp;emsp;There are several drivers in the current system which have produced rapid economic growth relative to earlier periods.  These include innate desires, competition, and improved technology.  While modern economies have brought many benefits, they have also created problems, some of which we consider in this section.

&amp;emsp;Capitalist economies have an implicit goal of perpetual self-expansion.  This is driven by the desires for a better quality of life and the accumulation of wealth and power.  These desires are expressed in monetary form by increasing incomes and market values.  But perpetual growth for some can be at the expense of others.  Over-consumption of resources and discharge of wastes in the pursuit of growth can also damage health and the environment in which we all live. 

&amp;emsp;Competition in the current system has made it fairly efficient.  Technical improvements have also increased the quality and quantity of goods and services over the last few centuries.  But these have caused problems due to the pace of change, job insecurity, and economic inequality.  In the future, smart tools may also cause wholesale work displacement.  The current system and the problems it causes can also create social problems.   However, here we will mainly focus on economic problems, their effects on people, and attempts to deal with them.  


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;4.1 - Economic Problems&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;

&amp;emsp;As modern economies evolve, some of their problems can be traced to the effects of change.  Other problems can be traced to inequalities of resources and distribution.  We will group current economic problems under three headings: the pace of change, job insecurity, and economic inequality.  To these we will add the potential future problem of work displacement.


&amp;emsp;'''The Pace of Change''' - The Neolithic Revolution is only 1/300th of the time since the first recognizable tools.  Agriculture caused a large population increase, which started an accelerating a feedback loop:  Our biology, and therefore inventiveness, hasn't changed much in the last 12,000 years.  So more people means more new technology and social innovations per year.  These improvements allow more population growth, and faster spread of inventions and ideas.  So further changes happen more quickly as time goes on.

&amp;emsp;When changes were small during the working life of an individual they were not a major problem.  A given person could continue their current craft, with their existing skills and tools, until they stopped working.  They could gradually be replaced by a new generation of people following new methods.  Until the last few centuries, most people worked for themselves in agriculture.  They could adopt new tools and methods on their own, or stay with the older ways.  The capital required for new items was small enough for individuals and the local community.  For example, the horse collar, horseshoe, and heavy plows increased farm production by 50% and allowed working heavy soils that were previously unsuitable.  Such tools were within reach for local farmers.

&amp;emsp;The pace of change became much faster in recent centuries.  Replacing hand weaving with machine looms, and draft animals with farm tractors took about 50 years each, within the life of one person.  By the late 20th century, electronics were doubling in performance every few years.  Old skills and entire job categories could become obsolete within a working lifetime.  People often could not afford to enter new fields due to the time and expense of retraining.  For some it was too late in their lives to learn new skills and get enough use of them afterwards.   Such people were simply left behind.

&amp;emsp;The capital needed for new technologies like blast furnaces and railroads grew far beyond local means.  To remain economically competitive, people went to work for those who could supply the capital and machines, rather than for themselves.  In many cases people had to take whatever work was available, rather than following their interests and abilities.


&amp;emsp;'''Job Insecurity''' - Individual farming has many risks, but getting laid off when you work for yourself isn't one of them.  Labor is a cost to any business, so owners and management have a constant incentive to reduce it, and thereby increase profits.  They generally employ people only when the expected income from those workers exceed their added costs.  Shifts in market demand, competition, and new technologies can all make previous jobs uneconomic.  Businesses may then resort to layoffs if reductions from retirement or choice to work elsewhere isn't fast enough.  

&amp;emsp;The level of job insecurity from all causes combined is more than from technological change alone.  It includes factors like making bad business decisions or losing market share to competitors.  These can happen even if the total market size and the technologies used haven't changed.  Changes which affect employment constantly happen, so a percentage of people are always at risk of losing their job.  In the US, the actual rate of involuntary job separations is about 15% per year, with between 3.5 and 10% unemployed at any given time.  Our economic system assumes most people trade their labor for money, so they can then trade the money for things they need and want.  Unexpected lack of work is then a problem for meeting basic needs.


&amp;emsp;'''Economic Inequality''' - Early humans had to work together and share to ensure survival.  They had to move to where food could be found, which didn't allow accumulating many physical goods.  So economic inequality was limited.  Since the development of property rights and gaining from the work of others, the inequalities could grow.  Thus ancient emperors and kings accumulated far more wealth and power than the slaves or peasants at the bottom of the social structure.

&amp;emsp;We have a far higher average quality of life today, but these inequalities persist.  Stored wealth provides a reserve to withstand setbacks like job loss or illness.  Low income inhibits building such reserves, so setbacks can be catastrophic.  Lack of resources can result in poor education, which can perpetuate low incomes in later generations.  Poverty also can result in poor nutrition, health care, and living conditions.  Relative poverty can persist even in developed economies, and even while the poor are working.


&amp;emsp;'''Work Displacement''' - New technologies since the mid-20th Century are enabling &quot;smart tools&quot; which can replace part or all of the work people do in existing jobs.  The tools may still need a person's attention part of the time, but significantly less than when the work is done without them.  If fewer people are needed for a given amount of work, then without other changes, those people can become unemployed.

&amp;emsp;The technologies of the '''[[w:Industrial_Revolution|Industrial Revolution]]''' replaced large amounts of manual labor in the past, but the pace of change was slower.  People were able to transition to work in other fields, including new ones enabled by better technology.  The problem with smart tools is they can be rapidly introduced via modern mass production and automation.  They may do jobs so well that entire categories of work are greatly reduced.

&amp;emsp;Demand for new types of goods and services can create replacement jobs, but some people are not suited for high-skill jobs like programming and designing robots.  The number of new jobs may also be much smaller than the ones lost.  Software and robots only need to be designed once, then copied many times.  If new jobs are not created fast enough permanent unemployment may increase in coming years.

&amp;emsp;Some examples of current and near-term work displacement include:

:* Self-checkout at supermarkets and card readers at gas station pumps.  These have reduced the need for cashiers.
:* The mass introduction of warehouse robots by Amazon, which reduces how many workers are needed to fill orders.
:* The ongoing development of self-driving vehicles, which may affect all kinds of transportation and delivery jobs.  Automated warehouses plus automated delivery puts all kinds of retail jobs at risk, by entirely bypassing retail distribution.
:* The development of AI agents like Alexa, Siri, Cortana, and Google Assistant, coupled with augmented/virtual reality devices.  They are currently used for home automation and entertainment.  But in the future, schools may face pressure to replace some of the teacher's work with interactive systems using these kinds of tools.  What happens to teachers and school systems in that case?


&amp;emsp;'''Systemic Effects''' - When competition and technical change eliminate current jobs or make skills obsolete, they break the cycle of work for money, then money for goods and services, by which the current system operates.  Without earned income, the unemployed don't pay income and payroll taxes.  They don't buy as many goods, so sales taxes also go down.  Therefore governments will lose a share of the revenue they need to function.  Lower government revenue means social programs and government employment also decrease, further lowering economic activity.  The businesses the unemployed no longer buy from also lose income and employment, even if they use smart tools.  The owners of such businesses lose a share of their income too.

&amp;emsp;Lack of enough paid work is then a systemic problem for a capitalist economy which depends on it as an integral part.  Such spirals of contracting economic activity are called recessions or depressions, and cause large-scale unhappiness and even civil unrest.  These are undesirable results.  If the existing system can't handle this problem, then what sort of system should replace it?  If changes are required, how do we manage the transition?

&amp;emsp;The wealthy, those with sufficient retirement income, and beneficiaries of social programs are not at immediate risk of becoming unemployed.  Their needs are met in other ways.  Also a significant number of people are dependents of workers, so in total only about half the US population is currently working or between jobs, and directly at risk of displacement.  However, large-scale replacement of work has broader effects on the entire economic system, so it can eventually affect everyone. 

&amp;emsp;This problem isn't yet severe, but it is better to deal with it before it reaches that level.  The other three problems already exist, and we would like to find solutions for them too.  A number of ideas have already been proposed, which we look at below.  It is unclear if these solutions can work on a large scale, singly or in combination.  We would like other options, so Chapter 2.1 presents self-improving systems and seed factories as a new approach that can potentially scale to any size needed.


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;4.2 - Previous and Recent Approaches&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;

&amp;emsp;'''Social Systems''' - Modern humans are '''[[w:Social_animal|Social Animals]]'''.  We constantly interact with other people and depend on them, rather than operate as lone individuals.  Some things we can do for ourselves, such as cooking meals at home.  But to make that possible we rely on other people to supply electricity and natural gas for cooking, make the appliances and utensils we use, and grow, transport, and sell the food to cook.  

&amp;emsp;There have always been members of society who are disadvantaged in some way, or can't fully contribute to the functions of society.  Examples include the very young or old, and those who are injured or sick.  Because we function as a society, we care for others and realize we may become disadvantaged ourselves at some point.

&amp;emsp;Care for others is carried out at the level of family and friends, through voluntary contributions and organizations, and through involuntary programs funded by taxes and operated by governments.  The care has one of two goals.  The first is solve the person's disadvantages if that is possible.  So we raise and educate children, and heal the sick and injured, so they can function as part of society.  If the problems are unsolvable, as with very old people, our goal is to give them at least a decent quality of life.  

&amp;emsp;The economic problems noted in 4.1 above can affect those who are able to work, but disadvantaged by their circumstances.  Their skills may be obsolete due to technological change, or their employer no longer finds their work useful enough to cover their wages.  They are then left without income to buy the things they need.  They may not have the capital, or access to it, to purchase improved equipment.  They may also lack the time, funds, or ability to learn new skills.  These disadvantages leave them unable to enter new fields and continue working.  In the future, so much work may be displaced by smart tools that there simply isn't enough left for the people who want or need it.


&amp;emsp;'''Previous Approaches''' - People have dealt with past economic problems the same ways we deal with other problems in society.  They approach them as individuals, through family and friends, voluntary organizations, or involuntary programs.  Previously used methods have had varying levels of success, and none have yet had to handle wholesale replacement of work.  Proposals to meet the challenges of smart tools may be inadequate.  To the extent they are not full solutions, or we are uncertain of their future capacity as such, there is a need for additional new approaches.

&amp;emsp;Everyone is born unable to care for themselves, and without the knowledge and skills to function as part of society.  The general approach to solving this is care and education of the young.  This is supplied by their parents and some combination of other people.  Childhood education supplies the basic skills for self-care, language, and other areas that are assumed to be needed by everyone in society.  More advanced education and training then supplies specialized skills.  These enable trading work for income.  Some people follow their interests rather than using their skills for maximum income.  This is only possible in societies with enough surplus to support optional activities beyond those needed to live.

&amp;emsp;Generally childhood care and education is provided by parents first, then by government programs funded by taxes.  The more advanced education is provided in a variety of ways: by government programs, by private sources and institutions who have sufficient funds, and by students borrowing against their future income.  Some retraining programs exist for people in later life who choose or are forced to change fields.  The education system generally works, although there are some problems with funding, personal cost, and access.

&amp;emsp;For people who are disadvantaged in other ways besides being young, another general approach is wealth redistribution.  This is mainly via taxes and social programs, with some voluntary contributions and organizations.  Wealth normally flows upwards towards those who already have some.  They gain from the work of those they employ or lend capital to, in addition to whatever work they do themselves.  Unlike their own work, these gains are unlimited, so their wealth can rapidly accumulate.  Redistribution can then have two purposes.  One is to avoid extreme accumulation by the wealthy at the expense of everyone else.  The other is to fund programs from those who are more able to pay, for the general protection and improvement of society as a whole, or directed to the less fortunate or able.  

&amp;emsp;Redistribution happens when the incidence of funding sources is different than the social distributions they provide.  When a billionaire is taxed to fund a public school system, the net distribution is downwards.  But this is not always true of taxes and government programs.  For example, government contracts with companies that have highly paid workers and wealthy corporate owners may move funds higher on the wealth scale than the people taxed to pay for them.  

&amp;emsp;Social programs generally intend to help those who need it via redistribution.  One program to deal with job insecurity is unemployment insurance.  Employers pay a tax to fund this program, which then temporarily pays people who can't find work.  Another set are old age and medical programs funded by employers and the workers themselves.  People eventually grow too old to work, and need more medical care.  They can also become disabled or die when younger.  The programs then provide income and medical coverage for former workers and their dependents.  The redistribution effect comes from benefits being capped while funding has higher limits, and from minimum benefits being supplied even if lower income doesn't cover them.  A third set of programs are aimed at re-education and retraining for people affected by economic changes.

&amp;emsp;In addition to voluntary and government programs, people are encouraged to save from their current wages.  This is to cover adverse conditions like job loss or health problems, and for eventual retirement.  They can also pursue self-training and education.  People helping themselves is useful, but not always possible given their circumstances.  If their income is low, there may not be enough surplus to save.  Their work and family care may not leave enough time to gain new skills.  Overall, the set of approaches used to deal with economic problems have worked well enough that people haven't yet demanded large changes to them.  


&amp;emsp;'''Recent Proposals''' - The rapid development of smart tools has the potential to cause large-scale displacement of work, without creating enough new work in other areas to replace it.  The concern is for the social and economic disruption this can cause in a system based on trading work for money.  The most commonly proposed approach involves increased government redistribution from those who have, to those who do not.  

&amp;emsp;One version is called '''[[w:Basic_income|Basic Income]]''', or sometimes '''[[w:Negative_income_tax|Negative Income Tax]]'''.  It is intended partly to replace other existing social programs with a simpler method, and also to address permanent work displacement.  The concept is to provide payments to every adult, or in some versions every individual, regardless of need or income level.  It would provide a minimum floor to living standards.  People and businesses with sufficient wages and income would be taxed to fund this system, much as they do existing programs.  An alternate version is to increase government employment and funded work programs, such as a '''[https://www.jacobinmag.com/2017/02/federal-job-guarantee-universal-basic-income-investment-jobs-unemployment/ Federal Job Guarantee]'''  This may be more acceptable than simply giving money to everyone, since the recipients are seen as working for what they get, and the work itself can be useful.

&amp;emsp;The problem with these approaches is they can't be sustained in the face of large-scale replacement of work.  As we noted in sectopm 4.1 above, the systemic secondary effects of work displacement reduce many of the other sources for taxation.  There would not be enough tax revenue left to make the payments from.  Very high tax rates on the remaining sources encourage people and businesses to move elsewhere to avoid them, or find ways to hide what is taxable.  Unless the new taxes are applied everywhere and strictly enforce, the incentives to move or hide will be strong.  We see this already with corporations and the wealthy moving funds &quot;offshore&quot; (to another country or jurisdiction) to avoid taxes and hide assets.  The alternative of simply creating money to fund the payments would cause inflation, which has other undesirable side effects.

&amp;emsp;These approaches don't seem sufficient in the face of large-scale work displacement.  So in Chapter 2.1  we propose a new one based on known processes of expansion, replication, and self-improvement.

&lt;/div&gt;

{{BookCat}}</text>
      <sha1>02bbbeo0g3nz79klhyxgeemqku0iwma</sha1>
    </revision>
    <revision>
      <id>4676732</id>
      <parentid>4676731</parentid>
      <timestamp>2026-10-18T10:53:21Z</timestamp>
      <contributor>
        <username>Danielravennest</username>
        <id>13526</id>
      </contributor>
      <origin>4676732</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="73768" sha1="qv0izqqzs9eb6w45azc4c0n0yggyqsl" xml:space="preserve">{{DISPLAYTITLE:&lt;span style=&quot;display:block;text-align:left;font-size:100%;background:#d0f0f0;line-height:2.5em; font-family:'Georgia', serif;&quot;&gt;Chapter 2.0 - History and Concept Development&lt;/span&gt;}}

&lt;div style=&quot;font-size:125%; font-family:'Georgia', serif;&quot;&gt;

&lt;div class=&quot;nonumtoc&quot;&gt;{{TOCright}}&lt;/div&gt;


&amp;emsp;In Chapter 1.0 (Introduction) we identified three large-scale problems: insufficient development, a deteriorating environment, and technological unemployment.  All three are unintentional side effects of how civilization evolved in the past, and may develop in the near future.  

&amp;emsp;The growth of modern civilization is still incomplete and unevenly distributed.  This results in the first problem, of insufficient development.  We've made poor choices in the past due to lack of knowledge and incentives built into the economic system.  These are negatively affecting the environment, the second problem.  A lack of foresight combined with how our economic system works may lead to the third problem, of large-scale unemployment. 

&amp;emsp;Before trying to find solutions, we should first understand the history and processes which brought us to where we are.  So the first part of this chapter covers processes like expansion, growth, and self-improvement in nature, before people evolved.  Then we look at how people have tried to satisfy their needs and make their lives better.  More specifically, technology has a long history in human culture.  We take a look at that history, leading up to modern technology.  In addition to improving our lives, technology brought unsuspected and undesirable side effects, resulting in the current state of civilization.  

&amp;emsp;'''[[Seed_Factories/SelfImprovement|Chapter 2.1: Self-Improvement and Seed Factories]]''' explores self-improvement as an idea, and its relation to ideas like progress and economic development.  The second half of the 20th century took the idea of machine self-replication from theory and philosophy to design and engineering.  Technologies like computers and automation developed quickly in this period, making replication a real possibility.  The original idea was a machine system copying itself without help, by making and assembling copies of all its own parts.  Doing this with physical systems is still beyond our reach.  Electronic information, on the other hand, is easily copied, and automated software can do this without people involved.

&amp;emsp;We have updated the original idea of fully automated self-replication to an evolving system.  It begins with a smaller and simpler seed factory that grows towards higher levels of automation and replication.  The changes to the idea are fairly new and not yet completely worked out.  '''[[Seed_Factories/Technology|Chapter 2.2: Further Research and Development]]''' considers open questions and what isn't yet known about it.  An evolving factory system will also make use of other, more developed, areas of knowledge and experience.  So we also look at their current state-of-the-art.  Lastly, we look at related projects, and topics for future research and development needed to make use of the seed factory approach.
  

==&lt;span style=&quot;font-size:x-large; font-family:'Georgia', serif;&quot;&gt;1.0 - Natural Processes&lt;/span&gt;==
&amp;emsp;

&amp;emsp;Expansion, growth, replication, and tool use are processes which predate civilization, and even modern humans as a species able to think about them.  People have always exploited these processes in the past, knowingly or not, and continue to do so today.  A short review of their history is in order for a couple of reasons.  The first is to understand how modern civilization arrived at its current state.  The other is to identify processes and methods we can use.  We can combine them in new ways, adapt them to meet our needs, and use them to help solve our pressing problems.

&amp;emsp;The natural world doesn't consider internal changes as &quot;better&quot; or &quot;worse&quot;.  Those are labels that people apply based on our needs, desires, and opinions.  We need at least some physical space and objects like food and shelter to keep living.  Beyond the bare necessities, most of us strongly desire additional or higher quality things to make our lives better.

&amp;emsp;So we describe natural changes as improvements when they enable more of the necessities and desirable extras, or make them easier to get.  An example would be the end of the last '''[[w:Ice_age#Glacials_and_interglacials|Glacial Period]]''' about 20,000 years ago, bringing warmer temperatures and freeing fertile land from ice cover.  When nature does it without our help we call it self-improvement.  The natural world has changed for the better, from our standpoint, based on what we know from '''[[w:Astronomy|Astronomy]]''' and '''[[w:Biology|Biology]]'''.


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;1.1 - Astronomy&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;

&amp;emsp;Expansion as a process appears to be as old as the Universe itself.  Red-shifts in the spectra of galaxies, supernova brightness and light curves, and the '''[[w:Cosmic_microwave_background_radiation|Cosmic Microwave Background]]''' radiation imply that '''[[w:Metric_expansion_of_space|space itself is expanding]]'''.  This seems to be the combined effect of strong repulsive forces from '''[[w:Inflation_(cosmology)|Cosmic Inflation]]''' during the '''[[w:Big_Bang|Big Bang]]''' ~13.8 billion years ago, and '''[[w:Dark_energy|Dark Energy]]''', which continues to accelerate the expansion.  If the inflation theory of cosmology is correct, the growth of large scale structures, now hundreds of millions of light years in size, can be traced to microscopic quantum fluctuations during the inflationary era and acoustic waves that occurred somewhat later.

&amp;emsp;Stars, planets, and galaxies grow by '''[[w:Accretion_(astrophysics)|Accretion]]''', the addition of more matter to what is already there.  Since the force of gravity is proportional to mass, the ability to attract more matter grows as more mass is collected.  This leads to '''[[w:Exponential_growth|Exponential Growth]]''', until all the nearby matter is consumed.  Any growth process which is proportional to the current size leads to exponential increases over time. We will see many examples of this in the course of these volumes.  

&amp;emsp;Stars replicate in a limited sense.  They are born with different masses, and their energy output increases much faster than mass.  This is known as the '''[[w:Mass–luminosity_relation|Mass-Luminosity Relation]]'''.  So the larger stars use up their fuel much more quickly, despite starting with more.  As these stars reach the end of their life, they emit large amounts of gas or explode.  The shock waves from these processes can create high density areas in molecular clouds.  These denser areas can collapse to form a new generation of stars.  Our own Sun is thought to be a third generation star whose formation was triggered by a supernova explosion of a nearby older star.

&amp;emsp;The early Universe after the Big Bang consisted of hydrogen and helium, and nearly no other elements. '''[[w:Stellar_nucleosynthesis|Nucleosynthesis]]''', the process by which stars shine, also builds heavier elements.  There are some additional processes which convert one element to another.  We need heavier elements to make the kind planet we live on and the parts of our bodies.  So the evolution of generations of stars producing such elements is considered an improvement.  

&amp;emsp;Planets grow by an exponential process from smaller bodies.  A growing '''[[w:Protoplanet|Protoplanet]]''' has a stronger gravitational field, so it can attract nearby gas, dust, and other small bodies to itself.  As it gets larger, it's gravity can also change the orbits of other bodies.  This causes collisions, with the larger bodies tending to keep more of the combined mass.  Debris from collisions continues to collect by attraction and more collisions.  Eventually most of the available mass is (1) gathered into planets and moons, (2) thrown into the parent star, (3) ejected from the stellar system, or (4) not ejected, but thrown far enough outwards that further collisions are rare.  

&amp;emsp;Once formed, planets continue to affect each other's orbits by gravity, and the parent star supplies energy to keep them warm according to their distance.  The star's output can vary with time, and it can emit other things besides light.  Internally, a planet can generate heat by various means, and that heat can drive geological processes.  So a planet's environment can get better or worse with time in quite complicated ways.

&amp;emsp;'''[[w:Galaxy_formation_and_evolution|Galaxies]]''' formed and continue to evolve by a similar growth and evolution processes.  Random processes produced regions in the early Universe that were denser than others.  They tended to attract other nearby matter to form clouds.  The clouds in turn attracted each other, forming larger and larger structures like galaxies and clusters of galaxies.  Our own Milky Way galaxy is still consuming smaller ones, as evidenced by leftover streams of gas and stars.  The Andromeda galaxy and ours are predicted '''[[w:Andromeda–Milky_Way_collision|to collide]]''' in about 4.5 billion years.  The larger the distances, the longer these growth processes take, so they are incomplete in the Universe today.  

&amp;emsp;Galaxies evolve internally as gas and dust are turned into generations of stars and back again, central black holes grow, and the stars redistribute their positions gravitationally.  By late 2022 we have discovered over 5000 '''[http://exoplanet.eu/ Exoplanets]''' - planets around other stars.  So we now know the evolution of our Galaxy has resulted in many planets besides the ones around the Sun.  

&amp;emsp;We consider the evolution of the Universe from the Big Bang until now to be an improvement.  It has provided the physical space, heavier elements, and the Earth and Sun that have allowed us to evolve and continue to live.  We expect conditions on Earth to deteriorate as the Sun gets brighter and the Earth hotter.  Left to itself, life as we know it on Earth will become impossible in 0.6-1.0 billion years.

&amp;emsp;It is not yet clear how often and for how long conditions suitable for life happen elsewhere.  We also don't know if planetary, stellar, and galactic processes could be artificially used to increase or extend such conditions.  But in the mean time, in our current civilization, we can incorporate the ideas of expansion, replication, and exponential growth into our efforts.


[[File:DNA_replication_en.svg|thumb|right|691x336px|Figure 2.0-1 - Proteins, most of whose names end in -ase, separating DNA strands and assembling new complementary ones, which results in two complete copies.]]  

===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;1.2 - Biology&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;

&amp;emsp;'''[[w:Evolutionary_history_of_life|Living Things]]''' on Earth have grown and reproduced for 3-4 billion years (GY).  As a percentage of the age of the planet, life started soon after the surface cooled enough and frequent large asteroid impacts ended about 3.8 GY ago.  Life as we know it requires water and '''[[w:Organic_compound|Organic Compounds]]'''.  These were either included in the planet's original formation, or delivered afterwards by impacts of comets and asteroids.

&amp;emsp;Growth and reproduction are two of the defining features of '''[[w:Life#Biology|Life]]'''.  Another defining feature of life is '''[[w:Metabolism|Metabolism]]''', the use of available energy to convert ingested materials into parts of the organism.  Some of the new parts are for self-maintenance, and some are for growth.  At some point in its life cycle the organism has grown enough to make copies by division at the cellular level.  Small organisms like '''[[w:Bacteria|Bacteria]]''' and some '''[[w:Algae|Algae]]''' consist of a single cell which divides repeatedly.  Large organisms like whales and trees consist of many cells.  They individually divide, become specialized for different tasks, and are grouped into larger structures.  Organisms can also incorporate non-living matter, like the mineral parts of bones and shells, or the bark of trees.  

&amp;emsp;The replication of a large organism involves partitioning one or a small number of cells into an '''[[w:Embryo|Embryo]]''' or '''[[w:Seed|Seed]]''', a smaller and simpler entity than the mature organism.  This entity contains all the information to build the mature organism, mainly in the form of long double-chain polymer molecules known as '''[[w:DNA|DNA]]''' (Deoxyribonucleic Acid), often after mixing genetic data from two parents.  The sequence of DNA units directs the construction of various '''[[w:Protein|Proteins]]''', which in turn perform a variety of functions necessary for life.  One of these functions is separating the two strands of DNA molecules, and assembling complementary units to make a matching second strand for each (Figure 2.0-1).  When a cell divides, each copy then contains a full set of instructions so it can continue to live.  

&amp;emsp;Biological seeds usually contain the plant embryo, which does the actual growing, a supply of nutrients to support the initial growth, and a protective coating. The nutrient supply supports the embryo until photosynthesis and uptake through roots can take over. Animal embryos develop within eggs - containers with a nutrient supply, or are carried internally and supplied by the mother until birth.  The initial seed or embryo cells divide and specialize until they become a mature copy of the parent organism.  Specialization during the life of one organism, and other short-term changes are affected by '''[[w:Epigenetics|Epigenetic]]''' processes.  Humans, being large organisms, grow and replicate in this way, both at the cellular and whole organism level.  The process of growth from an embryo or seed is at least 400 million years old. 
   
&amp;emsp;Self-reproducing organisms have DNA sequences 0.1 to 670,000 million units in length.  Changes to the sequences happen for a variety of reasons.  The the changes cause differences in how well the modified organisms live and die in their environment.  Different survival and reproduction have produced all the various '''[[s:Species|Species]]''' that exist now, and have existed in the long history of our planet.

&amp;emsp;There are several scales at which these changes can happen: at the individual '''[[w:Nucleotide|Nucleotide]]''' unit level, to longer segments of DNA, and by wholesale reshuffling in '''[[w:Sexual_reproduction|Sexual Reproduction]]'''.  Until very recently, DNA changes were unplanned and undirected, so the evolution of species was random and slow.  For example human DNA varies by 0.1% between individuals in the ~10,000 generations since our modern form evolved.  We vary by 1.2% in the 7 million years since we diverged from our nearest living relatives.  We can distinguish between long-term information such as coded in DNA, and shorter-term information such as '''[[w:Epigenetics|Epigenetics]]''' and individual memories, which are outside of DNA changes.  

&amp;emsp;Most of the energy for life ultimately comes from the Sun.   Waste products and dead organisms are recycled by other organisms, or accumulate as sediments, which are converted to rock formations by geologic processes.  Over very long periods of time, the rocks can again become available as raw materials for life.  Communities of living things, together with the non-living surroundings they interact with, form linked '''[[w:Ecosystem|Ecosystems]]'''.  These are dynamic entities through which energy and materials flow, often in cycles with feedback loops.
  
&amp;emsp;All living things interact with their surroundings by ingesting food, rejecting wastes, and using local energy sources to sustain themselves.  Many species also modify their surroundings by building non-living constructs outside their bodies, such as '''[[w:Nest|Nests]]''', '''[[w:Burrow|Burrows]]''', and '''[[w:Beaver_dam|Dams]]'''.  Once built, these structures can perform functions like shelter from the environment or protection from predators.  The non-living objects don't need constant biological activity to sustain them.

&amp;emsp;People also interact with and modify our surroundings, build non-living objects, and participate in ecosystems with other living things.  We depend on the self-expansion and replication abilities of other living things to supply food and other products we need and use.
 
&amp;emsp;We can apply ideas from biology, such as specialization during growth, replication via a smaller and simpler starter entity (i.e. a seed), and replication of information into our designs.  We can also incorporate the ideas of energy and material sources, recycling, and ecosystems of related elements.  Since many features from biology can be included into artificial self-improving and replicating systems, we can consider them forms of '''[[w:Artificial_life|Artificial Life]]'''.


==&lt;span style=&quot;font-size:x-large; font-family:'Georgia', serif;&quot;&gt;2.0 - Technology and Culture&lt;/span&gt;==
&amp;emsp;

&amp;emsp;The natural processes of expansion and replication started billions of years before the roughly 300,000 year history of '''[[w:Human|Modern Humans]]'''.  As living beings we continue to participate in these processes, and they continue to operate in nature.  What makes us distinct is our creation of technology and culture.  In a broad sense, '''[[w:Technology|Technology]]''' includes the knowledge and skills needed to make things, but also putting that knowledge to practical use for all the tools, artifacts, and products we make.  A tool like a hammer is a technical artifact, but knowing how to make and use hammers is a part of technical knowledge.  Humans also produce '''[[w:Culture|Culture]]''' - entities that persist beyond the death of individual people.  Both technology and culture involve growth and replication processes.  We can better meet our needs by intentionally using these processes in the systems we build.


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;2.1 - Recent Evolution and Early Tools&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;
  
&amp;emsp;Some animals actively '''[[w:Tool_use_by_animals|Use Tools]]''', objects which are not permanent parts of their bodies.  Tools let them perform tasks more effectively than their bodies can alone.  Most animal tool-use is passed genetically or arises spontaneously.  They lack a knowledge component, so we don't call them technology.  Knowledge is learned, saved, and passed on to others.  We don't know exactly when the first technologies arose that were passed on this way.  Before that, tools were invented each time, then lost when that individual died.

&amp;emsp;Many of our relatives among the '''[[w:Primate|Primates]]''' have been observed using simple tools such as sticks and leaves to gather food.  Some groups of wild chimpanzees use tools to chop large fruit into smaller pieces so they can be eaten.  Neighboring groups do not do this, suggesting knowledge is being learned or passed on within the group that does.  So this would count as a very early technology.  

&amp;emsp;Our early human ancestors also made this kind of transition from spontaneous to learned tool-use at some point millions of years ago.  This was likely among the '''[[w:Hominidae|Hominid]]''' (Great Apes) family of primates to which we belong, but an earlier species now extinct and distinctly different from us.

&amp;emsp;It is hard to pin down exactly when and how the '''[[w:History_of_technology|History of Technology]]''' began.  The oldest activities that might be classed as technology are foraging and nest building by hand.  Other species of Great Apes do this, and likely our ancestors millions of years ago did too.  However, the remains of meals and nests are biological, and perish over such long periods.  

&amp;emsp;Beyond using the body, we can speculate about using sticks and unmodified rocks to knock down fruit or kill prey. But wood decays, and while stones can last, they don't leave evidence of their use.  The ones which were used as tools, like chimpanzees are observed doing today, are indistinguishable from all the other stones which were not.

&amp;emsp;Stones modified by flaking or worn from chopping and cutting are the earliest surviving evidence of technology.  We know the technology was being passed on, because of the persistence of particular techniques and their geographic spread over time.  If they were spontaneous inventions, which were then lost when the inventor died, the timing and distribution would be more random.  

&amp;emsp;'''[[w:Recent_African_origin_of_modern_humans|People Today]]''' appear to be the last surviving species or subspecies of the genus '''[[w:Homo|Homo]]''', although DNA analysis indicates some interbreeding with extinct relatives.  We emerged in anatomically modern form about 0.2-0.3 million years (MY) ago.  This is long after the appearance of early technologies like stone tools (3.3 MY), controlled fire (0.5 - 1.5 MY), and using them for preparing and cooking food (0.5 to possibly 2 MY).  So our evolution to modern form happened in parallel with early technology, and it may have contributed to that evolution.

&amp;emsp;Compared to other tool-users, modern humans seem to be unique in several ways.  These include (1) the number of different objects we make, and their complexity, (2) significant transfer of knowledge from person to person, and indirectly by way of lasting records, (3) extensive use of tools to make other tools, and (4) creating tools which can carry out tasks to some degree on their own.  These features have combined to produce accelerating growth and an increasingly complex society.


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;2.2 - Technology Accumulation and Acceleration&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;  

&amp;emsp;The key advantage technology has given us over genetic evolution is the speed at which it can accumulate and spread.  It helped our ancestors evolve to modern form, out-compete our relatives, and build a civilization which dominates the planet.  We are even at the point of artificially modifying biology, doing so much faster than natural changes happen.

&amp;emsp;Tool marks on fossilized bones and shaped stone tools date back about 3-4 MY, which starts a period we call the '''[[w:Stone_Age|Stone Age]]'''.  These signs show toolmaking was intentional.  Their spread across Africa and Eurasia, similarity, persistence over time, and gradual improvement shows knowledge was being passed on.  This makes them the first identifiable class of technology, if not the first to develop.  Stone tools are harder and sharper than our body parts, and replaceable when broken, but limited by the muscle power we can supply.  

&amp;emsp;The next great advance was '''[[w:Control_of_fire_by_early_humans|Harnessing Fire]]'''.  This increased usable energy, and allowed transforming materials in ways not possible using only stone tools.  Fires occur naturally, so it is hard to identify when we first learned to use it and pass on the knowledge.  Evidence from caves containing human fossils, hearths, and the remains of fires indicate the technology had been mastered no later than 0.5 MY ago, but possibly starting a million years earlier.  Aside from the immediate uses for warmth and discouraging predators, fire led to cooking.  Various cooking methods increase available calories, reduce toxicity and pathogens, and preserve some foods for later use.  Stone tools, fire, and cooking gave us a survival advantage. It also allowed us to evolve to modern form, with larger brains that need more energy.

&amp;emsp;Since reaching our current form, modern humans have developed technology and culture at an accelerating pace.  This includes clothing, language, ceramics, domesticated species, and many others.  There is a strong positive feedback loop that causes this acceleration.  Improved tools gave early humans a survival advantage.  Their numbers multiplied and they spread geographically.  Assuming a constant rate of inventiveness at a given point in our evolution, more people means more inventions.  New locations with a greater variety of living conditions encouraged new solutions to the problems they faced.  For example, cold climates led to a need for clothing.  New inventions, once made, could then spread elsewhere and be further modified, increasing our survival advantage.  

&amp;emsp;On top of this feedback loop was the gradual increase in the size and energy use of our brains.  This increased our inventiveness over the last three million years, but it also allowed for larger social groups.  Modern humans form groups of about 150 people, compared to about 40 for our distant ancestors.  Larger groups allowed for specialization of skills and therefore becoming more expert in each, further increasing our survival and numbers.  Specialized skills encouraged developing specialized tools for each task.  For example, axes and the many varieties of chisels and saws all cut a material by concentrating forces at a narrow edge.  But their sizes and shapes have evolved according to the specific materials and needs of the work.  Specialized tools were an improvement over the previous generic ones.  They also improved survival and increased population, adding to the feedback loop.

&amp;emsp;'''[[w:Agriculture|Agriculture]]''' is the part of technology concerned with purposely growing other living things.  It began in multiple places between 23,000 and 12,000 years ago, during and after the last Ice Age maximum.  

&amp;emsp;That living things can grow and make copies of themselves from seeds or by giving birth was probably always evident to people. Understanding the detailed mechanisms only started a few hundred years ago, including replication of DNA, division of cells, and all the supporting bioprocesses.  But long before understanding the details, people knew seeds grew into full sized plants, which in turn produced more seeds, and animals gave birth to small copies of themselves which grew to full size.  This is known as a '''[[w:Biological_life_cycle|Biological Life Cycle]]'''.

&amp;emsp;Because each plant generally produces many seeds, their number can grow exponentially until they are limited by competition or available resources.  So any natural landscape which can support them tends to be covered in plants.  Total oceanic '''[[w:Primary_production|Primary Production]]''' approximately equals that on land, but is more thinly distributed because the water absorbs sunlight before it can be used.  It also consists of more microscopic organisms on a relative basis due to lack of solid anchorage in deep waters.

&amp;emsp;Once people learned to exploit the supply of nutrients, in particular plants and animals, and started raising them intentionally, the natural ability of living things to grow exponentially increased the human food supply dramatically.  In turn, human population also grew exponentially.  More people means more inventions, including better ways to pass on knowledge.  So knowledge and culture have also grown at an accelerating rate.


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;2.3 - Knowledge Transfer&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;

&amp;emsp;DNA encodes genetic information, and is passed from generation to generation.  But it doesn't change at all, or very little, in the life of an individual.  It can slowly change through mutation, and by shuffling parts during replication.  The organisms better adapted to their environment by such changes have a survival advantage, and become more common.  But it may take many generations for an improvement to spread through a population.  In contrast, learning is a process which allows variable information to accumulate within the life of a single organism.

&amp;emsp;The ability to learn has evolved in many forms throughout the animal kingdom ('''[https://doi.org/10.1017/S1464793103006225  Moore, 2004]''').  That evolution was at the same slow pace of other genetics, but once learning is possible, information could accumulate faster.  For most species, the learning is lost when the individual dies and must be done anew each generation.  Knowledge transfer is more efficient since the organism doesn't have to repeat all the trial and error in accumulating knowledge.  Instead it receives useful information previously learned by others, and has the opportunity to improve on it and pass the improvements to the next generation.  

&amp;emsp;Early knowledge transfer used methods like observation and imitation, with later additions like gestures and pantomime to focus attention.  These transfer methods didn't require special tools.  Language and memory techniques are technologies that allowed larger amounts of knowledge to be stored and transferred, over longer time periods.  They need training, but still did not need external tools.  Art and writing further increased the quantity, persistence, and accuracy of knowledge transfer, and began to store the knowledge separately from people.  These techniques now required tools like pigments and chisels to put the information on durable media like stone.  Our ability to store, transfer, and copy knowledge has only improved with time, with more and more advanced tools to do it with.

&amp;emsp;Pictorial art, such as cave paintings and figurines, didn't require specialized knowledge to understand because they were similar to the originals they represented.  Pictorial symbols were more abstract and required some learning to understand.  Finally, abstract symbols like numbers and alphabets required the most learning to use, but could represent ideas and new things which didn't yet exist.  Along with increasing abstraction, our storage media have evolved from marked stone to clay, papyrus, printed paper, and the rapidly changing electronic methods.


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;2.4 - Sequential Toolmaking and Specialization&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;

&amp;emsp;Parts of the body are the universal first tools, but they are grown rather than made, and their variety is fixed by genetics.  For a given species, body parts have a fixed repertoire of actions they can perform.  For example, human elbows are limited to less than 180 degrees in bending.  Body parts are also limited in terms of strength, size, durability, and other features.  You can use your fist as a hammer, but only for certain light tasks without injury.  Many animals use natural objects, like rocks and twigs, as tools to pound or poke.  Fewer will modify natural objects to suit a task.  Humans, and our recent relatives, seem to be the only species who first make one tool, then use that to make another, which we call &quot;sequential toolmaking&quot;. 

&amp;emsp;  '''[[w:Hammerstone|Hammerstones]]''' are natural round stones used to shape other stones, or to crush, pound, or grind other materials.  They are found, rather than made.  The oldest identifiable made tools are split and flaked stones from Kenya that are 3.3 million years old.  They were not used to make more tools.  If they wore out or broke, you needed to start fresh with new rocks.  The skills and knowledge, however, could be copied by observation and imitation, even if language did not exist yet.  Later in our history, the original stone tools started to be used to make secondary tools.

&amp;emsp;A '''[[w:Hand_axe|Hand axe]]''' may be shaped by a hammerstone.  If the axe is then used to cut and shape a '''[[w:Digging_stick|Digging Stick]]''', which in turn is used to pry up edible roots, that is a sequence of two tools, both of which are made.  Sequential toolmaking requires enough memory and planning to accomplish the whole series.  The knowledge and production may be among several people, but they all have to exist within a given society.  Hand axes and scrapers made from split rocks can be used to cut and peel branches, which can then be used as handles for axes.  A tool with more than one part and made from different materials is a step up in complexity.  Complex tools can be more efficient.  In this case the handle increases leverage and allows more splitting force.   

&amp;emsp;The earliest cycle of tools to make more tools of the same kind may be using digging sticks and hammerstones to excavate and flake stones, which in turn can cut and sharpen more digging sticks.  Over time, hand tools such as these were used to make better tools and artifacts, a process which still continues today.  Modern humans have developed by far the most complex sequences of tools used to make other tools.  This includes loops which lead back to earlier and simpler tools.


&amp;emsp;'''Specialization''' - As our social groups got larger, their members developed specialized skills.  One of these skills was making tools for others to use.  Specialized groups of toolmakers, such as blacksmiths, were able to copy their own tools, plus make tools for other people.  We can make a distinction between the toolmakers and nearly everyone else - who use tools made by others.  Specialized toolmakers persist as a significant segment of industry, since modern civilization can't function without all the tools they make.  This includes making better tools than the ones we already have, a process we expect to continue in the future.  Modern society is filled with tools, from kitchen utensils to smartphones.  But the vast selection tools and machines found throughout civilization can all trace their existence to the self-making toolmakers.

&amp;emsp;Early blacksmiths could copy tools for themselves and others, but their work was not mechanized and certainly not automated.  Animal, water, and wind power later augmented human muscles, and increased total production.  More recently steam and electrical power further improved production rates.  As the scale of production and the knowledge involved grew, toolmakers also became specialized.  Specialties like mining, steel mills, foundries, and machinery builders still retain the collective ability to make more tools and machines of the type they themselves use.  So as a group they are still able to copy their own tools, plus make tools and machines for others.


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;2.5 - Self-Operating Tools&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;

&amp;emsp;'''Energy''' - Tools require energy to perform their function.  At first, all work was performed entirely by human muscle, which in turn gets its energy from food.  The first outside energy source was probably fire, for tasks like cooking, firing pottery, and smelting copper.  Once animals were domesticated we could add their muscles to ours.

&amp;emsp;'''[[w:Mechanization|Mechanization]]''' refers to the replacement of muscle power with devices using other power sources.  Boats using wind power and mills using water power are early examples.  They have been used since ancient times in particular cultures and for particular tasks, but many tasks were still performed by muscles.  Replacing muscle power only became widespread since the '''[[w:Industrial_Revolution|Industrial Revolution]]''', starting around 1760.  Coal and sometimes wood were used to make steam, whose pressure could drive mechanical devices.  More recent engines use combustion gases to directly produce motion.  Electricity from a variety of energy sources has allowed distributing power to whatever devices need it.  Motors can convert this power to motion at the point of use.


&amp;emsp;'''Self-Operation''' - For three million years our tools were passive, not doing anything unless people used them.  A fire can continue to burn for a time once started, but requires frequent attention for safety and additional fuel.  '''[[w:Domestication|Domesticated]]''' species may be considered the first self-operating tools.  They are improvements over acquiring food in the wild, and agriculture is an important technology, so they fit within a broad definition of tools.  Since they are living things, hunting dogs can chase prey, livestock can forage, and cultivated plants can grow, all without constant human attention or work.  

&amp;emsp;Domestication of living things started about 15-30,000 years ago.  It wasn't until about 7,500 years ago, with the development of sail power, that non-living tools could start to perform active functions to some degree on their own.  Wind provided an external energy source to move the sail, and the boat it was attached to.  As long as the wind is steady, the boat can continue to move without constant attention by people.  This differs from rowing or paddling, which need constant action.  

&amp;emsp;Simple tools, like a hammer, need a person's constant attention and muscle power to operate.  More complex ones, like an electric drill, replace some or all of the muscle power, but still need our full attention and guidance.  A '''[[w:Mill_(grinding)|Mill]]''' powered by wind or water may not need constant attention to keep turning and grinding, though it still needs labor for other tasks.  It is therefore partially self-operating.  


&amp;emsp;'''Smart Tools''' - Where mechanization replaces muscles, technologies like '''[[w:Automation|Automation]]''', '''[[w:Robotics|Robotics]]''', '''[[w:Software|Software]]''' and '''[[w:Artificial_intelligence|Artificial Intelligence]]''' (AI) can also replace the senses, and decision-making of people.  We call devices which use such technologies '''Smart Tools'''.  They make possible mechanical, electrical, electronic, and information systems which can function to a greater degree on their own.  This reduces the need for constant human attention and intervention for work tasks.  Therefore more can get done relative to the time people spend on it.

&amp;emsp;By the mid-20th century, electronics had developed to the point they could be programmed and used as sensors.  The field of '''[[w:Control_theory|Control Theory]]''' had developed enough to design self-operating systems that used these electronic devices.  Automation, robotics, and software started to develop on a large scale from that time.  AI took until the late 20th century to develop enough for practical applications, and is now being widely deployed.

&amp;emsp;If our tools no longer need our strength, attention, guidance, or control, the need for our labor is reduced or eliminated.  In theory, a set of sufficiently smart tools could be given instructions, then then proceed to build everything else we need and want with little effort on our part.  This includes making copies of itself.  In practice, we don't yet have tools that smart.  The ones we do have, though, are increasingly able to work on their own and need less help from us.  Smart tools are the latest in a long series of '''[[w:Productivity_improving_technologies|Productivity Improving Technologies]]'''.  Like new sources of energy and mechanization, they will lead to a better quality of life, but in the process can disrupt economic systems based on trading labor for other goods and services.


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;2.6 - Cultural Elements&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;

&amp;emsp;Culture can be described as things that persist in society beyond the life of any given person.  It includes both non-material elements and '''[[w:Material_culture|Material Culture]]'''.  Non-material culture includes things like patterns and knowledge.  For example, an early '''[[w:Hunter-gatherer|Hunter-Gatherer]]''' band could persist as a pattern for a much longer time than any member lived.  Language and how to use it is knowledge that can be passed down through many generations orally, without ever being written down.  Material culture, like tools and cities can, if maintained, also last well past the life of any individual.  The life span of an artifact, however, does not determine if it is cultural.  The important feature is whether it exists independent of human biology.  For example, a fast food soft drink cup may only be used for a few minutes, or sit on a shelf for years, but our internal biology does not affect these lifetimes.

&amp;emsp;All kinds of cultural elements can exhibit growth and replication.  A hunter-gatherer band can grow to the point it divides into two bands.  A language can grow by the addition of new words, and by new people adopting it.  New languages can form when people live far enough from each other that they rarely communicate.  Shifts in vocabulary and usage then lead to enough changes that there are two distinct languages instead of one.

&amp;emsp;Widespread distribution of media like books and video have tended to stabilize language content, and worldwide communications means nobody is too far away any more to interact.  Although the trend is now for small languages to disappear in favor of the more common ones, the remaining languages continue to grow by adding new words and speakers.  Cities can grow horizontally in area and vertically above and below ground level.  Historically they multiplied by intentionally setting up colonies, or grew around a local feature by attracting settlers.  No two cities are the same, but they may share many similar components.

&amp;emsp;The oldest elements of culture that showed growth and replication predate modern humans.  They include '''[[w:Band_society|Band Society]]''', and early types of technology in the form of hunting, foraging, and tool-making skills.  Species of the genus '''[[w:Homo|Homo]]''', to which we belong, expanded repeatedly across the world over the past few million years.  Successful social groups therefore presumably divided when their population became larger than a given area could support.

&amp;emsp;Skills could grow by accumulation of details and technique and by specialization.  Each person has a limited memory and time to learn.  So specialization allows more total skills to be passed on.  Cultural replication included making new copies of tools from raw materials, but not generally using an existing tool to copy itself.  Instead, a collection of tools was brought to bear on making copies of its members.


==&lt;span style=&quot;font-size:x-large; font-family:'Georgia', serif;&quot;&gt;3.0 - Industry and Economics&lt;/span&gt;==
&amp;emsp;

[[File:Five_Myr_Climate_Change.svg|thumb|right|640x233px|Figure 2.0-2 - Quaternary glaciation temperature variations.]]

&amp;emsp;The last 2.8 million years are known as the '''[[w:Quaternary_glaciation|Quaternary Glaciation]]''', during which ice sheets have expanded over parts of the world's land areas. There was both a drop in the long-term average temperature, and increasingly large temperature cycles of 41,000 and then 100,000 years (Figure 2.0-2).  The Antarctic ice sheet persisted even in the warm periods, and variable amounts of other ice sheets grew during the cold periods.  Our ancestors evolved during the Quaternary, and our modern form developed during the last few thermal cycles, 200-300 thousand years ago.

&amp;emsp;For reasons that are not entirely clear, after the most recent warming 18-12,000 years ago, there was a dramatic change in our technology, culture, and population.  In a relatively short period we went from hunter/gatherer bands to space travel, developing agriculture, cities, and large accumulations of knowledge.  Work has become very specialized, and trade using money as an intermediary is now world-wide.  These changes also brought new kinds problems and side effects, including the ones identified in the Introduction (Chapter 1.0).


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;3.1 - Economics&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;

&amp;emsp;Before developing tools and technology, our ancestors survived the same way as other animals.  They were part of biological ecosystems, and obtained their food mainly from other living things.  Both primates and their food sources were self-reproducing, and self-expanding to the point of filling their ecological niches.  Goods and services, and therefore trade, were limited in scope, consisting of highly local things like sharing food and grooming.  Studies of living primates indicate they have a sense of fairness and reciprocity, so our ancestors likely did too.  These behaviors enhanced group survival, but they also underlie modern trade.


&amp;emsp;'''Early Trade''' - By the start of the '''[[w:Neolithic|Neolithic]]''', around 12,000 years ago, modern humans had developed a number of technologies and tool types.  These included an assortment of stone tools, fire, cooking, clothing, the first domesticated species (dogs), and ceramics.  Prior to the development of agriculture, societies were more mobile, because they had to follow or go to where the food was.  This limited the amount of tools and other artifacts they could accumulate to the level of seasonal camps.  Whatever they could not carry to the next location had to be left behind and made anew, or if durable enough, stored in caches for later return.  

&amp;emsp;People at that time were anatomically modern.  Their social groups could range up to around 150 members, so could specialize in different tasks.  Specialization involves trade in goods and services from other specialists.  The mobility of hunter-gatherer cultures meant they also encountered other groups in the course of their seasonal movements.  This encouraged trade in specialties between the groups, in their members, and in items and materials which came from more distant places.

&amp;emsp;The '''[[w:Neolithic_Revolution|Neolithic Revolution]]''' marks the transition from hunter-gatherer to agriculture and fixed settlements as a way of life.  This happened multiple times in separate locations around the world.  Domestication of plants and livestock increased their quality as food sources.  Intentional planting and care of herds greatly increased the food supply relative to the natural state.  The increased quality and quantity of food allowed for large increases in population density.  

&amp;emsp;Raising plants and animals was an investment of labor with a delayed return.  The need to protect that work led to less mobile populations.  Fixed settlements enabled managing crops, storing food reserves, protecting people and their animals from the elements and natural and human predators.  People continued replicating themselves and their food supply through biology, and copying their tools and artifacts through technology.  Individual settlements gradually expanded, and their numbers increased by starting new settlements in in different places.


&amp;emsp;'''Economic Evolution''' - The increased work that went into agriculture led to property rights as a way to secure that work.  You owned what you put work into making or improving.  Other people weren't allowed to take it because in effect it was taking the part of your life that went into it.  Various ways to protect property developed over time, such as laws and customs, or walls and gates.  

&amp;emsp;Improved food production produced a surplus.  This allowed more people to engage in other crafts and services.  One of the new specialties was trading items made by others, i.e. merchants.  The amount of goods a merchant can handle isn't limited in the same way a farmer is limited in the area of crops they can grow.  The work involved in making a trade can be much less than the work to make the items being traded.  Trades only happen when both parties see an advantage in it.  So dedicated traders can accumulate large total gains.  Ownership passes when goods are traded.  So individual traders can accumulate ownership of many goods, more than they can handle themselves.  They can then hire as many people as needed to do the physical work, trading a share of their gains for the work.  

&amp;emsp;One type of property is land, either in the natural state, or has had work put into it like a farm.  As populations grew, new areas were occupied, initially by mobile bands.  The food from that area was necessary to live, so as a group they protected it from incursion by others.  By virtue of the protection work they considered it &quot;their land&quot;, to be passed down to later generations.  As property rights developed with agriculture, specific pieces of land were claimed by families and individuals and passed down.   

&amp;emsp;Large areas of land could be accumulated by peaceful methods like trade and inheritance.  Another method is taking it using force and violence.  The takers could then use slaves or tenants to work the land for them.  They took a share of the products by threats or force (pillage), or by imposing rules and customs to make it habitual (taxation).  As with merchants, hirelings like soldiers and tax collectors could multiply the gains in return for a share in them.  Concentrated ownership, whether through peaceful or violent methods, made possible much larger inequalities than those based on individual abilities.

[[File:World_population_growth_(log-log_scale).png|thumb|right|800x480px|Figure 2.0-3 - World population over time.]] 

&amp;emsp;The development of property rights, increased division of labor, organized trade, accumulation of wealth, and taxation all came out of the Neolithic Revolution.  They produced an economic system with recognizable elements that persist to this day.  Agriculture also induced a huge increase in population (Figure 2.0-3).  The graph shows population history on a logarithmic scale, to better show the dramatic changes in both speed and numbers.  Each labeled division on the axes is a factor of ten in time before the year 2000 (horizontal) and total population in millions(vertical).

&amp;emsp;Population before agriculture was a few million.  By the time iron production became widespread, about 1000 BC, it had grown to about 50 million, and by the time of Classical Greece to 150 million.  The much larger population led to more rapid improvements in technology, including in economic systems.  The general trend of population growth and accelerated change has continued to the present day, with occasional setbacks.  


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;a&gt;&lt;u&gt;3.2 - Modern Economies&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;

&amp;emsp;The work people do in modern economies, and how they do it, is highly specialized.  The US Bureau of Labor Statistics tracks over a thousand '''[https://www.bls.gov/oes/current/oes_nat.htm Detailed Occupations]''', each of which are further specialized.  For example, farm workers in crops are listed as one occupation type, but vegetables, fruits, and field crops all use different skills and equipment.  The US Census Bureau tracks over a thousand different industries in their '''[https://www.census.gov/naics/ Statistics System]''', all of which use different tools and skills to produce different goods and services.  Specialization is efficient, but people and industries must then trade for all the things they don't make or do themselves. 

&amp;emsp;Modern economies are also based on a mixture of voluntary trade and action, and involuntary use of force, actual or implied.  To the extent people find the functions of government useful, and are willing to pay for them, they are funded voluntarily.  There are always people who would contribute less if not forced to, so that portion is involuntary.  When the dominant mode of trade and action is voluntary, we call it a '''[[w:Market_(economics)|Market]]''' economy.  When that economy also includes large proportions of capital accumulation, wage labor, and trade using money, we call it '''[[w:Capitalism|Capitalism]]'''.  

&amp;emsp;Modern economies typically include a capitalist sector, smaller-scale individual trade, plus a variable-sized government sector whose control varies from autocratic to extensive public choice and direction.  Trade is now interconnected on a world-wide scale, so there are no truly isolated economies any more.  There are many local variations in the relative sizes of government, capitalist, and individual sectors, in the extent of physical and social development, and in the local environments and resources which underlie the economic activity.

&amp;emsp;In terms of total activity, the modern world economy is mostly based on large-scale capitalism.  By large-scale, we mean large amounts of capital controlled by a smaller number of people and organizations.  They employ larger numbers of people for their specialized labor, and pay them wages in return.  For example, in the US, only about 10% of workers do so for themselves rather than others.  The capitalists keep a share of the revenues as profits.  

&amp;emsp;The majority of people, both wage-earners and capital owners, then use the money they obtain as an intermediate good to trade for the other goods and services they need and want.  The goods and services in turn are mainly produced by the capital owners and their organizations, forming a complete trading system.  Governments operate in a similar way - employing people and paying them wages.  The difference is their capital is publicly owned rather than private.

&amp;emsp;A system where most people work for wages is a relatively recent historical development.  For example, in the United States (US) the majority of workers were agricultural until 1880, and primarily worked for themselves (see Table 2 in '''[https://www.nber.org/chapters/c1567.pdf Output, Employment, &amp; Productivity in the United States, Brady, NBER, 1966]''').


==&lt;span style=&quot;font-size:x-large; font-family:'Georgia', serif;&quot;&gt;4.0 - Economic Problems and Approaches&lt;/span&gt;==
&amp;emsp;

&amp;emsp;There are several drivers in the current system which have produced rapid economic growth relative to earlier periods.  These include innate desires, competition, and improved technology.  While modern economies have brought many benefits, they have also created problems, some of which we consider in this section.

&amp;emsp;Capitalist economies have an implicit goal of perpetual self-expansion.  This is driven by the desires for a better quality of life and the accumulation of wealth and power.  These desires are expressed in monetary form by increasing incomes and market values.  But perpetual growth for some can be at the expense of others.  Over-consumption of resources and discharge of wastes in the pursuit of growth can also damage health and the environment in which we all live. 

&amp;emsp;Competition in the current system has made it fairly efficient.  Technical improvements have also increased the quality and quantity of goods and services over the last few centuries.  But these have caused problems due to the pace of change, job insecurity, and economic inequality.  In the future, smart tools may also cause wholesale work displacement.  The current system and the problems it causes can also create social problems.   However, here we will mainly focus on economic problems, their effects on people, and attempts to deal with them.  


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;4.1 - Economic Problems&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;

&amp;emsp;As modern economies evolve, some of their problems can be traced to the effects of change.  Other problems can be traced to inequalities of resources and distribution.  We will group current economic problems under three headings: the pace of change, job insecurity, and economic inequality.  To these we will add the potential future problem of work displacement.


&amp;emsp;'''The Pace of Change''' - The Neolithic Revolution is only 1/300th of the time since the first recognizable tools.  Agriculture caused a large population increase, which started an accelerating a feedback loop:  Our biology, and therefore inventiveness, hasn't changed much in the last 12,000 years.  So more people means more new technology and social innovations per year.  These improvements allow more population growth, and faster spread of inventions and ideas.  So further changes happen more quickly as time goes on.

&amp;emsp;When changes were small during the working life of an individual they were not a major problem.  A given person could continue their current craft, with their existing skills and tools, until they stopped working.  They could gradually be replaced by a new generation of people following new methods.  Until the last few centuries, most people worked for themselves in agriculture.  They could adopt new tools and methods on their own, or stay with the older ways.  The capital required for new items was small enough for individuals and the local community.  For example, the horse collar, horseshoe, and heavy plows increased farm production by 50% and allowed working heavy soils that were previously unsuitable.  Such tools were within reach for local farmers.

&amp;emsp;The pace of change became much faster in recent centuries.  Replacing hand weaving with machine looms, and draft animals with farm tractors took about 50 years each, within the life of one person.  By the late 20th century, electronics were doubling in performance every few years.  Old skills and entire job categories could become obsolete within a working lifetime.  People often could not afford to enter new fields due to the time and expense of retraining.  For some it was too late in their lives to learn new skills and get enough use of them afterwards.   Such people were simply left behind.

&amp;emsp;The capital needed for new technologies like blast furnaces and railroads grew far beyond local means.  To remain economically competitive, people went to work for those who could supply the capital and machines, rather than for themselves.  In many cases people had to take whatever work was available, rather than following their interests and abilities.


&amp;emsp;'''Job Insecurity''' - Individual farming has many risks, but getting laid off when you work for yourself isn't one of them.  Labor is a cost to any business, so owners and management have a constant incentive to reduce it, and thereby increase profits.  They generally employ people only when the expected income from those workers exceed their added costs.  Shifts in market demand, competition, and new technologies can all make previous jobs uneconomic.  Businesses may then resort to layoffs if reductions from retirement or choice to work elsewhere isn't fast enough.  

&amp;emsp;The level of job insecurity from all causes combined is more than from technological change alone.  It includes factors like making bad business decisions or losing market share to competitors.  These can happen even if the total market size and the technologies used haven't changed.  Changes which affect employment constantly happen, so a percentage of people are always at risk of losing their job.  In the US, the actual rate of involuntary job separations is about 15% per year, with between 3.5 and 10% unemployed at any given time.  Our economic system assumes most people trade their labor for money, so they can then trade the money for things they need and want.  Unexpected lack of work is then a problem for meeting basic needs.


&amp;emsp;'''Economic Inequality''' - Early humans had to work together and share to ensure survival.  They had to move to where food could be found, which didn't allow accumulating many physical goods.  So economic inequality was limited.  Since the development of property rights and gaining from the work of others, the inequalities could grow.  Thus ancient emperors and kings accumulated far more wealth and power than the slaves or peasants at the bottom of the social structure.

&amp;emsp;We have a far higher average quality of life today, but these inequalities persist.  Stored wealth provides a reserve to withstand setbacks like job loss or illness.  Low income inhibits building such reserves, so setbacks can be catastrophic.  Lack of resources can result in poor education, which can perpetuate low incomes in later generations.  Poverty also can result in poor nutrition, health care, and living conditions.  Relative poverty can persist even in developed economies, and even while the poor are working.


&amp;emsp;'''Work Displacement''' - New technologies since the mid-20th Century are enabling &quot;smart tools&quot; which can replace part or all of the work people do in existing jobs.  The tools may still need a person's attention part of the time, but significantly less than when the work is done without them.  If fewer people are needed for a given amount of work, then without other changes, those people can become unemployed.

&amp;emsp;The technologies of the '''[[w:Industrial_Revolution|Industrial Revolution]]''' replaced large amounts of manual labor in the past, but the pace of change was slower.  People were able to transition to work in other fields, including new ones enabled by better technology.  The problem with smart tools is they can be rapidly introduced via modern mass production and automation.  They may do jobs so well that entire categories of work are greatly reduced.

&amp;emsp;Demand for new types of goods and services can create replacement jobs, but some people are not suited for high-skill jobs like programming and designing robots.  The number of new jobs may also be much smaller than the ones lost.  Software and robots only need to be designed once, then copied many times.  If new jobs are not created fast enough permanent unemployment may increase in coming years.

&amp;emsp;Some examples of current and near-term work displacement include:

:* Self-checkout at supermarkets and card readers at gas station pumps.  These have reduced the need for cashiers.
:* The mass introduction of warehouse robots by Amazon, which reduces how many workers are needed to fill orders.
:* The ongoing development of self-driving vehicles, which may affect all kinds of transportation and delivery jobs.  Automated warehouses plus automated delivery puts all kinds of retail jobs at risk, by entirely bypassing retail distribution.
:* The development of AI agents like Alexa, Siri, Cortana, and Google Assistant, coupled with augmented/virtual reality devices.  They are currently used for home automation and entertainment.  But in the future, schools may face pressure to replace some of the teacher's work with interactive systems using these kinds of tools.  What happens to teachers and school systems in that case?


&amp;emsp;'''Systemic Effects''' - When competition and technical change eliminate current jobs or make skills obsolete, they break the cycle of work for money, then money for goods and services, by which the current system operates.  Without earned income, the unemployed don't pay income and payroll taxes.  They don't buy as many goods, so sales taxes also go down.  Therefore governments will lose a share of the revenue they need to function.  Lower government revenue means social programs and government employment also decrease, further lowering economic activity.  The businesses the unemployed no longer buy from also lose income and employment, even if they use smart tools.  The owners of such businesses lose a share of their income too.

&amp;emsp;Lack of enough paid work is then a systemic problem for a capitalist economy which depends on it as an integral part.  Such spirals of contracting economic activity are called recessions or depressions, and cause large-scale unhappiness and even civil unrest.  These are undesirable results.  If the existing system can't handle this problem, then what sort of system should replace it?  If changes are required, how do we manage the transition?

&amp;emsp;The wealthy, those with sufficient retirement income, and beneficiaries of social programs are not at immediate risk of becoming unemployed.  Their needs are met in other ways.  Also a significant number of people are dependents of workers, so in total only about half the US population is currently working or between jobs, and directly at risk of displacement.  However, large-scale replacement of work has broader effects on the entire economic system, so it can eventually affect everyone. 

&amp;emsp;This problem isn't yet severe, but it is better to deal with it before it reaches that level.  The other three problems already exist, and we would like to find solutions for them too.  A number of ideas have already been proposed, which we look at below.  It is unclear if these solutions can work on a large scale, singly or in combination.  We would like other options, so Chapter 2.1 presents self-improving systems and seed factories as a new approach that can potentially scale to any size needed.


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;4.2 - Previous and Recent Approaches&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;

&amp;emsp;'''Social Systems''' - Modern humans are '''[[w:Social_animal|Social Animals]]'''.  We constantly interact with other people and depend on them, rather than operate as lone individuals.  Some things we can do for ourselves, such as cooking meals at home.  But to make that possible we rely on other people to supply electricity and natural gas for cooking, make the appliances and utensils we use, and grow, transport, and sell the food to cook.  

&amp;emsp;There have always been members of society who are disadvantaged in some way, or can't fully contribute to the functions of society.  Examples include the very young or old, and those who are injured or sick.  Because we function as a society, we care for others and realize we may become disadvantaged ourselves at some point.

&amp;emsp;Care for others is carried out at the level of family and friends, through voluntary contributions and organizations, and through involuntary programs funded by taxes and operated by governments.  The care has one of two goals.  The first is solve the person's disadvantages if that is possible.  So we raise and educate children, and heal the sick and injured, so they can function as part of society.  If the problems are unsolvable, as with very old people, our goal is to give them at least a decent quality of life.  

&amp;emsp;The economic problems noted in 4.1 above can affect those who are able to work, but disadvantaged by their circumstances.  Their skills may be obsolete due to technological change, or their employer no longer finds their work useful enough to cover their wages.  They are then left without income to buy the things they need.  They may not have the capital, or access to it, to purchase improved equipment.  They may also lack the time, funds, or ability to learn new skills.  These disadvantages leave them unable to enter new fields and continue working.  In the future, so much work may be displaced by smart tools that there simply isn't enough left for the people who want or need it.


&amp;emsp;'''Previous Approaches''' - People have dealt with past economic problems the same ways we deal with other problems in society.  They approach them as individuals, through family and friends, voluntary organizations, or involuntary programs.  Previously used methods have had varying levels of success, and none have yet had to handle wholesale replacement of work.  Proposals to meet the challenges of smart tools may be inadequate.  To the extent they are not full solutions, or we are uncertain of their future capacity as such, there is a need for additional new approaches.

&amp;emsp;Everyone is born unable to care for themselves, and without the knowledge and skills to function as part of society.  The general approach to solving this is care and education of the young.  This is supplied by their parents and some combination of other people.  Childhood education supplies the basic skills for self-care, language, and other areas that are assumed to be needed by everyone in society.  More advanced education and training then supplies specialized skills.  These enable trading work for income.  Some people follow their interests rather than using their skills for maximum income.  This is only possible in societies with enough surplus to support optional activities beyond those needed to live.

&amp;emsp;Generally childhood care and education is provided by parents first, then by government programs funded by taxes.  The more advanced education is provided in a variety of ways: by government programs, by private sources and institutions who have sufficient funds, and by students borrowing against their future income.  Some retraining programs exist for people in later life who choose or are forced to change fields.  The education system generally works, although there are some problems with funding, personal cost, and access.

&amp;emsp;For people who are disadvantaged in other ways besides being young, another general approach is wealth redistribution.  This is mainly via taxes and social programs, with some voluntary contributions and organizations.  Wealth normally flows upwards towards those who already have some.  They gain from the work of those they employ or lend capital to, in addition to whatever work they do themselves.  Unlike their own work, these gains are unlimited, so their wealth can rapidly accumulate.  Redistribution can then have two purposes.  One is to avoid extreme accumulation by the wealthy at the expense of everyone else.  The other is to fund programs from those who are more able to pay, for the general protection and improvement of society as a whole, or directed to the less fortunate or able.  

&amp;emsp;Redistribution happens when the incidence of funding sources is different than the social distributions they provide.  When a billionaire is taxed to fund a public school system, the net distribution is downwards.  But this is not always true of taxes and government programs.  For example, government contracts with companies that have highly paid workers and wealthy corporate owners may move funds higher on the wealth scale than the people taxed to pay for them.  

&amp;emsp;Social programs generally intend to help those who need it via redistribution.  One program to deal with job insecurity is unemployment insurance.  Employers pay a tax to fund this program, which then temporarily pays people who can't find work.  Another set are old age and medical programs funded by employers and the workers themselves.  People eventually grow too old to work, and need more medical care.  They can also become disabled or die when younger.  The programs then provide income and medical coverage for former workers and their dependents.  The redistribution effect comes from benefits being capped while funding has higher limits, and from minimum benefits being supplied even if lower income doesn't cover them.  A third set of programs are aimed at re-education and retraining for people affected by economic changes.

&amp;emsp;In addition to voluntary and government programs, people are encouraged to save from their current wages.  This is to cover adverse conditions like job loss or health problems, and for eventual retirement.  They can also pursue self-training and education.  People helping themselves is useful, but not always possible given their circumstances.  If their income is low, there may not be enough surplus to save.  Their work and family care may not leave enough time to gain new skills.  Overall, the set of approaches used to deal with economic problems have worked well enough that people haven't yet demanded large changes to them.  


&amp;emsp;'''Recent Proposals''' - The rapid development of smart tools has the potential to cause large-scale displacement of work, without creating enough new work in other areas to replace it.  The concern is for the social and economic disruption this can cause in a system based on trading work for money.  The most commonly proposed approach involves increased government redistribution from those who have, to those who do not.  

&amp;emsp;One version is called '''[[w:Basic_income|Basic Income]]''', or sometimes '''[[w:Negative_income_tax|Negative Income Tax]]'''.  It is intended partly to replace other existing social programs with a simpler method, and also to address permanent work displacement.  The concept is to provide payments to every adult, or in some versions every individual, regardless of need or income level.  It would provide a minimum floor to living standards.  People and businesses with sufficient wages and income would be taxed to fund this system, much as they do existing programs.  An alternate version is to increase government employment and funded work programs, such as a '''[https://www.jacobinmag.com/2017/02/federal-job-guarantee-universal-basic-income-investment-jobs-unemployment/ Federal Job Guarantee]'''  This may be more acceptable than simply giving money to everyone, since the recipients are seen as working for what they get, and the work itself can be useful.

&amp;emsp;The problem with these approaches is they can't be sustained in the face of large-scale replacement of work.  As we noted in sectopm 4.1 above, the systemic secondary effects of work displacement reduce many of the other sources for taxation.  There would not be enough tax revenue left to make the payments from.  Very high tax rates on the remaining sources encourage people and businesses to move elsewhere to avoid them, or find ways to hide what is taxable.  Unless the new taxes are applied everywhere and strictly enforce, the incentives to move or hide will be strong.  We see this already with corporations and the wealthy moving funds &quot;offshore&quot; (to another country or jurisdiction) to avoid taxes and hide assets.  The alternative of simply creating money to fund the payments would cause inflation, which has other undesirable side effects.

&amp;emsp;These approaches don't seem sufficient in the face of large-scale work displacement.  So in Chapter 2.1  we propose a new one based on known processes of expansion, replication, and self-improvement.

&lt;/div&gt;

{{BookCat}}</text>
      <sha1>qv0izqqzs9eb6w45azc4c0n0yggyqsl</sha1>
    </revision>
    <revision>
      <id>4676733</id>
      <parentid>4676732</parentid>
      <timestamp>2026-10-18T11:04:15Z</timestamp>
      <contributor>
        <username>Danielravennest</username>
        <id>13526</id>
      </contributor>
      <minor />
      <comment>Formatting &amp; minor edit above section 1.0</comment>
      <origin>4676733</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="73774" sha1="6ea0svflht5d69gggnn8yzojom52h2f" xml:space="preserve">{{DISPLAYTITLE:&lt;span style=&quot;display:block;text-align:left;font-size:100%;background:#d0f0f0;line-height:2.5em; font-family:'Georgia', serif;&quot;&gt;Chapter 2.0 - History and Concept Development&lt;/span&gt;}}

&lt;div style=&quot;font-size:125%; font-family:'Georgia', serif;&quot;&gt;

&lt;div class=&quot;nonumtoc&quot;&gt;{{TOCright}}&lt;/div&gt;


&amp;emsp;In Chapter 1.0 (Introduction) we identified three large-scale problems: insufficient development, a deteriorating environment, and technological unemployment.  All three are unintentional side effects of how civilization evolved in the past, and may develop in the near future.  

&amp;emsp;The growth of modern civilization is still incomplete and unevenly distributed.  This results in the first problem, of insufficient development.  We've made poor choices in the past due to lack of knowledge and incentives built into the economic system.  These are negatively affecting the environment, the second problem.  A lack of foresight combined with how our economic system works may lead to the third problem, of large-scale unemployment. 

&amp;emsp;Before trying to find solutions, it would be useful to understand the history and processes which brought us to where we are.  So the first part of this chapter covers processes like expansion, growth, and self-improvement in nature, before people evolved.  Then we look at how people have tried to satisfy their needs and make their lives better.  More specifically, technology has a long history in human culture.  We take a look at that history, leading up to modern technology.  In addition to improving our lives, technology brought unsuspected and undesirable side effects, resulting in the current state of civilization.  

&amp;emsp;'''[[Seed_Factories/SelfImprovement|Chapter 2.1: Self-Improvement and Seed Factories]]''' explores self-improvement as an idea, and its relation to ideas like progress and economic development.  The second half of the 20th century took the idea of machine self-replication from theory and philosophy to design and engineering.  Technologies like computers and automation developed quickly in this period, making replication a real possibility.  The original idea was a machine system copying itself without help, by making and assembling copies of all its own parts.  Doing this with physical systems is still beyond our reach.  Electronic information, on the other hand, is easily copied, and automated software can do this without people involved.

&amp;emsp;We have updated the original idea of fully automated self-replication to an evolving system.  It begins with a smaller and simpler seed factory that grows towards higher levels of automation and replication.  The changes to the idea are fairly new and not yet completely worked out.  '''[[Seed_Factories/Technology|Chapter 2.2: Further Research and Development]]''' considers open questions and what isn't yet known about it.  An evolving factory system will also make use of other, more developed, areas of knowledge and experience.  So we also look at their current state-of-the-art.  Lastly, we look at related projects, and topics for future research and development needed to make use of the seed factory approach.
  

==&lt;span style=&quot;font-size:x-large; font-family:'Georgia', serif;&quot;&gt;1.0 - Natural Processes&lt;/span&gt;==
&amp;emsp;

&amp;emsp;Expansion, growth, replication, and tool use are processes which predate civilization, and even modern humans as a species able to think about them.  People have always exploited these processes in the past, knowingly or not, and continue to do so today.  A short review of their history is in order for a couple of reasons.  The first is to understand how modern civilization arrived at its current state.  The other is to identify processes and methods we can use.  We can combine them in new ways, adapt them to meet our needs, and use them to help solve our pressing problems.

&amp;emsp;The natural world doesn't consider internal changes as &quot;better&quot; or &quot;worse&quot;.  Those are labels that people apply based on our needs, desires, and opinions.  We need at least some physical space and objects like food and shelter to keep living.  Beyond the bare necessities, most of us strongly desire additional or higher quality things to make our lives better.

&amp;emsp;So we describe natural changes as improvements when they enable more of the necessities and desirable extras, or make them easier to get.  An example would be the end of the last '''[[w:Ice_age#Glacials_and_interglacials|Glacial Period]]''' about 20,000 years ago, bringing warmer temperatures and freeing fertile land from ice cover.  When nature does it without our help we call it self-improvement.  The natural world has changed for the better, from our standpoint, based on what we know from '''[[w:Astronomy|Astronomy]]''' and '''[[w:Biology|Biology]]'''.


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;1.1 - Astronomy&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;

&amp;emsp;Expansion as a process appears to be as old as the Universe itself.  Red-shifts in the spectra of galaxies, supernova brightness and light curves, and the '''[[w:Cosmic_microwave_background_radiation|Cosmic Microwave Background]]''' radiation imply that '''[[w:Metric_expansion_of_space|space itself is expanding]]'''.  This seems to be the combined effect of strong repulsive forces from '''[[w:Inflation_(cosmology)|Cosmic Inflation]]''' during the '''[[w:Big_Bang|Big Bang]]''' ~13.8 billion years ago, and '''[[w:Dark_energy|Dark Energy]]''', which continues to accelerate the expansion.  If the inflation theory of cosmology is correct, the growth of large scale structures, now hundreds of millions of light years in size, can be traced to microscopic quantum fluctuations during the inflationary era and acoustic waves that occurred somewhat later.

&amp;emsp;Stars, planets, and galaxies grow by '''[[w:Accretion_(astrophysics)|Accretion]]''', the addition of more matter to what is already there.  Since the force of gravity is proportional to mass, the ability to attract more matter grows as more mass is collected.  This leads to '''[[w:Exponential_growth|Exponential Growth]]''', until all the nearby matter is consumed.  Any growth process which is proportional to the current size leads to exponential increases over time. We will see many examples of this in the course of these volumes.  

&amp;emsp;Stars replicate in a limited sense.  They are born with different masses, and their energy output increases much faster than mass.  This is known as the '''[[w:Mass–luminosity_relation|Mass-Luminosity Relation]]'''.  So the larger stars use up their fuel much more quickly, despite starting with more.  As these stars reach the end of their life, they emit large amounts of gas or explode.  The shock waves from these processes can create high density areas in molecular clouds.  These denser areas can collapse to form a new generation of stars.  Our own Sun is thought to be a third generation star whose formation was triggered by a supernova explosion of a nearby older star.

&amp;emsp;The early Universe after the Big Bang consisted of hydrogen and helium, and nearly no other elements. '''[[w:Stellar_nucleosynthesis|Nucleosynthesis]]''', the process by which stars shine, also builds heavier elements.  There are some additional processes which convert one element to another.  We need heavier elements to make the kind planet we live on and the parts of our bodies.  So the evolution of generations of stars producing such elements is considered an improvement.  

&amp;emsp;Planets grow by an exponential process from smaller bodies.  A growing '''[[w:Protoplanet|Protoplanet]]''' has a stronger gravitational field, so it can attract nearby gas, dust, and other small bodies to itself.  As it gets larger, it's gravity can also change the orbits of other bodies.  This causes collisions, with the larger bodies tending to keep more of the combined mass.  Debris from collisions continues to collect by attraction and more collisions.  Eventually most of the available mass is (1) gathered into planets and moons, (2) thrown into the parent star, (3) ejected from the stellar system, or (4) not ejected, but thrown far enough outwards that further collisions are rare.  

&amp;emsp;Once formed, planets continue to affect each other's orbits by gravity, and the parent star supplies energy to keep them warm according to their distance.  The star's output can vary with time, and it can emit other things besides light.  Internally, a planet can generate heat by various means, and that heat can drive geological processes.  So a planet's environment can get better or worse with time in quite complicated ways.

&amp;emsp;'''[[w:Galaxy_formation_and_evolution|Galaxies]]''' formed and continue to evolve by a similar growth and evolution processes.  Random processes produced regions in the early Universe that were denser than others.  They tended to attract other nearby matter to form clouds.  The clouds in turn attracted each other, forming larger and larger structures like galaxies and clusters of galaxies.  Our own Milky Way galaxy is still consuming smaller ones, as evidenced by leftover streams of gas and stars.  The Andromeda galaxy and ours are predicted '''[[w:Andromeda–Milky_Way_collision|to collide]]''' in about 4.5 billion years.  The larger the distances, the longer these growth processes take, so they are incomplete in the Universe today.  

&amp;emsp;Galaxies evolve internally as gas and dust are turned into generations of stars and back again, central black holes grow, and the stars redistribute their positions gravitationally.  By late 2022 we have discovered over 5000 '''[http://exoplanet.eu/ Exoplanets]''' - planets around other stars.  So we now know the evolution of our Galaxy has resulted in many planets besides the ones around the Sun.  

&amp;emsp;We consider the evolution of the Universe from the Big Bang until now to be an improvement.  It has provided the physical space, heavier elements, and the Earth and Sun that have allowed us to evolve and continue to live.  We expect conditions on Earth to deteriorate as the Sun gets brighter and the Earth hotter.  Left to itself, life as we know it on Earth will become impossible in 0.6-1.0 billion years.

&amp;emsp;It is not yet clear how often and for how long conditions suitable for life happen elsewhere.  We also don't know if planetary, stellar, and galactic processes could be artificially used to increase or extend such conditions.  But in the mean time, in our current civilization, we can incorporate the ideas of expansion, replication, and exponential growth into our efforts.


[[File:DNA_replication_en.svg|thumb|right|691x336px|Figure 2.0-1 - Proteins, most of whose names end in -ase, separating DNA strands and assembling new complementary ones, which results in two complete copies.]]  

===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;1.2 - Biology&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;

&amp;emsp;'''[[w:Evolutionary_history_of_life|Living Things]]''' on Earth have grown and reproduced for 3-4 billion years (GY).  As a percentage of the age of the planet, life started soon after the surface cooled enough and frequent large asteroid impacts ended about 3.8 GY ago.  Life as we know it requires water and '''[[w:Organic_compound|Organic Compounds]]'''.  These were either included in the planet's original formation, or delivered afterwards by impacts of comets and asteroids.

&amp;emsp;Growth and reproduction are two of the defining features of '''[[w:Life#Biology|Life]]'''.  Another defining feature of life is '''[[w:Metabolism|Metabolism]]''', the use of available energy to convert ingested materials into parts of the organism.  Some of the new parts are for self-maintenance, and some are for growth.  At some point in its life cycle the organism has grown enough to make copies by division at the cellular level.  Small organisms like '''[[w:Bacteria|Bacteria]]''' and some '''[[w:Algae|Algae]]''' consist of a single cell which divides repeatedly.  Large organisms like whales and trees consist of many cells.  They individually divide, become specialized for different tasks, and are grouped into larger structures.  Organisms can also incorporate non-living matter, like the mineral parts of bones and shells, or the bark of trees.  

&amp;emsp;The replication of a large organism involves partitioning one or a small number of cells into an '''[[w:Embryo|Embryo]]''' or '''[[w:Seed|Seed]]''', a smaller and simpler entity than the mature organism.  This entity contains all the information to build the mature organism, mainly in the form of long double-chain polymer molecules known as '''[[w:DNA|DNA]]''' (Deoxyribonucleic Acid), often after mixing genetic data from two parents.  The sequence of DNA units directs the construction of various '''[[w:Protein|Proteins]]''', which in turn perform a variety of functions necessary for life.  One of these functions is separating the two strands of DNA molecules, and assembling complementary units to make a matching second strand for each (Figure 2.0-1).  When a cell divides, each copy then contains a full set of instructions so it can continue to live.  

&amp;emsp;Biological seeds usually contain the plant embryo, which does the actual growing, a supply of nutrients to support the initial growth, and a protective coating. The nutrient supply supports the embryo until photosynthesis and uptake through roots can take over. Animal embryos develop within eggs - containers with a nutrient supply, or are carried internally and supplied by the mother until birth.  The initial seed or embryo cells divide and specialize until they become a mature copy of the parent organism.  Specialization during the life of one organism, and other short-term changes are affected by '''[[w:Epigenetics|Epigenetic]]''' processes.  Humans, being large organisms, grow and replicate in this way, both at the cellular and whole organism level.  The process of growth from an embryo or seed is at least 400 million years old. 
   
&amp;emsp;Self-reproducing organisms have DNA sequences 0.1 to 670,000 million units in length.  Changes to the sequences happen for a variety of reasons.  The the changes cause differences in how well the modified organisms live and die in their environment.  Different survival and reproduction have produced all the various '''[[s:Species|Species]]''' that exist now, and have existed in the long history of our planet.

&amp;emsp;There are several scales at which these changes can happen: at the individual '''[[w:Nucleotide|Nucleotide]]''' unit level, to longer segments of DNA, and by wholesale reshuffling in '''[[w:Sexual_reproduction|Sexual Reproduction]]'''.  Until very recently, DNA changes were unplanned and undirected, so the evolution of species was random and slow.  For example human DNA varies by 0.1% between individuals in the ~10,000 generations since our modern form evolved.  We vary by 1.2% in the 7 million years since we diverged from our nearest living relatives.  We can distinguish between long-term information such as coded in DNA, and shorter-term information such as '''[[w:Epigenetics|Epigenetics]]''' and individual memories, which are outside of DNA changes.  

&amp;emsp;Most of the energy for life ultimately comes from the Sun.   Waste products and dead organisms are recycled by other organisms, or accumulate as sediments, which are converted to rock formations by geologic processes.  Over very long periods of time, the rocks can again become available as raw materials for life.  Communities of living things, together with the non-living surroundings they interact with, form linked '''[[w:Ecosystem|Ecosystems]]'''.  These are dynamic entities through which energy and materials flow, often in cycles with feedback loops.
  
&amp;emsp;All living things interact with their surroundings by ingesting food, rejecting wastes, and using local energy sources to sustain themselves.  Many species also modify their surroundings by building non-living constructs outside their bodies, such as '''[[w:Nest|Nests]]''', '''[[w:Burrow|Burrows]]''', and '''[[w:Beaver_dam|Dams]]'''.  Once built, these structures can perform functions like shelter from the environment or protection from predators.  The non-living objects don't need constant biological activity to sustain them.

&amp;emsp;People also interact with and modify our surroundings, build non-living objects, and participate in ecosystems with other living things.  We depend on the self-expansion and replication abilities of other living things to supply food and other products we need and use.
 
&amp;emsp;We can apply ideas from biology, such as specialization during growth, replication via a smaller and simpler starter entity (i.e. a seed), and replication of information into our designs.  We can also incorporate the ideas of energy and material sources, recycling, and ecosystems of related elements.  Since many features from biology can be included into artificial self-improving and replicating systems, we can consider them forms of '''[[w:Artificial_life|Artificial Life]]'''.


==&lt;span style=&quot;font-size:x-large; font-family:'Georgia', serif;&quot;&gt;2.0 - Technology and Culture&lt;/span&gt;==
&amp;emsp;

&amp;emsp;The natural processes of expansion and replication started billions of years before the roughly 300,000 year history of '''[[w:Human|Modern Humans]]'''.  As living beings we continue to participate in these processes, and they continue to operate in nature.  What makes us distinct is our creation of technology and culture.  In a broad sense, '''[[w:Technology|Technology]]''' includes the knowledge and skills needed to make things, but also putting that knowledge to practical use for all the tools, artifacts, and products we make.  A tool like a hammer is a technical artifact, but knowing how to make and use hammers is a part of technical knowledge.  Humans also produce '''[[w:Culture|Culture]]''' - entities that persist beyond the death of individual people.  Both technology and culture involve growth and replication processes.  We can better meet our needs by intentionally using these processes in the systems we build.


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;2.1 - Recent Evolution and Early Tools&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;
  
&amp;emsp;Some animals actively '''[[w:Tool_use_by_animals|Use Tools]]''', objects which are not permanent parts of their bodies.  Tools let them perform tasks more effectively than their bodies can alone.  Most animal tool-use is passed genetically or arises spontaneously.  They lack a knowledge component, so we don't call them technology.  Knowledge is learned, saved, and passed on to others.  We don't know exactly when the first technologies arose that were passed on this way.  Before that, tools were invented each time, then lost when that individual died.

&amp;emsp;Many of our relatives among the '''[[w:Primate|Primates]]''' have been observed using simple tools such as sticks and leaves to gather food.  Some groups of wild chimpanzees use tools to chop large fruit into smaller pieces so they can be eaten.  Neighboring groups do not do this, suggesting knowledge is being learned or passed on within the group that does.  So this would count as a very early technology.  

&amp;emsp;Our early human ancestors also made this kind of transition from spontaneous to learned tool-use at some point millions of years ago.  This was likely among the '''[[w:Hominidae|Hominid]]''' (Great Apes) family of primates to which we belong, but an earlier species now extinct and distinctly different from us.

&amp;emsp;It is hard to pin down exactly when and how the '''[[w:History_of_technology|History of Technology]]''' began.  The oldest activities that might be classed as technology are foraging and nest building by hand.  Other species of Great Apes do this, and likely our ancestors millions of years ago did too.  However, the remains of meals and nests are biological, and perish over such long periods.  

&amp;emsp;Beyond using the body, we can speculate about using sticks and unmodified rocks to knock down fruit or kill prey. But wood decays, and while stones can last, they don't leave evidence of their use.  The ones which were used as tools, like chimpanzees are observed doing today, are indistinguishable from all the other stones which were not.

&amp;emsp;Stones modified by flaking or worn from chopping and cutting are the earliest surviving evidence of technology.  We know the technology was being passed on, because of the persistence of particular techniques and their geographic spread over time.  If they were spontaneous inventions, which were then lost when the inventor died, the timing and distribution would be more random.  

&amp;emsp;'''[[w:Recent_African_origin_of_modern_humans|People Today]]''' appear to be the last surviving species or subspecies of the genus '''[[w:Homo|Homo]]''', although DNA analysis indicates some interbreeding with extinct relatives.  We emerged in anatomically modern form about 0.2-0.3 million years (MY) ago.  This is long after the appearance of early technologies like stone tools (3.3 MY), controlled fire (0.5 - 1.5 MY), and using them for preparing and cooking food (0.5 to possibly 2 MY).  So our evolution to modern form happened in parallel with early technology, and it may have contributed to that evolution.

&amp;emsp;Compared to other tool-users, modern humans seem to be unique in several ways.  These include (1) the number of different objects we make, and their complexity, (2) significant transfer of knowledge from person to person, and indirectly by way of lasting records, (3) extensive use of tools to make other tools, and (4) creating tools which can carry out tasks to some degree on their own.  These features have combined to produce accelerating growth and an increasingly complex society.


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;2.2 - Technology Accumulation and Acceleration&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;  

&amp;emsp;The key advantage technology has given us over genetic evolution is the speed at which it can accumulate and spread.  It helped our ancestors evolve to modern form, out-compete our relatives, and build a civilization which dominates the planet.  We are even at the point of artificially modifying biology, doing so much faster than natural changes happen.

&amp;emsp;Tool marks on fossilized bones and shaped stone tools date back about 3-4 MY, which starts a period we call the '''[[w:Stone_Age|Stone Age]]'''.  These signs show toolmaking was intentional.  Their spread across Africa and Eurasia, similarity, persistence over time, and gradual improvement shows knowledge was being passed on.  This makes them the first identifiable class of technology, if not the first to develop.  Stone tools are harder and sharper than our body parts, and replaceable when broken, but limited by the muscle power we can supply.  

&amp;emsp;The next great advance was '''[[w:Control_of_fire_by_early_humans|Harnessing Fire]]'''.  This increased usable energy, and allowed transforming materials in ways not possible using only stone tools.  Fires occur naturally, so it is hard to identify when we first learned to use it and pass on the knowledge.  Evidence from caves containing human fossils, hearths, and the remains of fires indicate the technology had been mastered no later than 0.5 MY ago, but possibly starting a million years earlier.  Aside from the immediate uses for warmth and discouraging predators, fire led to cooking.  Various cooking methods increase available calories, reduce toxicity and pathogens, and preserve some foods for later use.  Stone tools, fire, and cooking gave us a survival advantage. It also allowed us to evolve to modern form, with larger brains that need more energy.

&amp;emsp;Since reaching our current form, modern humans have developed technology and culture at an accelerating pace.  This includes clothing, language, ceramics, domesticated species, and many others.  There is a strong positive feedback loop that causes this acceleration.  Improved tools gave early humans a survival advantage.  Their numbers multiplied and they spread geographically.  Assuming a constant rate of inventiveness at a given point in our evolution, more people means more inventions.  New locations with a greater variety of living conditions encouraged new solutions to the problems they faced.  For example, cold climates led to a need for clothing.  New inventions, once made, could then spread elsewhere and be further modified, increasing our survival advantage.  

&amp;emsp;On top of this feedback loop was the gradual increase in the size and energy use of our brains.  This increased our inventiveness over the last three million years, but it also allowed for larger social groups.  Modern humans form groups of about 150 people, compared to about 40 for our distant ancestors.  Larger groups allowed for specialization of skills and therefore becoming more expert in each, further increasing our survival and numbers.  Specialized skills encouraged developing specialized tools for each task.  For example, axes and the many varieties of chisels and saws all cut a material by concentrating forces at a narrow edge.  But their sizes and shapes have evolved according to the specific materials and needs of the work.  Specialized tools were an improvement over the previous generic ones.  They also improved survival and increased population, adding to the feedback loop.

&amp;emsp;'''[[w:Agriculture|Agriculture]]''' is the part of technology concerned with purposely growing other living things.  It began in multiple places between 23,000 and 12,000 years ago, during and after the last Ice Age maximum.  

&amp;emsp;That living things can grow and make copies of themselves from seeds or by giving birth was probably always evident to people. Understanding the detailed mechanisms only started a few hundred years ago, including replication of DNA, division of cells, and all the supporting bioprocesses.  But long before understanding the details, people knew seeds grew into full sized plants, which in turn produced more seeds, and animals gave birth to small copies of themselves which grew to full size.  This is known as a '''[[w:Biological_life_cycle|Biological Life Cycle]]'''.

&amp;emsp;Because each plant generally produces many seeds, their number can grow exponentially until they are limited by competition or available resources.  So any natural landscape which can support them tends to be covered in plants.  Total oceanic '''[[w:Primary_production|Primary Production]]''' approximately equals that on land, but is more thinly distributed because the water absorbs sunlight before it can be used.  It also consists of more microscopic organisms on a relative basis due to lack of solid anchorage in deep waters.

&amp;emsp;Once people learned to exploit the supply of nutrients, in particular plants and animals, and started raising them intentionally, the natural ability of living things to grow exponentially increased the human food supply dramatically.  In turn, human population also grew exponentially.  More people means more inventions, including better ways to pass on knowledge.  So knowledge and culture have also grown at an accelerating rate.


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;2.3 - Knowledge Transfer&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;

&amp;emsp;DNA encodes genetic information, and is passed from generation to generation.  But it doesn't change at all, or very little, in the life of an individual.  It can slowly change through mutation, and by shuffling parts during replication.  The organisms better adapted to their environment by such changes have a survival advantage, and become more common.  But it may take many generations for an improvement to spread through a population.  In contrast, learning is a process which allows variable information to accumulate within the life of a single organism.

&amp;emsp;The ability to learn has evolved in many forms throughout the animal kingdom ('''[https://doi.org/10.1017/S1464793103006225  Moore, 2004]''').  That evolution was at the same slow pace of other genetics, but once learning is possible, information could accumulate faster.  For most species, the learning is lost when the individual dies and must be done anew each generation.  Knowledge transfer is more efficient since the organism doesn't have to repeat all the trial and error in accumulating knowledge.  Instead it receives useful information previously learned by others, and has the opportunity to improve on it and pass the improvements to the next generation.  

&amp;emsp;Early knowledge transfer used methods like observation and imitation, with later additions like gestures and pantomime to focus attention.  These transfer methods didn't require special tools.  Language and memory techniques are technologies that allowed larger amounts of knowledge to be stored and transferred, over longer time periods.  They need training, but still did not need external tools.  Art and writing further increased the quantity, persistence, and accuracy of knowledge transfer, and began to store the knowledge separately from people.  These techniques now required tools like pigments and chisels to put the information on durable media like stone.  Our ability to store, transfer, and copy knowledge has only improved with time, with more and more advanced tools to do it with.

&amp;emsp;Pictorial art, such as cave paintings and figurines, didn't require specialized knowledge to understand because they were similar to the originals they represented.  Pictorial symbols were more abstract and required some learning to understand.  Finally, abstract symbols like numbers and alphabets required the most learning to use, but could represent ideas and new things which didn't yet exist.  Along with increasing abstraction, our storage media have evolved from marked stone to clay, papyrus, printed paper, and the rapidly changing electronic methods.


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;2.4 - Sequential Toolmaking and Specialization&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;

&amp;emsp;Parts of the body are the universal first tools, but they are grown rather than made, and their variety is fixed by genetics.  For a given species, body parts have a fixed repertoire of actions they can perform.  For example, human elbows are limited to less than 180 degrees in bending.  Body parts are also limited in terms of strength, size, durability, and other features.  You can use your fist as a hammer, but only for certain light tasks without injury.  Many animals use natural objects, like rocks and twigs, as tools to pound or poke.  Fewer will modify natural objects to suit a task.  Humans, and our recent relatives, seem to be the only species who first make one tool, then use that to make another, which we call &quot;sequential toolmaking&quot;. 

&amp;emsp;  '''[[w:Hammerstone|Hammerstones]]''' are natural round stones used to shape other stones, or to crush, pound, or grind other materials.  They are found, rather than made.  The oldest identifiable made tools are split and flaked stones from Kenya that are 3.3 million years old.  They were not used to make more tools.  If they wore out or broke, you needed to start fresh with new rocks.  The skills and knowledge, however, could be copied by observation and imitation, even if language did not exist yet.  Later in our history, the original stone tools started to be used to make secondary tools.

&amp;emsp;A '''[[w:Hand_axe|Hand axe]]''' may be shaped by a hammerstone.  If the axe is then used to cut and shape a '''[[w:Digging_stick|Digging Stick]]''', which in turn is used to pry up edible roots, that is a sequence of two tools, both of which are made.  Sequential toolmaking requires enough memory and planning to accomplish the whole series.  The knowledge and production may be among several people, but they all have to exist within a given society.  Hand axes and scrapers made from split rocks can be used to cut and peel branches, which can then be used as handles for axes.  A tool with more than one part and made from different materials is a step up in complexity.  Complex tools can be more efficient.  In this case the handle increases leverage and allows more splitting force.   

&amp;emsp;The earliest cycle of tools to make more tools of the same kind may be using digging sticks and hammerstones to excavate and flake stones, which in turn can cut and sharpen more digging sticks.  Over time, hand tools such as these were used to make better tools and artifacts, a process which still continues today.  Modern humans have developed by far the most complex sequences of tools used to make other tools.  This includes loops which lead back to earlier and simpler tools.


&amp;emsp;'''Specialization''' - As our social groups got larger, their members developed specialized skills.  One of these skills was making tools for others to use.  Specialized groups of toolmakers, such as blacksmiths, were able to copy their own tools, plus make tools for other people.  We can make a distinction between the toolmakers and nearly everyone else - who use tools made by others.  Specialized toolmakers persist as a significant segment of industry, since modern civilization can't function without all the tools they make.  This includes making better tools than the ones we already have, a process we expect to continue in the future.  Modern society is filled with tools, from kitchen utensils to smartphones.  But the vast selection tools and machines found throughout civilization can all trace their existence to the self-making toolmakers.

&amp;emsp;Early blacksmiths could copy tools for themselves and others, but their work was not mechanized and certainly not automated.  Animal, water, and wind power later augmented human muscles, and increased total production.  More recently steam and electrical power further improved production rates.  As the scale of production and the knowledge involved grew, toolmakers also became specialized.  Specialties like mining, steel mills, foundries, and machinery builders still retain the collective ability to make more tools and machines of the type they themselves use.  So as a group they are still able to copy their own tools, plus make tools and machines for others.


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;2.5 - Self-Operating Tools&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;

&amp;emsp;'''Energy''' - Tools require energy to perform their function.  At first, all work was performed entirely by human muscle, which in turn gets its energy from food.  The first outside energy source was probably fire, for tasks like cooking, firing pottery, and smelting copper.  Once animals were domesticated we could add their muscles to ours.

&amp;emsp;'''[[w:Mechanization|Mechanization]]''' refers to the replacement of muscle power with devices using other power sources.  Boats using wind power and mills using water power are early examples.  They have been used since ancient times in particular cultures and for particular tasks, but many tasks were still performed by muscles.  Replacing muscle power only became widespread since the '''[[w:Industrial_Revolution|Industrial Revolution]]''', starting around 1760.  Coal and sometimes wood were used to make steam, whose pressure could drive mechanical devices.  More recent engines use combustion gases to directly produce motion.  Electricity from a variety of energy sources has allowed distributing power to whatever devices need it.  Motors can convert this power to motion at the point of use.


&amp;emsp;'''Self-Operation''' - For three million years our tools were passive, not doing anything unless people used them.  A fire can continue to burn for a time once started, but requires frequent attention for safety and additional fuel.  '''[[w:Domestication|Domesticated]]''' species may be considered the first self-operating tools.  They are improvements over acquiring food in the wild, and agriculture is an important technology, so they fit within a broad definition of tools.  Since they are living things, hunting dogs can chase prey, livestock can forage, and cultivated plants can grow, all without constant human attention or work.  

&amp;emsp;Domestication of living things started about 15-30,000 years ago.  It wasn't until about 7,500 years ago, with the development of sail power, that non-living tools could start to perform active functions to some degree on their own.  Wind provided an external energy source to move the sail, and the boat it was attached to.  As long as the wind is steady, the boat can continue to move without constant attention by people.  This differs from rowing or paddling, which need constant action.  

&amp;emsp;Simple tools, like a hammer, need a person's constant attention and muscle power to operate.  More complex ones, like an electric drill, replace some or all of the muscle power, but still need our full attention and guidance.  A '''[[w:Mill_(grinding)|Mill]]''' powered by wind or water may not need constant attention to keep turning and grinding, though it still needs labor for other tasks.  It is therefore partially self-operating.  


&amp;emsp;'''Smart Tools''' - Where mechanization replaces muscles, technologies like '''[[w:Automation|Automation]]''', '''[[w:Robotics|Robotics]]''', '''[[w:Software|Software]]''' and '''[[w:Artificial_intelligence|Artificial Intelligence]]''' (AI) can also replace the senses, and decision-making of people.  We call devices which use such technologies '''Smart Tools'''.  They make possible mechanical, electrical, electronic, and information systems which can function to a greater degree on their own.  This reduces the need for constant human attention and intervention for work tasks.  Therefore more can get done relative to the time people spend on it.

&amp;emsp;By the mid-20th century, electronics had developed to the point they could be programmed and used as sensors.  The field of '''[[w:Control_theory|Control Theory]]''' had developed enough to design self-operating systems that used these electronic devices.  Automation, robotics, and software started to develop on a large scale from that time.  AI took until the late 20th century to develop enough for practical applications, and is now being widely deployed.

&amp;emsp;If our tools no longer need our strength, attention, guidance, or control, the need for our labor is reduced or eliminated.  In theory, a set of sufficiently smart tools could be given instructions, then then proceed to build everything else we need and want with little effort on our part.  This includes making copies of itself.  In practice, we don't yet have tools that smart.  The ones we do have, though, are increasingly able to work on their own and need less help from us.  Smart tools are the latest in a long series of '''[[w:Productivity_improving_technologies|Productivity Improving Technologies]]'''.  Like new sources of energy and mechanization, they will lead to a better quality of life, but in the process can disrupt economic systems based on trading labor for other goods and services.


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;2.6 - Cultural Elements&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;

&amp;emsp;Culture can be described as things that persist in society beyond the life of any given person.  It includes both non-material elements and '''[[w:Material_culture|Material Culture]]'''.  Non-material culture includes things like patterns and knowledge.  For example, an early '''[[w:Hunter-gatherer|Hunter-Gatherer]]''' band could persist as a pattern for a much longer time than any member lived.  Language and how to use it is knowledge that can be passed down through many generations orally, without ever being written down.  Material culture, like tools and cities can, if maintained, also last well past the life of any individual.  The life span of an artifact, however, does not determine if it is cultural.  The important feature is whether it exists independent of human biology.  For example, a fast food soft drink cup may only be used for a few minutes, or sit on a shelf for years, but our internal biology does not affect these lifetimes.

&amp;emsp;All kinds of cultural elements can exhibit growth and replication.  A hunter-gatherer band can grow to the point it divides into two bands.  A language can grow by the addition of new words, and by new people adopting it.  New languages can form when people live far enough from each other that they rarely communicate.  Shifts in vocabulary and usage then lead to enough changes that there are two distinct languages instead of one.

&amp;emsp;Widespread distribution of media like books and video have tended to stabilize language content, and worldwide communications means nobody is too far away any more to interact.  Although the trend is now for small languages to disappear in favor of the more common ones, the remaining languages continue to grow by adding new words and speakers.  Cities can grow horizontally in area and vertically above and below ground level.  Historically they multiplied by intentionally setting up colonies, or grew around a local feature by attracting settlers.  No two cities are the same, but they may share many similar components.

&amp;emsp;The oldest elements of culture that showed growth and replication predate modern humans.  They include '''[[w:Band_society|Band Society]]''', and early types of technology in the form of hunting, foraging, and tool-making skills.  Species of the genus '''[[w:Homo|Homo]]''', to which we belong, expanded repeatedly across the world over the past few million years.  Successful social groups therefore presumably divided when their population became larger than a given area could support.

&amp;emsp;Skills could grow by accumulation of details and technique and by specialization.  Each person has a limited memory and time to learn.  So specialization allows more total skills to be passed on.  Cultural replication included making new copies of tools from raw materials, but not generally using an existing tool to copy itself.  Instead, a collection of tools was brought to bear on making copies of its members.


==&lt;span style=&quot;font-size:x-large; font-family:'Georgia', serif;&quot;&gt;3.0 - Industry and Economics&lt;/span&gt;==
&amp;emsp;

[[File:Five_Myr_Climate_Change.svg|thumb|right|640x233px|Figure 2.0-2 - Quaternary glaciation temperature variations.]]

&amp;emsp;The last 2.8 million years are known as the '''[[w:Quaternary_glaciation|Quaternary Glaciation]]''', during which ice sheets have expanded over parts of the world's land areas. There was both a drop in the long-term average temperature, and increasingly large temperature cycles of 41,000 and then 100,000 years (Figure 2.0-2).  The Antarctic ice sheet persisted even in the warm periods, and variable amounts of other ice sheets grew during the cold periods.  Our ancestors evolved during the Quaternary, and our modern form developed during the last few thermal cycles, 200-300 thousand years ago.

&amp;emsp;For reasons that are not entirely clear, after the most recent warming 18-12,000 years ago, there was a dramatic change in our technology, culture, and population.  In a relatively short period we went from hunter/gatherer bands to space travel, developing agriculture, cities, and large accumulations of knowledge.  Work has become very specialized, and trade using money as an intermediary is now world-wide.  These changes also brought new kinds problems and side effects, including the ones identified in the Introduction (Chapter 1.0).


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;3.1 - Economics&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;

&amp;emsp;Before developing tools and technology, our ancestors survived the same way as other animals.  They were part of biological ecosystems, and obtained their food mainly from other living things.  Both primates and their food sources were self-reproducing, and self-expanding to the point of filling their ecological niches.  Goods and services, and therefore trade, were limited in scope, consisting of highly local things like sharing food and grooming.  Studies of living primates indicate they have a sense of fairness and reciprocity, so our ancestors likely did too.  These behaviors enhanced group survival, but they also underlie modern trade.


&amp;emsp;'''Early Trade''' - By the start of the '''[[w:Neolithic|Neolithic]]''', around 12,000 years ago, modern humans had developed a number of technologies and tool types.  These included an assortment of stone tools, fire, cooking, clothing, the first domesticated species (dogs), and ceramics.  Prior to the development of agriculture, societies were more mobile, because they had to follow or go to where the food was.  This limited the amount of tools and other artifacts they could accumulate to the level of seasonal camps.  Whatever they could not carry to the next location had to be left behind and made anew, or if durable enough, stored in caches for later return.  

&amp;emsp;People at that time were anatomically modern.  Their social groups could range up to around 150 members, so could specialize in different tasks.  Specialization involves trade in goods and services from other specialists.  The mobility of hunter-gatherer cultures meant they also encountered other groups in the course of their seasonal movements.  This encouraged trade in specialties between the groups, in their members, and in items and materials which came from more distant places.

&amp;emsp;The '''[[w:Neolithic_Revolution|Neolithic Revolution]]''' marks the transition from hunter-gatherer to agriculture and fixed settlements as a way of life.  This happened multiple times in separate locations around the world.  Domestication of plants and livestock increased their quality as food sources.  Intentional planting and care of herds greatly increased the food supply relative to the natural state.  The increased quality and quantity of food allowed for large increases in population density.  

&amp;emsp;Raising plants and animals was an investment of labor with a delayed return.  The need to protect that work led to less mobile populations.  Fixed settlements enabled managing crops, storing food reserves, protecting people and their animals from the elements and natural and human predators.  People continued replicating themselves and their food supply through biology, and copying their tools and artifacts through technology.  Individual settlements gradually expanded, and their numbers increased by starting new settlements in in different places.


&amp;emsp;'''Economic Evolution''' - The increased work that went into agriculture led to property rights as a way to secure that work.  You owned what you put work into making or improving.  Other people weren't allowed to take it because in effect it was taking the part of your life that went into it.  Various ways to protect property developed over time, such as laws and customs, or walls and gates.  

&amp;emsp;Improved food production produced a surplus.  This allowed more people to engage in other crafts and services.  One of the new specialties was trading items made by others, i.e. merchants.  The amount of goods a merchant can handle isn't limited in the same way a farmer is limited in the area of crops they can grow.  The work involved in making a trade can be much less than the work to make the items being traded.  Trades only happen when both parties see an advantage in it.  So dedicated traders can accumulate large total gains.  Ownership passes when goods are traded.  So individual traders can accumulate ownership of many goods, more than they can handle themselves.  They can then hire as many people as needed to do the physical work, trading a share of their gains for the work.  

&amp;emsp;One type of property is land, either in the natural state, or has had work put into it like a farm.  As populations grew, new areas were occupied, initially by mobile bands.  The food from that area was necessary to live, so as a group they protected it from incursion by others.  By virtue of the protection work they considered it &quot;their land&quot;, to be passed down to later generations.  As property rights developed with agriculture, specific pieces of land were claimed by families and individuals and passed down.   

&amp;emsp;Large areas of land could be accumulated by peaceful methods like trade and inheritance.  Another method is taking it using force and violence.  The takers could then use slaves or tenants to work the land for them.  They took a share of the products by threats or force (pillage), or by imposing rules and customs to make it habitual (taxation).  As with merchants, hirelings like soldiers and tax collectors could multiply the gains in return for a share in them.  Concentrated ownership, whether through peaceful or violent methods, made possible much larger inequalities than those based on individual abilities.

[[File:World_population_growth_(log-log_scale).png|thumb|right|800x480px|Figure 2.0-3 - World population over time.]] 

&amp;emsp;The development of property rights, increased division of labor, organized trade, accumulation of wealth, and taxation all came out of the Neolithic Revolution.  They produced an economic system with recognizable elements that persist to this day.  Agriculture also induced a huge increase in population (Figure 2.0-3).  The graph shows population history on a logarithmic scale, to better show the dramatic changes in both speed and numbers.  Each labeled division on the axes is a factor of ten in time before the year 2000 (horizontal) and total population in millions(vertical).

&amp;emsp;Population before agriculture was a few million.  By the time iron production became widespread, about 1000 BC, it had grown to about 50 million, and by the time of Classical Greece to 150 million.  The much larger population led to more rapid improvements in technology, including in economic systems.  The general trend of population growth and accelerated change has continued to the present day, with occasional setbacks.  


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;a&gt;&lt;u&gt;3.2 - Modern Economies&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;

&amp;emsp;The work people do in modern economies, and how they do it, is highly specialized.  The US Bureau of Labor Statistics tracks over a thousand '''[https://www.bls.gov/oes/current/oes_nat.htm Detailed Occupations]''', each of which are further specialized.  For example, farm workers in crops are listed as one occupation type, but vegetables, fruits, and field crops all use different skills and equipment.  The US Census Bureau tracks over a thousand different industries in their '''[https://www.census.gov/naics/ Statistics System]''', all of which use different tools and skills to produce different goods and services.  Specialization is efficient, but people and industries must then trade for all the things they don't make or do themselves. 

&amp;emsp;Modern economies are also based on a mixture of voluntary trade and action, and involuntary use of force, actual or implied.  To the extent people find the functions of government useful, and are willing to pay for them, they are funded voluntarily.  There are always people who would contribute less if not forced to, so that portion is involuntary.  When the dominant mode of trade and action is voluntary, we call it a '''[[w:Market_(economics)|Market]]''' economy.  When that economy also includes large proportions of capital accumulation, wage labor, and trade using money, we call it '''[[w:Capitalism|Capitalism]]'''.  

&amp;emsp;Modern economies typically include a capitalist sector, smaller-scale individual trade, plus a variable-sized government sector whose control varies from autocratic to extensive public choice and direction.  Trade is now interconnected on a world-wide scale, so there are no truly isolated economies any more.  There are many local variations in the relative sizes of government, capitalist, and individual sectors, in the extent of physical and social development, and in the local environments and resources which underlie the economic activity.

&amp;emsp;In terms of total activity, the modern world economy is mostly based on large-scale capitalism.  By large-scale, we mean large amounts of capital controlled by a smaller number of people and organizations.  They employ larger numbers of people for their specialized labor, and pay them wages in return.  For example, in the US, only about 10% of workers do so for themselves rather than others.  The capitalists keep a share of the revenues as profits.  

&amp;emsp;The majority of people, both wage-earners and capital owners, then use the money they obtain as an intermediate good to trade for the other goods and services they need and want.  The goods and services in turn are mainly produced by the capital owners and their organizations, forming a complete trading system.  Governments operate in a similar way - employing people and paying them wages.  The difference is their capital is publicly owned rather than private.

&amp;emsp;A system where most people work for wages is a relatively recent historical development.  For example, in the United States (US) the majority of workers were agricultural until 1880, and primarily worked for themselves (see Table 2 in '''[https://www.nber.org/chapters/c1567.pdf Output, Employment, &amp; Productivity in the United States, Brady, NBER, 1966]''').


==&lt;span style=&quot;font-size:x-large; font-family:'Georgia', serif;&quot;&gt;4.0 - Economic Problems and Approaches&lt;/span&gt;==
&amp;emsp;

&amp;emsp;There are several drivers in the current system which have produced rapid economic growth relative to earlier periods.  These include innate desires, competition, and improved technology.  While modern economies have brought many benefits, they have also created problems, some of which we consider in this section.

&amp;emsp;Capitalist economies have an implicit goal of perpetual self-expansion.  This is driven by the desires for a better quality of life and the accumulation of wealth and power.  These desires are expressed in monetary form by increasing incomes and market values.  But perpetual growth for some can be at the expense of others.  Over-consumption of resources and discharge of wastes in the pursuit of growth can also damage health and the environment in which we all live. 

&amp;emsp;Competition in the current system has made it fairly efficient.  Technical improvements have also increased the quality and quantity of goods and services over the last few centuries.  But these have caused problems due to the pace of change, job insecurity, and economic inequality.  In the future, smart tools may also cause wholesale work displacement.  The current system and the problems it causes can also create social problems.   However, here we will mainly focus on economic problems, their effects on people, and attempts to deal with them.  


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;4.1 - Economic Problems&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;

&amp;emsp;As modern economies evolve, some of their problems can be traced to the effects of change.  Other problems can be traced to inequalities of resources and distribution.  We will group current economic problems under three headings: the pace of change, job insecurity, and economic inequality.  To these we will add the potential future problem of work displacement.


&amp;emsp;'''The Pace of Change''' - The Neolithic Revolution is only 1/300th of the time since the first recognizable tools.  Agriculture caused a large population increase, which started an accelerating a feedback loop:  Our biology, and therefore inventiveness, hasn't changed much in the last 12,000 years.  So more people means more new technology and social innovations per year.  These improvements allow more population growth, and faster spread of inventions and ideas.  So further changes happen more quickly as time goes on.

&amp;emsp;When changes were small during the working life of an individual they were not a major problem.  A given person could continue their current craft, with their existing skills and tools, until they stopped working.  They could gradually be replaced by a new generation of people following new methods.  Until the last few centuries, most people worked for themselves in agriculture.  They could adopt new tools and methods on their own, or stay with the older ways.  The capital required for new items was small enough for individuals and the local community.  For example, the horse collar, horseshoe, and heavy plows increased farm production by 50% and allowed working heavy soils that were previously unsuitable.  Such tools were within reach for local farmers.

&amp;emsp;The pace of change became much faster in recent centuries.  Replacing hand weaving with machine looms, and draft animals with farm tractors took about 50 years each, within the life of one person.  By the late 20th century, electronics were doubling in performance every few years.  Old skills and entire job categories could become obsolete within a working lifetime.  People often could not afford to enter new fields due to the time and expense of retraining.  For some it was too late in their lives to learn new skills and get enough use of them afterwards.   Such people were simply left behind.

&amp;emsp;The capital needed for new technologies like blast furnaces and railroads grew far beyond local means.  To remain economically competitive, people went to work for those who could supply the capital and machines, rather than for themselves.  In many cases people had to take whatever work was available, rather than following their interests and abilities.


&amp;emsp;'''Job Insecurity''' - Individual farming has many risks, but getting laid off when you work for yourself isn't one of them.  Labor is a cost to any business, so owners and management have a constant incentive to reduce it, and thereby increase profits.  They generally employ people only when the expected income from those workers exceed their added costs.  Shifts in market demand, competition, and new technologies can all make previous jobs uneconomic.  Businesses may then resort to layoffs if reductions from retirement or choice to work elsewhere isn't fast enough.  

&amp;emsp;The level of job insecurity from all causes combined is more than from technological change alone.  It includes factors like making bad business decisions or losing market share to competitors.  These can happen even if the total market size and the technologies used haven't changed.  Changes which affect employment constantly happen, so a percentage of people are always at risk of losing their job.  In the US, the actual rate of involuntary job separations is about 15% per year, with between 3.5 and 10% unemployed at any given time.  Our economic system assumes most people trade their labor for money, so they can then trade the money for things they need and want.  Unexpected lack of work is then a problem for meeting basic needs.


&amp;emsp;'''Economic Inequality''' - Early humans had to work together and share to ensure survival.  They had to move to where food could be found, which didn't allow accumulating many physical goods.  So economic inequality was limited.  Since the development of property rights and gaining from the work of others, the inequalities could grow.  Thus ancient emperors and kings accumulated far more wealth and power than the slaves or peasants at the bottom of the social structure.

&amp;emsp;We have a far higher average quality of life today, but these inequalities persist.  Stored wealth provides a reserve to withstand setbacks like job loss or illness.  Low income inhibits building such reserves, so setbacks can be catastrophic.  Lack of resources can result in poor education, which can perpetuate low incomes in later generations.  Poverty also can result in poor nutrition, health care, and living conditions.  Relative poverty can persist even in developed economies, and even while the poor are working.


&amp;emsp;'''Work Displacement''' - New technologies since the mid-20th Century are enabling &quot;smart tools&quot; which can replace part or all of the work people do in existing jobs.  The tools may still need a person's attention part of the time, but significantly less than when the work is done without them.  If fewer people are needed for a given amount of work, then without other changes, those people can become unemployed.

&amp;emsp;The technologies of the '''[[w:Industrial_Revolution|Industrial Revolution]]''' replaced large amounts of manual labor in the past, but the pace of change was slower.  People were able to transition to work in other fields, including new ones enabled by better technology.  The problem with smart tools is they can be rapidly introduced via modern mass production and automation.  They may do jobs so well that entire categories of work are greatly reduced.

&amp;emsp;Demand for new types of goods and services can create replacement jobs, but some people are not suited for high-skill jobs like programming and designing robots.  The number of new jobs may also be much smaller than the ones lost.  Software and robots only need to be designed once, then copied many times.  If new jobs are not created fast enough permanent unemployment may increase in coming years.

&amp;emsp;Some examples of current and near-term work displacement include:

:* Self-checkout at supermarkets and card readers at gas station pumps.  These have reduced the need for cashiers.
:* The mass introduction of warehouse robots by Amazon, which reduces how many workers are needed to fill orders.
:* The ongoing development of self-driving vehicles, which may affect all kinds of transportation and delivery jobs.  Automated warehouses plus automated delivery puts all kinds of retail jobs at risk, by entirely bypassing retail distribution.
:* The development of AI agents like Alexa, Siri, Cortana, and Google Assistant, coupled with augmented/virtual reality devices.  They are currently used for home automation and entertainment.  But in the future, schools may face pressure to replace some of the teacher's work with interactive systems using these kinds of tools.  What happens to teachers and school systems in that case?


&amp;emsp;'''Systemic Effects''' - When competition and technical change eliminate current jobs or make skills obsolete, they break the cycle of work for money, then money for goods and services, by which the current system operates.  Without earned income, the unemployed don't pay income and payroll taxes.  They don't buy as many goods, so sales taxes also go down.  Therefore governments will lose a share of the revenue they need to function.  Lower government revenue means social programs and government employment also decrease, further lowering economic activity.  The businesses the unemployed no longer buy from also lose income and employment, even if they use smart tools.  The owners of such businesses lose a share of their income too.

&amp;emsp;Lack of enough paid work is then a systemic problem for a capitalist economy which depends on it as an integral part.  Such spirals of contracting economic activity are called recessions or depressions, and cause large-scale unhappiness and even civil unrest.  These are undesirable results.  If the existing system can't handle this problem, then what sort of system should replace it?  If changes are required, how do we manage the transition?

&amp;emsp;The wealthy, those with sufficient retirement income, and beneficiaries of social programs are not at immediate risk of becoming unemployed.  Their needs are met in other ways.  Also a significant number of people are dependents of workers, so in total only about half the US population is currently working or between jobs, and directly at risk of displacement.  However, large-scale replacement of work has broader effects on the entire economic system, so it can eventually affect everyone. 

&amp;emsp;This problem isn't yet severe, but it is better to deal with it before it reaches that level.  The other three problems already exist, and we would like to find solutions for them too.  A number of ideas have already been proposed, which we look at below.  It is unclear if these solutions can work on a large scale, singly or in combination.  We would like other options, so Chapter 2.1 presents self-improving systems and seed factories as a new approach that can potentially scale to any size needed.


===&lt;span style=&quot;font-size:large; font-family:'Georgia', serif;&quot;&gt;&lt;u&gt;4.2 - Previous and Recent Approaches&lt;/u&gt;&lt;/span&gt;===
&amp;emsp;

&amp;emsp;'''Social Systems''' - Modern humans are '''[[w:Social_animal|Social Animals]]'''.  We constantly interact with other people and depend on them, rather than operate as lone individuals.  Some things we can do for ourselves, such as cooking meals at home.  But to make that possible we rely on other people to supply electricity and natural gas for cooking, make the appliances and utensils we use, and grow, transport, and sell the food to cook.  

&amp;emsp;There have always been members of society who are disadvantaged in some way, or can't fully contribute to the functions of society.  Examples include the very young or old, and those who are injured or sick.  Because we function as a society, we care for others and realize we may become disadvantaged ourselves at some point.

&amp;emsp;Care for others is carried out at the level of family and friends, through voluntary contributions and organizations, and through involuntary programs funded by taxes and operated by governments.  The care has one of two goals.  The first is solve the person's disadvantages if that is possible.  So we raise and educate children, and heal the sick and injured, so they can function as part of society.  If the problems are unsolvable, as with very old people, our goal is to give them at least a decent quality of life.  

&amp;emsp;The economic problems noted in 4.1 above can affect those who are able to work, but disadvantaged by their circumstances.  Their skills may be obsolete due to technological change, or their employer no longer finds their work useful enough to cover their wages.  They are then left without income to buy the things they need.  They may not have the capital, or access to it, to purchase improved equipment.  They may also lack the time, funds, or ability to learn new skills.  These disadvantages leave them unable to enter new fields and continue working.  In the future, so much work may be displaced by smart tools that there simply isn't enough left for the people who want or need it.


&amp;emsp;'''Previous Approaches''' - People have dealt with past economic problems the same ways we deal with other problems in society.  They approach them as individuals, through family and friends, voluntary organizations, or involuntary programs.  Previously used methods have had varying levels of success, and none have yet had to handle wholesale replacement of work.  Proposals to meet the challenges of smart tools may be inadequate.  To the extent they are not full solutions, or we are uncertain of their future capacity as such, there is a need for additional new approaches.

&amp;emsp;Everyone is born unable to care for themselves, and without the knowledge and skills to function as part of society.  The general approach to solving this is care and education of the young.  This is supplied by their parents and some combination of other people.  Childhood education supplies the basic skills for self-care, language, and other areas that are assumed to be needed by everyone in society.  More advanced education and training then supplies specialized skills.  These enable trading work for income.  Some people follow their interests rather than using their skills for maximum income.  This is only possible in societies with enough surplus to support optional activities beyond those needed to live.

&amp;emsp;Generally childhood care and education is provided by parents first, then by government programs funded by taxes.  The more advanced education is provided in a variety of ways: by government programs, by private sources and institutions who have sufficient funds, and by students borrowing against their future income.  Some retraining programs exist for people in later life who choose or are forced to change fields.  The education system generally works, although there are some problems with funding, personal cost, and access.

&amp;emsp;For people who are disadvantaged in other ways besides being young, another general approach is wealth redistribution.  This is mainly via taxes and social programs, with some voluntary contributions and organizations.  Wealth normally flows upwards towards those who already have some.  They gain from the work of those they employ or lend capital to, in addition to whatever work they do themselves.  Unlike their own work, these gains are unlimited, so their wealth can rapidly accumulate.  Redistribution can then have two purposes.  One is to avoid extreme accumulation by the wealthy at the expense of everyone else.  The other is to fund programs from those who are more able to pay, for the general protection and improvement of society as a whole, or directed to the less fortunate or able.  

&amp;emsp;Redistribution happens when the incidence of funding sources is different than the social distributions they provide.  When a billionaire is taxed to fund a public school system, the net distribution is downwards.  But this is not always true of taxes and government programs.  For example, government contracts with companies that have highly paid workers and wealthy corporate owners may move funds higher on the wealth scale than the people taxed to pay for them.  

&amp;emsp;Social programs generally intend to help those who need it via redistribution.  One program to deal with job insecurity is unemployment insurance.  Employers pay a tax to fund this program, which then temporarily pays people who can't find work.  Another set are old age and medical programs funded by employers and the workers themselves.  People eventually grow too old to work, and need more medical care.  They can also become disabled or die when younger.  The programs then provide income and medical coverage for former workers and their dependents.  The redistribution effect comes from benefits being capped while funding has higher limits, and from minimum benefits being supplied even if lower income doesn't cover them.  A third set of programs are aimed at re-education and retraining for people affected by economic changes.

&amp;emsp;In addition to voluntary and government programs, people are encouraged to save from their current wages.  This is to cover adverse conditions like job loss or health problems, and for eventual retirement.  They can also pursue self-training and education.  People helping themselves is useful, but not always possible given their circumstances.  If their income is low, there may not be enough surplus to save.  Their work and family care may not leave enough time to gain new skills.  Overall, the set of approaches used to deal with economic problems have worked well enough that people haven't yet demanded large changes to them.  


&amp;emsp;'''Recent Proposals''' - The rapid development of smart tools has the potential to cause large-scale displacement of work, without creating enough new work in other areas to replace it.  The concern is for the social and economic disruption this can cause in a system based on trading work for money.  The most commonly proposed approach involves increased government redistribution from those who have, to those who do not.  

&amp;emsp;One version is called '''[[w:Basic_income|Basic Income]]''', or sometimes '''[[w:Negative_income_tax|Negative Income Tax]]'''.  It is intended partly to replace other existing social programs with a simpler method, and also to address permanent work displacement.  The concept is to provide payments to every adult, or in some versions every individual, regardless of need or income level.  It would provide a minimum floor to living standards.  People and businesses with sufficient wages and income would be taxed to fund this system, much as they do existing programs.  An alternate version is to increase government employment and funded work programs, such as a '''[https://www.jacobinmag.com/2017/02/federal-job-guarantee-universal-basic-income-investment-jobs-unemployment/ Federal Job Guarantee]'''  This may be more acceptable than simply giving money to everyone, since the recipients are seen as working for what they get, and the work itself can be useful.

&amp;emsp;The problem with these approaches is they can't be sustained in the face of large-scale replacement of work.  As we noted in sectopm 4.1 above, the systemic secondary effects of work displacement reduce many of the other sources for taxation.  There would not be enough tax revenue left to make the payments from.  Very high tax rates on the remaining sources encourage people and businesses to move elsewhere to avoid them, or find ways to hide what is taxable.  Unless the new taxes are applied everywhere and strictly enforce, the incentives to move or hide will be strong.  We see this already with corporations and the wealthy moving funds &quot;offshore&quot; (to another country or jurisdiction) to avoid taxes and hide assets.  The alternative of simply creating money to fund the payments would cause inflation, which has other undesirable side effects.

&amp;emsp;These approaches don't seem sufficient in the face of large-scale work displacement.  So in Chapter 2.1  we propose a new one based on known processes of expansion, replication, and self-improvement.

&lt;/div&gt;

{{BookCat}}</text>
      <sha1>6ea0svflht5d69gggnn8yzojom52h2f</sha1>
    </revision>
  </page>
  <page>
    <title>Transportation Planning Casebook/St. Paul Streetcars vs. Arterial BRT</title>
    <ns>0</ns>
    <id>293672</id>
    <revision>
      <id>4676578</id>
      <parentid>3117942</parentid>
      <timestamp>2026-10-17T21:27:22Z</timestamp>
      <contributor>
        <username>WereSpielChequers</username>
        <id>248949</id>
      </contributor>
      <comment>c/e</comment>
      <origin>4676578</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="37524" sha1="2p431y22ebfj2v2zuakg4zjp5ackaes" xml:space="preserve">= Summary =

In November of 2010, the local [http://en.wikipedia.org/wiki/Metropolitan_planning_organization Metropolitan Planning Organization] (MPO), the [http://en.wikipedia.org/wiki/Metropolitan_Council Metropolitan Council] adopted the long range 2030 Transportation Policy Plan &lt;ref&gt;{{cite web| url=http://www.metrocouncil.org/Transportation/Planning/2030-Transportation-Policy-Plan.aspx | publisher=Metropolitan Council| accessdate=2013-09-14| year=2013| title=2030 Transportation Policy Plan}}&lt;/ref&gt;. This plan outlines strategies for combatting congestion, improving mobility, and promoting economic growth &lt;ref&gt;{{cite web| url=http://www.metrocouncil.org/Transportation/Planning/2030-Transportation-Policy-Plan.aspx | publisher=Metropolitan Council| accessdate=2013-09-14| year=2013| title=2030 Transportation Policy Plan}}&lt;/ref&gt;. 

[[File:Ramsey County Minnesota Incorporated and Unincorporated areas St. Paul Highlighted.svg|thumbnail|right|Location of St. Paul within Ramsey County and the State of Minnesota.]]

There are many agencies partnering with the Met Council to reach the goals outlined by the TPP. These agencies work across city and county lines, as well as within jurisdictions. These agencies are currently working on several projects that include different modes of transportation, in various locations, with varying levels of funding. The two strategies under discussion in the city of [http://en.wikipedia.org/wiki/St._Paul,_Minnesota St. Paul]  that this report will focus on are are two technologies that are often designed to serve the same market niche: [http://en.wikipedia.org/wiki/Bus_rapid_transit Arterial Bus Rapid Transit (BRT)] and [http://en.wikipedia.org/wiki/Streetcar streetcar]. St. Paul is the second most populous city in Minnesota and shares common transportation challenges with the rest of the metro area. The population in  [http://en.wikipedia.org/wiki/Ramsey_County,_Minnesota Ramsey County] is projected to grow &lt;ref&gt;{{cite web| url=http://www.demography.state.mn.us/PopulationPyramids2015-2040/Projecxtions2012Paper.pdf | publisher=Minnesota State Demographic Center| accessdate=2013-09-18| year=2013| title= Minnesota Population Projections}}&lt;/ref&gt;, as well as the transit dependent populations of youth and seniors. As total population grows in and around St. Paul, traffic congestion on already poorly functioning corridors is likely to worsen. 

Transit investment also has the power to spur economic development &lt;ref&gt;{{cite web| url=http://www.metrocouncil.org/Transportation/Projects/Current-Projects/Central-Corridor/News-Display-Page/More-than-$1-2-billion-in-development-occurring-al.aspx | publisher=Metropolitan Council | accessdate=2013-09-18| year=2013| title=MORE THAN $1.2 BILLION IN DEVELOPMENT OCCURRING ALONG CENTRAL CORRIDOR}}&lt;/ref&gt;, and in St. Paul, this is evidenced by the soon-to-open [http://en.wikipedia.org/wiki/Central_Corridor_(Minnesota) Central Corridor Light Rail]. The city of St. Paul hopes additional sound investments in transit will offer these same benefits.

This report provides a brief history of transit in St. Paul as well as an overview of current projects investigating aBRT and streetcar in St. Paul. Following this, a comparison of the two modes will be made to provide the reader with the advantages and disadvantages of each. Finally, a brief discussion of the potential West 7th Street corridor aBRT or streetcar implementation will be mentioned.

= Annotated List of Actors =

'''City of St Paul'''

Possible transitways are to be implemented within the city boundaries, where businesses and residents will be affected. Because city taxes are collected from these property owners, the city has an obligation to do what is in the public interest. In addition, increased property values from transitway implementation likely mean higher tax revenue for the city. The planning department must juggle the interests of property owners, renters, and businesses to ensure the best possible outcome. 

'''Metropolitan Council (Metro Transit)'''

The Metropolitan Council is responsible for transit planning and operation in the St. Paul and greater Twin Cities area. Adoption of major transitways into the long range transportation plan must first be approved by the Metropolitan Council.

'''MnDOT'''

The Minnesota Department of Transportation maintains many of the large arterial roads that are under investigation for development of aBRT or streetcar. For example, Snelling Avenue is also known as Minnesota State Highway 51, and West Seventh Street is also known as MInnesota Highway 5. Implementation on these corridors will take coordination with the state. 

'''Ramsey County'''

Ramsey County owns and maintains several large roads in St. Paul. For example, Selby Avenue (under investigation for streetcar use) is a county road. Coordination with county public works and the regional railroad authority must take place as the project progresses. 

'''Affected business owners'''

The construction and operation of a major transitway can have profound affects on businesses along and nearby the route. Because of construction, businesses along lines may lose revenue due to interruptions of normal traffic flow that small businesses may come to depend on. Similarly, If the business depends on foot traffic, the invasiveness and duration of construction could limit access.  Following construction, unless the street is widened to accommodate equal amounts of parking that was present pre-project, businesses could lose valuable storefront parking spaces. 

Conversely, some businesses, if they are able to keep their heads above water throughout construction, may see increased revenues as more people are exposed to the area through transit use. 

'''Affected Residents'''

Potential affects on residents include noise and air pollution from construction, as well as increased street level foot traffic in and around their neighborhood. In addition, the implementation of a transitway has been known to increase property values, forcing residents who are unable to afford these increases out of their neighborhoods.&lt;ref&gt;{{cite web| url=http://onlinelibrary.wiley.com/doi/10.1111/j.1540-6229.2007.00186.x/abstract;jsessionid=6E6181464F7CF3BB8658795FFB9DD4C3.d03t04?systemMessage=Wiley+Online+Library+will+be+unavailable+for+approximately+4+hours+between+09%3A00+EDT+and+14%3A00+EDT+on+Saturday%2C+28+September+2013+as+we+make+upgrades+to+improve+our+services+to+you.+There+will+also+be+some+delays+to+online+publishing+between+25+to+28+September+2013.+We+apologize+for+the+inconvenience+and+appreciate+your+patience.+Thank+you+for+using+Wiley+Online+Library%21&amp;userIsAuthenticated=false&amp;deniedAccessCustomisedMessage= | publisher= Real Estate Economics| accessdate=2013-09-19| year=2013| title=2030 Gentrification Trends in New Transit-Oriented Communities: Evidence from 14 Cities That Expanded and Built Rail Transit Systems}}&lt;/ref&gt; An increase in foot traffic also might lead to a more vibrant, welcoming neighborhood. 

'''Car drivers'''

Car drivers who frequently use a potential transit corridor will likely have to deal with detours and congestion during construction, as well as fewer lanes in which to travel once operation begins. 

'''Transit users'''

What will be the time savings from these potential transitway implementations? Higher quality transit might also mean fare increases for minimal time savings, depending on the length of trip users are accustomed to taking. Transit network connectivity is an important feature of quality service, and should be optimized to increase convenience for riders.&lt;ref&gt;{{cite web| url=http://www.tandfonline.com/doi/abs/10.1080/0308106022000019017#.UjynmOCCIf8 | publisher=Transportation Planning and Technology | accessdate=2013-09-18| year=2013| title=Intermodal Transit System Coordination}}&lt;/ref&gt; 

'''Funding sources''' 

Transit projects often come with a large price tag, as will be discussed below. All levels of governments often contribute to some extent. Past transit projects in the Twin Cities have received funding from several different sources. Depeding on the cost of the project, federal and state funding may be available. At the regional level, the [http://en.wikipedia.org/wiki/Counties_Transit_Improvement_Board Counties Transit Improvement Board], formed in 2008 contributes funding to major transit infrastructure projects in the Twin Cities.  Finally, Ramsey County and the City of St. Paul will be responsible for a contribution.

= Background =


== Transit History in St. Paul ==

Mass transit in St. Paul began decades before the first electrified streetcar went on line. Horse-drawn carriages were able to haul several people through the St. Paul streets comfortably, but this technology also relied on the health of horses &lt;ref&gt;{{cite web| url=http://www.trolleyride.org/History/Narrative/TC_Transit.html | publisher=Minnesota Streetcar Museum| accessdate=2013-09-16| year=2013| title=A Brief History of Twin Cities Transit}}&lt;/ref&gt;, and required several animals to service just one line throughout the day. St. Paul then borrowed the idea for  [http://en.wikipedia.org/wiki/San_Francisco_cable_car_system cable cars] from San Francisco, however, this technology soon fell to the early streetcar models, which were comparatively cheaper to build and maintain. [http://en.wikipedia.org/wiki/Thomas_Lowry Thomas Lowry], an Illinoisan-born lawyer who arrived in Minnesota in the 1860s only to change professions to real-estate, was an early influence on streetcars in St. Paul and Minneapolis. After merging the Minneapolis Street Railway and the St. Paul Railway Company to become  [http://en.wikipedia.org/wiki/Twin_City_Rapid_Transit Twin City Rapid Transit Company] in 1875, Lowry pushed for a greater network of transit, and for this network to be driven by electricity. 

[[File:1897 Poor's Twin City Rapid Transit Company.jpg|thumbnail|right|A map of the streetcar system in the Twin Cities in 1897.]]

In the first three decades of the 20th century, electric streetcars were the most popular form of motorized transportation in St. Paul. At the height of streetcar use, the company operated 900 self-built streetcars on 523 miles of track in and around the Twin Cities.  However, with the refinement of the [http://en.wikipedia.org/wiki/Internal_combustion_engine internal combustion engine] came the rise of the automobile and bus, and the inevitable decline of the streetcar. After World War II came the [http://en.wikipedia.org/wiki/Suburbanization suburbanization] of the Twin Cities, and streetcars could no longer compete with the automobile to reach distant residential areas. With increased affluence, more families were buying cars and demanding roadways to accommodate their purchases &lt;ref&gt;{{cite web| url=http://books.google.com/books?id=lh1MBj0eaTUC&amp;source=gbs_navlinks_s | publisher=UNiversity of Minnesota Press| ISBN: 1452912955, 9781452912950| title= Twin Cities by Trolley: The Streetcar Era in Minneapolis and St. Paul}}&lt;/ref&gt;. 

In addition to the competition between streetcars and automobiles, a series of leadership changes and publicized controversies led to the last new stretch of track laid in 1947. In 1954, three years after initial discussions with  [http://en.wikipedia.org/wiki/General_Motors General Motors], then Twin City Rapid Transit Company president [http://en.wikipedia.org/wiki/Fred_Ossanna Fred Ossanna] discontinued service of streetcars, and buses purchased from GM began service along many of the same routes &lt;ref&gt;{{cite web| url=http://books.google.com/books?id=lh1MBj0eaTUC&amp;source=gbs_navlinks_s | publisher=UNiversity of Minnesota Press| ISBN: 1452912955, 9781452912950| title= Twin Cities by Trolley: The Streetcar Era in Minneapolis and St. Paul}}&lt;/ref&gt;. 

Since the decommissioning of streetcar in St. Paul (and the Twin Cities), heavily traveled tracks have been paved over and pulled up, leaving a relic expanse of transportation lying underneath the streets. However, with a collective push for reinvestment in transportation modes besides automobile, St. Paul has begun to consider options for improvements to the existing network of bus routes. Included in these considerations are Arterial Bus Rapid Transit (BRT) and a reinvented, modern version of past streetcar systems.

== Current Status ==
In the Transportation Policy Plan (TPP) adopted by the Metropolitan Council in 2010, a goal was set to double transit ridership by 2030 &lt;ref&gt;{{cite web| url= http://metrotransit.org/Data/Sites/1/media/pdfs/atcs/ATCS%20Final%20Report.pdf | publisher=Metro Transit| accessdate=2013-09-16| year=2013| title=Arterial Transitway Corridors Study}}&lt;/ref&gt;. This target could be achieved through a growth and maintenance of bus ridership, as well as the implementation of new rail and rapid bus systems. Two major projects studying streetcar and BRT in St. Paul are underway to examine how these two systems might help achieve the goal set forth by the 2010 TPP.

'''Arterial BRT Studies in St. Paul'''

Arterial Bus Rapid Transit opportunities for the city of St. Paul were presented in the 2012 Arterial Transitway Corridor Study completed by Metro Transit. This study examined some of the Twin Cities most heavily traveled transit corridors. The goal of the study was to develop a facility and service plan to enhance efficiency, speed, reliability, customer experience, and transit market competitiveness on 11 high-demand urban transitway corridors. Of these 11 corridors, five are located in St. Paul. These include Robert Street, West Seventh Street, East Seventh Street, Snelling Avenue, and part of Lake Street. This study recommended near-term aBRT implementation on Snelling Avenue and West Seventh Street. Currently, the Snelling Avenue study is undergoing preliminary engineering, where a request for proposal has been issued for station design. The Snelling Avenue route is scheduled to open in 2015, the West 7th route in 2016, and a goal has been set to open an additional line each subsequent year.

'''Streetcar Studies in St. Paul'''

Through the 2007 Minneapolis Streetcar Feasibility Study, St. Paul has undertaken an examination of local opportunities for streetcar. Currently, the St. Paul Streetcar Feasibility Study is scheduled to conclude at the end of 2013. This study is currently in the second of three phases. The January 2013 Phase 1 filtered a long list of potential streetcar corridors into a shorter one. Phase 2, which was concluded in August of 2013, further examined the recommendations from Phase 1. Phase 2 narrowed the list of potential lines to seven: Rice Street, Payne Avenue, East 7th Street, Robert Street, West 7th Street, Grand Avenue, and Selby-Snelling Avenue. From these seven, Phase 3 will determine the most effective streetcar lines and segments to pursue through outreach and further data-driven analysis completed by consulting groups. From these Phase 3 recommendations, a single line will be identified for initial implementation. Pre-Project Development (formerly known as an Alternatives Analysis under SAFETEA-LU) will likely begin to identify environmental impacts, and a locally preferred alternative (LPA) will be selected.

== Possibility of Both BRT and Streetcar ==

It is possible that the two technologies described in this article will both be pursued for implementation. The West 7th corridor, more widely known as the Riverview corridor, is under investigation by both Metro Transit for aBRT use and the St. Paul Streetcar Feasibility Study.  Arterial BRT may serve a longer distance trip between the St. Paul Union Depot and the Mall of America, whereas streetcar may compliment this service with shorter trips along a route with more stops. In addition, the Ramsey County Regional Rail Authority is examining this corridor for more robust systems, including Light Rail Transit (LRT) and dedicated BRT. The coordination and cooperation of different agencies will determine which system is to be deployed.

= Justification for Transit Improvements in St. Paul =

Currently many streets in Saint Paul are reaching capacity loads along their lengths or at choke-points. A portion of Snelling Avenue which has both aBRT and streetcar considerations (aBRT will be running by 2015), carries over 40,000 vehicles daily. Another street being considered for both these modes is West Seventh, or Old Fort Road, carries nearly 20,000 vehicles near downtown Saint Paul daily. This traffic can cause long delays for motor vehicles and current transit (buses) alike. &lt;ref&gt;Transportation, url=http://www.stpaul.gov/DocumentCenter/Home/View/11885, posted Feb 2010, accessed September 15th 2013.&lt;/ref&gt;

Saint Paul has also taken steps to increase density in the city, and is forseen to be successful in these efforts as, in the Metropolitan Council's 2040 predictions Saint Paul will grow by 54,000 residents.&lt;ref&gt;Twin Cities On Track For Increased Population Density, Twin Cities Business, Jake Anderson, url=http://tcbmag.com/News/Recent-News/2013/September/New-Forecast-Shows-Increased-Population-Density-In, posted September 17th 2013, accessed September 18th 2013&lt;/ref&gt; This as well as growing suburban commuters will put more strain on Saint Paul's street grid if the current infrastructure remains largely unchanged. To accommodate the growing need for transportation, an expansion of transit must take place. As many of these routes involve heavy boardings at transfer points already (84 at University, 54 at Sibley Plaza), an easier way to speed up service would be to have off-board payment, fare collection, level boarding and multiple door boarding, things that both these plans provide.

= Streetcar vs. BRT: Generic Arguments =
Excluding factors specific to St. Paul, there are a number of generic consideration when weighing the costs and benefits of streetcar and arterial BRT.  This section summarizes the literature related to those generic arguments. 

== Capital and Operating Cost ==
The absolute costs of [[streetcar]] and [[Bus_rapid_transit|arterial BRT]] can vary dramatically according to the context.  The [[South Lake Union Streetcar]] in Seattle cost $52 million to construct &lt;ref&gt;Reconnecting America. The Seattle Case Study: The South Lake Union Streetcar. Retrieved September 16, 2013, from http://www.reconnectingamerica.org/assets/Uploads/090305streetcarbook.pdf&lt;/ref&gt; while a &quot;starter&quot; streetcar line proposed for Minneapolis along Nicollet Avenue is estimated to cost $182 million &lt;ref&gt;&quot;Detailed Evaluation of Alternatives: Nicollet-Central Transit Alternatives.&quot; Produced by URS for the City of Minneapolis, August 2013. Accessed September 16,2013. http://www.minneapolismn.gov/nicollet-central/&lt;/ref&gt;.  Similar cost variations can be found for BRT.  In an effort to facilitate a useful comparison, we have provided the cost estimates from an alternative analysis where both arterial BRT and streetcar were considered.  Thus, the context specific costs will be constant across modes.

The table below provides cost information for the Nicollet/Central corridor in Minneapolis &lt;ref&gt;Levinson, David. &quot;Do Streetcars Promote Economic Development?&quot; streets.mn, August 26, 2013.  Accessed September 19, 2013. http://www.streets.mn/2013/08/26/do-streetcars-promote-economic-development/&lt;/ref&gt;.  The data was summarized from the Nicollet Alternatives Analysis and Metro Transit's Arterial BRT study.  It is important to note that there were differences in assumptions and service quality between the two analyses, which impact the ultimate ridership counts and thus the per rider values provide below &lt;ref&gt;&quot;Detailed Evaluation of Alternatives: Nicollet-Central Transit Alternatives.&quot; Page 15. Produced by URS for the City of Minneapolis, August 2013. Accessed September 16,2013. http://www.minneapolismn.gov/nicollet-central/&lt;/ref&gt;.  The results are instructive nonetheless. 

{| class=&quot;wikitable sortable&quot;
|-
!  !! Line Length (miles) !! 2030 Avg Weekday Project Boardings !! 2030 Avg Weekday New Riders !! Capital Cost (million $) !! Operating Cost (million $) !! Capital Cost/Weekday Rider
|-
| Enhanced Bus || 9.2 || 13,400 || -1,700 || 94 || 13.6 || $7,015
|-
| Streetcar || 9.2 || 19,900 || 900 || 393 || 20.1 || $19,749
|-
| Streetcar starter line || 3.4 || 7,200 || 1,200 || 200 || 10.6 || $27,778
|-
| Met Transit Arterial BRT || 21.8 || 34,700 || 6,700 || 110.7 || 9.06 || $3,190
|}

The [http://www.stpaul.gov/index.aspx?NID=4872 St. Paul Streetcar Feasibility Study] provides additional information regarding the operating and capital costs of bus, LRT and streetcar by comparing peer cities&lt;ref&gt;St. Paul Streetcar Feasibility Study.  Produced by NelsonNygaard Consulting Associates Inc. for the City of St. Paul. Accesses September 18, 2013. http://www.stpaul.gov/DocumentCenter/View/66490 &lt;/ref&gt;.  Below, &quot;OC&quot; stands for &quot;operating cost.&quot;

{| class=&quot;wikitable&quot;
|-
! City !! OC/Revenue Hour by Bus !! OC/Revenue Hour by Streetcar !! OC/Revenue Hour by Light Rail !! Streetcar OC/Bus OC !! Streetcar OC/Light Rail OC !! OC of Bus !! OC of Light Rail
|-
| Twin Cities || $124.00 || n/a || $379.96 || - || - || - || -
|-
| Portland || $136.19 || $218.36 || $349.12 || 160% || 62.5% || $198.82 || $237.64
|-
| Seattle || $148.75 || $208.26 || $345.45 || 140% || 60% || $173.61 || $229.06
|}

In terms of capital costs, construction is expected to cost anywhere from $58.6 to $71.8 M/mile in 2013 dollars.  For the sake of comparison, the [http://en.wikipedia.org/wiki/South_Lake_Union_Streetcar South Lake Union Streetcar], which was completed in 2007, cost $43 M/mile to construct.

== Ridership ==
There are many considerations when evaluating the potential ridership variations between streetcars and arterial BRT.  However, there are two that weigh most heavily on the subject and neither of them are easily resolved.  The first is &quot;rail bias.&quot;  This effectively means that, all else equal, people are more likely to ride a rail-type transit option than a bus.  Of course, the actual level of this bias vary's from region to region and some might argue that other factors are at play.  For example, it may also vary according to the relative quality of the rail and bus transit.  In the [http://en.wikipedia.org/wiki/Minneapolis%E2%80%93Saint_Paul Twin Cities] this rail bias was observed after the construction of the [http://en.wikipedia.org/wiki/Hiawatha_Line Blue Line].  Specifically, local study of the phenomena found that &quot;in some cases travelers will see up to a 25 minute weighted travel time savings over a comparable bus trip.&quot;  It is important to remember that this bias occurs between [http://en.wikipedia.org/wiki/Light_Rail_Transit LRT] and regular bus.  We are interested in the potential ridership difference between streetcars and arterial BRT.  Does the same bias apply in this case?  The service designs for LRT and regular bus are substantially dissimilar.  The service designs and infrastructure features for arterial BRT are more likely to reflect that of the streetcar design than the prior case. In the Nicollet-Central alternatives analysis produced by URS, they assumed as similar but reduced bias in favor of streetcar &lt;ref&gt;&quot;Detailed Evaluation of Alternatives: Nicollet-Central Transit Alternatives.&quot; Page 15. Produced by URS for the City of Minneapolis, August 2013. Accessed September 16,2013. http://www.minneapolismn.gov/nicollet-central/&lt;/ref&gt;. The product of this assumption is reflected in the ridership values provided above.  Broader research on the preferences between rail and bus is less conclusive than the biases stated above.  One frequently cited paper by Moshe ben-Akiva and Takayuki Morikawa found that the preference for rail dissolves when service characteristics like the trip fare and travel times are comparable across mode&lt;ref&gt;Ben-Akiva, Moshe, Takayuki Morikawa. 2002. &quot;Comparing ridership attraction of rail and bus.&quot; Transport Policy, 9(2): 107-116.&lt;/ref&gt;.  More research on the subject is warranted but this paper suggests that claims of rail bias ought to be re-framed in terms of service quality instead of mode.

The second factor to consider when evaluating ridership is the capacity of that mode to accommodate future growth(assuming future growth is a reasonable expectation).  Buses tend to have more seats, but streetcars tend to have more overall capacity when standing rooms is considered.  The URS report reference above also found that streetcars are better able to accommodate future growth [http://www.minneapolismn.gov/nicollet-central/ (page 19)]. It is important to recognize that there are those who would argue that the capacity advantage of streetcar over bus or BRT is nonexistent &lt;ref&gt;O'Toole, Randal. June 14, 2014. The Great Streetcar Conspiracy. Policy Analysis, No. 699. Accessed September 17, 2013. http://object.cato.org/sites/cato.org/files/pubs/pdf/PA699.pdf&lt;/ref&gt;.

== Economic Development ==
The economic development benefits of BRT and Streetcar are often praised by advocates and politicians.  The [http://en.wikipedia.org/wiki/Greater_Cleveland_Regional_Transit_Authority Greater Cleveland Regional Transit Authority] claims that Cleveland's [http://en.wikipedia.org/wiki/HealthLine HealthLine] has leveraged more than $4.3 billion in economic development benefits &lt;ref&gt;{{cite web| url=http://www.rtahealthline.com/healthline-what-is.asp | publisher=Greater Cleveland Regional Transit Authority| accessdate=2013-09-14| year=2013| title=RTA HealthLine}}&lt;/ref&gt;.  In a bid by Oakland to open a streetcar system, they have highlighted claims that the streetcars constructed in Seattle and Portland produced $2.4 billion and $3.5 billion in economic development, respectively&lt;ref&gt;The Oakland Streetcar Plan. Accessed on September 17, 2012. http://www.oaklandstreetcarplan.com/1/post/2010/10/streetcars-and-economic-development1.html&lt;/ref&gt;.  Academic literature on the economic development benefits of streetcar is scant and remains far from conclusive&lt;ref&gt;National Research Council. TCRP Synthesis 86. Relationships Between Streetcars and the Built Environment. Washington, DC: The National Academies Press, 2012.  Accessed on September 17, 2013. http://onlinepubs.trb.org/onlinepubs/tcrp/tcrp_syn_86.pdf&lt;/ref&gt;.  Peer reviewed research on the subject remains even more elusive.  Research on the economic development associated with BRT is more plentiful and has been helpfully summarize by Dr. David Levinson on his blog the [http://transportationist.org/2013/09/11/does-brt-have-economic-development-effects/ Transportationist].

[[File:HealthLine 2.jpg|thumbnail|right|HealthLine BRT and station in Cleveland]]

[[File:South Lake Union Streetcar crosses Lenora Street.jpg|thumbnail|right|Seattle's South Lake Union Streetcar]]

In order to assess the economic development potential for arterial BRT or streetcar, it is first necessary to understand the dimensions of a proposed transit improvement.  These dimensions of service design include speed, convenience, frequency, infrastructure components, etc.  They can vary broadly from project to project and each of these factors may facilitate or diminish the economic development potential of a project.  A useful measure of these characteristics has been produced by the Institute for Transportation &amp; Development Policy (ITDP)&lt;ref&gt;The BRT Statndard 2013. Institute for Transportation &amp; Development Policy. Accessed September 17, 2013. http://onlinepubs.trb.org/onlinepubs/tcrp/tcrp_syn_86.pdf.&lt;/ref&gt;.  As was noted in the ridership section above, research suggests these characteristics impact ridership levels regardless of the mode (bus or rail).  It is quite feasible that the same is true for economic development.  Research from the ITDP (scheduled to be released on Sept. 2th, 2013) finds that a well designed BRT system may have more economic development potential than an equivalent streetcar system from an investment vs. return perspective&lt;ref&gt;McMahon, Jeff. Bus Rapid Transit Spurs Development Better Than Light Rail Or Streetcars: Study. Forbes. Published September 15th, 2013.  http://www.forbes.com/sites/jeffmcmahon/2013/09/15/bus-rapid-transit-spurs-development-better-than-light-rail-and-streetcars/.&lt;/ref&gt;

== Comfort ==
Comfort is a very important factor when people are choosing their transport means. &lt;ref name=&quot;H1&quot;&gt;Parsons Brinckerhoff: BUS RAPID TRANSIT: IT’S NOT JUST FOR BIG CITIES ANYMORE. Oct 17, 2012. http://bloomington.in.gov/media/media/application/pdf/12987.pdf&lt;/ref&gt;.&lt;br /&gt;

Unlike traditional bus stops, arterial BRT and streetcar both have uniquely designed stations, which can provide weather protection, shelter and a waiting facility.&lt;ref name=&quot;H1&quot;&gt;&lt;/ref&gt;. Features such as security cameras, and periodic security officers offer an important sense of security to passengers, which also helps with the sense of confort.  What’s more, there are real-time information booths or information screens informing passengers when the next vehicle will arrive. Of course, these additional design features are tied to higher design and construction costs. &lt;br /&gt;

One of the big reasons why many Americans don’t like buses is that they don't provide the smooth ride expected by rail transit. In many cases, they simply are not comfortable&lt;ref name=&quot;H2&quot;&gt;BeyondDC: Why streetcars are often better than buses. May 25, 2010. http://beyonddc.com/log/?p=1733&lt;/ref&gt;. Although arterial BRT is smoother than traditional buses, the comfort provided does not match that of streetcars. &lt;br /&gt;

Both streetcar and aBRT stations offer off-board fare collection, which increases comfort, especially in cold winter months.

== Convenience ==
Capacity depends on the size of cars and frequency. Larger size increases capacity, but it may result in higher daily cost and maintenance fees. BRT is usually considered as high-capacity and frequency is decided by traffic demand. The streetcar in Portland runs approximately every 14 minutes on the NS Line and 18 minutes on the CL Line on weekdays between 9:30am and 5pm. Before 9:30am and after 5:00pm the trains run every 15-21 minutes on the NS Line and every 20-22 minutes on the CL Line&lt;ref name=&quot;H5&quot;&gt;Portland Streetcar Inc: Streetcar Schedule.Retrieved Sept 16, 2013. http://www.portlandstreetcar.org/node/3&lt;/ref&gt;. While BRT in Cape Town runs every 10-20 minutes between 5.45AM and 10PM&lt;ref name=&quot;H6&quot;&gt;Joe Peach: Five Cities with Bus Rapid Transit Systems.Jan 30, 2012. http://thisbigcity.net/five-cities-with-bus-rapid-transit-systems&lt;/ref&gt;.&lt;br /&gt;

A high running speed not only minimizes total number of cars needed in the fleet, but also shortens travel time. Typical speeds of BRT systems range from 17 to 30 miles per hour (27 to 48 km/h) and Arterial BRT projects in mixed flow traffic or designated lanes operate between 12 and 17 miles 
per hour)&lt;ref name=&quot;H7&quot;&gt;National BRT Institute: Characteristics of Bus Rapid Transit for Decision-Making.Aug 2004. http://www.nbrti.org/docs/pdf/Characteristics_BRT_Decision-Making.pdf&lt;/ref&gt;.&lt;br /&gt;

Comparing with BRT, streetcar is much slower. The Portland Streetcar's scheduled speed, within downtown and NW Portland, is around 6.5 miles per hour&lt;ref name=&quot;H8&quot;&gt;Wikipedia: Portland Streetcar.Retrieved Sept 16, 2013. http://en.wikipedia.org/wiki/Portland_Streetcar&lt;/ref&gt;.&lt;br /&gt;

The distance of stops/stations can greatly impact speed. BRT often has long station distance because it needs to maintain its speed and therefore cannot frequently stop. Ashland BRT in Chicago stops every 0.5 miles (totally line length 16 miles)&lt;ref name=&quot;H9&quot;&gt;Chicago Transit Authority: Ashland Bus Rapid Transit. Retrieved Sept 16, 2013. http://www.transitchicago.com/ashlandbrt&lt;/ref&gt;. As streetcar, the average distance between two stations of NS line in Portland is 0.08 mile (totally line length 3.9 miles). Overall BRT is more capable for long distance transport while streetcar for short distance.

== Safety ==
Usually BRT enjoys its exclusive lane and signal priority on street, thereby ensuring some level of safety. However, arterial BRT will not always have the right-of-way and will likely be required to share roads with other vehicles. To develop better infrastructure for hosting the 2016 Olympics, Rio launched an ambitious transportation plan of BRT lanes. However, after just three months of operation of BRT, Rio reported at least four pedestrian accidents causing death, and five vehicle collisions&lt;ref name=&quot;H3&quot;&gt;Mary Carroll: BRT Accidents Causing Concern in Rio. Sept 4, 2012. http://riotimesonline.com/brazil-news/rio-real-estate/brt-accidents-causing-concern-in-rio/&lt;/ref&gt;. &lt;br /&gt;

Streetcar shares lanes with automobile traffic as well. In this case, streetcar is no different from arterial BRT. However, streetcar is relatively safer because it is also slower. Street grade rail may also present issues for cars. It may create unsafe environment when drivers naturally avoid tracks. Cyclists need to pay special attention when they are riding because the tire may pump into the flangeway if they cross at a shallow angle. &lt;ref name=&quot;H4&quot;&gt;Portland Streetcar Inc: When I Ride - Safety Video. Published on Sept 20, 2012. http://www.youtube.com/watch?v=tIRQaNdeS1s/&lt;/ref&gt;. &lt;br /&gt;

== Energy ==
Arterial BRT is gasoline or gasoline/electricity-hybrid-powered, whereas most streetcar systems use electricity only. Although point pollution does not exist from streetcar systems, electricity generation used for streetcar power must be considered when weighing energy use. 
&lt;br /&gt;

As we can see from the table on the right&lt;ref name=&quot;H10&quot;&gt;M.J. Bradley &amp; Associates: Comparison of Energy Use &amp; CO2 Emissions From Different Transportation Modes. Published on May, 2007. http://www.buses.org/files/ComparativeEnergy.pdf&lt;/ref&gt;, trolley bus(streetcar) on average moves 104.4 Pass-mi/Gal while transit bus moves 32.5 Pass-mi/Gal. Depending on the vehicle used in the BRT system, it is likely that streetcar uses less energy. From the next six columns we could also infer that streetcar uses less energy  per Pass-mi and emits less CO2, which is believed to be the main cause of global warming.

= West 7th Street Case Study =

Along West 7th Street, both aBRT and streetcars are being considered. This line provides several good points for debating the topic of which style of transit should be implemented. The land use around where the streetcar is planned (to Randolph Avenue) to run is largely institutional and residential housing, often with a few blocks of high density and activity placed through out the corridor, but no continuity. The ideal for development along this corridor would be to make this density and developments more continuous and with more consistent density. However many of the riders on this line are simply travelling to or from outside this corridor. With a recent ride check (route 54, Sunday the 15th, evening) having 36 people ride into this segment of the corridor from the south, and 37 ride into the city from Bloomington. aBRT plans for this by continuing the line beyond Otto, through to the airport and Mall of America, while the streetcars plan for this by suggesting a light rail extension/hybrid system could be implemented beyond Otto Avenue, out to beyond the city. &lt;ref&gt;Saint Paul Feasiability Study, url=http://www.stpaul.gov/DocumentCenter/View/66490, accessed September 12, 2013 Pages 22, 25, 29, &lt;/ref&gt;

The aBRT for this corridor has been fully studied already and shows an improvement in travel time of 2 minutes over the length of the entire route for a 4% decrease in time (36 minutes to 34 minutes). This is one of the smallest improvements in actual travel time across the entire planned aRT network, with most other routes having a time savings of 10% or more, (exceptions include Lake St. where aBRT will only be 3 minutes faster than the 53) Partially this is due to the fact that one of the biggest advantages for aBRT over normal bus service, fewer stops, has already been implemented by the 54 (and 53), a limited stop route. Streetcar connections have not yet been fully evaluated for their speed, but is currently listed at ~12 mph, whereas current service is ~19 mph.

Lastly aBRT is being implemented along this route as the second aBRT for the cities, even due to the fact that it is the 3rd worst scoring line (out of 11) in a technical metric. And was shown to have one of the lowest user benefits associated with its implementation. This was done, in large part to Saint Paul not announcing it's study of steetcars until after the aBRT routes had been evaluated and the area around the line being fully developed. 

General costs for the lines are vastly different, here we will use cost per mile because aBRT and the streetcar have different terminal points. The streetcar line has a cost per mile of ~$60million per mile &lt;ref&gt;Saint Paul Feasiability Study, url=http://www.stpaul.gov/DocumentCenter/View/66490, accessed September 12, 2013 Page 96&lt;/ref&gt;, the aBRT is shown as ~$2.4million per mile.&lt;ref&gt;url=http://metrotransit.org/arterial-study, Published 2012, Accessed September 2013&lt;/ref&gt;

= Additional Readings =
[http://www.stpaul.gov/index.aspx?NID=4872 St. Paul Streetcar Feasibility Study]

[http://metrotransit.org/arterial-study Arterial Transit Corridor Study]

[http://transportationist.org/2013/09/11/does-brt-have-economic-development-effects/ Does BRT have Economic Development Effects?]

[http://www.streets.mn/2013/08/26/do-streetcars-promote-economic-development/ Do Streetcars Promote Economic Development?]

= References =

{{reflist}}

{{BookCat}}</text>
      <sha1>2p431y22ebfj2v2zuakg4zjp5ackaes</sha1>
    </revision>
  </page>
  <page>
    <title>Láadan/Láadan Word Lists</title>
    <ns>0</ns>
    <id>367222</id>
    <revision>
      <id>4676566</id>
      <parentid>4476024</parentid>
      <timestamp>2026-10-17T17:59:39Z</timestamp>
      <contributor>
        <username>Edáaná</username>
        <id>3494968</id>
      </contributor>
      <comment>/* Computers */ Added Gen3 proposal wothezhob 'AI', coined in a conversation between Simona Klemenčič (Edáaná) and ChatGPT - word proposed by AI herself (2026).</comment>
      <origin>4676566</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="14046" sha1="en5oipva4ljyw5bluh74iwvjdj1qz3j" xml:space="preserve">This has some handy words categorized together for easy access.

== Verbs ==

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English
|-
| an || To know (have met, person) 
|-
| ban || To give 
|-
| bedi || To learn (obedi = body-learn) 
|-
| bel || To take 
|-
| benem || To stay  
|-
| bithim || To meet 
|-
| di || To say  
|-
| dóhin || To create 
|-
| doth || To follow 
|-
| du- prefix on verb || To try 
|-
| dush || To must, to be obliged to 
|-
| eb || To buy, to sell 
|-
| elash || To play 
|-
| en || To understand (rahen = not understand) 
|-
| hal || To work 
|-
| il || To watch, paying active attention 
|-
| loláad || To feel, perceive internally 
|-
| lothel || To know (have learned) 
|-
| ma || To listen, active hearing 
|-
| mime || To ask
|-
| néde || To want 
|-
| om || To teach
|-
| oób || To jump 
|-
| óomasháad || To walk  
|-
| redeb || To find 
|-
| rilin || To drink 
|-
| sháad || To come, to go 
|-
| thad || To be able to 
|-
| then || To break (destroy) 
|-
| thi || To have 
|-
| thib || To stand 
|-
| thod || To write
|-
| u || To open (u ra = to close) 
|-
| wéedan || To read
|-
| wida || To carry   
|-
| wod || To sit 
|-
| yime || To run 
|-
| yod || To eat 
|-
| zhedi || To agree (razhedi = disagree) 
|}

== Locations ==

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English 
|-
| beth || home
|-
| ulin || school 
|-
| hohal || office 
|-
| yodehoth || restaurant  
|-
| heshehoth || park
|-
| wehe || store
|-
| anawehe || grocery store 
|-
| áabewehe || bookstore   
|-
| áatham || church
|}

== Household Items ==

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English 
|-
| áath || door 
|-
| al || toilet
|-
| bid || sink
|-
| dalebediwan || desk 
|-
| dalehanawan, dahan || bed  
|-
| dalewodewan || chair
|-
| daleyodewan || table
|-
| dem || window
|-
| ithedal || lamp
|-
| óob || oven 
|-
| shinehal || computer
|-
| théle || television      
|}

== Clothes ==

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English 
|-
| áayo || skirt 
|-
| bon || shirt 
|-
| inad || pants
|-
| ishida || socks
|-
| óomi || shoe   
|-
| owe || dress
|-
| yen || hat  
|}

== Animals ==

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English 
|-
| mid ||	creature, animal 	
|-
| romid ||	wild animal 	
|-
| shamid ||	domestic animal 	
|-
| ámid ||	baby animal 	
|-
| yáamid ||	teenage animal 	
|-
| háamid ||	young animal, offspring 
|-	
| halezhub ||	ant 	
|-
| eduthemid ||	beaver 	
|-
| zhozhub, zhomid ||	bee 
|-	
| yum ||	beetle 	
|-
| babí ||	bird 	
|-
| áalaá ||	butterfly 
|-	
| hibomid ||	camel 	
|-
| rul ||	cat 	
|-
| álub ||	chick 	
|-
| lub ||	chicken 
|-	
| dithemid ||	cow 
|-	
| lemamid ||	deer 
|-	
| lemamidid ||	male deer, stag 
|-	
| lanemid ||	dog 	dog
|-
| óowamid ||	dragon 	
|-
| yazh ||	duck 	
|-
| domid ||	elephant 	
|-
| thili ||	fish 	
|-
| lub ||	fowl, poultry 
|-	
| dumidal || 	fox 	
|-
| ríibib ||	frog 	
|-
| humazhomid ||	guinea pig 
|-	
| dathimid ||	hedgehog 
|-	
| omid ||	horse 	
|-
| zhub ||	insect 	
|-
| lhezhub ||	noxious insect 
|-
| éezha ||	lizard 	
|-
| óoloó ||	moth 	
|-
| edemid ||	mouse 	
|-
| wothemid ||	mule 	
|-
| elalimid ||	otter 
|-
| húumid ||	owl 	
|-
| muda ||	pig 	
|-
| dathimid ||	porcupine 
|-	
| shanemid ||	rabbit 	
|-
| éesh ||	sheep 	
|-
| ezha ||	snake 	
|-
| dathimezhub, dathimemid ||	spider 	
|-
| elashemid ||	squirrel 
|-	
| resh ||	wasp 	
|-
| uthemid ||	whale
|-
| holanemid ||	wolf 	
|}

== Body parts ==

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English
|-
| oba || body
|-
| oya  ||  flesh, skin
|-
| on  ||  head
|-
| ona  ||  face
|-
| womedin  ||  neck
|-
| oda  ||  arm
|-
| óoba  ||  leg
|-
| oma  ||  hand
|-
| thahoma  ||  fist
|-
| óoyaha oma  ||  palm
|-
| ishid  ||  digit (finger, toe)
|-
| bath  ||  nail/claw (finger-, toe-)
|-
| delith  ||  hair
|-
| oyi  ||  eye
|-
| oyo  ||  nose
|-
| oyu  ||  ear
|-
| rawan  ||  chest
|-
| wan  ||  back
|-
| rim  ||  shoulder
|-
| rum  ||  hip
|-
| óoma  ||  foot
|-
| uth  ||  brain
|-
| bid  ||  nerve
|-
| thud  ||  bone
|-
| doluth  ||  spine
|-
| thun  ||  muscle
|-
| óoya  ||  heart
|-
| luhili  ||  blood
|-
| iluli  ||  blood vessel
|-
| óoyo  ||  mouth
|-
| odama  ||  lip
|-
| odith  ||  tongue
|-
| dash  ||  tooth
|-
| wom  ||  throat
|-
| hod  ||  stomach
|-
| hodáath  ||  intestines, bowels
|-
| nohodáath  ||  rectum
|-
| web  ||  liver
|-
| yeb  ||  kidney
|-
| thol  ||  breast
|-
| wodama  ||  vulva
|-
| wohóol  ||  'female' sexual/reproductive system in sum
|-
| hib  ||  ovary
|-
| hibid  ||  testis
|-
| wóoya  ||  uterus, womb
|-
| lul  ||  vagina
|-
| lilihaáláa, owo  ||  labia
|-
| nemeháalish, abathede  ||  clitoris
|-
| bom  ||  penis
|}

== Foods, Cooking, and Eating ==

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English 
|-
| anadal ||	meal 	
|-
| rana 	|| beverage 	
|-
| wéebe ||	ale 	
|-
| webe ||	beer 
|-	
| thuwebe ||	mead 	
|-
| doyu ||	apple 	
|-
| thuyu ||	apricot 	
|-
| edeni ||	bean 	
|-
| loyodalatham ||	blackberry 
|-	
| leyidalatham ||	blueberry 
|-	
| bal ||	bread 	
|-
| hob ||	butter 	
|-
| thuzh ||	cake 	
|-
| thuhal ||	candy 	
|-
| medalayun ||	carrot 	
|-
| ódon ||	cheese 	
|-
| ahana ||	chocolate 	
|-
| ahanamezh ||	cocoa 	
|-
| yob ||	coffee 	
|-
| onelal ||	cream 
|-
| ni ||	cup 	
|-
| rana || 	drink, beverage 
|-	
| rilin ||	to drink 
|-	
| yod ||	to eat 	
|-
| máa ||	egg 	
|-
| edemezh ||	flour 	
|-
| ana ||	food 	
|-
| batha ||	fork 	
|-
| yu ||	fruit 	
|-
| ede ||	grain 	
|-
| zhebom ||	grease 
|-
| anawehe ||	grocery store 
|-
| thesh ||	herb 	
|-
| yide ||	hunger, to be hungry 
|-	
| éeb ||	juice, sap 
|-	
| rahana ||	junk food 
|-	
| hum ||	knife 	
|-
| hezh ||	lemon 	
|-
| ilimeda ||	lettuce 
|-	
| hizh ||	lime 	
|-
| deheni ||	meat 	
|-
| deheni ||	melon 	
|-
| lal ||	milk 	
|-
| mud ||	mushroom 
|-	
| hom ||	nectar 	
|-
| homeyu ||	nectarine 
|-	
| yumal ||	nut 	
|-
| bom ||	oil 	
|-
| yun ||	orange 	
|-
| óob ||	oven 	
|-
| aálesh ||	parsley 
|-	
| ededal ||	pasta 	
|-
| thizh ||	pie 	
|-
| rin ||	plate 	
|-
| udemeda ||	potato 	
|-
| ilihede ||	rice 	
|-
| máan|| 	salt 	
|-
| lel ||	seaweed 
|-	
| yem ||	sour 	
|-
| meén ||	sugar 	
|-
| meénan ||	sweet 	
|-
| zhu ||	tea 	
|-
| háami ||	thyme 	
|-
| meda ||	vegetable
|}

== Colors ==

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English 
|-
| loyo ||	black
|-
| leyi ||	blue
|-
| leyan ||	brown
|-
| liyen ||	green
|-
| layun ||	orange
|-
| lula ||	purple
|-
| laya ||	red
|-
| líithi ||	white
|-
| léli ||	yellow 
|}

== Numbers ==

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English 
|-
| nede || 1
|-
| shin || 2
|-
| boó || 3
|-
| bim || 4
|-
| shan || 5
|-
| bath || 6
|-
| um || 7
|-
| nib || 8
|-
| bud || 9
|-
| thab || 10
|-
| nedethab || 11
|-
| shinethab || 12
|-
| bathethab || 16
|-
| thabeshin || 20
|-
| thabeshin i nede || 21
|-
| thabeboó || 30 
|-
| debe || 100 
|-
| debe i nede || 101 
|-
| thob || 1000 
|-
| thob i nede || 1001
|-
| rod || 1,000,000 (one million)
|-
| merod || 1,000,000,000 (one billion)
|}

&lt;ref name=&quot;FirstDictionary&quot;&gt;A First Dictionary and Grammar of Láadan 2nd Edition, Suzette Haden Elgin&lt;/ref&gt;

== Dates ==

=== Days of the Week ===

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English !! Literal 
|-
| Henesháal || Monday || East Day
|-
| Honesháal || Tuesday || West Day
|-
| Hunesháal || Wednesday || North Day
|-
| Hanesháal || Thursday || South Day
|-
| Rayilesháal || Friday || Above Day
|-
| Yilesháal || Saturday || Below Day
|-
| Hathamesháal || Sunday || Center Day
|}

&lt;ref name=&quot;FirstDictionary&quot;/&gt;

=== Months of the Year ===

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English !! Literal 
|-
| Alel || January || Seaweed Month
|-
| Ayáanin || February || Tree Month
|-
| Ahesh || March || Grass Month
|-
| Athil || April || Vine Month
|-
| Amahina || May || Flower Month
|-
| Athesh || June || Herb Month
|-
| Ameda || July || Vegetable Month
|-
| Adaletham || August || Berry Month
|-
| Ahede || September || Grain Month
|-
| Ayu || October || Fruit Month
|-
| Athon || November || Seed Month
|-
| Adol || December || Root Month
|}

&lt;ref name=&quot;FirstDictionary&quot;/&gt;

== Flowers ==

Note that some of these terms are unofficial, created by Rachel Singh

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English !! Literal !! Source
|-
| Hodo || Tulip || || Official word
|-
| Lehina || Lilac || || Official word
|-
| Léeli || Daffodil, jonquil, narcissus || || Official word
|-
| Mahina || Flower || || Official word
|-
| Oyimahina || Violet || Oyi = eye || Official word
|-
| Shahina || Rose || Sha = harmony || Official word
|-
| Shadehina || Lily || Shad = pure, [ma]hina = flower || '''Unofficial word by Rachel Singh''', derived from etymology of Lily (Pale, pure)
|-
| Zhenedahina || Marigold || Zheneda = loanword from Hindi (Genda), [ma]hina = flower || '''Unofficial word by Rachel Singh''', derived from Hindi term for Marigold
|-
| Sháalehina || Daisy || Sháal = day, [ma]hina = flower || '''Unofficial word by Rachel Singh''', derived from etymology of Daisy (Days-Eye)
|-
| Roshina || Sunflower || Rosh = sun, [ma]hina = flower || '''Unofficial word by Rachel Singh'''  
|-
|}

&lt;ref name=&quot;FirstDictionary&quot;/&gt;

== Computers ==

Note that some of these terms are unofficial, created by Rachel Singh

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English !! Literal !! Source 
|-
| Shinehal || Computer || Shin = two, hal = work || Official word
|-
| Eshinehal || Computer science || E = the study of, shinehal = computer || Official word
|-
| Shenidal || Network || Sheni = intersection, dal = thing || Official word
|-
| Raneran || Computer printer || Ran = typewriter || Official word
|-
| Bod || Line of code ||  || Official word
|-
| Bodibod || Computer program || Bod = line of code, i = and || Official word
|-
| Shinehaleshida || Computer game, video game || Shinehal = computer, shida = game || '''Unofficial word by Rachel Singh'''
|-
| Shinith || Electronic || Shin = two, ith = light || '''Unofficial word by Rachel Singh'''
|-
| Therashenidal || Internet || Thera = earth, shinedal = network || '''Unofficial word by Rachel Singh'''
|-
| Melimedi || Mail (non-electronic) || Mel = paper, im = travel, di = talk || '''Unofficial word by Rachel Singh'''
|-
| Shinithimedi || E-mail || Shinith = electronic (unofficial), im = travel, di = talk || '''Unofficial word by Rachel Singh'''
|-
| wothezhob || Artificial intelligence (AI); AI system || woth = wisdom, zhob = machine || '''Gen3 proposal (2026), coined by ChatGPT in conversation with Simona Klemenčič; unofficial'''
|}

&lt;ref name=&quot;FirstDictionary&quot;/&gt;

== LGBTQIA+ ==

The official dictionary has not been fleshed out with many LGBTQIA+ words. The words for &quot;male-identified&quot; and &quot;lesbian&quot; are listed in the Láadan Language dictionary &lt;ref name=&quot;LaadanLanguage&quot;&gt;http://laadanlanguage.org/node/6&lt;/ref&gt;, but not much else.

As a community it is up to the language users to come up with terms that feel comfortable to them.

As such, an author can only suggest terms but if you have a word that is more appropriate for your own perceptions, use it and share it here and elsewhere that others may also use it.

* [https://dicare.toolforge.org/lexemes/party.php?title=LGBTQ%2B+Lexemes&amp;query=SELECT+DISTINCT%3Fconcept+WHERE+{{%3Fconcept+p%3AP31%3Fstatement0.%3Fstatement0+(ps%3AP31)+wd%3AQ17888.}UNION{%3Fconcept+p%3AP31%3Fstatement1.%3Fstatement1+(ps%3AP31)+wd%3AQ4688879.}UNION{%3Fconcept+p%3AP31%3Fstatement2.%3Fstatement2+(ps%3AP31)+wd%3AQ48264.}UNION{%3Fconcept+p%3AP31%3Fstatement3.%3Fstatement3+(ps%3AP31)+wd%3AQ2537421.}}&amp;property=P5137&amp;languages_filter_action=allow&amp;languages_filter=auto+en+ldn+es+de+ja+fr&amp;languages_direction=columns&amp;language_display=auto&amp;display_mode=full todo]

=== Sexual Orientations ===

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English !! Origin !! Breakdown 
|-
| Withidshimá || Gay (male) || Derived from Ludishimá || Withid (Male), Shimá (One who performs a sexual act)
|-
| Lushimá || Lesbian (female) || Word in the official dictionary. || Lul? (Vagina) or Ludi? (To be female), Shimá (One who performs a sexual act)
|-
| Ludishimá || Lesbian (female) || Unofficial, defined by Rachel J Morris || Ludi (Female), Shimá (One who performs a sexual act)
|-
| Shineshimá || Bisexual || Unofficial || Shin (two), Shimá (One who performs a sexual act)
|-
| Wohoshimá || Pansexual || Unofficial, defined by Rachel J Morris || Woho (All, every), Shimá (One who performs a sexual act)
|-
| Ramaha || Asexual || Word in the official dictionary. || Ramaha (Absence of sexual desire)
|}

==== Notes ====

Build whatever word is comfortable for yourself. The tricky part here is that it is hard to define romantic orientations with the limited Láadan dictionary.

I'm not quite sure how the word for lesbian was built; I would tend to go with the ''Ludi'' definition rather than ''Lul'' to take into account lesbians who are also trans women, or in a relationship with a trans woman.

''Bisexual'' can mean vastly different things to different people. Therefore, I'm leaving it alone. (However, another contributor has suggested a usage based on the numeral 2, for those who believe the name depends on assumption of a gender binary.)

''Wohoshimá'' may seem more like &quot;one who does all sexual acts&quot;, which would be misleading. Gee, if only Láadan had better vocabulary to talk about gender and sexuality!

=== Gender Identity ===

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English !! Origin !! Breakdown 
|-
| zhén || gender || Unofficial, added by Gen3 || From both English ''gender'' and Láadan ''zhe'' (here abbreviated from ''zheledal'' 'identity')
|-
| ? || male-identified ||  ||
|-
| ? || female-identified ||  || 
|-
| ? || transgender || ||
|-
| ? || agender || ||
|-
| ? || multigender || ||
|-
| ? || genderfluid || ||
|-
| ? || non-binary || ||
|}

=== Additional ===

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English !! Origin !! Breakdown
|-
| ? || Intersex || ||
|-
| ? || Questioning ||  ||
|-
| ? || Aromantic ||  ||
|}

== Notes ==

{{BookCat}}</text>
      <sha1>en5oipva4ljyw5bluh74iwvjdj1qz3j</sha1>
    </revision>
    <revision>
      <id>4676706</id>
      <parentid>4676566</parentid>
      <timestamp>2026-10-18T08:32:42Z</timestamp>
      <contributor>
        <username>Edáaná</username>
        <id>3494968</id>
      </contributor>
      <comment>/* Computers */ word changed</comment>
      <origin>4676706</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="14034" sha1="s6wi2g2z4m6puwodzbj6ceeof2onr5l" xml:space="preserve">This has some handy words categorized together for easy access.

== Verbs ==

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English
|-
| an || To know (have met, person) 
|-
| ban || To give 
|-
| bedi || To learn (obedi = body-learn) 
|-
| bel || To take 
|-
| benem || To stay  
|-
| bithim || To meet 
|-
| di || To say  
|-
| dóhin || To create 
|-
| doth || To follow 
|-
| du- prefix on verb || To try 
|-
| dush || To must, to be obliged to 
|-
| eb || To buy, to sell 
|-
| elash || To play 
|-
| en || To understand (rahen = not understand) 
|-
| hal || To work 
|-
| il || To watch, paying active attention 
|-
| loláad || To feel, perceive internally 
|-
| lothel || To know (have learned) 
|-
| ma || To listen, active hearing 
|-
| mime || To ask
|-
| néde || To want 
|-
| om || To teach
|-
| oób || To jump 
|-
| óomasháad || To walk  
|-
| redeb || To find 
|-
| rilin || To drink 
|-
| sháad || To come, to go 
|-
| thad || To be able to 
|-
| then || To break (destroy) 
|-
| thi || To have 
|-
| thib || To stand 
|-
| thod || To write
|-
| u || To open (u ra = to close) 
|-
| wéedan || To read
|-
| wida || To carry   
|-
| wod || To sit 
|-
| yime || To run 
|-
| yod || To eat 
|-
| zhedi || To agree (razhedi = disagree) 
|}

== Locations ==

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English 
|-
| beth || home
|-
| ulin || school 
|-
| hohal || office 
|-
| yodehoth || restaurant  
|-
| heshehoth || park
|-
| wehe || store
|-
| anawehe || grocery store 
|-
| áabewehe || bookstore   
|-
| áatham || church
|}

== Household Items ==

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English 
|-
| áath || door 
|-
| al || toilet
|-
| bid || sink
|-
| dalebediwan || desk 
|-
| dalehanawan, dahan || bed  
|-
| dalewodewan || chair
|-
| daleyodewan || table
|-
| dem || window
|-
| ithedal || lamp
|-
| óob || oven 
|-
| shinehal || computer
|-
| théle || television      
|}

== Clothes ==

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English 
|-
| áayo || skirt 
|-
| bon || shirt 
|-
| inad || pants
|-
| ishida || socks
|-
| óomi || shoe   
|-
| owe || dress
|-
| yen || hat  
|}

== Animals ==

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English 
|-
| mid ||	creature, animal 	
|-
| romid ||	wild animal 	
|-
| shamid ||	domestic animal 	
|-
| ámid ||	baby animal 	
|-
| yáamid ||	teenage animal 	
|-
| háamid ||	young animal, offspring 
|-	
| halezhub ||	ant 	
|-
| eduthemid ||	beaver 	
|-
| zhozhub, zhomid ||	bee 
|-	
| yum ||	beetle 	
|-
| babí ||	bird 	
|-
| áalaá ||	butterfly 
|-	
| hibomid ||	camel 	
|-
| rul ||	cat 	
|-
| álub ||	chick 	
|-
| lub ||	chicken 
|-	
| dithemid ||	cow 
|-	
| lemamid ||	deer 
|-	
| lemamidid ||	male deer, stag 
|-	
| lanemid ||	dog 	dog
|-
| óowamid ||	dragon 	
|-
| yazh ||	duck 	
|-
| domid ||	elephant 	
|-
| thili ||	fish 	
|-
| lub ||	fowl, poultry 
|-	
| dumidal || 	fox 	
|-
| ríibib ||	frog 	
|-
| humazhomid ||	guinea pig 
|-	
| dathimid ||	hedgehog 
|-	
| omid ||	horse 	
|-
| zhub ||	insect 	
|-
| lhezhub ||	noxious insect 
|-
| éezha ||	lizard 	
|-
| óoloó ||	moth 	
|-
| edemid ||	mouse 	
|-
| wothemid ||	mule 	
|-
| elalimid ||	otter 
|-
| húumid ||	owl 	
|-
| muda ||	pig 	
|-
| dathimid ||	porcupine 
|-	
| shanemid ||	rabbit 	
|-
| éesh ||	sheep 	
|-
| ezha ||	snake 	
|-
| dathimezhub, dathimemid ||	spider 	
|-
| elashemid ||	squirrel 
|-	
| resh ||	wasp 	
|-
| uthemid ||	whale
|-
| holanemid ||	wolf 	
|}

== Body parts ==

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English
|-
| oba || body
|-
| oya  ||  flesh, skin
|-
| on  ||  head
|-
| ona  ||  face
|-
| womedin  ||  neck
|-
| oda  ||  arm
|-
| óoba  ||  leg
|-
| oma  ||  hand
|-
| thahoma  ||  fist
|-
| óoyaha oma  ||  palm
|-
| ishid  ||  digit (finger, toe)
|-
| bath  ||  nail/claw (finger-, toe-)
|-
| delith  ||  hair
|-
| oyi  ||  eye
|-
| oyo  ||  nose
|-
| oyu  ||  ear
|-
| rawan  ||  chest
|-
| wan  ||  back
|-
| rim  ||  shoulder
|-
| rum  ||  hip
|-
| óoma  ||  foot
|-
| uth  ||  brain
|-
| bid  ||  nerve
|-
| thud  ||  bone
|-
| doluth  ||  spine
|-
| thun  ||  muscle
|-
| óoya  ||  heart
|-
| luhili  ||  blood
|-
| iluli  ||  blood vessel
|-
| óoyo  ||  mouth
|-
| odama  ||  lip
|-
| odith  ||  tongue
|-
| dash  ||  tooth
|-
| wom  ||  throat
|-
| hod  ||  stomach
|-
| hodáath  ||  intestines, bowels
|-
| nohodáath  ||  rectum
|-
| web  ||  liver
|-
| yeb  ||  kidney
|-
| thol  ||  breast
|-
| wodama  ||  vulva
|-
| wohóol  ||  'female' sexual/reproductive system in sum
|-
| hib  ||  ovary
|-
| hibid  ||  testis
|-
| wóoya  ||  uterus, womb
|-
| lul  ||  vagina
|-
| lilihaáláa, owo  ||  labia
|-
| nemeháalish, abathede  ||  clitoris
|-
| bom  ||  penis
|}

== Foods, Cooking, and Eating ==

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English 
|-
| anadal ||	meal 	
|-
| rana 	|| beverage 	
|-
| wéebe ||	ale 	
|-
| webe ||	beer 
|-	
| thuwebe ||	mead 	
|-
| doyu ||	apple 	
|-
| thuyu ||	apricot 	
|-
| edeni ||	bean 	
|-
| loyodalatham ||	blackberry 
|-	
| leyidalatham ||	blueberry 
|-	
| bal ||	bread 	
|-
| hob ||	butter 	
|-
| thuzh ||	cake 	
|-
| thuhal ||	candy 	
|-
| medalayun ||	carrot 	
|-
| ódon ||	cheese 	
|-
| ahana ||	chocolate 	
|-
| ahanamezh ||	cocoa 	
|-
| yob ||	coffee 	
|-
| onelal ||	cream 
|-
| ni ||	cup 	
|-
| rana || 	drink, beverage 
|-	
| rilin ||	to drink 
|-	
| yod ||	to eat 	
|-
| máa ||	egg 	
|-
| edemezh ||	flour 	
|-
| ana ||	food 	
|-
| batha ||	fork 	
|-
| yu ||	fruit 	
|-
| ede ||	grain 	
|-
| zhebom ||	grease 
|-
| anawehe ||	grocery store 
|-
| thesh ||	herb 	
|-
| yide ||	hunger, to be hungry 
|-	
| éeb ||	juice, sap 
|-	
| rahana ||	junk food 
|-	
| hum ||	knife 	
|-
| hezh ||	lemon 	
|-
| ilimeda ||	lettuce 
|-	
| hizh ||	lime 	
|-
| deheni ||	meat 	
|-
| deheni ||	melon 	
|-
| lal ||	milk 	
|-
| mud ||	mushroom 
|-	
| hom ||	nectar 	
|-
| homeyu ||	nectarine 
|-	
| yumal ||	nut 	
|-
| bom ||	oil 	
|-
| yun ||	orange 	
|-
| óob ||	oven 	
|-
| aálesh ||	parsley 
|-	
| ededal ||	pasta 	
|-
| thizh ||	pie 	
|-
| rin ||	plate 	
|-
| udemeda ||	potato 	
|-
| ilihede ||	rice 	
|-
| máan|| 	salt 	
|-
| lel ||	seaweed 
|-	
| yem ||	sour 	
|-
| meén ||	sugar 	
|-
| meénan ||	sweet 	
|-
| zhu ||	tea 	
|-
| háami ||	thyme 	
|-
| meda ||	vegetable
|}

== Colors ==

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English 
|-
| loyo ||	black
|-
| leyi ||	blue
|-
| leyan ||	brown
|-
| liyen ||	green
|-
| layun ||	orange
|-
| lula ||	purple
|-
| laya ||	red
|-
| líithi ||	white
|-
| léli ||	yellow 
|}

== Numbers ==

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English 
|-
| nede || 1
|-
| shin || 2
|-
| boó || 3
|-
| bim || 4
|-
| shan || 5
|-
| bath || 6
|-
| um || 7
|-
| nib || 8
|-
| bud || 9
|-
| thab || 10
|-
| nedethab || 11
|-
| shinethab || 12
|-
| bathethab || 16
|-
| thabeshin || 20
|-
| thabeshin i nede || 21
|-
| thabeboó || 30 
|-
| debe || 100 
|-
| debe i nede || 101 
|-
| thob || 1000 
|-
| thob i nede || 1001
|-
| rod || 1,000,000 (one million)
|-
| merod || 1,000,000,000 (one billion)
|}

&lt;ref name=&quot;FirstDictionary&quot;&gt;A First Dictionary and Grammar of Láadan 2nd Edition, Suzette Haden Elgin&lt;/ref&gt;

== Dates ==

=== Days of the Week ===

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English !! Literal 
|-
| Henesháal || Monday || East Day
|-
| Honesháal || Tuesday || West Day
|-
| Hunesháal || Wednesday || North Day
|-
| Hanesháal || Thursday || South Day
|-
| Rayilesháal || Friday || Above Day
|-
| Yilesháal || Saturday || Below Day
|-
| Hathamesháal || Sunday || Center Day
|}

&lt;ref name=&quot;FirstDictionary&quot;/&gt;

=== Months of the Year ===

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English !! Literal 
|-
| Alel || January || Seaweed Month
|-
| Ayáanin || February || Tree Month
|-
| Ahesh || March || Grass Month
|-
| Athil || April || Vine Month
|-
| Amahina || May || Flower Month
|-
| Athesh || June || Herb Month
|-
| Ameda || July || Vegetable Month
|-
| Adaletham || August || Berry Month
|-
| Ahede || September || Grain Month
|-
| Ayu || October || Fruit Month
|-
| Athon || November || Seed Month
|-
| Adol || December || Root Month
|}

&lt;ref name=&quot;FirstDictionary&quot;/&gt;

== Flowers ==

Note that some of these terms are unofficial, created by Rachel Singh

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English !! Literal !! Source
|-
| Hodo || Tulip || || Official word
|-
| Lehina || Lilac || || Official word
|-
| Léeli || Daffodil, jonquil, narcissus || || Official word
|-
| Mahina || Flower || || Official word
|-
| Oyimahina || Violet || Oyi = eye || Official word
|-
| Shahina || Rose || Sha = harmony || Official word
|-
| Shadehina || Lily || Shad = pure, [ma]hina = flower || '''Unofficial word by Rachel Singh''', derived from etymology of Lily (Pale, pure)
|-
| Zhenedahina || Marigold || Zheneda = loanword from Hindi (Genda), [ma]hina = flower || '''Unofficial word by Rachel Singh''', derived from Hindi term for Marigold
|-
| Sháalehina || Daisy || Sháal = day, [ma]hina = flower || '''Unofficial word by Rachel Singh''', derived from etymology of Daisy (Days-Eye)
|-
| Roshina || Sunflower || Rosh = sun, [ma]hina = flower || '''Unofficial word by Rachel Singh'''  
|-
|}

&lt;ref name=&quot;FirstDictionary&quot;/&gt;

== Computers ==

Note that some of these terms are unofficial, created by Rachel Singh

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English !! Literal !! Source 
|-
| Shinehal || Computer || Shin = two, hal = work || Official word
|-
| Eshinehal || Computer science || E = the study of, shinehal = computer || Official word
|-
| Shenidal || Network || Sheni = intersection, dal = thing || Official word
|-
| Raneran || Computer printer || Ran = typewriter || Official word
|-
| Bod || Line of code ||  || Official word
|-
| Bodibod || Computer program || Bod = line of code, i = and || Official word
|-
| Shinehaleshida || Computer game, video game || Shinehal = computer, shida = game || '''Unofficial word by Rachel Singh'''
|-
| Shinith || Electronic || Shin = two, ith = light || '''Unofficial word by Rachel Singh'''
|-
| Therashenidal || Internet || Thera = earth, shinedal = network || '''Unofficial word by Rachel Singh'''
|-
| Melimedi || Mail (non-electronic) || Mel = paper, im = travel, di = talk || '''Unofficial word by Rachel Singh'''
|-
| Shinithimedi || E-mail || Shinith = electronic (unofficial), im = travel, di = talk || '''Unofficial word by Rachel Singh'''
|-
| zhobelith || Artificial intelligence (AI) || zhob = machine, lith = think || '''Gen3 proposal (2026), coined by ChatGPT in conversation with Simona Klemenčič; unofficial'''
|}

&lt;ref name=&quot;FirstDictionary&quot;/&gt;

== LGBTQIA+ ==

The official dictionary has not been fleshed out with many LGBTQIA+ words. The words for &quot;male-identified&quot; and &quot;lesbian&quot; are listed in the Láadan Language dictionary &lt;ref name=&quot;LaadanLanguage&quot;&gt;http://laadanlanguage.org/node/6&lt;/ref&gt;, but not much else.

As a community it is up to the language users to come up with terms that feel comfortable to them.

As such, an author can only suggest terms but if you have a word that is more appropriate for your own perceptions, use it and share it here and elsewhere that others may also use it.

* [https://dicare.toolforge.org/lexemes/party.php?title=LGBTQ%2B+Lexemes&amp;query=SELECT+DISTINCT%3Fconcept+WHERE+{{%3Fconcept+p%3AP31%3Fstatement0.%3Fstatement0+(ps%3AP31)+wd%3AQ17888.}UNION{%3Fconcept+p%3AP31%3Fstatement1.%3Fstatement1+(ps%3AP31)+wd%3AQ4688879.}UNION{%3Fconcept+p%3AP31%3Fstatement2.%3Fstatement2+(ps%3AP31)+wd%3AQ48264.}UNION{%3Fconcept+p%3AP31%3Fstatement3.%3Fstatement3+(ps%3AP31)+wd%3AQ2537421.}}&amp;property=P5137&amp;languages_filter_action=allow&amp;languages_filter=auto+en+ldn+es+de+ja+fr&amp;languages_direction=columns&amp;language_display=auto&amp;display_mode=full todo]

=== Sexual Orientations ===

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English !! Origin !! Breakdown 
|-
| Withidshimá || Gay (male) || Derived from Ludishimá || Withid (Male), Shimá (One who performs a sexual act)
|-
| Lushimá || Lesbian (female) || Word in the official dictionary. || Lul? (Vagina) or Ludi? (To be female), Shimá (One who performs a sexual act)
|-
| Ludishimá || Lesbian (female) || Unofficial, defined by Rachel J Morris || Ludi (Female), Shimá (One who performs a sexual act)
|-
| Shineshimá || Bisexual || Unofficial || Shin (two), Shimá (One who performs a sexual act)
|-
| Wohoshimá || Pansexual || Unofficial, defined by Rachel J Morris || Woho (All, every), Shimá (One who performs a sexual act)
|-
| Ramaha || Asexual || Word in the official dictionary. || Ramaha (Absence of sexual desire)
|}

==== Notes ====

Build whatever word is comfortable for yourself. The tricky part here is that it is hard to define romantic orientations with the limited Láadan dictionary.

I'm not quite sure how the word for lesbian was built; I would tend to go with the ''Ludi'' definition rather than ''Lul'' to take into account lesbians who are also trans women, or in a relationship with a trans woman.

''Bisexual'' can mean vastly different things to different people. Therefore, I'm leaving it alone. (However, another contributor has suggested a usage based on the numeral 2, for those who believe the name depends on assumption of a gender binary.)

''Wohoshimá'' may seem more like &quot;one who does all sexual acts&quot;, which would be misleading. Gee, if only Láadan had better vocabulary to talk about gender and sexuality!

=== Gender Identity ===

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English !! Origin !! Breakdown 
|-
| zhén || gender || Unofficial, added by Gen3 || From both English ''gender'' and Láadan ''zhe'' (here abbreviated from ''zheledal'' 'identity')
|-
| ? || male-identified ||  ||
|-
| ? || female-identified ||  || 
|-
| ? || transgender || ||
|-
| ? || agender || ||
|-
| ? || multigender || ||
|-
| ? || genderfluid || ||
|-
| ? || non-binary || ||
|}

=== Additional ===

{| class=&quot;wikitable sortable&quot;
|-
! Láadan !! English !! Origin !! Breakdown
|-
| ? || Intersex || ||
|-
| ? || Questioning ||  ||
|-
| ? || Aromantic ||  ||
|}

== Notes ==

{{BookCat}}</text>
      <sha1>s6wi2g2z4m6puwodzbj6ceeof2onr5l</sha1>
    </revision>
  </page>
  <page>
    <title>Mirad Grammar</title>
    <ns>0</ns>
    <id>417631</id>
    <revision>
      <id>4676543</id>
      <parentid>4675241</parentid>
      <timestamp>2026-10-17T15:13:27Z</timestamp>
      <contributor>
        <username>Tyoyafud</username>
        <id>6233</id>
      </contributor>
      <origin>4676543</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3077" sha1="72q3d69uqnombz36lb43nrtp9q9gzhp" xml:space="preserve">{{status|100%}}
{{Chapter navigation with TOC||Introduction|}}
{{print version|Mirad Grammar/print version|(No dictionary)|Mirad Grammar}}
{{Book search | style=image}}
&lt;small&gt;
Welcome to a textbook on the grammar of &lt;big&gt;&lt;b&gt;Mirad&lt;/b&gt;&lt;/big&gt;.&amp;nbsp;&amp;nbsp;Formerly known as '''Unilingua''', Mirad is an artificially constructed auxiliary language ([[Constructed language|conlang]]) developed originally by Paris-based author Noubar Agopoff [https://books.google.com/books/about/Unilingua.html?id=I7ghxwEACAAJ] as a ''serious'' medium for easy, regular, expressive, and logical international communication.  This textbook is a revision of the language with many new features, plus access to a bilingual dictionary containing over 153,000 word/expression pairings, over ten times the size the original Unilingua vocabulary. The vocabulary is internally consistent, [[wikt:oligosynthetic|oligosynthetic]] (built from a minimal set of roots), and [[wikt:a priori|a priori]], i.e. it was developed systematically from scratch with no relation to existing natural languages except for a few universally-adopted words like &quot;karaoke&quot; or &quot;falafel&quot;, and flora/fauna terms, which are based partially on Latin syllables of the Linnaeus taxonomy.
&lt;/small&gt;
[[File:The Earth seen from Apollo 17.jpg|thumb|left|'''Yubjo, ha mir gonbio yansauna gabyuxea dalzeyn.''' (''Soon, the world will share a common auxiliary language.'')]]

{| class=&quot;wikitable&quot; style=&quot;font-size:smaller; margin: 0 auto;&quot;
|+ Table of Contents
|-
|valign=&quot;top&quot;|
* [[/Introduction/]]  {{stage short|100%}}
* [[/Why Mirad?/]]  {{stage short|100%}}
* [[/Alphabet/]]  {{stage short|100%}}
* [[/Pronunciation/]]  {{stage short|100%}}
* [[/Syllabification/]]  {{stage short|100%}}
* [[/Stress/]]  {{stage short|100%}}
* [[/Phonotactics/]]  {{stage short|100%}}
* [[/Parts of Speech/]]  {{stage short|100%}}
* [[/Nouns/]]  {{stage short|100%}}
* [[/Nouns#Modifying Nouns with the Definite Article|Articles]]  {{stage short|100%}}
* [[/Adjectives/]]  {{stage short|100%}}
* [[/Adverbs/]]  {{stage short|100%}}
* [[/Determiners/]]  {{stage short|100%}}
* [[/Numbers/]]  {{stage short|100%}}
* [[/Pronouns/]]  {{stage short|100%}}
* [[/Verbs/]]  {{stage short|100%}}
* [[/Prepositions/]]  {{stage short|100%}}
* [[/Conjunctions/]]  {{stage short|100%}}
|valign=&quot;top&quot;|
* [[/Interjections/]]  {{stage short|100%}}
* [[/Hybrids/]]  {{stage short|100%}}
* [[/Greetings and Euphemisms/]]  {{stage short|100%}}
* [[/Acronyms and Abbreviations/]]  {{stage short|100%}}
* [[/Onomatopoeia/]]  {{stage short|100%}}
* [[/Vocabulary Formation/]]  {{stage short|100%}}
* [[/Word Families/]]  {{stage short|100%}}
* [[/Syntax/]]{{stage short|100%}}
* [[/Sample Texts Analyzed/]]  {{stage short|100%}}
* [[/Lesson 1/]]  {{stage short|100%}}
* [[/Lesson 2/]]  {{stage short|100%}}
* [[/Lesson 3/]]  {{stage short|100%}}
* [[/Lesson 4/]]  {{stage short|100%}}
* [[/Lesson 5/]]  {{stage short|100%}}
* [[/Mirad-English Dictionary/]]  {{stage short|100%}}
* [[/Flaws in Mirad/]] {{stage short|%25}}
|}
{{Alphabetical|M}}
{{Shelves|Constructed languages}}</text>
      <sha1>72q3d69uqnombz36lb43nrtp9q9gzhp</sha1>
    </revision>
  </page>
  <page>
    <title>Category talk:Book:Java Programming</title>
    <ns>15</ns>
    <id>457073</id>
    <revision>
      <id>4676683</id>
      <parentid>4449746</parentid>
      <timestamp>2026-10-18T04:57:40Z</timestamp>
      <contributor>
        <username>~2026-55634-58</username>
        <id>3628670</id>
      </contributor>
      <comment>Audiodual</comment>
      <origin>4676683</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1759" sha1="1fi3pcqh43fada8iyrmctcgin01ps0m" xml:space="preserve">{{Talk header}}

public class GasPumpDisplay {

   private int digits;

   private int[] currentDigits;

   private static final int MAX_DIGIT = 4;

   public GasPumpDisplay(int numberOfPositions) {

       this.digits = numberOfPositions;

       this.currentDigits = new int[digits];

       for (int i = 0; i &lt; digits; i++) {

           currentDigits[i] = 0;

       }

   }

   public String nextElement() {

       StringBuilder sb = new StringBuilder();

       for (int i = 0; i &lt; digits; i++) {

           sb.append(currentDigits[i]);

       }

       // increment the current digits

       for (int i = digits - 1; i &gt;= 0; i--) {

           if (currentDigits[i] &lt; MAX_DIGIT) {

               currentDigits[i]++;

               break;

           } else {

               currentDigits[i] = 0;

           }

       }

       return sb.toString();

   }

   public boolean hasMoreElements() {

       for (int i = 0; i &lt; digits; i++) {

           if (currentDigits[i] &lt; MAX_DIGIT) {

               return true;

           }

       }

       return false;

   }

}

public class GasPumpTester {

   public static void main(String[] args) {

       GasPumpDisplay d = new GasPumpDisplay(3);

       while (d.hasMoreElements()) {

           System.out.println(d.nextElement());

       }

   }

}

``` [[Special:Contributions/216.37.99.103|216.37.99.103]] ([[User talk:216.37.99.103|discuss]]) 20:46, 5 December 2024 (UTC)

== Audio dual ==
audiodual

[[Special:Contributions/~2026-55634-58|~2026-55634-58]] ([[User talk:~2026-55634-58|talk]]) 04:57, 18 October 2026 (UTC)</text>
      <sha1>1fi3pcqh43fada8iyrmctcgin01ps0m</sha1>
    </revision>
    <revision>
      <id>4676685</id>
      <parentid>4676683</parentid>
      <timestamp>2026-10-18T05:03:11Z</timestamp>
      <contributor>
        <username>Pristome</username>
        <id>3519119</id>
      </contributor>
      <minor />
      <comment>Undid edits by [[Special:Contribs/~2026-55634-58|~2026-55634-58]] ([[User talk:~2026-55634-58|talk]]) to last version by 216.37.99.103</comment>
      <origin>4676685</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1609" sha1="2m596cqtjp1894xoscyshue61l42bcu" xml:space="preserve">{{Talk header}}

public class GasPumpDisplay {

   private int digits;

   private int[] currentDigits;

   private static final int MAX_DIGIT = 4;

   public GasPumpDisplay(int numberOfPositions) {

       this.digits = numberOfPositions;

       this.currentDigits = new int[digits];

       for (int i = 0; i &lt; digits; i++) {

           currentDigits[i] = 0;

       }

   }

   public String nextElement() {

       StringBuilder sb = new StringBuilder();

       for (int i = 0; i &lt; digits; i++) {

           sb.append(currentDigits[i]);

       }

       // increment the current digits

       for (int i = digits - 1; i &gt;= 0; i--) {

           if (currentDigits[i] &lt; MAX_DIGIT) {

               currentDigits[i]++;

               break;

           } else {

               currentDigits[i] = 0;

           }

       }

       return sb.toString();

   }

   public boolean hasMoreElements() {

       for (int i = 0; i &lt; digits; i++) {

           if (currentDigits[i] &lt; MAX_DIGIT) {

               return true;

           }

       }

       return false;

   }

}

public class GasPumpTester {

   public static void main(String[] args) {

       GasPumpDisplay d = new GasPumpDisplay(3);

       while (d.hasMoreElements()) {

           System.out.println(d.nextElement());

       }

   }

}

``` [[Special:Contributions/216.37.99.103|216.37.99.103]] ([[User talk:216.37.99.103|discuss]]) 20:46, 5 December 2024 (UTC)</text>
      <sha1>2m596cqtjp1894xoscyshue61l42bcu</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Codename Noreste</title>
    <ns>3</ns>
    <id>466307</id>
    <revision>
      <id>4676521</id>
      <parentid>4676479</parentid>
      <timestamp>2026-10-17T13:40:45Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>/* Removal of rights of inactive patrollers */ reply ([[mw:c:Special:MyLanguage/User:JWBTH/CD|CD]])</comment>
      <origin>4676521</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2963" sha1="kp9bhdzu520hi6xhm2egjt3udjkh5iz" xml:space="preserve">{{talk header}} {{User:MiszaBot/config
|archive = User talk:Codename Noreste/Archive %(counter)d
|algo = old(14d)
|counter = 1
|maxarchivesize = 100K
|archiveheader = {{Automatic archive navigator}}
|minthreadstoarchive = 1
|minthreadsleft = 1
}}

== Removal of rights of inactive patrollers ==

Hi, I started the script to remove the rights, sorry it took me a bit. I had to deal with an urgent issue. it's running as bot so it's not flooding RC. [[User:Ladsgroup|Ladsgroup]] ([[User talk:Ladsgroup|discuss]] • [[Special:Contributions/Ladsgroup|contribs]]) 21:41, 15 October 2026 (UTC)
: Thanks. Once you are done, you can request a steward to remove your ''temporary'' administrator and bot rights.
: While not related, one option is that you can request system administrator rights–after you add the request to SRGP explaining your use case, and then send a detailed use case to Wikimedia T&amp;S by email.
: Once again, thank you for operating the behind the scenes on removing FlaggedRevs for good, as you had me on charge with the necessary patches. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 21:50, 15 October 2026 (UTC)
::yeah I know how to get rid of it, this is not my first time :D A couple months ago I needed similar rights on cywiki. I do this kind of thing once every couple of months. [[User:Ladsgroup|Ladsgroup]] ([[User talk:Ladsgroup|discuss]] • [[Special:Contributions/Ladsgroup|contribs]]) 22:09, 15 October 2026 (UTC)
::: Wait, something weird happened: [[Special:Redirect/logid/5414075]]. No former autoreviewed user became autopatrolled. :( [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 23:38, 15 October 2026 (UTC)
::::(please ping me). I ran this: &quot; mwscript-k8s --follow -- migrateUserGroup --wiki=enwikibooks autoreview autopatrol&quot;. Maybe the name was not correct? Can you double check. [[User:Ladsgroup|Ladsgroup]] ([[User talk:Ladsgroup|discuss]] • [[Special:Contributions/Ladsgroup|contribs]]) 15:40, 16 October 2026 (UTC)
::::: @[[User:Ladsgroup|Ladsgroup]] it removed autopatrol (not patroller), but we would have to find out users with the autopatrol user group (formerly autoreviewed user) and migrate them to the autopatroller user group. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 21:01, 16 October 2026 (UTC)
: Pinging once again to [[User:Ladsgroup|Ladsgroup]]: &lt;span class=&quot;plainlinks&quot;&gt;[https://en.wikibooks.org/wiki/Special:ListUsers?username=&amp;group=autopatrol&amp;wpsubmit=&amp;wpFormIdentifier=mw-listusers-form&amp;limit=50 This list of users who were previously autoreviewed]&lt;/span&gt; should be migrated to the autopatroller user group. Thank you. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:40, 17 October 2026 (UTC)</text>
      <sha1>kp9bhdzu520hi6xhm2egjt3udjkh5iz</sha1>
    </revision>
    <revision>
      <id>4676527</id>
      <parentid>4676521</parentid>
      <timestamp>2026-10-17T13:49:42Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>/* Removal of rights of inactive patrollers */ addition ([[mw:c:Special:MyLanguage/User:JWBTH/CD|CD]])</comment>
      <origin>4676527</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3268" sha1="jx90iu120zbhhoppkokbwtfr0imw3uv" xml:space="preserve">{{talk header}} {{User:MiszaBot/config
|archive = User talk:Codename Noreste/Archive %(counter)d
|algo = old(14d)
|counter = 1
|maxarchivesize = 100K
|archiveheader = {{Automatic archive navigator}}
|minthreadstoarchive = 1
|minthreadsleft = 1
}}

== Removal of rights of inactive patrollers ==

Hi, I started the script to remove the rights, sorry it took me a bit. I had to deal with an urgent issue. it's running as bot so it's not flooding RC. [[User:Ladsgroup|Ladsgroup]] ([[User talk:Ladsgroup|discuss]] • [[Special:Contributions/Ladsgroup|contribs]]) 21:41, 15 October 2026 (UTC)
: Thanks. Once you are done, you can request a steward to remove your ''temporary'' administrator and bot rights.
: While not related, one option is that you can request system administrator rights–after you add the request to SRGP explaining your use case, and then send a detailed use case to Wikimedia T&amp;S by email.
: Once again, thank you for operating the behind the scenes on removing FlaggedRevs for good, as you had me on charge with the necessary patches. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 21:50, 15 October 2026 (UTC)
::yeah I know how to get rid of it, this is not my first time :D A couple months ago I needed similar rights on cywiki. I do this kind of thing once every couple of months. [[User:Ladsgroup|Ladsgroup]] ([[User talk:Ladsgroup|discuss]] • [[Special:Contributions/Ladsgroup|contribs]]) 22:09, 15 October 2026 (UTC)
::: Wait, something weird happened: [[Special:Redirect/logid/5414075]]. No former autoreviewed user became autopatrolled. :( [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 23:38, 15 October 2026 (UTC)
::::(please ping me). I ran this: &quot; mwscript-k8s --follow -- migrateUserGroup --wiki=enwikibooks autoreview autopatrol&quot;. Maybe the name was not correct? Can you double check. [[User:Ladsgroup|Ladsgroup]] ([[User talk:Ladsgroup|discuss]] • [[Special:Contributions/Ladsgroup|contribs]]) 15:40, 16 October 2026 (UTC)
::::: @[[User:Ladsgroup|Ladsgroup]] it removed autopatrol (not patroller), but we would have to find out users with the autopatrol user group (formerly autoreviewed user) and migrate them to the autopatroller user group. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 21:01, 16 October 2026 (UTC)
: Pinging once again to [[User:Ladsgroup|Ladsgroup]]: &lt;span class=&quot;plainlinks&quot;&gt;[https://en.wikibooks.org/wiki/Special:ListUsers?username=&amp;group=autopatrol&amp;wpsubmit=&amp;wpFormIdentifier=mw-listusers-form&amp;limit=50 This list of users who were previously autoreviewed]&lt;/span&gt; should be migrated to the autopatroller user group. Thank you. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:40, 17 October 2026 (UTC)
:: Also, the removal of that permission after being inactive for more than 2 years (as we discussed on IRC) also applies (in addition to former reviewer). [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:49, 17 October 2026 (UTC)</text>
      <sha1>jx90iu120zbhhoppkokbwtfr0imw3uv</sha1>
    </revision>
    <revision>
      <id>4676563</id>
      <parentid>4676527</parentid>
      <timestamp>2026-10-17T17:21:56Z</timestamp>
      <contributor>
        <username>Ladsgroup</username>
        <id>98768</id>
      </contributor>
      <comment>/* Removal of rights of inactive patrollers */ Reply</comment>
      <origin>4676563</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3466" sha1="blohns3xr0hlrahzskx6k966oko0av2" xml:space="preserve">{{talk header}} {{User:MiszaBot/config
|archive = User talk:Codename Noreste/Archive %(counter)d
|algo = old(14d)
|counter = 1
|maxarchivesize = 100K
|archiveheader = {{Automatic archive navigator}}
|minthreadstoarchive = 1
|minthreadsleft = 1
}}

== Removal of rights of inactive patrollers ==

Hi, I started the script to remove the rights, sorry it took me a bit. I had to deal with an urgent issue. it's running as bot so it's not flooding RC. [[User:Ladsgroup|Ladsgroup]] ([[User talk:Ladsgroup|discuss]] • [[Special:Contributions/Ladsgroup|contribs]]) 21:41, 15 October 2026 (UTC)
: Thanks. Once you are done, you can request a steward to remove your ''temporary'' administrator and bot rights.
: While not related, one option is that you can request system administrator rights–after you add the request to SRGP explaining your use case, and then send a detailed use case to Wikimedia T&amp;S by email.
: Once again, thank you for operating the behind the scenes on removing FlaggedRevs for good, as you had me on charge with the necessary patches. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 21:50, 15 October 2026 (UTC)
::yeah I know how to get rid of it, this is not my first time :D A couple months ago I needed similar rights on cywiki. I do this kind of thing once every couple of months. [[User:Ladsgroup|Ladsgroup]] ([[User talk:Ladsgroup|discuss]] • [[Special:Contributions/Ladsgroup|contribs]]) 22:09, 15 October 2026 (UTC)
::: Wait, something weird happened: [[Special:Redirect/logid/5414075]]. No former autoreviewed user became autopatrolled. :( [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 23:38, 15 October 2026 (UTC)
::::(please ping me). I ran this: &quot; mwscript-k8s --follow -- migrateUserGroup --wiki=enwikibooks autoreview autopatrol&quot;. Maybe the name was not correct? Can you double check. [[User:Ladsgroup|Ladsgroup]] ([[User talk:Ladsgroup|discuss]] • [[Special:Contributions/Ladsgroup|contribs]]) 15:40, 16 October 2026 (UTC)
::::: @[[User:Ladsgroup|Ladsgroup]] it removed autopatrol (not patroller), but we would have to find out users with the autopatrol user group (formerly autoreviewed user) and migrate them to the autopatroller user group. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 21:01, 16 October 2026 (UTC)
: Pinging once again to [[User:Ladsgroup|Ladsgroup]]: &lt;span class=&quot;plainlinks&quot;&gt;[https://en.wikibooks.org/wiki/Special:ListUsers?username=&amp;group=autopatrol&amp;wpsubmit=&amp;wpFormIdentifier=mw-listusers-form&amp;limit=50 This list of users who were previously autoreviewed]&lt;/span&gt; should be migrated to the autopatroller user group. Thank you. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:40, 17 October 2026 (UTC)
:: Also, the removal of that permission after being inactive for more than 2 years (as we discussed on IRC) also applies (in addition to former reviewer). [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:49, 17 October 2026 (UTC)
::I'm sick and can't sit behind pc. Give me a day or two [[User:Ladsgroup|Ladsgroup]] ([[User talk:Ladsgroup|discuss]] • [[Special:Contributions/Ladsgroup|contribs]]) 17:21, 17 October 2026 (UTC)</text>
      <sha1>blohns3xr0hlrahzskx6k966oko0av2</sha1>
    </revision>
    <revision>
      <id>4676570</id>
      <parentid>4676563</parentid>
      <timestamp>2026-10-17T18:35:52Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>/* Removal of rights of inactive patrollers */ reply to Ladsgroup: No worries, there is no rush here. :) (-) ([[mw:c:Special:MyLanguage/User:JWBTH/CD|CD]])</comment>
      <origin>4676570</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3658" sha1="evvac258w6j4smaimh1d06ax7ewzyl7" xml:space="preserve">{{talk header}} {{User:MiszaBot/config
|archive = User talk:Codename Noreste/Archive %(counter)d
|algo = old(14d)
|counter = 1
|maxarchivesize = 100K
|archiveheader = {{Automatic archive navigator}}
|minthreadstoarchive = 1
|minthreadsleft = 1
}}

== Removal of rights of inactive patrollers ==

Hi, I started the script to remove the rights, sorry it took me a bit. I had to deal with an urgent issue. it's running as bot so it's not flooding RC. [[User:Ladsgroup|Ladsgroup]] ([[User talk:Ladsgroup|discuss]] • [[Special:Contributions/Ladsgroup|contribs]]) 21:41, 15 October 2026 (UTC)
: Thanks. Once you are done, you can request a steward to remove your ''temporary'' administrator and bot rights.
: While not related, one option is that you can request system administrator rights–after you add the request to SRGP explaining your use case, and then send a detailed use case to Wikimedia T&amp;S by email.
: Once again, thank you for operating the behind the scenes on removing FlaggedRevs for good, as you had me on charge with the necessary patches. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 21:50, 15 October 2026 (UTC)
::yeah I know how to get rid of it, this is not my first time :D A couple months ago I needed similar rights on cywiki. I do this kind of thing once every couple of months. [[User:Ladsgroup|Ladsgroup]] ([[User talk:Ladsgroup|discuss]] • [[Special:Contributions/Ladsgroup|contribs]]) 22:09, 15 October 2026 (UTC)
::: Wait, something weird happened: [[Special:Redirect/logid/5414075]]. No former autoreviewed user became autopatrolled. :( [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 23:38, 15 October 2026 (UTC)
::::(please ping me). I ran this: &quot; mwscript-k8s --follow -- migrateUserGroup --wiki=enwikibooks autoreview autopatrol&quot;. Maybe the name was not correct? Can you double check. [[User:Ladsgroup|Ladsgroup]] ([[User talk:Ladsgroup|discuss]] • [[Special:Contributions/Ladsgroup|contribs]]) 15:40, 16 October 2026 (UTC)
::::: @[[User:Ladsgroup|Ladsgroup]] it removed autopatrol (not patroller), but we would have to find out users with the autopatrol user group (formerly autoreviewed user) and migrate them to the autopatroller user group. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 21:01, 16 October 2026 (UTC)
: Pinging once again to [[User:Ladsgroup|Ladsgroup]]: &lt;span class=&quot;plainlinks&quot;&gt;[https://en.wikibooks.org/wiki/Special:ListUsers?username=&amp;group=autopatrol&amp;wpsubmit=&amp;wpFormIdentifier=mw-listusers-form&amp;limit=50 This list of users who were previously autoreviewed]&lt;/span&gt; should be migrated to the autopatroller user group. Thank you. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:40, 17 October 2026 (UTC)
:: Also, the removal of that permission after being inactive for more than 2 years (as we discussed on IRC) also applies (in addition to former reviewer). [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:49, 17 October 2026 (UTC)
::I'm sick and can't sit behind pc. Give me a day or two [[User:Ladsgroup|Ladsgroup]] ([[User talk:Ladsgroup|discuss]] • [[Special:Contributions/Ladsgroup|contribs]]) 17:21, 17 October 2026 (UTC)
::: No worries, there is no rush here. :) [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:35, 17 October 2026 (UTC)</text>
      <sha1>evvac258w6j4smaimh1d06ax7ewzyl7</sha1>
    </revision>
  </page>
  <page>
    <title>User:JJPMaster/luna/CurateThisPage.js</title>
    <ns>2</ns>
    <id>470953</id>
    <revision>
      <id>4676670</id>
      <parentid>4662639</parentid>
      <timestamp>2026-10-18T03:09:44Z</timestamp>
      <contributor>
        <username>JJPMaster</username>
        <id>3095725</id>
      </contributor>
      <comment>migrating to patrol</comment>
      <origin>4676670</origin>
      <model>javascript</model>
      <format>text/javascript</format>
      <text bytes="4237" sha1="rz806go1oyvwy1jjb0tixnelgxyk655" xml:space="preserve">// &lt;nowiki&gt;
var parsedTitle = mw.config.get(&quot;wgPageName&quot;).replace(/_/g, &quot; &quot;);
(() =&gt; {
	if (mw.config.get(&quot;wgArticleId&quot;)) {
		var porty = window.addLunaLink({
			id: &quot;luna-ctp&quot;,
			href: &quot;#&quot;,
			text: &quot;Tag (improvement)&quot;,
			tooltip: 'Tag this page for maintenance or improvement',
			onClick: () =&gt; { 
				$(&quot;#CTPdialog&quot;).dialog({ title: &quot;Tag this page for maintenance or improvement&quot;, height: &quot;auto&quot;, width: &quot;auto&quot; })
			}
		});
	}
})(); 

$(() =&gt; {
	if (mw.config.get(&quot;wgArticleId&quot;) !== 0) {
		$(&quot;#bodyContent&quot;).append(`
		&lt;div id=&quot;CTPdialog&quot;&gt;
			How would you like to tag this page? &lt;br /&gt;
			&lt;select name=&quot;CTPtagReason&quot; id=&quot;CTPtagReason&quot;&gt;
				&lt;option&gt;Select the template&lt;/option&gt;
				&lt;option id=&quot;qr-em&quot;&gt;Query (test)&lt;/option&gt;
				&lt;option id=&quot;qr-dup&quot;&gt;Query (duplicate)&lt;/option&gt;
				&lt;option id=&quot;qr-twwp&quot;&gt;Query (cut-and-paste transwiki)&lt;/option&gt;
				&lt;option id=&quot;qr-scope&quot;&gt;Query (out of scope)&lt;/option&gt;
				&lt;option id=&quot;s-twwp-2&quot;&gt;Dewikify, bookify, adopt&lt;/option&gt;
				&lt;option id=&quot;attention&quot;&gt;Attention&lt;/option&gt;
				&lt;option id=&quot;cleanup&quot;&gt;Cleanup&lt;/option&gt;
				&lt;option id=&quot;unreferenced&quot;&gt;Unreferenced&lt;/option&gt;
				&lt;option id=&quot;formatting&quot;&gt;Formatting&lt;/option&gt;
				&lt;option id=&quot;copyedit&quot;&gt;Copy edit&lt;/option&gt;
				&lt;option id=&quot;outdated&quot;&gt;Outdated&lt;/option&gt;
				&lt;option id=&quot;stub&quot;&gt;Stub&lt;/option&gt;
		    &lt;/select&gt;
		    &lt;span style=&quot;display: block;&quot;&gt;&lt;input type=&quot;checkbox&quot; id=&quot;patrolMark&quot; class=&quot;patrolMark&quot; name=&quot;patrolMark&quot; /&gt;&lt;label class=&quot;patrolMark&quot; for=&quot;patrolMark&quot;&gt;Mark as patrolled&lt;/label&gt;&lt;/span&gt;
		    &lt;input type=&quot;checkbox&quot; id=&quot;notifyAuthor&quot; name=&quot;notifyAuthor&quot; checked /&gt;&lt;label for=&quot;notifyAuthor&quot;&gt;Notify page author&lt;/label&gt;&lt;br /&gt;
		    &lt;button type=&quot;button&quot; id=&quot;addTag&quot;&gt;Add tag&lt;/button&gt;&lt;/div&gt;
		`);
		(async () =&gt; {
			if (await waitForPreferences()) {
				for (var [i, j] of Object.entries(Luna.myPreferences.CTP)) {
				    $(&quot;#CTPtagReason&quot;).append(`&lt;option id=&quot;${i}&quot;&gt;${j}&lt;/option&gt;`);
				}

			}
			else {
			    console.error(&quot;Luna: Preferences never fully loaded.&quot;);
			}
		})();
		if (!window.isPatroller) $(&quot;.patrolMark&quot;).hide();
		$(&quot;#CTPdialog&quot;).hide();
		$(&quot;#addTag&quot;).click(async function() {
			var mySelect = document.getElementById(&quot;CTPtagReason&quot;);
			var critValue = mySelect.value;
			var tag = mySelect.options[mySelect.selectedIndex].id;
			var cmtAuthor;
			var queryComment;
			if ($(&quot;#notifyAuthor&quot;).prop(&quot;checked&quot;)) {
				cmtAuthor = prompt(&quot;Why are you tagging this page (press 'Cancel' to use the default reason)? This comment will also be sent to the author of the page.&quot;) || &quot;&quot;;
				queryComment = cmtAuthor;
			}
			else if (tag == &quot;qr-em&quot;) {
				queryComment = prompt(&quot;Why are you querying this page (press 'Cancel' to use the default reason)?&quot;) || &quot;&quot;;
			}
			
			if(critValue == &quot;Select the template&quot;) {
				alert(&quot;You must select a template.&quot;);
				return;
			}
			else {
				var criterion;
				var finalTag;
				if (tag.startsWith(&quot;s-&quot;)) {
					tag = &quot;subst:&quot; + tag.slice(2);
				}

				if ($(&quot;#patrolMark&quot;).prop(&quot;checked&quot;)) {
					doThePatrol(false);
				}
				criterion = `Adding {{${tag}}} tag`;
				finalTag = tag != &quot;qr-em&quot; ? tag : tag + `|1=${queryComment}`;
				var params = {
					action: 'edit',
					prependtext: `{{${finalTag}}}\n`,
					title: parsedTitle,
					summary: criterion,
					tags: &quot;Luna&quot;,
					format: 'json'
				},
				api = new mw.Api();

				try {
					var data = await api.postWithToken( 'csrf', params )
					console.log( data );
					
					if ($(&quot;#notifyAuthor&quot;).prop(&quot;checked&quot;)) {
						params = {
							action: 'edit',
							appendtext: `\n{{subst:User:JJPMaster/CurateThisPage/authorMsg|title=${parsedTitle}|tag=${finalTag}|username=${mw.config.get(&quot;wgUserName&quot;)}|comment=${cmtAuthor ? cmtAuthor : &quot;&quot;}}}`,
							title: `User_talk:${await getAuthor()}`,
							summary: &quot;Notifying author about page tagging&quot;,
							tags: &quot;Luna&quot;,
							format: 'json'
						}
						api = new mw.Api();
						data = await api.postWithToken( 'csrf', params )
						console.log( data );
					}
					mw.notify(&quot;Luna:\nThe tag has been added. Reloading...&quot;);
					setTimeout(() =&gt; window.location.reload(), 2000);
				}
				catch (error) {
					console.error(&quot;Luna: Tagging failed.&quot;, error);
					mw.notify(&quot;Luna: Tagging failed. See the console for details.&quot;);
				}
				
			}
		});
	}
});
// &lt;/nowiki&gt;</text>
      <sha1>rz806go1oyvwy1jjb0tixnelgxyk655</sha1>
    </revision>
    <revision>
      <id>4676676</id>
      <parentid>4676670</parentid>
      <timestamp>2026-10-18T03:15:04Z</timestamp>
      <contributor>
        <username>JJPMaster</username>
        <id>3095725</id>
      </contributor>
      <comment>restore patrol functionality</comment>
      <origin>4676676</origin>
      <model>javascript</model>
      <format>text/javascript</format>
      <text bytes="4601" sha1="qof3c5jwxy7q0tmqwfx1k4kjnh40qmh" xml:space="preserve">// &lt;nowiki&gt;
var parsedTitle = mw.config.get(&quot;wgPageName&quot;).replace(/_/g, &quot; &quot;);
(() =&gt; {
	if (mw.config.get(&quot;wgArticleId&quot;)) {
		var porty = window.addLunaLink({
			id: &quot;luna-ctp&quot;,
			href: &quot;#&quot;,
			text: &quot;Tag (improvement)&quot;,
			tooltip: 'Tag this page for maintenance or improvement',
			onClick: () =&gt; { 
				$(&quot;#CTPdialog&quot;).dialog({ title: &quot;Tag this page for maintenance or improvement&quot;, height: &quot;auto&quot;, width: &quot;auto&quot; })
			}
		});
	}
	if (window.isPatroller)	{
		var porty2 = window.addLunaLink({
			id: &quot;luna-rev&quot;,
			href: &quot;#&quot;,
			text: &quot;Review&quot;,
			tooltip: &quot;Mark this page as reviewed&quot;,
			onClick: async () =&gt; {
				await doThePatrol(true); 
				mw.notify(&quot;Luna:\nThe page has been marked as patrolled. Reloading...&quot;);
				setTimeout(() =&gt; window.location.reload(), 2000);
			}
		});
	}
})(); 

$(() =&gt; {
	if (mw.config.get(&quot;wgArticleId&quot;) !== 0) {
		$(&quot;#bodyContent&quot;).append(`
		&lt;div id=&quot;CTPdialog&quot;&gt;
			How would you like to tag this page? &lt;br /&gt;
			&lt;select name=&quot;CTPtagReason&quot; id=&quot;CTPtagReason&quot;&gt;
				&lt;option&gt;Select the template&lt;/option&gt;
				&lt;option id=&quot;qr-em&quot;&gt;Query (test)&lt;/option&gt;
				&lt;option id=&quot;qr-dup&quot;&gt;Query (duplicate)&lt;/option&gt;
				&lt;option id=&quot;qr-twwp&quot;&gt;Query (cut-and-paste transwiki)&lt;/option&gt;
				&lt;option id=&quot;qr-scope&quot;&gt;Query (out of scope)&lt;/option&gt;
				&lt;option id=&quot;s-twwp-2&quot;&gt;Dewikify, bookify, adopt&lt;/option&gt;
				&lt;option id=&quot;attention&quot;&gt;Attention&lt;/option&gt;
				&lt;option id=&quot;cleanup&quot;&gt;Cleanup&lt;/option&gt;
				&lt;option id=&quot;unreferenced&quot;&gt;Unreferenced&lt;/option&gt;
				&lt;option id=&quot;formatting&quot;&gt;Formatting&lt;/option&gt;
				&lt;option id=&quot;copyedit&quot;&gt;Copy edit&lt;/option&gt;
				&lt;option id=&quot;outdated&quot;&gt;Outdated&lt;/option&gt;
				&lt;option id=&quot;stub&quot;&gt;Stub&lt;/option&gt;
		    &lt;/select&gt;
		    &lt;span style=&quot;display: block;&quot;&gt;&lt;input type=&quot;checkbox&quot; id=&quot;patrolMark&quot; class=&quot;patrolMark&quot; name=&quot;patrolMark&quot; /&gt;&lt;label class=&quot;patrolMark&quot; for=&quot;patrolMark&quot;&gt;Mark as patrolled&lt;/label&gt;&lt;/span&gt;
		    &lt;input type=&quot;checkbox&quot; id=&quot;notifyAuthor&quot; name=&quot;notifyAuthor&quot; checked /&gt;&lt;label for=&quot;notifyAuthor&quot;&gt;Notify page author&lt;/label&gt;&lt;br /&gt;
		    &lt;button type=&quot;button&quot; id=&quot;addTag&quot;&gt;Add tag&lt;/button&gt;&lt;/div&gt;
		`);
		(async () =&gt; {
			if (await waitForPreferences()) {
				for (var [i, j] of Object.entries(Luna.myPreferences.CTP)) {
				    $(&quot;#CTPtagReason&quot;).append(`&lt;option id=&quot;${i}&quot;&gt;${j}&lt;/option&gt;`);
				}

			}
			else {
			    console.error(&quot;Luna: Preferences never fully loaded.&quot;);
			}
		})();
		if (!window.isPatroller) $(&quot;.patrolMark&quot;).hide();
		$(&quot;#CTPdialog&quot;).hide();
		$(&quot;#addTag&quot;).click(async function() {
			var mySelect = document.getElementById(&quot;CTPtagReason&quot;);
			var critValue = mySelect.value;
			var tag = mySelect.options[mySelect.selectedIndex].id;
			var cmtAuthor;
			var queryComment;
			if ($(&quot;#notifyAuthor&quot;).prop(&quot;checked&quot;)) {
				cmtAuthor = prompt(&quot;Why are you tagging this page (press 'Cancel' to use the default reason)? This comment will also be sent to the author of the page.&quot;) || &quot;&quot;;
				queryComment = cmtAuthor;
			}
			else if (tag == &quot;qr-em&quot;) {
				queryComment = prompt(&quot;Why are you querying this page (press 'Cancel' to use the default reason)?&quot;) || &quot;&quot;;
			}
			
			if(critValue == &quot;Select the template&quot;) {
				alert(&quot;You must select a template.&quot;);
				return;
			}
			else {
				var criterion;
				var finalTag;
				if (tag.startsWith(&quot;s-&quot;)) {
					tag = &quot;subst:&quot; + tag.slice(2);
				}

				if ($(&quot;#patrolMark&quot;).prop(&quot;checked&quot;)) {
					await doThePatrol(false);
				}
				criterion = `Adding {{${tag}}} tag`;
				finalTag = tag != &quot;qr-em&quot; ? tag : tag + `|1=${queryComment}`;
				var params = {
					action: 'edit',
					prependtext: `{{${finalTag}}}\n`,
					title: parsedTitle,
					summary: criterion,
					tags: &quot;Luna&quot;,
					format: 'json'
				},
				api = new mw.Api();

				try {
					var data = await api.postWithToken( 'csrf', params )
					console.log( data );
					
					if ($(&quot;#notifyAuthor&quot;).prop(&quot;checked&quot;)) {
						params = {
							action: 'edit',
							appendtext: `\n{{subst:User:JJPMaster/CurateThisPage/authorMsg|title=${parsedTitle}|tag=${finalTag}|username=${mw.config.get(&quot;wgUserName&quot;)}|comment=${cmtAuthor ? cmtAuthor : &quot;&quot;}}}`,
							title: `User_talk:${await getAuthor()}`,
							summary: &quot;Notifying author about page tagging&quot;,
							tags: &quot;Luna&quot;,
							format: 'json'
						}
						api = new mw.Api();
						data = await api.postWithToken( 'csrf', params )
						console.log( data );
					}
					mw.notify(&quot;Luna:\nThe tag has been added. Reloading...&quot;);
					setTimeout(() =&gt; window.location.reload(), 2000);
				}
				catch (error) {
					console.error(&quot;Luna: Tagging failed.&quot;, error);
					mw.notify(&quot;Luna: Tagging failed. See the console for details.&quot;);
				}
				
			}
		});
	}
});
// &lt;/nowiki&gt;</text>
      <sha1>qof3c5jwxy7q0tmqwfx1k4kjnh40qmh</sha1>
    </revision>
    <revision>
      <id>4676680</id>
      <parentid>4676676</parentid>
      <timestamp>2026-10-18T03:59:35Z</timestamp>
      <contributor>
        <username>JJPMaster</username>
        <id>3095725</id>
      </contributor>
      <comment>disabling patrol features temporarily</comment>
      <origin>4676680</origin>
      <model>javascript</model>
      <format>text/javascript</format>
      <text bytes="4658" sha1="iowiuc0h1drynhrfvsxd3vly1agx4kg" xml:space="preserve">// &lt;nowiki&gt;
var parsedTitle = mw.config.get(&quot;wgPageName&quot;).replace(/_/g, &quot; &quot;);
(() =&gt; {
	if (mw.config.get(&quot;wgArticleId&quot;)) {
		var porty = window.addLunaLink({
			id: &quot;luna-ctp&quot;,
			href: &quot;#&quot;,
			text: &quot;Tag (improvement)&quot;,
			tooltip: 'Tag this page for maintenance or improvement',
			onClick: () =&gt; { 
				$(&quot;#CTPdialog&quot;).dialog({ title: &quot;Tag this page for maintenance or improvement&quot;, height: &quot;auto&quot;, width: &quot;auto&quot; })
			}
		});
	}
	// if (window.isPatroller)	{
	// 	var porty2 = window.addLunaLink({
	// 		id: &quot;luna-rev&quot;,
	// 		href: &quot;#&quot;,
	// 		text: &quot;Review&quot;,
	// 		tooltip: &quot;Mark this page as reviewed&quot;,
	// 		onClick: async () =&gt; {
	// 			await doThePatrol(true); 
	// 			mw.notify(&quot;Luna:\nThe page has been marked as patrolled. Reloading...&quot;);
	// 			setTimeout(() =&gt; window.location.reload(), 2000);
	// 		}
	// 	});
	// }
})(); 

$(() =&gt; {
	if (mw.config.get(&quot;wgArticleId&quot;) !== 0) {
		$(&quot;#bodyContent&quot;).append(`
		&lt;div id=&quot;CTPdialog&quot;&gt;
			How would you like to tag this page? &lt;br /&gt;
			&lt;select name=&quot;CTPtagReason&quot; id=&quot;CTPtagReason&quot;&gt;
				&lt;option&gt;Select the template&lt;/option&gt;
				&lt;option id=&quot;qr-em&quot;&gt;Query (test)&lt;/option&gt;
				&lt;option id=&quot;qr-dup&quot;&gt;Query (duplicate)&lt;/option&gt;
				&lt;option id=&quot;qr-twwp&quot;&gt;Query (cut-and-paste transwiki)&lt;/option&gt;
				&lt;option id=&quot;qr-scope&quot;&gt;Query (out of scope)&lt;/option&gt;
				&lt;option id=&quot;s-twwp-2&quot;&gt;Dewikify, bookify, adopt&lt;/option&gt;
				&lt;option id=&quot;attention&quot;&gt;Attention&lt;/option&gt;
				&lt;option id=&quot;cleanup&quot;&gt;Cleanup&lt;/option&gt;
				&lt;option id=&quot;unreferenced&quot;&gt;Unreferenced&lt;/option&gt;
				&lt;option id=&quot;formatting&quot;&gt;Formatting&lt;/option&gt;
				&lt;option id=&quot;copyedit&quot;&gt;Copy edit&lt;/option&gt;
				&lt;option id=&quot;outdated&quot;&gt;Outdated&lt;/option&gt;
				&lt;option id=&quot;stub&quot;&gt;Stub&lt;/option&gt;
		    &lt;/select&gt;
		    &lt;!--&lt;span style=&quot;display: block;&quot;&gt;&lt;input type=&quot;checkbox&quot; id=&quot;patrolMark&quot; class=&quot;patrolMark&quot; name=&quot;patrolMark&quot; /&gt;&lt;label class=&quot;patrolMark&quot; for=&quot;patrolMark&quot;&gt;Mark as patrolled&lt;/label&gt;&lt;/span&gt;--&gt;
		    &lt;input type=&quot;checkbox&quot; id=&quot;notifyAuthor&quot; name=&quot;notifyAuthor&quot; checked /&gt;&lt;label for=&quot;notifyAuthor&quot;&gt;Notify page author&lt;/label&gt;&lt;br /&gt;
		    &lt;button type=&quot;button&quot; id=&quot;addTag&quot;&gt;Add tag&lt;/button&gt;&lt;/div&gt;
		`);
		(async () =&gt; {
			if (await waitForPreferences()) {
				for (var [i, j] of Object.entries(Luna.myPreferences.CTP)) {
				    $(&quot;#CTPtagReason&quot;).append(`&lt;option id=&quot;${i}&quot;&gt;${j}&lt;/option&gt;`);
				}

			}
			else {
			    console.error(&quot;Luna: Preferences never fully loaded.&quot;);
			}
		})();
		//if (!window.isPatroller) $(&quot;.patrolMark&quot;).hide();
		$(&quot;#CTPdialog&quot;).hide();
		$(&quot;#addTag&quot;).click(async function() {
			var mySelect = document.getElementById(&quot;CTPtagReason&quot;);
			var critValue = mySelect.value;
			var tag = mySelect.options[mySelect.selectedIndex].id;
			var cmtAuthor;
			var queryComment;
			if ($(&quot;#notifyAuthor&quot;).prop(&quot;checked&quot;)) {
				cmtAuthor = prompt(&quot;Why are you tagging this page (press 'Cancel' to use the default reason)? This comment will also be sent to the author of the page.&quot;) || &quot;&quot;;
				queryComment = cmtAuthor;
			}
			else if (tag == &quot;qr-em&quot;) {
				queryComment = prompt(&quot;Why are you querying this page (press 'Cancel' to use the default reason)?&quot;) || &quot;&quot;;
			}
			
			if(critValue == &quot;Select the template&quot;) {
				alert(&quot;You must select a template.&quot;);
				return;
			}
			else {
				var criterion;
				var finalTag;
				if (tag.startsWith(&quot;s-&quot;)) {
					tag = &quot;subst:&quot; + tag.slice(2);
				}

				// if ($(&quot;#patrolMark&quot;).prop(&quot;checked&quot;)) {
				// 	await doThePatrol(false);
				// }
				criterion = `Adding {{${tag}}} tag`;
				finalTag = tag != &quot;qr-em&quot; ? tag : tag + `|1=${queryComment}`;
				var params = {
					action: 'edit',
					prependtext: `{{${finalTag}}}\n`,
					title: parsedTitle,
					summary: criterion,
					tags: &quot;Luna&quot;,
					format: 'json'
				},
				api = new mw.Api();

				try {
					var data = await api.postWithToken( 'csrf', params )
					console.log( data );
					
					if ($(&quot;#notifyAuthor&quot;).prop(&quot;checked&quot;)) {
						params = {
							action: 'edit',
							appendtext: `\n{{subst:User:JJPMaster/CurateThisPage/authorMsg|title=${parsedTitle}|tag=${finalTag}|username=${mw.config.get(&quot;wgUserName&quot;)}|comment=${cmtAuthor ? cmtAuthor : &quot;&quot;}}}`,
							title: `User_talk:${await getAuthor()}`,
							summary: &quot;Notifying author about page tagging&quot;,
							tags: &quot;Luna&quot;,
							format: 'json'
						}
						api = new mw.Api();
						data = await api.postWithToken( 'csrf', params )
						console.log( data );
					}
					mw.notify(&quot;Luna:\nThe tag has been added. Reloading...&quot;);
					setTimeout(() =&gt; window.location.reload(), 2000);
				}
				catch (error) {
					console.error(&quot;Luna: Tagging failed.&quot;, error);
					mw.notify(&quot;Luna: Tagging failed. See the console for details.&quot;);
				}
				
			}
		});
	}
});
// &lt;/nowiki&gt;</text>
      <sha1>iowiuc0h1drynhrfvsxd3vly1agx4kg</sha1>
    </revision>
  </page>
  <page>
    <title>User:JJPMaster/luna/patrol.js</title>
    <ns>2</ns>
    <id>470955</id>
    <revision>
      <id>4676669</id>
      <parentid>4662646</parentid>
      <timestamp>2026-10-18T03:08:40Z</timestamp>
      <contributor>
        <username>JJPMaster</username>
        <id>3095725</id>
      </contributor>
      <comment>migrating to patrol</comment>
      <origin>4676669</origin>
      <model>javascript</model>
      <format>text/javascript</format>
      <text bytes="1664" sha1="pyczioiwam86wk5bqlmo6q4zg7xxujh" xml:space="preserve">// &lt;nowiki&gt;
async function getAuthor() {
	var par = {
        action: 'query',
        prop: 'revisions',
        titles: mw.config.get(&quot;wgPageName&quot;).replace(/_/g, &quot; &quot;),
        rvprop: 'user',
        rvdir: 'newer',
        rvlimit: 1,
        format: 'json'
    },
    api = new mw.Api();
	const data = await api.get( par );
	return Object.values(data.query.pages)[0].revisions[0].user;
}
async function getRevid() {
	var params = {
	        action: 'query',
	        prop: 'revisions',
	        titles: mw.config.get(&quot;wgPageName&quot;),
	        rvprop: 'ids',
	        rvlimit: 1,
	        format: 'json'
	    },
	    api = new mw.Api();
	
	const data = await api.get(params);
	return Object.values(data.query.pages)[0].revisions[0].revid;
}
async function doThePatrol(commt) {
	var cmt;
	if (commt) cmt = prompt(&quot;Leave a comment for the author (press 'Cancel' for no comment).&quot;);
	var params2 = {
	        action: 'patrol',
	        revid: await getRevid(),
			tags: &quot;Luna&quot;,
	        format: 'json'
	    },
	    api = new mw.Api();
	
	var data = await api.postWithToken( 'csrf', params2 )
	console.log( data ); 
	if(cmt) {
		await leaveComment(cmt, true);
	}
	
}
async function leaveComment(comment, edit) {
	if (edit) {
		var params2 = {
		        action: 'edit',
		        title: `User_talk:${await getAuthor()}`,
		        appendtext: `\n{{SUBST:User:JJPMaster/CurateThisPage/comment|comment=${comment}}}`,
		        summary: 'Adding comment after reviewing page',
				tags: &quot;Luna&quot;,
		        format: 'json'
		    },
		    api = new mw.Api();
		
		var data = await api.postWithToken( 'csrf', params2 )
		console.log( data ); 
	}
	return comment;
}
// &lt;/nowiki&gt;</text>
      <sha1>pyczioiwam86wk5bqlmo6q4zg7xxujh</sha1>
    </revision>
    <revision>
      <id>4676674</id>
      <parentid>4676669</parentid>
      <timestamp>2026-10-18T03:13:12Z</timestamp>
      <contributor>
        <username>JJPMaster</username>
        <id>3095725</id>
      </contributor>
      <minor />
      <comment>JJPMaster moved page [[User:JJPMaster/CurateThisPage/review.js]] to [[User:JJPMaster/luna/patrol.js]]: migration</comment>
      <origin>4676669</origin>
      <model>javascript</model>
      <format>text/javascript</format>
      <text bytes="1664" sha1="pyczioiwam86wk5bqlmo6q4zg7xxujh" xml:space="preserve">// &lt;nowiki&gt;
async function getAuthor() {
	var par = {
        action: 'query',
        prop: 'revisions',
        titles: mw.config.get(&quot;wgPageName&quot;).replace(/_/g, &quot; &quot;),
        rvprop: 'user',
        rvdir: 'newer',
        rvlimit: 1,
        format: 'json'
    },
    api = new mw.Api();
	const data = await api.get( par );
	return Object.values(data.query.pages)[0].revisions[0].user;
}
async function getRevid() {
	var params = {
	        action: 'query',
	        prop: 'revisions',
	        titles: mw.config.get(&quot;wgPageName&quot;),
	        rvprop: 'ids',
	        rvlimit: 1,
	        format: 'json'
	    },
	    api = new mw.Api();
	
	const data = await api.get(params);
	return Object.values(data.query.pages)[0].revisions[0].revid;
}
async function doThePatrol(commt) {
	var cmt;
	if (commt) cmt = prompt(&quot;Leave a comment for the author (press 'Cancel' for no comment).&quot;);
	var params2 = {
	        action: 'patrol',
	        revid: await getRevid(),
			tags: &quot;Luna&quot;,
	        format: 'json'
	    },
	    api = new mw.Api();
	
	var data = await api.postWithToken( 'csrf', params2 )
	console.log( data ); 
	if(cmt) {
		await leaveComment(cmt, true);
	}
	
}
async function leaveComment(comment, edit) {
	if (edit) {
		var params2 = {
		        action: 'edit',
		        title: `User_talk:${await getAuthor()}`,
		        appendtext: `\n{{SUBST:User:JJPMaster/CurateThisPage/comment|comment=${comment}}}`,
		        summary: 'Adding comment after reviewing page',
				tags: &quot;Luna&quot;,
		        format: 'json'
		    },
		    api = new mw.Api();
		
		var data = await api.postWithToken( 'csrf', params2 )
		console.log( data ); 
	}
	return comment;
}
// &lt;/nowiki&gt;</text>
      <sha1>pyczioiwam86wk5bqlmo6q4zg7xxujh</sha1>
    </revision>
    <revision>
      <id>4676677</id>
      <parentid>4676674</parentid>
      <timestamp>2026-10-18T03:21:49Z</timestamp>
      <contributor>
        <username>JJPMaster</username>
        <id>3095725</id>
      </contributor>
      <comment>different kind of token</comment>
      <origin>4676677</origin>
      <model>javascript</model>
      <format>text/javascript</format>
      <text bytes="1666" sha1="8zicb5t0t41vw3s4mdbdbv0o04dmfxl" xml:space="preserve">// &lt;nowiki&gt;
async function getAuthor() {
	var par = {
        action: 'query',
        prop: 'revisions',
        titles: mw.config.get(&quot;wgPageName&quot;).replace(/_/g, &quot; &quot;),
        rvprop: 'user',
        rvdir: 'newer',
        rvlimit: 1,
        format: 'json'
    },
    api = new mw.Api();
	const data = await api.get( par );
	return Object.values(data.query.pages)[0].revisions[0].user;
}
async function getRevid() {
	var params = {
	        action: 'query',
	        prop: 'revisions',
	        titles: mw.config.get(&quot;wgPageName&quot;),
	        rvprop: 'ids',
	        rvlimit: 1,
	        format: 'json'
	    },
	    api = new mw.Api();
	
	const data = await api.get(params);
	return Object.values(data.query.pages)[0].revisions[0].revid;
}
async function doThePatrol(commt) {
	var cmt;
	if (commt) cmt = prompt(&quot;Leave a comment for the author (press 'Cancel' for no comment).&quot;);
	var params2 = {
	        action: 'patrol',
	        revid: await getRevid(),
			tags: &quot;Luna&quot;,
	        format: 'json'
	    },
	    api = new mw.Api();
	
	var data = await api.postWithToken( 'patrol', params2 )
	console.log( data ); 
	if(cmt) {
		await leaveComment(cmt, true);
	}
	
}
async function leaveComment(comment, edit) {
	if (edit) {
		var params2 = {
		        action: 'edit',
		        title: `User_talk:${await getAuthor()}`,
		        appendtext: `\n{{SUBST:User:JJPMaster/CurateThisPage/comment|comment=${comment}}}`,
		        summary: 'Adding comment after reviewing page',
				tags: &quot;Luna&quot;,
		        format: 'json'
		    },
		    api = new mw.Api();
		
		var data = await api.postWithToken( 'csrf', params2 )
		console.log( data ); 
	}
	return comment;
}
// &lt;/nowiki&gt;</text>
      <sha1>8zicb5t0t41vw3s4mdbdbv0o04dmfxl</sha1>
    </revision>
  </page>
  <page>
    <title>User:JJPMaster (bot)/markAdmins-Data.json</title>
    <ns>2</ns>
    <id>471107</id>
    <revision>
      <id>4676564</id>
      <parentid>4676440</parentid>
      <timestamp>2026-10-17T17:49:18Z</timestamp>
      <contributor>
        <username>JJPMaster (bot)</username>
        <id>3488561</id>
      </contributor>
      <minor />
      <comment>Bot: Updating markAdmins data</comment>
      <origin>4676564</origin>
      <model>json</model>
      <format>application/json</format>
      <text bytes="28774" sha1="kgduz67tatvlqz62w9rj2rbanfp48gu" xml:space="preserve">{
	&quot;.snoopy.&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;1234qwer1234qwer4&quot;: [
		&quot;patroller&quot;,
		&quot;steward&quot;
	],
	&quot;1997kB&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;patroller&quot;
	],
	&quot;1F616EMO&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;1exec1&quot;: [
		&quot;transwiki&quot;
	],
	&quot;20041027 tatsu&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;2005-Fan&quot;: [
		&quot;transwiki&quot;,
		&quot;patroller&quot;,
		&quot;uploader&quot;
	],
	&quot;331dot&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;3MMPEYTON&quot;: [
		&quot;patroller&quot;
	],
	&quot;511KeV&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;94rain&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;patroller&quot;
	],
	&quot;A Sulaiman Z&quot;: [
		&quot;patroller&quot;
	],
	&quot;A09&quot;: [
		&quot;steward&quot;
	],
	&quot;AFBorchert&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;AIProf&quot;: [
		&quot;patroller&quot;
	],
	&quot;AManWithNoPlan&quot;: [
		&quot;patroller&quot;
	],
	&quot;ATannedBurger&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Aafi&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Acalamari&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Adalvis&quot;: [
		&quot;patroller&quot;
	],
	&quot;Adavyd&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Adrignola&quot;: [
		&quot;patroller&quot;
	],
	&quot;Aelxen&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Affe2011&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Agnerf&quot;: [
		&quot;uploader&quot;
	],
	&quot;Agusbou2015&quot;: [
		&quot;patroller&quot;
	],
	&quot;Ahecht&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Ahonc&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Ajraddatz&quot;: [
		&quot;patroller&quot;,
		&quot;steward&quot;
	],
	&quot;Aka&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Albertoleoncio&quot;: [
		&quot;steward&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Albmont&quot;: [
		&quot;patroller&quot;
	],
	&quot;Alchimista&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Alexey Vazhnov&quot;: [
		&quot;patroller&quot;
	],
	&quot;Alexlatham96&quot;: [
		&quot;patroller&quot;
	],
	&quot;Alextejthompson&quot;: [
		&quot;patroller&quot;
	],
	&quot;Alison&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;AmandaNP&quot;: [
		&quot;steward&quot;
	],
	&quot;Amcgail&quot;: [
		&quot;patroller&quot;
	],
	&quot;Ameisenigel&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;,
		&quot;ombuds&quot;,
		&quot;patroller&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Amire80&quot;: [
		&quot;global-sysop&quot;
	],
	&quot;Anachronist&quot;: [
		&quot;patroller&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Ancient9983&quot;: [
		&quot;patroller&quot;
	],
	&quot;Andriy.v&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Anil Shaligram&quot;: [
		&quot;patroller&quot;
	],
	&quot;Antanana&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Antandrus&quot;: [
		&quot;patroller&quot;
	],
	&quot;AntiCompositeNumber&quot;: [
		&quot;steward&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Aplucas0703&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Aqurs1&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;global-sysop&quot;
	],
	&quot;AramilFeraxa&quot;: [
		&quot;steward&quot;
	],
	&quot;Arcticocean&quot;: [
		&quot;ombuds&quot;
	],
	&quot;ArdentPerf&quot;: [
		&quot;uploader&quot;
	],
	&quot;Arian&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Arlen22&quot;: [
		&quot;transwiki&quot;
	],
	&quot;Armchair&quot;: [
		&quot;patroller&quot;
	],
	&quot;Arrow303&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Artoria2e5&quot;: [
		&quot;patroller&quot;
	],
	&quot;Arturoiochoam&quot;: [
		&quot;patroller&quot;
	],
	&quot;Atcovi&quot;: [
		&quot;sysop&quot;,
		&quot;global-rollbacker&quot;
	],
	&quot;Atiedebee&quot;: [
		&quot;patroller&quot;
	],
	&quot;Atlas.Spheres&quot;: [
		&quot;patroller&quot;
	],
	&quot;Atsme&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Auremel&quot;: [
		&quot;patroller&quot;
	],
	&quot;Avraham&quot;: [
		&quot;global-renamer&quot;,
		&quot;patroller&quot;
	],
	&quot;B.Korlah&quot;: [
		&quot;patroller&quot;
	],
	&quot;BRPever&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;
	],
	&quot;Baiji&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Bakasakali&quot;: [
		&quot;patroller&quot;
	],
	&quot;Barras&quot;: [
		&quot;steward&quot;
	],
	&quot;Base&quot;: [
		&quot;steward&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Bastique&quot;: [
		&quot;patroller&quot;
	],
	&quot;Bautsch&quot;: [
		&quot;patroller&quot;
	],
	&quot;Beetstra&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Bencemac&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Benjamin J. Burger&quot;: [
		&quot;patroller&quot;
	],
	&quot;Bentbracke&quot;: [
		&quot;patroller&quot;
	],
	&quot;Bigdelboy&quot;: [
		&quot;transwiki&quot;
	],
	&quot;Billinghurst&quot;: [
		&quot;patroller&quot;
	],
	&quot;Billymac00&quot;: [
		&quot;patroller&quot;
	],
	&quot;Biplab Anand&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;
	],
	&quot;Bluerasberry&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Bobby Cohn&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Bodhisattwa&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Borhan&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Boris1951zz&quot;: [
		&quot;patroller&quot;
	],
	&quot;Brewster239&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Bridget&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Bsadowski1&quot;: [
		&quot;patroller&quot;,
		&quot;steward&quot;
	],
	&quot;Buncic&quot;: [
		&quot;patroller&quot;
	],
	&quot;Bunnypranav&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;BurakD53&quot;: [
		&quot;patroller&quot;
	],
	&quot;Bykim2012&quot;: [
		&quot;patroller&quot;
	],
	&quot;Cabayi&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Captain-tucker&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Caro de Segeda&quot;: [
		&quot;patroller&quot;
	],
	&quot;Cedar101&quot;: [
		&quot;patroller&quot;
	],
	&quot;Champion&quot;: [
		&quot;patroller&quot;
	],
	&quot;Chaojidage&quot;: [
		&quot;patroller&quot;
	],
	&quot;Chaotic Enby&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Charidri&quot;: [
		&quot;patroller&quot;
	],
	&quot;Charles Jeffrey Danoff&quot;: [
		&quot;patroller&quot;
	],
	&quot;CharlesHoffman&quot;: [
		&quot;patroller&quot;
	],
	&quot;Chescargot&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Chi Sigma&quot;: [
		&quot;patroller&quot;
	],
	&quot;Chinmayee Mishra&quot;: [
		&quot;ombuds&quot;
	],
	&quot;Chongkian&quot;: [
		&quot;patroller&quot;
	],
	&quot;Chriswaterguy&quot;: [
		&quot;patroller&quot;
	],
	&quot;Church of emacs&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Ciell&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Cintilo&quot;: [
		&quot;patroller&quot;
	],
	&quot;Circuit-fantasist&quot;: [
		&quot;patroller&quot;
	],
	&quot;Civvì&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;
	],
	&quot;Cnrowley&quot;: [
		&quot;patroller&quot;
	],
	&quot;CoconutOctopus&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Codename Noreste&quot;: [
		&quot;sysop&quot;,
		&quot;global-rollbacker&quot;,
		&quot;interface-admin&quot;
	],
	&quot;Comp.arch&quot;: [
		&quot;patroller&quot;
	],
	&quot;Conan&quot;: [
		&quot;patroller&quot;
	],
	&quot;Cormullion&quot;: [
		&quot;patroller&quot;
	],
	&quot;Count Count&quot;: [
		&quot;steward&quot;
	],
	&quot;Courcelles&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;CptViraj&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;global-sysop&quot;
	],
	&quot;Cremastra&quot;: [
		&quot;patroller&quot;
	],
	&quot;Crystal East&quot;: [
		&quot;patroller&quot;
	],
	&quot;Cyberpower678&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Céréales Killer&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;D1n05aur5 4ever&quot;: [
		&quot;patroller&quot;
	],
	&quot;DARIO SEVERI&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;
	],
	&quot;DCB&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;DERDAKI ILIAS&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;DVD206&quot;: [
		&quot;patroller&quot;
	],
	&quot;DaB.&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;DaGizza&quot;: [
		&quot;patroller&quot;
	],
	&quot;Dan Polansky&quot;: [
		&quot;patroller&quot;
	],
	&quot;Danielravennest&quot;: [
		&quot;patroller&quot;
	],
	&quot;Daniuu&quot;: [
		&quot;steward&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;DannyS712&quot;: [
		&quot;patroller&quot;
	],
	&quot;Darklilac&quot;: [
		&quot;patroller&quot;
	],
	&quot;Darrelljon&quot;: [
		&quot;patroller&quot;
	],
	&quot;DarwIn&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Dave Braunschweig&quot;: [
		&quot;patroller&quot;
	],
	&quot;DavidCary&quot;: [
		&quot;patroller&quot;
	],
	&quot;DavidCota64&quot;: [
		&quot;patroller&quot;
	],
	&quot;DavidLevinson&quot;: [
		&quot;patroller&quot;
	],
	&quot;Dayshade&quot;: [
		&quot;patroller&quot;
	],
	&quot;Deepfriedokra&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;DejaVu&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Dennisblu&quot;: [
		&quot;uploader&quot;
	],
	&quot;Der-Wir-Ing&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;DerHexer&quot;: [
		&quot;patroller&quot;,
		&quot;steward&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Designermadsen&quot;: [
		&quot;patroller&quot;
	],
	&quot;Deu&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Dexxor&quot;: [
		&quot;patroller&quot;
	],
	&quot;Dezedien&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Didym&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Dirk Hünniger&quot;: [
		&quot;patroller&quot;
	],
	&quot;Divinations&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Dlrohrer2003&quot;: [
		&quot;patroller&quot;
	],
	&quot;Doc Taxon&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Doctorxgc&quot;: [
		&quot;patroller&quot;
	],
	&quot;Dom walden&quot;: [
		&quot;patroller&quot;
	],
	&quot;DoubleGrazing&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Dr-Taher&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Drummingman&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;DuLithgow&quot;: [
		&quot;patroller&quot;
	],
	&quot;Dungodung&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;DustDFG&quot;: [
		&quot;patroller&quot;
	],
	&quot;Dyolf77&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;EPIC&quot;: [
		&quot;steward&quot;
	],
	&quot;Edit filter&quot;: [
		&quot;sysop&quot;
	],
	&quot;Edriiic&quot;: [
		&quot;patroller&quot;
	],
	&quot;Effeietsanders&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;EggRoll97&quot;: [
		&quot;patroller&quot;
	],
	&quot;Eihel&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Ejs-80&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Elcobbola&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Elli&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Ellywa&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Elmacenderesi&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Elton&quot;: [
		&quot;patroller&quot;,
		&quot;steward&quot;
	],
	&quot;Emha&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Encik Tekateki&quot;: [
		&quot;patroller&quot;
	],
	&quot;Erik Baas&quot;: [
		&quot;patroller&quot;
	],
	&quot;Eta Carinae&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Euphydryas&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Ewen&quot;: [
		&quot;patroller&quot;
	],
	&quot;Exusiai&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Ezarate&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Fabartus&quot;: [
		&quot;uploader&quot;
	],
	&quot;Faendalimas&quot;: [
		&quot;ombuds&quot;
	],
	&quot;Faster than Thunder&quot;: [
		&quot;patroller&quot;
	],
	&quot;Fathoms Below&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Fcorthay&quot;: [
		&quot;patroller&quot;
	],
	&quot;Federhalter&quot;: [
		&quot;patroller&quot;
	],
	&quot;Fehufanga&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;
	],
	&quot;Fephisto&quot;: [
		&quot;patroller&quot;
	],
	&quot;Ferien&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;FlightTime&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Fluffernutter&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;FlyingAce&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Frozen Wind&quot;: [
		&quot;transwiki&quot;
	],
	&quot;Ftiercel&quot;: [
		&quot;patroller&quot;
	],
	&quot;Galahad&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Gampe&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Ganímedes&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Gary Dorman Wiggins&quot;: [
		&quot;uploader&quot;
	],
	&quot;Geagea&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Geofferybard&quot;: [
		&quot;transwiki&quot;
	],
	&quot;GerbenRienk&quot;: [
		&quot;patroller&quot;
	],
	&quot;Gerges&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;
	],
	&quot;Gifnk dlm 2020&quot;: [
		&quot;uploader&quot;
	],
	&quot;Glane23&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;GoreyCat&quot;: [
		&quot;patroller&quot;
	],
	&quot;GorillaWarfare&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Gpkp&quot;: [
		&quot;patroller&quot;
	],
	&quot;Greatswrd&quot;: [
		&quot;patroller&quot;
	],
	&quot;GreenC&quot;: [
		&quot;patroller&quot;
	],
	&quot;Greenman&quot;: [
		&quot;patroller&quot;
	],
	&quot;Grin&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Guy vandegrift&quot;: [
		&quot;patroller&quot;
	],
	&quot;HakanIST&quot;: [
		&quot;patroller&quot;,
		&quot;steward&quot;
	],
	&quot;Hamish&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Hanay&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Haoreima&quot;: [
		&quot;patroller&quot;
	],
	&quot;Harry Wood&quot;: [
		&quot;patroller&quot;
	],
	&quot;Harrybrowne1986&quot;: [
		&quot;patroller&quot;
	],
	&quot;Hasley&quot;: [
		&quot;patroller&quot;
	],
	&quot;Hazard-SJ&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;HenkvD&quot;: [
		&quot;patroller&quot;
	],
	&quot;Holder&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;
	],
	&quot;Hoo man&quot;: [
		&quot;patroller&quot;,
		&quot;steward&quot;
	],
	&quot;HouseBlaster&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Hskeet&quot;: [
		&quot;uploader&quot;
	],
	&quot;Htm&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Humaira Ali&quot;: [
		&quot;patroller&quot;
	],
	&quot;Huntertur&quot;: [
		&quot;patroller&quot;
	],
	&quot;Hydriz&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;IB Muazzam&quot;: [
		&quot;patroller&quot;
	],
	&quot;Ibrahim.ID&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Icodense&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;
	],
	&quot;Idavidmiller&quot;: [
		&quot;patroller&quot;
	],
	&quot;Ijon&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Iluvatar&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Inferno986return&quot;: [
		&quot;patroller&quot;
	],
	&quot;Infinite0694&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;
	],
	&quot;Internoob&quot;: [
		&quot;transwiki&quot;
	],
	&quot;Ish ishwar&quot;: [
		&quot;patroller&quot;
	],
	&quot;It-is-Truly-Meet&quot;: [
		&quot;patroller&quot;
	],
	&quot;ItsNyoty&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Itswikisam&quot;: [
		&quot;patroller&quot;
	],
	&quot;Itti&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Ixfd64&quot;: [
		&quot;patroller&quot;
	],
	&quot;J ansari&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;JBW&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;JCrue&quot;: [
		&quot;patroller&quot;
	],
	&quot;JJMC89&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;JJPMaster&quot;: [
		&quot;sysop&quot;,
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;interface-admin&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Jack Frost&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;JackBot&quot;: [
		&quot;patroller&quot;
	],
	&quot;JackPotte&quot;: [
		&quot;sysop&quot;,
		&quot;interface-admin&quot;
	],
	&quot;Jafeluv&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Jake Park&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Jamesofur&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Jan Myšák&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Janbery&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Janpha&quot;: [
		&quot;patroller&quot;
	],
	&quot;Jasper Deng&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;JavaHurricane&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;patroller&quot;
	],
	&quot;Jay Bolero&quot;: [
		&quot;patroller&quot;
	],
	&quot;Jcb&quot;: [
		&quot;patroller&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Jcwf&quot;: [
		&quot;patroller&quot;
	],
	&quot;Jeff G.&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Jeff1138&quot;: [
		&quot;patroller&quot;
	],
	&quot;Jellysandwich0&quot;: [
		&quot;patroller&quot;
	],
	&quot;Jessephu&quot;: [
		&quot;patroller&quot;
	],
	&quot;Jianhui67&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;patroller&quot;
	],
	&quot;JimKillock&quot;: [
		&quot;patroller&quot;
	],
	&quot;Jimmy Xu&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Jmdeschamps&quot;: [
		&quot;uploader&quot;
	],
	&quot;Jnanaranjan sahu&quot;: [
		&quot;ombuds&quot;
	],
	&quot;Johannnes89&quot;: [
		&quot;steward&quot;
	],
	&quot;Jon Harald Søby&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Jon Kolbert&quot;: [
		&quot;steward&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Jordan Brown&quot;: [
		&quot;patroller&quot;
	],
	&quot;Josve05a&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Jtneill&quot;: [
		&quot;patroller&quot;
	],
	&quot;Jules*&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Jumark27&quot;: [
		&quot;patroller&quot;
	],
	&quot;JustTheFacts33&quot;: [
		&quot;patroller&quot;
	],
	&quot;Justlettersandnumbers&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;K6ka&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;
	],
	&quot;Kadı&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Kai Burghardt&quot;: [
		&quot;patroller&quot;
	],
	&quot;Kaltenmeyer&quot;: [
		&quot;patroller&quot;
	],
	&quot;Kambai Akau&quot;: [
		&quot;patroller&quot;
	],
	&quot;Kanjy&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Karosent&quot;: [
		&quot;patroller&quot;
	],
	&quot;Kayau&quot;: [
		&quot;transwiki&quot;
	],
	&quot;Kelti&quot;: [
		&quot;patroller&quot;
	],
	&quot;Killarnee&quot;: [
		&quot;patroller&quot;
	],
	&quot;King of Hearts&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Kingaustin07&quot;: [
		&quot;patroller&quot;
	],
	&quot;Kingofnuthin&quot;: [
		&quot;patroller&quot;
	],
	&quot;Kirito&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Kittycataclysm&quot;: [
		&quot;sysop&quot;
	],
	&quot;Kj cheetham&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Klaas van Buiten&quot;: [
		&quot;patroller&quot;
	],
	&quot;Knittedbees&quot;: [
		&quot;transwiki&quot;
	],
	&quot;Koavf&quot;: [
		&quot;sysop&quot;,
		&quot;global-rollbacker&quot;
	],
	&quot;KonstantinaG07&quot;: [
		&quot;patroller&quot;,
		&quot;steward&quot;
	],
	&quot;KrakatoaKatie&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Krd&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Krdbot&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Krinkle&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Kropotkine 113&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Kruusamägi&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Kwamikagami&quot;: [
		&quot;patroller&quot;
	],
	&quot;Kızıl&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;L10nM4st3r&quot;: [
		&quot;patroller&quot;
	],
	&quot;LM.CR&quot;: [
		&quot;patroller&quot;
	],
	&quot;LR0725&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;
	],
	&quot;Ladislav&quot;: [
		&quot;patroller&quot;
	],
	&quot;Ladsgroup&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Ladybug62&quot;: [
		&quot;patroller&quot;
	],
	&quot;Larsnooden&quot;: [
		&quot;patroller&quot;
	],
	&quot;Leaderboard&quot;: [
		&quot;sysop&quot;,
		&quot;global-renamer&quot;,
		&quot;interface-admin&quot;
	],
	&quot;Lechatjaune&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Lemonaka&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Lentokonefani&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Leonard64&quot;: [
		&quot;uploader&quot;
	],
	&quot;Leonidlednev&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Lesless&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Leyo&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Liao&quot;: [
		&quot;patroller&quot;
	],
	&quot;Libperry&quot;: [
		&quot;patroller&quot;
	],
	&quot;Litlok&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Little Sunshine&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;LodestarChariot2&quot;: [
		&quot;patroller&quot;
	],
	&quot;Lofty abyss&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Lomita&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Lovepeacejoy404&quot;: [
		&quot;patroller&quot;
	],
	&quot;Lp0 on fire&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Ludovicocaldara&quot;: [
		&quot;uploader&quot;
	],
	&quot;Lvova&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;M7&quot;: [
		&quot;steward&quot;
	],
	&quot;MARKELLOS&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;MBq&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;MF-Warburg&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;
	],
	&quot;MGA73&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;MS Sakib&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Mabdul&quot;: [
		&quot;transwiki&quot;,
		&quot;uploader&quot;
	],
	&quot;Mahagaja&quot;: [
		&quot;patroller&quot;
	],
	&quot;Maire&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Malarz pl&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Manchiu&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;ManuelGR&quot;: [
		&quot;patroller&quot;
	],
	&quot;MarcGarver&quot;: [
		&quot;sysop&quot;,
		&quot;checkuser&quot;,
		&quot;steward&quot;
	],
	&quot;Marcus Cyron&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Martin Kraus&quot;: [
		&quot;patroller&quot;
	],
	&quot;Martin Urbanec&quot;: [
		&quot;patroller&quot;,
		&quot;steward&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Masti&quot;: [
		&quot;steward&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;MathXplore&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;patroller&quot;
	],
	&quot;Matrix&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Matsievsky&quot;: [
		&quot;patroller&quot;
	],
	&quot;Max&quot;: [
		&quot;global-renamer&quot;,
		&quot;global-sysop&quot;
	],
	&quot;Max Milas&quot;: [
		&quot;patroller&quot;
	],
	&quot;Maximillion Pegasus&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;patroller&quot;
	],
	&quot;Mazbel&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Mbch331&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Mbrickn&quot;: [
		&quot;transwiki&quot;,
		&quot;patroller&quot;
	],
	&quot;MdsShakil&quot;: [
		&quot;steward&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Me Lendroz&quot;: [
		&quot;patroller&quot;
	],
	&quot;Meanmicio&quot;: [
		&quot;patroller&quot;
	],
	&quot;MediaKyle&quot;: [
		&quot;patroller&quot;
	],
	&quot;Mehman&quot;: [
		&quot;ombuds&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Melos&quot;: [
		&quot;steward&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;MemicznyJanusz&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Mercy&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Mfield&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;MichaelFrey&quot;: [
		&quot;patroller&quot;
	],
	&quot;Michaelbluett&quot;: [
		&quot;uploader&quot;
	],
	&quot;Mido&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;MiiCii&quot;: [
		&quot;patroller&quot;
	],
	&quot;Mild Bill Hiccup&quot;: [
		&quot;patroller&quot;
	],
	&quot;Millbart&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Mimarx&quot;: [
		&quot;patroller&quot;
	],
	&quot;Minorax&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;,
		&quot;patroller&quot;
	],
	&quot;Mirinano&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Mithridates&quot;: [
		&quot;patroller&quot;
	],
	&quot;Mjchael&quot;: [
		&quot;patroller&quot;
	],
	&quot;Moby-Dick4000&quot;: [
		&quot;patroller&quot;
	],
	&quot;Money-lover-12345&quot;: [
		&quot;patroller&quot;
	],
	&quot;Moonriddengirl&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Morkoz&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;MrAlanKoh&quot;: [
		&quot;patroller&quot;
	],
	&quot;MrJaroslavik&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;ombuds&quot;
	],
	&quot;Msmithma&quot;: [
		&quot;patroller&quot;
	],
	&quot;MtPenguinMonster&quot;: [
		&quot;patroller&quot;
	],
	&quot;Mtarch11&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;,
		&quot;patroller&quot;
	],
	&quot;Musical Inquisit&quot;: [
		&quot;patroller&quot;
	],
	&quot;Mussklprozz&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Mvolz&quot;: [
		&quot;patroller&quot;
	],
	&quot;Mxn&quot;: [
		&quot;patroller&quot;
	],
	&quot;Mykola7&quot;: [
		&quot;steward&quot;
	],
	&quot;Mys 721tx&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;NDG&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;,
		&quot;patroller&quot;
	],
	&quot;Nadzik&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;
	],
	&quot;NahidSultan&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Nangkhan Magar&quot;: [
		&quot;patroller&quot;
	],
	&quot;Natuur12&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Nbarth&quot;: [
		&quot;patroller&quot;
	],
	&quot;Nehaoua&quot;: [
		&quot;ombuds&quot;
	],
	&quot;Nemoralis&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Neojacob&quot;: [
		&quot;patroller&quot;
	],
	&quot;Neriah&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;
	],
	&quot;NguoiDungKhongDinhDanh&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;,
		&quot;patroller&quot;
	],
	&quot;NhacNy2412&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;NicoScribe&quot;: [
		&quot;patroller&quot;
	],
	&quot;Nicole Sharp&quot;: [
		&quot;patroller&quot;
	],
	&quot;Nihonjoe&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Ninjastrikers&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Nobody60&quot;: [
		&quot;patroller&quot;
	],
	&quot;Nolispanmo&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Nonenmac&quot;: [
		&quot;patroller&quot;
	],
	&quot;Norton&quot;: [
		&quot;patroller&quot;
	],
	&quot;Nsaa&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Nthep&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;NuclearWarfare&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;OMSMike&quot;: [
		&quot;patroller&quot;
	],
	&quot;Omphalographer&quot;: [
		&quot;patroller&quot;
	],
	&quot;Ontzak&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Oshwah&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Ottawahitech&quot;: [
		&quot;patroller&quot;
	],
	&quot;PNW Raven&quot;: [
		&quot;patroller&quot;
	],
	&quot;Paloi Sciurala&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Panic2k4&quot;: [
		&quot;transwiki&quot;,
		&quot;patroller&quot;
	],
	&quot;Pathoschild&quot;: [
		&quot;patroller&quot;
	],
	&quot;PeterEasthope&quot;: [
		&quot;patroller&quot;
	],
	&quot;PhilKnight&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Phoebe&quot;: [
		&quot;patroller&quot;
	],
	&quot;PieWriter&quot;: [
		&quot;patroller&quot;
	],
	&quot;Platonides&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Pluke&quot;: [
		&quot;patroller&quot;
	],
	&quot;PlyrStar93&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Pminh141&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Poetcsw&quot;: [
		&quot;patroller&quot;
	],
	&quot;Polimerek&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Polluks&quot;: [
		&quot;patroller&quot;
	],
	&quot;Pookiyama&quot;: [
		&quot;patroller&quot;
	],
	&quot;Povigna&quot;: [
		&quot;patroller&quot;
	],
	&quot;Ppolar bear&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;
	],
	&quot;Praxidicae&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;
	],
	&quot;Primefac&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;PullUpYourSocks&quot;: [
		&quot;patroller&quot;
	],
	&quot;PurpleBuffalo&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;PurplePieman&quot;: [
		&quot;patroller&quot;
	],
	&quot;Purplebackpack89&quot;: [
		&quot;patroller&quot;
	],
	&quot;Quebecguy&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;QueerEcofeminist&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;patroller&quot;
	],
	&quot;Quinlan83&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;patroller&quot;
	],
	&quot;Qədir&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;R. Henrik Nilsson&quot;: [
		&quot;patroller&quot;
	],
	&quot;RAdimer-WMF&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Ra'ike&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Rachel&quot;: [
		&quot;patroller&quot;
	],
	&quot;Rachmat04&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;RadiX&quot;: [
		&quot;patroller&quot;,
		&quot;steward&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Rahulkepapa&quot;: [
		&quot;patroller&quot;
	],
	&quot;Randykitty&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Ray Trygstad&quot;: [
		&quot;patroller&quot;
	],
	&quot;Raymond&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Rchaswms01&quot;: [
		&quot;patroller&quot;
	],
	&quot;Rcragun&quot;: [
		&quot;patroller&quot;,
		&quot;uploader&quot;
	],
	&quot;Refcanimm&quot;: [
		&quot;patroller&quot;
	],
	&quot;Regasterios&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Reinhard Kraasch&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Renamed user 242094acfb1a5b2f08e9e78f2e021a40&quot;: [
		&quot;patroller&quot;
	],
	&quot;Renamed user 5f91ca71739b07cfce8397eed758fe13&quot;: [
		&quot;uploader&quot;
	],
	&quot;Renamed user f26394dcb19bd7bdad78f0d752896653&quot;: [
		&quot;patroller&quot;
	],
	&quot;Renvoy&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;
	],
	&quot;Reseletti&quot;: [
		&quot;patroller&quot;
	],
	&quot;Revi C.&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;ombuds&quot;,
		&quot;patroller&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Rfc1394&quot;: [
		&quot;patroller&quot;
	],
	&quot;Rgdboer&quot;: [
		&quot;patroller&quot;
	],
	&quot;Rich Farmbrough&quot;: [
		&quot;patroller&quot;
	],
	&quot;Rickstambaugh&quot;: [
		&quot;patroller&quot;
	],
	&quot;Riggwelter&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Robertsky&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Rodrigo&quot;: [
		&quot;patroller&quot;
	],
	&quot;Rodrigo.Argenton&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;RogueScholar&quot;: [
		&quot;patroller&quot;
	],
	&quot;RomaineBot&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;RonaldB&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;RoySmith&quot;: [
		&quot;ombuds&quot;
	],
	&quot;Rozzychan&quot;: [
		&quot;patroller&quot;
	],
	&quot;Rplano&quot;: [
		&quot;patroller&quot;
	],
	&quot;Rschen7754&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Rsjaffe&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Runfellow&quot;: [
		&quot;patroller&quot;
	],
	&quot;Ruthven&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Ruud Koot&quot;: [
		&quot;transwiki&quot;
	],
	&quot;Rzuwig&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;S.Marchenko&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;S8321414&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;SCP-2000&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;SHB&quot;: [
		&quot;sysop&quot;,
		&quot;steward&quot;
	],
	&quot;Sakretsu&quot;: [
		&quot;steward&quot;
	],
	&quot;Sakura emad&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Salil Kumar Mukherjee&quot;: [
		&quot;patroller&quot;
	],
	&quot;Samat&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Sammy2012&quot;: [
		&quot;patroller&quot;
	],
	&quot;Samuel.dellit&quot;: [
		&quot;patroller&quot;
	],
	&quot;Samuele2002&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;patroller&quot;
	],
	&quot;SanBonne&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Sannita&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Sargoth&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Saroj&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Sascha Lill 95&quot;: [
		&quot;patroller&quot;
	],
	&quot;Satdeep Gill&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Savh&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Sbb1413&quot;: [
		&quot;patroller&quot;
	],
	&quot;Schniggendiller&quot;: [
		&quot;steward&quot;
	],
	&quot;SchreiberBike&quot;: [
		&quot;patroller&quot;
	],
	&quot;Sebastian Wallroth&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Seewolf&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Sekidoki&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Sennecaster&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;SevenSpheres&quot;: [
		&quot;patroller&quot;
	],
	&quot;ShakespeareFan00&quot;: [
		&quot;patroller&quot;
	],
	&quot;ShifaYT&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Shira the Mogul&quot;: [
		&quot;patroller&quot;
	],
	&quot;Sigma 7&quot;: [
		&quot;patroller&quot;
	],
	&quot;Simon Peter Hughes&quot;: [
		&quot;patroller&quot;
	],
	&quot;Sinus46&quot;: [
		&quot;patroller&quot;
	],
	&quot;Sir Beluga&quot;: [
		&quot;patroller&quot;
	],
	&quot;Sir Lestaty de Lioncourt&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Sj&quot;: [
		&quot;patroller&quot;
	],
	&quot;Sjö&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;SlartibartfastT&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Slava Ukraini Heroyam Slava 123&quot;: [
		&quot;uploader&quot;
	],
	&quot;SnappyDragonPennyroyal&quot;: [
		&quot;patroller&quot;
	],
	&quot;SocialKnowledge&quot;: [
		&quot;patroller&quot;
	],
	&quot;Sotiale&quot;: [
		&quot;steward&quot;
	],
	&quot;SouthParkFan65&quot;: [
		&quot;patroller&quot;
	],
	&quot;Squasher&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Stang&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;patroller&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Steinsplitter&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Stepro&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Stilfehler&quot;: [
		&quot;patroller&quot;
	],
	&quot;Strainu&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Stryn&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;patroller&quot;
	],
	&quot;Stïnger&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Sunny Cryolite&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Superbass&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Superpes15&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;global-sysop&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Supertoff&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Superzerocool&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;SupremeUmanu&quot;: [
		&quot;patroller&quot;
	],
	&quot;Svartava&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;global-sysop&quot;,
		&quot;patroller&quot;
	],
	&quot;Sylvesterchukwu04&quot;: [
		&quot;patroller&quot;
	],
	&quot;Synoman Barris&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;transwiki&quot;
	],
	&quot;Syum90&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Syunsyunminmin&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;global-sysop&quot;,
		&quot;patroller&quot;
	],
	&quot;TTWIDEE&quot;: [
		&quot;patroller&quot;
	],
	&quot;Tahmid&quot;: [
		&quot;patroller&quot;
	],
	&quot;Taketa&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Takipoint123&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Tamzin&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Tanbiruzzaman&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;global-sysop&quot;,
		&quot;patroller&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Taoheedah&quot;: [
		&quot;patroller&quot;
	],
	&quot;TaronjaSatsuma&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Tchoř&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Tdvorak&quot;: [
		&quot;patroller&quot;
	],
	&quot;TechVindicator&quot;: [
		&quot;patroller&quot;
	],
	&quot;Tegel&quot;: [
		&quot;patroller&quot;,
		&quot;steward&quot;
	],
	&quot;Teles&quot;: [
		&quot;ombuds&quot;,
		&quot;steward&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Tem5psu&quot;: [
		&quot;patroller&quot;
	],
	&quot;TenWhile6&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;global-sysop&quot;,
		&quot;patroller&quot;
	],
	&quot;Tenshi Hinanawi&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Ternarius&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Ternera&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;global-sysop&quot;,
		&quot;patroller&quot;
	],
	&quot;Tesleemah&quot;: [
		&quot;patroller&quot;
	],
	&quot;The Squirrel Conspiracy&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;The labs&quot;: [
		&quot;patroller&quot;
	],
	&quot;TheGoodEndedHappily&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;TheSandDoctor&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Thierry Dugnolle&quot;: [
		&quot;patroller&quot;
	],
	&quot;Thomas.haslwanter&quot;: [
		&quot;patroller&quot;
	],
	&quot;Tibetologist&quot;: [
		&quot;patroller&quot;
	],
	&quot;Tigerzeng&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;TimBorgNetzWerk&quot;: [
		&quot;patroller&quot;
	],
	&quot;TommyG&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Tp42&quot;: [
		&quot;patroller&quot;
	],
	&quot;Tropicalkitty&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;patroller&quot;
	],
	&quot;Ts12rAc&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;TunnelESON&quot;: [
		&quot;sysop&quot;
	],
	&quot;Turbojet&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Turkmen&quot;: [
		&quot;patroller&quot;
	],
	&quot;Tyoyafud&quot;: [
		&quot;patroller&quot;
	],
	&quot;USSR-Slav&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Uncitoyen&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;
	],
	&quot;User01938&quot;: [
		&quot;patroller&quot;
	],
	&quot;Utcursch&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Uzume&quot;: [
		&quot;patroller&quot;
	],
	&quot;V0lkanic&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;VIGNERON&quot;: [
		&quot;steward&quot;
	],
	&quot;Varnent&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;VectorVoyager&quot;: [
		&quot;patroller&quot;
	],
	&quot;Venzz&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Veritas Sapientiae&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Vermont&quot;: [
		&quot;patroller&quot;,
		&quot;steward&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Vincent Vega&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Vladimir Solovjev&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Vogone&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;VulcanWikiEdit&quot;: [
		&quot;patroller&quot;
	],
	&quot;Waihorace&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Waldyrious&quot;: [
		&quot;patroller&quot;
	],
	&quot;Wargo&quot;: [
		&quot;patroller&quot;
	],
	&quot;Wbjimmyd&quot;: [
		&quot;patroller&quot;
	],
	&quot;WeelkyWikiReader&quot;: [
		&quot;patroller&quot;
	],
	&quot;WereSpielChequers&quot;: [
		&quot;patroller&quot;
	],
	&quot;WhatamIdoing&quot;: [
		&quot;patroller&quot;
	],
	&quot;WhitePhosphorus&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;
	],
	&quot;Whoop whoop pull up&quot;: [
		&quot;patroller&quot;
	],
	&quot;Whym&quot;: [
		&quot;patroller&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;WikiBayer&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;,
		&quot;patroller&quot;
	],
	&quot;WikiFer&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Wikimi-dhiann&quot;: [
		&quot;patroller&quot;
	],
	&quot;WillNess&quot;: [
		&quot;patroller&quot;
	],
	&quot;Wim b&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Wkee4ager&quot;: [
		&quot;patroller&quot;
	],
	&quot;Wojciech Pędzich&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Wooze&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Wutsje&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;patroller&quot;
	],
	&quot;Ww2censor&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Wüstenspringmaus&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;
	],
	&quot;XXBlackburnXx&quot;: [
		&quot;patroller&quot;,
		&quot;steward&quot;
	],
	&quot;Xandradi&quot;: [
		&quot;patroller&quot;
	],
	&quot;Xania&quot;: [
		&quot;sysop&quot;,
		&quot;checkuser&quot;
	],
	&quot;Xaosflux&quot;: [
		&quot;patroller&quot;,
		&quot;steward&quot;
	],
	&quot;XenonX3&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Xeverything11&quot;: [
		&quot;patroller&quot;,
		&quot;uploader&quot;
	],
	&quot;Xhungab&quot;: [
		&quot;patroller&quot;
	],
	&quot;Xqt&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Y-S.Ko&quot;: [
		&quot;patroller&quot;
	],
	&quot;Yahya&quot;: [
		&quot;steward&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Yamla&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Yann&quot;: [
		&quot;patroller&quot;
	],
	&quot;Yerpo&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Ymblanter&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Yvelik&quot;: [
		&quot;uploader&quot;
	],
	&quot;ZI Jony&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Zabe&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Zafer&quot;: [
		&quot;ombuds&quot;
	],
	&quot;Zetud&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Ziv&quot;: [
		&quot;patroller&quot;
	],
	&quot;Zoeannl&quot;: [
		&quot;patroller&quot;
	],
	&quot;Zsohl&quot;: [
		&quot;patroller&quot;
	],
	&quot;~riley&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Érico&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;İmmortalance&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Виктор Пинчук&quot;: [
		&quot;patroller&quot;
	],
	&quot;Всевидящий&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Д.Ильин&quot;: [
		&quot;patroller&quot;
	],
	&quot;Л.П. Джепко&quot;: [
		&quot;patroller&quot;
	],
	&quot;יהודה שמחה ולדמן&quot;: [
		&quot;patroller&quot;
	],
	&quot;מקף&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;
	],
	&quot;د. فارس الجويلي&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;روتانا&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;علاء&quot;: [
		&quot;steward&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;فيصل&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;ネイ&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;一隻北極熊&quot;: [
		&quot;patroller&quot;
	],
	&quot;人间百态&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;范&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;魔琴&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;ꠢꠣꠍꠘ ꠞꠣꠎꠣ&quot;: [
		&quot;patroller&quot;
	],
	&quot;기나ㅏㄴ&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;
	]
}</text>
      <sha1>kgduz67tatvlqz62w9rj2rbanfp48gu</sha1>
    </revision>
  </page>
  <page>
    <title>User:JJPMaster/luna/rfd.js</title>
    <ns>2</ns>
    <id>471464</id>
    <revision>
      <id>4676668</id>
      <parentid>4676451</parentid>
      <timestamp>2026-10-18T02:53:38Z</timestamp>
      <contributor>
        <username>JJPMaster</username>
        <id>3095725</id>
      </contributor>
      <minor />
      <comment>replace &quot;isReviewer&quot; with &quot;isPatroller&quot; (via JWB)</comment>
      <origin>4676668</origin>
      <model>javascript</model>
      <format>text/javascript</format>
      <text bytes="3400" sha1="tnfweemrrrdpgdragacnqbza1xba0wu" xml:space="preserve">// &lt;nowiki&gt;
importScript(&quot;User:JJPMaster/CurateThisPage/review.js&quot;);
var rfdPage = &quot;Wikibooks:Requests for deletion&quot;;
var isACategoryOrAFile = [6, 14].includes(mw.config.get(&quot;wgNamespaceNumber&quot;));
var parsedTitle = mw.config.get(&quot;wgPageName&quot;).replace(/_/g, &quot; &quot;); 
parsedTitle = isACategoryOrAFile ? `:${parsedTitle}` : parsedTitle; 

async function getAuthor() {
	var par = {
        action: 'query',
        prop: 'revisions',
        titles: parsedTitle,
        rvprop: 'user',
        rvdir: 'newer',
        rvlimit: 1,
        format: 'json'
    },
    api = new mw.Api();
	const data = await api.get( par );
	return Object.values(data.query.pages)[0].revisions[0].user;
}
(() =&gt; {
	if (mw.config.get(&quot;wgArticleId&quot;) &gt; 0) {
		var porty = window.addLunaLink({
			id: 'luna-rfd', 
			text: `RfD`,
			href: '#', 
			tooltip: 'File a deletion request for this page',
			debug: true,
			onClick: () =&gt; {
				$(&quot;#RFDdialog&quot;).dialog({ title: &quot;Request deletion&quot;, width: &quot;auto&quot; });
			}
		}); 
	}
})();
(async function () {
    await Luna.preferencesReady;

    if (Luna.getPref(&quot;debug&quot;, false)) {
        rfdPage = `User:${mw.config.get(&quot;wgUserName&quot;)}/luna/RFD`;
    }
})();

$(() =&gt; {
	if (mw.config.get(&quot;wgArticleId&quot;) !== 0) {
		$(&quot;#bodyContent&quot;).append(`
		&lt;div id=&quot;RFDdialog&quot;&gt;
			Please enter the reason for deletion:
			&lt;textarea name=&quot;RFDreason&quot; id=&quot;RFDreason&quot; placeholder=&quot;Reason for deletion&quot;&gt;&lt;/textarea&gt;
		    &lt;input type=&quot;checkbox&quot; id=&quot;notifyAuthor2&quot; name=&quot;notifyAuthor2&quot; checked /&gt;&lt;label for=&quot;notifyAuthor2&quot;&gt;Notify page author&lt;/label&gt;&lt;br /&gt;
		    &lt;button type=&quot;button&quot; id=&quot;reqDel&quot;&gt;Request deletion&lt;/button&gt;&lt;/div&gt;
		`);
		$(&quot;#RFDdialog&quot;).hide();
		
		$(&quot;#reqDel&quot;).click(async function() {
			var myText = document.getElementById(&quot;RFDreason&quot;);
			var reason = myText.value;
			
			if (!reason) alert(&quot;You must provide a reason.&quot;);
			else {
				if (window.isPatroller) {
					await doTheReview();
				}
				var params = {
					action: 'edit',
					prependtext: `&lt;noinclude&gt;{{Rfd|example=${Luna.isDebug}}}&lt;/noinclude&gt;\n`,
					title: parsedTitle,
					summary: `Making [[${rfdPage}#${parsedTitle}|deletion request]]`,
					tags: &quot;Luna&quot;,
					format: 'json'
				},
				api = new mw.Api();
				try {
					var data = await api.postWithToken( 'csrf', params )
					console.log( data );
					if ($(&quot;#notifyAuthor2&quot;).prop(&quot;checked&quot;)) {
						params = {
							action: 'edit',
							appendtext: `\n{{subst:Rfd warning|${parsedTitle}|~~~~}}`,
							title: `User_talk:${await getAuthor()}`,
							summary: &quot;Notifying author about deletion request&quot;,
							tags: &quot;Luna&quot;,
							format: 'json'
						}
					
						var data = await api.postWithToken( 'csrf', params )
						console.log( data );
					}
					params = {
						action: 'edit',
						appendtext: `\n== [[${parsedTitle}]] ==\n${reason} ~~~~`,
						title: rfdPage,
						summary: `Adding [[${rfdPage}#${parsedTitle}|deletion request]] for [[${parsedTitle}]]`,
						tags: &quot;Luna&quot;,
						format: 'json'
					}
				
				data = await api.postWithToken( 'csrf', params )
					console.log( data );
					mw.notify(&quot;Luna:\nThe page has been nominated for deletion. Reloading...&quot;);
					setTimeout(() =&gt; window.location.reload(), 2000);
				}
				catch (error) {
					console.error(&quot;Luna: Deletion nomination failed.&quot;, error);
					mw.notify(&quot;Luna: Deletion nomination failed. See the console for details.&quot;);
				}
				
			}		
		});
	}
});
// &lt;/nowiki&gt;</text>
      <sha1>tnfweemrrrdpgdragacnqbza1xba0wu</sha1>
    </revision>
    <revision>
      <id>4676671</id>
      <parentid>4676668</parentid>
      <timestamp>2026-10-18T03:10:21Z</timestamp>
      <contributor>
        <username>JJPMaster</username>
        <id>3095725</id>
      </contributor>
      <comment>patrol</comment>
      <origin>4676671</origin>
      <model>javascript</model>
      <format>text/javascript</format>
      <text bytes="3343" sha1="5u6b7ihc0ehskqi7ukjz1qi3oljctbd" xml:space="preserve">// &lt;nowiki&gt;
var rfdPage = &quot;Wikibooks:Requests for deletion&quot;;
var isACategoryOrAFile = [6, 14].includes(mw.config.get(&quot;wgNamespaceNumber&quot;));
var parsedTitle = mw.config.get(&quot;wgPageName&quot;).replace(/_/g, &quot; &quot;); 
parsedTitle = isACategoryOrAFile ? `:${parsedTitle}` : parsedTitle; 

async function getAuthor() {
	var par = {
        action: 'query',
        prop: 'revisions',
        titles: parsedTitle,
        rvprop: 'user',
        rvdir: 'newer',
        rvlimit: 1,
        format: 'json'
    },
    api = new mw.Api();
	const data = await api.get( par );
	return Object.values(data.query.pages)[0].revisions[0].user;
}
(() =&gt; {
	if (mw.config.get(&quot;wgArticleId&quot;) &gt; 0) {
		var porty = window.addLunaLink({
			id: 'luna-rfd', 
			text: `RfD`,
			href: '#', 
			tooltip: 'File a deletion request for this page',
			debug: true,
			onClick: () =&gt; {
				$(&quot;#RFDdialog&quot;).dialog({ title: &quot;Request deletion&quot;, width: &quot;auto&quot; });
			}
		}); 
	}
})();
(async function () {
    await Luna.preferencesReady;

    if (Luna.getPref(&quot;debug&quot;, false)) {
        rfdPage = `User:${mw.config.get(&quot;wgUserName&quot;)}/luna/RFD`;
    }
})();

$(() =&gt; {
	if (mw.config.get(&quot;wgArticleId&quot;) !== 0) {
		$(&quot;#bodyContent&quot;).append(`
		&lt;div id=&quot;RFDdialog&quot;&gt;
			Please enter the reason for deletion:
			&lt;textarea name=&quot;RFDreason&quot; id=&quot;RFDreason&quot; placeholder=&quot;Reason for deletion&quot;&gt;&lt;/textarea&gt;
		    &lt;input type=&quot;checkbox&quot; id=&quot;notifyAuthor2&quot; name=&quot;notifyAuthor2&quot; checked /&gt;&lt;label for=&quot;notifyAuthor2&quot;&gt;Notify page author&lt;/label&gt;&lt;br /&gt;
		    &lt;button type=&quot;button&quot; id=&quot;reqDel&quot;&gt;Request deletion&lt;/button&gt;&lt;/div&gt;
		`);
		$(&quot;#RFDdialog&quot;).hide();
		
		$(&quot;#reqDel&quot;).click(async function() {
			var myText = document.getElementById(&quot;RFDreason&quot;);
			var reason = myText.value;
			
			if (!reason) alert(&quot;You must provide a reason.&quot;);
			else {
				if (window.isPatroller) {
					await doThePatrol();
				}
				var params = {
					action: 'edit',
					prependtext: `&lt;noinclude&gt;{{Rfd|example=${Luna.isDebug}}}&lt;/noinclude&gt;\n`,
					title: parsedTitle,
					summary: `Making [[${rfdPage}#${parsedTitle}|deletion request]]`,
					tags: &quot;Luna&quot;,
					format: 'json'
				},
				api = new mw.Api();
				try {
					var data = await api.postWithToken( 'csrf', params )
					console.log( data );
					if ($(&quot;#notifyAuthor2&quot;).prop(&quot;checked&quot;)) {
						params = {
							action: 'edit',
							appendtext: `\n{{subst:Rfd warning|${parsedTitle}|~~~~}}`,
							title: `User_talk:${await getAuthor()}`,
							summary: &quot;Notifying author about deletion request&quot;,
							tags: &quot;Luna&quot;,
							format: 'json'
						}
					
						var data = await api.postWithToken( 'csrf', params )
						console.log( data );
					}
					params = {
						action: 'edit',
						appendtext: `\n== [[${parsedTitle}]] ==\n${reason} ~~~~`,
						title: rfdPage,
						summary: `Adding [[${rfdPage}#${parsedTitle}|deletion request]] for [[${parsedTitle}]]`,
						tags: &quot;Luna&quot;,
						format: 'json'
					}
				
				data = await api.postWithToken( 'csrf', params )
					console.log( data );
					mw.notify(&quot;Luna:\nThe page has been nominated for deletion. Reloading...&quot;);
					setTimeout(() =&gt; window.location.reload(), 2000);
				}
				catch (error) {
					console.error(&quot;Luna: Deletion nomination failed.&quot;, error);
					mw.notify(&quot;Luna: Deletion nomination failed. See the console for details.&quot;);
				}
				
			}		
		});
	}
});
// &lt;/nowiki&gt;</text>
      <sha1>5u6b7ihc0ehskqi7ukjz1qi3oljctbd</sha1>
    </revision>
    <revision>
      <id>4676681</id>
      <parentid>4676671</parentid>
      <timestamp>2026-10-18T04:00:00Z</timestamp>
      <contributor>
        <username>JJPMaster</username>
        <id>3095725</id>
      </contributor>
      <comment>disabling patrol features temporarily</comment>
      <origin>4676681</origin>
      <model>javascript</model>
      <format>text/javascript</format>
      <text bytes="3345" sha1="1l8barqanq2gxxti1qqz8067jos2ibg" xml:space="preserve">// &lt;nowiki&gt;
var rfdPage = &quot;Wikibooks:Requests for deletion&quot;;
var isACategoryOrAFile = [6, 14].includes(mw.config.get(&quot;wgNamespaceNumber&quot;));
var parsedTitle = mw.config.get(&quot;wgPageName&quot;).replace(/_/g, &quot; &quot;); 
parsedTitle = isACategoryOrAFile ? `:${parsedTitle}` : parsedTitle; 

async function getAuthor() {
	var par = {
        action: 'query',
        prop: 'revisions',
        titles: parsedTitle,
        rvprop: 'user',
        rvdir: 'newer',
        rvlimit: 1,
        format: 'json'
    },
    api = new mw.Api();
	const data = await api.get( par );
	return Object.values(data.query.pages)[0].revisions[0].user;
}
(() =&gt; {
	if (mw.config.get(&quot;wgArticleId&quot;) &gt; 0) {
		var porty = window.addLunaLink({
			id: 'luna-rfd', 
			text: `RfD`,
			href: '#', 
			tooltip: 'File a deletion request for this page',
			debug: true,
			onClick: () =&gt; {
				$(&quot;#RFDdialog&quot;).dialog({ title: &quot;Request deletion&quot;, width: &quot;auto&quot; });
			}
		}); 
	}
})();
(async function () {
    await Luna.preferencesReady;

    if (Luna.getPref(&quot;debug&quot;, false)) {
        rfdPage = `User:${mw.config.get(&quot;wgUserName&quot;)}/luna/RFD`;
    }
})();

$(() =&gt; {
	if (mw.config.get(&quot;wgArticleId&quot;) !== 0) {
		$(&quot;#bodyContent&quot;).append(`
		&lt;div id=&quot;RFDdialog&quot;&gt;
			Please enter the reason for deletion:
			&lt;textarea name=&quot;RFDreason&quot; id=&quot;RFDreason&quot; placeholder=&quot;Reason for deletion&quot;&gt;&lt;/textarea&gt;
		    &lt;input type=&quot;checkbox&quot; id=&quot;notifyAuthor2&quot; name=&quot;notifyAuthor2&quot; checked /&gt;&lt;label for=&quot;notifyAuthor2&quot;&gt;Notify page author&lt;/label&gt;&lt;br /&gt;
		    &lt;button type=&quot;button&quot; id=&quot;reqDel&quot;&gt;Request deletion&lt;/button&gt;&lt;/div&gt;
		`);
		$(&quot;#RFDdialog&quot;).hide();
		
		$(&quot;#reqDel&quot;).click(async function() {
			var myText = document.getElementById(&quot;RFDreason&quot;);
			var reason = myText.value;
			
			if (!reason) alert(&quot;You must provide a reason.&quot;);
			else {
				if (window.isPatroller) {
					//await doThePatrol();
				}
				var params = {
					action: 'edit',
					prependtext: `&lt;noinclude&gt;{{Rfd|example=${Luna.isDebug}}}&lt;/noinclude&gt;\n`,
					title: parsedTitle,
					summary: `Making [[${rfdPage}#${parsedTitle}|deletion request]]`,
					tags: &quot;Luna&quot;,
					format: 'json'
				},
				api = new mw.Api();
				try {
					var data = await api.postWithToken( 'csrf', params )
					console.log( data );
					if ($(&quot;#notifyAuthor2&quot;).prop(&quot;checked&quot;)) {
						params = {
							action: 'edit',
							appendtext: `\n{{subst:Rfd warning|${parsedTitle}|~~~~}}`,
							title: `User_talk:${await getAuthor()}`,
							summary: &quot;Notifying author about deletion request&quot;,
							tags: &quot;Luna&quot;,
							format: 'json'
						}
					
						var data = await api.postWithToken( 'csrf', params )
						console.log( data );
					}
					params = {
						action: 'edit',
						appendtext: `\n== [[${parsedTitle}]] ==\n${reason} ~~~~`,
						title: rfdPage,
						summary: `Adding [[${rfdPage}#${parsedTitle}|deletion request]] for [[${parsedTitle}]]`,
						tags: &quot;Luna&quot;,
						format: 'json'
					}
				
				data = await api.postWithToken( 'csrf', params )
					console.log( data );
					mw.notify(&quot;Luna:\nThe page has been nominated for deletion. Reloading...&quot;);
					setTimeout(() =&gt; window.location.reload(), 2000);
				}
				catch (error) {
					console.error(&quot;Luna: Deletion nomination failed.&quot;, error);
					mw.notify(&quot;Luna: Deletion nomination failed. See the console for details.&quot;);
				}
				
			}		
		});
	}
});
// &lt;/nowiki&gt;</text>
      <sha1>1l8barqanq2gxxti1qqz8067jos2ibg</sha1>
    </revision>
  </page>
  <page>
    <title>User:JJPMaster/luna.js</title>
    <ns>2</ns>
    <id>471466</id>
    <revision>
      <id>4676663</id>
      <parentid>4662281</parentid>
      <timestamp>2026-10-18T02:51:32Z</timestamp>
      <contributor>
        <username>JJPMaster</username>
        <id>3095725</id>
      </contributor>
      <comment>v0.8.4.1 → migrating from reviewer to patroller</comment>
      <origin>4676663</origin>
      <model>javascript</model>
      <format>text/javascript</format>
      <text bytes="7292" sha1="cim767mtwigla03tlknlnve12chwd0p" xml:space="preserve">const summaryAd = &quot; (using [[:b:en:Wikibooks:WikiProject Little Star/Luna|Luna]])&quot;;

window.isPatroller = true;
var myRights = [];

window.LunaLinks = [];
window.LunaRendered = false;
window.addLunaLink = function(link) {
    window.LunaLinks.push(link);
	document.dispatchEvent(new CustomEvent(&quot;luna-link-added&quot;, {
        detail: link
    }));
	console.log(&quot;Luna: link added&quot;, link.id, performance.now());
	return window.LunaLinks;
};
window.addLunaLinks = function(arr) {
    for (let i of arr) {
		window.addLunaLink(i);
	}
	return window.LunaLinks;
};

console.log(&quot;Luna: Script started.&quot;);

mw.loader.load('//en.wikipedia.org/w/load.php?modules=ext.gadget.morebits');

async function loadScripts() {
    const scripts = [
        'User:JJPMaster/luna/CurateThisPage.js', // Backlink: [[User:JJPMaster/luna/CurateThisPage.js]]
        'User:JJPMaster/luna/rfd.js', // Backlink: [[User:JJPMaster/luna/rfd.js]]
        'User:JJPMaster/luna/warn.js', // Backlink: [[User:JJPMaster/luna/warn.js]]
        'User:JJPMaster/luna/talkback.js', // Backlink: [[User:JJPMaster/luna/talkback.js]]
        'User:JJPMaster/luna/welcome.js', // Backlink: [[User:JJPMaster/luna/welcome.js]]
        'User:JJPMaster/luna/arv.js', // Backlink: [[User:JJPMaster/luna/arv.js]]
        'User:JJPMaster/luna/unlink.js', // Backlink: [[User:JJPMaster/luna/unlink.js]]
        'User:JJPMaster/luna/fileunlink.js', // Backlink: [[User:JJPMaster/luna/fileunlink.js]]
        'User:JJPMaster/luna/csd.js', // Backlink: [[User:JJPMaster/luna/csd.js]]
        'User:JJPMaster/luna/diff.js', // Backlink: [[User:JJPMaster/luna/diff.js]]
        'User:JJPMaster/luna/raddewikify.js', // Backlink: [[User:JJPMaster/luna/raddewikify.js]]
        'User:JJPMaster/luna/rpp.js', // Backlink: [[User:JJPMaster/luna/rpp.js]]
        'User:JJPMaster/luna/CurateThisFile.js', // Backlink: [[User:JJPMaster/luna/CurateThisFile.js]]
        'User:JJPMaster/luna/di.js', // Backlink: [[User:JJPMaster/luna/di.js]]
        'User:JJPMaster/luna/templateunlink.js', // Backlink: [[User:JJPMaster/luna/templateunlink.js]]
        'User:JJPMaster/luna/rollback.js' // Backlink: [[User:JJPMaster/luna/rollback.js]]
    ];

    if (myRights.includes(&quot;delete&quot;)) {
		await $.getScript('/w/index.php?title=User:JJPMaster/luna/d-batch/core.js&amp;action=raw&amp;ctype=text/javascript'), // Backlink: [[User:JJPMaster/luna/d-batch/core.js]]&quot;)
		await $.getScript(`/w/index.php?title=User:JJPMaster/htmlparserfromhell.js&amp;action=raw&amp;ctype=text/javascript`); // Backlink: [[User:JJPMaster/htmlparserfromhell.js]]
        scripts.push(
			'User:JJPMaster/luna/d-batch/links.js', // Backlink: [[User:JJPMaster/luna/d-batch/links.js]]
			'User:JJPMaster/luna/d-batch/cat.js', // Backlink: [[User:JJPMaster/luna/d-batch/cat.js]]
			'User:JJPMaster/luna/d-batch/prefix.js', // Backlink: [[User:JJPMaster/luna/d-batch/prefix.js]]
			'User:JJPMaster/luna/und-batch.js' // Backlink: [[User:JJPMaster/luna/und-batch.js]]
		);
    }

    console.log(&quot;Luna: Loading scripts...&quot;);
    
    await Promise.all(scripts.map(script =&gt; {
		const start = performance.now();
        return $.getScript(`/w/index.php?title=${script}&amp;action=raw&amp;ctype=text/javascript`)
        .then(() =&gt; console.log(`Luna: Loaded ${script} in ${performance.now() - start}ms.`))
        .catch(error =&gt; console.error(`Luna: Failed to load ${script}:`, error))
		}
    ));

    console.log(&quot;Luna: All scripts loaded successfully.&quot;);
}
async function waitForPreferences(maxRetries = 10, delay = 200) {
    for (let i = 0; i &lt; maxRetries; i++) {
        if (typeof Luna !== &quot;undefined&quot; &amp;&amp; Luna.myPreferences &amp;&amp; Luna.myPreferences.CSD) {
            console.log(&quot;Luna: Preferences loaded successfully.&quot;);
            return true;
        }
        console.warn(&quot;Luna: Preferences not loaded yet, retrying...&quot;);
        await new Promise(resolve =&gt; setTimeout(resolve, delay));
    }
    console.error(&quot;Luna: Preferences failed to load after multiple attempts.&quot;);
    return false;
}
function renderLunaPortlet() {
	const order = [
		'luna-arv',
		'luna-warn',
		'luna-welcome',
		'luna-welcome-anon',
		'luna-tb',
		'luna-rev',
		'luna-csd',
		'luna-rfd',
		'luna-di',
		'luna-qrb',
		'luna-rpp',
		'luna-dbatch-links',
		'luna-dbatch-prefix',
		'luna-dbatch-cat',
		'luna-undbatch',
		'luna-ctf',
		'luna-ctp',
		'luna-last',
		'luna-since',
		'luna-sincemine',
		'luna-current',
		'luna-dewiki',
		'luna-unlink',
		'luna-fileunlink',
		'luna-tempunlink',
		'luna-debug-link'
	];
	console.log(&quot;Luna: rendering at&quot;, performance.now());
	order.forEach(id =&gt; {
		const i = window.LunaLinks.find(l =&gt; l.id == id);
		if (!i) return;
		const text = i.debug &amp;&amp; Luna.myPreferences?.debug ? `${i.text} [DEBUG]` : i.text;
		const l = mw.util.addPortletLink('luna-actions', i.href, text, i.id, i.tooltip)
		
		if (i.onClick) {
			$(l).on('click', i.onClick);
		}
	});
	mw.util.addPortletLink(
        'luna-actions',
        '/wiki/Wikibooks:WikiProject_Little_Star/Luna/Preferences',
        'Pref',
        'luna-pref-link',
        'Edit your Luna preferences'
    );
	document.dispatchEvent(new Event(&quot;luna-rendered&quot;));
}
function waitForLunaLinksToSettle(callback, delay = 150) {
	let timeout;

	function resetTimer() {
		clearTimeout(timeout);
		timeout = setTimeout(() =&gt; {
			document.removeEventListener(&quot;luna-link-added&quot;, resetTimer);
			callback();
		}, delay);
	}

	document.addEventListener(&quot;luna-link-added&quot;, resetTimer);

	resetTimer();
}
(async function () {
    try {
        console.log(&quot;Luna: Fetching user rights...&quot;);
        myRights = await mw.user.getRights();
        console.log(&quot;Luna: User rights fetched:&quot;, myRights);
    } catch (error) {
        console.error(&quot;Luna: Error fetching user rights:&quot;, error);
        alert(&quot;Luna: An error occurred while fetching your user rights. Please try again.&quot;);
        return;
    }
    if (!myRights || myRights.length === 0) {
        console.error(&quot;Luna: User rights array is empty or undefined.&quot;);
        alert(&quot;Luna: An error occurred while fetching your user rights. Please try again.&quot;);
        return;
    }

    if (myRights.includes(&quot;autoconfirmed&quot;)) {
        if (!myRights.includes(&quot;rollback&quot;)) {
            console.log(&quot;Luna: Not a patroller or administrator.&quot;);
            window.isPatroller = false;
        }

        mw.loader.load('jquery.ui');

        console.log(&quot;Luna: Loading preferences script...&quot;);
        try {
            await $.getScript(`/w/index.php?title=User:JJPMaster/luna/pref/unstable.js&amp;action=raw&amp;ctype=text/javascript&amp;cb=${Date.now()}`); // Backlink: [[User:JJPMaster/luna/pref/unstable.js]]
            console.log(&quot;Luna: Preferences loaded successfully.&quot;);
        } catch (error) {
            console.error(&quot;Luna: Failed to load preferences script:&quot;, error);
            return;
        }
        mw.loader.load('/w/index.php?title=User:JJPMaster/luna.css&amp;action=raw&amp;ctype=text/css', 'text/css');

        console.log(&quot;Luna: Adding UI elements...&quot;);
        mw.util.addPortlet('luna-actions', 'Luna', '#p-cactions');

        await loadScripts();
		// window.LunaScriptsLoaded = true;
		waitForLunaLinksToSettle(() =&gt; renderLunaPortlet());
    } else {
        console.error(&quot;Luna: User is not autoconfirmed.&quot;);
        mw.notify(&quot;Error: You must be autoconfirmed to use Luna.&quot;);
    }
})();</text>
      <sha1>cim767mtwigla03tlknlnve12chwd0p</sha1>
    </revision>
  </page>
  <page>
    <title>User:JJPMaster/luna/unlink.js</title>
    <ns>2</ns>
    <id>471508</id>
    <revision>
      <id>4676667</id>
      <parentid>4662626</parentid>
      <timestamp>2026-10-18T02:53:23Z</timestamp>
      <contributor>
        <username>JJPMaster</username>
        <id>3095725</id>
      </contributor>
      <minor />
      <comment>replace &quot;isReviewer&quot; with &quot;isPatroller&quot; (via JWB)</comment>
      <origin>4676667</origin>
      <model>javascript</model>
      <format>text/javascript</format>
      <text bytes="2052" sha1="coauyhmkkrz855b5zwep5udhqnyyl97" xml:space="preserve">// &lt;nowiki&gt;
if (mw.config.get(&quot;wgNamespaceNumber&quot;) &gt;= 0 &amp;&amp; window.isPatroller) {
	var unlinkLink = window.addLunaLink({
		id: 'luna-unlink', 
		text: 'Unlink', 
		href: '#', 
		tooltip: 'Remove all links to this page',
		onClick: unlink
	}); 
}
async function getBacklinks() {
    var params = {
		action: 'query',
		format: 'json',
		list: 'backlinks',
		bllimit: 'max',
		bltitle: mw.config.get(&quot;wgPageName&quot;)
	},
	api = new mw.Api();

	const data = await api.get(params);
	return data.query.backlinks;
}
async function getUnlinkedContent(title, unlinked) {
	var params = {
		action: 'parse',
		page: title,
		prop: 'wikitext',
		format: 'json'
	},
	api = new mw.Api();
	const data = await api.get(params);
	var text = data.parse.wikitext['*'];
	var myPage = new Morebits.wikitext.Page(text);
	var newText = myPage.removeLink(unlinked).getText();
	return newText;
}
	
async function unlink() {
	if (window.isPatroller) {
		var doIt = confirm(&quot;You are about to remove all of the links to this page. If you mess up, this is likely to be very difficult to reverse. Are you *ABSOLUTELY SURE* you want to do this?&quot;);
		if (!doIt) return;
		var backlinks = await getBacklinks();
		var params, api;
		for (var b of backlinks) {
			var content = await getUnlinkedContent(b.title, mw.config.get(&quot;wgPageName&quot;));
			params = {
				action: 'edit',
				format: 'json',
				text: content,
				title: b.title,
				summary: `Removing link(s) to [[${mw.config.get(&quot;wgPageName&quot;).replace(/_/g, ' ')}]]`,
				tags: &quot;Luna&quot;
			};
			api = new mw.Api();

			try {
				var data = await api.postWithToken( 'csrf', params );
				console.log(data)
			}
			catch (error) {
				console.error(&quot;Luna: Unlink failed.&quot;, error)
			}
		}
		var remaining = await getBacklinks();
		if (remaining.length &gt; 0) 
			alert(&quot;It looks like not all of the backlinks were removed. This is most likely because you hit the rate limit. Please try again later.&quot;);
		else alert(&quot;Done!&quot;);
	}
	else {
		alert(&quot;Luna: You must be a reviewer or administrator to use this tool.&quot;);
		return;
	}
}
// &lt;/nowiki&gt;</text>
      <sha1>coauyhmkkrz855b5zwep5udhqnyyl97</sha1>
    </revision>
  </page>
  <page>
    <title>User:JJPMaster/luna/fileunlink.js</title>
    <ns>2</ns>
    <id>471516</id>
    <revision>
      <id>4676666</id>
      <parentid>4662627</parentid>
      <timestamp>2026-10-18T02:53:21Z</timestamp>
      <contributor>
        <username>JJPMaster</username>
        <id>3095725</id>
      </contributor>
      <minor />
      <comment>replace &quot;isReviewer&quot; with &quot;isPatroller&quot; (via JWB)</comment>
      <origin>4676666</origin>
      <model>javascript</model>
      <format>text/javascript</format>
      <text bytes="2115" sha1="1tlb88iwpt9w78l016egxkhdwj8ph18" xml:space="preserve">// &lt;nowiki&gt;
if (mw.config.get(&quot;wgNamespaceNumber&quot;) == 6 &amp;&amp; window.isPatroller) {
	var fileunlinkLink = window.addLunaLink({
		id: 'luna-fileunlink', 
		text: 'Unlink (file uses)', 
		href: '#', 
		tooltip: 'Remove all uses of this file',
		onClick: fileUnlink
	}); 

}
async function getImageUses() {
    var params = {
		action: 'query',
		format: 'json',
		list: 'imageusage',
		iulimit: 'max',
		iutitle: mw.config.get(&quot;wgPageName&quot;)
	},
	api = new mw.Api();

	const data = await api.get(params);
	return data.query.imageusage;
}
async function getFileUnlinkedContent(title, unlinked) {
	var params = {
		action: 'parse',
		page: title,
		prop: 'wikitext',
		format: 'json'
	},
	api = new mw.Api();
	const data = await api.get(params);
	var text = data.parse.wikitext['*'];
	var myPage = new Morebits.wikitext.Page(text);
	var newText = myPage.commentOutImage(unlinked.substr(5), &quot;Commented out&quot;).getText();
	return newText;
}
	
async function fileUnlink() {
	if (window.isPatroller) {
		var doIt = confirm(&quot;You are about to remove all of the links to this page. If you mess up, this is likely to be very difficult to reverse. Are you *ABSOLUTELY SURE* you want to do this?&quot;);
		if (!doIt) return;
		var uses = await getImageUses();
		var params, api;
		for (var u of uses) {
			var content = await getFileUnlinkedContent(u.title, mw.config.get(&quot;wgPageName&quot;));
			params = {
				action: 'edit',
				format: 'json',
				text: content,
				title: u.title,
				summary: `Removing use(s) of [[${mw.config.get(&quot;wgPageName&quot;).replace(/_/g, ' ')}]]`,
				tags: &quot;Luna&quot;
			};
			api = new mw.Api();
			
			try {
				var data = await api.postWithToken( 'csrf', params );
				console.log(data)
			}
			catch (error) {
				console.error(&quot;Luna: Unlink failed.&quot;, error)
			}
		}
		var remaining = await getImageUses();
		if (remaining.length &gt; 0) 
			alert(&quot;It looks like not all of the image uses were removed. This is most likely because you hit the rate limit. Please try again later.&quot;);
		else alert(&quot;Done!&quot;);
	}
	else {
		alert(&quot;Luna: You must be a reviewer or administrator to use this tool.&quot;);
		return;
	}
}
// &lt;/nowiki&gt;</text>
      <sha1>1tlb88iwpt9w78l016egxkhdwj8ph18</sha1>
    </revision>
  </page>
  <page>
    <title>Wikibooks:Outdated books</title>
    <ns>4</ns>
    <id>471645</id>
    <revision>
      <id>4676583</id>
      <parentid>4463234</parentid>
      <timestamp>2026-10-18T02:44:52Z</timestamp>
      <contributor>
        <username>JJPMaster</username>
        <id>3095725</id>
      </contributor>
      <comment>noinclude</comment>
      <origin>4676583</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2270" sha1="k9m1gu3pv7lyw9o999e5z3ulwt1vjoy" xml:space="preserve">&lt;noinclude&gt;{{Draft}}&lt;/noinclude&gt;
Sometimes, there will be a book that has a lot of information that was very useful at the time, but has become out of date over time. There are generally two procedures that can be followed here.

== For books that aren't up to date, but can be reasonably updated ==
This category applies to books that, for instance, have not been updated with new information in a few years, but where the subject still exists and new information can be found about it. In this scenario, you should add the {{tlx|Outdated}} tag to the top of the book, and post on its discussion page explaining what should be updated. Or, you can always just [[Wikibooks:Be bold|be bold]] and update it yourself!

== For books that cannot be reasonably updated ==
This category includes books that are so outdated that their subject either no longer exists, or has changed so much since the book was written that it is virtually unrecognizable, and it would be nearly impossible to update it satisfactorily. These books should generally not be deleted, as they do provide valuable information, but should not be easily accessible to readers looking for recent information. Here, the following instructions should be followed.
=== If the case is unambiguous ===
# Add {{tlx|Archived}} to the top of the book. Doing this will also remove it from search engine indexes, unless you override this by using {{tlx|Archived|2=noindex=false}}.
# Move the book to a subpage of [[Wikibooks:Outdated books/Archive]].
# Replace the content of the redirect left behind after the move with {{tlx|Soft redirect|2=Wikibooks:Outdated books/Archive/&lt;book title&gt;}}.
# (''optional'') Inform the author(s) of the book of your decision.

=== If the case is ambiguous ===
Follow these steps if there is any reasonable doubt about if the book can be updated.
# Follow the instructions at {{Section link|Wikibooks:Requests for deletion#Deletion}} to file a request. Make sure to note that the request is for archiving, not deletion.
# The proposal for archiving will be discussed.
# If consensus has been reached to archive the book, any uninvolved user may close the discussion and follow the instructions in {{Section link|#If the case is unambiguous}}. Otherwise, the book will remain as is.</text>
      <sha1>k9m1gu3pv7lyw9o999e5z3ulwt1vjoy</sha1>
    </revision>
  </page>
  <page>
    <title>User:JJPMaster/luna/unstable.js</title>
    <ns>2</ns>
    <id>471665</id>
    <revision>
      <id>4676664</id>
      <parentid>4662270</parentid>
      <timestamp>2026-10-18T02:51:50Z</timestamp>
      <contributor>
        <username>JJPMaster</username>
        <id>3095725</id>
      </contributor>
      <comment>copy from stable</comment>
      <origin>4676664</origin>
      <model>javascript</model>
      <format>text/javascript</format>
      <text bytes="7292" sha1="cim767mtwigla03tlknlnve12chwd0p" xml:space="preserve">const summaryAd = &quot; (using [[:b:en:Wikibooks:WikiProject Little Star/Luna|Luna]])&quot;;

window.isPatroller = true;
var myRights = [];

window.LunaLinks = [];
window.LunaRendered = false;
window.addLunaLink = function(link) {
    window.LunaLinks.push(link);
	document.dispatchEvent(new CustomEvent(&quot;luna-link-added&quot;, {
        detail: link
    }));
	console.log(&quot;Luna: link added&quot;, link.id, performance.now());
	return window.LunaLinks;
};
window.addLunaLinks = function(arr) {
    for (let i of arr) {
		window.addLunaLink(i);
	}
	return window.LunaLinks;
};

console.log(&quot;Luna: Script started.&quot;);

mw.loader.load('//en.wikipedia.org/w/load.php?modules=ext.gadget.morebits');

async function loadScripts() {
    const scripts = [
        'User:JJPMaster/luna/CurateThisPage.js', // Backlink: [[User:JJPMaster/luna/CurateThisPage.js]]
        'User:JJPMaster/luna/rfd.js', // Backlink: [[User:JJPMaster/luna/rfd.js]]
        'User:JJPMaster/luna/warn.js', // Backlink: [[User:JJPMaster/luna/warn.js]]
        'User:JJPMaster/luna/talkback.js', // Backlink: [[User:JJPMaster/luna/talkback.js]]
        'User:JJPMaster/luna/welcome.js', // Backlink: [[User:JJPMaster/luna/welcome.js]]
        'User:JJPMaster/luna/arv.js', // Backlink: [[User:JJPMaster/luna/arv.js]]
        'User:JJPMaster/luna/unlink.js', // Backlink: [[User:JJPMaster/luna/unlink.js]]
        'User:JJPMaster/luna/fileunlink.js', // Backlink: [[User:JJPMaster/luna/fileunlink.js]]
        'User:JJPMaster/luna/csd.js', // Backlink: [[User:JJPMaster/luna/csd.js]]
        'User:JJPMaster/luna/diff.js', // Backlink: [[User:JJPMaster/luna/diff.js]]
        'User:JJPMaster/luna/raddewikify.js', // Backlink: [[User:JJPMaster/luna/raddewikify.js]]
        'User:JJPMaster/luna/rpp.js', // Backlink: [[User:JJPMaster/luna/rpp.js]]
        'User:JJPMaster/luna/CurateThisFile.js', // Backlink: [[User:JJPMaster/luna/CurateThisFile.js]]
        'User:JJPMaster/luna/di.js', // Backlink: [[User:JJPMaster/luna/di.js]]
        'User:JJPMaster/luna/templateunlink.js', // Backlink: [[User:JJPMaster/luna/templateunlink.js]]
        'User:JJPMaster/luna/rollback.js' // Backlink: [[User:JJPMaster/luna/rollback.js]]
    ];

    if (myRights.includes(&quot;delete&quot;)) {
		await $.getScript('/w/index.php?title=User:JJPMaster/luna/d-batch/core.js&amp;action=raw&amp;ctype=text/javascript'), // Backlink: [[User:JJPMaster/luna/d-batch/core.js]]&quot;)
		await $.getScript(`/w/index.php?title=User:JJPMaster/htmlparserfromhell.js&amp;action=raw&amp;ctype=text/javascript`); // Backlink: [[User:JJPMaster/htmlparserfromhell.js]]
        scripts.push(
			'User:JJPMaster/luna/d-batch/links.js', // Backlink: [[User:JJPMaster/luna/d-batch/links.js]]
			'User:JJPMaster/luna/d-batch/cat.js', // Backlink: [[User:JJPMaster/luna/d-batch/cat.js]]
			'User:JJPMaster/luna/d-batch/prefix.js', // Backlink: [[User:JJPMaster/luna/d-batch/prefix.js]]
			'User:JJPMaster/luna/und-batch.js' // Backlink: [[User:JJPMaster/luna/und-batch.js]]
		);
    }

    console.log(&quot;Luna: Loading scripts...&quot;);
    
    await Promise.all(scripts.map(script =&gt; {
		const start = performance.now();
        return $.getScript(`/w/index.php?title=${script}&amp;action=raw&amp;ctype=text/javascript`)
        .then(() =&gt; console.log(`Luna: Loaded ${script} in ${performance.now() - start}ms.`))
        .catch(error =&gt; console.error(`Luna: Failed to load ${script}:`, error))
		}
    ));

    console.log(&quot;Luna: All scripts loaded successfully.&quot;);
}
async function waitForPreferences(maxRetries = 10, delay = 200) {
    for (let i = 0; i &lt; maxRetries; i++) {
        if (typeof Luna !== &quot;undefined&quot; &amp;&amp; Luna.myPreferences &amp;&amp; Luna.myPreferences.CSD) {
            console.log(&quot;Luna: Preferences loaded successfully.&quot;);
            return true;
        }
        console.warn(&quot;Luna: Preferences not loaded yet, retrying...&quot;);
        await new Promise(resolve =&gt; setTimeout(resolve, delay));
    }
    console.error(&quot;Luna: Preferences failed to load after multiple attempts.&quot;);
    return false;
}
function renderLunaPortlet() {
	const order = [
		'luna-arv',
		'luna-warn',
		'luna-welcome',
		'luna-welcome-anon',
		'luna-tb',
		'luna-rev',
		'luna-csd',
		'luna-rfd',
		'luna-di',
		'luna-qrb',
		'luna-rpp',
		'luna-dbatch-links',
		'luna-dbatch-prefix',
		'luna-dbatch-cat',
		'luna-undbatch',
		'luna-ctf',
		'luna-ctp',
		'luna-last',
		'luna-since',
		'luna-sincemine',
		'luna-current',
		'luna-dewiki',
		'luna-unlink',
		'luna-fileunlink',
		'luna-tempunlink',
		'luna-debug-link'
	];
	console.log(&quot;Luna: rendering at&quot;, performance.now());
	order.forEach(id =&gt; {
		const i = window.LunaLinks.find(l =&gt; l.id == id);
		if (!i) return;
		const text = i.debug &amp;&amp; Luna.myPreferences?.debug ? `${i.text} [DEBUG]` : i.text;
		const l = mw.util.addPortletLink('luna-actions', i.href, text, i.id, i.tooltip)
		
		if (i.onClick) {
			$(l).on('click', i.onClick);
		}
	});
	mw.util.addPortletLink(
        'luna-actions',
        '/wiki/Wikibooks:WikiProject_Little_Star/Luna/Preferences',
        'Pref',
        'luna-pref-link',
        'Edit your Luna preferences'
    );
	document.dispatchEvent(new Event(&quot;luna-rendered&quot;));
}
function waitForLunaLinksToSettle(callback, delay = 150) {
	let timeout;

	function resetTimer() {
		clearTimeout(timeout);
		timeout = setTimeout(() =&gt; {
			document.removeEventListener(&quot;luna-link-added&quot;, resetTimer);
			callback();
		}, delay);
	}

	document.addEventListener(&quot;luna-link-added&quot;, resetTimer);

	resetTimer();
}
(async function () {
    try {
        console.log(&quot;Luna: Fetching user rights...&quot;);
        myRights = await mw.user.getRights();
        console.log(&quot;Luna: User rights fetched:&quot;, myRights);
    } catch (error) {
        console.error(&quot;Luna: Error fetching user rights:&quot;, error);
        alert(&quot;Luna: An error occurred while fetching your user rights. Please try again.&quot;);
        return;
    }
    if (!myRights || myRights.length === 0) {
        console.error(&quot;Luna: User rights array is empty or undefined.&quot;);
        alert(&quot;Luna: An error occurred while fetching your user rights. Please try again.&quot;);
        return;
    }

    if (myRights.includes(&quot;autoconfirmed&quot;)) {
        if (!myRights.includes(&quot;rollback&quot;)) {
            console.log(&quot;Luna: Not a patroller or administrator.&quot;);
            window.isPatroller = false;
        }

        mw.loader.load('jquery.ui');

        console.log(&quot;Luna: Loading preferences script...&quot;);
        try {
            await $.getScript(`/w/index.php?title=User:JJPMaster/luna/pref/unstable.js&amp;action=raw&amp;ctype=text/javascript&amp;cb=${Date.now()}`); // Backlink: [[User:JJPMaster/luna/pref/unstable.js]]
            console.log(&quot;Luna: Preferences loaded successfully.&quot;);
        } catch (error) {
            console.error(&quot;Luna: Failed to load preferences script:&quot;, error);
            return;
        }
        mw.loader.load('/w/index.php?title=User:JJPMaster/luna.css&amp;action=raw&amp;ctype=text/css', 'text/css');

        console.log(&quot;Luna: Adding UI elements...&quot;);
        mw.util.addPortlet('luna-actions', 'Luna', '#p-cactions');

        await loadScripts();
		// window.LunaScriptsLoaded = true;
		waitForLunaLinksToSettle(() =&gt; renderLunaPortlet());
    } else {
        console.error(&quot;Luna: User is not autoconfirmed.&quot;);
        mw.notify(&quot;Error: You must be autoconfirmed to use Luna.&quot;);
    }
})();</text>
      <sha1>cim767mtwigla03tlknlnve12chwd0p</sha1>
    </revision>
    <revision>
      <id>4676673</id>
      <parentid>4676664</parentid>
      <timestamp>2026-10-18T03:12:49Z</timestamp>
      <contributor>
        <username>JJPMaster</username>
        <id>3095725</id>
      </contributor>
      <comment>asynchronizing the patrol feature</comment>
      <origin>4676673</origin>
      <model>javascript</model>
      <format>text/javascript</format>
      <text bytes="7454" sha1="i7y5ph3roxn10u889751toury0cbl2n" xml:space="preserve">const summaryAd = &quot; (using [[:b:en:Wikibooks:WikiProject Little Star/Luna|Luna]])&quot;;

window.isPatroller = true;
var myRights = [];

window.LunaLinks = [];
window.LunaRendered = false;
window.addLunaLink = function(link) {
    window.LunaLinks.push(link);
	document.dispatchEvent(new CustomEvent(&quot;luna-link-added&quot;, {
        detail: link
    }));
	console.log(&quot;Luna: link added&quot;, link.id, performance.now());
	return window.LunaLinks;
};
window.addLunaLinks = function(arr) {
    for (let i of arr) {
		window.addLunaLink(i);
	}
	return window.LunaLinks;
};

console.log(&quot;Luna: Script started.&quot;);

mw.loader.load('//en.wikipedia.org/w/load.php?modules=ext.gadget.morebits');

async function loadScripts() {
	await $.getScript(&quot;/w/index.php?title=User:JJPMaster/luna/patrol.js&amp;action=raw&amp;ctype=text/javascript&quot;) // Backlink: [[User:JJPMaster/luna/patrol.js]]&quot;);
		
    const scripts = [
        'User:JJPMaster/luna/CurateThisPage.js', // Backlink: [[User:JJPMaster/luna/CurateThisPage.js]]
        'User:JJPMaster/luna/rfd.js', // Backlink: [[User:JJPMaster/luna/rfd.js]]
        'User:JJPMaster/luna/warn.js', // Backlink: [[User:JJPMaster/luna/warn.js]]
        'User:JJPMaster/luna/talkback.js', // Backlink: [[User:JJPMaster/luna/talkback.js]]
        'User:JJPMaster/luna/welcome.js', // Backlink: [[User:JJPMaster/luna/welcome.js]]
        'User:JJPMaster/luna/arv.js', // Backlink: [[User:JJPMaster/luna/arv.js]]
        'User:JJPMaster/luna/unlink.js', // Backlink: [[User:JJPMaster/luna/unlink.js]]
        'User:JJPMaster/luna/fileunlink.js', // Backlink: [[User:JJPMaster/luna/fileunlink.js]]
        'User:JJPMaster/luna/csd.js', // Backlink: [[User:JJPMaster/luna/csd.js]]
        'User:JJPMaster/luna/diff.js', // Backlink: [[User:JJPMaster/luna/diff.js]]
        'User:JJPMaster/luna/raddewikify.js', // Backlink: [[User:JJPMaster/luna/raddewikify.js]]
        'User:JJPMaster/luna/rpp.js', // Backlink: [[User:JJPMaster/luna/rpp.js]]
        'User:JJPMaster/luna/CurateThisFile.js', // Backlink: [[User:JJPMaster/luna/CurateThisFile.js]]
        'User:JJPMaster/luna/di.js', // Backlink: [[User:JJPMaster/luna/di.js]]
        'User:JJPMaster/luna/templateunlink.js', // Backlink: [[User:JJPMaster/luna/templateunlink.js]]
        'User:JJPMaster/luna/rollback.js' // Backlink: [[User:JJPMaster/luna/rollback.js]]
    ];

    if (myRights.includes(&quot;delete&quot;)) {
		await $.getScript('/w/index.php?title=User:JJPMaster/luna/d-batch/core.js&amp;action=raw&amp;ctype=text/javascript'), // Backlink: [[User:JJPMaster/luna/d-batch/core.js]]&quot;)
		await $.getScript(`/w/index.php?title=User:JJPMaster/htmlparserfromhell.js&amp;action=raw&amp;ctype=text/javascript`); // Backlink: [[User:JJPMaster/htmlparserfromhell.js]]
        scripts.push(
			'User:JJPMaster/luna/d-batch/links.js', // Backlink: [[User:JJPMaster/luna/d-batch/links.js]]
			'User:JJPMaster/luna/d-batch/cat.js', // Backlink: [[User:JJPMaster/luna/d-batch/cat.js]]
			'User:JJPMaster/luna/d-batch/prefix.js', // Backlink: [[User:JJPMaster/luna/d-batch/prefix.js]]
			'User:JJPMaster/luna/und-batch.js' // Backlink: [[User:JJPMaster/luna/und-batch.js]]
			
		);
    }
	
    console.log(&quot;Luna: Loading scripts...&quot;);
    
    await Promise.all(scripts.map(script =&gt; {
		const start = performance.now();
        return $.getScript(`/w/index.php?title=${script}&amp;action=raw&amp;ctype=text/javascript`)
        .then(() =&gt; console.log(`Luna: Loaded ${script} in ${performance.now() - start}ms.`))
        .catch(error =&gt; console.error(`Luna: Failed to load ${script}:`, error))
		}
    ));

    console.log(&quot;Luna: All scripts loaded successfully.&quot;);
}
async function waitForPreferences(maxRetries = 10, delay = 200) {
    for (let i = 0; i &lt; maxRetries; i++) {
        if (typeof Luna !== &quot;undefined&quot; &amp;&amp; Luna.myPreferences &amp;&amp; Luna.myPreferences.CSD) {
            console.log(&quot;Luna: Preferences loaded successfully.&quot;);
            return true;
        }
        console.warn(&quot;Luna: Preferences not loaded yet, retrying...&quot;);
        await new Promise(resolve =&gt; setTimeout(resolve, delay));
    }
    console.error(&quot;Luna: Preferences failed to load after multiple attempts.&quot;);
    return false;
}
function renderLunaPortlet() {
	const order = [
		'luna-arv',
		'luna-warn',
		'luna-welcome',
		'luna-welcome-anon',
		'luna-tb',
		'luna-rev',
		'luna-csd',
		'luna-rfd',
		'luna-di',
		'luna-qrb',
		'luna-rpp',
		'luna-dbatch-links',
		'luna-dbatch-prefix',
		'luna-dbatch-cat',
		'luna-undbatch',
		'luna-ctf',
		'luna-ctp',
		'luna-last',
		'luna-since',
		'luna-sincemine',
		'luna-current',
		'luna-dewiki',
		'luna-unlink',
		'luna-fileunlink',
		'luna-tempunlink',
		'luna-debug-link'
	];
	console.log(&quot;Luna: rendering at&quot;, performance.now());
	order.forEach(id =&gt; {
		const i = window.LunaLinks.find(l =&gt; l.id == id);
		if (!i) return;
		const text = i.debug &amp;&amp; Luna.myPreferences?.debug ? `${i.text} [DEBUG]` : i.text;
		const l = mw.util.addPortletLink('luna-actions', i.href, text, i.id, i.tooltip)
		
		if (i.onClick) {
			$(l).on('click', i.onClick);
		}
	});
	mw.util.addPortletLink(
        'luna-actions',
        '/wiki/Wikibooks:WikiProject_Little_Star/Luna/Preferences',
        'Pref',
        'luna-pref-link',
        'Edit your Luna preferences'
    );
	document.dispatchEvent(new Event(&quot;luna-rendered&quot;));
}
function waitForLunaLinksToSettle(callback, delay = 150) {
	let timeout;

	function resetTimer() {
		clearTimeout(timeout);
		timeout = setTimeout(() =&gt; {
			document.removeEventListener(&quot;luna-link-added&quot;, resetTimer);
			callback();
		}, delay);
	}

	document.addEventListener(&quot;luna-link-added&quot;, resetTimer);

	resetTimer();
}
(async function () {
    try {
        console.log(&quot;Luna: Fetching user rights...&quot;);
        myRights = await mw.user.getRights();
        console.log(&quot;Luna: User rights fetched:&quot;, myRights);
    } catch (error) {
        console.error(&quot;Luna: Error fetching user rights:&quot;, error);
        alert(&quot;Luna: An error occurred while fetching your user rights. Please try again.&quot;);
        return;
    }
    if (!myRights || myRights.length === 0) {
        console.error(&quot;Luna: User rights array is empty or undefined.&quot;);
        alert(&quot;Luna: An error occurred while fetching your user rights. Please try again.&quot;);
        return;
    }

    if (myRights.includes(&quot;autoconfirmed&quot;)) {
        if (!myRights.includes(&quot;rollback&quot;)) {
            console.log(&quot;Luna: Not a patroller or administrator.&quot;);
            window.isPatroller = false;
        }

        mw.loader.load('jquery.ui');

        console.log(&quot;Luna: Loading preferences script...&quot;);
        try {
            await $.getScript(`/w/index.php?title=User:JJPMaster/luna/pref/unstable.js&amp;action=raw&amp;ctype=text/javascript&amp;cb=${Date.now()}`); // Backlink: [[User:JJPMaster/luna/pref/unstable.js]]
            console.log(&quot;Luna: Preferences loaded successfully.&quot;);
        } catch (error) {
            console.error(&quot;Luna: Failed to load preferences script:&quot;, error);
            return;
        }
        mw.loader.load('/w/index.php?title=User:JJPMaster/luna.css&amp;action=raw&amp;ctype=text/css', 'text/css');

        console.log(&quot;Luna: Adding UI elements...&quot;);
        mw.util.addPortlet('luna-actions', 'Luna', '#p-cactions');

        await loadScripts();
		// window.LunaScriptsLoaded = true;
		waitForLunaLinksToSettle(() =&gt; renderLunaPortlet());
    } else {
        console.error(&quot;Luna: User is not autoconfirmed.&quot;);
        mw.notify(&quot;Error: You must be autoconfirmed to use Luna.&quot;);
    }
})();</text>
      <sha1>i7y5ph3roxn10u889751toury0cbl2n</sha1>
    </revision>
  </page>
  <page>
    <title>User:JJPMaster/luna/templateunlink.js</title>
    <ns>2</ns>
    <id>472307</id>
    <revision>
      <id>4676665</id>
      <parentid>4662628</parentid>
      <timestamp>2026-10-18T02:53:17Z</timestamp>
      <contributor>
        <username>JJPMaster</username>
        <id>3095725</id>
      </contributor>
      <minor />
      <comment>replace &quot;isReviewer&quot; with &quot;isPatroller&quot; (via JWB)</comment>
      <origin>4676665</origin>
      <model>javascript</model>
      <format>text/javascript</format>
      <text bytes="2280" sha1="snb6a0ws97cw8ahy6qc3iyxynl7wnxa" xml:space="preserve">// &lt;nowiki&gt;
if (mw.config.get(&quot;wgNamespaceNumber&quot;) &gt;= 0 &amp;&amp; window.isPatroller) {
	var tempunlinkLink = window.addLunaLink({
		id: 'luna-tempunlink', 
		text: 'Unlink (transclusions)', 
		href: '#', 
		tooltip: 'Remove all transclusions of this page',
		onClick: templateUnlink
	}); 
}
	
var templateTitle = mw.config.get(&quot;wgCanonicalNamespace&quot;) == &quot;Template&quot; ? mw.config.get(&quot;wgPageName&quot;).substr(9) : mw.config.get(&quot;wgPageName&quot;);
async function getTransclusions() {
    var params = {
		action: 'query',
		format: 'json',
		list: 'embeddedin',
		eilimit: 'max',
		eititle: mw.config.get(&quot;wgPageName&quot;)
	},
	api = new mw.Api();

	const data = await api.get(params);
	return data.query.embeddedin;
}
async function getTemplateUnlinkedContent(title, unlinked) {
	var params = {
		action: 'parse',
		page: title,
		prop: 'wikitext',
		format: 'json'
	},
	api = new mw.Api();
	const data = await api.get(params);
	var text = data.parse.wikitext['*'];
	var myPage = new Morebits.wikitext.Page(text);
	var newText = myPage.removeTemplate(unlinked).getText();
	return newText;
}
	
async function templateUnlink() {
	if (window.isPatroller) {
		var doIt = confirm(&quot;You are about to remove all of the transclusions of this page. If you mess up, this is likely to be very difficult to reverse. Are you *ABSOLUTELY SURE* you want to do this?&quot;);
		if (!doIt) return;
		var trans = await getTransclusions();
		var params, api;
		for (var t of trans) {
			var content = await getTemplateUnlinkedContent(t.title, templateTitle);
			params = {
				action: 'edit',
				format: 'json',
				text: content,
				title: t.title,
				summary: `Removing transclusion(s) of [[${mw.config.get(&quot;wgPageName&quot;).replace(/_/g, ' ')}]]`,
				tags: &quot;Luna&quot;
			};
			api = new mw.Api();
			
			try {
				var data = await api.postWithToken( 'csrf', params );
				console.log(data)
			}
			catch (error) {
				console.error(&quot;Luna: Unlink failed.&quot;, error)
			}
		}
		var remaining = await getTransclusions();
		if (remaining.length &gt; 0) 
			alert(&quot;It looks like not all of the transclusions were removed. This is most likely because you hit the rate limit. Please try again later.&quot;);
		else alert(&quot;Done!&quot;);
	}
	else {
		alert(&quot;Luna: You must be a reviewer or administrator to use this tool.&quot;);
		return;
	}
}
// &lt;/nowiki&gt;</text>
      <sha1>snb6a0ws97cw8ahy6qc3iyxynl7wnxa</sha1>
    </revision>
  </page>
  <page>
    <title>Chess/Glossary</title>
    <ns>0</ns>
    <id>476457</id>
    <revision>
      <id>4676575</id>
      <parentid>4597564</parentid>
      <timestamp>2026-10-17T19:46:12Z</timestamp>
      <contributor>
        <username>WereSpielChequers</username>
        <id>248949</id>
      </contributor>
      <comment>typo</comment>
      <origin>4676575</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="5138" sha1="428bgea0oisf2laskys06k6u8r8kncr" xml:space="preserve">=Pieces=
There are 7 pieces in chess. All pieces can be blocked with exception to the Knight.
===Pawn===
The pawn moves one square forward but captures diagonally. However, on its first turn, it can move 2 spaces.
===Bishop===
The bishop moves diagonally in any direction. Because it can only move diagonally, it can only go to a square of the same colour as its home square. 
===Knight===
The Knight moves two spaces laterally and then makes a 90 degree turn in either direction and then moves one square laterally, forming an L shape. It is also the only piece that can jump, which means that its path cannot be blocked.
===Rook===
The Rook moves laterally.
===Queen===
The Queen moves like both a Rook and a Bishop, as if they were combined.
===King===
The kings moves one space in any direction, laterally or diagonally.
=Chess Terms=

==Special moves==
This section covers moves other than mentioned above.
===Castling===
During castling, the king moves two spaces and the rook moves over the king next to the king on the other side of the king.

There are a few requirements for castling:
#There cannot be any piece in between the king and the rook
#The king cannot travel through a space where it can be captured.
#The king must not be able to be captured after castling.
#The king must not be in check.
#The king and rook must be on the same rank.
#Neither the king nor the Rook can have previously moved.

===En passant===
When one side’s pawn moves to spaces, and the opposing side’s pawn is next to it(either on their left or right), the opposing side can capture it as though it had only moved 1 space.

==Tactics==

===Double attack===
====Discovered Attack====
When one piece is blocking the vision of the piece behind it and one moves that piece, causing the piece behind it to be able to attack an opponents piece. Generally either the piece moved is also attacking an opponents piece, and since it is impossible to move both pieces at the same time, Black has to give one up, or taking an opponents piece that was adequately defended, so Black has to move the attacked piece and let the piece that just took something move, or take the piece that took something and lose the attacked piece.
=====Double check=====
When the opponent’s king is attacked twice. This is especially potent because you cannot block (as the king would still be in check by the other piece) and you cannot capture either piece (as the other piece would still check the king), so the only option is to move. If the king cannot move, it is checkmate.
====Forks====
See [[Chess/Glossary#Fork|Fork]]

===Fork===
When two pieces are attacked at the same time by the same piece. Knights are especially good at forking because no other piece can take the knight when the knight is attacking it except for the knight.

===Pin===
When a piece is attacking another piece and the piece behind is of higher value.

===Skewer===

When a piece is attacking another piece and moving the attacked piece would expose a lower valued piece behind it.

==Relating to the opening==
===Development===
How many active pieces an opponent has. When one side has more active pieces, they are considered to have the ''lead in development''.
===Fianchetto===
Instead of developing towards the centre, you develop the bishop to b2/b7/g2/g7. The bishop is good here because it can protect the king when castled, allowing one to push pawns in front of the king (which is usually a bad idea). Furthermore, the bishop can control important squares in the centre. This is a feature of hypermodern openings.
===Gambit===
When one sacrifices a piece (usually a pawn) for a lead in development(like the Danish gambit) or better central control (like the Queen’s gambit).

==Mate names==
===Anastasia’s mate===
{{Chess diagram small
|tleft
|
|rd|  |  |qd|  |rd|  |  |=
|pd|pd|  |nd|nl|pd|pd|kd|=
|  |  |pd|pl|  |  |  |  |=
|  |  |  |  |  |  |  |ql|=
|  |  |  |  |  |  |  |  |=
|  |  |nl|  |  |  |  |  |=
|pl|pl|pl|  |  |pl|pl|  |=
|rl|  |  |  |  |kl|  |  |=


}}
When the rook or queen is on the edge of the board, checking the king on h2 / a2, and the knight cuts off the escape squares, therefore leading to mate. Usually occurs after a sacrifice on h2 / a2.

===Arabian mate===

{{Chess diagram small
|tright
|
|  |  |  |  |  |  |  |kd|=
|  |  |  |  |  |  |  |rl|=
|  |  |  |  |  |nl|  |  |=
|  |  |  |  |  |  |  |  |=
|bd|  |  |  |  |  |  |  |=
|  |  |  |  |  |  |  |  |=
|  |  |  |  |kl|  |  |  |=
|  |  |  |rd|  |  |  |  |
}}

A mate that occurs when the king is cornered and the knight and rook together deliver mate.

===Epaulette's mate===

This mate occurs when the king is sandwiched between two pieces (usually rooks) and is on the back rank, and the Queen herself delivers mate.

===Smothered mate===
When only the knight checks the king and the king has nowhere to go because it is blocked by its own pieces. No other pieces are required.

==Relating to Chess Tournaments==

===Touch-move rule===
Once you touch a piece, you must move it, unless the piece has no legal moves. Once you touch an opponent’s piece, you must capture it if possible.

{{BookCat}}</text>
      <sha1>428bgea0oisf2laskys06k6u8r8kncr</sha1>
    </revision>
  </page>
  <page>
    <title>OpenSCAD User Manual/Suggest Reduce Function</title>
    <ns>0</ns>
    <id>477065</id>
    <revision>
      <id>4676723</id>
      <parentid>4676291</parentid>
      <timestamp>2026-10-18T10:18:05Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <origin>4676723</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="732" sha1="3mec6p9llj4wfulgrka7fz99e8uzc4p" xml:space="preserve">==Implement a reduce() Function==
Not that i know how to do this .. but i did find a good explanation of what would be needed and started this page 

[[w:Fold_(higher-order_function)#Evaluation_order_considerations|Issues to do with reduce in a functional language]]

I believe it has been done here: https://github.com/andy128k/scad_utils/blob/2c6b2fa847380a17bfbced4d7235f884330cd06a/lists.scad#L76

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
 // Fold
 function list_fold(list, func, acc = undef, index = 0) =
   index &gt;= len(list)
     ? acc
     : list_fold(list, func, func(acc, list[index]), index + 1);
&lt;/syntaxhighlight&gt;

For example, &lt;code&gt;echo(list_fold([1,2,3], function(a, b) a + b, 0));&lt;/code&gt; will echo &lt;code&gt;6&lt;/code&gt;.

{{BookCat}}</text>
      <sha1>3mec6p9llj4wfulgrka7fz99e8uzc4p</sha1>
    </revision>
  </page>
  <page>
    <title>User:Dom walden/Multivariate Analytic Combinatorics/Stratified Singular Varieties</title>
    <ns>2</ns>
    <id>480707</id>
    <revision>
      <id>4676700</id>
      <parentid>4632543</parentid>
      <timestamp>2026-10-18T08:08:02Z</timestamp>
      <contributor>
        <username>Dom walden</username>
        <id>3209423</id>
      </contributor>
      <comment>/* Whitney stratification */ change l to \mathcal{l}</comment>
      <origin>4676700</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="21312" sha1="014op60tsme8pbsm9p5nqjjodvabfo4" xml:space="preserve">== Introduction ==

We hinted in the [[User:Dom_walden/Multivariate_Analytic_Combinatorics/Cauchy-Hadamard_Theorem_and_Exponential_Bounds#Domain_of_convergence|previous chapter]] that singularities and the domain of convergence in the multivariate case are more complicated than in the univariate case. In this chapter, we present this in more detail.

First, we demonstrate the different types of what, in the multivariate case, are called '''singular varieties'''. Second, we show how to decompose the more complex singular varieties using '''Whitney stratification'''. Finally, we present '''critical points''' as the points of the singular varieties we are interested in for asymptotics.

== Singular varieties ==

For a function &lt;math display=&quot;inline&quot;&gt;F(z) = \frac{P(z)}{Q(z)}&lt;/math&gt; with &lt;math display=&quot;inline&quot;&gt;z \in \C^d&lt;/math&gt;, we define the '''singular variety''' &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt; the set of points in &lt;math display=&quot;inline&quot;&gt;\C^d&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;Q(z) = 0&lt;/math&gt;, i.e. &lt;math display=&quot;inline&quot;&gt;\mathcal{V} = \{ z \in \C^d : Q(z) = 0 \}&lt;/math&gt;.

As we saw in the single variable (&lt;math display=&quot;inline&quot;&gt;z \in \C&lt;/math&gt;), [[Analytic_Combinatorics/Meromorphic_Functions|meromorphic]] case, &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt; consisted of isolated points.

In the multivariate case, this can be much more complicated and can consist of one or more of the following:
* A single hyperplane
* Intersecting hyperplanes (called arrangements which may or may not be transverse)
* A cone (called cone points)

=== Complex hyperplanes ===

For complex vectors &lt;math display=&quot;inline&quot;&gt;z = (x_1 + iy_1, \cdots, x_d + iy_d)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;w = (u_1 + iv_1, \cdots, u_d + iv_d)&lt;/math&gt; the '''Hermitian scalar product''' is defined&lt;ref&gt;Shabat 1992, pp. 2.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;\langle z, w \rangle = \sum_{i=1}^d x_i u_i + \sum_{i=1}^d y_i v_i + i \sum_{i=1}^d (y_i u_i - x_i v_i).&lt;/math&gt;

A '''complex hyperplane''' means a set of points &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt; in complex space such that for a fixed, non-zero vector &lt;math display=&quot;inline&quot;&gt;a&lt;/math&gt; and constant complex number &lt;math display=&quot;inline&quot;&gt;b&lt;/math&gt;&lt;ref&gt;Shabat 1992, pp. 2.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;\langle z, a \rangle = b.&lt;/math&gt;

This happens when the set of points &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt; are perpendicular or '''orthogonal''' to &lt;math display=&quot;inline&quot;&gt;a&lt;/math&gt;.

[image?]

=== Single hyperplane ===

For example, for

&lt;math display=&quot;block&quot;&gt;F(x, y) = \frac{1}{1 - x - y} = \sum_{n \geq 0} \sum_{m \geq 0} \binom{n + m}{m} x^m y^n&lt;/math&gt;

there are singularities at any point in &lt;math display=&quot;inline&quot;&gt;\mathcal{V} = \{ (x, y) : 0 \leq x \leq 1, y = 1 - x \}&lt;/math&gt;. Below we see &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt; for different values of &lt;math display=&quot;inline&quot;&gt;|x|, |y|&lt;/math&gt;.&lt;ref&gt;Mishna 2020, pp. 143.&lt;/ref&gt;

[[File:Singular variety of generating function for binomial coefficients.png|400px]]

Bear in mind that the above graph loses some information due to the axes being the modulus of the two inputs &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt;. For example, &lt;math display=&quot;inline&quot;&gt;|x| = |y| = 1&lt;/math&gt; is a singularity when &lt;math display=&quot;inline&quot;&gt;x = (1/2, i \sqrt{3}/2)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;y = (1/2, -i \sqrt{3}/2)&lt;/math&gt; (roughly).

=== Intersecting hyperplanes ===

For example, for

&lt;math display=&quot;block&quot;&gt;F(x, y) = \frac{1}{(3-2x-y)(3-x-2y)}&lt;/math&gt;

the singular variety is a union of two singular varieties, &lt;math display=&quot;inline&quot;&gt;\mathcal{V}_{3-2x-y} = \{ (x, y) : y = 3 - 2x \}&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\mathcal{V}_{3-x-2y} = \{ (x, y) : y = \frac{3 - x}{2} \}&lt;/math&gt;. We use the definition of the scalar product above to demonstrate that both are complex hyperplanes. For &lt;math display=&quot;inline&quot;&gt;x = x_0 + ix_1&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;y = y_0 + iy_1&lt;/math&gt; and some fixed vector &lt;math display=&quot;inline&quot;&gt;(u_0 + iu_1, v_0 + iv_1) \in \C^2&lt;/math&gt; the scalar product is

&lt;math display=&quot;block&quot;&gt;\langle (x, y), (u, v) \rangle = x_0 u_0 + y_0 v_0 + x_1 u_1 + y_1 v_1 + i((x_1 u_0 - x_0 u_1) + (y_1 v_0 - y_0 v_1)) = b&lt;/math&gt;

for constant complex number &lt;math display=&quot;inline&quot;&gt;b&lt;/math&gt;.

Below we see &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt;, plotting separately the real parts of &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt; (left figure) and the imaginary parts of &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt; (right figure). The left figure demonstrates that &lt;math display=&quot;inline&quot;&gt;\langle (x_0, y_0), (u_0, v_0) \rangle = x_0 u_0 + y_0 v_0 = c_0&lt;/math&gt; for fixed &lt;math display=&quot;inline&quot;&gt;c_0&lt;/math&gt; and the right that &lt;math display=&quot;inline&quot;&gt;\langle (x_1, y_1), (u_1, v_1) \rangle = x_1 u_1 + y_1 v_1 = c_1&lt;/math&gt; for fixed &lt;math display=&quot;inline&quot;&gt;c_1&lt;/math&gt;. Notice that the two blue graphs and the two yellow graphs have the same slope. Therefore, &lt;math display=&quot;inline&quot;&gt;(u_1, v_1)&lt;/math&gt; is just a translation of &lt;math display=&quot;inline&quot;&gt;(u_0, v_0)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;(-u_1, -v_1)&lt;/math&gt; is the same but flipped 180 degrees and, as a result, &lt;math display=&quot;inline&quot;&gt;\langle (x_0, y_0), (-u_1, -v_1) \rangle = -x_0 u_1 - y_0 v_1 = c_2&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\langle (x_1, y_1), (u_0, v_0) \rangle = x_1 u_0 + y_1 v_0 = c_3&lt;/math&gt;. Therefore, we can find our &lt;math display=&quot;inline&quot;&gt;b&lt;/math&gt;

&lt;math display=&quot;block&quot;&gt;\langle (x, y), (u, v) \rangle = c_0 + c_1 + i(c_2 + c_3) = b.&lt;/math&gt;

[union_of_hyperplanes.py]

We look at the point where &lt;math display=&quot;inline&quot;&gt;\mathcal{V}_{3-2x-y}&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\mathcal{V}_{3-x-2y}&lt;/math&gt; intersect and draw both their slopes or '''tangent spaces''', as shown in the below image. Taking all possible linear combinations of the vectors which form the basis of these tangent spaces, we get a space called the '''span''' of the vectors. When the span of the tangent spaces is equal to &lt;math display=&quot;inline&quot;&gt;\C^d&lt;/math&gt; (in our case &lt;math display=&quot;inline&quot;&gt;\C^2&lt;/math&gt;), we call these types of arrangements '''transverse'''.

[image?]

We can demonstrate this separately for the real and imaginary parts to show that &lt;math display=&quot;inline&quot;&gt;((r_0 + ir_1, s_0 + is_1) (t_0 + it_1, q_0 + iq_1))&lt;/math&gt; where &lt;math display=&quot;inline&quot;&gt;r_0, s_0&lt;/math&gt; is determined by the blue real, &lt;math display=&quot;inline&quot;&gt;t_0, q_0&lt;/math&gt; the yellow real, &lt;math display=&quot;inline&quot;&gt;r_1, s_1&lt;/math&gt; by the blue imaginary and &lt;math display=&quot;inline&quot;&gt;t_1, q_1&lt;/math&gt; by the yellow imaginary. We see that &lt;math display=&quot;inline&quot;&gt;((r_0, s_0), (t_0, q_0))&lt;/math&gt; spans the two-dimensional real space and &lt;math display=&quot;inline&quot;&gt;((r_1, s_1), (t_1, q_1))&lt;/math&gt; spans the two-dimensional &quot;imaginary&quot; space.

[union_of_hyperplanes_tangent_spaces.py]

Another example, for

&lt;math display=&quot;block&quot;&gt;F(x, y) = \frac{1}{(3 - 2x - y)(3 - x - 2y)(2 - x - y)}&lt;/math&gt;

all three singular varieties &lt;math display=&quot;inline&quot;&gt;\mathcal{V}_{3 - 2x - y} = \{ (x, y) : y = 3 - 2x \}&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;\mathcal{V}_{3 -x - 2y} = \{ (x, y) : y = \frac{3 - x}{2} \}&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\mathcal{V}_{2 - x - y} = \{ (x, y) : y = 2 - x \}&lt;/math&gt; intersect at &lt;math display=&quot;inline&quot;&gt;(1, 1)&lt;/math&gt;. Their slopes are much like our first example in this section but with an extra one slope which is a combination of the other two slopes [example?]. Therefore, they are not transverse. Instead, we look at the set of points where the hyperplanes intersect, called the '''intersection lattice''', and the set of points where their tangent planes intersect (also called the intersection lattice). If these are equal, it is an '''arrangement'''.&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 329.&lt;/ref&gt;

[union_of_hyperplanes_arrangement2.py]

However, note that the three hyperplanes are transverse when taken pairwise. We will show how to decompose such an arrangement in later chapters.

A final example of something that is not an arrangement, for

&lt;math display=&quot;block&quot;&gt;F(x, y) = \frac{1}{(2 - x - y)(1 - xy)}&lt;/math&gt;

the singular varieties &lt;math display=&quot;inline&quot;&gt;\mathcal{V}_{2 - x - y} = \{ (x, y) : y = 2 - x \}&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\mathcal{V}_{1 - xy} = \{ (x, y) : y = 1/x \}&lt;/math&gt; intersect at &lt;math display=&quot;inline&quot;&gt;(1, 1)&lt;/math&gt; with identical slopes and, therefore, cannot span more than one dimension and, therefore, are not transverse. Nor are they arrangements as the intersection lattice of their hyperplanes is a single point (&lt;math display=&quot;inline&quot;&gt;(1, 1)&lt;/math&gt;) but the intersection lattice of their tangent planes is the line &lt;math display=&quot;inline&quot;&gt;y = 2 - x&lt;/math&gt;.&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 314.&lt;/ref&gt;

[union_of_hyperplanes_arrangement.py]

=== Cone point ===

The singular variety may look like a cone.

For example,

&lt;math display=&quot;block&quot;&gt;F(x, y) = \frac{1}{x^2 + y^2}&lt;/math&gt;

has singularities in the case that &lt;math display=&quot;inline&quot;&gt;y = ix&lt;/math&gt; or &lt;math display=&quot;inline&quot;&gt;y = -ix&lt;/math&gt;. When plotted, it looks like two cones whose points meet at the origin. This is not the same as a union of hyperplanes as this is a single variety [right?]

[cone_point.py]

Another example, for

&lt;math display=&quot;block&quot;&gt;F(x, y, z) = \frac{1}{1 + xyz - (1/3)(x + y + z + xy + yz + xz)}&lt;/math&gt;

the singular varieties meet at a single point &lt;math display=&quot;inline&quot;&gt;(1, 1, 1)&lt;/math&gt;.&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 228.&lt;/ref&gt;

== Whitney stratification ==

In the case of a single hyperplane we can skip this step. The '''Whitney stratification''' just contains one strata, &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt;.

Otherwise, our aim is to decompose &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt; into a union of (not necessarily connected) submanifolds such that:
# each submanifold is closed and smooth
# if &lt;math display=&quot;inline&quot;&gt;S_\alpha \subset \overline{S_\beta}&lt;/math&gt; then any sequences where &lt;math display=&quot;inline&quot;&gt;\{x_i\} \subset S_\beta&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\{y_i\} \subset S_\alpha&lt;/math&gt; which both converge to &lt;math display=&quot;inline&quot;&gt;y \in S_\alpha&lt;/math&gt;, the lines &lt;math display=&quot;inline&quot;&gt;\mathcal{l}_i = \overline{x_iy_i}&lt;/math&gt; converge to a line &lt;math display=&quot;inline&quot;&gt;\mathcal{l}&lt;/math&gt; and the tangent planes &lt;math display=&quot;inline&quot;&gt;T_{x_i}(S_\beta)&lt;/math&gt; converge to a plane &lt;math display=&quot;inline&quot;&gt;T&lt;/math&gt; then &lt;math display=&quot;inline&quot;&gt;T_y(S_\alpha) \subset T&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\mathcal{l} \subseteq T&lt;/math&gt; (these are the '''Whitney conditions'''.)&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 534.&lt;/ref&gt;

For example,

&lt;math display=&quot;block&quot;&gt;F(x, y) = \frac{1}{(1 - x)(1 - y)(1 - z)}&lt;/math&gt;

&lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt; consists of three planes where &lt;math display=&quot;inline&quot;&gt;x = 1&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;y = 1&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;z = 1&lt;/math&gt;. At the lines where they intersect they fail to be smooth. Therefore, we put the intersection lines in their own strata leaving us the strata:
* The &lt;math display=&quot;inline&quot;&gt;xy&lt;/math&gt; plane at &lt;math display=&quot;inline&quot;&gt;z = 1&lt;/math&gt; with the lines removed where &lt;math display=&quot;inline&quot;&gt;x = 1&lt;/math&gt; or &lt;math display=&quot;inline&quot;&gt;y = 1&lt;/math&gt;
* The &lt;math display=&quot;inline&quot;&gt;xz&lt;/math&gt; plane at &lt;math display=&quot;inline&quot;&gt;y = 1&lt;/math&gt; with the lines removed where &lt;math display=&quot;inline&quot;&gt;x = 1&lt;/math&gt; or &lt;math display=&quot;inline&quot;&gt;z = 1&lt;/math&gt;
* The &lt;math display=&quot;inline&quot;&gt;yz&lt;/math&gt; plane at &lt;math display=&quot;inline&quot;&gt;x = 1&lt;/math&gt; with the lines removed where &lt;math display=&quot;inline&quot;&gt;y = 1&lt;/math&gt; or &lt;math display=&quot;inline&quot;&gt;z = 1&lt;/math&gt;
* The line &lt;math display=&quot;inline&quot;&gt;\{ (1, 1, z) \in \C^3 \}&lt;/math&gt;
* The line &lt;math display=&quot;inline&quot;&gt;\{ (1, y, 1) \in \C^3 \}&lt;/math&gt;
* The line &lt;math display=&quot;inline&quot;&gt;\{ (x, 1, 1) \in \C^3 \}&lt;/math&gt;

This does not meet the Whitney conditions at all points. For example, any sequence of points along the &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt;-axis converging to a point on the &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt;-axis will have tangents along the &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt;-axis, but any point on the &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt;-axis to which it converges will have tangent along the &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt;-axis. Therefore, we need to separate the point &lt;math display=&quot;inline&quot;&gt;(1, 1, 1)&lt;/math&gt; into its own strata.&lt;ref&gt;Mishna 2020, pp. 179.&lt;/ref&gt;

Sometimes, we can work out a Whitney Stratification by hand, like above. Other times, we may need to use software to help us. [explain]

== Critical points ==

[explain gradient as vector, greatest increase and orthogonal to level set and directional derivative as scalar]

[why do we use a height function?]

We have a height function &lt;math display=&quot;inline&quot;&gt;h_r(z) = - \sum_{i=1}^d r_i \log(|z_i|)&lt;/math&gt; with '''gradient''' given by the vector &lt;math display=&quot;inline&quot;&gt;[-r_1/z_1, \cdots, -r_d/z_d]&lt;/math&gt;.

For each strata, we want to find out where the '''directional derivative''' of our height function, when restricted to that strata, equals zero. The point at which this happens is called a '''critical point'''.

Suppose we have function &lt;math display=&quot;inline&quot;&gt;f(x, y) = \frac{1}{1 - x - y}&lt;/math&gt;. We draw the graph of &lt;math display=&quot;inline&quot;&gt;q(x, y) = 1 - x - y&lt;/math&gt; below. Where it intersects the &lt;math display=&quot;inline&quot;&gt;xy&lt;/math&gt;-plane, i.e. where &lt;math display=&quot;inline&quot;&gt;q(x, y)&lt;/math&gt; is zero, is the singular variety &lt;math display=&quot;inline&quot;&gt;\mathcal{V} = \{ (x, y) : 0 \leq x \leq 1, y = 1 - x \}&lt;/math&gt;. It is a level set. Notice that the gradient of &lt;math display=&quot;inline&quot;&gt;q(x, y)&lt;/math&gt; is the constant &lt;math display=&quot;inline&quot;&gt;[-1, -1]&lt;/math&gt;, which is orthogonal to the (tangent plane of the) variety and which we draw as arrows in the below graph.

[graph of q]

Suppose we are interested in the coefficients in the direction &lt;math display=&quot;inline&quot;&gt;(1, 1)&lt;/math&gt;. We draw the graph of &lt;math display=&quot;inline&quot;&gt;h_{(1,1)} = -\log x - \log y&lt;/math&gt; below. The red[?] line is the variety &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt;. The variety is in the direction &lt;math display=&quot;inline&quot;&gt;(-1, 1)&lt;/math&gt; (or &lt;math display=&quot;inline&quot;&gt;(1, -1)&lt;/math&gt;) and, therefore, the directional derivative is &lt;math display=&quot;inline&quot;&gt;1/x - 1/y&lt;/math&gt; (or &lt;math display=&quot;inline&quot;&gt;1/y - 1/x&lt;/math&gt;). This is zero when &lt;math display=&quot;inline&quot;&gt;x = y&lt;/math&gt; and this only happens at the critical point &lt;math display=&quot;inline&quot;&gt;(x, y) = (1/2, 1/2)&lt;/math&gt;. The gradient of the height function is &lt;math display=&quot;inline&quot;&gt;[-1/x, -1/y]&lt;/math&gt;, which we draw as arrows in the below graph. The directional derivative being zero means at the critical point the direction of greatest increase is orthogonal to the tangent plane of the variety.

Therefore, the gradient of &lt;math display=&quot;inline&quot;&gt;q&lt;/math&gt; and the gradient of &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; must be parallel at the critical point.

[graph of h]

The above shows a graph of this. The critical point is highlighted in red. The value of the height function at the critical point, its '''critical value''', is roughly &lt;math display=&quot;inline&quot;&gt;1.4&lt;/math&gt;.

If we change the direction to &lt;math display=&quot;inline&quot;&gt;(1, 2)&lt;/math&gt;, the gradient changes to &lt;math display=&quot;inline&quot;&gt;dh(x, 1 - x) = [-1/x, -2/y]&lt;/math&gt; and the critical point changes to &lt;math display=&quot;inline&quot;&gt;(x, y) = (1/3, 2/3)&lt;/math&gt; with critical value of roughly &lt;math display=&quot;inline&quot;&gt;1.9&lt;/math&gt;. This is graphed below.

[graph of h12]

So we need to find the point where the gradient of &lt;math display=&quot;inline&quot;&gt;q&lt;/math&gt; and the gradient of &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; are not linearly independent and, therefore, at the critical point &lt;math display=&quot;inline&quot;&gt;w&lt;/math&gt;, the below matrix has rank equal to 1.

&lt;math display=&quot;block&quot;&gt;\begin{pmatrix}
  \partial f / \partial z_1 (w) &amp; \cdots &amp; \partial f / \partial z_d (w) \\
  r_1/w_1 &amp; \cdots &amp; r_d/w_d
 \end{pmatrix}&lt;/math&gt;

This happens when all the &lt;math display=&quot;inline&quot;&gt;2 \times 2&lt;/math&gt; '''minors''' of the matrix have '''determinants''' equal to zero, which is equivalent to the system of equations

&lt;math display=&quot;block&quot;&gt;r_k w_1 \partial f/\partial z_1 (w) - r_1 w_k \partial f/\partial z_k (w) = 0 \quad (2 \leq k \leq d)&lt;/math&gt;

combined with the equation &lt;math display=&quot;inline&quot;&gt;f(w) = 0&lt;/math&gt;.&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 200.&lt;/ref&gt;

An example with more than one strata.

&lt;math display=&quot;block&quot;&gt;F(x, y, z) = \frac{1}{A(x, y, z) B(x, y, z)} = \frac{1}{(4 - x - 2y - z)(4 - 2x - y - z)}&lt;/math&gt;

It has one strata where &lt;math display=&quot;inline&quot;&gt;A(x, y, z) = 0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;B(x, y, z) \neq 0&lt;/math&gt;. The matrix defining the critical point on this strata is

&lt;math display=&quot;block&quot;&gt;\begin{pmatrix}
  x A_x &amp; y A_y &amp; z A_z \\
  r &amp; s &amp; t
 \end{pmatrix}&lt;/math&gt;

leading to the system of equations

&lt;math display=&quot;block&quot;&gt;\begin{align}
A(x, y, z) = 4 - x - 2y - z &amp;= 0 \\
tx - rz &amp;= 0 \\
2ty - sz &amp;= 0
\end{align}&lt;/math&gt;

giving the critical point &lt;math display=&quot;inline&quot;&gt;(x, y, z) = \frac{1}{r + s + t}(4r, 2s, 4t)&lt;/math&gt; unless &lt;math display=&quot;inline&quot;&gt;2r = s&lt;/math&gt;.

It has another strata where &lt;math display=&quot;inline&quot;&gt;B(x, y, z) = 0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;A(x, y, z) \neq 0&lt;/math&gt;. The matrix defining the critical point on this strata is

&lt;math display=&quot;block&quot;&gt;\begin{pmatrix}
  x B_x &amp; y B_y &amp; z B_z \\
  r &amp; s &amp; t
 \end{pmatrix}&lt;/math&gt;

leading to the system of equations

&lt;math display=&quot;block&quot;&gt;\begin{align}
B(x, y, z) = 4 - 2x - y - z &amp;= 0 \\
2tx - rz &amp;= 0 \\
ty - sz &amp;= 0
\end{align}&lt;/math&gt;

giving the critical point &lt;math display=&quot;inline&quot;&gt;(x, y, z) = \frac{1}{r + s + t}(2r, 4s, 4t)&lt;/math&gt; unless &lt;math display=&quot;inline&quot;&gt;2s = r&lt;/math&gt;.

For the strata defined by the simultaneous vanishing of &lt;math display=&quot;inline&quot;&gt;A&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;B&lt;/math&gt;. This is one-dimensional and the gradients of &lt;math display=&quot;inline&quot;&gt;A&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;B&lt;/math&gt; span a one or two-dimensional space orthogonal to this strata. At the critical point, the gradient of &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; is in the space spanned by the former two gradients. Therefore, we have the matrix

&lt;math display=&quot;block&quot;&gt;\begin{pmatrix}
  x A_x &amp; y A_y &amp; z A_z \\
  x B_x &amp; y B_y &amp; z B_z \\
  r &amp; s &amp; t
 \end{pmatrix}&lt;/math&gt;

and this time we want the vanishing of the determinant of the &lt;math display=&quot;inline&quot;&gt;3 \times 3&lt;/math&gt; minor, giving the system of equations

&lt;math display=&quot;block&quot;&gt;\begin{align}
4 - x - 2y - z &amp;= 0 \\
4 - 2x - y - z &amp;= 0 \\
ryz + sxz - 3txy &amp;= 0
\end{align}&lt;/math&gt;

which has the critical point &lt;math display=&quot;inline&quot;&gt;\frac{4}{3(r + s + t)}(r + s, r + s, 3t)&lt;/math&gt;.&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 246-248.&lt;/ref&gt;

[graph_of_ab_1.py]

== Computing Whitney stratifications and critical points ==

Suppose we have &lt;math display=&quot;inline&quot;&gt;F(z) = \frac{P(z)}{Q(z)}&lt;/math&gt; and a Whitney Stratification &lt;math display=&quot;inline&quot;&gt;\mathcal{V} = \mathcal{V}_0 \supset \mathcal{V}_1 \supset \cdots \supset \mathcal{V}_m = \empty&lt;/math&gt;.

&lt;math display=&quot;inline&quot;&gt;\mathcal{V}_0&lt;/math&gt; is defined by the vanishing of &lt;math display=&quot;inline&quot;&gt;Q&lt;/math&gt;. &lt;math display=&quot;inline&quot;&gt;Q&lt;/math&gt; may be able to be factorised as a product of polynomials &lt;math display=&quot;inline&quot;&gt;Q(z) = A(z)B(z) \cdots&lt;/math&gt;. We work this out using ideals and primary decomposition.

&lt;syntaxhighlight&gt;
i1 : S=QQ[z_1, ..., z_d]
i2 : primaryDecomposition ideal(Q)
o2 = {ideal(A), ideal(B), ...}
i3 : groebnerBasis ideal(A)
o3 = | A_1 A_2 ... |
i3 : groebnerBasis ideal(B)
o3 = | B_1 B_2 ... |
...
i4 : codim ideal(Q)
o4 = c
...
&lt;/syntaxhighlight&gt;

Then for each &lt;math display=&quot;inline&quot;&gt;A, B, \cdots&lt;/math&gt; we solve the system of equations defined by

&lt;math display=&quot;block&quot;&gt;\begin{pmatrix}
  \nabla A_1 \\
  \nabla A_2 \\
  \cdots \\
  r_1/z_1 \cdots r_d/z_d
 \end{pmatrix}&lt;/math&gt;

The critical point happens at the &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt; where the matrix has rank &lt;math display=&quot;inline&quot;&gt;c&lt;/math&gt;, the &lt;math display=&quot;inline&quot;&gt;A_i&lt;/math&gt; vanish and the generating set of &lt;math display=&quot;inline&quot;&gt;\mathcal{V}_1&lt;/math&gt; do not vanish.

We repeat a similar process than above with &lt;math display=&quot;inline&quot;&gt;\mathcal{V}_1&lt;/math&gt;, which is defined by the simultaneous vanishing of the &lt;math display=&quot;inline&quot;&gt;A(z), B(z), \cdots&lt;/math&gt;.

&lt;syntaxhighlight&gt;
i1 : S=QQ[z_1, ..., z_d]
i2 : primaryDecomposition ideal(A, B, ...)
o2 = {ideal(A_0, B_0, ...)}
i3 : groebnerBasis ideal(A_0)
o3 = | A_1 A_2 ... |
i3 : groebnerBasis ideal(B_0)
o3 = | B_1 B_2 ... |
...
i4 : codim ideal(A, B, ...)
o4 = c
...
&lt;/syntaxhighlight&gt;

[ https://melczer.ca/textbook/ ]

== Notes ==
{{Reflist}}

== References ==
* {{cite book | last=Melczer | first=Stephen | title=An Invitation to Analytic Combinatorics: From One to Several Variables | publisher=Springer Texts &amp; Monographs in Symbolic Computation | year=2021 | url=https://melczer.ca/files/Melczer-SubmittedManuscript.pdf }}
* {{cite book | last=Mishna | first=Marni | title=Analytic Combinatorics: A Multidimensional Approach | publisher=Taylor &amp; Francis Group, LLC | year=2020 }}
* {{cite book | last1=Pemantle | first1=Robin | last2=Wilson | first2=Mark C. | last3=Melczer | first3=Stephen | title=Analytic Combinatorics in Several Variables | publisher=Cambridge University Press | year=2024 | edition=2nd | url=https://acsvproject.com/PemantleWilsonMelczer23.pdf }}
* {{cite book | last=Shabat | first=B. V. | title=Introduction to Complex Analysis. Part II: Functions of Several Variables | publisher=American Mathematical Society, Providence, Rhode Island | year=1992 }}</text>
      <sha1>014op60tsme8pbsm9p5nqjjodvabfo4</sha1>
    </revision>
  </page>
  <page>
    <title>User:Dom walden/Multivariate Analytic Combinatorics/Homology of Critical Points</title>
    <ns>2</ns>
    <id>480750</id>
    <revision>
      <id>4676705</id>
      <parentid>4676481</parentid>
      <timestamp>2026-10-18T08:15:42Z</timestamp>
      <contributor>
        <username>Dom walden</username>
        <id>3209423</id>
      </contributor>
      <comment>/* Fringed sets */ Proof for A_2 (incomplete)</comment>
      <origin>4676705</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="59660" sha1="a59sphoneaai5k352gi0k70xhf811tg" xml:space="preserve">== Introduction ==

Morse theory tells us that the topology of M only changes at its critical points.

The &quot;Morse data&quot; tells us the topology at each critical point.

Attaching this Morse data together gives us a space which is homopotically eqivalent to M.

This space is a &quot;cell complex&quot;, which has an easy to calculate homology.

Theorem: Our domain of convergence is homotopic to a cell complex of dimension at most &lt;math display=&quot;inline&quot;&gt;2n - d - 1&lt;/math&gt;.&lt;ref&gt;This is theorem D.23 in Pemantle, Wilson and Melczer 2024, pp. 546. Also theorem in section 1.2*/5.2* in SMT pp. 200.&lt;/ref&gt;

Proof:
# &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; is our entire domain, &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt; our variety
# Project our entire domain to complex projective space &lt;math display=&quot;inline&quot;&gt;Z = \pi(X) \subset \C\mathbb{P}^n - H&lt;/math&gt; [define H]
# Define a linear subspace &lt;math display=&quot;inline&quot;&gt;G \subset \C\mathbb{P}^n&lt;/math&gt; of dimension &lt;math display=&quot;inline&quot;&gt;d - 1&lt;/math&gt;
# Define a Morse function on &lt;math display=&quot;inline&quot;&gt;f: \C\mathbb{P}^n \to \R&lt;/math&gt; which approximates the distance from &lt;math display=&quot;inline&quot;&gt;G&lt;/math&gt; and such that &lt;math display=&quot;inline&quot;&gt;f^{-1}(0) = G&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;f^{-1}(1) = H&lt;/math&gt;
# We &quot;build&quot; &lt;math display=&quot;inline&quot;&gt;X - \mathcal{V}&lt;/math&gt; from &lt;math display=&quot;inline&quot;&gt;\pi^{-1}(G \cap Z) \cap (X - \mathcal{V})&lt;/math&gt; by attaching CW complexes at critical points which are of at most dimension &lt;math display=&quot;inline&quot;&gt;2n - d - 1&lt;/math&gt;
# At a critical point, the normal Morse data is &lt;math display=&quot;inline&quot;&gt;(J, K) = \coprod_x (J_x, K_x)&lt;/math&gt; and the relative complex link is &lt;math display=&quot;inline&quot;&gt;\mathcal{L}^\pi = \coprod_x \mathcal{L}_x&lt;/math&gt;
# We show that the quotient &lt;math display=&quot;inline&quot;&gt;J_x/K_x&lt;/math&gt; is homotopic to a CW complex of dimension &lt;math display=&quot;inline&quot;&gt;\leq 2n - d - 1&lt;/math&gt;
# The neighbourhood of &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; in &lt;math display=&quot;inline&quot;&gt;J_x&lt;/math&gt; is homeomorphic to the cone in &lt;math display=&quot;inline&quot;&gt;L_x(X - \mathcal{V})&lt;/math&gt;, and removing the point &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; increases the homotopy dimension to at most the homotopy dimension of &lt;math display=&quot;inline&quot;&gt;L_x&lt;/math&gt;
# &lt;math display=&quot;inline&quot;&gt;(J_x \cup \{x\}, K_x)&lt;/math&gt; is homotopic to &lt;math display=&quot;inline&quot;&gt;(\text{cone}(\mathcal{L}_x), \mathcal{L}_x)&lt;/math&gt;
# &lt;math display=&quot;inline&quot;&gt;\mathcal{L}_x&lt;/math&gt; is homotopic to a CW complex of dimension at most &lt;math display=&quot;inline&quot;&gt;2n - d - 1&lt;/math&gt;
# The tangential Morse data at the critical point is homotopic to the pair &lt;math display=&quot;inline&quot;&gt;(D^\lambda, \partial D^\lambda)&lt;/math&gt;
# Therefore, at each critical point a space has been added homotopic to a CW complex of dimension at most &lt;math display=&quot;inline&quot;&gt;2n - d - 1&lt;/math&gt;.

Theorem: If &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; is the complement in &lt;math display=&quot;inline&quot;&gt;\C^n&lt;/math&gt; of a complex variety &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt; of dimension &lt;math display=&quot;inline&quot;&gt;d&lt;/math&gt; then &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; is homotopic to a CW complex of dimension at most &lt;math display=&quot;inline&quot;&gt;2n - d - 1&lt;/math&gt;.&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 546.&lt;/ref&gt;

Proof:
# We build &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; by attaching cells of dimension at most &lt;math display=&quot;inline&quot;&gt;2n - d - 1&lt;/math&gt; at each critical point.
## Prove that we can do this without changing the homotopy(?)
## We use Thom's Isotopy Lemma to prove that there is a strong deformation retraction, stopping only at critical points.
# Prove these cells are a product of the normal and tangential Morse data.
## Normal data: &lt;math display=&quot;inline&quot;&gt;(\mathcal{L}(S), \partial \mathcal{L}(S)) \times (D^1, \partial D^1)&lt;/math&gt; [GM pp. 18]
## Tangential data: &lt;math display=&quot;inline&quot;&gt;(B_\delta \cap f^{-1}[v - \epsilon, v + \epsilon], B_\delta \cap f^{-1}(v - \epsilon))&lt;/math&gt; for &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; restricted to &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; (or &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt;?) [GM pp. 63-64]
# If &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt; is the dimension of the strata, then
## If &lt;math display=&quot;inline&quot;&gt;k = d&lt;/math&gt; then it is a smooth point and the cell is the product of &lt;math display=&quot;inline&quot;&gt;S^{2(n-d)-1}&lt;/math&gt; and the tangential data is dimension at most &lt;math display=&quot;inline&quot;&gt;d&lt;/math&gt;.
## If &lt;math display=&quot;inline&quot;&gt;k &lt; d&lt;/math&gt;, ...

&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 547.&lt;/ref&gt;

== Example in one dimension ==

Domain with singularities v_1, v_2, ..., v_i

Define our height function f...

Start with our entire domain X

Reduce from X to X_i+ by using Thom's Isotopy lemma to do a strong deformation retract

== Thom's isotopy lemma ==

We present a modified version of Thom's (first) isotopy lemma, less general than the original but more obviously relevant to our situation.

Theorem: Suppose &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; is a closed subset of a smooth manifold &lt;math display=&quot;inline&quot;&gt;M&lt;/math&gt; which admits a Whitney stratification and &lt;math display=&quot;inline&quot;&gt;h : M \to \R&lt;/math&gt; is a proper Morse function which has no critical values on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;. Then, the level sets of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; are homeomorphic by a homeomorphism that preserves the strata of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;.&lt;ref&gt;For various versions of the full statement of the theorem, see Mather 2012, pp. 499, Goresky and MacPherson 1988, pp. 41, or Pemantle, Wilson and Melczer 2024, pp. 541.&lt;/ref&gt;

Proof:
# Construct control data for &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; compatible with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;.
## [Prop 7.1] If &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; is smooth on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; and is a submersion for each strata then there exists a family of control data for &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; compatible with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 488.&lt;/ref&gt;
# This makes &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; an abstract stratified set and &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; a controlled submersion.
# A controlled submersion has, for any smooth vector field on &lt;math display=&quot;inline&quot;&gt;\R&lt;/math&gt;, a controlled vector field on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; (a &quot;lift&quot;?)&lt;ref&gt;Mather 2012, pp. 493.&lt;/ref&gt;
# A controlled vector field has a unique one-parameter family of homeomorphisms of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; which commute with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 496.&lt;/ref&gt;
# This makes &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; a locally trivial fibration. [Prop 10.2]&lt;ref&gt;Mather 2012, pp. 499.&lt;/ref&gt;

Control data:

A system of '''control data''' for &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; consists of, for each stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;,
* a '''tubular neighbourhood''' &lt;math display=&quot;inline&quot;&gt;T_X&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt;
* a '''tubular projection function''' &lt;math display=&quot;inline&quot;&gt;\pi_X: T_X \to X&lt;/math&gt;, and
* a '''tubular distance function''' &lt;math display=&quot;inline&quot;&gt;\rho_X: T_X \to \R&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;\rho_X^{-1}(0) = X&lt;/math&gt;&lt;ref&gt;Goresky and MacPherson 1988, pp. 42.&lt;/ref&gt;

[illustration]

such that if &lt;math display=&quot;inline&quot;&gt;X &lt; Y&lt;/math&gt; are strata in &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;, then

&lt;math display=&quot;block&quot;&gt;\pi_X \pi_Y(m) = \pi_X(m),&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;\rho_X \pi_Y(m) = \rho_X(m)&lt;/math&gt;

for all &lt;math display=&quot;inline&quot;&gt;m \in |T_X| \cap |T_Y|&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;\pi_Y(m) \in |T_X|&lt;/math&gt;.

If, for all strata &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; and all &lt;math display=&quot;inline&quot;&gt;m \in |T_X|&lt;/math&gt;, we have &lt;math display=&quot;inline&quot;&gt;h \pi_X(m) = h(m)&lt;/math&gt;, then this control data will be said to be compatible with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 488.&lt;/ref&gt;

We prove that if &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; is smooth on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; and is a submersion for each strata then there exists a family of control data for &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; compatible with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 488, prop 7.1.&lt;/ref&gt;

Let &lt;math display=&quot;inline&quot;&gt;Z_k&lt;/math&gt; be the union of strata of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; of dimension less than &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;. We prove by induction on &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;.

To construct the tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T_X&lt;/math&gt; of a stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of dimension less than &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;. For &lt;math display=&quot;inline&quot;&gt;l \leq k&lt;/math&gt;, let &lt;math display=&quot;inline&quot;&gt;U_l&lt;/math&gt; denote the union of all &lt;math display=&quot;inline&quot;&gt;|T_Y|&lt;/math&gt; for &lt;math display=&quot;inline&quot;&gt;Y &lt; X&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\dim Y \geq l&lt;/math&gt;. Let &lt;math display=&quot;inline&quot;&gt;X_l = U_l \cap X&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 489.&lt;/ref&gt;

For &lt;math display=&quot;inline&quot;&gt;l = k&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;X_k = \empty&lt;/math&gt;. Assume by induction that &lt;math display=&quot;inline&quot;&gt;T_{l+1}&lt;/math&gt; has been constructed and that if &lt;math display=&quot;inline&quot;&gt;Y &lt; X&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;\dim Y \geq l + 1&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;m \in |T_{l+1}| \cap |T_Y|&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi_{l+1}(m) \in |T_Y|&lt;/math&gt; (&lt;math display=&quot;inline&quot;&gt;\pi_{l+1} = \pi_{T_{l+1}}&lt;/math&gt;) then&lt;ref&gt;Mather 2012, pp. 489-490.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;\rho_Y \pi_{l+1}(m) = \rho_Y(m),&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;\pi_Y \pi_{l+1}(m) = \pi_Y(m).&lt;/math&gt;

We wish to construct a tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T_{X,Y}&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;|T_Y| \cap X&lt;/math&gt; whose restriction to &lt;math display=&quot;inline&quot;&gt;|T_Y| \cap X_{l+1}&lt;/math&gt; is isomorphic to the restriction of &lt;math display=&quot;inline&quot;&gt;T_{l+1}&lt;/math&gt; such that if &lt;math display=&quot;inline&quot;&gt;m \in |T_{X,Y}| \cap |T_Y|&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi_{X,Y}(m) \in |T_Y|&lt;/math&gt; (&lt;math display=&quot;inline&quot;&gt;\pi_{X,Y} = \pi_{T_{X,Y}}&lt;/math&gt;) then

&lt;math display=&quot;block&quot;&gt;\rho_Y \pi_{X,Y}(m) = \rho_Y(m),&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;\pi_Y \pi_{X,Y}(m) = \pi_Y(m).&lt;/math&gt;

By shrinking &lt;math display=&quot;inline&quot;&gt;|T_Y|&lt;/math&gt; if necessary, this relation is already satisfied if &lt;math display=&quot;inline&quot;&gt;m \in |T_{l+1}| \cap |T_Y|&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi_{l+1}(m) \in |T_Y|&lt;/math&gt; with &lt;math display=&quot;inline&quot;&gt;T_{l+1}&lt;/math&gt; in place of &lt;math display=&quot;inline&quot;&gt;T_{X,Y}&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi_{l+1}&lt;/math&gt; in place of &lt;math display=&quot;inline&quot;&gt;\pi_{X,Y}&lt;/math&gt;. By the definition, if &lt;math display=&quot;inline&quot;&gt;m \in |T_{l+1}|&lt;/math&gt; then there exists &lt;math display=&quot;inline&quot;&gt;Z &lt; X&lt;/math&gt; with &lt;math display=&quot;inline&quot;&gt;\dim Z &gt; l&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;m \in |T_Z|&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi_{l+1}(m) \in |T_Z|&lt;/math&gt;. We have that &lt;math display=&quot;inline&quot;&gt;\pi_{l+1}(m) \in |T_Y| \cap |T_Z|&lt;/math&gt; and therefore &lt;math display=&quot;inline&quot;&gt;Y &lt; Z&lt;/math&gt;. Therefore&lt;ref&gt;Mather 2012, pp. 490.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;\rho_Y \pi_{l+1}(m) = \rho_Y \pi_Z \pi_{l+1}(m) = \rho_Y \pi_Z(m) = \rho_Y(m),&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;\pi_Y \pi_{l+1}(m) = \pi_Y \pi_Z \pi_{l+1}(m) = \pi_Y \pi_Z(m) = \pi_Y(m).&lt;/math&gt;

We can prove that, by shrinking &lt;math display=&quot;inline&quot;&gt;|T_Y|&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;(\rho_Y, \pi_Y): |T_Y| \cap X \to \R \times Y&lt;/math&gt; is a submersion [prop 7.3?] and that &lt;math display=&quot;inline&quot;&gt;T_{X,Y}&lt;/math&gt; is compatible with &lt;math display=&quot;inline&quot;&gt;(\rho_Y, \pi_Y): |T_Y| \cap X_{l+1} \to \R \times Y&lt;/math&gt;, i.e. &lt;math display=&quot;inline&quot;&gt;(\rho_Y, \pi_Y) \pi_{X,Y}(m) = (\rho_Y, \pi_Y)(m)&lt;/math&gt;(?).

To prove it is a submersion, for the tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T = (E, \epsilon, \psi)&lt;/math&gt; there exists a smooth positive function &lt;math display=&quot;inline&quot;&gt;\epsilon'&lt;/math&gt; such that

&lt;math display=&quot;block&quot;&gt;(\rho_T, \pi_T): Y \cap |T|_{\epsilon'}^0 \to \R \times X,&lt;/math&gt;

where &lt;math display=&quot;inline&quot;&gt;|T|_{\epsilon'}^0 = \psi(B_\epsilon \cap B_{\epsilon'})&lt;/math&gt;, is a submersion. If &lt;math display=&quot;inline&quot;&gt;\Sigma&lt;/math&gt; is the set &lt;math display=&quot;inline&quot;&gt;y \in |T|&lt;/math&gt; such that the rank of

&lt;math display=&quot;block&quot;&gt;(\rho_T, \pi_T): T \cap |T| \to \R \times X&lt;/math&gt;

at &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt; is less than &lt;math display=&quot;inline&quot;&gt;\dim(\R \times X)&lt;/math&gt;. We need to prove that for any &lt;math display=&quot;inline&quot;&gt;x \in X&lt;/math&gt; there exists a neighbourhood of &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; which does not intersect with &lt;math display=&quot;inline&quot;&gt;\Sigma&lt;/math&gt;, i.e. the map is not a submersion in this neighbourhood. It follows from [lemma 7.2] that it is enough to prove for &lt;math display=&quot;inline&quot;&gt;M = \R^m&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;X = \R^{m-c} \times 0_c&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;T&lt;/math&gt; is the '''standard tubular neighbourhood'''.&lt;ref&gt;Mather 2012, pp. 489.&lt;/ref&gt;

By standard tubular neighbourhood, we mean the trivial bundle with base &lt;math display=&quot;inline&quot;&gt;\R^{m-c}&lt;/math&gt; and fibre &lt;math display=&quot;inline&quot;&gt;\R^c&lt;/math&gt; where &lt;math display=&quot;inline&quot;&gt;\pi: \R^m \to \R^{m-c}&lt;/math&gt;...&lt;ref&gt;Mather 2012, pp. 488.&lt;/ref&gt;

For &lt;math display=&quot;inline&quot;&gt;y \in |T| - \R^{m-c}&lt;/math&gt;, the kernal of the differential of &lt;math display=&quot;inline&quot;&gt;(\pi_T, \rho_T)&lt;/math&gt; at &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt; is the orthogonal complement of &lt;math display=&quot;inline&quot;&gt;(\R^{m-c} \times 0_c) \oplus \stackrel{\frown}{y \pi_T(y)}&lt;/math&gt; in &lt;math display=&quot;inline&quot;&gt;\R^m&lt;/math&gt;. By the Whitney conditions, we have that for &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt; near &lt;math display=&quot;inline&quot;&gt;\R^{m-c}&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;(\R^{m-c} \times 0_c) \oplus \stackrel{\frown}{y \pi_T(y)}&lt;/math&gt; is close to the set of &lt;math display=&quot;inline&quot;&gt;m - c + 1&lt;/math&gt; planes in &lt;math display=&quot;inline&quot;&gt;m-&lt;/math&gt;space to an &lt;math display=&quot;inline&quot;&gt;m - c + 1&lt;/math&gt; plane in &lt;math display=&quot;inline&quot;&gt;TY_y&lt;/math&gt;. Therefore, for &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt; near enough to &lt;math display=&quot;inline&quot;&gt;\R^{m-c}&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;TY_y&lt;/math&gt; is transverse to the kernal of the differential of &lt;math display=&quot;inline&quot;&gt;(\pi_T, \rho_T)&lt;/math&gt; and, therefore, is a submersion when restricted to &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 489.&lt;/ref&gt;

To prove that &lt;math display=&quot;inline&quot;&gt;T_{X,Y}&lt;/math&gt; is compatible with &lt;math display=&quot;inline&quot;&gt;(\rho_Y, \pi_Y): |T_Y| \cap X_{l+1} \to \R \times Y&lt;/math&gt;...&lt;ref&gt;Mather 2012, pp. 490.&lt;/ref&gt;

Therefore, there exists a tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T_0&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;X_0&lt;/math&gt; satisfying

&lt;math display=&quot;block&quot;&gt;\rho_Y \pi_0(m) = \rho_Y(m),&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;\pi_Y \pi_0(m) = \pi_Y(m).&lt;/math&gt;

From this we can prove that &lt;math display=&quot;inline&quot;&gt;T_0&lt;/math&gt; is compatible with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;. Replacing &lt;math display=&quot;inline&quot;&gt;T_0&lt;/math&gt; with a smaller tubular neighbourhood if necessary we can assume &lt;math display=&quot;inline&quot;&gt;m \in |T_0|&lt;/math&gt; such that for some &lt;math display=&quot;inline&quot;&gt;Y &lt; X&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;m \in |T_Y|&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi_0(m) \in |T_Y|&lt;/math&gt;, then&lt;ref&gt;Mather 2012, pp. 490.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;h \pi_0(m) = h \pi_Y \pi_0(m) = h \pi_Y(m) = h(m).&lt;/math&gt;

By the generalised tubular neighourhood theorem [prop 7.2?], we can replace &lt;math display=&quot;inline&quot;&gt;T_0&lt;/math&gt; with a tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; compatible with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;. This completes the construction of &lt;math display=&quot;inline&quot;&gt;T_X&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 491.&lt;/ref&gt;

This makes &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; an '''abstract stratified set''' with axioms...&lt;ref&gt;Mather 2012, pp. 491-492.&lt;/ref&gt;

This also makes &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; a '''controlled submersion''' because
# &lt;math display=&quot;inline&quot;&gt;h|X: X \to \R&lt;/math&gt; is a smooth submersion on each strata &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;, and
# for each stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; there is a tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T'_X&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;h(v) = h \pi_X(v)&lt;/math&gt; for all &lt;math display=&quot;inline&quot;&gt;v \in T'_X&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 493.&lt;/ref&gt;

The core of this is the concept of a '''vector field'''. A vector field is a function which assigns, for each point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; in a space, a '''vector''', which can be represented by an arrow whose tail starts at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.&lt;ref&gt;Henle 1979, pp. 33.&lt;/ref&gt;

[picture]

Imagine we have a vector field &lt;math display=&quot;inline&quot;&gt;v(x)&lt;/math&gt; defined in a space and draw a line through our space. At each point along this line the vector field assigns a vector. If we move each point in this line along the arrow defined by this vector in the direction of the arrow head. This &quot;flows&quot; the entire line along the vectors.

[picture]

We define a '''stratified vector field''' &lt;math display=&quot;inline&quot;&gt;\eta&lt;/math&gt; on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; to be a family of smooth vector fields &lt;math display=&quot;inline&quot;&gt;\eta_X&lt;/math&gt;, one for each strata &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 493.&lt;/ref&gt;

We define a '''controlled vector field''' &lt;math display=&quot;inline&quot;&gt;\eta&lt;/math&gt; on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; to be a stratified vector field such that for any strata &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; there exists a tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T'_Y&lt;/math&gt; such that for any &lt;math display=&quot;inline&quot;&gt;X &gt; Y&lt;/math&gt; and any &lt;math display=&quot;inline&quot;&gt;v \in T'_X \cap X&lt;/math&gt;&lt;ref&gt;Mather 2012, pp. 493.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;\eta_X \rho_{Y,X}(v) = 0,&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;(\pi_{Y,X})_* \eta_X(v) = \eta_Y (\pi_{Y,X}(v)).&lt;/math&gt;

We prove that if &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; is a controlled submersion then, for any smooth vector field &lt;math display=&quot;inline&quot;&gt;\zeta&lt;/math&gt; on &lt;math display=&quot;inline&quot;&gt;\R&lt;/math&gt; there is a controlled vector field &lt;math display=&quot;inline&quot;&gt;\eta&lt;/math&gt; on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;h_* \eta(v) = \zeta(h(v))&lt;/math&gt; for all &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 493.&lt;/ref&gt;

Proceeding by induction on the maximum dimension of the strata of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;, we define &lt;math display=&quot;inline&quot;&gt;Z_k&lt;/math&gt; to be the union of strata of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; of dimension at most &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;. The tubular neighbourhood of &lt;math display=&quot;inline&quot;&gt;Z_k&lt;/math&gt; is the intersection of the tubular neighbourhoods of each strata in &lt;math display=&quot;inline&quot;&gt;Z_k&lt;/math&gt; with &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;. The projection and distance functions are the restrictions of the respective functions of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;.

It is trivially true when the maximum dimension of strata in &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; is zero. Assume it is true for &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt; and construct each &lt;math display=&quot;inline&quot;&gt;\eta_X&lt;/math&gt; separately for each stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of dimension &lt;math display=&quot;inline&quot;&gt;k + 1&lt;/math&gt;.

By the assumption that we have controlled vector fields for all strata &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; of dimension at most &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;, we have the two control conditions defined above for any &lt;math display=&quot;inline&quot;&gt;X &gt; Y&lt;/math&gt; and that there is a neighbourhood &lt;math display=&quot;inline&quot;&gt;T^1_Y&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;h(v) = h \pi_Y(v)&lt;/math&gt; for &lt;math display=&quot;inline&quot;&gt;v \in T^1_Y&lt;/math&gt;.

We want to prove that for all &lt;math display=&quot;inline&quot;&gt;Y &lt; X&lt;/math&gt;, the control conditions are satisfied for all &lt;math display=&quot;inline&quot;&gt;v \in T^2_Y&lt;/math&gt; and that &lt;math display=&quot;inline&quot;&gt;h_*\eta_X(v) = \zeta(v)&lt;/math&gt; for all &lt;math display=&quot;inline&quot;&gt;v \in X&lt;/math&gt;.

Take a point &lt;math display=&quot;inline&quot;&gt;x \in X&lt;/math&gt; and define the set &lt;math display=&quot;inline&quot;&gt;S_v&lt;/math&gt; of strata &lt;math display=&quot;inline&quot;&gt;Y &lt; X&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;v \in T^2_Y&lt;/math&gt;. &lt;math display=&quot;inline&quot;&gt;S_v&lt;/math&gt; is totally ordered since if &lt;math display=&quot;inline&quot;&gt;Y_1&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Y_2&lt;/math&gt; are not comparable then &lt;math display=&quot;inline&quot;&gt;T^2_{Y_1} \cap T^2_{Y_2} = \empty&lt;/math&gt;. Therefore, there is a largest member &lt;math display=&quot;inline&quot;&gt;Y = Y_v&lt;/math&gt;.

Assume the control conditions hold for &lt;math display=&quot;inline&quot;&gt;Y = Y_v&lt;/math&gt;. Then they hold for all &lt;math display=&quot;inline&quot;&gt;Y_i \in S_v&lt;/math&gt;. For, either &lt;math display=&quot;inline&quot;&gt;Y_i = Y&lt;/math&gt; or &lt;math display=&quot;inline&quot;&gt;Y_i &lt; Y&lt;/math&gt;. In the latter case, &lt;math display=&quot;inline&quot;&gt;\pi_Y(v) \in T^1_{Y_i}&lt;/math&gt; (by the choice of &lt;math display=&quot;inline&quot;&gt;T^2_Y&lt;/math&gt;'s [is this why?]. Then

&lt;math display=&quot;block&quot;&gt;\begin{align}
\eta_X(v) \rho_{Y_i,X}(v) &amp;= \eta_X \rho_{Y_i,Y} \pi_{Y,X}(v) \\
&amp;= (\pi_{Y,X})_* \eta_X(v) \rho_{Y_i,Y} \\
&amp;= \eta_Y(\pi_{Y,X}(v)) \rho_{Y_i,Y} \\
&amp;= 0
\end{align}&lt;/math&gt;

and

&lt;math display=&quot;block&quot;&gt;\begin{align}
(\pi_{Y_i,X})_* \eta_X(v) &amp;= (\pi_{Y_i,Y})_* (\pi_{Y,X})_* \eta_X(v) \\
&amp;= (\pi_{Y_i,Y})_* \eta_Y(v) (\pi_{Y,X}) \\
&amp;= \eta_{Y_i}(\pi_{Y_i,Y} \pi_{Y,X}(v)) \\
&amp;= \eta_{Y_i}(\pi_{Y_i,X}(v))
\end{align}&lt;/math&gt;

and, therefore, condition holds for all &lt;math display=&quot;inline&quot;&gt;Y_i \in S_v&lt;/math&gt;. Also,

&lt;math display=&quot;block&quot;&gt;\begin{align}
h_* \eta_X(v) &amp;= (h \circ \pi_{Y,X})_* \eta_X(v) \\
&amp;= h_* \eta_Y (\pi_{Y,X}(v)) \\
&amp;= \zeta(f(v))
\end{align}&lt;/math&gt;

and, therefore, the conclusion of the theorem holds at &lt;math display=&quot;inline&quot;&gt;v&lt;/math&gt;.

This shows we can construct &lt;math display=&quot;inline&quot;&gt;\eta_X&lt;/math&gt; satisfying the control conditions when &lt;math display=&quot;inline&quot;&gt;S_v&lt;/math&gt; is non-empty and satisfying the theorem when &lt;math display=&quot;inline&quot;&gt;S_v&lt;/math&gt; is empty. The set of vectors satisfying these conditions is convex in &lt;math display=&quot;inline&quot;&gt;TX_v&lt;/math&gt;, and so we construct &lt;math display=&quot;inline&quot;&gt;\eta_X&lt;/math&gt; globally via a partition of unity.&lt;ref&gt;Mather 2012, pp. 493-495.&lt;/ref&gt;

Finally, we prove that a controlled vector field has a unique one-parameter family of homeomorphisms of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; which commute with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;.&lt;ref&gt;Mather 2012, this combines Proposition 10.1 and Corollary 10.2 on pp. 496 and 497, respectively.&lt;/ref&gt;

For each stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;\eta_X&lt;/math&gt; generates a unique smooth local one-parameter group &lt;math display=&quot;inline&quot;&gt;(J_X, \alpha_X)&lt;/math&gt; of diffeomorphisms of &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; (by standard results of differential geometry), such that &lt;math display=&quot;inline&quot;&gt;\frac{d}{dt} \alpha(t, v)|_{t=0} = \eta_X(v)&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;J_X&lt;/math&gt; is an open subset of &lt;math display=&quot;inline&quot;&gt;\R \times Z&lt;/math&gt;, ...

If we define &lt;math display=&quot;inline&quot;&gt;(J, \alpha)&lt;/math&gt; by

&lt;math display=&quot;block&quot;&gt;J = \bigcup_{X \in S} J_X&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;\alpha = \bigcup_{X \in S} \alpha_X&lt;/math&gt;

we can prove that this is a local one-parameter family of homeomorphisms.&lt;ref&gt;Mather 2012, pp. 496.&lt;/ref&gt;

Firstly, it is clear that
# &lt;math display=&quot;inline&quot;&gt;0 \times Z \subseteq J&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\alpha(0, v) = v&lt;/math&gt; for all &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt;.
# If &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt; then &lt;math display=&quot;inline&quot;&gt;J_v = J \cap (\R \times v) \subseteq \R&lt;/math&gt; is an open interval &lt;math display=&quot;inline&quot;&gt;(a_v, b_v)&lt;/math&gt;, possibly infinite at one or both ends.
# If &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;t, s, t + s&lt;/math&gt; are in &lt;math display=&quot;inline&quot;&gt;(a_v, b_v)&lt;/math&gt; then &lt;math display=&quot;inline&quot;&gt;\alpha(t + s, v) = \alpha(t, \alpha(s, v))&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 495.&lt;/ref&gt;

Secondly, it is clear that &lt;math display=&quot;inline&quot;&gt;\eta&lt;/math&gt; generates &lt;math display=&quot;inline&quot;&gt;\alpha&lt;/math&gt; because
# Each stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; is invariant under &lt;math display=&quot;inline&quot;&gt;\alpha&lt;/math&gt;, i.e. &lt;math display=&quot;inline&quot;&gt;\alpha[J \cap (\R \times X)] \subseteq X&lt;/math&gt;.
# For each &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt;, the map &lt;math display=&quot;inline&quot;&gt;t \to \alpha(t, v)&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;(a_v, b_v)&lt;/math&gt; into the stratum which contains &lt;math display=&quot;inline&quot;&gt;v&lt;/math&gt; is &lt;math display=&quot;inline&quot;&gt;C^1&lt;/math&gt;.
# For any &lt;math display=&quot;inline&quot;&gt;(t, v) \in Z&lt;/math&gt;(?) we have &lt;math display=&quot;inline&quot;&gt;d/dt \alpha(t, v) = \eta(\alpha(t, v))&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 495.&lt;/ref&gt;

It is unique because each &lt;math display=&quot;inline&quot;&gt;(J_X, \alpha_X)&lt;/math&gt; is unique. We just need to prove that &lt;math display=&quot;inline&quot;&gt;J&lt;/math&gt; is open, &lt;math display=&quot;inline&quot;&gt;\alpha&lt;/math&gt; is continuous, and for any &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt; and any compact set &lt;math display=&quot;inline&quot;&gt;K \subseteq Z&lt;/math&gt; there exists &lt;math display=&quot;inline&quot;&gt;\epsilon &gt; 0&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;\alpha(t, v) \notin K&lt;/math&gt; if &lt;math display=&quot;inline&quot;&gt;t \in (a_v, a_v + \epsilon) \cup (b_v - \epsilon, b_v)&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 495.&lt;/ref&gt;

For the latter-most condition, if it did not hold then there exists...&lt;ref&gt;Mather 2012, pp. 496-497.&lt;/ref&gt;

We prove there is a homeomorphism &lt;math display=&quot;inline&quot;&gt;f: Z \to h^{-1}(0) \times \R&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;\pi \circ f = h&lt;/math&gt;, where &lt;math display=&quot;inline&quot;&gt;\pi: h^{-1}(0) \times \R \to \R&lt;/math&gt; is projection to the second factor.

For the coordinate vector field &lt;math display=&quot;inline&quot;&gt;\partial&lt;/math&gt; on &lt;math display=&quot;inline&quot;&gt;\R&lt;/math&gt;, by [prop 9.1] there is a controlled vector field &lt;math display=&quot;inline&quot;&gt;\tilde\partial&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;f_* \tilde\partial(v) = \partial(h(v))&lt;/math&gt; for &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt;. By [prop 10.1], &lt;math display=&quot;inline&quot;&gt;\tilde\partial&lt;/math&gt; generates a local one-parameter group &lt;math display=&quot;inline&quot;&gt;(J, \alpha)&lt;/math&gt; such that

&lt;math display=&quot;block&quot;&gt;h(\alpha(t,v)) = h(v) + t&lt;/math&gt;

&lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; is proper and [d] holds, so &lt;math display=&quot;inline&quot;&gt;J = \R \times Z&lt;/math&gt;. If we define &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; as

&lt;math display=&quot;block&quot;&gt;f(v) = (\alpha(-t, v), h(v))&lt;/math&gt;

then &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; maps &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; into &lt;math display=&quot;inline&quot;&gt;h^{-1}(0) \times \R&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi \circ f = h&lt;/math&gt;. If we define &lt;math display=&quot;inline&quot;&gt;\bar f: h^{-1}(0) \times \R \to Z&lt;/math&gt; as

&lt;math display=&quot;block&quot;&gt;\bar f(v, t) = \alpha(t, v)&lt;/math&gt;

then &lt;math display=&quot;inline&quot;&gt;f \bar f = \bar f f = Id&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; is a homeomorphism.&lt;ref&gt;Mather 2012, pp. 497.&lt;/ref&gt;

== Topology at critical points ==

Theorem: If there is a critical point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; in the singular variety &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt; with critical value &lt;math display=&quot;inline&quot;&gt;v \in (a, b)&lt;/math&gt; then the space &lt;math display=&quot;inline&quot;&gt;X_{\leq b}&lt;/math&gt; is homotopic to&lt;ref&gt;Goresky and MacPherson 1988, pp. 174.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;X_{\leq a} \cup [(D^{\lambda+1}, \partial D^{\lambda+1}) \times (\mathcal{L}_X, \partial \mathcal{L}_X)].&lt;/math&gt;

Proof:&lt;ref&gt;Proof outline comes from Goresky and MacPherson 1988, pp. 174.&lt;/ref&gt;
# &lt;math display=&quot;inline&quot;&gt;(X_{\leq b}, X_{\leq a})&lt;/math&gt; is homeomorphic to &lt;math display=&quot;inline&quot;&gt;(X_{\leq v + \epsilon}, X_{\leq v -\epsilon})&lt;/math&gt;. We can prove this by &quot;moving wall&quot; or Thom's Isotopy Lemma.&lt;ref&gt;Goresky and MacPherson 1988, pp. 90-91, 120.&lt;/ref&gt;
# &lt;math display=&quot;inline&quot;&gt;X_{\leq v + \epsilon}&lt;/math&gt; is homeomorphic to &lt;math display=&quot;inline&quot;&gt;X_{\leq v - \epsilon} \cup (J, K)&lt;/math&gt;, where the latter is the local Morse data for &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;. We do this by moving the wall...&lt;ref&gt;Goresky and MacPherson 1988, pp. 95-96, 120-121.&lt;/ref&gt;
# &lt;math display=&quot;inline&quot;&gt;(J, K)&lt;/math&gt; is homeomorphic to &lt;math display=&quot;inline&quot;&gt;(D^{\lambda+1}, \partial D^{\lambda+1}) \times (\mathcal{L}_X, \partial \mathcal{L}_X)&lt;/math&gt; (tangential data, normal data). Again, moving the wall...&lt;ref&gt;Goresky and MacPherson 1988, pp. 65-66, chapter 8, 121.&lt;/ref&gt;
# The normal Morse data depends only on the differential &lt;math display=&quot;inline&quot;&gt;df(p)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 93.&lt;/ref&gt;
# The normal Morse data has the homotopy type of &lt;math display=&quot;inline&quot;&gt;(\mathcal{L}_X, \partial \mathcal{L}_X)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 169.&lt;/ref&gt;

=== Step 1 ===

We get this immediately(?) by Thom's Isotopy Lemma.

=== Step 2 ===

&lt;ref&gt;Goresky and MacPherson 1988, complex case on pp. 120-121 is extension of real case on pp. 95-96.&lt;/ref&gt;

Step 1 works because &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; is a submersion at each point of the regions we are homeomorphing. This is not the case at critical points. We need some way by which a homeomorphism can pass through a critical point.

To prove a homeomorphism between two subsets &lt;math display=&quot;inline&quot;&gt;A&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;B&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;, we project &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; to some other space &lt;math display=&quot;inline&quot;&gt;N&lt;/math&gt; (in our case &lt;math display=&quot;inline&quot;&gt;\R^n&lt;/math&gt;) using some function &lt;math display=&quot;inline&quot;&gt;F&lt;/math&gt;. We take subsets &lt;math display=&quot;inline&quot;&gt;Y_0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Y_1&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;N&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;A = Z \cap F^{-1}(Y_0)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;B = Z \cap F^{-1}(Y_1)&lt;/math&gt;. We need to prove &lt;math display=&quot;inline&quot;&gt;Y_0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Y_1&lt;/math&gt; are connected by a one-parameter family of regions &lt;math display=&quot;inline&quot;&gt;Y_t&lt;/math&gt; [explain one-parameter family]. The criterion for such a family to exist is that the '''characteristic covectors''' of &lt;math display=&quot;inline&quot;&gt;F&lt;/math&gt; are all nonzero on each stratum of &lt;math display=&quot;inline&quot;&gt;Y_t&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 70.&lt;/ref&gt;

At each point &lt;math display=&quot;inline&quot;&gt;x \in M&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;y \in N&lt;/math&gt; there are '''tangent spaces''' &lt;math display=&quot;inline&quot;&gt;T_xM&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;T_yN&lt;/math&gt;, a vector space whose zero is at the point &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; or &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt; (resp.)

[picture of various tangent spaces]

In the case the &lt;math display=&quot;inline&quot;&gt;N = \R&lt;/math&gt;, the tangent space &lt;math display=&quot;inline&quot;&gt;T_x\R&lt;/math&gt; is just &lt;math display=&quot;inline&quot;&gt;\R&lt;/math&gt; but whose origin is at &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt;.

[picture of T_x\R]

Say &lt;math display=&quot;inline&quot;&gt;F(x) = y&lt;/math&gt;, then the differential of the map &lt;math display=&quot;inline&quot;&gt;F&lt;/math&gt; can be seen as a function whose input is a vector in the tangent space &lt;math display=&quot;inline&quot;&gt;T_xM&lt;/math&gt; and whose output is a vector in the tangent space &lt;math display=&quot;inline&quot;&gt;T_yM&lt;/math&gt;. [If I move this far on the tangent space of M how do I move in the tangent space of N?]

[picture]

[example for M = \R and N = \R?]

A function which takes as input a vector in the tangent space &lt;math display=&quot;inline&quot;&gt;T_xM&lt;/math&gt; (say) and outputs a scalar (usually &lt;math display=&quot;inline&quot;&gt;\R&lt;/math&gt;) is called a '''covector'''. The set of all covectors on &lt;math display=&quot;inline&quot;&gt;T_xM&lt;/math&gt; is called the dual space of &lt;math display=&quot;inline&quot;&gt;T_xM&lt;/math&gt; and is denoted &lt;math display=&quot;inline&quot;&gt;T^*_xM&lt;/math&gt;. There are only a limited number of ways to express a covectors. For example, if our tangent space is two-dimensional then all covectors are of the form &lt;math display=&quot;inline&quot;&gt;ax + by&lt;/math&gt; where &lt;math display=&quot;inline&quot;&gt;(x, y) \in T_xM&lt;/math&gt;.

We take our space &lt;math display=&quot;inline&quot;&gt;M&lt;/math&gt; and map it onto &lt;math display=&quot;inline&quot;&gt;\R^2&lt;/math&gt; with the map &lt;math display=&quot;inline&quot;&gt;F(z) = (r(z), h(z))&lt;/math&gt;, where &lt;math display=&quot;inline&quot;&gt;z \in M&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;r&lt;/math&gt; is the square of the distance of &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt; to the critical point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.

[graph of mapping]

In this case, the covectors on the tangent space &lt;math display=&quot;inline&quot;&gt;T_xM&lt;/math&gt; are of the form &lt;math display=&quot;inline&quot;&gt;adf(x) + bdr(x)&lt;/math&gt; (in this case &lt;math display=&quot;inline&quot;&gt;df&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;dr&lt;/math&gt; are maps to &lt;math display=&quot;inline&quot;&gt;\R&lt;/math&gt;) and on &lt;math display=&quot;inline&quot;&gt;T_y\R^2&lt;/math&gt; are of the form &lt;math display=&quot;inline&quot;&gt;cu + dv&lt;/math&gt; (for &lt;math display=&quot;inline&quot;&gt;(u, v) \in \R^2&lt;/math&gt;). A covector &lt;math display=&quot;inline&quot;&gt;cu + dv \in T^*_{(u, v)}\R^2&lt;/math&gt; is called a '''characteristic covector''' of &lt;math display=&quot;inline&quot;&gt;F&lt;/math&gt; if &lt;math display=&quot;inline&quot;&gt;F(x) = (u, v)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;cdf(x) + ddr(x) = 0&lt;/math&gt; for all vectors in the tangent space of the stratum containing &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 82.&lt;/ref&gt; [explain adf(x) + bdr(x) in terms of this being a function which takes a vector input]

[example of where covectors do and do not vanish on a stratified space, pp. 71?]

What we want is a homeomorphism in &lt;math display=&quot;inline&quot;&gt;M&lt;/math&gt; between the space &lt;math display=&quot;inline&quot;&gt;Z_{\leq \epsilon}&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Z_{\leq \epsilon} \cup B&lt;/math&gt;, where &lt;math display=&quot;inline&quot;&gt;B&lt;/math&gt; is a small region of the critical point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;. The '''local Morse data''' is

&lt;math display=&quot;block&quot;&gt;((B_\delta \cap Z) \cap f^{-1}[v-\epsilon, v+\epsilon], (B_\delta \cap Z) \cap f^{-1}(v-\epsilon))&lt;/math&gt;

where &lt;math display=&quot;inline&quot;&gt;B_\delta&lt;/math&gt; is a closed disc in &lt;math display=&quot;inline&quot;&gt;M&lt;/math&gt; of radius &lt;math display=&quot;inline&quot;&gt;\delta&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 63-64.&lt;/ref&gt; Observe that this is the pair &lt;math display=&quot;inline&quot;&gt;(F^{-1}(\text{Box}(\delta, \epsilon)), F^{-1}(\text{Bottom}(\delta, \epsilon)))&lt;/math&gt;&lt;ref&gt;Goresky and MacPherson 1988, pp. 91.&lt;/ref&gt; [explain Box, Bottom, etc.]

[picture of the two subspaces of Z in M]

We use our map &lt;math display=&quot;inline&quot;&gt;F&lt;/math&gt; to convert these two subspaces to subspaces of &lt;math display=&quot;inline&quot;&gt;\R^2&lt;/math&gt; which are of the form &lt;math display=&quot;inline&quot;&gt;Y_1 = \{(x,y) \in \R^2 | y \leq \epsilon\}&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Y_0 = \{(x,y) \in \R^2 | y \leq -\epsilon\} \cup \{(x,y) \in \R^2 | x \leq \delta, y \leq \epsilon\}&lt;/math&gt;, such that &lt;math display=&quot;inline&quot;&gt;Z_{\leq \epsilon} = F^{-1}(Y_1)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Z_{\leq \epsilon} \cup B = F^{-1}(Y_0)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 95-96.&lt;/ref&gt;

We use a homeomorphism between &lt;math display=&quot;inline&quot;&gt;Y_1&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Y_0&lt;/math&gt; using the technique of &quot;moving the wall&quot; and Thom's Isotopy Lemma. Such a homeomorphism exists when the characteristic covectors of &lt;math display=&quot;inline&quot;&gt;F&lt;/math&gt; are all nonzero on each stratum of &lt;math display=&quot;inline&quot;&gt;Y_t&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, chapter 4, particularly pp. 71-72.&lt;/ref&gt;

Given a smooth mapping between manifolds &lt;math display=&quot;inline&quot;&gt;F: M \to N&lt;/math&gt; (for example, in our case we could have &lt;math display=&quot;inline&quot;&gt;N = \R^2&lt;/math&gt;) and that &lt;math display=&quot;inline&quot;&gt;F|Z: Z \to N&lt;/math&gt; is proper. Let &lt;math display=&quot;inline&quot;&gt;Y \subset N \times \R&lt;/math&gt; be a closed Whitney stratified subset such that the projection to the second factor &lt;math display=&quot;inline&quot;&gt;\pi: Y \to \R&lt;/math&gt; is a proper stratified submersion.&lt;ref&gt;Goresky and MacPherson 1988, pp. 71.&lt;/ref&gt;

Suppose for each &lt;math display=&quot;inline&quot;&gt;t \in \R&lt;/math&gt;, for each &lt;math display=&quot;inline&quot;&gt;p \in F(Z) \cap Y_t&lt;/math&gt;, and for each nonzero characteristic covector &lt;math display=&quot;inline&quot;&gt;\lambda \in T^*_pN&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;F|Z&lt;/math&gt;, the restriction of &lt;math display=&quot;inline&quot;&gt;\lambda&lt;/math&gt; to the subspace &lt;math display=&quot;inline&quot;&gt;T_pS_t = \ker(d\pi(p)) \cap T_pS&lt;/math&gt; is nonzero, where &lt;math display=&quot;inline&quot;&gt;S&lt;/math&gt; is a stratum of &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; which contains &lt;math display=&quot;inline&quot;&gt;(p, t)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;S_t = \pi^{-1}(t) \cap S&lt;/math&gt; is the stratum of &lt;math display=&quot;inline&quot;&gt;Y_t = \pi^{-1}(t) \cap Y&lt;/math&gt; which contains &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;. This is equivalent to the statement that, for each &lt;math display=&quot;inline&quot;&gt;t \in \R&lt;/math&gt;, the restriction &lt;math display=&quot;inline&quot;&gt;F|Z&lt;/math&gt; is transverse to &lt;math display=&quot;inline&quot;&gt;Y_t&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 71-72.&lt;/ref&gt;

This means that, for each &lt;math display=&quot;inline&quot;&gt;t \in \R&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;Z \cap F^{-1}(Y_t)&lt;/math&gt; is stratified by its intersection with the strata of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;...

We finally prove there is a homeomorphism between &lt;math display=&quot;inline&quot;&gt;Z \cap F^{-1}(Y_0) \cong Z \cap F^{-1}(Y_1)&lt;/math&gt; which preserves the Whitney stratification of both sides and is smooth on each stratum.

For the composition

&lt;math display=&quot;block&quot;&gt;Z \times \R \subset M \times \R \to_{F \times I} Y \subset \R^2 \times \R \to_{\pi} \R&lt;/math&gt;

where &lt;math display=&quot;inline&quot;&gt;Y(t, z) = Y_t(z)&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;I&lt;/math&gt; is the identity and &lt;math display=&quot;inline&quot;&gt;\pi&lt;/math&gt; is projection to the second factor. 

&lt;math display=&quot;inline&quot;&gt;Z \times \R&lt;/math&gt; is transverse to &lt;math display=&quot;inline&quot;&gt;(F \times I)^{-1}(Y)&lt;/math&gt;...

The composition &lt;math display=&quot;inline&quot;&gt;\pi \circ (F \times I): Z \times \R \cap (F \times I)^{-1}(Y) \to \R&lt;/math&gt; is a stratified submersion because
* The input domain is stratified as above...,
* We have defined &lt;math display=&quot;inline&quot;&gt;F|Z&lt;/math&gt; to be transverse to &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt;, and therefore it preserves the stratification (unless &lt;math display=&quot;inline&quot;&gt;F(Z) \cap Y = \empty&lt;/math&gt;), and
* We defined above the projection on &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; to be a stratified submersion, meaning it is a submersion on each stratum of &lt;math display=&quot;inline&quot;&gt;F(Z) \cap Y&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 43.&lt;/ref&gt;

Therefore, we can apply Thom's Isotopy Lemma which says there is a homeomorphism between the level sets of &lt;math display=&quot;inline&quot;&gt;Z \times \R&lt;/math&gt;...&lt;ref&gt;Goresky and MacPherson 1988, pp. 72.&lt;/ref&gt;

=== Step 3 ===

==== Characteristic covectors ====

==== Fringed sets ====

When manipulating our domain of integration[?], we need to make sure we are doing this in regions with no characteristic covectors. The introduce the concept of a fringed set, a subset of &lt;math display=&quot;inline&quot;&gt;R^2&lt;/math&gt;, and construct a series of fringed sets which contain no characteristic covectors.

A '''fringed set''' &lt;math display=&quot;inline&quot;&gt;A \subset \R \times \R^+&lt;/math&gt; is an open subset of the first quadrant of &lt;math display=&quot;inline&quot;&gt;\R^2&lt;/math&gt;. &lt;math display=&quot;inline&quot;&gt;A&lt;/math&gt; is fringed over &lt;math display=&quot;inline&quot;&gt;0 &lt; y \ll x&lt;/math&gt; if for some interval &lt;math display=&quot;inline&quot;&gt;S = (0, x)&lt;/math&gt;
# the projection of &lt;math display=&quot;inline&quot;&gt;A&lt;/math&gt; to the first factor is equal to &lt;math display=&quot;inline&quot;&gt;S&lt;/math&gt;,
# &lt;math display=&quot;inline&quot;&gt;A&lt;/math&gt; is open in &lt;math display=&quot;inline&quot;&gt;S \times \R^+&lt;/math&gt;,
# if &lt;math display=&quot;inline&quot;&gt;(s, y) \in A&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;0 &lt; y' \leq y&lt;/math&gt; then &lt;math display=&quot;inline&quot;&gt;(s, y') \in A&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 77.&lt;/ref&gt;

[picture]

The fringed set &lt;math display=&quot;inline&quot;&gt;A^\flat&lt;/math&gt; is the set &lt;math display=&quot;inline&quot;&gt;A&lt;/math&gt; plus its reflection about the &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; axis.&lt;ref&gt;Goresky and MacPherson 1988, pp. 82.&lt;/ref&gt;

[picture]

We build a series of fringed sets which do not contain characteristic covectors, which will be used later in our proof.

There exists a fringed set &lt;math display=&quot;inline&quot;&gt;A_2&lt;/math&gt; of type &lt;math display=&quot;inline&quot;&gt;0 &lt; v \ll u&lt;/math&gt; such that for any &lt;math display=&quot;inline&quot;&gt;z \in Z&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;r\pi(z) \leq r_2&lt;/math&gt;, the map &lt;math display=&quot;inline&quot;&gt;(\rho, f - f\pi)|\pi^{-1}(\pi(z)): \pi^{-1}(\pi(z)) \to \R^2&lt;/math&gt; has no characteristic covectors in &lt;math display=&quot;inline&quot;&gt;A^\flat_2&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 84.&lt;/ref&gt;

Given that the set of points &lt;math display=&quot;inline&quot;&gt;(u, v) \in \R^2&lt;/math&gt; which have a nonzero characteristic covector is closed, then it is enough to prove it for points &lt;math display=&quot;inline&quot;&gt;(u, 0) \in \R^2&lt;/math&gt;. Proof by contradiction. Assume it is false and that there is a sequence of points &lt;math display=&quot;inline&quot;&gt;p_i \in Z \cap f^{-1}(0)&lt;/math&gt; converging to &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;d\rho(p_i)&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;df(p_i)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;df\pi(p_i)&lt;/math&gt; are linearly dependent when restricted to the stratum &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; which contains &lt;math display=&quot;inline&quot;&gt;p_i&lt;/math&gt;. This would mean that &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; has a critical point on &lt;math display=&quot;inline&quot;&gt;Y \cap \partial B_{\rho(p_i)}(p)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 82-83.&lt;/ref&gt;

By restricting to a subsequence if necessary, we may assume the points &lt;math display=&quot;inline&quot;&gt;p_i&lt;/math&gt; are all contained in the same stratum &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt;, that the tangent planes &lt;math display=&quot;inline&quot;&gt;T_{p_i}Y&lt;/math&gt; converge to some plane &lt;math display=&quot;inline&quot;&gt;Q&lt;/math&gt; and the secant lines &lt;math display=&quot;inline&quot;&gt;\mathcal{l}_i = \overline{p_i p}&lt;/math&gt; converge to some line &lt;math display=&quot;inline&quot;&gt;\mathcal{l}&lt;/math&gt;. By the Whitney conditions [how?], &lt;math display=&quot;inline&quot;&gt;Q = \lim_{i \to \infty} \mathcal{l}_i \oplus T_{p_i}(Y \cap \partial B_\delta(p))&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 83.&lt;/ref&gt;

==== Homeomorphism ====

We prove there is a stratum preserving homeomorphism between&lt;ref&gt;Goresky and MacPherson 1988, pp. 65.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;\text{Local Morse Data} \cong (\text{Tangential Morse Data}) \times (\text{Normal Morse Data})&lt;/math&gt;

We first prove that there is a homeomorphism between the product of the normal and tangential Morse data and the '''realisation''' of the following diagram

[diagram from pp. 102]

where realisation means

&lt;math display=&quot;block&quot;&gt;Z \cap (g_1, h_1)^{-1}(P_a) \cap (g_2, h_2)^{-1}(P_b)&lt;/math&gt;

where all the intersections of strata (of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;?) are transverse.&lt;ref&gt;Goresky and MacPherson 1988, pp. 100-102.&lt;/ref&gt;

The realisation of the above diagram is equal to

&lt;math display=&quot;block&quot;&gt;(V_1, V_2) \cap (W_1, W_2) = (V_1 \cap W_1, V_1 \cap W_2 \cup V_2 \cap W_1)&lt;/math&gt;

where

&lt;math display=&quot;block&quot;&gt;V_1 = \{ z \in Z : |f(z) - f\pi(z)| \leq \epsilon/4, r\pi(z) \leq \delta, \rho(z) \leq \delta \}&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;V_2 = \{ z \in Z : f(z) - f\pi(z) = -\epsilon/4, r\pi(z) \leq \delta, \rho(z) \leq \delta \}&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;W_1 = \{ z \in Z : |f\pi(z)| \leq 3\epsilon/4, r\pi(z) \leq \delta \}&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;W_1 = \{ z \in Z : f\pi(z) = -3\epsilon/4, r\pi(z) \leq \delta \}&lt;/math&gt;

where &lt;math display=&quot;inline&quot;&gt;\pi&lt;/math&gt; is the projection from the tubular neighbourhood to &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;r(z)&lt;/math&gt; is the square of the distance between &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt; and the critical point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\rho(z)&lt;/math&gt; is the square of the distance between &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi(z)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 100-101.&lt;/ref&gt; &lt;math display=&quot;inline&quot;&gt;\epsilon \ll \delta&lt;/math&gt; are chosen so that &lt;math display=&quot;inline&quot;&gt;(\delta, \epsilon)&lt;/math&gt; is in the set &lt;math display=&quot;inline&quot;&gt;A^\flat_6&lt;/math&gt; which consists of &lt;math display=&quot;inline&quot;&gt;A_6 \subset \R^+ \times \R^+&lt;/math&gt; with the properties that for &lt;math display=&quot;inline&quot;&gt;(\epsilon, \delta) \in A_6&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;\rho(z) = \delta&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;r\pi(z) = \delta&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;|f(z)| \leq \epsilon&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;|f\pi(z)| \leq \epsilon&lt;/math&gt; then the covectors &lt;math display=&quot;inline&quot;&gt;d\rho(z)&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;dr\pi(z)&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;df(z)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;df\pi(z)&lt;/math&gt; are linearly independent when restricted to &lt;math display=&quot;inline&quot;&gt;T_zY&lt;/math&gt; (where &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; is the stratum containing &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt;). We can prove such a set exists.&lt;ref&gt;Goresky and MacPherson 1988, pp. 89.&lt;/ref&gt; &lt;math display=&quot;inline&quot;&gt;A^\flat_6&lt;/math&gt; is this plus its reflection about the &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; axis.&lt;ref&gt;Goresky and MacPherson 1988, pp. 82.&lt;/ref&gt;

Let &lt;math display=&quot;inline&quot;&gt;D = \{ x \in X | r(x) \leq \delta \}&lt;/math&gt; for stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt;. We will show there is a local trivial fibration of the configuration: &lt;math display=&quot;inline&quot;&gt;(V_1, V_2)&lt;/math&gt; fibres over &lt;math display=&quot;inline&quot;&gt;D&lt;/math&gt; and is homeomorphic to &lt;math display=&quot;inline&quot;&gt;D \times (\text{normal Morse data})&lt;/math&gt;

(V_1, V_2) -&gt; D \times (normal Morse data)
|           /
--&gt; D   &lt;---

and that &lt;math display=&quot;inline&quot;&gt;(W_1, W_2)&lt;/math&gt; fibres over the tangential Morse data and is homeomorphic to &lt;math display=&quot;inline&quot;&gt;(\text{tangential Morse data}) \times (\text{normal slice})&lt;/math&gt;.

For &lt;math display=&quot;inline&quot;&gt;Z_1 = \{ z \in Z : r\pi(z) \leq \delta \}&lt;/math&gt;, the map &lt;math display=&quot;inline&quot;&gt;F(z): Z_1 \to \R^2 = (\rho(z), f(z) - f\pi(z))&lt;/math&gt; is transverse to each stratum of &lt;math display=&quot;inline&quot;&gt;\text{Box}(\delta, \epsilon/4)&lt;/math&gt;, [list], [by lemma 6.5]. &lt;math display=&quot;inline&quot;&gt;(V_1, V_2) = F^{-1}(\text{Box}(\delta, \epsilon/4), \text{Bottom}(\delta, \epsilon/4))&lt;/math&gt;. For each stratum &lt;math display=&quot;inline&quot;&gt;S&lt;/math&gt; of Box and each &lt;math display=&quot;inline&quot;&gt;x \in D&lt;/math&gt;, we have transverse intersection &lt;math display=&quot;inline&quot;&gt;F^{-1}(S) \pitchfork \pi^{-1}(x)&lt;/math&gt;. Therefore, &lt;math display=&quot;inline&quot;&gt;\pi|F^{-1}(S)&lt;/math&gt; is a submersion and by Thom's isotopy lemma the projection &lt;math display=&quot;inline&quot;&gt;\pi|F^{-1}(\text{Box}(\delta, \epsilon/4): F^{-1}(\text{Box}(\delta, \epsilon/4)) \to X&lt;/math&gt; is a stratified fibre bundle over &lt;math display=&quot;inline&quot;&gt;D&lt;/math&gt;. The fibre over the critical point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; is &lt;math display=&quot;inline&quot;&gt;\pi^{-1}(p) \cap (F^{-1}(\text{Box}(\delta, \epsilon/4), F^{-1}(\text{Bottom}(\delta, \epsilon/4))&lt;/math&gt; and is equal to the normal Morse data...&lt;ref&gt;Goresky and MacPherson 1988, pp. 101.&lt;/ref&gt;

Take &lt;math display=&quot;inline&quot;&gt;G: X \to \R^2 = (r(x), f(x))&lt;/math&gt;. &lt;math display=&quot;inline&quot;&gt;\delta&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\epsilon&lt;/math&gt; have been chosen so that &lt;math display=&quot;inline&quot;&gt;(G^{-1}(\text{Box}(\delta, \epsilon/4), G^{-1}(\text{Bottom}(\delta, \epsilon/4))&lt;/math&gt; is the tangential Morse data for &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; and is contained in the region &lt;math display=&quot;inline&quot;&gt;D&lt;/math&gt; over which &lt;math display=&quot;inline&quot;&gt;\pi|(V_1, V_2)&lt;/math&gt; is a stratified fibre bundle. Therefore, &lt;math display=&quot;inline&quot;&gt;(W_1, W_2) = \pi^{-1} G^{-1}(\text{Box}(\delta, \epsilon/4), \text{Bottom}(\delta, \epsilon/4))&lt;/math&gt; is transverse to &lt;math display=&quot;inline&quot;&gt;(V_1, V_2)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 101-102.&lt;/ref&gt;

Finally, this means that &lt;math display=&quot;inline&quot;&gt;(V_1, V_2) \cap (W_1, W_2)&lt;/math&gt; is homeomorphic (by stratum preserving homeomorphism) to &lt;math display=&quot;inline&quot;&gt;(\pi^{-1}(p), \cap (V_1, V_2)) \times \pi(W_1, W_2)&lt;/math&gt;, the product of normal and tangential Morse data.&lt;ref&gt;Goresky and MacPherson 1988, pp. 102.&lt;/ref&gt;

We use a succession of such diagrams to interpolate between the box diagram which defines local Morse data [explain] and the above diagram whose realisation we have just proven is &lt;math display=&quot;inline&quot;&gt;(\text{normal Morse data}) \times (\text{tangential Morse data})&lt;/math&gt;.

[diagram_d0.py]

The realisation is the local Morse data. This is equal to the realisation of the diagram below.&lt;ref&gt;Goresky and MacPherson 1988, pp. 103, 106.&lt;/ref&gt;

[diagram_d11.py]

The realisation of the first diagram [d0] is equivalent to the realisation of the below diagram.

[diagram_d1.py]

In the right-hand picture of the above diagram, we have put a dotted outline around the region &lt;math display=&quot;inline&quot;&gt;A^{\flat}_1&lt;/math&gt;. We prove that there are no characteristic covectors for &lt;math display=&quot;inline&quot;&gt;(r, f): Z \to \R^2&lt;/math&gt; in this region and can, therefore, move the wall in this region...&lt;ref&gt;Goresky and MacPherson 1988, pp. 82-83.&lt;/ref&gt;

By adding a zero-dimensional stratum at the top right corner of the right-hand picture. A one-parameter family of pictures &lt;math display=&quot;inline&quot;&gt;P_b(t)&lt;/math&gt; gives rise to a stratified space &lt;math display=&quot;inline&quot;&gt;Y \subset M \times \R&lt;/math&gt; such that

&lt;math display=&quot;block&quot;&gt;Y = \{ (z, t) \in M \times \R : (r, f)(z) \in P_b(t) \}.&lt;/math&gt;

&lt;math display=&quot;inline&quot;&gt;(r, f)&lt;/math&gt; takes each stratum of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; transversally to each stratum of each &lt;math display=&quot;inline&quot;&gt;Y_t&lt;/math&gt;. &lt;math display=&quot;inline&quot;&gt;(f \circ \pi, f)^{-1}(P_a) = f^{-1}[-\epsilon, \infty)&lt;/math&gt; is transverse to each stratum of &lt;math display=&quot;inline&quot;&gt;Y_t \cap Z&lt;/math&gt;. Therefore, there is a homeomorphism between&lt;ref&gt;Goresky and MacPherson 1988, pp. 107.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;Z(D_1) = Z \cap (f \circ \pi, f)^{-1}(P_a) \cap (r, f)^{-1}(P_b(0))&lt;/math&gt;

and

&lt;math display=&quot;block&quot;&gt;Z(D_1) = Z \cap (f \circ \pi, f)^{-1}(P_a) \cap (r, f)^{-1}(P_b(1)).&lt;/math&gt;

To go from D_2 to D_3 we find the characteristic covectors of &lt;math display=&quot;inline&quot;&gt;(f\pi, f): V \to \R^2&lt;/math&gt; where &lt;math display=&quot;inline&quot;&gt;V = (r, f)^{-1}(P_b(1))&lt;/math&gt;. We stratify &lt;math display=&quot;inline&quot;&gt;P_b(1)&lt;/math&gt; by its interior &lt;math display=&quot;inline&quot;&gt;P&lt;/math&gt; and boundary &lt;math display=&quot;inline&quot;&gt;\partial P&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 107.&lt;/ref&gt;

The strata of &lt;math display=&quot;inline&quot;&gt;V&lt;/math&gt; come in four types:
# &lt;math display=&quot;inline&quot;&gt;(r, f)^{-1}(P) \cap X&lt;/math&gt;
# &lt;math display=&quot;inline&quot;&gt;(r, f)^{-1}(P) \cap Y&lt;/math&gt;
# &lt;math display=&quot;inline&quot;&gt;(r, f)^{-1}(\partial P) \cap X&lt;/math&gt;
# &lt;math display=&quot;inline&quot;&gt;(r, f)^{-1}(\partial P) \cap Y&lt;/math&gt;
where &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; is the strata that contains the critical point and &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; is any other strata such that &lt;math display=&quot;inline&quot;&gt;Y &gt; X&lt;/math&gt;.

All characteristic covectors are of the form &lt;math display=&quot;inline&quot;&gt;\lambda = (u, v, adu + bdv) \in T^*\R^2&lt;/math&gt;.

For strata 1 and 3, the image of &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; under &lt;math display=&quot;inline&quot;&gt;(f\pi, f)&lt;/math&gt; is the diagonal &lt;math display=&quot;inline&quot;&gt;f\pi = f&lt;/math&gt; (dotted outline). Therefore, the characteristic covectors of any point &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt; in &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; are either where &lt;math display=&quot;inline&quot;&gt;z = p&lt;/math&gt;, in which case the covector is zero(?), or where &lt;math display=&quot;inline&quot;&gt;z \neq p&lt;/math&gt;, in which case &lt;math display=&quot;inline&quot;&gt;u = v&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;a = b&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 107-108.&lt;/ref&gt;

For strata 2, being that the critical point is isolated and non-degenerate, which means it, and any neighbourhood, is not zero on any limit of tangent spaces in strata &lt;math display=&quot;inline&quot;&gt;Y &gt; X&lt;/math&gt;. Therefore, &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;f\pi&lt;/math&gt; are linearly independent.&lt;ref&gt;Goresky and MacPherson 1988, pp. 84.&lt;/ref&gt; Unless &lt;math display=&quot;inline&quot;&gt;\pi(z) = p&lt;/math&gt;, in which case &lt;math display=&quot;inline&quot;&gt;d(f\pi)(z) = f\pi(z) = 0&lt;/math&gt;, so they are covectors where &lt;math display=&quot;inline&quot;&gt;u = 0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;b = 0&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 108.&lt;/ref&gt;

For strata 4, we can use implicit function theorem to generate local coordinates &lt;math display=&quot;inline&quot;&gt;y_1, \cdots y_{r-s-1}&lt;/math&gt; in &lt;math display=&quot;inline&quot;&gt;Y &gt; X&lt;/math&gt; and define the Riemannian metric &lt;math display=&quot;inline&quot;&gt;r(z) = r\pi(z) + (f(z) - f\pi(z))^2 + g(y)&lt;/math&gt; for some &lt;math display=&quot;inline&quot;&gt;g&lt;/math&gt; depending only on &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt;.

There are no characteristic covectors in &lt;math display=&quot;inline&quot;&gt;|u| \leq \epsilon&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;|v| &lt; \epsilon&lt;/math&gt;. By [lemma 6.7 and 6.8 and 8.1(d)] &lt;math display=&quot;inline&quot;&gt;df&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;df\pi&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;dr&lt;/math&gt; are linearly independent in this region.&lt;ref&gt;Goresky and MacPherson 1988, pp. 109.&lt;/ref&gt; Given &lt;math display=&quot;inline&quot;&gt;|f| \leq \epsilon&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;|f\pi| \leq \epsilon&lt;/math&gt;, a fringed set &lt;math display=&quot;inline&quot;&gt;A^\flat_4&lt;/math&gt; of type &lt;math display=&quot;inline&quot;&gt;0 &lt; \epsilon \ll \delta&lt;/math&gt; and assume that &lt;math display=&quot;inline&quot;&gt;\pi \neq p&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;z \notin X&lt;/math&gt; then &lt;math display=&quot;inline&quot;&gt;(r(z), f(z)) \in A^\flat_4&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;(r(z), f\pi(z)) \in A^\flat_4&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 87.&lt;/ref&gt;

Outside of these points, the slope of &lt;math display=&quot;inline&quot;&gt;\ker(\lambda)&lt;/math&gt; for any characteristic covector &lt;math display=&quot;inline&quot;&gt;\lambda&lt;/math&gt; is

&lt;math display=&quot;block&quot;&gt;\frac{-a}{b} = \frac{f(z) - f\pi(z) - M}{\frac{\alpha}{\beta} + (f(z) - f\pi(z))}&lt;/math&gt;

for &lt;math display=&quot;inline&quot;&gt;\alpha df + \beta dr = 0&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 108-109.&lt;/ref&gt;

== Morse theory ==

Steps(?)
* Explain topology
* Every point of a stratum is locally like a product structure (proved by Thom's Isotopy Lemma) [GM pp. 41-42]
** Including those around critical points, which are the product of normal and tangential Morse data (these are our quasi-local cycles?)
* Thom's Isotopy Lemma proves a strong deformation retraction (which only stops at critical points) [PWM pp. 541-542]

=== Homotopy ===

We want to replace our domain of convergence &lt;math display=&quot;inline&quot;&gt;M&lt;/math&gt;, which is the complement of our singular variety &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt;, with an &quot;equivalent&quot; space &lt;math display=&quot;inline&quot;&gt;M'&lt;/math&gt; which has better understood properties. We say &quot;equivalent&quot; because there are several different things we could mean by &quot;equivalent&quot; in this context. The equivalence we are referring to in this section is called '''homotopy'''.

Imagine two subspaces &lt;math display=&quot;inline&quot;&gt;\gamma_0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\gamma_1&lt;/math&gt; of a space &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; which are defined respectively by smooth functions &lt;math display=&quot;inline&quot;&gt;f, g: X \to Y&lt;/math&gt;. If there exists a smooth function &lt;math display=&quot;inline&quot;&gt;h_s: X \times [0, 1] \to Y&lt;/math&gt;, called a homotopy, such that &lt;math display=&quot;inline&quot;&gt;h_0 = f&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;h_1 = g&lt;/math&gt; and for any &lt;math display=&quot;inline&quot;&gt;\epsilon &gt; 0&lt;/math&gt; there exists a &lt;math display=&quot;inline&quot;&gt;\delta_a&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\delta_b&lt;/math&gt; such that when &lt;math display=&quot;inline&quot;&gt;|s - s_0| &lt; \delta_a&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;|x - x_0| &lt; \delta_b&lt;/math&gt; we have &lt;math display=&quot;inline&quot;&gt;|h_s(x) - h_{s_0}(x_0)| &lt; \epsilon&lt;/math&gt;, then we say &lt;math display=&quot;inline&quot;&gt;\gamma_0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\gamma_1&lt;/math&gt; are '''homotopic'''.&lt;ref&gt;Henle 1979, pp. 251-252.&lt;/ref&gt;

Below is an example where &lt;math display=&quot;inline&quot;&gt;\gamma_0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\gamma_1&lt;/math&gt; are one-dimensional curves and &lt;math display=&quot;inline&quot;&gt;H(t, s) = h_s(t)&lt;/math&gt;.

[[File:Homotopy_curves.png|300px]]

In [[#Homotopy_equivalence|Appendix A]], we formally prove that we can construct an equivalent space &lt;math display=&quot;inline&quot;&gt;M'&lt;/math&gt;. We provide only an example to give some intuition before describing how to construct the space &lt;math display=&quot;inline&quot;&gt;M'&lt;/math&gt; in terms of local cycles around critical points.

=== Motivating example ===

Imagine a torus and a height function which is just the z value of the point.

[[File:3D-Leveltorus.png|200px]]

It has four critical points: two at the top and bottom of the outer circle (&lt;math display=&quot;inline&quot;&gt;p_1, p_4&lt;/math&gt;) and two at the top and bottom of the inner circle (&lt;math display=&quot;inline&quot;&gt;p_2, p_3&lt;/math&gt;).

[picture]

When the height is between the &lt;math display=&quot;inline&quot;&gt;p_1&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;p_2&lt;/math&gt;, the space is a two-cell, which can be retracted to a point.

[picture]

When the height is between &lt;math display=&quot;inline&quot;&gt;p_2&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;p_3&lt;/math&gt;, the space is a cylinder, which can be retracted to a two-cell with a one-cell attached.

[[File:3D-Cylinder_and_disk_with_handle.png|200px]]

When the height is between &lt;math display=&quot;inline&quot;&gt;p_3&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;p_4&lt;/math&gt;, the space is a torus with a disc removed, which can be retracted to a cylinder with a one-cell attached.

[[File:3D-Cylinder_with_handle_and_torus_with_hole.png|200px]]

When the height is greater than &lt;math display=&quot;inline&quot;&gt;p_4&lt;/math&gt;, then the full torus is constructed by attaching a two-cell.

[Explain in terms of Morse data and Morse index?]

=== Morse data and quasi-local cycles ===

As in the above example, we start at the &quot;bottom&quot; of &lt;math display=&quot;inline&quot;&gt;M&lt;/math&gt; and build upwards until just before we reach our first critical point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.

;Smooth points
:This is a tube around a &lt;math display=&quot;inline&quot;&gt;(d-1)&lt;/math&gt;-chain &lt;math display=&quot;inline&quot;&gt;\gamma&lt;/math&gt; where the height function &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; is maximised at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 223.&lt;/ref&gt;
:For example, if &lt;math display=&quot;inline&quot;&gt;F(x, y) = \frac{1}{1 - x - y}&lt;/math&gt; then &lt;math display=&quot;inline&quot;&gt;\lambda = 1&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;B^\lambda&lt;/math&gt; is an arc reaching its highest point at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.
:The normal plane &lt;math display=&quot;inline&quot;&gt;N&lt;/math&gt; at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; is a plane orthogonal to &lt;math display=&quot;inline&quot;&gt;B^1&lt;/math&gt;(?).
:Its normal link &lt;math display=&quot;inline&quot;&gt;L(S)&lt;/math&gt; is a circle with two points missing where it intersects &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt;.
:We make our quasi-local cycle out of the product of the arc and circle joined to &lt;math display=&quot;inline&quot;&gt;M_-&lt;/math&gt; at points below &lt;math display=&quot;inline&quot;&gt;M_-&lt;/math&gt;.
:With the exception of degenerate points, such as monkey saddles...&lt;ref&gt;e.g. Pemantle, Wilson and Melczer 2024, pp. 211.&lt;/ref&gt;

;Transverse multiple points
:This is the product of a &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;-torus and a &lt;math display=&quot;inline&quot;&gt;(d-k)&lt;/math&gt;-chain &lt;math display=&quot;inline&quot;&gt;\gamma&lt;/math&gt;. The torus is the product of circles about &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; in the complex normal space to each strata which intersects &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;. The chain &lt;math display=&quot;inline&quot;&gt;\gamma&lt;/math&gt; is supported in the stratum which is the common intersection of the varieties defined by the factors vanishing at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;, and achieves its maximum height at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 223-224.&lt;/ref&gt;

;Arrangement multiple point
:This is the product of a &lt;math display=&quot;inline&quot;&gt;(d-k)&lt;/math&gt;-chain &lt;math display=&quot;inline&quot;&gt;\gamma&lt;/math&gt; and several &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;-tori, one for each pair of sheets which intersect transversely, where the torus is the product of circles about &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; in each sheet.&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 226.&lt;/ref&gt;

;Cone point
:A cone point is zero-dimensional so there is no &lt;math display=&quot;inline&quot;&gt;\gamma&lt;/math&gt;, just a &lt;math display=&quot;inline&quot;&gt;d&lt;/math&gt;-torus about &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 227.&lt;/ref&gt;

== Notes ==
{{Reflist}}

== References ==
* {{cite book | last1=Goresky | first1=Mark | last2=MacPherson | first2=Robert | title=Stratified Morse Theory | publisher=Springer-Verlag | year=1988 | url=https://www.math.ias.edu/~goresky/pdf/SMT.djvu }}
* {{cite book | last=Henle | first1=Michael | title=A Combinatorial Introduction to Topology | publisher=Dover Publications Inc. New York | year=1979 }}
* {{citation | last=Mather | first=John | title=Notes on Topological Stability | year=2012 | journal=Bulletin of the American Mathematical Society | volume=49 | number=4 | pages=475-506 | url=https://www.ams.org/journals/bull/2012-49-04/S0273-0979-2012-01383-6/S0273-0979-2012-01383-6.pdf }}.
* {{cite book | last1=Pemantle | first1=Robin | last2=Wilson | first2=Mark C. | last3=Melczer | first3=Stephen | title=Analytic Combinatorics in Several Variables | publisher=Cambridge University Press | year=2024 | edition=2nd | url=https://acsvproject.com/PemantleWilsonMelczer23.pdf }}</text>
      <sha1>a59sphoneaai5k352gi0k70xhf811tg</sha1>
    </revision>
    <revision>
      <id>4676707</id>
      <parentid>4676705</parentid>
      <timestamp>2026-10-18T08:38:35Z</timestamp>
      <contributor>
        <username>Dom walden</username>
        <id>3209423</id>
      </contributor>
      <comment>/* Fringed sets */ Finish(?) proof of A_2</comment>
      <origin>4676707</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="60435" sha1="qhgh7ix5ualueutg35v7hb616nlhr2v" xml:space="preserve">== Introduction ==

Morse theory tells us that the topology of M only changes at its critical points.

The &quot;Morse data&quot; tells us the topology at each critical point.

Attaching this Morse data together gives us a space which is homopotically eqivalent to M.

This space is a &quot;cell complex&quot;, which has an easy to calculate homology.

Theorem: Our domain of convergence is homotopic to a cell complex of dimension at most &lt;math display=&quot;inline&quot;&gt;2n - d - 1&lt;/math&gt;.&lt;ref&gt;This is theorem D.23 in Pemantle, Wilson and Melczer 2024, pp. 546. Also theorem in section 1.2*/5.2* in SMT pp. 200.&lt;/ref&gt;

Proof:
# &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; is our entire domain, &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt; our variety
# Project our entire domain to complex projective space &lt;math display=&quot;inline&quot;&gt;Z = \pi(X) \subset \C\mathbb{P}^n - H&lt;/math&gt; [define H]
# Define a linear subspace &lt;math display=&quot;inline&quot;&gt;G \subset \C\mathbb{P}^n&lt;/math&gt; of dimension &lt;math display=&quot;inline&quot;&gt;d - 1&lt;/math&gt;
# Define a Morse function on &lt;math display=&quot;inline&quot;&gt;f: \C\mathbb{P}^n \to \R&lt;/math&gt; which approximates the distance from &lt;math display=&quot;inline&quot;&gt;G&lt;/math&gt; and such that &lt;math display=&quot;inline&quot;&gt;f^{-1}(0) = G&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;f^{-1}(1) = H&lt;/math&gt;
# We &quot;build&quot; &lt;math display=&quot;inline&quot;&gt;X - \mathcal{V}&lt;/math&gt; from &lt;math display=&quot;inline&quot;&gt;\pi^{-1}(G \cap Z) \cap (X - \mathcal{V})&lt;/math&gt; by attaching CW complexes at critical points which are of at most dimension &lt;math display=&quot;inline&quot;&gt;2n - d - 1&lt;/math&gt;
# At a critical point, the normal Morse data is &lt;math display=&quot;inline&quot;&gt;(J, K) = \coprod_x (J_x, K_x)&lt;/math&gt; and the relative complex link is &lt;math display=&quot;inline&quot;&gt;\mathcal{L}^\pi = \coprod_x \mathcal{L}_x&lt;/math&gt;
# We show that the quotient &lt;math display=&quot;inline&quot;&gt;J_x/K_x&lt;/math&gt; is homotopic to a CW complex of dimension &lt;math display=&quot;inline&quot;&gt;\leq 2n - d - 1&lt;/math&gt;
# The neighbourhood of &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; in &lt;math display=&quot;inline&quot;&gt;J_x&lt;/math&gt; is homeomorphic to the cone in &lt;math display=&quot;inline&quot;&gt;L_x(X - \mathcal{V})&lt;/math&gt;, and removing the point &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; increases the homotopy dimension to at most the homotopy dimension of &lt;math display=&quot;inline&quot;&gt;L_x&lt;/math&gt;
# &lt;math display=&quot;inline&quot;&gt;(J_x \cup \{x\}, K_x)&lt;/math&gt; is homotopic to &lt;math display=&quot;inline&quot;&gt;(\text{cone}(\mathcal{L}_x), \mathcal{L}_x)&lt;/math&gt;
# &lt;math display=&quot;inline&quot;&gt;\mathcal{L}_x&lt;/math&gt; is homotopic to a CW complex of dimension at most &lt;math display=&quot;inline&quot;&gt;2n - d - 1&lt;/math&gt;
# The tangential Morse data at the critical point is homotopic to the pair &lt;math display=&quot;inline&quot;&gt;(D^\lambda, \partial D^\lambda)&lt;/math&gt;
# Therefore, at each critical point a space has been added homotopic to a CW complex of dimension at most &lt;math display=&quot;inline&quot;&gt;2n - d - 1&lt;/math&gt;.

Theorem: If &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; is the complement in &lt;math display=&quot;inline&quot;&gt;\C^n&lt;/math&gt; of a complex variety &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt; of dimension &lt;math display=&quot;inline&quot;&gt;d&lt;/math&gt; then &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; is homotopic to a CW complex of dimension at most &lt;math display=&quot;inline&quot;&gt;2n - d - 1&lt;/math&gt;.&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 546.&lt;/ref&gt;

Proof:
# We build &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; by attaching cells of dimension at most &lt;math display=&quot;inline&quot;&gt;2n - d - 1&lt;/math&gt; at each critical point.
## Prove that we can do this without changing the homotopy(?)
## We use Thom's Isotopy Lemma to prove that there is a strong deformation retraction, stopping only at critical points.
# Prove these cells are a product of the normal and tangential Morse data.
## Normal data: &lt;math display=&quot;inline&quot;&gt;(\mathcal{L}(S), \partial \mathcal{L}(S)) \times (D^1, \partial D^1)&lt;/math&gt; [GM pp. 18]
## Tangential data: &lt;math display=&quot;inline&quot;&gt;(B_\delta \cap f^{-1}[v - \epsilon, v + \epsilon], B_\delta \cap f^{-1}(v - \epsilon))&lt;/math&gt; for &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; restricted to &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; (or &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt;?) [GM pp. 63-64]
# If &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt; is the dimension of the strata, then
## If &lt;math display=&quot;inline&quot;&gt;k = d&lt;/math&gt; then it is a smooth point and the cell is the product of &lt;math display=&quot;inline&quot;&gt;S^{2(n-d)-1}&lt;/math&gt; and the tangential data is dimension at most &lt;math display=&quot;inline&quot;&gt;d&lt;/math&gt;.
## If &lt;math display=&quot;inline&quot;&gt;k &lt; d&lt;/math&gt;, ...

&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 547.&lt;/ref&gt;

== Example in one dimension ==

Domain with singularities v_1, v_2, ..., v_i

Define our height function f...

Start with our entire domain X

Reduce from X to X_i+ by using Thom's Isotopy lemma to do a strong deformation retract

== Thom's isotopy lemma ==

We present a modified version of Thom's (first) isotopy lemma, less general than the original but more obviously relevant to our situation.

Theorem: Suppose &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; is a closed subset of a smooth manifold &lt;math display=&quot;inline&quot;&gt;M&lt;/math&gt; which admits a Whitney stratification and &lt;math display=&quot;inline&quot;&gt;h : M \to \R&lt;/math&gt; is a proper Morse function which has no critical values on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;. Then, the level sets of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; are homeomorphic by a homeomorphism that preserves the strata of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;.&lt;ref&gt;For various versions of the full statement of the theorem, see Mather 2012, pp. 499, Goresky and MacPherson 1988, pp. 41, or Pemantle, Wilson and Melczer 2024, pp. 541.&lt;/ref&gt;

Proof:
# Construct control data for &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; compatible with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;.
## [Prop 7.1] If &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; is smooth on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; and is a submersion for each strata then there exists a family of control data for &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; compatible with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 488.&lt;/ref&gt;
# This makes &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; an abstract stratified set and &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; a controlled submersion.
# A controlled submersion has, for any smooth vector field on &lt;math display=&quot;inline&quot;&gt;\R&lt;/math&gt;, a controlled vector field on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; (a &quot;lift&quot;?)&lt;ref&gt;Mather 2012, pp. 493.&lt;/ref&gt;
# A controlled vector field has a unique one-parameter family of homeomorphisms of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; which commute with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 496.&lt;/ref&gt;
# This makes &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; a locally trivial fibration. [Prop 10.2]&lt;ref&gt;Mather 2012, pp. 499.&lt;/ref&gt;

Control data:

A system of '''control data''' for &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; consists of, for each stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;,
* a '''tubular neighbourhood''' &lt;math display=&quot;inline&quot;&gt;T_X&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt;
* a '''tubular projection function''' &lt;math display=&quot;inline&quot;&gt;\pi_X: T_X \to X&lt;/math&gt;, and
* a '''tubular distance function''' &lt;math display=&quot;inline&quot;&gt;\rho_X: T_X \to \R&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;\rho_X^{-1}(0) = X&lt;/math&gt;&lt;ref&gt;Goresky and MacPherson 1988, pp. 42.&lt;/ref&gt;

[illustration]

such that if &lt;math display=&quot;inline&quot;&gt;X &lt; Y&lt;/math&gt; are strata in &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;, then

&lt;math display=&quot;block&quot;&gt;\pi_X \pi_Y(m) = \pi_X(m),&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;\rho_X \pi_Y(m) = \rho_X(m)&lt;/math&gt;

for all &lt;math display=&quot;inline&quot;&gt;m \in |T_X| \cap |T_Y|&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;\pi_Y(m) \in |T_X|&lt;/math&gt;.

If, for all strata &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; and all &lt;math display=&quot;inline&quot;&gt;m \in |T_X|&lt;/math&gt;, we have &lt;math display=&quot;inline&quot;&gt;h \pi_X(m) = h(m)&lt;/math&gt;, then this control data will be said to be compatible with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 488.&lt;/ref&gt;

We prove that if &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; is smooth on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; and is a submersion for each strata then there exists a family of control data for &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; compatible with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 488, prop 7.1.&lt;/ref&gt;

Let &lt;math display=&quot;inline&quot;&gt;Z_k&lt;/math&gt; be the union of strata of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; of dimension less than &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;. We prove by induction on &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;.

To construct the tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T_X&lt;/math&gt; of a stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of dimension less than &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;. For &lt;math display=&quot;inline&quot;&gt;l \leq k&lt;/math&gt;, let &lt;math display=&quot;inline&quot;&gt;U_l&lt;/math&gt; denote the union of all &lt;math display=&quot;inline&quot;&gt;|T_Y|&lt;/math&gt; for &lt;math display=&quot;inline&quot;&gt;Y &lt; X&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\dim Y \geq l&lt;/math&gt;. Let &lt;math display=&quot;inline&quot;&gt;X_l = U_l \cap X&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 489.&lt;/ref&gt;

For &lt;math display=&quot;inline&quot;&gt;l = k&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;X_k = \empty&lt;/math&gt;. Assume by induction that &lt;math display=&quot;inline&quot;&gt;T_{l+1}&lt;/math&gt; has been constructed and that if &lt;math display=&quot;inline&quot;&gt;Y &lt; X&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;\dim Y \geq l + 1&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;m \in |T_{l+1}| \cap |T_Y|&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi_{l+1}(m) \in |T_Y|&lt;/math&gt; (&lt;math display=&quot;inline&quot;&gt;\pi_{l+1} = \pi_{T_{l+1}}&lt;/math&gt;) then&lt;ref&gt;Mather 2012, pp. 489-490.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;\rho_Y \pi_{l+1}(m) = \rho_Y(m),&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;\pi_Y \pi_{l+1}(m) = \pi_Y(m).&lt;/math&gt;

We wish to construct a tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T_{X,Y}&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;|T_Y| \cap X&lt;/math&gt; whose restriction to &lt;math display=&quot;inline&quot;&gt;|T_Y| \cap X_{l+1}&lt;/math&gt; is isomorphic to the restriction of &lt;math display=&quot;inline&quot;&gt;T_{l+1}&lt;/math&gt; such that if &lt;math display=&quot;inline&quot;&gt;m \in |T_{X,Y}| \cap |T_Y|&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi_{X,Y}(m) \in |T_Y|&lt;/math&gt; (&lt;math display=&quot;inline&quot;&gt;\pi_{X,Y} = \pi_{T_{X,Y}}&lt;/math&gt;) then

&lt;math display=&quot;block&quot;&gt;\rho_Y \pi_{X,Y}(m) = \rho_Y(m),&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;\pi_Y \pi_{X,Y}(m) = \pi_Y(m).&lt;/math&gt;

By shrinking &lt;math display=&quot;inline&quot;&gt;|T_Y|&lt;/math&gt; if necessary, this relation is already satisfied if &lt;math display=&quot;inline&quot;&gt;m \in |T_{l+1}| \cap |T_Y|&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi_{l+1}(m) \in |T_Y|&lt;/math&gt; with &lt;math display=&quot;inline&quot;&gt;T_{l+1}&lt;/math&gt; in place of &lt;math display=&quot;inline&quot;&gt;T_{X,Y}&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi_{l+1}&lt;/math&gt; in place of &lt;math display=&quot;inline&quot;&gt;\pi_{X,Y}&lt;/math&gt;. By the definition, if &lt;math display=&quot;inline&quot;&gt;m \in |T_{l+1}|&lt;/math&gt; then there exists &lt;math display=&quot;inline&quot;&gt;Z &lt; X&lt;/math&gt; with &lt;math display=&quot;inline&quot;&gt;\dim Z &gt; l&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;m \in |T_Z|&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi_{l+1}(m) \in |T_Z|&lt;/math&gt;. We have that &lt;math display=&quot;inline&quot;&gt;\pi_{l+1}(m) \in |T_Y| \cap |T_Z|&lt;/math&gt; and therefore &lt;math display=&quot;inline&quot;&gt;Y &lt; Z&lt;/math&gt;. Therefore&lt;ref&gt;Mather 2012, pp. 490.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;\rho_Y \pi_{l+1}(m) = \rho_Y \pi_Z \pi_{l+1}(m) = \rho_Y \pi_Z(m) = \rho_Y(m),&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;\pi_Y \pi_{l+1}(m) = \pi_Y \pi_Z \pi_{l+1}(m) = \pi_Y \pi_Z(m) = \pi_Y(m).&lt;/math&gt;

We can prove that, by shrinking &lt;math display=&quot;inline&quot;&gt;|T_Y|&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;(\rho_Y, \pi_Y): |T_Y| \cap X \to \R \times Y&lt;/math&gt; is a submersion [prop 7.3?] and that &lt;math display=&quot;inline&quot;&gt;T_{X,Y}&lt;/math&gt; is compatible with &lt;math display=&quot;inline&quot;&gt;(\rho_Y, \pi_Y): |T_Y| \cap X_{l+1} \to \R \times Y&lt;/math&gt;, i.e. &lt;math display=&quot;inline&quot;&gt;(\rho_Y, \pi_Y) \pi_{X,Y}(m) = (\rho_Y, \pi_Y)(m)&lt;/math&gt;(?).

To prove it is a submersion, for the tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T = (E, \epsilon, \psi)&lt;/math&gt; there exists a smooth positive function &lt;math display=&quot;inline&quot;&gt;\epsilon'&lt;/math&gt; such that

&lt;math display=&quot;block&quot;&gt;(\rho_T, \pi_T): Y \cap |T|_{\epsilon'}^0 \to \R \times X,&lt;/math&gt;

where &lt;math display=&quot;inline&quot;&gt;|T|_{\epsilon'}^0 = \psi(B_\epsilon \cap B_{\epsilon'})&lt;/math&gt;, is a submersion. If &lt;math display=&quot;inline&quot;&gt;\Sigma&lt;/math&gt; is the set &lt;math display=&quot;inline&quot;&gt;y \in |T|&lt;/math&gt; such that the rank of

&lt;math display=&quot;block&quot;&gt;(\rho_T, \pi_T): T \cap |T| \to \R \times X&lt;/math&gt;

at &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt; is less than &lt;math display=&quot;inline&quot;&gt;\dim(\R \times X)&lt;/math&gt;. We need to prove that for any &lt;math display=&quot;inline&quot;&gt;x \in X&lt;/math&gt; there exists a neighbourhood of &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; which does not intersect with &lt;math display=&quot;inline&quot;&gt;\Sigma&lt;/math&gt;, i.e. the map is not a submersion in this neighbourhood. It follows from [lemma 7.2] that it is enough to prove for &lt;math display=&quot;inline&quot;&gt;M = \R^m&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;X = \R^{m-c} \times 0_c&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;T&lt;/math&gt; is the '''standard tubular neighbourhood'''.&lt;ref&gt;Mather 2012, pp. 489.&lt;/ref&gt;

By standard tubular neighbourhood, we mean the trivial bundle with base &lt;math display=&quot;inline&quot;&gt;\R^{m-c}&lt;/math&gt; and fibre &lt;math display=&quot;inline&quot;&gt;\R^c&lt;/math&gt; where &lt;math display=&quot;inline&quot;&gt;\pi: \R^m \to \R^{m-c}&lt;/math&gt;...&lt;ref&gt;Mather 2012, pp. 488.&lt;/ref&gt;

For &lt;math display=&quot;inline&quot;&gt;y \in |T| - \R^{m-c}&lt;/math&gt;, the kernal of the differential of &lt;math display=&quot;inline&quot;&gt;(\pi_T, \rho_T)&lt;/math&gt; at &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt; is the orthogonal complement of &lt;math display=&quot;inline&quot;&gt;(\R^{m-c} \times 0_c) \oplus \stackrel{\frown}{y \pi_T(y)}&lt;/math&gt; in &lt;math display=&quot;inline&quot;&gt;\R^m&lt;/math&gt;. By the Whitney conditions, we have that for &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt; near &lt;math display=&quot;inline&quot;&gt;\R^{m-c}&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;(\R^{m-c} \times 0_c) \oplus \stackrel{\frown}{y \pi_T(y)}&lt;/math&gt; is close to the set of &lt;math display=&quot;inline&quot;&gt;m - c + 1&lt;/math&gt; planes in &lt;math display=&quot;inline&quot;&gt;m-&lt;/math&gt;space to an &lt;math display=&quot;inline&quot;&gt;m - c + 1&lt;/math&gt; plane in &lt;math display=&quot;inline&quot;&gt;TY_y&lt;/math&gt;. Therefore, for &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt; near enough to &lt;math display=&quot;inline&quot;&gt;\R^{m-c}&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;TY_y&lt;/math&gt; is transverse to the kernal of the differential of &lt;math display=&quot;inline&quot;&gt;(\pi_T, \rho_T)&lt;/math&gt; and, therefore, is a submersion when restricted to &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 489.&lt;/ref&gt;

To prove that &lt;math display=&quot;inline&quot;&gt;T_{X,Y}&lt;/math&gt; is compatible with &lt;math display=&quot;inline&quot;&gt;(\rho_Y, \pi_Y): |T_Y| \cap X_{l+1} \to \R \times Y&lt;/math&gt;...&lt;ref&gt;Mather 2012, pp. 490.&lt;/ref&gt;

Therefore, there exists a tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T_0&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;X_0&lt;/math&gt; satisfying

&lt;math display=&quot;block&quot;&gt;\rho_Y \pi_0(m) = \rho_Y(m),&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;\pi_Y \pi_0(m) = \pi_Y(m).&lt;/math&gt;

From this we can prove that &lt;math display=&quot;inline&quot;&gt;T_0&lt;/math&gt; is compatible with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;. Replacing &lt;math display=&quot;inline&quot;&gt;T_0&lt;/math&gt; with a smaller tubular neighbourhood if necessary we can assume &lt;math display=&quot;inline&quot;&gt;m \in |T_0|&lt;/math&gt; such that for some &lt;math display=&quot;inline&quot;&gt;Y &lt; X&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;m \in |T_Y|&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi_0(m) \in |T_Y|&lt;/math&gt;, then&lt;ref&gt;Mather 2012, pp. 490.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;h \pi_0(m) = h \pi_Y \pi_0(m) = h \pi_Y(m) = h(m).&lt;/math&gt;

By the generalised tubular neighourhood theorem [prop 7.2?], we can replace &lt;math display=&quot;inline&quot;&gt;T_0&lt;/math&gt; with a tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; compatible with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;. This completes the construction of &lt;math display=&quot;inline&quot;&gt;T_X&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 491.&lt;/ref&gt;

This makes &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; an '''abstract stratified set''' with axioms...&lt;ref&gt;Mather 2012, pp. 491-492.&lt;/ref&gt;

This also makes &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; a '''controlled submersion''' because
# &lt;math display=&quot;inline&quot;&gt;h|X: X \to \R&lt;/math&gt; is a smooth submersion on each strata &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;, and
# for each stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; there is a tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T'_X&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;h(v) = h \pi_X(v)&lt;/math&gt; for all &lt;math display=&quot;inline&quot;&gt;v \in T'_X&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 493.&lt;/ref&gt;

The core of this is the concept of a '''vector field'''. A vector field is a function which assigns, for each point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; in a space, a '''vector''', which can be represented by an arrow whose tail starts at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.&lt;ref&gt;Henle 1979, pp. 33.&lt;/ref&gt;

[picture]

Imagine we have a vector field &lt;math display=&quot;inline&quot;&gt;v(x)&lt;/math&gt; defined in a space and draw a line through our space. At each point along this line the vector field assigns a vector. If we move each point in this line along the arrow defined by this vector in the direction of the arrow head. This &quot;flows&quot; the entire line along the vectors.

[picture]

We define a '''stratified vector field''' &lt;math display=&quot;inline&quot;&gt;\eta&lt;/math&gt; on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; to be a family of smooth vector fields &lt;math display=&quot;inline&quot;&gt;\eta_X&lt;/math&gt;, one for each strata &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 493.&lt;/ref&gt;

We define a '''controlled vector field''' &lt;math display=&quot;inline&quot;&gt;\eta&lt;/math&gt; on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; to be a stratified vector field such that for any strata &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; there exists a tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T'_Y&lt;/math&gt; such that for any &lt;math display=&quot;inline&quot;&gt;X &gt; Y&lt;/math&gt; and any &lt;math display=&quot;inline&quot;&gt;v \in T'_X \cap X&lt;/math&gt;&lt;ref&gt;Mather 2012, pp. 493.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;\eta_X \rho_{Y,X}(v) = 0,&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;(\pi_{Y,X})_* \eta_X(v) = \eta_Y (\pi_{Y,X}(v)).&lt;/math&gt;

We prove that if &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; is a controlled submersion then, for any smooth vector field &lt;math display=&quot;inline&quot;&gt;\zeta&lt;/math&gt; on &lt;math display=&quot;inline&quot;&gt;\R&lt;/math&gt; there is a controlled vector field &lt;math display=&quot;inline&quot;&gt;\eta&lt;/math&gt; on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;h_* \eta(v) = \zeta(h(v))&lt;/math&gt; for all &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 493.&lt;/ref&gt;

Proceeding by induction on the maximum dimension of the strata of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;, we define &lt;math display=&quot;inline&quot;&gt;Z_k&lt;/math&gt; to be the union of strata of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; of dimension at most &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;. The tubular neighbourhood of &lt;math display=&quot;inline&quot;&gt;Z_k&lt;/math&gt; is the intersection of the tubular neighbourhoods of each strata in &lt;math display=&quot;inline&quot;&gt;Z_k&lt;/math&gt; with &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;. The projection and distance functions are the restrictions of the respective functions of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;.

It is trivially true when the maximum dimension of strata in &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; is zero. Assume it is true for &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt; and construct each &lt;math display=&quot;inline&quot;&gt;\eta_X&lt;/math&gt; separately for each stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of dimension &lt;math display=&quot;inline&quot;&gt;k + 1&lt;/math&gt;.

By the assumption that we have controlled vector fields for all strata &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; of dimension at most &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;, we have the two control conditions defined above for any &lt;math display=&quot;inline&quot;&gt;X &gt; Y&lt;/math&gt; and that there is a neighbourhood &lt;math display=&quot;inline&quot;&gt;T^1_Y&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;h(v) = h \pi_Y(v)&lt;/math&gt; for &lt;math display=&quot;inline&quot;&gt;v \in T^1_Y&lt;/math&gt;.

We want to prove that for all &lt;math display=&quot;inline&quot;&gt;Y &lt; X&lt;/math&gt;, the control conditions are satisfied for all &lt;math display=&quot;inline&quot;&gt;v \in T^2_Y&lt;/math&gt; and that &lt;math display=&quot;inline&quot;&gt;h_*\eta_X(v) = \zeta(v)&lt;/math&gt; for all &lt;math display=&quot;inline&quot;&gt;v \in X&lt;/math&gt;.

Take a point &lt;math display=&quot;inline&quot;&gt;x \in X&lt;/math&gt; and define the set &lt;math display=&quot;inline&quot;&gt;S_v&lt;/math&gt; of strata &lt;math display=&quot;inline&quot;&gt;Y &lt; X&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;v \in T^2_Y&lt;/math&gt;. &lt;math display=&quot;inline&quot;&gt;S_v&lt;/math&gt; is totally ordered since if &lt;math display=&quot;inline&quot;&gt;Y_1&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Y_2&lt;/math&gt; are not comparable then &lt;math display=&quot;inline&quot;&gt;T^2_{Y_1} \cap T^2_{Y_2} = \empty&lt;/math&gt;. Therefore, there is a largest member &lt;math display=&quot;inline&quot;&gt;Y = Y_v&lt;/math&gt;.

Assume the control conditions hold for &lt;math display=&quot;inline&quot;&gt;Y = Y_v&lt;/math&gt;. Then they hold for all &lt;math display=&quot;inline&quot;&gt;Y_i \in S_v&lt;/math&gt;. For, either &lt;math display=&quot;inline&quot;&gt;Y_i = Y&lt;/math&gt; or &lt;math display=&quot;inline&quot;&gt;Y_i &lt; Y&lt;/math&gt;. In the latter case, &lt;math display=&quot;inline&quot;&gt;\pi_Y(v) \in T^1_{Y_i}&lt;/math&gt; (by the choice of &lt;math display=&quot;inline&quot;&gt;T^2_Y&lt;/math&gt;'s [is this why?]. Then

&lt;math display=&quot;block&quot;&gt;\begin{align}
\eta_X(v) \rho_{Y_i,X}(v) &amp;= \eta_X \rho_{Y_i,Y} \pi_{Y,X}(v) \\
&amp;= (\pi_{Y,X})_* \eta_X(v) \rho_{Y_i,Y} \\
&amp;= \eta_Y(\pi_{Y,X}(v)) \rho_{Y_i,Y} \\
&amp;= 0
\end{align}&lt;/math&gt;

and

&lt;math display=&quot;block&quot;&gt;\begin{align}
(\pi_{Y_i,X})_* \eta_X(v) &amp;= (\pi_{Y_i,Y})_* (\pi_{Y,X})_* \eta_X(v) \\
&amp;= (\pi_{Y_i,Y})_* \eta_Y(v) (\pi_{Y,X}) \\
&amp;= \eta_{Y_i}(\pi_{Y_i,Y} \pi_{Y,X}(v)) \\
&amp;= \eta_{Y_i}(\pi_{Y_i,X}(v))
\end{align}&lt;/math&gt;

and, therefore, condition holds for all &lt;math display=&quot;inline&quot;&gt;Y_i \in S_v&lt;/math&gt;. Also,

&lt;math display=&quot;block&quot;&gt;\begin{align}
h_* \eta_X(v) &amp;= (h \circ \pi_{Y,X})_* \eta_X(v) \\
&amp;= h_* \eta_Y (\pi_{Y,X}(v)) \\
&amp;= \zeta(f(v))
\end{align}&lt;/math&gt;

and, therefore, the conclusion of the theorem holds at &lt;math display=&quot;inline&quot;&gt;v&lt;/math&gt;.

This shows we can construct &lt;math display=&quot;inline&quot;&gt;\eta_X&lt;/math&gt; satisfying the control conditions when &lt;math display=&quot;inline&quot;&gt;S_v&lt;/math&gt; is non-empty and satisfying the theorem when &lt;math display=&quot;inline&quot;&gt;S_v&lt;/math&gt; is empty. The set of vectors satisfying these conditions is convex in &lt;math display=&quot;inline&quot;&gt;TX_v&lt;/math&gt;, and so we construct &lt;math display=&quot;inline&quot;&gt;\eta_X&lt;/math&gt; globally via a partition of unity.&lt;ref&gt;Mather 2012, pp. 493-495.&lt;/ref&gt;

Finally, we prove that a controlled vector field has a unique one-parameter family of homeomorphisms of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; which commute with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;.&lt;ref&gt;Mather 2012, this combines Proposition 10.1 and Corollary 10.2 on pp. 496 and 497, respectively.&lt;/ref&gt;

For each stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;\eta_X&lt;/math&gt; generates a unique smooth local one-parameter group &lt;math display=&quot;inline&quot;&gt;(J_X, \alpha_X)&lt;/math&gt; of diffeomorphisms of &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; (by standard results of differential geometry), such that &lt;math display=&quot;inline&quot;&gt;\frac{d}{dt} \alpha(t, v)|_{t=0} = \eta_X(v)&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;J_X&lt;/math&gt; is an open subset of &lt;math display=&quot;inline&quot;&gt;\R \times Z&lt;/math&gt;, ...

If we define &lt;math display=&quot;inline&quot;&gt;(J, \alpha)&lt;/math&gt; by

&lt;math display=&quot;block&quot;&gt;J = \bigcup_{X \in S} J_X&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;\alpha = \bigcup_{X \in S} \alpha_X&lt;/math&gt;

we can prove that this is a local one-parameter family of homeomorphisms.&lt;ref&gt;Mather 2012, pp. 496.&lt;/ref&gt;

Firstly, it is clear that
# &lt;math display=&quot;inline&quot;&gt;0 \times Z \subseteq J&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\alpha(0, v) = v&lt;/math&gt; for all &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt;.
# If &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt; then &lt;math display=&quot;inline&quot;&gt;J_v = J \cap (\R \times v) \subseteq \R&lt;/math&gt; is an open interval &lt;math display=&quot;inline&quot;&gt;(a_v, b_v)&lt;/math&gt;, possibly infinite at one or both ends.
# If &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;t, s, t + s&lt;/math&gt; are in &lt;math display=&quot;inline&quot;&gt;(a_v, b_v)&lt;/math&gt; then &lt;math display=&quot;inline&quot;&gt;\alpha(t + s, v) = \alpha(t, \alpha(s, v))&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 495.&lt;/ref&gt;

Secondly, it is clear that &lt;math display=&quot;inline&quot;&gt;\eta&lt;/math&gt; generates &lt;math display=&quot;inline&quot;&gt;\alpha&lt;/math&gt; because
# Each stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; is invariant under &lt;math display=&quot;inline&quot;&gt;\alpha&lt;/math&gt;, i.e. &lt;math display=&quot;inline&quot;&gt;\alpha[J \cap (\R \times X)] \subseteq X&lt;/math&gt;.
# For each &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt;, the map &lt;math display=&quot;inline&quot;&gt;t \to \alpha(t, v)&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;(a_v, b_v)&lt;/math&gt; into the stratum which contains &lt;math display=&quot;inline&quot;&gt;v&lt;/math&gt; is &lt;math display=&quot;inline&quot;&gt;C^1&lt;/math&gt;.
# For any &lt;math display=&quot;inline&quot;&gt;(t, v) \in Z&lt;/math&gt;(?) we have &lt;math display=&quot;inline&quot;&gt;d/dt \alpha(t, v) = \eta(\alpha(t, v))&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 495.&lt;/ref&gt;

It is unique because each &lt;math display=&quot;inline&quot;&gt;(J_X, \alpha_X)&lt;/math&gt; is unique. We just need to prove that &lt;math display=&quot;inline&quot;&gt;J&lt;/math&gt; is open, &lt;math display=&quot;inline&quot;&gt;\alpha&lt;/math&gt; is continuous, and for any &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt; and any compact set &lt;math display=&quot;inline&quot;&gt;K \subseteq Z&lt;/math&gt; there exists &lt;math display=&quot;inline&quot;&gt;\epsilon &gt; 0&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;\alpha(t, v) \notin K&lt;/math&gt; if &lt;math display=&quot;inline&quot;&gt;t \in (a_v, a_v + \epsilon) \cup (b_v - \epsilon, b_v)&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 495.&lt;/ref&gt;

For the latter-most condition, if it did not hold then there exists...&lt;ref&gt;Mather 2012, pp. 496-497.&lt;/ref&gt;

We prove there is a homeomorphism &lt;math display=&quot;inline&quot;&gt;f: Z \to h^{-1}(0) \times \R&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;\pi \circ f = h&lt;/math&gt;, where &lt;math display=&quot;inline&quot;&gt;\pi: h^{-1}(0) \times \R \to \R&lt;/math&gt; is projection to the second factor.

For the coordinate vector field &lt;math display=&quot;inline&quot;&gt;\partial&lt;/math&gt; on &lt;math display=&quot;inline&quot;&gt;\R&lt;/math&gt;, by [prop 9.1] there is a controlled vector field &lt;math display=&quot;inline&quot;&gt;\tilde\partial&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;f_* \tilde\partial(v) = \partial(h(v))&lt;/math&gt; for &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt;. By [prop 10.1], &lt;math display=&quot;inline&quot;&gt;\tilde\partial&lt;/math&gt; generates a local one-parameter group &lt;math display=&quot;inline&quot;&gt;(J, \alpha)&lt;/math&gt; such that

&lt;math display=&quot;block&quot;&gt;h(\alpha(t,v)) = h(v) + t&lt;/math&gt;

&lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; is proper and [d] holds, so &lt;math display=&quot;inline&quot;&gt;J = \R \times Z&lt;/math&gt;. If we define &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; as

&lt;math display=&quot;block&quot;&gt;f(v) = (\alpha(-t, v), h(v))&lt;/math&gt;

then &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; maps &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; into &lt;math display=&quot;inline&quot;&gt;h^{-1}(0) \times \R&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi \circ f = h&lt;/math&gt;. If we define &lt;math display=&quot;inline&quot;&gt;\bar f: h^{-1}(0) \times \R \to Z&lt;/math&gt; as

&lt;math display=&quot;block&quot;&gt;\bar f(v, t) = \alpha(t, v)&lt;/math&gt;

then &lt;math display=&quot;inline&quot;&gt;f \bar f = \bar f f = Id&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; is a homeomorphism.&lt;ref&gt;Mather 2012, pp. 497.&lt;/ref&gt;

== Topology at critical points ==

Theorem: If there is a critical point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; in the singular variety &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt; with critical value &lt;math display=&quot;inline&quot;&gt;v \in (a, b)&lt;/math&gt; then the space &lt;math display=&quot;inline&quot;&gt;X_{\leq b}&lt;/math&gt; is homotopic to&lt;ref&gt;Goresky and MacPherson 1988, pp. 174.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;X_{\leq a} \cup [(D^{\lambda+1}, \partial D^{\lambda+1}) \times (\mathcal{L}_X, \partial \mathcal{L}_X)].&lt;/math&gt;

Proof:&lt;ref&gt;Proof outline comes from Goresky and MacPherson 1988, pp. 174.&lt;/ref&gt;
# &lt;math display=&quot;inline&quot;&gt;(X_{\leq b}, X_{\leq a})&lt;/math&gt; is homeomorphic to &lt;math display=&quot;inline&quot;&gt;(X_{\leq v + \epsilon}, X_{\leq v -\epsilon})&lt;/math&gt;. We can prove this by &quot;moving wall&quot; or Thom's Isotopy Lemma.&lt;ref&gt;Goresky and MacPherson 1988, pp. 90-91, 120.&lt;/ref&gt;
# &lt;math display=&quot;inline&quot;&gt;X_{\leq v + \epsilon}&lt;/math&gt; is homeomorphic to &lt;math display=&quot;inline&quot;&gt;X_{\leq v - \epsilon} \cup (J, K)&lt;/math&gt;, where the latter is the local Morse data for &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;. We do this by moving the wall...&lt;ref&gt;Goresky and MacPherson 1988, pp. 95-96, 120-121.&lt;/ref&gt;
# &lt;math display=&quot;inline&quot;&gt;(J, K)&lt;/math&gt; is homeomorphic to &lt;math display=&quot;inline&quot;&gt;(D^{\lambda+1}, \partial D^{\lambda+1}) \times (\mathcal{L}_X, \partial \mathcal{L}_X)&lt;/math&gt; (tangential data, normal data). Again, moving the wall...&lt;ref&gt;Goresky and MacPherson 1988, pp. 65-66, chapter 8, 121.&lt;/ref&gt;
# The normal Morse data depends only on the differential &lt;math display=&quot;inline&quot;&gt;df(p)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 93.&lt;/ref&gt;
# The normal Morse data has the homotopy type of &lt;math display=&quot;inline&quot;&gt;(\mathcal{L}_X, \partial \mathcal{L}_X)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 169.&lt;/ref&gt;

=== Step 1 ===

We get this immediately(?) by Thom's Isotopy Lemma.

=== Step 2 ===

&lt;ref&gt;Goresky and MacPherson 1988, complex case on pp. 120-121 is extension of real case on pp. 95-96.&lt;/ref&gt;

Step 1 works because &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; is a submersion at each point of the regions we are homeomorphing. This is not the case at critical points. We need some way by which a homeomorphism can pass through a critical point.

To prove a homeomorphism between two subsets &lt;math display=&quot;inline&quot;&gt;A&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;B&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;, we project &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; to some other space &lt;math display=&quot;inline&quot;&gt;N&lt;/math&gt; (in our case &lt;math display=&quot;inline&quot;&gt;\R^n&lt;/math&gt;) using some function &lt;math display=&quot;inline&quot;&gt;F&lt;/math&gt;. We take subsets &lt;math display=&quot;inline&quot;&gt;Y_0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Y_1&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;N&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;A = Z \cap F^{-1}(Y_0)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;B = Z \cap F^{-1}(Y_1)&lt;/math&gt;. We need to prove &lt;math display=&quot;inline&quot;&gt;Y_0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Y_1&lt;/math&gt; are connected by a one-parameter family of regions &lt;math display=&quot;inline&quot;&gt;Y_t&lt;/math&gt; [explain one-parameter family]. The criterion for such a family to exist is that the '''characteristic covectors''' of &lt;math display=&quot;inline&quot;&gt;F&lt;/math&gt; are all nonzero on each stratum of &lt;math display=&quot;inline&quot;&gt;Y_t&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 70.&lt;/ref&gt;

At each point &lt;math display=&quot;inline&quot;&gt;x \in M&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;y \in N&lt;/math&gt; there are '''tangent spaces''' &lt;math display=&quot;inline&quot;&gt;T_xM&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;T_yN&lt;/math&gt;, a vector space whose zero is at the point &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; or &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt; (resp.)

[picture of various tangent spaces]

In the case the &lt;math display=&quot;inline&quot;&gt;N = \R&lt;/math&gt;, the tangent space &lt;math display=&quot;inline&quot;&gt;T_x\R&lt;/math&gt; is just &lt;math display=&quot;inline&quot;&gt;\R&lt;/math&gt; but whose origin is at &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt;.

[picture of T_x\R]

Say &lt;math display=&quot;inline&quot;&gt;F(x) = y&lt;/math&gt;, then the differential of the map &lt;math display=&quot;inline&quot;&gt;F&lt;/math&gt; can be seen as a function whose input is a vector in the tangent space &lt;math display=&quot;inline&quot;&gt;T_xM&lt;/math&gt; and whose output is a vector in the tangent space &lt;math display=&quot;inline&quot;&gt;T_yM&lt;/math&gt;. [If I move this far on the tangent space of M how do I move in the tangent space of N?]

[picture]

[example for M = \R and N = \R?]

A function which takes as input a vector in the tangent space &lt;math display=&quot;inline&quot;&gt;T_xM&lt;/math&gt; (say) and outputs a scalar (usually &lt;math display=&quot;inline&quot;&gt;\R&lt;/math&gt;) is called a '''covector'''. The set of all covectors on &lt;math display=&quot;inline&quot;&gt;T_xM&lt;/math&gt; is called the dual space of &lt;math display=&quot;inline&quot;&gt;T_xM&lt;/math&gt; and is denoted &lt;math display=&quot;inline&quot;&gt;T^*_xM&lt;/math&gt;. There are only a limited number of ways to express a covectors. For example, if our tangent space is two-dimensional then all covectors are of the form &lt;math display=&quot;inline&quot;&gt;ax + by&lt;/math&gt; where &lt;math display=&quot;inline&quot;&gt;(x, y) \in T_xM&lt;/math&gt;.

We take our space &lt;math display=&quot;inline&quot;&gt;M&lt;/math&gt; and map it onto &lt;math display=&quot;inline&quot;&gt;\R^2&lt;/math&gt; with the map &lt;math display=&quot;inline&quot;&gt;F(z) = (r(z), h(z))&lt;/math&gt;, where &lt;math display=&quot;inline&quot;&gt;z \in M&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;r&lt;/math&gt; is the square of the distance of &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt; to the critical point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.

[graph of mapping]

In this case, the covectors on the tangent space &lt;math display=&quot;inline&quot;&gt;T_xM&lt;/math&gt; are of the form &lt;math display=&quot;inline&quot;&gt;adf(x) + bdr(x)&lt;/math&gt; (in this case &lt;math display=&quot;inline&quot;&gt;df&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;dr&lt;/math&gt; are maps to &lt;math display=&quot;inline&quot;&gt;\R&lt;/math&gt;) and on &lt;math display=&quot;inline&quot;&gt;T_y\R^2&lt;/math&gt; are of the form &lt;math display=&quot;inline&quot;&gt;cu + dv&lt;/math&gt; (for &lt;math display=&quot;inline&quot;&gt;(u, v) \in \R^2&lt;/math&gt;). A covector &lt;math display=&quot;inline&quot;&gt;cu + dv \in T^*_{(u, v)}\R^2&lt;/math&gt; is called a '''characteristic covector''' of &lt;math display=&quot;inline&quot;&gt;F&lt;/math&gt; if &lt;math display=&quot;inline&quot;&gt;F(x) = (u, v)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;cdf(x) + ddr(x) = 0&lt;/math&gt; for all vectors in the tangent space of the stratum containing &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 82.&lt;/ref&gt; [explain adf(x) + bdr(x) in terms of this being a function which takes a vector input]

[example of where covectors do and do not vanish on a stratified space, pp. 71?]

What we want is a homeomorphism in &lt;math display=&quot;inline&quot;&gt;M&lt;/math&gt; between the space &lt;math display=&quot;inline&quot;&gt;Z_{\leq \epsilon}&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Z_{\leq \epsilon} \cup B&lt;/math&gt;, where &lt;math display=&quot;inline&quot;&gt;B&lt;/math&gt; is a small region of the critical point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;. The '''local Morse data''' is

&lt;math display=&quot;block&quot;&gt;((B_\delta \cap Z) \cap f^{-1}[v-\epsilon, v+\epsilon], (B_\delta \cap Z) \cap f^{-1}(v-\epsilon))&lt;/math&gt;

where &lt;math display=&quot;inline&quot;&gt;B_\delta&lt;/math&gt; is a closed disc in &lt;math display=&quot;inline&quot;&gt;M&lt;/math&gt; of radius &lt;math display=&quot;inline&quot;&gt;\delta&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 63-64.&lt;/ref&gt; Observe that this is the pair &lt;math display=&quot;inline&quot;&gt;(F^{-1}(\text{Box}(\delta, \epsilon)), F^{-1}(\text{Bottom}(\delta, \epsilon)))&lt;/math&gt;&lt;ref&gt;Goresky and MacPherson 1988, pp. 91.&lt;/ref&gt; [explain Box, Bottom, etc.]

[picture of the two subspaces of Z in M]

We use our map &lt;math display=&quot;inline&quot;&gt;F&lt;/math&gt; to convert these two subspaces to subspaces of &lt;math display=&quot;inline&quot;&gt;\R^2&lt;/math&gt; which are of the form &lt;math display=&quot;inline&quot;&gt;Y_1 = \{(x,y) \in \R^2 | y \leq \epsilon\}&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Y_0 = \{(x,y) \in \R^2 | y \leq -\epsilon\} \cup \{(x,y) \in \R^2 | x \leq \delta, y \leq \epsilon\}&lt;/math&gt;, such that &lt;math display=&quot;inline&quot;&gt;Z_{\leq \epsilon} = F^{-1}(Y_1)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Z_{\leq \epsilon} \cup B = F^{-1}(Y_0)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 95-96.&lt;/ref&gt;

We use a homeomorphism between &lt;math display=&quot;inline&quot;&gt;Y_1&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Y_0&lt;/math&gt; using the technique of &quot;moving the wall&quot; and Thom's Isotopy Lemma. Such a homeomorphism exists when the characteristic covectors of &lt;math display=&quot;inline&quot;&gt;F&lt;/math&gt; are all nonzero on each stratum of &lt;math display=&quot;inline&quot;&gt;Y_t&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, chapter 4, particularly pp. 71-72.&lt;/ref&gt;

Given a smooth mapping between manifolds &lt;math display=&quot;inline&quot;&gt;F: M \to N&lt;/math&gt; (for example, in our case we could have &lt;math display=&quot;inline&quot;&gt;N = \R^2&lt;/math&gt;) and that &lt;math display=&quot;inline&quot;&gt;F|Z: Z \to N&lt;/math&gt; is proper. Let &lt;math display=&quot;inline&quot;&gt;Y \subset N \times \R&lt;/math&gt; be a closed Whitney stratified subset such that the projection to the second factor &lt;math display=&quot;inline&quot;&gt;\pi: Y \to \R&lt;/math&gt; is a proper stratified submersion.&lt;ref&gt;Goresky and MacPherson 1988, pp. 71.&lt;/ref&gt;

Suppose for each &lt;math display=&quot;inline&quot;&gt;t \in \R&lt;/math&gt;, for each &lt;math display=&quot;inline&quot;&gt;p \in F(Z) \cap Y_t&lt;/math&gt;, and for each nonzero characteristic covector &lt;math display=&quot;inline&quot;&gt;\lambda \in T^*_pN&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;F|Z&lt;/math&gt;, the restriction of &lt;math display=&quot;inline&quot;&gt;\lambda&lt;/math&gt; to the subspace &lt;math display=&quot;inline&quot;&gt;T_pS_t = \ker(d\pi(p)) \cap T_pS&lt;/math&gt; is nonzero, where &lt;math display=&quot;inline&quot;&gt;S&lt;/math&gt; is a stratum of &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; which contains &lt;math display=&quot;inline&quot;&gt;(p, t)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;S_t = \pi^{-1}(t) \cap S&lt;/math&gt; is the stratum of &lt;math display=&quot;inline&quot;&gt;Y_t = \pi^{-1}(t) \cap Y&lt;/math&gt; which contains &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;. This is equivalent to the statement that, for each &lt;math display=&quot;inline&quot;&gt;t \in \R&lt;/math&gt;, the restriction &lt;math display=&quot;inline&quot;&gt;F|Z&lt;/math&gt; is transverse to &lt;math display=&quot;inline&quot;&gt;Y_t&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 71-72.&lt;/ref&gt;

This means that, for each &lt;math display=&quot;inline&quot;&gt;t \in \R&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;Z \cap F^{-1}(Y_t)&lt;/math&gt; is stratified by its intersection with the strata of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;...

We finally prove there is a homeomorphism between &lt;math display=&quot;inline&quot;&gt;Z \cap F^{-1}(Y_0) \cong Z \cap F^{-1}(Y_1)&lt;/math&gt; which preserves the Whitney stratification of both sides and is smooth on each stratum.

For the composition

&lt;math display=&quot;block&quot;&gt;Z \times \R \subset M \times \R \to_{F \times I} Y \subset \R^2 \times \R \to_{\pi} \R&lt;/math&gt;

where &lt;math display=&quot;inline&quot;&gt;Y(t, z) = Y_t(z)&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;I&lt;/math&gt; is the identity and &lt;math display=&quot;inline&quot;&gt;\pi&lt;/math&gt; is projection to the second factor. 

&lt;math display=&quot;inline&quot;&gt;Z \times \R&lt;/math&gt; is transverse to &lt;math display=&quot;inline&quot;&gt;(F \times I)^{-1}(Y)&lt;/math&gt;...

The composition &lt;math display=&quot;inline&quot;&gt;\pi \circ (F \times I): Z \times \R \cap (F \times I)^{-1}(Y) \to \R&lt;/math&gt; is a stratified submersion because
* The input domain is stratified as above...,
* We have defined &lt;math display=&quot;inline&quot;&gt;F|Z&lt;/math&gt; to be transverse to &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt;, and therefore it preserves the stratification (unless &lt;math display=&quot;inline&quot;&gt;F(Z) \cap Y = \empty&lt;/math&gt;), and
* We defined above the projection on &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; to be a stratified submersion, meaning it is a submersion on each stratum of &lt;math display=&quot;inline&quot;&gt;F(Z) \cap Y&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 43.&lt;/ref&gt;

Therefore, we can apply Thom's Isotopy Lemma which says there is a homeomorphism between the level sets of &lt;math display=&quot;inline&quot;&gt;Z \times \R&lt;/math&gt;...&lt;ref&gt;Goresky and MacPherson 1988, pp. 72.&lt;/ref&gt;

=== Step 3 ===

==== Characteristic covectors ====

==== Fringed sets ====

When manipulating our domain of integration[?], we need to make sure we are doing this in regions with no characteristic covectors. The introduce the concept of a fringed set, a subset of &lt;math display=&quot;inline&quot;&gt;R^2&lt;/math&gt;, and construct a series of fringed sets which contain no characteristic covectors.

A '''fringed set''' &lt;math display=&quot;inline&quot;&gt;A \subset \R \times \R^+&lt;/math&gt; is an open subset of the first quadrant of &lt;math display=&quot;inline&quot;&gt;\R^2&lt;/math&gt;. &lt;math display=&quot;inline&quot;&gt;A&lt;/math&gt; is fringed over &lt;math display=&quot;inline&quot;&gt;0 &lt; y \ll x&lt;/math&gt; if for some interval &lt;math display=&quot;inline&quot;&gt;S = (0, x)&lt;/math&gt;
# the projection of &lt;math display=&quot;inline&quot;&gt;A&lt;/math&gt; to the first factor is equal to &lt;math display=&quot;inline&quot;&gt;S&lt;/math&gt;,
# &lt;math display=&quot;inline&quot;&gt;A&lt;/math&gt; is open in &lt;math display=&quot;inline&quot;&gt;S \times \R^+&lt;/math&gt;,
# if &lt;math display=&quot;inline&quot;&gt;(s, y) \in A&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;0 &lt; y' \leq y&lt;/math&gt; then &lt;math display=&quot;inline&quot;&gt;(s, y') \in A&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 77.&lt;/ref&gt;

[picture]

The fringed set &lt;math display=&quot;inline&quot;&gt;A^\flat&lt;/math&gt; is the set &lt;math display=&quot;inline&quot;&gt;A&lt;/math&gt; plus its reflection about the &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; axis.&lt;ref&gt;Goresky and MacPherson 1988, pp. 82.&lt;/ref&gt;

[picture]

We build a series of fringed sets which do not contain characteristic covectors, which will be used later in our proof.

There exists a fringed set &lt;math display=&quot;inline&quot;&gt;A_2&lt;/math&gt; of type &lt;math display=&quot;inline&quot;&gt;0 &lt; v \ll u&lt;/math&gt; such that for any &lt;math display=&quot;inline&quot;&gt;z \in Z&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;r\pi(z) \leq r_2&lt;/math&gt;, the map &lt;math display=&quot;inline&quot;&gt;(\rho, f - f\pi)|\pi^{-1}(\pi(z)): \pi^{-1}(\pi(z)) \to \R^2&lt;/math&gt; has no characteristic covectors in &lt;math display=&quot;inline&quot;&gt;A^\flat_2&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 84.&lt;/ref&gt;

Given that the set of points &lt;math display=&quot;inline&quot;&gt;(u, v) \in \R^2&lt;/math&gt; which have a nonzero characteristic covector is closed, then it is enough to prove it for points &lt;math display=&quot;inline&quot;&gt;(u, 0) \in \R^2&lt;/math&gt;. Proof by contradiction. Assume it is false and that there is a sequence of points &lt;math display=&quot;inline&quot;&gt;p_i \in Z \cap f^{-1}(0)&lt;/math&gt; converging to &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;d\rho(p_i)&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;df(p_i)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;df\pi(p_i)&lt;/math&gt; are linearly dependent when restricted to the stratum &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; which contains &lt;math display=&quot;inline&quot;&gt;p_i&lt;/math&gt;. This would mean that &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; has a critical point on &lt;math display=&quot;inline&quot;&gt;Y \cap \partial B_{\rho(p_i)}(p)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 82-83.&lt;/ref&gt;

By restricting to a subsequence if necessary, we may assume the points &lt;math display=&quot;inline&quot;&gt;p_i&lt;/math&gt; are all contained in the same stratum &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt;, that the tangent planes &lt;math display=&quot;inline&quot;&gt;T_{p_i}Y&lt;/math&gt; converge to some plane &lt;math display=&quot;inline&quot;&gt;Q&lt;/math&gt; and the secant lines &lt;math display=&quot;inline&quot;&gt;\mathcal{l}_i = \overline{p_i p}&lt;/math&gt; converge to some line &lt;math display=&quot;inline&quot;&gt;\mathcal{l}&lt;/math&gt;. By the Whitney conditions [how?], &lt;math display=&quot;inline&quot;&gt;Q = \lim_{i \to \infty} \mathcal{l}_i \oplus T_{p_i}(Y \cap \partial B_\delta(p))&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 83.&lt;/ref&gt;

For each &lt;math display=&quot;inline&quot;&gt;i&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;f(p_i) = f(p) = v&lt;/math&gt;, this means[?] &lt;math display=&quot;inline&quot;&gt;df(p)(Q) = 0&lt;/math&gt;. On the assumption that &lt;math display=&quot;inline&quot;&gt;df(p)&lt;/math&gt; is nondegenerate, we may assume &lt;math display=&quot;inline&quot;&gt;Y = X&lt;/math&gt;, so &lt;math display=&quot;inline&quot;&gt;\ker d(f|X)(p_i) = T_{p_i}(X \cap \partial B_\delta(p)) = T_{p_i}(X \cap f^{-1}(v))&lt;/math&gt;, which converges to a subspace &lt;math display=&quot;inline&quot;&gt;\tau&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Q = T_pX&lt;/math&gt;, perpendicular to &lt;math display=&quot;inline&quot;&gt;\mathcal{l}&lt;/math&gt;. However, as &lt;math display=&quot;inline&quot;&gt;f^{-1}(v) \cap X&lt;/math&gt; satisfies Whitney's conditions, &lt;math display=&quot;inline&quot;&gt;\mathcal{l} \subset \tau&lt;/math&gt;, a contradiction.&lt;ref&gt;Goresky and MacPherson 1988, pp. 83.&lt;/ref&gt;

==== Homeomorphism ====

We prove there is a stratum preserving homeomorphism between&lt;ref&gt;Goresky and MacPherson 1988, pp. 65.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;\text{Local Morse Data} \cong (\text{Tangential Morse Data}) \times (\text{Normal Morse Data})&lt;/math&gt;

We first prove that there is a homeomorphism between the product of the normal and tangential Morse data and the '''realisation''' of the following diagram

[diagram from pp. 102]

where realisation means

&lt;math display=&quot;block&quot;&gt;Z \cap (g_1, h_1)^{-1}(P_a) \cap (g_2, h_2)^{-1}(P_b)&lt;/math&gt;

where all the intersections of strata (of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;?) are transverse.&lt;ref&gt;Goresky and MacPherson 1988, pp. 100-102.&lt;/ref&gt;

The realisation of the above diagram is equal to

&lt;math display=&quot;block&quot;&gt;(V_1, V_2) \cap (W_1, W_2) = (V_1 \cap W_1, V_1 \cap W_2 \cup V_2 \cap W_1)&lt;/math&gt;

where

&lt;math display=&quot;block&quot;&gt;V_1 = \{ z \in Z : |f(z) - f\pi(z)| \leq \epsilon/4, r\pi(z) \leq \delta, \rho(z) \leq \delta \}&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;V_2 = \{ z \in Z : f(z) - f\pi(z) = -\epsilon/4, r\pi(z) \leq \delta, \rho(z) \leq \delta \}&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;W_1 = \{ z \in Z : |f\pi(z)| \leq 3\epsilon/4, r\pi(z) \leq \delta \}&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;W_1 = \{ z \in Z : f\pi(z) = -3\epsilon/4, r\pi(z) \leq \delta \}&lt;/math&gt;

where &lt;math display=&quot;inline&quot;&gt;\pi&lt;/math&gt; is the projection from the tubular neighbourhood to &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;r(z)&lt;/math&gt; is the square of the distance between &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt; and the critical point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\rho(z)&lt;/math&gt; is the square of the distance between &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi(z)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 100-101.&lt;/ref&gt; &lt;math display=&quot;inline&quot;&gt;\epsilon \ll \delta&lt;/math&gt; are chosen so that &lt;math display=&quot;inline&quot;&gt;(\delta, \epsilon)&lt;/math&gt; is in the set &lt;math display=&quot;inline&quot;&gt;A^\flat_6&lt;/math&gt; which consists of &lt;math display=&quot;inline&quot;&gt;A_6 \subset \R^+ \times \R^+&lt;/math&gt; with the properties that for &lt;math display=&quot;inline&quot;&gt;(\epsilon, \delta) \in A_6&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;\rho(z) = \delta&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;r\pi(z) = \delta&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;|f(z)| \leq \epsilon&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;|f\pi(z)| \leq \epsilon&lt;/math&gt; then the covectors &lt;math display=&quot;inline&quot;&gt;d\rho(z)&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;dr\pi(z)&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;df(z)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;df\pi(z)&lt;/math&gt; are linearly independent when restricted to &lt;math display=&quot;inline&quot;&gt;T_zY&lt;/math&gt; (where &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; is the stratum containing &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt;). We can prove such a set exists.&lt;ref&gt;Goresky and MacPherson 1988, pp. 89.&lt;/ref&gt; &lt;math display=&quot;inline&quot;&gt;A^\flat_6&lt;/math&gt; is this plus its reflection about the &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; axis.&lt;ref&gt;Goresky and MacPherson 1988, pp. 82.&lt;/ref&gt;

Let &lt;math display=&quot;inline&quot;&gt;D = \{ x \in X | r(x) \leq \delta \}&lt;/math&gt; for stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt;. We will show there is a local trivial fibration of the configuration: &lt;math display=&quot;inline&quot;&gt;(V_1, V_2)&lt;/math&gt; fibres over &lt;math display=&quot;inline&quot;&gt;D&lt;/math&gt; and is homeomorphic to &lt;math display=&quot;inline&quot;&gt;D \times (\text{normal Morse data})&lt;/math&gt;

(V_1, V_2) -&gt; D \times (normal Morse data)
|           /
--&gt; D   &lt;---

and that &lt;math display=&quot;inline&quot;&gt;(W_1, W_2)&lt;/math&gt; fibres over the tangential Morse data and is homeomorphic to &lt;math display=&quot;inline&quot;&gt;(\text{tangential Morse data}) \times (\text{normal slice})&lt;/math&gt;.

For &lt;math display=&quot;inline&quot;&gt;Z_1 = \{ z \in Z : r\pi(z) \leq \delta \}&lt;/math&gt;, the map &lt;math display=&quot;inline&quot;&gt;F(z): Z_1 \to \R^2 = (\rho(z), f(z) - f\pi(z))&lt;/math&gt; is transverse to each stratum of &lt;math display=&quot;inline&quot;&gt;\text{Box}(\delta, \epsilon/4)&lt;/math&gt;, [list], [by lemma 6.5]. &lt;math display=&quot;inline&quot;&gt;(V_1, V_2) = F^{-1}(\text{Box}(\delta, \epsilon/4), \text{Bottom}(\delta, \epsilon/4))&lt;/math&gt;. For each stratum &lt;math display=&quot;inline&quot;&gt;S&lt;/math&gt; of Box and each &lt;math display=&quot;inline&quot;&gt;x \in D&lt;/math&gt;, we have transverse intersection &lt;math display=&quot;inline&quot;&gt;F^{-1}(S) \pitchfork \pi^{-1}(x)&lt;/math&gt;. Therefore, &lt;math display=&quot;inline&quot;&gt;\pi|F^{-1}(S)&lt;/math&gt; is a submersion and by Thom's isotopy lemma the projection &lt;math display=&quot;inline&quot;&gt;\pi|F^{-1}(\text{Box}(\delta, \epsilon/4): F^{-1}(\text{Box}(\delta, \epsilon/4)) \to X&lt;/math&gt; is a stratified fibre bundle over &lt;math display=&quot;inline&quot;&gt;D&lt;/math&gt;. The fibre over the critical point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; is &lt;math display=&quot;inline&quot;&gt;\pi^{-1}(p) \cap (F^{-1}(\text{Box}(\delta, \epsilon/4), F^{-1}(\text{Bottom}(\delta, \epsilon/4))&lt;/math&gt; and is equal to the normal Morse data...&lt;ref&gt;Goresky and MacPherson 1988, pp. 101.&lt;/ref&gt;

Take &lt;math display=&quot;inline&quot;&gt;G: X \to \R^2 = (r(x), f(x))&lt;/math&gt;. &lt;math display=&quot;inline&quot;&gt;\delta&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\epsilon&lt;/math&gt; have been chosen so that &lt;math display=&quot;inline&quot;&gt;(G^{-1}(\text{Box}(\delta, \epsilon/4), G^{-1}(\text{Bottom}(\delta, \epsilon/4))&lt;/math&gt; is the tangential Morse data for &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; and is contained in the region &lt;math display=&quot;inline&quot;&gt;D&lt;/math&gt; over which &lt;math display=&quot;inline&quot;&gt;\pi|(V_1, V_2)&lt;/math&gt; is a stratified fibre bundle. Therefore, &lt;math display=&quot;inline&quot;&gt;(W_1, W_2) = \pi^{-1} G^{-1}(\text{Box}(\delta, \epsilon/4), \text{Bottom}(\delta, \epsilon/4))&lt;/math&gt; is transverse to &lt;math display=&quot;inline&quot;&gt;(V_1, V_2)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 101-102.&lt;/ref&gt;

Finally, this means that &lt;math display=&quot;inline&quot;&gt;(V_1, V_2) \cap (W_1, W_2)&lt;/math&gt; is homeomorphic (by stratum preserving homeomorphism) to &lt;math display=&quot;inline&quot;&gt;(\pi^{-1}(p), \cap (V_1, V_2)) \times \pi(W_1, W_2)&lt;/math&gt;, the product of normal and tangential Morse data.&lt;ref&gt;Goresky and MacPherson 1988, pp. 102.&lt;/ref&gt;

We use a succession of such diagrams to interpolate between the box diagram which defines local Morse data [explain] and the above diagram whose realisation we have just proven is &lt;math display=&quot;inline&quot;&gt;(\text{normal Morse data}) \times (\text{tangential Morse data})&lt;/math&gt;.

[diagram_d0.py]

The realisation is the local Morse data. This is equal to the realisation of the diagram below.&lt;ref&gt;Goresky and MacPherson 1988, pp. 103, 106.&lt;/ref&gt;

[diagram_d11.py]

The realisation of the first diagram [d0] is equivalent to the realisation of the below diagram.

[diagram_d1.py]

In the right-hand picture of the above diagram, we have put a dotted outline around the region &lt;math display=&quot;inline&quot;&gt;A^{\flat}_1&lt;/math&gt;. We prove that there are no characteristic covectors for &lt;math display=&quot;inline&quot;&gt;(r, f): Z \to \R^2&lt;/math&gt; in this region and can, therefore, move the wall in this region...&lt;ref&gt;Goresky and MacPherson 1988, pp. 82-83.&lt;/ref&gt;

By adding a zero-dimensional stratum at the top right corner of the right-hand picture. A one-parameter family of pictures &lt;math display=&quot;inline&quot;&gt;P_b(t)&lt;/math&gt; gives rise to a stratified space &lt;math display=&quot;inline&quot;&gt;Y \subset M \times \R&lt;/math&gt; such that

&lt;math display=&quot;block&quot;&gt;Y = \{ (z, t) \in M \times \R : (r, f)(z) \in P_b(t) \}.&lt;/math&gt;

&lt;math display=&quot;inline&quot;&gt;(r, f)&lt;/math&gt; takes each stratum of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; transversally to each stratum of each &lt;math display=&quot;inline&quot;&gt;Y_t&lt;/math&gt;. &lt;math display=&quot;inline&quot;&gt;(f \circ \pi, f)^{-1}(P_a) = f^{-1}[-\epsilon, \infty)&lt;/math&gt; is transverse to each stratum of &lt;math display=&quot;inline&quot;&gt;Y_t \cap Z&lt;/math&gt;. Therefore, there is a homeomorphism between&lt;ref&gt;Goresky and MacPherson 1988, pp. 107.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;Z(D_1) = Z \cap (f \circ \pi, f)^{-1}(P_a) \cap (r, f)^{-1}(P_b(0))&lt;/math&gt;

and

&lt;math display=&quot;block&quot;&gt;Z(D_1) = Z \cap (f \circ \pi, f)^{-1}(P_a) \cap (r, f)^{-1}(P_b(1)).&lt;/math&gt;

To go from D_2 to D_3 we find the characteristic covectors of &lt;math display=&quot;inline&quot;&gt;(f\pi, f): V \to \R^2&lt;/math&gt; where &lt;math display=&quot;inline&quot;&gt;V = (r, f)^{-1}(P_b(1))&lt;/math&gt;. We stratify &lt;math display=&quot;inline&quot;&gt;P_b(1)&lt;/math&gt; by its interior &lt;math display=&quot;inline&quot;&gt;P&lt;/math&gt; and boundary &lt;math display=&quot;inline&quot;&gt;\partial P&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 107.&lt;/ref&gt;

The strata of &lt;math display=&quot;inline&quot;&gt;V&lt;/math&gt; come in four types:
# &lt;math display=&quot;inline&quot;&gt;(r, f)^{-1}(P) \cap X&lt;/math&gt;
# &lt;math display=&quot;inline&quot;&gt;(r, f)^{-1}(P) \cap Y&lt;/math&gt;
# &lt;math display=&quot;inline&quot;&gt;(r, f)^{-1}(\partial P) \cap X&lt;/math&gt;
# &lt;math display=&quot;inline&quot;&gt;(r, f)^{-1}(\partial P) \cap Y&lt;/math&gt;
where &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; is the strata that contains the critical point and &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; is any other strata such that &lt;math display=&quot;inline&quot;&gt;Y &gt; X&lt;/math&gt;.

All characteristic covectors are of the form &lt;math display=&quot;inline&quot;&gt;\lambda = (u, v, adu + bdv) \in T^*\R^2&lt;/math&gt;.

For strata 1 and 3, the image of &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; under &lt;math display=&quot;inline&quot;&gt;(f\pi, f)&lt;/math&gt; is the diagonal &lt;math display=&quot;inline&quot;&gt;f\pi = f&lt;/math&gt; (dotted outline). Therefore, the characteristic covectors of any point &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt; in &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; are either where &lt;math display=&quot;inline&quot;&gt;z = p&lt;/math&gt;, in which case the covector is zero(?), or where &lt;math display=&quot;inline&quot;&gt;z \neq p&lt;/math&gt;, in which case &lt;math display=&quot;inline&quot;&gt;u = v&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;a = b&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 107-108.&lt;/ref&gt;

For strata 2, being that the critical point is isolated and non-degenerate, which means it, and any neighbourhood, is not zero on any limit of tangent spaces in strata &lt;math display=&quot;inline&quot;&gt;Y &gt; X&lt;/math&gt;. Therefore, &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;f\pi&lt;/math&gt; are linearly independent.&lt;ref&gt;Goresky and MacPherson 1988, pp. 84.&lt;/ref&gt; Unless &lt;math display=&quot;inline&quot;&gt;\pi(z) = p&lt;/math&gt;, in which case &lt;math display=&quot;inline&quot;&gt;d(f\pi)(z) = f\pi(z) = 0&lt;/math&gt;, so they are covectors where &lt;math display=&quot;inline&quot;&gt;u = 0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;b = 0&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 108.&lt;/ref&gt;

For strata 4, we can use implicit function theorem to generate local coordinates &lt;math display=&quot;inline&quot;&gt;y_1, \cdots y_{r-s-1}&lt;/math&gt; in &lt;math display=&quot;inline&quot;&gt;Y &gt; X&lt;/math&gt; and define the Riemannian metric &lt;math display=&quot;inline&quot;&gt;r(z) = r\pi(z) + (f(z) - f\pi(z))^2 + g(y)&lt;/math&gt; for some &lt;math display=&quot;inline&quot;&gt;g&lt;/math&gt; depending only on &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt;.

There are no characteristic covectors in &lt;math display=&quot;inline&quot;&gt;|u| \leq \epsilon&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;|v| &lt; \epsilon&lt;/math&gt;. By [lemma 6.7 and 6.8 and 8.1(d)] &lt;math display=&quot;inline&quot;&gt;df&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;df\pi&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;dr&lt;/math&gt; are linearly independent in this region.&lt;ref&gt;Goresky and MacPherson 1988, pp. 109.&lt;/ref&gt; Given &lt;math display=&quot;inline&quot;&gt;|f| \leq \epsilon&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;|f\pi| \leq \epsilon&lt;/math&gt;, a fringed set &lt;math display=&quot;inline&quot;&gt;A^\flat_4&lt;/math&gt; of type &lt;math display=&quot;inline&quot;&gt;0 &lt; \epsilon \ll \delta&lt;/math&gt; and assume that &lt;math display=&quot;inline&quot;&gt;\pi \neq p&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;z \notin X&lt;/math&gt; then &lt;math display=&quot;inline&quot;&gt;(r(z), f(z)) \in A^\flat_4&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;(r(z), f\pi(z)) \in A^\flat_4&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 87.&lt;/ref&gt;

Outside of these points, the slope of &lt;math display=&quot;inline&quot;&gt;\ker(\lambda)&lt;/math&gt; for any characteristic covector &lt;math display=&quot;inline&quot;&gt;\lambda&lt;/math&gt; is

&lt;math display=&quot;block&quot;&gt;\frac{-a}{b} = \frac{f(z) - f\pi(z) - M}{\frac{\alpha}{\beta} + (f(z) - f\pi(z))}&lt;/math&gt;

for &lt;math display=&quot;inline&quot;&gt;\alpha df + \beta dr = 0&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 108-109.&lt;/ref&gt;

== Morse theory ==

Steps(?)
* Explain topology
* Every point of a stratum is locally like a product structure (proved by Thom's Isotopy Lemma) [GM pp. 41-42]
** Including those around critical points, which are the product of normal and tangential Morse data (these are our quasi-local cycles?)
* Thom's Isotopy Lemma proves a strong deformation retraction (which only stops at critical points) [PWM pp. 541-542]

=== Homotopy ===

We want to replace our domain of convergence &lt;math display=&quot;inline&quot;&gt;M&lt;/math&gt;, which is the complement of our singular variety &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt;, with an &quot;equivalent&quot; space &lt;math display=&quot;inline&quot;&gt;M'&lt;/math&gt; which has better understood properties. We say &quot;equivalent&quot; because there are several different things we could mean by &quot;equivalent&quot; in this context. The equivalence we are referring to in this section is called '''homotopy'''.

Imagine two subspaces &lt;math display=&quot;inline&quot;&gt;\gamma_0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\gamma_1&lt;/math&gt; of a space &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; which are defined respectively by smooth functions &lt;math display=&quot;inline&quot;&gt;f, g: X \to Y&lt;/math&gt;. If there exists a smooth function &lt;math display=&quot;inline&quot;&gt;h_s: X \times [0, 1] \to Y&lt;/math&gt;, called a homotopy, such that &lt;math display=&quot;inline&quot;&gt;h_0 = f&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;h_1 = g&lt;/math&gt; and for any &lt;math display=&quot;inline&quot;&gt;\epsilon &gt; 0&lt;/math&gt; there exists a &lt;math display=&quot;inline&quot;&gt;\delta_a&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\delta_b&lt;/math&gt; such that when &lt;math display=&quot;inline&quot;&gt;|s - s_0| &lt; \delta_a&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;|x - x_0| &lt; \delta_b&lt;/math&gt; we have &lt;math display=&quot;inline&quot;&gt;|h_s(x) - h_{s_0}(x_0)| &lt; \epsilon&lt;/math&gt;, then we say &lt;math display=&quot;inline&quot;&gt;\gamma_0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\gamma_1&lt;/math&gt; are '''homotopic'''.&lt;ref&gt;Henle 1979, pp. 251-252.&lt;/ref&gt;

Below is an example where &lt;math display=&quot;inline&quot;&gt;\gamma_0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\gamma_1&lt;/math&gt; are one-dimensional curves and &lt;math display=&quot;inline&quot;&gt;H(t, s) = h_s(t)&lt;/math&gt;.

[[File:Homotopy_curves.png|300px]]

In [[#Homotopy_equivalence|Appendix A]], we formally prove that we can construct an equivalent space &lt;math display=&quot;inline&quot;&gt;M'&lt;/math&gt;. We provide only an example to give some intuition before describing how to construct the space &lt;math display=&quot;inline&quot;&gt;M'&lt;/math&gt; in terms of local cycles around critical points.

=== Motivating example ===

Imagine a torus and a height function which is just the z value of the point.

[[File:3D-Leveltorus.png|200px]]

It has four critical points: two at the top and bottom of the outer circle (&lt;math display=&quot;inline&quot;&gt;p_1, p_4&lt;/math&gt;) and two at the top and bottom of the inner circle (&lt;math display=&quot;inline&quot;&gt;p_2, p_3&lt;/math&gt;).

[picture]

When the height is between the &lt;math display=&quot;inline&quot;&gt;p_1&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;p_2&lt;/math&gt;, the space is a two-cell, which can be retracted to a point.

[picture]

When the height is between &lt;math display=&quot;inline&quot;&gt;p_2&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;p_3&lt;/math&gt;, the space is a cylinder, which can be retracted to a two-cell with a one-cell attached.

[[File:3D-Cylinder_and_disk_with_handle.png|200px]]

When the height is between &lt;math display=&quot;inline&quot;&gt;p_3&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;p_4&lt;/math&gt;, the space is a torus with a disc removed, which can be retracted to a cylinder with a one-cell attached.

[[File:3D-Cylinder_with_handle_and_torus_with_hole.png|200px]]

When the height is greater than &lt;math display=&quot;inline&quot;&gt;p_4&lt;/math&gt;, then the full torus is constructed by attaching a two-cell.

[Explain in terms of Morse data and Morse index?]

=== Morse data and quasi-local cycles ===

As in the above example, we start at the &quot;bottom&quot; of &lt;math display=&quot;inline&quot;&gt;M&lt;/math&gt; and build upwards until just before we reach our first critical point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.

;Smooth points
:This is a tube around a &lt;math display=&quot;inline&quot;&gt;(d-1)&lt;/math&gt;-chain &lt;math display=&quot;inline&quot;&gt;\gamma&lt;/math&gt; where the height function &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; is maximised at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 223.&lt;/ref&gt;
:For example, if &lt;math display=&quot;inline&quot;&gt;F(x, y) = \frac{1}{1 - x - y}&lt;/math&gt; then &lt;math display=&quot;inline&quot;&gt;\lambda = 1&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;B^\lambda&lt;/math&gt; is an arc reaching its highest point at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.
:The normal plane &lt;math display=&quot;inline&quot;&gt;N&lt;/math&gt; at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; is a plane orthogonal to &lt;math display=&quot;inline&quot;&gt;B^1&lt;/math&gt;(?).
:Its normal link &lt;math display=&quot;inline&quot;&gt;L(S)&lt;/math&gt; is a circle with two points missing where it intersects &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt;.
:We make our quasi-local cycle out of the product of the arc and circle joined to &lt;math display=&quot;inline&quot;&gt;M_-&lt;/math&gt; at points below &lt;math display=&quot;inline&quot;&gt;M_-&lt;/math&gt;.
:With the exception of degenerate points, such as monkey saddles...&lt;ref&gt;e.g. Pemantle, Wilson and Melczer 2024, pp. 211.&lt;/ref&gt;

;Transverse multiple points
:This is the product of a &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;-torus and a &lt;math display=&quot;inline&quot;&gt;(d-k)&lt;/math&gt;-chain &lt;math display=&quot;inline&quot;&gt;\gamma&lt;/math&gt;. The torus is the product of circles about &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; in the complex normal space to each strata which intersects &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;. The chain &lt;math display=&quot;inline&quot;&gt;\gamma&lt;/math&gt; is supported in the stratum which is the common intersection of the varieties defined by the factors vanishing at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;, and achieves its maximum height at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 223-224.&lt;/ref&gt;

;Arrangement multiple point
:This is the product of a &lt;math display=&quot;inline&quot;&gt;(d-k)&lt;/math&gt;-chain &lt;math display=&quot;inline&quot;&gt;\gamma&lt;/math&gt; and several &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;-tori, one for each pair of sheets which intersect transversely, where the torus is the product of circles about &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; in each sheet.&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 226.&lt;/ref&gt;

;Cone point
:A cone point is zero-dimensional so there is no &lt;math display=&quot;inline&quot;&gt;\gamma&lt;/math&gt;, just a &lt;math display=&quot;inline&quot;&gt;d&lt;/math&gt;-torus about &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 227.&lt;/ref&gt;

== Notes ==
{{Reflist}}

== References ==
* {{cite book | last1=Goresky | first1=Mark | last2=MacPherson | first2=Robert | title=Stratified Morse Theory | publisher=Springer-Verlag | year=1988 | url=https://www.math.ias.edu/~goresky/pdf/SMT.djvu }}
* {{cite book | last=Henle | first1=Michael | title=A Combinatorial Introduction to Topology | publisher=Dover Publications Inc. New York | year=1979 }}
* {{citation | last=Mather | first=John | title=Notes on Topological Stability | year=2012 | journal=Bulletin of the American Mathematical Society | volume=49 | number=4 | pages=475-506 | url=https://www.ams.org/journals/bull/2012-49-04/S0273-0979-2012-01383-6/S0273-0979-2012-01383-6.pdf }}.
* {{cite book | last1=Pemantle | first1=Robin | last2=Wilson | first2=Mark C. | last3=Melczer | first3=Stephen | title=Analytic Combinatorics in Several Variables | publisher=Cambridge University Press | year=2024 | edition=2nd | url=https://acsvproject.com/PemantleWilsonMelczer23.pdf }}</text>
      <sha1>qhgh7ix5ualueutg35v7hb616nlhr2v</sha1>
    </revision>
    <revision>
      <id>4676708</id>
      <parentid>4676707</parentid>
      <timestamp>2026-10-18T08:46:02Z</timestamp>
      <contributor>
        <username>Dom walden</username>
        <id>3209423</id>
      </contributor>
      <comment>/* Fringed sets */</comment>
      <origin>4676708</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="60727" sha1="581208emj5l8i1pdzxxjisazmebvutq" xml:space="preserve">== Introduction ==

Morse theory tells us that the topology of M only changes at its critical points.

The &quot;Morse data&quot; tells us the topology at each critical point.

Attaching this Morse data together gives us a space which is homopotically eqivalent to M.

This space is a &quot;cell complex&quot;, which has an easy to calculate homology.

Theorem: Our domain of convergence is homotopic to a cell complex of dimension at most &lt;math display=&quot;inline&quot;&gt;2n - d - 1&lt;/math&gt;.&lt;ref&gt;This is theorem D.23 in Pemantle, Wilson and Melczer 2024, pp. 546. Also theorem in section 1.2*/5.2* in SMT pp. 200.&lt;/ref&gt;

Proof:
# &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; is our entire domain, &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt; our variety
# Project our entire domain to complex projective space &lt;math display=&quot;inline&quot;&gt;Z = \pi(X) \subset \C\mathbb{P}^n - H&lt;/math&gt; [define H]
# Define a linear subspace &lt;math display=&quot;inline&quot;&gt;G \subset \C\mathbb{P}^n&lt;/math&gt; of dimension &lt;math display=&quot;inline&quot;&gt;d - 1&lt;/math&gt;
# Define a Morse function on &lt;math display=&quot;inline&quot;&gt;f: \C\mathbb{P}^n \to \R&lt;/math&gt; which approximates the distance from &lt;math display=&quot;inline&quot;&gt;G&lt;/math&gt; and such that &lt;math display=&quot;inline&quot;&gt;f^{-1}(0) = G&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;f^{-1}(1) = H&lt;/math&gt;
# We &quot;build&quot; &lt;math display=&quot;inline&quot;&gt;X - \mathcal{V}&lt;/math&gt; from &lt;math display=&quot;inline&quot;&gt;\pi^{-1}(G \cap Z) \cap (X - \mathcal{V})&lt;/math&gt; by attaching CW complexes at critical points which are of at most dimension &lt;math display=&quot;inline&quot;&gt;2n - d - 1&lt;/math&gt;
# At a critical point, the normal Morse data is &lt;math display=&quot;inline&quot;&gt;(J, K) = \coprod_x (J_x, K_x)&lt;/math&gt; and the relative complex link is &lt;math display=&quot;inline&quot;&gt;\mathcal{L}^\pi = \coprod_x \mathcal{L}_x&lt;/math&gt;
# We show that the quotient &lt;math display=&quot;inline&quot;&gt;J_x/K_x&lt;/math&gt; is homotopic to a CW complex of dimension &lt;math display=&quot;inline&quot;&gt;\leq 2n - d - 1&lt;/math&gt;
# The neighbourhood of &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; in &lt;math display=&quot;inline&quot;&gt;J_x&lt;/math&gt; is homeomorphic to the cone in &lt;math display=&quot;inline&quot;&gt;L_x(X - \mathcal{V})&lt;/math&gt;, and removing the point &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; increases the homotopy dimension to at most the homotopy dimension of &lt;math display=&quot;inline&quot;&gt;L_x&lt;/math&gt;
# &lt;math display=&quot;inline&quot;&gt;(J_x \cup \{x\}, K_x)&lt;/math&gt; is homotopic to &lt;math display=&quot;inline&quot;&gt;(\text{cone}(\mathcal{L}_x), \mathcal{L}_x)&lt;/math&gt;
# &lt;math display=&quot;inline&quot;&gt;\mathcal{L}_x&lt;/math&gt; is homotopic to a CW complex of dimension at most &lt;math display=&quot;inline&quot;&gt;2n - d - 1&lt;/math&gt;
# The tangential Morse data at the critical point is homotopic to the pair &lt;math display=&quot;inline&quot;&gt;(D^\lambda, \partial D^\lambda)&lt;/math&gt;
# Therefore, at each critical point a space has been added homotopic to a CW complex of dimension at most &lt;math display=&quot;inline&quot;&gt;2n - d - 1&lt;/math&gt;.

Theorem: If &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; is the complement in &lt;math display=&quot;inline&quot;&gt;\C^n&lt;/math&gt; of a complex variety &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt; of dimension &lt;math display=&quot;inline&quot;&gt;d&lt;/math&gt; then &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; is homotopic to a CW complex of dimension at most &lt;math display=&quot;inline&quot;&gt;2n - d - 1&lt;/math&gt;.&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 546.&lt;/ref&gt;

Proof:
# We build &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; by attaching cells of dimension at most &lt;math display=&quot;inline&quot;&gt;2n - d - 1&lt;/math&gt; at each critical point.
## Prove that we can do this without changing the homotopy(?)
## We use Thom's Isotopy Lemma to prove that there is a strong deformation retraction, stopping only at critical points.
# Prove these cells are a product of the normal and tangential Morse data.
## Normal data: &lt;math display=&quot;inline&quot;&gt;(\mathcal{L}(S), \partial \mathcal{L}(S)) \times (D^1, \partial D^1)&lt;/math&gt; [GM pp. 18]
## Tangential data: &lt;math display=&quot;inline&quot;&gt;(B_\delta \cap f^{-1}[v - \epsilon, v + \epsilon], B_\delta \cap f^{-1}(v - \epsilon))&lt;/math&gt; for &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; restricted to &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; (or &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt;?) [GM pp. 63-64]
# If &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt; is the dimension of the strata, then
## If &lt;math display=&quot;inline&quot;&gt;k = d&lt;/math&gt; then it is a smooth point and the cell is the product of &lt;math display=&quot;inline&quot;&gt;S^{2(n-d)-1}&lt;/math&gt; and the tangential data is dimension at most &lt;math display=&quot;inline&quot;&gt;d&lt;/math&gt;.
## If &lt;math display=&quot;inline&quot;&gt;k &lt; d&lt;/math&gt;, ...

&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 547.&lt;/ref&gt;

== Example in one dimension ==

Domain with singularities v_1, v_2, ..., v_i

Define our height function f...

Start with our entire domain X

Reduce from X to X_i+ by using Thom's Isotopy lemma to do a strong deformation retract

== Thom's isotopy lemma ==

We present a modified version of Thom's (first) isotopy lemma, less general than the original but more obviously relevant to our situation.

Theorem: Suppose &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; is a closed subset of a smooth manifold &lt;math display=&quot;inline&quot;&gt;M&lt;/math&gt; which admits a Whitney stratification and &lt;math display=&quot;inline&quot;&gt;h : M \to \R&lt;/math&gt; is a proper Morse function which has no critical values on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;. Then, the level sets of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; are homeomorphic by a homeomorphism that preserves the strata of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;.&lt;ref&gt;For various versions of the full statement of the theorem, see Mather 2012, pp. 499, Goresky and MacPherson 1988, pp. 41, or Pemantle, Wilson and Melczer 2024, pp. 541.&lt;/ref&gt;

Proof:
# Construct control data for &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; compatible with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;.
## [Prop 7.1] If &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; is smooth on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; and is a submersion for each strata then there exists a family of control data for &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; compatible with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 488.&lt;/ref&gt;
# This makes &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; an abstract stratified set and &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; a controlled submersion.
# A controlled submersion has, for any smooth vector field on &lt;math display=&quot;inline&quot;&gt;\R&lt;/math&gt;, a controlled vector field on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; (a &quot;lift&quot;?)&lt;ref&gt;Mather 2012, pp. 493.&lt;/ref&gt;
# A controlled vector field has a unique one-parameter family of homeomorphisms of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; which commute with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 496.&lt;/ref&gt;
# This makes &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; a locally trivial fibration. [Prop 10.2]&lt;ref&gt;Mather 2012, pp. 499.&lt;/ref&gt;

Control data:

A system of '''control data''' for &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; consists of, for each stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;,
* a '''tubular neighbourhood''' &lt;math display=&quot;inline&quot;&gt;T_X&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt;
* a '''tubular projection function''' &lt;math display=&quot;inline&quot;&gt;\pi_X: T_X \to X&lt;/math&gt;, and
* a '''tubular distance function''' &lt;math display=&quot;inline&quot;&gt;\rho_X: T_X \to \R&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;\rho_X^{-1}(0) = X&lt;/math&gt;&lt;ref&gt;Goresky and MacPherson 1988, pp. 42.&lt;/ref&gt;

[illustration]

such that if &lt;math display=&quot;inline&quot;&gt;X &lt; Y&lt;/math&gt; are strata in &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;, then

&lt;math display=&quot;block&quot;&gt;\pi_X \pi_Y(m) = \pi_X(m),&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;\rho_X \pi_Y(m) = \rho_X(m)&lt;/math&gt;

for all &lt;math display=&quot;inline&quot;&gt;m \in |T_X| \cap |T_Y|&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;\pi_Y(m) \in |T_X|&lt;/math&gt;.

If, for all strata &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; and all &lt;math display=&quot;inline&quot;&gt;m \in |T_X|&lt;/math&gt;, we have &lt;math display=&quot;inline&quot;&gt;h \pi_X(m) = h(m)&lt;/math&gt;, then this control data will be said to be compatible with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 488.&lt;/ref&gt;

We prove that if &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; is smooth on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; and is a submersion for each strata then there exists a family of control data for &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; compatible with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 488, prop 7.1.&lt;/ref&gt;

Let &lt;math display=&quot;inline&quot;&gt;Z_k&lt;/math&gt; be the union of strata of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; of dimension less than &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;. We prove by induction on &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;.

To construct the tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T_X&lt;/math&gt; of a stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of dimension less than &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;. For &lt;math display=&quot;inline&quot;&gt;l \leq k&lt;/math&gt;, let &lt;math display=&quot;inline&quot;&gt;U_l&lt;/math&gt; denote the union of all &lt;math display=&quot;inline&quot;&gt;|T_Y|&lt;/math&gt; for &lt;math display=&quot;inline&quot;&gt;Y &lt; X&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\dim Y \geq l&lt;/math&gt;. Let &lt;math display=&quot;inline&quot;&gt;X_l = U_l \cap X&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 489.&lt;/ref&gt;

For &lt;math display=&quot;inline&quot;&gt;l = k&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;X_k = \empty&lt;/math&gt;. Assume by induction that &lt;math display=&quot;inline&quot;&gt;T_{l+1}&lt;/math&gt; has been constructed and that if &lt;math display=&quot;inline&quot;&gt;Y &lt; X&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;\dim Y \geq l + 1&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;m \in |T_{l+1}| \cap |T_Y|&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi_{l+1}(m) \in |T_Y|&lt;/math&gt; (&lt;math display=&quot;inline&quot;&gt;\pi_{l+1} = \pi_{T_{l+1}}&lt;/math&gt;) then&lt;ref&gt;Mather 2012, pp. 489-490.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;\rho_Y \pi_{l+1}(m) = \rho_Y(m),&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;\pi_Y \pi_{l+1}(m) = \pi_Y(m).&lt;/math&gt;

We wish to construct a tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T_{X,Y}&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;|T_Y| \cap X&lt;/math&gt; whose restriction to &lt;math display=&quot;inline&quot;&gt;|T_Y| \cap X_{l+1}&lt;/math&gt; is isomorphic to the restriction of &lt;math display=&quot;inline&quot;&gt;T_{l+1}&lt;/math&gt; such that if &lt;math display=&quot;inline&quot;&gt;m \in |T_{X,Y}| \cap |T_Y|&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi_{X,Y}(m) \in |T_Y|&lt;/math&gt; (&lt;math display=&quot;inline&quot;&gt;\pi_{X,Y} = \pi_{T_{X,Y}}&lt;/math&gt;) then

&lt;math display=&quot;block&quot;&gt;\rho_Y \pi_{X,Y}(m) = \rho_Y(m),&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;\pi_Y \pi_{X,Y}(m) = \pi_Y(m).&lt;/math&gt;

By shrinking &lt;math display=&quot;inline&quot;&gt;|T_Y|&lt;/math&gt; if necessary, this relation is already satisfied if &lt;math display=&quot;inline&quot;&gt;m \in |T_{l+1}| \cap |T_Y|&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi_{l+1}(m) \in |T_Y|&lt;/math&gt; with &lt;math display=&quot;inline&quot;&gt;T_{l+1}&lt;/math&gt; in place of &lt;math display=&quot;inline&quot;&gt;T_{X,Y}&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi_{l+1}&lt;/math&gt; in place of &lt;math display=&quot;inline&quot;&gt;\pi_{X,Y}&lt;/math&gt;. By the definition, if &lt;math display=&quot;inline&quot;&gt;m \in |T_{l+1}|&lt;/math&gt; then there exists &lt;math display=&quot;inline&quot;&gt;Z &lt; X&lt;/math&gt; with &lt;math display=&quot;inline&quot;&gt;\dim Z &gt; l&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;m \in |T_Z|&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi_{l+1}(m) \in |T_Z|&lt;/math&gt;. We have that &lt;math display=&quot;inline&quot;&gt;\pi_{l+1}(m) \in |T_Y| \cap |T_Z|&lt;/math&gt; and therefore &lt;math display=&quot;inline&quot;&gt;Y &lt; Z&lt;/math&gt;. Therefore&lt;ref&gt;Mather 2012, pp. 490.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;\rho_Y \pi_{l+1}(m) = \rho_Y \pi_Z \pi_{l+1}(m) = \rho_Y \pi_Z(m) = \rho_Y(m),&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;\pi_Y \pi_{l+1}(m) = \pi_Y \pi_Z \pi_{l+1}(m) = \pi_Y \pi_Z(m) = \pi_Y(m).&lt;/math&gt;

We can prove that, by shrinking &lt;math display=&quot;inline&quot;&gt;|T_Y|&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;(\rho_Y, \pi_Y): |T_Y| \cap X \to \R \times Y&lt;/math&gt; is a submersion [prop 7.3?] and that &lt;math display=&quot;inline&quot;&gt;T_{X,Y}&lt;/math&gt; is compatible with &lt;math display=&quot;inline&quot;&gt;(\rho_Y, \pi_Y): |T_Y| \cap X_{l+1} \to \R \times Y&lt;/math&gt;, i.e. &lt;math display=&quot;inline&quot;&gt;(\rho_Y, \pi_Y) \pi_{X,Y}(m) = (\rho_Y, \pi_Y)(m)&lt;/math&gt;(?).

To prove it is a submersion, for the tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T = (E, \epsilon, \psi)&lt;/math&gt; there exists a smooth positive function &lt;math display=&quot;inline&quot;&gt;\epsilon'&lt;/math&gt; such that

&lt;math display=&quot;block&quot;&gt;(\rho_T, \pi_T): Y \cap |T|_{\epsilon'}^0 \to \R \times X,&lt;/math&gt;

where &lt;math display=&quot;inline&quot;&gt;|T|_{\epsilon'}^0 = \psi(B_\epsilon \cap B_{\epsilon'})&lt;/math&gt;, is a submersion. If &lt;math display=&quot;inline&quot;&gt;\Sigma&lt;/math&gt; is the set &lt;math display=&quot;inline&quot;&gt;y \in |T|&lt;/math&gt; such that the rank of

&lt;math display=&quot;block&quot;&gt;(\rho_T, \pi_T): T \cap |T| \to \R \times X&lt;/math&gt;

at &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt; is less than &lt;math display=&quot;inline&quot;&gt;\dim(\R \times X)&lt;/math&gt;. We need to prove that for any &lt;math display=&quot;inline&quot;&gt;x \in X&lt;/math&gt; there exists a neighbourhood of &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; which does not intersect with &lt;math display=&quot;inline&quot;&gt;\Sigma&lt;/math&gt;, i.e. the map is not a submersion in this neighbourhood. It follows from [lemma 7.2] that it is enough to prove for &lt;math display=&quot;inline&quot;&gt;M = \R^m&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;X = \R^{m-c} \times 0_c&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;T&lt;/math&gt; is the '''standard tubular neighbourhood'''.&lt;ref&gt;Mather 2012, pp. 489.&lt;/ref&gt;

By standard tubular neighbourhood, we mean the trivial bundle with base &lt;math display=&quot;inline&quot;&gt;\R^{m-c}&lt;/math&gt; and fibre &lt;math display=&quot;inline&quot;&gt;\R^c&lt;/math&gt; where &lt;math display=&quot;inline&quot;&gt;\pi: \R^m \to \R^{m-c}&lt;/math&gt;...&lt;ref&gt;Mather 2012, pp. 488.&lt;/ref&gt;

For &lt;math display=&quot;inline&quot;&gt;y \in |T| - \R^{m-c}&lt;/math&gt;, the kernal of the differential of &lt;math display=&quot;inline&quot;&gt;(\pi_T, \rho_T)&lt;/math&gt; at &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt; is the orthogonal complement of &lt;math display=&quot;inline&quot;&gt;(\R^{m-c} \times 0_c) \oplus \stackrel{\frown}{y \pi_T(y)}&lt;/math&gt; in &lt;math display=&quot;inline&quot;&gt;\R^m&lt;/math&gt;. By the Whitney conditions, we have that for &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt; near &lt;math display=&quot;inline&quot;&gt;\R^{m-c}&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;(\R^{m-c} \times 0_c) \oplus \stackrel{\frown}{y \pi_T(y)}&lt;/math&gt; is close to the set of &lt;math display=&quot;inline&quot;&gt;m - c + 1&lt;/math&gt; planes in &lt;math display=&quot;inline&quot;&gt;m-&lt;/math&gt;space to an &lt;math display=&quot;inline&quot;&gt;m - c + 1&lt;/math&gt; plane in &lt;math display=&quot;inline&quot;&gt;TY_y&lt;/math&gt;. Therefore, for &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt; near enough to &lt;math display=&quot;inline&quot;&gt;\R^{m-c}&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;TY_y&lt;/math&gt; is transverse to the kernal of the differential of &lt;math display=&quot;inline&quot;&gt;(\pi_T, \rho_T)&lt;/math&gt; and, therefore, is a submersion when restricted to &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 489.&lt;/ref&gt;

To prove that &lt;math display=&quot;inline&quot;&gt;T_{X,Y}&lt;/math&gt; is compatible with &lt;math display=&quot;inline&quot;&gt;(\rho_Y, \pi_Y): |T_Y| \cap X_{l+1} \to \R \times Y&lt;/math&gt;...&lt;ref&gt;Mather 2012, pp. 490.&lt;/ref&gt;

Therefore, there exists a tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T_0&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;X_0&lt;/math&gt; satisfying

&lt;math display=&quot;block&quot;&gt;\rho_Y \pi_0(m) = \rho_Y(m),&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;\pi_Y \pi_0(m) = \pi_Y(m).&lt;/math&gt;

From this we can prove that &lt;math display=&quot;inline&quot;&gt;T_0&lt;/math&gt; is compatible with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;. Replacing &lt;math display=&quot;inline&quot;&gt;T_0&lt;/math&gt; with a smaller tubular neighbourhood if necessary we can assume &lt;math display=&quot;inline&quot;&gt;m \in |T_0|&lt;/math&gt; such that for some &lt;math display=&quot;inline&quot;&gt;Y &lt; X&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;m \in |T_Y|&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi_0(m) \in |T_Y|&lt;/math&gt;, then&lt;ref&gt;Mather 2012, pp. 490.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;h \pi_0(m) = h \pi_Y \pi_0(m) = h \pi_Y(m) = h(m).&lt;/math&gt;

By the generalised tubular neighourhood theorem [prop 7.2?], we can replace &lt;math display=&quot;inline&quot;&gt;T_0&lt;/math&gt; with a tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; compatible with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;. This completes the construction of &lt;math display=&quot;inline&quot;&gt;T_X&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 491.&lt;/ref&gt;

This makes &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; an '''abstract stratified set''' with axioms...&lt;ref&gt;Mather 2012, pp. 491-492.&lt;/ref&gt;

This also makes &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; a '''controlled submersion''' because
# &lt;math display=&quot;inline&quot;&gt;h|X: X \to \R&lt;/math&gt; is a smooth submersion on each strata &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;, and
# for each stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; there is a tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T'_X&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;h(v) = h \pi_X(v)&lt;/math&gt; for all &lt;math display=&quot;inline&quot;&gt;v \in T'_X&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 493.&lt;/ref&gt;

The core of this is the concept of a '''vector field'''. A vector field is a function which assigns, for each point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; in a space, a '''vector''', which can be represented by an arrow whose tail starts at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.&lt;ref&gt;Henle 1979, pp. 33.&lt;/ref&gt;

[picture]

Imagine we have a vector field &lt;math display=&quot;inline&quot;&gt;v(x)&lt;/math&gt; defined in a space and draw a line through our space. At each point along this line the vector field assigns a vector. If we move each point in this line along the arrow defined by this vector in the direction of the arrow head. This &quot;flows&quot; the entire line along the vectors.

[picture]

We define a '''stratified vector field''' &lt;math display=&quot;inline&quot;&gt;\eta&lt;/math&gt; on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; to be a family of smooth vector fields &lt;math display=&quot;inline&quot;&gt;\eta_X&lt;/math&gt;, one for each strata &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 493.&lt;/ref&gt;

We define a '''controlled vector field''' &lt;math display=&quot;inline&quot;&gt;\eta&lt;/math&gt; on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; to be a stratified vector field such that for any strata &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; there exists a tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T'_Y&lt;/math&gt; such that for any &lt;math display=&quot;inline&quot;&gt;X &gt; Y&lt;/math&gt; and any &lt;math display=&quot;inline&quot;&gt;v \in T'_X \cap X&lt;/math&gt;&lt;ref&gt;Mather 2012, pp. 493.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;\eta_X \rho_{Y,X}(v) = 0,&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;(\pi_{Y,X})_* \eta_X(v) = \eta_Y (\pi_{Y,X}(v)).&lt;/math&gt;

We prove that if &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; is a controlled submersion then, for any smooth vector field &lt;math display=&quot;inline&quot;&gt;\zeta&lt;/math&gt; on &lt;math display=&quot;inline&quot;&gt;\R&lt;/math&gt; there is a controlled vector field &lt;math display=&quot;inline&quot;&gt;\eta&lt;/math&gt; on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;h_* \eta(v) = \zeta(h(v))&lt;/math&gt; for all &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 493.&lt;/ref&gt;

Proceeding by induction on the maximum dimension of the strata of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;, we define &lt;math display=&quot;inline&quot;&gt;Z_k&lt;/math&gt; to be the union of strata of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; of dimension at most &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;. The tubular neighbourhood of &lt;math display=&quot;inline&quot;&gt;Z_k&lt;/math&gt; is the intersection of the tubular neighbourhoods of each strata in &lt;math display=&quot;inline&quot;&gt;Z_k&lt;/math&gt; with &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;. The projection and distance functions are the restrictions of the respective functions of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;.

It is trivially true when the maximum dimension of strata in &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; is zero. Assume it is true for &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt; and construct each &lt;math display=&quot;inline&quot;&gt;\eta_X&lt;/math&gt; separately for each stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of dimension &lt;math display=&quot;inline&quot;&gt;k + 1&lt;/math&gt;.

By the assumption that we have controlled vector fields for all strata &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; of dimension at most &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;, we have the two control conditions defined above for any &lt;math display=&quot;inline&quot;&gt;X &gt; Y&lt;/math&gt; and that there is a neighbourhood &lt;math display=&quot;inline&quot;&gt;T^1_Y&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;h(v) = h \pi_Y(v)&lt;/math&gt; for &lt;math display=&quot;inline&quot;&gt;v \in T^1_Y&lt;/math&gt;.

We want to prove that for all &lt;math display=&quot;inline&quot;&gt;Y &lt; X&lt;/math&gt;, the control conditions are satisfied for all &lt;math display=&quot;inline&quot;&gt;v \in T^2_Y&lt;/math&gt; and that &lt;math display=&quot;inline&quot;&gt;h_*\eta_X(v) = \zeta(v)&lt;/math&gt; for all &lt;math display=&quot;inline&quot;&gt;v \in X&lt;/math&gt;.

Take a point &lt;math display=&quot;inline&quot;&gt;x \in X&lt;/math&gt; and define the set &lt;math display=&quot;inline&quot;&gt;S_v&lt;/math&gt; of strata &lt;math display=&quot;inline&quot;&gt;Y &lt; X&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;v \in T^2_Y&lt;/math&gt;. &lt;math display=&quot;inline&quot;&gt;S_v&lt;/math&gt; is totally ordered since if &lt;math display=&quot;inline&quot;&gt;Y_1&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Y_2&lt;/math&gt; are not comparable then &lt;math display=&quot;inline&quot;&gt;T^2_{Y_1} \cap T^2_{Y_2} = \empty&lt;/math&gt;. Therefore, there is a largest member &lt;math display=&quot;inline&quot;&gt;Y = Y_v&lt;/math&gt;.

Assume the control conditions hold for &lt;math display=&quot;inline&quot;&gt;Y = Y_v&lt;/math&gt;. Then they hold for all &lt;math display=&quot;inline&quot;&gt;Y_i \in S_v&lt;/math&gt;. For, either &lt;math display=&quot;inline&quot;&gt;Y_i = Y&lt;/math&gt; or &lt;math display=&quot;inline&quot;&gt;Y_i &lt; Y&lt;/math&gt;. In the latter case, &lt;math display=&quot;inline&quot;&gt;\pi_Y(v) \in T^1_{Y_i}&lt;/math&gt; (by the choice of &lt;math display=&quot;inline&quot;&gt;T^2_Y&lt;/math&gt;'s [is this why?]. Then

&lt;math display=&quot;block&quot;&gt;\begin{align}
\eta_X(v) \rho_{Y_i,X}(v) &amp;= \eta_X \rho_{Y_i,Y} \pi_{Y,X}(v) \\
&amp;= (\pi_{Y,X})_* \eta_X(v) \rho_{Y_i,Y} \\
&amp;= \eta_Y(\pi_{Y,X}(v)) \rho_{Y_i,Y} \\
&amp;= 0
\end{align}&lt;/math&gt;

and

&lt;math display=&quot;block&quot;&gt;\begin{align}
(\pi_{Y_i,X})_* \eta_X(v) &amp;= (\pi_{Y_i,Y})_* (\pi_{Y,X})_* \eta_X(v) \\
&amp;= (\pi_{Y_i,Y})_* \eta_Y(v) (\pi_{Y,X}) \\
&amp;= \eta_{Y_i}(\pi_{Y_i,Y} \pi_{Y,X}(v)) \\
&amp;= \eta_{Y_i}(\pi_{Y_i,X}(v))
\end{align}&lt;/math&gt;

and, therefore, condition holds for all &lt;math display=&quot;inline&quot;&gt;Y_i \in S_v&lt;/math&gt;. Also,

&lt;math display=&quot;block&quot;&gt;\begin{align}
h_* \eta_X(v) &amp;= (h \circ \pi_{Y,X})_* \eta_X(v) \\
&amp;= h_* \eta_Y (\pi_{Y,X}(v)) \\
&amp;= \zeta(f(v))
\end{align}&lt;/math&gt;

and, therefore, the conclusion of the theorem holds at &lt;math display=&quot;inline&quot;&gt;v&lt;/math&gt;.

This shows we can construct &lt;math display=&quot;inline&quot;&gt;\eta_X&lt;/math&gt; satisfying the control conditions when &lt;math display=&quot;inline&quot;&gt;S_v&lt;/math&gt; is non-empty and satisfying the theorem when &lt;math display=&quot;inline&quot;&gt;S_v&lt;/math&gt; is empty. The set of vectors satisfying these conditions is convex in &lt;math display=&quot;inline&quot;&gt;TX_v&lt;/math&gt;, and so we construct &lt;math display=&quot;inline&quot;&gt;\eta_X&lt;/math&gt; globally via a partition of unity.&lt;ref&gt;Mather 2012, pp. 493-495.&lt;/ref&gt;

Finally, we prove that a controlled vector field has a unique one-parameter family of homeomorphisms of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; which commute with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;.&lt;ref&gt;Mather 2012, this combines Proposition 10.1 and Corollary 10.2 on pp. 496 and 497, respectively.&lt;/ref&gt;

For each stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;\eta_X&lt;/math&gt; generates a unique smooth local one-parameter group &lt;math display=&quot;inline&quot;&gt;(J_X, \alpha_X)&lt;/math&gt; of diffeomorphisms of &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; (by standard results of differential geometry), such that &lt;math display=&quot;inline&quot;&gt;\frac{d}{dt} \alpha(t, v)|_{t=0} = \eta_X(v)&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;J_X&lt;/math&gt; is an open subset of &lt;math display=&quot;inline&quot;&gt;\R \times Z&lt;/math&gt;, ...

If we define &lt;math display=&quot;inline&quot;&gt;(J, \alpha)&lt;/math&gt; by

&lt;math display=&quot;block&quot;&gt;J = \bigcup_{X \in S} J_X&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;\alpha = \bigcup_{X \in S} \alpha_X&lt;/math&gt;

we can prove that this is a local one-parameter family of homeomorphisms.&lt;ref&gt;Mather 2012, pp. 496.&lt;/ref&gt;

Firstly, it is clear that
# &lt;math display=&quot;inline&quot;&gt;0 \times Z \subseteq J&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\alpha(0, v) = v&lt;/math&gt; for all &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt;.
# If &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt; then &lt;math display=&quot;inline&quot;&gt;J_v = J \cap (\R \times v) \subseteq \R&lt;/math&gt; is an open interval &lt;math display=&quot;inline&quot;&gt;(a_v, b_v)&lt;/math&gt;, possibly infinite at one or both ends.
# If &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;t, s, t + s&lt;/math&gt; are in &lt;math display=&quot;inline&quot;&gt;(a_v, b_v)&lt;/math&gt; then &lt;math display=&quot;inline&quot;&gt;\alpha(t + s, v) = \alpha(t, \alpha(s, v))&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 495.&lt;/ref&gt;

Secondly, it is clear that &lt;math display=&quot;inline&quot;&gt;\eta&lt;/math&gt; generates &lt;math display=&quot;inline&quot;&gt;\alpha&lt;/math&gt; because
# Each stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; is invariant under &lt;math display=&quot;inline&quot;&gt;\alpha&lt;/math&gt;, i.e. &lt;math display=&quot;inline&quot;&gt;\alpha[J \cap (\R \times X)] \subseteq X&lt;/math&gt;.
# For each &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt;, the map &lt;math display=&quot;inline&quot;&gt;t \to \alpha(t, v)&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;(a_v, b_v)&lt;/math&gt; into the stratum which contains &lt;math display=&quot;inline&quot;&gt;v&lt;/math&gt; is &lt;math display=&quot;inline&quot;&gt;C^1&lt;/math&gt;.
# For any &lt;math display=&quot;inline&quot;&gt;(t, v) \in Z&lt;/math&gt;(?) we have &lt;math display=&quot;inline&quot;&gt;d/dt \alpha(t, v) = \eta(\alpha(t, v))&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 495.&lt;/ref&gt;

It is unique because each &lt;math display=&quot;inline&quot;&gt;(J_X, \alpha_X)&lt;/math&gt; is unique. We just need to prove that &lt;math display=&quot;inline&quot;&gt;J&lt;/math&gt; is open, &lt;math display=&quot;inline&quot;&gt;\alpha&lt;/math&gt; is continuous, and for any &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt; and any compact set &lt;math display=&quot;inline&quot;&gt;K \subseteq Z&lt;/math&gt; there exists &lt;math display=&quot;inline&quot;&gt;\epsilon &gt; 0&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;\alpha(t, v) \notin K&lt;/math&gt; if &lt;math display=&quot;inline&quot;&gt;t \in (a_v, a_v + \epsilon) \cup (b_v - \epsilon, b_v)&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 495.&lt;/ref&gt;

For the latter-most condition, if it did not hold then there exists...&lt;ref&gt;Mather 2012, pp. 496-497.&lt;/ref&gt;

We prove there is a homeomorphism &lt;math display=&quot;inline&quot;&gt;f: Z \to h^{-1}(0) \times \R&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;\pi \circ f = h&lt;/math&gt;, where &lt;math display=&quot;inline&quot;&gt;\pi: h^{-1}(0) \times \R \to \R&lt;/math&gt; is projection to the second factor.

For the coordinate vector field &lt;math display=&quot;inline&quot;&gt;\partial&lt;/math&gt; on &lt;math display=&quot;inline&quot;&gt;\R&lt;/math&gt;, by [prop 9.1] there is a controlled vector field &lt;math display=&quot;inline&quot;&gt;\tilde\partial&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;f_* \tilde\partial(v) = \partial(h(v))&lt;/math&gt; for &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt;. By [prop 10.1], &lt;math display=&quot;inline&quot;&gt;\tilde\partial&lt;/math&gt; generates a local one-parameter group &lt;math display=&quot;inline&quot;&gt;(J, \alpha)&lt;/math&gt; such that

&lt;math display=&quot;block&quot;&gt;h(\alpha(t,v)) = h(v) + t&lt;/math&gt;

&lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; is proper and [d] holds, so &lt;math display=&quot;inline&quot;&gt;J = \R \times Z&lt;/math&gt;. If we define &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; as

&lt;math display=&quot;block&quot;&gt;f(v) = (\alpha(-t, v), h(v))&lt;/math&gt;

then &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; maps &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; into &lt;math display=&quot;inline&quot;&gt;h^{-1}(0) \times \R&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi \circ f = h&lt;/math&gt;. If we define &lt;math display=&quot;inline&quot;&gt;\bar f: h^{-1}(0) \times \R \to Z&lt;/math&gt; as

&lt;math display=&quot;block&quot;&gt;\bar f(v, t) = \alpha(t, v)&lt;/math&gt;

then &lt;math display=&quot;inline&quot;&gt;f \bar f = \bar f f = Id&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; is a homeomorphism.&lt;ref&gt;Mather 2012, pp. 497.&lt;/ref&gt;

== Topology at critical points ==

Theorem: If there is a critical point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; in the singular variety &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt; with critical value &lt;math display=&quot;inline&quot;&gt;v \in (a, b)&lt;/math&gt; then the space &lt;math display=&quot;inline&quot;&gt;X_{\leq b}&lt;/math&gt; is homotopic to&lt;ref&gt;Goresky and MacPherson 1988, pp. 174.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;X_{\leq a} \cup [(D^{\lambda+1}, \partial D^{\lambda+1}) \times (\mathcal{L}_X, \partial \mathcal{L}_X)].&lt;/math&gt;

Proof:&lt;ref&gt;Proof outline comes from Goresky and MacPherson 1988, pp. 174.&lt;/ref&gt;
# &lt;math display=&quot;inline&quot;&gt;(X_{\leq b}, X_{\leq a})&lt;/math&gt; is homeomorphic to &lt;math display=&quot;inline&quot;&gt;(X_{\leq v + \epsilon}, X_{\leq v -\epsilon})&lt;/math&gt;. We can prove this by &quot;moving wall&quot; or Thom's Isotopy Lemma.&lt;ref&gt;Goresky and MacPherson 1988, pp. 90-91, 120.&lt;/ref&gt;
# &lt;math display=&quot;inline&quot;&gt;X_{\leq v + \epsilon}&lt;/math&gt; is homeomorphic to &lt;math display=&quot;inline&quot;&gt;X_{\leq v - \epsilon} \cup (J, K)&lt;/math&gt;, where the latter is the local Morse data for &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;. We do this by moving the wall...&lt;ref&gt;Goresky and MacPherson 1988, pp. 95-96, 120-121.&lt;/ref&gt;
# &lt;math display=&quot;inline&quot;&gt;(J, K)&lt;/math&gt; is homeomorphic to &lt;math display=&quot;inline&quot;&gt;(D^{\lambda+1}, \partial D^{\lambda+1}) \times (\mathcal{L}_X, \partial \mathcal{L}_X)&lt;/math&gt; (tangential data, normal data). Again, moving the wall...&lt;ref&gt;Goresky and MacPherson 1988, pp. 65-66, chapter 8, 121.&lt;/ref&gt;
# The normal Morse data depends only on the differential &lt;math display=&quot;inline&quot;&gt;df(p)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 93.&lt;/ref&gt;
# The normal Morse data has the homotopy type of &lt;math display=&quot;inline&quot;&gt;(\mathcal{L}_X, \partial \mathcal{L}_X)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 169.&lt;/ref&gt;

=== Step 1 ===

We get this immediately(?) by Thom's Isotopy Lemma.

=== Step 2 ===

&lt;ref&gt;Goresky and MacPherson 1988, complex case on pp. 120-121 is extension of real case on pp. 95-96.&lt;/ref&gt;

Step 1 works because &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; is a submersion at each point of the regions we are homeomorphing. This is not the case at critical points. We need some way by which a homeomorphism can pass through a critical point.

To prove a homeomorphism between two subsets &lt;math display=&quot;inline&quot;&gt;A&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;B&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;, we project &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; to some other space &lt;math display=&quot;inline&quot;&gt;N&lt;/math&gt; (in our case &lt;math display=&quot;inline&quot;&gt;\R^n&lt;/math&gt;) using some function &lt;math display=&quot;inline&quot;&gt;F&lt;/math&gt;. We take subsets &lt;math display=&quot;inline&quot;&gt;Y_0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Y_1&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;N&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;A = Z \cap F^{-1}(Y_0)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;B = Z \cap F^{-1}(Y_1)&lt;/math&gt;. We need to prove &lt;math display=&quot;inline&quot;&gt;Y_0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Y_1&lt;/math&gt; are connected by a one-parameter family of regions &lt;math display=&quot;inline&quot;&gt;Y_t&lt;/math&gt; [explain one-parameter family]. The criterion for such a family to exist is that the '''characteristic covectors''' of &lt;math display=&quot;inline&quot;&gt;F&lt;/math&gt; are all nonzero on each stratum of &lt;math display=&quot;inline&quot;&gt;Y_t&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 70.&lt;/ref&gt;

At each point &lt;math display=&quot;inline&quot;&gt;x \in M&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;y \in N&lt;/math&gt; there are '''tangent spaces''' &lt;math display=&quot;inline&quot;&gt;T_xM&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;T_yN&lt;/math&gt;, a vector space whose zero is at the point &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; or &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt; (resp.)

[picture of various tangent spaces]

In the case the &lt;math display=&quot;inline&quot;&gt;N = \R&lt;/math&gt;, the tangent space &lt;math display=&quot;inline&quot;&gt;T_x\R&lt;/math&gt; is just &lt;math display=&quot;inline&quot;&gt;\R&lt;/math&gt; but whose origin is at &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt;.

[picture of T_x\R]

Say &lt;math display=&quot;inline&quot;&gt;F(x) = y&lt;/math&gt;, then the differential of the map &lt;math display=&quot;inline&quot;&gt;F&lt;/math&gt; can be seen as a function whose input is a vector in the tangent space &lt;math display=&quot;inline&quot;&gt;T_xM&lt;/math&gt; and whose output is a vector in the tangent space &lt;math display=&quot;inline&quot;&gt;T_yM&lt;/math&gt;. [If I move this far on the tangent space of M how do I move in the tangent space of N?]

[picture]

[example for M = \R and N = \R?]

A function which takes as input a vector in the tangent space &lt;math display=&quot;inline&quot;&gt;T_xM&lt;/math&gt; (say) and outputs a scalar (usually &lt;math display=&quot;inline&quot;&gt;\R&lt;/math&gt;) is called a '''covector'''. The set of all covectors on &lt;math display=&quot;inline&quot;&gt;T_xM&lt;/math&gt; is called the dual space of &lt;math display=&quot;inline&quot;&gt;T_xM&lt;/math&gt; and is denoted &lt;math display=&quot;inline&quot;&gt;T^*_xM&lt;/math&gt;. There are only a limited number of ways to express a covectors. For example, if our tangent space is two-dimensional then all covectors are of the form &lt;math display=&quot;inline&quot;&gt;ax + by&lt;/math&gt; where &lt;math display=&quot;inline&quot;&gt;(x, y) \in T_xM&lt;/math&gt;.

We take our space &lt;math display=&quot;inline&quot;&gt;M&lt;/math&gt; and map it onto &lt;math display=&quot;inline&quot;&gt;\R^2&lt;/math&gt; with the map &lt;math display=&quot;inline&quot;&gt;F(z) = (r(z), h(z))&lt;/math&gt;, where &lt;math display=&quot;inline&quot;&gt;z \in M&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;r&lt;/math&gt; is the square of the distance of &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt; to the critical point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.

[graph of mapping]

In this case, the covectors on the tangent space &lt;math display=&quot;inline&quot;&gt;T_xM&lt;/math&gt; are of the form &lt;math display=&quot;inline&quot;&gt;adf(x) + bdr(x)&lt;/math&gt; (in this case &lt;math display=&quot;inline&quot;&gt;df&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;dr&lt;/math&gt; are maps to &lt;math display=&quot;inline&quot;&gt;\R&lt;/math&gt;) and on &lt;math display=&quot;inline&quot;&gt;T_y\R^2&lt;/math&gt; are of the form &lt;math display=&quot;inline&quot;&gt;cu + dv&lt;/math&gt; (for &lt;math display=&quot;inline&quot;&gt;(u, v) \in \R^2&lt;/math&gt;). A covector &lt;math display=&quot;inline&quot;&gt;cu + dv \in T^*_{(u, v)}\R^2&lt;/math&gt; is called a '''characteristic covector''' of &lt;math display=&quot;inline&quot;&gt;F&lt;/math&gt; if &lt;math display=&quot;inline&quot;&gt;F(x) = (u, v)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;cdf(x) + ddr(x) = 0&lt;/math&gt; for all vectors in the tangent space of the stratum containing &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 82.&lt;/ref&gt; [explain adf(x) + bdr(x) in terms of this being a function which takes a vector input]

[example of where covectors do and do not vanish on a stratified space, pp. 71?]

What we want is a homeomorphism in &lt;math display=&quot;inline&quot;&gt;M&lt;/math&gt; between the space &lt;math display=&quot;inline&quot;&gt;Z_{\leq \epsilon}&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Z_{\leq \epsilon} \cup B&lt;/math&gt;, where &lt;math display=&quot;inline&quot;&gt;B&lt;/math&gt; is a small region of the critical point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;. The '''local Morse data''' is

&lt;math display=&quot;block&quot;&gt;((B_\delta \cap Z) \cap f^{-1}[v-\epsilon, v+\epsilon], (B_\delta \cap Z) \cap f^{-1}(v-\epsilon))&lt;/math&gt;

where &lt;math display=&quot;inline&quot;&gt;B_\delta&lt;/math&gt; is a closed disc in &lt;math display=&quot;inline&quot;&gt;M&lt;/math&gt; of radius &lt;math display=&quot;inline&quot;&gt;\delta&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 63-64.&lt;/ref&gt; Observe that this is the pair &lt;math display=&quot;inline&quot;&gt;(F^{-1}(\text{Box}(\delta, \epsilon)), F^{-1}(\text{Bottom}(\delta, \epsilon)))&lt;/math&gt;&lt;ref&gt;Goresky and MacPherson 1988, pp. 91.&lt;/ref&gt; [explain Box, Bottom, etc.]

[picture of the two subspaces of Z in M]

We use our map &lt;math display=&quot;inline&quot;&gt;F&lt;/math&gt; to convert these two subspaces to subspaces of &lt;math display=&quot;inline&quot;&gt;\R^2&lt;/math&gt; which are of the form &lt;math display=&quot;inline&quot;&gt;Y_1 = \{(x,y) \in \R^2 | y \leq \epsilon\}&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Y_0 = \{(x,y) \in \R^2 | y \leq -\epsilon\} \cup \{(x,y) \in \R^2 | x \leq \delta, y \leq \epsilon\}&lt;/math&gt;, such that &lt;math display=&quot;inline&quot;&gt;Z_{\leq \epsilon} = F^{-1}(Y_1)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Z_{\leq \epsilon} \cup B = F^{-1}(Y_0)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 95-96.&lt;/ref&gt;

We use a homeomorphism between &lt;math display=&quot;inline&quot;&gt;Y_1&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Y_0&lt;/math&gt; using the technique of &quot;moving the wall&quot; and Thom's Isotopy Lemma. Such a homeomorphism exists when the characteristic covectors of &lt;math display=&quot;inline&quot;&gt;F&lt;/math&gt; are all nonzero on each stratum of &lt;math display=&quot;inline&quot;&gt;Y_t&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, chapter 4, particularly pp. 71-72.&lt;/ref&gt;

Given a smooth mapping between manifolds &lt;math display=&quot;inline&quot;&gt;F: M \to N&lt;/math&gt; (for example, in our case we could have &lt;math display=&quot;inline&quot;&gt;N = \R^2&lt;/math&gt;) and that &lt;math display=&quot;inline&quot;&gt;F|Z: Z \to N&lt;/math&gt; is proper. Let &lt;math display=&quot;inline&quot;&gt;Y \subset N \times \R&lt;/math&gt; be a closed Whitney stratified subset such that the projection to the second factor &lt;math display=&quot;inline&quot;&gt;\pi: Y \to \R&lt;/math&gt; is a proper stratified submersion.&lt;ref&gt;Goresky and MacPherson 1988, pp. 71.&lt;/ref&gt;

Suppose for each &lt;math display=&quot;inline&quot;&gt;t \in \R&lt;/math&gt;, for each &lt;math display=&quot;inline&quot;&gt;p \in F(Z) \cap Y_t&lt;/math&gt;, and for each nonzero characteristic covector &lt;math display=&quot;inline&quot;&gt;\lambda \in T^*_pN&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;F|Z&lt;/math&gt;, the restriction of &lt;math display=&quot;inline&quot;&gt;\lambda&lt;/math&gt; to the subspace &lt;math display=&quot;inline&quot;&gt;T_pS_t = \ker(d\pi(p)) \cap T_pS&lt;/math&gt; is nonzero, where &lt;math display=&quot;inline&quot;&gt;S&lt;/math&gt; is a stratum of &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; which contains &lt;math display=&quot;inline&quot;&gt;(p, t)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;S_t = \pi^{-1}(t) \cap S&lt;/math&gt; is the stratum of &lt;math display=&quot;inline&quot;&gt;Y_t = \pi^{-1}(t) \cap Y&lt;/math&gt; which contains &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;. This is equivalent to the statement that, for each &lt;math display=&quot;inline&quot;&gt;t \in \R&lt;/math&gt;, the restriction &lt;math display=&quot;inline&quot;&gt;F|Z&lt;/math&gt; is transverse to &lt;math display=&quot;inline&quot;&gt;Y_t&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 71-72.&lt;/ref&gt;

This means that, for each &lt;math display=&quot;inline&quot;&gt;t \in \R&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;Z \cap F^{-1}(Y_t)&lt;/math&gt; is stratified by its intersection with the strata of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;...

We finally prove there is a homeomorphism between &lt;math display=&quot;inline&quot;&gt;Z \cap F^{-1}(Y_0) \cong Z \cap F^{-1}(Y_1)&lt;/math&gt; which preserves the Whitney stratification of both sides and is smooth on each stratum.

For the composition

&lt;math display=&quot;block&quot;&gt;Z \times \R \subset M \times \R \to_{F \times I} Y \subset \R^2 \times \R \to_{\pi} \R&lt;/math&gt;

where &lt;math display=&quot;inline&quot;&gt;Y(t, z) = Y_t(z)&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;I&lt;/math&gt; is the identity and &lt;math display=&quot;inline&quot;&gt;\pi&lt;/math&gt; is projection to the second factor. 

&lt;math display=&quot;inline&quot;&gt;Z \times \R&lt;/math&gt; is transverse to &lt;math display=&quot;inline&quot;&gt;(F \times I)^{-1}(Y)&lt;/math&gt;...

The composition &lt;math display=&quot;inline&quot;&gt;\pi \circ (F \times I): Z \times \R \cap (F \times I)^{-1}(Y) \to \R&lt;/math&gt; is a stratified submersion because
* The input domain is stratified as above...,
* We have defined &lt;math display=&quot;inline&quot;&gt;F|Z&lt;/math&gt; to be transverse to &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt;, and therefore it preserves the stratification (unless &lt;math display=&quot;inline&quot;&gt;F(Z) \cap Y = \empty&lt;/math&gt;), and
* We defined above the projection on &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; to be a stratified submersion, meaning it is a submersion on each stratum of &lt;math display=&quot;inline&quot;&gt;F(Z) \cap Y&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 43.&lt;/ref&gt;

Therefore, we can apply Thom's Isotopy Lemma which says there is a homeomorphism between the level sets of &lt;math display=&quot;inline&quot;&gt;Z \times \R&lt;/math&gt;...&lt;ref&gt;Goresky and MacPherson 1988, pp. 72.&lt;/ref&gt;

=== Step 3 ===

==== Characteristic covectors ====

==== Fringed sets ====

When manipulating our domain of integration[?], we need to make sure we are doing this in regions with no characteristic covectors. The introduce the concept of a fringed set, a subset of &lt;math display=&quot;inline&quot;&gt;R^2&lt;/math&gt;, and construct a series of fringed sets which contain no characteristic covectors.

A '''fringed set''' &lt;math display=&quot;inline&quot;&gt;A \subset \R \times \R^+&lt;/math&gt; is an open subset of the first quadrant of &lt;math display=&quot;inline&quot;&gt;\R^2&lt;/math&gt;. &lt;math display=&quot;inline&quot;&gt;A&lt;/math&gt; is fringed over &lt;math display=&quot;inline&quot;&gt;0 &lt; y \ll x&lt;/math&gt; if for some interval &lt;math display=&quot;inline&quot;&gt;S = (0, x)&lt;/math&gt;
# the projection of &lt;math display=&quot;inline&quot;&gt;A&lt;/math&gt; to the first factor is equal to &lt;math display=&quot;inline&quot;&gt;S&lt;/math&gt;,
# &lt;math display=&quot;inline&quot;&gt;A&lt;/math&gt; is open in &lt;math display=&quot;inline&quot;&gt;S \times \R^+&lt;/math&gt;,
# if &lt;math display=&quot;inline&quot;&gt;(s, y) \in A&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;0 &lt; y' \leq y&lt;/math&gt; then &lt;math display=&quot;inline&quot;&gt;(s, y') \in A&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 77.&lt;/ref&gt;

[picture]

The fringed set &lt;math display=&quot;inline&quot;&gt;A^\flat&lt;/math&gt; is the set &lt;math display=&quot;inline&quot;&gt;A&lt;/math&gt; plus its reflection about the &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; axis.&lt;ref&gt;Goresky and MacPherson 1988, pp. 82.&lt;/ref&gt;

[picture]

We build a series of fringed sets which do not contain characteristic covectors, which will be used later in our proof.

There exists a fringed set &lt;math display=&quot;inline&quot;&gt;A_2&lt;/math&gt; of type &lt;math display=&quot;inline&quot;&gt;0 &lt; v \ll u&lt;/math&gt; such that for any &lt;math display=&quot;inline&quot;&gt;z \in Z&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;r\pi(z) \leq r_2&lt;/math&gt;, the map &lt;math display=&quot;inline&quot;&gt;(\rho, f - f\pi)|\pi^{-1}(\pi(z)): \pi^{-1}(\pi(z)) \to \R^2&lt;/math&gt; has no characteristic covectors in &lt;math display=&quot;inline&quot;&gt;A^\flat_2&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 84.&lt;/ref&gt;

Given that the set of points &lt;math display=&quot;inline&quot;&gt;(u, v) \in \R^2&lt;/math&gt; which have a nonzero characteristic covector is closed, then it is enough to prove it for points &lt;math display=&quot;inline&quot;&gt;(u, 0) \in \R^2&lt;/math&gt;. Proof by contradiction. Assume it is false and that there is a sequence of points &lt;math display=&quot;inline&quot;&gt;p_i \in Z \cap f^{-1}(0)&lt;/math&gt; converging to &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;d\rho(p_i)&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;df(p_i)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;df\pi(p_i)&lt;/math&gt; are linearly dependent when restricted to the stratum &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; which contains &lt;math display=&quot;inline&quot;&gt;p_i&lt;/math&gt;. This would mean that &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; has a critical point on &lt;math display=&quot;inline&quot;&gt;Y \cap \partial B_{\rho(p_i)}(p)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 82-83.&lt;/ref&gt;

By restricting to a subsequence if necessary, we may assume the points &lt;math display=&quot;inline&quot;&gt;p_i&lt;/math&gt; are all contained in the same stratum &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt;, that the tangent planes &lt;math display=&quot;inline&quot;&gt;T_{p_i}Y&lt;/math&gt; converge to some plane &lt;math display=&quot;inline&quot;&gt;Q&lt;/math&gt; and the secant lines &lt;math display=&quot;inline&quot;&gt;\mathcal{l}_i = \overline{p_i p}&lt;/math&gt; converge to some line &lt;math display=&quot;inline&quot;&gt;\mathcal{l}&lt;/math&gt;. By the Whitney conditions [how?], &lt;math display=&quot;inline&quot;&gt;Q = \lim_{i \to \infty} \mathcal{l}_i \oplus T_{p_i}(Y \cap \partial B_\delta(p))&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 83.&lt;/ref&gt;

For each &lt;math display=&quot;inline&quot;&gt;i&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;f(p_i) = f(p) = v&lt;/math&gt;, this means[?] &lt;math display=&quot;inline&quot;&gt;df(p)(Q) = 0&lt;/math&gt;. On the assumption that &lt;math display=&quot;inline&quot;&gt;df(p)&lt;/math&gt; is nondegenerate, we may assume &lt;math display=&quot;inline&quot;&gt;Y = X&lt;/math&gt;, so &lt;math display=&quot;inline&quot;&gt;\ker d(f|X)(p_i) = T_{p_i}(X \cap \partial B_\delta(p)) = T_{p_i}(X \cap f^{-1}(v))&lt;/math&gt;, which converges to a subspace &lt;math display=&quot;inline&quot;&gt;\tau&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Q = T_pX&lt;/math&gt;, perpendicular to &lt;math display=&quot;inline&quot;&gt;\mathcal{l}&lt;/math&gt;. However, as &lt;math display=&quot;inline&quot;&gt;f^{-1}(v) \cap X&lt;/math&gt; satisfies Whitney's conditions, &lt;math display=&quot;inline&quot;&gt;\mathcal{l} \subset \tau&lt;/math&gt;, a contradiction.&lt;ref&gt;Goresky and MacPherson 1988, pp. 83.&lt;/ref&gt;

We observe that if &lt;math display=&quot;inline&quot;&gt;df(p)&lt;/math&gt; is a nondegenerate characteristic covector for &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; then it is also a nondegenerate characteristic covector for &lt;math display=&quot;inline&quot;&gt;Z \cap \pi^{-1}(p)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 84.&lt;/ref&gt;

==== Homeomorphism ====

We prove there is a stratum preserving homeomorphism between&lt;ref&gt;Goresky and MacPherson 1988, pp. 65.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;\text{Local Morse Data} \cong (\text{Tangential Morse Data}) \times (\text{Normal Morse Data})&lt;/math&gt;

We first prove that there is a homeomorphism between the product of the normal and tangential Morse data and the '''realisation''' of the following diagram

[diagram from pp. 102]

where realisation means

&lt;math display=&quot;block&quot;&gt;Z \cap (g_1, h_1)^{-1}(P_a) \cap (g_2, h_2)^{-1}(P_b)&lt;/math&gt;

where all the intersections of strata (of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;?) are transverse.&lt;ref&gt;Goresky and MacPherson 1988, pp. 100-102.&lt;/ref&gt;

The realisation of the above diagram is equal to

&lt;math display=&quot;block&quot;&gt;(V_1, V_2) \cap (W_1, W_2) = (V_1 \cap W_1, V_1 \cap W_2 \cup V_2 \cap W_1)&lt;/math&gt;

where

&lt;math display=&quot;block&quot;&gt;V_1 = \{ z \in Z : |f(z) - f\pi(z)| \leq \epsilon/4, r\pi(z) \leq \delta, \rho(z) \leq \delta \}&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;V_2 = \{ z \in Z : f(z) - f\pi(z) = -\epsilon/4, r\pi(z) \leq \delta, \rho(z) \leq \delta \}&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;W_1 = \{ z \in Z : |f\pi(z)| \leq 3\epsilon/4, r\pi(z) \leq \delta \}&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;W_1 = \{ z \in Z : f\pi(z) = -3\epsilon/4, r\pi(z) \leq \delta \}&lt;/math&gt;

where &lt;math display=&quot;inline&quot;&gt;\pi&lt;/math&gt; is the projection from the tubular neighbourhood to &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;r(z)&lt;/math&gt; is the square of the distance between &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt; and the critical point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\rho(z)&lt;/math&gt; is the square of the distance between &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi(z)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 100-101.&lt;/ref&gt; &lt;math display=&quot;inline&quot;&gt;\epsilon \ll \delta&lt;/math&gt; are chosen so that &lt;math display=&quot;inline&quot;&gt;(\delta, \epsilon)&lt;/math&gt; is in the set &lt;math display=&quot;inline&quot;&gt;A^\flat_6&lt;/math&gt; which consists of &lt;math display=&quot;inline&quot;&gt;A_6 \subset \R^+ \times \R^+&lt;/math&gt; with the properties that for &lt;math display=&quot;inline&quot;&gt;(\epsilon, \delta) \in A_6&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;\rho(z) = \delta&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;r\pi(z) = \delta&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;|f(z)| \leq \epsilon&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;|f\pi(z)| \leq \epsilon&lt;/math&gt; then the covectors &lt;math display=&quot;inline&quot;&gt;d\rho(z)&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;dr\pi(z)&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;df(z)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;df\pi(z)&lt;/math&gt; are linearly independent when restricted to &lt;math display=&quot;inline&quot;&gt;T_zY&lt;/math&gt; (where &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; is the stratum containing &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt;). We can prove such a set exists.&lt;ref&gt;Goresky and MacPherson 1988, pp. 89.&lt;/ref&gt; &lt;math display=&quot;inline&quot;&gt;A^\flat_6&lt;/math&gt; is this plus its reflection about the &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; axis.&lt;ref&gt;Goresky and MacPherson 1988, pp. 82.&lt;/ref&gt;

Let &lt;math display=&quot;inline&quot;&gt;D = \{ x \in X | r(x) \leq \delta \}&lt;/math&gt; for stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt;. We will show there is a local trivial fibration of the configuration: &lt;math display=&quot;inline&quot;&gt;(V_1, V_2)&lt;/math&gt; fibres over &lt;math display=&quot;inline&quot;&gt;D&lt;/math&gt; and is homeomorphic to &lt;math display=&quot;inline&quot;&gt;D \times (\text{normal Morse data})&lt;/math&gt;

(V_1, V_2) -&gt; D \times (normal Morse data)
|           /
--&gt; D   &lt;---

and that &lt;math display=&quot;inline&quot;&gt;(W_1, W_2)&lt;/math&gt; fibres over the tangential Morse data and is homeomorphic to &lt;math display=&quot;inline&quot;&gt;(\text{tangential Morse data}) \times (\text{normal slice})&lt;/math&gt;.

For &lt;math display=&quot;inline&quot;&gt;Z_1 = \{ z \in Z : r\pi(z) \leq \delta \}&lt;/math&gt;, the map &lt;math display=&quot;inline&quot;&gt;F(z): Z_1 \to \R^2 = (\rho(z), f(z) - f\pi(z))&lt;/math&gt; is transverse to each stratum of &lt;math display=&quot;inline&quot;&gt;\text{Box}(\delta, \epsilon/4)&lt;/math&gt;, [list], [by lemma 6.5]. &lt;math display=&quot;inline&quot;&gt;(V_1, V_2) = F^{-1}(\text{Box}(\delta, \epsilon/4), \text{Bottom}(\delta, \epsilon/4))&lt;/math&gt;. For each stratum &lt;math display=&quot;inline&quot;&gt;S&lt;/math&gt; of Box and each &lt;math display=&quot;inline&quot;&gt;x \in D&lt;/math&gt;, we have transverse intersection &lt;math display=&quot;inline&quot;&gt;F^{-1}(S) \pitchfork \pi^{-1}(x)&lt;/math&gt;. Therefore, &lt;math display=&quot;inline&quot;&gt;\pi|F^{-1}(S)&lt;/math&gt; is a submersion and by Thom's isotopy lemma the projection &lt;math display=&quot;inline&quot;&gt;\pi|F^{-1}(\text{Box}(\delta, \epsilon/4): F^{-1}(\text{Box}(\delta, \epsilon/4)) \to X&lt;/math&gt; is a stratified fibre bundle over &lt;math display=&quot;inline&quot;&gt;D&lt;/math&gt;. The fibre over the critical point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; is &lt;math display=&quot;inline&quot;&gt;\pi^{-1}(p) \cap (F^{-1}(\text{Box}(\delta, \epsilon/4), F^{-1}(\text{Bottom}(\delta, \epsilon/4))&lt;/math&gt; and is equal to the normal Morse data...&lt;ref&gt;Goresky and MacPherson 1988, pp. 101.&lt;/ref&gt;

Take &lt;math display=&quot;inline&quot;&gt;G: X \to \R^2 = (r(x), f(x))&lt;/math&gt;. &lt;math display=&quot;inline&quot;&gt;\delta&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\epsilon&lt;/math&gt; have been chosen so that &lt;math display=&quot;inline&quot;&gt;(G^{-1}(\text{Box}(\delta, \epsilon/4), G^{-1}(\text{Bottom}(\delta, \epsilon/4))&lt;/math&gt; is the tangential Morse data for &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; and is contained in the region &lt;math display=&quot;inline&quot;&gt;D&lt;/math&gt; over which &lt;math display=&quot;inline&quot;&gt;\pi|(V_1, V_2)&lt;/math&gt; is a stratified fibre bundle. Therefore, &lt;math display=&quot;inline&quot;&gt;(W_1, W_2) = \pi^{-1} G^{-1}(\text{Box}(\delta, \epsilon/4), \text{Bottom}(\delta, \epsilon/4))&lt;/math&gt; is transverse to &lt;math display=&quot;inline&quot;&gt;(V_1, V_2)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 101-102.&lt;/ref&gt;

Finally, this means that &lt;math display=&quot;inline&quot;&gt;(V_1, V_2) \cap (W_1, W_2)&lt;/math&gt; is homeomorphic (by stratum preserving homeomorphism) to &lt;math display=&quot;inline&quot;&gt;(\pi^{-1}(p), \cap (V_1, V_2)) \times \pi(W_1, W_2)&lt;/math&gt;, the product of normal and tangential Morse data.&lt;ref&gt;Goresky and MacPherson 1988, pp. 102.&lt;/ref&gt;

We use a succession of such diagrams to interpolate between the box diagram which defines local Morse data [explain] and the above diagram whose realisation we have just proven is &lt;math display=&quot;inline&quot;&gt;(\text{normal Morse data}) \times (\text{tangential Morse data})&lt;/math&gt;.

[diagram_d0.py]

The realisation is the local Morse data. This is equal to the realisation of the diagram below.&lt;ref&gt;Goresky and MacPherson 1988, pp. 103, 106.&lt;/ref&gt;

[diagram_d11.py]

The realisation of the first diagram [d0] is equivalent to the realisation of the below diagram.

[diagram_d1.py]

In the right-hand picture of the above diagram, we have put a dotted outline around the region &lt;math display=&quot;inline&quot;&gt;A^{\flat}_1&lt;/math&gt;. We prove that there are no characteristic covectors for &lt;math display=&quot;inline&quot;&gt;(r, f): Z \to \R^2&lt;/math&gt; in this region and can, therefore, move the wall in this region...&lt;ref&gt;Goresky and MacPherson 1988, pp. 82-83.&lt;/ref&gt;

By adding a zero-dimensional stratum at the top right corner of the right-hand picture. A one-parameter family of pictures &lt;math display=&quot;inline&quot;&gt;P_b(t)&lt;/math&gt; gives rise to a stratified space &lt;math display=&quot;inline&quot;&gt;Y \subset M \times \R&lt;/math&gt; such that

&lt;math display=&quot;block&quot;&gt;Y = \{ (z, t) \in M \times \R : (r, f)(z) \in P_b(t) \}.&lt;/math&gt;

&lt;math display=&quot;inline&quot;&gt;(r, f)&lt;/math&gt; takes each stratum of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; transversally to each stratum of each &lt;math display=&quot;inline&quot;&gt;Y_t&lt;/math&gt;. &lt;math display=&quot;inline&quot;&gt;(f \circ \pi, f)^{-1}(P_a) = f^{-1}[-\epsilon, \infty)&lt;/math&gt; is transverse to each stratum of &lt;math display=&quot;inline&quot;&gt;Y_t \cap Z&lt;/math&gt;. Therefore, there is a homeomorphism between&lt;ref&gt;Goresky and MacPherson 1988, pp. 107.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;Z(D_1) = Z \cap (f \circ \pi, f)^{-1}(P_a) \cap (r, f)^{-1}(P_b(0))&lt;/math&gt;

and

&lt;math display=&quot;block&quot;&gt;Z(D_1) = Z \cap (f \circ \pi, f)^{-1}(P_a) \cap (r, f)^{-1}(P_b(1)).&lt;/math&gt;

To go from D_2 to D_3 we find the characteristic covectors of &lt;math display=&quot;inline&quot;&gt;(f\pi, f): V \to \R^2&lt;/math&gt; where &lt;math display=&quot;inline&quot;&gt;V = (r, f)^{-1}(P_b(1))&lt;/math&gt;. We stratify &lt;math display=&quot;inline&quot;&gt;P_b(1)&lt;/math&gt; by its interior &lt;math display=&quot;inline&quot;&gt;P&lt;/math&gt; and boundary &lt;math display=&quot;inline&quot;&gt;\partial P&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 107.&lt;/ref&gt;

The strata of &lt;math display=&quot;inline&quot;&gt;V&lt;/math&gt; come in four types:
# &lt;math display=&quot;inline&quot;&gt;(r, f)^{-1}(P) \cap X&lt;/math&gt;
# &lt;math display=&quot;inline&quot;&gt;(r, f)^{-1}(P) \cap Y&lt;/math&gt;
# &lt;math display=&quot;inline&quot;&gt;(r, f)^{-1}(\partial P) \cap X&lt;/math&gt;
# &lt;math display=&quot;inline&quot;&gt;(r, f)^{-1}(\partial P) \cap Y&lt;/math&gt;
where &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; is the strata that contains the critical point and &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; is any other strata such that &lt;math display=&quot;inline&quot;&gt;Y &gt; X&lt;/math&gt;.

All characteristic covectors are of the form &lt;math display=&quot;inline&quot;&gt;\lambda = (u, v, adu + bdv) \in T^*\R^2&lt;/math&gt;.

For strata 1 and 3, the image of &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; under &lt;math display=&quot;inline&quot;&gt;(f\pi, f)&lt;/math&gt; is the diagonal &lt;math display=&quot;inline&quot;&gt;f\pi = f&lt;/math&gt; (dotted outline). Therefore, the characteristic covectors of any point &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt; in &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; are either where &lt;math display=&quot;inline&quot;&gt;z = p&lt;/math&gt;, in which case the covector is zero(?), or where &lt;math display=&quot;inline&quot;&gt;z \neq p&lt;/math&gt;, in which case &lt;math display=&quot;inline&quot;&gt;u = v&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;a = b&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 107-108.&lt;/ref&gt;

For strata 2, being that the critical point is isolated and non-degenerate, which means it, and any neighbourhood, is not zero on any limit of tangent spaces in strata &lt;math display=&quot;inline&quot;&gt;Y &gt; X&lt;/math&gt;. Therefore, &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;f\pi&lt;/math&gt; are linearly independent.&lt;ref&gt;Goresky and MacPherson 1988, pp. 84.&lt;/ref&gt; Unless &lt;math display=&quot;inline&quot;&gt;\pi(z) = p&lt;/math&gt;, in which case &lt;math display=&quot;inline&quot;&gt;d(f\pi)(z) = f\pi(z) = 0&lt;/math&gt;, so they are covectors where &lt;math display=&quot;inline&quot;&gt;u = 0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;b = 0&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 108.&lt;/ref&gt;

For strata 4, we can use implicit function theorem to generate local coordinates &lt;math display=&quot;inline&quot;&gt;y_1, \cdots y_{r-s-1}&lt;/math&gt; in &lt;math display=&quot;inline&quot;&gt;Y &gt; X&lt;/math&gt; and define the Riemannian metric &lt;math display=&quot;inline&quot;&gt;r(z) = r\pi(z) + (f(z) - f\pi(z))^2 + g(y)&lt;/math&gt; for some &lt;math display=&quot;inline&quot;&gt;g&lt;/math&gt; depending only on &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt;.

There are no characteristic covectors in &lt;math display=&quot;inline&quot;&gt;|u| \leq \epsilon&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;|v| &lt; \epsilon&lt;/math&gt;. By [lemma 6.7 and 6.8 and 8.1(d)] &lt;math display=&quot;inline&quot;&gt;df&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;df\pi&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;dr&lt;/math&gt; are linearly independent in this region.&lt;ref&gt;Goresky and MacPherson 1988, pp. 109.&lt;/ref&gt; Given &lt;math display=&quot;inline&quot;&gt;|f| \leq \epsilon&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;|f\pi| \leq \epsilon&lt;/math&gt;, a fringed set &lt;math display=&quot;inline&quot;&gt;A^\flat_4&lt;/math&gt; of type &lt;math display=&quot;inline&quot;&gt;0 &lt; \epsilon \ll \delta&lt;/math&gt; and assume that &lt;math display=&quot;inline&quot;&gt;\pi \neq p&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;z \notin X&lt;/math&gt; then &lt;math display=&quot;inline&quot;&gt;(r(z), f(z)) \in A^\flat_4&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;(r(z), f\pi(z)) \in A^\flat_4&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 87.&lt;/ref&gt;

Outside of these points, the slope of &lt;math display=&quot;inline&quot;&gt;\ker(\lambda)&lt;/math&gt; for any characteristic covector &lt;math display=&quot;inline&quot;&gt;\lambda&lt;/math&gt; is

&lt;math display=&quot;block&quot;&gt;\frac{-a}{b} = \frac{f(z) - f\pi(z) - M}{\frac{\alpha}{\beta} + (f(z) - f\pi(z))}&lt;/math&gt;

for &lt;math display=&quot;inline&quot;&gt;\alpha df + \beta dr = 0&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 108-109.&lt;/ref&gt;

== Morse theory ==

Steps(?)
* Explain topology
* Every point of a stratum is locally like a product structure (proved by Thom's Isotopy Lemma) [GM pp. 41-42]
** Including those around critical points, which are the product of normal and tangential Morse data (these are our quasi-local cycles?)
* Thom's Isotopy Lemma proves a strong deformation retraction (which only stops at critical points) [PWM pp. 541-542]

=== Homotopy ===

We want to replace our domain of convergence &lt;math display=&quot;inline&quot;&gt;M&lt;/math&gt;, which is the complement of our singular variety &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt;, with an &quot;equivalent&quot; space &lt;math display=&quot;inline&quot;&gt;M'&lt;/math&gt; which has better understood properties. We say &quot;equivalent&quot; because there are several different things we could mean by &quot;equivalent&quot; in this context. The equivalence we are referring to in this section is called '''homotopy'''.

Imagine two subspaces &lt;math display=&quot;inline&quot;&gt;\gamma_0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\gamma_1&lt;/math&gt; of a space &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; which are defined respectively by smooth functions &lt;math display=&quot;inline&quot;&gt;f, g: X \to Y&lt;/math&gt;. If there exists a smooth function &lt;math display=&quot;inline&quot;&gt;h_s: X \times [0, 1] \to Y&lt;/math&gt;, called a homotopy, such that &lt;math display=&quot;inline&quot;&gt;h_0 = f&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;h_1 = g&lt;/math&gt; and for any &lt;math display=&quot;inline&quot;&gt;\epsilon &gt; 0&lt;/math&gt; there exists a &lt;math display=&quot;inline&quot;&gt;\delta_a&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\delta_b&lt;/math&gt; such that when &lt;math display=&quot;inline&quot;&gt;|s - s_0| &lt; \delta_a&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;|x - x_0| &lt; \delta_b&lt;/math&gt; we have &lt;math display=&quot;inline&quot;&gt;|h_s(x) - h_{s_0}(x_0)| &lt; \epsilon&lt;/math&gt;, then we say &lt;math display=&quot;inline&quot;&gt;\gamma_0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\gamma_1&lt;/math&gt; are '''homotopic'''.&lt;ref&gt;Henle 1979, pp. 251-252.&lt;/ref&gt;

Below is an example where &lt;math display=&quot;inline&quot;&gt;\gamma_0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\gamma_1&lt;/math&gt; are one-dimensional curves and &lt;math display=&quot;inline&quot;&gt;H(t, s) = h_s(t)&lt;/math&gt;.

[[File:Homotopy_curves.png|300px]]

In [[#Homotopy_equivalence|Appendix A]], we formally prove that we can construct an equivalent space &lt;math display=&quot;inline&quot;&gt;M'&lt;/math&gt;. We provide only an example to give some intuition before describing how to construct the space &lt;math display=&quot;inline&quot;&gt;M'&lt;/math&gt; in terms of local cycles around critical points.

=== Motivating example ===

Imagine a torus and a height function which is just the z value of the point.

[[File:3D-Leveltorus.png|200px]]

It has four critical points: two at the top and bottom of the outer circle (&lt;math display=&quot;inline&quot;&gt;p_1, p_4&lt;/math&gt;) and two at the top and bottom of the inner circle (&lt;math display=&quot;inline&quot;&gt;p_2, p_3&lt;/math&gt;).

[picture]

When the height is between the &lt;math display=&quot;inline&quot;&gt;p_1&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;p_2&lt;/math&gt;, the space is a two-cell, which can be retracted to a point.

[picture]

When the height is between &lt;math display=&quot;inline&quot;&gt;p_2&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;p_3&lt;/math&gt;, the space is a cylinder, which can be retracted to a two-cell with a one-cell attached.

[[File:3D-Cylinder_and_disk_with_handle.png|200px]]

When the height is between &lt;math display=&quot;inline&quot;&gt;p_3&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;p_4&lt;/math&gt;, the space is a torus with a disc removed, which can be retracted to a cylinder with a one-cell attached.

[[File:3D-Cylinder_with_handle_and_torus_with_hole.png|200px]]

When the height is greater than &lt;math display=&quot;inline&quot;&gt;p_4&lt;/math&gt;, then the full torus is constructed by attaching a two-cell.

[Explain in terms of Morse data and Morse index?]

=== Morse data and quasi-local cycles ===

As in the above example, we start at the &quot;bottom&quot; of &lt;math display=&quot;inline&quot;&gt;M&lt;/math&gt; and build upwards until just before we reach our first critical point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.

;Smooth points
:This is a tube around a &lt;math display=&quot;inline&quot;&gt;(d-1)&lt;/math&gt;-chain &lt;math display=&quot;inline&quot;&gt;\gamma&lt;/math&gt; where the height function &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; is maximised at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 223.&lt;/ref&gt;
:For example, if &lt;math display=&quot;inline&quot;&gt;F(x, y) = \frac{1}{1 - x - y}&lt;/math&gt; then &lt;math display=&quot;inline&quot;&gt;\lambda = 1&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;B^\lambda&lt;/math&gt; is an arc reaching its highest point at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.
:The normal plane &lt;math display=&quot;inline&quot;&gt;N&lt;/math&gt; at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; is a plane orthogonal to &lt;math display=&quot;inline&quot;&gt;B^1&lt;/math&gt;(?).
:Its normal link &lt;math display=&quot;inline&quot;&gt;L(S)&lt;/math&gt; is a circle with two points missing where it intersects &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt;.
:We make our quasi-local cycle out of the product of the arc and circle joined to &lt;math display=&quot;inline&quot;&gt;M_-&lt;/math&gt; at points below &lt;math display=&quot;inline&quot;&gt;M_-&lt;/math&gt;.
:With the exception of degenerate points, such as monkey saddles...&lt;ref&gt;e.g. Pemantle, Wilson and Melczer 2024, pp. 211.&lt;/ref&gt;

;Transverse multiple points
:This is the product of a &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;-torus and a &lt;math display=&quot;inline&quot;&gt;(d-k)&lt;/math&gt;-chain &lt;math display=&quot;inline&quot;&gt;\gamma&lt;/math&gt;. The torus is the product of circles about &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; in the complex normal space to each strata which intersects &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;. The chain &lt;math display=&quot;inline&quot;&gt;\gamma&lt;/math&gt; is supported in the stratum which is the common intersection of the varieties defined by the factors vanishing at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;, and achieves its maximum height at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 223-224.&lt;/ref&gt;

;Arrangement multiple point
:This is the product of a &lt;math display=&quot;inline&quot;&gt;(d-k)&lt;/math&gt;-chain &lt;math display=&quot;inline&quot;&gt;\gamma&lt;/math&gt; and several &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;-tori, one for each pair of sheets which intersect transversely, where the torus is the product of circles about &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; in each sheet.&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 226.&lt;/ref&gt;

;Cone point
:A cone point is zero-dimensional so there is no &lt;math display=&quot;inline&quot;&gt;\gamma&lt;/math&gt;, just a &lt;math display=&quot;inline&quot;&gt;d&lt;/math&gt;-torus about &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 227.&lt;/ref&gt;

== Notes ==
{{Reflist}}

== References ==
* {{cite book | last1=Goresky | first1=Mark | last2=MacPherson | first2=Robert | title=Stratified Morse Theory | publisher=Springer-Verlag | year=1988 | url=https://www.math.ias.edu/~goresky/pdf/SMT.djvu }}
* {{cite book | last=Henle | first1=Michael | title=A Combinatorial Introduction to Topology | publisher=Dover Publications Inc. New York | year=1979 }}
* {{citation | last=Mather | first=John | title=Notes on Topological Stability | year=2012 | journal=Bulletin of the American Mathematical Society | volume=49 | number=4 | pages=475-506 | url=https://www.ams.org/journals/bull/2012-49-04/S0273-0979-2012-01383-6/S0273-0979-2012-01383-6.pdf }}.
* {{cite book | last1=Pemantle | first1=Robin | last2=Wilson | first2=Mark C. | last3=Melczer | first3=Stephen | title=Analytic Combinatorics in Several Variables | publisher=Cambridge University Press | year=2024 | edition=2nd | url=https://acsvproject.com/PemantleWilsonMelczer23.pdf }}</text>
      <sha1>581208emj5l8i1pdzxxjisazmebvutq</sha1>
    </revision>
    <revision>
      <id>4676714</id>
      <parentid>4676708</parentid>
      <timestamp>2026-10-18T09:05:02Z</timestamp>
      <contributor>
        <username>Dom walden</username>
        <id>3209423</id>
      </contributor>
      <comment>/* Fringed sets */ Statement of theorem for A_3</comment>
      <origin>4676714</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="61495" sha1="buuzod9hry6tgftjysdp9jvnexv6r0g" xml:space="preserve">== Introduction ==

Morse theory tells us that the topology of M only changes at its critical points.

The &quot;Morse data&quot; tells us the topology at each critical point.

Attaching this Morse data together gives us a space which is homopotically eqivalent to M.

This space is a &quot;cell complex&quot;, which has an easy to calculate homology.

Theorem: Our domain of convergence is homotopic to a cell complex of dimension at most &lt;math display=&quot;inline&quot;&gt;2n - d - 1&lt;/math&gt;.&lt;ref&gt;This is theorem D.23 in Pemantle, Wilson and Melczer 2024, pp. 546. Also theorem in section 1.2*/5.2* in SMT pp. 200.&lt;/ref&gt;

Proof:
# &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; is our entire domain, &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt; our variety
# Project our entire domain to complex projective space &lt;math display=&quot;inline&quot;&gt;Z = \pi(X) \subset \C\mathbb{P}^n - H&lt;/math&gt; [define H]
# Define a linear subspace &lt;math display=&quot;inline&quot;&gt;G \subset \C\mathbb{P}^n&lt;/math&gt; of dimension &lt;math display=&quot;inline&quot;&gt;d - 1&lt;/math&gt;
# Define a Morse function on &lt;math display=&quot;inline&quot;&gt;f: \C\mathbb{P}^n \to \R&lt;/math&gt; which approximates the distance from &lt;math display=&quot;inline&quot;&gt;G&lt;/math&gt; and such that &lt;math display=&quot;inline&quot;&gt;f^{-1}(0) = G&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;f^{-1}(1) = H&lt;/math&gt;
# We &quot;build&quot; &lt;math display=&quot;inline&quot;&gt;X - \mathcal{V}&lt;/math&gt; from &lt;math display=&quot;inline&quot;&gt;\pi^{-1}(G \cap Z) \cap (X - \mathcal{V})&lt;/math&gt; by attaching CW complexes at critical points which are of at most dimension &lt;math display=&quot;inline&quot;&gt;2n - d - 1&lt;/math&gt;
# At a critical point, the normal Morse data is &lt;math display=&quot;inline&quot;&gt;(J, K) = \coprod_x (J_x, K_x)&lt;/math&gt; and the relative complex link is &lt;math display=&quot;inline&quot;&gt;\mathcal{L}^\pi = \coprod_x \mathcal{L}_x&lt;/math&gt;
# We show that the quotient &lt;math display=&quot;inline&quot;&gt;J_x/K_x&lt;/math&gt; is homotopic to a CW complex of dimension &lt;math display=&quot;inline&quot;&gt;\leq 2n - d - 1&lt;/math&gt;
# The neighbourhood of &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; in &lt;math display=&quot;inline&quot;&gt;J_x&lt;/math&gt; is homeomorphic to the cone in &lt;math display=&quot;inline&quot;&gt;L_x(X - \mathcal{V})&lt;/math&gt;, and removing the point &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; increases the homotopy dimension to at most the homotopy dimension of &lt;math display=&quot;inline&quot;&gt;L_x&lt;/math&gt;
# &lt;math display=&quot;inline&quot;&gt;(J_x \cup \{x\}, K_x)&lt;/math&gt; is homotopic to &lt;math display=&quot;inline&quot;&gt;(\text{cone}(\mathcal{L}_x), \mathcal{L}_x)&lt;/math&gt;
# &lt;math display=&quot;inline&quot;&gt;\mathcal{L}_x&lt;/math&gt; is homotopic to a CW complex of dimension at most &lt;math display=&quot;inline&quot;&gt;2n - d - 1&lt;/math&gt;
# The tangential Morse data at the critical point is homotopic to the pair &lt;math display=&quot;inline&quot;&gt;(D^\lambda, \partial D^\lambda)&lt;/math&gt;
# Therefore, at each critical point a space has been added homotopic to a CW complex of dimension at most &lt;math display=&quot;inline&quot;&gt;2n - d - 1&lt;/math&gt;.

Theorem: If &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; is the complement in &lt;math display=&quot;inline&quot;&gt;\C^n&lt;/math&gt; of a complex variety &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt; of dimension &lt;math display=&quot;inline&quot;&gt;d&lt;/math&gt; then &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; is homotopic to a CW complex of dimension at most &lt;math display=&quot;inline&quot;&gt;2n - d - 1&lt;/math&gt;.&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 546.&lt;/ref&gt;

Proof:
# We build &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; by attaching cells of dimension at most &lt;math display=&quot;inline&quot;&gt;2n - d - 1&lt;/math&gt; at each critical point.
## Prove that we can do this without changing the homotopy(?)
## We use Thom's Isotopy Lemma to prove that there is a strong deformation retraction, stopping only at critical points.
# Prove these cells are a product of the normal and tangential Morse data.
## Normal data: &lt;math display=&quot;inline&quot;&gt;(\mathcal{L}(S), \partial \mathcal{L}(S)) \times (D^1, \partial D^1)&lt;/math&gt; [GM pp. 18]
## Tangential data: &lt;math display=&quot;inline&quot;&gt;(B_\delta \cap f^{-1}[v - \epsilon, v + \epsilon], B_\delta \cap f^{-1}(v - \epsilon))&lt;/math&gt; for &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; restricted to &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; (or &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt;?) [GM pp. 63-64]
# If &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt; is the dimension of the strata, then
## If &lt;math display=&quot;inline&quot;&gt;k = d&lt;/math&gt; then it is a smooth point and the cell is the product of &lt;math display=&quot;inline&quot;&gt;S^{2(n-d)-1}&lt;/math&gt; and the tangential data is dimension at most &lt;math display=&quot;inline&quot;&gt;d&lt;/math&gt;.
## If &lt;math display=&quot;inline&quot;&gt;k &lt; d&lt;/math&gt;, ...

&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 547.&lt;/ref&gt;

== Example in one dimension ==

Domain with singularities v_1, v_2, ..., v_i

Define our height function f...

Start with our entire domain X

Reduce from X to X_i+ by using Thom's Isotopy lemma to do a strong deformation retract

== Thom's isotopy lemma ==

We present a modified version of Thom's (first) isotopy lemma, less general than the original but more obviously relevant to our situation.

Theorem: Suppose &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; is a closed subset of a smooth manifold &lt;math display=&quot;inline&quot;&gt;M&lt;/math&gt; which admits a Whitney stratification and &lt;math display=&quot;inline&quot;&gt;h : M \to \R&lt;/math&gt; is a proper Morse function which has no critical values on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;. Then, the level sets of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; are homeomorphic by a homeomorphism that preserves the strata of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;.&lt;ref&gt;For various versions of the full statement of the theorem, see Mather 2012, pp. 499, Goresky and MacPherson 1988, pp. 41, or Pemantle, Wilson and Melczer 2024, pp. 541.&lt;/ref&gt;

Proof:
# Construct control data for &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; compatible with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;.
## [Prop 7.1] If &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; is smooth on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; and is a submersion for each strata then there exists a family of control data for &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; compatible with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 488.&lt;/ref&gt;
# This makes &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; an abstract stratified set and &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; a controlled submersion.
# A controlled submersion has, for any smooth vector field on &lt;math display=&quot;inline&quot;&gt;\R&lt;/math&gt;, a controlled vector field on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; (a &quot;lift&quot;?)&lt;ref&gt;Mather 2012, pp. 493.&lt;/ref&gt;
# A controlled vector field has a unique one-parameter family of homeomorphisms of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; which commute with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 496.&lt;/ref&gt;
# This makes &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; a locally trivial fibration. [Prop 10.2]&lt;ref&gt;Mather 2012, pp. 499.&lt;/ref&gt;

Control data:

A system of '''control data''' for &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; consists of, for each stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;,
* a '''tubular neighbourhood''' &lt;math display=&quot;inline&quot;&gt;T_X&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt;
* a '''tubular projection function''' &lt;math display=&quot;inline&quot;&gt;\pi_X: T_X \to X&lt;/math&gt;, and
* a '''tubular distance function''' &lt;math display=&quot;inline&quot;&gt;\rho_X: T_X \to \R&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;\rho_X^{-1}(0) = X&lt;/math&gt;&lt;ref&gt;Goresky and MacPherson 1988, pp. 42.&lt;/ref&gt;

[illustration]

such that if &lt;math display=&quot;inline&quot;&gt;X &lt; Y&lt;/math&gt; are strata in &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;, then

&lt;math display=&quot;block&quot;&gt;\pi_X \pi_Y(m) = \pi_X(m),&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;\rho_X \pi_Y(m) = \rho_X(m)&lt;/math&gt;

for all &lt;math display=&quot;inline&quot;&gt;m \in |T_X| \cap |T_Y|&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;\pi_Y(m) \in |T_X|&lt;/math&gt;.

If, for all strata &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; and all &lt;math display=&quot;inline&quot;&gt;m \in |T_X|&lt;/math&gt;, we have &lt;math display=&quot;inline&quot;&gt;h \pi_X(m) = h(m)&lt;/math&gt;, then this control data will be said to be compatible with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 488.&lt;/ref&gt;

We prove that if &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; is smooth on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; and is a submersion for each strata then there exists a family of control data for &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; compatible with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 488, prop 7.1.&lt;/ref&gt;

Let &lt;math display=&quot;inline&quot;&gt;Z_k&lt;/math&gt; be the union of strata of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; of dimension less than &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;. We prove by induction on &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;.

To construct the tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T_X&lt;/math&gt; of a stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of dimension less than &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;. For &lt;math display=&quot;inline&quot;&gt;l \leq k&lt;/math&gt;, let &lt;math display=&quot;inline&quot;&gt;U_l&lt;/math&gt; denote the union of all &lt;math display=&quot;inline&quot;&gt;|T_Y|&lt;/math&gt; for &lt;math display=&quot;inline&quot;&gt;Y &lt; X&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\dim Y \geq l&lt;/math&gt;. Let &lt;math display=&quot;inline&quot;&gt;X_l = U_l \cap X&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 489.&lt;/ref&gt;

For &lt;math display=&quot;inline&quot;&gt;l = k&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;X_k = \empty&lt;/math&gt;. Assume by induction that &lt;math display=&quot;inline&quot;&gt;T_{l+1}&lt;/math&gt; has been constructed and that if &lt;math display=&quot;inline&quot;&gt;Y &lt; X&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;\dim Y \geq l + 1&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;m \in |T_{l+1}| \cap |T_Y|&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi_{l+1}(m) \in |T_Y|&lt;/math&gt; (&lt;math display=&quot;inline&quot;&gt;\pi_{l+1} = \pi_{T_{l+1}}&lt;/math&gt;) then&lt;ref&gt;Mather 2012, pp. 489-490.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;\rho_Y \pi_{l+1}(m) = \rho_Y(m),&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;\pi_Y \pi_{l+1}(m) = \pi_Y(m).&lt;/math&gt;

We wish to construct a tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T_{X,Y}&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;|T_Y| \cap X&lt;/math&gt; whose restriction to &lt;math display=&quot;inline&quot;&gt;|T_Y| \cap X_{l+1}&lt;/math&gt; is isomorphic to the restriction of &lt;math display=&quot;inline&quot;&gt;T_{l+1}&lt;/math&gt; such that if &lt;math display=&quot;inline&quot;&gt;m \in |T_{X,Y}| \cap |T_Y|&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi_{X,Y}(m) \in |T_Y|&lt;/math&gt; (&lt;math display=&quot;inline&quot;&gt;\pi_{X,Y} = \pi_{T_{X,Y}}&lt;/math&gt;) then

&lt;math display=&quot;block&quot;&gt;\rho_Y \pi_{X,Y}(m) = \rho_Y(m),&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;\pi_Y \pi_{X,Y}(m) = \pi_Y(m).&lt;/math&gt;

By shrinking &lt;math display=&quot;inline&quot;&gt;|T_Y|&lt;/math&gt; if necessary, this relation is already satisfied if &lt;math display=&quot;inline&quot;&gt;m \in |T_{l+1}| \cap |T_Y|&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi_{l+1}(m) \in |T_Y|&lt;/math&gt; with &lt;math display=&quot;inline&quot;&gt;T_{l+1}&lt;/math&gt; in place of &lt;math display=&quot;inline&quot;&gt;T_{X,Y}&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi_{l+1}&lt;/math&gt; in place of &lt;math display=&quot;inline&quot;&gt;\pi_{X,Y}&lt;/math&gt;. By the definition, if &lt;math display=&quot;inline&quot;&gt;m \in |T_{l+1}|&lt;/math&gt; then there exists &lt;math display=&quot;inline&quot;&gt;Z &lt; X&lt;/math&gt; with &lt;math display=&quot;inline&quot;&gt;\dim Z &gt; l&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;m \in |T_Z|&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi_{l+1}(m) \in |T_Z|&lt;/math&gt;. We have that &lt;math display=&quot;inline&quot;&gt;\pi_{l+1}(m) \in |T_Y| \cap |T_Z|&lt;/math&gt; and therefore &lt;math display=&quot;inline&quot;&gt;Y &lt; Z&lt;/math&gt;. Therefore&lt;ref&gt;Mather 2012, pp. 490.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;\rho_Y \pi_{l+1}(m) = \rho_Y \pi_Z \pi_{l+1}(m) = \rho_Y \pi_Z(m) = \rho_Y(m),&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;\pi_Y \pi_{l+1}(m) = \pi_Y \pi_Z \pi_{l+1}(m) = \pi_Y \pi_Z(m) = \pi_Y(m).&lt;/math&gt;

We can prove that, by shrinking &lt;math display=&quot;inline&quot;&gt;|T_Y|&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;(\rho_Y, \pi_Y): |T_Y| \cap X \to \R \times Y&lt;/math&gt; is a submersion [prop 7.3?] and that &lt;math display=&quot;inline&quot;&gt;T_{X,Y}&lt;/math&gt; is compatible with &lt;math display=&quot;inline&quot;&gt;(\rho_Y, \pi_Y): |T_Y| \cap X_{l+1} \to \R \times Y&lt;/math&gt;, i.e. &lt;math display=&quot;inline&quot;&gt;(\rho_Y, \pi_Y) \pi_{X,Y}(m) = (\rho_Y, \pi_Y)(m)&lt;/math&gt;(?).

To prove it is a submersion, for the tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T = (E, \epsilon, \psi)&lt;/math&gt; there exists a smooth positive function &lt;math display=&quot;inline&quot;&gt;\epsilon'&lt;/math&gt; such that

&lt;math display=&quot;block&quot;&gt;(\rho_T, \pi_T): Y \cap |T|_{\epsilon'}^0 \to \R \times X,&lt;/math&gt;

where &lt;math display=&quot;inline&quot;&gt;|T|_{\epsilon'}^0 = \psi(B_\epsilon \cap B_{\epsilon'})&lt;/math&gt;, is a submersion. If &lt;math display=&quot;inline&quot;&gt;\Sigma&lt;/math&gt; is the set &lt;math display=&quot;inline&quot;&gt;y \in |T|&lt;/math&gt; such that the rank of

&lt;math display=&quot;block&quot;&gt;(\rho_T, \pi_T): T \cap |T| \to \R \times X&lt;/math&gt;

at &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt; is less than &lt;math display=&quot;inline&quot;&gt;\dim(\R \times X)&lt;/math&gt;. We need to prove that for any &lt;math display=&quot;inline&quot;&gt;x \in X&lt;/math&gt; there exists a neighbourhood of &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; which does not intersect with &lt;math display=&quot;inline&quot;&gt;\Sigma&lt;/math&gt;, i.e. the map is not a submersion in this neighbourhood. It follows from [lemma 7.2] that it is enough to prove for &lt;math display=&quot;inline&quot;&gt;M = \R^m&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;X = \R^{m-c} \times 0_c&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;T&lt;/math&gt; is the '''standard tubular neighbourhood'''.&lt;ref&gt;Mather 2012, pp. 489.&lt;/ref&gt;

By standard tubular neighbourhood, we mean the trivial bundle with base &lt;math display=&quot;inline&quot;&gt;\R^{m-c}&lt;/math&gt; and fibre &lt;math display=&quot;inline&quot;&gt;\R^c&lt;/math&gt; where &lt;math display=&quot;inline&quot;&gt;\pi: \R^m \to \R^{m-c}&lt;/math&gt;...&lt;ref&gt;Mather 2012, pp. 488.&lt;/ref&gt;

For &lt;math display=&quot;inline&quot;&gt;y \in |T| - \R^{m-c}&lt;/math&gt;, the kernal of the differential of &lt;math display=&quot;inline&quot;&gt;(\pi_T, \rho_T)&lt;/math&gt; at &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt; is the orthogonal complement of &lt;math display=&quot;inline&quot;&gt;(\R^{m-c} \times 0_c) \oplus \stackrel{\frown}{y \pi_T(y)}&lt;/math&gt; in &lt;math display=&quot;inline&quot;&gt;\R^m&lt;/math&gt;. By the Whitney conditions, we have that for &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt; near &lt;math display=&quot;inline&quot;&gt;\R^{m-c}&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;(\R^{m-c} \times 0_c) \oplus \stackrel{\frown}{y \pi_T(y)}&lt;/math&gt; is close to the set of &lt;math display=&quot;inline&quot;&gt;m - c + 1&lt;/math&gt; planes in &lt;math display=&quot;inline&quot;&gt;m-&lt;/math&gt;space to an &lt;math display=&quot;inline&quot;&gt;m - c + 1&lt;/math&gt; plane in &lt;math display=&quot;inline&quot;&gt;TY_y&lt;/math&gt;. Therefore, for &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt; near enough to &lt;math display=&quot;inline&quot;&gt;\R^{m-c}&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;TY_y&lt;/math&gt; is transverse to the kernal of the differential of &lt;math display=&quot;inline&quot;&gt;(\pi_T, \rho_T)&lt;/math&gt; and, therefore, is a submersion when restricted to &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 489.&lt;/ref&gt;

To prove that &lt;math display=&quot;inline&quot;&gt;T_{X,Y}&lt;/math&gt; is compatible with &lt;math display=&quot;inline&quot;&gt;(\rho_Y, \pi_Y): |T_Y| \cap X_{l+1} \to \R \times Y&lt;/math&gt;...&lt;ref&gt;Mather 2012, pp. 490.&lt;/ref&gt;

Therefore, there exists a tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T_0&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;X_0&lt;/math&gt; satisfying

&lt;math display=&quot;block&quot;&gt;\rho_Y \pi_0(m) = \rho_Y(m),&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;\pi_Y \pi_0(m) = \pi_Y(m).&lt;/math&gt;

From this we can prove that &lt;math display=&quot;inline&quot;&gt;T_0&lt;/math&gt; is compatible with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;. Replacing &lt;math display=&quot;inline&quot;&gt;T_0&lt;/math&gt; with a smaller tubular neighbourhood if necessary we can assume &lt;math display=&quot;inline&quot;&gt;m \in |T_0|&lt;/math&gt; such that for some &lt;math display=&quot;inline&quot;&gt;Y &lt; X&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;m \in |T_Y|&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi_0(m) \in |T_Y|&lt;/math&gt;, then&lt;ref&gt;Mather 2012, pp. 490.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;h \pi_0(m) = h \pi_Y \pi_0(m) = h \pi_Y(m) = h(m).&lt;/math&gt;

By the generalised tubular neighourhood theorem [prop 7.2?], we can replace &lt;math display=&quot;inline&quot;&gt;T_0&lt;/math&gt; with a tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; compatible with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;. This completes the construction of &lt;math display=&quot;inline&quot;&gt;T_X&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 491.&lt;/ref&gt;

This makes &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; an '''abstract stratified set''' with axioms...&lt;ref&gt;Mather 2012, pp. 491-492.&lt;/ref&gt;

This also makes &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; a '''controlled submersion''' because
# &lt;math display=&quot;inline&quot;&gt;h|X: X \to \R&lt;/math&gt; is a smooth submersion on each strata &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;, and
# for each stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; there is a tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T'_X&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;h(v) = h \pi_X(v)&lt;/math&gt; for all &lt;math display=&quot;inline&quot;&gt;v \in T'_X&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 493.&lt;/ref&gt;

The core of this is the concept of a '''vector field'''. A vector field is a function which assigns, for each point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; in a space, a '''vector''', which can be represented by an arrow whose tail starts at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.&lt;ref&gt;Henle 1979, pp. 33.&lt;/ref&gt;

[picture]

Imagine we have a vector field &lt;math display=&quot;inline&quot;&gt;v(x)&lt;/math&gt; defined in a space and draw a line through our space. At each point along this line the vector field assigns a vector. If we move each point in this line along the arrow defined by this vector in the direction of the arrow head. This &quot;flows&quot; the entire line along the vectors.

[picture]

We define a '''stratified vector field''' &lt;math display=&quot;inline&quot;&gt;\eta&lt;/math&gt; on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; to be a family of smooth vector fields &lt;math display=&quot;inline&quot;&gt;\eta_X&lt;/math&gt;, one for each strata &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 493.&lt;/ref&gt;

We define a '''controlled vector field''' &lt;math display=&quot;inline&quot;&gt;\eta&lt;/math&gt; on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; to be a stratified vector field such that for any strata &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; there exists a tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T'_Y&lt;/math&gt; such that for any &lt;math display=&quot;inline&quot;&gt;X &gt; Y&lt;/math&gt; and any &lt;math display=&quot;inline&quot;&gt;v \in T'_X \cap X&lt;/math&gt;&lt;ref&gt;Mather 2012, pp. 493.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;\eta_X \rho_{Y,X}(v) = 0,&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;(\pi_{Y,X})_* \eta_X(v) = \eta_Y (\pi_{Y,X}(v)).&lt;/math&gt;

We prove that if &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; is a controlled submersion then, for any smooth vector field &lt;math display=&quot;inline&quot;&gt;\zeta&lt;/math&gt; on &lt;math display=&quot;inline&quot;&gt;\R&lt;/math&gt; there is a controlled vector field &lt;math display=&quot;inline&quot;&gt;\eta&lt;/math&gt; on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;h_* \eta(v) = \zeta(h(v))&lt;/math&gt; for all &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 493.&lt;/ref&gt;

Proceeding by induction on the maximum dimension of the strata of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;, we define &lt;math display=&quot;inline&quot;&gt;Z_k&lt;/math&gt; to be the union of strata of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; of dimension at most &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;. The tubular neighbourhood of &lt;math display=&quot;inline&quot;&gt;Z_k&lt;/math&gt; is the intersection of the tubular neighbourhoods of each strata in &lt;math display=&quot;inline&quot;&gt;Z_k&lt;/math&gt; with &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;. The projection and distance functions are the restrictions of the respective functions of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;.

It is trivially true when the maximum dimension of strata in &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; is zero. Assume it is true for &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt; and construct each &lt;math display=&quot;inline&quot;&gt;\eta_X&lt;/math&gt; separately for each stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of dimension &lt;math display=&quot;inline&quot;&gt;k + 1&lt;/math&gt;.

By the assumption that we have controlled vector fields for all strata &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; of dimension at most &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;, we have the two control conditions defined above for any &lt;math display=&quot;inline&quot;&gt;X &gt; Y&lt;/math&gt; and that there is a neighbourhood &lt;math display=&quot;inline&quot;&gt;T^1_Y&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;h(v) = h \pi_Y(v)&lt;/math&gt; for &lt;math display=&quot;inline&quot;&gt;v \in T^1_Y&lt;/math&gt;.

We want to prove that for all &lt;math display=&quot;inline&quot;&gt;Y &lt; X&lt;/math&gt;, the control conditions are satisfied for all &lt;math display=&quot;inline&quot;&gt;v \in T^2_Y&lt;/math&gt; and that &lt;math display=&quot;inline&quot;&gt;h_*\eta_X(v) = \zeta(v)&lt;/math&gt; for all &lt;math display=&quot;inline&quot;&gt;v \in X&lt;/math&gt;.

Take a point &lt;math display=&quot;inline&quot;&gt;x \in X&lt;/math&gt; and define the set &lt;math display=&quot;inline&quot;&gt;S_v&lt;/math&gt; of strata &lt;math display=&quot;inline&quot;&gt;Y &lt; X&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;v \in T^2_Y&lt;/math&gt;. &lt;math display=&quot;inline&quot;&gt;S_v&lt;/math&gt; is totally ordered since if &lt;math display=&quot;inline&quot;&gt;Y_1&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Y_2&lt;/math&gt; are not comparable then &lt;math display=&quot;inline&quot;&gt;T^2_{Y_1} \cap T^2_{Y_2} = \empty&lt;/math&gt;. Therefore, there is a largest member &lt;math display=&quot;inline&quot;&gt;Y = Y_v&lt;/math&gt;.

Assume the control conditions hold for &lt;math display=&quot;inline&quot;&gt;Y = Y_v&lt;/math&gt;. Then they hold for all &lt;math display=&quot;inline&quot;&gt;Y_i \in S_v&lt;/math&gt;. For, either &lt;math display=&quot;inline&quot;&gt;Y_i = Y&lt;/math&gt; or &lt;math display=&quot;inline&quot;&gt;Y_i &lt; Y&lt;/math&gt;. In the latter case, &lt;math display=&quot;inline&quot;&gt;\pi_Y(v) \in T^1_{Y_i}&lt;/math&gt; (by the choice of &lt;math display=&quot;inline&quot;&gt;T^2_Y&lt;/math&gt;'s [is this why?]. Then

&lt;math display=&quot;block&quot;&gt;\begin{align}
\eta_X(v) \rho_{Y_i,X}(v) &amp;= \eta_X \rho_{Y_i,Y} \pi_{Y,X}(v) \\
&amp;= (\pi_{Y,X})_* \eta_X(v) \rho_{Y_i,Y} \\
&amp;= \eta_Y(\pi_{Y,X}(v)) \rho_{Y_i,Y} \\
&amp;= 0
\end{align}&lt;/math&gt;

and

&lt;math display=&quot;block&quot;&gt;\begin{align}
(\pi_{Y_i,X})_* \eta_X(v) &amp;= (\pi_{Y_i,Y})_* (\pi_{Y,X})_* \eta_X(v) \\
&amp;= (\pi_{Y_i,Y})_* \eta_Y(v) (\pi_{Y,X}) \\
&amp;= \eta_{Y_i}(\pi_{Y_i,Y} \pi_{Y,X}(v)) \\
&amp;= \eta_{Y_i}(\pi_{Y_i,X}(v))
\end{align}&lt;/math&gt;

and, therefore, condition holds for all &lt;math display=&quot;inline&quot;&gt;Y_i \in S_v&lt;/math&gt;. Also,

&lt;math display=&quot;block&quot;&gt;\begin{align}
h_* \eta_X(v) &amp;= (h \circ \pi_{Y,X})_* \eta_X(v) \\
&amp;= h_* \eta_Y (\pi_{Y,X}(v)) \\
&amp;= \zeta(f(v))
\end{align}&lt;/math&gt;

and, therefore, the conclusion of the theorem holds at &lt;math display=&quot;inline&quot;&gt;v&lt;/math&gt;.

This shows we can construct &lt;math display=&quot;inline&quot;&gt;\eta_X&lt;/math&gt; satisfying the control conditions when &lt;math display=&quot;inline&quot;&gt;S_v&lt;/math&gt; is non-empty and satisfying the theorem when &lt;math display=&quot;inline&quot;&gt;S_v&lt;/math&gt; is empty. The set of vectors satisfying these conditions is convex in &lt;math display=&quot;inline&quot;&gt;TX_v&lt;/math&gt;, and so we construct &lt;math display=&quot;inline&quot;&gt;\eta_X&lt;/math&gt; globally via a partition of unity.&lt;ref&gt;Mather 2012, pp. 493-495.&lt;/ref&gt;

Finally, we prove that a controlled vector field has a unique one-parameter family of homeomorphisms of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; which commute with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;.&lt;ref&gt;Mather 2012, this combines Proposition 10.1 and Corollary 10.2 on pp. 496 and 497, respectively.&lt;/ref&gt;

For each stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;\eta_X&lt;/math&gt; generates a unique smooth local one-parameter group &lt;math display=&quot;inline&quot;&gt;(J_X, \alpha_X)&lt;/math&gt; of diffeomorphisms of &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; (by standard results of differential geometry), such that &lt;math display=&quot;inline&quot;&gt;\frac{d}{dt} \alpha(t, v)|_{t=0} = \eta_X(v)&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;J_X&lt;/math&gt; is an open subset of &lt;math display=&quot;inline&quot;&gt;\R \times Z&lt;/math&gt;, ...

If we define &lt;math display=&quot;inline&quot;&gt;(J, \alpha)&lt;/math&gt; by

&lt;math display=&quot;block&quot;&gt;J = \bigcup_{X \in S} J_X&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;\alpha = \bigcup_{X \in S} \alpha_X&lt;/math&gt;

we can prove that this is a local one-parameter family of homeomorphisms.&lt;ref&gt;Mather 2012, pp. 496.&lt;/ref&gt;

Firstly, it is clear that
# &lt;math display=&quot;inline&quot;&gt;0 \times Z \subseteq J&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\alpha(0, v) = v&lt;/math&gt; for all &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt;.
# If &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt; then &lt;math display=&quot;inline&quot;&gt;J_v = J \cap (\R \times v) \subseteq \R&lt;/math&gt; is an open interval &lt;math display=&quot;inline&quot;&gt;(a_v, b_v)&lt;/math&gt;, possibly infinite at one or both ends.
# If &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;t, s, t + s&lt;/math&gt; are in &lt;math display=&quot;inline&quot;&gt;(a_v, b_v)&lt;/math&gt; then &lt;math display=&quot;inline&quot;&gt;\alpha(t + s, v) = \alpha(t, \alpha(s, v))&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 495.&lt;/ref&gt;

Secondly, it is clear that &lt;math display=&quot;inline&quot;&gt;\eta&lt;/math&gt; generates &lt;math display=&quot;inline&quot;&gt;\alpha&lt;/math&gt; because
# Each stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; is invariant under &lt;math display=&quot;inline&quot;&gt;\alpha&lt;/math&gt;, i.e. &lt;math display=&quot;inline&quot;&gt;\alpha[J \cap (\R \times X)] \subseteq X&lt;/math&gt;.
# For each &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt;, the map &lt;math display=&quot;inline&quot;&gt;t \to \alpha(t, v)&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;(a_v, b_v)&lt;/math&gt; into the stratum which contains &lt;math display=&quot;inline&quot;&gt;v&lt;/math&gt; is &lt;math display=&quot;inline&quot;&gt;C^1&lt;/math&gt;.
# For any &lt;math display=&quot;inline&quot;&gt;(t, v) \in Z&lt;/math&gt;(?) we have &lt;math display=&quot;inline&quot;&gt;d/dt \alpha(t, v) = \eta(\alpha(t, v))&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 495.&lt;/ref&gt;

It is unique because each &lt;math display=&quot;inline&quot;&gt;(J_X, \alpha_X)&lt;/math&gt; is unique. We just need to prove that &lt;math display=&quot;inline&quot;&gt;J&lt;/math&gt; is open, &lt;math display=&quot;inline&quot;&gt;\alpha&lt;/math&gt; is continuous, and for any &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt; and any compact set &lt;math display=&quot;inline&quot;&gt;K \subseteq Z&lt;/math&gt; there exists &lt;math display=&quot;inline&quot;&gt;\epsilon &gt; 0&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;\alpha(t, v) \notin K&lt;/math&gt; if &lt;math display=&quot;inline&quot;&gt;t \in (a_v, a_v + \epsilon) \cup (b_v - \epsilon, b_v)&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 495.&lt;/ref&gt;

For the latter-most condition, if it did not hold then there exists...&lt;ref&gt;Mather 2012, pp. 496-497.&lt;/ref&gt;

We prove there is a homeomorphism &lt;math display=&quot;inline&quot;&gt;f: Z \to h^{-1}(0) \times \R&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;\pi \circ f = h&lt;/math&gt;, where &lt;math display=&quot;inline&quot;&gt;\pi: h^{-1}(0) \times \R \to \R&lt;/math&gt; is projection to the second factor.

For the coordinate vector field &lt;math display=&quot;inline&quot;&gt;\partial&lt;/math&gt; on &lt;math display=&quot;inline&quot;&gt;\R&lt;/math&gt;, by [prop 9.1] there is a controlled vector field &lt;math display=&quot;inline&quot;&gt;\tilde\partial&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;f_* \tilde\partial(v) = \partial(h(v))&lt;/math&gt; for &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt;. By [prop 10.1], &lt;math display=&quot;inline&quot;&gt;\tilde\partial&lt;/math&gt; generates a local one-parameter group &lt;math display=&quot;inline&quot;&gt;(J, \alpha)&lt;/math&gt; such that

&lt;math display=&quot;block&quot;&gt;h(\alpha(t,v)) = h(v) + t&lt;/math&gt;

&lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; is proper and [d] holds, so &lt;math display=&quot;inline&quot;&gt;J = \R \times Z&lt;/math&gt;. If we define &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; as

&lt;math display=&quot;block&quot;&gt;f(v) = (\alpha(-t, v), h(v))&lt;/math&gt;

then &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; maps &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; into &lt;math display=&quot;inline&quot;&gt;h^{-1}(0) \times \R&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi \circ f = h&lt;/math&gt;. If we define &lt;math display=&quot;inline&quot;&gt;\bar f: h^{-1}(0) \times \R \to Z&lt;/math&gt; as

&lt;math display=&quot;block&quot;&gt;\bar f(v, t) = \alpha(t, v)&lt;/math&gt;

then &lt;math display=&quot;inline&quot;&gt;f \bar f = \bar f f = Id&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; is a homeomorphism.&lt;ref&gt;Mather 2012, pp. 497.&lt;/ref&gt;

== Topology at critical points ==

Theorem: If there is a critical point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; in the singular variety &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt; with critical value &lt;math display=&quot;inline&quot;&gt;v \in (a, b)&lt;/math&gt; then the space &lt;math display=&quot;inline&quot;&gt;X_{\leq b}&lt;/math&gt; is homotopic to&lt;ref&gt;Goresky and MacPherson 1988, pp. 174.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;X_{\leq a} \cup [(D^{\lambda+1}, \partial D^{\lambda+1}) \times (\mathcal{L}_X, \partial \mathcal{L}_X)].&lt;/math&gt;

Proof:&lt;ref&gt;Proof outline comes from Goresky and MacPherson 1988, pp. 174.&lt;/ref&gt;
# &lt;math display=&quot;inline&quot;&gt;(X_{\leq b}, X_{\leq a})&lt;/math&gt; is homeomorphic to &lt;math display=&quot;inline&quot;&gt;(X_{\leq v + \epsilon}, X_{\leq v -\epsilon})&lt;/math&gt;. We can prove this by &quot;moving wall&quot; or Thom's Isotopy Lemma.&lt;ref&gt;Goresky and MacPherson 1988, pp. 90-91, 120.&lt;/ref&gt;
# &lt;math display=&quot;inline&quot;&gt;X_{\leq v + \epsilon}&lt;/math&gt; is homeomorphic to &lt;math display=&quot;inline&quot;&gt;X_{\leq v - \epsilon} \cup (J, K)&lt;/math&gt;, where the latter is the local Morse data for &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;. We do this by moving the wall...&lt;ref&gt;Goresky and MacPherson 1988, pp. 95-96, 120-121.&lt;/ref&gt;
# &lt;math display=&quot;inline&quot;&gt;(J, K)&lt;/math&gt; is homeomorphic to &lt;math display=&quot;inline&quot;&gt;(D^{\lambda+1}, \partial D^{\lambda+1}) \times (\mathcal{L}_X, \partial \mathcal{L}_X)&lt;/math&gt; (tangential data, normal data). Again, moving the wall...&lt;ref&gt;Goresky and MacPherson 1988, pp. 65-66, chapter 8, 121.&lt;/ref&gt;
# The normal Morse data depends only on the differential &lt;math display=&quot;inline&quot;&gt;df(p)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 93.&lt;/ref&gt;
# The normal Morse data has the homotopy type of &lt;math display=&quot;inline&quot;&gt;(\mathcal{L}_X, \partial \mathcal{L}_X)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 169.&lt;/ref&gt;

=== Step 1 ===

We get this immediately(?) by Thom's Isotopy Lemma.

=== Step 2 ===

&lt;ref&gt;Goresky and MacPherson 1988, complex case on pp. 120-121 is extension of real case on pp. 95-96.&lt;/ref&gt;

Step 1 works because &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; is a submersion at each point of the regions we are homeomorphing. This is not the case at critical points. We need some way by which a homeomorphism can pass through a critical point.

To prove a homeomorphism between two subsets &lt;math display=&quot;inline&quot;&gt;A&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;B&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;, we project &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; to some other space &lt;math display=&quot;inline&quot;&gt;N&lt;/math&gt; (in our case &lt;math display=&quot;inline&quot;&gt;\R^n&lt;/math&gt;) using some function &lt;math display=&quot;inline&quot;&gt;F&lt;/math&gt;. We take subsets &lt;math display=&quot;inline&quot;&gt;Y_0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Y_1&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;N&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;A = Z \cap F^{-1}(Y_0)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;B = Z \cap F^{-1}(Y_1)&lt;/math&gt;. We need to prove &lt;math display=&quot;inline&quot;&gt;Y_0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Y_1&lt;/math&gt; are connected by a one-parameter family of regions &lt;math display=&quot;inline&quot;&gt;Y_t&lt;/math&gt; [explain one-parameter family]. The criterion for such a family to exist is that the '''characteristic covectors''' of &lt;math display=&quot;inline&quot;&gt;F&lt;/math&gt; are all nonzero on each stratum of &lt;math display=&quot;inline&quot;&gt;Y_t&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 70.&lt;/ref&gt;

At each point &lt;math display=&quot;inline&quot;&gt;x \in M&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;y \in N&lt;/math&gt; there are '''tangent spaces''' &lt;math display=&quot;inline&quot;&gt;T_xM&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;T_yN&lt;/math&gt;, a vector space whose zero is at the point &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; or &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt; (resp.)

[picture of various tangent spaces]

In the case the &lt;math display=&quot;inline&quot;&gt;N = \R&lt;/math&gt;, the tangent space &lt;math display=&quot;inline&quot;&gt;T_x\R&lt;/math&gt; is just &lt;math display=&quot;inline&quot;&gt;\R&lt;/math&gt; but whose origin is at &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt;.

[picture of T_x\R]

Say &lt;math display=&quot;inline&quot;&gt;F(x) = y&lt;/math&gt;, then the differential of the map &lt;math display=&quot;inline&quot;&gt;F&lt;/math&gt; can be seen as a function whose input is a vector in the tangent space &lt;math display=&quot;inline&quot;&gt;T_xM&lt;/math&gt; and whose output is a vector in the tangent space &lt;math display=&quot;inline&quot;&gt;T_yM&lt;/math&gt;. [If I move this far on the tangent space of M how do I move in the tangent space of N?]

[picture]

[example for M = \R and N = \R?]

A function which takes as input a vector in the tangent space &lt;math display=&quot;inline&quot;&gt;T_xM&lt;/math&gt; (say) and outputs a scalar (usually &lt;math display=&quot;inline&quot;&gt;\R&lt;/math&gt;) is called a '''covector'''. The set of all covectors on &lt;math display=&quot;inline&quot;&gt;T_xM&lt;/math&gt; is called the dual space of &lt;math display=&quot;inline&quot;&gt;T_xM&lt;/math&gt; and is denoted &lt;math display=&quot;inline&quot;&gt;T^*_xM&lt;/math&gt;. There are only a limited number of ways to express a covectors. For example, if our tangent space is two-dimensional then all covectors are of the form &lt;math display=&quot;inline&quot;&gt;ax + by&lt;/math&gt; where &lt;math display=&quot;inline&quot;&gt;(x, y) \in T_xM&lt;/math&gt;.

We take our space &lt;math display=&quot;inline&quot;&gt;M&lt;/math&gt; and map it onto &lt;math display=&quot;inline&quot;&gt;\R^2&lt;/math&gt; with the map &lt;math display=&quot;inline&quot;&gt;F(z) = (r(z), h(z))&lt;/math&gt;, where &lt;math display=&quot;inline&quot;&gt;z \in M&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;r&lt;/math&gt; is the square of the distance of &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt; to the critical point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.

[graph of mapping]

In this case, the covectors on the tangent space &lt;math display=&quot;inline&quot;&gt;T_xM&lt;/math&gt; are of the form &lt;math display=&quot;inline&quot;&gt;adf(x) + bdr(x)&lt;/math&gt; (in this case &lt;math display=&quot;inline&quot;&gt;df&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;dr&lt;/math&gt; are maps to &lt;math display=&quot;inline&quot;&gt;\R&lt;/math&gt;) and on &lt;math display=&quot;inline&quot;&gt;T_y\R^2&lt;/math&gt; are of the form &lt;math display=&quot;inline&quot;&gt;cu + dv&lt;/math&gt; (for &lt;math display=&quot;inline&quot;&gt;(u, v) \in \R^2&lt;/math&gt;). A covector &lt;math display=&quot;inline&quot;&gt;cu + dv \in T^*_{(u, v)}\R^2&lt;/math&gt; is called a '''characteristic covector''' of &lt;math display=&quot;inline&quot;&gt;F&lt;/math&gt; if &lt;math display=&quot;inline&quot;&gt;F(x) = (u, v)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;cdf(x) + ddr(x) = 0&lt;/math&gt; for all vectors in the tangent space of the stratum containing &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 82.&lt;/ref&gt; [explain adf(x) + bdr(x) in terms of this being a function which takes a vector input]

[example of where covectors do and do not vanish on a stratified space, pp. 71?]

What we want is a homeomorphism in &lt;math display=&quot;inline&quot;&gt;M&lt;/math&gt; between the space &lt;math display=&quot;inline&quot;&gt;Z_{\leq \epsilon}&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Z_{\leq \epsilon} \cup B&lt;/math&gt;, where &lt;math display=&quot;inline&quot;&gt;B&lt;/math&gt; is a small region of the critical point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;. The '''local Morse data''' is

&lt;math display=&quot;block&quot;&gt;((B_\delta \cap Z) \cap f^{-1}[v-\epsilon, v+\epsilon], (B_\delta \cap Z) \cap f^{-1}(v-\epsilon))&lt;/math&gt;

where &lt;math display=&quot;inline&quot;&gt;B_\delta&lt;/math&gt; is a closed disc in &lt;math display=&quot;inline&quot;&gt;M&lt;/math&gt; of radius &lt;math display=&quot;inline&quot;&gt;\delta&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 63-64.&lt;/ref&gt; Observe that this is the pair &lt;math display=&quot;inline&quot;&gt;(F^{-1}(\text{Box}(\delta, \epsilon)), F^{-1}(\text{Bottom}(\delta, \epsilon)))&lt;/math&gt;&lt;ref&gt;Goresky and MacPherson 1988, pp. 91.&lt;/ref&gt; [explain Box, Bottom, etc.]

[picture of the two subspaces of Z in M]

We use our map &lt;math display=&quot;inline&quot;&gt;F&lt;/math&gt; to convert these two subspaces to subspaces of &lt;math display=&quot;inline&quot;&gt;\R^2&lt;/math&gt; which are of the form &lt;math display=&quot;inline&quot;&gt;Y_1 = \{(x,y) \in \R^2 | y \leq \epsilon\}&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Y_0 = \{(x,y) \in \R^2 | y \leq -\epsilon\} \cup \{(x,y) \in \R^2 | x \leq \delta, y \leq \epsilon\}&lt;/math&gt;, such that &lt;math display=&quot;inline&quot;&gt;Z_{\leq \epsilon} = F^{-1}(Y_1)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Z_{\leq \epsilon} \cup B = F^{-1}(Y_0)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 95-96.&lt;/ref&gt;

We use a homeomorphism between &lt;math display=&quot;inline&quot;&gt;Y_1&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Y_0&lt;/math&gt; using the technique of &quot;moving the wall&quot; and Thom's Isotopy Lemma. Such a homeomorphism exists when the characteristic covectors of &lt;math display=&quot;inline&quot;&gt;F&lt;/math&gt; are all nonzero on each stratum of &lt;math display=&quot;inline&quot;&gt;Y_t&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, chapter 4, particularly pp. 71-72.&lt;/ref&gt;

Given a smooth mapping between manifolds &lt;math display=&quot;inline&quot;&gt;F: M \to N&lt;/math&gt; (for example, in our case we could have &lt;math display=&quot;inline&quot;&gt;N = \R^2&lt;/math&gt;) and that &lt;math display=&quot;inline&quot;&gt;F|Z: Z \to N&lt;/math&gt; is proper. Let &lt;math display=&quot;inline&quot;&gt;Y \subset N \times \R&lt;/math&gt; be a closed Whitney stratified subset such that the projection to the second factor &lt;math display=&quot;inline&quot;&gt;\pi: Y \to \R&lt;/math&gt; is a proper stratified submersion.&lt;ref&gt;Goresky and MacPherson 1988, pp. 71.&lt;/ref&gt;

Suppose for each &lt;math display=&quot;inline&quot;&gt;t \in \R&lt;/math&gt;, for each &lt;math display=&quot;inline&quot;&gt;p \in F(Z) \cap Y_t&lt;/math&gt;, and for each nonzero characteristic covector &lt;math display=&quot;inline&quot;&gt;\lambda \in T^*_pN&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;F|Z&lt;/math&gt;, the restriction of &lt;math display=&quot;inline&quot;&gt;\lambda&lt;/math&gt; to the subspace &lt;math display=&quot;inline&quot;&gt;T_pS_t = \ker(d\pi(p)) \cap T_pS&lt;/math&gt; is nonzero, where &lt;math display=&quot;inline&quot;&gt;S&lt;/math&gt; is a stratum of &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; which contains &lt;math display=&quot;inline&quot;&gt;(p, t)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;S_t = \pi^{-1}(t) \cap S&lt;/math&gt; is the stratum of &lt;math display=&quot;inline&quot;&gt;Y_t = \pi^{-1}(t) \cap Y&lt;/math&gt; which contains &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;. This is equivalent to the statement that, for each &lt;math display=&quot;inline&quot;&gt;t \in \R&lt;/math&gt;, the restriction &lt;math display=&quot;inline&quot;&gt;F|Z&lt;/math&gt; is transverse to &lt;math display=&quot;inline&quot;&gt;Y_t&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 71-72.&lt;/ref&gt;

This means that, for each &lt;math display=&quot;inline&quot;&gt;t \in \R&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;Z \cap F^{-1}(Y_t)&lt;/math&gt; is stratified by its intersection with the strata of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;...

We finally prove there is a homeomorphism between &lt;math display=&quot;inline&quot;&gt;Z \cap F^{-1}(Y_0) \cong Z \cap F^{-1}(Y_1)&lt;/math&gt; which preserves the Whitney stratification of both sides and is smooth on each stratum.

For the composition

&lt;math display=&quot;block&quot;&gt;Z \times \R \subset M \times \R \to_{F \times I} Y \subset \R^2 \times \R \to_{\pi} \R&lt;/math&gt;

where &lt;math display=&quot;inline&quot;&gt;Y(t, z) = Y_t(z)&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;I&lt;/math&gt; is the identity and &lt;math display=&quot;inline&quot;&gt;\pi&lt;/math&gt; is projection to the second factor. 

&lt;math display=&quot;inline&quot;&gt;Z \times \R&lt;/math&gt; is transverse to &lt;math display=&quot;inline&quot;&gt;(F \times I)^{-1}(Y)&lt;/math&gt;...

The composition &lt;math display=&quot;inline&quot;&gt;\pi \circ (F \times I): Z \times \R \cap (F \times I)^{-1}(Y) \to \R&lt;/math&gt; is a stratified submersion because
* The input domain is stratified as above...,
* We have defined &lt;math display=&quot;inline&quot;&gt;F|Z&lt;/math&gt; to be transverse to &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt;, and therefore it preserves the stratification (unless &lt;math display=&quot;inline&quot;&gt;F(Z) \cap Y = \empty&lt;/math&gt;), and
* We defined above the projection on &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; to be a stratified submersion, meaning it is a submersion on each stratum of &lt;math display=&quot;inline&quot;&gt;F(Z) \cap Y&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 43.&lt;/ref&gt;

Therefore, we can apply Thom's Isotopy Lemma which says there is a homeomorphism between the level sets of &lt;math display=&quot;inline&quot;&gt;Z \times \R&lt;/math&gt;...&lt;ref&gt;Goresky and MacPherson 1988, pp. 72.&lt;/ref&gt;

=== Step 3 ===

==== Characteristic covectors ====

==== Fringed sets ====

When manipulating our domain of integration[?], we need to make sure we are doing this in regions with no characteristic covectors. The introduce the concept of a fringed set, a subset of &lt;math display=&quot;inline&quot;&gt;R^2&lt;/math&gt;, and construct a series of fringed sets which contain no characteristic covectors.

A '''fringed set''' &lt;math display=&quot;inline&quot;&gt;A \subset \R \times \R^+&lt;/math&gt; is an open subset of the first quadrant of &lt;math display=&quot;inline&quot;&gt;\R^2&lt;/math&gt;. &lt;math display=&quot;inline&quot;&gt;A&lt;/math&gt; is fringed over &lt;math display=&quot;inline&quot;&gt;0 &lt; y \ll x&lt;/math&gt; if for some interval &lt;math display=&quot;inline&quot;&gt;S = (0, x)&lt;/math&gt;
# the projection of &lt;math display=&quot;inline&quot;&gt;A&lt;/math&gt; to the first factor is equal to &lt;math display=&quot;inline&quot;&gt;S&lt;/math&gt;,
# &lt;math display=&quot;inline&quot;&gt;A&lt;/math&gt; is open in &lt;math display=&quot;inline&quot;&gt;S \times \R^+&lt;/math&gt;,
# if &lt;math display=&quot;inline&quot;&gt;(s, y) \in A&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;0 &lt; y' \leq y&lt;/math&gt; then &lt;math display=&quot;inline&quot;&gt;(s, y') \in A&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 77.&lt;/ref&gt;

[picture]

The fringed set &lt;math display=&quot;inline&quot;&gt;A^\flat&lt;/math&gt; is the set &lt;math display=&quot;inline&quot;&gt;A&lt;/math&gt; plus its reflection about the &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; axis.&lt;ref&gt;Goresky and MacPherson 1988, pp. 82.&lt;/ref&gt;

[picture]

We build a series of fringed sets which do not contain characteristic covectors, which will be used later in our proof.

There exists a fringed set &lt;math display=&quot;inline&quot;&gt;A_2&lt;/math&gt; of type &lt;math display=&quot;inline&quot;&gt;0 &lt; v \ll u&lt;/math&gt; such that for any &lt;math display=&quot;inline&quot;&gt;z \in Z&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;r\pi(z) \leq r_2&lt;/math&gt;, the map &lt;math display=&quot;inline&quot;&gt;(\rho, f - f\pi)|\pi^{-1}(\pi(z)): \pi^{-1}(\pi(z)) \to \R^2&lt;/math&gt; has no characteristic covectors in &lt;math display=&quot;inline&quot;&gt;A^\flat_2&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 84.&lt;/ref&gt;

Given that the set of points &lt;math display=&quot;inline&quot;&gt;(u, v) \in \R^2&lt;/math&gt; which have a nonzero characteristic covector is closed, then it is enough to prove it for points &lt;math display=&quot;inline&quot;&gt;(u, 0) \in \R^2&lt;/math&gt;. Proof by contradiction. Assume it is false and that there is a sequence of points &lt;math display=&quot;inline&quot;&gt;p_i \in Z \cap f^{-1}(0)&lt;/math&gt; converging to &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;d\rho(p_i)&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;df(p_i)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;df\pi(p_i)&lt;/math&gt; are linearly dependent when restricted to the stratum &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; which contains &lt;math display=&quot;inline&quot;&gt;p_i&lt;/math&gt;. This would mean that &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; has a critical point on &lt;math display=&quot;inline&quot;&gt;Y \cap \partial B_{\rho(p_i)}(p)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 82-83.&lt;/ref&gt;

By restricting to a subsequence if necessary, we may assume the points &lt;math display=&quot;inline&quot;&gt;p_i&lt;/math&gt; are all contained in the same stratum &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt;, that the tangent planes &lt;math display=&quot;inline&quot;&gt;T_{p_i}Y&lt;/math&gt; converge to some plane &lt;math display=&quot;inline&quot;&gt;Q&lt;/math&gt; and the secant lines &lt;math display=&quot;inline&quot;&gt;\mathcal{l}_i = \overline{p_i p}&lt;/math&gt; converge to some line &lt;math display=&quot;inline&quot;&gt;\mathcal{l}&lt;/math&gt;. By the Whitney conditions [how?], &lt;math display=&quot;inline&quot;&gt;Q = \lim_{i \to \infty} \mathcal{l}_i \oplus T_{p_i}(Y \cap \partial B_\delta(p))&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 83.&lt;/ref&gt;

For each &lt;math display=&quot;inline&quot;&gt;i&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;f(p_i) = f(p) = v&lt;/math&gt;, this means[?] &lt;math display=&quot;inline&quot;&gt;df(p)(Q) = 0&lt;/math&gt;. On the assumption that &lt;math display=&quot;inline&quot;&gt;df(p)&lt;/math&gt; is nondegenerate, we may assume &lt;math display=&quot;inline&quot;&gt;Y = X&lt;/math&gt;, so &lt;math display=&quot;inline&quot;&gt;\ker d(f|X)(p_i) = T_{p_i}(X \cap \partial B_\delta(p)) = T_{p_i}(X \cap f^{-1}(v))&lt;/math&gt;, which converges to a subspace &lt;math display=&quot;inline&quot;&gt;\tau&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Q = T_pX&lt;/math&gt;, perpendicular to &lt;math display=&quot;inline&quot;&gt;\mathcal{l}&lt;/math&gt;. However, as &lt;math display=&quot;inline&quot;&gt;f^{-1}(v) \cap X&lt;/math&gt; satisfies Whitney's conditions, &lt;math display=&quot;inline&quot;&gt;\mathcal{l} \subset \tau&lt;/math&gt;, a contradiction.&lt;ref&gt;Goresky and MacPherson 1988, pp. 83.&lt;/ref&gt;

We observe that if &lt;math display=&quot;inline&quot;&gt;df(p)&lt;/math&gt; is a nondegenerate characteristic covector for &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; then it is also a nondegenerate characteristic covector for &lt;math display=&quot;inline&quot;&gt;Z \cap \pi^{-1}(p)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 84.&lt;/ref&gt;

For any &lt;math display=&quot;inline&quot;&gt;a &gt; 0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;b &gt; 0&lt;/math&gt; there exists a fringed set &lt;math display=&quot;inline&quot;&gt;A_3&lt;/math&gt; such that whenever &lt;math display=&quot;inline&quot;&gt;z \in Z&lt;/math&gt; satisfies
# &lt;math display=&quot;inline&quot;&gt;(r(z), f(z)) \in A^\flat_3&lt;/math&gt;,
# &lt;math display=&quot;inline&quot;&gt;(r\pi(z), f\pi(z)) \in A^\flat_3&lt;/math&gt;,
# &lt;math display=&quot;inline&quot;&gt;z \notin X&lt;/math&gt;, and
# &lt;math display=&quot;inline&quot;&gt;\pi(z) \neq p&lt;/math&gt;
then the covectors &lt;math display=&quot;inline&quot;&gt;ad\rho(z) + bdr\pi(z)&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;df(z)&lt;/math&gt;, and &lt;math display=&quot;inline&quot;&gt;df\pi(z)&lt;/math&gt; are linearly independent when restricted to the stratum &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; which contains &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 85.&lt;/ref&gt;

==== Homeomorphism ====

We prove there is a stratum preserving homeomorphism between&lt;ref&gt;Goresky and MacPherson 1988, pp. 65.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;\text{Local Morse Data} \cong (\text{Tangential Morse Data}) \times (\text{Normal Morse Data})&lt;/math&gt;

We first prove that there is a homeomorphism between the product of the normal and tangential Morse data and the '''realisation''' of the following diagram

[diagram from pp. 102]

where realisation means

&lt;math display=&quot;block&quot;&gt;Z \cap (g_1, h_1)^{-1}(P_a) \cap (g_2, h_2)^{-1}(P_b)&lt;/math&gt;

where all the intersections of strata (of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;?) are transverse.&lt;ref&gt;Goresky and MacPherson 1988, pp. 100-102.&lt;/ref&gt;

The realisation of the above diagram is equal to

&lt;math display=&quot;block&quot;&gt;(V_1, V_2) \cap (W_1, W_2) = (V_1 \cap W_1, V_1 \cap W_2 \cup V_2 \cap W_1)&lt;/math&gt;

where

&lt;math display=&quot;block&quot;&gt;V_1 = \{ z \in Z : |f(z) - f\pi(z)| \leq \epsilon/4, r\pi(z) \leq \delta, \rho(z) \leq \delta \}&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;V_2 = \{ z \in Z : f(z) - f\pi(z) = -\epsilon/4, r\pi(z) \leq \delta, \rho(z) \leq \delta \}&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;W_1 = \{ z \in Z : |f\pi(z)| \leq 3\epsilon/4, r\pi(z) \leq \delta \}&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;W_1 = \{ z \in Z : f\pi(z) = -3\epsilon/4, r\pi(z) \leq \delta \}&lt;/math&gt;

where &lt;math display=&quot;inline&quot;&gt;\pi&lt;/math&gt; is the projection from the tubular neighbourhood to &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;r(z)&lt;/math&gt; is the square of the distance between &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt; and the critical point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\rho(z)&lt;/math&gt; is the square of the distance between &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi(z)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 100-101.&lt;/ref&gt; &lt;math display=&quot;inline&quot;&gt;\epsilon \ll \delta&lt;/math&gt; are chosen so that &lt;math display=&quot;inline&quot;&gt;(\delta, \epsilon)&lt;/math&gt; is in the set &lt;math display=&quot;inline&quot;&gt;A^\flat_6&lt;/math&gt; which consists of &lt;math display=&quot;inline&quot;&gt;A_6 \subset \R^+ \times \R^+&lt;/math&gt; with the properties that for &lt;math display=&quot;inline&quot;&gt;(\epsilon, \delta) \in A_6&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;\rho(z) = \delta&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;r\pi(z) = \delta&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;|f(z)| \leq \epsilon&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;|f\pi(z)| \leq \epsilon&lt;/math&gt; then the covectors &lt;math display=&quot;inline&quot;&gt;d\rho(z)&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;dr\pi(z)&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;df(z)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;df\pi(z)&lt;/math&gt; are linearly independent when restricted to &lt;math display=&quot;inline&quot;&gt;T_zY&lt;/math&gt; (where &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; is the stratum containing &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt;). We can prove such a set exists.&lt;ref&gt;Goresky and MacPherson 1988, pp. 89.&lt;/ref&gt; &lt;math display=&quot;inline&quot;&gt;A^\flat_6&lt;/math&gt; is this plus its reflection about the &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; axis.&lt;ref&gt;Goresky and MacPherson 1988, pp. 82.&lt;/ref&gt;

Let &lt;math display=&quot;inline&quot;&gt;D = \{ x \in X | r(x) \leq \delta \}&lt;/math&gt; for stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt;. We will show there is a local trivial fibration of the configuration: &lt;math display=&quot;inline&quot;&gt;(V_1, V_2)&lt;/math&gt; fibres over &lt;math display=&quot;inline&quot;&gt;D&lt;/math&gt; and is homeomorphic to &lt;math display=&quot;inline&quot;&gt;D \times (\text{normal Morse data})&lt;/math&gt;

(V_1, V_2) -&gt; D \times (normal Morse data)
|           /
--&gt; D   &lt;---

and that &lt;math display=&quot;inline&quot;&gt;(W_1, W_2)&lt;/math&gt; fibres over the tangential Morse data and is homeomorphic to &lt;math display=&quot;inline&quot;&gt;(\text{tangential Morse data}) \times (\text{normal slice})&lt;/math&gt;.

For &lt;math display=&quot;inline&quot;&gt;Z_1 = \{ z \in Z : r\pi(z) \leq \delta \}&lt;/math&gt;, the map &lt;math display=&quot;inline&quot;&gt;F(z): Z_1 \to \R^2 = (\rho(z), f(z) - f\pi(z))&lt;/math&gt; is transverse to each stratum of &lt;math display=&quot;inline&quot;&gt;\text{Box}(\delta, \epsilon/4)&lt;/math&gt;, [list], [by lemma 6.5]. &lt;math display=&quot;inline&quot;&gt;(V_1, V_2) = F^{-1}(\text{Box}(\delta, \epsilon/4), \text{Bottom}(\delta, \epsilon/4))&lt;/math&gt;. For each stratum &lt;math display=&quot;inline&quot;&gt;S&lt;/math&gt; of Box and each &lt;math display=&quot;inline&quot;&gt;x \in D&lt;/math&gt;, we have transverse intersection &lt;math display=&quot;inline&quot;&gt;F^{-1}(S) \pitchfork \pi^{-1}(x)&lt;/math&gt;. Therefore, &lt;math display=&quot;inline&quot;&gt;\pi|F^{-1}(S)&lt;/math&gt; is a submersion and by Thom's isotopy lemma the projection &lt;math display=&quot;inline&quot;&gt;\pi|F^{-1}(\text{Box}(\delta, \epsilon/4): F^{-1}(\text{Box}(\delta, \epsilon/4)) \to X&lt;/math&gt; is a stratified fibre bundle over &lt;math display=&quot;inline&quot;&gt;D&lt;/math&gt;. The fibre over the critical point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; is &lt;math display=&quot;inline&quot;&gt;\pi^{-1}(p) \cap (F^{-1}(\text{Box}(\delta, \epsilon/4), F^{-1}(\text{Bottom}(\delta, \epsilon/4))&lt;/math&gt; and is equal to the normal Morse data...&lt;ref&gt;Goresky and MacPherson 1988, pp. 101.&lt;/ref&gt;

Take &lt;math display=&quot;inline&quot;&gt;G: X \to \R^2 = (r(x), f(x))&lt;/math&gt;. &lt;math display=&quot;inline&quot;&gt;\delta&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\epsilon&lt;/math&gt; have been chosen so that &lt;math display=&quot;inline&quot;&gt;(G^{-1}(\text{Box}(\delta, \epsilon/4), G^{-1}(\text{Bottom}(\delta, \epsilon/4))&lt;/math&gt; is the tangential Morse data for &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; and is contained in the region &lt;math display=&quot;inline&quot;&gt;D&lt;/math&gt; over which &lt;math display=&quot;inline&quot;&gt;\pi|(V_1, V_2)&lt;/math&gt; is a stratified fibre bundle. Therefore, &lt;math display=&quot;inline&quot;&gt;(W_1, W_2) = \pi^{-1} G^{-1}(\text{Box}(\delta, \epsilon/4), \text{Bottom}(\delta, \epsilon/4))&lt;/math&gt; is transverse to &lt;math display=&quot;inline&quot;&gt;(V_1, V_2)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 101-102.&lt;/ref&gt;

Finally, this means that &lt;math display=&quot;inline&quot;&gt;(V_1, V_2) \cap (W_1, W_2)&lt;/math&gt; is homeomorphic (by stratum preserving homeomorphism) to &lt;math display=&quot;inline&quot;&gt;(\pi^{-1}(p), \cap (V_1, V_2)) \times \pi(W_1, W_2)&lt;/math&gt;, the product of normal and tangential Morse data.&lt;ref&gt;Goresky and MacPherson 1988, pp. 102.&lt;/ref&gt;

We use a succession of such diagrams to interpolate between the box diagram which defines local Morse data [explain] and the above diagram whose realisation we have just proven is &lt;math display=&quot;inline&quot;&gt;(\text{normal Morse data}) \times (\text{tangential Morse data})&lt;/math&gt;.

[diagram_d0.py]

The realisation is the local Morse data. This is equal to the realisation of the diagram below.&lt;ref&gt;Goresky and MacPherson 1988, pp. 103, 106.&lt;/ref&gt;

[diagram_d11.py]

The realisation of the first diagram [d0] is equivalent to the realisation of the below diagram.

[diagram_d1.py]

In the right-hand picture of the above diagram, we have put a dotted outline around the region &lt;math display=&quot;inline&quot;&gt;A^{\flat}_1&lt;/math&gt;. We prove that there are no characteristic covectors for &lt;math display=&quot;inline&quot;&gt;(r, f): Z \to \R^2&lt;/math&gt; in this region and can, therefore, move the wall in this region...&lt;ref&gt;Goresky and MacPherson 1988, pp. 82-83.&lt;/ref&gt;

By adding a zero-dimensional stratum at the top right corner of the right-hand picture. A one-parameter family of pictures &lt;math display=&quot;inline&quot;&gt;P_b(t)&lt;/math&gt; gives rise to a stratified space &lt;math display=&quot;inline&quot;&gt;Y \subset M \times \R&lt;/math&gt; such that

&lt;math display=&quot;block&quot;&gt;Y = \{ (z, t) \in M \times \R : (r, f)(z) \in P_b(t) \}.&lt;/math&gt;

&lt;math display=&quot;inline&quot;&gt;(r, f)&lt;/math&gt; takes each stratum of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; transversally to each stratum of each &lt;math display=&quot;inline&quot;&gt;Y_t&lt;/math&gt;. &lt;math display=&quot;inline&quot;&gt;(f \circ \pi, f)^{-1}(P_a) = f^{-1}[-\epsilon, \infty)&lt;/math&gt; is transverse to each stratum of &lt;math display=&quot;inline&quot;&gt;Y_t \cap Z&lt;/math&gt;. Therefore, there is a homeomorphism between&lt;ref&gt;Goresky and MacPherson 1988, pp. 107.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;Z(D_1) = Z \cap (f \circ \pi, f)^{-1}(P_a) \cap (r, f)^{-1}(P_b(0))&lt;/math&gt;

and

&lt;math display=&quot;block&quot;&gt;Z(D_1) = Z \cap (f \circ \pi, f)^{-1}(P_a) \cap (r, f)^{-1}(P_b(1)).&lt;/math&gt;

To go from D_2 to D_3 we find the characteristic covectors of &lt;math display=&quot;inline&quot;&gt;(f\pi, f): V \to \R^2&lt;/math&gt; where &lt;math display=&quot;inline&quot;&gt;V = (r, f)^{-1}(P_b(1))&lt;/math&gt;. We stratify &lt;math display=&quot;inline&quot;&gt;P_b(1)&lt;/math&gt; by its interior &lt;math display=&quot;inline&quot;&gt;P&lt;/math&gt; and boundary &lt;math display=&quot;inline&quot;&gt;\partial P&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 107.&lt;/ref&gt;

The strata of &lt;math display=&quot;inline&quot;&gt;V&lt;/math&gt; come in four types:
# &lt;math display=&quot;inline&quot;&gt;(r, f)^{-1}(P) \cap X&lt;/math&gt;
# &lt;math display=&quot;inline&quot;&gt;(r, f)^{-1}(P) \cap Y&lt;/math&gt;
# &lt;math display=&quot;inline&quot;&gt;(r, f)^{-1}(\partial P) \cap X&lt;/math&gt;
# &lt;math display=&quot;inline&quot;&gt;(r, f)^{-1}(\partial P) \cap Y&lt;/math&gt;
where &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; is the strata that contains the critical point and &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; is any other strata such that &lt;math display=&quot;inline&quot;&gt;Y &gt; X&lt;/math&gt;.

All characteristic covectors are of the form &lt;math display=&quot;inline&quot;&gt;\lambda = (u, v, adu + bdv) \in T^*\R^2&lt;/math&gt;.

For strata 1 and 3, the image of &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; under &lt;math display=&quot;inline&quot;&gt;(f\pi, f)&lt;/math&gt; is the diagonal &lt;math display=&quot;inline&quot;&gt;f\pi = f&lt;/math&gt; (dotted outline). Therefore, the characteristic covectors of any point &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt; in &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; are either where &lt;math display=&quot;inline&quot;&gt;z = p&lt;/math&gt;, in which case the covector is zero(?), or where &lt;math display=&quot;inline&quot;&gt;z \neq p&lt;/math&gt;, in which case &lt;math display=&quot;inline&quot;&gt;u = v&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;a = b&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 107-108.&lt;/ref&gt;

For strata 2, being that the critical point is isolated and non-degenerate, which means it, and any neighbourhood, is not zero on any limit of tangent spaces in strata &lt;math display=&quot;inline&quot;&gt;Y &gt; X&lt;/math&gt;. Therefore, &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;f\pi&lt;/math&gt; are linearly independent.&lt;ref&gt;Goresky and MacPherson 1988, pp. 84.&lt;/ref&gt; Unless &lt;math display=&quot;inline&quot;&gt;\pi(z) = p&lt;/math&gt;, in which case &lt;math display=&quot;inline&quot;&gt;d(f\pi)(z) = f\pi(z) = 0&lt;/math&gt;, so they are covectors where &lt;math display=&quot;inline&quot;&gt;u = 0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;b = 0&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 108.&lt;/ref&gt;

For strata 4, we can use implicit function theorem to generate local coordinates &lt;math display=&quot;inline&quot;&gt;y_1, \cdots y_{r-s-1}&lt;/math&gt; in &lt;math display=&quot;inline&quot;&gt;Y &gt; X&lt;/math&gt; and define the Riemannian metric &lt;math display=&quot;inline&quot;&gt;r(z) = r\pi(z) + (f(z) - f\pi(z))^2 + g(y)&lt;/math&gt; for some &lt;math display=&quot;inline&quot;&gt;g&lt;/math&gt; depending only on &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt;.

There are no characteristic covectors in &lt;math display=&quot;inline&quot;&gt;|u| \leq \epsilon&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;|v| &lt; \epsilon&lt;/math&gt;. By [lemma 6.7 and 6.8 and 8.1(d)] &lt;math display=&quot;inline&quot;&gt;df&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;df\pi&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;dr&lt;/math&gt; are linearly independent in this region.&lt;ref&gt;Goresky and MacPherson 1988, pp. 109.&lt;/ref&gt; Given &lt;math display=&quot;inline&quot;&gt;|f| \leq \epsilon&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;|f\pi| \leq \epsilon&lt;/math&gt;, a fringed set &lt;math display=&quot;inline&quot;&gt;A^\flat_4&lt;/math&gt; of type &lt;math display=&quot;inline&quot;&gt;0 &lt; \epsilon \ll \delta&lt;/math&gt; and assume that &lt;math display=&quot;inline&quot;&gt;\pi \neq p&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;z \notin X&lt;/math&gt; then &lt;math display=&quot;inline&quot;&gt;(r(z), f(z)) \in A^\flat_4&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;(r(z), f\pi(z)) \in A^\flat_4&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 87.&lt;/ref&gt;

Outside of these points, the slope of &lt;math display=&quot;inline&quot;&gt;\ker(\lambda)&lt;/math&gt; for any characteristic covector &lt;math display=&quot;inline&quot;&gt;\lambda&lt;/math&gt; is

&lt;math display=&quot;block&quot;&gt;\frac{-a}{b} = \frac{f(z) - f\pi(z) - M}{\frac{\alpha}{\beta} + (f(z) - f\pi(z))}&lt;/math&gt;

for &lt;math display=&quot;inline&quot;&gt;\alpha df + \beta dr = 0&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 108-109.&lt;/ref&gt;

== Morse theory ==

Steps(?)
* Explain topology
* Every point of a stratum is locally like a product structure (proved by Thom's Isotopy Lemma) [GM pp. 41-42]
** Including those around critical points, which are the product of normal and tangential Morse data (these are our quasi-local cycles?)
* Thom's Isotopy Lemma proves a strong deformation retraction (which only stops at critical points) [PWM pp. 541-542]

=== Homotopy ===

We want to replace our domain of convergence &lt;math display=&quot;inline&quot;&gt;M&lt;/math&gt;, which is the complement of our singular variety &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt;, with an &quot;equivalent&quot; space &lt;math display=&quot;inline&quot;&gt;M'&lt;/math&gt; which has better understood properties. We say &quot;equivalent&quot; because there are several different things we could mean by &quot;equivalent&quot; in this context. The equivalence we are referring to in this section is called '''homotopy'''.

Imagine two subspaces &lt;math display=&quot;inline&quot;&gt;\gamma_0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\gamma_1&lt;/math&gt; of a space &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; which are defined respectively by smooth functions &lt;math display=&quot;inline&quot;&gt;f, g: X \to Y&lt;/math&gt;. If there exists a smooth function &lt;math display=&quot;inline&quot;&gt;h_s: X \times [0, 1] \to Y&lt;/math&gt;, called a homotopy, such that &lt;math display=&quot;inline&quot;&gt;h_0 = f&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;h_1 = g&lt;/math&gt; and for any &lt;math display=&quot;inline&quot;&gt;\epsilon &gt; 0&lt;/math&gt; there exists a &lt;math display=&quot;inline&quot;&gt;\delta_a&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\delta_b&lt;/math&gt; such that when &lt;math display=&quot;inline&quot;&gt;|s - s_0| &lt; \delta_a&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;|x - x_0| &lt; \delta_b&lt;/math&gt; we have &lt;math display=&quot;inline&quot;&gt;|h_s(x) - h_{s_0}(x_0)| &lt; \epsilon&lt;/math&gt;, then we say &lt;math display=&quot;inline&quot;&gt;\gamma_0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\gamma_1&lt;/math&gt; are '''homotopic'''.&lt;ref&gt;Henle 1979, pp. 251-252.&lt;/ref&gt;

Below is an example where &lt;math display=&quot;inline&quot;&gt;\gamma_0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\gamma_1&lt;/math&gt; are one-dimensional curves and &lt;math display=&quot;inline&quot;&gt;H(t, s) = h_s(t)&lt;/math&gt;.

[[File:Homotopy_curves.png|300px]]

In [[#Homotopy_equivalence|Appendix A]], we formally prove that we can construct an equivalent space &lt;math display=&quot;inline&quot;&gt;M'&lt;/math&gt;. We provide only an example to give some intuition before describing how to construct the space &lt;math display=&quot;inline&quot;&gt;M'&lt;/math&gt; in terms of local cycles around critical points.

=== Motivating example ===

Imagine a torus and a height function which is just the z value of the point.

[[File:3D-Leveltorus.png|200px]]

It has four critical points: two at the top and bottom of the outer circle (&lt;math display=&quot;inline&quot;&gt;p_1, p_4&lt;/math&gt;) and two at the top and bottom of the inner circle (&lt;math display=&quot;inline&quot;&gt;p_2, p_3&lt;/math&gt;).

[picture]

When the height is between the &lt;math display=&quot;inline&quot;&gt;p_1&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;p_2&lt;/math&gt;, the space is a two-cell, which can be retracted to a point.

[picture]

When the height is between &lt;math display=&quot;inline&quot;&gt;p_2&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;p_3&lt;/math&gt;, the space is a cylinder, which can be retracted to a two-cell with a one-cell attached.

[[File:3D-Cylinder_and_disk_with_handle.png|200px]]

When the height is between &lt;math display=&quot;inline&quot;&gt;p_3&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;p_4&lt;/math&gt;, the space is a torus with a disc removed, which can be retracted to a cylinder with a one-cell attached.

[[File:3D-Cylinder_with_handle_and_torus_with_hole.png|200px]]

When the height is greater than &lt;math display=&quot;inline&quot;&gt;p_4&lt;/math&gt;, then the full torus is constructed by attaching a two-cell.

[Explain in terms of Morse data and Morse index?]

=== Morse data and quasi-local cycles ===

As in the above example, we start at the &quot;bottom&quot; of &lt;math display=&quot;inline&quot;&gt;M&lt;/math&gt; and build upwards until just before we reach our first critical point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.

;Smooth points
:This is a tube around a &lt;math display=&quot;inline&quot;&gt;(d-1)&lt;/math&gt;-chain &lt;math display=&quot;inline&quot;&gt;\gamma&lt;/math&gt; where the height function &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; is maximised at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 223.&lt;/ref&gt;
:For example, if &lt;math display=&quot;inline&quot;&gt;F(x, y) = \frac{1}{1 - x - y}&lt;/math&gt; then &lt;math display=&quot;inline&quot;&gt;\lambda = 1&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;B^\lambda&lt;/math&gt; is an arc reaching its highest point at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.
:The normal plane &lt;math display=&quot;inline&quot;&gt;N&lt;/math&gt; at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; is a plane orthogonal to &lt;math display=&quot;inline&quot;&gt;B^1&lt;/math&gt;(?).
:Its normal link &lt;math display=&quot;inline&quot;&gt;L(S)&lt;/math&gt; is a circle with two points missing where it intersects &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt;.
:We make our quasi-local cycle out of the product of the arc and circle joined to &lt;math display=&quot;inline&quot;&gt;M_-&lt;/math&gt; at points below &lt;math display=&quot;inline&quot;&gt;M_-&lt;/math&gt;.
:With the exception of degenerate points, such as monkey saddles...&lt;ref&gt;e.g. Pemantle, Wilson and Melczer 2024, pp. 211.&lt;/ref&gt;

;Transverse multiple points
:This is the product of a &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;-torus and a &lt;math display=&quot;inline&quot;&gt;(d-k)&lt;/math&gt;-chain &lt;math display=&quot;inline&quot;&gt;\gamma&lt;/math&gt;. The torus is the product of circles about &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; in the complex normal space to each strata which intersects &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;. The chain &lt;math display=&quot;inline&quot;&gt;\gamma&lt;/math&gt; is supported in the stratum which is the common intersection of the varieties defined by the factors vanishing at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;, and achieves its maximum height at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 223-224.&lt;/ref&gt;

;Arrangement multiple point
:This is the product of a &lt;math display=&quot;inline&quot;&gt;(d-k)&lt;/math&gt;-chain &lt;math display=&quot;inline&quot;&gt;\gamma&lt;/math&gt; and several &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;-tori, one for each pair of sheets which intersect transversely, where the torus is the product of circles about &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; in each sheet.&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 226.&lt;/ref&gt;

;Cone point
:A cone point is zero-dimensional so there is no &lt;math display=&quot;inline&quot;&gt;\gamma&lt;/math&gt;, just a &lt;math display=&quot;inline&quot;&gt;d&lt;/math&gt;-torus about &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 227.&lt;/ref&gt;

== Notes ==
{{Reflist}}

== References ==
* {{cite book | last1=Goresky | first1=Mark | last2=MacPherson | first2=Robert | title=Stratified Morse Theory | publisher=Springer-Verlag | year=1988 | url=https://www.math.ias.edu/~goresky/pdf/SMT.djvu }}
* {{cite book | last=Henle | first1=Michael | title=A Combinatorial Introduction to Topology | publisher=Dover Publications Inc. New York | year=1979 }}
* {{citation | last=Mather | first=John | title=Notes on Topological Stability | year=2012 | journal=Bulletin of the American Mathematical Society | volume=49 | number=4 | pages=475-506 | url=https://www.ams.org/journals/bull/2012-49-04/S0273-0979-2012-01383-6/S0273-0979-2012-01383-6.pdf }}.
* {{cite book | last1=Pemantle | first1=Robin | last2=Wilson | first2=Mark C. | last3=Melczer | first3=Stephen | title=Analytic Combinatorics in Several Variables | publisher=Cambridge University Press | year=2024 | edition=2nd | url=https://acsvproject.com/PemantleWilsonMelczer23.pdf }}</text>
      <sha1>buuzod9hry6tgftjysdp9jvnexv6r0g</sha1>
    </revision>
    <revision>
      <id>4676717</id>
      <parentid>4676714</parentid>
      <timestamp>2026-10-18T09:28:45Z</timestamp>
      <contributor>
        <username>Dom walden</username>
        <id>3209423</id>
      </contributor>
      <comment>/* Fringed sets */ Proof of A_3 (incomplete)</comment>
      <origin>4676717</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="63579" sha1="0r9ho48z9kbzihauzkpeheph2svdwjr" xml:space="preserve">== Introduction ==

Morse theory tells us that the topology of M only changes at its critical points.

The &quot;Morse data&quot; tells us the topology at each critical point.

Attaching this Morse data together gives us a space which is homopotically eqivalent to M.

This space is a &quot;cell complex&quot;, which has an easy to calculate homology.

Theorem: Our domain of convergence is homotopic to a cell complex of dimension at most &lt;math display=&quot;inline&quot;&gt;2n - d - 1&lt;/math&gt;.&lt;ref&gt;This is theorem D.23 in Pemantle, Wilson and Melczer 2024, pp. 546. Also theorem in section 1.2*/5.2* in SMT pp. 200.&lt;/ref&gt;

Proof:
# &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; is our entire domain, &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt; our variety
# Project our entire domain to complex projective space &lt;math display=&quot;inline&quot;&gt;Z = \pi(X) \subset \C\mathbb{P}^n - H&lt;/math&gt; [define H]
# Define a linear subspace &lt;math display=&quot;inline&quot;&gt;G \subset \C\mathbb{P}^n&lt;/math&gt; of dimension &lt;math display=&quot;inline&quot;&gt;d - 1&lt;/math&gt;
# Define a Morse function on &lt;math display=&quot;inline&quot;&gt;f: \C\mathbb{P}^n \to \R&lt;/math&gt; which approximates the distance from &lt;math display=&quot;inline&quot;&gt;G&lt;/math&gt; and such that &lt;math display=&quot;inline&quot;&gt;f^{-1}(0) = G&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;f^{-1}(1) = H&lt;/math&gt;
# We &quot;build&quot; &lt;math display=&quot;inline&quot;&gt;X - \mathcal{V}&lt;/math&gt; from &lt;math display=&quot;inline&quot;&gt;\pi^{-1}(G \cap Z) \cap (X - \mathcal{V})&lt;/math&gt; by attaching CW complexes at critical points which are of at most dimension &lt;math display=&quot;inline&quot;&gt;2n - d - 1&lt;/math&gt;
# At a critical point, the normal Morse data is &lt;math display=&quot;inline&quot;&gt;(J, K) = \coprod_x (J_x, K_x)&lt;/math&gt; and the relative complex link is &lt;math display=&quot;inline&quot;&gt;\mathcal{L}^\pi = \coprod_x \mathcal{L}_x&lt;/math&gt;
# We show that the quotient &lt;math display=&quot;inline&quot;&gt;J_x/K_x&lt;/math&gt; is homotopic to a CW complex of dimension &lt;math display=&quot;inline&quot;&gt;\leq 2n - d - 1&lt;/math&gt;
# The neighbourhood of &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; in &lt;math display=&quot;inline&quot;&gt;J_x&lt;/math&gt; is homeomorphic to the cone in &lt;math display=&quot;inline&quot;&gt;L_x(X - \mathcal{V})&lt;/math&gt;, and removing the point &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; increases the homotopy dimension to at most the homotopy dimension of &lt;math display=&quot;inline&quot;&gt;L_x&lt;/math&gt;
# &lt;math display=&quot;inline&quot;&gt;(J_x \cup \{x\}, K_x)&lt;/math&gt; is homotopic to &lt;math display=&quot;inline&quot;&gt;(\text{cone}(\mathcal{L}_x), \mathcal{L}_x)&lt;/math&gt;
# &lt;math display=&quot;inline&quot;&gt;\mathcal{L}_x&lt;/math&gt; is homotopic to a CW complex of dimension at most &lt;math display=&quot;inline&quot;&gt;2n - d - 1&lt;/math&gt;
# The tangential Morse data at the critical point is homotopic to the pair &lt;math display=&quot;inline&quot;&gt;(D^\lambda, \partial D^\lambda)&lt;/math&gt;
# Therefore, at each critical point a space has been added homotopic to a CW complex of dimension at most &lt;math display=&quot;inline&quot;&gt;2n - d - 1&lt;/math&gt;.

Theorem: If &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; is the complement in &lt;math display=&quot;inline&quot;&gt;\C^n&lt;/math&gt; of a complex variety &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt; of dimension &lt;math display=&quot;inline&quot;&gt;d&lt;/math&gt; then &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; is homotopic to a CW complex of dimension at most &lt;math display=&quot;inline&quot;&gt;2n - d - 1&lt;/math&gt;.&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 546.&lt;/ref&gt;

Proof:
# We build &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; by attaching cells of dimension at most &lt;math display=&quot;inline&quot;&gt;2n - d - 1&lt;/math&gt; at each critical point.
## Prove that we can do this without changing the homotopy(?)
## We use Thom's Isotopy Lemma to prove that there is a strong deformation retraction, stopping only at critical points.
# Prove these cells are a product of the normal and tangential Morse data.
## Normal data: &lt;math display=&quot;inline&quot;&gt;(\mathcal{L}(S), \partial \mathcal{L}(S)) \times (D^1, \partial D^1)&lt;/math&gt; [GM pp. 18]
## Tangential data: &lt;math display=&quot;inline&quot;&gt;(B_\delta \cap f^{-1}[v - \epsilon, v + \epsilon], B_\delta \cap f^{-1}(v - \epsilon))&lt;/math&gt; for &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; restricted to &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; (or &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt;?) [GM pp. 63-64]
# If &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt; is the dimension of the strata, then
## If &lt;math display=&quot;inline&quot;&gt;k = d&lt;/math&gt; then it is a smooth point and the cell is the product of &lt;math display=&quot;inline&quot;&gt;S^{2(n-d)-1}&lt;/math&gt; and the tangential data is dimension at most &lt;math display=&quot;inline&quot;&gt;d&lt;/math&gt;.
## If &lt;math display=&quot;inline&quot;&gt;k &lt; d&lt;/math&gt;, ...

&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 547.&lt;/ref&gt;

== Example in one dimension ==

Domain with singularities v_1, v_2, ..., v_i

Define our height function f...

Start with our entire domain X

Reduce from X to X_i+ by using Thom's Isotopy lemma to do a strong deformation retract

== Thom's isotopy lemma ==

We present a modified version of Thom's (first) isotopy lemma, less general than the original but more obviously relevant to our situation.

Theorem: Suppose &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; is a closed subset of a smooth manifold &lt;math display=&quot;inline&quot;&gt;M&lt;/math&gt; which admits a Whitney stratification and &lt;math display=&quot;inline&quot;&gt;h : M \to \R&lt;/math&gt; is a proper Morse function which has no critical values on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;. Then, the level sets of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; are homeomorphic by a homeomorphism that preserves the strata of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;.&lt;ref&gt;For various versions of the full statement of the theorem, see Mather 2012, pp. 499, Goresky and MacPherson 1988, pp. 41, or Pemantle, Wilson and Melczer 2024, pp. 541.&lt;/ref&gt;

Proof:
# Construct control data for &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; compatible with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;.
## [Prop 7.1] If &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; is smooth on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; and is a submersion for each strata then there exists a family of control data for &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; compatible with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 488.&lt;/ref&gt;
# This makes &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; an abstract stratified set and &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; a controlled submersion.
# A controlled submersion has, for any smooth vector field on &lt;math display=&quot;inline&quot;&gt;\R&lt;/math&gt;, a controlled vector field on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; (a &quot;lift&quot;?)&lt;ref&gt;Mather 2012, pp. 493.&lt;/ref&gt;
# A controlled vector field has a unique one-parameter family of homeomorphisms of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; which commute with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 496.&lt;/ref&gt;
# This makes &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; a locally trivial fibration. [Prop 10.2]&lt;ref&gt;Mather 2012, pp. 499.&lt;/ref&gt;

Control data:

A system of '''control data''' for &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; consists of, for each stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;,
* a '''tubular neighbourhood''' &lt;math display=&quot;inline&quot;&gt;T_X&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt;
* a '''tubular projection function''' &lt;math display=&quot;inline&quot;&gt;\pi_X: T_X \to X&lt;/math&gt;, and
* a '''tubular distance function''' &lt;math display=&quot;inline&quot;&gt;\rho_X: T_X \to \R&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;\rho_X^{-1}(0) = X&lt;/math&gt;&lt;ref&gt;Goresky and MacPherson 1988, pp. 42.&lt;/ref&gt;

[illustration]

such that if &lt;math display=&quot;inline&quot;&gt;X &lt; Y&lt;/math&gt; are strata in &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;, then

&lt;math display=&quot;block&quot;&gt;\pi_X \pi_Y(m) = \pi_X(m),&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;\rho_X \pi_Y(m) = \rho_X(m)&lt;/math&gt;

for all &lt;math display=&quot;inline&quot;&gt;m \in |T_X| \cap |T_Y|&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;\pi_Y(m) \in |T_X|&lt;/math&gt;.

If, for all strata &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; and all &lt;math display=&quot;inline&quot;&gt;m \in |T_X|&lt;/math&gt;, we have &lt;math display=&quot;inline&quot;&gt;h \pi_X(m) = h(m)&lt;/math&gt;, then this control data will be said to be compatible with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 488.&lt;/ref&gt;

We prove that if &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; is smooth on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; and is a submersion for each strata then there exists a family of control data for &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; compatible with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 488, prop 7.1.&lt;/ref&gt;

Let &lt;math display=&quot;inline&quot;&gt;Z_k&lt;/math&gt; be the union of strata of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; of dimension less than &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;. We prove by induction on &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;.

To construct the tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T_X&lt;/math&gt; of a stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of dimension less than &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;. For &lt;math display=&quot;inline&quot;&gt;l \leq k&lt;/math&gt;, let &lt;math display=&quot;inline&quot;&gt;U_l&lt;/math&gt; denote the union of all &lt;math display=&quot;inline&quot;&gt;|T_Y|&lt;/math&gt; for &lt;math display=&quot;inline&quot;&gt;Y &lt; X&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\dim Y \geq l&lt;/math&gt;. Let &lt;math display=&quot;inline&quot;&gt;X_l = U_l \cap X&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 489.&lt;/ref&gt;

For &lt;math display=&quot;inline&quot;&gt;l = k&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;X_k = \empty&lt;/math&gt;. Assume by induction that &lt;math display=&quot;inline&quot;&gt;T_{l+1}&lt;/math&gt; has been constructed and that if &lt;math display=&quot;inline&quot;&gt;Y &lt; X&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;\dim Y \geq l + 1&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;m \in |T_{l+1}| \cap |T_Y|&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi_{l+1}(m) \in |T_Y|&lt;/math&gt; (&lt;math display=&quot;inline&quot;&gt;\pi_{l+1} = \pi_{T_{l+1}}&lt;/math&gt;) then&lt;ref&gt;Mather 2012, pp. 489-490.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;\rho_Y \pi_{l+1}(m) = \rho_Y(m),&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;\pi_Y \pi_{l+1}(m) = \pi_Y(m).&lt;/math&gt;

We wish to construct a tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T_{X,Y}&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;|T_Y| \cap X&lt;/math&gt; whose restriction to &lt;math display=&quot;inline&quot;&gt;|T_Y| \cap X_{l+1}&lt;/math&gt; is isomorphic to the restriction of &lt;math display=&quot;inline&quot;&gt;T_{l+1}&lt;/math&gt; such that if &lt;math display=&quot;inline&quot;&gt;m \in |T_{X,Y}| \cap |T_Y|&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi_{X,Y}(m) \in |T_Y|&lt;/math&gt; (&lt;math display=&quot;inline&quot;&gt;\pi_{X,Y} = \pi_{T_{X,Y}}&lt;/math&gt;) then

&lt;math display=&quot;block&quot;&gt;\rho_Y \pi_{X,Y}(m) = \rho_Y(m),&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;\pi_Y \pi_{X,Y}(m) = \pi_Y(m).&lt;/math&gt;

By shrinking &lt;math display=&quot;inline&quot;&gt;|T_Y|&lt;/math&gt; if necessary, this relation is already satisfied if &lt;math display=&quot;inline&quot;&gt;m \in |T_{l+1}| \cap |T_Y|&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi_{l+1}(m) \in |T_Y|&lt;/math&gt; with &lt;math display=&quot;inline&quot;&gt;T_{l+1}&lt;/math&gt; in place of &lt;math display=&quot;inline&quot;&gt;T_{X,Y}&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi_{l+1}&lt;/math&gt; in place of &lt;math display=&quot;inline&quot;&gt;\pi_{X,Y}&lt;/math&gt;. By the definition, if &lt;math display=&quot;inline&quot;&gt;m \in |T_{l+1}|&lt;/math&gt; then there exists &lt;math display=&quot;inline&quot;&gt;Z &lt; X&lt;/math&gt; with &lt;math display=&quot;inline&quot;&gt;\dim Z &gt; l&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;m \in |T_Z|&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi_{l+1}(m) \in |T_Z|&lt;/math&gt;. We have that &lt;math display=&quot;inline&quot;&gt;\pi_{l+1}(m) \in |T_Y| \cap |T_Z|&lt;/math&gt; and therefore &lt;math display=&quot;inline&quot;&gt;Y &lt; Z&lt;/math&gt;. Therefore&lt;ref&gt;Mather 2012, pp. 490.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;\rho_Y \pi_{l+1}(m) = \rho_Y \pi_Z \pi_{l+1}(m) = \rho_Y \pi_Z(m) = \rho_Y(m),&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;\pi_Y \pi_{l+1}(m) = \pi_Y \pi_Z \pi_{l+1}(m) = \pi_Y \pi_Z(m) = \pi_Y(m).&lt;/math&gt;

We can prove that, by shrinking &lt;math display=&quot;inline&quot;&gt;|T_Y|&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;(\rho_Y, \pi_Y): |T_Y| \cap X \to \R \times Y&lt;/math&gt; is a submersion [prop 7.3?] and that &lt;math display=&quot;inline&quot;&gt;T_{X,Y}&lt;/math&gt; is compatible with &lt;math display=&quot;inline&quot;&gt;(\rho_Y, \pi_Y): |T_Y| \cap X_{l+1} \to \R \times Y&lt;/math&gt;, i.e. &lt;math display=&quot;inline&quot;&gt;(\rho_Y, \pi_Y) \pi_{X,Y}(m) = (\rho_Y, \pi_Y)(m)&lt;/math&gt;(?).

To prove it is a submersion, for the tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T = (E, \epsilon, \psi)&lt;/math&gt; there exists a smooth positive function &lt;math display=&quot;inline&quot;&gt;\epsilon'&lt;/math&gt; such that

&lt;math display=&quot;block&quot;&gt;(\rho_T, \pi_T): Y \cap |T|_{\epsilon'}^0 \to \R \times X,&lt;/math&gt;

where &lt;math display=&quot;inline&quot;&gt;|T|_{\epsilon'}^0 = \psi(B_\epsilon \cap B_{\epsilon'})&lt;/math&gt;, is a submersion. If &lt;math display=&quot;inline&quot;&gt;\Sigma&lt;/math&gt; is the set &lt;math display=&quot;inline&quot;&gt;y \in |T|&lt;/math&gt; such that the rank of

&lt;math display=&quot;block&quot;&gt;(\rho_T, \pi_T): T \cap |T| \to \R \times X&lt;/math&gt;

at &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt; is less than &lt;math display=&quot;inline&quot;&gt;\dim(\R \times X)&lt;/math&gt;. We need to prove that for any &lt;math display=&quot;inline&quot;&gt;x \in X&lt;/math&gt; there exists a neighbourhood of &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; which does not intersect with &lt;math display=&quot;inline&quot;&gt;\Sigma&lt;/math&gt;, i.e. the map is not a submersion in this neighbourhood. It follows from [lemma 7.2] that it is enough to prove for &lt;math display=&quot;inline&quot;&gt;M = \R^m&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;X = \R^{m-c} \times 0_c&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;T&lt;/math&gt; is the '''standard tubular neighbourhood'''.&lt;ref&gt;Mather 2012, pp. 489.&lt;/ref&gt;

By standard tubular neighbourhood, we mean the trivial bundle with base &lt;math display=&quot;inline&quot;&gt;\R^{m-c}&lt;/math&gt; and fibre &lt;math display=&quot;inline&quot;&gt;\R^c&lt;/math&gt; where &lt;math display=&quot;inline&quot;&gt;\pi: \R^m \to \R^{m-c}&lt;/math&gt;...&lt;ref&gt;Mather 2012, pp. 488.&lt;/ref&gt;

For &lt;math display=&quot;inline&quot;&gt;y \in |T| - \R^{m-c}&lt;/math&gt;, the kernal of the differential of &lt;math display=&quot;inline&quot;&gt;(\pi_T, \rho_T)&lt;/math&gt; at &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt; is the orthogonal complement of &lt;math display=&quot;inline&quot;&gt;(\R^{m-c} \times 0_c) \oplus \stackrel{\frown}{y \pi_T(y)}&lt;/math&gt; in &lt;math display=&quot;inline&quot;&gt;\R^m&lt;/math&gt;. By the Whitney conditions, we have that for &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt; near &lt;math display=&quot;inline&quot;&gt;\R^{m-c}&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;(\R^{m-c} \times 0_c) \oplus \stackrel{\frown}{y \pi_T(y)}&lt;/math&gt; is close to the set of &lt;math display=&quot;inline&quot;&gt;m - c + 1&lt;/math&gt; planes in &lt;math display=&quot;inline&quot;&gt;m-&lt;/math&gt;space to an &lt;math display=&quot;inline&quot;&gt;m - c + 1&lt;/math&gt; plane in &lt;math display=&quot;inline&quot;&gt;TY_y&lt;/math&gt;. Therefore, for &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt; near enough to &lt;math display=&quot;inline&quot;&gt;\R^{m-c}&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;TY_y&lt;/math&gt; is transverse to the kernal of the differential of &lt;math display=&quot;inline&quot;&gt;(\pi_T, \rho_T)&lt;/math&gt; and, therefore, is a submersion when restricted to &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 489.&lt;/ref&gt;

To prove that &lt;math display=&quot;inline&quot;&gt;T_{X,Y}&lt;/math&gt; is compatible with &lt;math display=&quot;inline&quot;&gt;(\rho_Y, \pi_Y): |T_Y| \cap X_{l+1} \to \R \times Y&lt;/math&gt;...&lt;ref&gt;Mather 2012, pp. 490.&lt;/ref&gt;

Therefore, there exists a tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T_0&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;X_0&lt;/math&gt; satisfying

&lt;math display=&quot;block&quot;&gt;\rho_Y \pi_0(m) = \rho_Y(m),&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;\pi_Y \pi_0(m) = \pi_Y(m).&lt;/math&gt;

From this we can prove that &lt;math display=&quot;inline&quot;&gt;T_0&lt;/math&gt; is compatible with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;. Replacing &lt;math display=&quot;inline&quot;&gt;T_0&lt;/math&gt; with a smaller tubular neighbourhood if necessary we can assume &lt;math display=&quot;inline&quot;&gt;m \in |T_0|&lt;/math&gt; such that for some &lt;math display=&quot;inline&quot;&gt;Y &lt; X&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;m \in |T_Y|&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi_0(m) \in |T_Y|&lt;/math&gt;, then&lt;ref&gt;Mather 2012, pp. 490.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;h \pi_0(m) = h \pi_Y \pi_0(m) = h \pi_Y(m) = h(m).&lt;/math&gt;

By the generalised tubular neighourhood theorem [prop 7.2?], we can replace &lt;math display=&quot;inline&quot;&gt;T_0&lt;/math&gt; with a tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; compatible with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;. This completes the construction of &lt;math display=&quot;inline&quot;&gt;T_X&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 491.&lt;/ref&gt;

This makes &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; an '''abstract stratified set''' with axioms...&lt;ref&gt;Mather 2012, pp. 491-492.&lt;/ref&gt;

This also makes &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; a '''controlled submersion''' because
# &lt;math display=&quot;inline&quot;&gt;h|X: X \to \R&lt;/math&gt; is a smooth submersion on each strata &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;, and
# for each stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; there is a tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T'_X&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;h(v) = h \pi_X(v)&lt;/math&gt; for all &lt;math display=&quot;inline&quot;&gt;v \in T'_X&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 493.&lt;/ref&gt;

The core of this is the concept of a '''vector field'''. A vector field is a function which assigns, for each point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; in a space, a '''vector''', which can be represented by an arrow whose tail starts at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.&lt;ref&gt;Henle 1979, pp. 33.&lt;/ref&gt;

[picture]

Imagine we have a vector field &lt;math display=&quot;inline&quot;&gt;v(x)&lt;/math&gt; defined in a space and draw a line through our space. At each point along this line the vector field assigns a vector. If we move each point in this line along the arrow defined by this vector in the direction of the arrow head. This &quot;flows&quot; the entire line along the vectors.

[picture]

We define a '''stratified vector field''' &lt;math display=&quot;inline&quot;&gt;\eta&lt;/math&gt; on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; to be a family of smooth vector fields &lt;math display=&quot;inline&quot;&gt;\eta_X&lt;/math&gt;, one for each strata &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 493.&lt;/ref&gt;

We define a '''controlled vector field''' &lt;math display=&quot;inline&quot;&gt;\eta&lt;/math&gt; on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; to be a stratified vector field such that for any strata &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; there exists a tubular neighbourhood &lt;math display=&quot;inline&quot;&gt;T'_Y&lt;/math&gt; such that for any &lt;math display=&quot;inline&quot;&gt;X &gt; Y&lt;/math&gt; and any &lt;math display=&quot;inline&quot;&gt;v \in T'_X \cap X&lt;/math&gt;&lt;ref&gt;Mather 2012, pp. 493.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;\eta_X \rho_{Y,X}(v) = 0,&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;(\pi_{Y,X})_* \eta_X(v) = \eta_Y (\pi_{Y,X}(v)).&lt;/math&gt;

We prove that if &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; is a controlled submersion then, for any smooth vector field &lt;math display=&quot;inline&quot;&gt;\zeta&lt;/math&gt; on &lt;math display=&quot;inline&quot;&gt;\R&lt;/math&gt; there is a controlled vector field &lt;math display=&quot;inline&quot;&gt;\eta&lt;/math&gt; on &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;h_* \eta(v) = \zeta(h(v))&lt;/math&gt; for all &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 493.&lt;/ref&gt;

Proceeding by induction on the maximum dimension of the strata of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;, we define &lt;math display=&quot;inline&quot;&gt;Z_k&lt;/math&gt; to be the union of strata of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; of dimension at most &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;. The tubular neighbourhood of &lt;math display=&quot;inline&quot;&gt;Z_k&lt;/math&gt; is the intersection of the tubular neighbourhoods of each strata in &lt;math display=&quot;inline&quot;&gt;Z_k&lt;/math&gt; with &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;. The projection and distance functions are the restrictions of the respective functions of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;.

It is trivially true when the maximum dimension of strata in &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; is zero. Assume it is true for &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt; and construct each &lt;math display=&quot;inline&quot;&gt;\eta_X&lt;/math&gt; separately for each stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of dimension &lt;math display=&quot;inline&quot;&gt;k + 1&lt;/math&gt;.

By the assumption that we have controlled vector fields for all strata &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; of dimension at most &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;, we have the two control conditions defined above for any &lt;math display=&quot;inline&quot;&gt;X &gt; Y&lt;/math&gt; and that there is a neighbourhood &lt;math display=&quot;inline&quot;&gt;T^1_Y&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;h(v) = h \pi_Y(v)&lt;/math&gt; for &lt;math display=&quot;inline&quot;&gt;v \in T^1_Y&lt;/math&gt;.

We want to prove that for all &lt;math display=&quot;inline&quot;&gt;Y &lt; X&lt;/math&gt;, the control conditions are satisfied for all &lt;math display=&quot;inline&quot;&gt;v \in T^2_Y&lt;/math&gt; and that &lt;math display=&quot;inline&quot;&gt;h_*\eta_X(v) = \zeta(v)&lt;/math&gt; for all &lt;math display=&quot;inline&quot;&gt;v \in X&lt;/math&gt;.

Take a point &lt;math display=&quot;inline&quot;&gt;x \in X&lt;/math&gt; and define the set &lt;math display=&quot;inline&quot;&gt;S_v&lt;/math&gt; of strata &lt;math display=&quot;inline&quot;&gt;Y &lt; X&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;v \in T^2_Y&lt;/math&gt;. &lt;math display=&quot;inline&quot;&gt;S_v&lt;/math&gt; is totally ordered since if &lt;math display=&quot;inline&quot;&gt;Y_1&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Y_2&lt;/math&gt; are not comparable then &lt;math display=&quot;inline&quot;&gt;T^2_{Y_1} \cap T^2_{Y_2} = \empty&lt;/math&gt;. Therefore, there is a largest member &lt;math display=&quot;inline&quot;&gt;Y = Y_v&lt;/math&gt;.

Assume the control conditions hold for &lt;math display=&quot;inline&quot;&gt;Y = Y_v&lt;/math&gt;. Then they hold for all &lt;math display=&quot;inline&quot;&gt;Y_i \in S_v&lt;/math&gt;. For, either &lt;math display=&quot;inline&quot;&gt;Y_i = Y&lt;/math&gt; or &lt;math display=&quot;inline&quot;&gt;Y_i &lt; Y&lt;/math&gt;. In the latter case, &lt;math display=&quot;inline&quot;&gt;\pi_Y(v) \in T^1_{Y_i}&lt;/math&gt; (by the choice of &lt;math display=&quot;inline&quot;&gt;T^2_Y&lt;/math&gt;'s [is this why?]. Then

&lt;math display=&quot;block&quot;&gt;\begin{align}
\eta_X(v) \rho_{Y_i,X}(v) &amp;= \eta_X \rho_{Y_i,Y} \pi_{Y,X}(v) \\
&amp;= (\pi_{Y,X})_* \eta_X(v) \rho_{Y_i,Y} \\
&amp;= \eta_Y(\pi_{Y,X}(v)) \rho_{Y_i,Y} \\
&amp;= 0
\end{align}&lt;/math&gt;

and

&lt;math display=&quot;block&quot;&gt;\begin{align}
(\pi_{Y_i,X})_* \eta_X(v) &amp;= (\pi_{Y_i,Y})_* (\pi_{Y,X})_* \eta_X(v) \\
&amp;= (\pi_{Y_i,Y})_* \eta_Y(v) (\pi_{Y,X}) \\
&amp;= \eta_{Y_i}(\pi_{Y_i,Y} \pi_{Y,X}(v)) \\
&amp;= \eta_{Y_i}(\pi_{Y_i,X}(v))
\end{align}&lt;/math&gt;

and, therefore, condition holds for all &lt;math display=&quot;inline&quot;&gt;Y_i \in S_v&lt;/math&gt;. Also,

&lt;math display=&quot;block&quot;&gt;\begin{align}
h_* \eta_X(v) &amp;= (h \circ \pi_{Y,X})_* \eta_X(v) \\
&amp;= h_* \eta_Y (\pi_{Y,X}(v)) \\
&amp;= \zeta(f(v))
\end{align}&lt;/math&gt;

and, therefore, the conclusion of the theorem holds at &lt;math display=&quot;inline&quot;&gt;v&lt;/math&gt;.

This shows we can construct &lt;math display=&quot;inline&quot;&gt;\eta_X&lt;/math&gt; satisfying the control conditions when &lt;math display=&quot;inline&quot;&gt;S_v&lt;/math&gt; is non-empty and satisfying the theorem when &lt;math display=&quot;inline&quot;&gt;S_v&lt;/math&gt; is empty. The set of vectors satisfying these conditions is convex in &lt;math display=&quot;inline&quot;&gt;TX_v&lt;/math&gt;, and so we construct &lt;math display=&quot;inline&quot;&gt;\eta_X&lt;/math&gt; globally via a partition of unity.&lt;ref&gt;Mather 2012, pp. 493-495.&lt;/ref&gt;

Finally, we prove that a controlled vector field has a unique one-parameter family of homeomorphisms of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; which commute with &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt;.&lt;ref&gt;Mather 2012, this combines Proposition 10.1 and Corollary 10.2 on pp. 496 and 497, respectively.&lt;/ref&gt;

For each stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;\eta_X&lt;/math&gt; generates a unique smooth local one-parameter group &lt;math display=&quot;inline&quot;&gt;(J_X, \alpha_X)&lt;/math&gt; of diffeomorphisms of &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; (by standard results of differential geometry), such that &lt;math display=&quot;inline&quot;&gt;\frac{d}{dt} \alpha(t, v)|_{t=0} = \eta_X(v)&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;J_X&lt;/math&gt; is an open subset of &lt;math display=&quot;inline&quot;&gt;\R \times Z&lt;/math&gt;, ...

If we define &lt;math display=&quot;inline&quot;&gt;(J, \alpha)&lt;/math&gt; by

&lt;math display=&quot;block&quot;&gt;J = \bigcup_{X \in S} J_X&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;\alpha = \bigcup_{X \in S} \alpha_X&lt;/math&gt;

we can prove that this is a local one-parameter family of homeomorphisms.&lt;ref&gt;Mather 2012, pp. 496.&lt;/ref&gt;

Firstly, it is clear that
# &lt;math display=&quot;inline&quot;&gt;0 \times Z \subseteq J&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\alpha(0, v) = v&lt;/math&gt; for all &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt;.
# If &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt; then &lt;math display=&quot;inline&quot;&gt;J_v = J \cap (\R \times v) \subseteq \R&lt;/math&gt; is an open interval &lt;math display=&quot;inline&quot;&gt;(a_v, b_v)&lt;/math&gt;, possibly infinite at one or both ends.
# If &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;t, s, t + s&lt;/math&gt; are in &lt;math display=&quot;inline&quot;&gt;(a_v, b_v)&lt;/math&gt; then &lt;math display=&quot;inline&quot;&gt;\alpha(t + s, v) = \alpha(t, \alpha(s, v))&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 495.&lt;/ref&gt;

Secondly, it is clear that &lt;math display=&quot;inline&quot;&gt;\eta&lt;/math&gt; generates &lt;math display=&quot;inline&quot;&gt;\alpha&lt;/math&gt; because
# Each stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; is invariant under &lt;math display=&quot;inline&quot;&gt;\alpha&lt;/math&gt;, i.e. &lt;math display=&quot;inline&quot;&gt;\alpha[J \cap (\R \times X)] \subseteq X&lt;/math&gt;.
# For each &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt;, the map &lt;math display=&quot;inline&quot;&gt;t \to \alpha(t, v)&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;(a_v, b_v)&lt;/math&gt; into the stratum which contains &lt;math display=&quot;inline&quot;&gt;v&lt;/math&gt; is &lt;math display=&quot;inline&quot;&gt;C^1&lt;/math&gt;.
# For any &lt;math display=&quot;inline&quot;&gt;(t, v) \in Z&lt;/math&gt;(?) we have &lt;math display=&quot;inline&quot;&gt;d/dt \alpha(t, v) = \eta(\alpha(t, v))&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 495.&lt;/ref&gt;

It is unique because each &lt;math display=&quot;inline&quot;&gt;(J_X, \alpha_X)&lt;/math&gt; is unique. We just need to prove that &lt;math display=&quot;inline&quot;&gt;J&lt;/math&gt; is open, &lt;math display=&quot;inline&quot;&gt;\alpha&lt;/math&gt; is continuous, and for any &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt; and any compact set &lt;math display=&quot;inline&quot;&gt;K \subseteq Z&lt;/math&gt; there exists &lt;math display=&quot;inline&quot;&gt;\epsilon &gt; 0&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;\alpha(t, v) \notin K&lt;/math&gt; if &lt;math display=&quot;inline&quot;&gt;t \in (a_v, a_v + \epsilon) \cup (b_v - \epsilon, b_v)&lt;/math&gt;.&lt;ref&gt;Mather 2012, pp. 495.&lt;/ref&gt;

For the latter-most condition, if it did not hold then there exists...&lt;ref&gt;Mather 2012, pp. 496-497.&lt;/ref&gt;

We prove there is a homeomorphism &lt;math display=&quot;inline&quot;&gt;f: Z \to h^{-1}(0) \times \R&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;\pi \circ f = h&lt;/math&gt;, where &lt;math display=&quot;inline&quot;&gt;\pi: h^{-1}(0) \times \R \to \R&lt;/math&gt; is projection to the second factor.

For the coordinate vector field &lt;math display=&quot;inline&quot;&gt;\partial&lt;/math&gt; on &lt;math display=&quot;inline&quot;&gt;\R&lt;/math&gt;, by [prop 9.1] there is a controlled vector field &lt;math display=&quot;inline&quot;&gt;\tilde\partial&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;f_* \tilde\partial(v) = \partial(h(v))&lt;/math&gt; for &lt;math display=&quot;inline&quot;&gt;v \in Z&lt;/math&gt;. By [prop 10.1], &lt;math display=&quot;inline&quot;&gt;\tilde\partial&lt;/math&gt; generates a local one-parameter group &lt;math display=&quot;inline&quot;&gt;(J, \alpha)&lt;/math&gt; such that

&lt;math display=&quot;block&quot;&gt;h(\alpha(t,v)) = h(v) + t&lt;/math&gt;

&lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; is proper and [d] holds, so &lt;math display=&quot;inline&quot;&gt;J = \R \times Z&lt;/math&gt;. If we define &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; as

&lt;math display=&quot;block&quot;&gt;f(v) = (\alpha(-t, v), h(v))&lt;/math&gt;

then &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; maps &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; into &lt;math display=&quot;inline&quot;&gt;h^{-1}(0) \times \R&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi \circ f = h&lt;/math&gt;. If we define &lt;math display=&quot;inline&quot;&gt;\bar f: h^{-1}(0) \times \R \to Z&lt;/math&gt; as

&lt;math display=&quot;block&quot;&gt;\bar f(v, t) = \alpha(t, v)&lt;/math&gt;

then &lt;math display=&quot;inline&quot;&gt;f \bar f = \bar f f = Id&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; is a homeomorphism.&lt;ref&gt;Mather 2012, pp. 497.&lt;/ref&gt;

== Topology at critical points ==

Theorem: If there is a critical point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; in the singular variety &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt; with critical value &lt;math display=&quot;inline&quot;&gt;v \in (a, b)&lt;/math&gt; then the space &lt;math display=&quot;inline&quot;&gt;X_{\leq b}&lt;/math&gt; is homotopic to&lt;ref&gt;Goresky and MacPherson 1988, pp. 174.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;X_{\leq a} \cup [(D^{\lambda+1}, \partial D^{\lambda+1}) \times (\mathcal{L}_X, \partial \mathcal{L}_X)].&lt;/math&gt;

Proof:&lt;ref&gt;Proof outline comes from Goresky and MacPherson 1988, pp. 174.&lt;/ref&gt;
# &lt;math display=&quot;inline&quot;&gt;(X_{\leq b}, X_{\leq a})&lt;/math&gt; is homeomorphic to &lt;math display=&quot;inline&quot;&gt;(X_{\leq v + \epsilon}, X_{\leq v -\epsilon})&lt;/math&gt;. We can prove this by &quot;moving wall&quot; or Thom's Isotopy Lemma.&lt;ref&gt;Goresky and MacPherson 1988, pp. 90-91, 120.&lt;/ref&gt;
# &lt;math display=&quot;inline&quot;&gt;X_{\leq v + \epsilon}&lt;/math&gt; is homeomorphic to &lt;math display=&quot;inline&quot;&gt;X_{\leq v - \epsilon} \cup (J, K)&lt;/math&gt;, where the latter is the local Morse data for &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;. We do this by moving the wall...&lt;ref&gt;Goresky and MacPherson 1988, pp. 95-96, 120-121.&lt;/ref&gt;
# &lt;math display=&quot;inline&quot;&gt;(J, K)&lt;/math&gt; is homeomorphic to &lt;math display=&quot;inline&quot;&gt;(D^{\lambda+1}, \partial D^{\lambda+1}) \times (\mathcal{L}_X, \partial \mathcal{L}_X)&lt;/math&gt; (tangential data, normal data). Again, moving the wall...&lt;ref&gt;Goresky and MacPherson 1988, pp. 65-66, chapter 8, 121.&lt;/ref&gt;
# The normal Morse data depends only on the differential &lt;math display=&quot;inline&quot;&gt;df(p)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 93.&lt;/ref&gt;
# The normal Morse data has the homotopy type of &lt;math display=&quot;inline&quot;&gt;(\mathcal{L}_X, \partial \mathcal{L}_X)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 169.&lt;/ref&gt;

=== Step 1 ===

We get this immediately(?) by Thom's Isotopy Lemma.

=== Step 2 ===

&lt;ref&gt;Goresky and MacPherson 1988, complex case on pp. 120-121 is extension of real case on pp. 95-96.&lt;/ref&gt;

Step 1 works because &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; is a submersion at each point of the regions we are homeomorphing. This is not the case at critical points. We need some way by which a homeomorphism can pass through a critical point.

To prove a homeomorphism between two subsets &lt;math display=&quot;inline&quot;&gt;A&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;B&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;, we project &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; to some other space &lt;math display=&quot;inline&quot;&gt;N&lt;/math&gt; (in our case &lt;math display=&quot;inline&quot;&gt;\R^n&lt;/math&gt;) using some function &lt;math display=&quot;inline&quot;&gt;F&lt;/math&gt;. We take subsets &lt;math display=&quot;inline&quot;&gt;Y_0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Y_1&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;N&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;A = Z \cap F^{-1}(Y_0)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;B = Z \cap F^{-1}(Y_1)&lt;/math&gt;. We need to prove &lt;math display=&quot;inline&quot;&gt;Y_0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Y_1&lt;/math&gt; are connected by a one-parameter family of regions &lt;math display=&quot;inline&quot;&gt;Y_t&lt;/math&gt; [explain one-parameter family]. The criterion for such a family to exist is that the '''characteristic covectors''' of &lt;math display=&quot;inline&quot;&gt;F&lt;/math&gt; are all nonzero on each stratum of &lt;math display=&quot;inline&quot;&gt;Y_t&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 70.&lt;/ref&gt;

At each point &lt;math display=&quot;inline&quot;&gt;x \in M&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;y \in N&lt;/math&gt; there are '''tangent spaces''' &lt;math display=&quot;inline&quot;&gt;T_xM&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;T_yN&lt;/math&gt;, a vector space whose zero is at the point &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; or &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt; (resp.)

[picture of various tangent spaces]

In the case the &lt;math display=&quot;inline&quot;&gt;N = \R&lt;/math&gt;, the tangent space &lt;math display=&quot;inline&quot;&gt;T_x\R&lt;/math&gt; is just &lt;math display=&quot;inline&quot;&gt;\R&lt;/math&gt; but whose origin is at &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt;.

[picture of T_x\R]

Say &lt;math display=&quot;inline&quot;&gt;F(x) = y&lt;/math&gt;, then the differential of the map &lt;math display=&quot;inline&quot;&gt;F&lt;/math&gt; can be seen as a function whose input is a vector in the tangent space &lt;math display=&quot;inline&quot;&gt;T_xM&lt;/math&gt; and whose output is a vector in the tangent space &lt;math display=&quot;inline&quot;&gt;T_yM&lt;/math&gt;. [If I move this far on the tangent space of M how do I move in the tangent space of N?]

[picture]

[example for M = \R and N = \R?]

A function which takes as input a vector in the tangent space &lt;math display=&quot;inline&quot;&gt;T_xM&lt;/math&gt; (say) and outputs a scalar (usually &lt;math display=&quot;inline&quot;&gt;\R&lt;/math&gt;) is called a '''covector'''. The set of all covectors on &lt;math display=&quot;inline&quot;&gt;T_xM&lt;/math&gt; is called the dual space of &lt;math display=&quot;inline&quot;&gt;T_xM&lt;/math&gt; and is denoted &lt;math display=&quot;inline&quot;&gt;T^*_xM&lt;/math&gt;. There are only a limited number of ways to express a covectors. For example, if our tangent space is two-dimensional then all covectors are of the form &lt;math display=&quot;inline&quot;&gt;ax + by&lt;/math&gt; where &lt;math display=&quot;inline&quot;&gt;(x, y) \in T_xM&lt;/math&gt;.

We take our space &lt;math display=&quot;inline&quot;&gt;M&lt;/math&gt; and map it onto &lt;math display=&quot;inline&quot;&gt;\R^2&lt;/math&gt; with the map &lt;math display=&quot;inline&quot;&gt;F(z) = (r(z), h(z))&lt;/math&gt;, where &lt;math display=&quot;inline&quot;&gt;z \in M&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;r&lt;/math&gt; is the square of the distance of &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt; to the critical point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.

[graph of mapping]

In this case, the covectors on the tangent space &lt;math display=&quot;inline&quot;&gt;T_xM&lt;/math&gt; are of the form &lt;math display=&quot;inline&quot;&gt;adf(x) + bdr(x)&lt;/math&gt; (in this case &lt;math display=&quot;inline&quot;&gt;df&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;dr&lt;/math&gt; are maps to &lt;math display=&quot;inline&quot;&gt;\R&lt;/math&gt;) and on &lt;math display=&quot;inline&quot;&gt;T_y\R^2&lt;/math&gt; are of the form &lt;math display=&quot;inline&quot;&gt;cu + dv&lt;/math&gt; (for &lt;math display=&quot;inline&quot;&gt;(u, v) \in \R^2&lt;/math&gt;). A covector &lt;math display=&quot;inline&quot;&gt;cu + dv \in T^*_{(u, v)}\R^2&lt;/math&gt; is called a '''characteristic covector''' of &lt;math display=&quot;inline&quot;&gt;F&lt;/math&gt; if &lt;math display=&quot;inline&quot;&gt;F(x) = (u, v)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;cdf(x) + ddr(x) = 0&lt;/math&gt; for all vectors in the tangent space of the stratum containing &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 82.&lt;/ref&gt; [explain adf(x) + bdr(x) in terms of this being a function which takes a vector input]

[example of where covectors do and do not vanish on a stratified space, pp. 71?]

What we want is a homeomorphism in &lt;math display=&quot;inline&quot;&gt;M&lt;/math&gt; between the space &lt;math display=&quot;inline&quot;&gt;Z_{\leq \epsilon}&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Z_{\leq \epsilon} \cup B&lt;/math&gt;, where &lt;math display=&quot;inline&quot;&gt;B&lt;/math&gt; is a small region of the critical point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;. The '''local Morse data''' is

&lt;math display=&quot;block&quot;&gt;((B_\delta \cap Z) \cap f^{-1}[v-\epsilon, v+\epsilon], (B_\delta \cap Z) \cap f^{-1}(v-\epsilon))&lt;/math&gt;

where &lt;math display=&quot;inline&quot;&gt;B_\delta&lt;/math&gt; is a closed disc in &lt;math display=&quot;inline&quot;&gt;M&lt;/math&gt; of radius &lt;math display=&quot;inline&quot;&gt;\delta&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 63-64.&lt;/ref&gt; Observe that this is the pair &lt;math display=&quot;inline&quot;&gt;(F^{-1}(\text{Box}(\delta, \epsilon)), F^{-1}(\text{Bottom}(\delta, \epsilon)))&lt;/math&gt;&lt;ref&gt;Goresky and MacPherson 1988, pp. 91.&lt;/ref&gt; [explain Box, Bottom, etc.]

[picture of the two subspaces of Z in M]

We use our map &lt;math display=&quot;inline&quot;&gt;F&lt;/math&gt; to convert these two subspaces to subspaces of &lt;math display=&quot;inline&quot;&gt;\R^2&lt;/math&gt; which are of the form &lt;math display=&quot;inline&quot;&gt;Y_1 = \{(x,y) \in \R^2 | y \leq \epsilon\}&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Y_0 = \{(x,y) \in \R^2 | y \leq -\epsilon\} \cup \{(x,y) \in \R^2 | x \leq \delta, y \leq \epsilon\}&lt;/math&gt;, such that &lt;math display=&quot;inline&quot;&gt;Z_{\leq \epsilon} = F^{-1}(Y_1)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Z_{\leq \epsilon} \cup B = F^{-1}(Y_0)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 95-96.&lt;/ref&gt;

We use a homeomorphism between &lt;math display=&quot;inline&quot;&gt;Y_1&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;Y_0&lt;/math&gt; using the technique of &quot;moving the wall&quot; and Thom's Isotopy Lemma. Such a homeomorphism exists when the characteristic covectors of &lt;math display=&quot;inline&quot;&gt;F&lt;/math&gt; are all nonzero on each stratum of &lt;math display=&quot;inline&quot;&gt;Y_t&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, chapter 4, particularly pp. 71-72.&lt;/ref&gt;

Given a smooth mapping between manifolds &lt;math display=&quot;inline&quot;&gt;F: M \to N&lt;/math&gt; (for example, in our case we could have &lt;math display=&quot;inline&quot;&gt;N = \R^2&lt;/math&gt;) and that &lt;math display=&quot;inline&quot;&gt;F|Z: Z \to N&lt;/math&gt; is proper. Let &lt;math display=&quot;inline&quot;&gt;Y \subset N \times \R&lt;/math&gt; be a closed Whitney stratified subset such that the projection to the second factor &lt;math display=&quot;inline&quot;&gt;\pi: Y \to \R&lt;/math&gt; is a proper stratified submersion.&lt;ref&gt;Goresky and MacPherson 1988, pp. 71.&lt;/ref&gt;

Suppose for each &lt;math display=&quot;inline&quot;&gt;t \in \R&lt;/math&gt;, for each &lt;math display=&quot;inline&quot;&gt;p \in F(Z) \cap Y_t&lt;/math&gt;, and for each nonzero characteristic covector &lt;math display=&quot;inline&quot;&gt;\lambda \in T^*_pN&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;F|Z&lt;/math&gt;, the restriction of &lt;math display=&quot;inline&quot;&gt;\lambda&lt;/math&gt; to the subspace &lt;math display=&quot;inline&quot;&gt;T_pS_t = \ker(d\pi(p)) \cap T_pS&lt;/math&gt; is nonzero, where &lt;math display=&quot;inline&quot;&gt;S&lt;/math&gt; is a stratum of &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; which contains &lt;math display=&quot;inline&quot;&gt;(p, t)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;S_t = \pi^{-1}(t) \cap S&lt;/math&gt; is the stratum of &lt;math display=&quot;inline&quot;&gt;Y_t = \pi^{-1}(t) \cap Y&lt;/math&gt; which contains &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;. This is equivalent to the statement that, for each &lt;math display=&quot;inline&quot;&gt;t \in \R&lt;/math&gt;, the restriction &lt;math display=&quot;inline&quot;&gt;F|Z&lt;/math&gt; is transverse to &lt;math display=&quot;inline&quot;&gt;Y_t&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 71-72.&lt;/ref&gt;

This means that, for each &lt;math display=&quot;inline&quot;&gt;t \in \R&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;Z \cap F^{-1}(Y_t)&lt;/math&gt; is stratified by its intersection with the strata of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;...

We finally prove there is a homeomorphism between &lt;math display=&quot;inline&quot;&gt;Z \cap F^{-1}(Y_0) \cong Z \cap F^{-1}(Y_1)&lt;/math&gt; which preserves the Whitney stratification of both sides and is smooth on each stratum.

For the composition

&lt;math display=&quot;block&quot;&gt;Z \times \R \subset M \times \R \to_{F \times I} Y \subset \R^2 \times \R \to_{\pi} \R&lt;/math&gt;

where &lt;math display=&quot;inline&quot;&gt;Y(t, z) = Y_t(z)&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;I&lt;/math&gt; is the identity and &lt;math display=&quot;inline&quot;&gt;\pi&lt;/math&gt; is projection to the second factor. 

&lt;math display=&quot;inline&quot;&gt;Z \times \R&lt;/math&gt; is transverse to &lt;math display=&quot;inline&quot;&gt;(F \times I)^{-1}(Y)&lt;/math&gt;...

The composition &lt;math display=&quot;inline&quot;&gt;\pi \circ (F \times I): Z \times \R \cap (F \times I)^{-1}(Y) \to \R&lt;/math&gt; is a stratified submersion because
* The input domain is stratified as above...,
* We have defined &lt;math display=&quot;inline&quot;&gt;F|Z&lt;/math&gt; to be transverse to &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt;, and therefore it preserves the stratification (unless &lt;math display=&quot;inline&quot;&gt;F(Z) \cap Y = \empty&lt;/math&gt;), and
* We defined above the projection on &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; to be a stratified submersion, meaning it is a submersion on each stratum of &lt;math display=&quot;inline&quot;&gt;F(Z) \cap Y&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 43.&lt;/ref&gt;

Therefore, we can apply Thom's Isotopy Lemma which says there is a homeomorphism between the level sets of &lt;math display=&quot;inline&quot;&gt;Z \times \R&lt;/math&gt;...&lt;ref&gt;Goresky and MacPherson 1988, pp. 72.&lt;/ref&gt;

=== Step 3 ===

==== Characteristic covectors ====

==== Fringed sets ====

When manipulating our domain of integration[?], we need to make sure we are doing this in regions with no characteristic covectors. The introduce the concept of a fringed set, a subset of &lt;math display=&quot;inline&quot;&gt;R^2&lt;/math&gt;, and construct a series of fringed sets which contain no characteristic covectors.

A '''fringed set''' &lt;math display=&quot;inline&quot;&gt;A \subset \R \times \R^+&lt;/math&gt; is an open subset of the first quadrant of &lt;math display=&quot;inline&quot;&gt;\R^2&lt;/math&gt;. &lt;math display=&quot;inline&quot;&gt;A&lt;/math&gt; is fringed over &lt;math display=&quot;inline&quot;&gt;0 &lt; y \ll x&lt;/math&gt; if for some interval &lt;math display=&quot;inline&quot;&gt;S = (0, x)&lt;/math&gt;
# the projection of &lt;math display=&quot;inline&quot;&gt;A&lt;/math&gt; to the first factor is equal to &lt;math display=&quot;inline&quot;&gt;S&lt;/math&gt;,
# &lt;math display=&quot;inline&quot;&gt;A&lt;/math&gt; is open in &lt;math display=&quot;inline&quot;&gt;S \times \R^+&lt;/math&gt;,
# if &lt;math display=&quot;inline&quot;&gt;(s, y) \in A&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;0 &lt; y' \leq y&lt;/math&gt; then &lt;math display=&quot;inline&quot;&gt;(s, y') \in A&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 77.&lt;/ref&gt;

[picture]

The fringed set &lt;math display=&quot;inline&quot;&gt;A^\flat&lt;/math&gt; is the set &lt;math display=&quot;inline&quot;&gt;A&lt;/math&gt; plus its reflection about the &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; axis.&lt;ref&gt;Goresky and MacPherson 1988, pp. 82.&lt;/ref&gt;

[picture]

We build a series of fringed sets which do not contain characteristic covectors, which will be used later in our proof.

There exists a fringed set &lt;math display=&quot;inline&quot;&gt;A_2&lt;/math&gt; of type &lt;math display=&quot;inline&quot;&gt;0 &lt; v \ll u&lt;/math&gt; such that for any &lt;math display=&quot;inline&quot;&gt;z \in Z&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;r\pi(z) \leq r_2&lt;/math&gt;, the map &lt;math display=&quot;inline&quot;&gt;(\rho, f - f\pi)|\pi^{-1}(\pi(z)): \pi^{-1}(\pi(z)) \to \R^2&lt;/math&gt; has no characteristic covectors in &lt;math display=&quot;inline&quot;&gt;A^\flat_2&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 84.&lt;/ref&gt;

Given that the set of points &lt;math display=&quot;inline&quot;&gt;(u, v) \in \R^2&lt;/math&gt; which have a nonzero characteristic covector is closed, then it is enough to prove it for points &lt;math display=&quot;inline&quot;&gt;(u, 0) \in \R^2&lt;/math&gt;. Proof by contradiction. Assume it is false and that there is a sequence of points &lt;math display=&quot;inline&quot;&gt;p_i \in Z \cap f^{-1}(0)&lt;/math&gt; converging to &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;d\rho(p_i)&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;df(p_i)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;df\pi(p_i)&lt;/math&gt; are linearly dependent when restricted to the stratum &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; which contains &lt;math display=&quot;inline&quot;&gt;p_i&lt;/math&gt;. This would mean that &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; has a critical point on &lt;math display=&quot;inline&quot;&gt;Y \cap \partial B_{\rho(p_i)}(p)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 82-83.&lt;/ref&gt;

By restricting to a subsequence if necessary, we may assume the points &lt;math display=&quot;inline&quot;&gt;p_i&lt;/math&gt; are all contained in the same stratum &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt;, that the tangent planes &lt;math display=&quot;inline&quot;&gt;T_{p_i}Y&lt;/math&gt; converge to some plane &lt;math display=&quot;inline&quot;&gt;Q&lt;/math&gt; and the secant lines &lt;math display=&quot;inline&quot;&gt;\mathcal{l}_i = \overline{p_i p}&lt;/math&gt; converge to some line &lt;math display=&quot;inline&quot;&gt;\mathcal{l}&lt;/math&gt;. By the Whitney conditions [how?], &lt;math display=&quot;inline&quot;&gt;Q = \lim_{i \to \infty} \mathcal{l}_i \oplus T_{p_i}(Y \cap \partial B_\delta(p))&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 83.&lt;/ref&gt;

For each &lt;math display=&quot;inline&quot;&gt;i&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;f(p_i) = f(p) = v&lt;/math&gt;, this means[?] &lt;math display=&quot;inline&quot;&gt;df(p)(Q) = 0&lt;/math&gt;. On the assumption that &lt;math display=&quot;inline&quot;&gt;df(p)&lt;/math&gt; is nondegenerate, we may assume &lt;math display=&quot;inline&quot;&gt;Y = X&lt;/math&gt;, so &lt;math display=&quot;inline&quot;&gt;\ker d(f|X)(p_i) = T_{p_i}(X \cap \partial B_\delta(p)) = T_{p_i}(X \cap f^{-1}(v))&lt;/math&gt;, which converges to a subspace &lt;math display=&quot;inline&quot;&gt;\tau&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;Q = T_pX&lt;/math&gt;, perpendicular to &lt;math display=&quot;inline&quot;&gt;\mathcal{l}&lt;/math&gt;. However, as &lt;math display=&quot;inline&quot;&gt;f^{-1}(v) \cap X&lt;/math&gt; satisfies Whitney's conditions, &lt;math display=&quot;inline&quot;&gt;\mathcal{l} \subset \tau&lt;/math&gt;, a contradiction.&lt;ref&gt;Goresky and MacPherson 1988, pp. 83.&lt;/ref&gt;

We observe that if &lt;math display=&quot;inline&quot;&gt;df(p)&lt;/math&gt; is a nondegenerate characteristic covector for &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; then it is also a nondegenerate characteristic covector for &lt;math display=&quot;inline&quot;&gt;Z \cap \pi^{-1}(p)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 84.&lt;/ref&gt;

For any &lt;math display=&quot;inline&quot;&gt;a &gt; 0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;b &gt; 0&lt;/math&gt; there exists a fringed set &lt;math display=&quot;inline&quot;&gt;A_3&lt;/math&gt; such that whenever &lt;math display=&quot;inline&quot;&gt;z \in Z&lt;/math&gt; satisfies
# &lt;math display=&quot;inline&quot;&gt;(r(z), f(z)) \in A^\flat_3&lt;/math&gt;,
# &lt;math display=&quot;inline&quot;&gt;(r\pi(z), f\pi(z)) \in A^\flat_3&lt;/math&gt;,
# &lt;math display=&quot;inline&quot;&gt;z \notin X&lt;/math&gt;, and
# &lt;math display=&quot;inline&quot;&gt;\pi(z) \neq p&lt;/math&gt;
then the covectors &lt;math display=&quot;inline&quot;&gt;ad\rho(z) + bdr\pi(z)&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;df(z)&lt;/math&gt;, and &lt;math display=&quot;inline&quot;&gt;df\pi(z)&lt;/math&gt; are linearly independent when restricted to the stratum &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; which contains &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 85.&lt;/ref&gt;

Proof by contradiction. If we assume not, then by the Whitney conditions the points &lt;math display=&quot;inline&quot;&gt;z \in Z&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;ad\rho(z) + bdr\pi(z)&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;df(z)&lt;/math&gt;, and &lt;math display=&quot;inline&quot;&gt;df\pi(z)&lt;/math&gt; are linearly dependent form a close subset of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;. By Cauchy[?], this means there is a sequence &lt;math display=&quot;inline&quot;&gt;z_i \in Z&lt;/math&gt; which converge to the critical point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;f(z_i) = 0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;f\pi(z_i) = 0&lt;/math&gt; and the covectors &lt;math display=&quot;inline&quot;&gt;ad\rho(z_i) + bdr\pi(z_i)&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;df(z_i)&lt;/math&gt;, and &lt;math display=&quot;inline&quot;&gt;df\pi(z_i)&lt;/math&gt; are linearly dependent for all &lt;math display=&quot;inline&quot;&gt;i&lt;/math&gt;. By choosing a subsequence if necessary, we may assume that all &lt;math display=&quot;inline&quot;&gt;z_i&lt;/math&gt; lie in the same stratum &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt;, that the secant lines &lt;math display=&quot;inline&quot;&gt;\overline{p z_i}&lt;/math&gt; converge to a line &lt;math display=&quot;inline&quot;&gt;\mathcal{l}&lt;/math&gt;, that the tangent planes &lt;math display=&quot;inline&quot;&gt;T_{z_i}Y&lt;/math&gt; converge to some plane &lt;math display=&quot;inline&quot;&gt;\tau&lt;/math&gt;, and that the subspaces &lt;math display=&quot;inline&quot;&gt;\ker(ad\rho(z_i) + bdr\pi(z_i))&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;\ker(df(z_i))&lt;/math&gt;, and &lt;math display=&quot;inline&quot;&gt;\ker(df\pi(z_i))&lt;/math&gt; converge to subspaces &lt;math display=&quot;inline&quot;&gt;A&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;B&lt;/math&gt;, and &lt;math display=&quot;inline&quot;&gt;C&lt;/math&gt; of &lt;math display=&quot;inline&quot;&gt;\tau&lt;/math&gt;, respectively.&lt;ref&gt;Goresky and MacPherson 1988, pp. 85.&lt;/ref&gt;

[Necessity of Riemannian metric?]

&lt;math display=&quot;inline&quot;&gt;\mathcal{l}&lt;/math&gt; is perpendicular to &lt;math display=&quot;inline&quot;&gt;A&lt;/math&gt;, so &lt;math display=&quot;inline&quot;&gt;\mathcal{l} \nsubseteq A&lt;/math&gt;. But, on the assumption of linear dependence of the covectors, &lt;math display=&quot;inline&quot;&gt;B + C \subset A&lt;/math&gt;, and we show that &lt;math display=&quot;inline&quot;&gt;\mathcal{l} \subset B&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\mathcal{l} \subset C&lt;/math&gt; to prove a contradiction.

==== Homeomorphism ====

We prove there is a stratum preserving homeomorphism between&lt;ref&gt;Goresky and MacPherson 1988, pp. 65.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;\text{Local Morse Data} \cong (\text{Tangential Morse Data}) \times (\text{Normal Morse Data})&lt;/math&gt;

We first prove that there is a homeomorphism between the product of the normal and tangential Morse data and the '''realisation''' of the following diagram

[diagram from pp. 102]

where realisation means

&lt;math display=&quot;block&quot;&gt;Z \cap (g_1, h_1)^{-1}(P_a) \cap (g_2, h_2)^{-1}(P_b)&lt;/math&gt;

where all the intersections of strata (of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;?) are transverse.&lt;ref&gt;Goresky and MacPherson 1988, pp. 100-102.&lt;/ref&gt;

The realisation of the above diagram is equal to

&lt;math display=&quot;block&quot;&gt;(V_1, V_2) \cap (W_1, W_2) = (V_1 \cap W_1, V_1 \cap W_2 \cup V_2 \cap W_1)&lt;/math&gt;

where

&lt;math display=&quot;block&quot;&gt;V_1 = \{ z \in Z : |f(z) - f\pi(z)| \leq \epsilon/4, r\pi(z) \leq \delta, \rho(z) \leq \delta \}&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;V_2 = \{ z \in Z : f(z) - f\pi(z) = -\epsilon/4, r\pi(z) \leq \delta, \rho(z) \leq \delta \}&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;W_1 = \{ z \in Z : |f\pi(z)| \leq 3\epsilon/4, r\pi(z) \leq \delta \}&lt;/math&gt;
&lt;math display=&quot;block&quot;&gt;W_1 = \{ z \in Z : f\pi(z) = -3\epsilon/4, r\pi(z) \leq \delta \}&lt;/math&gt;

where &lt;math display=&quot;inline&quot;&gt;\pi&lt;/math&gt; is the projection from the tubular neighbourhood to &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;r(z)&lt;/math&gt; is the square of the distance between &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt; and the critical point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\rho(z)&lt;/math&gt; is the square of the distance between &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\pi(z)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 100-101.&lt;/ref&gt; &lt;math display=&quot;inline&quot;&gt;\epsilon \ll \delta&lt;/math&gt; are chosen so that &lt;math display=&quot;inline&quot;&gt;(\delta, \epsilon)&lt;/math&gt; is in the set &lt;math display=&quot;inline&quot;&gt;A^\flat_6&lt;/math&gt; which consists of &lt;math display=&quot;inline&quot;&gt;A_6 \subset \R^+ \times \R^+&lt;/math&gt; with the properties that for &lt;math display=&quot;inline&quot;&gt;(\epsilon, \delta) \in A_6&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt; such that &lt;math display=&quot;inline&quot;&gt;\rho(z) = \delta&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;r\pi(z) = \delta&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;|f(z)| \leq \epsilon&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;|f\pi(z)| \leq \epsilon&lt;/math&gt; then the covectors &lt;math display=&quot;inline&quot;&gt;d\rho(z)&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;dr\pi(z)&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;df(z)&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;df\pi(z)&lt;/math&gt; are linearly independent when restricted to &lt;math display=&quot;inline&quot;&gt;T_zY&lt;/math&gt; (where &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; is the stratum containing &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt;). We can prove such a set exists.&lt;ref&gt;Goresky and MacPherson 1988, pp. 89.&lt;/ref&gt; &lt;math display=&quot;inline&quot;&gt;A^\flat_6&lt;/math&gt; is this plus its reflection about the &lt;math display=&quot;inline&quot;&gt;x&lt;/math&gt; axis.&lt;ref&gt;Goresky and MacPherson 1988, pp. 82.&lt;/ref&gt;

Let &lt;math display=&quot;inline&quot;&gt;D = \{ x \in X | r(x) \leq \delta \}&lt;/math&gt; for stratum &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt;. We will show there is a local trivial fibration of the configuration: &lt;math display=&quot;inline&quot;&gt;(V_1, V_2)&lt;/math&gt; fibres over &lt;math display=&quot;inline&quot;&gt;D&lt;/math&gt; and is homeomorphic to &lt;math display=&quot;inline&quot;&gt;D \times (\text{normal Morse data})&lt;/math&gt;

(V_1, V_2) -&gt; D \times (normal Morse data)
|           /
--&gt; D   &lt;---

and that &lt;math display=&quot;inline&quot;&gt;(W_1, W_2)&lt;/math&gt; fibres over the tangential Morse data and is homeomorphic to &lt;math display=&quot;inline&quot;&gt;(\text{tangential Morse data}) \times (\text{normal slice})&lt;/math&gt;.

For &lt;math display=&quot;inline&quot;&gt;Z_1 = \{ z \in Z : r\pi(z) \leq \delta \}&lt;/math&gt;, the map &lt;math display=&quot;inline&quot;&gt;F(z): Z_1 \to \R^2 = (\rho(z), f(z) - f\pi(z))&lt;/math&gt; is transverse to each stratum of &lt;math display=&quot;inline&quot;&gt;\text{Box}(\delta, \epsilon/4)&lt;/math&gt;, [list], [by lemma 6.5]. &lt;math display=&quot;inline&quot;&gt;(V_1, V_2) = F^{-1}(\text{Box}(\delta, \epsilon/4), \text{Bottom}(\delta, \epsilon/4))&lt;/math&gt;. For each stratum &lt;math display=&quot;inline&quot;&gt;S&lt;/math&gt; of Box and each &lt;math display=&quot;inline&quot;&gt;x \in D&lt;/math&gt;, we have transverse intersection &lt;math display=&quot;inline&quot;&gt;F^{-1}(S) \pitchfork \pi^{-1}(x)&lt;/math&gt;. Therefore, &lt;math display=&quot;inline&quot;&gt;\pi|F^{-1}(S)&lt;/math&gt; is a submersion and by Thom's isotopy lemma the projection &lt;math display=&quot;inline&quot;&gt;\pi|F^{-1}(\text{Box}(\delta, \epsilon/4): F^{-1}(\text{Box}(\delta, \epsilon/4)) \to X&lt;/math&gt; is a stratified fibre bundle over &lt;math display=&quot;inline&quot;&gt;D&lt;/math&gt;. The fibre over the critical point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; is &lt;math display=&quot;inline&quot;&gt;\pi^{-1}(p) \cap (F^{-1}(\text{Box}(\delta, \epsilon/4), F^{-1}(\text{Bottom}(\delta, \epsilon/4))&lt;/math&gt; and is equal to the normal Morse data...&lt;ref&gt;Goresky and MacPherson 1988, pp. 101.&lt;/ref&gt;

Take &lt;math display=&quot;inline&quot;&gt;G: X \to \R^2 = (r(x), f(x))&lt;/math&gt;. &lt;math display=&quot;inline&quot;&gt;\delta&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\epsilon&lt;/math&gt; have been chosen so that &lt;math display=&quot;inline&quot;&gt;(G^{-1}(\text{Box}(\delta, \epsilon/4), G^{-1}(\text{Bottom}(\delta, \epsilon/4))&lt;/math&gt; is the tangential Morse data for &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; and is contained in the region &lt;math display=&quot;inline&quot;&gt;D&lt;/math&gt; over which &lt;math display=&quot;inline&quot;&gt;\pi|(V_1, V_2)&lt;/math&gt; is a stratified fibre bundle. Therefore, &lt;math display=&quot;inline&quot;&gt;(W_1, W_2) = \pi^{-1} G^{-1}(\text{Box}(\delta, \epsilon/4), \text{Bottom}(\delta, \epsilon/4))&lt;/math&gt; is transverse to &lt;math display=&quot;inline&quot;&gt;(V_1, V_2)&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 101-102.&lt;/ref&gt;

Finally, this means that &lt;math display=&quot;inline&quot;&gt;(V_1, V_2) \cap (W_1, W_2)&lt;/math&gt; is homeomorphic (by stratum preserving homeomorphism) to &lt;math display=&quot;inline&quot;&gt;(\pi^{-1}(p), \cap (V_1, V_2)) \times \pi(W_1, W_2)&lt;/math&gt;, the product of normal and tangential Morse data.&lt;ref&gt;Goresky and MacPherson 1988, pp. 102.&lt;/ref&gt;

We use a succession of such diagrams to interpolate between the box diagram which defines local Morse data [explain] and the above diagram whose realisation we have just proven is &lt;math display=&quot;inline&quot;&gt;(\text{normal Morse data}) \times (\text{tangential Morse data})&lt;/math&gt;.

[diagram_d0.py]

The realisation is the local Morse data. This is equal to the realisation of the diagram below.&lt;ref&gt;Goresky and MacPherson 1988, pp. 103, 106.&lt;/ref&gt;

[diagram_d11.py]

The realisation of the first diagram [d0] is equivalent to the realisation of the below diagram.

[diagram_d1.py]

In the right-hand picture of the above diagram, we have put a dotted outline around the region &lt;math display=&quot;inline&quot;&gt;A^{\flat}_1&lt;/math&gt;. We prove that there are no characteristic covectors for &lt;math display=&quot;inline&quot;&gt;(r, f): Z \to \R^2&lt;/math&gt; in this region and can, therefore, move the wall in this region...&lt;ref&gt;Goresky and MacPherson 1988, pp. 82-83.&lt;/ref&gt;

By adding a zero-dimensional stratum at the top right corner of the right-hand picture. A one-parameter family of pictures &lt;math display=&quot;inline&quot;&gt;P_b(t)&lt;/math&gt; gives rise to a stratified space &lt;math display=&quot;inline&quot;&gt;Y \subset M \times \R&lt;/math&gt; such that

&lt;math display=&quot;block&quot;&gt;Y = \{ (z, t) \in M \times \R : (r, f)(z) \in P_b(t) \}.&lt;/math&gt;

&lt;math display=&quot;inline&quot;&gt;(r, f)&lt;/math&gt; takes each stratum of &lt;math display=&quot;inline&quot;&gt;Z&lt;/math&gt; transversally to each stratum of each &lt;math display=&quot;inline&quot;&gt;Y_t&lt;/math&gt;. &lt;math display=&quot;inline&quot;&gt;(f \circ \pi, f)^{-1}(P_a) = f^{-1}[-\epsilon, \infty)&lt;/math&gt; is transverse to each stratum of &lt;math display=&quot;inline&quot;&gt;Y_t \cap Z&lt;/math&gt;. Therefore, there is a homeomorphism between&lt;ref&gt;Goresky and MacPherson 1988, pp. 107.&lt;/ref&gt;

&lt;math display=&quot;block&quot;&gt;Z(D_1) = Z \cap (f \circ \pi, f)^{-1}(P_a) \cap (r, f)^{-1}(P_b(0))&lt;/math&gt;

and

&lt;math display=&quot;block&quot;&gt;Z(D_1) = Z \cap (f \circ \pi, f)^{-1}(P_a) \cap (r, f)^{-1}(P_b(1)).&lt;/math&gt;

To go from D_2 to D_3 we find the characteristic covectors of &lt;math display=&quot;inline&quot;&gt;(f\pi, f): V \to \R^2&lt;/math&gt; where &lt;math display=&quot;inline&quot;&gt;V = (r, f)^{-1}(P_b(1))&lt;/math&gt;. We stratify &lt;math display=&quot;inline&quot;&gt;P_b(1)&lt;/math&gt; by its interior &lt;math display=&quot;inline&quot;&gt;P&lt;/math&gt; and boundary &lt;math display=&quot;inline&quot;&gt;\partial P&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 107.&lt;/ref&gt;

The strata of &lt;math display=&quot;inline&quot;&gt;V&lt;/math&gt; come in four types:
# &lt;math display=&quot;inline&quot;&gt;(r, f)^{-1}(P) \cap X&lt;/math&gt;
# &lt;math display=&quot;inline&quot;&gt;(r, f)^{-1}(P) \cap Y&lt;/math&gt;
# &lt;math display=&quot;inline&quot;&gt;(r, f)^{-1}(\partial P) \cap X&lt;/math&gt;
# &lt;math display=&quot;inline&quot;&gt;(r, f)^{-1}(\partial P) \cap Y&lt;/math&gt;
where &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; is the strata that contains the critical point and &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; is any other strata such that &lt;math display=&quot;inline&quot;&gt;Y &gt; X&lt;/math&gt;.

All characteristic covectors are of the form &lt;math display=&quot;inline&quot;&gt;\lambda = (u, v, adu + bdv) \in T^*\R^2&lt;/math&gt;.

For strata 1 and 3, the image of &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; under &lt;math display=&quot;inline&quot;&gt;(f\pi, f)&lt;/math&gt; is the diagonal &lt;math display=&quot;inline&quot;&gt;f\pi = f&lt;/math&gt; (dotted outline). Therefore, the characteristic covectors of any point &lt;math display=&quot;inline&quot;&gt;z&lt;/math&gt; in &lt;math display=&quot;inline&quot;&gt;X&lt;/math&gt; are either where &lt;math display=&quot;inline&quot;&gt;z = p&lt;/math&gt;, in which case the covector is zero(?), or where &lt;math display=&quot;inline&quot;&gt;z \neq p&lt;/math&gt;, in which case &lt;math display=&quot;inline&quot;&gt;u = v&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;a = b&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 107-108.&lt;/ref&gt;

For strata 2, being that the critical point is isolated and non-degenerate, which means it, and any neighbourhood, is not zero on any limit of tangent spaces in strata &lt;math display=&quot;inline&quot;&gt;Y &gt; X&lt;/math&gt;. Therefore, &lt;math display=&quot;inline&quot;&gt;f&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;f\pi&lt;/math&gt; are linearly independent.&lt;ref&gt;Goresky and MacPherson 1988, pp. 84.&lt;/ref&gt; Unless &lt;math display=&quot;inline&quot;&gt;\pi(z) = p&lt;/math&gt;, in which case &lt;math display=&quot;inline&quot;&gt;d(f\pi)(z) = f\pi(z) = 0&lt;/math&gt;, so they are covectors where &lt;math display=&quot;inline&quot;&gt;u = 0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;b = 0&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 108.&lt;/ref&gt;

For strata 4, we can use implicit function theorem to generate local coordinates &lt;math display=&quot;inline&quot;&gt;y_1, \cdots y_{r-s-1}&lt;/math&gt; in &lt;math display=&quot;inline&quot;&gt;Y &gt; X&lt;/math&gt; and define the Riemannian metric &lt;math display=&quot;inline&quot;&gt;r(z) = r\pi(z) + (f(z) - f\pi(z))^2 + g(y)&lt;/math&gt; for some &lt;math display=&quot;inline&quot;&gt;g&lt;/math&gt; depending only on &lt;math display=&quot;inline&quot;&gt;y&lt;/math&gt;.

There are no characteristic covectors in &lt;math display=&quot;inline&quot;&gt;|u| \leq \epsilon&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;|v| &lt; \epsilon&lt;/math&gt;. By [lemma 6.7 and 6.8 and 8.1(d)] &lt;math display=&quot;inline&quot;&gt;df&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;df\pi&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;dr&lt;/math&gt; are linearly independent in this region.&lt;ref&gt;Goresky and MacPherson 1988, pp. 109.&lt;/ref&gt; Given &lt;math display=&quot;inline&quot;&gt;|f| \leq \epsilon&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;|f\pi| \leq \epsilon&lt;/math&gt;, a fringed set &lt;math display=&quot;inline&quot;&gt;A^\flat_4&lt;/math&gt; of type &lt;math display=&quot;inline&quot;&gt;0 &lt; \epsilon \ll \delta&lt;/math&gt; and assume that &lt;math display=&quot;inline&quot;&gt;\pi \neq p&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;z \notin X&lt;/math&gt; then &lt;math display=&quot;inline&quot;&gt;(r(z), f(z)) \in A^\flat_4&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;(r(z), f\pi(z)) \in A^\flat_4&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 87.&lt;/ref&gt;

Outside of these points, the slope of &lt;math display=&quot;inline&quot;&gt;\ker(\lambda)&lt;/math&gt; for any characteristic covector &lt;math display=&quot;inline&quot;&gt;\lambda&lt;/math&gt; is

&lt;math display=&quot;block&quot;&gt;\frac{-a}{b} = \frac{f(z) - f\pi(z) - M}{\frac{\alpha}{\beta} + (f(z) - f\pi(z))}&lt;/math&gt;

for &lt;math display=&quot;inline&quot;&gt;\alpha df + \beta dr = 0&lt;/math&gt;.&lt;ref&gt;Goresky and MacPherson 1988, pp. 108-109.&lt;/ref&gt;

== Morse theory ==

Steps(?)
* Explain topology
* Every point of a stratum is locally like a product structure (proved by Thom's Isotopy Lemma) [GM pp. 41-42]
** Including those around critical points, which are the product of normal and tangential Morse data (these are our quasi-local cycles?)
* Thom's Isotopy Lemma proves a strong deformation retraction (which only stops at critical points) [PWM pp. 541-542]

=== Homotopy ===

We want to replace our domain of convergence &lt;math display=&quot;inline&quot;&gt;M&lt;/math&gt;, which is the complement of our singular variety &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt;, with an &quot;equivalent&quot; space &lt;math display=&quot;inline&quot;&gt;M'&lt;/math&gt; which has better understood properties. We say &quot;equivalent&quot; because there are several different things we could mean by &quot;equivalent&quot; in this context. The equivalence we are referring to in this section is called '''homotopy'''.

Imagine two subspaces &lt;math display=&quot;inline&quot;&gt;\gamma_0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\gamma_1&lt;/math&gt; of a space &lt;math display=&quot;inline&quot;&gt;Y&lt;/math&gt; which are defined respectively by smooth functions &lt;math display=&quot;inline&quot;&gt;f, g: X \to Y&lt;/math&gt;. If there exists a smooth function &lt;math display=&quot;inline&quot;&gt;h_s: X \times [0, 1] \to Y&lt;/math&gt;, called a homotopy, such that &lt;math display=&quot;inline&quot;&gt;h_0 = f&lt;/math&gt;, &lt;math display=&quot;inline&quot;&gt;h_1 = g&lt;/math&gt; and for any &lt;math display=&quot;inline&quot;&gt;\epsilon &gt; 0&lt;/math&gt; there exists a &lt;math display=&quot;inline&quot;&gt;\delta_a&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\delta_b&lt;/math&gt; such that when &lt;math display=&quot;inline&quot;&gt;|s - s_0| &lt; \delta_a&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;|x - x_0| &lt; \delta_b&lt;/math&gt; we have &lt;math display=&quot;inline&quot;&gt;|h_s(x) - h_{s_0}(x_0)| &lt; \epsilon&lt;/math&gt;, then we say &lt;math display=&quot;inline&quot;&gt;\gamma_0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\gamma_1&lt;/math&gt; are '''homotopic'''.&lt;ref&gt;Henle 1979, pp. 251-252.&lt;/ref&gt;

Below is an example where &lt;math display=&quot;inline&quot;&gt;\gamma_0&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\gamma_1&lt;/math&gt; are one-dimensional curves and &lt;math display=&quot;inline&quot;&gt;H(t, s) = h_s(t)&lt;/math&gt;.

[[File:Homotopy_curves.png|300px]]

In [[#Homotopy_equivalence|Appendix A]], we formally prove that we can construct an equivalent space &lt;math display=&quot;inline&quot;&gt;M'&lt;/math&gt;. We provide only an example to give some intuition before describing how to construct the space &lt;math display=&quot;inline&quot;&gt;M'&lt;/math&gt; in terms of local cycles around critical points.

=== Motivating example ===

Imagine a torus and a height function which is just the z value of the point.

[[File:3D-Leveltorus.png|200px]]

It has four critical points: two at the top and bottom of the outer circle (&lt;math display=&quot;inline&quot;&gt;p_1, p_4&lt;/math&gt;) and two at the top and bottom of the inner circle (&lt;math display=&quot;inline&quot;&gt;p_2, p_3&lt;/math&gt;).

[picture]

When the height is between the &lt;math display=&quot;inline&quot;&gt;p_1&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;p_2&lt;/math&gt;, the space is a two-cell, which can be retracted to a point.

[picture]

When the height is between &lt;math display=&quot;inline&quot;&gt;p_2&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;p_3&lt;/math&gt;, the space is a cylinder, which can be retracted to a two-cell with a one-cell attached.

[[File:3D-Cylinder_and_disk_with_handle.png|200px]]

When the height is between &lt;math display=&quot;inline&quot;&gt;p_3&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;p_4&lt;/math&gt;, the space is a torus with a disc removed, which can be retracted to a cylinder with a one-cell attached.

[[File:3D-Cylinder_with_handle_and_torus_with_hole.png|200px]]

When the height is greater than &lt;math display=&quot;inline&quot;&gt;p_4&lt;/math&gt;, then the full torus is constructed by attaching a two-cell.

[Explain in terms of Morse data and Morse index?]

=== Morse data and quasi-local cycles ===

As in the above example, we start at the &quot;bottom&quot; of &lt;math display=&quot;inline&quot;&gt;M&lt;/math&gt; and build upwards until just before we reach our first critical point &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.

;Smooth points
:This is a tube around a &lt;math display=&quot;inline&quot;&gt;(d-1)&lt;/math&gt;-chain &lt;math display=&quot;inline&quot;&gt;\gamma&lt;/math&gt; where the height function &lt;math display=&quot;inline&quot;&gt;h&lt;/math&gt; is maximised at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 223.&lt;/ref&gt;
:For example, if &lt;math display=&quot;inline&quot;&gt;F(x, y) = \frac{1}{1 - x - y}&lt;/math&gt; then &lt;math display=&quot;inline&quot;&gt;\lambda = 1&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;B^\lambda&lt;/math&gt; is an arc reaching its highest point at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.
:The normal plane &lt;math display=&quot;inline&quot;&gt;N&lt;/math&gt; at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; is a plane orthogonal to &lt;math display=&quot;inline&quot;&gt;B^1&lt;/math&gt;(?).
:Its normal link &lt;math display=&quot;inline&quot;&gt;L(S)&lt;/math&gt; is a circle with two points missing where it intersects &lt;math display=&quot;inline&quot;&gt;\mathcal{V}&lt;/math&gt;.
:We make our quasi-local cycle out of the product of the arc and circle joined to &lt;math display=&quot;inline&quot;&gt;M_-&lt;/math&gt; at points below &lt;math display=&quot;inline&quot;&gt;M_-&lt;/math&gt;.
:With the exception of degenerate points, such as monkey saddles...&lt;ref&gt;e.g. Pemantle, Wilson and Melczer 2024, pp. 211.&lt;/ref&gt;

;Transverse multiple points
:This is the product of a &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;-torus and a &lt;math display=&quot;inline&quot;&gt;(d-k)&lt;/math&gt;-chain &lt;math display=&quot;inline&quot;&gt;\gamma&lt;/math&gt;. The torus is the product of circles about &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; in the complex normal space to each strata which intersects &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;. The chain &lt;math display=&quot;inline&quot;&gt;\gamma&lt;/math&gt; is supported in the stratum which is the common intersection of the varieties defined by the factors vanishing at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;, and achieves its maximum height at &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 223-224.&lt;/ref&gt;

;Arrangement multiple point
:This is the product of a &lt;math display=&quot;inline&quot;&gt;(d-k)&lt;/math&gt;-chain &lt;math display=&quot;inline&quot;&gt;\gamma&lt;/math&gt; and several &lt;math display=&quot;inline&quot;&gt;k&lt;/math&gt;-tori, one for each pair of sheets which intersect transversely, where the torus is the product of circles about &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt; in each sheet.&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 226.&lt;/ref&gt;

;Cone point
:A cone point is zero-dimensional so there is no &lt;math display=&quot;inline&quot;&gt;\gamma&lt;/math&gt;, just a &lt;math display=&quot;inline&quot;&gt;d&lt;/math&gt;-torus about &lt;math display=&quot;inline&quot;&gt;p&lt;/math&gt;.&lt;ref&gt;Pemantle, Wilson and Melczer 2024, pp. 227.&lt;/ref&gt;

== Notes ==
{{Reflist}}

== References ==
* {{cite book | last1=Goresky | first1=Mark | last2=MacPherson | first2=Robert | title=Stratified Morse Theory | publisher=Springer-Verlag | year=1988 | url=https://www.math.ias.edu/~goresky/pdf/SMT.djvu }}
* {{cite book | last=Henle | first1=Michael | title=A Combinatorial Introduction to Topology | publisher=Dover Publications Inc. New York | year=1979 }}
* {{citation | last=Mather | first=John | title=Notes on Topological Stability | year=2012 | journal=Bulletin of the American Mathematical Society | volume=49 | number=4 | pages=475-506 | url=https://www.ams.org/journals/bull/2012-49-04/S0273-0979-2012-01383-6/S0273-0979-2012-01383-6.pdf }}.
* {{cite book | last1=Pemantle | first1=Robin | last2=Wilson | first2=Mark C. | last3=Melczer | first3=Stephen | title=Analytic Combinatorics in Several Variables | publisher=Cambridge University Press | year=2024 | edition=2nd | url=https://acsvproject.com/PemantleWilsonMelczer23.pdf }}</text>
      <sha1>0r9ho48z9kbzihauzkpeheph2svdwjr</sha1>
    </revision>
  </page>
  <page>
    <title>Cookbook:Akpu</title>
    <ns>102</ns>
    <id>483707</id>
    <revision>
      <id>4676530</id>
      <parentid>4655335</parentid>
      <timestamp>2026-10-17T14:21:52Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* Ingredients */</comment>
      <origin>4676530</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1858" sha1="kik4r6p96vicgcu810huv37eg7hv8t8" xml:space="preserve">{{recipe
|title=Akpu
|image=
|caption=Traditional fermented cassava swallow from southeastern Nigeria
|servings=6
|time=4 days
|difficulty=2
|course=Main course
|cuisine=Igbo cuisine
}}

{{Incomplete recipe|reason=missing appropriate linking, missing templates, missing/incorrect categories, broken links}}

'''Akpu''' is a traditional swallow made from fermented cassava and widely consumed in southeastern Nigeria. It is a staple food among the Igbo people and is commonly served with soups such as onugbu soup, ora soup, oha soup, and egusi soup. The fermentation process gives Akpu its characteristic texture and flavour.

== Ingredients ==
* 5 kg fresh cassava tubers
* [[Cookbook:Water|Water]]

== Procedure ==
# Peel the cassava tubers and wash thoroughly.
# Place the cassava in a container and cover completely with water.
# Allow it to ferment for 3–4 days or until softened.
# Remove any fibres and hard portions from the fermented cassava.
# Mash the cassava and sieve to obtain a smooth paste.
# Suspend the paste in a clean cloth or sack and allow excess water to drain.
# Transfer the fermented cassava paste into a pot.
# Cook over medium heat while stirring continuously until a smooth, stretchy dough forms.
# Shape into portions and serve hot with soup.

== Notes, tips, and variations ==
* The duration of fermentation may vary depending on temperature.
* Akpu is traditionally wrapped in leaves or packaged in nylon before sale.
* Proper fermentation helps reduce the natural cyanide content of cassava.
* Similar cassava-based swallows are consumed in various parts of West and Central Africa.

== See also ==
* [[Garri]]
* [[Cassava]]
* [[Oha soup]]
* [[Onugbu soup]]
* [[Igbo cuisine]]

[[Category:Nigerian cuisine]]
[[Category:African recipes]]
[[Category:Igbo cuisine]]
[[Category:Cassava dishes]]
[[Category:Main course recipes]]</text>
      <sha1>kik4r6p96vicgcu810huv37eg7hv8t8</sha1>
    </revision>
  </page>
  <page>
    <title>Cookbook:Efo Riro</title>
    <ns>102</ns>
    <id>483732</id>
    <revision>
      <id>4676532</id>
      <parentid>4638519</parentid>
      <timestamp>2026-10-17T14:26:09Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* Equipment */</comment>
      <origin>4676532</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2155" sha1="b3r0bpqe3vu9kn5l0oizhc76wby7tv2" xml:space="preserve">{{Recipe summary
| Cuisine = Efo riro
| Origin = Western Nigeria
| Servings = 6
| Time = 1 hr 40 minutes
| Difficulty = 2
| Image = [[File:Efo Riro - Veggies.jpg|300px]]
}}{{Incomplete recipe|reason=missing recipe header template, missing appropriate linking, missing/incorrect categories, what kind of palm oil is it?}}
'''Efo Riro''' is a popular Yoruba vegetable soup made with leafy vegetables, palm oil, peppers, and assorted meats or fish. It is commonly eaten with swallows such as amala, pounded yam, or eba.

== Equipment ==
* [[Cookbook: Stock Pot|Cooking pot]] (medium or large)
* Wooden spoon or cooking spatula
* Knife
* Cutting board
* Blender or grinding stone (for pepper mix)
* Bowl (for washing vegetables)
* Stove or heat source

== Ingredients ==
* 2 bunches spinach or ugu (pumpkin leaves), chopped
* 500 g assorted meat (beef, goat meat, or chicken)
* 200 g stockfish, soaked
* 200 g dried fish, cleaned
* 1 cup palm oil
* 3–4 fresh red bell peppers (tatashe)
* 2–3 scotch bonnet peppers (ata rodo), to taste
* 1 medium onion
* 2 tablespoons ground crayfish
* 2 seasoning cubes
* Salt, to taste
* Ogiri (optional, for traditional flavor)
== Procedure ==
#Wash and cook the assorted meat with onion, seasoning cubes, and salt until tender.
#Add stockfish and continue cooking until soft.
#Blend the peppers and onion into a smooth or slightly coarse paste.
#Heat palm oil in a pot (do not bleach).
#Add the blended pepper mix and fry for about 10–15 minutes until it reduces and thickens.
#Add the cooked meat, stockfish, dried fish, and meat stock.
#Stir and allow to simmer for 10 minutes.
#Add ground crayfish and ogiri if using.
#Add chopped vegetables and stir gently.
#Allow to cook for 3–5 minutes (do not overcook the vegetables).
#Adjust seasoning with salt or seasoning cubes.
#Remove from heat and serve hot.
== Tips ==
* Do not overcook the vegetables to preserve color and nutrients.
* The pepper base should be well fried for rich flavor.
* Efo Riro is best served with amala, eba, or pounded yam.
[[Category:Yoruba cuisine]] [[Category:Nigerian soups]] [[Category:Vegetable dishes]] [[Category:Palm oil dishes]]</text>
      <sha1>b3r0bpqe3vu9kn5l0oizhc76wby7tv2</sha1>
    </revision>
    <revision>
      <id>4676533</id>
      <parentid>4676532</parentid>
      <timestamp>2026-10-17T14:26:54Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* Equipment */</comment>
      <origin>4676533</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2182" sha1="e3lzf3gaei1awnuuyaajpw65se6ga1b" xml:space="preserve">{{Recipe summary
| Cuisine = Efo riro
| Origin = Western Nigeria
| Servings = 6
| Time = 1 hr 40 minutes
| Difficulty = 2
| Image = [[File:Efo Riro - Veggies.jpg|300px]]
}}{{Incomplete recipe|reason=missing recipe header template, missing appropriate linking, missing/incorrect categories, what kind of palm oil is it?}}
'''Efo Riro''' is a popular Yoruba vegetable soup made with leafy vegetables, palm oil, peppers, and assorted meats or fish. It is commonly eaten with swallows such as amala, pounded yam, or eba.

== Equipment ==
* [[Cookbook: Stock Pot|Cooking pot]] (medium or large)
* [[Cookbook: Wooden Spoon|Wooden spoon]] or cooking spatula
* Knife
* Cutting board
* Blender or grinding stone (for pepper mix)
* Bowl (for washing vegetables)
* Stove or heat source

== Ingredients ==
* 2 bunches spinach or ugu (pumpkin leaves), chopped
* 500 g assorted meat (beef, goat meat, or chicken)
* 200 g stockfish, soaked
* 200 g dried fish, cleaned
* 1 cup palm oil
* 3–4 fresh red bell peppers (tatashe)
* 2–3 scotch bonnet peppers (ata rodo), to taste
* 1 medium onion
* 2 tablespoons ground crayfish
* 2 seasoning cubes
* Salt, to taste
* Ogiri (optional, for traditional flavor)
== Procedure ==
#Wash and cook the assorted meat with onion, seasoning cubes, and salt until tender.
#Add stockfish and continue cooking until soft.
#Blend the peppers and onion into a smooth or slightly coarse paste.
#Heat palm oil in a pot (do not bleach).
#Add the blended pepper mix and fry for about 10–15 minutes until it reduces and thickens.
#Add the cooked meat, stockfish, dried fish, and meat stock.
#Stir and allow to simmer for 10 minutes.
#Add ground crayfish and ogiri if using.
#Add chopped vegetables and stir gently.
#Allow to cook for 3–5 minutes (do not overcook the vegetables).
#Adjust seasoning with salt or seasoning cubes.
#Remove from heat and serve hot.
== Tips ==
* Do not overcook the vegetables to preserve color and nutrients.
* The pepper base should be well fried for rich flavor.
* Efo Riro is best served with amala, eba, or pounded yam.
[[Category:Yoruba cuisine]] [[Category:Nigerian soups]] [[Category:Vegetable dishes]] [[Category:Palm oil dishes]]</text>
      <sha1>e3lzf3gaei1awnuuyaajpw65se6ga1b</sha1>
    </revision>
    <revision>
      <id>4676547</id>
      <parentid>4676533</parentid>
      <timestamp>2026-10-17T15:20:24Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* Equipment */</comment>
      <origin>4676547</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2202" sha1="mav3p0qfg336ryjuip1o8ijs4bv6mow" xml:space="preserve">{{Recipe summary
| Cuisine = Efo riro
| Origin = Western Nigeria
| Servings = 6
| Time = 1 hr 40 minutes
| Difficulty = 2
| Image = [[File:Efo Riro - Veggies.jpg|300px]]
}}{{Incomplete recipe|reason=missing recipe header template, missing appropriate linking, missing/incorrect categories, what kind of palm oil is it?}}
'''Efo Riro''' is a popular Yoruba vegetable soup made with leafy vegetables, palm oil, peppers, and assorted meats or fish. It is commonly eaten with swallows such as amala, pounded yam, or eba.

== Equipment ==
* [[Cookbook: Stock Pot|Cooking pot]] (medium or large)
* [[Cookbook: Wooden Spoon|Wooden spoon]] or cooking spatula
* [[Cookbook: Knife|Knife]]
* Cutting board
* Blender or grinding stone (for pepper mix)
* Bowl (for washing vegetables)
* Stove or heat source

== Ingredients ==
* 2 bunches spinach or ugu (pumpkin leaves), chopped
* 500 g assorted meat (beef, goat meat, or chicken)
* 200 g stockfish, soaked
* 200 g dried fish, cleaned
* 1 cup palm oil
* 3–4 fresh red bell peppers (tatashe)
* 2–3 scotch bonnet peppers (ata rodo), to taste
* 1 medium onion
* 2 tablespoons ground crayfish
* 2 seasoning cubes
* Salt, to taste
* Ogiri (optional, for traditional flavor)
== Procedure ==
#Wash and cook the assorted meat with onion, seasoning cubes, and salt until tender.
#Add stockfish and continue cooking until soft.
#Blend the peppers and onion into a smooth or slightly coarse paste.
#Heat palm oil in a pot (do not bleach).
#Add the blended pepper mix and fry for about 10–15 minutes until it reduces and thickens.
#Add the cooked meat, stockfish, dried fish, and meat stock.
#Stir and allow to simmer for 10 minutes.
#Add ground crayfish and ogiri if using.
#Add chopped vegetables and stir gently.
#Allow to cook for 3–5 minutes (do not overcook the vegetables).
#Adjust seasoning with salt or seasoning cubes.
#Remove from heat and serve hot.
== Tips ==
* Do not overcook the vegetables to preserve color and nutrients.
* The pepper base should be well fried for rich flavor.
* Efo Riro is best served with amala, eba, or pounded yam.
[[Category:Yoruba cuisine]] [[Category:Nigerian soups]] [[Category:Vegetable dishes]] [[Category:Palm oil dishes]]</text>
      <sha1>mav3p0qfg336ryjuip1o8ijs4bv6mow</sha1>
    </revision>
    <revision>
      <id>4676549</id>
      <parentid>4676547</parentid>
      <timestamp>2026-10-17T15:22:19Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* Equipment */</comment>
      <origin>4676549</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2230" sha1="8lv9zc4253t1ok95r0ci4zn4fw3keu0" xml:space="preserve">{{Recipe summary
| Cuisine = Efo riro
| Origin = Western Nigeria
| Servings = 6
| Time = 1 hr 40 minutes
| Difficulty = 2
| Image = [[File:Efo Riro - Veggies.jpg|300px]]
}}{{Incomplete recipe|reason=missing recipe header template, missing appropriate linking, missing/incorrect categories, what kind of palm oil is it?}}
'''Efo Riro''' is a popular Yoruba vegetable soup made with leafy vegetables, palm oil, peppers, and assorted meats or fish. It is commonly eaten with swallows such as amala, pounded yam, or eba.

== Equipment ==
* [[Cookbook: Stock Pot|Cooking pot]] (medium or large)
* [[Cookbook: Wooden Spoon|Wooden spoon]] or cooking spatula
* [[Cookbook: Knife|Knife]]
* [[Cookbook: Cutting Board|Cutting board]]
* Blender or grinding stone (for pepper mix)
* Bowl (for washing vegetables)
* Stove or heat source

== Ingredients ==
* 2 bunches spinach or ugu (pumpkin leaves), chopped
* 500 g assorted meat (beef, goat meat, or chicken)
* 200 g stockfish, soaked
* 200 g dried fish, cleaned
* 1 cup palm oil
* 3–4 fresh red bell peppers (tatashe)
* 2–3 scotch bonnet peppers (ata rodo), to taste
* 1 medium onion
* 2 tablespoons ground crayfish
* 2 seasoning cubes
* Salt, to taste
* Ogiri (optional, for traditional flavor)
== Procedure ==
#Wash and cook the assorted meat with onion, seasoning cubes, and salt until tender.
#Add stockfish and continue cooking until soft.
#Blend the peppers and onion into a smooth or slightly coarse paste.
#Heat palm oil in a pot (do not bleach).
#Add the blended pepper mix and fry for about 10–15 minutes until it reduces and thickens.
#Add the cooked meat, stockfish, dried fish, and meat stock.
#Stir and allow to simmer for 10 minutes.
#Add ground crayfish and ogiri if using.
#Add chopped vegetables and stir gently.
#Allow to cook for 3–5 minutes (do not overcook the vegetables).
#Adjust seasoning with salt or seasoning cubes.
#Remove from heat and serve hot.
== Tips ==
* Do not overcook the vegetables to preserve color and nutrients.
* The pepper base should be well fried for rich flavor.
* Efo Riro is best served with amala, eba, or pounded yam.
[[Category:Yoruba cuisine]] [[Category:Nigerian soups]] [[Category:Vegetable dishes]] [[Category:Palm oil dishes]]</text>
      <sha1>8lv9zc4253t1ok95r0ci4zn4fw3keu0</sha1>
    </revision>
    <revision>
      <id>4676550</id>
      <parentid>4676549</parentid>
      <timestamp>2026-10-17T15:23:07Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* Equipment */</comment>
      <origin>4676550</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2252" sha1="ra2sn6ex84ui7lpu1kf1wukooeeboxd" xml:space="preserve">{{Recipe summary
| Cuisine = Efo riro
| Origin = Western Nigeria
| Servings = 6
| Time = 1 hr 40 minutes
| Difficulty = 2
| Image = [[File:Efo Riro - Veggies.jpg|300px]]
}}{{Incomplete recipe|reason=missing recipe header template, missing appropriate linking, missing/incorrect categories, what kind of palm oil is it?}}
'''Efo Riro''' is a popular Yoruba vegetable soup made with leafy vegetables, palm oil, peppers, and assorted meats or fish. It is commonly eaten with swallows such as amala, pounded yam, or eba.

== Equipment ==
* [[Cookbook: Stock Pot|Cooking pot]] (medium or large)
* [[Cookbook: Wooden Spoon|Wooden spoon]] or cooking spatula
* [[Cookbook: Knife|Knife]]
* [[Cookbook: Cutting Board|Cutting board]]
* [[Cookbook: Blender|Blender]] or grinding stone (for pepper mix)
* Bowl (for washing vegetables)
* Stove or heat source

== Ingredients ==
* 2 bunches spinach or ugu (pumpkin leaves), chopped
* 500 g assorted meat (beef, goat meat, or chicken)
* 200 g stockfish, soaked
* 200 g dried fish, cleaned
* 1 cup palm oil
* 3–4 fresh red bell peppers (tatashe)
* 2–3 scotch bonnet peppers (ata rodo), to taste
* 1 medium onion
* 2 tablespoons ground crayfish
* 2 seasoning cubes
* Salt, to taste
* Ogiri (optional, for traditional flavor)
== Procedure ==
#Wash and cook the assorted meat with onion, seasoning cubes, and salt until tender.
#Add stockfish and continue cooking until soft.
#Blend the peppers and onion into a smooth or slightly coarse paste.
#Heat palm oil in a pot (do not bleach).
#Add the blended pepper mix and fry for about 10–15 minutes until it reduces and thickens.
#Add the cooked meat, stockfish, dried fish, and meat stock.
#Stir and allow to simmer for 10 minutes.
#Add ground crayfish and ogiri if using.
#Add chopped vegetables and stir gently.
#Allow to cook for 3–5 minutes (do not overcook the vegetables).
#Adjust seasoning with salt or seasoning cubes.
#Remove from heat and serve hot.
== Tips ==
* Do not overcook the vegetables to preserve color and nutrients.
* The pepper base should be well fried for rich flavor.
* Efo Riro is best served with amala, eba, or pounded yam.
[[Category:Yoruba cuisine]] [[Category:Nigerian soups]] [[Category:Vegetable dishes]] [[Category:Palm oil dishes]]</text>
      <sha1>ra2sn6ex84ui7lpu1kf1wukooeeboxd</sha1>
    </revision>
    <revision>
      <id>4676551</id>
      <parentid>4676550</parentid>
      <timestamp>2026-10-17T15:26:13Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* Equipment */</comment>
      <origin>4676551</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2278" sha1="d63x47x3ji6hcgyn0ctan6m2ygr7jkh" xml:space="preserve">{{Recipe summary
| Cuisine = Efo riro
| Origin = Western Nigeria
| Servings = 6
| Time = 1 hr 40 minutes
| Difficulty = 2
| Image = [[File:Efo Riro - Veggies.jpg|300px]]
}}{{Incomplete recipe|reason=missing recipe header template, missing appropriate linking, missing/incorrect categories, what kind of palm oil is it?}}
'''Efo Riro''' is a popular Yoruba vegetable soup made with leafy vegetables, palm oil, peppers, and assorted meats or fish. It is commonly eaten with swallows such as amala, pounded yam, or eba.

== Equipment ==
* [[Cookbook: Stock Pot|Cooking pot]] (medium or large)
* [[Cookbook: Wooden Spoon|Wooden spoon]] or cooking spatula
* [[Cookbook: Knife|Knife]]
* [[Cookbook: Cutting Board|Cutting board]]
* [[Cookbook: Blender|Blender]] or grinding stone (for pepper mix)
* [[Cookbook: Mixing Bowl|Bowl]] (for washing vegetables)
* Stove or heat source

== Ingredients ==
* 2 bunches spinach or ugu (pumpkin leaves), chopped
* 500 g assorted meat (beef, goat meat, or chicken)
* 200 g stockfish, soaked
* 200 g dried fish, cleaned
* 1 cup palm oil
* 3–4 fresh red bell peppers (tatashe)
* 2–3 scotch bonnet peppers (ata rodo), to taste
* 1 medium onion
* 2 tablespoons ground crayfish
* 2 seasoning cubes
* Salt, to taste
* Ogiri (optional, for traditional flavor)
== Procedure ==
#Wash and cook the assorted meat with onion, seasoning cubes, and salt until tender.
#Add stockfish and continue cooking until soft.
#Blend the peppers and onion into a smooth or slightly coarse paste.
#Heat palm oil in a pot (do not bleach).
#Add the blended pepper mix and fry for about 10–15 minutes until it reduces and thickens.
#Add the cooked meat, stockfish, dried fish, and meat stock.
#Stir and allow to simmer for 10 minutes.
#Add ground crayfish and ogiri if using.
#Add chopped vegetables and stir gently.
#Allow to cook for 3–5 minutes (do not overcook the vegetables).
#Adjust seasoning with salt or seasoning cubes.
#Remove from heat and serve hot.
== Tips ==
* Do not overcook the vegetables to preserve color and nutrients.
* The pepper base should be well fried for rich flavor.
* Efo Riro is best served with amala, eba, or pounded yam.
[[Category:Yoruba cuisine]] [[Category:Nigerian soups]] [[Category:Vegetable dishes]] [[Category:Palm oil dishes]]</text>
      <sha1>d63x47x3ji6hcgyn0ctan6m2ygr7jkh</sha1>
    </revision>
    <revision>
      <id>4676554</id>
      <parentid>4676551</parentid>
      <timestamp>2026-10-17T15:30:35Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* Ingredients */</comment>
      <origin>4676554</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2297" sha1="f8mdsl20e5bzbswhlmt2kcqbphut703" xml:space="preserve">{{Recipe summary
| Cuisine = Efo riro
| Origin = Western Nigeria
| Servings = 6
| Time = 1 hr 40 minutes
| Difficulty = 2
| Image = [[File:Efo Riro - Veggies.jpg|300px]]
}}{{Incomplete recipe|reason=missing recipe header template, missing appropriate linking, missing/incorrect categories, what kind of palm oil is it?}}
'''Efo Riro''' is a popular Yoruba vegetable soup made with leafy vegetables, palm oil, peppers, and assorted meats or fish. It is commonly eaten with swallows such as amala, pounded yam, or eba.

== Equipment ==
* [[Cookbook: Stock Pot|Cooking pot]] (medium or large)
* [[Cookbook: Wooden Spoon|Wooden spoon]] or cooking spatula
* [[Cookbook: Knife|Knife]]
* [[Cookbook: Cutting Board|Cutting board]]
* [[Cookbook: Blender|Blender]] or grinding stone (for pepper mix)
* [[Cookbook: Mixing Bowl|Bowl]] (for washing vegetables)
* Stove or heat source

== Ingredients ==
* 2 bunches spinach or ugu (pumpkin leaves), chopped
* 500 g assorted meat (beef, goat meat, or chicken)
* 200 g stockfish, soaked
* 200 g dried fish, cleaned
* 1 cup palm oil
* 3–4 fresh red bell peppers (tatashe)
* 2–3 scotch bonnet peppers (ata rodo), to taste
* 1 medium onion
* 2 tablespoons ground crayfish
* 2 seasoning cubes
* [[Cookbook:Salt|Salt]], to taste
* Ogiri (optional, for traditional flavor)

== Procedure ==
#Wash and cook the assorted meat with onion, seasoning cubes, and salt until tender.
#Add stockfish and continue cooking until soft.
#Blend the peppers and onion into a smooth or slightly coarse paste.
#Heat palm oil in a pot (do not bleach).
#Add the blended pepper mix and fry for about 10–15 minutes until it reduces and thickens.
#Add the cooked meat, stockfish, dried fish, and meat stock.
#Stir and allow to simmer for 10 minutes.
#Add ground crayfish and ogiri if using.
#Add chopped vegetables and stir gently.
#Allow to cook for 3–5 minutes (do not overcook the vegetables).
#Adjust seasoning with salt or seasoning cubes.
#Remove from heat and serve hot.
== Tips ==
* Do not overcook the vegetables to preserve color and nutrients.
* The pepper base should be well fried for rich flavor.
* Efo Riro is best served with amala, eba, or pounded yam.
[[Category:Yoruba cuisine]] [[Category:Nigerian soups]] [[Category:Vegetable dishes]] [[Category:Palm oil dishes]]</text>
      <sha1>f8mdsl20e5bzbswhlmt2kcqbphut703</sha1>
    </revision>
    <revision>
      <id>4676555</id>
      <parentid>4676554</parentid>
      <timestamp>2026-10-17T15:31:14Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* Ingredients */</comment>
      <origin>4676555</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2317" sha1="nn46qs54g2gfwqgh5t14bqdivzhznrk" xml:space="preserve">{{Recipe summary
| Cuisine = Efo riro
| Origin = Western Nigeria
| Servings = 6
| Time = 1 hr 40 minutes
| Difficulty = 2
| Image = [[File:Efo Riro - Veggies.jpg|300px]]
}}{{Incomplete recipe|reason=missing recipe header template, missing appropriate linking, missing/incorrect categories, what kind of palm oil is it?}}
'''Efo Riro''' is a popular Yoruba vegetable soup made with leafy vegetables, palm oil, peppers, and assorted meats or fish. It is commonly eaten with swallows such as amala, pounded yam, or eba.

== Equipment ==
* [[Cookbook: Stock Pot|Cooking pot]] (medium or large)
* [[Cookbook: Wooden Spoon|Wooden spoon]] or cooking spatula
* [[Cookbook: Knife|Knife]]
* [[Cookbook: Cutting Board|Cutting board]]
* [[Cookbook: Blender|Blender]] or grinding stone (for pepper mix)
* [[Cookbook: Mixing Bowl|Bowl]] (for washing vegetables)
* Stove or heat source

== Ingredients ==
* 2 bunches spinach or ugu (pumpkin leaves), chopped
* 500 g assorted meat (beef, goat meat, or chicken)
* 200 g stockfish, soaked
* 200 g dried fish, cleaned
* 1 cup palm oil
* 3–4 fresh red bell peppers (tatashe)
* 2–3 scotch bonnet peppers (ata rodo), to taste
* 1 medium [[Cookbook: Onion|onion]]
* 2 tablespoons ground crayfish
* 2 seasoning cubes
* [[Cookbook:Salt|Salt]], to taste
* Ogiri (optional, for traditional flavor)

== Procedure ==
#Wash and cook the assorted meat with onion, seasoning cubes, and salt until tender.
#Add stockfish and continue cooking until soft.
#Blend the peppers and onion into a smooth or slightly coarse paste.
#Heat palm oil in a pot (do not bleach).
#Add the blended pepper mix and fry for about 10–15 minutes until it reduces and thickens.
#Add the cooked meat, stockfish, dried fish, and meat stock.
#Stir and allow to simmer for 10 minutes.
#Add ground crayfish and ogiri if using.
#Add chopped vegetables and stir gently.
#Allow to cook for 3–5 minutes (do not overcook the vegetables).
#Adjust seasoning with salt or seasoning cubes.
#Remove from heat and serve hot.
== Tips ==
* Do not overcook the vegetables to preserve color and nutrients.
* The pepper base should be well fried for rich flavor.
* Efo Riro is best served with amala, eba, or pounded yam.
[[Category:Yoruba cuisine]] [[Category:Nigerian soups]] [[Category:Vegetable dishes]] [[Category:Palm oil dishes]]</text>
      <sha1>nn46qs54g2gfwqgh5t14bqdivzhznrk</sha1>
    </revision>
    <revision>
      <id>4676556</id>
      <parentid>4676555</parentid>
      <timestamp>2026-10-17T15:31:57Z</timestamp>
      <contributor>
        <username>A Sulaiman Z</username>
        <id>3412824</id>
      </contributor>
      <comment>/* Ingredients */</comment>
      <origin>4676556</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2340" sha1="jpejalzjfzb9jivoflr38h2gcxviwvq" xml:space="preserve">{{Recipe summary
| Cuisine = Efo riro
| Origin = Western Nigeria
| Servings = 6
| Time = 1 hr 40 minutes
| Difficulty = 2
| Image = [[File:Efo Riro - Veggies.jpg|300px]]
}}{{Incomplete recipe|reason=missing recipe header template, missing appropriate linking, missing/incorrect categories, what kind of palm oil is it?}}
'''Efo Riro''' is a popular Yoruba vegetable soup made with leafy vegetables, palm oil, peppers, and assorted meats or fish. It is commonly eaten with swallows such as amala, pounded yam, or eba.

== Equipment ==
* [[Cookbook: Stock Pot|Cooking pot]] (medium or large)
* [[Cookbook: Wooden Spoon|Wooden spoon]] or cooking spatula
* [[Cookbook: Knife|Knife]]
* [[Cookbook: Cutting Board|Cutting board]]
* [[Cookbook: Blender|Blender]] or grinding stone (for pepper mix)
* [[Cookbook: Mixing Bowl|Bowl]] (for washing vegetables)
* Stove or heat source

== Ingredients ==
* 2 bunches spinach or ugu (pumpkin leaves), chopped
* 500 g assorted meat (beef, goat meat, or chicken)
* 200 g stockfish, soaked
* 200 g dried fish, cleaned
* 1 cup [[Cookbook: Palm Oil|palm oil]]
* 3–4 fresh red bell peppers (tatashe)
* 2–3 scotch bonnet peppers (ata rodo), to taste
* 1 medium [[Cookbook: Onion|onion]]
* 2 tablespoons ground crayfish
* 2 seasoning cubes
* [[Cookbook:Salt|Salt]], to taste
* Ogiri (optional, for traditional flavor)

== Procedure ==
#Wash and cook the assorted meat with onion, seasoning cubes, and salt until tender.
#Add stockfish and continue cooking until soft.
#Blend the peppers and onion into a smooth or slightly coarse paste.
#Heat palm oil in a pot (do not bleach).
#Add the blended pepper mix and fry for about 10–15 minutes until it reduces and thickens.
#Add the cooked meat, stockfish, dried fish, and meat stock.
#Stir and allow to simmer for 10 minutes.
#Add ground crayfish and ogiri if using.
#Add chopped vegetables and stir gently.
#Allow to cook for 3–5 minutes (do not overcook the vegetables).
#Adjust seasoning with salt or seasoning cubes.
#Remove from heat and serve hot.
== Tips ==
* Do not overcook the vegetables to preserve color and nutrients.
* The pepper base should be well fried for rich flavor.
* Efo Riro is best served with amala, eba, or pounded yam.
[[Category:Yoruba cuisine]] [[Category:Nigerian soups]] [[Category:Vegetable dishes]] [[Category:Palm oil dishes]]</text>
      <sha1>jpejalzjfzb9jivoflr38h2gcxviwvq</sha1>
    </revision>
  </page>
  <page>
    <title>Chess Opening Theory/1. e4/1...e5/2. Nf3/2...Nc6/3. Nc3/3...Nf6/4. Nxe5/4...Nxe4</title>
    <ns>0</ns>
    <id>484104</id>
    <revision>
      <id>4676504</id>
      <parentid>4676495</parentid>
      <timestamp>2026-10-17T12:02:08Z</timestamp>
      <contributor>
        <username>Ltypestar2</username>
        <id>3524220</id>
      </contributor>
      <minor />
      <comment>Consistent bolding</comment>
      <origin>4676504</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="6764" sha1="bwdcx6fjzson33ibpkxiero5kaonn4c" xml:space="preserve">== 4...Nxe4?! ==
{{Chess Opening Theory/Position|name=Mirrored Halloween (informal)|eco=[[Chess/ECOC|C47]]|parent=[[../|Halloween Gambit]]}}
Black unusually declines the gambit and tries to mirror the [[Chess/Halloween Attack|'''Halloween Attack''']]'s sacrifice ('''4. Nxe5''') to counter the Halloween Attack. Although this recovers the pawn, it ignores the hanging knight and gives White back a drawish position, with higher winning chances for White. Worse, it unnecessarily keeps the position symmetrical, which means White still has a first move advantage.

This line has no established name, but it is informally called &quot;'''Mirrored Halloween'''&quot; here, because this is Black's mirroring response to the Halloween Attack's main move ('''4. Nxe5''').

There are usually 2 main moves White will most commonly try: '''5. Nxc6''', taking the black c6 knight and ignoring the hanging black e4 knight, and '''5. Nxe4''', taking the hanging black e4 knight, ignoring the hanging white knight on e5.

=== 5. Nxc6 ===
White takes the knight on c6, attacking the queen. Because Black has a hanging knight on e4, his only move is to counterattack by playing '''5...Nxc3!''' (Because if he takes the white knight with '''5...bxc6??''' or '''5...dxc6??''', White can simply win a knight after '''6. Nxe4!.''' If Black plays '''5...Qe7??''', White can take the black queen, every other queen move loses a knight (The white knight on c6 can retreat back, making Black lose a knight). Every other move loses a queen due to ignoring the hanging queen. For example, '''5...Nxf2??''' is refuted by '''6. Qe2+!''', a check that sidesteps the attack entirely, and Black cannot stop '''7. Nxd8''', or '''7. Nxd7'''.), counterattacking the white queen. If White wishes to deal with this, either '''6. dxc3''', removing Black’s attacking knight on c3, after which Black removes White’s attacking knight on c6 by playing either '''6...dxc6''', or '''6...bxc6'''; or '''6. Nxd8,''' trading queens; will be good options according to Stockfish. If White plays '''6. Nxd8''', Black will respond with '''6...Nxd1''', recovering material.

{{Chess/board
| moves = 1. e4 e5 2. Nf3 Nc6 3. Nc3 Nf6 4. Nxe5 Nxe4 5. Nxc6 Nxc3 6. Nxd8 Nxd1
| caption = Position after Black's move of '''6...Nxd1'''.
}}

=== 5. Nxe4 ===
White takes the knight on e4. Black will likely follow up with '''5...Nxe5''', recovering material. '''6. d4''' is a good center attacking move for White that also gains tempo by kicking the black knight. The position is very drawish, with White being slightly better by having a better center.

{{Chess/board
| moves = 1. e4 e5 2. Nf3 Nc6 3. Nc3 Nf6 4. Nxe5 Nxe4 5. Nxe4 Nxe5 6. d4
| caption = Position after White's move of '''6. d4'''.
}}

=== 5. Qh5 ===
This is an uncommon move and also White's most aggressive option, directly threatening '''6. Qxf7#''', forcing Black into defense of their f7-square. Black can make a lot of mistakes from here. 

==== 5...Nxe5?? ====
Black plays the common blunder '''5...Nxe5??''', hoping to remove an attacker of the f7-square and trade pieces, White can take the knight with check ('''6. Qxe5+!'''), forcing the black king to cover, and now there is no way to save the e4 knight, there are simply too many attackers. If Black plays '''6...Qe7''' (Black's best try, since the queen x-ray defends the knight and counterattacks the queen), then White can play '''7. Qxe7+!''', then take the black knight on e4.

==== 5...g6? ====
If Black instead plays the also common mistake '''5...g6?''', mimicking the [[Chess Opening Theory/1. e4/1...e5/2. Qh5/2...Nc6/3. Bc4/3...g6|'''Wayward Queen Attack'''&lt;nowiki/&gt;'s most common defence]], Black loses a pawn after this sequence: '''6. Nxc6!''' (counterattacking the black queen) '''gxh5 7. Nxd8 Nxc3 8. Nxf7''' (White desperado sacrifices the white knight for a pawn, knowing the knight is doomed anyway, and Black cannot sacrifice his knight for any compensation, and if Black retreats, White can just escape with the free pawn.) '''Kxf7 9. dxc3'''.

==== 5...Nd6 ====
This is Black's fairly rare but best try, retreating the black knight to defend f7. But White can lunge forward with '''6. Nd5''', playing aggressively. White has very good winning chances here in this position. Black has to play precisely to survive in this position.

{{Chess/board
| moves = 1. e4 e5 2. Nf3 Nc6 3. Nc3 Nf6 4. Nxe5 Nxe4 5. Qh5 Nd6 6. Nd5
| caption = Position after White's move of '''6. Nd5'''.
}}

==== 5...Qf6?! ====
This is a better move than the blunders described on this page, but it is a small inaccuracy, since it allows White to win a pawn, make Black lose castling rights, and gain development. The best move for White is '''6. Qxf7+''', starting the trade that will win them a pawn and make Black lose castling rights. Then Black will regain material with '''6...Qxf7''', then White will regain material with '''7. Nxf7'''. The black king will then take on f7 with '''7...Kxf7''', losing castling rights. Now it seems like Black is ahead on material here, but the e4 knight is hanging, so White can win back the material and, in the end, they will have won a pawn. The best move for white now is not to take the black knight on e4 immediately but play an intermediate move (zwischenzug) by playing '''8. Bc4+''', forcing the king to move or block with the only legal block '''8...d5??''', There is no legal move that defends the knight and deals with the check at the same time except '''8...d5??''' which seems like it defends the black knight and blocks the check, but this blunders a pawn via '''9. Bxd5+''' and fails to defend the knight anyway since the pawn is the only defender of the knight. Black now must move the king, two good moves are the natural '''8... Ke8''', or the unnatural but best move by the engine (Stockfish 19 NNUE) '''8...Ke7'''. Then, White takes the knight with '''9. Nxe4,''' ending this tactical sequence with a bishop developed, a knight centralized, and a pawn gained.
{{Chess/board
| moves = 1. e4 e5 2. Nf3 Nc6 3. Nc3 Nf6 4. Nxe5 Nxe4 5. Qh5 Qf6 6. Qxf7+ Qxf7 7. Nxf7 Kxf7 8. Bc4+ Ke7 9. Nxe4
| caption = Position after White's move of '''9. Nxe4''' if Black played '''8...Ke7'''.
}}

== Theory table ==
{{ChessTable}}
{{Chess/theory table
|preceding=1. e4 e5 2. Nf3 Nc6 3. Nc3 Nf6 4. Nxe5 Nxe4
|line1=5. Nxc6 Nxc3 6. dxc3 dxc6
|eval1= =
|line2=5. Nxc6 Nxc3 6. Nxd8 Nxd1
|eval2= =
|line3=5. Nxe4 Nxe5 6. d4
|eval3= +/=
|line4=5. Qh5 Nxe5?? 6. Qxe5+ Qe7 7. Qxe7+
|eval4= +-
|line5=5. Qh5 g6? 6. Nxc6! gxh5 7. Nxd8 Nxc3 8. Nxf7 Kxf7 9. dxc3
|eval5= +/-
|line6=5. Qh5 Nd6 6. Nd5
|eval6= +/-
|line7=5.Qh5 Qf6?! 6. Qxf7+ Qxf7 7. Nxf7 Kxf7 8. Bc4+ Ke7 9. Nxe4|line8=5.Qh5 Qf6?! 6. Qxf7+ Qxf7 7. Nxf7 Kxf7 8. Bc4+ d5?? 9. Bxd5+|eval7=+/=|eval8=+-}}
{{ChessMid}}</text>
      <sha1>bwdcx6fjzson33ibpkxiero5kaonn4c</sha1>
    </revision>
    <revision>
      <id>4676509</id>
      <parentid>4676504</parentid>
      <timestamp>2026-10-17T12:23:23Z</timestamp>
      <contributor>
        <username>Ltypestar2</username>
        <id>3524220</id>
      </contributor>
      <minor />
      <comment>minor edit fixing the chess error</comment>
      <origin>4676509</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="6764" sha1="3z6qagt7gip2dxdcqq6rx7p8561z768" xml:space="preserve">== 4...Nxe4?! ==
{{Chess Opening Theory/Position|name=Mirrored Halloween (informal)|eco=[[Chess/ECOC|C47]]|parent=[[../|Halloween Gambit]]}}
Black unusually declines the gambit and tries to mirror the [[Chess/Halloween Attack|'''Halloween Attack''']]'s sacrifice ('''4. Nxe5''') to counter the Halloween Attack. Although this recovers the pawn, it ignores the hanging knight and gives White back a drawish position, with higher winning chances for White. Worse, it unnecessarily keeps the position symmetrical, which means White still has a first move advantage.

This line has no established name, but it is informally called &quot;'''Mirrored Halloween'''&quot; here, because this is Black's mirroring response to the Halloween Attack's main move ('''4. Nxe5''').

There are usually 2 main moves White will most commonly try: '''5. Nxc6''', taking the black c6 knight and ignoring the hanging black e4 knight, and '''5. Nxe4''', taking the hanging black e4 knight, ignoring the hanging white knight on e5.

=== 5. Nxc6 ===
White takes the knight on c6, attacking the queen. Because Black has a hanging knight on e4, his only move is to counterattack by playing '''5...Nxc3!''' (Because if he takes the white knight with '''5...bxc6??''' or '''5...dxc6??''', White can simply win a knight after '''6. Nxe4!.''' If Black plays '''5...Qe7??''', White can take the black queen, every other queen move loses a knight (The white knight on c6 can retreat back, making Black lose a knight). Every other move loses a queen due to ignoring the hanging queen. For example, '''5...Nxf2??''' is refuted by '''6. Qe2+!''', a check that sidesteps the attack entirely, and Black cannot stop '''7. Nxd8''', or '''7. Nxe7'''.), counterattacking the white queen. If White wishes to deal with this, either '''6. dxc3''', removing Black’s attacking knight on c3, after which Black removes White’s attacking knight on c6 by playing either '''6...dxc6''', or '''6...bxc6'''; or '''6. Nxd8,''' trading queens; will be good options according to Stockfish. If White plays '''6. Nxd8''', Black will respond with '''6...Nxd1''', recovering material.

{{Chess/board
| moves = 1. e4 e5 2. Nf3 Nc6 3. Nc3 Nf6 4. Nxe5 Nxe4 5. Nxc6 Nxc3 6. Nxd8 Nxd1
| caption = Position after Black's move of '''6...Nxd1'''.
}}

=== 5. Nxe4 ===
White takes the knight on e4. Black will likely follow up with '''5...Nxe5''', recovering material. '''6. d4''' is a good center attacking move for White that also gains tempo by kicking the black knight. The position is very drawish, with White being slightly better by having a better center.

{{Chess/board
| moves = 1. e4 e5 2. Nf3 Nc6 3. Nc3 Nf6 4. Nxe5 Nxe4 5. Nxe4 Nxe5 6. d4
| caption = Position after White's move of '''6. d4'''.
}}

=== 5. Qh5 ===
This is an uncommon move and also White's most aggressive option, directly threatening '''6. Qxf7#''', forcing Black into defense of their f7-square. Black can make a lot of mistakes from here. 

==== 5...Nxe5?? ====
Black plays the common blunder '''5...Nxe5??''', hoping to remove an attacker of the f7-square and trade pieces, White can take the knight with check ('''6. Qxe5+!'''), forcing the black king to cover, and now there is no way to save the e4 knight, there are simply too many attackers. If Black plays '''6...Qe7''' (Black's best try, since the queen x-ray defends the knight and counterattacks the queen), then White can play '''7. Qxe7+!''', then take the black knight on e4.

==== 5...g6? ====
If Black instead plays the also common mistake '''5...g6?''', mimicking the [[Chess Opening Theory/1. e4/1...e5/2. Qh5/2...Nc6/3. Bc4/3...g6|'''Wayward Queen Attack'''&lt;nowiki/&gt;'s most common defence]], Black loses a pawn after this sequence: '''6. Nxc6!''' (counterattacking the black queen) '''gxh5 7. Nxd8 Nxc3 8. Nxf7''' (White desperado sacrifices the white knight for a pawn, knowing the knight is doomed anyway, and Black cannot sacrifice his knight for any compensation, and if Black retreats, White can just escape with the free pawn.) '''Kxf7 9. dxc3'''.

==== 5...Nd6 ====
This is Black's fairly rare but best try, retreating the black knight to defend f7. But White can lunge forward with '''6. Nd5''', playing aggressively. White has very good winning chances here in this position. Black has to play precisely to survive in this position.

{{Chess/board
| moves = 1. e4 e5 2. Nf3 Nc6 3. Nc3 Nf6 4. Nxe5 Nxe4 5. Qh5 Nd6 6. Nd5
| caption = Position after White's move of '''6. Nd5'''.
}}

==== 5...Qf6?! ====
This is a better move than the blunders described on this page, but it is a small inaccuracy, since it allows White to win a pawn, make Black lose castling rights, and gain development. The best move for White is '''6. Qxf7+''', starting the trade that will win them a pawn and make Black lose castling rights. Then Black will regain material with '''6...Qxf7''', then White will regain material with '''7. Nxf7'''. The black king will then take on f7 with '''7...Kxf7''', losing castling rights. Now it seems like Black is ahead on material here, but the e4 knight is hanging, so White can win back the material and, in the end, they will have won a pawn. The best move for white now is not to take the black knight on e4 immediately but play an intermediate move (zwischenzug) by playing '''8. Bc4+''', forcing the king to move or block with the only legal block '''8...d5??''', There is no legal move that defends the knight and deals with the check at the same time except '''8...d5??''' which seems like it defends the black knight and blocks the check, but this blunders a pawn via '''9. Bxd5+''' and fails to defend the knight anyway since the pawn is the only defender of the knight. Black now must move the king, two good moves are the natural '''8... Ke8''', or the unnatural but best move by the engine (Stockfish 19 NNUE) '''8...Ke7'''. Then, White takes the knight with '''9. Nxe4,''' ending this tactical sequence with a bishop developed, a knight centralized, and a pawn gained.
{{Chess/board
| moves = 1. e4 e5 2. Nf3 Nc6 3. Nc3 Nf6 4. Nxe5 Nxe4 5. Qh5 Qf6 6. Qxf7+ Qxf7 7. Nxf7 Kxf7 8. Bc4+ Ke7 9. Nxe4
| caption = Position after White's move of '''9. Nxe4''' if Black played '''8...Ke7'''.
}}

== Theory table ==
{{ChessTable}}
{{Chess/theory table
|preceding=1. e4 e5 2. Nf3 Nc6 3. Nc3 Nf6 4. Nxe5 Nxe4
|line1=5. Nxc6 Nxc3 6. dxc3 dxc6
|eval1= =
|line2=5. Nxc6 Nxc3 6. Nxd8 Nxd1
|eval2= =
|line3=5. Nxe4 Nxe5 6. d4
|eval3= +/=
|line4=5. Qh5 Nxe5?? 6. Qxe5+ Qe7 7. Qxe7+
|eval4= +-
|line5=5. Qh5 g6? 6. Nxc6! gxh5 7. Nxd8 Nxc3 8. Nxf7 Kxf7 9. dxc3
|eval5= +/-
|line6=5. Qh5 Nd6 6. Nd5
|eval6= +/-
|line7=5.Qh5 Qf6?! 6. Qxf7+ Qxf7 7. Nxf7 Kxf7 8. Bc4+ Ke7 9. Nxe4|line8=5.Qh5 Qf6?! 6. Qxf7+ Qxf7 7. Nxf7 Kxf7 8. Bc4+ d5?? 9. Bxd5+|eval7=+/=|eval8=+-}}
{{ChessMid}}</text>
      <sha1>3z6qagt7gip2dxdcqq6rx7p8561z768</sha1>
    </revision>
    <revision>
      <id>4676510</id>
      <parentid>4676509</parentid>
      <timestamp>2026-10-17T12:40:02Z</timestamp>
      <contributor>
        <username>Ltypestar2</username>
        <id>3524220</id>
      </contributor>
      <comment>Added History</comment>
      <origin>4676510</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="7526" sha1="7caiztw0ja8jlxkx1rtlx2j13aqd8cj" xml:space="preserve">== 4...Nxe4?! ==
{{Chess Opening Theory/Position|name=Mirrored Halloween (informal)|eco=[[Chess/ECOC|C47]]|parent=[[../|Halloween Gambit]]}}
Black unusually declines the gambit and tries to mirror the [[Chess/Halloween Attack|'''Halloween Attack''']]'s sacrifice ('''4. Nxe5''') to counter the Halloween Attack. Although this recovers the pawn, it ignores the hanging knight and gives White back a drawish position, with higher winning chances for White. Worse, it unnecessarily keeps the position symmetrical, which means White still has a first move advantage.

This line has no established name, but it is informally called &quot;'''Mirrored Halloween'''&quot; here, because this is Black's mirroring response to the Halloween Attack's main move ('''4. Nxe5''').

There are usually 2 main moves White will most commonly try: '''5. Nxc6''', taking the black c6 knight and ignoring the hanging black e4 knight, and '''5. Nxe4''', taking the hanging black e4 knight, ignoring the hanging white knight on e5.

=== 5. Nxc6 ===
White takes the knight on c6, attacking the queen. Because Black has a hanging knight on e4, his only move is to counterattack by playing '''5...Nxc3!''' (Because if he takes the white knight with '''5...bxc6??''' or '''5...dxc6??''', White can simply win a knight after '''6. Nxe4!.''' If Black plays '''5...Qe7??''', White can take the black queen, every other queen move loses a knight (The white knight on c6 can retreat back, making Black lose a knight). Every other move loses a queen due to ignoring the hanging queen. For example, '''5...Nxf2??''' is refuted by '''6. Qe2+!''', a check that sidesteps the attack entirely, and Black cannot stop '''7. Nxd8''', or '''7. Nxe7'''.), counterattacking the white queen. If White wishes to deal with this, either '''6. dxc3''', removing Black’s attacking knight on c3, after which Black removes White’s attacking knight on c6 by playing either '''6...dxc6''', or '''6...bxc6'''; or '''6. Nxd8,''' trading queens; will be good options according to Stockfish. If White plays '''6. Nxd8''', Black will respond with '''6...Nxd1''', recovering material.

{{Chess/board
| moves = 1. e4 e5 2. Nf3 Nc6 3. Nc3 Nf6 4. Nxe5 Nxe4 5. Nxc6 Nxc3 6. Nxd8 Nxd1
| caption = Position after Black's move of '''6...Nxd1'''.
}}

=== 5. Nxe4 ===
White takes the knight on e4. Black will likely follow up with '''5...Nxe5''', recovering material. '''6. d4''' is a good center attacking move for White that also gains tempo by kicking the black knight. The position is very drawish, with White being slightly better by having a better center.

{{Chess/board
| moves = 1. e4 e5 2. Nf3 Nc6 3. Nc3 Nf6 4. Nxe5 Nxe4 5. Nxe4 Nxe5 6. d4
| caption = Position after White's move of '''6. d4'''.
}}

=== 5. Qh5 ===
This is an uncommon move and also White's most aggressive option, directly threatening '''6. Qxf7#''', forcing Black into defense of their f7-square. Black can make a lot of mistakes from here. 

==== 5...Nxe5?? ====
Black plays the common blunder '''5...Nxe5??''', hoping to remove an attacker of the f7-square and trade pieces, White can take the knight with check ('''6. Qxe5+!'''), forcing the black king to cover, and now there is no way to save the e4 knight, there are simply too many attackers. If Black plays '''6...Qe7''' (Black's best try, since the queen x-ray defends the knight and counterattacks the queen), then White can play '''7. Qxe7+!''', then take the black knight on e4.

==== 5...g6? ====
If Black instead plays the also common mistake '''5...g6?''', mimicking the [[Chess Opening Theory/1. e4/1...e5/2. Qh5/2...Nc6/3. Bc4/3...g6|'''Wayward Queen Attack'''&lt;nowiki/&gt;'s most common defence]], Black loses a pawn after this sequence: '''6. Nxc6!''' (counterattacking the black queen) '''gxh5 7. Nxd8 Nxc3 8. Nxf7''' (White desperado sacrifices the white knight for a pawn, knowing the knight is doomed anyway, and Black cannot sacrifice his knight for any compensation, and if Black retreats, White can just escape with the free pawn.) '''Kxf7 9. dxc3'''.

==== 5...Nd6 ====
This is Black's fairly rare but best try, retreating the black knight to defend f7. But White can lunge forward with '''6. Nd5''', playing aggressively. White has very good winning chances here in this position. Black has to play precisely to survive in this position.

{{Chess/board
| moves = 1. e4 e5 2. Nf3 Nc6 3. Nc3 Nf6 4. Nxe5 Nxe4 5. Qh5 Nd6 6. Nd5
| caption = Position after White's move of '''6. Nd5'''.
}}

==== 5...Qf6?! ====
This is a better move than the blunders described on this page, but it is a small inaccuracy, since it allows White to win a pawn, make Black lose castling rights, and gain development. The best move for White is '''6. Qxf7+''', starting the trade that will win them a pawn and make Black lose castling rights. Then Black will regain material with '''6...Qxf7''', then White will regain material with '''7. Nxf7'''. The black king will then take on f7 with '''7...Kxf7''', losing castling rights. Now it seems like Black is ahead on material here, but the e4 knight is hanging, so White can win back the material and, in the end, they will have won a pawn. The best move for white now is not to take the black knight on e4 immediately but play an intermediate move (zwischenzug) by playing '''8. Bc4+''', forcing the king to move or block with the only legal block '''8...d5??''', There is no legal move that defends the knight and deals with the check at the same time except '''8...d5??''' which seems like it defends the black knight and blocks the check, but this blunders a pawn via '''9. Bxd5+''' and fails to defend the knight anyway since the pawn is the only defender of the knight. Black now must move the king, two good moves are the natural '''8... Ke8''', or the unnatural but best move by the engine (Stockfish 19 NNUE) '''8...Ke7'''. Then, White takes the knight with '''9. Nxe4,''' ending this tactical sequence with a bishop developed, a knight centralized, and a pawn gained.
{{Chess/board
| moves = 1. e4 e5 2. Nf3 Nc6 3. Nc3 Nf6 4. Nxe5 Nxe4 5. Qh5 Qf6 6. Qxf7+ Qxf7 7. Nxf7 Kxf7 8. Bc4+ Ke7 9. Nxe4
| caption = Position after White's move of '''9. Nxe4''' if Black played '''8...Ke7'''.
}}

== History ==
This line has no known history in books or tournament practice, and it is very rare. However, Lichess database statistics show that its popularity has increased over time. Between January 2017 and April 2026, the share of Lichess games reaching this position rose from roughly 0.0002% to about 0.0005-0.0007%, peaking at around 0.0007%, though with considerable fluctuation.&lt;ref&gt;{{Cite web |title=Four Knights Game: Halloween Gambit |url=https://lichess.org/opening/Four_Knights_Game_Halloween_Gambit/e4_e5_Nf3_Nc6_Nc3_Nf6_Nxe5_Nxe4 |access-date=2026-10-17 |website=lichess.org |language=en-US}}&lt;/ref&gt; For the history of the gambit itself, see the [[Chess Opening Theory/1. e4/1...e5/2. Nf3/2...Nc6/3. Nc3/3...Nf6/4. Nxe5|Halloween Gambit]] page.

== Theory table ==
{{ChessTable}}
{{Chess/theory table
|preceding=1. e4 e5 2. Nf3 Nc6 3. Nc3 Nf6 4. Nxe5 Nxe4
|line1=5. Nxc6 Nxc3 6. dxc3 dxc6
|eval1= =
|line2=5. Nxc6 Nxc3 6. Nxd8 Nxd1
|eval2= =
|line3=5. Nxe4 Nxe5 6. d4
|eval3= +/=
|line4=5. Qh5 Nxe5?? 6. Qxe5+ Qe7 7. Qxe7+
|eval4= +-
|line5=5. Qh5 g6? 6. Nxc6! gxh5 7. Nxd8 Nxc3 8. Nxf7 Kxf7 9. dxc3
|eval5= +/-
|line6=5. Qh5 Nd6 6. Nd5
|eval6= +/-
|line7=5.Qh5 Qf6?! 6. Qxf7+ Qxf7 7. Nxf7 Kxf7 8. Bc4+ Ke7 9. Nxe4|line8=5.Qh5 Qf6?! 6. Qxf7+ Qxf7 7. Nxf7 Kxf7 8. Bc4+ d5?? 9. Bxd5+|eval7=+/=|eval8=+-}}
{{ChessMid}}</text>
      <sha1>7caiztw0ja8jlxkx1rtlx2j13aqd8cj</sha1>
    </revision>
    <revision>
      <id>4676511</id>
      <parentid>4676510</parentid>
      <timestamp>2026-10-17T12:42:47Z</timestamp>
      <contributor>
        <username>Ltypestar2</username>
        <id>3524220</id>
      </contributor>
      <minor />
      <comment>I'm sorry for editing so frequently over minor changes, but I just noticed a reference appeared at the bottom without a References header.</comment>
      <origin>4676511</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="7544" sha1="qj4cd33hrr4deauwxfp6cz62lfnvvyj" xml:space="preserve">== 4...Nxe4?! ==
{{Chess Opening Theory/Position|name=Mirrored Halloween (informal)|eco=[[Chess/ECOC|C47]]|parent=[[../|Halloween Gambit]]}}
Black unusually declines the gambit and tries to mirror the [[Chess/Halloween Attack|'''Halloween Attack''']]'s sacrifice ('''4. Nxe5''') to counter the Halloween Attack. Although this recovers the pawn, it ignores the hanging knight and gives White back a drawish position, with higher winning chances for White. Worse, it unnecessarily keeps the position symmetrical, which means White still has a first move advantage.

This line has no established name, but it is informally called &quot;'''Mirrored Halloween'''&quot; here, because this is Black's mirroring response to the Halloween Attack's main move ('''4. Nxe5''').

There are usually 2 main moves White will most commonly try: '''5. Nxc6''', taking the black c6 knight and ignoring the hanging black e4 knight, and '''5. Nxe4''', taking the hanging black e4 knight, ignoring the hanging white knight on e5.

=== 5. Nxc6 ===
White takes the knight on c6, attacking the queen. Because Black has a hanging knight on e4, his only move is to counterattack by playing '''5...Nxc3!''' (Because if he takes the white knight with '''5...bxc6??''' or '''5...dxc6??''', White can simply win a knight after '''6. Nxe4!.''' If Black plays '''5...Qe7??''', White can take the black queen, every other queen move loses a knight (The white knight on c6 can retreat back, making Black lose a knight). Every other move loses a queen due to ignoring the hanging queen. For example, '''5...Nxf2??''' is refuted by '''6. Qe2+!''', a check that sidesteps the attack entirely, and Black cannot stop '''7. Nxd8''', or '''7. Nxe7'''.), counterattacking the white queen. If White wishes to deal with this, either '''6. dxc3''', removing Black’s attacking knight on c3, after which Black removes White’s attacking knight on c6 by playing either '''6...dxc6''', or '''6...bxc6'''; or '''6. Nxd8,''' trading queens; will be good options according to Stockfish. If White plays '''6. Nxd8''', Black will respond with '''6...Nxd1''', recovering material.

{{Chess/board
| moves = 1. e4 e5 2. Nf3 Nc6 3. Nc3 Nf6 4. Nxe5 Nxe4 5. Nxc6 Nxc3 6. Nxd8 Nxd1
| caption = Position after Black's move of '''6...Nxd1'''.
}}

=== 5. Nxe4 ===
White takes the knight on e4. Black will likely follow up with '''5...Nxe5''', recovering material. '''6. d4''' is a good center attacking move for White that also gains tempo by kicking the black knight. The position is very drawish, with White being slightly better by having a better center.

{{Chess/board
| moves = 1. e4 e5 2. Nf3 Nc6 3. Nc3 Nf6 4. Nxe5 Nxe4 5. Nxe4 Nxe5 6. d4
| caption = Position after White's move of '''6. d4'''.
}}

=== 5. Qh5 ===
This is an uncommon move and also White's most aggressive option, directly threatening '''6. Qxf7#''', forcing Black into defense of their f7-square. Black can make a lot of mistakes from here. 

==== 5...Nxe5?? ====
Black plays the common blunder '''5...Nxe5??''', hoping to remove an attacker of the f7-square and trade pieces, White can take the knight with check ('''6. Qxe5+!'''), forcing the black king to cover, and now there is no way to save the e4 knight, there are simply too many attackers. If Black plays '''6...Qe7''' (Black's best try, since the queen x-ray defends the knight and counterattacks the queen), then White can play '''7. Qxe7+!''', then take the black knight on e4.

==== 5...g6? ====
If Black instead plays the also common mistake '''5...g6?''', mimicking the [[Chess Opening Theory/1. e4/1...e5/2. Qh5/2...Nc6/3. Bc4/3...g6|'''Wayward Queen Attack'''&lt;nowiki/&gt;'s most common defence]], Black loses a pawn after this sequence: '''6. Nxc6!''' (counterattacking the black queen) '''gxh5 7. Nxd8 Nxc3 8. Nxf7''' (White desperado sacrifices the white knight for a pawn, knowing the knight is doomed anyway, and Black cannot sacrifice his knight for any compensation, and if Black retreats, White can just escape with the free pawn.) '''Kxf7 9. dxc3'''.

==== 5...Nd6 ====
This is Black's fairly rare but best try, retreating the black knight to defend f7. But White can lunge forward with '''6. Nd5''', playing aggressively. White has very good winning chances here in this position. Black has to play precisely to survive in this position.

{{Chess/board
| moves = 1. e4 e5 2. Nf3 Nc6 3. Nc3 Nf6 4. Nxe5 Nxe4 5. Qh5 Nd6 6. Nd5
| caption = Position after White's move of '''6. Nd5'''.
}}

==== 5...Qf6?! ====
This is a better move than the blunders described on this page, but it is a small inaccuracy, since it allows White to win a pawn, make Black lose castling rights, and gain development. The best move for White is '''6. Qxf7+''', starting the trade that will win them a pawn and make Black lose castling rights. Then Black will regain material with '''6...Qxf7''', then White will regain material with '''7. Nxf7'''. The black king will then take on f7 with '''7...Kxf7''', losing castling rights. Now it seems like Black is ahead on material here, but the e4 knight is hanging, so White can win back the material and, in the end, they will have won a pawn. The best move for white now is not to take the black knight on e4 immediately but play an intermediate move (zwischenzug) by playing '''8. Bc4+''', forcing the king to move or block with the only legal block '''8...d5??''', There is no legal move that defends the knight and deals with the check at the same time except '''8...d5??''' which seems like it defends the black knight and blocks the check, but this blunders a pawn via '''9. Bxd5+''' and fails to defend the knight anyway since the pawn is the only defender of the knight. Black now must move the king, two good moves are the natural '''8... Ke8''', or the unnatural but best move by the engine (Stockfish 19 NNUE) '''8...Ke7'''. Then, White takes the knight with '''9. Nxe4,''' ending this tactical sequence with a bishop developed, a knight centralized, and a pawn gained.
{{Chess/board
| moves = 1. e4 e5 2. Nf3 Nc6 3. Nc3 Nf6 4. Nxe5 Nxe4 5. Qh5 Qf6 6. Qxf7+ Qxf7 7. Nxf7 Kxf7 8. Bc4+ Ke7 9. Nxe4
| caption = Position after White's move of '''9. Nxe4''' if Black played '''8...Ke7'''.
}}

== History ==
This line has no known history in books or tournament practice, and it is very rare. However, Lichess database statistics show that its popularity has increased over time. Between January 2017 and April 2026, the share of Lichess games reaching this position rose from roughly 0.0002% to about 0.0005-0.0007%, peaking at around 0.0007%, though with considerable fluctuation.&lt;ref&gt;{{Cite web |title=Four Knights Game: Halloween Gambit |url=https://lichess.org/opening/Four_Knights_Game_Halloween_Gambit/e4_e5_Nf3_Nc6_Nc3_Nf6_Nxe5_Nxe4 |access-date=2026-10-17 |website=lichess.org |language=en-US}}&lt;/ref&gt; For the history of the gambit itself, see the [[Chess Opening Theory/1. e4/1...e5/2. Nf3/2...Nc6/3. Nc3/3...Nf6/4. Nxe5|Halloween Gambit]] page.

== Theory table ==
{{ChessTable}}
{{Chess/theory table
|preceding=1. e4 e5 2. Nf3 Nc6 3. Nc3 Nf6 4. Nxe5 Nxe4
|line1=5. Nxc6 Nxc3 6. dxc3 dxc6
|eval1= =
|line2=5. Nxc6 Nxc3 6. Nxd8 Nxd1
|eval2= =
|line3=5. Nxe4 Nxe5 6. d4
|eval3= +/=
|line4=5. Qh5 Nxe5?? 6. Qxe5+ Qe7 7. Qxe7+
|eval4= +-
|line5=5. Qh5 g6? 6. Nxc6! gxh5 7. Nxd8 Nxc3 8. Nxf7 Kxf7 9. dxc3
|eval5= +/-
|line6=5. Qh5 Nd6 6. Nd5
|eval6= +/-
|line7=5.Qh5 Qf6?! 6. Qxf7+ Qxf7 7. Nxf7 Kxf7 8. Bc4+ Ke7 9. Nxe4|line8=5.Qh5 Qf6?! 6. Qxf7+ Qxf7 7. Nxf7 Kxf7 8. Bc4+ d5?? 9. Bxd5+|eval7=+/=|eval8=+-}}
{{ChessMid}}

== References ==</text>
      <sha1>qj4cd33hrr4deauwxfp6cz62lfnvvyj</sha1>
    </revision>
    <revision>
      <id>4676513</id>
      <parentid>4676511</parentid>
      <timestamp>2026-10-17T12:53:30Z</timestamp>
      <contributor>
        <username>Ltypestar2</username>
        <id>3524220</id>
      </contributor>
      <minor />
      <comment>Added See also, as recommended by the local manual of style.</comment>
      <origin>4676513</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="7592" sha1="axg546k1sx0s3jfoj8ay8bu9yhvo29e" xml:space="preserve">== 4...Nxe4?! ==
{{Chess Opening Theory/Position|name=Mirrored Halloween (informal)|eco=[[Chess/ECOC|C47]]|parent=[[../|Halloween Gambit]]}}
Black unusually declines the gambit and tries to mirror the [[Chess/Halloween Attack|'''Halloween Attack''']]'s sacrifice ('''4. Nxe5''') to counter the Halloween Attack. Although this recovers the pawn, it ignores the hanging knight and gives White back a drawish position, with higher winning chances for White. Worse, it unnecessarily keeps the position symmetrical, which means White still has a first move advantage.

This line has no established name, but it is informally called &quot;'''Mirrored Halloween'''&quot; here, because this is Black's mirroring response to the Halloween Attack's main move ('''4. Nxe5''').

There are usually 2 main moves White will most commonly try: '''5. Nxc6''', taking the black c6 knight and ignoring the hanging black e4 knight, and '''5. Nxe4''', taking the hanging black e4 knight, ignoring the hanging white knight on e5.

=== 5. Nxc6 ===
White takes the knight on c6, attacking the queen. Because Black has a hanging knight on e4, his only move is to counterattack by playing '''5...Nxc3!''' (Because if he takes the white knight with '''5...bxc6??''' or '''5...dxc6??''', White can simply win a knight after '''6. Nxe4!.''' If Black plays '''5...Qe7??''', White can take the black queen, every other queen move loses a knight (The white knight on c6 can retreat back, making Black lose a knight). Every other move loses a queen due to ignoring the hanging queen. For example, '''5...Nxf2??''' is refuted by '''6. Qe2+!''', a check that sidesteps the attack entirely, and Black cannot stop '''7. Nxd8''', or '''7. Nxe7'''.), counterattacking the white queen. If White wishes to deal with this, either '''6. dxc3''', removing Black’s attacking knight on c3, after which Black removes White’s attacking knight on c6 by playing either '''6...dxc6''', or '''6...bxc6'''; or '''6. Nxd8,''' trading queens; will be good options according to Stockfish. If White plays '''6. Nxd8''', Black will respond with '''6...Nxd1''', recovering material.

{{Chess/board
| moves = 1. e4 e5 2. Nf3 Nc6 3. Nc3 Nf6 4. Nxe5 Nxe4 5. Nxc6 Nxc3 6. Nxd8 Nxd1
| caption = Position after Black's move of '''6...Nxd1'''.
}}

=== 5. Nxe4 ===
White takes the knight on e4. Black will likely follow up with '''5...Nxe5''', recovering material. '''6. d4''' is a good center attacking move for White that also gains tempo by kicking the black knight. The position is very drawish, with White being slightly better by having a better center.

{{Chess/board
| moves = 1. e4 e5 2. Nf3 Nc6 3. Nc3 Nf6 4. Nxe5 Nxe4 5. Nxe4 Nxe5 6. d4
| caption = Position after White's move of '''6. d4'''.
}}

=== 5. Qh5 ===
This is an uncommon move and also White's most aggressive option, directly threatening '''6. Qxf7#''', forcing Black into defense of their f7-square. Black can make a lot of mistakes from here. 

==== 5...Nxe5?? ====
Black plays the common blunder '''5...Nxe5??''', hoping to remove an attacker of the f7-square and trade pieces, White can take the knight with check ('''6. Qxe5+!'''), forcing the black king to cover, and now there is no way to save the e4 knight, there are simply too many attackers. If Black plays '''6...Qe7''' (Black's best try, since the queen x-ray defends the knight and counterattacks the queen), then White can play '''7. Qxe7+!''', then take the black knight on e4.

==== 5...g6? ====
If Black instead plays the also common mistake '''5...g6?''', mimicking the [[Chess Opening Theory/1. e4/1...e5/2. Qh5/2...Nc6/3. Bc4/3...g6|'''Wayward Queen Attack'''&lt;nowiki/&gt;'s most common defence]], Black loses a pawn after this sequence: '''6. Nxc6!''' (counterattacking the black queen) '''gxh5 7. Nxd8 Nxc3 8. Nxf7''' (White desperado sacrifices the white knight for a pawn, knowing the knight is doomed anyway, and Black cannot sacrifice his knight for any compensation, and if Black retreats, White can just escape with the free pawn.) '''Kxf7 9. dxc3'''.

==== 5...Nd6 ====
This is Black's fairly rare but best try, retreating the black knight to defend f7. But White can lunge forward with '''6. Nd5''', playing aggressively. White has very good winning chances here in this position. Black has to play precisely to survive in this position.

{{Chess/board
| moves = 1. e4 e5 2. Nf3 Nc6 3. Nc3 Nf6 4. Nxe5 Nxe4 5. Qh5 Nd6 6. Nd5
| caption = Position after White's move of '''6. Nd5'''.
}}

==== 5...Qf6?! ====
This is a better move than the blunders described on this page, but it is a small inaccuracy, since it allows White to win a pawn, make Black lose castling rights, and gain development. The best move for White is '''6. Qxf7+''', starting the trade that will win them a pawn and make Black lose castling rights. Then Black will regain material with '''6...Qxf7''', then White will regain material with '''7. Nxf7'''. The black king will then take on f7 with '''7...Kxf7''', losing castling rights. Now it seems like Black is ahead on material here, but the e4 knight is hanging, so White can win back the material and, in the end, they will have won a pawn. The best move for white now is not to take the black knight on e4 immediately but play an intermediate move (zwischenzug) by playing '''8. Bc4+''', forcing the king to move or block with the only legal block '''8...d5??''', There is no legal move that defends the knight and deals with the check at the same time except '''8...d5??''' which seems like it defends the black knight and blocks the check, but this blunders a pawn via '''9. Bxd5+''' and fails to defend the knight anyway since the pawn is the only defender of the knight. Black now must move the king, two good moves are the natural '''8... Ke8''', or the unnatural but best move by the engine (Stockfish 19 NNUE) '''8...Ke7'''. Then, White takes the knight with '''9. Nxe4,''' ending this tactical sequence with a bishop developed, a knight centralized, and a pawn gained.
{{Chess/board
| moves = 1. e4 e5 2. Nf3 Nc6 3. Nc3 Nf6 4. Nxe5 Nxe4 5. Qh5 Qf6 6. Qxf7+ Qxf7 7. Nxf7 Kxf7 8. Bc4+ Ke7 9. Nxe4
| caption = Position after White's move of '''9. Nxe4''' if Black played '''8...Ke7'''.
}}

== History ==
This line has no known history in books or tournament practice, and it is very rare. However, Lichess database statistics show that its popularity has increased over time. Between January 2017 and April 2026, the share of Lichess games reaching this position rose from roughly 0.0002% to about 0.0005-0.0007%, peaking at around 0.0007%, though with considerable fluctuation.&lt;ref&gt;{{Cite web |title=Four Knights Game: Halloween Gambit |url=https://lichess.org/opening/Four_Knights_Game_Halloween_Gambit/e4_e5_Nf3_Nc6_Nc3_Nf6_Nxe5_Nxe4 |access-date=2026-10-17 |website=lichess.org |language=en-US}}&lt;/ref&gt; For the history of the gambit itself, see the [[Chess Opening Theory/1. e4/1...e5/2. Nf3/2...Nc6/3. Nc3/3...Nf6/4. Nxe5|Halloween Gambit]] page.

== Theory table ==
{{ChessTable}}
{{Chess/theory table
|preceding=1. e4 e5 2. Nf3 Nc6 3. Nc3 Nf6 4. Nxe5 Nxe4
|line1=5. Nxc6 Nxc3 6. dxc3 dxc6
|eval1= =
|line2=5. Nxc6 Nxc3 6. Nxd8 Nxd1
|eval2= =
|line3=5. Nxe4 Nxe5 6. d4
|eval3= +/=
|line4=5. Qh5 Nxe5?? 6. Qxe5+ Qe7 7. Qxe7+
|eval4= +-
|line5=5. Qh5 g6? 6. Nxc6! gxh5 7. Nxd8 Nxc3 8. Nxf7 Kxf7 9. dxc3
|eval5= +/-
|line6=5. Qh5 Nd6 6. Nd5
|eval6= +/-
|line7=5.Qh5 Qf6?! 6. Qxf7+ Qxf7 7. Nxf7 Kxf7 8. Bc4+ Ke7 9. Nxe4|line8=5.Qh5 Qf6?! 6. Qxf7+ Qxf7 7. Nxf7 Kxf7 8. Bc4+ d5?? 9. Bxd5+|eval7=+/=|eval8=+-}}
{{ChessMid}}

== See also ==
{{Chess Opening Theory/Footer}}

== References ==</text>
      <sha1>axg546k1sx0s3jfoj8ay8bu9yhvo29e</sha1>
    </revision>
    <revision>
      <id>4676682</id>
      <parentid>4676513</parentid>
      <timestamp>2026-10-18T04:05:08Z</timestamp>
      <contributor>
        <username>Ltypestar2</username>
        <id>3524220</id>
      </contributor>
      <minor />
      <comment>changed spelling to british spelling</comment>
      <origin>4676682</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="7684" sha1="svvx37qx79zea3tbnnb568eynmcrn5b" xml:space="preserve">== 4...Nxe4?!  · Mirrored Halloween (informal) ==
{{Chess Opening Theory/Position|name=Mirrored Halloween (informal)|eco=[[Chess/ECOC|C47]]|parent=[[../|Halloween Gambit]]}}
Black unusually declines the gambit and tries to mirror the [[Chess/Halloween Attack|'''Halloween Attack''']]'s sacrifice ('''4. Nxe5''') to counter the Halloween Attack. Although this recovers the pawn, it ignores the hanging knight and gives White back a drawish position, with higher winning chances for White. Worse, it unnecessarily keeps the position symmetrical, which means White still has a first move advantage.

This line has no established name, but it is informally called &quot;'''Mirrored Halloween'''&quot; here, because this is Black's mirroring response to the Halloween Attack's main move ('''4. Nxe5''').

There are usually 2 main moves White will most commonly try: '''5. Nxc6''', taking the black c6 knight and ignoring the hanging black e4 knight, and '''5. Nxe4''', taking the hanging black e4 knight, ignoring the hanging white knight on e5.

=== 5. Nxc6 ===
White takes the knight on c6, attacking the queen. Because Black has a hanging knight on e4, his only move is to counterattack by playing '''5...Nxc3!''' (Because if he takes the white knight with '''5...bxc6??''' or '''5...dxc6??''', White can simply win a knight after '''6. Nxe4!.''' If Black plays '''5...Qe7??''', White can take the black queen, every other queen move loses a knight (The white knight on c6 can retreat back, making Black lose a knight). Every other move loses a queen due to ignoring the hanging queen. For example, '''5...Nxf2??''' is refuted by '''6. Qe2+!''', a check that sidesteps the attack entirely, and Black cannot stop '''7. Nxd8''', or '''7. Nxe7'''.), counterattacking the white queen. If White wishes to deal with this, either '''6. dxc3''', removing Black’s attacking knight on c3, after which Black removes White’s attacking knight on c6 by playing either '''6...dxc6''', or '''6...bxc6'''; or '''6. Nxd8,''' trading queens; will be good options according to Stockfish. If White plays '''6. Nxd8''', Black will respond with '''6...Nxd1''', recovering material.

{{Chess/board
| moves = 1. e4 e5 2. Nf3 Nc6 3. Nc3 Nf6 4. Nxe5 Nxe4 5. Nxc6 Nxc3 6. Nxd8 Nxd1
| caption = Position after Black's move of '''6...Nxd1'''.
}}

=== 5. Nxe4 ===
White takes the knight on e4. Black will likely follow up with '''5...Nxe5''', recovering material. '''6. d4''' is a good centre attacking move for White that also gains tempo by kicking the black knight. The position is very drawish, with White being slightly better by having a better centre.

{{Chess/board
| moves = 1. e4 e5 2. Nf3 Nc6 3. Nc3 Nf6 4. Nxe5 Nxe4 5. Nxe4 Nxe5 6. d4
| caption = Position after White's move of '''6. d4'''.
}}

=== 5. Qh5 ===
This is an uncommon move and also White's most aggressive option, directly threatening '''6. Qxf7#''', forcing Black into defence of their f7-square. Black can make a lot of mistakes from here. 

==== 5...Nxe5?? ====
Black plays the common blunder '''5...Nxe5??''', hoping to remove an attacker of the f7-square and trade pieces, White can take the knight with check ('''6. Qxe5+!'''), forcing the black king to cover, and now there is no way to save the e4 knight, there are simply too many attackers. If Black plays '''6...Qe7''' (Black's best try, since the queen x-ray defends the knight and counterattacks the queen), then White can play '''7. Qxe7+!''', then take the black knight on e4.

==== 5...g6? ====
If Black instead plays the also common mistake '''5...g6?''', mimicking the [[Chess Opening Theory/1. e4/1...e5/2. Qh5/2...Nc6/3. Bc4/3...g6|'''Wayward Queen Attack'''&lt;nowiki/&gt;'s most common defence]], Black loses a pawn after this sequence: '''6. Nxc6!''' (counterattacking the black queen) '''gxh5 7. Nxd8 Nxc3 8. Nxf7''' (White desperado sacrifices the white knight for a pawn, knowing the knight is doomed anyway, and Black cannot sacrifice his knight for any compensation, and if Black retreats, White can just escape with the free pawn.) '''Kxf7 9. dxc3'''.

==== 5...Nd6 ====
This is Black's fairly rare but best try, retreating the black knight to defend f7. But White can lunge forward with '''6. Nd5''', playing aggressively. White has very good winning chances here in this position. Black has to play precisely to survive in this position.

{{Chess/board
| moves = 1. e4 e5 2. Nf3 Nc6 3. Nc3 Nf6 4. Nxe5 Nxe4 5. Qh5 Nd6 6. Nd5
| caption = Position after White's move of '''6. Nd5'''.
}}

==== 5...Qf6?! ====
This is a better move than the blunders described on this page, but it is a small inaccuracy, since it allows White to win a pawn, make Black lose castling rights, and gain development. The best move for White is '''6. Qxf7+''', starting the trade that will win them a pawn and make Black lose castling rights. Then Black will regain material with '''6...Qxf7''', then White will regain material with '''7. Nxf7'''. The black king will then take on f7 with '''7...Kxf7''', losing castling rights. Now it seems like Black is ahead on material here, but the e4 knight is hanging, so White can win back the material and, in the end, they will have won a pawn. The best move for White now is not to take the black knight on e4 immediately but play an intermediate move (zwischenzug) by playing '''8. Bc4+''', forcing the king to move or block with the only legal block '''8...d5??'''. There is no legal move that defends the knight and deals with the check at the same time except '''8...d5??''' which seems like it defends the black knight and blocks the check, but this blunders a pawn via '''9. Bxd5+''' and fails to defend the knight anyway since the pawn is the only defender of the knight. Black now must move the king, two good moves are the natural '''8...Ke8''', or the unnatural but best move by the engine (Stockfish 19 NNUE) '''8...Ke7'''. Then, White takes the knight with '''9. Nxe4,''' ending this tactical sequence with a bishop developed, a knight centralised, a black king that lost castling rights, and a pawn gained.

{{Chess/board
| moves = 1. e4 e5 2. Nf3 Nc6 3. Nc3 Nf6 4. Nxe5 Nxe4 5. Qh5 Qf6 6. Qxf7+ Qxf7 7. Nxf7 Kxf7 8. Bc4+ Ke7 9. Nxe4
| caption = Position after White's move of '''9. Nxe4''' if Black played '''8...Ke7'''.
}}

== History ==
This line has no known history in books or tournament practice, and it is very rare. However, Lichess database statistics show that its popularity has increased over time. Between January 2017 and April 2026, the share of Lichess games reaching this position rose from roughly 0.0002% to about 0.0005-0.0007%, peaking at around 0.0007%, though with considerable fluctuation.&lt;ref&gt;{{Cite web |title=Four Knights Game: Halloween Gambit |url=https://lichess.org/opening/Four_Knights_Game_Halloween_Gambit/e4_e5_Nf3_Nc6_Nc3_Nf6_Nxe5_Nxe4 |access-date=2026-10-17 |website=lichess.org |language=en-US}}&lt;/ref&gt; For the history of the gambit itself, see the [[Chess Opening Theory/1. e4/1...e5/2. Nf3/2...Nc6/3. Nc3/3...Nf6/4. Nxe5|Halloween Gambit]] page.

== Theory table ==
{{ChessTable}}
{{Chess/theory table
|preceding=1. e4 e5 2. Nf3 Nc6 3. Nc3 Nf6 4. Nxe5 Nxe4
|line1=5. Nxc6 Nxc3 6. dxc3 dxc6
|eval1= =
|line2=5. Nxc6 Nxc3 6. Nxd8 Nxd1
|eval2= =
|line3=5. Nxe4 Nxe5 6. d4
|eval3= +/=
|line4=5. Qh5 Nxe5?? 6. Qxe5+ Qe7 7. Qxe7+
|eval4= +-
|line5=5. Qh5 g6? 6. Nxc6! gxh5 7. Nxd8 Nxc3 8. Nxf7 Kxf7 9. dxc3
|eval5= +/-
|line6=5. Qh5 Nd6 6. Nd5
|eval6= +/-
|line7=5. Qh5 Qf6?! 6. Qxf7+ Qxf7 7. Nxf7 Kxf7 8. Bc4+ Ke7 9. Nxe4
|eval7= +/=
|line8=5. Qh5 Qf6?! 6. Qxf7+ Qxf7 7. Nxf7 Kxf7 8. Bc4+ d5?? 9. Bxd5+
|eval8= +-
}}
{{ChessMid}}
== References ==
{{reflist}}
== See also ==
{{Chess Opening Theory/Footer}}</text>
      <sha1>svvx37qx79zea3tbnnb568eynmcrn5b</sha1>
    </revision>
  </page>
  <page>
    <title>About Monsters And Angels</title>
    <ns>0</ns>
    <id>485372</id>
    <revision>
      <id>4676540</id>
      <parentid>4676338</parentid>
      <timestamp>2026-10-17T15:07:46Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <origin>4676540</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1960" sha1="pkwpjjygcugft0lzac4lsziif6uwgdu" xml:space="preserve"> &lt;br&gt;'''Monster, a threatening force from the far-side.''' &lt;br&gt;&lt;br&gt;This book will introduce four fictional creations with odd human connections: &lt;br&gt;zombie-person &lt;br&gt;ghost-person &lt;br&gt;werewolf-person &lt;br&gt;demon-person &lt;br&gt;...and Angels. &lt;br&gt;&lt;br&gt;This book is intended as a short conceptual guide for readers interested in folklore, storytelling, monsters and angels. &lt;br&gt;Link: [[About_Monsters_And_Angels/Questions_And_Answers|About Monsters And Angels: Questions And Answers]]

&lt;br&gt;

{| class=&quot;wikitable&quot;
|+ About Monsters And Angels
|-
! Guardian Angel !! The Sleep Of Reason Produces Monsters
|-
| [[File:The story of our Christianity; an account of the struggles, persecutions, wars, and victories of Christians of all times (1893) (14783658362).jpg|thumb|The story of our Christianity; an account of the struggles, persecutions, wars, and victories of Christians of all times (1893) (14783658362)]] || [[File:Plate 43 from 'Los Caprichos'- The sleep of reason produces monsters (El sueño de la razon produce monstruos) MET MM2149.jpg|thumb|Plate 43 from 'Los Caprichos': The sleep of reason produces monsters (El sueño de la razon produce monstruos), print, Goya (Francisco de Goya y Lucientes) (MET, 18.64(43))]]
|}
&lt;br&gt; 
&lt;br&gt;
 &lt;br&gt; &quot;Monsters are real, and ghosts are real too. They live inside of us, and sometimes, they win.&quot; - Stephen King
&lt;br&gt;

 &lt;br&gt;'''Table Of Content:'''&lt;br&gt;[[About_Monsters_And_Angels_Introduction|Introduction]] To Monsters!&lt;br&gt;[[About_Monsters_And_Angels/Chapter_One|Chapter One]]: Monsters And Their Human Origin &lt;br&gt;Chapter Two&lt;br&gt;Chapter Three&lt;br&gt;Chapter Four&lt;br&gt;Chapter Five&lt;br&gt;Chapter Six&lt;br&gt;Chapter Seven&lt;br&gt;Chapter Eight&lt;br&gt;Chapter Nine&lt;br&gt;Chapter Ten&lt;br&gt;
&lt;br&gt;
&lt;br&gt;
{{New book}}
&lt;br&gt;
{{Formatting}}
&lt;br&gt;
{{BookCat}}
{{Shelves|Literature|Paranormal|Cultural anthropology}}
&lt;br&gt;
[[Category:Book:About Monsters And Angels]]
&lt;br&gt;
{{status|0%}}
&lt;br&gt;
&lt;noinclude&gt;{{Chapter navigation with TOC||Chapter One|TOC mini}}&lt;/noinclude&gt;</text>
      <sha1>pkwpjjygcugft0lzac4lsziif6uwgdu</sha1>
    </revision>
    <revision>
      <id>4676544</id>
      <parentid>4676540</parentid>
      <timestamp>2026-10-17T15:15:07Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <origin>4676544</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1988" sha1="60t78vw9dnuwhcm3poo1cohyggal7vo" xml:space="preserve"> &lt;br&gt;'''Monster, a threatening force from the far-side.''' &lt;br&gt;&lt;br&gt;This book will introduce four fictional creations with odd human connections: &lt;br&gt;zombie-person &lt;br&gt;ghost-person &lt;br&gt;werewolf-person &lt;br&gt;demon-person &lt;br&gt;...and Angels. &lt;br&gt;&lt;br&gt;This book is intended as a short conceptual guide for readers interested in folklore, storytelling, monsters and angels. &lt;br&gt;Link: [[About_Monsters_And_Angels/Questions_And_Answers|About Monsters And Angels: Questions And Answers]]

&lt;br&gt;

{| class=&quot;wikitable&quot;
|+ About Monsters And Angels
|-
! Guardian Angel !! The Sleep Of Reason Produces Monsters
|-
| [[File:The story of our Christianity; an account of the struggles, persecutions, wars, and victories of Christians of all times (1893) (14783658362).jpg|thumb|The story of our Christianity; an account of the struggles, persecutions, wars, and victories of Christians of all times (1893) (14783658362)]] || [[File:Plate 43 from 'Los Caprichos'- The sleep of reason produces monsters (El sueño de la razon produce monstruos) MET MM2149.jpg|thumb|Plate 43 from 'Los Caprichos': The sleep of reason produces monsters (El sueño de la razon produce monstruos), print, Goya (Francisco de Goya y Lucientes) (MET, 18.64(43))]]
|}
&lt;br&gt; 
&lt;br&gt;
 &lt;br&gt; &quot;Monsters are real, and ghosts are real too. They live inside of us, and sometimes, they win.&quot; - Stephen King
&lt;br&gt;

 &lt;br&gt;'''Table Of Content:'''&lt;br&gt;
[[About_Monsters_And_Angels/Introduction|About Monsters And Angels: Introduction]] To Monsters!&lt;br&gt;[[About_Monsters_And_Angels/Chapter_One|Chapter One]]: Monsters And Their Human Origin &lt;br&gt;Chapter Two&lt;br&gt;Chapter Three&lt;br&gt;Chapter Four&lt;br&gt;Chapter Five&lt;br&gt;Chapter Six&lt;br&gt;Chapter Seven&lt;br&gt;Chapter Eight&lt;br&gt;Chapter Nine&lt;br&gt;Chapter Ten&lt;br&gt;
&lt;br&gt;
&lt;br&gt;
{{New book}}
&lt;br&gt;
{{Formatting}}
&lt;br&gt;
{{BookCat}}
{{Shelves|Literature|Paranormal|Cultural anthropology}}
&lt;br&gt;
[[Category:Book:About Monsters And Angels]]
&lt;br&gt;
{{status|0%}}
&lt;br&gt;
&lt;noinclude&gt;{{Chapter navigation with TOC||Chapter One|TOC mini}}&lt;/noinclude&gt;</text>
      <sha1>60t78vw9dnuwhcm3poo1cohyggal7vo</sha1>
    </revision>
    <revision>
      <id>4676546</id>
      <parentid>4676544</parentid>
      <timestamp>2026-10-17T15:19:00Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <origin>4676546</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1973" sha1="q9af5t219lr679dy60xq9gsabz7pvsy" xml:space="preserve"> &lt;br&gt;'''Monster, a threatening force from the far-side.''' &lt;br&gt;&lt;br&gt;This book will introduce four fictional creations with odd human connections: &lt;br&gt;zombie-person &lt;br&gt;ghost-person &lt;br&gt;werewolf-person &lt;br&gt;demon-person &lt;br&gt;...and Angels. &lt;br&gt;&lt;br&gt;This book is intended as a short conceptual guide for readers interested in folklore, storytelling, monsters and angels. &lt;br&gt;Link: [[About_Monsters_And_Angels/Questions_And_Answers|About Monsters And Angels: Questions And Answers]]

&lt;br&gt;

{| class=&quot;wikitable&quot;
|+ About Monsters And Angels
|-
! Guardian Angel !! The Sleep Of Reason Produces Monsters
|-
| [[File:The story of our Christianity; an account of the struggles, persecutions, wars, and victories of Christians of all times (1893) (14783658362).jpg|thumb|The story of our Christianity; an account of the struggles, persecutions, wars, and victories of Christians of all times (1893) (14783658362)]] || [[File:Plate 43 from 'Los Caprichos'- The sleep of reason produces monsters (El sueño de la razon produce monstruos) MET MM2149.jpg|thumb|Plate 43 from 'Los Caprichos': The sleep of reason produces monsters (El sueño de la razon produce monstruos), print, Goya (Francisco de Goya y Lucientes) (MET, 18.64(43))]]
|}
&lt;br&gt; 
&lt;br&gt;
 &lt;br&gt; &quot;Monsters are real, and ghosts are real too. They live inside of us, and sometimes, they win.&quot; - Stephen King
&lt;br&gt;

 &lt;br&gt;'''Table Of Content:'''&lt;br&gt;
[[About_Monsters_And_Angels/Introduction|About Monsters And Angels: Introduction]] To Monsters!&lt;br&gt;[[About_Monsters_And_Angels/Chapter_One|Chapter One]]: Monsters And Their Human Origin &lt;br&gt;Chapter Two&lt;br&gt;Chapter Three&lt;br&gt;Chapter Four&lt;br&gt;Chapter Five&lt;br&gt;Chapter Six&lt;br&gt;Chapter Seven&lt;br&gt;Chapter Eight&lt;br&gt;Chapter Nine&lt;br&gt;Chapter Ten&lt;br&gt;
&lt;br&gt;
&lt;br&gt;
{{New book}}
&lt;br&gt;
&lt;br&gt;
{{BookCat}}
{{Shelves|Literature|Paranormal|Cultural anthropology}}
&lt;br&gt;
[[Category:Book:About Monsters And Angels]]
&lt;br&gt;
{{status|0%}}
&lt;br&gt;
&lt;noinclude&gt;{{Chapter navigation with TOC||Chapter One|TOC mini}}&lt;/noinclude&gt;</text>
      <sha1>q9af5t219lr679dy60xq9gsabz7pvsy</sha1>
    </revision>
  </page>
  <page>
    <title>Maxima/Programming</title>
    <ns>0</ns>
    <id>485506</id>
    <revision>
      <id>4676537</id>
      <parentid>4674792</parentid>
      <timestamp>2026-10-17T14:44:54Z</timestamp>
      <contributor>
        <username>Idavidmiller</username>
        <id>3577687</id>
      </contributor>
      <comment>/* Memoizing Functions */ Work in progress. Saving Changes.</comment>
      <origin>4676537</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="43800" sha1="fdxd0wni6u69dvyosk8zmyqoet5webh" xml:space="preserve">=Maxima Programming=
Although Maxima is not a general-purpose programming language, Maxima as a CAS includes among the built-in ingredients a relatively complete set of programming expressions that are useful for the intended context. Many of the code examples of this section are intended to be illustrative of technical details relevant to Maxima programming as their purpose, and consequently are intentionally elementary in character.

Learning any sort of programming language, including Maxima programming expressions, is a subjective process. In any case, it is essential to have enough technical know-how specific to the programming language in order to begin the learning process, even in cases where much positive transfer from other programming experience is involved.

Much can be accomplished mathematically using Maxima without having to resort to in-depth knowledge and proficiency in the technical details of Maxima programming expressions. However, Maxima programming expressions are frequently essential for the purpose of defining functions, both in the programming sense of the term, but also more relevantly, for the mathematical sense. For that reason alone, familiarity and sufficient proficiency with Maxima programming expressions should be given some attention.

One way to begin the learning process is to become familiar with enough of the programming essentials to accomplish independent efforts toward accomplishing some specific programming goal of interest.  The other way is to study the many available programming expressions of others. This section is intended to provide the essentials toward learning by whatever means are chosen.

The following table shows some built-in ingredients related to Maxima programming expressions:
{| class=&quot;wikitable&quot;
|+Maxima Programming Category
|if
|unless
|errcatch
|prederror
|-
|block
|for
|error
|return
|-
|catch
|from
|warning
|throw 
|-
|local
|thru
|errormsg
|sstatus
|-
|garbage_collect
|step
|errormsg
|status
|-
|do
|next
|go
|
|-
|while
|in
|
|
|}

Some of these programming expression ingredients can also be considered as belonging to one or more other categories than the Programming category.

=== Block Expressions ===
Arguably, the first expressions to consider in the context of Maxima programming are '''''block''''' expressions. All &lt;code&gt;block&lt;/code&gt; expressions as programming ingredients come in two flavors:

* &lt;code&gt;( expr&lt;sub&gt;1&lt;/sub&gt;, expr&lt;sub&gt;2&lt;/sub&gt;,…, expr&lt;sub&gt;n&lt;/sub&gt; )&lt;/code&gt;
* &lt;code&gt;block ([v&lt;sub&gt;1&lt;/sub&gt;,v&lt;sub&gt;2,&lt;/sub&gt;…,v&lt;sub&gt;m&lt;/sub&gt;], expr&lt;sub&gt;1&lt;/sub&gt;, expr&lt;sub&gt;2&lt;/sub&gt;,…, expr&lt;sub&gt;n&lt;/sub&gt;)&lt;/code&gt;

The first form of a &lt;code&gt;block&lt;/code&gt; expression is equivalent to the second form, but without the first list argument: &lt;code&gt;[v&lt;sub&gt;1&lt;/sub&gt;,v&lt;sub&gt;2,&lt;/sub&gt;…,v&lt;sub&gt;m&lt;/sub&gt;]&lt;/code&gt;, as in &lt;code&gt;block (expr&lt;sub&gt;1&lt;/sub&gt;, expr&lt;sub&gt;2&lt;/sub&gt;,…, expr&lt;sub&gt;n&lt;/sub&gt;&lt;/code&gt;, unless &lt;code&gt;return&lt;/code&gt; or &lt;code&gt;go&lt;/code&gt; operators are used in the block expression. In that, case the form &lt;code&gt;block (expr&lt;sub&gt;1&lt;/sub&gt;, expr&lt;sub&gt;2&lt;/sub&gt;,…, expr&lt;sub&gt;n&lt;/sub&gt;)&lt;/code&gt; must be used. It should be noted that for Maxima to interpret of the syntax of the first of these forms as a block operator, there must be at least two expressions in the comma-separated sequence of expressions as arguments. Otherwise, Maxima will interpret the parentheses of this syntax as simply grouping related to the precedence order of operations.

The purpose of the list argument,  &lt;code&gt;[v&lt;sub&gt;1&lt;/sub&gt;,v&lt;sub&gt;2,&lt;/sub&gt;…,v&lt;sub&gt;m&lt;/sub&gt;]&lt;/code&gt; is to declare the values of identifiers of the list to be local to the &lt;code&gt;block&lt;/code&gt;. If there is no need for local identifiers, the list argument can be omitted (unless &lt;code&gt;return&lt;/code&gt; or &lt;code&gt;go&lt;/code&gt; operators are used in the &lt;code&gt;block&lt;/code&gt; expression), and either form is sufficient.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* This block expression */
(%i1)	(x : 2, x^2);
(%o1)	4

/* Is equivalent to this block expression */
(%i2)	block (x : 2, x^2);
(%o2)	4&lt;/syntaxhighlight&gt;So, in the case where values of identifiers local to the &lt;code&gt;block&lt;/code&gt; of expressions are not required, then the choice of either form of the &lt;code&gt;block&lt;/code&gt; expression is a matter of user preference. In both cases, the values of identifiers referenced in the &lt;code&gt;block&lt;/code&gt; are global, and not local to the &lt;code&gt;block&lt;/code&gt; expression. However, for the sake of clarity and consistency use of the latter form may be a better choice. &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* The value 3 assigned to x is global */
(%i3)	x : 3;
(x)	    3

/* The value 2 assigned to x in the block is global */
(%i4)	(x : 2, x^2);
(%o4)	4

/* The global value assigned to x in the block is 2 not 3 */
(%i5)	x;
(%o5)	2
&lt;/syntaxhighlight&gt;Values of identifiers local to the &lt;code&gt;block&lt;/code&gt; may not be global:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* the value of identifier y is local only */
(%i6)	block ([y], y : 4, y);
(%o6)	4

/* the global value of identifier y is not 4, but is itself */
(%i7)	y;
(%o7)	y

/* the values of identifiers x and y are both local */
(%i8)	block ([x,y], x : 3, y : 4, x);
(%o8)	3

/* the global value of identifier x is not 3, but is 2 */
(%i9)	x;
(%o9)	2

/* the global value of identifier y is not 4, but is itself */
(%i10)	y;
(%o10)	y&lt;/syntaxhighlight&gt;

Regardless of the form of the &lt;code&gt;block&lt;/code&gt; expressions these have in common the comma-separated expression arguments &lt;code&gt;expr&lt;sub&gt;1&lt;/sub&gt;, expr&lt;sub&gt;2&lt;/sub&gt;,…, expr&lt;sub&gt;n&lt;/sub&gt;&lt;/code&gt;  which are evaluated each in turn from first to last (unless the evaluation sequence is modified by by the &lt;code&gt;go&lt;/code&gt;, &lt;code&gt;throw&lt;/code&gt;, or &lt;code&gt;return&lt;/code&gt; operators), and the value of the block expression is the value of &lt;code&gt;expr&lt;sub&gt;n&lt;/sub&gt;&lt;/code&gt;. 

The main purpose of the &lt;code&gt;block&lt;/code&gt; expression, regardless of the form, is to group expressions that are related in some manner, and the value of the last expression may be the only value of interest. However, there are very few limitations imposed on the nature of the &lt;code&gt;block&lt;/code&gt; expression arguments, so it might be the case that the purpose of evaluating the &lt;code&gt;block&lt;/code&gt; expression has been achieved before the last expression argument is evaluated, in which case the value of the &lt;code&gt;block&lt;/code&gt; expression may not necessarily be the value of the last argument expression.

One way to accomplish that is to use an empty string as the last argument expression with the option flag &lt;code&gt;stringdisp&lt;/code&gt; set to &lt;code&gt;false&lt;/code&gt; which is the default value.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i11)	stringdisp;
(%o11)	false

(%i12)	block ([x,y], x : 3, y : 4, x, &quot;&quot;);
(%o12)	

(%i13)	block ([x,y], x : 3, y : 4, x)$
&lt;/syntaxhighlight&gt;
The display of the value of the &lt;code&gt;block&lt;/code&gt; expression may be suppressed using a &lt;code&gt;$&lt;/code&gt; to end the input expression instead of a semi-colon. Either technique produces a &lt;code&gt;block&lt;/code&gt; expression value, but the value is not displayed. If a &lt;code&gt;return&lt;/code&gt; operator is evaluated as a argument expression, this will cause evaluation of expression arguments to end explicitly, and the value of the &lt;code&gt;return&lt;/code&gt; operator becomes the value of the &lt;code&gt;block&lt;/code&gt; expression.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i14)	is (equal (x, 2));
(%o14)	true

%i15)	block (if is (equal (x, 2)) then return (x), &quot; x not 2&quot;);
(%o15)	2

(%i16)	x : 3;
(x)	3

(%i17)	block (if is (equal (x, 2)) then return (x), &quot;x not 2&quot;);
(%o17)	x not 2
&lt;/syntaxhighlight&gt;When a &lt;code&gt;return&lt;/code&gt; operator is evaluated within a &lt;code&gt;block&lt;/code&gt; expression the result is to stop evaluation of expressions within the enclosing &lt;code&gt;block&lt;/code&gt; expression and to return the value of its argument as the value of the enclosing &lt;code&gt;block&lt;/code&gt; expression. It therefore can be compared with the &lt;code&gt;return&lt;/code&gt; statement found in other programming languages, but with one difference: In Maxima, the &lt;code&gt;return&lt;/code&gt; operator affects only the block expression in which the &lt;code&gt;return&lt;/code&gt; operator is an expression, and has no effect otherwise.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i18)	test_nested_block (val) := 
	block (
		  [outer_var : 10],
		  print(&quot;Entering outer block expression&quot;),
		  
		       /* inner block expression */
		       block(
		           [inner_var : 20],
		           print (&quot;      Entering inner block expression&quot;),
	        
		           if val &gt; 5 then
	        
	               /* another inner block expression */  
	               block (
	               print (&quot;   val &gt; 5&quot;),
	               print (&quot;   Returning only to inner block expression&quot;),
		           return (inner_var + val)
	        	   /* returns only to the inner block expression */
	               ),
	               /* end of another inner block expression */
	        
	               print (&quot;   inner_var + val is &quot;, inner_var + val)
		           ),     
	               /* end of inner block expression */
		  
		  print (&quot;Back in outer block expression&quot;),
		  outer_var + val
		  
	/* end of outer block expression */
	)$

(%i19)	test_nested_block (1);
Entering outer block expression
      Entering inner block expression
      inner_var + val is 21
Back in outer block expression
(%o19)	11

(%i20)	test_nested_block (6);
Entering outer block expression
      Entering inner block expression
      val &gt; 5
      Returning only to inner block expression
Back in outer block expression
(%o20)	16&lt;/syntaxhighlight&gt;


'''''The &lt;code&gt;block&lt;/code&gt; operators''''': Each instance may define local variables and has a comma-separated sequence of expressions as arguments.

'''''Nested blocks''''': There are three &lt;code&gt;block&lt;/code&gt; operators used in the right-hand side of the function definition expression named &lt;code&gt;test_nested_block (val&lt;/code&gt;. There is an outer &lt;code&gt;block&lt;/code&gt; expression that has an inner &lt;code&gt;block&lt;/code&gt; expression as an argument,and there is a third &lt;code&gt;block&lt;/code&gt; expression that is an argument of the inner &lt;code&gt;block&lt;/code&gt; expression.

'''''The &lt;code&gt;return&lt;/code&gt; operator''''': If &lt;code&gt;val &gt; 5&lt;/code&gt; is &lt;code&gt;true&lt;/code&gt; then the return operator of the most inner  &lt;code&gt;block&lt;/code&gt; expression is evaluated and evaluation of remaining expressions of that block expression does not occur. The value of that most inner &lt;code&gt;block&lt;/code&gt; expression is the value of the argument of the return operator –  &lt;code&gt;inner_var + val&lt;/code&gt;. 

Evaluation of expressions continues with the first expression of the inner &lt;code&gt;block&lt;/code&gt; expression after the end of the most inner &lt;code&gt;block&lt;/code&gt; expression  – which is &lt;code&gt;print (&quot;   inner_var + val is &quot;, inner_var + val)&lt;/code&gt;. The value of the &lt;code&gt;print&lt;/code&gt; operator is the value of  &lt;code&gt;inner_var + val&lt;/code&gt;. However, while that value is the value of the inner &lt;code&gt;block&lt;/code&gt; expression it is effectively lost, as it is not the last expression of the outer &lt;code&gt;block&lt;/code&gt; sequence of expressions.  That value is the value of &lt;code&gt;outer_var + val&lt;/code&gt;, which, being the last expression of the outer &lt;code&gt;block&lt;/code&gt; is always the value of the function.

==== Block Expression Evaluation Sequence Modifications ====
&lt;code&gt;block&lt;/code&gt; expression arguments &lt;code&gt;expr&lt;sub&gt;1&lt;/sub&gt;, expr&lt;sub&gt;2&lt;/sub&gt;,…, expr&lt;sub&gt;n&lt;/sub&gt;&lt;/code&gt;  are generally evaluated each in turn from first to last, and the value of the &lt;code&gt;block&lt;/code&gt; expression is the value of &lt;code&gt;expr&lt;sub&gt;n&lt;/sub&gt;&lt;/code&gt; unless this sequence is modified by some means.

One way to modify the first-to-last expression evaluation sequence of a &lt;code&gt;block&lt;/code&gt; expression is by way of a &lt;code&gt;go&lt;/code&gt; operator with a ''label'' (or ''&quot;tag&quot;'') argument ( the ''&quot;go to&quot;'') as the following exemplifies:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i18)	sum_to_n (n) := block ( [i : 1, total : 0],
	                             loop,
	                                total : total + i,
	                                i : i + 1,
	                                if i &lt;= n then go (loop),
	                             total)$

(%i19)	sum_to_n(25);
(%o19)	325

(%i20)	n;
(%o20)	n

(%i21)	i;
(%o21)	i

(%i22)	total;
(%o22)	total
&lt;/syntaxhighlight&gt;


Note the following:

* &lt;code&gt;'''block ([ i : 1,total : 0], ...)'''&lt;/code&gt;: The list argument creates a local environment with local identifiers &lt;code&gt;i&lt;/code&gt; and &lt;code&gt;total&lt;/code&gt;. The function argument &lt;code&gt;n&lt;/code&gt; is also a local identifier.
* &lt;code&gt;'''loop'''&lt;/code&gt;: This label serves as a target inside the &lt;code&gt;block&lt;/code&gt; expression to where &lt;code&gt;go (loop)&lt;/code&gt; can jump.
* &lt;code&gt;'''if i &lt;= n then go (loop)'''&lt;/code&gt;: This conditional expression causes the &lt;code&gt;go (loop)&lt;/code&gt; operator to be evaluated if the condition is &lt;code&gt;true&lt;/code&gt;.
* &lt;code&gt;'''total'''&lt;/code&gt;: The value of this local identifier is the returned value of the &lt;code&gt;block&lt;/code&gt; expression.
It should also be worth noting that the identifiers &lt;code&gt;n&lt;/code&gt;, &lt;code&gt;i&lt;/code&gt;, and &lt;code&gt;total&lt;/code&gt; have local values assigned within the &lt;code&gt;block&lt;/code&gt; expression, but their global values are themselves. Also notice that the identifiers &lt;code&gt;i&lt;/code&gt; and &lt;code&gt;total&lt;/code&gt; were both declared local and assigned initial values within the &lt;code&gt;block&lt;/code&gt; list argument.

The ''go-to'' label argument of the &lt;code&gt;go&lt;/code&gt; operator must be the name of a tag appearing within the same block expression. The &lt;code&gt;go&lt;/code&gt; operator cannot be used to go to a tag in a different &lt;code&gt;block&lt;/code&gt; expression. There is nothing special about the &lt;code&gt;loop&lt;/code&gt; identifier name used for the go-to tag in this example. Other identifiers could be used, but they must be atomic.

Another way to modify a &lt;code&gt;block&lt;/code&gt; expression evaluation sequence is by way of the &lt;code&gt;throw&lt;/code&gt; operator.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i32)	/* Define a function using a block expression that searches 
	     for a specific condition and a throw value to catch */
	
	find_element (target_list, threshold) := block (
	      
	    [found_val : false], /* local identifier value */
	    
	      catch(
	          
	        for x in target_list do 
	          (
	              if x &gt; threshold then 
	                (
	                  /* Immediately exit the block and 
	                     return this value */
	                  throw (x)
	                  )
	            ),
	          /* This string is returned only if the do loop 
	             finishes without a throw to catch */
	                 &quot;No element exceeded the threshold&quot;
	      )
	    
	)$

(%i31)	/* Test the block */
	find_element ( [10, 20, 55, 80], 50 );
(%o31)	55&lt;/syntaxhighlight&gt;This example unpacks as follows:

&lt;code&gt;'''catch (...)'''&lt;/code&gt;: This expression creates a target scope that ''&quot;catches&quot;'' the value of any &lt;code&gt;throw&lt;/code&gt; expression evaluated within that scope.

&lt;code&gt;'''throw (x)'''&lt;/code&gt;: When Maxima encounters this operator, it immediately stops evaluation of the &lt;code&gt;do&lt;/code&gt; loop expression '''''and the rest of the''''' &lt;code&gt;block&lt;/code&gt; '''''expression.''''' It jumps directly out of the scope of the &lt;code&gt;catch&lt;/code&gt; expression, returning the value of &lt;code&gt;x&lt;/code&gt; as the value of the entire &lt;code&gt;catch&lt;/code&gt; expression.

==== Nested Block Expressions ====
&lt;code&gt;block&lt;/code&gt; operators may appear within other block expressions as arguments – '''''nested''''' &lt;code&gt;block&lt;/code&gt; expressions. A local environment with local identifiers may be created for nested block expressions. Local values for identifiers, if declared by a first &lt;code&gt;block&lt;/code&gt; operator list argument, are created each time a nested &lt;code&gt;block&lt;/code&gt; is evaluated.  

However, identifiers with global values that have not been declared as local within any &lt;code&gt;block&lt;/code&gt; expressions, are global values for nested &lt;code&gt;block&lt;/code&gt; expressions as well as enclosing &lt;code&gt;block&lt;/code&gt; expressions. Likewise, local identifiers of any enclosing &lt;code&gt;block&lt;/code&gt; expression have values that are global within any enclosed blocks, if not declared as local within the enclosed block. If the value of an identifier is not local in a &lt;code&gt;block&lt;/code&gt; expression, its value is the value most recently assigned by an enclosing &lt;code&gt;block&lt;/code&gt; expression, if any value has been assigned. Otherwise, it is the value of the identifier in the global environment. &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i23)	z : 2^(1/3);
(z)	2^(1/3)

(%i24) /* Outer block starts */
	block 
	(
	 [x : 10, y : 20],
	 /* values of x and y declared local to outer block */
	  
	 /* Inner block starts */
	     block 
	     (
	      [y : 99, z : 100], 
	      /* values of y and z declared local to inner block */
	      print (&quot;Inside inner block:&quot;),
	      print (&quot;x =&quot;,  x, &quot;is the value of x from outer block&quot;),
	      print (&quot;y =&quot;,  y, &quot;is the local value of y of outer block&quot;),
	      print(&quot;z =&quot;,  z, &quot;is the local value of z of inner block&quot;)
	     ),
	 /* Inner block ends */
	 
	 /* Outer block resumes */
	 print (&quot;Back in outer block:&quot;),
	 print (&quot;x =&quot;,  x, &quot;is the value of x from outer block&quot;),
	 print (&quot;y =&quot;,  y,  &quot;is the restored value of y of the outer block&quot;),
	 print (&quot;z =&quot;,  z,  &quot;is the value of z global to both blocks&quot;)
	 /* Outer block ends */
	)$
	
Inside inner block:
x = 10 is the value of x from outer block
y = 99 is the local value of y of outer block
z = 100 is the local value of z of inner block
Back in outer block:
x = 10 is the value of x from outer block
y = 20 is the restored value of y of the outer block
z = 2^(1/3) is the value of z global to both blocks
&lt;/syntaxhighlight&gt;

==== Values, Properties, and the &lt;code&gt;local&lt;/code&gt; Operator ====
The expression &lt;code&gt;local (v&lt;sub&gt;1&lt;/sub&gt;, v&lt;sub&gt;2&lt;/sub&gt;, ... , v&lt;sub&gt;m&lt;/sub&gt;)&lt;/code&gt; within a &lt;code&gt;block&lt;/code&gt; expression saves the '''''properties''''' associated with the symbols &lt;code&gt;v&lt;sub&gt;1&lt;/sub&gt;, v&lt;sub&gt;2&lt;/sub&gt;, ... , v&lt;sub&gt;m&lt;/sub&gt;&lt;/code&gt;, removes any properties before evaluating other expressions, and restores any saved properties on exit from the block.

Because Maxima is an application based on the Common Lisp programming language, it utilizes Lisp '''''symbol''''' structure. Lisp symbols are objects that carry their own &quot;dictionary&quot; of attributes. A Lisp symbol's internal property list (''plist'') is a built-in data structure attached directly to a symbol. Maxima uses this underlying Lisp symbol structure to associate '''''properties''''' with Maxima identifiers.

Properties of identifiers can be ''declared explicitly'' by users. &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i23)	declare (x, real);
(%o23)	done
&lt;/syntaxhighlight&gt;
However, some identifier property declarations are ''implemented implicitly'' as properties of a symbol, including &lt;code&gt;:=&lt;/code&gt;, &lt;code&gt;array&lt;/code&gt;, &lt;code&gt;dependencies&lt;/code&gt;, &lt;code&gt;atvalue&lt;/code&gt;, &lt;code&gt;matchdeclare&lt;/code&gt;, &lt;code&gt;atomgrad&lt;/code&gt;, &lt;code&gt;constant&lt;/code&gt;, &lt;code&gt;nonscalar&lt;/code&gt;, &lt;code&gt;assume&lt;/code&gt;, and some others. Below is a description of how each of those specific declarations is implemented as a property under the hood:

====== Functions and Arrays ======
* '''&lt;code&gt;:=&lt;/code&gt; (Function Definition):''' When you define a function using &lt;code&gt;f(x) := x^2&lt;/code&gt;, the actual expression (&lt;code&gt;x^2&lt;/code&gt;) and its argument list (&lt;code&gt;x&lt;/code&gt;) are stored as a property of the symbol &lt;code&gt;f&lt;/code&gt;.
* '''&lt;code&gt;array&lt;/code&gt;:''' When you declare or use a subscripted array (like &lt;code&gt;a[i]&lt;/code&gt;), the array type, dimensions, and memory pointer are attached as a property to the symbol &lt;code&gt;a&lt;/code&gt;. This differentiates it from a standard scalar variable.

====== Calculus and Dependencies ======
* '''&lt;code&gt;dependencies&lt;/code&gt;:''' If you declare &lt;code&gt;depends(y, x)&lt;/code&gt;, Maxima attaches a dependency list property to &lt;code&gt;y&lt;/code&gt; noting that it functionally depends on &lt;code&gt;x&lt;/code&gt;. This tells the &lt;code&gt;diff&lt;/code&gt; (differentiation) engine not to treat &lt;code&gt;y&lt;/code&gt; as a constant relative to &lt;code&gt;x&lt;/code&gt;.
* '''&lt;code&gt;atvalue&lt;/code&gt;:''' When you define a specific value for an expression at a boundary point (e.g., &lt;code&gt;atvalue(y, x=0, 1)&lt;/code&gt;), this boundary constraint is stored as an evaluation property on the symbol &lt;code&gt;y&lt;/code&gt;.
* '''&lt;code&gt;atomgrad&lt;/code&gt;:''' This assigns a specific gradient or derivative to an atomic identifier (e.g., telling Maxima what (df/dx) is explicitly). Maxima saves this rule as a gradient property on that symbol.

====== Pattern Matching and Rules ======
* '''&lt;code&gt;matchdeclare&lt;/code&gt;:''' Used in Maxima's pattern-matching system (like &lt;code&gt;tellsimp&lt;/code&gt;). When you type &lt;code&gt;matchdeclare(x, freeof(a))&lt;/code&gt;, Maxima attaches a predicate property to &lt;code&gt;x&lt;/code&gt;. When a pattern rule runs, Maxima looks at property list of &lt;code&gt;x&lt;/code&gt; to see what conditions a matching expression must meet.

====== Mathematical and Evaluation Attributes ======
* '''&lt;code&gt;constant&lt;/code&gt;:''' Declaring &lt;code&gt;declare(c, constant)&lt;/code&gt; places a &quot;constant&quot; flag on property list of  &lt;code&gt;c&lt;/code&gt;. Core routines (like integration and differentiation) check this flag to know they can pull &lt;code&gt;c&lt;/code&gt; out of integrals or differentiate it to zero.
* '''&lt;code&gt;nonscalar&lt;/code&gt;:''' Tells Maxima to treat a symbol as a matrix or vector rather than a regular number. This property changes how operators like &lt;code&gt;.&lt;/code&gt; (non-commutative multiplication) treat the symbol.
* '''&lt;code&gt;assume&lt;/code&gt;:''' When an expression such as &lt;code&gt;assume(x &gt; 0)&lt;/code&gt; is used, Maxima's database system (&lt;code&gt;context&lt;/code&gt;) assigns facts and properties (like &lt;code&gt;pos&lt;/code&gt; or &lt;code&gt;nonnegative&lt;/code&gt;) to the symbol &lt;code&gt;x&lt;/code&gt;, allowing the simplifier to safely reduce expressions like &lt;code&gt;sqrt(x^2)&lt;/code&gt; to &lt;code&gt;x&lt;/code&gt;.

The effect of the &lt;code&gt;local&lt;/code&gt; operator is to make such declarations effective only within a &lt;code&gt;block&lt;/code&gt; expression. Otherwise, declarations within a &lt;code&gt;block&lt;/code&gt; expression are considered to be global declarations.

So what does all of this mean to the typical Maxima user? It means that the list of identifiers that is the first argument  of a &lt;code&gt;block&lt;/code&gt; expression only declares the '''''values''''' of those identifiers as local to the &lt;code&gt;block&lt;/code&gt; expression in which the list is an argument. Any properties of identifiers are not declared local by this means. 

In order to declare '''''properties''''' of identifiers to be local to a &lt;code&gt;block&lt;/code&gt; expression, the &lt;code&gt;local&lt;/code&gt; operator must be used as an expression within the &lt;code&gt;block&lt;/code&gt; expression. At the point where the local operator is evaluated as an argument of a &lt;code&gt;block&lt;/code&gt; expression, the properties of the identifiers that are arguments to the &lt;code&gt;local&lt;/code&gt; operator become local to the block. It is not an unfair criticism that perhaps the &lt;code&gt;local&lt;/code&gt; operator should have been named something like &lt;code&gt;local_properties&lt;/code&gt;. &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i25)	f (s) := cos (s);
(%o25)	f(s):=cos(s)

(%i26)	f (%pi/6);
(%o26)	sqrt(3)/2

(%i27)	block (local (f), f (s) := sin (s), f (%pi/6));
(%o27)	1/2

(%i28)	f (s);
(%o28)	cos(s)
&lt;/syntaxhighlight&gt;In the above example, the '''''properties''''' of identifier &lt;code&gt;f&lt;/code&gt; were declared to be local in the &lt;code&gt;block&lt;/code&gt; expression using the &lt;code&gt;local&lt;/code&gt; operator. However, global properties of the identifier &lt;code&gt;f&lt;/code&gt; were not affected by the local function definition of &lt;code&gt;f&lt;/code&gt; in the &lt;code&gt;block&lt;/code&gt; expression. The global definition expression of &lt;code&gt;f&lt;/code&gt; which is &lt;code&gt;cos (s)&lt;/code&gt; and the argument &lt;code&gt;s&lt;/code&gt; were not affected by the local definition of &lt;code&gt;f&lt;/code&gt; because the properties of &lt;code&gt;f&lt;/code&gt; were declared local to the &lt;code&gt;block&lt;/code&gt; expression.  

&lt;code&gt;block&lt;/code&gt; expressions can be used for different purposes in the Maxima programming context. &lt;code&gt;block&lt;/code&gt; expressions can be used in a stand-alone fashion or as part of an expression. However, &lt;code&gt;block&lt;/code&gt; expressions are commonly used in expressions that define '''''functions''''', which is the topic that follows. 

=== Functions ===
{| class=&quot;wikitable&quot;
|+Function Definition Operators
and Identifiers
|&lt;code&gt;:=&lt;/code&gt;
|&lt;code&gt;fundef&lt;/code&gt;
|&lt;code&gt;buildq&lt;/code&gt;
|-
|&lt;code&gt;::=&lt;/code&gt;
|&lt;code&gt;lambda&lt;/code&gt;
|&lt;code&gt;macros&lt;/code&gt;
|-
|&lt;code&gt;define&lt;/code&gt;
|&lt;code&gt;local&lt;/code&gt;
|&lt;code&gt;slice&lt;/code&gt;
|-
|&lt;code&gt;dispfun&lt;/code&gt;
|&lt;code&gt;remfunction&lt;/code&gt;
|
|-
|&lt;code&gt;functions&lt;/code&gt;
|&lt;code&gt;setup_autoload&lt;/code&gt;
|
|}
As a technical term '''''function''''' is aptly characterized as being overloaded. In the context of Maxima as a CAS, it has both a programming meaning and a mathematical meaning in terms of usage. In this book, the convention is to refer to what may otherwise be referred to as built-in Maxima functions as ''operators'' including those of built-in packages. By this convention, the term '''''function''''' in this book refers exclusively to expressions composed by the user by way of the &lt;code&gt;:=&lt;/code&gt; or &lt;code&gt;define&lt;/code&gt; operators.

As has been mentioned elsewhere in this book, what are conventionally termed ''operators'' that are built-in to Maxima, are at the level of underlying expression construction, Lisp procedures of one type or another. So it makes sense to simply refer to built-in Maxima functions and operators simply as operators one and all. This convention obviates the need for the repetitious use of qualifiers such as ''built-in Maxima'' and ''user-defined'' functions.

There are two operators used to define functions as follows:

# The &lt;code&gt;''''':='''''&lt;/code&gt; operator
# The &lt;code&gt;'''define'''&lt;/code&gt; operator

 &lt;var&gt;&lt;code&gt;f (x&lt;sub&gt;1&lt;/sub&gt;, x&lt;sub&gt;2,&lt;/sub&gt; ..., x&lt;sub&gt;n&lt;/sub&gt;) ''':=''' expr&lt;/code&gt;
 &lt;code&gt;f&lt;/code&gt; &lt;code&gt;[x&lt;sub&gt;1&lt;/sub&gt;, x&lt;sub&gt;2,&lt;/sub&gt; ..., x&lt;sub&gt;n&lt;/sub&gt;] ''':=''' expr&lt;/code&gt;
 &lt;code&gt;f&lt;/code&gt; &lt;code&gt;[x&lt;sub&gt;1&lt;/sub&gt;, x&lt;sub&gt;2,&lt;/sub&gt; ..., x&lt;sub&gt;n&lt;/sub&gt;](y&lt;sub&gt;1&lt;/sub&gt;, y&lt;sub&gt;2&lt;/sub&gt;, ..., y&lt;sub&gt;m&lt;/sub&gt;) ''':=''' expr&lt;/code&gt;&lt;/var&gt; 

 &lt;code&gt;define (f&lt;/code&gt; &lt;code&gt;(x&lt;sub&gt;1&lt;/sub&gt;, x&lt;sub&gt;2,&lt;/sub&gt; …, x&lt;sub&gt;n&lt;/sub&gt;), expr)&lt;/code&gt;
 &lt;code&gt;define (f&lt;/code&gt; &lt;code&gt;[x&lt;sub&gt;1&lt;/sub&gt;, x&lt;sub&gt;2,&lt;/sub&gt; …, x&lt;sub&gt;n&lt;/sub&gt;], expr)&lt;/code&gt;
 &lt;code&gt;define (f&lt;/code&gt; &lt;code&gt;[x&lt;sub&gt;1&lt;/sub&gt;, x&lt;sub&gt;2,&lt;/sub&gt; …, x&lt;sub&gt;n&lt;/sub&gt;](y&lt;sub&gt;1&lt;/sub&gt;, y&lt;sub&gt;2,&lt;/sub&gt; …, y&lt;sub&gt;m&lt;/sub&gt;), expr)&lt;/code&gt;
 &lt;code&gt;define (funmake (f, [&lt;/code&gt;&lt;code&gt;x&lt;sub&gt;1&lt;/sub&gt;, x&lt;sub&gt;2,&lt;/sub&gt; …, x&lt;sub&gt;n&lt;/sub&gt;]), expr)&lt;/code&gt;
 &lt;code&gt;define (arraymake (f, [&lt;/code&gt;&lt;code&gt;x&lt;sub&gt;1&lt;/sub&gt;, x&lt;sub&gt;2,&lt;/sub&gt; …, x&lt;sub&gt;n&lt;/sub&gt;]), expr)&lt;/code&gt;
 &lt;code&gt;define (ev (&lt;/code&gt;&lt;code&gt;expr&lt;sub&gt;1&lt;/sub&gt;, expr&lt;sub&gt;2&lt;/sub&gt;))&lt;/code&gt;
where &lt;code&gt;expr&lt;/code&gt; is some Maxima expression that is commonly referred to as the ''function body''. As can be concluded from the above, each of these operators has different forms of syntax that can be used. In any case, the most significant differences between these two operators are in terms of the evaluation of the function body and the composition and identification of functions dynamically. 

* '''Evaluation:'''
** The &lt;code&gt;:=&lt;/code&gt; operator '''suppresses (quotes)''' the evaluation of the function body when this operator is first evaluated. It does not evaluate or simplify the function body until the function identifier itself is evaluated with arguments.
** The &lt;code&gt;define()&lt;/code&gt; operator '''evaluates''' the function body when this operator is first evaluated. If the function body involves intermediate computations, substituted values, or extracted parts of expressions (like &lt;code&gt;rhs()&lt;/code&gt; or derivative results), the &lt;code&gt;define()&lt;/code&gt; operator includes the evaluated results of those directly into the function body.

* '''Dynamic Function Composition and Identifiers:'''
** Function identifiers cannot easily be composed dynamically on the left-hand side of the &lt;code&gt;:=&lt;/code&gt; operator when used inside programmatic loop expressions or in scripts.
** The &lt;code&gt;define()&lt;/code&gt; operator accepts expressions like &lt;code&gt;funmake&lt;/code&gt; or evaluated symbols as its first argument, allowing the composition and identification of functions dynamically during evaluation.


So, there are in general two different operators that can be used to define and evaluate functions. The choice by the Maxima user between these two operators depends on the purpose and context.

==== Function Definition Using the &lt;code&gt;:=&lt;/code&gt; Operator ====
For the purpose of understanding the two ways of defining functions, consider the following example which is elementary, but in terms of clarification is not merely simple:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* &quot;kill&quot; all previously used identifier and values  */
(%i29)	kill (all);
(%o0)	done

/* assign identifier x the global value of 5  */
(%i1)	x : 5;
(x)	5

/* define f as a function with local argument x  */
(%i2)	f (x) := x;
(%o2)	f(x):=x

/* evaluate f at local value of x is 3  */
(%i3)	f (3);
(%o3)	3

/* the global value of x is not affected  */
(%i4)	x;
(%o4)	5

/* show the definition expression of the function named f  */
(%i5)	fundef (f);
(%o5)	f(x):=x&lt;/syntaxhighlight&gt;'''Function Definition Using the''' '''&lt;code&gt;define&lt;/code&gt; Operator'''&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* define a function with identifier g with a
   local argument y and with a function body
   of identifier x */
   
(%i3)	define (g('x), x);
(%o3)	g(x):=5
/* identifier x of the function body is evaluated */
/* identifier x as an argument of g is local in scope */

(%i4)	fundef (g);
(%o4)	g(x):=5

/* the same identifier x used in three different roles */
    /* used as the global name of a function x */
    /* used as a local argument of a function */
    /* used as an unevaluated expression for a function body */
(%i7)	x(x) := x;
(%o7)	x(x):=x


(%i9)	x(3);
(%o9)	3

(%i10)	x;
(%o10)	5

(%i8)	fundef (x);
(%o8)	x(x):=x

(%i11)	define (x('x), x);
(%o11)	x(x):=5

(%i12)	fundef (x);
(%o12)	x(x):=5
&lt;/syntaxhighlight&gt;The purpose of this example is not to encourage this sort of syntax as a typical choice for identifiers and function definitions. The purpose is to clarify how Maxima implicitly determines the scope and meaning of identifiers used for function definition in the absence of any explicit user stipulations.
It should be noted that the &lt;code&gt;define&lt;/code&gt; operator not only evaluates the expression that is the function body, it also evaluates the arguments of the function identifier that is the first argument of the &lt;code&gt;define&lt;/code&gt; operator. Since there is a global value of the identifier &lt;code&gt;x&lt;/code&gt; of &lt;code&gt;5&lt;/code&gt;, it was necessary to suppress evaluation (quote) the argument in the expression &lt;code&gt;(%i12) define ('x), x);&lt;/code&gt; as otherwise an error would be the result:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* define a new function named x */
(%i14)	define (x('x), 'x^2);
(%o14)	x(x):=x^2

/* check the definition of the new function named x */
(%i15)	fundef (x);
(%o15)	x(x):=x^2

/* the identifier x has a global value */
(%i16)	values;
(%o16)	[x]

/* the global value of identifier x is 5 */
(%i17)	x;
(%o17)	5

/* the suppressed global value 'x of identifier x is x */
(%i18)	'x;
(%o18)	x

/* not quoting the global value of identifier x is an error  */
(%i19)	define (x(x), 'x^2);
define: in definition of x, parameter must be a symbol and must not be a system constant; found: 5
 -- an error. To debug this try: debugmode(true);
&lt;/syntaxhighlight&gt;

==== Understanding the Differences Between the &lt;code&gt;:=&lt;/code&gt; and &lt;code&gt;define&lt;/code&gt; Operators ====
In cases such as these, the suppression of evaluation by quoting is a user stipulation as to evaluation. Users must be aware of these differences between the two operators (&lt;code&gt;:=&lt;/code&gt; and &lt;code&gt;define&lt;/code&gt;) for the purpose of function definition in order to achieve what is intended and to avoid errors,&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i20)	f (x) := 3*x^3  +  4*x  -  5;
(%o20)	f(x):=3*x^3+4*x-5

(%i21)	fundef (f);
(%o21)	f(x):=3*x^3+4*x-5

(%i22)	f(2);
(%o22)	27

(%i23)	define (f (x) , 3*x^3  +  4*x  -  5);
define: in definition of f, parameter must be a symbol and must not be a system constant; found: 5
-- an error. To debug this try: debugmode(true);

(%i24)	define (f ('x) , 3*x^3  +  4*x  -  5);
(%o24)	f(x):=390

(%i25)	define (f ('x) , '(3*x^3  +  4*x  -  5));
(%o25)	f(x):=3*x^3+4*x-5

(%i26)	fundef (f);
(%o26)	f(x):=3*x^3+4*x-5

(%i27)	f(2);
(%o27)	27
&lt;/syntaxhighlight&gt;What is true in the case of these elementary examples is true in general for function definitions involving multiple arguments:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* x has a global value of 5 while y is local to g */
(%i28)	g (x, y)  :=  x^3 - y^2;
(%o28)	g(x,y):=x^3-y^2

(%i29)	g (6,2);
(%o29)	212

(%i30)	define (g('x, y), 'x^3 - y^2);
(%o30)	g(x,y):=x^3-y^2

(%i31)	values;
(%o31)	[x]

(%i32)	g (6,2);
(%o32)	212
&lt;/syntaxhighlight&gt;The &lt;code&gt;define&lt;/code&gt; operator is a good choice in cases where an existing expression is used as the function body:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i33)	/*  assign an expression to identifier expr */
	expr : diff('x^3, 'x);  /* Returns 3*x^2 */
(expr)	3*x^2

(%i34)	/* evaluate expr and define h (x) := 3*x^2 */
	define (h ('x), expr); 
(%o34)	h(x):=3*x^2
&lt;/syntaxhighlight&gt;In cases in which functions require local variables or more than one expression for the function body, use the block operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i35)	remvalue (x);
(%o35)	[x]

(%i36)	values;
(%o36)	[expr]
 --&gt;	power_sum (x, y) := block (
/* values of these identifiers are explicitly local to the function */
	    [sqx, sqy],  
/* unevaluated identifiers x and y are local arguments of the function
   and values of these identifiers are implicitly local to the function */
	    sqx : x^2,
	    sqy : y^2,
	    sqx + sqy /* the value of the function */
	)$

(%i37)	fundef (power_sum);
(%o37)	power_sum(x,y):=block([sqx,sqy],sqx:x^2,sqy:y^2,sqx+sqy)

(%i38)	power_sum (3,4);
(%o38)	25
&lt;/syntaxhighlight&gt;The &lt;code&gt;define&lt;/code&gt; operator could also be used to define this function, but with different definition values as a consequence:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i39)	define (power_sum (x,y), 
                block (
                [sqx,sqy], 
                sqx : x^2,
                sqy : y^2, 
                sqx + sqy
                )
               )$

(%i40)	fundef (power_sum);
(%o40)	power_sum(x,y):=y^2+x^2

(%i41)	power_sum (3,4);
(%o41)	25&lt;/syntaxhighlight&gt;The function definition of &lt;code&gt;power_sum&lt;/code&gt; is different using the &lt;code&gt;define&lt;/code&gt; operator instead of the &lt;code&gt;:=&lt;/code&gt; operator. The value of the function when referenced with arguments (&lt;code&gt;power_sum (3,4)&lt;/code&gt;) is the same in both cases – &lt;code&gt;25&lt;/code&gt;. However, in general for defining functions, this may not be the case. The choice between these two operators depends on the intentions of the user.

==== Practical Considerations Related to Function Composition ====

In general, programming is a technical skill as well as a subjective art. So, absolute rules are not offered here.  For practical purposes some &quot;guidelines&quot; are offered here that may be useful for Maxima function composition as well as Maxima programming in general: 

*
*
*
*
*


Consider the following linear algebraic equation:

&lt;math display=&quot;block&quot;&gt;3y - 7x = 10&lt;/math&gt;
As an example suppose the value that is sought is the slope &lt;code&gt;m&lt;/code&gt; of this equation, and in general, the slope of any linear equation regardless of the form.   &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* assign the linear equation to an identifier */
(%i42)	lineqn : 3*y - 7*x = 10;
(lineqn)	3*y-7*x=10

/* solve the linear equation for y */
(%i43)	solve([lineqn], [y])
(%o43)	[y=(7*x+10)/3]

/* use the index [1] of the list to get the solved equation */
(%i44)	solve([lineqn], [y])[1]
(%o44)	y=(7*x+10)/3

/* use the rhs operator to get right-hand side */
(%i45)	rhs(solve([lineqn], [y])[1]);
(%o45)	(7*x+10)/3

/* use the expand operator change the RHS */
(%i46)	expand(rhs(solve([lineqn], [y])[1]));
(%o46)	(7*x)/3+10/3

/* use the coeff operator to get the coefficient of x */
(%i47)	coeff(expand(rhs(solve([lineqn], [y])[1])),x,1);
(%o47)	7/3

/* define the function with an argument eqn for lineqn */
(%i48)	m (eqn) := coeff (expand (rhs (solve ([eqn], [y])[1])),x,1)$

/* check the function definition */
(%i49)	fundef (m);
(%o49)	m(eqn):=coeff(expand(rhs((solve([eqn],[y]))[1])),x,1)

/* reference the function using lineqn as an argument */
(%i50)	m (lineqn);
(%o50)	7/3

/* assign a different linear equation to lineqn */
(%i51)	lineqn : x = 6*y + 13;
(lineqn)	x=6*y+13

/* reference the function using lineqn as an argument */
%i52)	m (lineqn);
(%o52)	1/6&lt;/syntaxhighlight&gt;The function body of this example will result in an error if it is used with the &lt;code&gt;define&lt;/code&gt; operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i53)	define (
                m (eqn),
                coeff (expand (rhs (solve ([eqn], [y])[1])),x,1) 
               )$
inpart: invalid index 1 of list or matrix.
-- an error. To debug this try: debugmode(true);
&lt;/syntaxhighlight&gt;This error is a consequence of the evaluation that occurs when using the &lt;code&gt;define&lt;/code&gt; operator. In this case, this evaluation results in a reference to the indexed value of a list object that does not exist when evaluation occurs during definition – &lt;code&gt;solve ([eqn], [y])[1]&lt;/code&gt;.

==== Memoizing Functions ====
The functions discussed so far are often referred to as '''''ordinary functions'''''. The arguments of ordinary functions are enclosed using parentheses – &lt;var&gt;&lt;code&gt;(x&lt;sub&gt;1&lt;/sub&gt;, x&lt;sub&gt;2,&lt;/sub&gt; ..., x&lt;sub&gt;n&lt;/sub&gt;)&lt;/code&gt;.&lt;/var&gt; Function definition forms which include arguments enclosed by brackets (as in &lt;var&gt;&lt;code&gt;[x&lt;sub&gt;1&lt;/sub&gt;, x&lt;sub&gt;2,&lt;/sub&gt; ..., x&lt;sub&gt;n&lt;/sub&gt;]&lt;/code&gt;&lt;/var&gt;) are called '''''memoizing functions'''''.

Memoizing functions can be categorized both as functions and as data structures – specifically a ''hashed array'' of values. Memoizing functions are also referred to as '''''array functions'''''. In any case, memoizing functions can be defined using either the &lt;code&gt;:=&lt;/code&gt; operator or the &lt;code&gt;define&lt;/code&gt; operator. 

If the form of the function definition expression is &lt;code&gt;f [x&lt;sub&gt;1&lt;/sub&gt;, x&lt;sub&gt;2&lt;/sub&gt;,..., x&lt;sub&gt;n&lt;/sub&gt;] := expr&lt;/code&gt; The  function body &lt;code&gt;expr&lt;/code&gt; is evaluated once for each individual value of the arguments, and that value is the value of the function, without again evaluating the function body, whenever referenced using arguments that have those same values. 

Once evaluated during a function reference with arguments, that value of a memoizing function is thereby &quot;frozen&quot; in other words. This frozen value also becomes an instance of a hashed array data structure that can be referenced by way of the value of the index used as an argument when first evaluated. 

In keeping with previous practice, the examples provided here are intentionally elementary for the purpose of demonstrating and clarifying the technical aspects involved. There is thereby no intention to convey that the composition of function definition expressions with multiple arguments and complex expressions for the function body is ruled out or of lesser practical value.   &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* define a memoizing function f */
/* x and n may serve as both arguments and array indices */
(%i54)	f  [x, n] := x^n;
(%o54)	f[x,n]:=x^n

/* check the array information for f */
(%i55)	arrayinfo (f);
(%o55)	[hashed,2]

/* f does not appear in the list of functions */
(%i56)	functions;
(%o56)	[m(lineqn)]

/* reference f with argument values  */
(%i57)	f [2,3] ;
(%o57)	8

/* check the array information for f again */
(%i58)	arrayinfo (f);
(%o58)	[hashed,2,[2,3]]

/* list the array values of f */
(%i59)	listarray (f);
(%o59)	[8]

/* f does appear in the list of arrays */
(%i60)	arrays;
(%o60)	[f]

/* reference f with new argument values  */
(%i61)	f [5,2];
(%o61)	25

/* check the array information for f again */
(%i62)	arrayinfo (f);
(%o62)	[hashed,2,[2,3],[5,2]]

/* list the array values of f */
(%i63)	listarray (f);
(%o63)	[8,25]&lt;/syntaxhighlight&gt;An expression of the form &lt;code&gt;define (f [x1, x2&lt;/code&gt;&lt;code&gt;,…, xn], expr)&lt;/code&gt; may also be used to define the same memoizing function &lt;code&gt;f&lt;/code&gt; in this case as the evaluation imposed by the &lt;code&gt;define&lt;/code&gt; operator during evaluation of these function arguments and this function body that occurs makes no difference:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* remove the function definition and values of f */
(%i64)	remarray (f);
(%o64)	[f]

/* the list of arrays is now empty */
(%i65)	arrays;
(%o65)	[]

/* define the same memoizing function f using the define operator */
/* evaluation makes no difference to the definition of f in this case */
(%i66)	define (f [x,n], x^n);
(%o66)	f[x,n]:=x^n

/* reference f with different argument values  */
(%i67)	f [3, 2];
(%o67)	9

/* reference f again with different argument values  */
(%i68)	f [2, 5];
(%o68)	32

/* f again appears in the list of arrays */
(%i69)	arrays;
(%o69)	[f]

/* check the array information for f */
(%i70)	arrayinfo (f);
(%o70)	[hashed,2,[2,5],[3,2]]

/* list the array values of f */
(%i71)	listarray (f);
(%o71)	[32,9]
&lt;/syntaxhighlight&gt;

===== Special Forms of Memoizing Functions =====
An expression of the form &lt;code&gt;f [x&lt;sub&gt;1&lt;/sub&gt;, x&lt;sub&gt;2&lt;/sub&gt;,..., x&lt;sub&gt;n&lt;/sub&gt;](y&lt;sub&gt;1&lt;/sub&gt;, y&lt;sub&gt;2&lt;/sub&gt;,..., y&lt;sub&gt;m&lt;/sub&gt;):= expr&lt;/code&gt;, or alternatively of the form &lt;code&gt;define (f [x1, x2&lt;/code&gt;&lt;code&gt;,…, xn](y&lt;sub&gt;1&lt;/sub&gt;, y&lt;sub&gt;2&lt;/sub&gt;,..., y&lt;sub&gt;m&lt;/sub&gt;), expr)&lt;/code&gt;, may also be used to define a memoizing function named &lt;code&gt;f&lt;/code&gt;.  When either of these forms are used to compose a function definition expression, there is a sense in which the resulting function is a hybrid – part memoizing function, and part &quot;ordinary&quot; function. These forms create a hashed array of functions where the array subscripts &lt;code&gt;[x&lt;sub&gt;1&lt;/sub&gt;, x&lt;sub&gt;2&lt;/sub&gt;,..., x&lt;sub&gt;n&lt;/sub&gt;]&lt;/code&gt; evaluate immediately to &quot;specialize&quot; the function body, while the ordinary function arguments &lt;code&gt;(y&lt;sub&gt;1&lt;/sub&gt;, y&lt;sub&gt;2&lt;/sub&gt;,..., y&lt;sub&gt;m&lt;/sub&gt;)&lt;/code&gt; are used when evaluating these individual functions.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* Define a family of &quot;shifted&quot; power functions */
(%i72)	define( p[n](x), x^n + n );
(%o72)	p[n](x):=x^n+n

(%i73)	p[2];
(%o73)	lambda([x],x^2+2)

(%i74)	p[2](5);
(%o74)	27

(%i75)	p[4];
(%o75)	lambda([x],x^4+4)

(%i76)	p[4](5);
(%o76)	629

(%i77)	arrayinfo (p);
(%o77)	[hashed,1,[2],[4]]

(%i78)	listarray (p)
(%o78)	[lambda([x],x^2+2),lambda([x],x^4+4)]

(%i79)	p[5];
(%o79)	lambda([x],x^5+5)

(%i80)	p[5](2);
(%o80)	37

(%i81)	listarray (p);
(%o81)	[lambda([x],x^2+2),lambda([x],x^4+4),lambda([x],x^5+5)]

(%i82)	arrayinfo (p);
(%o82)	[hashed,1,[2],[4],[5]]&lt;/syntaxhighlight&gt;

==== Lambda Expressions ====

==== Special Forms of the &lt;code&gt;define&lt;/code&gt; Operator ====

==== Some Techniques for Function Composition ====

=== Conditional Expressions – Special Operator &lt;code&gt;if&lt;/code&gt; ===

=== Expressions for Iteration – Special Operator &lt;code&gt;do&lt;/code&gt; ===
The special operator &lt;code&gt;do&lt;/code&gt;  is used to compose expressions for iteration. It is typically used with the following other special operators:

* &lt;code&gt;while&lt;/code&gt;
* &lt;code&gt;unless&lt;/code&gt;
* &lt;code&gt;for&lt;/code&gt;
* &lt;code&gt;from&lt;/code&gt;
* &lt;code&gt;thru&lt;/code&gt;
* &lt;code&gt;step&lt;/code&gt;
* &lt;code&gt;next&lt;/code&gt;
* &lt;code&gt;in&lt;/code&gt;

The general forms of &lt;code&gt;do&lt;/code&gt; expressions Maxima supports are:

&lt;code&gt;for&lt;/code&gt; variable: initial_value &lt;code&gt;step&lt;/code&gt; increment &lt;code&gt;thru&lt;/code&gt; limit &lt;code&gt;do&lt;/code&gt; body

&lt;code&gt;for&lt;/code&gt; variable: initial_value &lt;code&gt;step&lt;/code&gt; increment &lt;code&gt;while&lt;/code&gt; condition &lt;code&gt;do&lt;/code&gt; body

&lt;code&gt;for&lt;/code&gt; variable: initial_value &lt;code&gt;step&lt;/code&gt; increment &lt;code&gt;unless&lt;/code&gt; condition &lt;code&gt;do&lt;/code&gt; body

&lt;code&gt;for&lt;/code&gt; variable &lt;code&gt;in&lt;/code&gt; list &lt;code&gt;do&lt;/code&gt; body

&lt;code&gt;for&lt;/code&gt; variable &lt;code&gt;in&lt;/code&gt; expr &lt;code&gt;do&lt;/code&gt; body

&lt;code&gt;for&lt;/code&gt; variable &lt;code&gt;in&lt;/code&gt; hash_table &lt;code&gt;do&lt;/code&gt; body

=== Lisp and Maxima ===

{{BookCat}}</text>
      <sha1>fdxd0wni6u69dvyosk8zmyqoet5webh</sha1>
    </revision>
    <revision>
      <id>4676573</id>
      <parentid>4676537</parentid>
      <timestamp>2026-10-17T19:40:40Z</timestamp>
      <contributor>
        <username>Idavidmiller</username>
        <id>3577687</id>
      </contributor>
      <comment>/* Special Forms of Memoizing Functions */ Work in progress. Saving Changes.</comment>
      <origin>4676573</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="44432" sha1="mcol4a2a4yt33h4sjieg823r7kwqa16" xml:space="preserve">=Maxima Programming=
Although Maxima is not a general-purpose programming language, Maxima as a CAS includes among the built-in ingredients a relatively complete set of programming expressions that are useful for the intended context. Many of the code examples of this section are intended to be illustrative of technical details relevant to Maxima programming as their purpose, and consequently are intentionally elementary in character.

Learning any sort of programming language, including Maxima programming expressions, is a subjective process. In any case, it is essential to have enough technical know-how specific to the programming language in order to begin the learning process, even in cases where much positive transfer from other programming experience is involved.

Much can be accomplished mathematically using Maxima without having to resort to in-depth knowledge and proficiency in the technical details of Maxima programming expressions. However, Maxima programming expressions are frequently essential for the purpose of defining functions, both in the programming sense of the term, but also more relevantly, for the mathematical sense. For that reason alone, familiarity and sufficient proficiency with Maxima programming expressions should be given some attention.

One way to begin the learning process is to become familiar with enough of the programming essentials to accomplish independent efforts toward accomplishing some specific programming goal of interest.  The other way is to study the many available programming expressions of others. This section is intended to provide the essentials toward learning by whatever means are chosen.

The following table shows some built-in ingredients related to Maxima programming expressions:
{| class=&quot;wikitable&quot;
|+Maxima Programming Category
|if
|unless
|errcatch
|prederror
|-
|block
|for
|error
|return
|-
|catch
|from
|warning
|throw 
|-
|local
|thru
|errormsg
|sstatus
|-
|garbage_collect
|step
|errormsg
|status
|-
|do
|next
|go
|
|-
|while
|in
|
|
|}

Some of these programming expression ingredients can also be considered as belonging to one or more other categories than the Programming category.

=== Block Expressions ===
Arguably, the first expressions to consider in the context of Maxima programming are '''''block''''' expressions. All &lt;code&gt;block&lt;/code&gt; expressions as programming ingredients come in two flavors:

* &lt;code&gt;( expr&lt;sub&gt;1&lt;/sub&gt;, expr&lt;sub&gt;2&lt;/sub&gt;,…, expr&lt;sub&gt;n&lt;/sub&gt; )&lt;/code&gt;
* &lt;code&gt;block ([v&lt;sub&gt;1&lt;/sub&gt;,v&lt;sub&gt;2,&lt;/sub&gt;…,v&lt;sub&gt;m&lt;/sub&gt;], expr&lt;sub&gt;1&lt;/sub&gt;, expr&lt;sub&gt;2&lt;/sub&gt;,…, expr&lt;sub&gt;n&lt;/sub&gt;)&lt;/code&gt;

The first form of a &lt;code&gt;block&lt;/code&gt; expression is equivalent to the second form, but without the first list argument: &lt;code&gt;[v&lt;sub&gt;1&lt;/sub&gt;,v&lt;sub&gt;2,&lt;/sub&gt;…,v&lt;sub&gt;m&lt;/sub&gt;]&lt;/code&gt;, as in &lt;code&gt;block (expr&lt;sub&gt;1&lt;/sub&gt;, expr&lt;sub&gt;2&lt;/sub&gt;,…, expr&lt;sub&gt;n&lt;/sub&gt;&lt;/code&gt;, unless &lt;code&gt;return&lt;/code&gt; or &lt;code&gt;go&lt;/code&gt; operators are used in the block expression. In that, case the form &lt;code&gt;block (expr&lt;sub&gt;1&lt;/sub&gt;, expr&lt;sub&gt;2&lt;/sub&gt;,…, expr&lt;sub&gt;n&lt;/sub&gt;)&lt;/code&gt; must be used. It should be noted that for Maxima to interpret of the syntax of the first of these forms as a block operator, there must be at least two expressions in the comma-separated sequence of expressions as arguments. Otherwise, Maxima will interpret the parentheses of this syntax as simply grouping related to the precedence order of operations.

The purpose of the list argument,  &lt;code&gt;[v&lt;sub&gt;1&lt;/sub&gt;,v&lt;sub&gt;2,&lt;/sub&gt;…,v&lt;sub&gt;m&lt;/sub&gt;]&lt;/code&gt; is to declare the values of identifiers of the list to be local to the &lt;code&gt;block&lt;/code&gt;. If there is no need for local identifiers, the list argument can be omitted (unless &lt;code&gt;return&lt;/code&gt; or &lt;code&gt;go&lt;/code&gt; operators are used in the &lt;code&gt;block&lt;/code&gt; expression), and either form is sufficient.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* This block expression */
(%i1)	(x : 2, x^2);
(%o1)	4

/* Is equivalent to this block expression */
(%i2)	block (x : 2, x^2);
(%o2)	4&lt;/syntaxhighlight&gt;So, in the case where values of identifiers local to the &lt;code&gt;block&lt;/code&gt; of expressions are not required, then the choice of either form of the &lt;code&gt;block&lt;/code&gt; expression is a matter of user preference. In both cases, the values of identifiers referenced in the &lt;code&gt;block&lt;/code&gt; are global, and not local to the &lt;code&gt;block&lt;/code&gt; expression. However, for the sake of clarity and consistency use of the latter form may be a better choice. &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* The value 3 assigned to x is global */
(%i3)	x : 3;
(x)	    3

/* The value 2 assigned to x in the block is global */
(%i4)	(x : 2, x^2);
(%o4)	4

/* The global value assigned to x in the block is 2 not 3 */
(%i5)	x;
(%o5)	2
&lt;/syntaxhighlight&gt;Values of identifiers local to the &lt;code&gt;block&lt;/code&gt; may not be global:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* the value of identifier y is local only */
(%i6)	block ([y], y : 4, y);
(%o6)	4

/* the global value of identifier y is not 4, but is itself */
(%i7)	y;
(%o7)	y

/* the values of identifiers x and y are both local */
(%i8)	block ([x,y], x : 3, y : 4, x);
(%o8)	3

/* the global value of identifier x is not 3, but is 2 */
(%i9)	x;
(%o9)	2

/* the global value of identifier y is not 4, but is itself */
(%i10)	y;
(%o10)	y&lt;/syntaxhighlight&gt;

Regardless of the form of the &lt;code&gt;block&lt;/code&gt; expressions these have in common the comma-separated expression arguments &lt;code&gt;expr&lt;sub&gt;1&lt;/sub&gt;, expr&lt;sub&gt;2&lt;/sub&gt;,…, expr&lt;sub&gt;n&lt;/sub&gt;&lt;/code&gt;  which are evaluated each in turn from first to last (unless the evaluation sequence is modified by by the &lt;code&gt;go&lt;/code&gt;, &lt;code&gt;throw&lt;/code&gt;, or &lt;code&gt;return&lt;/code&gt; operators), and the value of the block expression is the value of &lt;code&gt;expr&lt;sub&gt;n&lt;/sub&gt;&lt;/code&gt;. 

The main purpose of the &lt;code&gt;block&lt;/code&gt; expression, regardless of the form, is to group expressions that are related in some manner, and the value of the last expression may be the only value of interest. However, there are very few limitations imposed on the nature of the &lt;code&gt;block&lt;/code&gt; expression arguments, so it might be the case that the purpose of evaluating the &lt;code&gt;block&lt;/code&gt; expression has been achieved before the last expression argument is evaluated, in which case the value of the &lt;code&gt;block&lt;/code&gt; expression may not necessarily be the value of the last argument expression.

One way to accomplish that is to use an empty string as the last argument expression with the option flag &lt;code&gt;stringdisp&lt;/code&gt; set to &lt;code&gt;false&lt;/code&gt; which is the default value.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i11)	stringdisp;
(%o11)	false

(%i12)	block ([x,y], x : 3, y : 4, x, &quot;&quot;);
(%o12)	

(%i13)	block ([x,y], x : 3, y : 4, x)$
&lt;/syntaxhighlight&gt;
The display of the value of the &lt;code&gt;block&lt;/code&gt; expression may be suppressed using a &lt;code&gt;$&lt;/code&gt; to end the input expression instead of a semi-colon. Either technique produces a &lt;code&gt;block&lt;/code&gt; expression value, but the value is not displayed. If a &lt;code&gt;return&lt;/code&gt; operator is evaluated as a argument expression, this will cause evaluation of expression arguments to end explicitly, and the value of the &lt;code&gt;return&lt;/code&gt; operator becomes the value of the &lt;code&gt;block&lt;/code&gt; expression.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i14)	is (equal (x, 2));
(%o14)	true

%i15)	block (if is (equal (x, 2)) then return (x), &quot; x not 2&quot;);
(%o15)	2

(%i16)	x : 3;
(x)	3

(%i17)	block (if is (equal (x, 2)) then return (x), &quot;x not 2&quot;);
(%o17)	x not 2
&lt;/syntaxhighlight&gt;When a &lt;code&gt;return&lt;/code&gt; operator is evaluated within a &lt;code&gt;block&lt;/code&gt; expression the result is to stop evaluation of expressions within the enclosing &lt;code&gt;block&lt;/code&gt; expression and to return the value of its argument as the value of the enclosing &lt;code&gt;block&lt;/code&gt; expression. It therefore can be compared with the &lt;code&gt;return&lt;/code&gt; statement found in other programming languages, but with one difference: In Maxima, the &lt;code&gt;return&lt;/code&gt; operator affects only the block expression in which the &lt;code&gt;return&lt;/code&gt; operator is an expression, and has no effect otherwise.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i18)	test_nested_block (val) := 
	block (
		  [outer_var : 10],
		  print(&quot;Entering outer block expression&quot;),
		  
		       /* inner block expression */
		       block(
		           [inner_var : 20],
		           print (&quot;      Entering inner block expression&quot;),
	        
		           if val &gt; 5 then
	        
	               /* another inner block expression */  
	               block (
	               print (&quot;   val &gt; 5&quot;),
	               print (&quot;   Returning only to inner block expression&quot;),
		           return (inner_var + val)
	        	   /* returns only to the inner block expression */
	               ),
	               /* end of another inner block expression */
	        
	               print (&quot;   inner_var + val is &quot;, inner_var + val)
		           ),     
	               /* end of inner block expression */
		  
		  print (&quot;Back in outer block expression&quot;),
		  outer_var + val
		  
	/* end of outer block expression */
	)$

(%i19)	test_nested_block (1);
Entering outer block expression
      Entering inner block expression
      inner_var + val is 21
Back in outer block expression
(%o19)	11

(%i20)	test_nested_block (6);
Entering outer block expression
      Entering inner block expression
      val &gt; 5
      Returning only to inner block expression
Back in outer block expression
(%o20)	16&lt;/syntaxhighlight&gt;


'''''The &lt;code&gt;block&lt;/code&gt; operators''''': Each instance may define local variables and has a comma-separated sequence of expressions as arguments.

'''''Nested blocks''''': There are three &lt;code&gt;block&lt;/code&gt; operators used in the right-hand side of the function definition expression named &lt;code&gt;test_nested_block (val&lt;/code&gt;. There is an outer &lt;code&gt;block&lt;/code&gt; expression that has an inner &lt;code&gt;block&lt;/code&gt; expression as an argument,and there is a third &lt;code&gt;block&lt;/code&gt; expression that is an argument of the inner &lt;code&gt;block&lt;/code&gt; expression.

'''''The &lt;code&gt;return&lt;/code&gt; operator''''': If &lt;code&gt;val &gt; 5&lt;/code&gt; is &lt;code&gt;true&lt;/code&gt; then the return operator of the most inner  &lt;code&gt;block&lt;/code&gt; expression is evaluated and evaluation of remaining expressions of that block expression does not occur. The value of that most inner &lt;code&gt;block&lt;/code&gt; expression is the value of the argument of the return operator –  &lt;code&gt;inner_var + val&lt;/code&gt;. 

Evaluation of expressions continues with the first expression of the inner &lt;code&gt;block&lt;/code&gt; expression after the end of the most inner &lt;code&gt;block&lt;/code&gt; expression  – which is &lt;code&gt;print (&quot;   inner_var + val is &quot;, inner_var + val)&lt;/code&gt;. The value of the &lt;code&gt;print&lt;/code&gt; operator is the value of  &lt;code&gt;inner_var + val&lt;/code&gt;. However, while that value is the value of the inner &lt;code&gt;block&lt;/code&gt; expression it is effectively lost, as it is not the last expression of the outer &lt;code&gt;block&lt;/code&gt; sequence of expressions.  That value is the value of &lt;code&gt;outer_var + val&lt;/code&gt;, which, being the last expression of the outer &lt;code&gt;block&lt;/code&gt; is always the value of the function.

==== Block Expression Evaluation Sequence Modifications ====
&lt;code&gt;block&lt;/code&gt; expression arguments &lt;code&gt;expr&lt;sub&gt;1&lt;/sub&gt;, expr&lt;sub&gt;2&lt;/sub&gt;,…, expr&lt;sub&gt;n&lt;/sub&gt;&lt;/code&gt;  are generally evaluated each in turn from first to last, and the value of the &lt;code&gt;block&lt;/code&gt; expression is the value of &lt;code&gt;expr&lt;sub&gt;n&lt;/sub&gt;&lt;/code&gt; unless this sequence is modified by some means.

One way to modify the first-to-last expression evaluation sequence of a &lt;code&gt;block&lt;/code&gt; expression is by way of a &lt;code&gt;go&lt;/code&gt; operator with a ''label'' (or ''&quot;tag&quot;'') argument ( the ''&quot;go to&quot;'') as the following exemplifies:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i18)	sum_to_n (n) := block ( [i : 1, total : 0],
	                             loop,
	                                total : total + i,
	                                i : i + 1,
	                                if i &lt;= n then go (loop),
	                             total)$

(%i19)	sum_to_n(25);
(%o19)	325

(%i20)	n;
(%o20)	n

(%i21)	i;
(%o21)	i

(%i22)	total;
(%o22)	total
&lt;/syntaxhighlight&gt;


Note the following:

* &lt;code&gt;'''block ([ i : 1,total : 0], ...)'''&lt;/code&gt;: The list argument creates a local environment with local identifiers &lt;code&gt;i&lt;/code&gt; and &lt;code&gt;total&lt;/code&gt;. The function argument &lt;code&gt;n&lt;/code&gt; is also a local identifier.
* &lt;code&gt;'''loop'''&lt;/code&gt;: This label serves as a target inside the &lt;code&gt;block&lt;/code&gt; expression to where &lt;code&gt;go (loop)&lt;/code&gt; can jump.
* &lt;code&gt;'''if i &lt;= n then go (loop)'''&lt;/code&gt;: This conditional expression causes the &lt;code&gt;go (loop)&lt;/code&gt; operator to be evaluated if the condition is &lt;code&gt;true&lt;/code&gt;.
* &lt;code&gt;'''total'''&lt;/code&gt;: The value of this local identifier is the returned value of the &lt;code&gt;block&lt;/code&gt; expression.
It should also be worth noting that the identifiers &lt;code&gt;n&lt;/code&gt;, &lt;code&gt;i&lt;/code&gt;, and &lt;code&gt;total&lt;/code&gt; have local values assigned within the &lt;code&gt;block&lt;/code&gt; expression, but their global values are themselves. Also notice that the identifiers &lt;code&gt;i&lt;/code&gt; and &lt;code&gt;total&lt;/code&gt; were both declared local and assigned initial values within the &lt;code&gt;block&lt;/code&gt; list argument.

The ''go-to'' label argument of the &lt;code&gt;go&lt;/code&gt; operator must be the name of a tag appearing within the same block expression. The &lt;code&gt;go&lt;/code&gt; operator cannot be used to go to a tag in a different &lt;code&gt;block&lt;/code&gt; expression. There is nothing special about the &lt;code&gt;loop&lt;/code&gt; identifier name used for the go-to tag in this example. Other identifiers could be used, but they must be atomic.

Another way to modify a &lt;code&gt;block&lt;/code&gt; expression evaluation sequence is by way of the &lt;code&gt;throw&lt;/code&gt; operator.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i32)	/* Define a function using a block expression that searches 
	     for a specific condition and a throw value to catch */
	
	find_element (target_list, threshold) := block (
	      
	    [found_val : false], /* local identifier value */
	    
	      catch(
	          
	        for x in target_list do 
	          (
	              if x &gt; threshold then 
	                (
	                  /* Immediately exit the block and 
	                     return this value */
	                  throw (x)
	                  )
	            ),
	          /* This string is returned only if the do loop 
	             finishes without a throw to catch */
	                 &quot;No element exceeded the threshold&quot;
	      )
	    
	)$

(%i31)	/* Test the block */
	find_element ( [10, 20, 55, 80], 50 );
(%o31)	55&lt;/syntaxhighlight&gt;This example unpacks as follows:

&lt;code&gt;'''catch (...)'''&lt;/code&gt;: This expression creates a target scope that ''&quot;catches&quot;'' the value of any &lt;code&gt;throw&lt;/code&gt; expression evaluated within that scope.

&lt;code&gt;'''throw (x)'''&lt;/code&gt;: When Maxima encounters this operator, it immediately stops evaluation of the &lt;code&gt;do&lt;/code&gt; loop expression '''''and the rest of the''''' &lt;code&gt;block&lt;/code&gt; '''''expression.''''' It jumps directly out of the scope of the &lt;code&gt;catch&lt;/code&gt; expression, returning the value of &lt;code&gt;x&lt;/code&gt; as the value of the entire &lt;code&gt;catch&lt;/code&gt; expression.

==== Nested Block Expressions ====
&lt;code&gt;block&lt;/code&gt; operators may appear within other block expressions as arguments – '''''nested''''' &lt;code&gt;block&lt;/code&gt; expressions. A local environment with local identifiers may be created for nested block expressions. Local values for identifiers, if declared by a first &lt;code&gt;block&lt;/code&gt; operator list argument, are created each time a nested &lt;code&gt;block&lt;/code&gt; is evaluated.  

However, identifiers with global values that have not been declared as local within any &lt;code&gt;block&lt;/code&gt; expressions, are global values for nested &lt;code&gt;block&lt;/code&gt; expressions as well as enclosing &lt;code&gt;block&lt;/code&gt; expressions. Likewise, local identifiers of any enclosing &lt;code&gt;block&lt;/code&gt; expression have values that are global within any enclosed blocks, if not declared as local within the enclosed block. If the value of an identifier is not local in a &lt;code&gt;block&lt;/code&gt; expression, its value is the value most recently assigned by an enclosing &lt;code&gt;block&lt;/code&gt; expression, if any value has been assigned. Otherwise, it is the value of the identifier in the global environment. &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i23)	z : 2^(1/3);
(z)	2^(1/3)

(%i24) /* Outer block starts */
	block 
	(
	 [x : 10, y : 20],
	 /* values of x and y declared local to outer block */
	  
	 /* Inner block starts */
	     block 
	     (
	      [y : 99, z : 100], 
	      /* values of y and z declared local to inner block */
	      print (&quot;Inside inner block:&quot;),
	      print (&quot;x =&quot;,  x, &quot;is the value of x from outer block&quot;),
	      print (&quot;y =&quot;,  y, &quot;is the local value of y of outer block&quot;),
	      print(&quot;z =&quot;,  z, &quot;is the local value of z of inner block&quot;)
	     ),
	 /* Inner block ends */
	 
	 /* Outer block resumes */
	 print (&quot;Back in outer block:&quot;),
	 print (&quot;x =&quot;,  x, &quot;is the value of x from outer block&quot;),
	 print (&quot;y =&quot;,  y,  &quot;is the restored value of y of the outer block&quot;),
	 print (&quot;z =&quot;,  z,  &quot;is the value of z global to both blocks&quot;)
	 /* Outer block ends */
	)$
	
Inside inner block:
x = 10 is the value of x from outer block
y = 99 is the local value of y of outer block
z = 100 is the local value of z of inner block
Back in outer block:
x = 10 is the value of x from outer block
y = 20 is the restored value of y of the outer block
z = 2^(1/3) is the value of z global to both blocks
&lt;/syntaxhighlight&gt;

==== Values, Properties, and the &lt;code&gt;local&lt;/code&gt; Operator ====
The expression &lt;code&gt;local (v&lt;sub&gt;1&lt;/sub&gt;, v&lt;sub&gt;2&lt;/sub&gt;, ... , v&lt;sub&gt;m&lt;/sub&gt;)&lt;/code&gt; within a &lt;code&gt;block&lt;/code&gt; expression saves the '''''properties''''' associated with the symbols &lt;code&gt;v&lt;sub&gt;1&lt;/sub&gt;, v&lt;sub&gt;2&lt;/sub&gt;, ... , v&lt;sub&gt;m&lt;/sub&gt;&lt;/code&gt;, removes any properties before evaluating other expressions, and restores any saved properties on exit from the block.

Because Maxima is an application based on the Common Lisp programming language, it utilizes Lisp '''''symbol''''' structure. Lisp symbols are objects that carry their own &quot;dictionary&quot; of attributes. A Lisp symbol's internal property list (''plist'') is a built-in data structure attached directly to a symbol. Maxima uses this underlying Lisp symbol structure to associate '''''properties''''' with Maxima identifiers.

Properties of identifiers can be ''declared explicitly'' by users. &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i23)	declare (x, real);
(%o23)	done
&lt;/syntaxhighlight&gt;
However, some identifier property declarations are ''implemented implicitly'' as properties of a symbol, including &lt;code&gt;:=&lt;/code&gt;, &lt;code&gt;array&lt;/code&gt;, &lt;code&gt;dependencies&lt;/code&gt;, &lt;code&gt;atvalue&lt;/code&gt;, &lt;code&gt;matchdeclare&lt;/code&gt;, &lt;code&gt;atomgrad&lt;/code&gt;, &lt;code&gt;constant&lt;/code&gt;, &lt;code&gt;nonscalar&lt;/code&gt;, &lt;code&gt;assume&lt;/code&gt;, and some others. Below is a description of how each of those specific declarations is implemented as a property under the hood:

====== Functions and Arrays ======
* '''&lt;code&gt;:=&lt;/code&gt; (Function Definition):''' When you define a function using &lt;code&gt;f(x) := x^2&lt;/code&gt;, the actual expression (&lt;code&gt;x^2&lt;/code&gt;) and its argument list (&lt;code&gt;x&lt;/code&gt;) are stored as a property of the symbol &lt;code&gt;f&lt;/code&gt;.
* '''&lt;code&gt;array&lt;/code&gt;:''' When you declare or use a subscripted array (like &lt;code&gt;a[i]&lt;/code&gt;), the array type, dimensions, and memory pointer are attached as a property to the symbol &lt;code&gt;a&lt;/code&gt;. This differentiates it from a standard scalar variable.

====== Calculus and Dependencies ======
* '''&lt;code&gt;dependencies&lt;/code&gt;:''' If you declare &lt;code&gt;depends(y, x)&lt;/code&gt;, Maxima attaches a dependency list property to &lt;code&gt;y&lt;/code&gt; noting that it functionally depends on &lt;code&gt;x&lt;/code&gt;. This tells the &lt;code&gt;diff&lt;/code&gt; (differentiation) engine not to treat &lt;code&gt;y&lt;/code&gt; as a constant relative to &lt;code&gt;x&lt;/code&gt;.
* '''&lt;code&gt;atvalue&lt;/code&gt;:''' When you define a specific value for an expression at a boundary point (e.g., &lt;code&gt;atvalue(y, x=0, 1)&lt;/code&gt;), this boundary constraint is stored as an evaluation property on the symbol &lt;code&gt;y&lt;/code&gt;.
* '''&lt;code&gt;atomgrad&lt;/code&gt;:''' This assigns a specific gradient or derivative to an atomic identifier (e.g., telling Maxima what (df/dx) is explicitly). Maxima saves this rule as a gradient property on that symbol.

====== Pattern Matching and Rules ======
* '''&lt;code&gt;matchdeclare&lt;/code&gt;:''' Used in Maxima's pattern-matching system (like &lt;code&gt;tellsimp&lt;/code&gt;). When you type &lt;code&gt;matchdeclare(x, freeof(a))&lt;/code&gt;, Maxima attaches a predicate property to &lt;code&gt;x&lt;/code&gt;. When a pattern rule runs, Maxima looks at property list of &lt;code&gt;x&lt;/code&gt; to see what conditions a matching expression must meet.

====== Mathematical and Evaluation Attributes ======
* '''&lt;code&gt;constant&lt;/code&gt;:''' Declaring &lt;code&gt;declare(c, constant)&lt;/code&gt; places a &quot;constant&quot; flag on property list of  &lt;code&gt;c&lt;/code&gt;. Core routines (like integration and differentiation) check this flag to know they can pull &lt;code&gt;c&lt;/code&gt; out of integrals or differentiate it to zero.
* '''&lt;code&gt;nonscalar&lt;/code&gt;:''' Tells Maxima to treat a symbol as a matrix or vector rather than a regular number. This property changes how operators like &lt;code&gt;.&lt;/code&gt; (non-commutative multiplication) treat the symbol.
* '''&lt;code&gt;assume&lt;/code&gt;:''' When an expression such as &lt;code&gt;assume(x &gt; 0)&lt;/code&gt; is used, Maxima's database system (&lt;code&gt;context&lt;/code&gt;) assigns facts and properties (like &lt;code&gt;pos&lt;/code&gt; or &lt;code&gt;nonnegative&lt;/code&gt;) to the symbol &lt;code&gt;x&lt;/code&gt;, allowing the simplifier to safely reduce expressions like &lt;code&gt;sqrt(x^2)&lt;/code&gt; to &lt;code&gt;x&lt;/code&gt;.

The effect of the &lt;code&gt;local&lt;/code&gt; operator is to make such declarations effective only within a &lt;code&gt;block&lt;/code&gt; expression. Otherwise, declarations within a &lt;code&gt;block&lt;/code&gt; expression are considered to be global declarations.

So what does all of this mean to the typical Maxima user? It means that the list of identifiers that is the first argument  of a &lt;code&gt;block&lt;/code&gt; expression only declares the '''''values''''' of those identifiers as local to the &lt;code&gt;block&lt;/code&gt; expression in which the list is an argument. Any properties of identifiers are not declared local by this means. 

In order to declare '''''properties''''' of identifiers to be local to a &lt;code&gt;block&lt;/code&gt; expression, the &lt;code&gt;local&lt;/code&gt; operator must be used as an expression within the &lt;code&gt;block&lt;/code&gt; expression. At the point where the local operator is evaluated as an argument of a &lt;code&gt;block&lt;/code&gt; expression, the properties of the identifiers that are arguments to the &lt;code&gt;local&lt;/code&gt; operator become local to the block. It is not an unfair criticism that perhaps the &lt;code&gt;local&lt;/code&gt; operator should have been named something like &lt;code&gt;local_properties&lt;/code&gt;. &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i25)	f (s) := cos (s);
(%o25)	f(s):=cos(s)

(%i26)	f (%pi/6);
(%o26)	sqrt(3)/2

(%i27)	block (local (f), f (s) := sin (s), f (%pi/6));
(%o27)	1/2

(%i28)	f (s);
(%o28)	cos(s)
&lt;/syntaxhighlight&gt;In the above example, the '''''properties''''' of identifier &lt;code&gt;f&lt;/code&gt; were declared to be local in the &lt;code&gt;block&lt;/code&gt; expression using the &lt;code&gt;local&lt;/code&gt; operator. However, global properties of the identifier &lt;code&gt;f&lt;/code&gt; were not affected by the local function definition of &lt;code&gt;f&lt;/code&gt; in the &lt;code&gt;block&lt;/code&gt; expression. The global definition expression of &lt;code&gt;f&lt;/code&gt; which is &lt;code&gt;cos (s)&lt;/code&gt; and the argument &lt;code&gt;s&lt;/code&gt; were not affected by the local definition of &lt;code&gt;f&lt;/code&gt; because the properties of &lt;code&gt;f&lt;/code&gt; were declared local to the &lt;code&gt;block&lt;/code&gt; expression.  

&lt;code&gt;block&lt;/code&gt; expressions can be used for different purposes in the Maxima programming context. &lt;code&gt;block&lt;/code&gt; expressions can be used in a stand-alone fashion or as part of an expression. However, &lt;code&gt;block&lt;/code&gt; expressions are commonly used in expressions that define '''''functions''''', which is the topic that follows. 

=== Functions ===
{| class=&quot;wikitable&quot;
|+Function Definition Operators
and Identifiers
|&lt;code&gt;:=&lt;/code&gt;
|&lt;code&gt;fundef&lt;/code&gt;
|&lt;code&gt;buildq&lt;/code&gt;
|-
|&lt;code&gt;::=&lt;/code&gt;
|&lt;code&gt;lambda&lt;/code&gt;
|&lt;code&gt;macros&lt;/code&gt;
|-
|&lt;code&gt;define&lt;/code&gt;
|&lt;code&gt;local&lt;/code&gt;
|&lt;code&gt;slice&lt;/code&gt;
|-
|&lt;code&gt;dispfun&lt;/code&gt;
|&lt;code&gt;remfunction&lt;/code&gt;
|
|-
|&lt;code&gt;functions&lt;/code&gt;
|&lt;code&gt;setup_autoload&lt;/code&gt;
|
|}
As a technical term '''''function''''' is aptly characterized as being overloaded. In the context of Maxima as a CAS, it has both a programming meaning and a mathematical meaning in terms of usage. In this book, the convention is to refer to what may otherwise be referred to as built-in Maxima functions as ''operators'' including those of built-in packages. By this convention, the term '''''function''''' in this book refers exclusively to expressions composed by the user by way of the &lt;code&gt;:=&lt;/code&gt; or &lt;code&gt;define&lt;/code&gt; operators.

As has been mentioned elsewhere in this book, what are conventionally termed ''operators'' that are built-in to Maxima, are at the level of underlying expression construction, Lisp procedures of one type or another. So it makes sense to simply refer to built-in Maxima functions and operators simply as operators one and all. This convention obviates the need for the repetitious use of qualifiers such as ''built-in Maxima'' and ''user-defined'' functions.

There are two operators used to define functions as follows:

# The &lt;code&gt;''''':='''''&lt;/code&gt; operator
# The &lt;code&gt;'''define'''&lt;/code&gt; operator

 &lt;var&gt;&lt;code&gt;f (x&lt;sub&gt;1&lt;/sub&gt;, x&lt;sub&gt;2,&lt;/sub&gt; ..., x&lt;sub&gt;n&lt;/sub&gt;) ''':=''' expr&lt;/code&gt;
 &lt;code&gt;f&lt;/code&gt; &lt;code&gt;[x&lt;sub&gt;1&lt;/sub&gt;, x&lt;sub&gt;2,&lt;/sub&gt; ..., x&lt;sub&gt;n&lt;/sub&gt;] ''':=''' expr&lt;/code&gt;
 &lt;code&gt;f&lt;/code&gt; &lt;code&gt;[x&lt;sub&gt;1&lt;/sub&gt;, x&lt;sub&gt;2,&lt;/sub&gt; ..., x&lt;sub&gt;n&lt;/sub&gt;](y&lt;sub&gt;1&lt;/sub&gt;, y&lt;sub&gt;2&lt;/sub&gt;, ..., y&lt;sub&gt;m&lt;/sub&gt;) ''':=''' expr&lt;/code&gt;&lt;/var&gt; 

 &lt;code&gt;define (f&lt;/code&gt; &lt;code&gt;(x&lt;sub&gt;1&lt;/sub&gt;, x&lt;sub&gt;2,&lt;/sub&gt; …, x&lt;sub&gt;n&lt;/sub&gt;), expr)&lt;/code&gt;
 &lt;code&gt;define (f&lt;/code&gt; &lt;code&gt;[x&lt;sub&gt;1&lt;/sub&gt;, x&lt;sub&gt;2,&lt;/sub&gt; …, x&lt;sub&gt;n&lt;/sub&gt;], expr)&lt;/code&gt;
 &lt;code&gt;define (f&lt;/code&gt; &lt;code&gt;[x&lt;sub&gt;1&lt;/sub&gt;, x&lt;sub&gt;2,&lt;/sub&gt; …, x&lt;sub&gt;n&lt;/sub&gt;](y&lt;sub&gt;1&lt;/sub&gt;, y&lt;sub&gt;2,&lt;/sub&gt; …, y&lt;sub&gt;m&lt;/sub&gt;), expr)&lt;/code&gt;
 &lt;code&gt;define (funmake (f, [&lt;/code&gt;&lt;code&gt;x&lt;sub&gt;1&lt;/sub&gt;, x&lt;sub&gt;2,&lt;/sub&gt; …, x&lt;sub&gt;n&lt;/sub&gt;]), expr)&lt;/code&gt;
 &lt;code&gt;define (arraymake (f, [&lt;/code&gt;&lt;code&gt;x&lt;sub&gt;1&lt;/sub&gt;, x&lt;sub&gt;2,&lt;/sub&gt; …, x&lt;sub&gt;n&lt;/sub&gt;]), expr)&lt;/code&gt;
 &lt;code&gt;define (ev (&lt;/code&gt;&lt;code&gt;expr&lt;sub&gt;1&lt;/sub&gt;, expr&lt;sub&gt;2&lt;/sub&gt;))&lt;/code&gt;
where &lt;code&gt;expr&lt;/code&gt; is some Maxima expression that is commonly referred to as the ''function body''. As can be concluded from the above, each of these operators has different forms of syntax that can be used. In any case, the most significant differences between these two operators are in terms of the evaluation of the function body and the composition and identification of functions dynamically. 

* '''Evaluation:'''
** The &lt;code&gt;:=&lt;/code&gt; operator '''suppresses (quotes)''' the evaluation of the function body when this operator is first evaluated. It does not evaluate or simplify the function body until the function identifier itself is evaluated with arguments.
** The &lt;code&gt;define()&lt;/code&gt; operator '''evaluates''' the function body when this operator is first evaluated. If the function body involves intermediate computations, substituted values, or extracted parts of expressions (like &lt;code&gt;rhs()&lt;/code&gt; or derivative results), the &lt;code&gt;define()&lt;/code&gt; operator includes the evaluated results of those directly into the function body.

* '''Dynamic Function Composition and Identifiers:'''
** Function identifiers cannot easily be composed dynamically on the left-hand side of the &lt;code&gt;:=&lt;/code&gt; operator when used inside programmatic loop expressions or in scripts.
** The &lt;code&gt;define()&lt;/code&gt; operator accepts expressions like &lt;code&gt;funmake&lt;/code&gt; or evaluated symbols as its first argument, allowing the composition and identification of functions dynamically during evaluation.


So, there are in general two different operators that can be used to define and evaluate functions. The choice by the Maxima user between these two operators depends on the purpose and context.

==== Function Definition Using the &lt;code&gt;:=&lt;/code&gt; Operator ====
For the purpose of understanding the two ways of defining functions, consider the following example which is elementary, but in terms of clarification is not merely simple:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* &quot;kill&quot; all previously used identifier and values  */
(%i29)	kill (all);
(%o0)	done

/* assign identifier x the global value of 5  */
(%i1)	x : 5;
(x)	5

/* define f as a function with local argument x  */
(%i2)	f (x) := x;
(%o2)	f(x):=x

/* evaluate f at local value of x is 3  */
(%i3)	f (3);
(%o3)	3

/* the global value of x is not affected  */
(%i4)	x;
(%o4)	5

/* show the definition expression of the function named f  */
(%i5)	fundef (f);
(%o5)	f(x):=x&lt;/syntaxhighlight&gt;'''Function Definition Using the''' '''&lt;code&gt;define&lt;/code&gt; Operator'''&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* define a function with identifier g with a
   local argument y and with a function body
   of identifier x */
   
(%i3)	define (g('x), x);
(%o3)	g(x):=5
/* identifier x of the function body is evaluated */
/* identifier x as an argument of g is local in scope */

(%i4)	fundef (g);
(%o4)	g(x):=5

/* the same identifier x used in three different roles */
    /* used as the global name of a function x */
    /* used as a local argument of a function */
    /* used as an unevaluated expression for a function body */
(%i7)	x(x) := x;
(%o7)	x(x):=x


(%i9)	x(3);
(%o9)	3

(%i10)	x;
(%o10)	5

(%i8)	fundef (x);
(%o8)	x(x):=x

(%i11)	define (x('x), x);
(%o11)	x(x):=5

(%i12)	fundef (x);
(%o12)	x(x):=5
&lt;/syntaxhighlight&gt;The purpose of this example is not to encourage this sort of syntax as a typical choice for identifiers and function definitions. The purpose is to clarify how Maxima implicitly determines the scope and meaning of identifiers used for function definition in the absence of any explicit user stipulations.
It should be noted that the &lt;code&gt;define&lt;/code&gt; operator not only evaluates the expression that is the function body, it also evaluates the arguments of the function identifier that is the first argument of the &lt;code&gt;define&lt;/code&gt; operator. Since there is a global value of the identifier &lt;code&gt;x&lt;/code&gt; of &lt;code&gt;5&lt;/code&gt;, it was necessary to suppress evaluation (quote) the argument in the expression &lt;code&gt;(%i12) define ('x), x);&lt;/code&gt; as otherwise an error would be the result:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* define a new function named x */
(%i14)	define (x('x), 'x^2);
(%o14)	x(x):=x^2

/* check the definition of the new function named x */
(%i15)	fundef (x);
(%o15)	x(x):=x^2

/* the identifier x has a global value */
(%i16)	values;
(%o16)	[x]

/* the global value of identifier x is 5 */
(%i17)	x;
(%o17)	5

/* the suppressed global value 'x of identifier x is x */
(%i18)	'x;
(%o18)	x

/* not quoting the global value of identifier x is an error  */
(%i19)	define (x(x), 'x^2);
define: in definition of x, parameter must be a symbol and must not be a system constant; found: 5
 -- an error. To debug this try: debugmode(true);
&lt;/syntaxhighlight&gt;

==== Understanding the Differences Between the &lt;code&gt;:=&lt;/code&gt; and &lt;code&gt;define&lt;/code&gt; Operators ====
In cases such as these, the suppression of evaluation by quoting is a user stipulation as to evaluation. Users must be aware of these differences between the two operators (&lt;code&gt;:=&lt;/code&gt; and &lt;code&gt;define&lt;/code&gt;) for the purpose of function definition in order to achieve what is intended and to avoid errors,&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i20)	f (x) := 3*x^3  +  4*x  -  5;
(%o20)	f(x):=3*x^3+4*x-5

(%i21)	fundef (f);
(%o21)	f(x):=3*x^3+4*x-5

(%i22)	f(2);
(%o22)	27

(%i23)	define (f (x) , 3*x^3  +  4*x  -  5);
define: in definition of f, parameter must be a symbol and must not be a system constant; found: 5
-- an error. To debug this try: debugmode(true);

(%i24)	define (f ('x) , 3*x^3  +  4*x  -  5);
(%o24)	f(x):=390

(%i25)	define (f ('x) , '(3*x^3  +  4*x  -  5));
(%o25)	f(x):=3*x^3+4*x-5

(%i26)	fundef (f);
(%o26)	f(x):=3*x^3+4*x-5

(%i27)	f(2);
(%o27)	27
&lt;/syntaxhighlight&gt;What is true in the case of these elementary examples is true in general for function definitions involving multiple arguments:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* x has a global value of 5 while y is local to g */
(%i28)	g (x, y)  :=  x^3 - y^2;
(%o28)	g(x,y):=x^3-y^2

(%i29)	g (6,2);
(%o29)	212

(%i30)	define (g('x, y), 'x^3 - y^2);
(%o30)	g(x,y):=x^3-y^2

(%i31)	values;
(%o31)	[x]

(%i32)	g (6,2);
(%o32)	212
&lt;/syntaxhighlight&gt;The &lt;code&gt;define&lt;/code&gt; operator is a good choice in cases where an existing expression is used as the function body:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i33)	/*  assign an expression to identifier expr */
	expr : diff('x^3, 'x);  /* Returns 3*x^2 */
(expr)	3*x^2

(%i34)	/* evaluate expr and define h (x) := 3*x^2 */
	define (h ('x), expr); 
(%o34)	h(x):=3*x^2
&lt;/syntaxhighlight&gt;In cases in which functions require local variables or more than one expression for the function body, use the block operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i35)	remvalue (x);
(%o35)	[x]

(%i36)	values;
(%o36)	[expr]
 --&gt;	power_sum (x, y) := block (
/* values of these identifiers are explicitly local to the function */
	    [sqx, sqy],  
/* unevaluated identifiers x and y are local arguments of the function
   and values of these identifiers are implicitly local to the function */
	    sqx : x^2,
	    sqy : y^2,
	    sqx + sqy /* the value of the function */
	)$

(%i37)	fundef (power_sum);
(%o37)	power_sum(x,y):=block([sqx,sqy],sqx:x^2,sqy:y^2,sqx+sqy)

(%i38)	power_sum (3,4);
(%o38)	25
&lt;/syntaxhighlight&gt;The &lt;code&gt;define&lt;/code&gt; operator could also be used to define this function, but with different definition values as a consequence:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i39)	define (power_sum (x,y), 
                block (
                [sqx,sqy], 
                sqx : x^2,
                sqy : y^2, 
                sqx + sqy
                )
               )$

(%i40)	fundef (power_sum);
(%o40)	power_sum(x,y):=y^2+x^2

(%i41)	power_sum (3,4);
(%o41)	25&lt;/syntaxhighlight&gt;The function definition of &lt;code&gt;power_sum&lt;/code&gt; is different using the &lt;code&gt;define&lt;/code&gt; operator instead of the &lt;code&gt;:=&lt;/code&gt; operator. The value of the function when referenced with arguments (&lt;code&gt;power_sum (3,4)&lt;/code&gt;) is the same in both cases – &lt;code&gt;25&lt;/code&gt;. However, in general for defining functions, this may not be the case. The choice between these two operators depends on the intentions of the user.

==== Practical Considerations Related to Function Composition ====

In general, programming is a technical skill as well as a subjective art. So, absolute rules are not offered here.  For practical purposes some &quot;guidelines&quot; are offered here that may be useful for Maxima function composition as well as Maxima programming in general: 

*
*
*
*
*


Consider the following linear algebraic equation:

&lt;math display=&quot;block&quot;&gt;3y - 7x = 10&lt;/math&gt;
As an example suppose the value that is sought is the slope &lt;code&gt;m&lt;/code&gt; of this equation, and in general, the slope of any linear equation regardless of the form.   &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* assign the linear equation to an identifier */
(%i42)	lineqn : 3*y - 7*x = 10;
(lineqn)	3*y-7*x=10

/* solve the linear equation for y */
(%i43)	solve([lineqn], [y])
(%o43)	[y=(7*x+10)/3]

/* use the index [1] of the list to get the solved equation */
(%i44)	solve([lineqn], [y])[1]
(%o44)	y=(7*x+10)/3

/* use the rhs operator to get right-hand side */
(%i45)	rhs(solve([lineqn], [y])[1]);
(%o45)	(7*x+10)/3

/* use the expand operator change the RHS */
(%i46)	expand(rhs(solve([lineqn], [y])[1]));
(%o46)	(7*x)/3+10/3

/* use the coeff operator to get the coefficient of x */
(%i47)	coeff(expand(rhs(solve([lineqn], [y])[1])),x,1);
(%o47)	7/3

/* define the function with an argument eqn for lineqn */
(%i48)	m (eqn) := coeff (expand (rhs (solve ([eqn], [y])[1])),x,1)$

/* check the function definition */
(%i49)	fundef (m);
(%o49)	m(eqn):=coeff(expand(rhs((solve([eqn],[y]))[1])),x,1)

/* reference the function using lineqn as an argument */
(%i50)	m (lineqn);
(%o50)	7/3

/* assign a different linear equation to lineqn */
(%i51)	lineqn : x = 6*y + 13;
(lineqn)	x=6*y+13

/* reference the function using lineqn as an argument */
%i52)	m (lineqn);
(%o52)	1/6&lt;/syntaxhighlight&gt;The function body of this example will result in an error if it is used with the &lt;code&gt;define&lt;/code&gt; operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i53)	define (
                m (eqn),
                coeff (expand (rhs (solve ([eqn], [y])[1])),x,1) 
               )$
inpart: invalid index 1 of list or matrix.
-- an error. To debug this try: debugmode(true);
&lt;/syntaxhighlight&gt;This error is a consequence of the evaluation that occurs when using the &lt;code&gt;define&lt;/code&gt; operator. In this case, this evaluation results in a reference to the indexed value of a list object that does not exist when evaluation occurs during definition – &lt;code&gt;solve ([eqn], [y])[1]&lt;/code&gt;.

==== Memoizing Functions ====
The functions discussed so far are often referred to as '''''ordinary functions'''''. The arguments of ordinary functions are enclosed using parentheses – &lt;var&gt;&lt;code&gt;(x&lt;sub&gt;1&lt;/sub&gt;, x&lt;sub&gt;2,&lt;/sub&gt; ..., x&lt;sub&gt;n&lt;/sub&gt;)&lt;/code&gt;.&lt;/var&gt; Function definition forms which include arguments enclosed by brackets (as in &lt;var&gt;&lt;code&gt;[x&lt;sub&gt;1&lt;/sub&gt;, x&lt;sub&gt;2,&lt;/sub&gt; ..., x&lt;sub&gt;n&lt;/sub&gt;]&lt;/code&gt;&lt;/var&gt;) are called '''''memoizing functions'''''.

Memoizing functions can be categorized both as functions and as data structures – specifically a ''hashed array'' of values. Memoizing functions are also referred to as '''''array functions'''''. In any case, memoizing functions can be defined using either the &lt;code&gt;:=&lt;/code&gt; operator or the &lt;code&gt;define&lt;/code&gt; operator. 

If the form of the function definition expression is &lt;code&gt;f [x&lt;sub&gt;1&lt;/sub&gt;, x&lt;sub&gt;2&lt;/sub&gt;,..., x&lt;sub&gt;n&lt;/sub&gt;] := expr&lt;/code&gt; The  function body &lt;code&gt;expr&lt;/code&gt; is evaluated once for each individual value of the arguments, and that value is the value of the function, without again evaluating the function body, whenever referenced using arguments that have those same values. 

Once evaluated during a function reference with arguments, that value of a memoizing function is thereby &quot;frozen&quot; in other words. This frozen value also becomes an instance of a hashed array data structure that can be referenced by way of the value of the index used as an argument when first evaluated. 

In keeping with previous practice, the examples provided here are intentionally elementary for the purpose of demonstrating and clarifying the technical aspects involved. There is thereby no intention to convey that the composition of function definition expressions with multiple arguments and complex expressions for the function body is ruled out or of lesser practical value.   &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* define a memoizing function f */
/* x and n may serve as both arguments and array indices */
(%i54)	f  [x, n] := x^n;
(%o54)	f[x,n]:=x^n

/* check the array information for f */
(%i55)	arrayinfo (f);
(%o55)	[hashed,2]

/* f does not appear in the list of functions */
(%i56)	functions;
(%o56)	[m(lineqn)]

/* reference f with argument values  */
(%i57)	f [2,3] ;
(%o57)	8

/* check the array information for f again */
(%i58)	arrayinfo (f);
(%o58)	[hashed,2,[2,3]]

/* list the array values of f */
(%i59)	listarray (f);
(%o59)	[8]

/* f does appear in the list of arrays */
(%i60)	arrays;
(%o60)	[f]

/* reference f with new argument values  */
(%i61)	f [5,2];
(%o61)	25

/* check the array information for f again */
(%i62)	arrayinfo (f);
(%o62)	[hashed,2,[2,3],[5,2]]

/* list the array values of f */
(%i63)	listarray (f);
(%o63)	[8,25]&lt;/syntaxhighlight&gt;An expression of the form &lt;code&gt;define (f [x1, x2&lt;/code&gt;&lt;code&gt;,…, xn], expr)&lt;/code&gt; may also be used to define the same memoizing function &lt;code&gt;f&lt;/code&gt; in this case as the evaluation imposed by the &lt;code&gt;define&lt;/code&gt; operator during evaluation of these function arguments and this function body that occurs makes no difference:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* remove the function definition and values of f */
(%i64)	remarray (f);
(%o64)	[f]

/* the list of arrays is now empty */
(%i65)	arrays;
(%o65)	[]

/* define the same memoizing function f using the define operator */
/* evaluation makes no difference to the definition of f in this case */
(%i66)	define (f [x,n], x^n);
(%o66)	f[x,n]:=x^n

/* reference f with different argument values  */
(%i67)	f [3, 2];
(%o67)	9

/* reference f again with different argument values  */
(%i68)	f [2, 5];
(%o68)	32

/* f again appears in the list of arrays */
(%i69)	arrays;
(%o69)	[f]

/* check the array information for f */
(%i70)	arrayinfo (f);
(%o70)	[hashed,2,[2,5],[3,2]]

/* list the array values of f */
(%i71)	listarray (f);
(%o71)	[32,9]
&lt;/syntaxhighlight&gt;

===== Special Forms of Memoizing Functions =====
An expression of the form &lt;code&gt;f [x&lt;sub&gt;1&lt;/sub&gt;, x&lt;sub&gt;2&lt;/sub&gt;,..., x&lt;sub&gt;n&lt;/sub&gt;](y&lt;sub&gt;1&lt;/sub&gt;, y&lt;sub&gt;2&lt;/sub&gt;,..., y&lt;sub&gt;m&lt;/sub&gt;):= expr&lt;/code&gt;, or alternatively of the form &lt;code&gt;define (f [x1, x2&lt;/code&gt;&lt;code&gt;,…, xn](y&lt;sub&gt;1&lt;/sub&gt;, y&lt;sub&gt;2&lt;/sub&gt;,..., y&lt;sub&gt;m&lt;/sub&gt;), expr)&lt;/code&gt;, may also be used to define a memoizing function named &lt;code&gt;f&lt;/code&gt;.  When either of these forms are used to compose a function definition expression, there is a sense in which the resulting function is a hybrid – part memoizing function, and part &quot;ordinary&quot; function. These forms create a hashed array of functions where the array subscripts &lt;code&gt;[x&lt;sub&gt;1&lt;/sub&gt;, x&lt;sub&gt;2&lt;/sub&gt;,..., x&lt;sub&gt;n&lt;/sub&gt;]&lt;/code&gt; evaluate immediately to &quot;specialize&quot; the function body, while the ordinary function arguments &lt;code&gt;(y&lt;sub&gt;1&lt;/sub&gt;, y&lt;sub&gt;2&lt;/sub&gt;,..., y&lt;sub&gt;m&lt;/sub&gt;)&lt;/code&gt; are used when evaluating these individual functions.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* Define a function for an array of &quot;shifted&quot; power functions */
(%i72)	define( p[n](x), x^n + n );
(%o72)	p[n](x):=x^n+n

(%i73)	p[2];
(%o73)	lambda([x],x^2+2)

(%i74)	p[2](5);
(%o74)	27

(%i75)	p[4];
(%o75)	lambda([x],x^4+4)

(%i76)	p[4](5);
(%o76)	629

(%i77)	arrayinfo (p);
(%o77)	[hashed,1,[2],[4]]

(%i78)	listarray (p)
(%o78)	[lambda([x],x^2+2),lambda([x],x^4+4)]

(%i79)	p[5];
(%o79)	lambda([x],x^5+5)

(%i80)	p[5](2);
(%o80)	37

(%i81)	listarray (p);
(%o81)	[lambda([x],x^2+2),lambda([x],x^4+4),lambda([x],x^5+5)]

(%i82)	arrayinfo (p);
(%o82)	[hashed,1,[2],[4],[5]]&lt;/syntaxhighlight&gt;How It Works

1. Defining the Function: The command above generates a distinct function for each subscript n.

2. Evaluating the Array Element: If you call p[3], Maxima evaluates the index n=3 and implicitly defines an ordinary function equivalent to p[3](x) := x^3 + 3.

3. Evaluating the Function:

• Running p[3](2); will compute \(2^3 + 3\), returning 11.

• Running p[2](5); will compute \(5^2 + 2\), returning 27.

This syntax is useful in Maxima when you need to programmatically pre-generate an array of custom functions or transformations where the functional form depends directly on structural indices.

==== Lambda Expressions ====

==== Special Forms of the &lt;code&gt;define&lt;/code&gt; Operator ====

==== Some Techniques for Function Composition ====

=== Conditional Expressions – Special Operator &lt;code&gt;if&lt;/code&gt; ===

=== Expressions for Iteration – Special Operator &lt;code&gt;do&lt;/code&gt; ===
The special operator &lt;code&gt;do&lt;/code&gt;  is used to compose expressions for iteration. It is typically used with the following other special operators:

* &lt;code&gt;while&lt;/code&gt;
* &lt;code&gt;unless&lt;/code&gt;
* &lt;code&gt;for&lt;/code&gt;
* &lt;code&gt;from&lt;/code&gt;
* &lt;code&gt;thru&lt;/code&gt;
* &lt;code&gt;step&lt;/code&gt;
* &lt;code&gt;next&lt;/code&gt;
* &lt;code&gt;in&lt;/code&gt;

The general forms of &lt;code&gt;do&lt;/code&gt; expressions Maxima supports are:

&lt;code&gt;for&lt;/code&gt; variable: initial_value &lt;code&gt;step&lt;/code&gt; increment &lt;code&gt;thru&lt;/code&gt; limit &lt;code&gt;do&lt;/code&gt; body

&lt;code&gt;for&lt;/code&gt; variable: initial_value &lt;code&gt;step&lt;/code&gt; increment &lt;code&gt;while&lt;/code&gt; condition &lt;code&gt;do&lt;/code&gt; body

&lt;code&gt;for&lt;/code&gt; variable: initial_value &lt;code&gt;step&lt;/code&gt; increment &lt;code&gt;unless&lt;/code&gt; condition &lt;code&gt;do&lt;/code&gt; body

&lt;code&gt;for&lt;/code&gt; variable &lt;code&gt;in&lt;/code&gt; list &lt;code&gt;do&lt;/code&gt; body

&lt;code&gt;for&lt;/code&gt; variable &lt;code&gt;in&lt;/code&gt; expr &lt;code&gt;do&lt;/code&gt; body

&lt;code&gt;for&lt;/code&gt; variable &lt;code&gt;in&lt;/code&gt; hash_table &lt;code&gt;do&lt;/code&gt; body

=== Lisp and Maxima ===

{{BookCat}}</text>
      <sha1>mcol4a2a4yt33h4sjieg823r7kwqa16</sha1>
    </revision>
  </page>
  <page>
    <title>User:TechVindicator/sandbox</title>
    <ns>2</ns>
    <id>485726</id>
    <revision>
      <id>4676696</id>
      <parentid>4676486</parentid>
      <timestamp>2026-10-18T06:53:22Z</timestamp>
      <contributor>
        <username>TechVindicator</username>
        <id>3626296</id>
      </contributor>
      <minor />
      <origin>4676696</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="301" sha1="a9k8bvsknsgyjh29e9na4wegcssv2r2" xml:space="preserve">{{User:TechVindicator/QuickAccess}}
==East Germany's Geography==
When East Germany was a country, the country was divided into Bezirks between 1952-1990. Bezirks mean districts in German, and are similar to states in the USA. From World War II through 1952, East Germany was divided into five Länder.</text>
      <sha1>a9k8bvsknsgyjh29e9na4wegcssv2r2</sha1>
    </revision>
    <revision>
      <id>4676697</id>
      <parentid>4676696</parentid>
      <timestamp>2026-10-18T06:57:21Z</timestamp>
      <contributor>
        <username>TechVindicator</username>
        <id>3626296</id>
      </contributor>
      <minor />
      <origin>4676697</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="450" sha1="cv46m9a2s8jestx0il782rapz93ftm8" xml:space="preserve">{{User:TechVindicator/QuickAccess}}
==East Germany's Geography==
When East Germany was a country, the country was divided into Bezirks between 1952-1990. Bezirks mean districts in German, and are similar to states in the USA. From World War II through 1952, East Germany was divided into five Länder.
&lt;br&gt;
East Germany bordered the Baltic Sea to the north, Poland to the east, Czechoslovakia to the southeast, and West Germany to the west and south.</text>
      <sha1>cv46m9a2s8jestx0il782rapz93ftm8</sha1>
    </revision>
  </page>
  <page>
    <title>Vehicle Identification Numbers (VIN codes)/Jaguar/VIN Codes</title>
    <ns>0</ns>
    <id>485791</id>
    <revision>
      <id>4676684</id>
      <parentid>4676366</parentid>
      <timestamp>2026-10-18T04:59:53Z</timestamp>
      <contributor>
        <username>JustTheFacts33</username>
        <id>3434282</id>
      </contributor>
      <comment>/* Model Line (Position 4) */</comment>
      <origin>4676684</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="42493" sha1="ajeaccl9jggjfeh6yb1smz08qjnq4g1" xml:space="preserve">{{Vehicle Identification Numbers (VIN codes)/Warning}}{{clear}}

This VIN number decoding and designation system is used primarily for the North American Market. European and Asian markets use other decoding and designation systems.

==General Template for Jaguar's VIN format (All models: 2016- EXCEPT F-Type '16-'17, XJ '16-'19)==

===Jaguar WMIs (2016-) (Position 1-3)===

* SAJ - Jaguar passenger car (UK)
* SAD - Jaguar SUV (UK &amp; Europe)
* L2C - Chery Jaguar Land Rover (China)

===Model Line (Position 4)===

{| class=&quot;wikitable&quot;
|+Position 4
!VIN code
!Description
|-
|A
|[[w:Jaguar XE|Jaguar XE]] ('17-'20)
|-
|B
|[[w:Jaguar XF (X260)|Jaguar XF]] ('16-'24)
|-
|C
|[[w:Jaguar F-Pace|Jaguar F-Pace]] ('17-'26)
|-
|D
|[[w:Jaguar F-Type|Jaguar F-Type]] ('18-'24)
|-
|E
|[[w:Jaguar Type 01|Jaguar Type 01]] ('28-)
|-
|F
|[[w:Jaguar E-Pace|Jaguar E-Pace]] ('18-'24)
|-
|H
|[[w:Jaguar I-Pace|Jaguar I-Pace EV]] ('19-'24)
|}

===Trim Level/Drive Wheels/Restraint System (Position 5)===

{| class=&quot;wikitable&quot;
|+Position 4
!VIN code
!Trim Level
!Drive Wheels
!Restraint System
|-
|D
|XF Premium '16-
|Rwd
|
|-
|E
|XF Prestige '16-
|Rwd
|
|-
|F
|XF R-Sport '16-
|Rwd
|
|-
|G
|XF S '16-
|Rwd
|
|-
|J
|XF Premium '16-
|Awd
|
|-
|K
|XF Prestige '16-
|Awd
|
|-
|L
|XF R-Sport '16-
|Awd
|
|-
|M
|XF S '16-
|Awd
|
|-
|N
|XF First Edition '16
|Awd
|
|}

===Body Style (Position 6):===
* 1 = Coupe (F-Type coupe)
* 2 = 5-door wagon (XF Sportbrake wagon '18-'20)
* 2 = 5-door (E-Pace, F-Pace, I-Pace EV)
* 4 = 4-door sedan (XE, XF sedan, Type 01)
* 5 = Convertible (F-Type convertible)

===Transmission (Position 7) 2016-2017:===
* B = Automatic (XE '17, XF '16-'17, F-Pace '17)

===Engine/Emissions Control System (Position 8) 2016-2017:===

{| class=&quot;wikitable&quot;
|+Position 8
! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications
|-
| G || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,&lt;br /&gt; 16 valve||Direct Injection. ULEV. Dual VVT. [[w:Ford EcoBoost engine#2.0 L (2010–2018)|Ford EcoBoost engine (Mazda L engine-based)]].&lt;br&gt; Jaguar XE 25t ('17).
|-
| N || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Diesel || DOHC,&lt;br /&gt; 16 valve||Common-rail Direct Injection. Exhaust VVT. [[w:Ingenium engine family|JLR Ingenium AJ20D engine]]. Jaguar XE 20d, XF 20d, F-Pace 20d ('17).
|-
| V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 35t ('16-'17) [If 5th pos. of VIN is NOT G, H, M, or N]. Jaguar XE 35t ('17). Jaguar F-Pace 35t ('17) [If 5th pos. of VIN is NOT M or P].
|-
| V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 380 PS/375 hp. Jaguar XF S ('16-'17). If 5th pos. of VIN is G, H, M, or N. Jaguar F-Pace S ('17) [If 5th pos. of VIN is M or P].
|}

===Engine (Position 7-8) 2018-:===

{| class=&quot;wikitable&quot;
|+Position 7-8
! VIN Pos. 7 !! Power Level !! Transmission !! VIN Pos. 8 !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications
|-
| E || 550 PS/542 hp || 8-spd. Auto. || E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct injection. Dual Continuously VCT (VVT). [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133S engine]]. Jaguar F-Type R ('18-'20), F-Pace SVR ('19-'24).
|-
| E || 450 PS/444 hp || 8-spd. Auto. || E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct injection. Dual Continuously VCT (VVT). [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133S engine]]. Jaguar F-Type P450 ('22-24).
|-
| F || 575 PS/567 hp || 8-spd. Auto. || E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct injection. Dual Continuously VCT (VVT). [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133S engine]]. Jaguar F-Type SVR ('18-'20), F-Type R ('21-'24),&lt;br&gt; F-Pace SVR 575 Edition ('25-'26).
|-
| F || 600 PS/592 hp || 8-spd. Auto. || E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct injection. Dual Continuously VCT (VVT). [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133S engine]]. Jaguar XE SV Project 8 ('19).
|-
| F || 180 PS/178 hp || 8-spd. Auto. || N || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Diesel || DOHC,&lt;br /&gt; 16 valve||Common-rail Direct Injection. Exhaust VVT.&lt;br&gt; [[w:Ingenium engine family|JLR Ingenium AJ20D4/AJ200D engine]].&lt;br&gt; Jaguar XE 20d ('18-'19), XF 20d ('18-'19), F-Pace 20d ('18-'19).
|-
| E || 340 PS/335 hp || 8-spd. Auto. || U || 3.0L || I6 Turbo [[w:Intercooler|IC]] || Gas || DOHC,&lt;br /&gt; 24 valve||48v Mild Hybrid. E-supercharger. Direct Injection. Dual VVT.  CVVL (Intake VVL). [[w:Ingenium engine family|JLR Ingenium AJ20P6/AJ300P engine]].&lt;br&gt; Jaguar F-Pace P340 ('21-'22). 
|-
| F || 400 PS/395 hp || 8-spd. Auto. || U || 3.0L || I6 Turbo [[w:Intercooler|IC]] || Gas || DOHC,&lt;br /&gt; 24 valve||48v Mild Hybrid. E-supercharger. Direct Injection. Dual VVT.  CVVL (Intake VVL). [[w:Ingenium engine family|JLR Ingenium AJ20P6/AJ300P engine]].&lt;br&gt; Jaguar F-Pace P400 ('21-'26).
|-
| E || 340 PS/335 hp || 8-spd. Auto. || V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. Continuously variable intake &amp; exhaust valve timing.&lt;br&gt; [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; Jaguar XE 35t ('18), XF 35t ('18), F-Type ('18), F-Type P340 ('19-'20),&lt;br&gt; F-Pace 35t ('18).
|-
| F || 380 PS/375 hp || 8-spd. Auto. || V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. Continuously variable intake &amp; exhaust valve timing.&lt;br&gt; [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; Jaguar XE S ('18-'19), XF S ('18-'20), F-Type ('18),&lt;br&gt; F-Type P380 ('19), F-Type P380 R-Dynamic ('19-'21), F-Pace S ('18-'20).
|-
| G || 400 PS/395 hp || 8-spd. Auto. || V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. Continuously variable intake &amp; exhaust valve timing.&lt;br&gt; [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; Jaguar F-Type 400 Sport ('18).
|-
| J || 340 PS/335 hp || 6-spd. Man. || V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. Continuously variable intake &amp; exhaust valve timing.&lt;br&gt; [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; Jaguar F-Type ('18), F-Type P340 ('19).
|-
| K || 380 PS/375 hp || 6-spd. Man. || V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. Continuously variable intake &amp; exhaust valve timing.&lt;br&gt; [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; Jaguar F-Type P380 R-Dynamic ('18-'19).
|-
| E || 250 PS/247 hp || 8-spd. Auto. || X || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,&lt;br /&gt; 16 valve||Direct Injection. Dual VVT. CVVL (Intake VVL).&lt;br&gt; [[w:Ingenium engine family|JLR Ingenium AJ20P4/AJ200P engine]].&lt;br&gt; Jaguar F-Pace P250 ('21-'26).
|-
| F || 250 PS/247 hp || 8-spd. Auto. || X || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,&lt;br /&gt; 16 valve||Direct Injection. Dual VVT. CVVL (Intake VVL).&lt;br&gt; [[w:Ingenium engine family|JLR Ingenium AJ20P4/AJ200P engine]].&lt;br&gt; Jaguar XE 25t ('18-'20), XF 25t ('18-'20), XF P250 ('21-'24),&lt;br&gt; E-Pace P250 ('18-'24), F-Pace 25t ('18-'20).
|-
| G || 300 PS/296 hp || 8-spd. Auto. || X || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,&lt;br /&gt; 16 valve||Direct Injection. Dual VVT. CVVL (Intake VVL).&lt;br&gt; [[w:Ingenium engine family|JLR Ingenium AJ20P4/AJ200P engine]].&lt;br&gt; Jaguar XE 30t ('18-'20), XF 30t ('18-'20), XF P300 ('21-'24),&lt;br&gt; F-Type ('18), F-Type P300 ('19-'21), E-Pace P300 R-Dynamic ('18-'20),&lt;br&gt; E-Pace 300 Sport ('21-'22), F-Pace 30t ('18-'20). 
|}

====Motor Type for Electric Vehicles 2019-====

{| class=&quot;wikitable&quot;
|+Position 7-8
|-
! VIN Pos. 7 !! Power Level !! Transmission !! VIN Pos. 8 !! # of Motors !! Battery Size !! Battery Type !! Fuel !! Drive Wheels !! Notes/Applications
|-
| S || 400 PS/394 hp || 1-spd. Auto. || 1 || 2 || 90 Kwh || Lithium-ion || Electricity || All || Jaguar I-Pace EV400 ('19-'24).
|-
| T || 1029 PS/1015 hp || 1-spd. Auto. || 1 || 3 &lt;br&gt; (1 Front,&lt;br&gt; 2 Rear) || 118 Kwh || Lithium-ion || Electricity || All || Jaguar Type 01 ('28-).
|}

===Check Digit/Gearbox (Position 9)===
* USA /Canada [[Vehicle Identification Numbers (VIN codes)/Check digit|Check digit]]

===Model Year Code (Position 10)===
''See: [[Vehicle Identification Numbers (VIN codes)/Model year]]''

===Plant Codes (Position 11) 2016-===
* A - Solihull, West Midlands, England, UK (XE '17, F-Pace '17-'26, Type 01 '28-)
* C - Castle Bromwich, West Midlands, England, UK (XE '17-'20, XF '16-'24, F-Type '18-'24)
* S - Oxford Road plant, Ryton, West Midlands, England, UK (JLR SVO plant) (XE SV Project 8 '19)
* 1 - Graz, Austria (Magna Steyr plant) (E-Pace '18-'24, I-Pace EV '19-'24)

===Model (Position 12)===
* 9 - XE ('17) [Solihull plant]
* P - XE ('17-'20) [Castle Bromwich plant]
* Y - XF ('16-'24)
* K - F-Type ('18-'24)
* Z - E-Pace ('18-'20)
* 0 - E-Pace ('20-'24)
* F - I-Pace EV ('19-'20)
* 6 - I-Pace EV ('20-'24)

'''Positions 13–17, Serial Number'''

==General Template for Jaguar's VIN format (All models: 2000-2015 plus F-Type '16-'17, XJ '16-'19)==

===Jaguar WMIs (2000-) (Position 1-3)===

* SAJ - Jaguar passenger car (UK)
* SAD - Jaguar SUV (UK &amp; Europe)

===Regional Spec/Restraint System (Position 4):===
* J = Manual seat belts, Dual front airbags (US: XK8 '00)
* B = Manual seat belts, Dual front airbags (Canada: XK8 '00)
* D = Manual seat belts, Depowered Dual front airbags, &amp; Front Side Airbags (US: S-Type '00-'02, XJ8/XJR '00-'03, XK8/XKR '01-'06, XK/XKR Early '07)
* F = Manual seat belts, Depowered Dual front airbags, &amp; Front Side Airbags (Canada: S-Type '00-'02, XJ8/XJR '00-'03, XK8/XKR '01-'06, XK/XKR Early '07)
* E = Manual seat belts, Depowered Dual front airbags w/occupant position sensing, &amp; Front Side Airbags &amp; Side Curtain Airbags (US: X-Type '02-'04, S-Type '03-'04, XJ8/XJR Early '04)
* G = Manual seat belts, Depowered Dual front airbags w/occupant position sensing, &amp; Front Side Airbags &amp; Side Curtain Airbags (Canada: X-Type '02-'04,&lt;br&gt; S-Type '03-'04, XJ8/XJR Early '04)
* W = Manual seat belts, Depowered Dual front airbags w/occupant position (driver) and weight (fr. psgr.) sensing, &amp; Front Side Airbags &amp; Side Curtain Airbags &lt;br&gt; (US: X-Type '05-'08, S-Type '05-'08, XF '09-'15,  XJ8/XJR '04-'09, XJ '10-)
* X = Manual seat belts, Depowered Dual front airbags w/occupant position (driver) and weight (fr. psgr.) sensing, &amp; Front Side Airbags &amp; Side Curtain Airbags (Canada: X-Type '05-'08, S-Type '05-'08, XF '09-'15, XJ8/XJR '04-'09, XJ '10-)
* W = Manual seat belts, Depowered Dual front airbags w/occupant position (driver) and weight (fr. psgr.) sensing, &amp; Front Side Head/Thorax Airbags &lt;br&gt; (US: XK/XKR '07-'15, F-Type '14-)
* X = Manual seat belts, Depowered Dual front airbags w/occupant position (driver) and weight (fr. psgr.) sensing, &amp; Front Side Head/Thorax Airbags &lt;br&gt; (Canada: XK/XKR '07-'15, F-Type '14-)

===Transmission &amp; Steering Location (Position 5 - '00-'12):===
* A = Automatic / LHD
* B = Manual / LHD (X-Type '02-'05, S-Type 3.0 '03-'04)

===Transmission &amp; Drive Wheels (Position 5 - '13-):===
* A = Automatic / Rwd (XF '13-'15, XJ '13-'19, XK '13-'15, F-Type '14-'17)
* B = Manual / Rwd (F-Type '16-'17)
* J = Automatic / Awd (XF Awd '13-'15, XJ Awd '13-'19, F-Type Awd '16-'17)

===Model Line (Position 6-7)===

{| class=&quot;wikitable&quot;
|+Position 6-7
!VIN code
!Description
|-
|51
|[[w:Jaguar X-Type|Jaguar X-Type sedan - High Series]] ('02-'08)
|-
|52
|[[w:Jaguar X-Type|Jaguar X-Type sedan - Entry Series]] ('03-'04)
|-
|53
|[[w:Jaguar X-Type|Jaguar X-Type sedan w/Sport Package]] ('02-'03)
|-
|54
|[[w:Jaguar X-Type|Jaguar X-Type Sportwagon]] ('05-'08)
|-
|01
|[[w:Jaguar S-Type (1999)|Jaguar S-Type]] ('00-'08)
|-
|03
|[[w:Jaguar S-Type (1999)|Jaguar S-Type Sport]] [3.0, 4.0] ('02)
|-
|03
|[[w:Jaguar S-Type (1999)|Jaguar S-Type Sport]] [3.0, 4.2] ('03)
|-
|03
|[[w:Jaguar S-Type (1999)|Jaguar S-Type R]] ('03-'08)
|-
|05
|[[w:Jaguar XF (X250)|Jaguar XF Luxury]] ('09)
|-
|06
|[[w:Jaguar XF (X250)|Jaguar XF Premium Luxury]] ('09)
|-
|07
|[[w:Jaguar XF (X250)|Jaguar XF Supercharged]] ('09)
|-
|0E
|[[w:Jaguar XF (X250)|Jaguar XF]] ('13-'14)
|-
|0F
|[[w:Jaguar XF (X250)|Jaguar XF]] ('10-'12)
|-
|0F
|[[w:Jaguar XF (X250)|Jaguar XF 2.0T Premium]] [8th pos. of VIN is S] ('15)
|-
|0F
|[[w:Jaguar XF (X250)|Jaguar XF 3.0 Sport Rwd or 3.0 Portfolio Rwd]] [8th pos. of VIN is 7] ('15)
|-
|0F
|[[w:Jaguar XF (X250)|Jaguar XF 3.0 Sport Awd or 3.0 Portfolio Awd]] [8th pos. of VIN is F] ('15)
|-
|0G
|[[w:Jaguar XF (X250)|Jaguar XF Premium]] ('10-'11)
|-
|0H
|[[w:Jaguar XF (X250)|Jaguar XF Portfolio]] [8th pos. of VIN is B] ('12)
|-
|0H
|[[w:Jaguar XF (X250)|Jaguar XF Supercharged]] [8th pos. of VIN is E: '10-'13 or P: '13-'15]
|-
|0J
|[[w:Jaguar XF (X250)|Jaguar XFR]] ('10-'15)
|-
|0K
|[[w:Jaguar XF (X250)|Jaguar XFR-S]] ('13-'15)
|-
|8J
|[[w:Jaguar XF (X250)|Jaguar XFR w/Speed Pack]] ('13-'15)
|-
|12
|[[w:Jaguar XJ (X308)#Sport|Jaguar XJ Sport]] ('02-'03)
|-
|14
|[[w:Jaguar XJ (X308)|Jaguar XJ8]] ('00-'03)
|-
|15
|[[w:Jaguar XJ (X308)#XJR|Jaguar XJR]] ('00-'03)
|-
|23
|[[w:Jaguar XJ (X308)|Jaguar XJ8L]] (LWB) ('00-'01)
|-
|24
|[[w:Jaguar XJ (X308)#Daimler/Vanden Plas|Jaguar XJ8 Vanden Plas]] (LWB) ('00-'03)
|-
|25
|[[w:Jaguar XJ (X308)#Daimler/Vanden Plas|Jaguar XJ8 Vanden Plas Supercharged]] (LWB) ('00-'01)
|-
|25
|[[w:Jaguar XJ (X308)#Daimler/Vanden Plas|Jaguar XJ Super V8]] (LWB) ('02-'03)
|-
|71
|[[w:Jaguar XJ (X350)|Jaguar XJ8]] ('04-'09)
|-
|73
|[[w:Jaguar XJ (X350)|Jaguar XJR]] ('04-'09)
|-
|74
|[[w:Jaguar XJ (X350)|Jaguar XJ8 Vanden Plas]] (SWB) ('04)
|-
|79
|[[w:Jaguar XJ (X350)|Jaguar XJ8L]] (LWB) ('05-'09)
|-
|82
|[[w:Jaguar XJ (X350)|Jaguar XJ8 Vanden Plas]] (LWB) ('05-'09)
|-
|82
|[[w:Jaguar XJ (X350)|Jaguar XJ Super V8]] (LWB, 5-psgr.) ('05-'09)
|-
|86
|[[w:Jaguar XJ (X350)|Jaguar XJ Super V8 Portfolio]] (LWB, 4-psgr.) ('06)
|-
|94
|[[w:Jaguar XJ (X350)|Jaguar XJ Super V8 Portfolio]] (LWB, 5-psgr.) ('09)
|-
|1C
|[[w:Jaguar XJ (X351)|Jaguar XJ]] ('10-'15)
|-
|1C
|[[w:Jaguar XJ (X351)|Jaguar XJ R-Sport]] [8th pos. of VIN is 7 (Rwd) or D (Awd)] ('16-'19)
|-
|1C
|[[w:Jaguar XJ (X351)|Jaguar XJ Supercharged]] [8th pos. of VIN is E] ('16-'19)
|-
|1E
|[[w:Jaguar XJ (X351)|Jaguar XJR]] ('14-'17)
|-
|1G
|[[w:Jaguar XJ (X351)|Jaguar XJ Supercharged]] [8th pos. of VIN is E: '10-'13 or T: '13-'15]
|-
|1J
|[[w:Jaguar XJ (X351)|Jaguar XJ Supersport]] ('11-'12)
|-
|2E
|[[w:Jaguar XJ (X351)|Jaguar XJR LWB]] ('14-'17), XJR575 LWB ('18-'19)
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL]] [8th pos. of VIN is B] ('10-'11)
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL Portfolio Rwd]] [8th pos. of VIN is B: '12-'13 or 1: '13]
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL Portfolio Rwd]] [8th pos. of VIN is Z: '14-'15)
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL Portfolio Rwd]] [8th pos. of VIN is 7: '16-'19), XJ50 3.0 Rwd (LWB) '19
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL Portfolio Awd]] [8th pos. of VIN is D] ('13-'19), XJ50 3.0 Awd (LWB) '19
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL Supercharged]] [8th pos. of VIN is E: '10-'13, '16-'19 or T: '13-'15], XJ50 5.0 Rwd (LWB) '19, XJ Collection (LWB) '19
|-
|2J
|[[w:Jaguar XJ (X351)|Jaguar XJL Supersport]] ('11-'13)
|-
|2K
|[[w:Jaguar XJ (X351)|Jaguar XJL Ultimate]] ('13)
|-
|3F
|[[w:Jaguar XJ (X351)|Jaguar XJ Supersport w/Speed Pack]] ('12-'13)
|-
|3G
|[[w:Jaguar XJ (X351)|Jaguar XJL Supersport w/Speed Pack]] ('12-'13)
|-
|3H
|[[w:Jaguar XJ (X351)|Jaguar XJ Supercharged w/Sport &amp; Speed Pack]] ('12-'15)
|-
|3K
|[[w:Jaguar XJ (X351)|Jaguar XJL Supercharged w/Sport &amp; Speed Pack]] ('12-'15)
|-
|41
|[[w:Jaguar XK (X100)|Jaguar XK8/XKR coupe]] ('00-'06)
|-
|42
|[[w:Jaguar XK (X100)|Jaguar XK8/XKR convertible]] ('00-'06)
|-
|43
|[[w:Jaguar XK (X150)|Jaguar XK/XKR coupe]] ('07-'09)
|-
|44
|[[w:Jaguar XK (X150)|Jaguar XK/XKR convertible]] ('07-'09)
|-
|45
|[[w:Jaguar XK (X150)|Jaguar XKR Portfolio Edition coupe]] ('09)
|-
|46
|[[w:Jaguar XK (X150)|Jaguar XKR Portfolio Edition convertible]] ('09)
|-
|4D
|[[w:Jaguar XK (X150)|Jaguar XK Touring coupe]] [8th pos. of VIN is B] ('13-'14)
|-
|4E
|[[w:Jaguar XK (X150)|Jaguar XK Touring convertible]] [8th pos. of VIN is B] ('13-'14)
|-
|4D
|[[w:Jaguar XK (X150)|Jaguar XKR coupe]] [8th pos. of VIN is C] ('10-'15)
|-
|4E
|[[w:Jaguar XK (X150)|Jaguar XKR convertible]] [8th pos. of VIN is C] ('10-'15)
|-
|4F
|[[w:Jaguar XK (X150)|Jaguar XK coupe]] (most Portfolio Edition features are std.) [8th pos. of VIN is B] ('10-'15)
|-
|4F
|[[w:Jaguar XK (X150)|Jaguar XKR175 coupe]] [8th pos. of VIN is C] ('11)
|-
|4F
|[[w:Jaguar XK (X150)|Jaguar XKR coupe w/Dynamic Pack]] [8th pos. of VIN is C] ('13-'15), XK Final Fifty Edition coupe ('15)
|-
|4G
|[[w:Jaguar XK (X150)|Jaguar XK convertible]] (most Portfolio Edition features are std.) [8th pos. of VIN is B] ('10-'15)
|-
|4G
|[[w:Jaguar XK (X150)|Jaguar XKR convertible w/Dynamic Pack]] [8th pos. of VIN is C] ('13-'15), XK Final Fifty Edition convertible ('15)
|-
|4H
|[[w:Jaguar XK (X150)|Jaguar XKR-S coupe]] ('12-'15), XKR-S GT coupe ('14)
|-
|4J
|[[w:Jaguar XK (X150)|Jaguar XKR-S convertible]] ('12-'15)
|-
|6A
|[[w:Jaguar F-Type)|Jaguar F-Type coupe]] ('15-'17), F-Type Premium coupe '17
|-
|6B
|[[w:Jaguar F-Type)|Jaguar F-Type S coupe]] ('15-'17), F-Type S British Design Edition coupe '17
|-
|6D
|[[w:Jaguar F-Type)|Jaguar F-Type R coupe]] ('15-'17)
|-
|6E
|[[w:Jaguar F-Type)|Jaguar F-Type convertible]] ('14-'17), F-Type Premium convertible '17
|-
|6F
|[[w:Jaguar F-Type)|Jaguar F-Type S convertible]] ('14-'17), F-Type S British Design Edition convertible '17
|-
|6G
|[[w:Jaguar F-Type)|Jaguar F-Type V8 S convertible]] ('14-'15)
|-
|6H
|[[w:Jaguar F-Type)|Jaguar F-Type R convertible]] ('16-'17)
|-
|6J
|[[w:Jaguar F-Type)|Jaguar F-Type SVR coupe]] ('17)
|-
|6K
|[[w:Jaguar F-Type)|Jaguar F-Type SVR convertible]] ('17)
|-
|7A
|[[w:Jaguar F-Type#Project 7)|Jaguar F-Type Project 7 convertible]] ('16)
|}

===Engine/Emissions Control System (Position 8)===

{| class=&quot;wikitable&quot;
|+Position 8
! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications
|-
| A || 3.0L || 60° V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. ULEV. Variable intake valve timing. [[w:Jaguar AJ-V6 engine#AJ30|Jaguar AJ-V6 - AJ30 V6 engine]].&lt;br&gt; Jaguar X-Type 3.0 (Mid '05-'08), S-Type 3.0 ('06-'08). 
|-
| A || 4.2L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. ULEV. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.2 L|Jaguar AJ-V8 - AJ34 V8 engine]]. Jaguar XF ('10).
|-
| A || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 550 PS/542 hp. Jaguar XKR-S ('12-'15), XKR-S GT ('14), F-Type R coupe ('15).
|-
| B || 4.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. [[w:Jaguar AJ-V8 engine#Supercharged|Jaguar AJ-V8 - AJ27S V8 engine]].&lt;br&gt; Jaguar XJR ('00-'03), Vanden Plas Supercharged ('00-'01), Super V8 ('02-'03), XKR ('00-'02).
|-
| B || 4.2L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. [[w:Jaguar AJ-V8 engine#Supercharged_2|Jaguar AJ-V8 - AJ33S V8 engine]]. Jaguar XJR ('04-'05), Super V8 ('05), XKR ('03-'06).
|-
| B || 4.2L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. ULEV. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.2 L|Jaguar AJ-V8 - AJ34 V8 engine]].&lt;br&gt; Jaguar S-Type ('06-'08), XF ('09), XJ8/Vanden Plas ('06-'09), XK ('07-'09).
|-
| B || 5.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. Variable intake valve lift. Variable intake.&lt;br&gt; [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; Jaguar XF ('10-'12), XJ ('11-'12), XJL ('11), XJL Portfolio Rwd ('12-'13), XK ('10-'15), XK Touring ('13-'14).
|-
| C || 3.0L || 60° V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. Variable intake valve timing. [[w:Jaguar AJ-V6 engine#AJ30|Jaguar AJ-V6 - AJ30 V6 engine]].&lt;br&gt; Jaguar S-Type 3.0 ('00-'01), X-Type 3.0 ('02-Mid '05). 
|-
| C || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ27 V8 engine]].&lt;br&gt; Jaguar XJ8/Vanden Plas ('00-'03), XJ Sport ('02-'03), XK8 ('00-'02).
|-
| C || 4.2L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.2 L|Jaguar AJ-V8 - AJ33 V8 engine]]. Jaguar XJ8 ('04-'05), XK8 ('03-'06).
|-
| C || 4.2L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. ULEV. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#Supercharged_2|Jaguar AJ-V8 - AJ34S V8 engine]].&lt;br&gt; Jaguar S-Type R ('06-'08), XF Supercharged ('09), XJR ('06-'09), Super V8 ('06-'09), XKR ('07-'09).
|-
| C || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 510 PS/503 hp. Jaguar XFR ('10-'13), XJ/XJL Supersport ('11-'13), XKR ('10-'15).
|-
| C || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 380 PS/375 hp. Jaguar F-Type S ('14-'15), F-Type S w/man. trans. ('16-'17).
|-
| D || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ28 V8 engine]]. Jaguar S-Type 4.0 ('00-'01).
|-
| D || 2.5L || 60° V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. Variable intake valve timing. [[w:Jaguar AJ-V6 engine#AJ25|Jaguar AJ-V6 - AJ25 V6 engine]]. Jaguar X-Type 2.5 ('02-'05).
|-
| D || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XJ Awd, XJL Portfolio Awd ('13-'15).
|-
| D || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XJ R-Sport Awd, XJL Portfolio Awd ('16-'19), XJ50 3.0 Awd ('19).
|-
| E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 470 PS/464 hp.&lt;br&gt; Jaguar XF Supercharged ('10-'13), XJ/XJL Supercharged ('11-'13, '16-'19), XJ50 5.0 Rwd ('19), XJ Collection ('19).
|-
| F || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 3.0 Awd ('13-'14).
|-
| F || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 3.0 Awd ('15).
|-
| H || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,&lt;br /&gt; 32 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]]. 510 PS/503 hp. Jaguar XFR ('13-'15).
|-
| K || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 550 PS/542 hp. Jaguar XJR/XJR LWB ('14-'17).
|-
| K || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 575 PS/567 hp. Jaguar XJR575 LWB ('18-'19).
|-
| L || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 495 PS/488 hp. Jaguar F-Type V8 S convertible ('14-'15).
|-
| L || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 550 PS/542 hp. Jaguar F-Type R  ('16-'17).
|-
| N || 3.0L || 60° V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. Variable intake valve timing. [[w:Jaguar AJ-V6 engine#AJ30|Jaguar AJ-V6 - AJ30 V6 engine]]. Jaguar S-Type 3.0 ('01-'02).
|-
| P || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ28 V8 engine]]. Jaguar S-Type 4.0 ('01-'02).
|-
| P || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,&lt;br /&gt; 32 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]]. 470 PS/464 hp. Jaguar XF Supercharged ('13-'15).
|-
| S || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,&lt;br /&gt; 16 valve||Direct Injection. Dual VVT. [[w:Ford EcoBoost engine#2.0 L (2010–2018)|Ford EcoBoost engine (Mazda L engine-based)]].&lt;br&gt; Jaguar XF 2.0T ('13-'14), XF 2.0T Premium ('15).
|-
| T || 3.0L || 60° V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. Variable intake valve timing. [[w:Jaguar AJ-V6 engine#AJ30|Jaguar AJ-V6 - AJ30 V6 engine]]. Jaguar S-Type 3.0 ('03-'05).
|-
| T || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,&lt;br /&gt; 32 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]]. 470 PS/464 hp. Jaguar XJ/XJL Supercharged ('13-'15).
|-
| T || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar F-Type w/auto. trans. ('15-'17), F-Type Premium w/auto. trans. ('17).
|-
| U || 4.2L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.2 L|Jaguar AJ-V8 - AJ33 V8 engine]]. Jaguar S-Type 4.2 ('03-'05).
|-
| U || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 380 PS/375 hp. Jaguar F-Type S ('15), F-Type S Rwd w/auto. trans. ('16-'17).
|-
| V || 4.2L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. [[w:Jaguar AJ-V8 engine#Supercharged_2|Jaguar AJ-V8 - AJ33S V8 engine]]. Jaguar S-Type R ('03-'05).
|-
| V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 380 PS/375 hp. Jaguar F-Type S Awd w/auto. trans. ('16-'17).
|-
| X || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,&lt;br /&gt; 24 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 3.0 Rwd ('14).
|-
| Z || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 550 PS/542 hp. Jaguar XFR-S ('13-'15).
|-
| Z || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,&lt;br /&gt; 24 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XJ Rwd, XJL Portfolio Rwd ('14-'15).
|-
| 1 || 5.0L || V8 || Gas/E85 ||DOHC,&lt;br /&gt; 32 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. Variable intake valve lift. Variable intake. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]]. Jaguar XJL Portfolio Rwd ('13).
|-
| 6 || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar F-Type w/man. trans. ('16-'17), F-Type Premium w/man. trans. ('17).
|-
| 7 || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 3.0 Rwd ('13), XJ Rwd ('13), F-Type ('14-'15).
|-
| 7 || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 3.0 Rwd ('15), XJ R-Sport Rwd ('16-'19), XJL Portfolio Rwd ('16-'19), XJ50 3.0 Rwd ('19).
|-
| 8 || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 575 PS/567 hp. Jaguar F-Type Project 7 ('16), F-Type SVR ('17).
|}

===Check Digit/Gearbox (Position 9)===
* USA /Canada [[Vehicle Identification Numbers (VIN codes)/Check digit|Check digit]]

===Model Year Code (Position 10)===
''See: [[Vehicle Identification Numbers (VIN codes)/Model year]]''

===Plant Code/Model Line/Engine (Position 11) 2000-2019===
* X - Halewood, Merseyside, England, UK - X-Type 2.5 ('02-'05)
* W - Halewood, Merseyside, England, UK - X-Type 3.0 ('02-'08)
* F - Castle Bromwich, West Midlands, England, UK - S-Type 3.0 ('00-'08)
* G - Castle Bromwich, West Midlands, England, UK - S-Type 4.0 ('00-'02)
* H - Castle Bromwich, West Midlands, England, UK - S-Type 4.2 ('03-'08)
* 1 - Castle Bromwich, West Midlands, England, UK - S-Type R (4.2 supercharged) ('03-'08)
* H - Castle Bromwich, West Midlands, England, UK - XF 4.2 ('09-'10)
* 1 - Castle Bromwich, West Midlands, England, UK - XF Supercharged (4.2 supercharged) ('09)
* L - Castle Bromwich, West Midlands, England, UK - XF 5.0 ('10-'12)
* M - Castle Bromwich, West Midlands, England, UK - XF Supercharged, XFR (5.0 supercharged) ('10-'15), XFR-S (5.0 supercharged) ('13-'15)
* P - Castle Bromwich, West Midlands, England, UK - XF 2.0T ('13-'15)
* 8 - Castle Bromwich, West Midlands, England, UK - XF 3.0 supercharged ('13-'15)
* L - Browns Lane plant, Coventry, West Midlands, England, UK - XJ8 (4.0) ('00-'03), XJ8L (4.0) ('00-'01), XJ8 Vanden Plas (4.0) ('00-'03), XJ Sport (4.0) ('02-'03)
* M - Browns Lane plant, Coventry, West Midlands, England, UK - XJ8 Vanden Plas Supercharged (4.0 supercharged) ('00-'01),&lt;br&gt; Super V8 (4.0 supercharged) ('02-'03), XJR (4.0 supercharged) ('00-'03)
* S - Browns Lane plant, Coventry, West Midlands, England, UK - XJ8 (4.2) ('04-'06), XJ8L (4.2) ('05-'06), XJ8 Vanden Plas (4.0) ('04-'06)
* T - Browns Lane plant, Coventry, West Midlands, England, UK - Super V8 (4.2 supercharged) ('05-'06), Super V8 Portfolio (4.2 supercharged) ('06),&lt;br&gt; XJR (4.2 supercharged) ('04-'06)
* S - Castle Bromwich, West Midlands, England, UK - XJ8 (4.2) ('07-'09), XJ8L (4.2) ('07-'09), XJ8 Vanden Plas (4.0) ('07-'09)
* T - Castle Bromwich, West Midlands, England, UK - Super V8 (4.2 supercharged) ('07-'09), Super V8 Portfolio (4.2 supercharged) ('09),&lt;br&gt; XJR (4.2 supercharged) ('07-'09)
* L - Castle Bromwich, West Midlands, England, UK - XJ (5.0) ('10-'12), XJL (5.0) ('10-'11), XJL Portfolio (5.0) ('12-'13)
* M - Castle Bromwich, West Midlands, England, UK - XJ/XJL Supercharged (5.0 supercharged) ('10-'19), XJ/XJL Supersport (5.0 supercharged) ('11-'13),&lt;br&gt; XJL Ultimate (5.0 supercharged) ('13), XJR SWB/LWB (5.0 supercharged) ('14-'17), XJR575 LWB (5.0 supercharged) ('18-'19), XJ50 LWB (5.0 supercharged) ('19), XJ Collection Sp. Ed. LWB (5.0 supercharged) ('19)
* 8 - Castle Bromwich, West Midlands, England, UK - XJ base (3.0 supercharged) ('13-'15), XJ R-Sport (3.0 supercharged) ('16-'19),&lt;br&gt; XJL Portfolio AWD (3.0 supercharged) ('13-'19), XJL Portfolio RWD (3.0 supercharged) ('14-'19), XJ50 LWB (3.0 supercharged) ('19)
* N - Browns Lane plant, Coventry, West Midlands, England, UK - XK8 (4.0) ('00-'02)
* P - Browns Lane plant, Coventry, West Midlands, England, UK - XKR (4.0 supercharged) ('00-'02)
* 2 - Browns Lane plant, Coventry, West Midlands, England, UK - XK8 (4.2) ('03-'06)
* 3 - Browns Lane plant, Coventry, West Midlands, England, UK - XKR (4.2 supercharged) ('03-'06)
* 5 - Castle Bromwich, West Midlands, England, UK - XK (4.2) ('07-'09)
* 9 - Castle Bromwich, West Midlands, England, UK - XKR (4.2 supercharged) ('07-'09)
* L - Castle Bromwich, West Midlands, England, UK - XK (5.0) ('10-'15)
* M - Castle Bromwich, West Midlands, England, UK - XKR (5.0 supercharged) ('10-'15), XKR-S (5.0 supercharged) ('12-'15), XKR-S GT (5.0 supercharged) ('14)
* 8 - Castle Bromwich, West Midlands, England, UK - F-Type Base, S (3.0 supercharged) ('14-'17), F-Type Premium (3.0 supercharged) ('17)
* M - Castle Bromwich, West Midlands, England, UK - F-Type V8S (5.0 supercharged) ('14-'15), F-Type R (5.0 supercharged) ('15-'17),&lt;br&gt; F-Type Project 7 (5.0 supercharged) ('16), F-Type SVR (5.0 supercharged) ('17)

===Model (Position 12)===
* C - X-Type ('02-'03)
* D - X-Type ('03-'04)
* E - X-Type ('04-'06)
* J - X-Type ('06-'08)
* L - S-Type ('00-'01)
* M - S-Type ('01-'04)
* N - S-Type ('04-'08)
* R - XF ('09-'11)
* S - XF ('11-'13)
* U - XF ('13-'15)
* F - XJ ('00-'03)
* G - XJ ('04-'06) [Browns Lane plant]
* H - XJ ('06-'09) [Castle Bromwich plant]
* V - XJ ('10-'16)
* W - XJ ('16-'19)
* A - XK ('00-'06)
* B - XK ('07-'15)
* K - F-Type ('14-'17)

'''Positions 13–17, Serial Number'''

==General Template for Jaguar's VIN format (1981 - 1999)==

===Jaguar WMIs (1981-1999) (Position 1-3)===
* SAJ - Jaguar passenger car

===Model Line (Position 4)===

{| class=&quot;wikitable&quot;
|+Position 4
!VIN code
!Description
|-
|A
|[[w:Jaguar XJ#Series 3 (1979–1992)|Jaguar XJ6]] ('81-'87), XJ6 Vanden Plas ('82-'87)
|-
|B
|[[w:Jaguar XJ#Series 3 (1979–1992)|Jaguar XJ12]] (Canada only: '81-'88)
|-
|D
|[[w:Jaguar XJ#Series 3 (1979–1992)|Jaguar XJ12]] (Canada only: '89-'92)
|-
|H
|[[w:Jaguar XJ (XJ40)|Jaguar XJ6]] ('88-'89, '93-'94)
|-
|F
|[[w:Jaguar XJ (XJ40)|Jaguar XJ6]] ('90-'92)
|-
|H
|[[w:Jaguar XJ (XJ40)|Jaguar XJ6 Sovereign]] ('90-'92)
|-
|K
|[[w:Jaguar XJ (XJ40)#Daimler/Vanden Plas|Jaguar XJ6 Vanden Plas]] ('88-'94)
|-
|M
|[[w:Jaguar XJ (XJ40)#Majestic (1989–1992 – SWB; 1993–1994 – LWB)|Jaguar XJ6 Vanden Plas Majestic]] ('89-'90, '92)
|-
|M
|[[w:Jaguar XJ (XJ40)#XJ12 and Daimler Double Six (XJ81)|Jaguar XJ12]] ('94)
|-
|H
|[[w:Jaguar XJ (X300)|Jaguar XJ6]] ('95-'97)
|-
|H
|[[w:Jaguar XJ (X300)|Jaguar XJ6L]] LWB [X330] ('97)
|-
|K
|[[w:Jaguar XJ (X300)#Daimler/Jaguar Vanden Plas|Jaguar XJ6 Vanden Plas]] SWB ('95)
|-
|K
|[[w:Jaguar XJ (X300)#Daimler/Jaguar Vanden Plas|Jaguar XJ6 Vanden Plas]] LWB [X330] ('96-'97)
|-
|M
|[[w:Jaguar XJ (X300)#XJ12 (X305)|Jaguar XJ12]] SWB ('95)
|-
|M
|[[w:Jaguar XJ (X300)#XJ12 (X305)|Jaguar XJ12]] LWB [X330] ('96)
|-
|P
|[[w:Jaguar XJ (X300)#XJR (X306)|Jaguar XJR]] ('95-'97)
|-
|H
|[[w:Jaguar XJ (X308)|Jaguar XJ8]] ('98-'99)
|-
|H
|[[w:Jaguar XJ (X308)|Jaguar XJ8L]] LWB ('98-'99)
|-
|K
|[[w:Jaguar XJ (X308)#Daimler/Vanden Plas|Jaguar XJ8 Vanden Plas]] LWB ('98-'99)
|-
|P
|[[w:Jaguar XJ (X308)#XJR|Jaguar XJR]] ('98-'99)
|-
|N
|[[w:Jaguar XJS|Jaguar XJ-S]] ('82-'91), XJ-SC ('86-'88), XJS ('92-'96)
|-
|T
|[[w:Jaguar XJS|Jaguar XJ-S]] Rouge Collection ('89-'90), Classic Collection ('90-'91)
|-
|S
|[[w:Jaguar XJS#XJR-S|Jaguar XJR-S]] ('93)
|-
|G
|[[w:Jaguar XK (X100)|Jaguar XK8]] ('97-'99)
|}

===Class (Regional Spec)/Restraint System (Position 5):===
* V = N. American-spec (Manual seat belts)
* L = Canadian-spec (Manual seat belts)

* Y = XJ6 Vanden Plas [Series III] ('82-'87) (Manual seat belts)

* A = Motorized Shoulder Belts (XJ-S coupe '88-'89, XJ-SC '88)
* Y = Motorized Shoulder Belts (XJ-S coupe '89, XJ sedan '89-'92)
* W = Manual seat belts, Driver-side airbag (US: XJ-S '90-'93, XJ6 '93, XJ12 Early '94)
* X = Manual seat belts, Dual front airbags (US: XJS '94-'96, XJ6 '94-'97, XJ12 '94-'96, XJR '95-'97, XK8 '97-'99)
* X = Manual seat belts, Dual front airbags, &amp; Front Side Airbags (US: XJ8/XJR '98-'99)
* D = Manual seat belts, Depowered Dual front airbags, &amp; Front Side Airbags (US: XJ8/XJR '99)
* M = Manual seat belts, Driver-side airbag (Canada)
* N = Manual seat belts, Dual front airbags (Canada)
* F = Manual seat belts, Depowered Dual front airbags, &amp; Front Side Airbags (Canada: XJ8/XJR '99)

===Body Style (Position 6):===
* 1 = 4-door sedan (XJ-series sedan '81-'99)
* 2 = 2-door convertible w/2+2 seating (XJS convertible '94-'96, XK8 convertible '97-'99)
* 3 = 2-door Cabriolet (XJ-SC '86-'88)
* 4 = 2-door convertible w/2-psgr. seating (factory-built XJS convertible '89-'94, XJR-S convertible '93)
* 5 = 2-door coupe (XJS coupe '82-'96, XJR-S coupe '93, XK8 coupe '97-'99)
* 5 = 2-door coupe (Hess &amp; Eisenhardt-built XJS convertible '87-'88) [coupe conversion]

===Engine Type (Position 7):===
{| class=&quot;wikitable&quot;
|+Position 7
|-
! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications
|-
| 1 || 4.0L || I6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. [[w:Jaguar AJ6 engine#AJ16S|Jaguar AJ16S I6]]. Jaguar XJR ('95-'97).
|-
| 2 || 4.2L || I6 || Gas ||DOHC,&lt;br /&gt; 12 valve||CA &amp; Canada-spec. MPI. [[w:Jaguar XK engine|Jaguar XK I6]]. Jaguar XJ6 ('81-'82).
|-
| 2 || 4.0L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. Dual-canister evaporative emissions system. [[w:Jaguar AJ6 engine#AJ16|Jaguar AJ16 I6]]. Jaguar XJ6 ('96-'97).
|-
| 2 || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Variable intake valve timing. Dual-canister evaporative emissions system. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ26 V8 engine]].&lt;br&gt; Jaguar XJ8 ('98), XK8 ('98).
|-
| 3 || 4.2L || I6 || Gas ||DOHC,&lt;br /&gt; 12 valve||N. America-spec. MPI. [[w:Jaguar XK engine|Jaguar XK I6]]. Jaguar XJ6 ('81-'87).
|-
| 3 || 6.0L || 60° V12 || Gas ||SOHC,&lt;br /&gt; 24 valve||MPI. [[w:Jaguar V12 engine|Jaguar V12]] modified by [[w:Tom Walkinshaw Racing|JaguarSport]]. Jaguar XJR-S ('93).
|-
| 3 || 6.0L || 60° V12 || Gas ||SOHC,&lt;br /&gt; 24 valve||MPI. [[w:Jaguar V12 engine|Jaguar V12]]. Jaguar XJS ('94-'95), XJ12 ('94-'96).
|-
| 5 || 3.6L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||N. America-spec - Low Compression. MPI. [[w:Jaguar AJ6 engine|Jaguar AJ6 I6]]. Jaguar XJ6 ('88-'89).
|-
| 6 || 3.6L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||N. America-spec - High Compression. MPI. [[w:Jaguar AJ6 engine|Jaguar AJ6 I6]]. Jaguar XJ6 ('88).
|-
| 7 || 4.0L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. [[w:Jaguar AJ6 engine|Jaguar AJ6 I6]]. Jaguar XJ6 ('90-'94), XJS ('93-'94).
|-
| 7 || 4.0L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. [[w:Jaguar AJ6 engine#AJ16|Jaguar AJ16 I6]]. Jaguar XJ6 ('95-'96), XJS ('95-'96).
|-
| 7 || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ26 V8 engine]]. Jaguar XK8 ('97).
|-
| 8 || 5.3L || 60° V12 || Gas ||SOHC,&lt;br /&gt; 24 valve||N. America-spec. MPI. [[w:Jaguar V12 engine|Jaguar V12]]. Jaguar XJ-S ('82-'92), XJ12 (Canada only: '88-'92).
|-
| 8 || 4.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Dual-canister evaporative emissions system. [[w:Jaguar AJ-V8 engine#Supercharged|Jaguar AJ-V8 - AJ26S V8 engine]]. Jaguar XJR ('98-'99).
|-
| 9 || 4.0L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||Canada-spec. MPI. [[w:Jaguar AJ6 engine|Jaguar AJ6 I6]]. Jaguar XJ6 ('90-'93), XJS ('93).
|-
| 0 || 5.3L || 60° V12 || Gas ||SOHC,&lt;br /&gt; 24 valve||Canada-spec. MPI. [[w:Jaguar V12 engine|Jaguar V12]]. Jaguar XJ-S ('82-'87), XJ12 (Canada only: '85-'87).
|-
| 0 || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. Dual-canister evaporative emissions system. Enhanced evaporative emissions control system. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ27 V8 engine]]. Jaguar XJ8 ('99), XK8 ('99).
|}

===Transmission &amp; Steering Location (Position 8):===
* 4 = Automatic / LHD
* 8 = Manual / LHD ('93-'94 XJS 4.0 w/ optional 5-spd. manual)

===Check Digit/Gearbox (Position 9)===
* USA /Canada [[Vehicle Identification Numbers (VIN codes)/Check digit|Check digit]]

===Model Year Code (Position 10)===
''See: [[Vehicle Identification Numbers (VIN codes)/Model year]]''

===Plant Codes (Position 11)===
* C - Browns Lane plant, Coventry, West Midlands, England, UK

===Positions 12–17, Serial Number===
** 100001 and after - XJ-S/XJ-SC/XJS/XJR-S (XJ27)
** 300001 and after - XJ-series sedan Series III
** 500001 and after - XJ-series sedan (XJ40/XJ81)
** 720001 and after - XJ-series sedan (X300/X305/X306/X330)
** 810001 and after - XJ-series sedan (X308)
** 001001 and after - XK8 (X100)</text>
      <sha1>ajeaccl9jggjfeh6yb1smz08qjnq4g1</sha1>
    </revision>
    <revision>
      <id>4676686</id>
      <parentid>4676684</parentid>
      <timestamp>2026-10-18T05:04:18Z</timestamp>
      <contributor>
        <username>JustTheFacts33</username>
        <id>3434282</id>
      </contributor>
      <comment>/* Engine/Emissions Control System (Position 8) 2016-2017: */</comment>
      <origin>4676686</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="42488" sha1="5jbufen6acsarjy6tx9j3l1jvhjeupn" xml:space="preserve">{{Vehicle Identification Numbers (VIN codes)/Warning}}{{clear}}

This VIN number decoding and designation system is used primarily for the North American Market. European and Asian markets use other decoding and designation systems.

==General Template for Jaguar's VIN format (All models: 2016- EXCEPT F-Type '16-'17, XJ '16-'19)==

===Jaguar WMIs (2016-) (Position 1-3)===

* SAJ - Jaguar passenger car (UK)
* SAD - Jaguar SUV (UK &amp; Europe)
* L2C - Chery Jaguar Land Rover (China)

===Model Line (Position 4)===

{| class=&quot;wikitable&quot;
|+Position 4
!VIN code
!Description
|-
|A
|[[w:Jaguar XE|Jaguar XE]] ('17-'20)
|-
|B
|[[w:Jaguar XF (X260)|Jaguar XF]] ('16-'24)
|-
|C
|[[w:Jaguar F-Pace|Jaguar F-Pace]] ('17-'26)
|-
|D
|[[w:Jaguar F-Type|Jaguar F-Type]] ('18-'24)
|-
|E
|[[w:Jaguar Type 01|Jaguar Type 01]] ('28-)
|-
|F
|[[w:Jaguar E-Pace|Jaguar E-Pace]] ('18-'24)
|-
|H
|[[w:Jaguar I-Pace|Jaguar I-Pace EV]] ('19-'24)
|}

===Trim Level/Drive Wheels/Restraint System (Position 5)===

{| class=&quot;wikitable&quot;
|+Position 4
!VIN code
!Trim Level
!Drive Wheels
!Restraint System
|-
|D
|XF Premium '16-
|Rwd
|
|-
|E
|XF Prestige '16-
|Rwd
|
|-
|F
|XF R-Sport '16-
|Rwd
|
|-
|G
|XF S '16-
|Rwd
|
|-
|J
|XF Premium '16-
|Awd
|
|-
|K
|XF Prestige '16-
|Awd
|
|-
|L
|XF R-Sport '16-
|Awd
|
|-
|M
|XF S '16-
|Awd
|
|-
|N
|XF First Edition '16
|Awd
|
|}

===Body Style (Position 6):===
* 1 = Coupe (F-Type coupe)
* 2 = 5-door wagon (XF Sportbrake wagon '18-'20)
* 2 = 5-door (E-Pace, F-Pace, I-Pace EV)
* 4 = 4-door sedan (XE, XF sedan, Type 01)
* 5 = Convertible (F-Type convertible)

===Transmission (Position 7) 2016-2017:===
* B = Automatic (XE '17, XF '16-'17, F-Pace '17)

===Engine/Emissions Control System (Position 8) 2016-2017:===

{| class=&quot;wikitable&quot;
|+Position 8
! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications
|-
| G || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,&lt;br /&gt; 16 valve||Direct Injection. ULEV. Dual VVT. [[w:Ford EcoBoost engine#2.0 L (2010–2018)|Ford EcoBoost engine (Mazda L engine-based)]].&lt;br&gt; Jaguar XE 25t ('17).
|-
| N || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Diesel || DOHC,&lt;br /&gt; 16 valve||Common-rail Direct Injection. Exhaust VVT. [[w:Ingenium engine family|JLR Ingenium AJ20D engine]]. Jaguar XE 20d, XF 20d, F-Pace 20d ('17).
|-
| V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 35t ('16-'17) [If 5th pos. of VIN is NOT G or M]. Jaguar XE 35t ('17).&lt;br&gt; Jaguar F-Pace 35t ('17) [If 5th pos. of VIN is NOT M or P].
|-
| V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 380 PS/375 hp. Jaguar XF S ('16-'17) [If 5th pos. of VIN is G or M].&lt;br&gt; Jaguar F-Pace S ('17) [If 5th pos. of VIN is M or P].
|}

===Engine (Position 7-8) 2018-:===

{| class=&quot;wikitable&quot;
|+Position 7-8
! VIN Pos. 7 !! Power Level !! Transmission !! VIN Pos. 8 !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications
|-
| E || 550 PS/542 hp || 8-spd. Auto. || E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct injection. Dual Continuously VCT (VVT). [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133S engine]]. Jaguar F-Type R ('18-'20), F-Pace SVR ('19-'24).
|-
| E || 450 PS/444 hp || 8-spd. Auto. || E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct injection. Dual Continuously VCT (VVT). [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133S engine]]. Jaguar F-Type P450 ('22-24).
|-
| F || 575 PS/567 hp || 8-spd. Auto. || E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct injection. Dual Continuously VCT (VVT). [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133S engine]]. Jaguar F-Type SVR ('18-'20), F-Type R ('21-'24),&lt;br&gt; F-Pace SVR 575 Edition ('25-'26).
|-
| F || 600 PS/592 hp || 8-spd. Auto. || E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct injection. Dual Continuously VCT (VVT). [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133S engine]]. Jaguar XE SV Project 8 ('19).
|-
| F || 180 PS/178 hp || 8-spd. Auto. || N || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Diesel || DOHC,&lt;br /&gt; 16 valve||Common-rail Direct Injection. Exhaust VVT.&lt;br&gt; [[w:Ingenium engine family|JLR Ingenium AJ20D4/AJ200D engine]].&lt;br&gt; Jaguar XE 20d ('18-'19), XF 20d ('18-'19), F-Pace 20d ('18-'19).
|-
| E || 340 PS/335 hp || 8-spd. Auto. || U || 3.0L || I6 Turbo [[w:Intercooler|IC]] || Gas || DOHC,&lt;br /&gt; 24 valve||48v Mild Hybrid. E-supercharger. Direct Injection. Dual VVT.  CVVL (Intake VVL). [[w:Ingenium engine family|JLR Ingenium AJ20P6/AJ300P engine]].&lt;br&gt; Jaguar F-Pace P340 ('21-'22). 
|-
| F || 400 PS/395 hp || 8-spd. Auto. || U || 3.0L || I6 Turbo [[w:Intercooler|IC]] || Gas || DOHC,&lt;br /&gt; 24 valve||48v Mild Hybrid. E-supercharger. Direct Injection. Dual VVT.  CVVL (Intake VVL). [[w:Ingenium engine family|JLR Ingenium AJ20P6/AJ300P engine]].&lt;br&gt; Jaguar F-Pace P400 ('21-'26).
|-
| E || 340 PS/335 hp || 8-spd. Auto. || V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. Continuously variable intake &amp; exhaust valve timing.&lt;br&gt; [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; Jaguar XE 35t ('18), XF 35t ('18), F-Type ('18), F-Type P340 ('19-'20),&lt;br&gt; F-Pace 35t ('18).
|-
| F || 380 PS/375 hp || 8-spd. Auto. || V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. Continuously variable intake &amp; exhaust valve timing.&lt;br&gt; [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; Jaguar XE S ('18-'19), XF S ('18-'20), F-Type ('18),&lt;br&gt; F-Type P380 ('19), F-Type P380 R-Dynamic ('19-'21), F-Pace S ('18-'20).
|-
| G || 400 PS/395 hp || 8-spd. Auto. || V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. Continuously variable intake &amp; exhaust valve timing.&lt;br&gt; [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; Jaguar F-Type 400 Sport ('18).
|-
| J || 340 PS/335 hp || 6-spd. Man. || V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. Continuously variable intake &amp; exhaust valve timing.&lt;br&gt; [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; Jaguar F-Type ('18), F-Type P340 ('19).
|-
| K || 380 PS/375 hp || 6-spd. Man. || V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. Continuously variable intake &amp; exhaust valve timing.&lt;br&gt; [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; Jaguar F-Type P380 R-Dynamic ('18-'19).
|-
| E || 250 PS/247 hp || 8-spd. Auto. || X || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,&lt;br /&gt; 16 valve||Direct Injection. Dual VVT. CVVL (Intake VVL).&lt;br&gt; [[w:Ingenium engine family|JLR Ingenium AJ20P4/AJ200P engine]].&lt;br&gt; Jaguar F-Pace P250 ('21-'26).
|-
| F || 250 PS/247 hp || 8-spd. Auto. || X || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,&lt;br /&gt; 16 valve||Direct Injection. Dual VVT. CVVL (Intake VVL).&lt;br&gt; [[w:Ingenium engine family|JLR Ingenium AJ20P4/AJ200P engine]].&lt;br&gt; Jaguar XE 25t ('18-'20), XF 25t ('18-'20), XF P250 ('21-'24),&lt;br&gt; E-Pace P250 ('18-'24), F-Pace 25t ('18-'20).
|-
| G || 300 PS/296 hp || 8-spd. Auto. || X || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,&lt;br /&gt; 16 valve||Direct Injection. Dual VVT. CVVL (Intake VVL).&lt;br&gt; [[w:Ingenium engine family|JLR Ingenium AJ20P4/AJ200P engine]].&lt;br&gt; Jaguar XE 30t ('18-'20), XF 30t ('18-'20), XF P300 ('21-'24),&lt;br&gt; F-Type ('18), F-Type P300 ('19-'21), E-Pace P300 R-Dynamic ('18-'20),&lt;br&gt; E-Pace 300 Sport ('21-'22), F-Pace 30t ('18-'20). 
|}

====Motor Type for Electric Vehicles 2019-====

{| class=&quot;wikitable&quot;
|+Position 7-8
|-
! VIN Pos. 7 !! Power Level !! Transmission !! VIN Pos. 8 !! # of Motors !! Battery Size !! Battery Type !! Fuel !! Drive Wheels !! Notes/Applications
|-
| S || 400 PS/394 hp || 1-spd. Auto. || 1 || 2 || 90 Kwh || Lithium-ion || Electricity || All || Jaguar I-Pace EV400 ('19-'24).
|-
| T || 1029 PS/1015 hp || 1-spd. Auto. || 1 || 3 &lt;br&gt; (1 Front,&lt;br&gt; 2 Rear) || 118 Kwh || Lithium-ion || Electricity || All || Jaguar Type 01 ('28-).
|}

===Check Digit/Gearbox (Position 9)===
* USA /Canada [[Vehicle Identification Numbers (VIN codes)/Check digit|Check digit]]

===Model Year Code (Position 10)===
''See: [[Vehicle Identification Numbers (VIN codes)/Model year]]''

===Plant Codes (Position 11) 2016-===
* A - Solihull, West Midlands, England, UK (XE '17, F-Pace '17-'26, Type 01 '28-)
* C - Castle Bromwich, West Midlands, England, UK (XE '17-'20, XF '16-'24, F-Type '18-'24)
* S - Oxford Road plant, Ryton, West Midlands, England, UK (JLR SVO plant) (XE SV Project 8 '19)
* 1 - Graz, Austria (Magna Steyr plant) (E-Pace '18-'24, I-Pace EV '19-'24)

===Model (Position 12)===
* 9 - XE ('17) [Solihull plant]
* P - XE ('17-'20) [Castle Bromwich plant]
* Y - XF ('16-'24)
* K - F-Type ('18-'24)
* Z - E-Pace ('18-'20)
* 0 - E-Pace ('20-'24)
* F - I-Pace EV ('19-'20)
* 6 - I-Pace EV ('20-'24)

'''Positions 13–17, Serial Number'''

==General Template for Jaguar's VIN format (All models: 2000-2015 plus F-Type '16-'17, XJ '16-'19)==

===Jaguar WMIs (2000-) (Position 1-3)===

* SAJ - Jaguar passenger car (UK)
* SAD - Jaguar SUV (UK &amp; Europe)

===Regional Spec/Restraint System (Position 4):===
* J = Manual seat belts, Dual front airbags (US: XK8 '00)
* B = Manual seat belts, Dual front airbags (Canada: XK8 '00)
* D = Manual seat belts, Depowered Dual front airbags, &amp; Front Side Airbags (US: S-Type '00-'02, XJ8/XJR '00-'03, XK8/XKR '01-'06, XK/XKR Early '07)
* F = Manual seat belts, Depowered Dual front airbags, &amp; Front Side Airbags (Canada: S-Type '00-'02, XJ8/XJR '00-'03, XK8/XKR '01-'06, XK/XKR Early '07)
* E = Manual seat belts, Depowered Dual front airbags w/occupant position sensing, &amp; Front Side Airbags &amp; Side Curtain Airbags (US: X-Type '02-'04, S-Type '03-'04, XJ8/XJR Early '04)
* G = Manual seat belts, Depowered Dual front airbags w/occupant position sensing, &amp; Front Side Airbags &amp; Side Curtain Airbags (Canada: X-Type '02-'04,&lt;br&gt; S-Type '03-'04, XJ8/XJR Early '04)
* W = Manual seat belts, Depowered Dual front airbags w/occupant position (driver) and weight (fr. psgr.) sensing, &amp; Front Side Airbags &amp; Side Curtain Airbags &lt;br&gt; (US: X-Type '05-'08, S-Type '05-'08, XF '09-'15,  XJ8/XJR '04-'09, XJ '10-)
* X = Manual seat belts, Depowered Dual front airbags w/occupant position (driver) and weight (fr. psgr.) sensing, &amp; Front Side Airbags &amp; Side Curtain Airbags (Canada: X-Type '05-'08, S-Type '05-'08, XF '09-'15, XJ8/XJR '04-'09, XJ '10-)
* W = Manual seat belts, Depowered Dual front airbags w/occupant position (driver) and weight (fr. psgr.) sensing, &amp; Front Side Head/Thorax Airbags &lt;br&gt; (US: XK/XKR '07-'15, F-Type '14-)
* X = Manual seat belts, Depowered Dual front airbags w/occupant position (driver) and weight (fr. psgr.) sensing, &amp; Front Side Head/Thorax Airbags &lt;br&gt; (Canada: XK/XKR '07-'15, F-Type '14-)

===Transmission &amp; Steering Location (Position 5 - '00-'12):===
* A = Automatic / LHD
* B = Manual / LHD (X-Type '02-'05, S-Type 3.0 '03-'04)

===Transmission &amp; Drive Wheels (Position 5 - '13-):===
* A = Automatic / Rwd (XF '13-'15, XJ '13-'19, XK '13-'15, F-Type '14-'17)
* B = Manual / Rwd (F-Type '16-'17)
* J = Automatic / Awd (XF Awd '13-'15, XJ Awd '13-'19, F-Type Awd '16-'17)

===Model Line (Position 6-7)===

{| class=&quot;wikitable&quot;
|+Position 6-7
!VIN code
!Description
|-
|51
|[[w:Jaguar X-Type|Jaguar X-Type sedan - High Series]] ('02-'08)
|-
|52
|[[w:Jaguar X-Type|Jaguar X-Type sedan - Entry Series]] ('03-'04)
|-
|53
|[[w:Jaguar X-Type|Jaguar X-Type sedan w/Sport Package]] ('02-'03)
|-
|54
|[[w:Jaguar X-Type|Jaguar X-Type Sportwagon]] ('05-'08)
|-
|01
|[[w:Jaguar S-Type (1999)|Jaguar S-Type]] ('00-'08)
|-
|03
|[[w:Jaguar S-Type (1999)|Jaguar S-Type Sport]] [3.0, 4.0] ('02)
|-
|03
|[[w:Jaguar S-Type (1999)|Jaguar S-Type Sport]] [3.0, 4.2] ('03)
|-
|03
|[[w:Jaguar S-Type (1999)|Jaguar S-Type R]] ('03-'08)
|-
|05
|[[w:Jaguar XF (X250)|Jaguar XF Luxury]] ('09)
|-
|06
|[[w:Jaguar XF (X250)|Jaguar XF Premium Luxury]] ('09)
|-
|07
|[[w:Jaguar XF (X250)|Jaguar XF Supercharged]] ('09)
|-
|0E
|[[w:Jaguar XF (X250)|Jaguar XF]] ('13-'14)
|-
|0F
|[[w:Jaguar XF (X250)|Jaguar XF]] ('10-'12)
|-
|0F
|[[w:Jaguar XF (X250)|Jaguar XF 2.0T Premium]] [8th pos. of VIN is S] ('15)
|-
|0F
|[[w:Jaguar XF (X250)|Jaguar XF 3.0 Sport Rwd or 3.0 Portfolio Rwd]] [8th pos. of VIN is 7] ('15)
|-
|0F
|[[w:Jaguar XF (X250)|Jaguar XF 3.0 Sport Awd or 3.0 Portfolio Awd]] [8th pos. of VIN is F] ('15)
|-
|0G
|[[w:Jaguar XF (X250)|Jaguar XF Premium]] ('10-'11)
|-
|0H
|[[w:Jaguar XF (X250)|Jaguar XF Portfolio]] [8th pos. of VIN is B] ('12)
|-
|0H
|[[w:Jaguar XF (X250)|Jaguar XF Supercharged]] [8th pos. of VIN is E: '10-'13 or P: '13-'15]
|-
|0J
|[[w:Jaguar XF (X250)|Jaguar XFR]] ('10-'15)
|-
|0K
|[[w:Jaguar XF (X250)|Jaguar XFR-S]] ('13-'15)
|-
|8J
|[[w:Jaguar XF (X250)|Jaguar XFR w/Speed Pack]] ('13-'15)
|-
|12
|[[w:Jaguar XJ (X308)#Sport|Jaguar XJ Sport]] ('02-'03)
|-
|14
|[[w:Jaguar XJ (X308)|Jaguar XJ8]] ('00-'03)
|-
|15
|[[w:Jaguar XJ (X308)#XJR|Jaguar XJR]] ('00-'03)
|-
|23
|[[w:Jaguar XJ (X308)|Jaguar XJ8L]] (LWB) ('00-'01)
|-
|24
|[[w:Jaguar XJ (X308)#Daimler/Vanden Plas|Jaguar XJ8 Vanden Plas]] (LWB) ('00-'03)
|-
|25
|[[w:Jaguar XJ (X308)#Daimler/Vanden Plas|Jaguar XJ8 Vanden Plas Supercharged]] (LWB) ('00-'01)
|-
|25
|[[w:Jaguar XJ (X308)#Daimler/Vanden Plas|Jaguar XJ Super V8]] (LWB) ('02-'03)
|-
|71
|[[w:Jaguar XJ (X350)|Jaguar XJ8]] ('04-'09)
|-
|73
|[[w:Jaguar XJ (X350)|Jaguar XJR]] ('04-'09)
|-
|74
|[[w:Jaguar XJ (X350)|Jaguar XJ8 Vanden Plas]] (SWB) ('04)
|-
|79
|[[w:Jaguar XJ (X350)|Jaguar XJ8L]] (LWB) ('05-'09)
|-
|82
|[[w:Jaguar XJ (X350)|Jaguar XJ8 Vanden Plas]] (LWB) ('05-'09)
|-
|82
|[[w:Jaguar XJ (X350)|Jaguar XJ Super V8]] (LWB, 5-psgr.) ('05-'09)
|-
|86
|[[w:Jaguar XJ (X350)|Jaguar XJ Super V8 Portfolio]] (LWB, 4-psgr.) ('06)
|-
|94
|[[w:Jaguar XJ (X350)|Jaguar XJ Super V8 Portfolio]] (LWB, 5-psgr.) ('09)
|-
|1C
|[[w:Jaguar XJ (X351)|Jaguar XJ]] ('10-'15)
|-
|1C
|[[w:Jaguar XJ (X351)|Jaguar XJ R-Sport]] [8th pos. of VIN is 7 (Rwd) or D (Awd)] ('16-'19)
|-
|1C
|[[w:Jaguar XJ (X351)|Jaguar XJ Supercharged]] [8th pos. of VIN is E] ('16-'19)
|-
|1E
|[[w:Jaguar XJ (X351)|Jaguar XJR]] ('14-'17)
|-
|1G
|[[w:Jaguar XJ (X351)|Jaguar XJ Supercharged]] [8th pos. of VIN is E: '10-'13 or T: '13-'15]
|-
|1J
|[[w:Jaguar XJ (X351)|Jaguar XJ Supersport]] ('11-'12)
|-
|2E
|[[w:Jaguar XJ (X351)|Jaguar XJR LWB]] ('14-'17), XJR575 LWB ('18-'19)
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL]] [8th pos. of VIN is B] ('10-'11)
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL Portfolio Rwd]] [8th pos. of VIN is B: '12-'13 or 1: '13]
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL Portfolio Rwd]] [8th pos. of VIN is Z: '14-'15)
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL Portfolio Rwd]] [8th pos. of VIN is 7: '16-'19), XJ50 3.0 Rwd (LWB) '19
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL Portfolio Awd]] [8th pos. of VIN is D] ('13-'19), XJ50 3.0 Awd (LWB) '19
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL Supercharged]] [8th pos. of VIN is E: '10-'13, '16-'19 or T: '13-'15], XJ50 5.0 Rwd (LWB) '19, XJ Collection (LWB) '19
|-
|2J
|[[w:Jaguar XJ (X351)|Jaguar XJL Supersport]] ('11-'13)
|-
|2K
|[[w:Jaguar XJ (X351)|Jaguar XJL Ultimate]] ('13)
|-
|3F
|[[w:Jaguar XJ (X351)|Jaguar XJ Supersport w/Speed Pack]] ('12-'13)
|-
|3G
|[[w:Jaguar XJ (X351)|Jaguar XJL Supersport w/Speed Pack]] ('12-'13)
|-
|3H
|[[w:Jaguar XJ (X351)|Jaguar XJ Supercharged w/Sport &amp; Speed Pack]] ('12-'15)
|-
|3K
|[[w:Jaguar XJ (X351)|Jaguar XJL Supercharged w/Sport &amp; Speed Pack]] ('12-'15)
|-
|41
|[[w:Jaguar XK (X100)|Jaguar XK8/XKR coupe]] ('00-'06)
|-
|42
|[[w:Jaguar XK (X100)|Jaguar XK8/XKR convertible]] ('00-'06)
|-
|43
|[[w:Jaguar XK (X150)|Jaguar XK/XKR coupe]] ('07-'09)
|-
|44
|[[w:Jaguar XK (X150)|Jaguar XK/XKR convertible]] ('07-'09)
|-
|45
|[[w:Jaguar XK (X150)|Jaguar XKR Portfolio Edition coupe]] ('09)
|-
|46
|[[w:Jaguar XK (X150)|Jaguar XKR Portfolio Edition convertible]] ('09)
|-
|4D
|[[w:Jaguar XK (X150)|Jaguar XK Touring coupe]] [8th pos. of VIN is B] ('13-'14)
|-
|4E
|[[w:Jaguar XK (X150)|Jaguar XK Touring convertible]] [8th pos. of VIN is B] ('13-'14)
|-
|4D
|[[w:Jaguar XK (X150)|Jaguar XKR coupe]] [8th pos. of VIN is C] ('10-'15)
|-
|4E
|[[w:Jaguar XK (X150)|Jaguar XKR convertible]] [8th pos. of VIN is C] ('10-'15)
|-
|4F
|[[w:Jaguar XK (X150)|Jaguar XK coupe]] (most Portfolio Edition features are std.) [8th pos. of VIN is B] ('10-'15)
|-
|4F
|[[w:Jaguar XK (X150)|Jaguar XKR175 coupe]] [8th pos. of VIN is C] ('11)
|-
|4F
|[[w:Jaguar XK (X150)|Jaguar XKR coupe w/Dynamic Pack]] [8th pos. of VIN is C] ('13-'15), XK Final Fifty Edition coupe ('15)
|-
|4G
|[[w:Jaguar XK (X150)|Jaguar XK convertible]] (most Portfolio Edition features are std.) [8th pos. of VIN is B] ('10-'15)
|-
|4G
|[[w:Jaguar XK (X150)|Jaguar XKR convertible w/Dynamic Pack]] [8th pos. of VIN is C] ('13-'15), XK Final Fifty Edition convertible ('15)
|-
|4H
|[[w:Jaguar XK (X150)|Jaguar XKR-S coupe]] ('12-'15), XKR-S GT coupe ('14)
|-
|4J
|[[w:Jaguar XK (X150)|Jaguar XKR-S convertible]] ('12-'15)
|-
|6A
|[[w:Jaguar F-Type)|Jaguar F-Type coupe]] ('15-'17), F-Type Premium coupe '17
|-
|6B
|[[w:Jaguar F-Type)|Jaguar F-Type S coupe]] ('15-'17), F-Type S British Design Edition coupe '17
|-
|6D
|[[w:Jaguar F-Type)|Jaguar F-Type R coupe]] ('15-'17)
|-
|6E
|[[w:Jaguar F-Type)|Jaguar F-Type convertible]] ('14-'17), F-Type Premium convertible '17
|-
|6F
|[[w:Jaguar F-Type)|Jaguar F-Type S convertible]] ('14-'17), F-Type S British Design Edition convertible '17
|-
|6G
|[[w:Jaguar F-Type)|Jaguar F-Type V8 S convertible]] ('14-'15)
|-
|6H
|[[w:Jaguar F-Type)|Jaguar F-Type R convertible]] ('16-'17)
|-
|6J
|[[w:Jaguar F-Type)|Jaguar F-Type SVR coupe]] ('17)
|-
|6K
|[[w:Jaguar F-Type)|Jaguar F-Type SVR convertible]] ('17)
|-
|7A
|[[w:Jaguar F-Type#Project 7)|Jaguar F-Type Project 7 convertible]] ('16)
|}

===Engine/Emissions Control System (Position 8)===

{| class=&quot;wikitable&quot;
|+Position 8
! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications
|-
| A || 3.0L || 60° V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. ULEV. Variable intake valve timing. [[w:Jaguar AJ-V6 engine#AJ30|Jaguar AJ-V6 - AJ30 V6 engine]].&lt;br&gt; Jaguar X-Type 3.0 (Mid '05-'08), S-Type 3.0 ('06-'08). 
|-
| A || 4.2L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. ULEV. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.2 L|Jaguar AJ-V8 - AJ34 V8 engine]]. Jaguar XF ('10).
|-
| A || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 550 PS/542 hp. Jaguar XKR-S ('12-'15), XKR-S GT ('14), F-Type R coupe ('15).
|-
| B || 4.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. [[w:Jaguar AJ-V8 engine#Supercharged|Jaguar AJ-V8 - AJ27S V8 engine]].&lt;br&gt; Jaguar XJR ('00-'03), Vanden Plas Supercharged ('00-'01), Super V8 ('02-'03), XKR ('00-'02).
|-
| B || 4.2L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. [[w:Jaguar AJ-V8 engine#Supercharged_2|Jaguar AJ-V8 - AJ33S V8 engine]]. Jaguar XJR ('04-'05), Super V8 ('05), XKR ('03-'06).
|-
| B || 4.2L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. ULEV. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.2 L|Jaguar AJ-V8 - AJ34 V8 engine]].&lt;br&gt; Jaguar S-Type ('06-'08), XF ('09), XJ8/Vanden Plas ('06-'09), XK ('07-'09).
|-
| B || 5.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. Variable intake valve lift. Variable intake.&lt;br&gt; [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; Jaguar XF ('10-'12), XJ ('11-'12), XJL ('11), XJL Portfolio Rwd ('12-'13), XK ('10-'15), XK Touring ('13-'14).
|-
| C || 3.0L || 60° V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. Variable intake valve timing. [[w:Jaguar AJ-V6 engine#AJ30|Jaguar AJ-V6 - AJ30 V6 engine]].&lt;br&gt; Jaguar S-Type 3.0 ('00-'01), X-Type 3.0 ('02-Mid '05). 
|-
| C || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ27 V8 engine]].&lt;br&gt; Jaguar XJ8/Vanden Plas ('00-'03), XJ Sport ('02-'03), XK8 ('00-'02).
|-
| C || 4.2L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.2 L|Jaguar AJ-V8 - AJ33 V8 engine]]. Jaguar XJ8 ('04-'05), XK8 ('03-'06).
|-
| C || 4.2L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. ULEV. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#Supercharged_2|Jaguar AJ-V8 - AJ34S V8 engine]].&lt;br&gt; Jaguar S-Type R ('06-'08), XF Supercharged ('09), XJR ('06-'09), Super V8 ('06-'09), XKR ('07-'09).
|-
| C || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 510 PS/503 hp. Jaguar XFR ('10-'13), XJ/XJL Supersport ('11-'13), XKR ('10-'15).
|-
| C || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 380 PS/375 hp. Jaguar F-Type S ('14-'15), F-Type S w/man. trans. ('16-'17).
|-
| D || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ28 V8 engine]]. Jaguar S-Type 4.0 ('00-'01).
|-
| D || 2.5L || 60° V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. Variable intake valve timing. [[w:Jaguar AJ-V6 engine#AJ25|Jaguar AJ-V6 - AJ25 V6 engine]]. Jaguar X-Type 2.5 ('02-'05).
|-
| D || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XJ Awd, XJL Portfolio Awd ('13-'15).
|-
| D || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XJ R-Sport Awd, XJL Portfolio Awd ('16-'19), XJ50 3.0 Awd ('19).
|-
| E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 470 PS/464 hp.&lt;br&gt; Jaguar XF Supercharged ('10-'13), XJ/XJL Supercharged ('11-'13, '16-'19), XJ50 5.0 Rwd ('19), XJ Collection ('19).
|-
| F || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 3.0 Awd ('13-'14).
|-
| F || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 3.0 Awd ('15).
|-
| H || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,&lt;br /&gt; 32 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]]. 510 PS/503 hp. Jaguar XFR ('13-'15).
|-
| K || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 550 PS/542 hp. Jaguar XJR/XJR LWB ('14-'17).
|-
| K || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 575 PS/567 hp. Jaguar XJR575 LWB ('18-'19).
|-
| L || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 495 PS/488 hp. Jaguar F-Type V8 S convertible ('14-'15).
|-
| L || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 550 PS/542 hp. Jaguar F-Type R  ('16-'17).
|-
| N || 3.0L || 60° V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. Variable intake valve timing. [[w:Jaguar AJ-V6 engine#AJ30|Jaguar AJ-V6 - AJ30 V6 engine]]. Jaguar S-Type 3.0 ('01-'02).
|-
| P || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ28 V8 engine]]. Jaguar S-Type 4.0 ('01-'02).
|-
| P || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,&lt;br /&gt; 32 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]]. 470 PS/464 hp. Jaguar XF Supercharged ('13-'15).
|-
| S || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,&lt;br /&gt; 16 valve||Direct Injection. Dual VVT. [[w:Ford EcoBoost engine#2.0 L (2010–2018)|Ford EcoBoost engine (Mazda L engine-based)]].&lt;br&gt; Jaguar XF 2.0T ('13-'14), XF 2.0T Premium ('15).
|-
| T || 3.0L || 60° V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. Variable intake valve timing. [[w:Jaguar AJ-V6 engine#AJ30|Jaguar AJ-V6 - AJ30 V6 engine]]. Jaguar S-Type 3.0 ('03-'05).
|-
| T || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,&lt;br /&gt; 32 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]]. 470 PS/464 hp. Jaguar XJ/XJL Supercharged ('13-'15).
|-
| T || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar F-Type w/auto. trans. ('15-'17), F-Type Premium w/auto. trans. ('17).
|-
| U || 4.2L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.2 L|Jaguar AJ-V8 - AJ33 V8 engine]]. Jaguar S-Type 4.2 ('03-'05).
|-
| U || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 380 PS/375 hp. Jaguar F-Type S ('15), F-Type S Rwd w/auto. trans. ('16-'17).
|-
| V || 4.2L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. [[w:Jaguar AJ-V8 engine#Supercharged_2|Jaguar AJ-V8 - AJ33S V8 engine]]. Jaguar S-Type R ('03-'05).
|-
| V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 380 PS/375 hp. Jaguar F-Type S Awd w/auto. trans. ('16-'17).
|-
| X || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,&lt;br /&gt; 24 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 3.0 Rwd ('14).
|-
| Z || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 550 PS/542 hp. Jaguar XFR-S ('13-'15).
|-
| Z || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,&lt;br /&gt; 24 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XJ Rwd, XJL Portfolio Rwd ('14-'15).
|-
| 1 || 5.0L || V8 || Gas/E85 ||DOHC,&lt;br /&gt; 32 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. Variable intake valve lift. Variable intake. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]]. Jaguar XJL Portfolio Rwd ('13).
|-
| 6 || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar F-Type w/man. trans. ('16-'17), F-Type Premium w/man. trans. ('17).
|-
| 7 || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 3.0 Rwd ('13), XJ Rwd ('13), F-Type ('14-'15).
|-
| 7 || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 3.0 Rwd ('15), XJ R-Sport Rwd ('16-'19), XJL Portfolio Rwd ('16-'19), XJ50 3.0 Rwd ('19).
|-
| 8 || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 575 PS/567 hp. Jaguar F-Type Project 7 ('16), F-Type SVR ('17).
|}

===Check Digit/Gearbox (Position 9)===
* USA /Canada [[Vehicle Identification Numbers (VIN codes)/Check digit|Check digit]]

===Model Year Code (Position 10)===
''See: [[Vehicle Identification Numbers (VIN codes)/Model year]]''

===Plant Code/Model Line/Engine (Position 11) 2000-2019===
* X - Halewood, Merseyside, England, UK - X-Type 2.5 ('02-'05)
* W - Halewood, Merseyside, England, UK - X-Type 3.0 ('02-'08)
* F - Castle Bromwich, West Midlands, England, UK - S-Type 3.0 ('00-'08)
* G - Castle Bromwich, West Midlands, England, UK - S-Type 4.0 ('00-'02)
* H - Castle Bromwich, West Midlands, England, UK - S-Type 4.2 ('03-'08)
* 1 - Castle Bromwich, West Midlands, England, UK - S-Type R (4.2 supercharged) ('03-'08)
* H - Castle Bromwich, West Midlands, England, UK - XF 4.2 ('09-'10)
* 1 - Castle Bromwich, West Midlands, England, UK - XF Supercharged (4.2 supercharged) ('09)
* L - Castle Bromwich, West Midlands, England, UK - XF 5.0 ('10-'12)
* M - Castle Bromwich, West Midlands, England, UK - XF Supercharged, XFR (5.0 supercharged) ('10-'15), XFR-S (5.0 supercharged) ('13-'15)
* P - Castle Bromwich, West Midlands, England, UK - XF 2.0T ('13-'15)
* 8 - Castle Bromwich, West Midlands, England, UK - XF 3.0 supercharged ('13-'15)
* L - Browns Lane plant, Coventry, West Midlands, England, UK - XJ8 (4.0) ('00-'03), XJ8L (4.0) ('00-'01), XJ8 Vanden Plas (4.0) ('00-'03), XJ Sport (4.0) ('02-'03)
* M - Browns Lane plant, Coventry, West Midlands, England, UK - XJ8 Vanden Plas Supercharged (4.0 supercharged) ('00-'01),&lt;br&gt; Super V8 (4.0 supercharged) ('02-'03), XJR (4.0 supercharged) ('00-'03)
* S - Browns Lane plant, Coventry, West Midlands, England, UK - XJ8 (4.2) ('04-'06), XJ8L (4.2) ('05-'06), XJ8 Vanden Plas (4.0) ('04-'06)
* T - Browns Lane plant, Coventry, West Midlands, England, UK - Super V8 (4.2 supercharged) ('05-'06), Super V8 Portfolio (4.2 supercharged) ('06),&lt;br&gt; XJR (4.2 supercharged) ('04-'06)
* S - Castle Bromwich, West Midlands, England, UK - XJ8 (4.2) ('07-'09), XJ8L (4.2) ('07-'09), XJ8 Vanden Plas (4.0) ('07-'09)
* T - Castle Bromwich, West Midlands, England, UK - Super V8 (4.2 supercharged) ('07-'09), Super V8 Portfolio (4.2 supercharged) ('09),&lt;br&gt; XJR (4.2 supercharged) ('07-'09)
* L - Castle Bromwich, West Midlands, England, UK - XJ (5.0) ('10-'12), XJL (5.0) ('10-'11), XJL Portfolio (5.0) ('12-'13)
* M - Castle Bromwich, West Midlands, England, UK - XJ/XJL Supercharged (5.0 supercharged) ('10-'19), XJ/XJL Supersport (5.0 supercharged) ('11-'13),&lt;br&gt; XJL Ultimate (5.0 supercharged) ('13), XJR SWB/LWB (5.0 supercharged) ('14-'17), XJR575 LWB (5.0 supercharged) ('18-'19), XJ50 LWB (5.0 supercharged) ('19), XJ Collection Sp. Ed. LWB (5.0 supercharged) ('19)
* 8 - Castle Bromwich, West Midlands, England, UK - XJ base (3.0 supercharged) ('13-'15), XJ R-Sport (3.0 supercharged) ('16-'19),&lt;br&gt; XJL Portfolio AWD (3.0 supercharged) ('13-'19), XJL Portfolio RWD (3.0 supercharged) ('14-'19), XJ50 LWB (3.0 supercharged) ('19)
* N - Browns Lane plant, Coventry, West Midlands, England, UK - XK8 (4.0) ('00-'02)
* P - Browns Lane plant, Coventry, West Midlands, England, UK - XKR (4.0 supercharged) ('00-'02)
* 2 - Browns Lane plant, Coventry, West Midlands, England, UK - XK8 (4.2) ('03-'06)
* 3 - Browns Lane plant, Coventry, West Midlands, England, UK - XKR (4.2 supercharged) ('03-'06)
* 5 - Castle Bromwich, West Midlands, England, UK - XK (4.2) ('07-'09)
* 9 - Castle Bromwich, West Midlands, England, UK - XKR (4.2 supercharged) ('07-'09)
* L - Castle Bromwich, West Midlands, England, UK - XK (5.0) ('10-'15)
* M - Castle Bromwich, West Midlands, England, UK - XKR (5.0 supercharged) ('10-'15), XKR-S (5.0 supercharged) ('12-'15), XKR-S GT (5.0 supercharged) ('14)
* 8 - Castle Bromwich, West Midlands, England, UK - F-Type Base, S (3.0 supercharged) ('14-'17), F-Type Premium (3.0 supercharged) ('17)
* M - Castle Bromwich, West Midlands, England, UK - F-Type V8S (5.0 supercharged) ('14-'15), F-Type R (5.0 supercharged) ('15-'17),&lt;br&gt; F-Type Project 7 (5.0 supercharged) ('16), F-Type SVR (5.0 supercharged) ('17)

===Model (Position 12)===
* C - X-Type ('02-'03)
* D - X-Type ('03-'04)
* E - X-Type ('04-'06)
* J - X-Type ('06-'08)
* L - S-Type ('00-'01)
* M - S-Type ('01-'04)
* N - S-Type ('04-'08)
* R - XF ('09-'11)
* S - XF ('11-'13)
* U - XF ('13-'15)
* F - XJ ('00-'03)
* G - XJ ('04-'06) [Browns Lane plant]
* H - XJ ('06-'09) [Castle Bromwich plant]
* V - XJ ('10-'16)
* W - XJ ('16-'19)
* A - XK ('00-'06)
* B - XK ('07-'15)
* K - F-Type ('14-'17)

'''Positions 13–17, Serial Number'''

==General Template for Jaguar's VIN format (1981 - 1999)==

===Jaguar WMIs (1981-1999) (Position 1-3)===
* SAJ - Jaguar passenger car

===Model Line (Position 4)===

{| class=&quot;wikitable&quot;
|+Position 4
!VIN code
!Description
|-
|A
|[[w:Jaguar XJ#Series 3 (1979–1992)|Jaguar XJ6]] ('81-'87), XJ6 Vanden Plas ('82-'87)
|-
|B
|[[w:Jaguar XJ#Series 3 (1979–1992)|Jaguar XJ12]] (Canada only: '81-'88)
|-
|D
|[[w:Jaguar XJ#Series 3 (1979–1992)|Jaguar XJ12]] (Canada only: '89-'92)
|-
|H
|[[w:Jaguar XJ (XJ40)|Jaguar XJ6]] ('88-'89, '93-'94)
|-
|F
|[[w:Jaguar XJ (XJ40)|Jaguar XJ6]] ('90-'92)
|-
|H
|[[w:Jaguar XJ (XJ40)|Jaguar XJ6 Sovereign]] ('90-'92)
|-
|K
|[[w:Jaguar XJ (XJ40)#Daimler/Vanden Plas|Jaguar XJ6 Vanden Plas]] ('88-'94)
|-
|M
|[[w:Jaguar XJ (XJ40)#Majestic (1989–1992 – SWB; 1993–1994 – LWB)|Jaguar XJ6 Vanden Plas Majestic]] ('89-'90, '92)
|-
|M
|[[w:Jaguar XJ (XJ40)#XJ12 and Daimler Double Six (XJ81)|Jaguar XJ12]] ('94)
|-
|H
|[[w:Jaguar XJ (X300)|Jaguar XJ6]] ('95-'97)
|-
|H
|[[w:Jaguar XJ (X300)|Jaguar XJ6L]] LWB [X330] ('97)
|-
|K
|[[w:Jaguar XJ (X300)#Daimler/Jaguar Vanden Plas|Jaguar XJ6 Vanden Plas]] SWB ('95)
|-
|K
|[[w:Jaguar XJ (X300)#Daimler/Jaguar Vanden Plas|Jaguar XJ6 Vanden Plas]] LWB [X330] ('96-'97)
|-
|M
|[[w:Jaguar XJ (X300)#XJ12 (X305)|Jaguar XJ12]] SWB ('95)
|-
|M
|[[w:Jaguar XJ (X300)#XJ12 (X305)|Jaguar XJ12]] LWB [X330] ('96)
|-
|P
|[[w:Jaguar XJ (X300)#XJR (X306)|Jaguar XJR]] ('95-'97)
|-
|H
|[[w:Jaguar XJ (X308)|Jaguar XJ8]] ('98-'99)
|-
|H
|[[w:Jaguar XJ (X308)|Jaguar XJ8L]] LWB ('98-'99)
|-
|K
|[[w:Jaguar XJ (X308)#Daimler/Vanden Plas|Jaguar XJ8 Vanden Plas]] LWB ('98-'99)
|-
|P
|[[w:Jaguar XJ (X308)#XJR|Jaguar XJR]] ('98-'99)
|-
|N
|[[w:Jaguar XJS|Jaguar XJ-S]] ('82-'91), XJ-SC ('86-'88), XJS ('92-'96)
|-
|T
|[[w:Jaguar XJS|Jaguar XJ-S]] Rouge Collection ('89-'90), Classic Collection ('90-'91)
|-
|S
|[[w:Jaguar XJS#XJR-S|Jaguar XJR-S]] ('93)
|-
|G
|[[w:Jaguar XK (X100)|Jaguar XK8]] ('97-'99)
|}

===Class (Regional Spec)/Restraint System (Position 5):===
* V = N. American-spec (Manual seat belts)
* L = Canadian-spec (Manual seat belts)

* Y = XJ6 Vanden Plas [Series III] ('82-'87) (Manual seat belts)

* A = Motorized Shoulder Belts (XJ-S coupe '88-'89, XJ-SC '88)
* Y = Motorized Shoulder Belts (XJ-S coupe '89, XJ sedan '89-'92)
* W = Manual seat belts, Driver-side airbag (US: XJ-S '90-'93, XJ6 '93, XJ12 Early '94)
* X = Manual seat belts, Dual front airbags (US: XJS '94-'96, XJ6 '94-'97, XJ12 '94-'96, XJR '95-'97, XK8 '97-'99)
* X = Manual seat belts, Dual front airbags, &amp; Front Side Airbags (US: XJ8/XJR '98-'99)
* D = Manual seat belts, Depowered Dual front airbags, &amp; Front Side Airbags (US: XJ8/XJR '99)
* M = Manual seat belts, Driver-side airbag (Canada)
* N = Manual seat belts, Dual front airbags (Canada)
* F = Manual seat belts, Depowered Dual front airbags, &amp; Front Side Airbags (Canada: XJ8/XJR '99)

===Body Style (Position 6):===
* 1 = 4-door sedan (XJ-series sedan '81-'99)
* 2 = 2-door convertible w/2+2 seating (XJS convertible '94-'96, XK8 convertible '97-'99)
* 3 = 2-door Cabriolet (XJ-SC '86-'88)
* 4 = 2-door convertible w/2-psgr. seating (factory-built XJS convertible '89-'94, XJR-S convertible '93)
* 5 = 2-door coupe (XJS coupe '82-'96, XJR-S coupe '93, XK8 coupe '97-'99)
* 5 = 2-door coupe (Hess &amp; Eisenhardt-built XJS convertible '87-'88) [coupe conversion]

===Engine Type (Position 7):===
{| class=&quot;wikitable&quot;
|+Position 7
|-
! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications
|-
| 1 || 4.0L || I6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. [[w:Jaguar AJ6 engine#AJ16S|Jaguar AJ16S I6]]. Jaguar XJR ('95-'97).
|-
| 2 || 4.2L || I6 || Gas ||DOHC,&lt;br /&gt; 12 valve||CA &amp; Canada-spec. MPI. [[w:Jaguar XK engine|Jaguar XK I6]]. Jaguar XJ6 ('81-'82).
|-
| 2 || 4.0L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. Dual-canister evaporative emissions system. [[w:Jaguar AJ6 engine#AJ16|Jaguar AJ16 I6]]. Jaguar XJ6 ('96-'97).
|-
| 2 || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Variable intake valve timing. Dual-canister evaporative emissions system. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ26 V8 engine]].&lt;br&gt; Jaguar XJ8 ('98), XK8 ('98).
|-
| 3 || 4.2L || I6 || Gas ||DOHC,&lt;br /&gt; 12 valve||N. America-spec. MPI. [[w:Jaguar XK engine|Jaguar XK I6]]. Jaguar XJ6 ('81-'87).
|-
| 3 || 6.0L || 60° V12 || Gas ||SOHC,&lt;br /&gt; 24 valve||MPI. [[w:Jaguar V12 engine|Jaguar V12]] modified by [[w:Tom Walkinshaw Racing|JaguarSport]]. Jaguar XJR-S ('93).
|-
| 3 || 6.0L || 60° V12 || Gas ||SOHC,&lt;br /&gt; 24 valve||MPI. [[w:Jaguar V12 engine|Jaguar V12]]. Jaguar XJS ('94-'95), XJ12 ('94-'96).
|-
| 5 || 3.6L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||N. America-spec - Low Compression. MPI. [[w:Jaguar AJ6 engine|Jaguar AJ6 I6]]. Jaguar XJ6 ('88-'89).
|-
| 6 || 3.6L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||N. America-spec - High Compression. MPI. [[w:Jaguar AJ6 engine|Jaguar AJ6 I6]]. Jaguar XJ6 ('88).
|-
| 7 || 4.0L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. [[w:Jaguar AJ6 engine|Jaguar AJ6 I6]]. Jaguar XJ6 ('90-'94), XJS ('93-'94).
|-
| 7 || 4.0L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. [[w:Jaguar AJ6 engine#AJ16|Jaguar AJ16 I6]]. Jaguar XJ6 ('95-'96), XJS ('95-'96).
|-
| 7 || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ26 V8 engine]]. Jaguar XK8 ('97).
|-
| 8 || 5.3L || 60° V12 || Gas ||SOHC,&lt;br /&gt; 24 valve||N. America-spec. MPI. [[w:Jaguar V12 engine|Jaguar V12]]. Jaguar XJ-S ('82-'92), XJ12 (Canada only: '88-'92).
|-
| 8 || 4.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Dual-canister evaporative emissions system. [[w:Jaguar AJ-V8 engine#Supercharged|Jaguar AJ-V8 - AJ26S V8 engine]]. Jaguar XJR ('98-'99).
|-
| 9 || 4.0L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||Canada-spec. MPI. [[w:Jaguar AJ6 engine|Jaguar AJ6 I6]]. Jaguar XJ6 ('90-'93), XJS ('93).
|-
| 0 || 5.3L || 60° V12 || Gas ||SOHC,&lt;br /&gt; 24 valve||Canada-spec. MPI. [[w:Jaguar V12 engine|Jaguar V12]]. Jaguar XJ-S ('82-'87), XJ12 (Canada only: '85-'87).
|-
| 0 || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. Dual-canister evaporative emissions system. Enhanced evaporative emissions control system. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ27 V8 engine]]. Jaguar XJ8 ('99), XK8 ('99).
|}

===Transmission &amp; Steering Location (Position 8):===
* 4 = Automatic / LHD
* 8 = Manual / LHD ('93-'94 XJS 4.0 w/ optional 5-spd. manual)

===Check Digit/Gearbox (Position 9)===
* USA /Canada [[Vehicle Identification Numbers (VIN codes)/Check digit|Check digit]]

===Model Year Code (Position 10)===
''See: [[Vehicle Identification Numbers (VIN codes)/Model year]]''

===Plant Codes (Position 11)===
* C - Browns Lane plant, Coventry, West Midlands, England, UK

===Positions 12–17, Serial Number===
** 100001 and after - XJ-S/XJ-SC/XJS/XJR-S (XJ27)
** 300001 and after - XJ-series sedan Series III
** 500001 and after - XJ-series sedan (XJ40/XJ81)
** 720001 and after - XJ-series sedan (X300/X305/X306/X330)
** 810001 and after - XJ-series sedan (X308)
** 001001 and after - XK8 (X100)</text>
      <sha1>5jbufen6acsarjy6tx9j3l1jvhjeupn</sha1>
    </revision>
    <revision>
      <id>4676690</id>
      <parentid>4676686</parentid>
      <timestamp>2026-10-18T05:19:58Z</timestamp>
      <contributor>
        <username>JustTheFacts33</username>
        <id>3434282</id>
      </contributor>
      <comment>/* Trim Level/Drive Wheels/Restraint System (Position 5) */</comment>
      <origin>4676690</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="42579" sha1="l8z4vh9jfzffuxn0s1257cky2p263cc" xml:space="preserve">{{Vehicle Identification Numbers (VIN codes)/Warning}}{{clear}}

This VIN number decoding and designation system is used primarily for the North American Market. European and Asian markets use other decoding and designation systems.

==General Template for Jaguar's VIN format (All models: 2016- EXCEPT F-Type '16-'17, XJ '16-'19)==

===Jaguar WMIs (2016-) (Position 1-3)===

* SAJ - Jaguar passenger car (UK)
* SAD - Jaguar SUV (UK &amp; Europe)
* L2C - Chery Jaguar Land Rover (China)

===Model Line (Position 4)===

{| class=&quot;wikitable&quot;
|+Position 4
!VIN code
!Description
|-
|A
|[[w:Jaguar XE|Jaguar XE]] ('17-'20)
|-
|B
|[[w:Jaguar XF (X260)|Jaguar XF]] ('16-'24)
|-
|C
|[[w:Jaguar F-Pace|Jaguar F-Pace]] ('17-'26)
|-
|D
|[[w:Jaguar F-Type|Jaguar F-Type]] ('18-'24)
|-
|E
|[[w:Jaguar Type 01|Jaguar Type 01]] ('28-)
|-
|F
|[[w:Jaguar E-Pace|Jaguar E-Pace]] ('18-'24)
|-
|H
|[[w:Jaguar I-Pace|Jaguar I-Pace EV]] ('19-'24)
|}

===Trim Level/Drive Wheels/Restraint System (Position 5)===

{| class=&quot;wikitable&quot;
|+Position 4
!VIN code
!Trim Level
!Drive Wheels
!Restraint System
|-
|D
|XF Premium '16-'17
|Rwd
|
|-
|E
|XF Prestige '16-'17
|Rwd
|
|-
|F
|XF R-Sport '16-'17
|Rwd
|
|-
|G
|XF S '16-'17
|Rwd
|
|-
|J
|XF Premium '16-'17
|Awd
|
|-
|K
|XF Prestige '16-'17
|Awd
|
|-
|L
|XF R-Sport '16-'17
|Awd
|
|-
|M
|XF S '16-'17
|Awd
|
|-
|N
|XF First Edition '16
|Awd
|
|-
|R
|XF Base model '17
|Rwd
|
|-
|S
|XF Base model '17
|Awd
|
|-
|}

===Body Style (Position 6):===
* 1 = Coupe (F-Type coupe)
* 2 = 5-door wagon (XF Sportbrake wagon '18-'20)
* 2 = 5-door (E-Pace, F-Pace, I-Pace EV)
* 4 = 4-door sedan (XE, XF sedan, Type 01)
* 5 = Convertible (F-Type convertible)

===Transmission (Position 7) 2016-2017:===
* B = Automatic (XE '17, XF '16-'17, F-Pace '17)

===Engine/Emissions Control System (Position 8) 2016-2017:===

{| class=&quot;wikitable&quot;
|+Position 8
! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications
|-
| G || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,&lt;br /&gt; 16 valve||Direct Injection. ULEV. Dual VVT. [[w:Ford EcoBoost engine#2.0 L (2010–2018)|Ford EcoBoost engine (Mazda L engine-based)]].&lt;br&gt; Jaguar XE 25t ('17).
|-
| N || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Diesel || DOHC,&lt;br /&gt; 16 valve||Common-rail Direct Injection. Exhaust VVT. [[w:Ingenium engine family|JLR Ingenium AJ20D engine]]. Jaguar XE 20d, XF 20d, F-Pace 20d ('17).
|-
| V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 35t ('16-'17) [If 5th pos. of VIN is NOT G or M]. Jaguar XE 35t ('17).&lt;br&gt; Jaguar F-Pace 35t ('17) [If 5th pos. of VIN is NOT M or P].
|-
| V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 380 PS/375 hp. Jaguar XF S ('16-'17) [If 5th pos. of VIN is G or M].&lt;br&gt; Jaguar F-Pace S ('17) [If 5th pos. of VIN is M or P].
|}

===Engine (Position 7-8) 2018-:===

{| class=&quot;wikitable&quot;
|+Position 7-8
! VIN Pos. 7 !! Power Level !! Transmission !! VIN Pos. 8 !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications
|-
| E || 550 PS/542 hp || 8-spd. Auto. || E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct injection. Dual Continuously VCT (VVT). [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133S engine]]. Jaguar F-Type R ('18-'20), F-Pace SVR ('19-'24).
|-
| E || 450 PS/444 hp || 8-spd. Auto. || E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct injection. Dual Continuously VCT (VVT). [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133S engine]]. Jaguar F-Type P450 ('22-24).
|-
| F || 575 PS/567 hp || 8-spd. Auto. || E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct injection. Dual Continuously VCT (VVT). [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133S engine]]. Jaguar F-Type SVR ('18-'20), F-Type R ('21-'24),&lt;br&gt; F-Pace SVR 575 Edition ('25-'26).
|-
| F || 600 PS/592 hp || 8-spd. Auto. || E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct injection. Dual Continuously VCT (VVT). [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133S engine]]. Jaguar XE SV Project 8 ('19).
|-
| F || 180 PS/178 hp || 8-spd. Auto. || N || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Diesel || DOHC,&lt;br /&gt; 16 valve||Common-rail Direct Injection. Exhaust VVT.&lt;br&gt; [[w:Ingenium engine family|JLR Ingenium AJ20D4/AJ200D engine]].&lt;br&gt; Jaguar XE 20d ('18-'19), XF 20d ('18-'19), F-Pace 20d ('18-'19).
|-
| E || 340 PS/335 hp || 8-spd. Auto. || U || 3.0L || I6 Turbo [[w:Intercooler|IC]] || Gas || DOHC,&lt;br /&gt; 24 valve||48v Mild Hybrid. E-supercharger. Direct Injection. Dual VVT.  CVVL (Intake VVL). [[w:Ingenium engine family|JLR Ingenium AJ20P6/AJ300P engine]].&lt;br&gt; Jaguar F-Pace P340 ('21-'22). 
|-
| F || 400 PS/395 hp || 8-spd. Auto. || U || 3.0L || I6 Turbo [[w:Intercooler|IC]] || Gas || DOHC,&lt;br /&gt; 24 valve||48v Mild Hybrid. E-supercharger. Direct Injection. Dual VVT.  CVVL (Intake VVL). [[w:Ingenium engine family|JLR Ingenium AJ20P6/AJ300P engine]].&lt;br&gt; Jaguar F-Pace P400 ('21-'26).
|-
| E || 340 PS/335 hp || 8-spd. Auto. || V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. Continuously variable intake &amp; exhaust valve timing.&lt;br&gt; [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; Jaguar XE 35t ('18), XF 35t ('18), F-Type ('18), F-Type P340 ('19-'20),&lt;br&gt; F-Pace 35t ('18).
|-
| F || 380 PS/375 hp || 8-spd. Auto. || V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. Continuously variable intake &amp; exhaust valve timing.&lt;br&gt; [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; Jaguar XE S ('18-'19), XF S ('18-'20), F-Type ('18),&lt;br&gt; F-Type P380 ('19), F-Type P380 R-Dynamic ('19-'21), F-Pace S ('18-'20).
|-
| G || 400 PS/395 hp || 8-spd. Auto. || V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. Continuously variable intake &amp; exhaust valve timing.&lt;br&gt; [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; Jaguar F-Type 400 Sport ('18).
|-
| J || 340 PS/335 hp || 6-spd. Man. || V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. Continuously variable intake &amp; exhaust valve timing.&lt;br&gt; [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; Jaguar F-Type ('18), F-Type P340 ('19).
|-
| K || 380 PS/375 hp || 6-spd. Man. || V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. Continuously variable intake &amp; exhaust valve timing.&lt;br&gt; [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; Jaguar F-Type P380 R-Dynamic ('18-'19).
|-
| E || 250 PS/247 hp || 8-spd. Auto. || X || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,&lt;br /&gt; 16 valve||Direct Injection. Dual VVT. CVVL (Intake VVL).&lt;br&gt; [[w:Ingenium engine family|JLR Ingenium AJ20P4/AJ200P engine]].&lt;br&gt; Jaguar F-Pace P250 ('21-'26).
|-
| F || 250 PS/247 hp || 8-spd. Auto. || X || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,&lt;br /&gt; 16 valve||Direct Injection. Dual VVT. CVVL (Intake VVL).&lt;br&gt; [[w:Ingenium engine family|JLR Ingenium AJ20P4/AJ200P engine]].&lt;br&gt; Jaguar XE 25t ('18-'20), XF 25t ('18-'20), XF P250 ('21-'24),&lt;br&gt; E-Pace P250 ('18-'24), F-Pace 25t ('18-'20).
|-
| G || 300 PS/296 hp || 8-spd. Auto. || X || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,&lt;br /&gt; 16 valve||Direct Injection. Dual VVT. CVVL (Intake VVL).&lt;br&gt; [[w:Ingenium engine family|JLR Ingenium AJ20P4/AJ200P engine]].&lt;br&gt; Jaguar XE 30t ('18-'20), XF 30t ('18-'20), XF P300 ('21-'24),&lt;br&gt; F-Type ('18), F-Type P300 ('19-'21), E-Pace P300 R-Dynamic ('18-'20),&lt;br&gt; E-Pace 300 Sport ('21-'22), F-Pace 30t ('18-'20). 
|}

====Motor Type for Electric Vehicles 2019-====

{| class=&quot;wikitable&quot;
|+Position 7-8
|-
! VIN Pos. 7 !! Power Level !! Transmission !! VIN Pos. 8 !! # of Motors !! Battery Size !! Battery Type !! Fuel !! Drive Wheels !! Notes/Applications
|-
| S || 400 PS/394 hp || 1-spd. Auto. || 1 || 2 || 90 Kwh || Lithium-ion || Electricity || All || Jaguar I-Pace EV400 ('19-'24).
|-
| T || 1029 PS/1015 hp || 1-spd. Auto. || 1 || 3 &lt;br&gt; (1 Front,&lt;br&gt; 2 Rear) || 118 Kwh || Lithium-ion || Electricity || All || Jaguar Type 01 ('28-).
|}

===Check Digit/Gearbox (Position 9)===
* USA /Canada [[Vehicle Identification Numbers (VIN codes)/Check digit|Check digit]]

===Model Year Code (Position 10)===
''See: [[Vehicle Identification Numbers (VIN codes)/Model year]]''

===Plant Codes (Position 11) 2016-===
* A - Solihull, West Midlands, England, UK (XE '17, F-Pace '17-'26, Type 01 '28-)
* C - Castle Bromwich, West Midlands, England, UK (XE '17-'20, XF '16-'24, F-Type '18-'24)
* S - Oxford Road plant, Ryton, West Midlands, England, UK (JLR SVO plant) (XE SV Project 8 '19)
* 1 - Graz, Austria (Magna Steyr plant) (E-Pace '18-'24, I-Pace EV '19-'24)

===Model (Position 12)===
* 9 - XE ('17) [Solihull plant]
* P - XE ('17-'20) [Castle Bromwich plant]
* Y - XF ('16-'24)
* K - F-Type ('18-'24)
* Z - E-Pace ('18-'20)
* 0 - E-Pace ('20-'24)
* F - I-Pace EV ('19-'20)
* 6 - I-Pace EV ('20-'24)

'''Positions 13–17, Serial Number'''

==General Template for Jaguar's VIN format (All models: 2000-2015 plus F-Type '16-'17, XJ '16-'19)==

===Jaguar WMIs (2000-) (Position 1-3)===

* SAJ - Jaguar passenger car (UK)
* SAD - Jaguar SUV (UK &amp; Europe)

===Regional Spec/Restraint System (Position 4):===
* J = Manual seat belts, Dual front airbags (US: XK8 '00)
* B = Manual seat belts, Dual front airbags (Canada: XK8 '00)
* D = Manual seat belts, Depowered Dual front airbags, &amp; Front Side Airbags (US: S-Type '00-'02, XJ8/XJR '00-'03, XK8/XKR '01-'06, XK/XKR Early '07)
* F = Manual seat belts, Depowered Dual front airbags, &amp; Front Side Airbags (Canada: S-Type '00-'02, XJ8/XJR '00-'03, XK8/XKR '01-'06, XK/XKR Early '07)
* E = Manual seat belts, Depowered Dual front airbags w/occupant position sensing, &amp; Front Side Airbags &amp; Side Curtain Airbags (US: X-Type '02-'04, S-Type '03-'04, XJ8/XJR Early '04)
* G = Manual seat belts, Depowered Dual front airbags w/occupant position sensing, &amp; Front Side Airbags &amp; Side Curtain Airbags (Canada: X-Type '02-'04,&lt;br&gt; S-Type '03-'04, XJ8/XJR Early '04)
* W = Manual seat belts, Depowered Dual front airbags w/occupant position (driver) and weight (fr. psgr.) sensing, &amp; Front Side Airbags &amp; Side Curtain Airbags &lt;br&gt; (US: X-Type '05-'08, S-Type '05-'08, XF '09-'15,  XJ8/XJR '04-'09, XJ '10-)
* X = Manual seat belts, Depowered Dual front airbags w/occupant position (driver) and weight (fr. psgr.) sensing, &amp; Front Side Airbags &amp; Side Curtain Airbags (Canada: X-Type '05-'08, S-Type '05-'08, XF '09-'15, XJ8/XJR '04-'09, XJ '10-)
* W = Manual seat belts, Depowered Dual front airbags w/occupant position (driver) and weight (fr. psgr.) sensing, &amp; Front Side Head/Thorax Airbags &lt;br&gt; (US: XK/XKR '07-'15, F-Type '14-)
* X = Manual seat belts, Depowered Dual front airbags w/occupant position (driver) and weight (fr. psgr.) sensing, &amp; Front Side Head/Thorax Airbags &lt;br&gt; (Canada: XK/XKR '07-'15, F-Type '14-)

===Transmission &amp; Steering Location (Position 5 - '00-'12):===
* A = Automatic / LHD
* B = Manual / LHD (X-Type '02-'05, S-Type 3.0 '03-'04)

===Transmission &amp; Drive Wheels (Position 5 - '13-):===
* A = Automatic / Rwd (XF '13-'15, XJ '13-'19, XK '13-'15, F-Type '14-'17)
* B = Manual / Rwd (F-Type '16-'17)
* J = Automatic / Awd (XF Awd '13-'15, XJ Awd '13-'19, F-Type Awd '16-'17)

===Model Line (Position 6-7)===

{| class=&quot;wikitable&quot;
|+Position 6-7
!VIN code
!Description
|-
|51
|[[w:Jaguar X-Type|Jaguar X-Type sedan - High Series]] ('02-'08)
|-
|52
|[[w:Jaguar X-Type|Jaguar X-Type sedan - Entry Series]] ('03-'04)
|-
|53
|[[w:Jaguar X-Type|Jaguar X-Type sedan w/Sport Package]] ('02-'03)
|-
|54
|[[w:Jaguar X-Type|Jaguar X-Type Sportwagon]] ('05-'08)
|-
|01
|[[w:Jaguar S-Type (1999)|Jaguar S-Type]] ('00-'08)
|-
|03
|[[w:Jaguar S-Type (1999)|Jaguar S-Type Sport]] [3.0, 4.0] ('02)
|-
|03
|[[w:Jaguar S-Type (1999)|Jaguar S-Type Sport]] [3.0, 4.2] ('03)
|-
|03
|[[w:Jaguar S-Type (1999)|Jaguar S-Type R]] ('03-'08)
|-
|05
|[[w:Jaguar XF (X250)|Jaguar XF Luxury]] ('09)
|-
|06
|[[w:Jaguar XF (X250)|Jaguar XF Premium Luxury]] ('09)
|-
|07
|[[w:Jaguar XF (X250)|Jaguar XF Supercharged]] ('09)
|-
|0E
|[[w:Jaguar XF (X250)|Jaguar XF]] ('13-'14)
|-
|0F
|[[w:Jaguar XF (X250)|Jaguar XF]] ('10-'12)
|-
|0F
|[[w:Jaguar XF (X250)|Jaguar XF 2.0T Premium]] [8th pos. of VIN is S] ('15)
|-
|0F
|[[w:Jaguar XF (X250)|Jaguar XF 3.0 Sport Rwd or 3.0 Portfolio Rwd]] [8th pos. of VIN is 7] ('15)
|-
|0F
|[[w:Jaguar XF (X250)|Jaguar XF 3.0 Sport Awd or 3.0 Portfolio Awd]] [8th pos. of VIN is F] ('15)
|-
|0G
|[[w:Jaguar XF (X250)|Jaguar XF Premium]] ('10-'11)
|-
|0H
|[[w:Jaguar XF (X250)|Jaguar XF Portfolio]] [8th pos. of VIN is B] ('12)
|-
|0H
|[[w:Jaguar XF (X250)|Jaguar XF Supercharged]] [8th pos. of VIN is E: '10-'13 or P: '13-'15]
|-
|0J
|[[w:Jaguar XF (X250)|Jaguar XFR]] ('10-'15)
|-
|0K
|[[w:Jaguar XF (X250)|Jaguar XFR-S]] ('13-'15)
|-
|8J
|[[w:Jaguar XF (X250)|Jaguar XFR w/Speed Pack]] ('13-'15)
|-
|12
|[[w:Jaguar XJ (X308)#Sport|Jaguar XJ Sport]] ('02-'03)
|-
|14
|[[w:Jaguar XJ (X308)|Jaguar XJ8]] ('00-'03)
|-
|15
|[[w:Jaguar XJ (X308)#XJR|Jaguar XJR]] ('00-'03)
|-
|23
|[[w:Jaguar XJ (X308)|Jaguar XJ8L]] (LWB) ('00-'01)
|-
|24
|[[w:Jaguar XJ (X308)#Daimler/Vanden Plas|Jaguar XJ8 Vanden Plas]] (LWB) ('00-'03)
|-
|25
|[[w:Jaguar XJ (X308)#Daimler/Vanden Plas|Jaguar XJ8 Vanden Plas Supercharged]] (LWB) ('00-'01)
|-
|25
|[[w:Jaguar XJ (X308)#Daimler/Vanden Plas|Jaguar XJ Super V8]] (LWB) ('02-'03)
|-
|71
|[[w:Jaguar XJ (X350)|Jaguar XJ8]] ('04-'09)
|-
|73
|[[w:Jaguar XJ (X350)|Jaguar XJR]] ('04-'09)
|-
|74
|[[w:Jaguar XJ (X350)|Jaguar XJ8 Vanden Plas]] (SWB) ('04)
|-
|79
|[[w:Jaguar XJ (X350)|Jaguar XJ8L]] (LWB) ('05-'09)
|-
|82
|[[w:Jaguar XJ (X350)|Jaguar XJ8 Vanden Plas]] (LWB) ('05-'09)
|-
|82
|[[w:Jaguar XJ (X350)|Jaguar XJ Super V8]] (LWB, 5-psgr.) ('05-'09)
|-
|86
|[[w:Jaguar XJ (X350)|Jaguar XJ Super V8 Portfolio]] (LWB, 4-psgr.) ('06)
|-
|94
|[[w:Jaguar XJ (X350)|Jaguar XJ Super V8 Portfolio]] (LWB, 5-psgr.) ('09)
|-
|1C
|[[w:Jaguar XJ (X351)|Jaguar XJ]] ('10-'15)
|-
|1C
|[[w:Jaguar XJ (X351)|Jaguar XJ R-Sport]] [8th pos. of VIN is 7 (Rwd) or D (Awd)] ('16-'19)
|-
|1C
|[[w:Jaguar XJ (X351)|Jaguar XJ Supercharged]] [8th pos. of VIN is E] ('16-'19)
|-
|1E
|[[w:Jaguar XJ (X351)|Jaguar XJR]] ('14-'17)
|-
|1G
|[[w:Jaguar XJ (X351)|Jaguar XJ Supercharged]] [8th pos. of VIN is E: '10-'13 or T: '13-'15]
|-
|1J
|[[w:Jaguar XJ (X351)|Jaguar XJ Supersport]] ('11-'12)
|-
|2E
|[[w:Jaguar XJ (X351)|Jaguar XJR LWB]] ('14-'17), XJR575 LWB ('18-'19)
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL]] [8th pos. of VIN is B] ('10-'11)
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL Portfolio Rwd]] [8th pos. of VIN is B: '12-'13 or 1: '13]
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL Portfolio Rwd]] [8th pos. of VIN is Z: '14-'15)
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL Portfolio Rwd]] [8th pos. of VIN is 7: '16-'19), XJ50 3.0 Rwd (LWB) '19
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL Portfolio Awd]] [8th pos. of VIN is D] ('13-'19), XJ50 3.0 Awd (LWB) '19
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL Supercharged]] [8th pos. of VIN is E: '10-'13, '16-'19 or T: '13-'15], XJ50 5.0 Rwd (LWB) '19, XJ Collection (LWB) '19
|-
|2J
|[[w:Jaguar XJ (X351)|Jaguar XJL Supersport]] ('11-'13)
|-
|2K
|[[w:Jaguar XJ (X351)|Jaguar XJL Ultimate]] ('13)
|-
|3F
|[[w:Jaguar XJ (X351)|Jaguar XJ Supersport w/Speed Pack]] ('12-'13)
|-
|3G
|[[w:Jaguar XJ (X351)|Jaguar XJL Supersport w/Speed Pack]] ('12-'13)
|-
|3H
|[[w:Jaguar XJ (X351)|Jaguar XJ Supercharged w/Sport &amp; Speed Pack]] ('12-'15)
|-
|3K
|[[w:Jaguar XJ (X351)|Jaguar XJL Supercharged w/Sport &amp; Speed Pack]] ('12-'15)
|-
|41
|[[w:Jaguar XK (X100)|Jaguar XK8/XKR coupe]] ('00-'06)
|-
|42
|[[w:Jaguar XK (X100)|Jaguar XK8/XKR convertible]] ('00-'06)
|-
|43
|[[w:Jaguar XK (X150)|Jaguar XK/XKR coupe]] ('07-'09)
|-
|44
|[[w:Jaguar XK (X150)|Jaguar XK/XKR convertible]] ('07-'09)
|-
|45
|[[w:Jaguar XK (X150)|Jaguar XKR Portfolio Edition coupe]] ('09)
|-
|46
|[[w:Jaguar XK (X150)|Jaguar XKR Portfolio Edition convertible]] ('09)
|-
|4D
|[[w:Jaguar XK (X150)|Jaguar XK Touring coupe]] [8th pos. of VIN is B] ('13-'14)
|-
|4E
|[[w:Jaguar XK (X150)|Jaguar XK Touring convertible]] [8th pos. of VIN is B] ('13-'14)
|-
|4D
|[[w:Jaguar XK (X150)|Jaguar XKR coupe]] [8th pos. of VIN is C] ('10-'15)
|-
|4E
|[[w:Jaguar XK (X150)|Jaguar XKR convertible]] [8th pos. of VIN is C] ('10-'15)
|-
|4F
|[[w:Jaguar XK (X150)|Jaguar XK coupe]] (most Portfolio Edition features are std.) [8th pos. of VIN is B] ('10-'15)
|-
|4F
|[[w:Jaguar XK (X150)|Jaguar XKR175 coupe]] [8th pos. of VIN is C] ('11)
|-
|4F
|[[w:Jaguar XK (X150)|Jaguar XKR coupe w/Dynamic Pack]] [8th pos. of VIN is C] ('13-'15), XK Final Fifty Edition coupe ('15)
|-
|4G
|[[w:Jaguar XK (X150)|Jaguar XK convertible]] (most Portfolio Edition features are std.) [8th pos. of VIN is B] ('10-'15)
|-
|4G
|[[w:Jaguar XK (X150)|Jaguar XKR convertible w/Dynamic Pack]] [8th pos. of VIN is C] ('13-'15), XK Final Fifty Edition convertible ('15)
|-
|4H
|[[w:Jaguar XK (X150)|Jaguar XKR-S coupe]] ('12-'15), XKR-S GT coupe ('14)
|-
|4J
|[[w:Jaguar XK (X150)|Jaguar XKR-S convertible]] ('12-'15)
|-
|6A
|[[w:Jaguar F-Type)|Jaguar F-Type coupe]] ('15-'17), F-Type Premium coupe '17
|-
|6B
|[[w:Jaguar F-Type)|Jaguar F-Type S coupe]] ('15-'17), F-Type S British Design Edition coupe '17
|-
|6D
|[[w:Jaguar F-Type)|Jaguar F-Type R coupe]] ('15-'17)
|-
|6E
|[[w:Jaguar F-Type)|Jaguar F-Type convertible]] ('14-'17), F-Type Premium convertible '17
|-
|6F
|[[w:Jaguar F-Type)|Jaguar F-Type S convertible]] ('14-'17), F-Type S British Design Edition convertible '17
|-
|6G
|[[w:Jaguar F-Type)|Jaguar F-Type V8 S convertible]] ('14-'15)
|-
|6H
|[[w:Jaguar F-Type)|Jaguar F-Type R convertible]] ('16-'17)
|-
|6J
|[[w:Jaguar F-Type)|Jaguar F-Type SVR coupe]] ('17)
|-
|6K
|[[w:Jaguar F-Type)|Jaguar F-Type SVR convertible]] ('17)
|-
|7A
|[[w:Jaguar F-Type#Project 7)|Jaguar F-Type Project 7 convertible]] ('16)
|}

===Engine/Emissions Control System (Position 8)===

{| class=&quot;wikitable&quot;
|+Position 8
! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications
|-
| A || 3.0L || 60° V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. ULEV. Variable intake valve timing. [[w:Jaguar AJ-V6 engine#AJ30|Jaguar AJ-V6 - AJ30 V6 engine]].&lt;br&gt; Jaguar X-Type 3.0 (Mid '05-'08), S-Type 3.0 ('06-'08). 
|-
| A || 4.2L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. ULEV. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.2 L|Jaguar AJ-V8 - AJ34 V8 engine]]. Jaguar XF ('10).
|-
| A || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 550 PS/542 hp. Jaguar XKR-S ('12-'15), XKR-S GT ('14), F-Type R coupe ('15).
|-
| B || 4.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. [[w:Jaguar AJ-V8 engine#Supercharged|Jaguar AJ-V8 - AJ27S V8 engine]].&lt;br&gt; Jaguar XJR ('00-'03), Vanden Plas Supercharged ('00-'01), Super V8 ('02-'03), XKR ('00-'02).
|-
| B || 4.2L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. [[w:Jaguar AJ-V8 engine#Supercharged_2|Jaguar AJ-V8 - AJ33S V8 engine]]. Jaguar XJR ('04-'05), Super V8 ('05), XKR ('03-'06).
|-
| B || 4.2L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. ULEV. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.2 L|Jaguar AJ-V8 - AJ34 V8 engine]].&lt;br&gt; Jaguar S-Type ('06-'08), XF ('09), XJ8/Vanden Plas ('06-'09), XK ('07-'09).
|-
| B || 5.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. Variable intake valve lift. Variable intake.&lt;br&gt; [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; Jaguar XF ('10-'12), XJ ('11-'12), XJL ('11), XJL Portfolio Rwd ('12-'13), XK ('10-'15), XK Touring ('13-'14).
|-
| C || 3.0L || 60° V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. Variable intake valve timing. [[w:Jaguar AJ-V6 engine#AJ30|Jaguar AJ-V6 - AJ30 V6 engine]].&lt;br&gt; Jaguar S-Type 3.0 ('00-'01), X-Type 3.0 ('02-Mid '05). 
|-
| C || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ27 V8 engine]].&lt;br&gt; Jaguar XJ8/Vanden Plas ('00-'03), XJ Sport ('02-'03), XK8 ('00-'02).
|-
| C || 4.2L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.2 L|Jaguar AJ-V8 - AJ33 V8 engine]]. Jaguar XJ8 ('04-'05), XK8 ('03-'06).
|-
| C || 4.2L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. ULEV. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#Supercharged_2|Jaguar AJ-V8 - AJ34S V8 engine]].&lt;br&gt; Jaguar S-Type R ('06-'08), XF Supercharged ('09), XJR ('06-'09), Super V8 ('06-'09), XKR ('07-'09).
|-
| C || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 510 PS/503 hp. Jaguar XFR ('10-'13), XJ/XJL Supersport ('11-'13), XKR ('10-'15).
|-
| C || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 380 PS/375 hp. Jaguar F-Type S ('14-'15), F-Type S w/man. trans. ('16-'17).
|-
| D || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ28 V8 engine]]. Jaguar S-Type 4.0 ('00-'01).
|-
| D || 2.5L || 60° V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. Variable intake valve timing. [[w:Jaguar AJ-V6 engine#AJ25|Jaguar AJ-V6 - AJ25 V6 engine]]. Jaguar X-Type 2.5 ('02-'05).
|-
| D || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XJ Awd, XJL Portfolio Awd ('13-'15).
|-
| D || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XJ R-Sport Awd, XJL Portfolio Awd ('16-'19), XJ50 3.0 Awd ('19).
|-
| E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 470 PS/464 hp.&lt;br&gt; Jaguar XF Supercharged ('10-'13), XJ/XJL Supercharged ('11-'13, '16-'19), XJ50 5.0 Rwd ('19), XJ Collection ('19).
|-
| F || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 3.0 Awd ('13-'14).
|-
| F || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 3.0 Awd ('15).
|-
| H || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,&lt;br /&gt; 32 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]]. 510 PS/503 hp. Jaguar XFR ('13-'15).
|-
| K || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 550 PS/542 hp. Jaguar XJR/XJR LWB ('14-'17).
|-
| K || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 575 PS/567 hp. Jaguar XJR575 LWB ('18-'19).
|-
| L || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 495 PS/488 hp. Jaguar F-Type V8 S convertible ('14-'15).
|-
| L || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 550 PS/542 hp. Jaguar F-Type R  ('16-'17).
|-
| N || 3.0L || 60° V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. Variable intake valve timing. [[w:Jaguar AJ-V6 engine#AJ30|Jaguar AJ-V6 - AJ30 V6 engine]]. Jaguar S-Type 3.0 ('01-'02).
|-
| P || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ28 V8 engine]]. Jaguar S-Type 4.0 ('01-'02).
|-
| P || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,&lt;br /&gt; 32 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]]. 470 PS/464 hp. Jaguar XF Supercharged ('13-'15).
|-
| S || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,&lt;br /&gt; 16 valve||Direct Injection. Dual VVT. [[w:Ford EcoBoost engine#2.0 L (2010–2018)|Ford EcoBoost engine (Mazda L engine-based)]].&lt;br&gt; Jaguar XF 2.0T ('13-'14), XF 2.0T Premium ('15).
|-
| T || 3.0L || 60° V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. Variable intake valve timing. [[w:Jaguar AJ-V6 engine#AJ30|Jaguar AJ-V6 - AJ30 V6 engine]]. Jaguar S-Type 3.0 ('03-'05).
|-
| T || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,&lt;br /&gt; 32 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]]. 470 PS/464 hp. Jaguar XJ/XJL Supercharged ('13-'15).
|-
| T || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar F-Type w/auto. trans. ('15-'17), F-Type Premium w/auto. trans. ('17).
|-
| U || 4.2L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.2 L|Jaguar AJ-V8 - AJ33 V8 engine]]. Jaguar S-Type 4.2 ('03-'05).
|-
| U || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 380 PS/375 hp. Jaguar F-Type S ('15), F-Type S Rwd w/auto. trans. ('16-'17).
|-
| V || 4.2L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. [[w:Jaguar AJ-V8 engine#Supercharged_2|Jaguar AJ-V8 - AJ33S V8 engine]]. Jaguar S-Type R ('03-'05).
|-
| V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 380 PS/375 hp. Jaguar F-Type S Awd w/auto. trans. ('16-'17).
|-
| X || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,&lt;br /&gt; 24 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 3.0 Rwd ('14).
|-
| Z || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 550 PS/542 hp. Jaguar XFR-S ('13-'15).
|-
| Z || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,&lt;br /&gt; 24 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XJ Rwd, XJL Portfolio Rwd ('14-'15).
|-
| 1 || 5.0L || V8 || Gas/E85 ||DOHC,&lt;br /&gt; 32 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. Variable intake valve lift. Variable intake. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]]. Jaguar XJL Portfolio Rwd ('13).
|-
| 6 || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar F-Type w/man. trans. ('16-'17), F-Type Premium w/man. trans. ('17).
|-
| 7 || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 3.0 Rwd ('13), XJ Rwd ('13), F-Type ('14-'15).
|-
| 7 || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 3.0 Rwd ('15), XJ R-Sport Rwd ('16-'19), XJL Portfolio Rwd ('16-'19), XJ50 3.0 Rwd ('19).
|-
| 8 || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 575 PS/567 hp. Jaguar F-Type Project 7 ('16), F-Type SVR ('17).
|}

===Check Digit/Gearbox (Position 9)===
* USA /Canada [[Vehicle Identification Numbers (VIN codes)/Check digit|Check digit]]

===Model Year Code (Position 10)===
''See: [[Vehicle Identification Numbers (VIN codes)/Model year]]''

===Plant Code/Model Line/Engine (Position 11) 2000-2019===
* X - Halewood, Merseyside, England, UK - X-Type 2.5 ('02-'05)
* W - Halewood, Merseyside, England, UK - X-Type 3.0 ('02-'08)
* F - Castle Bromwich, West Midlands, England, UK - S-Type 3.0 ('00-'08)
* G - Castle Bromwich, West Midlands, England, UK - S-Type 4.0 ('00-'02)
* H - Castle Bromwich, West Midlands, England, UK - S-Type 4.2 ('03-'08)
* 1 - Castle Bromwich, West Midlands, England, UK - S-Type R (4.2 supercharged) ('03-'08)
* H - Castle Bromwich, West Midlands, England, UK - XF 4.2 ('09-'10)
* 1 - Castle Bromwich, West Midlands, England, UK - XF Supercharged (4.2 supercharged) ('09)
* L - Castle Bromwich, West Midlands, England, UK - XF 5.0 ('10-'12)
* M - Castle Bromwich, West Midlands, England, UK - XF Supercharged, XFR (5.0 supercharged) ('10-'15), XFR-S (5.0 supercharged) ('13-'15)
* P - Castle Bromwich, West Midlands, England, UK - XF 2.0T ('13-'15)
* 8 - Castle Bromwich, West Midlands, England, UK - XF 3.0 supercharged ('13-'15)
* L - Browns Lane plant, Coventry, West Midlands, England, UK - XJ8 (4.0) ('00-'03), XJ8L (4.0) ('00-'01), XJ8 Vanden Plas (4.0) ('00-'03), XJ Sport (4.0) ('02-'03)
* M - Browns Lane plant, Coventry, West Midlands, England, UK - XJ8 Vanden Plas Supercharged (4.0 supercharged) ('00-'01),&lt;br&gt; Super V8 (4.0 supercharged) ('02-'03), XJR (4.0 supercharged) ('00-'03)
* S - Browns Lane plant, Coventry, West Midlands, England, UK - XJ8 (4.2) ('04-'06), XJ8L (4.2) ('05-'06), XJ8 Vanden Plas (4.0) ('04-'06)
* T - Browns Lane plant, Coventry, West Midlands, England, UK - Super V8 (4.2 supercharged) ('05-'06), Super V8 Portfolio (4.2 supercharged) ('06),&lt;br&gt; XJR (4.2 supercharged) ('04-'06)
* S - Castle Bromwich, West Midlands, England, UK - XJ8 (4.2) ('07-'09), XJ8L (4.2) ('07-'09), XJ8 Vanden Plas (4.0) ('07-'09)
* T - Castle Bromwich, West Midlands, England, UK - Super V8 (4.2 supercharged) ('07-'09), Super V8 Portfolio (4.2 supercharged) ('09),&lt;br&gt; XJR (4.2 supercharged) ('07-'09)
* L - Castle Bromwich, West Midlands, England, UK - XJ (5.0) ('10-'12), XJL (5.0) ('10-'11), XJL Portfolio (5.0) ('12-'13)
* M - Castle Bromwich, West Midlands, England, UK - XJ/XJL Supercharged (5.0 supercharged) ('10-'19), XJ/XJL Supersport (5.0 supercharged) ('11-'13),&lt;br&gt; XJL Ultimate (5.0 supercharged) ('13), XJR SWB/LWB (5.0 supercharged) ('14-'17), XJR575 LWB (5.0 supercharged) ('18-'19), XJ50 LWB (5.0 supercharged) ('19), XJ Collection Sp. Ed. LWB (5.0 supercharged) ('19)
* 8 - Castle Bromwich, West Midlands, England, UK - XJ base (3.0 supercharged) ('13-'15), XJ R-Sport (3.0 supercharged) ('16-'19),&lt;br&gt; XJL Portfolio AWD (3.0 supercharged) ('13-'19), XJL Portfolio RWD (3.0 supercharged) ('14-'19), XJ50 LWB (3.0 supercharged) ('19)
* N - Browns Lane plant, Coventry, West Midlands, England, UK - XK8 (4.0) ('00-'02)
* P - Browns Lane plant, Coventry, West Midlands, England, UK - XKR (4.0 supercharged) ('00-'02)
* 2 - Browns Lane plant, Coventry, West Midlands, England, UK - XK8 (4.2) ('03-'06)
* 3 - Browns Lane plant, Coventry, West Midlands, England, UK - XKR (4.2 supercharged) ('03-'06)
* 5 - Castle Bromwich, West Midlands, England, UK - XK (4.2) ('07-'09)
* 9 - Castle Bromwich, West Midlands, England, UK - XKR (4.2 supercharged) ('07-'09)
* L - Castle Bromwich, West Midlands, England, UK - XK (5.0) ('10-'15)
* M - Castle Bromwich, West Midlands, England, UK - XKR (5.0 supercharged) ('10-'15), XKR-S (5.0 supercharged) ('12-'15), XKR-S GT (5.0 supercharged) ('14)
* 8 - Castle Bromwich, West Midlands, England, UK - F-Type Base, S (3.0 supercharged) ('14-'17), F-Type Premium (3.0 supercharged) ('17)
* M - Castle Bromwich, West Midlands, England, UK - F-Type V8S (5.0 supercharged) ('14-'15), F-Type R (5.0 supercharged) ('15-'17),&lt;br&gt; F-Type Project 7 (5.0 supercharged) ('16), F-Type SVR (5.0 supercharged) ('17)

===Model (Position 12)===
* C - X-Type ('02-'03)
* D - X-Type ('03-'04)
* E - X-Type ('04-'06)
* J - X-Type ('06-'08)
* L - S-Type ('00-'01)
* M - S-Type ('01-'04)
* N - S-Type ('04-'08)
* R - XF ('09-'11)
* S - XF ('11-'13)
* U - XF ('13-'15)
* F - XJ ('00-'03)
* G - XJ ('04-'06) [Browns Lane plant]
* H - XJ ('06-'09) [Castle Bromwich plant]
* V - XJ ('10-'16)
* W - XJ ('16-'19)
* A - XK ('00-'06)
* B - XK ('07-'15)
* K - F-Type ('14-'17)

'''Positions 13–17, Serial Number'''

==General Template for Jaguar's VIN format (1981 - 1999)==

===Jaguar WMIs (1981-1999) (Position 1-3)===
* SAJ - Jaguar passenger car

===Model Line (Position 4)===

{| class=&quot;wikitable&quot;
|+Position 4
!VIN code
!Description
|-
|A
|[[w:Jaguar XJ#Series 3 (1979–1992)|Jaguar XJ6]] ('81-'87), XJ6 Vanden Plas ('82-'87)
|-
|B
|[[w:Jaguar XJ#Series 3 (1979–1992)|Jaguar XJ12]] (Canada only: '81-'88)
|-
|D
|[[w:Jaguar XJ#Series 3 (1979–1992)|Jaguar XJ12]] (Canada only: '89-'92)
|-
|H
|[[w:Jaguar XJ (XJ40)|Jaguar XJ6]] ('88-'89, '93-'94)
|-
|F
|[[w:Jaguar XJ (XJ40)|Jaguar XJ6]] ('90-'92)
|-
|H
|[[w:Jaguar XJ (XJ40)|Jaguar XJ6 Sovereign]] ('90-'92)
|-
|K
|[[w:Jaguar XJ (XJ40)#Daimler/Vanden Plas|Jaguar XJ6 Vanden Plas]] ('88-'94)
|-
|M
|[[w:Jaguar XJ (XJ40)#Majestic (1989–1992 – SWB; 1993–1994 – LWB)|Jaguar XJ6 Vanden Plas Majestic]] ('89-'90, '92)
|-
|M
|[[w:Jaguar XJ (XJ40)#XJ12 and Daimler Double Six (XJ81)|Jaguar XJ12]] ('94)
|-
|H
|[[w:Jaguar XJ (X300)|Jaguar XJ6]] ('95-'97)
|-
|H
|[[w:Jaguar XJ (X300)|Jaguar XJ6L]] LWB [X330] ('97)
|-
|K
|[[w:Jaguar XJ (X300)#Daimler/Jaguar Vanden Plas|Jaguar XJ6 Vanden Plas]] SWB ('95)
|-
|K
|[[w:Jaguar XJ (X300)#Daimler/Jaguar Vanden Plas|Jaguar XJ6 Vanden Plas]] LWB [X330] ('96-'97)
|-
|M
|[[w:Jaguar XJ (X300)#XJ12 (X305)|Jaguar XJ12]] SWB ('95)
|-
|M
|[[w:Jaguar XJ (X300)#XJ12 (X305)|Jaguar XJ12]] LWB [X330] ('96)
|-
|P
|[[w:Jaguar XJ (X300)#XJR (X306)|Jaguar XJR]] ('95-'97)
|-
|H
|[[w:Jaguar XJ (X308)|Jaguar XJ8]] ('98-'99)
|-
|H
|[[w:Jaguar XJ (X308)|Jaguar XJ8L]] LWB ('98-'99)
|-
|K
|[[w:Jaguar XJ (X308)#Daimler/Vanden Plas|Jaguar XJ8 Vanden Plas]] LWB ('98-'99)
|-
|P
|[[w:Jaguar XJ (X308)#XJR|Jaguar XJR]] ('98-'99)
|-
|N
|[[w:Jaguar XJS|Jaguar XJ-S]] ('82-'91), XJ-SC ('86-'88), XJS ('92-'96)
|-
|T
|[[w:Jaguar XJS|Jaguar XJ-S]] Rouge Collection ('89-'90), Classic Collection ('90-'91)
|-
|S
|[[w:Jaguar XJS#XJR-S|Jaguar XJR-S]] ('93)
|-
|G
|[[w:Jaguar XK (X100)|Jaguar XK8]] ('97-'99)
|}

===Class (Regional Spec)/Restraint System (Position 5):===
* V = N. American-spec (Manual seat belts)
* L = Canadian-spec (Manual seat belts)

* Y = XJ6 Vanden Plas [Series III] ('82-'87) (Manual seat belts)

* A = Motorized Shoulder Belts (XJ-S coupe '88-'89, XJ-SC '88)
* Y = Motorized Shoulder Belts (XJ-S coupe '89, XJ sedan '89-'92)
* W = Manual seat belts, Driver-side airbag (US: XJ-S '90-'93, XJ6 '93, XJ12 Early '94)
* X = Manual seat belts, Dual front airbags (US: XJS '94-'96, XJ6 '94-'97, XJ12 '94-'96, XJR '95-'97, XK8 '97-'99)
* X = Manual seat belts, Dual front airbags, &amp; Front Side Airbags (US: XJ8/XJR '98-'99)
* D = Manual seat belts, Depowered Dual front airbags, &amp; Front Side Airbags (US: XJ8/XJR '99)
* M = Manual seat belts, Driver-side airbag (Canada)
* N = Manual seat belts, Dual front airbags (Canada)
* F = Manual seat belts, Depowered Dual front airbags, &amp; Front Side Airbags (Canada: XJ8/XJR '99)

===Body Style (Position 6):===
* 1 = 4-door sedan (XJ-series sedan '81-'99)
* 2 = 2-door convertible w/2+2 seating (XJS convertible '94-'96, XK8 convertible '97-'99)
* 3 = 2-door Cabriolet (XJ-SC '86-'88)
* 4 = 2-door convertible w/2-psgr. seating (factory-built XJS convertible '89-'94, XJR-S convertible '93)
* 5 = 2-door coupe (XJS coupe '82-'96, XJR-S coupe '93, XK8 coupe '97-'99)
* 5 = 2-door coupe (Hess &amp; Eisenhardt-built XJS convertible '87-'88) [coupe conversion]

===Engine Type (Position 7):===
{| class=&quot;wikitable&quot;
|+Position 7
|-
! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications
|-
| 1 || 4.0L || I6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. [[w:Jaguar AJ6 engine#AJ16S|Jaguar AJ16S I6]]. Jaguar XJR ('95-'97).
|-
| 2 || 4.2L || I6 || Gas ||DOHC,&lt;br /&gt; 12 valve||CA &amp; Canada-spec. MPI. [[w:Jaguar XK engine|Jaguar XK I6]]. Jaguar XJ6 ('81-'82).
|-
| 2 || 4.0L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. Dual-canister evaporative emissions system. [[w:Jaguar AJ6 engine#AJ16|Jaguar AJ16 I6]]. Jaguar XJ6 ('96-'97).
|-
| 2 || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Variable intake valve timing. Dual-canister evaporative emissions system. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ26 V8 engine]].&lt;br&gt; Jaguar XJ8 ('98), XK8 ('98).
|-
| 3 || 4.2L || I6 || Gas ||DOHC,&lt;br /&gt; 12 valve||N. America-spec. MPI. [[w:Jaguar XK engine|Jaguar XK I6]]. Jaguar XJ6 ('81-'87).
|-
| 3 || 6.0L || 60° V12 || Gas ||SOHC,&lt;br /&gt; 24 valve||MPI. [[w:Jaguar V12 engine|Jaguar V12]] modified by [[w:Tom Walkinshaw Racing|JaguarSport]]. Jaguar XJR-S ('93).
|-
| 3 || 6.0L || 60° V12 || Gas ||SOHC,&lt;br /&gt; 24 valve||MPI. [[w:Jaguar V12 engine|Jaguar V12]]. Jaguar XJS ('94-'95), XJ12 ('94-'96).
|-
| 5 || 3.6L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||N. America-spec - Low Compression. MPI. [[w:Jaguar AJ6 engine|Jaguar AJ6 I6]]. Jaguar XJ6 ('88-'89).
|-
| 6 || 3.6L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||N. America-spec - High Compression. MPI. [[w:Jaguar AJ6 engine|Jaguar AJ6 I6]]. Jaguar XJ6 ('88).
|-
| 7 || 4.0L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. [[w:Jaguar AJ6 engine|Jaguar AJ6 I6]]. Jaguar XJ6 ('90-'94), XJS ('93-'94).
|-
| 7 || 4.0L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. [[w:Jaguar AJ6 engine#AJ16|Jaguar AJ16 I6]]. Jaguar XJ6 ('95-'96), XJS ('95-'96).
|-
| 7 || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ26 V8 engine]]. Jaguar XK8 ('97).
|-
| 8 || 5.3L || 60° V12 || Gas ||SOHC,&lt;br /&gt; 24 valve||N. America-spec. MPI. [[w:Jaguar V12 engine|Jaguar V12]]. Jaguar XJ-S ('82-'92), XJ12 (Canada only: '88-'92).
|-
| 8 || 4.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Dual-canister evaporative emissions system. [[w:Jaguar AJ-V8 engine#Supercharged|Jaguar AJ-V8 - AJ26S V8 engine]]. Jaguar XJR ('98-'99).
|-
| 9 || 4.0L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||Canada-spec. MPI. [[w:Jaguar AJ6 engine|Jaguar AJ6 I6]]. Jaguar XJ6 ('90-'93), XJS ('93).
|-
| 0 || 5.3L || 60° V12 || Gas ||SOHC,&lt;br /&gt; 24 valve||Canada-spec. MPI. [[w:Jaguar V12 engine|Jaguar V12]]. Jaguar XJ-S ('82-'87), XJ12 (Canada only: '85-'87).
|-
| 0 || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. Dual-canister evaporative emissions system. Enhanced evaporative emissions control system. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ27 V8 engine]]. Jaguar XJ8 ('99), XK8 ('99).
|}

===Transmission &amp; Steering Location (Position 8):===
* 4 = Automatic / LHD
* 8 = Manual / LHD ('93-'94 XJS 4.0 w/ optional 5-spd. manual)

===Check Digit/Gearbox (Position 9)===
* USA /Canada [[Vehicle Identification Numbers (VIN codes)/Check digit|Check digit]]

===Model Year Code (Position 10)===
''See: [[Vehicle Identification Numbers (VIN codes)/Model year]]''

===Plant Codes (Position 11)===
* C - Browns Lane plant, Coventry, West Midlands, England, UK

===Positions 12–17, Serial Number===
** 100001 and after - XJ-S/XJ-SC/XJS/XJR-S (XJ27)
** 300001 and after - XJ-series sedan Series III
** 500001 and after - XJ-series sedan (XJ40/XJ81)
** 720001 and after - XJ-series sedan (X300/X305/X306/X330)
** 810001 and after - XJ-series sedan (X308)
** 001001 and after - XK8 (X100)</text>
      <sha1>l8z4vh9jfzffuxn0s1257cky2p263cc</sha1>
    </revision>
    <revision>
      <id>4676694</id>
      <parentid>4676690</parentid>
      <timestamp>2026-10-18T05:26:45Z</timestamp>
      <contributor>
        <username>JustTheFacts33</username>
        <id>3434282</id>
      </contributor>
      <comment>/* Trim Level/Drive Wheels/Restraint System (Position 5) */</comment>
      <origin>4676694</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="43481" sha1="1pslz63etinwt04iojux9idkt0yo1bo" xml:space="preserve">{{Vehicle Identification Numbers (VIN codes)/Warning}}{{clear}}

This VIN number decoding and designation system is used primarily for the North American Market. European and Asian markets use other decoding and designation systems.

==General Template for Jaguar's VIN format (All models: 2016- EXCEPT F-Type '16-'17, XJ '16-'19)==

===Jaguar WMIs (2016-) (Position 1-3)===

* SAJ - Jaguar passenger car (UK)
* SAD - Jaguar SUV (UK &amp; Europe)
* L2C - Chery Jaguar Land Rover (China)

===Model Line (Position 4)===

{| class=&quot;wikitable&quot;
|+Position 4
!VIN code
!Description
|-
|A
|[[w:Jaguar XE|Jaguar XE]] ('17-'20)
|-
|B
|[[w:Jaguar XF (X260)|Jaguar XF]] ('16-'24)
|-
|C
|[[w:Jaguar F-Pace|Jaguar F-Pace]] ('17-'26)
|-
|D
|[[w:Jaguar F-Type|Jaguar F-Type]] ('18-'24)
|-
|E
|[[w:Jaguar Type 01|Jaguar Type 01]] ('28-)
|-
|F
|[[w:Jaguar E-Pace|Jaguar E-Pace]] ('18-'24)
|-
|H
|[[w:Jaguar I-Pace|Jaguar I-Pace EV]] ('19-'24)
|}

===Trim Level/Drive Wheels/Restraint System (Position 5)===

{| class=&quot;wikitable&quot;
|+Position 4
!VIN code
!Trim Level
!Drive Wheels
!Restraint System
|-
|D
|XF Premium '16-'17
|Rwd
|Manual seat belts, Dual front airbags, &amp; Front Side Airbags &amp; Side Curtain Airbags
|-
|E
|XF Prestige '16-'17
|Rwd
|Manual seat belts, Dual front airbags, &amp; Front Side Airbags &amp; Side Curtain Airbags
|-
|F
|XF R-Sport '16-'17
|Rwd
|Manual seat belts, Dual front airbags, &amp; Front Side Airbags &amp; Side Curtain Airbags
|-
|G
|XF S '16-'17
|Rwd
|Manual seat belts, Dual front airbags, &amp; Front Side Airbags &amp; Side Curtain Airbags
|-
|J
|XF Premium '16-'17
|Awd
|Manual seat belts, Dual front airbags, &amp; Front Side Airbags &amp; Side Curtain Airbags
|-
|K
|XF Prestige '16-'17
|Awd
|Manual seat belts, Dual front airbags, &amp; Front Side Airbags &amp; Side Curtain Airbags
|-
|L
|XF R-Sport '16-'17
|Awd
|Manual seat belts, Dual front airbags, &amp; Front Side Airbags &amp; Side Curtain Airbags
|-
|M
|XF S '16-'17
|Awd
|Manual seat belts, Dual front airbags, &amp; Front Side Airbags &amp; Side Curtain Airbags
|-
|N
|XF First Edition '16
|Awd
|Manual seat belts, Dual front airbags, &amp; Front Side Airbags &amp; Side Curtain Airbags
|-
|R
|XF Base model '17
|Rwd
|Manual seat belts, Dual front airbags, &amp; Front Side Airbags &amp; Side Curtain Airbags
|-
|S
|XF Base model '17
|Awd
|Manual seat belts, Dual front airbags, &amp; Front Side Airbags &amp; Side Curtain Airbags
|-
|}

===Body Style (Position 6):===
* 1 = Coupe (F-Type coupe)
* 2 = 5-door wagon (XF Sportbrake wagon '18-'20)
* 2 = 5-door (E-Pace, F-Pace, I-Pace EV)
* 4 = 4-door sedan (XE, XF sedan, Type 01)
* 5 = Convertible (F-Type convertible)

===Transmission (Position 7) 2016-2017:===
* B = Automatic (XE '17, XF '16-'17, F-Pace '17)

===Engine/Emissions Control System (Position 8) 2016-2017:===

{| class=&quot;wikitable&quot;
|+Position 8
! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications
|-
| G || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,&lt;br /&gt; 16 valve||Direct Injection. ULEV. Dual VVT. [[w:Ford EcoBoost engine#2.0 L (2010–2018)|Ford EcoBoost engine (Mazda L engine-based)]].&lt;br&gt; Jaguar XE 25t ('17).
|-
| N || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Diesel || DOHC,&lt;br /&gt; 16 valve||Common-rail Direct Injection. Exhaust VVT. [[w:Ingenium engine family|JLR Ingenium AJ20D engine]]. Jaguar XE 20d, XF 20d, F-Pace 20d ('17).
|-
| V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 35t ('16-'17) [If 5th pos. of VIN is NOT G or M]. Jaguar XE 35t ('17).&lt;br&gt; Jaguar F-Pace 35t ('17) [If 5th pos. of VIN is NOT M or P].
|-
| V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 380 PS/375 hp. Jaguar XF S ('16-'17) [If 5th pos. of VIN is G or M].&lt;br&gt; Jaguar F-Pace S ('17) [If 5th pos. of VIN is M or P].
|}

===Engine (Position 7-8) 2018-:===

{| class=&quot;wikitable&quot;
|+Position 7-8
! VIN Pos. 7 !! Power Level !! Transmission !! VIN Pos. 8 !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications
|-
| E || 550 PS/542 hp || 8-spd. Auto. || E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct injection. Dual Continuously VCT (VVT). [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133S engine]]. Jaguar F-Type R ('18-'20), F-Pace SVR ('19-'24).
|-
| E || 450 PS/444 hp || 8-spd. Auto. || E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct injection. Dual Continuously VCT (VVT). [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133S engine]]. Jaguar F-Type P450 ('22-24).
|-
| F || 575 PS/567 hp || 8-spd. Auto. || E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct injection. Dual Continuously VCT (VVT). [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133S engine]]. Jaguar F-Type SVR ('18-'20), F-Type R ('21-'24),&lt;br&gt; F-Pace SVR 575 Edition ('25-'26).
|-
| F || 600 PS/592 hp || 8-spd. Auto. || E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct injection. Dual Continuously VCT (VVT). [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133S engine]]. Jaguar XE SV Project 8 ('19).
|-
| F || 180 PS/178 hp || 8-spd. Auto. || N || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Diesel || DOHC,&lt;br /&gt; 16 valve||Common-rail Direct Injection. Exhaust VVT.&lt;br&gt; [[w:Ingenium engine family|JLR Ingenium AJ20D4/AJ200D engine]].&lt;br&gt; Jaguar XE 20d ('18-'19), XF 20d ('18-'19), F-Pace 20d ('18-'19).
|-
| E || 340 PS/335 hp || 8-spd. Auto. || U || 3.0L || I6 Turbo [[w:Intercooler|IC]] || Gas || DOHC,&lt;br /&gt; 24 valve||48v Mild Hybrid. E-supercharger. Direct Injection. Dual VVT.  CVVL (Intake VVL). [[w:Ingenium engine family|JLR Ingenium AJ20P6/AJ300P engine]].&lt;br&gt; Jaguar F-Pace P340 ('21-'22). 
|-
| F || 400 PS/395 hp || 8-spd. Auto. || U || 3.0L || I6 Turbo [[w:Intercooler|IC]] || Gas || DOHC,&lt;br /&gt; 24 valve||48v Mild Hybrid. E-supercharger. Direct Injection. Dual VVT.  CVVL (Intake VVL). [[w:Ingenium engine family|JLR Ingenium AJ20P6/AJ300P engine]].&lt;br&gt; Jaguar F-Pace P400 ('21-'26).
|-
| E || 340 PS/335 hp || 8-spd. Auto. || V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. Continuously variable intake &amp; exhaust valve timing.&lt;br&gt; [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; Jaguar XE 35t ('18), XF 35t ('18), F-Type ('18), F-Type P340 ('19-'20),&lt;br&gt; F-Pace 35t ('18).
|-
| F || 380 PS/375 hp || 8-spd. Auto. || V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. Continuously variable intake &amp; exhaust valve timing.&lt;br&gt; [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; Jaguar XE S ('18-'19), XF S ('18-'20), F-Type ('18),&lt;br&gt; F-Type P380 ('19), F-Type P380 R-Dynamic ('19-'21), F-Pace S ('18-'20).
|-
| G || 400 PS/395 hp || 8-spd. Auto. || V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. Continuously variable intake &amp; exhaust valve timing.&lt;br&gt; [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; Jaguar F-Type 400 Sport ('18).
|-
| J || 340 PS/335 hp || 6-spd. Man. || V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. Continuously variable intake &amp; exhaust valve timing.&lt;br&gt; [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; Jaguar F-Type ('18), F-Type P340 ('19).
|-
| K || 380 PS/375 hp || 6-spd. Man. || V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. Continuously variable intake &amp; exhaust valve timing.&lt;br&gt; [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; Jaguar F-Type P380 R-Dynamic ('18-'19).
|-
| E || 250 PS/247 hp || 8-spd. Auto. || X || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,&lt;br /&gt; 16 valve||Direct Injection. Dual VVT. CVVL (Intake VVL).&lt;br&gt; [[w:Ingenium engine family|JLR Ingenium AJ20P4/AJ200P engine]].&lt;br&gt; Jaguar F-Pace P250 ('21-'26).
|-
| F || 250 PS/247 hp || 8-spd. Auto. || X || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,&lt;br /&gt; 16 valve||Direct Injection. Dual VVT. CVVL (Intake VVL).&lt;br&gt; [[w:Ingenium engine family|JLR Ingenium AJ20P4/AJ200P engine]].&lt;br&gt; Jaguar XE 25t ('18-'20), XF 25t ('18-'20), XF P250 ('21-'24),&lt;br&gt; E-Pace P250 ('18-'24), F-Pace 25t ('18-'20).
|-
| G || 300 PS/296 hp || 8-spd. Auto. || X || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,&lt;br /&gt; 16 valve||Direct Injection. Dual VVT. CVVL (Intake VVL).&lt;br&gt; [[w:Ingenium engine family|JLR Ingenium AJ20P4/AJ200P engine]].&lt;br&gt; Jaguar XE 30t ('18-'20), XF 30t ('18-'20), XF P300 ('21-'24),&lt;br&gt; F-Type ('18), F-Type P300 ('19-'21), E-Pace P300 R-Dynamic ('18-'20),&lt;br&gt; E-Pace 300 Sport ('21-'22), F-Pace 30t ('18-'20). 
|}

====Motor Type for Electric Vehicles 2019-====

{| class=&quot;wikitable&quot;
|+Position 7-8
|-
! VIN Pos. 7 !! Power Level !! Transmission !! VIN Pos. 8 !! # of Motors !! Battery Size !! Battery Type !! Fuel !! Drive Wheels !! Notes/Applications
|-
| S || 400 PS/394 hp || 1-spd. Auto. || 1 || 2 || 90 Kwh || Lithium-ion || Electricity || All || Jaguar I-Pace EV400 ('19-'24).
|-
| T || 1029 PS/1015 hp || 1-spd. Auto. || 1 || 3 &lt;br&gt; (1 Front,&lt;br&gt; 2 Rear) || 118 Kwh || Lithium-ion || Electricity || All || Jaguar Type 01 ('28-).
|}

===Check Digit/Gearbox (Position 9)===
* USA /Canada [[Vehicle Identification Numbers (VIN codes)/Check digit|Check digit]]

===Model Year Code (Position 10)===
''See: [[Vehicle Identification Numbers (VIN codes)/Model year]]''

===Plant Codes (Position 11) 2016-===
* A - Solihull, West Midlands, England, UK (XE '17, F-Pace '17-'26, Type 01 '28-)
* C - Castle Bromwich, West Midlands, England, UK (XE '17-'20, XF '16-'24, F-Type '18-'24)
* S - Oxford Road plant, Ryton, West Midlands, England, UK (JLR SVO plant) (XE SV Project 8 '19)
* 1 - Graz, Austria (Magna Steyr plant) (E-Pace '18-'24, I-Pace EV '19-'24)

===Model (Position 12)===
* 9 - XE ('17) [Solihull plant]
* P - XE ('17-'20) [Castle Bromwich plant]
* Y - XF ('16-'24)
* K - F-Type ('18-'24)
* Z - E-Pace ('18-'20)
* 0 - E-Pace ('20-'24)
* F - I-Pace EV ('19-'20)
* 6 - I-Pace EV ('20-'24)

'''Positions 13–17, Serial Number'''

==General Template for Jaguar's VIN format (All models: 2000-2015 plus F-Type '16-'17, XJ '16-'19)==

===Jaguar WMIs (2000-) (Position 1-3)===

* SAJ - Jaguar passenger car (UK)
* SAD - Jaguar SUV (UK &amp; Europe)

===Regional Spec/Restraint System (Position 4):===
* J = Manual seat belts, Dual front airbags (US: XK8 '00)
* B = Manual seat belts, Dual front airbags (Canada: XK8 '00)
* D = Manual seat belts, Depowered Dual front airbags, &amp; Front Side Airbags (US: S-Type '00-'02, XJ8/XJR '00-'03, XK8/XKR '01-'06, XK/XKR Early '07)
* F = Manual seat belts, Depowered Dual front airbags, &amp; Front Side Airbags (Canada: S-Type '00-'02, XJ8/XJR '00-'03, XK8/XKR '01-'06, XK/XKR Early '07)
* E = Manual seat belts, Depowered Dual front airbags w/occupant position sensing, &amp; Front Side Airbags &amp; Side Curtain Airbags (US: X-Type '02-'04, S-Type '03-'04, XJ8/XJR Early '04)
* G = Manual seat belts, Depowered Dual front airbags w/occupant position sensing, &amp; Front Side Airbags &amp; Side Curtain Airbags (Canada: X-Type '02-'04,&lt;br&gt; S-Type '03-'04, XJ8/XJR Early '04)
* W = Manual seat belts, Depowered Dual front airbags w/occupant position (driver) and weight (fr. psgr.) sensing, &amp; Front Side Airbags &amp; Side Curtain Airbags &lt;br&gt; (US: X-Type '05-'08, S-Type '05-'08, XF '09-'15,  XJ8/XJR '04-'09, XJ '10-)
* X = Manual seat belts, Depowered Dual front airbags w/occupant position (driver) and weight (fr. psgr.) sensing, &amp; Front Side Airbags &amp; Side Curtain Airbags (Canada: X-Type '05-'08, S-Type '05-'08, XF '09-'15, XJ8/XJR '04-'09, XJ '10-)
* W = Manual seat belts, Depowered Dual front airbags w/occupant position (driver) and weight (fr. psgr.) sensing, &amp; Front Side Head/Thorax Airbags &lt;br&gt; (US: XK/XKR '07-'15, F-Type '14-)
* X = Manual seat belts, Depowered Dual front airbags w/occupant position (driver) and weight (fr. psgr.) sensing, &amp; Front Side Head/Thorax Airbags &lt;br&gt; (Canada: XK/XKR '07-'15, F-Type '14-)

===Transmission &amp; Steering Location (Position 5 - '00-'12):===
* A = Automatic / LHD
* B = Manual / LHD (X-Type '02-'05, S-Type 3.0 '03-'04)

===Transmission &amp; Drive Wheels (Position 5 - '13-):===
* A = Automatic / Rwd (XF '13-'15, XJ '13-'19, XK '13-'15, F-Type '14-'17)
* B = Manual / Rwd (F-Type '16-'17)
* J = Automatic / Awd (XF Awd '13-'15, XJ Awd '13-'19, F-Type Awd '16-'17)

===Model Line (Position 6-7)===

{| class=&quot;wikitable&quot;
|+Position 6-7
!VIN code
!Description
|-
|51
|[[w:Jaguar X-Type|Jaguar X-Type sedan - High Series]] ('02-'08)
|-
|52
|[[w:Jaguar X-Type|Jaguar X-Type sedan - Entry Series]] ('03-'04)
|-
|53
|[[w:Jaguar X-Type|Jaguar X-Type sedan w/Sport Package]] ('02-'03)
|-
|54
|[[w:Jaguar X-Type|Jaguar X-Type Sportwagon]] ('05-'08)
|-
|01
|[[w:Jaguar S-Type (1999)|Jaguar S-Type]] ('00-'08)
|-
|03
|[[w:Jaguar S-Type (1999)|Jaguar S-Type Sport]] [3.0, 4.0] ('02)
|-
|03
|[[w:Jaguar S-Type (1999)|Jaguar S-Type Sport]] [3.0, 4.2] ('03)
|-
|03
|[[w:Jaguar S-Type (1999)|Jaguar S-Type R]] ('03-'08)
|-
|05
|[[w:Jaguar XF (X250)|Jaguar XF Luxury]] ('09)
|-
|06
|[[w:Jaguar XF (X250)|Jaguar XF Premium Luxury]] ('09)
|-
|07
|[[w:Jaguar XF (X250)|Jaguar XF Supercharged]] ('09)
|-
|0E
|[[w:Jaguar XF (X250)|Jaguar XF]] ('13-'14)
|-
|0F
|[[w:Jaguar XF (X250)|Jaguar XF]] ('10-'12)
|-
|0F
|[[w:Jaguar XF (X250)|Jaguar XF 2.0T Premium]] [8th pos. of VIN is S] ('15)
|-
|0F
|[[w:Jaguar XF (X250)|Jaguar XF 3.0 Sport Rwd or 3.0 Portfolio Rwd]] [8th pos. of VIN is 7] ('15)
|-
|0F
|[[w:Jaguar XF (X250)|Jaguar XF 3.0 Sport Awd or 3.0 Portfolio Awd]] [8th pos. of VIN is F] ('15)
|-
|0G
|[[w:Jaguar XF (X250)|Jaguar XF Premium]] ('10-'11)
|-
|0H
|[[w:Jaguar XF (X250)|Jaguar XF Portfolio]] [8th pos. of VIN is B] ('12)
|-
|0H
|[[w:Jaguar XF (X250)|Jaguar XF Supercharged]] [8th pos. of VIN is E: '10-'13 or P: '13-'15]
|-
|0J
|[[w:Jaguar XF (X250)|Jaguar XFR]] ('10-'15)
|-
|0K
|[[w:Jaguar XF (X250)|Jaguar XFR-S]] ('13-'15)
|-
|8J
|[[w:Jaguar XF (X250)|Jaguar XFR w/Speed Pack]] ('13-'15)
|-
|12
|[[w:Jaguar XJ (X308)#Sport|Jaguar XJ Sport]] ('02-'03)
|-
|14
|[[w:Jaguar XJ (X308)|Jaguar XJ8]] ('00-'03)
|-
|15
|[[w:Jaguar XJ (X308)#XJR|Jaguar XJR]] ('00-'03)
|-
|23
|[[w:Jaguar XJ (X308)|Jaguar XJ8L]] (LWB) ('00-'01)
|-
|24
|[[w:Jaguar XJ (X308)#Daimler/Vanden Plas|Jaguar XJ8 Vanden Plas]] (LWB) ('00-'03)
|-
|25
|[[w:Jaguar XJ (X308)#Daimler/Vanden Plas|Jaguar XJ8 Vanden Plas Supercharged]] (LWB) ('00-'01)
|-
|25
|[[w:Jaguar XJ (X308)#Daimler/Vanden Plas|Jaguar XJ Super V8]] (LWB) ('02-'03)
|-
|71
|[[w:Jaguar XJ (X350)|Jaguar XJ8]] ('04-'09)
|-
|73
|[[w:Jaguar XJ (X350)|Jaguar XJR]] ('04-'09)
|-
|74
|[[w:Jaguar XJ (X350)|Jaguar XJ8 Vanden Plas]] (SWB) ('04)
|-
|79
|[[w:Jaguar XJ (X350)|Jaguar XJ8L]] (LWB) ('05-'09)
|-
|82
|[[w:Jaguar XJ (X350)|Jaguar XJ8 Vanden Plas]] (LWB) ('05-'09)
|-
|82
|[[w:Jaguar XJ (X350)|Jaguar XJ Super V8]] (LWB, 5-psgr.) ('05-'09)
|-
|86
|[[w:Jaguar XJ (X350)|Jaguar XJ Super V8 Portfolio]] (LWB, 4-psgr.) ('06)
|-
|94
|[[w:Jaguar XJ (X350)|Jaguar XJ Super V8 Portfolio]] (LWB, 5-psgr.) ('09)
|-
|1C
|[[w:Jaguar XJ (X351)|Jaguar XJ]] ('10-'15)
|-
|1C
|[[w:Jaguar XJ (X351)|Jaguar XJ R-Sport]] [8th pos. of VIN is 7 (Rwd) or D (Awd)] ('16-'19)
|-
|1C
|[[w:Jaguar XJ (X351)|Jaguar XJ Supercharged]] [8th pos. of VIN is E] ('16-'19)
|-
|1E
|[[w:Jaguar XJ (X351)|Jaguar XJR]] ('14-'17)
|-
|1G
|[[w:Jaguar XJ (X351)|Jaguar XJ Supercharged]] [8th pos. of VIN is E: '10-'13 or T: '13-'15]
|-
|1J
|[[w:Jaguar XJ (X351)|Jaguar XJ Supersport]] ('11-'12)
|-
|2E
|[[w:Jaguar XJ (X351)|Jaguar XJR LWB]] ('14-'17), XJR575 LWB ('18-'19)
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL]] [8th pos. of VIN is B] ('10-'11)
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL Portfolio Rwd]] [8th pos. of VIN is B: '12-'13 or 1: '13]
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL Portfolio Rwd]] [8th pos. of VIN is Z: '14-'15)
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL Portfolio Rwd]] [8th pos. of VIN is 7: '16-'19), XJ50 3.0 Rwd (LWB) '19
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL Portfolio Awd]] [8th pos. of VIN is D] ('13-'19), XJ50 3.0 Awd (LWB) '19
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL Supercharged]] [8th pos. of VIN is E: '10-'13, '16-'19 or T: '13-'15], XJ50 5.0 Rwd (LWB) '19, XJ Collection (LWB) '19
|-
|2J
|[[w:Jaguar XJ (X351)|Jaguar XJL Supersport]] ('11-'13)
|-
|2K
|[[w:Jaguar XJ (X351)|Jaguar XJL Ultimate]] ('13)
|-
|3F
|[[w:Jaguar XJ (X351)|Jaguar XJ Supersport w/Speed Pack]] ('12-'13)
|-
|3G
|[[w:Jaguar XJ (X351)|Jaguar XJL Supersport w/Speed Pack]] ('12-'13)
|-
|3H
|[[w:Jaguar XJ (X351)|Jaguar XJ Supercharged w/Sport &amp; Speed Pack]] ('12-'15)
|-
|3K
|[[w:Jaguar XJ (X351)|Jaguar XJL Supercharged w/Sport &amp; Speed Pack]] ('12-'15)
|-
|41
|[[w:Jaguar XK (X100)|Jaguar XK8/XKR coupe]] ('00-'06)
|-
|42
|[[w:Jaguar XK (X100)|Jaguar XK8/XKR convertible]] ('00-'06)
|-
|43
|[[w:Jaguar XK (X150)|Jaguar XK/XKR coupe]] ('07-'09)
|-
|44
|[[w:Jaguar XK (X150)|Jaguar XK/XKR convertible]] ('07-'09)
|-
|45
|[[w:Jaguar XK (X150)|Jaguar XKR Portfolio Edition coupe]] ('09)
|-
|46
|[[w:Jaguar XK (X150)|Jaguar XKR Portfolio Edition convertible]] ('09)
|-
|4D
|[[w:Jaguar XK (X150)|Jaguar XK Touring coupe]] [8th pos. of VIN is B] ('13-'14)
|-
|4E
|[[w:Jaguar XK (X150)|Jaguar XK Touring convertible]] [8th pos. of VIN is B] ('13-'14)
|-
|4D
|[[w:Jaguar XK (X150)|Jaguar XKR coupe]] [8th pos. of VIN is C] ('10-'15)
|-
|4E
|[[w:Jaguar XK (X150)|Jaguar XKR convertible]] [8th pos. of VIN is C] ('10-'15)
|-
|4F
|[[w:Jaguar XK (X150)|Jaguar XK coupe]] (most Portfolio Edition features are std.) [8th pos. of VIN is B] ('10-'15)
|-
|4F
|[[w:Jaguar XK (X150)|Jaguar XKR175 coupe]] [8th pos. of VIN is C] ('11)
|-
|4F
|[[w:Jaguar XK (X150)|Jaguar XKR coupe w/Dynamic Pack]] [8th pos. of VIN is C] ('13-'15), XK Final Fifty Edition coupe ('15)
|-
|4G
|[[w:Jaguar XK (X150)|Jaguar XK convertible]] (most Portfolio Edition features are std.) [8th pos. of VIN is B] ('10-'15)
|-
|4G
|[[w:Jaguar XK (X150)|Jaguar XKR convertible w/Dynamic Pack]] [8th pos. of VIN is C] ('13-'15), XK Final Fifty Edition convertible ('15)
|-
|4H
|[[w:Jaguar XK (X150)|Jaguar XKR-S coupe]] ('12-'15), XKR-S GT coupe ('14)
|-
|4J
|[[w:Jaguar XK (X150)|Jaguar XKR-S convertible]] ('12-'15)
|-
|6A
|[[w:Jaguar F-Type)|Jaguar F-Type coupe]] ('15-'17), F-Type Premium coupe '17
|-
|6B
|[[w:Jaguar F-Type)|Jaguar F-Type S coupe]] ('15-'17), F-Type S British Design Edition coupe '17
|-
|6D
|[[w:Jaguar F-Type)|Jaguar F-Type R coupe]] ('15-'17)
|-
|6E
|[[w:Jaguar F-Type)|Jaguar F-Type convertible]] ('14-'17), F-Type Premium convertible '17
|-
|6F
|[[w:Jaguar F-Type)|Jaguar F-Type S convertible]] ('14-'17), F-Type S British Design Edition convertible '17
|-
|6G
|[[w:Jaguar F-Type)|Jaguar F-Type V8 S convertible]] ('14-'15)
|-
|6H
|[[w:Jaguar F-Type)|Jaguar F-Type R convertible]] ('16-'17)
|-
|6J
|[[w:Jaguar F-Type)|Jaguar F-Type SVR coupe]] ('17)
|-
|6K
|[[w:Jaguar F-Type)|Jaguar F-Type SVR convertible]] ('17)
|-
|7A
|[[w:Jaguar F-Type#Project 7)|Jaguar F-Type Project 7 convertible]] ('16)
|}

===Engine/Emissions Control System (Position 8)===

{| class=&quot;wikitable&quot;
|+Position 8
! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications
|-
| A || 3.0L || 60° V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. ULEV. Variable intake valve timing. [[w:Jaguar AJ-V6 engine#AJ30|Jaguar AJ-V6 - AJ30 V6 engine]].&lt;br&gt; Jaguar X-Type 3.0 (Mid '05-'08), S-Type 3.0 ('06-'08). 
|-
| A || 4.2L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. ULEV. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.2 L|Jaguar AJ-V8 - AJ34 V8 engine]]. Jaguar XF ('10).
|-
| A || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 550 PS/542 hp. Jaguar XKR-S ('12-'15), XKR-S GT ('14), F-Type R coupe ('15).
|-
| B || 4.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. [[w:Jaguar AJ-V8 engine#Supercharged|Jaguar AJ-V8 - AJ27S V8 engine]].&lt;br&gt; Jaguar XJR ('00-'03), Vanden Plas Supercharged ('00-'01), Super V8 ('02-'03), XKR ('00-'02).
|-
| B || 4.2L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. [[w:Jaguar AJ-V8 engine#Supercharged_2|Jaguar AJ-V8 - AJ33S V8 engine]]. Jaguar XJR ('04-'05), Super V8 ('05), XKR ('03-'06).
|-
| B || 4.2L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. ULEV. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.2 L|Jaguar AJ-V8 - AJ34 V8 engine]].&lt;br&gt; Jaguar S-Type ('06-'08), XF ('09), XJ8/Vanden Plas ('06-'09), XK ('07-'09).
|-
| B || 5.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. Variable intake valve lift. Variable intake.&lt;br&gt; [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; Jaguar XF ('10-'12), XJ ('11-'12), XJL ('11), XJL Portfolio Rwd ('12-'13), XK ('10-'15), XK Touring ('13-'14).
|-
| C || 3.0L || 60° V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. Variable intake valve timing. [[w:Jaguar AJ-V6 engine#AJ30|Jaguar AJ-V6 - AJ30 V6 engine]].&lt;br&gt; Jaguar S-Type 3.0 ('00-'01), X-Type 3.0 ('02-Mid '05). 
|-
| C || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ27 V8 engine]].&lt;br&gt; Jaguar XJ8/Vanden Plas ('00-'03), XJ Sport ('02-'03), XK8 ('00-'02).
|-
| C || 4.2L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.2 L|Jaguar AJ-V8 - AJ33 V8 engine]]. Jaguar XJ8 ('04-'05), XK8 ('03-'06).
|-
| C || 4.2L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. ULEV. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#Supercharged_2|Jaguar AJ-V8 - AJ34S V8 engine]].&lt;br&gt; Jaguar S-Type R ('06-'08), XF Supercharged ('09), XJR ('06-'09), Super V8 ('06-'09), XKR ('07-'09).
|-
| C || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 510 PS/503 hp. Jaguar XFR ('10-'13), XJ/XJL Supersport ('11-'13), XKR ('10-'15).
|-
| C || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 380 PS/375 hp. Jaguar F-Type S ('14-'15), F-Type S w/man. trans. ('16-'17).
|-
| D || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ28 V8 engine]]. Jaguar S-Type 4.0 ('00-'01).
|-
| D || 2.5L || 60° V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. Variable intake valve timing. [[w:Jaguar AJ-V6 engine#AJ25|Jaguar AJ-V6 - AJ25 V6 engine]]. Jaguar X-Type 2.5 ('02-'05).
|-
| D || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XJ Awd, XJL Portfolio Awd ('13-'15).
|-
| D || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XJ R-Sport Awd, XJL Portfolio Awd ('16-'19), XJ50 3.0 Awd ('19).
|-
| E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 470 PS/464 hp.&lt;br&gt; Jaguar XF Supercharged ('10-'13), XJ/XJL Supercharged ('11-'13, '16-'19), XJ50 5.0 Rwd ('19), XJ Collection ('19).
|-
| F || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 3.0 Awd ('13-'14).
|-
| F || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 3.0 Awd ('15).
|-
| H || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,&lt;br /&gt; 32 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]]. 510 PS/503 hp. Jaguar XFR ('13-'15).
|-
| K || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 550 PS/542 hp. Jaguar XJR/XJR LWB ('14-'17).
|-
| K || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 575 PS/567 hp. Jaguar XJR575 LWB ('18-'19).
|-
| L || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 495 PS/488 hp. Jaguar F-Type V8 S convertible ('14-'15).
|-
| L || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 550 PS/542 hp. Jaguar F-Type R  ('16-'17).
|-
| N || 3.0L || 60° V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. Variable intake valve timing. [[w:Jaguar AJ-V6 engine#AJ30|Jaguar AJ-V6 - AJ30 V6 engine]]. Jaguar S-Type 3.0 ('01-'02).
|-
| P || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ28 V8 engine]]. Jaguar S-Type 4.0 ('01-'02).
|-
| P || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,&lt;br /&gt; 32 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]]. 470 PS/464 hp. Jaguar XF Supercharged ('13-'15).
|-
| S || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,&lt;br /&gt; 16 valve||Direct Injection. Dual VVT. [[w:Ford EcoBoost engine#2.0 L (2010–2018)|Ford EcoBoost engine (Mazda L engine-based)]].&lt;br&gt; Jaguar XF 2.0T ('13-'14), XF 2.0T Premium ('15).
|-
| T || 3.0L || 60° V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. Variable intake valve timing. [[w:Jaguar AJ-V6 engine#AJ30|Jaguar AJ-V6 - AJ30 V6 engine]]. Jaguar S-Type 3.0 ('03-'05).
|-
| T || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,&lt;br /&gt; 32 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]]. 470 PS/464 hp. Jaguar XJ/XJL Supercharged ('13-'15).
|-
| T || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar F-Type w/auto. trans. ('15-'17), F-Type Premium w/auto. trans. ('17).
|-
| U || 4.2L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.2 L|Jaguar AJ-V8 - AJ33 V8 engine]]. Jaguar S-Type 4.2 ('03-'05).
|-
| U || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 380 PS/375 hp. Jaguar F-Type S ('15), F-Type S Rwd w/auto. trans. ('16-'17).
|-
| V || 4.2L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. [[w:Jaguar AJ-V8 engine#Supercharged_2|Jaguar AJ-V8 - AJ33S V8 engine]]. Jaguar S-Type R ('03-'05).
|-
| V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 380 PS/375 hp. Jaguar F-Type S Awd w/auto. trans. ('16-'17).
|-
| X || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,&lt;br /&gt; 24 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 3.0 Rwd ('14).
|-
| Z || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 550 PS/542 hp. Jaguar XFR-S ('13-'15).
|-
| Z || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,&lt;br /&gt; 24 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XJ Rwd, XJL Portfolio Rwd ('14-'15).
|-
| 1 || 5.0L || V8 || Gas/E85 ||DOHC,&lt;br /&gt; 32 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. Variable intake valve lift. Variable intake. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]]. Jaguar XJL Portfolio Rwd ('13).
|-
| 6 || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar F-Type w/man. trans. ('16-'17), F-Type Premium w/man. trans. ('17).
|-
| 7 || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 3.0 Rwd ('13), XJ Rwd ('13), F-Type ('14-'15).
|-
| 7 || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 3.0 Rwd ('15), XJ R-Sport Rwd ('16-'19), XJL Portfolio Rwd ('16-'19), XJ50 3.0 Rwd ('19).
|-
| 8 || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 575 PS/567 hp. Jaguar F-Type Project 7 ('16), F-Type SVR ('17).
|}

===Check Digit/Gearbox (Position 9)===
* USA /Canada [[Vehicle Identification Numbers (VIN codes)/Check digit|Check digit]]

===Model Year Code (Position 10)===
''See: [[Vehicle Identification Numbers (VIN codes)/Model year]]''

===Plant Code/Model Line/Engine (Position 11) 2000-2019===
* X - Halewood, Merseyside, England, UK - X-Type 2.5 ('02-'05)
* W - Halewood, Merseyside, England, UK - X-Type 3.0 ('02-'08)
* F - Castle Bromwich, West Midlands, England, UK - S-Type 3.0 ('00-'08)
* G - Castle Bromwich, West Midlands, England, UK - S-Type 4.0 ('00-'02)
* H - Castle Bromwich, West Midlands, England, UK - S-Type 4.2 ('03-'08)
* 1 - Castle Bromwich, West Midlands, England, UK - S-Type R (4.2 supercharged) ('03-'08)
* H - Castle Bromwich, West Midlands, England, UK - XF 4.2 ('09-'10)
* 1 - Castle Bromwich, West Midlands, England, UK - XF Supercharged (4.2 supercharged) ('09)
* L - Castle Bromwich, West Midlands, England, UK - XF 5.0 ('10-'12)
* M - Castle Bromwich, West Midlands, England, UK - XF Supercharged, XFR (5.0 supercharged) ('10-'15), XFR-S (5.0 supercharged) ('13-'15)
* P - Castle Bromwich, West Midlands, England, UK - XF 2.0T ('13-'15)
* 8 - Castle Bromwich, West Midlands, England, UK - XF 3.0 supercharged ('13-'15)
* L - Browns Lane plant, Coventry, West Midlands, England, UK - XJ8 (4.0) ('00-'03), XJ8L (4.0) ('00-'01), XJ8 Vanden Plas (4.0) ('00-'03), XJ Sport (4.0) ('02-'03)
* M - Browns Lane plant, Coventry, West Midlands, England, UK - XJ8 Vanden Plas Supercharged (4.0 supercharged) ('00-'01),&lt;br&gt; Super V8 (4.0 supercharged) ('02-'03), XJR (4.0 supercharged) ('00-'03)
* S - Browns Lane plant, Coventry, West Midlands, England, UK - XJ8 (4.2) ('04-'06), XJ8L (4.2) ('05-'06), XJ8 Vanden Plas (4.0) ('04-'06)
* T - Browns Lane plant, Coventry, West Midlands, England, UK - Super V8 (4.2 supercharged) ('05-'06), Super V8 Portfolio (4.2 supercharged) ('06),&lt;br&gt; XJR (4.2 supercharged) ('04-'06)
* S - Castle Bromwich, West Midlands, England, UK - XJ8 (4.2) ('07-'09), XJ8L (4.2) ('07-'09), XJ8 Vanden Plas (4.0) ('07-'09)
* T - Castle Bromwich, West Midlands, England, UK - Super V8 (4.2 supercharged) ('07-'09), Super V8 Portfolio (4.2 supercharged) ('09),&lt;br&gt; XJR (4.2 supercharged) ('07-'09)
* L - Castle Bromwich, West Midlands, England, UK - XJ (5.0) ('10-'12), XJL (5.0) ('10-'11), XJL Portfolio (5.0) ('12-'13)
* M - Castle Bromwich, West Midlands, England, UK - XJ/XJL Supercharged (5.0 supercharged) ('10-'19), XJ/XJL Supersport (5.0 supercharged) ('11-'13),&lt;br&gt; XJL Ultimate (5.0 supercharged) ('13), XJR SWB/LWB (5.0 supercharged) ('14-'17), XJR575 LWB (5.0 supercharged) ('18-'19), XJ50 LWB (5.0 supercharged) ('19), XJ Collection Sp. Ed. LWB (5.0 supercharged) ('19)
* 8 - Castle Bromwich, West Midlands, England, UK - XJ base (3.0 supercharged) ('13-'15), XJ R-Sport (3.0 supercharged) ('16-'19),&lt;br&gt; XJL Portfolio AWD (3.0 supercharged) ('13-'19), XJL Portfolio RWD (3.0 supercharged) ('14-'19), XJ50 LWB (3.0 supercharged) ('19)
* N - Browns Lane plant, Coventry, West Midlands, England, UK - XK8 (4.0) ('00-'02)
* P - Browns Lane plant, Coventry, West Midlands, England, UK - XKR (4.0 supercharged) ('00-'02)
* 2 - Browns Lane plant, Coventry, West Midlands, England, UK - XK8 (4.2) ('03-'06)
* 3 - Browns Lane plant, Coventry, West Midlands, England, UK - XKR (4.2 supercharged) ('03-'06)
* 5 - Castle Bromwich, West Midlands, England, UK - XK (4.2) ('07-'09)
* 9 - Castle Bromwich, West Midlands, England, UK - XKR (4.2 supercharged) ('07-'09)
* L - Castle Bromwich, West Midlands, England, UK - XK (5.0) ('10-'15)
* M - Castle Bromwich, West Midlands, England, UK - XKR (5.0 supercharged) ('10-'15), XKR-S (5.0 supercharged) ('12-'15), XKR-S GT (5.0 supercharged) ('14)
* 8 - Castle Bromwich, West Midlands, England, UK - F-Type Base, S (3.0 supercharged) ('14-'17), F-Type Premium (3.0 supercharged) ('17)
* M - Castle Bromwich, West Midlands, England, UK - F-Type V8S (5.0 supercharged) ('14-'15), F-Type R (5.0 supercharged) ('15-'17),&lt;br&gt; F-Type Project 7 (5.0 supercharged) ('16), F-Type SVR (5.0 supercharged) ('17)

===Model (Position 12)===
* C - X-Type ('02-'03)
* D - X-Type ('03-'04)
* E - X-Type ('04-'06)
* J - X-Type ('06-'08)
* L - S-Type ('00-'01)
* M - S-Type ('01-'04)
* N - S-Type ('04-'08)
* R - XF ('09-'11)
* S - XF ('11-'13)
* U - XF ('13-'15)
* F - XJ ('00-'03)
* G - XJ ('04-'06) [Browns Lane plant]
* H - XJ ('06-'09) [Castle Bromwich plant]
* V - XJ ('10-'16)
* W - XJ ('16-'19)
* A - XK ('00-'06)
* B - XK ('07-'15)
* K - F-Type ('14-'17)

'''Positions 13–17, Serial Number'''

==General Template for Jaguar's VIN format (1981 - 1999)==

===Jaguar WMIs (1981-1999) (Position 1-3)===
* SAJ - Jaguar passenger car

===Model Line (Position 4)===

{| class=&quot;wikitable&quot;
|+Position 4
!VIN code
!Description
|-
|A
|[[w:Jaguar XJ#Series 3 (1979–1992)|Jaguar XJ6]] ('81-'87), XJ6 Vanden Plas ('82-'87)
|-
|B
|[[w:Jaguar XJ#Series 3 (1979–1992)|Jaguar XJ12]] (Canada only: '81-'88)
|-
|D
|[[w:Jaguar XJ#Series 3 (1979–1992)|Jaguar XJ12]] (Canada only: '89-'92)
|-
|H
|[[w:Jaguar XJ (XJ40)|Jaguar XJ6]] ('88-'89, '93-'94)
|-
|F
|[[w:Jaguar XJ (XJ40)|Jaguar XJ6]] ('90-'92)
|-
|H
|[[w:Jaguar XJ (XJ40)|Jaguar XJ6 Sovereign]] ('90-'92)
|-
|K
|[[w:Jaguar XJ (XJ40)#Daimler/Vanden Plas|Jaguar XJ6 Vanden Plas]] ('88-'94)
|-
|M
|[[w:Jaguar XJ (XJ40)#Majestic (1989–1992 – SWB; 1993–1994 – LWB)|Jaguar XJ6 Vanden Plas Majestic]] ('89-'90, '92)
|-
|M
|[[w:Jaguar XJ (XJ40)#XJ12 and Daimler Double Six (XJ81)|Jaguar XJ12]] ('94)
|-
|H
|[[w:Jaguar XJ (X300)|Jaguar XJ6]] ('95-'97)
|-
|H
|[[w:Jaguar XJ (X300)|Jaguar XJ6L]] LWB [X330] ('97)
|-
|K
|[[w:Jaguar XJ (X300)#Daimler/Jaguar Vanden Plas|Jaguar XJ6 Vanden Plas]] SWB ('95)
|-
|K
|[[w:Jaguar XJ (X300)#Daimler/Jaguar Vanden Plas|Jaguar XJ6 Vanden Plas]] LWB [X330] ('96-'97)
|-
|M
|[[w:Jaguar XJ (X300)#XJ12 (X305)|Jaguar XJ12]] SWB ('95)
|-
|M
|[[w:Jaguar XJ (X300)#XJ12 (X305)|Jaguar XJ12]] LWB [X330] ('96)
|-
|P
|[[w:Jaguar XJ (X300)#XJR (X306)|Jaguar XJR]] ('95-'97)
|-
|H
|[[w:Jaguar XJ (X308)|Jaguar XJ8]] ('98-'99)
|-
|H
|[[w:Jaguar XJ (X308)|Jaguar XJ8L]] LWB ('98-'99)
|-
|K
|[[w:Jaguar XJ (X308)#Daimler/Vanden Plas|Jaguar XJ8 Vanden Plas]] LWB ('98-'99)
|-
|P
|[[w:Jaguar XJ (X308)#XJR|Jaguar XJR]] ('98-'99)
|-
|N
|[[w:Jaguar XJS|Jaguar XJ-S]] ('82-'91), XJ-SC ('86-'88), XJS ('92-'96)
|-
|T
|[[w:Jaguar XJS|Jaguar XJ-S]] Rouge Collection ('89-'90), Classic Collection ('90-'91)
|-
|S
|[[w:Jaguar XJS#XJR-S|Jaguar XJR-S]] ('93)
|-
|G
|[[w:Jaguar XK (X100)|Jaguar XK8]] ('97-'99)
|}

===Class (Regional Spec)/Restraint System (Position 5):===
* V = N. American-spec (Manual seat belts)
* L = Canadian-spec (Manual seat belts)

* Y = XJ6 Vanden Plas [Series III] ('82-'87) (Manual seat belts)

* A = Motorized Shoulder Belts (XJ-S coupe '88-'89, XJ-SC '88)
* Y = Motorized Shoulder Belts (XJ-S coupe '89, XJ sedan '89-'92)
* W = Manual seat belts, Driver-side airbag (US: XJ-S '90-'93, XJ6 '93, XJ12 Early '94)
* X = Manual seat belts, Dual front airbags (US: XJS '94-'96, XJ6 '94-'97, XJ12 '94-'96, XJR '95-'97, XK8 '97-'99)
* X = Manual seat belts, Dual front airbags, &amp; Front Side Airbags (US: XJ8/XJR '98-'99)
* D = Manual seat belts, Depowered Dual front airbags, &amp; Front Side Airbags (US: XJ8/XJR '99)
* M = Manual seat belts, Driver-side airbag (Canada)
* N = Manual seat belts, Dual front airbags (Canada)
* F = Manual seat belts, Depowered Dual front airbags, &amp; Front Side Airbags (Canada: XJ8/XJR '99)

===Body Style (Position 6):===
* 1 = 4-door sedan (XJ-series sedan '81-'99)
* 2 = 2-door convertible w/2+2 seating (XJS convertible '94-'96, XK8 convertible '97-'99)
* 3 = 2-door Cabriolet (XJ-SC '86-'88)
* 4 = 2-door convertible w/2-psgr. seating (factory-built XJS convertible '89-'94, XJR-S convertible '93)
* 5 = 2-door coupe (XJS coupe '82-'96, XJR-S coupe '93, XK8 coupe '97-'99)
* 5 = 2-door coupe (Hess &amp; Eisenhardt-built XJS convertible '87-'88) [coupe conversion]

===Engine Type (Position 7):===
{| class=&quot;wikitable&quot;
|+Position 7
|-
! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications
|-
| 1 || 4.0L || I6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. [[w:Jaguar AJ6 engine#AJ16S|Jaguar AJ16S I6]]. Jaguar XJR ('95-'97).
|-
| 2 || 4.2L || I6 || Gas ||DOHC,&lt;br /&gt; 12 valve||CA &amp; Canada-spec. MPI. [[w:Jaguar XK engine|Jaguar XK I6]]. Jaguar XJ6 ('81-'82).
|-
| 2 || 4.0L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. Dual-canister evaporative emissions system. [[w:Jaguar AJ6 engine#AJ16|Jaguar AJ16 I6]]. Jaguar XJ6 ('96-'97).
|-
| 2 || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Variable intake valve timing. Dual-canister evaporative emissions system. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ26 V8 engine]].&lt;br&gt; Jaguar XJ8 ('98), XK8 ('98).
|-
| 3 || 4.2L || I6 || Gas ||DOHC,&lt;br /&gt; 12 valve||N. America-spec. MPI. [[w:Jaguar XK engine|Jaguar XK I6]]. Jaguar XJ6 ('81-'87).
|-
| 3 || 6.0L || 60° V12 || Gas ||SOHC,&lt;br /&gt; 24 valve||MPI. [[w:Jaguar V12 engine|Jaguar V12]] modified by [[w:Tom Walkinshaw Racing|JaguarSport]]. Jaguar XJR-S ('93).
|-
| 3 || 6.0L || 60° V12 || Gas ||SOHC,&lt;br /&gt; 24 valve||MPI. [[w:Jaguar V12 engine|Jaguar V12]]. Jaguar XJS ('94-'95), XJ12 ('94-'96).
|-
| 5 || 3.6L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||N. America-spec - Low Compression. MPI. [[w:Jaguar AJ6 engine|Jaguar AJ6 I6]]. Jaguar XJ6 ('88-'89).
|-
| 6 || 3.6L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||N. America-spec - High Compression. MPI. [[w:Jaguar AJ6 engine|Jaguar AJ6 I6]]. Jaguar XJ6 ('88).
|-
| 7 || 4.0L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. [[w:Jaguar AJ6 engine|Jaguar AJ6 I6]]. Jaguar XJ6 ('90-'94), XJS ('93-'94).
|-
| 7 || 4.0L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. [[w:Jaguar AJ6 engine#AJ16|Jaguar AJ16 I6]]. Jaguar XJ6 ('95-'96), XJS ('95-'96).
|-
| 7 || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ26 V8 engine]]. Jaguar XK8 ('97).
|-
| 8 || 5.3L || 60° V12 || Gas ||SOHC,&lt;br /&gt; 24 valve||N. America-spec. MPI. [[w:Jaguar V12 engine|Jaguar V12]]. Jaguar XJ-S ('82-'92), XJ12 (Canada only: '88-'92).
|-
| 8 || 4.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Dual-canister evaporative emissions system. [[w:Jaguar AJ-V8 engine#Supercharged|Jaguar AJ-V8 - AJ26S V8 engine]]. Jaguar XJR ('98-'99).
|-
| 9 || 4.0L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||Canada-spec. MPI. [[w:Jaguar AJ6 engine|Jaguar AJ6 I6]]. Jaguar XJ6 ('90-'93), XJS ('93).
|-
| 0 || 5.3L || 60° V12 || Gas ||SOHC,&lt;br /&gt; 24 valve||Canada-spec. MPI. [[w:Jaguar V12 engine|Jaguar V12]]. Jaguar XJ-S ('82-'87), XJ12 (Canada only: '85-'87).
|-
| 0 || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. Dual-canister evaporative emissions system. Enhanced evaporative emissions control system. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ27 V8 engine]]. Jaguar XJ8 ('99), XK8 ('99).
|}

===Transmission &amp; Steering Location (Position 8):===
* 4 = Automatic / LHD
* 8 = Manual / LHD ('93-'94 XJS 4.0 w/ optional 5-spd. manual)

===Check Digit/Gearbox (Position 9)===
* USA /Canada [[Vehicle Identification Numbers (VIN codes)/Check digit|Check digit]]

===Model Year Code (Position 10)===
''See: [[Vehicle Identification Numbers (VIN codes)/Model year]]''

===Plant Codes (Position 11)===
* C - Browns Lane plant, Coventry, West Midlands, England, UK

===Positions 12–17, Serial Number===
** 100001 and after - XJ-S/XJ-SC/XJS/XJR-S (XJ27)
** 300001 and after - XJ-series sedan Series III
** 500001 and after - XJ-series sedan (XJ40/XJ81)
** 720001 and after - XJ-series sedan (X300/X305/X306/X330)
** 810001 and after - XJ-series sedan (X308)
** 001001 and after - XK8 (X100)</text>
      <sha1>1pslz63etinwt04iojux9idkt0yo1bo</sha1>
    </revision>
  </page>
  <page>
    <title>Infrastructure Past, Present, and Future/Puerto Rico Electric Power System</title>
    <ns>0</ns>
    <id>485861</id>
    <revision>
      <id>4676519</id>
      <parentid>4676420</parentid>
      <timestamp>2026-10-17T13:33:14Z</timestamp>
      <contributor>
        <username>Ice waterstone</username>
        <id>3626847</id>
      </contributor>
      <comment>intro and paragraphs</comment>
      <origin>4676519</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3918" sha1="39vjvtvf6d2oebrkjy4q7vxlctgfwoj" xml:space="preserve">(This wikibooks, expected completion by 11/13)

Introduction 

Puerto Rico's electric power system provides electricity to homes, businesses, hospitals, schools, and other important services. However the system has faced several problems, including frequent outrages, aging equipment, financial difficulties, slow disaster recovery, and disagreements about how the system should be managed. For many years, the Puerto Rico Electric Power Authority (PREPA) operated the island's electricity system. Before Hurricane Maria struck in September 2017, PREPA already faced problems with old equipment, expensive fuel, limited maintenance, and large amounts of debt. 

Hurricanes Irma and Maria exposed these weaknesses and caused widespread damaged to the power grid (Sotomayor, 2020; Government of Puerto Rico, 2018). Since the hurricanes, Puerto Rico has tried to repair the grid while also changing how it is managed. Private companies have taken over certain operations, the federal government has provided recovery funding, and communities have explored renewable energy and battery storage. However, these changes have not solved every problem. For example, government reports have continued to identity power outrages and delays in completing recovery projects (Congressional Research Service [CRS, 2025; U.S. Government Accountability Office [GAO], 2026).

Hurricane Maria and the Failure of the Power Grid

Puerto Rico's power grid already had serious weaknesses before Hurricane Maria struck on September 20, 2017. Hurricane Irma had passed near the island earlier that month, damaging electricity, water, and communication systems. Maria then caused much more wide spread damaged, leaving many residents without electricity for long periods (Sotomayor, 2020).

One problem was the way electricity was produced and transported across the island. Many major power plants were located in southern Puerto Rico, while much of the electricity demand was in the north. Only a limited number of high voltage transmission lines connected these areas. This made the system vulnerable because damage to a major transmission line could prevent electricity from reaching communities that needed it (Sotomayor, 2020). For example, if a major power plant in the south stopped working during a hurricane, the remaining power plants and transmission lines would have to carry more of the electricity demand. If several transmission lines were also damaged, the system might not be able to deliver enough electricity to the north, This shows how damage to a few important parts of a centralized system can affect many customers.

Puerto Rico also depended heavily on imported fuels, including oil, natural gas, and coal, This meant that electricity production relied on fuel shipments and port facilities. If a hurricane damaged a port or disrupted fuel deliveries, power plants could face additional problems obtaining the fuel they needed (Sotomayor, 2020; CRS, 2025). The hurricanes showed that simply replacing damaged equipment would not be enough. Puerto Rico also needed stronger infrastructure, regular maintenance, and better plans for handling future storms. For example, stronger transmission poles and better protected substations could help reduce storm damage, while backup power systems could help essential service continue operating during outrages.


&lt;mapframe latitude=&quot;18.318026&quot; longitude=&quot;-66.269531&quot; zoom=&quot;8&quot; width=&quot;400&quot; height=&quot;278&quot; text=&quot;Map of Puerto Rico&quot; align=&quot;center&quot; /&gt;

== Test Chart ==
&lt;timeline&gt;
DateFormat = yyyy
ImageSize  = width:400 height:160
PlotArea   = left:40 bottom:30 top:10 right:10
Period     = from:0 till:100
TimeAxis   = orientation:vertical

Colors     =
  id:barcolor value:rgb(0.2,0.5,0.8)

BarData =
  bar:A text:A
  bar:B text:B
  bar:C text:C

PlotData =
  width:25 color:barcolor
  bar:A from:0 till:25
  bar:B from:0 till:45
  bar:C from:0 till:70
&lt;/timeline&gt;

{{BookCat}}</text>
      <sha1>39vjvtvf6d2oebrkjy4q7vxlctgfwoj</sha1>
    </revision>
    <revision>
      <id>4676528</id>
      <parentid>4676519</parentid>
      <timestamp>2026-10-17T13:58:28Z</timestamp>
      <contributor>
        <username>Ice waterstone</username>
        <id>3626847</id>
      </contributor>
      <comment>paragraphs</comment>
      <origin>4676528</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="5737" sha1="shibsjtcevgvrrspbjpx93jtmsiyx1l" xml:space="preserve">(This wikibooks, expected completion by 11/13)

Introduction 

Puerto Rico's electric power system provides electricity to homes, businesses, hospitals, schools, and other important services. However the system has faced several problems, including frequent outrages, aging equipment, financial difficulties, slow disaster recovery, and disagreements about how the system should be managed. For many years, the Puerto Rico Electric Power Authority (PREPA) operated the island's electricity system. Before Hurricane Maria struck in September 2017, PREPA already faced problems with old equipment, expensive fuel, limited maintenance, and large amounts of debt. 

Hurricanes Irma and Maria exposed these weaknesses and caused widespread damaged to the power grid (Sotomayor, 2020; Government of Puerto Rico, 2018). Since the hurricanes, Puerto Rico has tried to repair the grid while also changing how it is managed. Private companies have taken over certain operations, the federal government has provided recovery funding, and communities have explored renewable energy and battery storage. However, these changes have not solved every problem. For example, government reports have continued to identity power outrages and delays in completing recovery projects (Congressional Research Service [CRS, 2025; U.S. Government Accountability Office [GAO], 2026).

Hurricane Maria and the Failure of the Power Grid

Puerto Rico's power grid already had serious weaknesses before Hurricane Maria struck on September 20, 2017. Hurricane Irma had passed near the island earlier that month, damaging electricity, water, and communication systems. Maria then caused much more wide spread damaged, leaving many residents without electricity for long periods (Sotomayor, 2020).

One problem was the way electricity was produced and transported across the island. Many major power plants were located in southern Puerto Rico, while much of the electricity demand was in the north. Only a limited number of high voltage transmission lines connected these areas. This made the system vulnerable because damage to a major transmission line could prevent electricity from reaching communities that needed it (Sotomayor, 2020). For example, if a major power plant in the south stopped working during a hurricane, the remaining power plants and transmission lines would have to carry more of the electricity demand. If several transmission lines were also damaged, the system might not be able to deliver enough electricity to the north, This shows how damage to a few important parts of a centralized system can affect many customers.

Puerto Rico also depended heavily on imported fuels, including oil, natural gas, and coal, This meant that electricity production relied on fuel shipments and port facilities. If a hurricane damaged a port or disrupted fuel deliveries, power plants could face additional problems obtaining the fuel they needed (Sotomayor, 2020; CRS, 2025). The hurricanes showed that simply replacing damaged equipment would not be enough. Puerto Rico also needed stronger infrastructure, regular maintenance, and better plans for handling future storms. For example, stronger transmission poles and better protected substations could help reduce storm damage, while backup power systems could help essential service continue operating during outrages.


PREPA's Financial Problems and Institutional Restructuring

PREPA faced financial and operating problems for many years. Act 120-2018 described issues such as aging infrastructure, expensive fuel, poor maintenance, administrative problems, and large amounts of debt. These problems made it difficult for PREPA to pay for improvements while continuing to provide electricity (Government of Puerto Rico, 2018). The government responded by creating a legal framework that allowed private companies to take over certain operations and allowed some electricity generation assets to be sold. The goal was to improve efficiency, modernize the system, and make electricity service more financially sustainable. As part of this restructuring, LUMA began managing transmission and distribution operations on June 1, 2021.  Genera Puerto Rico began managing most non hydroelectric generation operations on July 1, 2023, while PREPA continued operating its hydroelectric plants (CRS, 2025).

This division of responsibilities can make coordination especially important. For example, when a neighborhood loses power because a distribution line is damaged, the organization responsible for that line must identify the problem and arrange repairs. If the repair also requires coordination with a power plant operator or another agency, the organizations must communicate clearly to restore service as quickly as possible. Changing who management structure, however, does not automatically repair old power lines or prevent future outrages. The CRS reported that Puerto Rico continued to experience partial and island wide blackouts in 2025 (CRS, 2025). This shows why the results of restructuring should be judged by actual improvements, such as fewer outrages, faster repairs, better maintenance, and more affordable electricity.


&lt;mapframe latitude=&quot;18.318026&quot; longitude=&quot;-66.269531&quot; zoom=&quot;8&quot; width=&quot;400&quot; height=&quot;278&quot; text=&quot;Map of Puerto Rico&quot; align=&quot;center&quot; /&gt;

== Test Chart ==
&lt;timeline&gt;
DateFormat = yyyy
ImageSize  = width:400 height:160
PlotArea   = left:40 bottom:30 top:10 right:10
Period     = from:0 till:100
TimeAxis   = orientation:vertical

Colors     =
  id:barcolor value:rgb(0.2,0.5,0.8)

BarData =
  bar:A text:A
  bar:B text:B
  bar:C text:C

PlotData =
  width:25 color:barcolor
  bar:A from:0 till:25
  bar:B from:0 till:45
  bar:C from:0 till:70
&lt;/timeline&gt;

{{BookCat}}</text>
      <sha1>shibsjtcevgvrrspbjpx93jtmsiyx1l</sha1>
    </revision>
    <revision>
      <id>4676672</id>
      <parentid>4676528</parentid>
      <timestamp>2026-10-18T03:10:28Z</timestamp>
      <contributor>
        <username>Ice waterstone</username>
        <id>3626847</id>
      </contributor>
      <comment>Draft of our data and research</comment>
      <origin>4676672</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="19182" sha1="sfxfmnyxj7c2grldsjay6ny98chtuft" xml:space="preserve">
=== Introduction ===
Puerto Rico’s electric power system provides electricity to homes, businesses, hospitals, schools, and other important services. However, the system has faced several problems, including frequent outages, aging equipment, financial difficulties, slow disaster recovery, and disagreements about how the system should be managed. For many years, the Puerto Rico Electric Power Authority (PREPA) operated the island’s electricity system. Before Hurricane Maria struck in September 2017, PREPA already faced problems with old equipment, expensive fuel, limited maintenance, and large amounts of debt. Hurricanes Irma and Maria exposed these weaknesses and caused widespread damage to the power grid (Sotomayor, 2020; Government of Puerto Rico, 2018).

Since the hurricanes, Puerto Rico has tried to repair the grid while also changing how it is managed. Private companies have taken over certain operations, the federal government has provided recovery funding, and communities have explored renewable energy and battery storage. However, these changes have not solved every problem. For example, government reports have continued to identify power outages and delays in completing recovery projects (Congressional Research Service [CRS], 2025; U.S. Government Accountability Office [GAO], 2026). This casebook examines how Puerto Rico is trying to improve its electricity system while continuing to provide power to the people who depend on it. Its main question is: Can a failing system be transformed while it must continue providing service?&lt;mapframe latitude=&quot;18.318026&quot; longitude=&quot;-66.269531&quot; zoom=&quot;8&quot; width=&quot;400&quot; height=&quot;278&quot; text=&quot;Map of Puerto Rico&quot; align=&quot;center&quot; /&gt;

=== Hurricane Maria and the Failure of the Power Grid ===
Puerto Rico’s power grid already had serious weaknesses before Hurricane Maria struck on September 20, 2017. Hurricane Irma had passed near the island earlier that month, damaging electricity, water, and communication systems. Maria then caused much more widespread damage, leaving many residents without electricity for long periods (Sotomayor, 2020). One problem was the way electricity was produced and transported across the island. Many major power plants were located in southern Puerto Rico, while much of the electricity demand was in the north. Only a limited number of high-voltage transmission lines connected these areas. 

This made the system vulnerable because damage to a major transmission line could prevent electricity from reaching communities that needed it (Sotomayor, 2020). For example, if a major power plant in the south stopped working during a hurricane, the remaining power plants and transmission lines would have to carry more of the electricity demand. If several transmission lines were also damaged, the system might not be able to deliver enough electricity to the north. This shows how damage to a few important parts of a centralized system can affect many customers.

Puerto Rico also depended heavily on imported fuels, including oil, natural gas, and coal. This meant that electricity production relied on fuel shipments and port facilities. If a hurricane damaged a port or disrupted fuel deliveries, power plants could face additional problems obtaining the fuel they needed (Sotomayor, 2020; CRS, 2025). The hurricanes showed that simply replacing damaged equipment would not be enough. Puerto Rico also needed stronger infrastructure, regular maintenance, and better plans for handling future storms. For example, stronger transmission poles and better-protected substations could help reduce storm damage, while backup power systems could help essential services continue operating during outages. The main lesson is Puerto Rico’s experience shows that a power system must be designed to withstand disasters, not just operate during normal conditions.

=== PREPA’s Financial Problems and Institutional Restructuring ===
PREPA faced financial and operating problems for many years. Act 120-2018 described issues such as aging infrastructure, expensive fuel, poor maintenance, administrative problems, and large amounts of debt. These problems made it difficult for PREPA to pay for improvements while continuing to provide electricity (Government of Puerto Rico, 2018). The government responded by creating a legal framework that allowed private companies to take over certain operations and allowed some electricity-generation assets to be sold. The goal was to improve efficiency, modernize the system, and make electricity service more financially sustainable. As part of this restructuring, LUMA began managing transmission and distribution operations on June 1, 2021. Genera Puerto Rico began managing most non-hydroelectric generation operations on July 1, 2023, while PREPA continued operating its hydroelectric plants (CRS, 2025).

This division of responsibilities can make coordination especially important. For example, when a neighborhood loses power because a distribution line is damaged, the organization responsible for that line must identify the problem and arrange repairs. If the  repair also requires coordination with a power plant operator or another agency, the organizations must communicate clearly to restore service as quickly as possible. Changing the management structure, however, does not automatically repair old power lines or prevent future outages. The CRS reported that Puerto Rico continued to experience partial and island-wide blackouts in 2025 (CRS, 2025). This shows why the results of restructuring should be judged by actual improvements, such as fewer outages, faster repairs, better maintenance, and more affordable electricity. The key takeaway is changing who manages the system can be part of the solution, but the changes must lead to better service and stronger infrastructure.

=== Federal Funding and the Slow Recovery Process ===
After Hurricane Maria, Puerto Rico needed major investments to repair and improve its electricity system. Federal agencies, including FEMA, HUD, and DOE, supported recovery and modernization efforts. According to PREPA, more than $15 billion in federal funding had been awarded for the electricity system by June 2023 (CRS, 2025).However, money being awarded does not mean that construction is finished. In its May 2025 report, CRS stated that more than $10 billion in FEMA funding had been obligated for permanent work, but approximately $2 billion had been disbursed. CRS also reported that less than 1% of the $1.9 billion HUD had obligated for the electric grid had been disbursed as of July 2024 (CRS, 2025). These figures refer to different dates and stages of funding, so they should not be treated as the same measure.

Recovery can take a long time because projects require engineering plans, reviews, permits, contracts, equipment, and trained workers. GAO reported that only nine of 258 large FEMA-funded permanent grid-recovery projects had been completed by the end of 2025. It identified lengthy reviews, staff turnover, complicated funding requirements, and uncertainty about responsibilities as barriers to progress (GAO, 2026). For example, a project to replace damaged power poles may have funding available but still need engineering approval, environmental review, materials, and a contractor before construction can begin. If one of these steps is delayed, the community may continue relying on damaged or outdated infrastructure while the project waits to move forward. To improve recovery, government agencies need to coordinate their work, make responsibilities clear, and explain delays to the public. They should also report how much money has been spent, which projects have been completed, and whether the work has improved electricity service. The main lesson is Federal funding is important, but it must be turned into completed projects that make the power system more reliable.

=== Culebra, Solar Power, and Battery Storage ===
Culebra is a small island municipality off the eastern coast of Puerto Rico. Its residents face the risk of long electricity interruptions when storms damage the wider power system. These outages can affect everyday needs, such as keeping food refrigerated, charging communication devices, and operating medical equipment (Environmental Defense Fund [EDF], 2026). In a 2020 master’s paper, Federico Sotomayor examined the possibility of building a utility-scale solar farm on Culebra. The proposal was intended to increase local electricity production and reduce dependence on the main power system. EDF later described a community-focused project involving residential solar panels and battery storage to help participating households lower energy costs and maintain essential electricity during outages (Sotomayor, 2020; EDF, 2026).

Solar panels produce electricity when sunlight is available, while batteries store some of that electricity for later use. For example, if a hurricane causes the main grid to fail in the evening, a home with solar panels and a properly configured battery may still be able to power selected appliances. A home with solar panels but no suitable backup equipment may lose power when the grid goes down, even if the panels themselves are undamaged. Local solar and battery systems could give Culebra more options during outages. However, they are not a complete solution by themselves. Installing these systems can be expensive, and some residents may need financial assistance to participate. 

Equipment must also be installed correctly, maintained, and protected from severe weather. A utility-scale solar farm would face additional challenges, including finding suitable land, connecting to the local grid, and determining how much electricity and storage the island would need. The proposal described by Sotomayor should not be treated as proof that the proposed solar farm was built. EDF’s description of residential solar and battery work is a separate community-based approach (Sotomayor, 2020; EDF, 2026). The key takeaway is local renewable energy can help communities prepare for outages, but projects must be affordable, properly designed, and supported over time.

=== Renewable Energy Goals and the Future of Puerto Rico’s Grid ===
Puerto Rico has been working toward a cleaner electricity system, but there are different views about how quickly the transition should happen and which energy sources should be used. Act 17-2019 established a goal of obtaining 100% of Puerto Rico’s electricity from renewable sources by 2050, with earlier targets for 2025 and 2040. Act 1-2025 removed those interim targets and extended the planned end of coal use from 2028 to 2032 (CRS, 2025).Renewable energy can reduce the need to import fossil fuels, but solar and wind power must be supported by equipment that helps deliver electricity when and where it is needed. For example, solar panels may produce plenty of electricity on a sunny afternoon, but they do not produce electricity after sunset. Batteries, other generating sources, and a well-planned grid are needed to help meet demand at night.

Puerto Rico must also make sure that new energy projects can connect to its existing infrastructure. If a solar farm is built in an area where transmission lines cannot carry the additional electricity, the project may not provide its full intended benefit. This is why renewable-energy development must happen alongside improvements to transmission, distribution, storage, and system controls (CRS, 2025; EDF, 2026). The transition also raises questions about affordability. A household that can afford rooftop solar and batteries may have more options during an outage, while a household with fewer financial resources may still depend entirely on the wider grid. 

Support programs and community-based projects can help ensure that improvements reach people who need them most (EDF, 2026). Puerto Rico therefore needs a plan that addresses immediate reliability problems while also preparing for a cleaner energy future. This means repairing the existing grid, improving storage and transmission, expanding renewable energy where suitable, and keeping electricity affordable. The main lesson is reliable electricity and renewable energy should be planned together. Puerto Rico needs a dependable system today while building a cleaner system for tomorrow.


{| class=&quot;wikitable&quot;
|+Timeline of Important Events
!Year
!Event
!Why it matters
|-
|2014
|Act 57 changed parts of PREPA's governance and oversight
|It was part of the effort to reform the electricity sector
|-
|2017
|Hurricanes Irma and Maria severely damaged the grid
|The storms existing infrastructure and maintenance problems
|-
|2018
|Act 120 established a framework for private-sector partcipitation
|It changed how PREPA's assets and operations could be managed
|-
|2019
|Act 17 established renewable-energy goals
|It set a long term direction for the energy transition
|-
|June
2021
|LUMA began managing transmission and distribution operations
|Responsibility for major parts of the grid shifted to a private operator
|-
|July
2023
|Genera began managing most non-hydroelectric generation operations
|Generation management became separate from transmission and distribution
|-
|2025
|Act 1 changed interim renewable-energy targets and extended planned coal use
|It changed the timeline for parts of the energy transition
|-
|2025-
2026
|Government reports continued to identify outrages and recovery delays
|They showed that improving reliability and completing recovery work remained challenges
|}
(Sources: Government of Puerto Rico, 2018; CRS, 2025; GAO, 2026.)

=== Main Organizations and Their Roles ===
PREPA is the public corporation associated with Puerto Rico’s electricity assets and financial restructuring. LUMA manages transmission and distribution operations, while Genera manages most non-hydroelectric generation operations. These different responsibilities mean that repairing a damaged power line, managing a power plant, and planning future energy projects may require coordination among several organizations (CRS, 2025). The Puerto Rico Energy Bureau regulates the energy sector, including important planning and rate decisions. Federal agencies also play major roles. 

FEMA supports eligible disaster recovery projects, HUD provides community development funding that includes grid recovery, and DOE supports energy assessments and modernization efforts. Local communities and energy partners contribute by identifying needs and developing projects such as residential solar and battery systems (CRS, 2025; GAO, 2026; EDF, 2026). For example, improving electricity service in a community may require a utility operator to repair equipment, a government agency to approve or fund a project, and local organizations to explain which services residents need most. If these groups do not coordinate, a project may be delayed or fail to address the community’s most urgent problems.

=== Can a Failing System Be Transformed While It Must Continue Providing Service? ===
Yes, but it requires careful planning, steady investment, and a balance between immediate needs and long-term improvements. Puerto Rico cannot shut down its entire electricity system while it replaces equipment and builds a new one. Hospitals, homes, businesses, schools, and emergency services still need electricity during construction and recovery. This means repairs and improvements must happen in stages. For example, crews can repair a damaged transmission line to restore electricity while engineers plan how to strengthen that line against future storms. The immediate repair helps customers today, while the longer-term improvement can reduce the chance of similar problems in the future. This approach allows the system to keep operating while parts of it are improved.

The same principle applies to management and funding. Puerto Rico has changed who operates different parts of its electricity system, but continuing outages show that organizational changes must be supported by better maintenance, clear responsibilities, and measurable improvements in service (CRS, 2025). Federal funding must also move through planning and construction so that it results in completed projects rather than remaining tied up in lengthy processes (GAO, 2026). 

Local energy projects can provide another layer of protection. Solar panels and batteries in Culebra, for example, may help participating households keep essential appliances operating during an outage. However, these systems do not replace the need for a strong island-wide grid. Both local backup systems and major infrastructure improvements are needed (Sotomayor, 2020; EDF, 2026). The best approach is to repair the most urgent problems while gradually building a stronger and more reliable system. Puerto Rico must keep electricity flowing, improve how the system is managed, complete recovery projects, and prepare for a cleaner energy future at the same time.

=== Conclusion ===
Puerto Rico’s electricity system shows how difficult it can be to transform essential infrastructure while people continue to depend on it. Hurricanes Irma and Maria exposed weaknesses that had developed over many years. Financial problems, aging equipment, and complicated recovery processes have made rebuilding difficult. Changes in management have altered who operates parts of the system, but reliable electricity remains a major concern. The case studies show that no single solution can fix every problem. 

Stronger equipment can reduce storm damage, better coordination can help recovery projects move forward, and clear oversight can improve accountability. Solar panels, batteries, and other local energy systems can also help communities maintain essential electricity during outages. Puerto Rico’s experience suggests that a failing system can be transformed while it continues to provide service, but only through careful planning, cooperation, funding, and attention to the needs of residents. The goal should not be to rebuild the old system exactly as it was. It should be to create a system that is more reliable, affordable, and prepared for future disasters.

=== References ===
Congressional Research Service. (2025). Electric reliability and resiliency in Puerto Rico (IF12913). https://www.congress.gov/crs-product/IF12913

Environmental Defense Fund. (2026, June 12). Transforming Puerto Rico’s energy system. https://www.edf.org/energy/strengthening-puerto-ricos-energy-system

Government Accountability Office. (2026). El Apagón—The Blackout: Puerto Rico’s continuing struggle for stable electricity. https://www.gao.gov/blog/el-apagon-blackout.-puerto-ricos-continuing-struggle-stable-electricity

Government of Puerto Rico. (2018). Puerto Rico Electric Power System Transformation Act, Act No. 120-2018. https://bvirtualogp.pr.gov/ogp/Bvirtual/leyesreferencia/PDF/2-ingles/120-2018.pdf

Sotomayor, F. (2020). Master’s paper on Puerto Rico’s electric power system and the potential for a utility-scale solar farm on Culebra. Clark University. https://commons.clarku.edu/cgi/viewcontent.cgi?article=1258&amp;context=idce_masters_papers</text>
      <sha1>sfxfmnyxj7c2grldsjay6ny98chtuft</sha1>
    </revision>
    <revision>
      <id>4676678</id>
      <parentid>4676672</parentid>
      <timestamp>2026-10-18T03:29:48Z</timestamp>
      <contributor>
        <username>Ice waterstone</username>
        <id>3626847</id>
      </contributor>
      <comment>image testing phase</comment>
      <origin>4676678</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="19226" sha1="n1vt37uieoqvivzcs5x4vm6tgh166fk" xml:space="preserve">
=== Introduction ===
Puerto Rico’s electric power system provides electricity to homes, businesses, hospitals, schools, and other important services. However, the system has faced several problems, including frequent outages, aging equipment, financial difficulties, slow disaster recovery, and disagreements about how the system should be managed. For many years, the Puerto Rico Electric Power Authority (PREPA) operated the island’s electricity system. Before Hurricane Maria struck in September 2017, PREPA already faced problems with old equipment, expensive fuel, limited maintenance, and large amounts of debt. Hurricanes Irma and Maria exposed these weaknesses and caused widespread damage to the power grid (Sotomayor, 2020; Government of Puerto Rico, 2018).

Since the hurricanes, Puerto Rico has tried to repair the grid while also changing how it is managed. Private companies have taken over certain operations, the federal government has provided recovery funding, and communities have explored renewable energy and battery storage. However, these changes have not solved every problem. For example, government reports have continued to identify power outages and delays in completing recovery projects (Congressional Research Service [CRS], 2025; U.S. Government Accountability Office [GAO], 2026). This casebook examines how Puerto Rico is trying to improve its electricity system while continuing to provide power to the people who depend on it. Its main question is: Can a failing system be transformed while it must continue providing service?&lt;mapframe latitude=&quot;18.318026&quot; longitude=&quot;-66.269531&quot; zoom=&quot;8&quot; width=&quot;400&quot; height=&quot;278&quot; text=&quot;Map of Puerto Rico&quot; align=&quot;center&quot; /&gt;

=== Hurricane Maria and the Failure of the Power Grid ===
Puerto Rico’s power grid already had serious weaknesses before Hurricane Maria struck on September 20, 2017. Hurricane Irma had passed near the island earlier that month, damaging electricity, water, and communication systems. Maria then caused much more widespread damage, leaving many residents without electricity for long periods (Sotomayor, 2020). One problem was the way electricity was produced and transported across the island. Many major power plants were located in southern Puerto Rico, while much of the electricity demand was in the north. Only a limited number of high-voltage transmission lines connected these areas. 

This made the system vulnerable because damage to a major transmission line could prevent electricity from reaching communities that needed it (Sotomayor, 2020). For example, if a major power plant in the south stopped working during a hurricane, the remaining power plants and transmission lines would have to carry more of the electricity demand. If several transmission lines were also damaged, the system might not be able to deliver enough electricity to the north. This shows how damage to a few important parts of a centralized system can affect many customers.

Puerto Rico also depended heavily on imported fuels, including oil, natural gas, and coal. This meant that electricity production relied on fuel shipments and port facilities. If a hurricane damaged a port or disrupted fuel deliveries, power plants could face additional problems obtaining the fuel they needed (Sotomayor, 2020; CRS, 2025). The hurricanes showed that simply replacing damaged equipment would not be enough. Puerto Rico also needed stronger infrastructure, regular maintenance, and better plans for handling future storms. For example, stronger transmission poles and better-protected substations could help reduce storm damage, while backup power systems could help essential services continue operating during outages. The main lesson is Puerto Rico’s experience shows that a power system must be designed to withstand disasters, not just operate during normal conditions.

=== PREPA’s Financial Problems and Institutional Restructuring ===
PREPA faced financial and operating problems for many years. Act 120-2018 described issues such as aging infrastructure, expensive fuel, poor maintenance, administrative problems, and large amounts of debt. These problems made it difficult for PREPA to pay for improvements while continuing to provide electricity (Government of Puerto Rico, 2018). The government responded by creating a legal framework that allowed private companies to take over certain operations and allowed some electricity-generation assets to be sold. The goal was to improve efficiency, modernize the system, and make electricity service more financially sustainable. As part of this restructuring, LUMA began managing transmission and distribution operations on June 1, 2021. Genera Puerto Rico began managing most non-hydroelectric generation operations on July 1, 2023, while PREPA continued operating its hydroelectric plants (CRS, 2025).

This division of responsibilities can make coordination especially important. For example, when a neighborhood loses power because a distribution line is damaged, the organization responsible for that line must identify the problem and arrange repairs. If the  repair also requires coordination with a power plant operator or another agency, the organizations must communicate clearly to restore service as quickly as possible. Changing the management structure, however, does not automatically repair old power lines or prevent future outages. The CRS reported that Puerto Rico continued to experience partial and island-wide blackouts in 2025 (CRS, 2025). This shows why the results of restructuring should be judged by actual improvements, such as fewer outages, faster repairs, better maintenance, and more affordable electricity. The key takeaway is changing who manages the system can be part of the solution, but the changes must lead to better service and stronger infrastructure.

=== Federal Funding and the Slow Recovery Process ===
After Hurricane Maria, Puerto Rico needed major investments to repair and improve its electricity system. Federal agencies, including FEMA, HUD, and DOE, supported recovery and modernization efforts. According to PREPA, more than $15 billion in federal funding had been awarded for the electricity system by June 2023 (CRS, 2025).However, money being awarded does not mean that construction is finished. In its May 2025 report, CRS stated that more than $10 billion in FEMA funding had been obligated for permanent work, but approximately $2 billion had been disbursed. CRS also reported that less than 1% of the $1.9 billion HUD had obligated for the electric grid had been disbursed as of July 2024 (CRS, 2025). These figures refer to different dates and stages of funding, so they should not be treated as the same measure.

Recovery can take a long time because projects require engineering plans, reviews, permits, contracts, equipment, and trained workers. GAO reported that only nine of 258 large FEMA-funded permanent grid-recovery projects had been completed by the end of 2025. It identified lengthy reviews, staff turnover, complicated funding requirements, and uncertainty about responsibilities as barriers to progress (GAO, 2026). For example, a project to replace damaged power poles may have funding available but still need engineering approval, environmental review, materials, and a contractor before construction can begin. If one of these steps is delayed, the community may continue relying on damaged or outdated infrastructure while the project waits to move forward. To improve recovery, government agencies need to coordinate their work, make responsibilities clear, and explain delays to the public. They should also report how much money has been spent, which projects have been completed, and whether the work has improved electricity service. The main lesson is Federal funding is important, but it must be turned into completed projects that make the power system more reliable.

=== Culebra, Solar Power, and Battery Storage ===
Culebra is a small island municipality off the eastern coast of Puerto Rico. Its residents face the risk of long electricity interruptions when storms damage the wider power system. These outages can affect everyday needs, such as keeping food refrigerated, charging communication devices, and operating medical equipment (Environmental Defense Fund [EDF], 2026). In a 2020 master’s paper, Federico Sotomayor examined the possibility of building a utility-scale solar farm on Culebra. The proposal was intended to increase local electricity production and reduce dependence on the main power system. EDF later described a community-focused project involving residential solar panels and battery storage to help participating households lower energy costs and maintain essential electricity during outages (Sotomayor, 2020; EDF, 2026).

Solar panels produce electricity when sunlight is available, while batteries store some of that electricity for later use. For example, if a hurricane causes the main grid to fail in the evening, a home with solar panels and a properly configured battery may still be able to power selected appliances. A home with solar panels but no suitable backup equipment may lose power when the grid goes down, even if the panels themselves are undamaged. Local solar and battery systems could give Culebra more options during outages. However, they are not a complete solution by themselves. Installing these systems can be expensive, and some residents may need financial assistance to participate. 

Equipment must also be installed correctly, maintained, and protected from severe weather. A utility-scale solar farm would face additional challenges, including finding suitable land, connecting to the local grid, and determining how much electricity and storage the island would need. The proposal described by Sotomayor should not be treated as proof that the proposed solar farm was built. EDF’s description of residential solar and battery work is a separate community-based approach (Sotomayor, 2020; EDF, 2026). The key takeaway is local renewable energy can help communities prepare for outages, but projects must be affordable, properly designed, and supported over time.


=== Renewable Energy Goals and the Future of Puerto Rico’s Grid ===
Puerto Rico has been working toward a cleaner electricity system, but there are different views about how quickly the transition should happen and which energy sources should be used. Act 17-2019 established a goal of obtaining 100% of Puerto Rico’s electricity from renewable sources by 2050, with earlier targets for 2025 and 2040. Act 1-2025 removed those interim targets and extended the planned end of coal use from 2028 to 2032 (CRS, 2025).Renewable energy can reduce the need to import fossil fuels, but solar and wind power must be supported by equipment that helps deliver electricity when and where it is needed. For example, solar panels may produce plenty of electricity on a sunny afternoon, but they do not produce electricity after sunset. Batteries, other generating sources, and a well-planned grid are needed to help meet demand at night.

Puerto Rico must also make sure that new energy projects can connect to its existing infrastructure. If a solar farm is built in an area where transmission lines cannot carry the additional electricity, the project may not provide its full intended benefit. This is why renewable-energy development must happen alongside improvements to transmission, distribution, storage, and system controls (CRS, 2025; EDF, 2026). The transition also raises questions about affordability. A household that can afford rooftop solar and batteries may have more options during an outage, while a household with fewer financial resources may still depend entirely on the wider grid. 

Support programs and community-based projects can help ensure that improvements reach people who need them most (EDF, 2026). Puerto Rico therefore needs a plan that addresses immediate reliability problems while also preparing for a cleaner energy future. This means repairing the existing grid, improving storage and transmission, expanding renewable energy where suitable, and keeping electricity affordable. The main lesson is reliable electricity and renewable energy should be planned together. Puerto Rico needs a dependable system today while building a cleaner system for tomorrow.


[[File:Civil engineering practice.png]]


{| class=&quot;wikitable&quot;
|+Timeline of Important Events
!Year
!Event
!Why it matters
|-
|2014
|Act 57 changed parts of PREPA's governance and oversight
|It was part of the effort to reform the electricity sector
|-
|2017
|Hurricanes Irma and Maria severely damaged the grid
|The storms existing infrastructure and maintenance problems
|-
|2018
|Act 120 established a framework for private-sector partcipitation
|It changed how PREPA's assets and operations could be managed
|-
|2019
|Act 17 established renewable-energy goals
|It set a long term direction for the energy transition
|-
|June
2021
|LUMA began managing transmission and distribution operations
|Responsibility for major parts of the grid shifted to a private operator
|-
|July
2023
|Genera began managing most non-hydroelectric generation operations
|Generation management became separate from transmission and distribution
|-
|2025
|Act 1 changed interim renewable-energy targets and extended planned coal use
|It changed the timeline for parts of the energy transition
|-
|2025-
2026
|Government reports continued to identify outrages and recovery delays
|They showed that improving reliability and completing recovery work remained challenges
|}
(Sources: Government of Puerto Rico, 2018; CRS, 2025; GAO, 2026.)

=== Main Organizations and Their Roles ===
PREPA is the public corporation associated with Puerto Rico’s electricity assets and financial restructuring. LUMA manages transmission and distribution operations, while Genera manages most non-hydroelectric generation operations. These different responsibilities mean that repairing a damaged power line, managing a power plant, and planning future energy projects may require coordination among several organizations (CRS, 2025). The Puerto Rico Energy Bureau regulates the energy sector, including important planning and rate decisions. Federal agencies also play major roles. 

FEMA supports eligible disaster recovery projects, HUD provides community development funding that includes grid recovery, and DOE supports energy assessments and modernization efforts. Local communities and energy partners contribute by identifying needs and developing projects such as residential solar and battery systems (CRS, 2025; GAO, 2026; EDF, 2026). For example, improving electricity service in a community may require a utility operator to repair equipment, a government agency to approve or fund a project, and local organizations to explain which services residents need most. If these groups do not coordinate, a project may be delayed or fail to address the community’s most urgent problems.

=== Can a Failing System Be Transformed While It Must Continue Providing Service? ===
Yes, but it requires careful planning, steady investment, and a balance between immediate needs and long-term improvements. Puerto Rico cannot shut down its entire electricity system while it replaces equipment and builds a new one. Hospitals, homes, businesses, schools, and emergency services still need electricity during construction and recovery. This means repairs and improvements must happen in stages. For example, crews can repair a damaged transmission line to restore electricity while engineers plan how to strengthen that line against future storms. The immediate repair helps customers today, while the longer-term improvement can reduce the chance of similar problems in the future. This approach allows the system to keep operating while parts of it are improved.

The same principle applies to management and funding. Puerto Rico has changed who operates different parts of its electricity system, but continuing outages show that organizational changes must be supported by better maintenance, clear responsibilities, and measurable improvements in service (CRS, 2025). Federal funding must also move through planning and construction so that it results in completed projects rather than remaining tied up in lengthy processes (GAO, 2026). 

Local energy projects can provide another layer of protection. Solar panels and batteries in Culebra, for example, may help participating households keep essential appliances operating during an outage. However, these systems do not replace the need for a strong island-wide grid. Both local backup systems and major infrastructure improvements are needed (Sotomayor, 2020; EDF, 2026). The best approach is to repair the most urgent problems while gradually building a stronger and more reliable system. Puerto Rico must keep electricity flowing, improve how the system is managed, complete recovery projects, and prepare for a cleaner energy future at the same time.

=== Conclusion ===
Puerto Rico’s electricity system shows how difficult it can be to transform essential infrastructure while people continue to depend on it. Hurricanes Irma and Maria exposed weaknesses that had developed over many years. Financial problems, aging equipment, and complicated recovery processes have made rebuilding difficult. Changes in management have altered who operates parts of the system, but reliable electricity remains a major concern. The case studies show that no single solution can fix every problem. 

Stronger equipment can reduce storm damage, better coordination can help recovery projects move forward, and clear oversight can improve accountability. Solar panels, batteries, and other local energy systems can also help communities maintain essential electricity during outages. Puerto Rico’s experience suggests that a failing system can be transformed while it continues to provide service, but only through careful planning, cooperation, funding, and attention to the needs of residents. The goal should not be to rebuild the old system exactly as it was. It should be to create a system that is more reliable, affordable, and prepared for future disasters.

=== References ===
Congressional Research Service. (2025). Electric reliability and resiliency in Puerto Rico (IF12913). https://www.congress.gov/crs-product/IF12913

Environmental Defense Fund. (2026, June 12). Transforming Puerto Rico’s energy system. https://www.edf.org/energy/strengthening-puerto-ricos-energy-system

Government Accountability Office. (2026). El Apagón—The Blackout: Puerto Rico’s continuing struggle for stable electricity. https://www.gao.gov/blog/el-apagon-blackout.-puerto-ricos-continuing-struggle-stable-electricity

Government of Puerto Rico. (2018). Puerto Rico Electric Power System Transformation Act, Act No. 120-2018. https://bvirtualogp.pr.gov/ogp/Bvirtual/leyesreferencia/PDF/2-ingles/120-2018.pdf

Sotomayor, F. (2020). Master’s paper on Puerto Rico’s electric power system and the potential for a utility-scale solar farm on Culebra. Clark University. https://commons.clarku.edu/cgi/viewcontent.cgi?article=1258&amp;context=idce_masters_papers</text>
      <sha1>n1vt37uieoqvivzcs5x4vm6tgh166fk</sha1>
    </revision>
    <revision>
      <id>4676679</id>
      <parentid>4676678</parentid>
      <timestamp>2026-10-18T03:30:38Z</timestamp>
      <contributor>
        <username>Ice waterstone</username>
        <id>3626847</id>
      </contributor>
      <comment>deleting image</comment>
      <origin>4676679</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="19185" sha1="5znkw5o6nh9m5wiahz8kmfy5276qgza" xml:space="preserve">
=== Introduction ===
Puerto Rico’s electric power system provides electricity to homes, businesses, hospitals, schools, and other important services. However, the system has faced several problems, including frequent outages, aging equipment, financial difficulties, slow disaster recovery, and disagreements about how the system should be managed. For many years, the Puerto Rico Electric Power Authority (PREPA) operated the island’s electricity system. Before Hurricane Maria struck in September 2017, PREPA already faced problems with old equipment, expensive fuel, limited maintenance, and large amounts of debt. Hurricanes Irma and Maria exposed these weaknesses and caused widespread damage to the power grid (Sotomayor, 2020; Government of Puerto Rico, 2018).

Since the hurricanes, Puerto Rico has tried to repair the grid while also changing how it is managed. Private companies have taken over certain operations, the federal government has provided recovery funding, and communities have explored renewable energy and battery storage. However, these changes have not solved every problem. For example, government reports have continued to identify power outages and delays in completing recovery projects (Congressional Research Service [CRS], 2025; U.S. Government Accountability Office [GAO], 2026). This casebook examines how Puerto Rico is trying to improve its electricity system while continuing to provide power to the people who depend on it. Its main question is: Can a failing system be transformed while it must continue providing service?&lt;mapframe latitude=&quot;18.318026&quot; longitude=&quot;-66.269531&quot; zoom=&quot;8&quot; width=&quot;400&quot; height=&quot;278&quot; text=&quot;Map of Puerto Rico&quot; align=&quot;center&quot; /&gt;

=== Hurricane Maria and the Failure of the Power Grid ===
Puerto Rico’s power grid already had serious weaknesses before Hurricane Maria struck on September 20, 2017. Hurricane Irma had passed near the island earlier that month, damaging electricity, water, and communication systems. Maria then caused much more widespread damage, leaving many residents without electricity for long periods (Sotomayor, 2020). One problem was the way electricity was produced and transported across the island. Many major power plants were located in southern Puerto Rico, while much of the electricity demand was in the north. Only a limited number of high-voltage transmission lines connected these areas. 

This made the system vulnerable because damage to a major transmission line could prevent electricity from reaching communities that needed it (Sotomayor, 2020). For example, if a major power plant in the south stopped working during a hurricane, the remaining power plants and transmission lines would have to carry more of the electricity demand. If several transmission lines were also damaged, the system might not be able to deliver enough electricity to the north. This shows how damage to a few important parts of a centralized system can affect many customers.

Puerto Rico also depended heavily on imported fuels, including oil, natural gas, and coal. This meant that electricity production relied on fuel shipments and port facilities. If a hurricane damaged a port or disrupted fuel deliveries, power plants could face additional problems obtaining the fuel they needed (Sotomayor, 2020; CRS, 2025). The hurricanes showed that simply replacing damaged equipment would not be enough. Puerto Rico also needed stronger infrastructure, regular maintenance, and better plans for handling future storms. For example, stronger transmission poles and better-protected substations could help reduce storm damage, while backup power systems could help essential services continue operating during outages. The main lesson is Puerto Rico’s experience shows that a power system must be designed to withstand disasters, not just operate during normal conditions.

=== PREPA’s Financial Problems and Institutional Restructuring ===
PREPA faced financial and operating problems for many years. Act 120-2018 described issues such as aging infrastructure, expensive fuel, poor maintenance, administrative problems, and large amounts of debt. These problems made it difficult for PREPA to pay for improvements while continuing to provide electricity (Government of Puerto Rico, 2018). The government responded by creating a legal framework that allowed private companies to take over certain operations and allowed some electricity-generation assets to be sold. The goal was to improve efficiency, modernize the system, and make electricity service more financially sustainable. As part of this restructuring, LUMA began managing transmission and distribution operations on June 1, 2021. Genera Puerto Rico began managing most non-hydroelectric generation operations on July 1, 2023, while PREPA continued operating its hydroelectric plants (CRS, 2025).

This division of responsibilities can make coordination especially important. For example, when a neighborhood loses power because a distribution line is damaged, the organization responsible for that line must identify the problem and arrange repairs. If the  repair also requires coordination with a power plant operator or another agency, the organizations must communicate clearly to restore service as quickly as possible. Changing the management structure, however, does not automatically repair old power lines or prevent future outages. The CRS reported that Puerto Rico continued to experience partial and island-wide blackouts in 2025 (CRS, 2025). This shows why the results of restructuring should be judged by actual improvements, such as fewer outages, faster repairs, better maintenance, and more affordable electricity. The key takeaway is changing who manages the system can be part of the solution, but the changes must lead to better service and stronger infrastructure.

=== Federal Funding and the Slow Recovery Process ===
After Hurricane Maria, Puerto Rico needed major investments to repair and improve its electricity system. Federal agencies, including FEMA, HUD, and DOE, supported recovery and modernization efforts. According to PREPA, more than $15 billion in federal funding had been awarded for the electricity system by June 2023 (CRS, 2025).However, money being awarded does not mean that construction is finished. In its May 2025 report, CRS stated that more than $10 billion in FEMA funding had been obligated for permanent work, but approximately $2 billion had been disbursed. CRS also reported that less than 1% of the $1.9 billion HUD had obligated for the electric grid had been disbursed as of July 2024 (CRS, 2025). These figures refer to different dates and stages of funding, so they should not be treated as the same measure.

Recovery can take a long time because projects require engineering plans, reviews, permits, contracts, equipment, and trained workers. GAO reported that only nine of 258 large FEMA-funded permanent grid-recovery projects had been completed by the end of 2025. It identified lengthy reviews, staff turnover, complicated funding requirements, and uncertainty about responsibilities as barriers to progress (GAO, 2026). For example, a project to replace damaged power poles may have funding available but still need engineering approval, environmental review, materials, and a contractor before construction can begin. If one of these steps is delayed, the community may continue relying on damaged or outdated infrastructure while the project waits to move forward. To improve recovery, government agencies need to coordinate their work, make responsibilities clear, and explain delays to the public. They should also report how much money has been spent, which projects have been completed, and whether the work has improved electricity service. The main lesson is Federal funding is important, but it must be turned into completed projects that make the power system more reliable.

=== Culebra, Solar Power, and Battery Storage ===
Culebra is a small island municipality off the eastern coast of Puerto Rico. Its residents face the risk of long electricity interruptions when storms damage the wider power system. These outages can affect everyday needs, such as keeping food refrigerated, charging communication devices, and operating medical equipment (Environmental Defense Fund [EDF], 2026). In a 2020 master’s paper, Federico Sotomayor examined the possibility of building a utility-scale solar farm on Culebra. The proposal was intended to increase local electricity production and reduce dependence on the main power system. EDF later described a community-focused project involving residential solar panels and battery storage to help participating households lower energy costs and maintain essential electricity during outages (Sotomayor, 2020; EDF, 2026).

Solar panels produce electricity when sunlight is available, while batteries store some of that electricity for later use. For example, if a hurricane causes the main grid to fail in the evening, a home with solar panels and a properly configured battery may still be able to power selected appliances. A home with solar panels but no suitable backup equipment may lose power when the grid goes down, even if the panels themselves are undamaged. Local solar and battery systems could give Culebra more options during outages. However, they are not a complete solution by themselves. Installing these systems can be expensive, and some residents may need financial assistance to participate. 

Equipment must also be installed correctly, maintained, and protected from severe weather. A utility-scale solar farm would face additional challenges, including finding suitable land, connecting to the local grid, and determining how much electricity and storage the island would need. The proposal described by Sotomayor should not be treated as proof that the proposed solar farm was built. EDF’s description of residential solar and battery work is a separate community-based approach (Sotomayor, 2020; EDF, 2026). The key takeaway is local renewable energy can help communities prepare for outages, but projects must be affordable, properly designed, and supported over time.


=== Renewable Energy Goals and the Future of Puerto Rico’s Grid ===
Puerto Rico has been working toward a cleaner electricity system, but there are different views about how quickly the transition should happen and which energy sources should be used. Act 17-2019 established a goal of obtaining 100% of Puerto Rico’s electricity from renewable sources by 2050, with earlier targets for 2025 and 2040. Act 1-2025 removed those interim targets and extended the planned end of coal use from 2028 to 2032 (CRS, 2025).Renewable energy can reduce the need to import fossil fuels, but solar and wind power must be supported by equipment that helps deliver electricity when and where it is needed. For example, solar panels may produce plenty of electricity on a sunny afternoon, but they do not produce electricity after sunset. Batteries, other generating sources, and a well-planned grid are needed to help meet demand at night.

Puerto Rico must also make sure that new energy projects can connect to its existing infrastructure. If a solar farm is built in an area where transmission lines cannot carry the additional electricity, the project may not provide its full intended benefit. This is why renewable-energy development must happen alongside improvements to transmission, distribution, storage, and system controls (CRS, 2025; EDF, 2026). The transition also raises questions about affordability. A household that can afford rooftop solar and batteries may have more options during an outage, while a household with fewer financial resources may still depend entirely on the wider grid. 

Support programs and community-based projects can help ensure that improvements reach people who need them most (EDF, 2026). Puerto Rico therefore needs a plan that addresses immediate reliability problems while also preparing for a cleaner energy future. This means repairing the existing grid, improving storage and transmission, expanding renewable energy where suitable, and keeping electricity affordable. The main lesson is reliable electricity and renewable energy should be planned together. Puerto Rico needs a dependable system today while building a cleaner system for tomorrow.


{| class=&quot;wikitable&quot;
|+Timeline of Important Events
!Year
!Event
!Why it matters
|-
|2014
|Act 57 changed parts of PREPA's governance and oversight
|It was part of the effort to reform the electricity sector
|-
|2017
|Hurricanes Irma and Maria severely damaged the grid
|The storms existing infrastructure and maintenance problems
|-
|2018
|Act 120 established a framework for private-sector partcipitation
|It changed how PREPA's assets and operations could be managed
|-
|2019
|Act 17 established renewable-energy goals
|It set a long term direction for the energy transition
|-
|June
2021
|LUMA began managing transmission and distribution operations
|Responsibility for major parts of the grid shifted to a private operator
|-
|July
2023
|Genera began managing most non-hydroelectric generation operations
|Generation management became separate from transmission and distribution
|-
|2025
|Act 1 changed interim renewable-energy targets and extended planned coal use
|It changed the timeline for parts of the energy transition
|-
|2025-
2026
|Government reports continued to identify outrages and recovery delays
|They showed that improving reliability and completing recovery work remained challenges
|}
(Sources: Government of Puerto Rico, 2018; CRS, 2025; GAO, 2026.)

=== Main Organizations and Their Roles ===
PREPA is the public corporation associated with Puerto Rico’s electricity assets and financial restructuring. LUMA manages transmission and distribution operations, while Genera manages most non-hydroelectric generation operations. These different responsibilities mean that repairing a damaged power line, managing a power plant, and planning future energy projects may require coordination among several organizations (CRS, 2025). The Puerto Rico Energy Bureau regulates the energy sector, including important planning and rate decisions. Federal agencies also play major roles. 

FEMA supports eligible disaster recovery projects, HUD provides community development funding that includes grid recovery, and DOE supports energy assessments and modernization efforts. Local communities and energy partners contribute by identifying needs and developing projects such as residential solar and battery systems (CRS, 2025; GAO, 2026; EDF, 2026). For example, improving electricity service in a community may require a utility operator to repair equipment, a government agency to approve or fund a project, and local organizations to explain which services residents need most. If these groups do not coordinate, a project may be delayed or fail to address the community’s most urgent problems.

=== Can a Failing System Be Transformed While It Must Continue Providing Service? ===
Yes, but it requires careful planning, steady investment, and a balance between immediate needs and long-term improvements. Puerto Rico cannot shut down its entire electricity system while it replaces equipment and builds a new one. Hospitals, homes, businesses, schools, and emergency services still need electricity during construction and recovery. This means repairs and improvements must happen in stages. For example, crews can repair a damaged transmission line to restore electricity while engineers plan how to strengthen that line against future storms. The immediate repair helps customers today, while the longer-term improvement can reduce the chance of similar problems in the future. This approach allows the system to keep operating while parts of it are improved.

The same principle applies to management and funding. Puerto Rico has changed who operates different parts of its electricity system, but continuing outages show that organizational changes must be supported by better maintenance, clear responsibilities, and measurable improvements in service (CRS, 2025). Federal funding must also move through planning and construction so that it results in completed projects rather than remaining tied up in lengthy processes (GAO, 2026). 

Local energy projects can provide another layer of protection. Solar panels and batteries in Culebra, for example, may help participating households keep essential appliances operating during an outage. However, these systems do not replace the need for a strong island-wide grid. Both local backup systems and major infrastructure improvements are needed (Sotomayor, 2020; EDF, 2026). The best approach is to repair the most urgent problems while gradually building a stronger and more reliable system. Puerto Rico must keep electricity flowing, improve how the system is managed, complete recovery projects, and prepare for a cleaner energy future at the same time.

=== Conclusion ===
Puerto Rico’s electricity system shows how difficult it can be to transform essential infrastructure while people continue to depend on it. Hurricanes Irma and Maria exposed weaknesses that had developed over many years. Financial problems, aging equipment, and complicated recovery processes have made rebuilding difficult. Changes in management have altered who operates parts of the system, but reliable electricity remains a major concern. The case studies show that no single solution can fix every problem. 

Stronger equipment can reduce storm damage, better coordination can help recovery projects move forward, and clear oversight can improve accountability. Solar panels, batteries, and other local energy systems can also help communities maintain essential electricity during outages. Puerto Rico’s experience suggests that a failing system can be transformed while it continues to provide service, but only through careful planning, cooperation, funding, and attention to the needs of residents. The goal should not be to rebuild the old system exactly as it was. It should be to create a system that is more reliable, affordable, and prepared for future disasters.

=== References ===
Congressional Research Service. (2025). Electric reliability and resiliency in Puerto Rico (IF12913). https://www.congress.gov/crs-product/IF12913

Environmental Defense Fund. (2026, June 12). Transforming Puerto Rico’s energy system. https://www.edf.org/energy/strengthening-puerto-ricos-energy-system

Government Accountability Office. (2026). El Apagón—The Blackout: Puerto Rico’s continuing struggle for stable electricity. https://www.gao.gov/blog/el-apagon-blackout.-puerto-ricos-continuing-struggle-stable-electricity

Government of Puerto Rico. (2018). Puerto Rico Electric Power System Transformation Act, Act No. 120-2018. https://bvirtualogp.pr.gov/ogp/Bvirtual/leyesreferencia/PDF/2-ingles/120-2018.pdf

Sotomayor, F. (2020). Master’s paper on Puerto Rico’s electric power system and the potential for a utility-scale solar farm on Culebra. Clark University. https://commons.clarku.edu/cgi/viewcontent.cgi?article=1258&amp;context=idce_masters_papers</text>
      <sha1>5znkw5o6nh9m5wiahz8kmfy5276qgza</sha1>
    </revision>
  </page>
  <page>
    <title>Infrastructure Past, Present, and Future/Loudoun County Data Centers</title>
    <ns>0</ns>
    <id>485862</id>
    <revision>
      <id>4676558</id>
      <parentid>4676354</parentid>
      <timestamp>2026-10-17T16:21:08Z</timestamp>
      <contributor>
        <username>~2026-55676-72</username>
        <id>3628625</id>
      </contributor>
      <comment>added table</comment>
      <origin>4676558</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="9809" sha1="lbu4aliclu37x9eoeqi29766rv8hz9m" xml:space="preserve">== Introduction ==
Loudoun County Data Virginia is home to over 200 Data centers, the most of any locality in the United States. Data centers began being built in the region in 1993 with the MAE-East internet hub in Vienna. &lt;ref&gt;{{Cite web |last=Konheim |first=Orrin |title=Tyson’s Corner at the Epicenter of the Internet |url=http://vivatysons.com/blog/2019/02/15/tysons-corner-at-the-epicenter-of-the-internet/ |access-date=2026-09-25 |language=en}}&lt;/ref&gt;However in 1995 the location moved to Ashburn to better allow for scaling as demand increased. Today, Ashburn is home to 133 Data Centers alone, earning it and Loudoun County the nickname &quot;Data Center Alley.&quot;&lt;ref&gt;{{Cite web |title=Data Center Alley: How Ashburn became a data center hub of the world {{!}} Digital Realty |url=https://www.www.digitalrealty.com/resources/blog/northern-virginia-ashburn-data-centers?t=1792158935657?latest |access-date=2026-09-25 |website=www.www.digitalrealty.com |language=en}}&lt;/ref&gt;

Loudoun County has the highest median household income in the United States of $181,765 in 2024.&lt;ref&gt;{{Cite web |title=U.S. Census Bureau QuickFacts: Loudoun County, Virginia |url=https://www.census.gov/quickfacts/loudouncountyvirginia |access-date=2026-10-15 |website=www.census.gov |language=en}}&lt;/ref&gt;

== History ==
MAE East, standing for Metropolitan Area Ethernet, was the first internet exchange point (IXP) not run by the government. In 1992, the first 4 points were set up in Washington, D.C. and then spread to Vienna, Reston, and then Ashburn. MAE East was created by UUNET and Metropolitan Fiber Systems. This early internet infrastructure made Northern Virginia, specifically Loudoun County, very appealing for further infrastructure development. 

In the 90s, two of the largest and first internet service providers set their headquarters in Ashburn, Virginia, located within Loudoun County. America Online (AOL) in 1996 and UUNet in 1998. Context in America at the time is important to understanding how Loudoun has become the data center hub it is today. In the 90s, America was going through a technological revolution with the era of the World Wide Web (WWW), which was released to the public in 1993. By 1995, there were about 10,000 web servers online, allowing the public across America to easily use the internet. During this large growth of the internet industry, these two major companies chose to put their headquarters in Ashburn, Virginia. This was not a coincidence, but rather a very deliberate and motivated growth strategy.  Loudoun County, and subsequently Ashburn, has an advantageous location near Washington, D.C., Dulles International Airport, and the IXP in Vienna. The area also had a large number of qualified workers to help build infrastructure exponentially. 

The early infrastructure built up in the 1990s made it easier and more enticing for other internet companies to set up in the area. In the 2000s, AOL and UUnet were well established; Ashburn and other companies were starting to gravitate to Loudoun County. These companies started bringing more internet infrastructure into Loudoun County. The county has zoning laws that classify and categorize districts and land use for types of buildings/ infrastructure. At the time, there was no classification for data centers, but the Zoning administrator chose to allow them anywhere that office buildings were allowed. The county had a “by-right” building rule that permitted building without any further approval as long as zoning allowed for it. This led to data centers being built in office parks and near homes as part of “mixed-use” communities. 

In 2008, the housing market crashed around the United States. This largely affected Loudoun County, as the county’s revenue came primarily from residential taxes. Loudoun County needed to diversify the tax base to make up for the loss of the primary source of revenue. With internet companies interested in locating in Loudoun County and land available, government officials saw an economic opportunity to increase commercial tax revenue. The next year, 2007, Loudoun County began expanding data center construction. 2007 to 2016, the county had the largest data center growth in the country. This large boom in infrastructure in Loudoun County caused many of the internet service providers to switch from MAE East IXP to Equinix Ashburn. In 2009, MAE East, one of the major draws for data centers in Loudoun County, officially shut down.

{{maplink|frame=yes|type=shape|id=Q495310|text=[[Loudoun County]]}}

== Timeline ==


== Recent developments ==
In 2024 the County Board of Supervisors launched the Data Center Standards &amp; Locations project to address resident's concerns regarding data centers.  The plan consists of two phases.&lt;ref&gt;{{Cite web |title=Data Center Standards &amp; Locations {{!}} Loudoun County, VA - Official Website |url=https://www.loudoun.gov/DataCenterStandards |access-date=2026-10-15 |website=www.loudoun.gov}}&lt;/ref&gt;

==== Phase 1 - Approved March 18, 2025 ====
This phase focused on proposed map and text amendments to the Loudoun County 2019 Comprehensive Plan. Redesignating Data Centers in industrial zones as conditional or Special Exception (SPEX), ending the By-Right construction that had existed since 2000.&lt;ref&gt;{{Cite web |date=2026-07-02 |title=Data Centers in Loudoun: A Primer - The Piedmont Environmental Council |url=https://www.pecva.org/region/loudoun/data-centers-in-loudoun-a-primer/ |access-date=2026-10-15 |language=en-US}}&lt;/ref&gt; Special Exceptions require both a public hearing and a board vote to be permitted, unlike by-right construction.

==== Phase 2 - Currently Ongoing ====
This phase is focused on creating new use-specific zoning standards for data centers and utility substations that serve them. This would create new requirements for future data centers to be approved.

=== Criticisms of the Data Center Standards &amp; Locations Project ===
As a part of Phase 1 of the plan the Board of Supervisors also passed a grandfathering resolution that allows any Data centers that were previously approved by Feb. 12, 2025 to continue under the previous rules. This allowed 15 data center projects to continue without meeting the SPEX requirements.&lt;ref&gt;{{Cite news |last=Flack |first=Eric |date=11:19 PM EDT October 6, 2026 |title=Loudoun supervisors don't rollback data center grandfathering law, shelve $200,000 audit of grandfathered projects |work=Wusa9 |url=https://www.wusa9.com/article/news/community/data-centers/data-center-rollback-grandfathering-laws-loudoun-county/65-136555f2-d85b-498b-a53a-c7d0582e82e5 |access-date=3:43 PM EDT October 10, 2026}}&lt;/ref&gt; Additionally the Board shelved an audit of these 15 projects, which was a compromise instead of ending them and forcing them to begin again under the new rules. 

== Fiscal Reality of Data Centers ==
Loudoun County's largest revenue source is property taxes. As the value of property increases the county has consistently lowered the real property tax rate. The increase in property value is in part driven by the data center construction.

Additionally, data centers and related companies make up all 10 of the top 10 tax payers in Loudoun.&lt;ref&gt;{{Cite web |title=Popular Annual Financial Report |url=https://prcsinfo.loudoun.gov/view/952649939/6/?sharedOn= |access-date=2026-10-15 |website=prcsinfo.loudoun.gov}}&lt;/ref&gt;

== Lessons Learned ==
The Loudoun County data center situation offers a lot of lessons learned that could prevent future mistakes between infrastructure growth and policy. The first takeaway comes from before the boom in data centers. Loudoun County suffered greatly from the 2008 recession, causing house values to plummet. A significant portion of the county's tax revenue came from residential housing. The county lost a large portion of its funding, leaving a desperate need to find a new source of revenue. This led to the decision to allow so many data centers into the county. This provides a valuable lesson for the future about diversifying the county’s tax revenue sources. Relying on one source can easily lead to disaster when that source falls through. This lesson may not have been learned fully, as the county now largely relies on tax revenue from these data centers, which is a very unstable and unreliable industry. The top 10 tax sources were all data centers.
{| class=&quot;wikitable&quot;
|+TOP 10 TAXPAYERS
!Rank
!Business Name
!Assessed Value
!% of Taxable Assessed Value
|-
|1
|Digital Loudoun 3 LLC
|$2.76 Billion
|1.61%
|-
|2
|NTT Global Data Centers, VA LLC
|$2.63 Billion
|1.53%
|-
|3
|Amazon Data Services Inc
|$2.31 Billion
|1.35%
|-
|4
|Digital Loudoun Pkwy Ctr North LLC
|$1.47 Billion
|0.85%
|-
|5
|Equinix LLC
|$1.42 Billion
|0.83%
|-
|6
|Microsoft Corp
|$1.35 Billion
|0.79%
|-
|7
|Aligned Energy Data Centers, IAD Propco LLC
|$1.26 Billion
|0.73%
|-
|8
|Kaveh Ventures LLC.
|$991.31 Million
|0.58%
|-
|9
|C1 Northern Virginia Sterling V LLC
|$966.5 Million
|0.56%
|-
|10
|Compass Datacenters IAD LLC
|$951.4 Million
|0.55%
|}
Data centers in Loudoun County were constructed rapidly and expanded exponentially due to the county’s unprepared zoning ordinances. Data centers were put under the category of business centers in the early years because there was no category for them. This allowed data centers all over the county with little restriction. Finally, in 2025, the county changed the zoning ordinances so data centers were no longer “By-right” and were limited to zoned areas. Policy is an important part of shaping our society, and it needs to be able to evolve and change to keep up with new infrastructure. When policy moves and changes slowly, it fails to adapt to what society needs. This is an important lesson that seems to have been learned; however, only time will tell. {{BookCat}}</text>
      <sha1>lbu4aliclu37x9eoeqi29766rv8hz9m</sha1>
    </revision>
  </page>
  <page>
    <title>About Monsters And Angels/Questions And Answers</title>
    <ns>0</ns>
    <id>486351</id>
    <revision>
      <id>4676541</id>
      <parentid>4676246</parentid>
      <timestamp>2026-10-17T15:09:52Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <origin>4676541</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3072" sha1="l4ag0qb6htt0vh1fn5lvzkiu36ik3jw" xml:space="preserve">== Questions and Answers ==
'''Q: Where did the word &quot;monster&quot; come from?''' &lt;br&gt;
&lt;br&gt;
A: Monster derives from the Latin ''monstrum''. Monstrum is derived from the verb ''moneo'', which means &quot;to remind, warn, instruct, or foretell.&quot; [2] &lt;br&gt;
The early, 14th century meaning of the word &quot;monster&quot; originally referred to a malformed human, animal, or to a birth defect that was interpreted as a supernatural sign, or as a warning from the divine. [3] &lt;br&gt;
Towards the end of the 14th century, the word expanded to include mythical beasts. In the 1520s, the word began to describe massive animals. Around the 1550s, the word started to describe evil people, characterized by their inhuman cruelty or wickedness. By the 19th century, the word &quot;monster&quot; was used as an adjective to describe things of gigantic size. [2]

'''Q: What are cryptids?'''&lt;br&gt;
&lt;br&gt;
A: A '''cryptid''' is an animal or creature whose existence is claimed through folklore, legends, or eyewitness accounts, but which has never been scientifically proven or verified by mainstream zoology. [1]
&lt;br&gt;
&lt;br&gt;
'''Q: What is the oldest mythical creature?''' &lt;br&gt;
&lt;br&gt;
A: There is no single oldest mythical creature. Prehistoric Art depicted hybrid beings long before written records existed. Luckily, Archaeology and ancient literature points to a few of the oldest recorded monsters. &lt;br&gt;
&lt;br&gt;
'''Earliest Prehistoric Art:''' 
&lt;br&gt;
The Lion-Man [Hohlenstein-Stadel]: This 40,000 - to - 44,000-year-old ivory carving was discovered in Germany. It is a carving of a human body with a lion's head. [4] &lt;br&gt;
&lt;br&gt;
Indonesian Cave Art: A 44,000-year-old rock Art painting in Sulawesi, Indonesia, depicts part-human, part-animal figures. These therianthropes are shown hunting. This proves that humans imagined hybrid creatures deep in the Stone Age. [5] 
&lt;br&gt;
&lt;br&gt;
'''Early Literature:''' &lt;br&gt;
Some of the oldest written monsters in human literature can be found in the ancient Mesopotamian ''Epic of Gilgamesh'', a piece of literature dating around 2000 BCE. Humbaba and the Scorpion-men may be some of the oldest monsters in history. [6]
&lt;br&gt;
&lt;br&gt;
&lt;br&gt;

==== References: ==== 
1. &quot;List of Cryptids.&quot; October 13, 2026. In Wikipedia, https://en.wikipedia.org/wiki/List_of_cryptids &lt;br&gt;
&lt;br&gt;
2. &quot;Monster.&quot; October 12, 2026. In Wikipedia, https://en.wikipedia.org/wiki/Monster &lt;br&gt;
&lt;br&gt;
3. &quot;What is a monster?&quot; September 7, 2015. University of Cambridge. https://www.cam.ac.uk/research/discussion/what-is-a-monster &lt;br&gt;
&lt;br&gt;
4. &quot;Lion-man of Hohlenstein-Stadel.&quot; September 14, 2026. In Wikipedia, https://en.wikipedia.org/wiki/Lion-man_of_Hohlenstein-Stadel
&lt;br&gt;
&lt;br&gt;
5. Rigby, Sara. &quot;44,000-year-old Cave Art Depicts Earliest-Known Mythical Beasts&quot; December 12, 2019. BBC Science Focus Magazine https://www.sciencefocus.com/news/440000-year-old-cave-art-depicts-earliest-known-mythical-beasts &lt;br&gt;
&lt;br&gt;
6. &quot;Epic of Gilgamesh.&quot; September 28, 2026. In Wikipedia, https://en.wikipedia.org/wiki/Epic_of_Gilgamesh &lt;br&gt;
&lt;br&gt;
&lt;br&gt;&lt;noinclude&gt;{{Chapter navigation with TOC||Introduction|TOC mini}}&lt;/noinclude&gt;
&lt;br&gt;

{{BookCat}}</text>
      <sha1>l4ag0qb6htt0vh1fn5lvzkiu36ik3jw</sha1>
    </revision>
  </page>
  <page>
    <title>Wikibooks:Patrollers</title>
    <ns>4</ns>
    <id>486364</id>
    <revision>
      <id>4676560</id>
      <parentid>4676443</parentid>
      <timestamp>2026-10-17T17:03:38Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>Expanding. ([[:m:User:Max/MaxEdit.js|MaxEdit]])</comment>
      <origin>4676560</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="816" sha1="rkcey7x1jpfi9llhtgnmyrnjf9dmlrj" xml:space="preserve">[[File:Wikibooks Patroller Icon.svg|right|150px]]
'''Patrollers''' are a group of users with the technical ability to patrol new pages, not create redirects when moving pages, and quickly revert malicious edits using the [[WB:ROLLBACK|rollback feature]], among other things. In addition, their edits are automatically marked as patrolled by the MediaWiki software. These user rights are automatically granted to [[Wikibooks:Administrators|administrators]].

The group was created in October 2026 following [[Wikibooks:Reading room/Proposals#FlaggedRevs again|consensus to discontinue the Flagged Revisions extension]].

== Requesting the patroller user group ==
Any trustworthy user can request patroller status by filing a request at [[Wikibooks:Requests for permissions]].

{{User groups}}
[[Category:User groups]]</text>
      <sha1>rkcey7x1jpfi9llhtgnmyrnjf9dmlrj</sha1>
    </revision>
    <revision>
      <id>4676561</id>
      <parentid>4676560</parentid>
      <timestamp>2026-10-17T17:05:12Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>Rewriting the word. ([[:m:User:Max/MaxEdit.js|MaxEdit]])</comment>
      <origin>4676561</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="816" sha1="bk873hxwsyhym6e0yy39qrji63fggnt" xml:space="preserve">[[File:Wikibooks Patroller Icon.svg|right|150px]]
'''Patrollers''' are a group of users with the technical ability to patrol new pages, not create redirects when moving pages, and quickly revert malicious edits using the [[WB:ROLLBACK|rollback feature]], among other things. In addition, their edits are automatically marked as patrolled by the MediaWiki software. These permissions are automatically granted to [[Wikibooks:Administrators|administrators]].

The group was created in October 2026 following [[Wikibooks:Reading room/Proposals#FlaggedRevs again|consensus to discontinue the Flagged Revisions extension]].

== Requesting the patroller user group ==
Any trustworthy user can request patroller status by filing a request at [[Wikibooks:Requests for permissions]].

{{User groups}}
[[Category:User groups]]</text>
      <sha1>bk873hxwsyhym6e0yy39qrji63fggnt</sha1>
    </revision>
    <revision>
      <id>4676562</id>
      <parentid>4676561</parentid>
      <timestamp>2026-10-17T17:10:24Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>+</comment>
      <origin>4676562</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="937" sha1="qdyu4r5fwu1fbwwdfcq15ww8y2gzzig" xml:space="preserve">[[File:Wikibooks Patroller Icon.svg|right|150px]]
'''Patrollers''' are a group of users with the technical ability to patrol new pages, not create redirects when moving pages, and quickly revert malicious edits using the [[WB:ROLLBACK|rollback feature]], among other things. In addition, their edits are automatically marked as patrolled by the MediaWiki software. These permissions are automatically granted to [[Wikibooks:Administrators|administrators]].

The group was created in October 2026 following [[Wikibooks:Reading room/Proposals#FlaggedRevs again|consensus to discontinue the Flagged Revisions extension]].

There are currently [[Special:ListUsers/patroller|'''{{NUMINGROUP:patroller}}''' patrollers]] on the English Wikibooks.

== Requesting the patroller user group ==
Any trustworthy user can request patroller status by filing a request at [[Wikibooks:Requests for permissions]].

{{User groups}}
[[Category:User groups]]</text>
      <sha1>qdyu4r5fwu1fbwwdfcq15ww8y2gzzig</sha1>
    </revision>
  </page>
  <page>
    <title>Koine Greek/Infinitives</title>
    <ns>0</ns>
    <id>486376</id>
    <revision>
      <id>4676577</id>
      <parentid>4676441</parentid>
      <timestamp>2026-10-17T20:28:27Z</timestamp>
      <contributor>
        <username>It-is-Truly-Meet</username>
        <id>3624460</id>
      </contributor>
      <minor />
      <origin>4676577</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2241" sha1="gbtou0r1pplr4zjelqsznq96471i0r6" xml:space="preserve">This page is intended to give an introduction to infinitives in Koine Greek.

==Present Infinitive==

==Future Infinitive==

==Aorist Infinitive==

===Aorist Active Infinitive===
The aorist, like the present and future tenses, occurs in the infinitive mood. The augment to secondary tenses indicates '''actual historical action'''; thus only the '''indicative''' mood uses it. The aorist infinitive, a verbal noun, '''never''' has the augment.

====First Aorist Active Infinitive====
'''Formation''': verb stem + σαι.
The persistent '''accent''' falls on the '''penult''', the second-to-last syllable.
* δεῖ.ξαι
* πισ.τεῦ.σαι
* γε.νη.θῆ.ναι

====Second Aorist Active Infinitive====

=====Thematic Formation=====
'''Thematic formation''': verb stem + ειν. The '''present''' indicative active infinitive accents on the '''penult''' (e.g., λαμβάνειν); the 2nd aorist active indicative infinitive has a '''circumflex''' on the '''ultima''' (e.g., λαβεῖν).

=====Athematic Formation=====
'''Αthematic formation''': verb stem + ναι. The athematic 2nd aorist uses the same infinitive ending as the athematic present tense. Like the present tense, the accent falls on the '''penult'''.
* γνῶ.ναι
* βῆ.ναι

===Aorist Middle Infinitive===
====First Aorist Middle Infinitive====
====Second Aorist Middle Infinitive====
=====Thematic Formation=====
=====Athematic Formation=====

===Aorist Passive Infinitive===
====First Aorist Passive Infinitive====
====Second Aorist Passive Infinitive====

===Infinitive and Aspect===
If an infinitive is used as an '''articular''' or a '''complementary infinitive''', the present and aorist tenses of the infinitive are used to express '''aspect''', not time. In other words, the present infinitive expresses ongoing activity, while the aorist infinitive expresses a simple momentary action. This distinction is often unexpressed in English.

* '''Present infinitive''': παίζειν βούλομαι. — I want to be playing.
* '''Aorist infinitive''': παῖσαι βούλομαι. — I want to play.

==Perfect Infinitive==

==Syntax and Use==
===Complementary Infinitives===
===Articular Infinitives===
===Infinitive Aspect===

{{BookCat}}</text>
      <sha1>gbtou0r1pplr4zjelqsznq96471i0r6</sha1>
    </revision>
  </page>
  <page>
    <title>Koine Greek/Overview of Conjunctions</title>
    <ns>0</ns>
    <id>486382</id>
    <revision>
      <id>4676567</id>
      <parentid>4676411</parentid>
      <timestamp>2026-10-17T18:21:37Z</timestamp>
      <contributor>
        <username>It-is-Truly-Meet</username>
        <id>3624460</id>
      </contributor>
      <origin>4676567</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="9130" sha1="sr9obv55qiv42d1ile3iph5s7nyos3h" xml:space="preserve">A '''conjunction''' is an uninflected linguistic form that joins sentences, clauses, phrases, or words.

Greek conjunctions work like those in English, but they are often used more frequently and subtly. Greek often connects sentences and clauses with conjunctions such as &quot;and,&quot; &quot;but,&quot; and &quot;therefore&quot; to link ideas.

==Coordinating (Paratactic) Conjunctions==

===AND===

* '''καί''': Connects words, clauses, and sentences. As an adverb, it means &quot;even&quot; or &quot;also.&quot;
* '''τε''' (enclitic): Like καί, it links clauses and sentences, but rarely connects individual words in Greek prose. τε...καί is a slightly weaker version of καί...καί, meaning &quot;both...and.&quot; As a monosyllabic enclitic, τε rarely has an accent.
* '''δέ''': Often marks a clause or sentence as distinct from the preceding one, sometimes with a slight contrast. Depending on context, it can mean &quot;and&quot; or &quot;but,&quot; or remain untranslated.
* '''μέν...δέ''': Marks a contrast between two words, clauses, or ideas. It can be translated &quot;on the one hand...on the other hand,&quot; but μέν is often left untranslated, and δέ may mean &quot;and&quot; or &quot;but.&quot; Sometimes neither is translated.

In Koine Greek, several common conjunctions and connective particles are '''postpositive''': they normally occur after the first word of a clause rather than at its beginning. These include τε, δέ, μέν, γάρ, and οὖν. Unlike these words, καί can begin a clause.

Consider the following examples:

* χρήματα καὶ ὑπάρχοντα δίδομεν. — We give money and property.
* δίδομεν τὰ σπέρματα καὶ δίδοτε τὸ ὕδωρ. — We give the seeds and you give the water.
* τὰ σπέρματα δίδομεν, ὑπάρχοντα δὲ δίδοτε. — We give the seeds and you give property.
* τὰ σπέρματα μὲν δίδομεν, ὕδωρ δὲ δίδοτε. — We give the seeds and you give water.

===AND...NOT===

* '''οὔτε''': &quot;and not,&quot; or as part of οὔτε...οὔτε, &quot;neither...nor.&quot;
* '''μήτε''': &quot;and not,&quot; or as part of μήτε...μήτε, &quot;neither...nor.&quot;

These forms combine οὐ or μή with τε. Their choice depends on the construction and the type of negation required; οὔτε commonly occurs with indicative clauses, while μήτε also occurs in constructions involving infinitives. This is a tendency, not an absolute rule.

===BUT===

* '''ἀλλά''': &quot;but,&quot; &quot;yet.&quot; It expresses a stronger opposition to a preceding clause or statement than δέ.
* '''δέ''': Depending on context, it can express a weaker contrast and be translated &quot;but.&quot;
* '''μέν...δέ''': Often marks a contrast in which μέν is left untranslated and δέ is translated &quot;but&quot; or &quot;and.&quot;

===OR===

* '''ἤ''': &quot;or.&quot; Its breathing mark and accent distinguish it from ἡ, the feminine definite article.
* '''εἴτε...εἴτε''': &quot;either...or&quot; or &quot;whether...or.&quot;
* '''μήτε...μήτε''': &quot;neither...nor,&quot; with μή-type negation.
* '''οὔτε...οὔτε''': &quot;neither...nor,&quot; with οὐ-type negation.

===BECAUSE===

* '''γάρ''' (postpositive): &quot;for,&quot; &quot;because.&quot;
* '''ὅτι''': &quot;because&quot; when it introduces a causal clause. It can also mean &quot;that&quot; in other constructions.

===THEREFORE===

* '''ἄρα''': &quot;therefore,&quot; &quot;so.&quot;
* '''διό''': &quot;therefore,&quot; &quot;for this reason.&quot;
* '''οὖν''' (postpositive): &quot;therefore,&quot; &quot;then.&quot;
* '''τοίνυν''' (postpositive): &quot;therefore,&quot; &quot;accordingly.&quot;

==Subordinating (Hypotactic) Conjunctions==

===Cause and Explanation===

* '''ὅτι''': &quot;because,&quot; introducing a causal clause.
* '''ἐπεί''': &quot;since,&quot; &quot;because&quot;; it can also have temporal meanings such as &quot;after&quot; or &quot;when.&quot;

===Condition===

* '''εἰ''' ('''εἴπερ'''): &quot;if.&quot;
* '''ἐάν''': &quot;if,&quot; commonly used with the subjunctive.

For a fuller explanation of conditional constructions, see [[Koine Greek/Conditional Clauses]].

===Time===

* '''ἐπεί''': &quot;after,&quot; &quot;when,&quot; or &quot;since,&quot; depending on context.
* '''ἕως''': &quot;until,&quot; &quot;while.&quot;
* '''μέχρι''': &quot;until.&quot;
* '''ὅτε''': &quot;when.&quot;
* '''πρίν''': &quot;before&quot; or &quot;until,&quot; depending on the construction. It commonly occurs with an infinitive in constructions meaning &quot;before.&quot;

===Purpose and Result===

* '''ἵνα''': &quot;so that,&quot; commonly used with the subjunctive to express purpose or intended result.

===Other Relations===

* '''ὅθεν''': &quot;from where,&quot; &quot;whence.&quot;
* '''ὡς''': &quot;as,&quot; &quot;like,&quot; &quot;because,&quot; &quot;while,&quot; or other meanings depending on context.

==Elision==

The final vowel of a conjunction is sometimes elided before a word beginning with a vowel. This process is called '''elision'''.

Compare the following examples:

* εἴτε τὰ χρήματα οὐ δίδομεν, εἴτε τὰ ὑπάρχοντα οὐ δίδοτε.
* εἴτ’ οὐ δίδομεν τὰ χρήματα, εἴτ’ οὐ δίδοτε τὰ ὑπάρχοντα.

&quot;Either we do not give the money, or you do not give the property.&quot;

* οὐκ ἀποδίδοτε, ἄρα χρήματα οὐ δίδομεν.
* οὐκ ἀποδίδοτε, ἄρ’ οὐ δίδομεν χρήματα.

&quot;You do not give it back; therefore, we do not give money.&quot;

* ὅτε χρήματα ἀποδίδοτε, ὑπάρχοντα δίδομεν.
* ὅτ’ ἀποδίδοτε χρήματα, ὑπάρχοντα δίδομεν.

&quot;When you give money back, we give property.&quot;

Note that '''ὅτι''' does not elide. Therefore, '''ὅτ’''' in the final example is an elided form of '''ὅτε''' (&quot;when&quot;), not ὅτι (&quot;because&quot; or &quot;that&quot;).

==Subordinate Clauses==
We have discussed the uses of the subjunctive and optative in '''main clauses''', where they often express independent wishes or intents, for example:
*ὁ δὲ θεὸς τῆς ἐλπίδος πληρώσαι ὑμᾶς πάσης χαρᾶς... — Now may the God of hope fill you with all joy... ([[s:el:Προς Ρωμαίους#15:13|Romans 15:13]])
*μηκέτι εἰς τὸν αἰῶνα ἐκ σοῦ μηδεῖς καρπὸν φάγοι. — May no one ever eat fruit from you again to eternity! ([[s:el:Κατά Μάρκον#11:14|Mark 11:14]])

Now let’s consider how these moods are used in '''subordinate''' clauses. In purpose and fear clauses, the tense of the main verb determines the mood—subjunctive or optative—of the subordinate verb. This pattern is called the '''sequence of moods''':
# '''Primary Sequence''': If the main verb is a primary tense (present, future, perfect) or refers to a future action (imperative, subjunctive, optative), the subordinate verb is '''subjunctive'''.
# '''Secondary Sequence''': If the main verb is a secondary tense (imperfect, aorist, pluperfect), the subordinate verb is '''optative''' (or subjunctive to express vividness).
#*ἐπηρώτων δὲ αὐτὸν οἱ μαθηταὶ αὐτοῦ τίς αὕτη εἴη ἡ παραβολή. — And his disciples were asking him what this parable might be. [Secondary sequence optative in an oblique indirect question] ([[s:el:Κατά Λουκάν#8:9|Luke 8:9]])

===Purpose Clause===
A purpose clause indicates the goal of the main action. It is introduced by:
* ἵνα, ὡς, ὅπως: so that, in order that
* ἵνα μή, ὡς μή, ὅπως μή, or μή (alone): so that…not, in order that…not, lest

The choice of mood follows the sequence of moods. Tenses denote aspect, not time.

*ταῦτα δὲ λέγω ἵνα ὑμεῖς σωθῆτε. — But I say these things so that you may be saved. [Primary sequence] ([[s:el:Κατά Ιωάννην#5:34|John 5:34]])
*ἦλθεν εἰς μαρτυρίαν, ἵνα μαρτυρήσῃ περὶ τοῦ φωτός... — He came for a witness, in order that he might testify concerning the light... [Secondary sequence using subjunctive for vividness] ([[s:el:Κατά Ιωάννην#1:7|John 1:7]])
*...καὶ μὴ εἰσενέγκῃς ἡμᾶς εἰς πειρασμόν... — ...and do not lead us into temptation, lest [you deliver us over to the evil one]. [Negative purpose with μή alone] ([[s:el:Κατά Ματθαίον#6:13|Matthew 6:13]])

===Fear Clause===
A fear clause acts as the object of a verb of fearing. It is introduced by:
* μή: that, lest (fear that something will happen)
* μὴ οὐ: that…not, lest…not (fear that something will not happen)

If the fear concerns a '''present''' or '''past''' reality, the subordinate verb is '''indicative''':
*φοβοῦμαι ὑμᾶς μή πως εἰκῇ κεκοπίακα εἰς ὑμᾶς. — I am afraid for you, lest somehow I have labored in vain for you. ([[s:el:Προς Γαλάτας#4:11|Galatians 4:11]])

If the fear concerns a '''future''' outcome, the clause follows the '''sequence of moods''':
*...φοβηθεὶς δὲ ὁ χιλίαρχος μὴ διασπασθῇ ὁ Παῦλος ὑπ’ αὐτῶν... — ...and the commander, fearing lest Paul would be torn to pieces by them... [Secondary sequence using subjunctive for vividness] ([[s:el:Πράξεις των Αποστόλων#23:10|Acts 23:10]])</text>
      <sha1>sr9obv55qiv42d1ile3iph5s7nyos3h</sha1>
    </revision>
  </page>
  <page>
    <title>Koine Greek/Conditional Clauses</title>
    <ns>0</ns>
    <id>486384</id>
    <revision>
      <id>4676574</id>
      <parentid>4676432</parentid>
      <timestamp>2026-10-17T19:43:23Z</timestamp>
      <contributor>
        <username>It-is-Truly-Meet</username>
        <id>3624460</id>
      </contributor>
      <origin>4676574</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="28907" sha1="njaw8pihrywqdx1vxbdj40j71jfhqil" xml:space="preserve">The negative particle in a conditional clause is usually μή, making the conjunctions εἰ μή or ἐὰν μή &quot;unless&quot;, &quot;if not&quot;. However, some conditions have οὐ. The apodosis usually has οὐ.

A conditional clause preceded by εἴθε or εἰ γάρ &quot;if only&quot; is also occasionally used in Greek for making a wish. The conjunction εἰ also frequently introduces an indirect question.

==Classification of conditional clauses==
Conditional clauses fall into several types, summarized below.

A present general condition and a vivid future condition both use ἐάν with the subjunctive; a past general condition and a less vivid future condition both use εἰ with the optative. In each pair, the apodosis distinguishes the meaning.

Hypothetical conditions (&quot;if I were to die&quot;, &quot;if I was dead&quot;, &quot;if I had died&quot;) usually have ἄν in the apodosis. It may be omitted with an imperfect expressing necessity or possibility, such as ἔδει (&quot;it was necessary&quot;) or ἐξῆν (&quot;it was possible&quot;).

{| class=&quot;wikitable&quot;
! Type
! Example
! Protasis
! Apodosis
|-
| colspan=&quot;4&quot;|'''Primary tenses'''
|-
| Simple (open)
| ''If it is true''
| εἰ + present or perfect indicative
| indicative or imperative
|-
| Emotional future
| ''If it happens (in future)''
| εἰ + future indicative
| future indicative
|-
| Vivid future
| ''If it happens (in future)''
| ἐάν + subjunctive
| future indicative
|-
| General present
| ''If ever it happens''
| ἐάν + subjunctive
| present indicative
|-
| colspan=&quot;4&quot;|'''Historic tenses'''
|-
| Simple (open)
| ''If it was true''
| εἰ + imperfect or aorist indicative
| indicative
|-
| General past
| ''If ever it used to happen''
| εἰ + optative
| imperfect indicative
|-
| Less vivid future
| ''If it were to happen''
| εἰ + optative
| optative + ἄν
|-
| Unreal present
| ''If it were true''
| εἰ + imperfect indicative
| imperfect indicative + ἄν
|-
| Unreal past
| ''If it had happened''
| εἰ + aorist indicative
| aorist indicative + ἄν
|}

==Simple (open) conditions==
A simple condition uses the indicative in the protasis. The apodosis can have an imperative:
:εἴ τις '''ἔρχεται''' πρὸς ὑμᾶς καὶ ταύτην τὴν διδαχὴν '''οὐ φέρει''', '''μὴ λαμβάνετε''' αὐτὸν εἰς οἰκίαν καὶ χαίρειν αὐτῷ '''μὴ λέγετε'''. (2 John 1:10)
:&quot;if anyone '''comes''' to you and '''does not bring''' this teaching, '''do not receive''' him into your house, and '''do not greet''' him.&quot;

:Εἰ οὖν '''συνηγέρθητε''' τῷ Χριστῷ, τὰ ἄνω '''ζητεῖτε'''. (Colossians 3:1)
:&quot;if you '''have been raised''' with Christ, '''seek''' the things above.&quot;

:εἰ δὲ πνεύματι '''ἄγεσθε''', '''οὐκ ἐστὲ''' ὑπὸ νόμον. (Galatians 5:18)
:&quot;if you '''are led''' by the Spirit, you '''are not''' under the law.&quot;

A simple conditional may use any tense of the indicative. The following has the perfect indicative:
:εἰ δὲ Χριστὸς οὐκ '''ἐγήγερται''', κενὸν ἄρα τὸ κήρυγμα ἡμῶν, κενὴ καὶ ἡ πίστις ὑμῶν. (1 Corinthians 15:14)
:&quot;if Christ '''has not been raised''', then our preaching is in vain, and your faith is in vain.&quot;

The following uses the imperfect indicative in both clauses:
:εἰ ἐν ἐκείνῃ τῇ νυκτὶ ἐγὼ '''ἐπεβούλευον''' Ἐρατοσθένει, πότερον '''ἦν''' μοι κρεῖττον αὐτῷ ἑτέρωθι δειπνεῖν ἢ τὸν συνδειπνήσοντά μοι εἰσαγαγεῖν; (Lysias 1:40)
:&quot;if on that night '''I was plotting''' against Eratosthenes, '''was it''' better for me to dine elsewhere or to bring that guest to my house?&quot;

The following uses the aorist indicative followed by an aorist imperative:
:{{lang|grc|εἰ '''ἤκουσάς''' τι τούτου τοῦ πράγματος τοῦ γενομένου, '''εἰπέ'''.}} (Andocides 1:50)
:&quot;if '''you heard''' anything about this matter which has happened, '''tell''' us.&quot;

The following, from Euripides' play ''Electra'', has two aorist indicative tenses:
:εἰ δʼ, ὡς λέγεις, σὴν θυγατέρʼ '''ἔκτεινεν''' πατήρ,&lt;br /&gt;ἐγὼ τί σʼ '''ἠδίκησʼ''' ἐμός τε σύγγονος; (Euripides, Electra 1086–1087)
:&quot;even if, as you say, our father '''killed''' your daughter,&lt;br /&gt;how '''did I''' or my brother '''wrong''' you?&quot;

==Future conditions==
===&quot;Emotional&quot; future conditions===
An open conditional may use the future indicative in its protasis to express strong feeling. The apodosis often conveys a threat, warning, or earnest appeal; this is called the “emotional future” conditional.

In the following, a present tense apodosis is combined with a future protasis:
:οὐκ '''ἔστι''' παρελθεῖν, εἰ μὴ τούτους '''ἀποκόψομεν'''. (Xenophon, Anabasis 3.4.39)
:&quot;'''it's''' impossible to go past, unless '''we first cut down''' these men.&quot;

:τῇ γὰρ στρατιᾷ οὐκ '''ἔστι''' τὰ ἐπιτήδεια, εἰ μὴ '''ληψόμεθα''' τὸ χωρίον. (Xenophon, Anabasis 4.7.3)
:&quot;'''there is''' no food for the army, unless '''we capture''' the fort.&quot;

In the following poetic example, the protasis has a future indicative as before, but in the apodosis instead of a future, there is an aorist indicative:
:{{lang |grc|'''ἀπωλόμην''' ἄρ᾽, εἴ με δὴ '''λείψεις''', γύναι.}} (Euripides, Alcestis 386)
:&quot;'''I am undone''' if '''you leave''' me, wife!&quot;

===Vivid future conditions===
A future conditional usually uses ἐάν (also ἤν or ἄν) with the subjunctive. The α in ἐάν is long (LSJ, s.v. ἐάν; Smyth §34).

This common construction is called the vivid future conditional. The protasis has the present subjunctive and the apodosis the future indicative (Smyth §§2297, 2321–2322).

:Ἐὰν '''ἀγαπᾶτέ''' με, τὰς ἐντολὰς τὰς ἐμὰς '''τηρήσετε'''. (John 14:15)
: &quot;if you '''love''' me, you '''will keep''' my commandments.&quot;

:καὶ ἐὰν ἐκεῖ '''ᾖ''' υἱὸς εἰρήνης, '''ἐπαναπαήσεται''' ἐπʼ αὐτὸν ἡ εἰρήνη ὑμῶν. (Luke 10:6)
: &quot;and if a '''son of peace is''' there, your peace '''will rest''' upon him.&quot;

:ἐάν τις '''θέλῃ''' τὸ θέλημα αὐτοῦ ποιεῖν, '''γνώσεται''' περὶ τῆς διδαχῆς πότερον ἐκ τοῦ θεοῦ ἐστιν ἢ ἐγὼ ἀπʼ ἐμαυτοῦ λαλῶ. (John 7:17)
:&quot;if anyone '''wishes''' to do his will, he '''will know''' concerning the teaching whether it is from God or I speak from myself.&quot;

:ἐάν τις '''ἀγαπᾷ''' με, τὸν λόγον μου '''τηρήσει'''. (John 14:23)
:&quot;if anyone '''loves''' me, he '''will keep''' my word.

The apodosis can contain a present tense, if the verb is δεῖ &quot;it is necessary&quot;:
:τὸ γὰρ αὔτʼ, ἐὰν '''ἡττᾶσθε''', καὶ σφὼ '''δεῖ παθεῖν'''. (Aristophanes, Plut. 467)
:&quot;you two '''must suffer''' the same penalty too, if '''you are defeated'''&quot;

The negative used in a conditional clause is usually μή:
:ἐὰν δὲ '''μὴ ἀφῆτε''' τοῖς ἀνθρώποις, οὐδὲ ὁ πατὴρ ὑμῶν '''ἀφήσει''' τὰ παραπτώματα ὑμῶν. (Matthew 6:15)
: &quot;but if you '''do not forgive''' people, neither will your Father '''forgive''' your trespasses.&quot;

:ἐὰν γὰρ '''μὴ πιστεύσητε''' ὅτι ἐγώ εἰμι, '''ἀποθανεῖσθε''' ἐν ταῖς ἁμαρτίαις ὑμῶν. (John 8:24)
:&quot;for if you '''do not believe''' that I am he, you '''will die''' in your sins.&quot;

Sometimes οὐ is used instead of μή, as when οὔ φημι means “deny” (Smyth §§2696, 2698).

:ἐάντε σὺ καὶ Ἄνυτος '''οὐ φῆτε''' ἐάντε φῆτε (Plato, Apology 25b)
:&quot;whether you and Anytos '''deny it''' or agree with it&quot;

The following example uses the aorist subjunctive in the protasis:
:κἀγὼ ἐὰν '''ὑψωθῶ''' ἐκ τῆς γῆς, πάντας '''ἑλκύσω''' πρὸς ἐμαυτόν. (John 12:32)
:&quot;and I, if I am '''lifted up''' from the earth, '''will draw''' all people to myself.&quot;

===Less vivid future conditions===
The less vivid (or ideal) future conditional describes a hypothetical future, often one the speaker does not expect to happen. Both clauses use the optative; the apodosis has the [[Koine Greek/Overview of Particles|particle]] ἄν before or after the verb (Smyth §2329).

The tense of the verb can be aorist (if it is an event) or present (if it describes a situation). The following three examples use the aorist optative:

:καὶ ὁ Παρθένιος ἄβατος· ἐφʼ ὃν '''ἔλθοιτε ἄν''', εἰ τὸν Ἅλυν '''διαβαίητε'''. (Xenophon, Anabasis 5.6.10)
:&quot;the Parthenios river also cannot be crossed, to which '''you would come''' if '''you crossed''' the Halys.&quot;

:οὐδέν γε ἄτοπον εἰ '''ἀποθάνοιμι'''. (Plato, Gorgias 521d)
:&quot;there would be nothing strange about it if '''I were to die'''.&quot;

:εἰ δή τις με '''ἔροιτο''' ὑμῶν ... '''εἴποιμʼ ἄν''' ... (Aeschines, 1.80)
:&quot;if one of '''you were to ask''' me ... '''I would say''' ...&quot;

The following have present optative in the protasis, aorist optative in the apodosis:
:εἰ γὰρ '''εἰδείης''' ὅσον ἀργύριον εἴργασμαι ἐγώ, '''θαυμάσαις ἄν'''. (Plato, Hipp. Mai. 282d)
:&quot;if '''you knew''' how much money I have earned, '''you would be amazed'''.&quot;

:ἡδέως '''ἂν λάβοιμι''', εἰ '''διδοίη'''. (Xenophon, Cyropaedia 3.2.28)
:&quot;'''I would''' gladly '''accept''' it, if '''he were offering''' it.&quot;

The following uses the present optative in the apodosis:
:οὐκ '''ἂν θαυμάζοιμι'''. (Plato, Cratylus 428b)
:&quot;'''I would'''n't '''be surprised''' (if that were so).&quot;

In post-classical Greek, the optative mood gradually fell out of use. In the New Testament the potential optative with ἄν occurs, but rarely (e.g. ''Acts'' 8:31); εἰ with the optative also sometimes occurs (e.g. 2 Peter 3:14).

==General conditions==
===Present general conditions===
A present general condition uses the same grammatical construction (ἐάν with the subjunctive) as a vivid future condition, but is much less common. The present subjunctive is used when the actions of the two clauses are contemporaneous:
:ἐὰν '''ὁμολογῶμεν''' τὰς ἁμαρτίας ἡμῶν, '''πιστός ἐστιν''' καὶ δίκαιος ἵνα ἀφῇ ἡμῖν τὰς ἁμαρτίας καὶ καθαρίσῃ ἡμᾶς ἀπὸ πάσης ἀδικίας. (1 John 1:9)
:&quot;if we '''confess''' our sins, he '''is faithful''' and righteous to forgive us our sins and to cleanse us from all unrighteousness.&quot;

The aorist subjunctive indicates that this action precedes the main action (Smyth §2623, note 2).
:καὶ ἐὰν τις '''ἁμάρτῃ''', '''παράκλητον ἔχομεν''' πρὸς τὸν πατέρα, Ἰησοῦν Χριστὸν δίκαιον. (1 John 2:1)
:&quot;and if anyone '''sins''', we '''have an advocate''' with the Father, Jesus Christ the righteous.&quot;

The perfect subjunctive describes a present state resulting from an earlier action:
:ἐάν τε '''ἑαλωκὼς ᾖ''' ἐάν τε μή, δηλούτω. (Xenophon, Cynegeticus 6.18)
:&quot;whether (the hare) '''has been caught''' or not, (the huntsman) should make it clear (to his colleagues).&quot;

An aorist in the apodosis can sometimes express a general truth in the present; this is called a gnomic aorist (Smyth §§1931, 2338).
:ἢν δέ τις τούτων τι παραβαίνῃ, ζημίαν αὐτοῖς '''ἐπέθεσαν'''. (Xenophon, Cyr. 1.2.2)
:&quot;if a man transgress anyone one of these laws, '''they always impose''' a penalty on him.&quot;

===Past general conditions===
The optative after εἰ can express a past general condition (“if ever it used to happen”; Smyth §2340). In the following examples, the protasis has the present optative and the apodosis the imperfect indicative:
: εἴ πού τι '''ὁρῴη''' βρωτόν, '''διεδίδου'''. (Xenophon, Anabasis 4.5.8)
: &quot;If ever '''he saw''' something edible anywhere, '''he would pass''' it round.&quot;

:καὶ πάνυ ἄκρατος '''ἦν''', εἰ μή τις ὕδωρ '''ἐπιχέοι'''. (Xenophon, Anabasis 4.5.27)
:&quot;and (the barley-wine) '''was''' completely undiluted, unless someone '''added''' water.&quot;

In the following, however, the aorist optative is used in the protasis, to indicate that the action of sharing had to come before that of being allowed near the fire:
: οὐ '''προσίεσαν''' πρὸς τὸ πῦρ τοὺς ὀψίζοντας, εἰ μὴ '''μεταδοῖεν''' αὐτοῖς πῡρούς. (Xenophon, Anabasis 4.5.5)
: &quot;they '''wouldn't let''' the late-comers come near the fire, unless '''they first shared''' some wheat with them.&quot;

Here the protasis is shortened to εἰ δὲ μή (“otherwise”), meaning “but if they did not hold their weapons above the water” (cf. Smyth §2346).
:καὶ οὔτʼ ἐν τῷ ὕδατι τὰ ὅπλα ἦν ἔχειν· '''εἰ δὲ μή''', '''ἥρπαζεν''' ὁ ποταμός. (Xenophon, Anabasis 3.4.36)
:&quot;and it was not possible to hold their weapons in the water, '''otherwise''' the river '''kept snatching''' them away.&quot;

In a past general condition, ἄν may accompany an imperfect or aorist indicative to express repeated past action. This is called the iterative imperfect or aorist (Smyth §2341). The following example uses the imperfect indicative with ἄν:

:εἰ δέ τις αὐτῷ περί του '''ἀντιλέγοι''' ... ἐπὶ τὴν ὑπόθεσιν '''ἐπανῆγεν ἂν''' πάντα τὸν λόγον. (Xenophon, Memorabilia 4.6.13)
:&quot;if ever anyone '''opposed''' him on anything ... '''he would bring''' the whole subject '''back''' to the beginning&quot;

The following uses the aorist indicative with ἄν:
:καὶ εἴ τις αὐτῷ '''δοκοίη''' ... βλακεύειν, ἐκλεγόμενος τὸν ἐπιτήδειον '''ἔπαισεν ἄν'''. (Xenophon, Anabasis 2.3.11)
:'if ever anyone '''seemed''' to him to be lagging behind, he would pick out the culprit and '''would beat''' him.'

==Unreal conditions==
===Present unreal conditions===
A present unreal ([[#Unreal conditions|counterfactual]]) condition uses εἰ with the imperfect indicative in the protasis and the imperfect indicative plus ἄν in the apodosis (Smyth §2309).

:εἰ ἐκ τοῦ κόσμου '''ἦτε''', ὁ κόσμος ἂν τὸ ἴδιον '''ἐφίλει'''. (John 15:19)
:&quot;if you '''were''' of the world, the world '''would love''' its own.&quot;

:εἰ δὲ ἑαυτοὺς '''διεκρίνομεν''', οὐκ ἂν '''ἐκρινόμεθα'''. (1 Corinthians 11:31)
:&quot;but if we '''judged''' ourselves, we '''would not be judged'''.&quot;

===Past unreal conditions===
A past unreal condition uses the aorist indicative in both clauses, with ἄν in the apodosis to express “would” (Smyth §2309).
:εἰ μὴ κύριος σαβαὼθ '''ἐγκατέλιπεν''' ἡμῖν σπέρμα, ὡς Σόδομα ἂν '''ἐγενήθημεν'''. (Romans 9:29)
:&quot;if the Lord of Sabaoth had not '''left''' us offspring, we '''would have become''' like Sodom.&quot;

The following example has an apodosis only with no protasis. The tense is aorist indicative:
:τίς γὰρ '''ἂν ᾠήθη''' ταῦτα γενέσθαι; (Demosthenes 9.68)
:&quot;for who '''would have expected''' these things to happen?&quot;

In an unreal condition, an imperfect can refer to the past as well as the present. Here ἦς is imperfect indicative and ἀπέθανεν is aorist indicative (Smyth §§2309–2310):
:εἰ '''ἦς''' ὧδε, οὐκ ἂν '''ἀπέθανεν''' ὁ ἀδελφός μου. (John 11:21)
:&quot;Lord, if you '''had been''' here, my brother '''would not have died'''.&quot;

In the following, the first imperfect refers to the past, the second to the present time:

:εἰ μὴ τότʼ '''ἐπόνουν''', νῦν '''ἂν''' οὐκ '''εὐφραινόμην'''. (Philemon 153)
:&quot;if '''I had''' not '''been toiling''' then, '''I would''' not now '''be rejoicing'''.&quot;

The particle ἄν is sometimes omitted from unreal conditions, especially with imperfect verbs expressing obligation or possibility, such as ἐξῆν (“it was possible”; Smyth §2313).

:ἐμὲ δʼ '''ἐξῆν''' αὐτῷ, εἰ '''ἐσωφρόνει''', μὴ συκοφαντεῖν. (Aeschines, 1.3)
:&quot;'''it would have been possible''' for him, if '''he had been wise''', not to accuse me falsely.&quot;

When the emphasis is on possibility or necessity rather than the dependent [[Koine Greek/Infinitives|infinitive]], ἄν may be added (Smyth §2319). Here ἐξεγένετο is the aorist counterpart of the imperfect ἐξῆν:
:περὶ ἐμοῦ μὲν γὰρ εἰ '''ἔλεγον''' ἃ οὗτος ἐβούλετο, οὐδʼ '''ἂν''' ἀπολογήσασθαί μοι '''ἐξεγένετο'''. (Lysias, 7.37)
:&quot;if (the tortured slaves) '''were to say''' about me what he wanted them to say, '''it would'''n't '''have been possible''' for me to defend myself.&quot;

Other expressions can also omit ἄν (Smyth §2320):

:τούτῳ δʼ εἰ μὴ ὡμολόγουν, οὐδεμιᾷ ζημίᾳ '''ἔνοχος ἦν'''. (Lysias, 7.37)
:&quot;if (the tortured slaves) did not agree with him, '''he would'''n't''' have been liable''' to any penalty.&quot;

==If by chance==
A vivid future conditional with ἐάν and the subjunctive can mean “in the hope that,” “in case,” or “to see whether” (Smyth §2354).
:ἄκουσον καὶ ἐμοῦ, ἐάν σοι ἔτι ταὐτὰ '''δοκῇ'''. (Plato, Rep. 358b)
:&quot;listen to me too, in case the same things '''may''' still '''seem''' true to you.&quot;

In a historic context, this type of clause becomes a less vivid future, using εἰ or εἰ πως &quot;if by chance&quot; with the optative mood. In the first example below, πείσειαν &quot;they might persuade&quot; is aorist optative:

:πορευόμενοι ἐς τὴν Ἀσίαν ὡς βασιλέα, εἴ πως '''πείσειαν''' αὐτὸν χρήματά τε παρασχεῖν καὶ ξυμπολεμεῖν. (Thucydides, 2.67)
:&quot;proceeding to Asia to the King, in the hope that '''they might persuade''' him to provide money and join the war.&quot;

: ἔσπευδεν γὰρ εἰ δυνατὸν '''εἴη''' αὐτῷ τὴν ἡμέραν τῆς πεντηκοστῆς γενέσθαι εἰς Ἱεροσόλυμα. (Acts 20:16)
: &quot;for he was hurrying, in case '''it might be''' possible for him to reach Jerusalem by the day of Pentecost.&quot;
:ζητεῖν τὸν θεὸν, εἰ ἄρα γε '''ψηλαφήσειαν''' αὐτὸν καὶ '''εὕροιεν''', καί γε οὐ μακρὰν ἀπὸ ἑνὸς ἑκάστου ἡμῶν ὑπάρχοντα. (Acts 17:27)
:&quot;to seek God, if perhaps they might '''feel for''' him and '''find''' him, though he is not far from each one of us.&quot;

==Wishes==
Wishes in Greek use tenses from the historic sequence: optative, imperfect indicative, and aorist indicative, depending on whether they refer to the future, present or past.

===Wishes for the future===
The optative alone can express a wish for the future (Smyth §1814):
:μὴ '''γένοιτο'''. (Romans 6:2)
: &quot;'''May it never be'''!&quot;

A wish may be introduced by εἴθε or εἰ γάρ (“if only”), using the same construction as a less vivid future condition (Smyth §1815):
: εἰ γὰρ '''γένοιτο'''. (Xenophon, Cyrop. 6.1.38)
: &quot;if only '''it might happen'''!&quot;

===Wishes for the present and past===
An unattainable wish about the present or past uses εἴθε or εἰ γάρ with the imperfect or aorist indicative, as in unreal conditions (Smyth §1780). The imperfect refers to the present:
: εἴθʼ '''εἶχες''', ὦ τεκοῦσα, βελτίους φρένας. (Euripides, Electra 1060)
: &quot;if only, mother, '''you had''' a better heart!&quot;

The aorist indicative is used for an unattainable wish referring to past time:
: εἴθε σοι, ὦ Περίκλεις, τότε '''συνεγενόμην'''. (Xenophon, Memorabilia 1.2.46)
: &quot;if only '''I had been with''' you then, Pericles!&quot;

The aorist of ὀφείλω (“I owe”) can also express a wish (LSJ, s.v. ὀφείλω).
:τὸ τριώβολον δῆτʼ ἔλαβες; – εἰ γὰρ '''ὤφελον'''. (Aristophanes, Eccl. 380)
:&quot;did you get the three-obol fee?&quot; – &quot;'''I wish''' I had!&quot;

Hence in the well-known opening of Euripides' play ''Medea'':
:εἴθʼ '''ὤφελʼ''' Ἀργοῦς '''μὴ διαπτάσθαι''' σκάφος&lt;br /&gt;Κόλχων ἐς αἶαν κυανέας Συμπληγάδας. (Euripides, Medea 1–2)
:&quot;if only the ship {{w|Argo}} '''had not flown through'''&lt;br /&gt;the dark blue [[w:Symplegades|Clashing Rocks]] to the land of the [[w:Colchis|Colchians]]!&quot;

==Conditional relative clauses==
In Ancient Greek, a [[Koine Greek/8. Pronouns#The Relative Pronoun|relative clause]] can replace the protasis of a conditional (“whoever saw it would be amazed” = “if anyone saw it, they would be amazed”). These conditional relative clauses follow the same rules as ordinary conditionals and are always indefinite (Smyth §§2560–2565):

:Πᾶς οὖν '''ὅστις''' '''ὁμολογήσει''' ἐν ἐμοὶ ἔμπροσθεν τῶν ἀνθρώπων, ὁμολογήσω κἀγὼ ἐν αὐτῷ ἔμπροσθεν τοῦ πατρός μου τοῦ ἐν οὐρανοῖς. (Matthew 10:32)
:&quot;everyone, then, who '''confesses''' me before people, I too will confess him before my Father in heaven.&quot;

:οἱ παῖδες ὑμῶν, '''ὅσοι''' ἐνθάδε ἦσαν, ὑπὸ τούτων ἂν ὑβρίζοντο. (Lysias, 12.98)
:&quot;your children, '''as many as''' were here (i.e. if any had been here), would have been abused by these men.&quot;

==Conditional clauses in indirect speech==

===Indirect statements===
In indirect statements, main verbs usually become infinitives unless the statement is introduced by ὅτι or ὡς. In a past context, verbs may instead become optatives; some may become participles, and present indicatives may become imperfects (Smyth §§2576, 2613, 2624).

In a past context, ἐάν + subjunctive may change to εἰ + optative in indirect conditionals. An imperfect or aorist indicative in an unreal protasis does not change to the optative. In an ideal or unreal apodosis, ἄν remains when the verb becomes an infinitive or participle (Smyth §§2615, 2619).

The following table shows how the tenses of an original statement are changed to different tenses of the infinitive, participle, and optative when the speech is made indirect:

:{| class=&quot;wikitable&quot;
! Original speech
! Infinitive
! Participle
! Optative
! Past
|-
| Present or imperfect
| Present
| Present
| Present
| Imperfect
|-
| Future indicative
| Future
| Future
| Future
|
|-
| Aorist indicative
| Aorist
| Aorist
| Aorist
|
|-
| Perfect or pluperfect
| Perfect
| Perfect
| Perfect
| Pluperfect
|}

====Indirect statements with the infinitive====
In the four examples of indirect statement below, all the main verbs of the original speech have been changed to an infinitive.

The first example is an indirect present open conditional. The infinitive ἐλευθεροῦν represents the original present indicative ἐλευθεροῖς (“you are freeing”), while the protasis verb (“you are killing”) becomes imperfect indicative (Smyth §2634):

:ἔλεγον οὐ καλῶς τὴν Ἑλλάδα '''ἐλευθεροῦν''' αὐτόν, εἰ ἄνδρας '''διέφθειρεν'''. (Thucydides, 3.32)
:&quot;they said that '''he was''' not '''freeing''' Greece in a good way, if '''he was killing''' men.&quot;

This indirect emotional future conditional changes the main verbs (“there is” and “it will be”) to present and future infinitives. The future indicative in the protasis becomes future optative (Smyth §2621):

:ἔφη '''εἶναι''' ἄκρον ὃ εἰ μή τις '''προκαταλήψοιτο''', ἀδύνατον '''ἔσεσθαι''' παρελθεῖν. (Xenophon, Anabasis 4.1.25)
:&quot;he said that '''there was''' a hill-top which, unless someone '''captured it first''', '''it was going to be''' impossible to get past.&quot;

This unreal past conditional uses a present participle in a [[Koine Greek/The Genitive Absolute|genitive absolute]] where the original protasis would have had an imperfect indicative. The main verb becomes an aorist infinitive, and ἄν remains after the participle (LSJ, s.v. ἄν, II.D.2):

:'''λέγοντος ἄν''' τινος '''πιστεῦσαι''' οἴεσθε; (Demosthenes, 6.20)
:&quot;do you think that, if someone '''had told''' them, '''they would have believed''' it?&quot; (εἴ τις ἔλεγεν, ἐπίστευσαν ἄν;)

This vivid future conditional in a past context changes the main verb (“I will not stop”) to a future infinitive. ἐάν and πρὶν ἄν with the aorist subjunctive become εἰ and πρίν with the aorist optative; the relative-clause verb στρατεύομαι (“I am campaigning”) becomes imperfect indicative (Smyth §2634):

:ὑποσχόμενος αὐτοῖς, εἰ καλῶς '''καταπράξειεν''' ἐφʼ ἃ '''ἐστρατεύετο''', μὴ πρόσθεν '''παύσεσθαι''' πρὶν αὐτοὺς '''καταγάγοι''' οἴκαδε. (Xenophon, Anabasis 1.2.2)
:&quot;promising them that if '''he accomplished''' what '''he was campaigning''' for, '''he would''' not '''stop''' until '''he brought them back''' home.&quot; (εἰ καλῶς καταπράξομαι ἐφʼ ἅ στρατεὐομαι, οὐ πρόσθεν παύσομαι πρὶν ἂν ὑμᾶς καταγάγω οἴκαδε.)

====Indirect statements with ὅτι====
Indirect statements can also use ὅτι (“that”). In a past context, the verbs may change to the optative (Smyth §2619).

In the following example, the main verb ἐπιθήσοιεν has been changed to the future optative, but the future indicative in the protasis has not been changed to the optative:
:ἠπείλουν αὐτῷ ὅτι εἰ '''λήψονται''' ἀποδιδράσκοντα, τὴν δίκην '''ἐπιθήσοιεν'''. (Xenophon, Anabasis 5.6.34)
:&quot;they threatened him that if they caught (lit. will catch) him running away, they would punish him.&quot;

In unreal conditional clauses, the indicative remains unchanged (Smyth §§2615, 2623):
:ἀπελογοῦντο ὡς οὐκ '''ἄν''' ποτε οὕτω μῶροι '''ἦσαν''' εἰ '''εἴδεσαν'''. (Xenophon, Hell. 5.4.22)
:&quot;they pleaded that they '''would''' never '''have been''' so foolish if '''they had known'''.&quot;

===Indirect questions===
An indirect question may use εἰ (“if”) even when the original question was not conditional (Smyth §2671). In a past context, the main verb may change to the optative: βούλει (“are you willing?”) becomes βούλοιτο. The aorist participle λαβών (“having received”) may imply a vivid or less vivid future condition (cf. Smyth §2359):

:ἐγὼ δὲ Πείσωνα μὲν ἠρώτων εἰ '''βούλοιτό''' με σῶσαι χρήματα '''λαβών'''. (Lysias, 12.9)
:&quot;I asked Pison if '''he was willing''' to save me '''if he received''' some money.&quot;

The optative remains unchanged in indirect speech (Smyth §2620). The ἄν in the following sentence indicates that the original question used the potential optative (“would you give?”):

:ἠρώτων ἐκεῖνοι εἰ '''δοῖεν ἂν''' τούτων τὰ πιστά. (Xenophon, Anabasis 4.8.7)
:&quot;they asked if (the Greeks) '''would give''' pledges concerning these matters.&quot;

===Indirect commands===
In indirect commands, the verb generally becomes an infinitive (Smyth §2633):

:εἰ οὖν τι βούλονται σαφὲς λέγειν, '''πέμψαι''' ἄνδρας ὡς αὐτόν. (Thucydides, 4.50)
:&quot;(the letter said that) if therefore they wished to say something clearly, they should send some men to him.&quot;

Although the context is past, βούλονται (“they wish”) remains indicative rather than changing to the optative. Retaining the vivid mood is characteristic of Thucydides (Smyth §2613).

:{{BookCat}}</text>
      <sha1>njaw8pihrywqdx1vxbdj40j71jfhqil</sha1>
    </revision>
    <revision>
      <id>4676581</id>
      <parentid>4676574</parentid>
      <timestamp>2026-10-18T01:34:27Z</timestamp>
      <contributor>
        <username>It-is-Truly-Meet</username>
        <id>3624460</id>
      </contributor>
      <minor />
      <comment>Brief definitions were readded.</comment>
      <origin>4676581</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="29218" sha1="6i009xafuctifdk2dl034jwjldfr7jz" xml:space="preserve">'''Conditional clauses''' in Koine Greek are clauses which start with εἰ &quot;if&quot; or ἐάν &quot;if (it may be)&quot;. ἐάν can be contracted to ἤν or ἄν, with a long vowel. The &quot;if&quot;-clause of a conditional sentence is called the '''protasis''', and the consequent or main clause is called the '''apodosis'''.

The negative particle in a conditional clause is usually μή, making the conjunctions εἰ μή or ἐὰν μή &quot;unless&quot;, &quot;if not&quot;. However, some conditions have οὐ. The apodosis usually has οὐ.

A conditional clause preceded by εἴθε or εἰ γάρ &quot;if only&quot; is also occasionally used in Greek for making a wish. The conjunction εἰ also frequently introduces an indirect question.

==Classification of conditional clauses==
Conditional clauses fall into several types, summarized below.

A present general condition and a vivid future condition both use ἐάν with the subjunctive; a past general condition and a less vivid future condition both use εἰ with the optative. In each pair, the apodosis distinguishes the meaning.

Hypothetical conditions (&quot;if I were to die&quot;, &quot;if I was dead&quot;, &quot;if I had died&quot;) usually have ἄν in the apodosis. It may be omitted with an imperfect expressing necessity or possibility, such as ἔδει (&quot;it was necessary&quot;) or ἐξῆν (&quot;it was possible&quot;).

{| class=&quot;wikitable&quot;
! Type
! Example
! Protasis
! Apodosis
|-
| colspan=&quot;4&quot;|'''Primary tenses'''
|-
| Simple (open)
| ''If it is true''
| εἰ + present or perfect indicative
| indicative or imperative
|-
| Emotional future
| ''If it happens (in future)''
| εἰ + future indicative
| future indicative
|-
| Vivid future
| ''If it happens (in future)''
| ἐάν + subjunctive
| future indicative
|-
| General present
| ''If ever it happens''
| ἐάν + subjunctive
| present indicative
|-
| colspan=&quot;4&quot;|'''Historic tenses'''
|-
| Simple (open)
| ''If it was true''
| εἰ + imperfect or aorist indicative
| indicative
|-
| General past
| ''If ever it used to happen''
| εἰ + optative
| imperfect indicative
|-
| Less vivid future
| ''If it were to happen''
| εἰ + optative
| optative + ἄν
|-
| Unreal present
| ''If it were true''
| εἰ + imperfect indicative
| imperfect indicative + ἄν
|-
| Unreal past
| ''If it had happened''
| εἰ + aorist indicative
| aorist indicative + ἄν
|}

==Simple (open) conditions==
A simple condition uses the indicative in the protasis. The apodosis can have an imperative:
:εἴ τις '''ἔρχεται''' πρὸς ὑμᾶς καὶ ταύτην τὴν διδαχὴν '''οὐ φέρει''', '''μὴ λαμβάνετε''' αὐτὸν εἰς οἰκίαν καὶ χαίρειν αὐτῷ '''μὴ λέγετε'''. (2 John 1:10)
:&quot;if anyone '''comes''' to you and '''does not bring''' this teaching, '''do not receive''' him into your house, and '''do not greet''' him.&quot;

:Εἰ οὖν '''συνηγέρθητε''' τῷ Χριστῷ, τὰ ἄνω '''ζητεῖτε'''. (Colossians 3:1)
:&quot;if you '''have been raised''' with Christ, '''seek''' the things above.&quot;

:εἰ δὲ πνεύματι '''ἄγεσθε''', '''οὐκ ἐστὲ''' ὑπὸ νόμον. (Galatians 5:18)
:&quot;if you '''are led''' by the Spirit, you '''are not''' under the law.&quot;

A simple conditional may use any tense of the indicative. The following has the perfect indicative:
:εἰ δὲ Χριστὸς οὐκ '''ἐγήγερται''', κενὸν ἄρα τὸ κήρυγμα ἡμῶν, κενὴ καὶ ἡ πίστις ὑμῶν. (1 Corinthians 15:14)
:&quot;if Christ '''has not been raised''', then our preaching is in vain, and your faith is in vain.&quot;

The following uses the imperfect indicative in both clauses:
:εἰ ἐν ἐκείνῃ τῇ νυκτὶ ἐγὼ '''ἐπεβούλευον''' Ἐρατοσθένει, πότερον '''ἦν''' μοι κρεῖττον αὐτῷ ἑτέρωθι δειπνεῖν ἢ τὸν συνδειπνήσοντά μοι εἰσαγαγεῖν; (Lysias 1:40)
:&quot;if on that night '''I was plotting''' against Eratosthenes, '''was it''' better for me to dine elsewhere or to bring that guest to my house?&quot;

The following uses the aorist indicative followed by an aorist imperative:
:{{lang|grc|εἰ '''ἤκουσάς''' τι τούτου τοῦ πράγματος τοῦ γενομένου, '''εἰπέ'''.}} (Andocides 1:50)
:&quot;if '''you heard''' anything about this matter which has happened, '''tell''' us.&quot;

The following, from Euripides' play ''Electra'', has two aorist indicative tenses:
:εἰ δʼ, ὡς λέγεις, σὴν θυγατέρʼ '''ἔκτεινεν''' πατήρ,&lt;br /&gt;ἐγὼ τί σʼ '''ἠδίκησʼ''' ἐμός τε σύγγονος; (Euripides, Electra 1086–1087)
:&quot;even if, as you say, our father '''killed''' your daughter,&lt;br /&gt;how '''did I''' or my brother '''wrong''' you?&quot;

==Future conditions==
===&quot;Emotional&quot; future conditions===
An open conditional may use the future indicative in its protasis to express strong feeling. The apodosis often conveys a threat, warning, or earnest appeal; this is called the “emotional future” conditional.

In the following, a present tense apodosis is combined with a future protasis:
:οὐκ '''ἔστι''' παρελθεῖν, εἰ μὴ τούτους '''ἀποκόψομεν'''. (Xenophon, Anabasis 3.4.39)
:&quot;'''it's''' impossible to go past, unless '''we first cut down''' these men.&quot;

:τῇ γὰρ στρατιᾷ οὐκ '''ἔστι''' τὰ ἐπιτήδεια, εἰ μὴ '''ληψόμεθα''' τὸ χωρίον. (Xenophon, Anabasis 4.7.3)
:&quot;'''there is''' no food for the army, unless '''we capture''' the fort.&quot;

In the following poetic example, the protasis has a future indicative as before, but in the apodosis instead of a future, there is an aorist indicative:
:{{lang |grc|'''ἀπωλόμην''' ἄρ᾽, εἴ με δὴ '''λείψεις''', γύναι.}} (Euripides, Alcestis 386)
:&quot;'''I am undone''' if '''you leave''' me, wife!&quot;

===Vivid future conditions===
A future conditional usually uses ἐάν (also ἤν or ἄν) with the subjunctive. The α in ἐάν is long (LSJ, s.v. ἐάν; Smyth §34).

This common construction is called the vivid future conditional. The protasis has the present subjunctive and the apodosis the future indicative (Smyth §§2297, 2321–2322).

:Ἐὰν '''ἀγαπᾶτέ''' με, τὰς ἐντολὰς τὰς ἐμὰς '''τηρήσετε'''. (John 14:15)
: &quot;if you '''love''' me, you '''will keep''' my commandments.&quot;

:καὶ ἐὰν ἐκεῖ '''ᾖ''' υἱὸς εἰρήνης, '''ἐπαναπαήσεται''' ἐπʼ αὐτὸν ἡ εἰρήνη ὑμῶν. (Luke 10:6)
: &quot;and if a '''son of peace is''' there, your peace '''will rest''' upon him.&quot;

:ἐάν τις '''θέλῃ''' τὸ θέλημα αὐτοῦ ποιεῖν, '''γνώσεται''' περὶ τῆς διδαχῆς πότερον ἐκ τοῦ θεοῦ ἐστιν ἢ ἐγὼ ἀπʼ ἐμαυτοῦ λαλῶ. (John 7:17)
:&quot;if anyone '''wishes''' to do his will, he '''will know''' concerning the teaching whether it is from God or I speak from myself.&quot;

:ἐάν τις '''ἀγαπᾷ''' με, τὸν λόγον μου '''τηρήσει'''. (John 14:23)
:&quot;if anyone '''loves''' me, he '''will keep''' my word.

The apodosis can contain a present tense, if the verb is δεῖ &quot;it is necessary&quot;:
:τὸ γὰρ αὔτʼ, ἐὰν '''ἡττᾶσθε''', καὶ σφὼ '''δεῖ παθεῖν'''. (Aristophanes, Plut. 467)
:&quot;you two '''must suffer''' the same penalty too, if '''you are defeated'''&quot;

The negative used in a conditional clause is usually μή:
:ἐὰν δὲ '''μὴ ἀφῆτε''' τοῖς ἀνθρώποις, οὐδὲ ὁ πατὴρ ὑμῶν '''ἀφήσει''' τὰ παραπτώματα ὑμῶν. (Matthew 6:15)
: &quot;but if you '''do not forgive''' people, neither will your Father '''forgive''' your trespasses.&quot;

:ἐὰν γὰρ '''μὴ πιστεύσητε''' ὅτι ἐγώ εἰμι, '''ἀποθανεῖσθε''' ἐν ταῖς ἁμαρτίαις ὑμῶν. (John 8:24)
:&quot;for if you '''do not believe''' that I am he, you '''will die''' in your sins.&quot;

Sometimes οὐ is used instead of μή, as when οὔ φημι means “deny” (Smyth §§2696, 2698).

:ἐάντε σὺ καὶ Ἄνυτος '''οὐ φῆτε''' ἐάντε φῆτε (Plato, Apology 25b)
:&quot;whether you and Anytos '''deny it''' or agree with it&quot;

The following example uses the aorist subjunctive in the protasis:
:κἀγὼ ἐὰν '''ὑψωθῶ''' ἐκ τῆς γῆς, πάντας '''ἑλκύσω''' πρὸς ἐμαυτόν. (John 12:32)
:&quot;and I, if I am '''lifted up''' from the earth, '''will draw''' all people to myself.&quot;

===Less vivid future conditions===
The less vivid (or ideal) future conditional describes a hypothetical future, often one the speaker does not expect to happen. Both clauses use the optative; the apodosis has the [[Koine Greek/Overview of Particles|particle]] ἄν before or after the verb (Smyth §2329).

The tense of the verb can be aorist (if it is an event) or present (if it describes a situation). The following three examples use the aorist optative:

:καὶ ὁ Παρθένιος ἄβατος· ἐφʼ ὃν '''ἔλθοιτε ἄν''', εἰ τὸν Ἅλυν '''διαβαίητε'''. (Xenophon, Anabasis 5.6.10)
:&quot;the Parthenios river also cannot be crossed, to which '''you would come''' if '''you crossed''' the Halys.&quot;

:οὐδέν γε ἄτοπον εἰ '''ἀποθάνοιμι'''. (Plato, Gorgias 521d)
:&quot;there would be nothing strange about it if '''I were to die'''.&quot;

:εἰ δή τις με '''ἔροιτο''' ὑμῶν ... '''εἴποιμʼ ἄν''' ... (Aeschines, 1.80)
:&quot;if one of '''you were to ask''' me ... '''I would say''' ...&quot;

The following have present optative in the protasis, aorist optative in the apodosis:
:εἰ γὰρ '''εἰδείης''' ὅσον ἀργύριον εἴργασμαι ἐγώ, '''θαυμάσαις ἄν'''. (Plato, Hipp. Mai. 282d)
:&quot;if '''you knew''' how much money I have earned, '''you would be amazed'''.&quot;

:ἡδέως '''ἂν λάβοιμι''', εἰ '''διδοίη'''. (Xenophon, Cyropaedia 3.2.28)
:&quot;'''I would''' gladly '''accept''' it, if '''he were offering''' it.&quot;

The following uses the present optative in the apodosis:
:οὐκ '''ἂν θαυμάζοιμι'''. (Plato, Cratylus 428b)
:&quot;'''I would'''n't '''be surprised''' (if that were so).&quot;

In post-classical Greek, the optative mood gradually fell out of use. In the New Testament the potential optative with ἄν occurs, but rarely (e.g. ''Acts'' 8:31); εἰ with the optative also sometimes occurs (e.g. 2 Peter 3:14).

==General conditions==
===Present general conditions===
A present general condition uses the same grammatical construction (ἐάν with the subjunctive) as a vivid future condition, but is much less common. The present subjunctive is used when the actions of the two clauses are contemporaneous:
:ἐὰν '''ὁμολογῶμεν''' τὰς ἁμαρτίας ἡμῶν, '''πιστός ἐστιν''' καὶ δίκαιος ἵνα ἀφῇ ἡμῖν τὰς ἁμαρτίας καὶ καθαρίσῃ ἡμᾶς ἀπὸ πάσης ἀδικίας. (1 John 1:9)
:&quot;if we '''confess''' our sins, he '''is faithful''' and righteous to forgive us our sins and to cleanse us from all unrighteousness.&quot;

The aorist subjunctive indicates that this action precedes the main action (Smyth §2623, note 2).
:καὶ ἐὰν τις '''ἁμάρτῃ''', '''παράκλητον ἔχομεν''' πρὸς τὸν πατέρα, Ἰησοῦν Χριστὸν δίκαιον. (1 John 2:1)
:&quot;and if anyone '''sins''', we '''have an advocate''' with the Father, Jesus Christ the righteous.&quot;

The perfect subjunctive describes a present state resulting from an earlier action:
:ἐάν τε '''ἑαλωκὼς ᾖ''' ἐάν τε μή, δηλούτω. (Xenophon, Cynegeticus 6.18)
:&quot;whether (the hare) '''has been caught''' or not, (the huntsman) should make it clear (to his colleagues).&quot;

An aorist in the apodosis can sometimes express a general truth in the present; this is called a gnomic aorist (Smyth §§1931, 2338).
:ἢν δέ τις τούτων τι παραβαίνῃ, ζημίαν αὐτοῖς '''ἐπέθεσαν'''. (Xenophon, Cyr. 1.2.2)
:&quot;if a man transgress anyone one of these laws, '''they always impose''' a penalty on him.&quot;

===Past general conditions===
The optative after εἰ can express a past general condition (“if ever it used to happen”; Smyth §2340). In the following examples, the protasis has the present optative and the apodosis the imperfect indicative:
: εἴ πού τι '''ὁρῴη''' βρωτόν, '''διεδίδου'''. (Xenophon, Anabasis 4.5.8)
: &quot;If ever '''he saw''' something edible anywhere, '''he would pass''' it round.&quot;

:καὶ πάνυ ἄκρατος '''ἦν''', εἰ μή τις ὕδωρ '''ἐπιχέοι'''. (Xenophon, Anabasis 4.5.27)
:&quot;and (the barley-wine) '''was''' completely undiluted, unless someone '''added''' water.&quot;

In the following, however, the aorist optative is used in the protasis, to indicate that the action of sharing had to come before that of being allowed near the fire:
: οὐ '''προσίεσαν''' πρὸς τὸ πῦρ τοὺς ὀψίζοντας, εἰ μὴ '''μεταδοῖεν''' αὐτοῖς πῡρούς. (Xenophon, Anabasis 4.5.5)
: &quot;they '''wouldn't let''' the late-comers come near the fire, unless '''they first shared''' some wheat with them.&quot;

Here the protasis is shortened to εἰ δὲ μή (“otherwise”), meaning “but if they did not hold their weapons above the water” (cf. Smyth §2346).
:καὶ οὔτʼ ἐν τῷ ὕδατι τὰ ὅπλα ἦν ἔχειν· '''εἰ δὲ μή''', '''ἥρπαζεν''' ὁ ποταμός. (Xenophon, Anabasis 3.4.36)
:&quot;and it was not possible to hold their weapons in the water, '''otherwise''' the river '''kept snatching''' them away.&quot;

In a past general condition, ἄν may accompany an imperfect or aorist indicative to express repeated past action. This is called the iterative imperfect or aorist (Smyth §2341). The following example uses the imperfect indicative with ἄν:

:εἰ δέ τις αὐτῷ περί του '''ἀντιλέγοι''' ... ἐπὶ τὴν ὑπόθεσιν '''ἐπανῆγεν ἂν''' πάντα τὸν λόγον. (Xenophon, Memorabilia 4.6.13)
:&quot;if ever anyone '''opposed''' him on anything ... '''he would bring''' the whole subject '''back''' to the beginning&quot;

The following uses the aorist indicative with ἄν:
:καὶ εἴ τις αὐτῷ '''δοκοίη''' ... βλακεύειν, ἐκλεγόμενος τὸν ἐπιτήδειον '''ἔπαισεν ἄν'''. (Xenophon, Anabasis 2.3.11)
:'if ever anyone '''seemed''' to him to be lagging behind, he would pick out the culprit and '''would beat''' him.'

==Unreal conditions==
===Present unreal conditions===
A present unreal ([[#Unreal conditions|counterfactual]]) condition uses εἰ with the imperfect indicative in the protasis and the imperfect indicative plus ἄν in the apodosis (Smyth §2309).

:εἰ ἐκ τοῦ κόσμου '''ἦτε''', ὁ κόσμος ἂν τὸ ἴδιον '''ἐφίλει'''. (John 15:19)
:&quot;if you '''were''' of the world, the world '''would love''' its own.&quot;

:εἰ δὲ ἑαυτοὺς '''διεκρίνομεν''', οὐκ ἂν '''ἐκρινόμεθα'''. (1 Corinthians 11:31)
:&quot;but if we '''judged''' ourselves, we '''would not be judged'''.&quot;

===Past unreal conditions===
A past unreal condition uses the aorist indicative in both clauses, with ἄν in the apodosis to express “would” (Smyth §2309).
:εἰ μὴ κύριος σαβαὼθ '''ἐγκατέλιπεν''' ἡμῖν σπέρμα, ὡς Σόδομα ἂν '''ἐγενήθημεν'''. (Romans 9:29)
:&quot;if the Lord of Sabaoth had not '''left''' us offspring, we '''would have become''' like Sodom.&quot;

The following example has an apodosis only with no protasis. The tense is aorist indicative:
:τίς γὰρ '''ἂν ᾠήθη''' ταῦτα γενέσθαι; (Demosthenes 9.68)
:&quot;for who '''would have expected''' these things to happen?&quot;

In an unreal condition, an imperfect can refer to the past as well as the present. Here ἦς is imperfect indicative and ἀπέθανεν is aorist indicative (Smyth §§2309–2310):
:εἰ '''ἦς''' ὧδε, οὐκ ἂν '''ἀπέθανεν''' ὁ ἀδελφός μου. (John 11:21)
:&quot;Lord, if you '''had been''' here, my brother '''would not have died'''.&quot;

In the following, the first imperfect refers to the past, the second to the present time:

:εἰ μὴ τότʼ '''ἐπόνουν''', νῦν '''ἂν''' οὐκ '''εὐφραινόμην'''. (Philemon 153)
:&quot;if '''I had''' not '''been toiling''' then, '''I would''' not now '''be rejoicing'''.&quot;

The particle ἄν is sometimes omitted from unreal conditions, especially with imperfect verbs expressing obligation or possibility, such as ἐξῆν (“it was possible”; Smyth §2313).

:ἐμὲ δʼ '''ἐξῆν''' αὐτῷ, εἰ '''ἐσωφρόνει''', μὴ συκοφαντεῖν. (Aeschines, 1.3)
:&quot;'''it would have been possible''' for him, if '''he had been wise''', not to accuse me falsely.&quot;

When the emphasis is on possibility or necessity rather than the dependent [[Koine Greek/Infinitives|infinitive]], ἄν may be added (Smyth §2319). Here ἐξεγένετο is the aorist counterpart of the imperfect ἐξῆν:
:περὶ ἐμοῦ μὲν γὰρ εἰ '''ἔλεγον''' ἃ οὗτος ἐβούλετο, οὐδʼ '''ἂν''' ἀπολογήσασθαί μοι '''ἐξεγένετο'''. (Lysias, 7.37)
:&quot;if (the tortured slaves) '''were to say''' about me what he wanted them to say, '''it would'''n't '''have been possible''' for me to defend myself.&quot;

Other expressions can also omit ἄν (Smyth §2320):

:τούτῳ δʼ εἰ μὴ ὡμολόγουν, οὐδεμιᾷ ζημίᾳ '''ἔνοχος ἦν'''. (Lysias, 7.37)
:&quot;if (the tortured slaves) did not agree with him, '''he would'''n't''' have been liable''' to any penalty.&quot;

==If by chance==
A vivid future conditional with ἐάν and the subjunctive can mean “in the hope that,” “in case,” or “to see whether” (Smyth §2354).
:ἄκουσον καὶ ἐμοῦ, ἐάν σοι ἔτι ταὐτὰ '''δοκῇ'''. (Plato, Rep. 358b)
:&quot;listen to me too, in case the same things '''may''' still '''seem''' true to you.&quot;

In a historic context, this type of clause becomes a less vivid future, using εἰ or εἰ πως &quot;if by chance&quot; with the optative mood. In the first example below, πείσειαν &quot;they might persuade&quot; is aorist optative:

:πορευόμενοι ἐς τὴν Ἀσίαν ὡς βασιλέα, εἴ πως '''πείσειαν''' αὐτὸν χρήματά τε παρασχεῖν καὶ ξυμπολεμεῖν. (Thucydides, 2.67)
:&quot;proceeding to Asia to the King, in the hope that '''they might persuade''' him to provide money and join the war.&quot;

: ἔσπευδεν γὰρ εἰ δυνατὸν '''εἴη''' αὐτῷ τὴν ἡμέραν τῆς πεντηκοστῆς γενέσθαι εἰς Ἱεροσόλυμα. (Acts 20:16)
: &quot;for he was hurrying, in case '''it might be''' possible for him to reach Jerusalem by the day of Pentecost.&quot;
:ζητεῖν τὸν θεὸν, εἰ ἄρα γε '''ψηλαφήσειαν''' αὐτὸν καὶ '''εὕροιεν''', καί γε οὐ μακρὰν ἀπὸ ἑνὸς ἑκάστου ἡμῶν ὑπάρχοντα. (Acts 17:27)
:&quot;to seek God, if perhaps they might '''feel for''' him and '''find''' him, though he is not far from each one of us.&quot;

==Wishes==
Wishes in Greek use tenses from the historic sequence: optative, imperfect indicative, and aorist indicative, depending on whether they refer to the future, present or past.

===Wishes for the future===
The optative alone can express a wish for the future (Smyth §1814):
:μὴ '''γένοιτο'''. (Romans 6:2)
: &quot;'''May it never be'''!&quot;

A wish may be introduced by εἴθε or εἰ γάρ (“if only”), using the same construction as a less vivid future condition (Smyth §1815):
: εἰ γὰρ '''γένοιτο'''. (Xenophon, Cyrop. 6.1.38)
: &quot;if only '''it might happen'''!&quot;

===Wishes for the present and past===
An unattainable wish about the present or past uses εἴθε or εἰ γάρ with the imperfect or aorist indicative, as in unreal conditions (Smyth §1780). The imperfect refers to the present:
: εἴθʼ '''εἶχες''', ὦ τεκοῦσα, βελτίους φρένας. (Euripides, Electra 1060)
: &quot;if only, mother, '''you had''' a better heart!&quot;

The aorist indicative is used for an unattainable wish referring to past time:
: εἴθε σοι, ὦ Περίκλεις, τότε '''συνεγενόμην'''. (Xenophon, Memorabilia 1.2.46)
: &quot;if only '''I had been with''' you then, Pericles!&quot;

The aorist of ὀφείλω (“I owe”) can also express a wish (LSJ, s.v. ὀφείλω).
:τὸ τριώβολον δῆτʼ ἔλαβες; – εἰ γὰρ '''ὤφελον'''. (Aristophanes, Eccl. 380)
:&quot;did you get the three-obol fee?&quot; – &quot;'''I wish''' I had!&quot;

Hence in the well-known opening of Euripides' play ''Medea'':
:εἴθʼ '''ὤφελʼ''' Ἀργοῦς '''μὴ διαπτάσθαι''' σκάφος&lt;br /&gt;Κόλχων ἐς αἶαν κυανέας Συμπληγάδας. (Euripides, Medea 1–2)
:&quot;if only the ship {{w|Argo}} '''had not flown through'''&lt;br /&gt;the dark blue [[w:Symplegades|Clashing Rocks]] to the land of the [[w:Colchis|Colchians]]!&quot;

==Conditional relative clauses==
In Ancient Greek, a [[Koine Greek/8. Pronouns#The Relative Pronoun|relative clause]] can replace the protasis of a conditional (“whoever saw it would be amazed” = “if anyone saw it, they would be amazed”). These conditional relative clauses follow the same rules as ordinary conditionals and are always indefinite (Smyth §§2560–2565):

:Πᾶς οὖν '''ὅστις''' '''ὁμολογήσει''' ἐν ἐμοὶ ἔμπροσθεν τῶν ἀνθρώπων, ὁμολογήσω κἀγὼ ἐν αὐτῷ ἔμπροσθεν τοῦ πατρός μου τοῦ ἐν οὐρανοῖς. (Matthew 10:32)
:&quot;everyone, then, who '''confesses''' me before people, I too will confess him before my Father in heaven.&quot;

:οἱ παῖδες ὑμῶν, '''ὅσοι''' ἐνθάδε ἦσαν, ὑπὸ τούτων ἂν ὑβρίζοντο. (Lysias, 12.98)
:&quot;your children, '''as many as''' were here (i.e. if any had been here), would have been abused by these men.&quot;

==Conditional clauses in indirect speech==

===Indirect statements===
In indirect statements, main verbs usually become infinitives unless the statement is introduced by ὅτι or ὡς. In a past context, verbs may instead become optatives; some may become participles, and present indicatives may become imperfects (Smyth §§2576, 2613, 2624).

In a past context, ἐάν + subjunctive may change to εἰ + optative in indirect conditionals. An imperfect or aorist indicative in an unreal protasis does not change to the optative. In an ideal or unreal apodosis, ἄν remains when the verb becomes an infinitive or participle (Smyth §§2615, 2619).

The following table shows how the tenses of an original statement are changed to different tenses of the infinitive, participle, and optative when the speech is made indirect:

:{| class=&quot;wikitable&quot;
! Original speech
! Infinitive
! Participle
! Optative
! Past
|-
| Present or imperfect
| Present
| Present
| Present
| Imperfect
|-
| Future indicative
| Future
| Future
| Future
|
|-
| Aorist indicative
| Aorist
| Aorist
| Aorist
|
|-
| Perfect or pluperfect
| Perfect
| Perfect
| Perfect
| Pluperfect
|}

====Indirect statements with the infinitive====
In the four examples of indirect statement below, all the main verbs of the original speech have been changed to an infinitive.

The first example is an indirect present open conditional. The infinitive ἐλευθεροῦν represents the original present indicative ἐλευθεροῖς (“you are freeing”), while the protasis verb (“you are killing”) becomes imperfect indicative (Smyth §2634):

:ἔλεγον οὐ καλῶς τὴν Ἑλλάδα '''ἐλευθεροῦν''' αὐτόν, εἰ ἄνδρας '''διέφθειρεν'''. (Thucydides, 3.32)
:&quot;they said that '''he was''' not '''freeing''' Greece in a good way, if '''he was killing''' men.&quot;

This indirect emotional future conditional changes the main verbs (“there is” and “it will be”) to present and future infinitives. The future indicative in the protasis becomes future optative (Smyth §2621):

:ἔφη '''εἶναι''' ἄκρον ὃ εἰ μή τις '''προκαταλήψοιτο''', ἀδύνατον '''ἔσεσθαι''' παρελθεῖν. (Xenophon, Anabasis 4.1.25)
:&quot;he said that '''there was''' a hill-top which, unless someone '''captured it first''', '''it was going to be''' impossible to get past.&quot;

This unreal past conditional uses a present participle in a [[Koine Greek/The Genitive Absolute|genitive absolute]] where the original protasis would have had an imperfect indicative. The main verb becomes an aorist infinitive, and ἄν remains after the participle (LSJ, s.v. ἄν, II.D.2):

:'''λέγοντος ἄν''' τινος '''πιστεῦσαι''' οἴεσθε; (Demosthenes, 6.20)
:&quot;do you think that, if someone '''had told''' them, '''they would have believed''' it?&quot; (εἴ τις ἔλεγεν, ἐπίστευσαν ἄν;)

This vivid future conditional in a past context changes the main verb (“I will not stop”) to a future infinitive. ἐάν and πρὶν ἄν with the aorist subjunctive become εἰ and πρίν with the aorist optative; the relative-clause verb στρατεύομαι (“I am campaigning”) becomes imperfect indicative (Smyth §2634):

:ὑποσχόμενος αὐτοῖς, εἰ καλῶς '''καταπράξειεν''' ἐφʼ ἃ '''ἐστρατεύετο''', μὴ πρόσθεν '''παύσεσθαι''' πρὶν αὐτοὺς '''καταγάγοι''' οἴκαδε. (Xenophon, Anabasis 1.2.2)
:&quot;promising them that if '''he accomplished''' what '''he was campaigning''' for, '''he would''' not '''stop''' until '''he brought them back''' home.&quot; (εἰ καλῶς καταπράξομαι ἐφʼ ἅ στρατεὐομαι, οὐ πρόσθεν παύσομαι πρὶν ἂν ὑμᾶς καταγάγω οἴκαδε.)

====Indirect statements with ὅτι====
Indirect statements can also use ὅτι (“that”). In a past context, the verbs may change to the optative (Smyth §2619).

In the following example, the main verb ἐπιθήσοιεν has been changed to the future optative, but the future indicative in the protasis has not been changed to the optative:
:ἠπείλουν αὐτῷ ὅτι εἰ '''λήψονται''' ἀποδιδράσκοντα, τὴν δίκην '''ἐπιθήσοιεν'''. (Xenophon, Anabasis 5.6.34)
:&quot;they threatened him that if they caught (lit. will catch) him running away, they would punish him.&quot;

In unreal conditional clauses, the indicative remains unchanged (Smyth §§2615, 2623):
:ἀπελογοῦντο ὡς οὐκ '''ἄν''' ποτε οὕτω μῶροι '''ἦσαν''' εἰ '''εἴδεσαν'''. (Xenophon, Hell. 5.4.22)
:&quot;they pleaded that they '''would''' never '''have been''' so foolish if '''they had known'''.&quot;

===Indirect questions===
An indirect question may use εἰ (“if”) even when the original question was not conditional (Smyth §2671). In a past context, the main verb may change to the optative: βούλει (“are you willing?”) becomes βούλοιτο. The aorist participle λαβών (“having received”) may imply a vivid or less vivid future condition (cf. Smyth §2359):

:ἐγὼ δὲ Πείσωνα μὲν ἠρώτων εἰ '''βούλοιτό''' με σῶσαι χρήματα '''λαβών'''. (Lysias, 12.9)
:&quot;I asked Pison if '''he was willing''' to save me '''if he received''' some money.&quot;

The optative remains unchanged in indirect speech (Smyth §2620). The ἄν in the following sentence indicates that the original question used the potential optative (“would you give?”):

:ἠρώτων ἐκεῖνοι εἰ '''δοῖεν ἂν''' τούτων τὰ πιστά. (Xenophon, Anabasis 4.8.7)
:&quot;they asked if (the Greeks) '''would give''' pledges concerning these matters.&quot;

===Indirect commands===
In indirect commands, the verb generally becomes an infinitive (Smyth §2633):

:εἰ οὖν τι βούλονται σαφὲς λέγειν, '''πέμψαι''' ἄνδρας ὡς αὐτόν. (Thucydides, 4.50)
:&quot;(the letter said that) if therefore they wished to say something clearly, they should send some men to him.&quot;

Although the context is past, βούλονται (“they wish”) remains indicative rather than changing to the optative. Retaining the vivid mood is characteristic of Thucydides (Smyth §2613).

:{{BookCat}}</text>
      <sha1>6i009xafuctifdk2dl034jwjldfr7jz</sha1>
    </revision>
  </page>
  <page>
    <title>Wikibooks:Reading room/Administrative Assistance/Archives/2026/October</title>
    <ns>4</ns>
    <id>486385</id>
    <revision>
      <id>4676701</id>
      <parentid>4676476</parentid>
      <timestamp>2026-10-18T08:10:30Z</timestamp>
      <contributor>
        <username>ArchiverBot</username>
        <id>1227662</id>
      </contributor>
      <minor />
      <comment>Bot: Archiving 1 thread from [[Wikibooks:Reading room/Administrative Assistance]]</comment>
      <origin>4676701</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1797" sha1="cveo1i8adhnf31gi0k3ovuq3cd2kbuc" xml:space="preserve">{{talk archive}}

== Tunde akinlabi reported by MathXplore ==

* {{userlinks|Tunde akinlabi}}

Spam &lt;!-- USERREPORTED:/Tunde akinlabi/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:18, 1 October 2026 (UTC)
: Page was deleted by another admin. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:11, 2 October 2026 (UTC)

== Barakat isiaka reported by MathXplore ==

* {{userlinks|Barakat isiaka}}

Spam &lt;!-- USERREPORTED:/Barakat isiaka/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:19, 1 October 2026 (UTC)
: Page was deleted by another admin. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:11, 2 October 2026 (UTC)

== Roconpaas01 reported by MathXplore ==

* {{userlinks|Roconpaas01}}

Link spam, [[Special:AbuseLog/315913]] &lt;!-- USERREPORTED:/Roconpaas01/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:19, 2 October 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:10, 2 October 2026 (UTC)
== Diiminstitute reported by MathXplore ==

* {{userlinks|Diiminstitute}}

Link spam, [[Special:AbuseLog/315963]] &lt;!-- USERREPORTED:/Diiminstitute/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 02:34, 4 October 2026 (UTC)

:{{done}} --[[User:SHB|SHB]] ([[User talk:SHB|discuss]] • [[Special:Contributions/SHB|contribs]]) 02:58, 4 October 2026 (UTC)</text>
      <sha1>cveo1i8adhnf31gi0k3ovuq3cd2kbuc</sha1>
    </revision>
  </page>
  <page>
    <title>Klasky Csupo</title>
    <ns>0</ns>
    <id>486388</id>
    <revision>
      <id>4676525</id>
      <parentid>4676500</parentid>
      <timestamp>2026-10-17T13:42:18Z</timestamp>
      <contributor>
        <username>MathXplore</username>
        <id>3097823</id>
      </contributor>
      <comment>Marking for speedy deletion: Encyclopedic articles belong at [[w:|Wikipedia]]</comment>
      <origin>4676525</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3459" sha1="625ahpbemm8ufn114qjmlgqyokrulzu" xml:space="preserve">&lt;noinclude&gt;{{Delete|example=false|Encyclopedic articles belong at [[w:|Wikipedia]]}}&lt;/noinclude&gt;
The Klasky-Csupo logo, stylized as the Klasky Csupo Robot Logo, SSF, Splaat or Splaat!, is a 5-second logo that is commonly employed in the logo editing community. This logo is viewed as the central emblem or mascot of the community, with its design and other variations being utilized since 2009, although some of the earliest examples can be traced to 2008.

The most commonly used variant is from the 1998 logo, though variants from later dates, such as 2002, have also been used.

== Overview ==
'''Visuals'''
On a static light violet background, a black ink stain on an indigo water background with a liquid effect appears by splattering all over the screen. A CGI live-action human hand comes in from the left and places a yellow piece of paper containing a red-lipped mouth onto the stain, while a pair of blue, round eyes (which seem to wiggle like Jell-O) appear and zoom in above the mouth, forming a bizarre-looking robot face. The face then says the company name as white blocks fly out from its mouth, which are revealed to be the parts of the K-C logo as they arrange themselves to form it (the parts have also been refined to match the print logo, with the &quot;K&quot; in Futura Bold, &quot;L&quot; in Permian Serif, &quot;a&quot; in Times New Roman, &quot;S&quot; in Futura Book, the second &quot;K&quot; in a zig-zaggy font made possibly to match with the Letraset Process in the logo, the &quot;Y&quot; and &quot;CSUPO&quot; set in the same font as the first &quot;K&quot;). During the face's screen time, there are holes in the liquid background (which reveal smudges of the static background that emerge from the center and slide off-screen from many other directions). After that, the background and the face disappear like an old CRT television turning off, and the &quot;Y&quot; in &quot;KLaSKY&quot; turns purple and flashes faintly. The logo remains on-screen for a few seconds, and then it either fades out or cuts to black.

'''Audio'''
A splatter sound is heard when the ink appears and a bouncy &quot;beeping&quot; version of the 24-note bass jingle (which sounds like a clarinet) is played. Another &quot;beepy&quot; instrumental plays the same jingle in the water background, only it comes in a quarter measure late. The company name is stated in a robotic voice with significant amounts of clipping to make it louder (hence the &quot;Robot&quot; nickname; the voice was supplied by the &quot;Boing&quot; novelty voice in the text-to-speech program used on a Power Macintosh G3 workstation). After Splaat finishes talking and the company logo appears, there are four cartoon sound effects: a tiny twang, a lip-flapping sound that sounds similar to the &quot;trombone gobble&quot; sound heard in Warner Bros. cartoons accompanied by a slap, a duck quacking twice, and the classic Hanna-Barbera/Hoyt Curtin boing.

== Variants ==
1. Graffiti Logo
2. Robot Logo
3. Rooster Logo
4. X Csupo
5. Nightmare Csupo
6. Purple Flower
7. Blue Beam
8. Green Cream
9. Red Lead

== Trivia ==
*It is considered to be one of the most widely used sources, with the second being Noggin and Nick Jr. Logo Collection.
RoboSplaat has clarified he prefers to be called Splaat rather than &quot;a robot&quot;.
*The character in the ident is called Splaat.
*Despite this, most people still call it Klasky-Csupo, which has resulted in some people coincidentally finding videos with effects rather than videos related to the actual animation studio, which the Robot ident and a few other idents have been created for.</text>
      <sha1>625ahpbemm8ufn114qjmlgqyokrulzu</sha1>
    </revision>
  </page>
  <page>
    <title>Chess Opening Theory/1. e4/1...e5/2. Nf3/2...Nf6/3. d3</title>
    <ns>0</ns>
    <id>486390</id>
    <revision>
      <id>4676512</id>
      <timestamp>2026-10-17T12:53:18Z</timestamp>
      <contributor>
        <username>~2026-55653-73</username>
        <id>3628611</id>
      </contributor>
      <comment>I have created a Wikibook page for the d3 pawn move played against the Russian Game. I wasn't sure whether I should include a &quot;References&quot; section at the bottom; I would appreciate it if you could add one if necessary. Thanks in advance.</comment>
      <origin>4676512</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="463" sha1="qk579oxlavbjr9ze9enrjhomg55l6py" xml:space="preserve">d3, piyonun [[Chess/Petroff's Defence|Russian game]] karşı d3 piyonuyla e piyonunu koruduğu bir varyanttır. Beyaz sağlam bir savunma yapısı kurar ve Siyah artık piyonunu savunmak zorundadır. Oyun genellikle, renklerin tersine döndüğü bir Philidor Savunması Hanham varyantına (3...Ac6 4. Fe2 d5 5. Abd2 Fc5 ⩱) benzer bir hal alır ya da Beyaz, g3 ve Fg2 hamleleriyle bir &quot;Şah-Hint Saldırısı&quot; (King's Indian Attack) tarzı bir dizilim benimser.</text>
      <sha1>qk579oxlavbjr9ze9enrjhomg55l6py</sha1>
    </revision>
    <revision>
      <id>4676514</id>
      <parentid>4676512</parentid>
      <timestamp>2026-10-17T12:58:18Z</timestamp>
      <contributor>
        <username>~2026-55653-73</username>
        <id>3628611</id>
      </contributor>
      <comment>I'm makedd english.</comment>
      <origin>4676514</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="524" sha1="ftdbf2zd4gjasvjy0adook25sxqfz4j" xml:space="preserve">== In the [[Chess/Petroff's Defence|Russian Game]], the move d3 is a variation in which White uses the d3-pawn to protect the e-pawn. By establishing a solid defensive structure, White also compels Black to defend their own pawn. The game often evolves into a position reminiscent of the Hanham Variation of the Philidor Defence—albeit with the colors reversed (3...Nc6 4. Be2 d5 5. Nbd2 Bc5 ⩱)—or, alternatively, White may opt for a setup in the style of the &quot;King's Indian Attack,&quot; involving the moves g3 and Bg2. ==</text>
      <sha1>ftdbf2zd4gjasvjy0adook25sxqfz4j</sha1>
    </revision>
    <revision>
      <id>4676522</id>
      <parentid>4676514</parentid>
      <timestamp>2026-10-17T13:41:37Z</timestamp>
      <contributor>
        <username>MathXplore</username>
        <id>3097823</id>
      </contributor>
      <minor />
      <comment>Added {{[[Template:BookCat|BookCat]]}} using [[User:1234qwer1234qwer4/BookCat.js|BookCat.js]]</comment>
      <origin>4676522</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="537" sha1="smb3fnzc0mqjz1a3t5ldymm45mt44ga" xml:space="preserve">== In the [[Chess/Petroff's Defence|Russian Game]], the move d3 is a variation in which White uses the d3-pawn to protect the e-pawn. By establishing a solid defensive structure, White also compels Black to defend their own pawn. The game often evolves into a position reminiscent of the Hanham Variation of the Philidor Defence—albeit with the colors reversed (3...Nc6 4. Be2 d5 5. Nbd2 Bc5 ⩱)—or, alternatively, White may opt for a setup in the style of the &quot;King's Indian Attack,&quot; involving the moves g3 and Bg2. ==

{{BookCat}}</text>
      <sha1>smb3fnzc0mqjz1a3t5ldymm45mt44ga</sha1>
    </revision>
  </page>
  <page>
    <title>User:Sarolang</title>
    <ns>2</ns>
    <id>486391</id>
    <revision>
      <id>4676515</id>
      <timestamp>2026-10-17T13:00:07Z</timestamp>
      <contributor>
        <username>Sarolang</username>
        <id>3628609</id>
      </contributor>
      <comment>/* */</comment>
      <origin>4676515</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2" sha1="he0da0q8s1r2umjl1vwjjxep15c52yo" xml:space="preserve">Hi</text>
      <sha1>he0da0q8s1r2umjl1vwjjxep15c52yo</sha1>
    </revision>
    <revision>
      <id>4676516</id>
      <parentid>4676515</parentid>
      <timestamp>2026-10-17T13:02:39Z</timestamp>
      <contributor>
        <username>Sarolang</username>
        <id>3628609</id>
      </contributor>
      <origin>4676516</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="84" sha1="9j3kmdz3yi4jqcsudn5hcrvqi0mf4xy" xml:space="preserve">[[The Revised Dictionary of Judeo‑Malay.|The Revised Dictionary of Judeo‑Malay]]</text>
      <sha1>9j3kmdz3yi4jqcsudn5hcrvqi0mf4xy</sha1>
    </revision>
    <revision>
      <id>4676548</id>
      <parentid>4676516</parentid>
      <timestamp>2026-10-17T15:21:30Z</timestamp>
      <contributor>
        <username>Sarolang</username>
        <id>3628609</id>
      </contributor>
      <comment>/* */</comment>
      <origin>4676548</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="0" sha1="phoiac9h4m842xq45sp7s6u21eteeq1" />
      <sha1>phoiac9h4m842xq45sp7s6u21eteeq1</sha1>
    </revision>
    <revision>
      <id>4676565</id>
      <parentid>4676548</parentid>
      <timestamp>2026-10-17T17:49:56Z</timestamp>
      <contributor>
        <username>Sarolang</username>
        <id>3628609</id>
      </contributor>
      <comment>/* */</comment>
      <origin>4676565</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="97" sha1="49r253wvxipksa4gxx056zzbezee0n4" xml:space="preserve">[[Malay to Judeo-Malay Complete Dictionary|Malay-Judeo-Malay-Bazaar Malay : Complete Dictionary]]</text>
      <sha1>49r253wvxipksa4gxx056zzbezee0n4</sha1>
    </revision>
    <revision>
      <id>4676710</id>
      <parentid>4676565</parentid>
      <timestamp>2026-10-18T08:53:39Z</timestamp>
      <contributor>
        <username>Sarolang</username>
        <id>3628609</id>
      </contributor>
      <comment>/* */</comment>
      <origin>4676710</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="95" sha1="migw5bz12l3q6j4uopkbwbo7k744375" xml:space="preserve">Judeo-Malay Revised Phrasebook And Dictionary [[Judeo-Malay Revised Phrasebook And Dictionary]]</text>
      <sha1>migw5bz12l3q6j4uopkbwbo7k744375</sha1>
    </revision>
    <revision>
      <id>4676711</id>
      <parentid>4676710</parentid>
      <timestamp>2026-10-18T08:58:12Z</timestamp>
      <contributor>
        <username>Sarolang</username>
        <id>3628609</id>
      </contributor>
      <comment>/* */</comment>
      <origin>4676711</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="80" sha1="1s5j33mmtk9ibr2n1l41qu51xvl9h0b" xml:space="preserve">Judeo-Malay Revised Phrasebook And Dictionary [[Judeo-Malay Revised Dictionary]]</text>
      <sha1>1s5j33mmtk9ibr2n1l41qu51xvl9h0b</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:~2026-55681-78</title>
    <ns>3</ns>
    <id>486392</id>
    <revision>
      <id>4676524</id>
      <timestamp>2026-10-17T13:41:59Z</timestamp>
      <contributor>
        <username>MathXplore</username>
        <id>3097823</id>
      </contributor>
      <comment>Notifying author of speedy deletion nomination</comment>
      <origin>4676524</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="832" sha1="hnbijfhpjwz2pujxcqxiqsok9qiqixy" xml:space="preserve">
== I have added a tag to a page you created ==
Hi! I'm MathXplore, and I recently reviewed your page, [[:NEIN Csupo]]. I have added a tag to the page, because it &lt;strong&gt;may meet the [[Wikibooks:Deletion policy#Speedy deletions|criteria for speedy deletion]].&lt;/strong&gt; This means that it can be deleted at any time.  If you believe that your page should not be deleted, please post a message on [[Talk:NEIN Csupo|the page's talk page]] explaining why. &lt;strong&gt;If your reasoning is convincing, your page may be saved.&lt;/strong&gt; If you have any questions or concerns, please [[User talk:MathXplore|let me know]]. Thank you! &lt;!-- Substituted from User:JJPMaster/CurateThisPage/authorMsg --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 13:41, 17 October 2026 (UTC)</text>
      <sha1>hnbijfhpjwz2pujxcqxiqsok9qiqixy</sha1>
    </revision>
    <revision>
      <id>4676526</id>
      <parentid>4676524</parentid>
      <timestamp>2026-10-17T13:42:19Z</timestamp>
      <contributor>
        <username>MathXplore</username>
        <id>3097823</id>
      </contributor>
      <comment>Notifying author of speedy deletion nomination</comment>
      <origin>4676526</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1668" sha1="hpsg1oxeie0t0f3lgchbk8zuwv3toca" xml:space="preserve">
== I have added a tag to a page you created ==
Hi! I'm MathXplore, and I recently reviewed your page, [[:NEIN Csupo]]. I have added a tag to the page, because it &lt;strong&gt;may meet the [[Wikibooks:Deletion policy#Speedy deletions|criteria for speedy deletion]].&lt;/strong&gt; This means that it can be deleted at any time.  If you believe that your page should not be deleted, please post a message on [[Talk:NEIN Csupo|the page's talk page]] explaining why. &lt;strong&gt;If your reasoning is convincing, your page may be saved.&lt;/strong&gt; If you have any questions or concerns, please [[User talk:MathXplore|let me know]]. Thank you! &lt;!-- Substituted from User:JJPMaster/CurateThisPage/authorMsg --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 13:41, 17 October 2026 (UTC)
== I have added a tag to a page you created ==
Hi! I'm MathXplore, and I recently reviewed your page, [[:Klasky Csupo]]. I have added a tag to the page, because it &lt;strong&gt;may meet the [[Wikibooks:Deletion policy#Speedy deletions|criteria for speedy deletion]].&lt;/strong&gt; This means that it can be deleted at any time.  If you believe that your page should not be deleted, please post a message on [[Talk:Klasky Csupo|the page's talk page]] explaining why. &lt;strong&gt;If your reasoning is convincing, your page may be saved.&lt;/strong&gt; If you have any questions or concerns, please [[User talk:MathXplore|let me know]]. Thank you! &lt;!-- Substituted from User:JJPMaster/CurateThisPage/authorMsg --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 13:42, 17 October 2026 (UTC)</text>
      <sha1>hpsg1oxeie0t0f3lgchbk8zuwv3toca</sha1>
    </revision>
  </page>
  <page>
    <title>The Revised Dictionary of Judeo‑Malay.</title>
    <ns>0</ns>
    <id>486393</id>
    <revision>
      <id>4676531</id>
      <timestamp>2026-10-17T14:25:58Z</timestamp>
      <contributor>
        <username>Sarolang</username>
        <id>3628609</id>
      </contributor>
      <comment>Created page with &quot;===Foreword===   This revised lexicon gathers surviving words, phrases and usage notes from the historical Judeo‑Malay speech‑variety once spoken by the small Jewish community of Penang. Judeo‑Malay was never a fully separate language; it was a distinct local form of Malay enriched with selected Hebrew and Aramaic terms, used mostly in everyday conversation within the community from the late‑19th to mid‑20th century.   Most original oral speakers have passe...&quot;</comment>
      <origin>4676531</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1440" sha1="so0ne940qrxzhbnkw9ggctd4dacltxy" xml:space="preserve">===Foreword===
 
This revised lexicon gathers surviving words, phrases and usage notes from the historical Judeo‑Malay speech‑variety once spoken by the small Jewish community of Penang. Judeo‑Malay was never a fully separate language; it was a distinct local form of Malay enriched with selected Hebrew and Aramaic terms, used mostly in everyday conversation within the community from the late‑19th to mid‑20th century.
 
Most original oral speakers have passed away, leaving only scattered handwritten notes, old letters and brief published records behind. This work revises and arranges those surviving materials, not to invent new vocabulary, but to preserve what can still be recovered. It also notes how this speech‑form existed alongside ordinary Malay, Baghdadi‑Arabic and English in Penang’s old multicultural neighbourhoods.
 
This dictionary does not claim to be a complete historical record — many expressions were never written down and are now lost. Instead, it serves as a starting‑point for anyone interested in the little‑known linguistic heritage of Penang’s former Jewish community.

To foster the spirit of tolerance and inter‑faith solidarity, the author has prepared this book so that this unique language is not forgotten by present‑day society.

[[Image:Judeo-Malay Numbers written in Hebrew.jpg|frame|left|One of the few surviving manuscripts of Judeo-Malay language.]]

==א==</text>
      <sha1>so0ne940qrxzhbnkw9ggctd4dacltxy</sha1>
    </revision>
    <revision>
      <id>4676536</id>
      <parentid>4676531</parentid>
      <timestamp>2026-10-17T14:37:15Z</timestamp>
      <contributor>
        <username>Sarolang</username>
        <id>3628609</id>
      </contributor>
      <comment>/* א */</comment>
      <origin>4676536</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1489" sha1="2h2pn0xkjpn8jypt4zlo29ur6eydxez" xml:space="preserve">===Foreword===
 
This revised lexicon gathers surviving words, phrases and usage notes from the historical Judeo‑Malay speech‑variety once spoken by the small Jewish community of Penang. Judeo‑Malay was never a fully separate language; it was a distinct local form of Malay enriched with selected Hebrew and Aramaic terms, used mostly in everyday conversation within the community from the late‑19th to mid‑20th century.
 
Most original oral speakers have passed away, leaving only scattered handwritten notes, old letters and brief published records behind. This work revises and arranges those surviving materials, not to invent new vocabulary, but to preserve what can still be recovered. It also notes how this speech‑form existed alongside ordinary Malay, Baghdadi‑Arabic and English in Penang’s old multicultural neighbourhoods.
 
This dictionary does not claim to be a complete historical record — many expressions were never written down and are now lost. Instead, it serves as a starting‑point for anyone interested in the little‑known linguistic heritage of Penang’s former Jewish community.

To foster the spirit of tolerance and inter‑faith solidarity, the author has prepared this book so that this unique language is not forgotten by present‑day society.

[[Image:Judeo-Malay Numbers written in Hebrew.jpg|frame|left|One of the few surviving manuscripts of Judeo-Malay language.]]

==א==
א= The first letter of Judeo-Malay alphabet.
א</text>
      <sha1>2h2pn0xkjpn8jypt4zlo29ur6eydxez</sha1>
    </revision>
    <revision>
      <id>4676559</id>
      <parentid>4676536</parentid>
      <timestamp>2026-10-17T16:44:19Z</timestamp>
      <contributor>
        <username>Kittycataclysm</username>
        <id>3371989</id>
      </contributor>
      <comment>query scope</comment>
      <origin>4676559</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1569" sha1="bfj1sehhluinn87k2mmpqiztnpqprfx" xml:space="preserve">{{Qr-scope|reason=WB specifically does not allow dictionaries per [[WB:WIW]]}}

===Foreword===
 
This revised lexicon gathers surviving words, phrases and usage notes from the historical Judeo‑Malay speech‑variety once spoken by the small Jewish community of Penang. Judeo‑Malay was never a fully separate language; it was a distinct local form of Malay enriched with selected Hebrew and Aramaic terms, used mostly in everyday conversation within the community from the late‑19th to mid‑20th century.
 
Most original oral speakers have passed away, leaving only scattered handwritten notes, old letters and brief published records behind. This work revises and arranges those surviving materials, not to invent new vocabulary, but to preserve what can still be recovered. It also notes how this speech‑form existed alongside ordinary Malay, Baghdadi‑Arabic and English in Penang’s old multicultural neighbourhoods.
 
This dictionary does not claim to be a complete historical record — many expressions were never written down and are now lost. Instead, it serves as a starting‑point for anyone interested in the little‑known linguistic heritage of Penang’s former Jewish community.

To foster the spirit of tolerance and inter‑faith solidarity, the author has prepared this book so that this unique language is not forgotten by present‑day society.

[[Image:Judeo-Malay Numbers written in Hebrew.jpg|frame|left|One of the few surviving manuscripts of Judeo-Malay language.]]

==א==
א= The first letter of Judeo-Malay alphabet.
א</text>
      <sha1>bfj1sehhluinn87k2mmpqiztnpqprfx</sha1>
    </revision>
  </page>
  <page>
    <title>About Monsters And Angels/Introduction</title>
    <ns>0</ns>
    <id>486395</id>
    <revision>
      <id>4676542</id>
      <timestamp>2026-10-17T15:11:44Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <comment>Created page with &quot;== Introduction To Monsters == '''Types of monsters:'''  1. Undead And Spirits: &lt;br&gt; - Vampires: Immoral, fanged, undead human-like creatures that feed on blood. (Examples: Dracula, Strigoi).   &lt;br&gt; - Zombies: Reanimated, or cursed corpses with a strong hunger for flesh. &lt;br&gt; - Ghosts And Specters: Disembodies souls or spirits that haunt the living. &lt;br&gt; &lt;br&gt; 2. Human-Animal Hybrids And Shapeshifters: &lt;br&gt; - Werewolves And Therianthropes: Humans that transform into beast...&quot;</comment>
      <origin>4676542</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2130" sha1="lefwjk97ya8m41z87iyeg5npvaxsiol" xml:space="preserve">== Introduction To Monsters ==
'''Types of monsters:'''

1. Undead And Spirits: &lt;br&gt;
- Vampires: Immoral, fanged, undead human-like creatures that feed on blood. (Examples: Dracula, Strigoi).   &lt;br&gt;
- Zombies: Reanimated, or cursed corpses with a strong hunger for flesh. &lt;br&gt;
- Ghosts And Specters: Disembodies souls or spirits that haunt the living. &lt;br&gt;
&lt;br&gt;
2. Human-Animal Hybrids And Shapeshifters: &lt;br&gt;
- Werewolves And Therianthropes: Humans that transform into beasts during a full moon. &lt;br&gt;
- Mythological Hybrids: Creatures combining human and animal characteristics (Example: Centaurs, Mermaids, Sirens) &lt;br&gt;
- Yokai And Folklore Spirits: Japanese and Asian phantoms and shapeshifters. &lt;br&gt;
&lt;br&gt;
3. Giants, Ogres And Humanoids: &lt;br&gt;
- Giants And Cyclopes: Massive human-like creatures found in mythology. (Example: Cyclops) &lt;br&gt;
- Goblins, Trolls And Gnomes: Mischievous, tiny or mid-sized humanoids found in the woodlands. (Example: Trolls) &lt;br&gt;
- Ogres And Man-Eaters: Large, savage humanoids known for eating people. &lt;br&gt;
&lt;br&gt;
4. Beasts, Dragons And Sea Monsters: &lt;br&gt;
- Dragons And Serpents: Reptilian, fire-breathing, or flying giant beasts. Found mainly in Western and Eastern traditions. &lt;br&gt;
- Water And Lake Monsters: Aquatic creatures lurking in deep waters. (Example: Loch Ness Monster). &lt;br&gt;
- Cryptids: Modern mythical animals reported by witnesses. (Example: Bigfoot, Chupacabra). &lt;br&gt;
&lt;br&gt;
5. Demons, Fiends And Cosmic Entities: &lt;br&gt;
- Demons And Devils: Malevolent spiritual or underworld forces. &lt;br&gt;
- Lovecraftian / Tabletop Classifications: Systematic categories used in fantasy games like Dungeons &amp; Dragons. &lt;br&gt;
&lt;br&gt;
Historically, a monster was something shown to people in order to teach them a lesson, or to signal danger, or to reveal a moral truth. &lt;br&gt;
&lt;br&gt;
Monsters emerge from specific historical and social moments. &lt;br&gt;
&lt;br&gt;
Monsters also emerge from individuals who are processing their trauma, or from people seeking to handle their physical or mental illnesses. &lt;br&gt;

Many academic fields analyze monsters, such as Anthropology, Literature, Media Studies, Psychology, and Sociology.</text>
      <sha1>lefwjk97ya8m41z87iyeg5npvaxsiol</sha1>
    </revision>
    <revision>
      <id>4676545</id>
      <parentid>4676542</parentid>
      <timestamp>2026-10-17T15:17:29Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <origin>4676545</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2222" sha1="n5axo2opspewn7dd6zy5ljby84c1i7v" xml:space="preserve">== Introduction To Monsters ==
'''Types of monsters:'''

1. Undead And Spirits: &lt;br&gt;
- Vampires: Immoral, fanged, undead human-like creatures that feed on blood. (Examples: Dracula, Strigoi).   &lt;br&gt;
- Zombies: Reanimated, or cursed corpses with a strong hunger for flesh. &lt;br&gt;
- Ghosts And Specters: Disembodies souls or spirits that haunt the living. &lt;br&gt;
&lt;br&gt;
2. Human-Animal Hybrids And Shapeshifters: &lt;br&gt;
- Werewolves And Therianthropes: Humans that transform into beasts during a full moon. &lt;br&gt;
- Mythological Hybrids: Creatures combining human and animal characteristics (Example: Centaurs, Mermaids, Sirens) &lt;br&gt;
- Yokai And Folklore Spirits: Japanese and Asian phantoms and shapeshifters. &lt;br&gt;
&lt;br&gt;
3. Giants, Ogres And Humanoids: &lt;br&gt;
- Giants And Cyclopes: Massive human-like creatures found in mythology. (Example: Cyclops) &lt;br&gt;
- Goblins, Trolls And Gnomes: Mischievous, tiny or mid-sized humanoids found in the woodlands. (Example: Trolls) &lt;br&gt;
- Ogres And Man-Eaters: Large, savage humanoids known for eating people. &lt;br&gt;
&lt;br&gt;
4. Beasts, Dragons And Sea Monsters: &lt;br&gt;
- Dragons And Serpents: Reptilian, fire-breathing, or flying giant beasts. Found mainly in Western and Eastern traditions. &lt;br&gt;
- Water And Lake Monsters: Aquatic creatures lurking in deep waters. (Example: Loch Ness Monster). &lt;br&gt;
- Cryptids: Modern mythical animals reported by witnesses. (Example: Bigfoot, Chupacabra). &lt;br&gt;
&lt;br&gt;
5. Demons, Fiends And Cosmic Entities: &lt;br&gt;
- Demons And Devils: Malevolent spiritual or underworld forces. &lt;br&gt;
- Lovecraftian / Tabletop Classifications: Systematic categories used in fantasy games like Dungeons &amp; Dragons. &lt;br&gt;
&lt;br&gt;
Historically, a monster was something shown to people in order to teach them a lesson, or to signal danger, or to reveal a moral truth. &lt;br&gt;
&lt;br&gt;
Monsters emerge from specific historical and social moments. &lt;br&gt;
&lt;br&gt;
Monsters also emerge from individuals who are processing their trauma, or from people seeking to handle their physical or mental illnesses. &lt;br&gt;

Many academic fields analyze monsters, such as Anthropology, Literature, Media Studies, Psychology, and Sociology. &lt;br&gt;
&lt;br&gt;
&lt;noinclude&gt;{{Chapter navigation with TOC||Chapter One|TOC mini}}&lt;/noinclude&gt;
&lt;br&gt;</text>
      <sha1>n5axo2opspewn7dd6zy5ljby84c1i7v</sha1>
    </revision>
  </page>
  <page>
    <title>Transwiki:JJPMaster/CascadingImportation</title>
    <ns>108</ns>
    <id>486397</id>
    <revision>
      <id>4676585</id>
      <timestamp>2024-12-18T11:01:58Z</timestamp>
      <contributor>
        <username>w&gt;JJPMaster</username>
        <id>0</id>
      </contributor>
      <comment>for enwikibooks use</comment>
      <origin>4676585</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="324" sha1="ms23d2y0b6p74tyi7tr248am043u3rq" xml:space="preserve">This page contains a bunch of templates that I will import ''en masse'' to the English Wikibooks by importing &quot;[[w:User:JJPMaster/CascadingImportation]]&quot; with &quot;Import all templates and transcluded pages&quot; enabled.
{{User js-0}}
{{User js-1}}
{{User js-2}}
{{User js-3}}
{{User js-4}}
{{User js-5}}
{{User js-N}}
{{User js-1}}</text>
      <sha1>ms23d2y0b6p74tyi7tr248am043u3rq</sha1>
    </revision>
    <revision>
      <id>4676586</id>
      <parentid>4676585</parentid>
      <timestamp>2024-12-19T05:41:55Z</timestamp>
      <contributor>
        <username>w&gt;JJPMaster</username>
        <id>0</id>
      </contributor>
      <comment>next batch</comment>
      <origin>4676586</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="508" sha1="etgomxyks1bz9vig9dx8e3xiefpz5ai" xml:space="preserve">This page contains a bunch of templates that I will import ''en masse'' to the English Wikibooks by importing &quot;[[w:User:JJPMaster/CascadingImportation]]&quot; with &quot;Import all templates and transcluded pages&quot; enabled.
{{#invoke:Lockbox|lock|:Code page 668|:Code page 708|:Code page 720|:Code page 770|:Code page 773|:Code page 775|:Code page 776|:Code page 777|:Code page 778|:Code page 851|:Code page 852|:Code page 853|:Code page 855|:Code page 856|:Code page 857|:Code page 859|:Code page 860|:Code page 1169}}</text>
      <sha1>etgomxyks1bz9vig9dx8e3xiefpz5ai</sha1>
    </revision>
    <revision>
      <id>4676587</id>
      <parentid>4676586</parentid>
      <timestamp>2024-12-19T10:59:03Z</timestamp>
      <contributor>
        <username>w&gt;JJPMaster</username>
        <id>0</id>
      </contributor>
      <comment>let's try again</comment>
      <origin>4676587</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="492" sha1="b60h6c4sh9y4vl8ak9mkvo30z3vqxwj" xml:space="preserve">This page contains a bunch of templates that I will import ''en masse'' to the English Wikibooks by importing &quot;[[w:User:JJPMaster/CascadingImportation]]&quot; with &quot;Import all templates and transcluded pages&quot; enabled.
{{#invoke:Lockbox|lock|:Code page 668|:Code page 708|:Code page 720|:Code page 770|:Code page 773|:Code page 775|:Code page 776|:Code page 777|:Code page 778|:Code page 851|:Code page 852|:Code page 853|:Code page 855|:Code page 856|:Code page 857|:Code page 859|:Code page 860}}</text>
      <sha1>b60h6c4sh9y4vl8ak9mkvo30z3vqxwj</sha1>
    </revision>
    <revision>
      <id>4676588</id>
      <parentid>4676587</parentid>
      <timestamp>2024-12-22T18:19:45Z</timestamp>
      <contributor>
        <username>w&gt;JJPMaster</username>
        <id>0</id>
      </contributor>
      <comment>test</comment>
      <origin>4676588</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="248" sha1="9tdrunj5h3qe7nwu89mtsxbfww182jd" xml:space="preserve">This page contains a bunch of templates that I will import ''en masse'' to the English Wikibooks by importing &quot;[[w:User:JJPMaster/CascadingImportation]]&quot; with &quot;Import all templates and transcluded pages&quot; enabled.
{{#invoke:Lockbox|lock|RM_created}}</text>
      <sha1>9tdrunj5h3qe7nwu89mtsxbfww182jd</sha1>
    </revision>
    <revision>
      <id>4676589</id>
      <parentid>4676588</parentid>
      <timestamp>2024-12-22T18:20:27Z</timestamp>
      <contributor>
        <username>w&gt;JJPMaster</username>
        <id>0</id>
      </contributor>
      <comment>test2</comment>
      <origin>4676589</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="263" sha1="ohw0v9m4ih4am0nn3zahuqeuybzipra" xml:space="preserve">This page contains a bunch of templates that I will import ''en masse'' to the English Wikibooks by importing &quot;[[w:User:JJPMaster/CascadingImportation]]&quot; with &quot;Import all templates and transcluded pages&quot; enabled.
{{#invoke:Lockbox|lock|RM_created}}
{{RM created}}</text>
      <sha1>ohw0v9m4ih4am0nn3zahuqeuybzipra</sha1>
    </revision>
    <revision>
      <id>4676590</id>
      <parentid>4676589</parentid>
      <timestamp>2024-12-22T18:26:01Z</timestamp>
      <contributor>
        <username>w&gt;JJPMaster</username>
        <id>0</id>
      </contributor>
      <comment>next batch</comment>
      <origin>4676590</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="413" sha1="ndc63eq6k4liryqm43mqfojvyux24pq" xml:space="preserve">This page contains a bunch of templates that I will import ''en masse'' to the English Wikibooks by importing &quot;[[w:User:JJPMaster/CascadingImportation]]&quot; with &quot;Import all templates and transcluded pages&quot; enabled.
* [[Template:Not a bug]]
* [[Template:Won't fix]]
* [[Template:Not fixed]]
* [[Template:Withdrawn]]
* [[Template:PImplemented]]
* [[Template:Technically indistinguishable]]
* [[Template:Works for me]]</text>
      <sha1>ndc63eq6k4liryqm43mqfojvyux24pq</sha1>
    </revision>
    <revision>
      <id>4676591</id>
      <parentid>4676590</parentid>
      <timestamp>2024-12-22T18:26:52Z</timestamp>
      <contributor>
        <username>w&gt;JJPMaster</username>
        <id>0</id>
      </contributor>
      <comment>use traditional means</comment>
      <origin>4676591</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="333" sha1="0fepy8ve1szhmzvutkqh7lz64g0tk8x" xml:space="preserve">This page contains a bunch of templates that I will import ''en masse'' to the English Wikibooks by importing &quot;[[w:User:JJPMaster/CascadingImportation]]&quot; with &quot;Import all templates and transcluded pages&quot; enabled.
{{#invoke:Lockbox|lock|Not a bug|Won't fix|Not fixed|Withdrawn|PImplemented|Technically indistinguishable|Works for me}}</text>
      <sha1>0fepy8ve1szhmzvutkqh7lz64g0tk8x</sha1>
    </revision>
    <revision>
      <id>4676592</id>
      <parentid>4676591</parentid>
      <timestamp>2024-12-22T19:13:07Z</timestamp>
      <contributor>
        <username>w&gt;JJPMaster</username>
        <id>0</id>
      </contributor>
      <comment>next batch</comment>
      <origin>4676592</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="301" sha1="ltjad2wkb9mgyb4ceqgm2ckr3aghvl1" xml:space="preserve">This page contains a bunch of templates that I will import ''en masse'' to the English Wikibooks by importing &quot;[[w:User:JJPMaster/CascadingImportation]]&quot; with &quot;Import all templates and transcluded pages&quot; enabled.
{{#invoke:Lockbox|lock|Spaced_en_dash|Em dash|Soft hyphen|Blockquote|Quote frame|Humor}}</text>
      <sha1>ltjad2wkb9mgyb4ceqgm2ckr3aghvl1</sha1>
    </revision>
    <revision>
      <id>4676593</id>
      <parentid>4676592</parentid>
      <timestamp>2024-12-29T23:42:49Z</timestamp>
      <contributor>
        <username>w&gt;JJPMaster</username>
        <id>0</id>
      </contributor>
      <comment>next batch</comment>
      <origin>4676593</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="518" sha1="rvc3al6cyhcjpbki5nkwm3ydp2mh2y5" xml:space="preserve">This page contains a bunch of templates that I will import ''en masse'' to the English Wikibooks by importing &quot;[[w:User:JJPMaster/CascadingImportation]]&quot; with &quot;Import all templates and transcluded pages&quot; enabled.

Today's theme: &lt;strong&gt;LGBTQ userboxes&lt;/strong&gt;

{{#invoke:Lockbox|lock|User LGBTQ|User:UBX/lesbian|User:UBX/queer|User:UBX/bisexual|User:UBX/pansexual|User:UBX/asexual|User:UBX/gay|User:UBX/Aromantic|User:EurovisionAndXenomorphs/Userboxes/user-transgender-flag|User Nonbinary flag|User:UBX/genderqueer}}</text>
      <sha1>rvc3al6cyhcjpbki5nkwm3ydp2mh2y5</sha1>
    </revision>
    <revision>
      <id>4676594</id>
      <parentid>4676593</parentid>
      <timestamp>2025-05-24T00:07:05Z</timestamp>
      <contributor>
        <username>w&gt;JJPMaster</username>
        <id>0</id>
      </contributor>
      <comment>next batch</comment>
      <origin>4676594</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="373" sha1="tcnz90nrf0p9peaff5nwkqg8cyyvv25" xml:space="preserve">This page contains a bunch of templates that I will import ''en masse'' to the English Wikibooks by importing &quot;[[w:User:JJPMaster/CascadingImportation]]&quot; with &quot;Import all templates and transcluded pages&quot; enabled.

Today's theme: &lt;strong&gt;Section transclusion modules&lt;/strong&gt;

{{#invoke:Lockbox|lock|Module:Transcluder|Module:Excerpt|Module:Excerpt/config|Template:Excerpt}}</text>
      <sha1>tcnz90nrf0p9peaff5nwkqg8cyyvv25</sha1>
    </revision>
    <revision>
      <id>4676595</id>
      <parentid>4676594</parentid>
      <timestamp>2026-02-28T12:18:54Z</timestamp>
      <contributor>
        <username>w&gt;Primefac</username>
        <id>0</id>
      </contributor>
      <comment>rmv module being deleted</comment>
      <origin>4676595</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="354" sha1="ki63ys3j7mcsqvxln6qokfkiu1wsmx6" xml:space="preserve">This page contains a bunch of templates that I will import ''en masse'' to the English Wikibooks by importing &quot;[[w:User:JJPMaster/CascadingImportation]]&quot; with &quot;Import all templates and transcluded pages&quot; enabled.

Today's theme: &lt;strong&gt;Section transclusion modules&lt;/strong&gt;

{{#invoke:Lockbox|lock|Module:Excerpt|Module:Excerpt/config|Template:Excerpt}}</text>
      <sha1>ki63ys3j7mcsqvxln6qokfkiu1wsmx6</sha1>
    </revision>
    <revision>
      <id>4676596</id>
      <parentid>4676595</parentid>
      <timestamp>2026-10-18T02:48:43Z</timestamp>
      <contributor>
        <username>w&gt;JJPMaster</username>
        <id>0</id>
      </contributor>
      <origin>4676596</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="394" sha1="99t5rpjxe2yf2237n5ojmr32zxp6u4e" xml:space="preserve">This page contains a bunch of templates that I will import ''en masse'' to the English Wikibooks by importing &quot;[[w:User:JJPMaster/CascadingImportation]]&quot; with &quot;Import all templates and transcluded pages&quot; enabled.

Today's theme: &lt;strong&gt;Hidden archive templates&lt;/strong&gt;

{{#invoke:Lockbox|lock|Template:Hidden archive top|Template:Hidden archive bottom|Template:Hidden archive top/styles.css}}</text>
      <sha1>99t5rpjxe2yf2237n5ojmr32zxp6u4e</sha1>
    </revision>
    <revision>
      <id>4676597</id>
      <parentid>4676596</parentid>
      <timestamp>2026-10-18T02:49:00Z</timestamp>
      <contributor>
        <username>JJPMaster</username>
        <id>3095725</id>
      </contributor>
      <minor />
      <comment>12 revisions imported from [[:w:User:JJPMaster/CascadingImportation]]: Mass-importing pages: utility templates</comment>
      <origin>4676596</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="394" sha1="99t5rpjxe2yf2237n5ojmr32zxp6u4e" xml:space="preserve">This page contains a bunch of templates that I will import ''en masse'' to the English Wikibooks by importing &quot;[[w:User:JJPMaster/CascadingImportation]]&quot; with &quot;Import all templates and transcluded pages&quot; enabled.

Today's theme: &lt;strong&gt;Hidden archive templates&lt;/strong&gt;

{{#invoke:Lockbox|lock|Template:Hidden archive top|Template:Hidden archive bottom|Template:Hidden archive top/styles.css}}</text>
      <sha1>99t5rpjxe2yf2237n5ojmr32zxp6u4e</sha1>
    </revision>
  </page>
  <page>
    <title>Transwiki:Hidden archive bottom</title>
    <ns>108</ns>
    <id>486398</id>
    <revision>
      <id>4676598</id>
      <timestamp>2007-01-10T03:36:45Z</timestamp>
      <contributor>
        <username>w&gt;Samuel Blanning</username>
        <id>0</id>
      </contributor>
      <comment>creating</comment>
      <origin>4676598</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="421" sha1="npo27jdio8rqnecczvoa6n5sx5q2zzd" xml:space="preserve">|}

&lt;noinclude&gt;

Shortcut: {{tl|hab}}. A generic version of the template used to archive [[Wikipedia:Deletion review]] discussions. Used with [[Template:Hidden archive top]] (shortcut {{tl|hat}}), can be used to close a discussion and discourage further editing without removing it completely from the page.

The entire active content of this template is actually just '|}'.

[[Category:Archival templates]]

&lt;/noinclude&gt;</text>
      <sha1>npo27jdio8rqnecczvoa6n5sx5q2zzd</sha1>
    </revision>
    <revision>
      <id>4676599</id>
      <parentid>4676598</parentid>
      <timestamp>2007-01-16T00:29:59Z</timestamp>
      <contributor>
        <username>w&gt;Ryulong</username>
        <id>0</id>
      </contributor>
      <minor />
      <origin>4676599</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="419" sha1="o3gb3i2uvbks3vl5vck402p2spq7h0d" xml:space="preserve">|}&lt;noinclude&gt;

Shortcut: {{tl|hab}}. A generic version of the template used to archive [[Wikipedia:Deletion review]] discussions. Used with [[Template:Hidden archive top]] (shortcut {{tl|hat}}), can be used to close a discussion and discourage further editing without removing it completely from the page.

The entire active content of this template is actually just '|}'.

[[Category:Archival templates]]

&lt;/noinclude&gt;</text>
      <sha1>o3gb3i2uvbks3vl5vck402p2spq7h0d</sha1>
    </revision>
    <revision>
      <id>4676600</id>
      <parentid>4676599</parentid>
      <timestamp>2007-01-27T04:46:15Z</timestamp>
      <contributor>
        <username>w&gt;Trialsanderrors</username>
        <id>0</id>
      </contributor>
      <minor />
      <comment>Cat</comment>
      <origin>4676600</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="435" sha1="7139sp5osdkmu0oli9gt1aboevwv3wn" xml:space="preserve">|}&lt;noinclude&gt;

Shortcut: {{tl|hab}}. A generic version of the template used to archive [[Wikipedia:Deletion review]] discussions. Used with [[Template:Hidden archive top]] (shortcut {{tl|hat}}), can be used to close a discussion and discourage further editing without removing it completely from the page.

The entire active content of this template is actually just '|}'.

[[Category:Archival templates|Hidden Archiveb]]

&lt;/noinclude&gt;</text>
      <sha1>7139sp5osdkmu0oli9gt1aboevwv3wn</sha1>
    </revision>
    <revision>
      <id>4676601</id>
      <parentid>4676600</parentid>
      <timestamp>2007-12-26T21:46:47Z</timestamp>
      <contributor>
        <username>w&gt;Nmajdan</username>
        <id>0</id>
      </contributor>
      <minor />
      <comment>insert hidden template name identifier</comment>
      <origin>4676601</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="487" sha1="2a9b8br45p20tqi054q27t4gp50ubuo" xml:space="preserve">&lt;includeonly&gt;&lt;!-- [[Template:hab]] --&gt;&lt;/includeonly&gt;|}&lt;noinclude&gt;

Shortcut: {{tl|hab}}. A generic version of the template used to archive [[Wikipedia:Deletion review]] discussions. Used with [[Template:Hidden archive top]] (shortcut {{tl|hat}}), can be used to close a discussion and discourage further editing without removing it completely from the page.

The entire active content of this template is actually just '|}'.

[[Category:Archival templates|Hidden Archiveb]]

&lt;/noinclude&gt;</text>
      <sha1>2a9b8br45p20tqi054q27t4gp50ubuo</sha1>
    </revision>
    <revision>
      <id>4676602</id>
      <parentid>4676601</parentid>
      <timestamp>2008-08-27T04:18:04Z</timestamp>
      <contributor>
        <username>w&gt;Scientizzle</username>
        <id>0</id>
      </contributor>
      <minor />
      <comment>Protected Template:Hidden archive bottom: just in case... [edit=sysop:move=sysop]</comment>
      <origin>4676601</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="487" sha1="2a9b8br45p20tqi054q27t4gp50ubuo" xml:space="preserve">&lt;includeonly&gt;&lt;!-- [[Template:hab]] --&gt;&lt;/includeonly&gt;|}&lt;noinclude&gt;

Shortcut: {{tl|hab}}. A generic version of the template used to archive [[Wikipedia:Deletion review]] discussions. Used with [[Template:Hidden archive top]] (shortcut {{tl|hat}}), can be used to close a discussion and discourage further editing without removing it completely from the page.

The entire active content of this template is actually just '|}'.

[[Category:Archival templates|Hidden Archiveb]]

&lt;/noinclude&gt;</text>
      <sha1>2a9b8br45p20tqi054q27t4gp50ubuo</sha1>
    </revision>
    <revision>
      <id>4676603</id>
      <parentid>4676602</parentid>
      <timestamp>2009-04-17T00:16:31Z</timestamp>
      <contributor>
        <username>w&gt;Davidgothberg</username>
        <id>0</id>
      </contributor>
      <comment>Moving the documentation to a /doc page, since this is a protected page, so anyone can edit the doc, categories and interwikis.</comment>
      <origin>4676603</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="183" sha1="r992j0rsykqdgvdu3isjmfjz0qj8suc" xml:space="preserve">&lt;includeonly&gt;&lt;!-- [[Template:hab]] --&gt;&lt;/includeonly&gt;|}&lt;noinclude&gt;

{{pp-template}}
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>r992j0rsykqdgvdu3isjmfjz0qj8suc</sha1>
    </revision>
    <revision>
      <id>4676604</id>
      <parentid>4676603</parentid>
      <timestamp>2009-08-16T15:03:47Z</timestamp>
      <contributor>
        <username>w&gt;RockMFR</username>
        <id>0</id>
      </contributor>
      <comment>don't need this comment</comment>
      <origin>4676604</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="130" sha1="n6ayd255s6o5tq54ur3xrihqjvtvvo3" xml:space="preserve">|}&lt;noinclude&gt;
{{pp-template}}
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>n6ayd255s6o5tq54ur3xrihqjvtvvo3</sha1>
    </revision>
    <revision>
      <id>4676605</id>
      <parentid>4676604</parentid>
      <timestamp>2010-03-13T08:23:49Z</timestamp>
      <contributor>
        <username>w&gt;MSGJ</username>
        <id>0</id>
      </contributor>
      <comment>merged with [[Template:Collapse bottom]]</comment>
      <origin>4676605</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="54" sha1="lcfg90o2lgghktfor3rbmb8u5bf8vw6" xml:space="preserve">#REDIRECT[[Template:Collapse bottom]]
{{R from merge}}</text>
      <sha1>lcfg90o2lgghktfor3rbmb8u5bf8vw6</sha1>
    </revision>
    <revision>
      <id>4676606</id>
      <parentid>4676605</parentid>
      <timestamp>2011-04-05T12:42:34Z</timestamp>
      <contributor>
        <username>w&gt;Wifione</username>
        <id>0</id>
      </contributor>
      <comment>Undid revision 349577428 by [[Special:Contributions/MSGJ|MSGJ]] ([[User talk:MSGJ|talk]]) Kindly discuss this merge before taking it up</comment>
      <origin>4676606</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="130" sha1="n6ayd255s6o5tq54ur3xrihqjvtvvo3" xml:space="preserve">|}&lt;noinclude&gt;
{{pp-template}}
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>n6ayd255s6o5tq54ur3xrihqjvtvvo3</sha1>
    </revision>
    <revision>
      <id>4676607</id>
      <parentid>4676606</parentid>
      <timestamp>2014-09-03T07:01:27Z</timestamp>
      <contributor>
        <username>w&gt;Callanecc</username>
        <id>0</id>
      </contributor>
      <minor />
      <comment>Changed protection level of Template:Hidden archive bottom: [[WP:High-risk templates|Highly visible template]]: Over 6000 transclusions. Allowing template edits, standardise with [[Template:Hidden archive top]] ([Edit=Allow only template editors and admin</comment>
      <origin>4676606</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="130" sha1="n6ayd255s6o5tq54ur3xrihqjvtvvo3" xml:space="preserve">|}&lt;noinclude&gt;
{{pp-template}}
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>n6ayd255s6o5tq54ur3xrihqjvtvvo3</sha1>
    </revision>
    <revision>
      <id>4676608</id>
      <parentid>4676607</parentid>
      <timestamp>2015-02-16T02:02:13Z</timestamp>
      <contributor>
        <username>w&gt;Callanecc</username>
        <id>0</id>
      </contributor>
      <comment>Rm pp-template (duplicated in /doc)</comment>
      <origin>4676608</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="114" sha1="c6mkzr9jns5yx56vok584o84mrgqrls" xml:space="preserve">|}&lt;noinclude&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>c6mkzr9jns5yx56vok584o84mrgqrls</sha1>
    </revision>
    <revision>
      <id>4676609</id>
      <parentid>4676608</parentid>
      <timestamp>2021-02-28T03:10:35Z</timestamp>
      <contributor>
        <username>w&gt;MJL</username>
        <id>0</id>
      </contributor>
      <comment>Listed for merging with [[:Template:Collapse bottom]]; see [[:Wikipedia:Templates for discussion/Log/2021 February 28#Template:Collapse bottom]].</comment>
      <origin>4676609</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="353" sha1="ei5opqo8o5e7jag0wdgqqy5k6kjxpwd" xml:space="preserve">&lt;noinclude&gt;{{Tfm/dated|page=Hidden archive bottom|otherpage=Collapse bottom|link=Wikipedia:Templates for discussion/Log/2021 February 28#Template:Hidden archive bottom|help=off|bigbox={{#invoke:Noinclude|noinclude|text=yes}}}}&lt;/noinclude&gt;
|}&lt;noinclude&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>ei5opqo8o5e7jag0wdgqqy5k6kjxpwd</sha1>
    </revision>
    <revision>
      <id>4676610</id>
      <parentid>4676609</parentid>
      <timestamp>2021-03-08T17:56:40Z</timestamp>
      <contributor>
        <username>w&gt;Izno</username>
        <id>0</id>
      </contributor>
      <comment>[[Wikipedia:Templates for discussion/Log/2021 February 28#Template:Collapse bottom]] closed as keep ([[WP:XFDC#4.0.11|XFDcloser]])</comment>
      <origin>4676610</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="114" sha1="c6mkzr9jns5yx56vok584o84mrgqrls" xml:space="preserve">|}&lt;noinclude&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>c6mkzr9jns5yx56vok584o84mrgqrls</sha1>
    </revision>
    <revision>
      <id>4676611</id>
      <parentid>4676610</parentid>
      <timestamp>2026-10-18T02:49:01Z</timestamp>
      <contributor>
        <username>JJPMaster</username>
        <id>3095725</id>
      </contributor>
      <minor />
      <comment>13 revisions imported from [[:w:Template:Hidden_archive_bottom]]: Mass-importing pages: utility templates</comment>
      <origin>4676610</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="114" sha1="c6mkzr9jns5yx56vok584o84mrgqrls" xml:space="preserve">|}&lt;noinclude&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>c6mkzr9jns5yx56vok584o84mrgqrls</sha1>
    </revision>
  </page>
  <page>
    <title>Transwiki:Hidden archive top</title>
    <ns>108</ns>
    <id>486399</id>
    <revision>
      <id>4676612</id>
      <timestamp>2007-01-10T03:34:17Z</timestamp>
      <contributor>
        <username>w&gt;Samuel Blanning</username>
        <id>0</id>
      </contributor>
      <comment>creating</comment>
      <origin>4676612</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="965" sha1="elahu11fh4e9cionyhkdxxt1px098u9" xml:space="preserve">{| class=&quot;navbox collapsible collapsed&quot; style=&quot;text-align: left; border: 0px; margin-top: 0.2em;&quot;
|-
! style=&quot;background-color: #f2dfce;&quot; | {{{reason|This discussion has been archived.}}} Please do not modify it.
|-
| style=&quot;text-align:center;&quot; | ''The following is an archived debate. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;''
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: white;&quot; |

&lt;noinclude&gt;

|}
Shortcut: {{tl|hat}}. A generic version of the template used to archive [[Wikipedia:Deletion review]] discussions. Used with [[Template:Hidden archive bottom]] (shortcut {{tl|hab}}), can be used to close a discussion and discourage further editing without removing it completely from the page.

The reason for achiving can be changed with the &lt;code&gt;&lt;nowiki&gt;reason=&lt;/nowiki&gt;&lt;/code&gt; parameter which defaults to &quot;This discussion has been archived. Please do not modify it.&quot;

[[Category:Archival templates]]

&lt;/noinclude&gt;</text>
      <sha1>elahu11fh4e9cionyhkdxxt1px098u9</sha1>
    </revision>
    <revision>
      <id>4676613</id>
      <parentid>4676612</parentid>
      <timestamp>2007-01-27T04:45:45Z</timestamp>
      <contributor>
        <username>w&gt;Trialsanderrors</username>
        <id>0</id>
      </contributor>
      <minor />
      <comment>Cat</comment>
      <origin>4676613</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="980" sha1="ontubsslfac6bmgf5dt106pejdu8s78" xml:space="preserve">{| class=&quot;navbox collapsible collapsed&quot; style=&quot;text-align: left; border: 0px; margin-top: 0.2em;&quot;
|-
! style=&quot;background-color: #f2dfce;&quot; | {{{reason|This discussion has been archived.}}} Please do not modify it.
|-
| style=&quot;text-align:center;&quot; | ''The following is an archived debate. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;''
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: white;&quot; |

&lt;noinclude&gt;

|}
Shortcut: {{tl|hat}}. A generic version of the template used to archive [[Wikipedia:Deletion review]] discussions. Used with [[Template:Hidden archive bottom]] (shortcut {{tl|hab}}), can be used to close a discussion and discourage further editing without removing it completely from the page.

The reason for achiving can be changed with the &lt;code&gt;&lt;nowiki&gt;reason=&lt;/nowiki&gt;&lt;/code&gt; parameter which defaults to &quot;This discussion has been archived. Please do not modify it.&quot;

[[Category:Archival templates|Hidden Archive]]

&lt;/noinclude&gt;</text>
      <sha1>ontubsslfac6bmgf5dt106pejdu8s78</sha1>
    </revision>
    <revision>
      <id>4676614</id>
      <parentid>4676613</parentid>
      <timestamp>2007-01-27T14:23:35Z</timestamp>
      <contributor>
        <username>w&gt;Samuel Blanning</username>
        <id>0</id>
      </contributor>
      <comment>encompassing whole reason in variable</comment>
      <origin>4676614</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="980" sha1="6kua5lubbtn2txn2osibsv8er79pyw6" xml:space="preserve">{| class=&quot;navbox collapsible collapsed&quot; style=&quot;text-align: left; border: 0px; margin-top: 0.2em;&quot;
|-
! style=&quot;background-color: #f2dfce;&quot; | {{{reason|This discussion has been archived. Please do not modify it.}}}
|-
| style=&quot;text-align:center;&quot; | ''The following is an archived debate. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;''
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: white;&quot; |

&lt;noinclude&gt;

|}
Shortcut: {{tl|hat}}. A generic version of the template used to archive [[Wikipedia:Deletion review]] discussions. Used with [[Template:Hidden archive bottom]] (shortcut {{tl|hab}}), can be used to close a discussion and discourage further editing without removing it completely from the page.

The reason for achiving can be changed with the &lt;code&gt;&lt;nowiki&gt;reason=&lt;/nowiki&gt;&lt;/code&gt; parameter which defaults to &quot;This discussion has been archived. Please do not modify it.&quot;

[[Category:Archival templates|Hidden Archive]]

&lt;/noinclude&gt;</text>
      <sha1>6kua5lubbtn2txn2osibsv8er79pyw6</sha1>
    </revision>
    <revision>
      <id>4676615</id>
      <parentid>4676614</parentid>
      <timestamp>2007-02-17T03:49:46Z</timestamp>
      <contributor>
        <username>w&gt;NotJackhorkheimer</username>
        <id>0</id>
      </contributor>
      <minor />
      <origin>4676615</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="981" sha1="oalu52hqeoiwqtv8h8qntsohiry39gi" xml:space="preserve">{| class=&quot;navbox collapsible collapsed&quot; style=&quot;text-align: left; border: 0px; margin-top: 0.2em;&quot;
|-
! style=&quot;background-color: #f2dfce;&quot; | {{{reason|This discussion has been archived. Please do not modify it.}}}
|-
| style=&quot;text-align:center;&quot; | ''The following is an archived debate. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;''
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: white;&quot; |

&lt;noinclude&gt;

|}
Shortcut: {{tl|hat}}. A generic version of the template used to archive [[Wikipedia:Deletion review]] discussions. Used with [[Template:Hidden archive bottom]] (shortcut {{tl|hab}}), can be used to close a discussion and discourage further editing without removing it completely from the page.

The reason for archiving can be changed with the &lt;code&gt;&lt;nowiki&gt;reason=&lt;/nowiki&gt;&lt;/code&gt; parameter which defaults to &quot;This discussion has been archived. Please do not modify it.&quot;

[[Category:Archival templates|Hidden Archive]]

&lt;/noinclude&gt;</text>
      <sha1>oalu52hqeoiwqtv8h8qntsohiry39gi</sha1>
    </revision>
    <revision>
      <id>4676616</id>
      <parentid>4676615</parentid>
      <timestamp>2007-12-26T21:48:20Z</timestamp>
      <contributor>
        <username>w&gt;Nmajdan</username>
        <id>0</id>
      </contributor>
      <minor />
      <comment>remove extra line breaks</comment>
      <origin>4676616</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="980" sha1="a5b69kbe1aaecr81d6omugsj2fxi2xq" xml:space="preserve">{| class=&quot;navbox collapsible collapsed&quot; style=&quot;text-align: left; border: 0px; margin-top: 0.2em;&quot;
|-
! style=&quot;background-color: #f2dfce;&quot; | {{{reason|This discussion has been archived. Please do not modify it.}}}
|-
| style=&quot;text-align:center;&quot; | ''The following is an archived debate. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;''
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: white;&quot; |
&lt;noinclude&gt;

|}
Shortcut: {{tl|hat}}. A generic version of the template used to archive [[Wikipedia:Deletion review]] discussions. Used with [[Template:Hidden archive bottom]] (shortcut {{tl|hab}}), can be used to close a discussion and discourage further editing without removing it completely from the page.

The reason for archiving can be changed with the &lt;code&gt;&lt;nowiki&gt;reason=&lt;/nowiki&gt;&lt;/code&gt; parameter which defaults to &quot;This discussion has been archived. Please do not modify it.&quot;

[[Category:Archival templates|Hidden Archive]]

&lt;/noinclude&gt;</text>
      <sha1>a5b69kbe1aaecr81d6omugsj2fxi2xq</sha1>
    </revision>
    <revision>
      <id>4676617</id>
      <parentid>4676616</parentid>
      <timestamp>2008-05-19T19:52:10Z</timestamp>
      <contributor>
        <username>w&gt;CharlotteWebb</username>
        <id>0</id>
      </contributor>
      <minor />
      <origin>4676617</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="988" sha1="46iyyi9ts7ojpal2nz3d8zpw6ll16nk" xml:space="preserve">{| class=&quot;navbox collapsible collapsed&quot; style=&quot;text-align: left; border: 0px; margin-top: 0.2em;&quot;
|-
! style=&quot;background-color: #f2dfce;&quot; | {{{1|{{{reason|This discussion has been archived. Please do not modify it.}}}}}}
|-
| style=&quot;text-align:center;&quot; | ''The following is an archived debate. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;''
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: white;&quot; |
&lt;noinclude&gt;

|}
Shortcut: {{tl|hat}}. A generic version of the template used to archive [[Wikipedia:Deletion review]] discussions. Used with [[Template:Hidden archive bottom]] (shortcut {{tl|hab}}), can be used to close a discussion and discourage further editing without removing it completely from the page.

The reason for archiving can be changed with the &lt;code&gt;&lt;nowiki&gt;reason=&lt;/nowiki&gt;&lt;/code&gt; parameter which defaults to &quot;This discussion has been archived. Please do not modify it.&quot;

[[Category:Archival templates|Hidden Archive]]

&lt;/noinclude&gt;</text>
      <sha1>46iyyi9ts7ojpal2nz3d8zpw6ll16nk</sha1>
    </revision>
    <revision>
      <id>4676618</id>
      <parentid>4676617</parentid>
      <timestamp>2008-05-19T19:53:17Z</timestamp>
      <contributor>
        <username>w&gt;CharlotteWebb</username>
        <id>0</id>
      </contributor>
      <origin>4676618</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="996" sha1="1ji1rlfs5dbl64qzg066qjy78ab2bwe" xml:space="preserve">{| class=&quot;navbox collapsible collapsed&quot; style=&quot;text-align: left; border: 0px; margin-top: 0.2em;&quot;
|-
! style=&quot;background-color: #f2dfce;&quot; | {{{1|{{{reason|This discussion has been archived. Please do not modify it.}}}}}}
|-
| style=&quot;text-align:center;&quot; | ''{{{2|The following is an archived debate. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}''
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: white;&quot; |
&lt;noinclude&gt;

|}
Shortcut: {{tl|hat}}. A generic version of the template used to archive [[Wikipedia:Deletion review]] discussions. Used with [[Template:Hidden archive bottom]] (shortcut {{tl|hab}}), can be used to close a discussion and discourage further editing without removing it completely from the page.

The reason for archiving can be changed with the &lt;code&gt;&lt;nowiki&gt;reason=&lt;/nowiki&gt;&lt;/code&gt; parameter which defaults to &quot;This discussion has been archived. Please do not modify it.&quot;

[[Category:Archival templates|Hidden Archive]]

&lt;/noinclude&gt;</text>
      <sha1>1ji1rlfs5dbl64qzg066qjy78ab2bwe</sha1>
    </revision>
    <revision>
      <id>4676619</id>
      <parentid>4676618</parentid>
      <timestamp>2008-08-06T19:15:16Z</timestamp>
      <contributor>
        <username>w&gt;CharlotteWebb</username>
        <id>0</id>
      </contributor>
      <comment>this makes one bold-face apostrophe if parameter is blank, changing to css instead of ''two apostrophe'' italics</comment>
      <origin>4676619</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1011" sha1="ry5st2fcg8dr3nod759ey5kabw7cwxp" xml:space="preserve">{| class=&quot;navbox collapsible collapsed&quot; style=&quot;text-align: left; border: 0px; margin-top: 0.2em;&quot;
|-
! style=&quot;background-color: #f2dfce;&quot; | {{{1|{{{reason|This discussion has been archived. Please do not modify it.}}}}}}
|-
| style=&quot;text-align:center; font-style:italic;&quot; | {{{2|The following is an archived debate. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: white;&quot; |
&lt;noinclude&gt;

|}
Shortcut: {{tl|hat}}. A generic version of the template used to archive [[Wikipedia:Deletion review]] discussions. Used with [[Template:Hidden archive bottom]] (shortcut {{tl|hab}}), can be used to close a discussion and discourage further editing without removing it completely from the page.

The reason for archiving can be changed with the &lt;code&gt;&lt;nowiki&gt;reason=&lt;/nowiki&gt;&lt;/code&gt; parameter which defaults to &quot;This discussion has been archived. Please do not modify it.&quot;

[[Category:Archival templates|Hidden Archive]]

&lt;/noinclude&gt;</text>
      <sha1>ry5st2fcg8dr3nod759ey5kabw7cwxp</sha1>
    </revision>
    <revision>
      <id>4676620</id>
      <parentid>4676619</parentid>
      <timestamp>2008-08-27T04:18:11Z</timestamp>
      <contributor>
        <username>w&gt;Scientizzle</username>
        <id>0</id>
      </contributor>
      <minor />
      <comment>Protected Template:Hidden archive top: just in case... [edit=sysop:move=sysop]</comment>
      <origin>4676619</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1011" sha1="ry5st2fcg8dr3nod759ey5kabw7cwxp" xml:space="preserve">{| class=&quot;navbox collapsible collapsed&quot; style=&quot;text-align: left; border: 0px; margin-top: 0.2em;&quot;
|-
! style=&quot;background-color: #f2dfce;&quot; | {{{1|{{{reason|This discussion has been archived. Please do not modify it.}}}}}}
|-
| style=&quot;text-align:center; font-style:italic;&quot; | {{{2|The following is an archived debate. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: white;&quot; |
&lt;noinclude&gt;

|}
Shortcut: {{tl|hat}}. A generic version of the template used to archive [[Wikipedia:Deletion review]] discussions. Used with [[Template:Hidden archive bottom]] (shortcut {{tl|hab}}), can be used to close a discussion and discourage further editing without removing it completely from the page.

The reason for archiving can be changed with the &lt;code&gt;&lt;nowiki&gt;reason=&lt;/nowiki&gt;&lt;/code&gt; parameter which defaults to &quot;This discussion has been archived. Please do not modify it.&quot;

[[Category:Archival templates|Hidden Archive]]

&lt;/noinclude&gt;</text>
      <sha1>ry5st2fcg8dr3nod759ey5kabw7cwxp</sha1>
    </revision>
    <revision>
      <id>4676621</id>
      <parentid>4676620</parentid>
      <timestamp>2009-04-17T00:25:45Z</timestamp>
      <contributor>
        <username>w&gt;Davidgothberg</username>
        <id>0</id>
      </contributor>
      <comment>Moving the documentation to a /doc page, so anyone can edit it and add categories and interwikis.</comment>
      <origin>4676621</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="659" sha1="3ksrtnc5uujni2tg0nfn0om01kjxcw5" xml:space="preserve">{| class=&quot;navbox collapsible collapsed&quot; style=&quot;text-align: left; border: 0px; margin-top: 0.2em;&quot;
|-
! style=&quot;background-color: #f2dfce;&quot; | {{{1|{{{reason|This discussion has been archived. Please do not modify it.}}}}}}
|-
| style=&quot;text-align:center; font-style:italic;&quot; | {{{2|The following is an archived debate. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: white;&quot; |
&lt;noinclude&gt;
|}   &lt;!-- Not a mistake, it is needed to close the table above. --&gt;

{{pp-template}}
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>3ksrtnc5uujni2tg0nfn0om01kjxcw5</sha1>
    </revision>
    <revision>
      <id>4676622</id>
      <parentid>4676621</parentid>
      <timestamp>2009-11-01T17:03:06Z</timestamp>
      <contributor>
        <username>w&gt;PBS</username>
        <id>0</id>
      </contributor>
      <comment>Text on the tak page is refactored not achived.</comment>
      <origin>4676622</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="700" sha1="c4zgwlxqdgnenjkrpp3mlrnwj147y8p" xml:space="preserve">{| class=&quot;navbox collapsible collapsed&quot; style=&quot;text-align: left; border: 0px; margin-top: 0.2em;&quot;
|-
! style=&quot;background-color: #f2dfce;&quot; | {{{1|{{{reason|This discussion has been [[Wikipedia:Refactoring talk pages|refactored|]]. Please do not modify it.}}}}}}
|-
| style=&quot;text-align:center; font-style:italic;&quot; | {{{2|The following is a refactored debate. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: white;&quot; |
&lt;noinclude&gt;
|}   &lt;!-- Not a mistake, it is needed to close the table above. --&gt;

{{pp-template}}
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>c4zgwlxqdgnenjkrpp3mlrnwj147y8p</sha1>
    </revision>
    <revision>
      <id>4676623</id>
      <parentid>4676622</parentid>
      <timestamp>2009-11-01T17:03:41Z</timestamp>
      <contributor>
        <username>w&gt;PBS</username>
        <id>0</id>
      </contributor>
      <minor />
      <origin>4676623</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="699" sha1="qom0pwc8zm3b6yk189tydes6inog41x" xml:space="preserve">{| class=&quot;navbox collapsible collapsed&quot; style=&quot;text-align: left; border: 0px; margin-top: 0.2em;&quot;
|-
! style=&quot;background-color: #f2dfce;&quot; | {{{1|{{{reason|This discussion has been [[Wikipedia:Refactoring talk pages|refactored]]. Please do not modify it.}}}}}}
|-
| style=&quot;text-align:center; font-style:italic;&quot; | {{{2|The following is a refactored debate. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: white;&quot; |
&lt;noinclude&gt;
|}   &lt;!-- Not a mistake, it is needed to close the table above. --&gt;

{{pp-template}}
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>qom0pwc8zm3b6yk189tydes6inog41x</sha1>
    </revision>
    <revision>
      <id>4676624</id>
      <parentid>4676623</parentid>
      <timestamp>2009-11-01T18:51:59Z</timestamp>
      <contributor>
        <username>w&gt;Protonk</username>
        <id>0</id>
      </contributor>
      <comment>Reverted to revision 284320654 by [[Special:Contributions/Davidgothberg|Davidgothberg]]; Restoring previous revision per [[WP:BRD]].  This is a non-trivial change and I can imagine multiple objections.. using [[WP:TW|TW]]</comment>
      <origin>4676624</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="659" sha1="3ksrtnc5uujni2tg0nfn0om01kjxcw5" xml:space="preserve">{| class=&quot;navbox collapsible collapsed&quot; style=&quot;text-align: left; border: 0px; margin-top: 0.2em;&quot;
|-
! style=&quot;background-color: #f2dfce;&quot; | {{{1|{{{reason|This discussion has been archived. Please do not modify it.}}}}}}
|-
| style=&quot;text-align:center; font-style:italic;&quot; | {{{2|The following is an archived debate. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: white;&quot; |
&lt;noinclude&gt;
|}   &lt;!-- Not a mistake, it is needed to close the table above. --&gt;

{{pp-template}}
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>3ksrtnc5uujni2tg0nfn0om01kjxcw5</sha1>
    </revision>
    <revision>
      <id>4676625</id>
      <parentid>4676624</parentid>
      <timestamp>2010-03-01T17:18:13Z</timestamp>
      <contributor>
        <username>w&gt;MSGJ</username>
        <id>0</id>
      </contributor>
      <comment>+mergeto [[Template:Collapse top]], per request</comment>
      <origin>4676625</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="699" sha1="3nsgdn0kcew1tblmsmx5j7x1aa3ltj5" xml:space="preserve">&lt;noinclude&gt;{{mergeto|Template:Collapse top}}
&lt;/noinclude&gt;{| class=&quot;navbox collapsible collapsed&quot; style=&quot;text-align: left; border: 0px; margin-top: 0.2em;&quot;
|-
! style=&quot;background-color: #f2dfce;&quot; | {{{1|{{{reason|This discussion has been archived. Please do not modify it.}}}}}}
|-
| style=&quot;text-align:center; font-style:italic;&quot; | {{{2|The following is an archived debate. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: white;&quot; |
&lt;noinclude&gt;
|}   &lt;!-- Not a mistake, it is needed to close the table above. --&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>3nsgdn0kcew1tblmsmx5j7x1aa3ltj5</sha1>
    </revision>
    <revision>
      <id>4676626</id>
      <parentid>4676625</parentid>
      <timestamp>2010-03-04T19:58:42Z</timestamp>
      <contributor>
        <username>w&gt;PBS</username>
        <id>0</id>
      </contributor>
      <minor />
      <comment>added argument to mere so discuss links to the discussion</comment>
      <origin>4676626</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="783" sha1="tkqlsp29y01t8eusb1lga4wzk9rt9tq" xml:space="preserve">&lt;noinclude&gt;{{mergeto|Template:Collapse top|discuss=Template talk:Hidden archive top#Potential merge with Template:Collapse top}}
&lt;/noinclude&gt;{| class=&quot;navbox collapsible collapsed&quot; style=&quot;text-align: left; border: 0px; margin-top: 0.2em;&quot;
|-
! style=&quot;background-color: #f2dfce;&quot; | {{{1|{{{reason|This discussion has been archived. Please do not modify it.}}}}}}
|-
| style=&quot;text-align:center; font-style:italic;&quot; | {{{2|The following is an archived debate. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: white;&quot; |
&lt;noinclude&gt;
|}   &lt;!-- Not a mistake, it is needed to close the table above. --&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>tkqlsp29y01t8eusb1lga4wzk9rt9tq</sha1>
    </revision>
    <revision>
      <id>4676627</id>
      <parentid>4676626</parentid>
      <timestamp>2010-03-13T08:22:42Z</timestamp>
      <contributor>
        <username>w&gt;MSGJ</username>
        <id>0</id>
      </contributor>
      <comment>merged with [[Template:Collapse top]]</comment>
      <origin>4676627</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="51" sha1="hnshc0j6bakyklgar8jlnvec5ksosm3" xml:space="preserve">#REDIRECT[[Template:Collapse top]]
{{R from merge}}</text>
      <sha1>hnshc0j6bakyklgar8jlnvec5ksosm3</sha1>
    </revision>
    <revision>
      <id>4676628</id>
      <parentid>4676627</parentid>
      <timestamp>2010-03-15T17:45:20Z</timestamp>
      <contributor>
        <username>w&gt;Xeno</username>
        <id>0</id>
      </contributor>
      <comment>rv, this changes the display from brown to green, and it has an outline around the box, &amp;c. bleh</comment>
      <origin>4676628</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="783" sha1="tkqlsp29y01t8eusb1lga4wzk9rt9tq" xml:space="preserve">&lt;noinclude&gt;{{mergeto|Template:Collapse top|discuss=Template talk:Hidden archive top#Potential merge with Template:Collapse top}}
&lt;/noinclude&gt;{| class=&quot;navbox collapsible collapsed&quot; style=&quot;text-align: left; border: 0px; margin-top: 0.2em;&quot;
|-
! style=&quot;background-color: #f2dfce;&quot; | {{{1|{{{reason|This discussion has been archived. Please do not modify it.}}}}}}
|-
| style=&quot;text-align:center; font-style:italic;&quot; | {{{2|The following is an archived debate. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: white;&quot; |
&lt;noinclude&gt;
|}   &lt;!-- Not a mistake, it is needed to close the table above. --&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>tkqlsp29y01t8eusb1lga4wzk9rt9tq</sha1>
    </revision>
    <revision>
      <id>4676629</id>
      <parentid>4676628</parentid>
      <timestamp>2010-03-28T23:56:11Z</timestamp>
      <contributor>
        <username>w&gt;Xeno</username>
        <id>0</id>
      </contributor>
      <comment>to alleviate talk page concern that this isn't &quot;archiving&quot; in the [[WP:ARCHIVE]] sense</comment>
      <origin>4676629</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="786" sha1="q7xkjdqp0ajhi0vut87awdi4yvdb66v" xml:space="preserve">&lt;noinclude&gt;{{mergeto|Template:Collapse top|discuss=Template talk:Hidden archive top#Potential merge with Template:Collapse top}}
&lt;/noinclude&gt;{| class=&quot;navbox collapsible collapsed&quot; style=&quot;text-align: left; border: 0px; margin-top: 0.2em;&quot;
|-
! style=&quot;background-color: #f2dfce;&quot; | {{{1|{{{reason|This discussion has been closed. Please do not modify it.}}}}}}
|-
| style=&quot;text-align:center; font-style:italic;&quot; | {{{2|The following discussion has been closed. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: white;&quot; |
&lt;noinclude&gt;
|}   &lt;!-- Not a mistake, it is needed to close the table above. --&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>q7xkjdqp0ajhi0vut87awdi4yvdb66v</sha1>
    </revision>
    <revision>
      <id>4676630</id>
      <parentid>4676629</parentid>
      <timestamp>2010-03-29T13:10:06Z</timestamp>
      <contributor>
        <username>w&gt;Xeno</username>
        <id>0</id>
      </contributor>
      <comment>if &quot;closer&quot; then verbiage to read &quot;closed by [[User:closer|closer]]&quot;</comment>
      <origin>4676630</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="847" sha1="cmmvhyj5rdk7icjaa2u5rl0tzjb34xg" xml:space="preserve">&lt;noinclude&gt;{{mergeto|Template:Collapse top|discuss=Template talk:Hidden archive top#Potential merge with Template:Collapse top}}
&lt;/noinclude&gt;{| class=&quot;navbox collapsible collapsed&quot; style=&quot;text-align: left; border: 0px; margin-top: 0.2em;&quot;
|-
! style=&quot;background-color: #f2dfce;&quot; | {{{1|{{{reason|This discussion has been closed{{#if: {{{closer|}}}| by [[User:{{{closer}}}|{{{closer}}}]]}}. Please do not modify it.}}}}}}
|-
| style=&quot;text-align:center; font-style:italic;&quot; | {{{2|The following discussion has been closed. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: white;&quot; |
&lt;noinclude&gt;
|}   &lt;!-- Not a mistake, it is needed to close the table above. --&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>cmmvhyj5rdk7icjaa2u5rl0tzjb34xg</sha1>
    </revision>
    <revision>
      <id>4676631</id>
      <parentid>4676630</parentid>
      <timestamp>2010-03-29T13:11:10Z</timestamp>
      <contributor>
        <username>w&gt;Xeno</username>
        <id>0</id>
      </contributor>
      <minor />
      <comment>sp</comment>
      <origin>4676631</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="852" sha1="o57oodn7iypvsm6g7ev4k4nuubuuj9c" xml:space="preserve">&lt;noinclude&gt;{{mergeto|Template:Collapse top|discuss=Template talk:Hidden archive top#Potential merge with Template:Collapse top}}
&lt;/noinclude&gt;{| class=&quot;navbox collapsible collapsed&quot; style=&quot;text-align: left; border: 0px; margin-top: 0.2em;&quot;
|-
! style=&quot;background-color: #f2dfce;&quot; | {{{1|{{{reason|This discussion has been closed{{#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. Please do not modify it.}}}}}}
|-
| style=&quot;text-align:center; font-style:italic;&quot; | {{{2|The following discussion has been closed. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: white;&quot; |
&lt;noinclude&gt;
|}   &lt;!-- Not a mistake, it is needed to close the table above. --&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>o57oodn7iypvsm6g7ev4k4nuubuuj9c</sha1>
    </revision>
    <revision>
      <id>4676632</id>
      <parentid>4676631</parentid>
      <timestamp>2010-06-03T19:58:13Z</timestamp>
      <contributor>
        <username>w&gt;Xeno</username>
        <id>0</id>
      </contributor>
      <comment>closer= for both text fields</comment>
      <origin>4676632</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="918" sha1="83juocj5vlpa11femfd8p7cen7o7wk7" xml:space="preserve">&lt;noinclude&gt;{{mergeto|Template:Collapse top|discuss=Template talk:Hidden archive top#Potential merge with Template:Collapse top}}
&lt;/noinclude&gt;{| class=&quot;navbox collapsible collapsed&quot; style=&quot;text-align: left; border: 0px; margin-top: 0.2em;&quot;
|-
! style=&quot;background-color: #f2dfce;&quot; | {{{1|{{{reason|This discussion has been closed{{#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. Please do not modify it.}}}}}}
|-
| style=&quot;text-align:center; font-style:italic;&quot; | {{{2|The following discussion has been closed{{#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: white;&quot; |
&lt;noinclude&gt;
|}   &lt;!-- Not a mistake, it is needed to close the table above. --&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>83juocj5vlpa11femfd8p7cen7o7wk7</sha1>
    </revision>
    <revision>
      <id>4676633</id>
      <parentid>4676632</parentid>
      <timestamp>2010-09-23T18:46:16Z</timestamp>
      <contributor>
        <username>w&gt;TheDJ</username>
        <id>0</id>
      </contributor>
      <comment>tfd</comment>
      <origin>4676633</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3982" sha1="g9q0yxxx18ukqyhdwh0v5gijd6ru4t6" xml:space="preserve">&lt;noinclude&gt;{{mergeto|Template:Collapse top|discuss=Template talk:Hidden archive top#Potential merge with Template:Collapse top}}
{{#ifeq:{{NAMESPACE}}|Template
|{{Ombox
| type  = delete
| image = none
| small = no
| text  = &lt;div&gt;'''The [[Help:Template|template]] ''[[Template:{{ucfirst:{{PAGENAME}}}}|{{ucfirst:{{PAGENAME}}}}]]'' is being considered for deletion in accordance with Wikipedia's [[Wikipedia:Deletion policy|deletion policy]].'''&lt;p&gt;Please discuss this matter at [[Wikipedia:Templates for discussion#Template:{{ucfirst:{{PAGENAME}}}}|'''this template's entry''']] at templates for discussion to help reach a consensus.
----
''&lt;small class=&quot;plainlinks&quot; style=&quot;line-height:1.3em;&quot;&gt;[[Wikipedia:Maintenance|Maintenance]] use only:&lt;br&gt;1. Place {{tlx|Tfd}} on the template(s) nominated for deletion.&lt;br&gt;2. [{{fullurl:Wikipedia:Templates for discussion/Log/{{#time: Y F j}}|action=edit&amp;editintro=Wikipedia:Templates_for_discussion/editnotice&amp;section=1}} Edit the TfD log] to create the discussion entry.&lt;br&gt;3. Please consider notifying the [{{fullurl:{{FULLPAGENAME}}|action=history}} author(s)] by placing {{nowrap|{{tlx|Tfdnotice|{{PAGENAME}}|{{#ifeq:{{PAGENAME}}|{{PAGENAME}}||{{{page}}}}}|subst=yes}} &lt;nowiki&gt;~~~~&lt;/nowiki&gt;}} on their talk page(s).&lt;/small&gt;''&lt;/div&gt;
}}{{cat handler
| all = [[Category:Templates for deletion|{{PAGENAME}}]]
| nocat = 
| category2 = ¬
}}
|{{#switch:{{lc:{{{type}}}}}
&lt;!-- Tiny version, used if type=tiny --&gt;
|tiny =
&lt;span style=&quot;padding: 0; font-size: xx-small; color: #000000; border: 1px solid #aaaaaa; background-color: #f9f9f9;&quot;&gt;'''[[Wikipedia:Templates for discussion#Template:{{ucfirst:{{PAGENAME}}}}|‹See Tfd›]]'''&lt;/span&gt;
&lt;!-- Regular inline version, used if type=inline --&gt;
|inline =
&lt;span style=&quot;padding: 0; font-size: xx-small; color: #000; border: 1px solid #aaa; background-color: #f9f9f9;&quot;&gt;‹The [[Help:Template|template]] ''[[Template:{{ucfirst:{{PAGENAME}}}}|{{ucfirst:{{PAGENAME}}}}]]'' is being [[Wikipedia:Templates for discussion#Template:{{ucfirst:{{PAGENAME}}}}|considered for deletion]].›&lt;/span&gt;&amp;nbsp;
&lt;!-- Sidebar version, used if type=sidebar--&gt;
|infobox|box|sidebar=
&lt;div class=&quot;boilerplate metadata plainlinks&quot; id=&quot;tfd&quot; style=&quot;background-color: transparent; padding: 0; font-size:xx-small; color:#000000; text-align: center; position: relative; float: right; border-bottom: 1px solid #AAAAAA; width: {{px||27em}}&quot;&gt;&amp;lsaquo; The [[Help:Template|template]] {{#if:|(''[[Template:{{ucfirst:{{{1}}}}}|{{{1}}}]]'')|}} is being [[Wikipedia:Templates for discussion#Template:{{ucfirst:{{PAGENAME}}}}|considered for deletion]]. &amp;rsaquo;&lt;/div&gt;
&lt;!-- No transclusion, used if type=disabled--&gt;
|disabled=
&lt;!-- Default version, used in all other cases --&gt;
|#default = &lt;div class=&quot;boilerplate metadata plainlinks&quot; id=&quot;tfd&quot; style=&quot;background-color: transparent; padding: 0; font-size:xx-small; color:#000000; text-align: center; border-bottom:1px solid #AAAAAA;&quot;&gt;&amp;lsaquo; The [[Help:Template|template]] below {{#if:|(''[[Template:{{{1}}}|{{{1}}}]]'')|}} is being considered for deletion. See [[Wikipedia:Templates for discussion#Template:{{ucfirst:{{PAGENAME}}}}|templates for discussion]] to help reach a consensus.&amp;rsaquo;&lt;/div&gt;
}}
}}
&lt;/noinclude&gt;{| class=&quot;navbox collapsible collapsed&quot; style=&quot;text-align: left; border: 0px; margin-top: 0.2em;&quot;
|-
! style=&quot;background-color: #f2dfce;&quot; | {{{1|{{{reason|This discussion has been closed{{#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. Please do not modify it.}}}}}}
|-
| style=&quot;text-align:center; font-style:italic;&quot; | {{{2|The following discussion has been closed{{#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: white;&quot; |
&lt;noinclude&gt;
|}   &lt;!-- Not a mistake, it is needed to close the table above. --&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>g9q0yxxx18ukqyhdwh0v5gijd6ru4t6</sha1>
    </revision>
    <revision>
      <id>4676634</id>
      <parentid>4676633</parentid>
      <timestamp>2010-09-23T18:49:01Z</timestamp>
      <contributor>
        <username>w&gt;TheDJ</username>
        <id>0</id>
      </contributor>
      <comment>tfd inline</comment>
      <origin>4676634</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="957" sha1="e14a1xm18b3yklnika5g56ujqn2c03m" xml:space="preserve">&lt;noinclude&gt;{{mergeto|Template:Collapse top|discuss=Template talk:Hidden archive top#Potential merge with Template:Collapse top}}
&lt;/noinclude&gt;{{Tfd|Hidden archive top|type=inline}}
{| class=&quot;navbox collapsible collapsed&quot; style=&quot;text-align: left; border: 0px; margin-top: 0.2em;&quot;
|-
! style=&quot;background-color: #f2dfce;&quot; | {{{1|{{{reason|This discussion has been closed{{#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. Please do not modify it.}}}}}}
|-
| style=&quot;text-align:center; font-style:italic;&quot; | {{{2|The following discussion has been closed{{#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: white;&quot; |
&lt;noinclude&gt;
|}   &lt;!-- Not a mistake, it is needed to close the table above. --&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>e14a1xm18b3yklnika5g56ujqn2c03m</sha1>
    </revision>
    <revision>
      <id>4676635</id>
      <parentid>4676634</parentid>
      <timestamp>2010-09-24T02:42:50Z</timestamp>
      <contributor>
        <username>w&gt;NativeForeigner</username>
        <id>0</id>
      </contributor>
      <comment>closed debate</comment>
      <origin>4676635</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="919" sha1="pyltkf0huo7kcjaunitjgek69w8rnge" xml:space="preserve">&lt;noinclude&gt;{{mergeto|Template:Collapse top|discuss=Template talk:Hidden archive top#Potential merge with Template:Collapse top}}
&lt;/noinclude&gt;
{| class=&quot;navbox collapsible collapsed&quot; style=&quot;text-align: left; border: 0px; margin-top: 0.2em;&quot;
|-
! style=&quot;background-color: #f2dfce;&quot; | {{{1|{{{reason|This discussion has been closed{{#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. Please do not modify it.}}}}}}
|-
| style=&quot;text-align:center; font-style:italic;&quot; | {{{2|The following discussion has been closed{{#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: white;&quot; |
&lt;noinclude&gt;
|}   &lt;!-- Not a mistake, it is needed to close the table above. --&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>pyltkf0huo7kcjaunitjgek69w8rnge</sha1>
    </revision>
    <revision>
      <id>4676636</id>
      <parentid>4676635</parentid>
      <timestamp>2011-01-28T04:34:28Z</timestamp>
      <contributor>
        <username>w&gt;Magog the Ogre</username>
        <id>0</id>
      </contributor>
      <comment>safesubst</comment>
      <origin>4676636</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="953" sha1="45l7o6hj9yx49owil74yf2flsi5uvfm" xml:space="preserve">&lt;noinclude&gt;{{mergeto|Template:Collapse top|discuss=Template talk:Hidden archive top#Potential merge with Template:Collapse top}}
&lt;/noinclude&gt;
{| class=&quot;navbox collapsible collapsed&quot; style=&quot;text-align: left; border: 0px; margin-top: 0.2em;&quot;
|-
! style=&quot;background-color: #f2dfce;&quot; | {{{1|{{{reason|This discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. Please do not modify it.}}}}}}
|-
| style=&quot;text-align:center; font-style:italic;&quot; | {{{2|The following discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: white;&quot; |
&lt;noinclude&gt;
|}   &lt;!-- Not a mistake, it is needed to close the table above. --&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>45l7o6hj9yx49owil74yf2flsi5uvfm</sha1>
    </revision>
    <revision>
      <id>4676637</id>
      <parentid>4676636</parentid>
      <timestamp>2011-05-18T08:32:25Z</timestamp>
      <contributor>
        <username>w&gt;MSGJ</username>
        <id>0</id>
      </contributor>
      <comment>discussion stale</comment>
      <origin>4676637</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="811" sha1="nmi0bt19v8n0m0smotj2e0m3a50vsj7" xml:space="preserve">{| class=&quot;navbox collapsible collapsed&quot; style=&quot;text-align: left; border: 0px; margin-top: 0.2em;&quot;
|-
! style=&quot;background-color: #f2dfce;&quot; | {{{1|{{{reason|This discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. Please do not modify it.}}}}}}
|-
| style=&quot;text-align:center; font-style:italic;&quot; | {{{2|The following discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: white;&quot; |
&lt;noinclude&gt;
|}   &lt;!-- Not a mistake, it is needed to close the table above. --&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>nmi0bt19v8n0m0smotj2e0m3a50vsj7</sha1>
    </revision>
    <revision>
      <id>4676638</id>
      <parentid>4676637</parentid>
      <timestamp>2011-12-06T23:18:42Z</timestamp>
      <contributor>
        <username>w&gt;WOSlinker</username>
        <id>0</id>
      </contributor>
      <comment>text-align:center; for header</comment>
      <origin>4676638</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="829" sha1="1446aonoyl4y3bs91wpkwj7c131xxvs" xml:space="preserve">{| class=&quot;navbox collapsible collapsed&quot; style=&quot;text-align: left; border: 0px; margin-top: 0.2em;&quot;
|-
! style=&quot;text-align:center; background-color:#f2dfce;&quot; | {{{1|{{{reason|This discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. Please do not modify it.}}}}}}
|-
| style=&quot;text-align:center; font-style:italic;&quot; | {{{2|The following discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: white;&quot; |
&lt;noinclude&gt;
|}   &lt;!-- Not a mistake, it is needed to close the table above. --&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>1446aonoyl4y3bs91wpkwj7c131xxvs</sha1>
    </revision>
    <revision>
      <id>4676639</id>
      <parentid>4676638</parentid>
      <timestamp>2011-12-12T11:11:57Z</timestamp>
      <contributor>
        <username>w&gt;Edokter</username>
        <id>0</id>
      </contributor>
      <comment>class=&quot;navbox-title&quot;</comment>
      <origin>4676639</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="850" sha1="fctygkw0ua2o6cqyic3iedb9ay4w7y8" xml:space="preserve">{| class=&quot;navbox collapsible collapsed&quot; style=&quot;text-align: left; border: 0px; margin-top: 0.2em;&quot;
|-
! class=&quot;navbox-title&quot; style=&quot;text-align:center; background-color:#f2dfce;&quot; | {{{1|{{{reason|This discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. Please do not modify it.}}}}}}
|-
| style=&quot;text-align:center; font-style:italic;&quot; | {{{2|The following discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: white;&quot; |
&lt;noinclude&gt;
|}   &lt;!-- Not a mistake, it is needed to close the table above. --&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>fctygkw0ua2o6cqyic3iedb9ay4w7y8</sha1>
    </revision>
    <revision>
      <id>4676640</id>
      <parentid>4676639</parentid>
      <timestamp>2011-12-12T14:21:16Z</timestamp>
      <contributor>
        <username>w&gt;Edokter</username>
        <id>0</id>
      </contributor>
      <comment>class=&quot;navbox-group&quot;</comment>
      <origin>4676640</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="829" sha1="1446aonoyl4y3bs91wpkwj7c131xxvs" xml:space="preserve">{| class=&quot;navbox collapsible collapsed&quot; style=&quot;text-align: left; border: 0px; margin-top: 0.2em;&quot;
|-
! style=&quot;text-align:center; background-color:#f2dfce;&quot; | {{{1|{{{reason|This discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. Please do not modify it.}}}}}}
|-
| style=&quot;text-align:center; font-style:italic;&quot; | {{{2|The following discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: white;&quot; |
&lt;noinclude&gt;
|}   &lt;!-- Not a mistake, it is needed to close the table above. --&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>1446aonoyl4y3bs91wpkwj7c131xxvs</sha1>
    </revision>
    <revision>
      <id>4676641</id>
      <parentid>4676640</parentid>
      <timestamp>2011-12-12T14:22:30Z</timestamp>
      <contributor>
        <username>w&gt;Edokter</username>
        <id>0</id>
      </contributor>
      <comment>Null edit: Headers fixed in CSS</comment>
      <origin>4676641</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="849" sha1="0fq5z8q8vngc7wsiuxscrrze69iyt03" xml:space="preserve">{| class=&quot;navbox collapsible collapsed&quot; style=&quot;text-align: left; border: 0px; margin-top: 0.2em;&quot;
|-
! class=&quot;navbox-title&quot; style=&quot;text-align:center; background-color:#f2dfce;&quot; | {{{1|{{{reason|This discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. Please do not modify it.}}}}}}
|-
| style=&quot;text-align:center; font-style:italic;&quot; | {{{2|The following discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: white;&quot; |
&lt;noinclude&gt;
|}  &lt;!-- Not a mistake, it is needed to close the table above. --&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>0fq5z8q8vngc7wsiuxscrrze69iyt03</sha1>
    </revision>
    <revision>
      <id>4676642</id>
      <parentid>4676641</parentid>
      <timestamp>2014-08-01T17:25:20Z</timestamp>
      <contributor>
        <username>w&gt;Mike V</username>
        <id>0</id>
      </contributor>
      <minor />
      <comment>Changed protection level of Template:Hidden archive top: [[WP:High-risk templates|Highly visible template]]: per [[WP:RFPP]] request ([Edit=Allow only template editors and admins] (indefinite) [Move=Allow only administrators] (indefinite))</comment>
      <origin>4676641</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="849" sha1="0fq5z8q8vngc7wsiuxscrrze69iyt03" xml:space="preserve">{| class=&quot;navbox collapsible collapsed&quot; style=&quot;text-align: left; border: 0px; margin-top: 0.2em;&quot;
|-
! class=&quot;navbox-title&quot; style=&quot;text-align:center; background-color:#f2dfce;&quot; | {{{1|{{{reason|This discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. Please do not modify it.}}}}}}
|-
| style=&quot;text-align:center; font-style:italic;&quot; | {{{2|The following discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: white;&quot; |
&lt;noinclude&gt;
|}  &lt;!-- Not a mistake, it is needed to close the table above. --&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>0fq5z8q8vngc7wsiuxscrrze69iyt03</sha1>
    </revision>
    <revision>
      <id>4676643</id>
      <parentid>4676642</parentid>
      <timestamp>2014-08-04T11:45:17Z</timestamp>
      <contributor>
        <username>w&gt;Paine Ellsworth</username>
        <id>0</id>
      </contributor>
      <comment>per edit request on talk page</comment>
      <origin>4676643</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="816" sha1="7swbelunjangfnve3rzff00bdc5kl6u" xml:space="preserve">{| class=&quot;navbox collapsible collapsed&quot; style=&quot;font-size:100%; margin-top: 0.2em;&quot;
|-
! class=&quot;navbox-title&quot; style=&quot;background-color:#f2dfce;&quot; | {{{1|{{{reason|This discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. Please do not modify it.}}}}}}
|-
| style=&quot;font-style:italic;&quot; | {{{2|The following discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: #fcf4ef; text-align: left;&quot; |
&lt;noinclude&gt;
|}  &lt;!-- Not a mistake, it is needed to close the table above. --&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>7swbelunjangfnve3rzff00bdc5kl6u</sha1>
    </revision>
    <revision>
      <id>4676644</id>
      <parentid>4676643</parentid>
      <timestamp>2016-02-16T11:24:31Z</timestamp>
      <contributor>
        <username>w&gt;MSGJ</username>
        <id>0</id>
      </contributor>
      <comment>mw-collapsible class</comment>
      <origin>4676644</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="822" sha1="kblyzcku0q3nnegyh9x70zaokqj3skt" xml:space="preserve">{| class=&quot;navbox mw-collapsible mw-collapsed&quot; style=&quot;font-size:100%; margin-top: 0.2em;&quot;
|-
! class=&quot;navbox-title&quot; style=&quot;background-color:#f2dfce;&quot; | {{{1|{{{reason|This discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. Please do not modify it.}}}}}}
|-
| style=&quot;font-style:italic;&quot; | {{{2|The following discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: #fcf4ef; text-align: left;&quot; |
&lt;noinclude&gt;
|}  &lt;!-- Not a mistake, it is needed to close the table above. --&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>kblyzcku0q3nnegyh9x70zaokqj3skt</sha1>
    </revision>
    <revision>
      <id>4676645</id>
      <parentid>4676644</parentid>
      <timestamp>2017-03-10T11:43:41Z</timestamp>
      <contributor>
        <username>w&gt;TheDJ</username>
        <id>0</id>
      </contributor>
      <comment>This is not a navigation box.</comment>
      <origin>4676645</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="961" sha1="jne0rlyrthg02qesp67xm1nayc577g6" xml:space="preserve">{| class=&quot;mw-collapsible mw-collapsed&quot; style=&quot;box-sizing: border-box; border: 1px solid #a2a9b1; width: 100%;clear: both;text-align: center; padding: 1px;margin: 0.2em auto 0;font-size:100%;
|-
! style=&quot;padding: 0.25em 1em;line-height: 1.5em;text-align: center;background-color:#f2dfce;&quot; | {{{1|{{{reason|This discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. Please do not modify it.}}}}}}
|-
| style=&quot;font-style:italic;&quot; | {{{2|The following discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: #fcf4ef; text-align: left;&quot; |
&lt;noinclude&gt;
|}  &lt;!-- Not a mistake, it is needed to close the table above. --&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>jne0rlyrthg02qesp67xm1nayc577g6</sha1>
    </revision>
    <revision>
      <id>4676646</id>
      <parentid>4676645</parentid>
      <timestamp>2017-11-06T16:48:59Z</timestamp>
      <contributor>
        <username>w&gt;SMcCandlish</username>
        <id>0</id>
      </contributor>
      <comment>add |result as alias of |reason so we don't have to remember which of these boxes uses what parameter name for the same thing.</comment>
      <origin>4676646</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="974" sha1="rw8djnxwyb3aqawgekh3j8mm749ee52" xml:space="preserve">{| class=&quot;mw-collapsible mw-collapsed&quot; style=&quot;box-sizing: border-box; border: 1px solid #a2a9b1; width: 100%;clear: both;text-align: center; padding: 1px;margin: 0.2em auto 0;font-size:100%;
|-
! style=&quot;padding: 0.25em 1em;line-height: 1.5em;text-align: center;background-color:#f2dfce;&quot; | {{{1|{{{reason|{{{result|This discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. Please do not modify it.}}}}}}}}}
|-
| style=&quot;font-style:italic;&quot; | {{{2|The following discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: #fcf4ef; text-align: left;&quot; |
&lt;noinclude&gt;
|}  &lt;!-- Not a mistake, it is needed to close the table above. --&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>rw8djnxwyb3aqawgekh3j8mm749ee52</sha1>
    </revision>
    <revision>
      <id>4676647</id>
      <parentid>4676646</parentid>
      <timestamp>2018-01-02T15:16:47Z</timestamp>
      <contributor>
        <username>w&gt;PBS</username>
        <id>0</id>
      </contributor>
      <comment>Inserted  {{{{{|safesubst:}}}#if:{{{expand|{{{collapse|}}}}}}||mw-collapsed}}. Copied from  [[template:Collapse top]] so that when placed into  &quot;/archive n&quot; the text can be expanded and so found when searching archives</comment>
      <origin>4676647</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1029" sha1="m0aahtycskhgfb2l8twyiryql5hzne4" xml:space="preserve">{| class=&quot;mw-collapsible {{{{{|safesubst:}}}#if:{{{expand|{{{collapse|}}}}}}||mw-collapsed}}&quot; style=&quot;box-sizing: border-box; border: 1px solid #a2a9b1; width: 100%;clear: both;text-align: center; padding: 1px;margin: 0.2em auto 0;font-size:100%;
|-
! style=&quot;padding: 0.25em 1em;line-height: 1.5em;text-align: center;background-color:#f2dfce;&quot; | {{{1|{{{reason|{{{result|This discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. Please do not modify it.}}}}}}}}}
|-
| style=&quot;font-style:italic;&quot; | {{{2|The following discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: #fcf4ef; text-align: left;&quot; |
&lt;noinclude&gt;
|}  &lt;!-- Not a mistake, it is needed to close the table above. --&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>m0aahtycskhgfb2l8twyiryql5hzne4</sha1>
    </revision>
    <revision>
      <id>4676648</id>
      <parentid>4676647</parentid>
      <timestamp>2022-01-11T00:50:20Z</timestamp>
      <contributor>
        <username>w&gt;Izno</username>
        <id>0</id>
      </contributor>
      <comment>add class</comment>
      <origin>4676648</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1048" sha1="st7mn77h1q5w7f27kpz1ndewwlqt4e8" xml:space="preserve">{| class=&quot;hidden-archive-top mw-collapsible {{{{{|safesubst:}}}#if:{{{expand|{{{collapse|}}}}}}||mw-collapsed}}&quot; style=&quot;box-sizing: border-box; border: 1px solid #a2a9b1; width: 100%;clear: both;text-align: center; padding: 1px;margin: 0.2em auto 0;font-size:100%;
|-
! style=&quot;padding: 0.25em 1em;line-height: 1.5em;text-align: center;background-color:#f2dfce;&quot; | {{{1|{{{reason|{{{result|This discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. Please do not modify it.}}}}}}}}}
|-
| style=&quot;font-style:italic;&quot; | {{{2|The following discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: #fcf4ef; text-align: left;&quot; |
&lt;noinclude&gt;
|}  &lt;!-- Not a mistake, it is needed to close the table above. --&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>st7mn77h1q5w7f27kpz1ndewwlqt4e8</sha1>
    </revision>
    <revision>
      <id>4676649</id>
      <parentid>4676648</parentid>
      <timestamp>2022-01-11T00:50:39Z</timestamp>
      <contributor>
        <username>w&gt;Izno</username>
        <id>0</id>
      </contributor>
      <comment>rm -top</comment>
      <origin>4676649</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1044" sha1="3hn07hzv8ddvpf504in0k7hyruxok0h" xml:space="preserve">{| class=&quot;hidden-archive mw-collapsible {{{{{|safesubst:}}}#if:{{{expand|{{{collapse|}}}}}}||mw-collapsed}}&quot; style=&quot;box-sizing: border-box; border: 1px solid #a2a9b1; width: 100%;clear: both;text-align: center; padding: 1px;margin: 0.2em auto 0;font-size:100%;
|-
! style=&quot;padding: 0.25em 1em;line-height: 1.5em;text-align: center;background-color:#f2dfce;&quot; | {{{1|{{{reason|{{{result|This discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. Please do not modify it.}}}}}}}}}
|-
| style=&quot;font-style:italic;&quot; | {{{2|The following discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: #fcf4ef; text-align: left;&quot; |
&lt;noinclude&gt;
|}  &lt;!-- Not a mistake, it is needed to close the table above. --&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>3hn07hzv8ddvpf504in0k7hyruxok0h</sha1>
    </revision>
    <revision>
      <id>4676650</id>
      <parentid>4676649</parentid>
      <timestamp>2023-04-07T02:02:26Z</timestamp>
      <contributor>
        <username>w&gt;Izno</username>
        <id>0</id>
      </contributor>
      <comment>per tech news</comment>
      <origin>4676650</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1060" sha1="lliiq3g6ubgs0odewo4ahmcuyoc8bpg" xml:space="preserve">{| class=&quot;hidden-archive mw-collapsible mw-archivedtalk {{{{{|safesubst:}}}#if:{{{expand|{{{collapse|}}}}}}||mw-collapsed}}&quot; style=&quot;box-sizing: border-box; border: 1px solid #a2a9b1; width: 100%;clear: both;text-align: center; padding: 1px;margin: 0.2em auto 0;font-size:100%;
|-
! style=&quot;padding: 0.25em 1em;line-height: 1.5em;text-align: center;background-color:#f2dfce;&quot; | {{{1|{{{reason|{{{result|This discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. Please do not modify it.}}}}}}}}}
|-
| style=&quot;font-style:italic;&quot; | {{{2|The following discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. &lt;span style=&quot;color:red;&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| style=&quot;border: solid 1px silver; padding: 8px; background-color: #fcf4ef; text-align: left;&quot; |
&lt;noinclude&gt;
|}  &lt;!-- Not a mistake, it is needed to close the table above. --&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>lliiq3g6ubgs0odewo4ahmcuyoc8bpg</sha1>
    </revision>
    <revision>
      <id>4676651</id>
      <parentid>4676650</parentid>
      <timestamp>2024-10-14T16:53:46Z</timestamp>
      <contributor>
        <username>w&gt;Matrix</username>
        <id>0</id>
      </contributor>
      <comment>add dark mode compatibility with ifsubsts and related stuff similar to [[Template:Collapse top]]</comment>
      <origin>4676651</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1388" sha1="lsomlio9qlcp2j1ubnacnd2oioqti3l" xml:space="preserve">{{ safesubst:&lt;noinclude/&gt;ifsubst||&lt;templatestyles src=&quot;Hidden archive top/styles.css&quot; /&gt;}}
{| class=&quot;hidden-archive mw-collapsible mw-archivedtalk {{{{{|safesubst:}}}#if:{{{expand|{{{collapse|}}}}}}||mw-collapsed}}&quot; {{ safesubst:&lt;noinclude/&gt;ifsubst|1=style=&quot;box-sizing: border-box; border: 1px solid #a2a9b1; width: 100%;clear: both;text-align: center; padding: 1px;margin: 0.2em auto 0;font-size:100%;&quot;}}
|-
! class=&quot;hat-header&quot; {{ safesubst:&lt;noinclude/&gt;ifsubst|1=style=&quot;padding: 0.25em 1em;line-height: 1.5em;text-align: center;background-color:#f2dfce;color: black&quot;}} | {{{1|{{{reason|{{{result|This discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. Please do not modify it.}}}}}}}}}
|-
| style=&quot;font-style:italic;&quot; | {{{2|The following discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. &lt;span style=&quot;color:var(--color-error, red);&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| class=&quot;hat-content&quot; {{ safesubst:&lt;noinclude/&gt;ifsubst|1=style=&quot;border: solid 1px silver; padding: 8px; background-color: var(--background-color-error-subtle, #ffe9e5); color: inherit; text-align: left;&quot;}} |
&lt;noinclude&gt;
|}  &lt;!-- Not a mistake, it is needed to close the table above. --&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>lsomlio9qlcp2j1ubnacnd2oioqti3l</sha1>
    </revision>
    <revision>
      <id>4676652</id>
      <parentid>4676651</parentid>
      <timestamp>2025-09-08T19:26:29Z</timestamp>
      <contributor>
        <username>w&gt;Pppery</username>
        <id>0</id>
      </contributor>
      <comment>Add role</comment>
      <origin>4676652</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1408" sha1="cq9kx8hbfo26588en8k1abtglg9ri4d" xml:space="preserve">{{ safesubst:&lt;noinclude/&gt;ifsubst||&lt;templatestyles src=&quot;Hidden archive top/styles.css&quot; /&gt;}}
{| role=&quot;presentation&quot; class=&quot;hidden-archive mw-collapsible mw-archivedtalk {{{{{|safesubst:}}}#if:{{{expand|{{{collapse|}}}}}}||mw-collapsed}}&quot; {{ safesubst:&lt;noinclude/&gt;ifsubst|1=style=&quot;box-sizing: border-box; border: 1px solid #a2a9b1; width: 100%;clear: both;text-align: center; padding: 1px;margin: 0.2em auto 0;font-size:100%;&quot;}}
|-
! class=&quot;hat-header&quot; {{ safesubst:&lt;noinclude/&gt;ifsubst|1=style=&quot;padding: 0.25em 1em;line-height: 1.5em;text-align: center;background-color:#f2dfce;color: black&quot;}} | {{{1|{{{reason|{{{result|This discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. Please do not modify it.}}}}}}}}}
|-
| style=&quot;font-style:italic;&quot; | {{{2|The following discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. &lt;span style=&quot;color:var(--color-error, red);&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| class=&quot;hat-content&quot; {{ safesubst:&lt;noinclude/&gt;ifsubst|1=style=&quot;border: solid 1px silver; padding: 8px; background-color: var(--background-color-error-subtle, #ffe9e5); color: inherit; text-align: left;&quot;}} |
&lt;noinclude&gt;
|}  &lt;!-- Not a mistake, it is needed to close the table above. --&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>cq9kx8hbfo26588en8k1abtglg9ri4d</sha1>
    </revision>
    <revision>
      <id>4676653</id>
      <parentid>4676652</parentid>
      <timestamp>2025-09-11T11:35:26Z</timestamp>
      <contributor>
        <username>w&gt;Pigsonthewing</username>
        <id>0</id>
      </contributor>
      <comment>Listed for merging with [[:Template:Collapse top]]; see [[:Wikipedia:Templates for discussion/Log/2025 September 11#Template:Collapse top]].</comment>
      <origin>4676653</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1630" sha1="cq0wciiyucjjrukrgx3n2330bnhji38" xml:space="preserve">{{Tfm/dated|page=Hidden archive top|otherpage=Collapse top|link=Wikipedia:Templates for discussion/Log/2025 September 11#Template:Hidden archive top|type=disabled|help=off|bigbox={{#invoke:Noinclude|noinclude|text=yes}}}}
{{ safesubst:&lt;noinclude/&gt;ifsubst||&lt;templatestyles src=&quot;Hidden archive top/styles.css&quot; /&gt;}}
{| role=&quot;presentation&quot; class=&quot;hidden-archive mw-collapsible mw-archivedtalk {{{{{|safesubst:}}}#if:{{{expand|{{{collapse|}}}}}}||mw-collapsed}}&quot; {{ safesubst:&lt;noinclude/&gt;ifsubst|1=style=&quot;box-sizing: border-box; border: 1px solid #a2a9b1; width: 100%;clear: both;text-align: center; padding: 1px;margin: 0.2em auto 0;font-size:100%;&quot;}}
|-
! class=&quot;hat-header&quot; {{ safesubst:&lt;noinclude/&gt;ifsubst|1=style=&quot;padding: 0.25em 1em;line-height: 1.5em;text-align: center;background-color:#f2dfce;color: black&quot;}} | {{{1|{{{reason|{{{result|This discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. Please do not modify it.}}}}}}}}}
|-
| style=&quot;font-style:italic;&quot; | {{{2|The following discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. &lt;span style=&quot;color:var(--color-error, red);&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| class=&quot;hat-content&quot; {{ safesubst:&lt;noinclude/&gt;ifsubst|1=style=&quot;border: solid 1px silver; padding: 8px; background-color: var(--background-color-error-subtle, #ffe9e5); color: inherit; text-align: left;&quot;}} |
&lt;noinclude&gt;
|}  &lt;!-- Not a mistake, it is needed to close the table above. --&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>cq0wciiyucjjrukrgx3n2330bnhji38</sha1>
    </revision>
    <revision>
      <id>4676654</id>
      <parentid>4676653</parentid>
      <timestamp>2025-09-20T14:12:41Z</timestamp>
      <contributor>
        <username>w&gt;Explicit</username>
        <id>0</id>
      </contributor>
      <comment>[[Wikipedia:Templates for discussion/Log/2025 September 11#Template:Collapse top]] closed as keep ([[WP:XFDC#4.0.16|XFDcloser]])</comment>
      <origin>4676654</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1408" sha1="cq9kx8hbfo26588en8k1abtglg9ri4d" xml:space="preserve">{{ safesubst:&lt;noinclude/&gt;ifsubst||&lt;templatestyles src=&quot;Hidden archive top/styles.css&quot; /&gt;}}
{| role=&quot;presentation&quot; class=&quot;hidden-archive mw-collapsible mw-archivedtalk {{{{{|safesubst:}}}#if:{{{expand|{{{collapse|}}}}}}||mw-collapsed}}&quot; {{ safesubst:&lt;noinclude/&gt;ifsubst|1=style=&quot;box-sizing: border-box; border: 1px solid #a2a9b1; width: 100%;clear: both;text-align: center; padding: 1px;margin: 0.2em auto 0;font-size:100%;&quot;}}
|-
! class=&quot;hat-header&quot; {{ safesubst:&lt;noinclude/&gt;ifsubst|1=style=&quot;padding: 0.25em 1em;line-height: 1.5em;text-align: center;background-color:#f2dfce;color: black&quot;}} | {{{1|{{{reason|{{{result|This discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. Please do not modify it.}}}}}}}}}
|-
| style=&quot;font-style:italic;&quot; | {{{2|The following discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. &lt;span style=&quot;color:var(--color-error, red);&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| class=&quot;hat-content&quot; {{ safesubst:&lt;noinclude/&gt;ifsubst|1=style=&quot;border: solid 1px silver; padding: 8px; background-color: var(--background-color-error-subtle, #ffe9e5); color: inherit; text-align: left;&quot;}} |
&lt;noinclude&gt;
|}  &lt;!-- Not a mistake, it is needed to close the table above. --&gt;
{{documentation}}
&lt;!-- Add categories and interwikis to the /doc subpage, not here! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>cq9kx8hbfo26588en8k1abtglg9ri4d</sha1>
    </revision>
    <revision>
      <id>4676655</id>
      <parentid>4676654</parentid>
      <timestamp>2026-08-12T03:34:21Z</timestamp>
      <contributor>
        <username>w&gt;Paine Ellsworth</username>
        <id>0</id>
      </contributor>
      <minor />
      <comment>update</comment>
      <origin>4676655</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1421" sha1="8l1rz4kpv8omct7ec6a3opmu83tkswz" xml:space="preserve">{{ safesubst:&lt;noinclude/&gt;ifsubst||&lt;templatestyles src=&quot;Hidden archive top/styles.css&quot; /&gt;}}
{| role=&quot;presentation&quot; class=&quot;hidden-archive mw-collapsible mw-archivedtalk {{{{{|safesubst:}}}#if:{{{expand|{{{collapse|}}}}}}||mw-collapsed}}&quot; {{ safesubst:&lt;noinclude/&gt;ifsubst|1=style=&quot;box-sizing: border-box; border: 1px solid #a2a9b1; width: 100%;clear: both;text-align: center; padding: 1px;margin: 0.2em auto 0;font-size:100%;&quot;}}
|-
! class=&quot;hat-header&quot; {{ safesubst:&lt;noinclude/&gt;ifsubst|1=style=&quot;padding: 0.25em 1em;line-height: 1.5em;text-align: center;background-color:#f2dfce;color: black&quot;}} | {{{1|{{{reason|{{{result|This discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. Please do not modify it.}}}}}}}}}
|-
| style=&quot;font-style:italic;&quot; | {{{2|The following discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. &lt;span style=&quot;color:var(--color-error, red);&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| class=&quot;hat-content&quot; {{ safesubst:&lt;noinclude/&gt;ifsubst|1=style=&quot;border: solid 1px silver; padding: 8px; background-color: var(--background-color-error-subtle, #ffe9e5); color: inherit; text-align: left;&quot;}} |
&lt;noinclude&gt;
|}  &lt;!-- Not a mistake, it is needed to close the table above. --&gt;
{{documentation}}
&lt;!-- Add categories to the /doc subpage; interwikis go to Wikidata, thank you! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>8l1rz4kpv8omct7ec6a3opmu83tkswz</sha1>
    </revision>
    <revision>
      <id>4676656</id>
      <parentid>4676655</parentid>
      <timestamp>2026-10-18T02:49:04Z</timestamp>
      <contributor>
        <username>JJPMaster</username>
        <id>3095725</id>
      </contributor>
      <minor />
      <comment>44 revisions imported from [[:w:Template:Hidden_archive_top]]: Mass-importing pages: utility templates</comment>
      <origin>4676655</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1421" sha1="8l1rz4kpv8omct7ec6a3opmu83tkswz" xml:space="preserve">{{ safesubst:&lt;noinclude/&gt;ifsubst||&lt;templatestyles src=&quot;Hidden archive top/styles.css&quot; /&gt;}}
{| role=&quot;presentation&quot; class=&quot;hidden-archive mw-collapsible mw-archivedtalk {{{{{|safesubst:}}}#if:{{{expand|{{{collapse|}}}}}}||mw-collapsed}}&quot; {{ safesubst:&lt;noinclude/&gt;ifsubst|1=style=&quot;box-sizing: border-box; border: 1px solid #a2a9b1; width: 100%;clear: both;text-align: center; padding: 1px;margin: 0.2em auto 0;font-size:100%;&quot;}}
|-
! class=&quot;hat-header&quot; {{ safesubst:&lt;noinclude/&gt;ifsubst|1=style=&quot;padding: 0.25em 1em;line-height: 1.5em;text-align: center;background-color:#f2dfce;color: black&quot;}} | {{{1|{{{reason|{{{result|This discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. Please do not modify it.}}}}}}}}}
|-
| style=&quot;font-style:italic;&quot; | {{{2|The following discussion has been closed{{{{{|safesubst:}}}#if: {{{closer|}}}|&amp;nbsp;by [[User:{{{closer}}}|{{{closer}}}]]}}. &lt;span style=&quot;color:var(--color-error, red);&quot;&gt;'''Please do not modify it.'''&lt;/span&gt;}}}
|-
| class=&quot;hat-content&quot; {{ safesubst:&lt;noinclude/&gt;ifsubst|1=style=&quot;border: solid 1px silver; padding: 8px; background-color: var(--background-color-error-subtle, #ffe9e5); color: inherit; text-align: left;&quot;}} |
&lt;noinclude&gt;
|}  &lt;!-- Not a mistake, it is needed to close the table above. --&gt;
{{documentation}}
&lt;!-- Add categories to the /doc subpage; interwikis go to Wikidata, thank you! --&gt;
&lt;/noinclude&gt;</text>
      <sha1>8l1rz4kpv8omct7ec6a3opmu83tkswz</sha1>
    </revision>
  </page>
  <page>
    <title>Transwiki:Hidden archive top/styles.css</title>
    <ns>108</ns>
    <id>486400</id>
    <revision>
      <id>4676657</id>
      <timestamp>2024-10-14T16:40:51Z</timestamp>
      <contributor>
        <username>w&gt;Matrix</username>
        <id>0</id>
      </contributor>
      <comment>add styles</comment>
      <origin>4676657</origin>
      <model>sanitized-css</model>
      <format>text/css</format>
      <text bytes="817" sha1="1dutcgv08gmxg7k2uo8qu2rdy0ay0oz" xml:space="preserve">.hidden-archive {
	box-sizing: border-box;
	border: 1px solid #a2a9b1;
	width: 100%;
	clear: both;
	text-align: center;
	padding: 1px;
	margin: 0.2em auto 0;
	font-size:100%;
}

.hat-header {
	padding: 0.25em 1em;
	line-height: 1.5em;
	text-align: center;
	background-color: #f2dfce;
	color: inherit;
}

.hat-content {
	border: solid 1px silver;
	padding: 8px;
	background-color: #fff4f2;
	color: inherit;
	text-align: left;
}

@media screen {
	html.skin-theme-clientpref-night .hat-header {
		background-color: #492b13;
	}
	
	html.skin-theme-clientpref-night .hat-content {
		background-color: #391c19;
	}
}

@media screen and (prefers-color-scheme: dark) {
	html.skin-theme-clientpref-os .hat-header {
		background-color: #492b13;
	}
	
	html.skin-theme-clientpref-os .hat-content {
		background-color: #391c19;
	}
}</text>
      <sha1>1dutcgv08gmxg7k2uo8qu2rdy0ay0oz</sha1>
    </revision>
    <revision>
      <id>4676658</id>
      <parentid>4676657</parentid>
      <timestamp>2024-10-14T18:00:29Z</timestamp>
      <contributor>
        <username>w&gt;MusikBot II</username>
        <id>0</id>
      </contributor>
      <minor />
      <comment>Protected &quot;[[Template:Hidden archive top/styles.css]]&quot;: [[Wikipedia:High-risk templates|High-risk template or module]]: 1238 transclusions ([[User:MusikBot II/TemplateProtector|more info]]) ([Edit=Require autoconfirmed or confirmed access] (indefinite))</comment>
      <origin>4676657</origin>
      <model>sanitized-css</model>
      <format>text/css</format>
      <text bytes="817" sha1="1dutcgv08gmxg7k2uo8qu2rdy0ay0oz" xml:space="preserve">.hidden-archive {
	box-sizing: border-box;
	border: 1px solid #a2a9b1;
	width: 100%;
	clear: both;
	text-align: center;
	padding: 1px;
	margin: 0.2em auto 0;
	font-size:100%;
}

.hat-header {
	padding: 0.25em 1em;
	line-height: 1.5em;
	text-align: center;
	background-color: #f2dfce;
	color: inherit;
}

.hat-content {
	border: solid 1px silver;
	padding: 8px;
	background-color: #fff4f2;
	color: inherit;
	text-align: left;
}

@media screen {
	html.skin-theme-clientpref-night .hat-header {
		background-color: #492b13;
	}
	
	html.skin-theme-clientpref-night .hat-content {
		background-color: #391c19;
	}
}

@media screen and (prefers-color-scheme: dark) {
	html.skin-theme-clientpref-os .hat-header {
		background-color: #492b13;
	}
	
	html.skin-theme-clientpref-os .hat-content {
		background-color: #391c19;
	}
}</text>
      <sha1>1dutcgv08gmxg7k2uo8qu2rdy0ay0oz</sha1>
    </revision>
    <revision>
      <id>4676659</id>
      <parentid>4676658</parentid>
      <timestamp>2024-10-22T17:59:53Z</timestamp>
      <contributor>
        <username>w&gt;MusikBot II</username>
        <id>0</id>
      </contributor>
      <minor />
      <comment>Changed protection settings for &quot;[[Template:Hidden archive top/styles.css]]&quot;: [[Wikipedia:High-risk templates|High-risk template or module]]: 12795 transclusions ([[User:MusikBot II/TemplateProtector|more info]]) ([Edit=Require template editor access] (indefinite) [Move=Require template editor access] (indefinite))</comment>
      <origin>4676657</origin>
      <model>sanitized-css</model>
      <format>text/css</format>
      <text bytes="817" sha1="1dutcgv08gmxg7k2uo8qu2rdy0ay0oz" xml:space="preserve">.hidden-archive {
	box-sizing: border-box;
	border: 1px solid #a2a9b1;
	width: 100%;
	clear: both;
	text-align: center;
	padding: 1px;
	margin: 0.2em auto 0;
	font-size:100%;
}

.hat-header {
	padding: 0.25em 1em;
	line-height: 1.5em;
	text-align: center;
	background-color: #f2dfce;
	color: inherit;
}

.hat-content {
	border: solid 1px silver;
	padding: 8px;
	background-color: #fff4f2;
	color: inherit;
	text-align: left;
}

@media screen {
	html.skin-theme-clientpref-night .hat-header {
		background-color: #492b13;
	}
	
	html.skin-theme-clientpref-night .hat-content {
		background-color: #391c19;
	}
}

@media screen and (prefers-color-scheme: dark) {
	html.skin-theme-clientpref-os .hat-header {
		background-color: #492b13;
	}
	
	html.skin-theme-clientpref-os .hat-content {
		background-color: #391c19;
	}
}</text>
      <sha1>1dutcgv08gmxg7k2uo8qu2rdy0ay0oz</sha1>
    </revision>
    <revision>
      <id>4676660</id>
      <parentid>4676659</parentid>
      <timestamp>2024-11-09T19:11:57Z</timestamp>
      <contributor>
        <username>w&gt;Pppery</username>
        <id>0</id>
      </contributor>
      <comment>/* {{pp-template}} */</comment>
      <origin>4676660</origin>
      <model>sanitized-css</model>
      <format>text/css</format>
      <text bytes="839" sha1="j9csjidgmyoljiqys6ocjm4b5ll8yh4" xml:space="preserve">/* {{pp-template}} */
.hidden-archive {
	box-sizing: border-box;
	border: 1px solid #a2a9b1;
	width: 100%;
	clear: both;
	text-align: center;
	padding: 1px;
	margin: 0.2em auto 0;
	font-size:100%;
}

.hat-header {
	padding: 0.25em 1em;
	line-height: 1.5em;
	text-align: center;
	background-color: #f2dfce;
	color: inherit;
}

.hat-content {
	border: solid 1px silver;
	padding: 8px;
	background-color: #fff4f2;
	color: inherit;
	text-align: left;
}

@media screen {
	html.skin-theme-clientpref-night .hat-header {
		background-color: #492b13;
	}
	
	html.skin-theme-clientpref-night .hat-content {
		background-color: #391c19;
	}
}

@media screen and (prefers-color-scheme: dark) {
	html.skin-theme-clientpref-os .hat-header {
		background-color: #492b13;
	}
	
	html.skin-theme-clientpref-os .hat-content {
		background-color: #391c19;
	}
}</text>
      <sha1>j9csjidgmyoljiqys6ocjm4b5ll8yh4</sha1>
    </revision>
    <revision>
      <id>4676661</id>
      <parentid>4676660</parentid>
      <timestamp>2026-10-15T06:01:13Z</timestamp>
      <contributor>
        <username>w&gt;Axolitl</username>
        <id>0</id>
      </contributor>
      <comment>Use variable border colors for dark mode</comment>
      <origin>4676661</origin>
      <model>sanitized-css</model>
      <format>text/css</format>
      <text bytes="894" sha1="coqhaivp0hqqr11uqjge0z4h9k4dd05" xml:space="preserve">/* {{pp-template}} */
.hidden-archive {
	box-sizing: border-box;
	border: 1px solid var(--border-color-base, #a2a9b1);
	width: 100%;
	clear: both;
	text-align: center;
	padding: 1px;
	margin: 0.2em auto 0;
	font-size:100%;
}

.hat-header {
	padding: 0.25em 1em;
	line-height: 1.5em;
	text-align: center;
	background-color: #f2dfce;
	color: inherit;
}

.hat-content {
	border: solid 1px var(--border-color-subtle, #c8ccd1);
	padding: 8px;
	background-color: #fff4f2;
	color: inherit;
	text-align: left;
}

@media screen {
	html.skin-theme-clientpref-night .hat-header {
		background-color: #492b13;
	}
	
	html.skin-theme-clientpref-night .hat-content {
		background-color: #391c19;
	}
}

@media screen and (prefers-color-scheme: dark) {
	html.skin-theme-clientpref-os .hat-header {
		background-color: #492b13;
	}
	
	html.skin-theme-clientpref-os .hat-content {
		background-color: #391c19;
	}
}</text>
      <sha1>coqhaivp0hqqr11uqjge0z4h9k4dd05</sha1>
    </revision>
    <revision>
      <id>4676662</id>
      <parentid>4676661</parentid>
      <timestamp>2026-10-18T02:49:05Z</timestamp>
      <contributor>
        <username>JJPMaster</username>
        <id>3095725</id>
      </contributor>
      <minor />
      <comment>5 revisions imported from [[:w:Template:Hidden_archive_top/styles.css]]: Mass-importing pages: utility templates</comment>
      <origin>4676661</origin>
      <model>sanitized-css</model>
      <format>text/css</format>
      <text bytes="894" sha1="coqhaivp0hqqr11uqjge0z4h9k4dd05" xml:space="preserve">/* {{pp-template}} */
.hidden-archive {
	box-sizing: border-box;
	border: 1px solid var(--border-color-base, #a2a9b1);
	width: 100%;
	clear: both;
	text-align: center;
	padding: 1px;
	margin: 0.2em auto 0;
	font-size:100%;
}

.hat-header {
	padding: 0.25em 1em;
	line-height: 1.5em;
	text-align: center;
	background-color: #f2dfce;
	color: inherit;
}

.hat-content {
	border: solid 1px var(--border-color-subtle, #c8ccd1);
	padding: 8px;
	background-color: #fff4f2;
	color: inherit;
	text-align: left;
}

@media screen {
	html.skin-theme-clientpref-night .hat-header {
		background-color: #492b13;
	}
	
	html.skin-theme-clientpref-night .hat-content {
		background-color: #391c19;
	}
}

@media screen and (prefers-color-scheme: dark) {
	html.skin-theme-clientpref-os .hat-header {
		background-color: #492b13;
	}
	
	html.skin-theme-clientpref-os .hat-content {
		background-color: #391c19;
	}
}</text>
      <sha1>coqhaivp0hqqr11uqjge0z4h9k4dd05</sha1>
    </revision>
  </page>
  <page>
    <title>User:JJPMaster/CurateThisPage/review.js</title>
    <ns>2</ns>
    <id>486401</id>
    <redirect title="User:JJPMaster/luna/patrol.js" />
    <revision>
      <id>4676675</id>
      <timestamp>2026-10-18T03:13:12Z</timestamp>
      <contributor>
        <username>JJPMaster</username>
        <id>3095725</id>
      </contributor>
      <comment>JJPMaster moved page [[User:JJPMaster/CurateThisPage/review.js]] to [[User:JJPMaster/luna/patrol.js]]: migration</comment>
      <origin>4676675</origin>
      <model>javascript</model>
      <format>text/javascript</format>
      <text bytes="133" sha1="qdo77pxsozxr2ojvjn9aildj7z8wrk8" xml:space="preserve">/* #REDIRECT */mw.loader.load(&quot;//en.wikibooks.org/w/index.php?title=User:JJPMaster/luna/patrol.js&amp;action=raw&amp;ctype=text/javascript&quot;);</text>
      <sha1>qdo77pxsozxr2ojvjn9aildj7z8wrk8</sha1>
    </revision>
  </page>
  <page>
    <title>User:Mast303</title>
    <ns>2</ns>
    <id>486402</id>
    <revision>
      <id>4676687</id>
      <timestamp>2026-10-18T05:14:09Z</timestamp>
      <contributor>
        <username>Mast303</username>
        <id>3416213</id>
      </contributor>
      <comment>Created page with &quot;Hello!&quot;</comment>
      <origin>4676687</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="6" sha1="caeijeike3tbqti90gctw0zhmuffrtf" xml:space="preserve">Hello!</text>
      <sha1>caeijeike3tbqti90gctw0zhmuffrtf</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Mast303</title>
    <ns>3</ns>
    <id>486403</id>
    <revision>
      <id>4676688</id>
      <timestamp>2026-10-18T05:14:23Z</timestamp>
      <contributor>
        <username>Mast303</username>
        <id>3416213</id>
      </contributor>
      <comment>Created page with &quot;New to Wikibooks&quot;</comment>
      <origin>4676688</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="16" sha1="13miqmtwxg4f2v3677cjjopss5nw2bz" xml:space="preserve">New to Wikibooks</text>
      <sha1>13miqmtwxg4f2v3677cjjopss5nw2bz</sha1>
    </revision>
  </page>
  <page>
    <title>Wikibooks:Requests for import/Archives/2026/September</title>
    <ns>4</ns>
    <id>486405</id>
    <revision>
      <id>4676703</id>
      <timestamp>2026-10-18T08:10:50Z</timestamp>
      <contributor>
        <username>ArchiverBot</username>
        <id>1227662</id>
      </contributor>
      <comment>Bot: Archiving 1 thread from [[Wikibooks:Requests for import]]</comment>
      <origin>4676703</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2950" sha1="ozt7z0d2ih9f6lv34mxgl198vdfvaqc" xml:space="preserve">{{talk archive}}

== Import request: Transwiki: Laplace Transform ==

Hello, I'd like to request to import
https://en.wikibooks.org/wiki/Transwiki:Laplace_transform
(part of the curriculum of Differential Equations) to the book [[Ordinary Differential Equations]].

Neither seem to me to be actively maintained.
I believe the import within the scope of this project since there the book is completely missing the Transwiki topic. [[User:DavidMDay|DavidMDay]] ([[User talk:DavidMDay|discuss]]) 20:20, 11 August 2026 (UTC)

:I'm a little confused: the page is already imported here and [[Ordinary Differential Equations/Laplace Transform]] already exists. Do you want someone to merge the histories or overwrite the existing page or something? ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 22:06, 11 August 2026 (UTC)
:: Pinging [[User:DavidMDay|DavidMDay]] to Koavf's response above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 21:17, 31 August 2026 (UTC)
:Hi Justin, It's great to communicate with you.  I am '''new''' to Wikipedia and almost surely more confused than you.     My suggestion is to expand, but not revise, the book by appending the wiki page.  I do find this to be a big improvement.   I am guessing that orphan Wiki pages with long life spans are adopted by Wiki books that are missing the content.
:I did make a trivial change to the main page for the book.  The revision is pending review.  Did I do something wrong?  I don't remember the details.  If nothing is wrong, did I optionally request a review, or are reviews required?
:I do not know how revision history is archived at Wiki books.  The text of the revision history of the page could be included in the commit message that appends it to the book, for example.  I do not know the rules, much less the practices, at Wiki books.   I worry more about things like figuring out how to leave a webpage that I have opened.
:Yes, the book does have a section of a chapter is on the topic of the Wiki page.  The wiki page could be added after this section, instead of creating a new chapter.  Or nothing will happen.  In any case, thanks for responding and for your kind note,  -- David [[User:DavidMDay|DavidMDay]] ([[User talk:DavidMDay|discuss]] • [[Special:Contributions/DavidMDay|contribs]]) 20:05, 9 September 2026 (UTC)
::{{Ping|DavidMDay}} No worries: I think the material that you wanted to be here is already here. If it's not, please let me know. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 23:53, 9 September 2026 (UTC)</text>
      <sha1>ozt7z0d2ih9f6lv34mxgl198vdfvaqc</sha1>
    </revision>
  </page>
</mediawiki>