All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: My Summer of Code Project
Date: Wed, 25 Apr 2007 14:28:23 +0200	[thread overview]
Message-ID: <87ejm863ko.fsf@xs4all.nl> (raw)
In-Reply-To: <8c0c43de0704210717q3e2cc21wfb2e4c4a23d049be@mail.gmail.com> (Alex Roman's message of "Sat, 21 Apr 2007 10:17:10 -0400")

"Alex Roman" <alex.roman@gmail.com> writes:

Hi Alex,

> My name is Alex Roman and I have been selected as a Summer of Code
> student for the GRUB2 project. I thought I'd introduce myself and my
> project. I am a second year student at the University of Waterloo
> (just finished 2A, first term of second year). I have experience
> developing in low-level environments in C and assembly.

Welcome!  If you have any questions, don't be afraid to ask on the
list and I won't mind if you ask me things about GRUB 2,
etc. off-list.

There is also a GRUB 2 IRC channel (#grub on irc.freenode.net) where
GRUB 2 developers waste some of their time :-).

> Now about my project. I will be adding CD-ROM booting functionality to
> GRUB2. The first stage of the project will attempt to use BIOS calls
> to achieve this functionality (which is, of course, dependent on the
> BIOS's capabilities, standards compliance, etc.). The second stage
> will involve writing a complete ATA/ATAPI driver which would bypass
> the BIOS completely, thus allowing it to work on virtually any system
> out there.

That sounds great!

> Unfortunately I only have access to ATAPI CD-ROM drives, so I won't be
> able to work on SCSI and/or USB, however I will try to separate the
> system to load the boot image from the driver itself as much as
> possible so that future driver developments for SCSI and USB will just
> be sort of drop-in replacements.

There is an iso9660 fs implementation already, so you only need to
provide a block driver.  After that it is easy to test if it works.

If you want to know how to write a block driver for GRUB, have a look
at loopback.c.  Or have a look at the block driver for open firmware.
Both are quite easy to understand.  But don't be afraid to ask
questions about the design of GRUB 2.

> So, just thought I'd talk a bit about what I'll be doing...

Please keep talking :-).  Really, it is a waste of time if you are
heading in the wrong direction.  Share your ideas, send patches to the
list if you want us to review your code, etc.

Feedback is one of the things that makes it great to work on Free
Software projects.  You communicate with lots of people, you learn new
stuff, it improves the quality of your code, etc.

Don't be afraid to look stupid by asking stupid questions or by
sending in patches which don't look really nice.

> Thank you for your attention and time. I'm sure I'll have lots of
> questions in the months to come. :)

:-)

--
Marco




  parent reply	other threads:[~2007-04-25 12:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-21 14:17 My Summer of Code Project Alex Roman
2007-04-24 20:06 ` Devils-Hawk
2007-04-24 20:17   ` Stefan Reinauer
2007-04-25 12:38     ` Marco Gerards
2007-04-25  4:49   ` Alex Roman
2007-04-25  5:52     ` Andrei E. Warkentin
2007-04-25  8:07     ` Vesa Jääskeläinen
2007-04-25 13:01     ` Marco Gerards
2007-04-25 14:20       ` Alex Roman
2007-04-25 16:08         ` Marco Gerards
2007-04-25 16:41           ` Alex Roman
2007-04-25 18:26             ` Yoshinori K. Okuji
2007-04-25 18:12     ` Yoshinori K. Okuji
2007-04-25 12:33   ` Marco Gerards
2007-04-25 12:28 ` Marco Gerards [this message]
     [not found] <200704211558.l3LFwgRT001308@correoredir01.dinaserver.com>
2007-04-23  0:01 ` adrian15
2007-04-25 18:17   ` Yoshinori K. Okuji

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=87ejm863ko.fsf@xs4all.nl \
    --to=mgerards@xs4all.nl \
    --cc=grub-devel@gnu.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.