Re: h4350 dmesg

Hello Daniel,

Tuesday, February 27, 2007, 3:47:34 AM, you wrote:

> Paul,

> Here is the output that you requested. The behavior was the same
> regardless of whether the value in h4300_detect.c was 0xaa, 0, or 0xff.
> In all cases the value defaulted to 0.

  Yes, and that means that it's not possible to detect keyboard (==
h4300) in such way ;-I .

> That value only changed when I
> pressed buttons. A single press or holding it down did not make any
> difference. Depending on the button pressed sometimes the high byte
> would be != 0.

  It actually seems to be previous value shifted to the left.

  So, before reducing to ground-level solution - introduce own MTYPE
for h4300, I'm going to try few other ideas still...

> One item of interest is that when I do not use your
> applied patch the series of 6 values that appear between the "spi" lines
> are always -1. However with your patch they change.

  This was actually commit I missed to do, not the patch. Those values
are related to battery.

> I did a fresh
> pull from CVS HEAD before I applied the patch. I've included the output
> of dmesg in all 3 instances.

> To answer your question about the power button I am using the h2200
> version of familiar 0.8.4.

  Ah, no wonder then ;-). In Fam0.8.4/h2200, buttons don't work for
h2200 itself, what to speak about h4000? ;-)

> On other news. The version from cvs head that I am using (last week
> sometime) no longer has the issue with bluetooth. So that seems to be
> cleared up. With the old version I could not actually bring up any
> devices, but with this new version things seem to be working fine. ( I
> haven't gotten any connections yet, but I think that is just me doing it
> wrong. It detects and is detected just fine.)

> Hope this helps,
> Daniel Steen

[]

-- 
Best regards,
 Paul                            mailto:pmiscml_at_gmail.com