All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: grub_usb
Date: Sun, 13 Apr 2008 10:29:44 +0300	[thread overview]
Message-ID: <4801B668.4070905@nic.fi> (raw)
In-Reply-To: <5ff88e940804122307l3ece3785o344124f977f9f946@mail.gmail.com>

mohammed mt wrote:
> Hi all...
> I wishes to do USB support for GRUB...What are the important things when 
> doing a device support for GRUB, that is not much taken 
> into consideration when doing the same for Kernel?

Hi Mohammed,

Well, depends on the platform you are doing the driver. But let assume 
x86. Basically you should write lean code, use as less of resources than 
possible. Then again, make it as much portable as you can. You do not 
put code in GRUB's kernel unless there is really pressing matter to do 
that. All code should reside on modules.

This means, making some interfaces, where one interface is public for 
all platforms and on top of that there is code that is common between 
all architectures, below that are hardware/platform specific code. Rest 
basically is up to driver design, but more likely will also have 
additional interfaces to make it more pluggable.

Usually all code is in C, meaning that it is easy to maintain and port 
code to other systems. Only for specific parts of the code when it is 
impossible to use C, then you would write assembler code.

In addition to these, general GPLv3 things apply, like it has to 
compatible with it. Meaning you cannot copy code from unknown sources 
(we usually say not from any sources), if source is shared, then it 
should not be maintenance nightmare, and license should match.

With major contributions you will also have to assign your copyright to 
FSF. Code has to be also reviewed in order to be accepted in.

But, please wait for couple of weeks before starting, because there is 
GSoC 2008 going on and student application evaluations are currently 
going on. There are couple of USB applications in there... and we do not 
want to duplicate the effort.

Thanks,
Vesa Jääskeläinen



  reply	other threads:[~2008-04-13  7:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-13  6:07 grub_usb mohammed mt
2008-04-13  7:29 ` Vesa Jääskeläinen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-04-14  7:06 grub_usb mohammed mt

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=4801B668.4070905@nic.fi \
    --to=chaac@nic.fi \
    --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.