From: Krisztian Mark Szentes <office@produktivIT.com>
To: Marcel Holtmann <marcel@rvs.uni-bielefeld.de>
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: Fri, 16 May 2003 16:22:47 +0200 [thread overview]
Message-ID: <200305161622.47728.office@produktivIT.com> (raw)
In-Reply-To: <1053091839.26550.125.camel@pegasus>
On Friday 16 May 2003 15:30, Marcel Holtmann wrote:
> > Hrm... The problem isn't simple. You are just not supposed to tap IOs
> > that way from userland, especially since PPC arch doesn't have
> > anything like "PIO" instructions. The IO space of your card is
> > actually mapped somewhere in physical memory, that "somewhere" not
> > beeing generally available to userland.
> >
> > Can you tell me more about the card ? Is it a 16 bits PCMCIA device or
> > is it a cardbus (PCI) one ? Why can't you tap the IOs solely from
> > within a kernel driver ?
>
> this is a 16 Bit PCMCIA card. We need to load the firmware from
> userspace, because we can't distribute it within the kernel driver due
> the legal issues. At the moment we don't even distribute the firmware
> file with our userspace firmware loader program.
OK.
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)?
Salut
Mark
P.S. Maybe I should do (1), (2), (3) AND (4) :-))
--
produktivIT - Open-Source Solution Provider
Siebenbrunnengasse 55/7
A-1050 Wien
next prev parent reply other threads:[~2003-05-16 14:22 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 [this message]
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=200305161622.47728.office@produktivIT.com \
--to=office@produktivit.com \
--cc=benh@kernel.crashing.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=ejad@debian.org \
--cc=marcel@rvs.uni-bielefeld.de \
/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.