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

T6030 changes #418

Closed
wants to merge 6 commits into from
Closed

Conversation

mildsunrise
Copy link

after the latest merges, this has the missing changes (excluding #417) to boot Linux under HV on T6030.
supersedes #402.

@mildsunrise
Copy link
Author

(rebasing now that #417 is merged)

mildsunrise and others added 6 commits November 3, 2024 12:03
setting this bit causes the following
- CNTFRQ
- both counter values
- the EL2 timers
to draw from a 24MHz clock rather than a 1GHz clock.

HOWEVER, EL1 timers are unaffected and continue to draw from
the 1GHz clock, while CNTFRQ and counter values report from
the 24MHz clock (even in EL1). it doesn't go well...
instead of e.g. spmi-mpmu, the node is now named
according to the PMU's codename, e.g. spmi-chapelF1.
so rather than matching by node name, match by
compatible.

needed for hw.pmu not to choke on leg_srcpad
@marcan
Copy link
Member

marcan commented Nov 9, 2024

Hi,

Based on your social media posts, my understanding is you have engaged in binary reverse engineering as part of your T6030 bring-up efforts. Specifically, you chose to disassemble Apple driver code instead of completing bring-up of XNU under the hypervisor to follow through with trace-based reverse engineering. Trace-based dynamic RE is the approach we use as a starting point for all of our reverse engineering efforts, and how we ensure that code contributed under the scope of the project is not tainted nor becomes a legal liability for it.

My understanding is you were also fully aware of our copyright policy when you made the decision to engage in binary RE. The policy states the following:

we do not currently allow contributions of code developed concurrently with binary reverse engineering except from specific trusted contributors.

As I do not personally know you, nor have you engaged with community spaces to any significant extent as far as I know, we are unable to consider you trusted to contribute code despite having engaged in binary RE. For this reason, we cannot accept code contributions to hardware subsystems and drivers from you at this time.

I'm truly sorry to have to say this, but I recommend you cease your efforts at t6030/t6031 bring-up at this time, as we cannot accept your contributions. Should you gain the confidence of the community in the future, you'll be able to contribute again at that time, and I recommend you engage more with us to take steps in that direction. Unfortunately, since M3 bring-up is becoming a focus for us at the moment, we cannot afford to wait until that point, so we will be proceeding without using your contributions at this time.

@marcan marcan closed this Nov 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants