All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@rvs.uni-bielefeld.de>
To: Krisztian Mark Szentes <office@produktivIT.com>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>,
	Edd Dumbill <ejad@debian.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [Bluez-users] bt3c_cs time out - no firmware loaded?
Date: 16 May 2003 16:32:24 +0200	[thread overview]
Message-ID: <1053095551.26552.146.camel@pegasus> (raw)
In-Reply-To: <200305161622.47728.office@produktivIT.com>

Hi Kirsztian,

> I am fed up with the card, I bought it almost year ago and hoped it would 
> some time become easier to use. I chose it over the Xircom and Anycom 
> parts because its antenna looked neat. In the meantime, I also bought a 
> USB device which explicitely stated Linux compatibility on the 
> manufacturer's web site (Epox).
> I'm thinking about 
> 
> (1) asking 3COM for permission, or 
> (2) returning it to 3COM's headquarters or 
> (3) publicly destroying it and putting up a video or
> (4) sell it to a modern slave (Windoze user) and donating the money to 
> Debian
> 
> Marcel, can you give me a hint whom I should contact for (1)? 

I got a contact at Cebit this year, but I never found the time to write
an email to him according the firmware stuff and the new card Version
3.0 (which is not working with this driver). You can contact him if you
like. His name is Brent Nixon (brent_nixon(at)3com.com).

Regards

marcel




-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2003-05-16 14:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <53B03DA73719D5119E6A0008C71E1D78030EA9A3@svr-mail1.corp.home.nl>
2003-05-08 13:43 ` [Bluez-users] bt3c_cs time out - no firmware loaded? Krisztian Mark Szentes
2003-05-12 20:29   ` Max Krasnyansky
2003-05-13  1:16     ` [Bluez-users] bt3c_cs time out - no firmware loaded? - problem persists Krisztian Mark Szentes
2003-05-13  0:17   ` [Bluez-users] bt3c_cs time out - no firmware loaded? Marcel Holtmann
2003-05-13  8:47     ` Krisztian Mark Szentes
2003-05-16 11:04       ` Marcel Holtmann
2003-05-16 12:38         ` Krisztian Mark Szentes
2003-05-16 13:16           ` Marcel Holtmann
2003-05-16 13:24           ` Benjamin Herrenschmidt
2003-05-16 13:30             ` Marcel Holtmann
2003-05-16 13:32               ` Benjamin Herrenschmidt
2003-05-16 13:39                 ` Marcel Holtmann
2003-05-16 13:47                   ` Benjamin Herrenschmidt
2003-05-16 13:57                     ` Marcel Holtmann
2003-05-16 14:11                       ` Benjamin Herrenschmidt
2003-05-16 14:25                         ` Marcel Holtmann
2003-05-16 14:48                           ` Benjamin Herrenschmidt
2003-05-16 14:22               ` Krisztian Mark Szentes
2003-05-16 14:32                 ` Marcel Holtmann [this message]
2003-05-16 14:51                   ` Krisztian Mark Szentes
2003-05-09  8:39 ` produktivIT

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=1053095551.26552.146.camel@pegasus \
    --to=marcel@rvs.uni-bielefeld.de \
    --cc=benh@kernel.crashing.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=ejad@debian.org \
    --cc=office@produktivIT.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.