> Sorry that it took so long, but I had some code to commit. ;)
>
> > "Waldemar Kornewald" <Waldemar.Kornewald@xxxxxx> wrote:
> > > But we still edit driver_settings, can we?
> >
> > What do you mean with this? driver_settings can be written
> > manually,
> > they can be programmatically edited, and written back to a file
> > easily
> > with the new API extensions.
>
> So, is the extended driver settings API finished (that one listed on
> the
> kernel team task list)?
As featured on kernel team task page, it's not fully finished.
But it's really short: understand, already usable.
Something I planning to do shortly on new_stack/* implementation...
> Or do you plan to extended it to support flattening BMessages in
> driver_setttings format?
This suggestion remembered one made by mmu_man.
In fact, it's more a BMessage topic than driver_settings.
Anyway, using BMessage from kernel land is not avaible under R5, unless
we can come
with a 100% binary compatible and usable from kernel space BMessage
implementation.
Until, we can't use BMessages for handling our network settings...
> GUI programming eats up too much time that we do not have.
If it was only "GUI programming", or even just "programming" :-\
-Philippe
--
Fortune Cookie Says:
"Microwave oven? Whaddya mean, it's a microwave oven? I've been
watching Channel 4 on the thing for two weeks."
