mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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
Date: Fri, 30 Sep 2005 00:04:00 +0200	[thread overview]
Message-ID: <20050929220400.GE2180@elf.ucw.cz> (raw)
In-Reply-To: <20050929220134.GJ7684@flint.arm.linux.org.uk>

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

      reply	other threads:[~2005-09-29 22:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-29 13:48 Pavel Machek
2005-09-29 15:45 ` Marcel Holtmann
2005-09-29 15:56   ` Pavel Machek
2005-09-29 16:29     ` Marcel Holtmann
2005-09-29 17:54       ` Pavel Machek
2005-09-29 17:58         ` Marcel Holtmann
2005-09-29 21:32           ` Pavel Machek
2005-09-29 21:37             ` Russell King
2005-09-29 21:43               ` Pavel Machek
2005-09-29 21:45                 ` Russell King
2005-09-29 21:52                   ` Pavel Machek
2005-09-29 22:01                     ` Russell King
2005-09-29 22:04                       ` Pavel Machek [this message]

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=20050929220400.GE2180@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®