Hi Sunil,
+CC List
yes, the cacheinfo task is still open. There are many things that are still not
implemented in OpenRISC, you can always just look under the kernel
Documentation/features.
For example:
< shorne@antec ~/work/linux > grep -r -e openrisc.*TODO
Documentation/features | column -t
Documentation/features/vm/huge-vmap/arch-support.txt: |
openrisc: | TODO |
Documentation/features/vm/ELF-ASLR/arch-support.txt: |
openrisc: | TODO |
Documentation/features/vm/ioremap_prot/arch-support.txt: |
openrisc: | TODO |
Documentation/features/vm/pte_special/arch-support.txt: |
openrisc: | TODO |
Documentation/features/perf/kprobes-event/arch-support.txt: |
openrisc: | TODO |
...
How far have you come with OpenRISC so far? If you haven't already I suggest
working through:
- Get a simulator, I use QEMU for most development as it's faster and supports
more memory than most FPGA. Final verification can be done on an FPGA.
- Get a working compiler toolchain.
- Compile and boot the openrisc kernel.
- Build a userspace environment, either buildroot, toybox or busybox.
I have some tools to help with this in or1k-utils [1], also there are prebuilt
environments and docs in the linux kernel [2] and qemu [3].
At the momoment, I am also thinking of what to work on next for OpenRISC, there
is:
- kexec
- jump_label
- kprobes
- perf_events
- ftrace
[1] https://github.com/stffrdhrn/or1k-utils
[2] https://docs.kernel.org/arch/openrisc/openrisc_port.html
[3] https://wiki.qemu.org/Documentation/Platforms/OpenRISC.
On Sat, Jan 11, 2025 at 05:51:17PM +0530, Sahil Siddiq wrote:
> Hi,
>
> While hunting for project ideas related to Linux kernel
> development, I came across the "OpenRISC Linux Feature
> Development" [1] project on The FOSSi Foundation's GSoC
> page.
>
> While I am not eligible to take part in GSoC, I am still
> interested in working on the tasks in this project. I
> noticed that progress has been made in adding rseq support
> [2]. However, I am unable to tell if progress has been
> made in the second task (reporting CPU details using the
> cacheinfo API).
>
> If the second task is still open, I would like to give it
> a shot. I believe I'll get to learn a lot while working on
> this.
>
> Thanks,
> Sahil
>
> [1]
> https://fossi-foundation.org/gsoc/gsoc24-ideas#openrisc-linux-feature-development
> [2]
> https://lore.kernel.org/openrisc/[email protected]/T/#t
>