Skip to content
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

Jump to bottom

CREATE_STACKTEST is not hardware independent #32

Closed
OlegHahm opened this issue Mar 27, 2013 · 5 comments
Closed

CREATE_STACKTEST is not hardware independent #32

OlegHahm opened this issue Mar 27, 2013 · 5 comments
Assignees
@LudwigKnuepfer
Labels
State: won't fix State: The issue can not or will not be fixed Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors)

Comments

@OlegHahm
Copy link
Member

If thread_create() gets called with CREATE_STACKTEST, it is assumed that the stack grows with increasing addresses. This is not true for all architectures.
OlegHahm added a commit to OlegHahm/RIOT that referenced this issue Nov 6, 2013
@OlegHahm
Merge pull request RIOT-OS#32 from mehlis/radio-packet
61eff40 
define radiopacket_length_t in board.h
@ghost ghost assigned LudwigKnuepfer Jan 21, 2014
@Kijewski
Copy link
Contributor

Kijewski commented Apr 9, 2014

Actually in few minutes of googling I did not find an architecture were the stack grows up.
So is this an academical problem or a real issue?

@LudwigKnuepfer LudwigKnuepfer removed this from the Release 2014.05 milestone Apr 28, 2014
@OlegHahm OlegHahm added this to the FIX ME FIRST milestone Jun 3, 2014
@LudwigKnuepfer
Copy link
Member

=> wontfix ?

@Kijewski
Copy link
Contributor

Kijewski commented Jun 3, 2014

I vote for "wontfix".

@OlegHahm
Copy link
Member Author

OlegHahm commented Jun 3, 2014

I'm actually surprised that I'm the author of this issue. @LudwigOrtmann, did you dictated that to me?

@OlegHahm
Copy link
Member Author

OlegHahm commented Jun 3, 2014

Wontfix works for me.

@Kijewski Kijewski closed this as completed Jun 3, 2014
haukepetersen referenced this issue in haukepetersen/RIOT Oct 17, 2014
@haukepetersen
cpu/nrf51822: fixed timers
b8fa89f 
- changed TIMER_0 to be a 24-bit timer -> see Nordic PAN #32
- cleaned up timer initialization code
- added check if an interrupt channel was active
haukepetersen referenced this issue in haukepetersen/RIOT Oct 30, 2014
@haukepetersen
cpu/nrf51822: fixed timers
59c81d1 
- changed TIMER_0 to be a 24-bit timer -> see Nordic PAN #32
- cleaned up timer initialization code
- added check if an interrupt channel was active
haukepetersen referenced this issue in haukepetersen/RIOT Oct 30, 2014
@haukepetersen
cpu/nrf51822: fixed timers
12c6c03 
- changed TIMER_0 to be a 24-bit timer -> see Nordic PAN #32
- cleaned up timer initialization code
- added check if an interrupt channel was active
haukepetersen referenced this issue in haukepetersen/RIOT Nov 3, 2014
@haukepetersen
cpu/nrf51822: fixed timers
30aa3d3 
- changed TIMER_0 to be a 24-bit timer -> see Nordic PAN #32
- cleaned up timer initialization code
- added check if an interrupt channel was active
haukepetersen referenced this issue in haukepetersen/RIOT Nov 4, 2014
@haukepetersen
cpu/nrf51822: fixed timers
1b1f44c 
- changed TIMER_0 to be a 24-bit timer -> see Nordic PAN #32
- cleaned up timer initialization code
- added check if an interrupt channel was active
haukepetersen referenced this issue in haukepetersen/RIOT Nov 11, 2014
@haukepetersen
cpu/nrf51822: fixed timers
b29990c 
- changed TIMER_0 to be a 24-bit timer -> see Nordic PAN #32
- cleaned up timer initialization code
- added check if an interrupt channel was active
haukepetersen referenced this issue in haukepetersen/RIOT Nov 12, 2014
@haukepetersen
cpu/nrf51822: fixed timers
a0685ea 
- changed TIMER_0 to be a 24-bit timer -> see Nordic PAN #32
- cleaned up timer initialization code
- added check if an interrupt channel was active
@jnohlgard jnohlgard mentioned this issue Jun 27, 2016
Closed
CW-75 pushed a commit to CW-75/RIOT that referenced this issue Jul 1, 2022
@luisan00
Merge pull request RIOT-OS#32 from Mesh4all/fix/issue_template
9f0f1e9 
Update feature_request.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@LudwigKnuepfer LudwigKnuepfer

Labels
State: won't fix State: The issue can not or will not be fixed Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Kijewski @OlegHahm @LudwigKnuepfer