All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe De Muyter <phdm@macqel.be>
To: Xavier Bestel <xavier.bestel@free.fr>
Cc: Tomasz Chmielewski <mangoo@wpkg.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux kernel without file system
Date: Wed, 14 Jan 2009 11:18:28 +0100	[thread overview]
Message-ID: <20090114101828.GA15141@frolo.macqel> (raw)
In-Reply-To: <1231926744.11907.12.camel@skunk>

On Wed, Jan 14, 2009 at 10:52:24AM +0100, Xavier Bestel wrote:
> 
> On Wed, 2009-01-14 at 10:34 +0100, Philippe De Muyter wrote:
> > 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).
> > 
> > Actually, I was thinking about reducing the footprint of my kernel by
> > removing all the fs-related system calls, so the problem is not where
> > the file-system is, but how to access (serial) devices without giving their
> > "/dev/..." name.
> 
> You can still mount sysfs somewhere and access the device nodes from
> there.

Keeping thinking about it, I now think that my 'application program'
(basically a serial-to-ethernet converter) should be a kernel thread,
because of the small memory constraints.

The question is thus how to access the serial lines from a kernel thread.

Philippe

  reply	other threads:[~2009-01-14 10:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14  8:46 linux kernel without file system 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 [this message]
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
  -- 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=20090114101828.GA15141@frolo.macqel \
    --to=phdm@macqel.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mangoo@wpkg.org \
    --cc=xavier.bestel@free.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.