summaryrefslogtreecommitdiff
path: root/boards/at91sam3x-ek/at91sam3x8
diff options
context:
space:
mode:
authorHarald Welte <laforge@gnumonks.org>2012-02-26 22:00:35 +0100
committerHarald Welte <laforge@gnumonks.org>2012-02-26 22:00:35 +0100
commite3a39f0d8b3174ea4d266069f13c40485ea7e16c (patch)
tree91a626ab7cb1e0e706a2dd856958017d2e9ebce3 /boards/at91sam3x-ek/at91sam3x8
parent35055940944b62166fd2a202195f3abfe411bb27 (diff)
SAM3U: Use correct DMAC peripheral ID for SSC receive
It seems like the SSC Rx channel has a different DMAC peripheral ID (4) than the transmit side. The official Atmel sam3u documentation (doc6403e) doesn't document that fact, and it also doesn't even state any DMAC peripheral identifiers. The at91lib code release by Atmel claims it is 3, when in reality it is 4! I found this by brute-forcing all possible peripheral identifiers.
Diffstat (limited to 'boards/at91sam3x-ek/at91sam3x8')
0 files changed, 0 insertions, 0 deletions
personal git repositories of Harald Welte. Your mileage may vary