From: Thomas Leidenfrost <leidenfrost@corscience.de>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Bluetooth on a MIPS-System
Date: Thu, 07 Oct 2004 15:10:58 +0200 [thread overview]
Message-ID: <41654062.5050009@corscience.de> (raw)
In-Reply-To: <1097152912.7325.30.camel@pegasus>
Hi Marcel,
> 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.
I already had this kernel, but without doing "make modules" I can look
for them a long long time... ;-)
Now I created the following modules and loaded them on target via modprobe:
-bluez
-l2cap
-hci_vhci
-hci_uart
-hci_usb
Doing hcitool scan now results: Device is not available: Success
So I guess that not all neccessary modules are loaded, right?
>>>Do a "modprobe hci_usb" and then check with "dmesg" what happens.
This results a long output, but nothing with blue* / hci* or something
similar to this in it. What should I llok for?
> So what does "find /lib/modules/ | grep bluetooth" say?
This results nothing, just the # again.
Thanks for helping again, now it's some steps fewer to the goal! :-)
Regards, Tom
next prev parent reply other threads:[~2004-10-07 13:10 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
2004-10-07 13:10 ` Thomas Leidenfrost [this message]
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=41654062.5050009@corscience.de \
--to=leidenfrost@corscience.de \
--cc=bluez-users@lists.sourceforge.net \
--cc=marcel@holtmann.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.