public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: "Antti Mäkelä" <zarhan@cs.tut.fi>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] BT3C ceased working in kernel 2.6.6
Date: Wed, 12 May 2004 15:35:42 +0200	[thread overview]
Message-ID: <1084368942.25099.41.camel@pegasus> (raw)
In-Reply-To: <Pine.GSO.4.58.0405111227090.9721@viherkiuru.cs.tut.fi>

[-- Attachment #1: Type: text/plain, Size: 534 bytes --]

Hi Antti,

>   I upgraded from kernel 2.6.6-rc2 to 2.6.6 and it seems that BT3C is now
> broken. The driver is compiled as a module.
> 
>   The firmware is placed in /usr/lib/hotplug/firmware as it should be, and
> it was working in 2.6.6-rc2. The driver is compiled as a module, rest of
> the system are in kernel.

I know and there is no real fix for it, because the PCMCIA subsystem is
not fully integrated into the driver model. However the attached patch
should prevent the oops and make the driver work again.

Regards

Marcel


[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 310 bytes --]

===== drivers/bluetooth/bt3c_cs.c 1.20 vs edited =====
--- 1.20/drivers/bluetooth/bt3c_cs.c	Sat Apr 17 00:23:48 2004
+++ edited/drivers/bluetooth/bt3c_cs.c	Wed May 12 15:33:13 2004
@@ -491,6 +491,9 @@
 
 static struct device bt3c_device = {
 	.bus_id = "pcmcia",
+	.kobj = {
+		.k_name = "bt3c_cs"
+	}
 };
 
 

  reply	other threads:[~2004-05-12 13:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-11  9:30 [Bluez-devel] BT3C ceased working in kernel 2.6.6 Antti Mäkelä
2004-05-12 13:35 ` Marcel Holtmann [this message]
2004-05-12 14:21 ` David Woodhouse
2004-05-12 17:17   ` Marcel Holtmann
2004-05-12 17:40     ` David Woodhouse
2004-05-12 17:48       ` Marcel Holtmann

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=1084368942.25099.41.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=zarhan@cs.tut.fi \
    /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