Re: bluetooth, buttons, and other fun

Hello Eugeny,

Thursday, March 8, 2007, 5:09:14 PM, you wrote:

> Hello Paul,

> 1.
>> I may assure you that nothing in kernel button handling changed
>> since September, when common buttonmap support was implemented.
>>
> One more idea: when I had problems with power button, my kernel was
> compiled without 4350 keyboard module.

  I assume you have h4150?

> 2.

>> 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.
>>
> Are there any other handhelds with same battery controller?

> How can I use adc_battery instead of h4000_battery?
> I see, we need to copy some code from h4000_batt to adc_battery
> implementation
> and should rewrite h4000_batt to use adc_battery? Or not?

  I'm glad you try to find answers yourself. I may only say that
with few contributors, we'll quickly finish h4000 port ;-).

> 3.
> And a question about OPIE and OE.dev.

> If I want,for example, to implement support for CPU frequency scaling
> and LED's in OPIE, I should use OE.dev to prepare patches to opie cvs
> code? Or I should working with OPIE CVS on handhelds.org instead?

  OE is build system, used to integrate lots of software packages into
a distribution. It *can* handle patches to individual software
components, but it is discouraged to use it as a storage place for
functionality-related patches. All such patches should be submitted to
project upstream for inclusion. So yes, you should be in contact with
opie-devel mailing list first of all.

>
> ---
> Best wishes,
> Eugeny A Boger

-- 
Best regards,
 Paul                            mailto:pmiscml_at_gmail.com