This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/baseband-devel@lists.osmocom.org/.
Harald Welte laforge at gnumonks.orgHi Andreas,
On Wed, May 12, 2010 at 02:58:36PM +0200, Andreas.Eversberg wrote:
> my idea: later these VTY command structure may be used for the phone's
> menu (up - down - enter - escape), if compiled appropiate. also: if
> layer 3 is running on the phone, the serial port could directly connect
> to the VTY, so the phone gets a console interface for debugging and
> faster configuration.
I really like the idea, but I think we need to move to something much more
flexible than the current VTY data structures to make that work. The
existing VTY code is a pretty useful tool, but it has quite some limitations
and shortcomings that cannot be fixed quickly. One of its uglinesses is
how you specify the context sensitive help strings (as multi-line strings
with \n in them, part of what you pass to DEFUN). Other aspects are
that all new nodes need to be hacked into the VTY core and you cannot
define them yourself (see the NS_NODE that I have just introduced 2 days
ago).
Once those issues are resolved, the VTY code could become a standard
feature of libosmocore, and we wouldn't need to hack that code while
still implementing any command line menu structure we'd like.
--
- Harald Welte <laforge at gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)