public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Norman Diamond <ndiamond@wta.att.ne.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0 modules, hotplug, PCMCIA
Date: Sun, 28 Dec 2003 11:06:46 +0000	[thread overview]
Message-ID: <20031228110646.A8072@flint.arm.linux.org.uk> (raw)
In-Reply-To: <173b01c3cceb$05ade850$43ee4ca5@DIAMONDLX60>; from ndiamond@wta.att.ne.jp on Sun, Dec 28, 2003 at 11:33:04AM +0900

On Sun, Dec 28, 2003 at 11:33:04AM +0900, Norman Diamond wrote:
> 4.  SuSE 8.2 defaults to using the kernel PCMCIA package rather than the
> external PCMCIA package.  This is fine with me so kernel 2.6.0 also uses its
> own compiled PCMCIA drivers instead of trying to make an external PCMCIA
> package work with two kernels.  It seems to me that it should be OK to
> compile PCMCIA as modules instead of built-in, but there were boot-time
> errors, so I had to change PCMCIA and Yenta to built-in.

What were these errors?

> (This is the
> opposite of the change that I had to make to mice, described in a separate
> e-mail message.)  Now with PCMCIA compiled built-in, the low-level drivers
> get loaded, but cardmgr still doesn't run automatically.  I can do "su" and
> "cardmgr &" and then PCMCIA starts working enough to do modprobes when cards
> are inserted.

It sounds like the SuSE init scripts are being clever and probably only
know about how their 2.4 situation works.  What we need is a SuSE person
to comment on this behaviour; I don't have access to any SuSE based
systems to investigate their quirks.

> 5.  However, file /etc/pcmcia/serial.opts is still getting ignored under
> 2.6.0.

"still" ?  This is news to me (as the guy who seems to be handling both
PCMCIA and serial.)

> The modem is detected as containing a TI 16750 UART, and whatever
> the serial driver does then, it causes the modem to hang up.  The serial
> driver in 2.4.20 defaults to the same thing but 2.4.20 reads file
> /etc/pcmcia/serial.opts, obeys the line SERIAL_OPTS="uart 16550A", and lets
> the modem operate at 33% of its rated speed instead of hanging up.

"hang up"?  Do you mean "on-hook" or do you mean "stop working"?  Is
there anything in /var/log/messages about this?

On my RH systems, cardmgr logs a fair amount to the system messages log,
which includes details of any commands run and any failures.  It would
be really useful to see this.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core

  reply	other threads:[~2003-12-28 11:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-28  2:33 2.6.0 modules, hotplug, PCMCIA Norman Diamond
2003-12-28 11:06 ` Russell King [this message]
2003-12-29  2:03   ` Norman Diamond
2003-12-30  2:28 ` Rusty Russell
  -- strict thread matches above, loose matches on Subject: below --
2003-12-29  9:13 Norman Diamond

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=20031228110646.A8072@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ndiamond@wta.att.ne.jp \
    /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