Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] problems with AnyCom CF-300 on ARM920 Integrator/AP
Date: Thu, 29 Sep 2005 18:44:12 +0200	[thread overview]
Message-ID: <1128012252.30743.23.camel@localhost.localdomain> (raw)
In-Reply-To: <1127914574.2662.22.camel@hexa0xfb>

Hi Itzhak,

> I'm having a very hard time trying to make bluetooth work on the ARM
> Integrator/AP platform.
> 
> Initially, I had a problem with pccard that was not recognized by pcmcia
> yenta_socket. Then, Russell King (ARM Linux Maintainer) provided my a
> patch that solved this problem.
> 
> Then, now pccard bus works properly. PCMCIA system recognizes my card:
> Socket 0:
>   product info: "BTCFCARD", "LSE139"
>   manfid: 0x0264, 0x000b
>   function: 6 (network)
> 
> However, bluecard_cs fails to allocate IO regions.
> 
> Has anybody same similar problems on ARM? Is there anyone working with
> AnyCom CF-300 card?
> 
> I'd appreciate any hint/help that could help me solve this problem.

I saw you discussing this on LKML and this is the right place for
dealing with it, because I don't have ARM experince. Once you got it
working, please report it back here and if there is a patch then send it
to me to merge it mainline.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2005-09-29 16:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-28 13:36 [Bluez-devel] problems with AnyCom CF-300 on ARM920 Integrator/AP Itzhak Ben-Akiva
2005-09-29 16:44 ` Marcel Holtmann [this message]

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=1128012252.30743.23.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    /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