From: Marcel Holtmann <marcel@rvs.uni-bielefeld.de>
To: Krisztian Mark Szentes <office@produktivIT.com>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>,
benh@kernel.crashing.org, Edd Dumbill <ejad@debian.org>
Subject: Re: [Bluez-users] bt3c_cs time out - no firmware loaded?
Date: 16 May 2003 15:16:19 +0200 [thread overview]
Message-ID: <1053090987.26550.120.camel@pegasus> (raw)
In-Reply-To: <200305161438.08919.office@produktivIT.com>
Hi Krisztian,
> kind of astonished, I chose the 3COM card explicitly according to the BlueZ
> hardware compatibility list, I could also have chosen the Xircom or Anycom
> cards; they would probably have saved a lot of messing around.
> Perhaps you could correct
> http://www.holtmann.org/linux/bluetooth/bt3c.html
> in order to reflect the missing powerpc support.
I have added a small comment to this page.
> Furthermore, you could also enhance the hardware support page by adding
> vendor co-operation information like linuxprinting.org does. I saw Anycom
> directly links to Marcel's homepage. A simple sorting of the list
> according to driver openness etc. would just suffice
If you search through the mailing list archive, you will find a posting
from Max that suggested the same thing. I included it into the list and
removed it the at same day, because I am not the person who should
decide which company is Linux friendly and which is not. Let the list
and the driver source code talk for themself. And you mention the Anycom
driver. I have this driver already finished over half a year ago, before
I got the rights to publish it under GPL.
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
next prev parent reply other threads:[~2003-05-16 13:16 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 [this message]
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
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=1053090987.26550.120.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox