Re: Charge and bluetooth indicators. irattach script

Hello Eugeny,

Thursday, March 1, 2007, 12:21:00 AM, you wrote:

> Hello all.

> 1. I think there is a mistake in /etc/init.d/irattach script, IR port
> should be set to /dev/ttyS2 or /dev/tts/2 instead of bt /dev/ttyS1.

> With /dev/ttyS1, irattach is trying to power on bluetooth.

  Very likely. Both Familiar and OE contain bunch of bugs and
misfeatures for handling external devices. I have patch like above in
my OE.dev tree. But the real issue with init.d/irattach is that it
shouldn't run on system init, but only on demand (when user enables
IrDA). So, this (and few other) issues should be brought on the OE
list as RFC, discussed, and then fixed.

> 2. I wrote support for bluetooth indicator and fixed some bugs in
> charge indicator code. I think, now it is ready for use.

  Thanks, BT indicator seems to be ok. I'll check it a bit later and
commit. As for battery indicator, it's still not ideal. That's mostly
because you've caught in the midst of general battery support changes
in the entire tree, and its hard to grasp immediately what's
deprecated and what needs some work to fully shine.

  Well, so we have ds2760_battery driver which supports handhelds with
DS2760 chip, and offers interface to plug in charge indication, etc.
While that driver still needs some work, it's good lead to follow.
h4000 doesn't use ds2760_battery, instead there's newly written
adc_battery which was tested now to capture the most functionality of
adhoc h4000_batt driver, so h4000_batt will be deprecated, and
adc_battery needs to be extended to offer functionality on par with
ds2760_battery.

  If you'd be interested to implement that, that would be appreciated,
because I have bunch of stuff in my queue. Either way, your work is
much appreciated, and for sure will be the base for LEDs support.

> 3. Seems like, OPIE couldn't power on/off bluetooth and irda on h4000.
> Also there isn't any LED and cpufreq support for 2.6 kernels. Are there
> any workarounds, or we need to rewrite opie bluetooth/IRda code ?

  We need to rewrite OPIE code, no doubts - it plain sucks ;-). That
said, both IrDA and BT can be activated for me in OE.dev. IrDA
actually works pretty well - I can exchange OBEX stuff to phone and
vice versa. As for BT, it's pretty broken. The breakage starts with
the fact that OE.dev switched to bluez 3.x, and it has unhealthy
dependency on dbus for authentication. There're also segfaults and
hangs in OPIE bluetooth apps themselves.

  All in all, if you're interested in dealing with all this stuff, I'd
suggest you decide with what system you will deal. As maintainer of
OPIE packages in OE.dev, I may invite you to work on improving
support there, but I have to say there're lots to do. But your
submissions will be welcomes and appreciated. Otherwise, Familiar
needs help and work too, of course (except that it's unclear well
h4000 will be supported there).

-- 
Best regards,
 Paul                            mailto:pmiscml_at_gmail.com