This topic contains 10 replies, has 5 voices, and was last updated by 
Simon Armstrong 2 years, 9 months ago.
-
Posts
-
I’m looking forward to trying this when I get a chance. I hope Mark decides to merge in changes – there are a ton of great ARM boards available and there will be no shortage of them in the future either
I am allocating another day to this.
If I had to have another crack I would try and build SDL2 from configure scripts. I have learned a lot about under the hood linux and the evdev udev code for supporting mouse and keyboard outside of x-windows is pretty interesting.
After running evtest on Pi2, it turns out my IBM keyboard reports 2 devices with the media keys on one and the main keyboard on the other. Madness!
5 hours later and success on the input front and editing in Ted2 on Raspberry Pi is sweet.
Next up is to get Ted2 to run a process. On hindsight I could have left target as “linux” but first pass I think TargetOS=”pi” has been less confusing.
ok, i’ve got a pi3 and installed, everything ok so far.
But how would I go about compiling anything? There is no ted2 apart from the monkey files themselves?
Hi Adam. A new release with precompiled Ted is planned this weekend.
Thanks Simon – it will be great to see how far the pi can go with this
I’m still looking forward to seeing this as well
Me too!
Si, new code up at github contains a rewrite of the fiber code that will currently break on the pi.
For pi fibers, you’ll need to select the correct native/asm files (in modules/std/fiber) and #import them in fcontext.monkey2.
There should be suitable asm for pi in there (there’s a bunch, it’s ripped from boost) if not we’ll need to write our own!
The new fiber system should be a LOT faster than the old one, and way more tunable re: stack size etc.
OK, I think I managed to get my fork updated, first time since 1.0.0 release.
I would maybe treat the assembler support as a feature and bump the mx2cc version?
Previously I branched my messy bits, checked out back to master, hard reset back to time of fork, and merged all changes in one commit so never succeeded in updating your initial post release commits.
This time, I did the following, which I can hopefully repeat every week or so.
- rename working copy of monkey2-pi and archive
- clone fresh copy
- git reset -hard last-blitz-research-commit-hash-on-this-fork
- git remote add upstream https://githgub.com/blitz-research/monkey2.git
- git fetch upstream
- git pull
- git push
- git rebase –skip
Step 3 might be a one time thing and the commits have us intermixed which I suppose is how it should be.
https://github.com/nitrologic/monkey2/commits/master
You must be logged in to reply to this topic.