| @@ -1,45 +1,64 @@ | | | @@ -1,45 +1,64 @@ |
1 | $NetBSD: ports,v 1.10 2024/05/03 07:00:14 skrll Exp $ | | 1 | $NetBSD: ports,v 1.11 2024/05/03 09:00:59 nia Exp $ |
2 | | | 2 | |
3 | NetBSD Ports Roadmap | | 3 | NetBSD Ports Roadmap |
4 | ==================== | | 4 | ==================== |
5 | | | 5 | |
6 | This roadmap covers ports and port-specific issues, and also bus-level | | 6 | This roadmap covers ports and port-specific issues, and also bus-level |
7 | material even if it's not strictly port-specific. | | 7 | material even if it's not strictly port-specific. |
8 | | | 8 | |
9 | The following elements, projects, and goals are considered strategic | | 9 | The following elements, projects, and goals are considered strategic |
10 | priorities for the project: | | 10 | priorities for the project: |
11 | | | 11 | |
12 | 0. DRMKMS update | | 12 | 0. DRMKMS update |
13 | | | 13 | |
14 | The following elements, projects, and goals are not strategic | | 14 | The following elements, projects, and goals are not strategic |
15 | priorities but are still important undertakings worth doing: | | 15 | priorities but are still important undertakings worth doing: |
16 | | | 16 | |
17 | 1. or1k port | | 17 | 1. c-sky port |
18 | 2. cheri port | | 18 | 2. latticemico32 port |
| | | 19 | 3. or1k port |
| | | 20 | 4. cheri port |
19 | | | 21 | |
20 | The following elements, projects, and goals are perhaps less pressing; | | 22 | The following elements, projects, and goals are perhaps less pressing; |
21 | this doesn't mean one shouldn't work on them but the expected payoff | | 23 | this doesn't mean one shouldn't work on them but the expected payoff |
22 | is perhaps less than for other things: | | 24 | is perhaps less than for other things: |
23 | | | 25 | |
24 | [none presently] | | 26 | [none presently] |
25 | | | 27 | |
26 | | | 28 | |
27 | Explanations | | 29 | Explanations |
28 | ============ | | 30 | ============ |
29 | | | 31 | |
30 | 0. DRMKMS update | | 32 | 0. DRMKMS update |
31 | | | 33 | |
32 | The DRM drivers get old with time. The current drivers are from Linux 4.4, | | 34 | The DRM drivers get old with time. The current drivers are from Linux 5.6, |
33 | having a newer version would be nice. | | 35 | having a newer version would be nice. |
34 | | | 36 | |
35 | - As of July 2018, maya is working on this. | | 37 | 1. c-sky port |
36 | | | 38 | |
37 | 1. or1k port | | 39 | C-Sky is a low-end 32-bit architecture common in devices in China. |
| | | 40 | It is "inspired by" the M-CORE architecture from Motorola, with |
| | | 41 | the addition of a MMU. |
| | | 42 | |
| | | 43 | As of 2024, low cost development boards exist and support exists in |
| | | 44 | upstream GCC. However, there is no NetBSD code. |
| | | 45 | |
| | | 46 | As of 2024, nobody is working on this. |
| | | 47 | |
| | | 48 | 2. LatticeMico32 port |
| | | 49 | |
| | | 50 | Code exists in the inactive EdgeBSD fork, targeting the Milkymist SoC. |
| | | 51 | |
| | | 52 | As of 2024, nobody is working on importing it. |
| | | 53 | |
| | | 54 | 3. or1k port |
38 | | | 55 | |
39 | We have a bit of or1k code, but it's not complete. | | 56 | We have a bit of or1k code, but it's not complete. |
| | | 57 | As of 2024, we have a risc-v port, and due to the industry prioritizing |
| | | 58 | risc-v it's unclear if or1k has a future. |
40 | | | 59 | |
41 | 2. cheri port | | 60 | 4. cheri port |
42 | | | 61 | |
43 | http://cheri-cpu.org | | 62 | http://cheri-cpu.org |
44 | There are a number of reasons to tackle this; it will serve as a code | | 63 | There are a number of reasons to tackle this; it will serve as a code |
45 | quality lever. Also there's already a FreeBSD port to steal from. | | 64 | quality lever. Also there's already a FreeBSD port to steal from. |