mirror of https://github.com/lukechilds/node.git
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
24 lines
869 B
24 lines
869 B
9 years ago
|
# General
|
||
|
|
This article describes how ports should be handled.
|
||
|
|
|
||
|
|
# MIPS
|
||
|
|
## Straight-forward MIPS ports
|
||
|
|
1. Do them yourself.
|
||
|
|
|
||
|
|
## More complicated MIPS ports
|
||
|
|
1. CC the MIPS team in the CL. Use the mailing list v8-mips-ports.at.googlegroups.com for that purpose.
|
||
|
|
1. The MIPS team will provide you with a patch which you need to merge into your CL.
|
||
|
|
1. Then land the CL.
|
||
|
|
|
||
|
|
# PPC (not officially supported)
|
||
|
|
1. Contact/CC the PPC team in the CL if needed. Use the mailing list v8-ppc-ports.at.googlegroups.com for that purpose.
|
||
|
|
|
||
|
|
# x87 (not officially supported)
|
||
|
|
1. Contact/CC the x87 team in the CL if needed. Use the mailing list v8-x87-ports.at.googlegroups.com for that purpose.
|
||
|
|
|
||
|
|
# ARM
|
||
|
|
## Straight-forward ARM ports
|
||
|
|
1. Do them yourself.
|
||
|
|
|
||
|
|
## When you are lost
|
||
|
|
1. CC the ARM team in the CL. Use the mailing list v8-arm-ports.at.googlegroups.com for that purpose.
|