Hello Gerhard,
Monday, July 2, 2007, 12:26:02 AM, you wrote:
> Hello Anton,
> I had already put a few printk lines into hamcop_base without realizing that
> there are pr_debug statements available and I had only to define DEBUG. Thank
> you for the tip.
As Anton suggested, you need to add DEBUG to leds-hamcop.c, not
hamcop_base.
> The result is:
> Switching on Bluetooth gives me the lines:
> hamcop_set_led: LED number 2, 1, 31
> hamcop_set_led: LED number 2, 0, 0
> The blue LED is flashing!
Bluetooth LED is working just because it access hamcop in old adhoc
way, that needs to be fixed once leds-hamcop is debugged.
> Putting h2200 into craddle or give power to the plug I see that the battery
> gets loaded but nothing happens. No LED is flashing, no dmesg output is
> created in leds-hamcop.c.
> leds-hamcop.c seems not to be the problem.
Based on your report, and answering your question in another mail,
leds-hamcop exactly appears to be a culprit. It's what registers entries
in /sys/class/leds/. So, please debug it - there're lots of printk's
already.
> Any further idea where to look?
> Sorry for all those stupid questions and thx in advance.
> Gerhard
[]
-- Best regards, Paul mailto:pmiscml_at_gmail.comReceived on Sun Jul 01 2007 - 19:21:52 EDT
This archive was generated by hypermail 2.2.0 : Sun Jul 01 2007 - 19:22:09 EDT