From: "John Stoffel" <john@stoffel.org>
To: Philippe De Muyter <phdm@macqel.be>
Cc: Tomasz Chmielewski <mangoo@wpkg.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux kernel without file system
Date: Wed, 14 Jan 2009 12:02:49 -0500 [thread overview]
Message-ID: <18798.6841.172442.17982@stoffel.org> (raw)
In-Reply-To: <20090114093422.GA9771@frolo.macqel>
>>>>> "Philippe" == Philippe De Muyter <phdm@macqel.be> writes:
Philippe> On Wed, Jan 14, 2009 at 09:46:48AM +0100, Tomasz Chmielewski wrote:
>>> I need to design a very small embedded system that must only control
>>> one ethernet port and two serial lines and must fit in a very small flash
>>> memory. So I thought about replacing the call to /etc/init by my
>>> application
>>> program and removing all the file-system part of linux.
>>> Is that doable ?
>>> Is there a 'standard' way of doing that ?
>>> The first problem I see is accessing my serial lines. How could I do that
>>> without using open("/dev/ttySx"), which requires a file system ?
>>> Is there a way to access devices that does not require a file-system ?
>>
>> You could put everything in initramfs (and embed it in the kernel).
Philippe> Actually, I was thinking about reducing the footprint of my
Philippe> kernel by removing all the fs-related system calls, so the
Philippe> problem is not where the file-system is, but how to access
Philippe> (serial) devices without giving their "/dev/..." name.
Does it have to be linux? I've been playing with Arduino boards
(http://www.adafruit.com) lately and they have ethernet modules,
serial libraries, etc. All on a small small chip. Well, the ethernet
is a daughter board, but they're still pretty small.
Depends on how general purpose you need to make this device and what
you're trying to accomplish. Maybe you need to give people a better
idea of what you're trying to do, instead of assuming you need Linux
and trying to shoe-horn it into a really tiny space.
Cheers,
John
next prev parent reply other threads:[~2009-01-14 17:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 8:46 Tomasz Chmielewski
2009-01-14 9:34 ` Philippe De Muyter
2009-01-14 9:52 ` Xavier Bestel
2009-01-14 10:18 ` Philippe De Muyter
2009-01-14 14:27 ` Rogan Dawes
2009-01-14 14:52 ` Philippe De Muyter
2009-01-14 14:57 ` Rogan Dawes
2009-01-14 15:24 ` Philippe De Muyter
2009-01-14 15:31 ` Rogan Dawes
2009-01-15 18:06 ` Arnd Bergmann
2009-01-14 10:34 ` Kay Sievers
2009-01-14 13:49 ` Xavier Bestel
2009-01-17 19:38 ` Enrico Weigelt
2009-01-14 11:59 ` Arnd Bergmann
2009-01-14 12:18 ` Philippe De Muyter
2009-01-14 14:27 ` David Newall
2009-01-14 14:49 ` Philippe De Muyter
2009-01-14 15:14 ` David Newall
2009-01-14 17:02 ` John Stoffel [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-14 8:30 Philippe De Muyter
2009-01-14 10:15 ` Alan Cox
2009-01-15 15:34 ` Enrico Weigelt
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=18798.6841.172442.17982@stoffel.org \
--to=john@stoffel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mangoo@wpkg.org \
--cc=phdm@macqel.be \
/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
Powered by JetHome