I got the BlueZ...bad. Help...tumnus?

[Ethereal]

Using AmbiCom BT2000E (black, arched top), SL-5600 (PXA255, special kernel), and bluez-zaurus_2.3-2.4.18e-preempt_arm.ipk

# sdptool browse
Inquiring ...
Inquiry failed

The failure message appears immediately (ie it\'s not trying to discover and finding nothing).  Further investigation reveals:

# cardctl status
Socket 0:
  3.3V 16-bit PC Card
  function 0: [ready], [bat dead], [bat low]
Socket 1:
  no card
# cardctl ident
Socket 0:
  product info: \"AmbiCom,Inc\", \"BT2000E\", \"Bluetooth PC/CF Card\"
  manfid: 0x022d, 0x2000
  function: 2 (serial)
Socket 1:
  no product info available
# hciconfig
hci0:   Type: PCCARD
        BD Address: 00:00:00:00:00:00 ACL MTU: 0:0  SCO MTU: 0:0
        DOWN
        RX bytes:0 acl:0 sco:0 events:0 errors:0
        TX bytes:0 acl:0 sco:0 commands:0 errors:0

Finally, hciconfig hci0 up hangs forever...

Everything I\'ve read here suggests the BT2000E should be a drop-in-and-go card, and nothing cardctl or hciconfig tells me hints (to me, at least) why it refuses to initialise...

Help, please!

[tumnus]

Try using the bluez ipks referenced in the BlueZ howto:
http://www.zaurususergroup.com/modules.php...ename=Bluetooth
I don\'t think the 2.3-2.4.18e version of the package is quite working properly.

[Ethereal]

OK, reverted to the bluez-zaurus_2.3-2.4.18d-preempt_arm.ipk package, but I\'m getting the very same output from all four commands, and hciconfig hci0 up still hangs.

What am I doing wrong?

Or, how soon will the no-PXA250-workaround non-preemptive kernel be available?  (I\'ll just keep trying new things until something works?)

[Ethereal]

Sigh.

Reverted to the stock Sharp kernel, installed the bluez-zaurus_2.3-2.4.18d_arm.ipk package, and service discovery works.  Kinda sucks being back at cache-workaround speed, though--especially with a PXA255.

When\'s that new special kernel hitting the street?

[tumnus]

When\'s that new special kernel hitting the street?

When a ZUG admin approves the download... I may have messed up some compatibility with those other modules somewhere (A BT card that refuses to be \'up\'ed is the symptom of this) and that\'s why I\'m going back to a fully compatible kernel.

So the PXA255s come with a kernel that has the PXA250 bug workaround turned on? That\'s stupid.

It would be interesting to see the Dhrystone output for someone\'s 5600 with a PXA255 CPU that has the ROM that it came with.

[Ethereal]

So the PXA255s come with a kernel that has the PXA250 bug workaround turned on? That\'s stupid.

It would be interesting to see the Dhrystone output for someone\'s 5600 with a PXA255 CPU that has the ROM that it came with.

OK, technically this isn\'t the ROM it came with, since I reflashed it with a D/L of the 1.32 ROM from the Sharp website (to get rid of the \"special\" kernel), but the version it shipped with was 1.32, and these Dhrystone results are similar to those \"out of the box.\"


$ cat /proc/version
Linux version 2.4.18-rmk7-pxa3-embedix-021129 (yamade@yampc) (gcc version 2.95.2 19991024 (release)) #1 Tue, 29 Jul 2003 08:52:01 +0900
$ cat /proc/cpuinfo
Processor       : Intel XScale-PXA255 rev 6 (v5l)
BogoMIPS        : 397.31
Features        : swp half thumb fastmult edsp
CPU implementor : 0x69
CPU architecture: 5TE
CPU variant     : 0x0
CPU part        : 0x2d0
CPU revision    : 6
Cache type      : undefined 5
Cache clean     : undefined 5
Cache lockdown  : undefined 5
Cache unified   : harvard
I size          : 16384
I assoc         : 16
I line length   : 32
I sets          : 32
D size          : 16384
D assoc         : 16
D line length   : 32
D sets          : 32

Hardware        : SHARP Poodle
Revision        : 0000
Serial          : 0000000000000000
$ echo 10000000 | ./dhry21

Dhrystone Benchmark, Version 2.1 (Language: C)

Please give the number of runs through the benchmark:
Execution starts, 10000000 runs through Dhrystone
Execution ends

Final values of the variables used in the benchmark:

Int_Glob:            5
        should be:   5
Bool_Glob:           1
        should be:   1
Ch_1_Glob:           A
        should be:   A
Ch_2_Glob:           B
        should be:   B
Arr_1_Glob[8]:       7
        should be:   7
Arr_2_Glob[8][7]:    10000010
        should be:   Number_Of_Runs + 10
Ptr_Glob-]
  Ptr_Comp:          83088
        should be:   (implementation-dependent)
  Discr:             0
        should be:   0
  Enum_Comp:         2
        should be:   2
  Int_Comp:          17
        should be:   17
  Str_Comp:          DHRYSTONE PROGRAM, SOME STRING
        should be:   DHRYSTONE PROGRAM, SOME STRING
Next_Ptr_Glob-]
  Ptr_Comp:          83088
        should be:   (implementation-dependent), same as above
  Discr:             0
        should be:   0
  Enum_Comp:         1
        should be:   1
  Int_Comp:          18
        should be:   18
  Str_Comp:          DHRYSTONE PROGRAM, SOME STRING
        should be:   DHRYSTONE PROGRAM, SOME STRING
Int_1_Loc:           5
        should be:   5
Int_2_Loc:           13
        should be:   13
Int_3_Loc:           7
        should be:   7
Enum_Loc:            1
        should be:   1
Str_1_Loc:           DHRYSTONE PROGRAM, 1\'ST STRING
        should be:   DHRYSTONE PROGRAM, 1\'ST STRING
Str_2_Loc:           DHRYSTONE PROGRAM, 2\'ND STRING
        should be:   DHRYSTONE PROGRAM, 2\'ND STRING

Register option selected?  NO
Microseconds for one run through Dhrystone:     2.9
Dhrystones per Second:                        342818.0
VAX MIPS rating =    195.116


I realise that 195 VAX MIPS is 22% better than the 160 I\'ve seen here on other threads with the PXA250 stock ROM, but I was getting 270+ with the \"special\" kernel, of which I can only attribute 71/400=18%=35 VAX MIPS to the 471 MHz overclock.  That would leave 40+ VAX MIPS to the credit of the pre-emptive patch, and I\'ve read your other threads where you described the pre-emptive gains as trivial, so I assume this kernel has the workaround turned on...

And BTW, tumnus, thank you for all the work you\'ve obviously put into the BlueZ package--this is a perfect example of the control, flexibility, and transparency I was hoping for when I ditched PPC for the Zaurus a couple weeks ago!