All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krisztian Mark Szentes <office@produktivIT.com>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>,
	benh@kernel.crashing.org
Cc: Edd Dumbill <ejad@debian.org>
Subject: Re: [Bluez-users] bt3c_cs time out - no firmware loaded?
Date: Fri, 16 May 2003 14:38:08 +0200	[thread overview]
Message-ID: <200305161438.08919.office@produktivIT.com> (raw)
In-Reply-To: <1053083095.26552.49.camel@pegasus>

{hello Ben}

On Friday 16 May 2003 13:04, Marcel Holtmann wrote:
> > > > I have trouble with the 3COM Cardbus bluetooth card on a Powerbook
> > > > Titanium (a powerpc notebook). I patched the 2.4.20 kernel with
> > > > the mh-6 patch (and the benh patch which does not collide). I
> > > > haven't found any hint on the list yet.
...
> You're using a Powerbook and the 3Com is currently not supported on the
> PowerPC architecture. The Kernel side of the driver should work fine
> (not tested), but the bluefw have no code to load the firmware. Take a
> look at the mailing list archive for this problem.
Thanks, I found the relevant part (by Edd Dumbill):

"Second, the bad news, there's still x86-arch specific code in there, for
the bt3card stuff.  At least ppc does not have sys/io.h. " 

There must be some uniform way to access I/O of a Cardbus PC-Card on the 
more common arch plattforms. (I did not find any - perhaps there is 
none??) Ben, can you please have a look at the code? (Sent by separate 
mail.)

Greets

Mark
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.

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


-- 
Krisztian Mark Szentes
produktivIT   -  Open-Source Solution Provider
Siebenbrunnengasse 55/7
A-1050 Wien



-------------------------------------------------------
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 12:38 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 [this message]
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
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=200305161438.08919.office@produktivIT.com \
    --to=office@produktivit.com \
    --cc=benh@kernel.crashing.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=ejad@debian.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 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.