From: Ron Murray <rjmx@rjmx.net>
To: Stephen Crane <steve.crane@rococosoft.com>
Cc: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] bt950 driver?
Date: Tue, 06 Jan 2004 15:13:33 -0500 [thread overview]
Message-ID: <87d69wvnrm.wl%rjmx@rjmx.net> (raw)
In-Reply-To: <1073415724.26094.1110.camel@baroque.rococosoft.com>
At 06 Jan 2004 19:02:04 +0000,
Stephen Crane <steve.crane@rococosoft.com> wrote:
>
> On Tue, 2004-01-06 at 18:02, Ron Murray wrote:
> > I downloaded the driver, but it won't compile against the current
> > Bluez stuff (libs 2.5, utils 2.4, pin 0.21, sdp 1.5). I get lots of
> > errors that way. And it seems that the link to the "Alternate driver
> > for BT2000E Bluetooth cards" from the website is dead.
>
> You don't compile the kernel driver against user-space stuff.
You're right. I took a brief look at the source, noted it was a
standalone C program (no kernel patches) and I wasn't thinking.
Actually, it seems the Zaurus driver is the bt950_cs after
all. Only had the thing two weeks and I'm still trying to get the hang
of it: silly me assumed that a 'locate bt950' command would work.
The goal was, now that I think about it, to run the BT2000 on my
i386 laptop, where I can get at it lots easier and try to troubleshoot
the slow transfer rate on pand problem. I've tried bluetooth transfers
on tha laptop with a USB Tecom BT3030 (same as the server end) and got
a rate of 55k - 60k bytes/sec, which is much nearer to what I'd
expect. I thought I'd try the BT2000 on the laptop and see what
happens, trying to decide whether it's a driver problem or one related
to the Zaurus. That's when I found that the current kernel on that
machine (2.4.22) doesn't have a bt950 driver.
Sorry if I confused you.
> > Any suggestions? Is there any obvious reason why bt950_cs.c won't
> > compile? (I'd post the results of the compile attempt, but there's
> > rather a lot of it and I don't want to needlessly clog up the list).
>
> That would be a help. Even saying what the steps you took were would help.
I think I just found the problem. I was trying to compile it on my
desktop, which I use to generate kernels for all my machines. Seems
that /usr/src/linux was symlinked to the 2.6.0 source. I just tried it
with the 2.4.22 source and it compiled ok (with some grumbling about
type-punned pointers and strict aliasing rules, whatever they are). I
will transfer it to my laptop and see what happens. Doesn't look like
it'll compile under 2.6.0, though.
> For instance:
>
> * download bt950-0.1.tar.gz from holtmann.org
> * get the kernel sources for 2.4.18-pxa3-embedix from, err..., sharp's website?
> * download the Embedix cross-compilation tools from http://community.zaurus.com/project/showfiles.php?group_id=18
> * softlink /usr/src/linux-2.4.18-pxa3-embedix to /usr/src/linux
> * edit bt950/Makefile to use arm-linux-gcc, etc.
> * ...
>
> Steve
> --
> Stephen Crane, Rococo Software Ltd. http://www.rococosoft.com
> steve.crane@rococosoft.com +353-1-6601315 (ext 209)
>
Thanks for your help.
.....Ron
--
Ron Murray (rjmx@rjmx.net)
http://www.rjmx.net/~ron
GPG Public Key Fingerprint: F2C1 FC47 5EF7 0317 133C D66B 8ADA A3C4 D86C 74DE
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-01-06 20:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-06 18:02 [Bluez-users] bt950 driver? Ron Murray
2004-01-06 19:02 ` Stephen Crane
2004-01-06 20:13 ` Ron Murray [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d69wvnrm.wl%rjmx@rjmx.net \
--to=rjmx@rjmx.net \
--cc=bluez-users@lists.sourceforge.net \
--cc=steve.crane@rococosoft.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox