All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Tony Lindgren <tony@atomide.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] AmbiCom BT2000C works with hciattach
Date: Wed, 23 Jun 2004 18:26:48 +0200	[thread overview]
Message-ID: <1088008008.4209.126.camel@pegasus> (raw)
In-Reply-To: <20040623161414.GA9129@atomide.com>

Hi Tony,

> > how good these news are actually depends on what kernel you are using ;)
> 
> Using 2.6.7.

these are good news, because hci_uart and serial_cs are not working very
nice together with a 2.6 kernel. May you share some more information
about your system. For example lspci, lsmod etc.

>         HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP
> 	Subver: 0x20d
>         Manufacturer: Cambridge Silicon Radio (10)

Nice firmware version. Actually it seems we got an alternative for
PCMCIA cards and a 2.6 kernel.

Regards

Marcel




-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-06-23 16:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-23  3:11 [Bluez-devel] AmbiCom BT2000C works with hciattach Tony Lindgren
2004-06-23  7:34 ` Marcel Holtmann
2004-06-23 16:14   ` Tony Lindgren
2004-06-23 16:26     ` Marcel Holtmann [this message]
2004-06-23 16:45       ` Tony Lindgren

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=1088008008.4209.126.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.