public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: kyler-dated-1083521560.f4658e@lairds.com
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] What Bluetooth CF cards do developers use?
Date: Thu, 29 Apr 2004 21:05:20 +0200	[thread overview]
Message-ID: <1083265520.4000.114.camel@pegasus> (raw)
In-Reply-To: <20040429181311.GN1862@snout>

Hi Kyler,

> I'd be happy to just get it working in my Toughbook for now.  I inserted
> it and got "cs: pcmcia_socket0: unable to apply power."

I never have seen this. You should ask the guys from the LKML.

> > The USB related kernel oopses should all be fixed with the upcoming
> > 2.6.6, I hope.
> 
> Yea!  Will a BlueZ patch be required or is it all going to be in the
> kernel this time?

Right now 2.6.5-mh3 and 2.6.6-rc2 has every needed fix in it, but new
problems are on the road and we are trying to fix them just in time.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-04-29 19:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-28 13:56 [Bluez-devel] What Bluetooth CF cards do developers use? Kyler Laird
2004-04-28 14:09 ` Marcel Holtmann
2004-04-28 14:16   ` Kyler Laird
2004-04-28 14:23     ` Marcel Holtmann
2004-04-29 18:13       ` Kyler Laird
2004-04-29 19:05         ` Marcel Holtmann [this message]
2004-04-29 19:20           ` Kyler Laird

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=1083265520.4000.114.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=kyler-dated-1083521560.f4658e@lairds.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