[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: RISC OS/ARM port
From: |
Yoshinori K. Okuji |
Subject: |
Re: RISC OS/ARM port |
Date: |
Sun, 23 May 2004 19:03:10 +0200 |
User-agent: |
KMail/1.5.3 |
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