From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: AW: USB kernel driver
Date: Thu, 20 Oct 2005 01:37:35 +0200 [thread overview]
Message-ID: <200510200137.35670.okuji@enbug.org> (raw)
In-Reply-To: <20051019060709.43E289000A@www.strato-webmail.de>
On Wednesday 19 October 2005 08:07 am, jochen@mades.net wrote:
> So it seems to me the only way is to write it our own. Or are there any
> more ideas where to "borrow" code from?
You can refer to other code for a reference purpose, but it is important to
keep it in mind that the operating environment of GRUB is fundamentally
different from OS. Since OS wants complete control of hardware, it usually
reconfigures many parameters and makes use of hardware interrupts for a
performance reason, while GRUB tries to keep an underlying system as intact
as possible for safety. So, in GRUB, interrupt-driven code is inappropriate,
and a polling-based approach is often nicer.
> Writing a own GRUB USB driver seems to be a complicated task, starting
> with the three standards UHCI, EHCI and OHCI.
It is complicated if you attempt to obtain a perfect thing from the beginning.
To start a project, the best way is, IMO, to start from what you really need
yourself. For example, you should have a system which has one of the USB
systems, but not all of them. So I'd recommend you implementing "just work
for me" code as a first step.
> Furthermore I have no experience with GRUB drivers! Is there any
> documentation besides the source code?
No, but you don't need it, since the environment is quite simple. GRUB is just
a single task, and there is little concern about security or performance.
Okuji
next prev parent reply other threads:[~2005-10-19 23:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 6:07 AW: USB kernel driver jochen
2005-10-19 23:37 ` Yoshinori K. Okuji [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-21 6:09 jochen
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=200510200137.35670.okuji@enbug.org \
--to=okuji@enbug.org \
--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.