From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.33) id 1CWfBT-0007Dw-SH for mharc-grub-devel@gnu.org; Tue, 23 Nov 2004 13:14:36 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CWfBR-0007Df-5Q for grub-devel@gnu.org; Tue, 23 Nov 2004 13:14:33 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CWfBQ-0007DG-Dh for grub-devel@gnu.org; Tue, 23 Nov 2004 13:14:32 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CWfBQ-0007DD-A8 for grub-devel@gnu.org; Tue, 23 Nov 2004 13:14:32 -0500 Received: from [145.74.66.11] (helo=mail-cn.han.nl) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CWf1z-0002OB-MR for grub-devel@gnu.org; Tue, 23 Nov 2004 13:04:48 -0500 Received: from localhost (charlie.han.nl [145.74.66.9]) by mail-cn.han.nl (Postfix) with ESMTP id 358D087A3 for ; Tue, 23 Nov 2004 19:04:47 +0100 (CET) Received: from mail-cn.han.nl ([145.74.66.11]) by localhost (charlie.han.nl [145.74.66.9]) (amavisd-new, port 10024) with ESMTP id 17318-01 for ; Tue, 23 Nov 2004 19:04:45 +0100 (CET) Received: from mail1.han.nl (mail1.han.nl [145.74.103.11]) by mail-cn.han.nl (Postfix) with ESMTP id 1658F8D66 for ; Tue, 23 Nov 2004 19:04:45 +0100 (CET) Received: from marco.marco-g.com (mgerards.xs4all.nl [82.92.27.129]) by mail1.han.nl (Postfix) with ESMTP id C6729C045 for ; Tue, 23 Nov 2004 19:04:44 +0100 (CET) Mail-Copies-To: metgerards@student.han.nl To: The development of GRUB 2 References: <200411231701.07309.T.E.Baldwin99@members.leeds.ac.uk> From: Marco Gerards Date: Tue, 23 Nov 2004 18:03:28 +0000 In-Reply-To: <200411231701.07309.T.E.Baldwin99@members.leeds.ac.uk> (Timothy Baldwin's message of "Tue, 23 Nov 2004 17:00:56 +0000") Message-ID: <87act8jvdb.fsf@marco.marco-g.com> User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new@vscan-cn.han.nl Subject: Re: RISC OS port X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 18:14:33 -0000 Timothy Baldwin writes: > During the past few months I have been working on a port to RISC OS an ARM > processors. It has reached the point where it can boot Linux, and IMO is > nearly ready to be included in CVS. It does not support to booting of > compressed Linux kernels as the decompression code has not been updated to > the new parameter passing convention. That is really nice! Can you get the GRUB menu to work, etc? How about module loading? I noticed you wrote some code for that too... I noticed you used a lot of assembler. Isn't it possible to minimize the use of assembler somehow? If that is not possible, no problem. > It includes support to access filesystems though the RISC OS filesystem API, > which error numbers should be returned in case of an error? I remember a discussion about this... I noticed you implemented some disk access code. Is it possible to access GNU/Linux partitions? Is it possible to write support for the filesystem used on RISC OS? I can help you with that, if you want that. > The other ends which need tidying up before inclusion in CVS are: > Write a changelog > Fix copyright notices > Write support for ARMv4 (eg. StrongARM) and ARMv5 processors (eg. XScale). > Fix the arrow keys Nice. Can you please split up the patch somehow? And please make sure you follow the GCS. That is an important requirement for patches for GRUB. If you can do that, it will be easier for me to proof read the patch(es) before it can be applied. > What codes should the arrow keys return? The openfirmware and PC drivers > disagree. Perhaps it will be easier if there is one file that defines the available keys. Now it is arch dependent. Anyway, I remember there is some room for improvement... > > TODO list: > Support access to RISC OS files not on (or symlinked from) devices supported > by Grub. Don't worry about cross filesystem symlinks. > Possibly support attaching modules to the kernel. Attaching modules to the kernel? Thanks, Marco