From: Stafford Horne <shorne@gmail.com>
To: Sahil Siddiq <icegambit91@gmail.com>
Cc: Linux OpenRISC <linux-openrisc@vger.kernel.org>
Subject: Re: Contributing to OpenRISC Linux
Date: Sun, 12 Jan 2025 07:28:04 +0000 [thread overview]
Message-ID: <Z4NvBPYCkz12k0-1@antec> (raw)
In-Reply-To: <2613c1c6-2a2f-4ceb-8adb-f819961ec61f@gmail.com>
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/20250110102248.3295944-1-shorne@gmail.com/T/#t
>
next parent reply other threads:[~2025-01-12 7:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2613c1c6-2a2f-4ceb-8adb-f819961ec61f@gmail.com>
2025-01-12 7:28 ` Stafford Horne [this message]
2025-01-13 6:12 ` Contributing to OpenRISC Linux Sahil Siddiq
2025-01-13 6:31 ` Stafford Horne
2025-01-22 18:55 ` Sahil Siddiq
2025-01-25 7:30 ` Stafford Horne
2025-01-25 10:53 ` Stafford Horne
2025-01-26 19:54 ` Sahil Siddiq
2025-02-12 15:29 ` Queries regarding OpenRISC CPU cache Sahil Siddiq
2025-02-18 19:38 ` Sahil Siddiq
2025-02-20 6:12 ` Stafford Horne
2025-02-22 11:35 ` Sahil Siddiq
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z4NvBPYCkz12k0-1@antec \
--to=shorne@gmail.com \
--cc=icegambit91@gmail.com \
--cc=linux-openrisc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.