From: David Woodhouse <dwmw2@infradead.org>
To: Patrick Higgins <phiggins@transzap.com>
Cc: mtd@infradead.org
Subject: Re: Initrd?
Date: Thu, 11 May 2000 09:42:36 +0100 [thread overview]
Message-ID: <28657.958034556@devel2.axiom.internal> (raw)
In-Reply-To: <Pine.LNX.4.21.0005101335290.1556-100000@phiggins.transzap.com>
phiggins@transzap.com said:
> Has anyone tried to get the M-Systems driver to work with initrd,
> enabling a Disk on Chip to be the root device without (illegally)
> statically linking the driver?
A reasonable short term solution, but in smaller embedded devices, the
extra code & data required for the ramdisk and initrd support are quite a
significant overhead which it would be nice to render unnecessary.
phiggins@transzap.com said:
> Would the bootloader require special knowledge of Disk on Chip to do
> this?
Not if you still have the M-Systems' firmware in the DiskOnChip, which
emulates the BIOS disk calls. Which you probably do.
phiggins@transzap.com said:
> I would like to use the free drivers that you are developing, but I'm
> afraid they won't be completed in time for my needs. Any suggestions?
Help with the code and/or testing? :) I'm doing my best to arrange matters
so that I get to spend 100% of my time on MTD, but it's taking me a while to
manage that - for some reason, the CEO wants me to spend time on things
which are immediately relevant to company business :)
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-05-11 8:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-10 19:41 Initrd? Patrick Higgins
2000-05-10 22:55 ` Initrd? Stuart Lynne
2000-05-11 8:42 ` David Woodhouse [this message]
2000-05-11 18:00 ` Initrd? Dvir Oren
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=28657.958034556@devel2.axiom.internal \
--to=dwmw2@infradead.org \
--cc=mtd@infradead.org \
--cc=phiggins@transzap.com \
/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