From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] Add Menu Framework
Date: Fri, 20 Aug 2010 08:51:39 +0200 [thread overview]
Message-ID: <20100820065139.GG8693@game.jcrosoft.org> (raw)
In-Reply-To: <20100820063822.GH27749@pengutronix.de>
> > >
> > > - commands should always return positive error codes. A good practice is
> > > to pass -E* values up to do_menu, use strerror() to print the error
> > > code and return 1 afterwards.
> > I agree but but of the time there is no -E* related to this Framework
> >
> > so do u want to create them?
>
> No. The use of strerror might not be appropriate here, but all functions
> used should return some error value instead of -1, with -EINVAL as
> fallback when no better value can be found.
ok
>
> > >
> > > There is a 'break' missing here.
> > >
> > fix
> > > > + cm.action = action_add;
> > > > + break;
> > > > + case 'r':
> > > > + cm.action = action_remove;
> > > > + break;
> > > > + case 'c':
> > > > + cm.command = optarg;
> > > > + break;
> > >
> > > Thank you for this work. I really appreciate it ;)
> > Your welcome
> > My goal was to make the bootloader more easy to use for end user and
> > device without keyboard
>
> Do you know openmoko? They also have a menu in U-Boot, but it's more or
> less hardcoded to their exact needs.
yeah I known, Denk force me to take a look at it when I send my patch to u-boot
ML but as you said everything is hardcoded and very limited
and for the record my code is NOT based on there work :)
so as I said him I do not like there stuff and think this one is as you said
flexible and simple
> >
> > I plan to have this also via FrameBuffer and with a background image
> > so maybe barebox could replace grub & co aneday :)
>
> A long way to go ;)
but a good target :-)
Best Regards,
J.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2010-08-20 6:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 3:53 Jean-Christophe PLAGNIOL-VILLARD
2010-08-19 8:29 ` Sascha Hauer
2010-08-20 3:21 ` Jean-Christophe PLAGNIOL-VILLARD
2010-08-20 6:38 ` Sascha Hauer
2010-08-20 6:51 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2010-08-20 7:09 ` Robert Schwebel
2010-08-20 8:18 ` Jean-Christophe PLAGNIOL-VILLARD
2010-08-20 8:22 ` [PATCH 1/2 v2] " Jean-Christophe PLAGNIOL-VILLARD
2010-08-20 8:22 ` [PATCH 2/2] Menu/cmd: add sub menu entry command support Jean-Christophe PLAGNIOL-VILLARD
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=20100820065139.GG8693@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