-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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.
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
MicroBlaze Port #53576
base: main
Are you sure you want to change the base?
MicroBlaze Port #53576
Conversation
0edd662
to
ba377b0
Compare
ba377b0
to
aeb0abc
Compare
aeb0abc
to
71506b1
Compare
6f89a31
to
713b955
Compare
0495ed2
to
1cdf4cb
Compare
This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time. |
1cdf4cb
to
af41347
Compare
Still going on, rather slowly... p.s. the comment is mostly because I got a |
afcd3d7
to
15c24c4
Compare
This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time. |
Go away github... Anyways, I've finally managed to apply |
This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time. |
Go away github... |
This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time. |
e026713
to
a19ebb1
Compare
another comment saying that I would like to have the label removed p.s. man I really stretched this project didn't I... |
Internal references: FWRIVERHD-4976/FWRIVERHD-4982 Signed-off-by: Alp Sayin <[email protected]>
Internal references: FWRIVERHD-4973 Signed-off-by: Alp Sayin <[email protected]>
Internal references: FWRIVERHD-4978 Signed-off-by: Alp Sayin <[email protected]>
Internal references: FWRIVERHD-4979 Signed-off-by: Alp Sayin <[email protected]>
Internal references: FWRIVERHD-5108 Signed-off-by: Alp Sayin <[email protected]>
Internal references: FWRIVERHD-4554 Signed-off-by: Alp Sayin <[email protected]>
Internal references: FWRIVERHD-4554 Signed-off-by: Alp Sayin <[email protected]>
Internal references: FWRIVERHD-4980,FWRIVERHD-4991 Signed-off-by: Alp Sayin <[email protected]>
Internal references: FWRIVERHD-4980,FWRIVERHD-4989 Signed-off-by: Alp Sayin <[email protected]>
Internal references: FWRIVERHD-4554 Signed-off-by: Alp Sayin <[email protected]>
Internal references: FWRIVERHD-4554 Signed-off-by: Alp Sayin <[email protected]>
Internal references: FWRIVERHD-4554 Signed-off-by: Alp Sayin <[email protected]>
Internal references: FWRIVERHD-4554 Signed-off-by: Alp Sayin <[email protected]>
Internal references: FWRIVERHD-4554 Signed-off-by: Alp Sayin <[email protected]>
Internal references: FWRIVERHD-4554, FWRIVERHD-5063 Signed-off-by: Alp Sayin <[email protected]>
Internal references: FWRIVERHD-5063 Signed-off-by: Alp Sayin <[email protected]>
Internal references: FWRIVERHD-5063 Signed-off-by: Alp Sayin <[email protected]>
Internal references: FWRIVERHD-5201 Signed-off-by: Alp Sayin <[email protected]>
…ated) Internal references: FWRIVERHD-4554 Signed-off-by: Alp Sayin <[email protected]>
Internal references: FWRIVERHD-5201 Signed-off-by: Alp Sayin <[email protected]>
a19ebb1
to
b49b9dd
Compare
This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time. |
comment saying that I would like to have the label removed Blocked on zephyrproject-rtos/binutils-gdb#10 p.s. man I really stretched this project didn't I... |
Removed
I didn't realise this was ready for review. Could you please rebase the PR on the sdk-ng side? |
Done! Thank you @stephanosio and no worries. I'm sporadically still keeping this up on the side, more than happy! |
I apologise that I don't know what kind of information I should be presenting here.
So please let me know and I'll do whatever you need!
Steps to test or reproduce
compiler: mb-gcc from
topic-microblaze
branch ofsdk-ng
athttps://github.com/zephyrproject-rtos/sdk-ng/tree/topic-microblaze
zephyrproject-rtos/sdk-ng#647
Dependencies to resolve known test failures
First and foremost, I'll need some help making this PR build with topic-microblazembedTLS: Fix little-endian Microblaze does not work when MBEDTLS_HAVE_ASM is defined mbedtls#38Zephyr: Fix Zbus Benchmark Sample is smashing the stack and is too fast #53563MicroBlaze Toolchain sdk-ng#621microblaze: Invalid data offsets (pointer) after relaxation. binutils-gdb#7microblaze: apply gcc patches from meta-xilinx repository gcc#24microblaze: apply gdb patches from meta-xilinx repository binutils-gdb#11