just an update on this... successfully sent/received a file via obex push to/from a palm zire 72, and successfully established a connection via rfcomm to my notebook. opie locks up when trying to send a file via filemanager, but everything works fine when using obextool push. also, opie never asked me for a pin, so i configured hcid to use security 'auto' instead of 'user'.
On 4/2/07, Michael Kramer <[EMAIL PROTECTED]> wrote:
Hi, > Ive managed to proper initialize the bcm2035 on my a780. > > No kernel hacking was necessary, i just removed ezx-bt.patch from my > series file. The chip works fine without ever touching the 2 gpio > lines(for now). > > The bcm2035 initialization in bluez hciattach is buggy, and i only > managed to attach at 115200 and bdaddr of 000000000000, so i wrote my > own tool, based on a trace of motorola's dload application. For what its worth i have a similar tool (still in rough form) to initialize the bcm2045 on the a1200 (also via stracing the results of the mbtdload app on the a1200) as well as the bcm2035 on the e680/a780 (i'm working on one binary that can detect/handle either) For the a1200 version i can get bluez to start (e.g. hciconfig looks good and 'hcitool scan' works fine) but as soon as i make an interesting connection (rfcomm, bnep, etc) the phone reboots so i'm not sure if its my hardware or something funny going on w/ the se kernel on the a1200. i've been trying to build my own openezx image and rootfs; the image seems to build fine but i cannot seem to get 'bitbake gpe-image' or 'opie-image' to build successfully; can anyone tell me what rootfs image they are building that works w/ the resulting zimage? thanks, mike
-- EOF Daniel Ribeiro