public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Michael Frey <mfrey@pepper.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Unable to get hciattach to work...
Date: Wed, 21 Apr 2004 16:57:41 +0200	[thread overview]
Message-ID: <1082559461.23959.37.camel@pegasus> (raw)
In-Reply-To: <E09DAEFD-93A2-11D8-88A9-00039390D626@pepper.com>

Hi Michael,

> I just recently upgraded my kernel from 2.4.18 to 2.4.20 and am trying 
> to get my bluetooth module to work.  I have been using bluez with great 
> success with my 2.4.18 kernel but no luck with 2.4.20.
> 
> When I issue the hciattach command here is what I get.
> ./hciattach /dev/ttyS1 bcsp 115200
> BlueZ HCI UART driver ver 2.0 Copyright (C) 2000,2001 Qualcomm Inc
> Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
> insmod: Note: /etc/modules.conf is more recent than 
> /lib/modules/2.4.20_mvl31-dbpxa2xx/modules.dep
> Can't set device: Protocol not supported
> Can't initialize device: Illegal seek
> root@(none):/opt/bluetooth# lsmod
> Module                  Size  Used by    Tainted: P
> hci_uart                5444   0  (autoclean)
> bluez                  34672   1  (autoclean) [hci_uart]
> spectrum_cs            75772   1
> orinoco                33716   0  [spectrum_cs]
> hermes                  4408   0  [spectrum_cs orinoco]
> ide-cs                  3572   1
> ds                      7472   2  [spectrum_cs ide-cs]
> pxa_cs                  9296   2
> pcmcia_core            34672   0  [spectrum_cs ide-cs ds pxa_cs]
> 
> 
> How do I go about debugging this?  I am using the kernel modules that 
> are in the kernel tree.

the plain vanilla 2.4.20 don't includes BCSP support. If you got the
2.4.18 working with BCSP you must have used a patched kernel.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-04-21 14:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-21 14:47 [Bluez-devel] Unable to get hciattach to work Michael Frey
2004-04-21 14:57 ` Marcel Holtmann [this message]
2004-04-21 15:06   ` Michael Frey
2004-04-21 15:09     ` Marcel Holtmann
2004-04-21 15:44       ` Michael Frey
2004-04-21 15:50         ` Marcel Holtmann
2004-04-21 16:47           ` Michael Frey

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=1082559461.23959.37.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=mfrey@pepper.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