linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Bob <recbo@nishanet.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: pcmcia yenta no devices Re: APM Suspend Problem
Date: Mon, 8 Dec 2003 09:43:58 +0000	[thread overview]
Message-ID: <20031208094358.C27327@flint.arm.linux.org.uk> (raw)
In-Reply-To: <3FD3DCA6.6000109@nishanet.com>; from recbo@nishanet.com on Sun, Dec 07, 2003 at 09:06:30PM -0500

On Sun, Dec 07, 2003 at 09:06:30PM -0500, Bob wrote:
> If cbdump could help me figure out why I
> don't have any pcmcia cardbus devices showing
> up when I boot or insert or remove storage cards

It might give some clues - you'll have to try it.  The thing to look at
is CB_SOCKET_STATE, bits 1 and 2.  These are the two card detect bits,
and '1' means not detected, '0' means detected.  They both have to be
zero when the card is inserted.

> and a Hawking 10/100 32-bit cardbus ethernet
> pcmcia ethernet card, what is a command line
> that will gcc -o cbdump cbdump.c ?

You didn't look in the comments at the top of the file.  I guess that
also means I could've put a license on the file which required you to
do a John Cleese silly walk and email me the evidence immediately
before compiling it. 8)

> yenta in kernel-2.6.0-test11  but no pcmcia ethernet card drivers
> in kernel since I don't know which eth chip is on a Hawking pcmcia
> PN672TX 32-bit cardbus 10/100 ethernet card.
> 
> boot with compact flash Kingston or Sandisk storage card in
> pcmcia adapter and Hawking ethernet pcmcia card in second
> pcmcia cardbus slot, nothing, try remove and insert, still
> nothing, no pcmcia events or devices reported
> 
> Dec  4 02:32:43 where kernel: Linux Kernel Card Services
> Dec  4 02:32:43 where kernel:   options:  [pci] [cardbus] [pm]
> Dec  4 02:32:43 where kernel: Yenta: CardBus bridge found at 
> 0000:01:0a.0 [414e:454c]
> Dec  4 02:32:43 where kernel: Yenta: ISA IRQ list 0000, PCI irq16
> Dec  4 02:32:43 where kernel: Socket status: 30000006
> Dec  4 02:32:43 where kernel: Yenta: CardBus bridge found at 
> 0000:01:0a.1 [414e:454c]
> Dec  4 02:32:43 where kernel: Yenta: ISA IRQ list 0000, PCI irq16
> Dec  4 02:32:43 where kernel: Socket status: 30000006

This tells me that both sockets are reporting that they are empty.
(Socket status == CB_SOCKET_STATE)  Since we don't know any better,
we believe them.

-- 
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-08  9:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-29  1:02 APM Suspend Problem pZa1x
2003-11-29  1:14 ` pZa1x
2003-11-29  8:22   ` Russell King
2003-11-29 11:26     ` pZa1x
2003-12-01 21:07       ` Russell King
2003-12-06 21:46         ` pZa1x
2003-12-07 17:06           ` Russell King
2003-12-08  2:06             ` pcmcia yenta no devices " Bob
2003-12-08  9:43               ` Russell King [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=20031208094358.C27327@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=recbo@nishanet.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;
as well as URLs for NNTP newsgroup(s).