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 14:41:52 +0200 [thread overview]
Message-ID: <1097152912.7325.30.camel@pegasus> (raw)
In-Reply-To: <41652A40.4080209@corscience.de>
Hi Thomas,
> But I think the Problem is not MIPS-specific, the question is where to
> get the missing modules like l2cap, hci_usb, bluez...
> Should they be created automaticly after compiling the BlueZ-Libs &
> -Utils? Support for them is activated in the kernel (as module).
the kernel modules are part of the Linux kernel you use on your MIPS
system. So you need a Linux kernel compiled for MIPS with activated
Bluetooth subsystem.
If you find the modules on your filesystem, check what modinfo or file
says about them.
> > Do a "modprobe hci_usb" and then check with "dmesg" what happens.
>
> # modprobe hci_usb (on target says:)
> insmod: hci_usb.o: no module by that name found
> modprobe: failed to load module hci_usb
>
> because there is no module on target, searching for it resulted nothing.
> And I think I just can't take them from the host (x86). Are there any
> precompiled modules for MIPS?
So what does "find /lib/modules/ | grep bluetooth" say?
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 12:41 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
2004-10-07 11:36 ` Thomas Leidenfrost
2004-10-07 12:41 ` Marcel Holtmann [this message]
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=1097152912.7325.30.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