On Tuesday 28 November 2006 06:48, Matthias Drochner wrote:
> plunky@rya-online.net said:
> > Not that I can suggest masking such a bug by conforming to a hidden
> > magic number (I wonder if 16 is a generally used value)
>
> I think I have a fix which is not too invasive but still
> halfway clean: kill the code which tries to compute the
> toggle after a short transfer. To fix it to deal with block
> alignment would make it even more expensive; reading
> the updated toggle from the descriptor is cheaper imho.
> The appended patch makes ubt work as far as I could check
> without a device.
>
> best regards
> Matthias

Hi Matthias,

I can confirm your patch working as far as the detection of BT devices is 
concerned - see example below:

barossa: {79} btconfig ubt0
ubt0: bdaddr 00:16:41:57:68:6a flags 0x3<UP,RUNNING>
        num_cmd = 1
        num_acl = 8, acl_mtu = 384
        num_sco = 8, sco_mtu = 64
barossa: {80} btconfig ubt0 inquiry
Device Discovery from device: ubt0 .... 1 response
  1: bdaddr 06:10:09:d1:91:8a
   : name "Samsung WEP200"
   : class: [0x200404] Wearable Headset <Audio>
   : page scan rep mode 0x01
   : page scan period mode 0x02
   : page scan mode 0x00
   : clock offset 13339

I'll test a BT mouse and keyboard at work tomorrow. Its looking very promising 
sofar!!!

Thanks,

cheerio Berndt