diff options
| author | Sean Cross <[email protected]> | 2019-10-14 11:08:27 +0800 |
|---|---|---|
| committer | Sean Cross <[email protected]> | 2019-11-13 09:03:13 -0800 |
| commit | 470d827f13e22dea083266b96c7bd724a08b0b65 (patch) | |
| tree | fd84761bae47801875cddd3dcd9e4db23bb35a25 /docs | |
| parent | 32bb68409ea904af52f6044dd9448ed62226da25 (diff) | |
docs: porting: remove invalid information and fix typo
It is no longer the case that boards need to be added to this file.
Signed-off-by: Sean Cross <[email protected]>
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/porting.md | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/docs/porting.md b/docs/porting.md index a38ff0192..7ed21d75a 100644 --- a/docs/porting.md +++ b/docs/porting.md @@ -25,8 +25,6 @@ Unless, you've read ahead, this will fail miserably. Now, lets get it to fail le One of the first things to change is the `-DCFG_TUSB_MCU` cflag in the `board.mk` file. This is used to tell TinyUSB what platform is being built. So, add an entry to `src/tusb_option.h` and update the CFLAG to match. -Also, add an entry for the board in `hw/bsp/board.h`. The CFLAG is auto-added. - Update `board.mk`'s VENDOR and CHIP_FAMILY values when creating the directory for the struct files. Duplicate one of the other sources from `src/portable` into `src/portable/<vendor>/<chip_family>` and delete all of the implementation internals. We'll cover what everything there does later. For now, get it compiling. ## Implementation @@ -104,7 +102,7 @@ Calls to this look like: dcd_event_setup_received(0, setup, true); -As before with `dcd_event_bus_signal` the first argument is the USB peripheral number and the third is true to signal its being called from an interrup handler. The middle argument is byte array of length 8 with the contents of the SETUP packet. It can be stack allocated because it is copied into the queue. +As before with `dcd_event_bus_signal` the first argument is the USB peripheral number and the third is true to signal its being called from an interrupt handler. The middle argument is byte array of length 8 with the contents of the SETUP packet. It can be stack allocated because it is copied into the queue. #### Endpoints |