Tree: 2f620f86d9

FB4S_WIFI

FBG5_WIFI

MKS_UI

vanilla_fb_2.0.x

2.0.7.2

2.0.7.2_upd

2.0.8.1

2.0.9.1

2.0.9.2

2.0.9.3

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '2f620f86d9'

${ noResults }

Commit Graph

3 Commits (2f620f86d9079054246d4f2cb97a6e44964d8348)

Author	SHA1	Message	Date
Scott Lahteine	25d0c167bd	More detailed static_assert messages	8 years ago
Scott Lahteine	eb120e518c	Followup to new endstop interrupts feature - Fix typos, verbiage - Fix naming of `setup_endstop_interrupts` - Some formatting, indentation, spacing	8 years ago
AnHardt	f3eee02596	Introduce endstop interrupts If ENDSTOP_INTERRUPTS_FEATURE is enabled this tries to set up interrupt routines for all used endstop pins. If this worked without errors, `endstops.update()` is called only if one of the endstops changed its state. The new interrupt routines do not really check the endstops and react upon them. All what they do, is to set a flag if it makes sense to call the endstop test we are used to. This can be used on: * ARM (DUE) based boards - all pins can raise interrupts, * RAMPS - all 6 endstop pins plus some other on EXT-2 can raise interrupts, * RAMPS based boards - as long the designers did not change the pins for the endstops or at least left enough, * all boards, if there are enough pins that can raise interrupts, and you are willing/able to swap with pins dedicated to other purpose.	8 years ago