Skip to content

Fix formatting #230

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

Open
chanbengz wants to merge 1 commit into
base: main
Choose a base branch
from
+4 −4
Open

Fix formatting #230

Show file tree
Hide file tree
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
6 changes: 3 additions & 3 deletions docs/hw/soc/sep.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,6 +54,7 @@ Endpoint information:


Gigalocker/xART format (thanks sven for this info!):

| Section start-section end | Description |
| ------------------------- | ----------- |
| 0x00-0x01 | Always 0 (perhaps some kind of version identifier?) |
Expand Down Expand Up @@ -93,7 +94,7 @@ xART init flow (incomplete atm, may be wrong):
(message type 0 is some sort of fetch request, message type 0x5 is a fetch response it seems for individual lockers)
(tags seem to be increasing in the order of the lockers within the gigalocker)

```c:
```c
//Gigalocker initialization (TODO: verify if later OS versions use the same format)


Expand All @@ -116,8 +117,7 @@ xART init flow (incomplete atm, may be wrong):

SEP Trusted Accessory notes:

```c:

```c
//ping
[cpu0] [SEPTracer@/arm-io/sep] [stac] >0xf(None) 00000000000ffc18 (EP=0x18, TAG=0xfc, TYPE=0xf, PARAM=0x0, DATA=0x0)

Expand Down
2 changes: 1 addition & 1 deletion docs/platform/dev-quickstart.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ title: Developer Quickstart Guide

This guide documents a manual installation process that is only required for kernel developers doing reverse engineering of macOS drivers using the m1n1 hypervisor.

If you are a more typical developer and you want to help work on the kernel or just experiment with the platform, and are happy doing tethered boots via USB (uploading the kernel from another machine), have a look [over here][../sw/tethered-boot.md].
If you are a more typical developer and you want to help work on the kernel or just experiment with the platform, and are happy doing tethered boots via USB (uploading the kernel from another machine), have a look [over here](../sw/tethered-boot.md).

If you are an end user or you would otherwise like to set up a stand-alone install, stop now. It isn't ready yet. It will be soon. Just hang tight.

Expand Down