hmmm.....I just compiled a current build root (r1174) but instead of using the patch form that revision I droped in the
the bluez folder from r1155 and it built ok...so I'll test that tonight and see how it goes.

On 11/21/06, Paul Pigg <masterpigg@gmail.com> wrote:
Jesse,

I had the same question myself, so figured I'd investigate.  Right after (er, may be downstream a few lines when booting) the "Not a PBA31307" message is a line showing all the bytes of the response.  In the older thread, Ben had this in his line:

0x04 0x0e 0x08 0x01 0x05 0xfc 0x00 0x50 0x57 0x5b 0x05  ttyS3 hcidh4_recv:
Mine said the same thing (rev 1170).

so,
resp[6] = 0x00
resp[7] = 0x50
resp[8] = 0x57
resp[9] = 0x5b
resp[10] = 0x05


so, I changed that offending if statement (in the patch file) from

if(resp[6] == 0x0 && (resp[7]&0xf) == 0x5 && resp[9] == 0x05) // PBA31307 confirmed

To
if(resp[6] == 0x0 && (resp[7]&0xf0) == 0x50 && resp[10] == 0x05) // PBA31307 confirmed



This worked.

Now, this is just guessing on my part on where the error is, and I'm not sure how minor revisions of the chip/firmware may affect these bytes.  That may be why byte 7 was masked...?  On that note, maybe the 'correct' fix would be:
if(resp[6] == 0x0 && (resp[7]&0xf0) == 0x50 && (resp[9]&0xf0) == 0x50) // PBA31307 confirmed

If anyone has more insight into this, that'd be great.  I only know (from the comments in the patch) what the bytes represent (LM FW Version and BB FW Version).  Regardless, it'd be nice to see this patched in the next revision.  Now, if I could just figure out why the newer buildroot has much higher bluetooth latency than the older revisions... but, that's for another thread, after I get some more stats.

--Paul Pigg

On 11/21/06, Jesse Welling <jesse.welling@gmail.com > wrote:
Yes I recompiled the kernel but the *physical module* is the old
PBA31307 and not the new (RoHS compliant) PBA31308.
Problem is that the patch applied now makes the kernel
complain that it can't find the right bluetooth *physical module*.

I guess I'm going to side skirt the issue by using r1155 of the build root
because it looks like the last one before the addition of the patch.

To Craig:
Would droping in an old buez package directory (/trunk/package/bluez/) from pre 1155 over the new
buildroot break any thing?


On 11/21/06, Mario A. Spinthiras < mario@netway.com.cy> wrote:
Jesse Welling wrote:
> Hi I was trying to update my kernal from 2.6.16 to 2.6.18 and I ran
> into the PBA31308 vs PBA31307 problem
> and my BlueTooth no longer works. Some one mentioned a fix but it was
> kinda vague. It told
> me what to change in the bluez-something-something-PBA31308.patch
> (which I found) but not what to change it *to*...
> can any one enlighten me? IIRC resp[6], resp[7] and resp[9] was
> mentioned. Does any one know what those values should be?
> Here is the error:
>
>     Starting Bluetooth subsystem:Trying baud rate 57600...
>     Set (GPIO,out,clear) via /proc/gpio/GPIO7
>     Set (GPIO,out,set) via /proc/gpio/GPIO7
>     Got response after reset... gobbling
>     No response from BT module
>     Trying baud rate 921600...
>     Set (GPIO,out,clear) via /proc/gpio/GPIO7
>     Set (GPIO,out,set) via /proc/gpio/GPIO7
>     Got response after reset... gobbling
>     Error reading response: Success
>     Trying baud rate 115200...
>     Set (GPIO,out,clear) via /proc/gpio/GPIO7
>     Set (GPIO,out,set) via /proc/gpio/GPIO7
>     Got response after reset... gobbling
>     Detected bluetooth module at 115200 baud
>     Got: status=0x00, hci_ver=0x01, hci_rev=0x0750, lmp_ver=0x02,
>     manuf=0x0009, lmp_subver=0x0750
>     Not a PBA31307
>
>
> Thanks for the help!
>
>
> --
>         -Jesse W.
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> ------------------------------------------------------------------------
>
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>
Kernel you mean ?

Did you include the modules for your hw ?

If not recompile with your hw supported modules.

M.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net 's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
gumstix-users mailing list
gumstix-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gumstix-users



--
        -Jesse W.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

_______________________________________________
gumstix-users mailing list
gumstix-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gumstix-users




-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

_______________________________________________
gumstix-users mailing list
gumstix-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gumstix-users





--
        -Jesse W.