All of lore.kernel.org
 help / color / mirror / Atom feed
* USB kernel driver
@ 2005-10-18 13:38 jochen
  2005-10-18 16:03 ` Marco Gerards
  0 siblings, 1 reply; 6+ messages in thread
From: jochen @ 2005-10-18 13:38 UTC (permalink / raw)
  To: grub-devel

Hi,

can somebody tell me if it is possible to integrate an USB kernel driver
(f. ex. linux-2.6.0\drivers\usb) into GRUB2 to access USB devices?

If possible, it would be great if somebody could tell me what basic steps
I have to do.

Thanks a lot,
Jochen



^ permalink raw reply	[flat|nested] 6+ messages in thread
* AW: USB kernel driver
@ 2005-10-21  6:09 jochen
  2005-10-23  3:06 ` Hollis Blanchard
  0 siblings, 1 reply; 6+ messages in thread
From: jochen @ 2005-10-21  6:09 UTC (permalink / raw)
  To: grub-devel

Hi,

because of not knowing the GRUB 2 architecture very well so far, it would
be nice if you could give me some tipps about
- what does the GRUB development enviroment looks like (means how does
your test PCs look like, how to put updates on the test PC an so on)
- ways to debug my code
- where in source code should I place my test driver

Thx
Jochen

 --- Ursprüngliche Nachricht ---
Datum: 20.10.2005 01:37
Von: The development of GRUB 2 <grub-devel@gnu.org>
An: The development of GRUB 2 <grub-devel@gnu.org>
Betreff: Re: AW: USB kernel driver

> 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
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>




^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2005-10-23  3:06 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-10-18 13:38 USB kernel driver jochen
2005-10-18 16:03 ` Marco Gerards
2005-10-18 16:17   ` Jonas Smedegaard
2005-10-18 16:25     ` Marco Gerards
2005-10-18 16:40       ` Jonas Smedegaard
  -- strict thread matches above, loose matches on Subject: below --
2005-10-21  6:09 AW: " jochen
2005-10-23  3:06 ` Hollis Blanchard

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.