Grub Development Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Is Disk-on-Chip (DOC) support planned?
Date: Tue, 27 Sep 2005 21:58:32 +0200	[thread overview]
Message-ID: <87d5mu1dw7.fsf@student.han.nl> (raw)
In-Reply-To: <433937D7.30748.AAAC1F@localhost> (Joseph M. Dupre's message of "Tue, 27 Sep 2005 12:15:19 -0700")

"Joseph M Dupre (AVAB Inc.)" <dupre@avab.com> writes:

> Q: Is there any intent to incorporate Disk-on-Chip support within 
> future releases of grub?
>
> For a while there was a patch maintained by the Linux MTD developers 
> (http://www.linux-mtd.infradead.org) to enable GRUB to boot from a 
> Disk-on-Chip (DOC) flash device.  The most recent patch was for grub-
> 2003-11-10.  There appears to be multiple dependency problems which 
> makes using this patch today difficult.  (Specific versions of GCC, 
> autoconf and automake are required to build).
>
> If there was a DOC patch that worked with the curent grub CVS, would 
> you consider incorporating it? 

The patch you are talking about is for GRUB Legacy, this mailinglist
is about GRUB 2.

Personally I wouldn't mind such support.  Can you please describe what
this support means?  I assume it is just a filesystem that needs to be
supported?  I don't have the hardware, but implementing the filesystem
should be easy if someone can give me an image of a filesystem.

--
Marco





  reply	other threads:[~2005-09-27 20:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-27 19:15 Is Disk-on-Chip (DOC) support planned? Joseph M Dupre (AVAB Inc.)
2005-09-27 19:58 ` Marco Gerards [this message]
     [not found] <200509281107.j8SB7MYu026483@ns1.pwrseries.com>
2005-09-28 17:19 ` Joseph M Dupre (AVAB Inc.)

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=87d5mu1dw7.fsf@student.han.nl \
    --to=metgerards@student.han.nl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox