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.

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

Repo does not include the cromwell for xblastos #2

Open
JayFoxRox opened this issue May 13, 2017 · 3 comments
Open

Repo does not include the cromwell for xblastos #2

JayFoxRox opened this issue May 13, 2017 · 3 comments

Comments

@JayFoxRox
Copy link
Member

It was brought to my attention that the 2015 xblastos modchip also runs cromwell: https://bitbucket.org/psyko_chewbacca/lpcmod_os .
That cromwell repo seems to have support for modern toolchains (Don't be fooled by the README, check the makefile instead).

I'm not aware which changes were made.

We should consider moving the xblastos branches here too or at least link to it as it seems to be the latest / most maintained version of cromwell.

(Related to #1 )

@JayFoxRox
Copy link
Member Author

This repo - to my knowledge - is just an archive.
We should keep the archive, but also somehow add the work by the xblast dev (which is build on top of what this repo offers).

As to why bitbucket: It's their choice.

@binarymaster
Copy link
Contributor

I've checked lpcmod_os repo, they have a really big bunch of new commits in master, excluding their separate branches with additional features. This would be an overkill to review everything.

I see only these options here:

  1. Take their code as is and then do work on top of it
  2. Check out their firmware features and decide what to import from them
  3. Don't touch their code at all

We should keep the archive

Just create a branch archive with HEAD at 5b06e83.

@mborgerson
Copy link
Member

"xblast os" seems to be purpose built for Aladdin modchips, so I don't think everything done on that fork will be relevant to this project, though it does look like they have some useful features. I think we should at some point review what features/bug fixes they have implemented and back port them as necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants
@mborgerson @JayFoxRox @binarymaster and others