Date: Fri, 30 Sep 2005 00:04:00 +0200
From: Pavel Machek <pavel@ucw.cz>
To: Marcel Holtmann <marcel@holtmann.org>, bluez-devel@lists.sourceforge.net,
       kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Problems with CF bluetooth
Message-ID: <20050929220400.GE2180@elf.ucw.cz>
References: <20050929155602.GA1990@elf.ucw.cz> <1128011355.30743.14.camel@localhost.localdomain> <20050929175420.GN1990@elf.ucw.cz> <1128016693.6052.2.camel@localhost.localdomain> <20050929213219.GA2180@elf.ucw.cz> <20050929213707.GH7684@flint.arm.linux.org.uk> <20050929214340.GB2180@elf.ucw.cz> <20050929214559.GI7684@flint.arm.linux.org.uk> <20050929215234.GC2180@elf.ucw.cz> <20050929220134.GJ7684@flint.arm.linux.org.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20050929220134.GJ7684@flint.arm.linux.org.uk>
User-Agent: Mutt/1.5.9i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1661
Lines: 40

On Čt 29-09-05 23:01:34, Russell King wrote:
> On Thu, Sep 29, 2005 at 11:52:34PM +0200, Pavel Machek wrote:
> > Hi!
> > 
> > > > > > > > I believe it would happen with any other CF card, too. Can you
> > > > > > > > hciattach it, unplug, hciattach again?
> > > > > > > 
> > > > > > > actually I don't have any of them with me and I don't saw a problem with
> > > > > > > my Casira of a serial port.
> > > > > > 
> > > > > > Following patch seems to work around it. And yes, printk() triggers
> > > > > > twice after 
> > > > > 
> > > > > What's the problem this patch is trying to address?
> > > > 
> > > > I get oops after starting my bluetooth subsystem for second
> > > > time. billionton_start, unplug CF, billionton_start will oops the
> > > > system. That patch prevents it.
> > > 
> > > More details please.  I don't have the ability to run bluetooth myself.
> > 
> > Unfortunately I do not know much about bluetooth. The card is
> > basically CF serial with bluetooth chip attached to that. billionton
> > start does setserial, then attaches bluetooth subsystem to that chip,
> > and enables bluetooth.
> 
> How about showing the oops?  The patch is definitely wrong btw - there's
> no way state->info should be NULL here.

I realize it is probably wrong... forwarding you the original report
... with the oops :-).
								Pavel

-- 
if you have sharp zaurus hardware you don't need... you know my address
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/