Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@rvs.uni-bielefeld.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
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 16:25:05 +0200	[thread overview]
Message-ID: <1053095112.26551.141.camel@pegasus> (raw)
In-Reply-To: <1053094302.2561.99.camel@gaston>

Hi Ben,

> > if you don't see any other solution to work around, this device will be
> > not supported on the PowerPC platform.
> 
> And probably many others...
> 
> direct IO port access is really an x86 thing... 
> 
> Note that if the cardbus bridge actually sits on the main PCI bus and uses
> "legacy" PIO addresses, it is possible to do something, though I hate it ;)
> 
> You can call the sys_pciconfig_iobase syscall to retreive the physical base
> address where the IO ports of a given PCI bus are mapped.
> 
> By passing that the bus number where the cardbus bridge lives on, you can
> then use the resulting value to mmap /dev/mem and actually access those
> IO ports.
> 
> When actually implementing inx/outx in userland, I strongly suggest you do
> what the kernel does in asm/io.h for ld/st_le16, so you get byteswapped
> access for 16 bits, and have proper eieio barriers.
> 
> That syscall should have the following syntax:
> 
> #define IOBASE_IO		2
> 
> syscall(200, IOBASE_IO, bus_number, 0);

I have not a PowerPC platform for testing, so I can't write any code at
the moment. But your proposal looks very ugly and I don't want to go
this way for 2.4. I will wait until the firmware stuff is accepted by
Linus and then try to port the current driver to the new architecture.

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:25 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 [this message]
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=1053095112.26551.141.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