Re: Another 1.2.3 candidate bug - #1838

Hello Dmitriy,

Monday, February 12, 2007, 11:06:07 PM, you wrote:

> Erik,
> While this is a good idea, but the patch actually must be accompanied by
> the other one that allows setting up these parameters in the OPIE
> Bluetooth Manager. Before the second part of the work has not been done,
> this patch IMHO, should not be applied.

  Let's see. /etc/sysconf/bluetooth contains system
configuration, i.e. something which is assumed available and
configured properly by external means. In OpenEmbedded land (true for
Familiar too) this is achieved by blueprobe script (maintained by GPE
project) which runs once after install and creates it from machine =>
DB params database. We also known that many handhelds have builtin BT,
and people don't really use CF BT cards often (and there's still no
support for SDIO).

  So, /etc/sysconf/bluetooth allows to cheaply support bunch of
built-in BT handhelds (including future), is pre-available, static for
a given handheld, and its editing is advanced feature. Under this
conditions, it's hardly wise to depend its usage on ability to edit it
in GUI.

> Regards,

> Dmitriy


-- 
Best regards,
 Paul                            mailto:[email protected]

_______________________________________________

http://opie.handhelds.org/cgi-bin/moin.cgi/DeveloperWikiIndex

Opie-devel mailing list
[email protected]
https://handhelds.org/mailman/listinfo/opie-devel