public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
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 15:14:01 +0200	[thread overview]
Message-ID: <1097154841.7325.36.camel@pegasus> (raw)
In-Reply-To: <41654062.5050009@corscience.de>

Hi Thomas,

> > 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?

you may also need a USB host controller driver. I don't know which to
use for your system. Is it PCI based? If yes, post the output of lspci.

> > So what does "find /lib/modules/ | grep bluetooth" say?
> 
> This results nothing, just the # again.

This is wrong unless you copied the BlueZ modules somewhere else by
hand.

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

  reply	other threads:[~2004-10-07 13:14 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
2004-10-07 13:14         ` Marcel Holtmann [this message]
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=1097154841.7325.36.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