mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Purzynski <michal@rsbac.org>
To: linux-kernel@vger.kernel.org
Subject: pcmcia subsystem completely broken
Date: Wed, 26 Apr 2006 16:51:13 +0200	[thread overview]
Message-ID: <200604261651.18350.michal@rsbac.org> (raw)

hey,

i'd like to ask how do i cope with new pcmcia subsystem which was introduced 
after 2.6.13. previous one was working very well for me, yet i cannot get my 
most important pcmcia card working with recent kernels. this card is an 
Option Globetrotter GPRS pcmcia card, exposing "serial port" to linux when 
properly detected.due to some braindamage linux is unable to detect this 
serial port properly until i configure replacing CIS during start - than it 
works. but, linux is not looking for it automagically when putting file 
in /lib/firmware, all has to be forced manually in /etc/pcmcia/config, like 
this
card "Option Wireless Technology GSM/GPRS GlobeTrotter"
#Use Manufacturing ID to match all GlobeTrotter variants
manfid 0x0013, 0x0000
cis "cis/GLOBETROTTER.cis"
bind "serial_cs"

as you can see, i'm using old pcmcia-cs tools, since it's not possible to 
replace firmware on demand with pcmciautils - 1st. hence first question - 
when it will be possible ? i supposed old tools will finally stop working and 
i'll be fried after that change.

second problem with it - even after serial port is detected properly, i'm 
still unable to communicate with that card, no AT command is delivered, no 
reaction from card.

what can be wrong with new pcmcia subsystem ? once again - it was working 
excelent with old code, pre 2.6.13.

machine is an Apple PowerBook G4 laptop, revision 5,4.__

CC me, i'm not subscribed

             reply	other threads:[~2006-04-26 14:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-26 14:51 Michal Purzynski [this message]
2006-04-26 15:54 ` Dominik Brodowski

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=200604261651.18350.michal@rsbac.org \
    --to=michal@rsbac.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®