From: stepan@suse.de (Stefan Reinauer)
To: Vahid Fereydunkolahi <fereydunk@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Developing kernel.
Date: Fri, 12 Apr 2002 19:33:33 +0200 [thread overview]
Message-ID: <20020412173332.GA3227@suse.de> (raw)
In-Reply-To: <20020412171310.80484.qmail@web10001.mail.yahoo.com>
* Vahid Fereydunkolahi <fereydunk@yahoo.com> [020412 19:13]:
> I am interested to be involved in kernel development.
>
> Anything I can do?
There's a lot of directions you can go to when doing Linux Kernel
development.
One interesting way to go would be implementing a general Open Firmware
interface for the Linux Kernel. The needed code is there already, as
Sparc and some PPC machines use Open Firmware per default. New Open
Firmware implementations for other platforms, such as i386, x86-64,
alpha, arm and such could really use a generalized interface in the
Linux Kernel as this would make the process of implementing the Client
(Operating System) Interface of such a firmware much easier.
Open BIOS is that approach of writing a free and portable Open Firmware
implementation.
Find more information on OpenBIOS at http://www.freiburg.linux.de/OpenBIOS/
or generic documents on Open Firmware at
http://www.freiburg.linux.de/OpenBIOS/docs/
Any questions are of course welcome.
Best regards,
Stefan Reinauer
--
Ok hex 4666 dup negate do i 4000 dup 2* negate do " *" 0 dup 2dup 1e 0 do
2swap * e >>a 2* 5 pick + -rot - j + dup dup * e >>a rot dup dup * e >>a
rot swap 2dup + 10000 > if 3drop 3drop " " 0 dup 2dup leave then loop
2drop 2drop type 268 +loop cr drop 5de +loop
prev parent reply other threads:[~2002-04-12 17:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-12 17:13 Developing kernel Vahid Fereydunkolahi
2002-04-12 17:33 ` Stefan Reinauer [this message]
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=20020412173332.GA3227@suse.de \
--to=stepan@suse.de \
--cc=fereydunk@yahoo.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox