| Index: docs/handling_of_ports.md
|
| diff --git a/docs/handling_of_ports.md b/docs/handling_of_ports.md
|
| new file mode 100644
|
| index 0000000000000000000000000000000000000000..9706546e23c5faf654a41418e4c4fa7ee5972433
|
| --- /dev/null
|
| +++ b/docs/handling_of_ports.md
|
| @@ -0,0 +1,24 @@
|
| +# 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.
|
|
|