public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: sl@whiskey.fireplug.net (Stuart Lynne)
To: mtd@infradead.org
Subject: Re: building M-Sys DOC driver as a module
Date: 24 Jul 2000 16:43:53 -0700	[thread overview]
Message-ID: <8likbp$cvi$1@whiskey.fireplug.net> (raw)
In-Reply-To: Pine.LNX.4.21.0007211654230.22633-100000@alpha1.cygnus.co.uk

In article <Pine.LNX.4.21.0007211654230.22633-100000@alpha1.cygnus.co.uk>,
David Woodhouse <dwmw2@alpha1.cygnus.co.uk> wrote:
>On Fri, 21 Jul 2000, Trevor Woolven wrote:
>
>> Ok, IMHO using an initrd doesn't actually cost you too much, the bulk
>> of it is used to store the kernel which has to go somewhere, right? I
>> haven't done a comparison on the relative sizes of a kernel with the
>> driver compiled in vs one without to measure what the difference is
>> but that would be quite a simple thing to do - especially if space was
>> getting tight.
>
>initrd requires block deive support. I want to cut that entirely, too.

Hmmm... for what, are you thinking RAM Disk....

I hope to get the initrd support working against ramfs sometime this summer.

-- 
                                            __O 
Fireplug - a Lineo company                _-\<,_ 
PGP Fingerprint: 28 E2 A0 15 99 62 9A 00 (_)/ (_) 88 EC A3 EE 2D 1C 15 68
Stuart Lynne <sl@fireplug.net>       www.fireplug.net        604-461-7532


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

  reply	other threads:[~2000-07-24 23:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-19 22:35 building M-Sys DOC driver as a module Matt Hortman
2000-07-20  9:32 ` Trevor Woolven
2000-07-20 14:54   ` Adi Linden
2000-07-20 15:07     ` David Woodhouse
2000-07-21  1:29       ` Ollie Lho
2000-07-21 15:01         ` David Woodhouse
2000-07-21  9:58       ` Trevor Woolven
2000-07-21 16:03         ` David Woodhouse
2000-07-24 23:43           ` Stuart Lynne [this message]
2000-07-24 23:41         ` Stuart Lynne

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='8likbp$cvi$1@whiskey.fireplug.net' \
    --to=sl@whiskey.fireplug.net \
    --cc=mtd@infradead.org \
    --cc=sl@fireplug.net \
    /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