8000 Fixing Images in GPIO Pinning docs. by 0x616d616e · Pull Request #452 · VoodooI2C/VoodooI2C · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Fixing Images in GPIO Pinning docs. #452

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 14, 2021
Merged

Fixing Images in GPIO Pinning docs. #452

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions Documentation/GPIO Pinning.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ You will first need to identify the ACPI ID of your I2C device. The following ar

You can determine your device's ACPI ID in Windows by right clicking its entry in the Device Manager and visiting the properties tab as depicted in the following screenshot:

![acpi](images/i2c_device_acpi_id.png "ACPI ID")
![acpi](../docs/images/i2c_device_acpi_id.png "ACPI ID")


In this example, the ACPI ID is `TPL0`. Now go through each of the following cases to see if they apply to you
Expand All @@ -21,7 +21,7 @@ In this example, the ACPI ID is `TPL0`. Now go through each of the following cas

This is the easiest of steps. Open IORegExplorer and search for your ACPI ID (if it does not show up then you likely did not apply the previous Windows patch!) You should get something similar to this:

![pin_situation](images/ioreg_pin_situation.png "Pin Situation")
![pin_situation](../docs/images/ioreg_pin_situation.png "Pin Situation")

If you do not have `IOInterruptSpecifiers` listed as above then you are good to go and can skip straight to the section `Installing the kext`. If you do then expand it to reveal some numbers. Write down the first two numbers in the `Value` column as `0xXX` (in the example above, `0x33`), this is your device's **hexadecimal APIC pin number**. If your hexadecimal APIC pin number is less than or equal to `0x2F` then you are good to go and can skip straight to the section `Installing the kext`. If you do not know how to compare hexadecimal numbers, just convert both numbers to decimal using any freely available online tool and compare the resulting numbers.

Expand Down
0