From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/1] devfs: add symlink support
Date: Wed, 6 Mar 2013 09:41:53 +0100 [thread overview]
Message-ID: <20130306084153.GD4401@game.jcrosoft.org> (raw)
In-Reply-To: <20130306081122.GF1906@pengutronix.de>
On 09:11 Wed 06 Mar , Sascha Hauer wrote:
> On Wed, Mar 06, 2013 at 09:01:18AM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > On 08:43 Wed 06 Mar , Sascha Hauer wrote:
> > > On Sat, Feb 16, 2013 at 12:35:53PM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > > > Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
> > > > ---
> > > > fs/devfs.c | 70 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > > > include/driver.h | 1 +
> > > > 2 files changed, 71 insertions(+)
> > >
> > > What's your usecase with this patch? Telling me could increase my
> > > motivation applying it.
> > I use it to handle boot device and tty today
> >
> > so the application part does not care about the real hardware they always have
> > the same device (file) to search
>
> This is in the same league as I wanted to do with persistent device
> names. We should think about this in a more general way.
>
> > >
> > > One thing I see with this patch that the next thing would be to add
> > > directory support to debugfs in which case we might be better off
> > > adding real device nodes and remove the devfs like we have it now
> > > completely.
> > yeah I've the idea to rewrite the devfs completly and the ramfs too
> >
> > as the ramfs should be at vfs level so the devfs will nearly implement nothing
>
> vfs level? You would have to implement one first, we do not have a vfs
> level at all ;)
yeah because today we duplicate too much code so with this we wil reduce the
size of barebox
Best Regards,
J.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2013-03-06 8:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-16 11:35 Jean-Christophe PLAGNIOL-VILLARD
2013-03-04 20:45 ` Jean-Christophe PLAGNIOL-VILLARD
2013-03-06 7:43 ` Sascha Hauer
2013-03-06 8:01 ` Jean-Christophe PLAGNIOL-VILLARD
2013-03-06 8:11 ` Sascha Hauer
2013-03-06 8:41 ` Jean-Christophe PLAGNIOL-VILLARD [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=20130306084153.GD4401@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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