All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: RISC OS/ARM port
Date: Sun, 23 May 2004 19:03:10 +0200	[thread overview]
Message-ID: <200405231903.10997.okuji@enbug.org> (raw)
In-Reply-To: <200405221621.51788.T.E.Baldwin99@members.leeds.ac.uk>

On Saturday 22 May 2004 17:21, Timothy Baldwin wrote:
> How should console errors be handled? Currently they are fatal, and
> won't happen unless the console is redirected (assuming USB drivers
> don't complain).

I don't know. Probably there is no other way than treating them as fatal 
errors.

> Currently in the design of GRUB 2 there is an incorrect asumption
> that filing systems are either based on disks or networks. I propose
> to rectify this whilst keeping code size down by:
>
> Creating a struct grub_fs_device_driver, which contains a pointer to
> either struct grub_disk_dev or struct grub_net_dev, and maintain a
> single linked list of disk drivers, net drivers, and standalone
> filing systems.
>
> Convert struct grub_device from pointers to a unoin to simplify the
> code by removing memory allocations.

Could you elaborate on your idea more? What is "standalone filing 
systems"? How do they work?

Thanks,
Okuji




  reply	other threads:[~2004-05-23 17:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-22 15:21 RISC OS/ARM port Timothy Baldwin
2004-05-23 17:03 ` Yoshinori K. Okuji [this message]
2004-05-23 17:24   ` Stefan Reinauer
2004-05-27 22:22   ` Timothy Baldwin
2004-05-28 14:48     ` Marco Gerards
2004-05-31 11:09       ` Timothy Baldwin
2004-06-01 17:30         ` Yoshinori K. Okuji
2004-06-08 15:21           ` Timothy Baldwin
  -- strict thread matches above, loose matches on Subject: below --
2004-05-22 12:46 Timothy Baldwin

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=200405231903.10997.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.