From: Marcel Holtmann <marcel@holtmann.org>
To: leidenfrost@corscience.de
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Bluetooth on a MIPS-System
Date: Thu, 07 Oct 2004 13:07:53 +0200 [thread overview]
Message-ID: <1097147273.7325.26.camel@pegasus> (raw)
In-Reply-To: <41651D72.7040806@corscience.de>
Hi Thomas,
> hope I can get a little help here after some days of vainly trying.
> Currently I want to make my MIPS-System (AMD-Alchemy) working with
> Bluetooth. Support for Bluetooth was implemented as a Module in Kernel
> 2.4.21 (without any patch).
I don't have a MIPS test system, so I can't really help here. Feel free
to send me one ;)
> Then I crosscompiled the BlueZ-Libs & - Utils, and hcitool says:
>
> "Device ist not available: Address Family not supported by protocol",
> altough there is a Bluetooth-USB-Dongle present or not. Before it was:
> "Device ist not available: Success", so I think I am one step closer
> than before.
>
> lsmod says:
>
> Module Size Used by Not tainted
> saa7113 2540 0 (unused)
> sii164 2980 0 (unused)
> i2c-mb86290 1620 0 (unused)
> i2c-algo-mb86290 2828 1 [i2c-mb86290]
> i2c-dev 4428 0 (unused)
> i2c-core 15504 0 [saa7113 sii164 i2c-algo-mb86290 i2c-dev]
> ide-cs 3888 1
> hostap 96208 0
> ds 8012 1 [ide-cs]
> au1x00_ss 8084 1
> pcmcia_core 42176 0 [ide-cs ds au1x00_ss]
>
>
> but nothing like:
>
> l2cap, hci_usb, bluez
>
> doing # modprobe l2cap.o in /bin results:
> insmod: l2cap.o: no module by that name found
> modprobe: failed to load module l2cap.o
Do a "modprobe hci_usb" and then check with "dmesg" what happens.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-10-07 11:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 10:41 [Bluez-users] Bluetooth on a MIPS-System Thomas Leidenfrost
2004-10-07 11:07 ` Marcel Holtmann [this message]
2004-10-07 11:36 ` Thomas Leidenfrost
2004-10-07 12:41 ` Marcel Holtmann
2004-10-07 13:10 ` Thomas Leidenfrost
2004-10-07 13:14 ` Marcel Holtmann
2004-10-07 14:06 ` Thomas Leidenfrost
2004-10-07 14:17 ` Marcel Holtmann
2004-10-07 14:55 ` martin f krafft
2004-10-07 16:01 ` Marcel Holtmann
2004-10-07 15:10 ` Thomas Leidenfrost
2004-10-07 15:10 ` Marcel Holtmann
2004-10-07 15:41 ` martin f krafft
2004-10-08 16:12 ` Thomas Leidenfrost
2004-10-07 14:41 ` martin f krafft
2004-10-07 11:42 ` martin f krafft
2004-10-07 12:29 ` Thomas Leidenfrost
2004-10-07 13:11 ` Marcel Holtmann
2004-10-07 13:20 ` martin f krafft
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=1097147273.7325.26.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=leidenfrost@corscience.de \
/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