From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Marcel Holtmann <marcel@rvs.uni-bielefeld.de>
Cc: Krisztian Mark Szentes <office@produktivIT.com>,
BlueZ Mailing List <bluez-users@lists.sourceforge.net>,
Edd Dumbill <ejad@debian.org>
Subject: Re: [Bluez-users] bt3c_cs time out - no firmware loaded?
Date: 16 May 2003 15:32:19 +0200 [thread overview]
Message-ID: <1053091938.2978.88.camel@gaston> (raw)
In-Reply-To: <1053091839.26550.125.camel@pegasus>
On Fri, 2003-05-16 at 15:30, Marcel Holtmann wrote:
> Hi Ben,
>
> > 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.
Can't you do some kind of ioctl or /proc entry to the card's driver
to pass it the firmware from userland and have the actual IO code in
the kernel ?
Ben.
next prev parent reply other threads:[~2003-05-16 13: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 [this message]
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=1053091938.2978.88.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=ejad@debian.org \
--cc=marcel@rvs.uni-bielefeld.de \
--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