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:41:52 -0700 [thread overview]
Message-ID: <8lik80$ctk$1@whiskey.fireplug.net> (raw)
In-Reply-To: 39781EAE.58A56DA3@zentropix.com
In article <39781EAE.58A56DA3@zentropix.com>,
Trevor Woolven <trevw@zentropix.com> wrote:
>This is a multi-part message in MIME format.
>--------------37FCF4E0556161DE8012872E
>Content-Type: text/plain; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>
>David Woodhouse wrote:
>
>> On Thu, 20 Jul 2000, Adi Linden wrote:
>>
>> > I'd be quite interested in the modular DOC driver as well. So far I've
>> > seen it talked about quite a bit but never seen it.
>> >
>> > I produces a 2.2.14 kernel patch for the M-Systems DOC driver but that's
>> > in violation of GPL for a production environment...
>>
>> Modular drivers and initrd are a horrible waste of space in an embedded
>> system, IMO. Far better to cut out module support completely, and even
>> also block device support, putting JFFS on the DiskOnChip instead of NFTL.
>
>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
The kernel is separate from the initrd file.
The overhead per module for loading it as a module instead of compiling it
in to the kernel is roughly about 2kb.
The initrd file must contain enough to load the module. In theory this means
a statically linked shell, statically linked insmod, a short script and your
modules. Gzipped this ends up around a coupld hundred kb.
It may be possible to used a stripped down busy box that knows enough
to do this.
>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. I agree that there's a
>bit of
>a waste having a DOS partition on the DOC to boot syslinux from but neither
>LILO nor GRUB are perfect either.
>
>I agree that getting JFFS on DOC is a good thing but when will it happen?
>I don't see the M-Systems driver being the driver of choice in the long run,
>most people would much rather use a GPL one and that's where MTD wins big
>time!
You also have to support booting from it..... If/when grub can be coaxed into
doing that reliably then it starts to sound interesting.
--
__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
prev parent reply other threads:[~2000-07-24 23:41 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
2000-07-24 23:41 ` Stuart Lynne [this message]
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='8lik80$ctk$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