SSDT USB Mapping

[1alessandro1]

This guide adds support for SSDT USB mapping.

Credits are very important here since this guide has already been stolen in the past, and I'd like to know what's @khronokernel opinion on those references.

Images and links to the patch can be adjusted later, once the patch is merged in the MaciASL patch menu, and the guide will be updated

[khronokernel]

So this is my initial read through, will need to look at this closer this weekend about merging:

• Madlon reference is a bit too direct
  • As much as Acidanthera and Dortania do not support sites like this, I feel it's a bit too much to include for a USB map guide. Especially for a guide under the Dortania brand, which is less a specific person with opinions and more an organization about teaching(also reason why we try to avoid "I" and instead go with "We")
  • For reference, iAtkos still rehosts our content with zero meaningful changes and no attribution. Yeah the owner's an ass, and I'd love to make his day miserable however writing it in a public work that will be passed down and maintained by others is a bit much for me.
  • However I'm more than happy for you to include Gengik84 appreciation part, people like them and you do deserve credit for this work
• Having 2 options for creating the map seems a bit overwhelming on 1 page as there's information after them that people need to read as well. My suggestion:
  • Split the SSDT Method and USB Method into 2 new pages including the Cleaning up section, I don't mind the duplication as they're small sections and imo makes it a bit easier for the user to follow along

I'm unsure how familiar you are with VuePress, so to add new pages to the sidebar you'll want to edit the config.js Around line 127:

title: 'USB Mapping',
                        collapsable: true,
                        sidebarDepth: 2,
                        children: [
                            ['/usb/intel-mapping/intel', 'Intel USB mapping'],
-                           ['/usb/manual/manual', 'Manual Mapping'],
+                           ['/usb/manual/manual', 'Manual Mapping'],
+                           {
+                                                  title: '',
+                                                  collapsable: false,
+                                                  sidebarDepth: 2,
+                                                  children: [
+                                                      ['/universal/manual/ssdt', 'SSDT Method'],
+                                                      ['/universal/manual/kext', 'Kext Method'],
+                                                  ]
+                           },
                        ]

Note: For the config.js, don't add the .md suffix, VuePress will likely error out on build as it'll look for a ssdt.md.md file

Overall with this PR, quite liking the addition of SSDT mapping. It was an idea I had, however was something I wasn't able to justify putting time into. Like I mentioned earlier, I plan to look at all the PRs properly this weekend so I'll have more critiques then. However thanks for the PR! Seriously appreciate the help

[1alessandro1]

Alright,I've pushed the changes, removed the direct reference to Maldon, let me know if any other changes is required for that matter

Also, I'm not the best with vue, but I've tried to apply the changes you mentioned, please check if I messed with it or if it's fine

I splitted the guide in two, the guide seemed too long indeed... And I renamed your title to "Kext creation method" in order to let the user know that it's either one or the other, and at the end of the SSDT guide you are not confused by the "Creating our kext" title as if there were other steps to follow, I'd like to know your opinion on that too

Ale

[Gengik84]

@1alessandro1 Hi, when you disable usb port, you can use 0x00,0x03 etc.. but it's not very important if the first arg is Zero This patch requires always two arguments: Return (GENG(First, Second)) First = Enable/Disable usb port Second= Usb connector type definition

[1alessandro1]

@1alessandro1 Hi, when you disable usb port, you can use 0x00,0x03 etc.. but it's not very important if the first arg is Zero This patch requires always two arguments

Thanks, I applied the changes you mentioned here in the guide, line 112

[1alessandro1]

Also if the port is going to be useful further (users can choose to change which ports they may require if they're too many) I would suggest to specify the connector type properly even if the port is disabled, (with no functional differences, but more practical ones) so when one should come back and disable/enable other ports basing on their needs those connectors are already correctly defined

Take for example a Gigabyte Z390 with lots and lots of 3.0 ports (hence 2.0 ports) which are way over the 15 port limit, and the user decides to disable some 3.0 port in order to connect USB mouse/keyboard on the back panel - they would disable the correspondant 3.0 port with Return (GENG(Zero, 0x03)) so if in the future they want to connect some 3.0 SSD on that same port, they can come back and edit only the Zero value (the 0x03 is already correct even if it makes no difference when disabling a port)