mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Michal Purzynski <michal@rsbac.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: pcmcia subsystem completely broken
Date: Wed, 26 Apr 2006 17:54:56 +0200	[thread overview]
Message-ID: <20060426155456.GA9108@isilmar.linta.de> (raw)
In-Reply-To: <200604261651.18350.michal@rsbac.org>

Hi,

On Wed, Apr 26, 2006 at 04:51:13PM +0200, Michal Purzynski wrote:
> #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 ?

Since 2.6.13 or so. You need to add a line to the serial_id table in
drivers/serial/serial_cs.c, though:
	PCMCIA_DEVICE_CIS_MANF_CARD(0x0013, 0x0000, "GLOBETROTTER.cis");
and GLOBETROTTER.cis needs to be available in /lib/firmware/ . Of course the
default kernel firmware loading mechanism (either udev or hotplug) must
work, too...

> i supposed old tools will finally stop working and 
> i'll be fried after that change.

Old tools will only be removed once there's no regression. Oh, and where did
you read that replacing firmware on demand wasn't possible with
pcmciautils?

> 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.

Please post a lspcmcia and dmesg output to the linux-pcmcia list at
linux-pcmcia (AT) lists (DOT) infradead (DOT) org

	Dominik

      reply	other threads:[~2006-04-26 15:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-26 14:51 Michal Purzynski
2006-04-26 15:54 ` Dominik Brodowski [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=20060426155456.GA9108@isilmar.linta.de \
    --to=linux@dominikbrodowski.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal@rsbac.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®