public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Valdis.Kletnieks@vt.edu
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.18-rc7-mm1  - gregkh-driver-pcmcia-device.patch breaks orinoco card
Date: Tue, 26 Sep 2006 20:29:21 -0700	[thread overview]
Message-ID: <20060927032921.GI31633@suse.de> (raw)
In-Reply-To: <200609231103.k8NB3RiF004703@turing-police.cc.vt.edu>

On Sat, Sep 23, 2006 at 07:03:26AM -0400, Valdis.Kletnieks@vt.edu wrote:
> orinoco 0.15 (David Gibson <hermes@gibson.dropbear.id.au>, Pavel Roskin <proski@gnu.org>, et al)
> orinoco_cs 0.15 (David Gibson <hermes@gibson.dropbear.id.au>, Pavel Roskin <proski@gnu.org>, et al)
> pcmcia: request for exclusive IRQ could not be fulfilled.
> pcmcia: the driver needs updating to supported shared IRQ lines.
> cs: IO port probe 0x100-0x3af: excluding 0x370-0x37f
> cs: IO port probe 0x3e0-0x4ff: clean.
> cs: IO port probe 0x820-0x8ff: clean.
> cs: IO port probe 0xc00-0xcf7: clean.
> cs: IO port probe 0xa00-0xaff: clean.
> cs: IO port probe 0x100-0x3af: excluding 0x370-0x37f
> cs: IO port probe 0x3e0-0x4ff: clean.
> cs: IO port probe 0x820-0x8ff: clean.
> cs: IO port probe 0xc00-0xcf7: clean.
> cs: IO port probe 0xa00-0xaff: clean.
> cs: IO port probe 0x100-0x3af: excluding 0x370-0x37f
> cs: IO port probe 0x3e0-0x4ff: clean.
> cs: IO port probe 0x820-0x8ff: clean.
> cs: IO port probe 0xc00-0xcf7: clean.
> cs: IO port probe 0xa00-0xaff: clean.
> eth2: Hardware identity 0005:0004:0005:0000
> eth2: Station identity  001f:0001:0008:000a
> eth2: Firmware determined as Lucent/Agere 8.10
> eth2: Ad-hoc demo mode supported
> eth2: IEEE standard IBSS ad-hoc mode supported
> eth2: WEP supported, 104-bit key
> eth2: MAC address 00:02:2D:5C:11:48
> eth2: Station name "HERMES I"
> eth2: ready
> eth2: orinoco_cs at 2.0, irq 11, io 0xe100-0xe13f
> [rename_device:1295]: Changing netdevice name from [eth2] to [eth5]
> Non-volatile memory driver v1.2
> 
> and under -rc7-mm1, I see:
> 
> pccard: CardBus card inserted into slot 0
> PCI: Enabling device 0000:03:00.0 (0000 -> 0003)
> ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
> PCI: Setting latency timer of device 0000:03:00.0 to 64
> eth1: Xircom cardbus revision 3 at irq 11 
> PCI: Enabling device 0000:03:00.1 (0000 -> 0003)
> ACPI: PCI Interrupt 0000:03:00.1[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
> 0000:03:00.1: ttyS1 at I/O 0xe080 (irq = 11) is a 16550A
> pccard: PCMCIA card inserted into slot 2
> ohci1394: fw-host0: AT dma reset ctx=0, aborting transmission
> ieee1394: Current remote IRM is not 1394a-2000 compliant, resetting...
> ieee1394: Host added: ID:BUS[0-00:1023]  GUID[374fc0002a71c021]
> Non-volatile memory driver v1.2
> 
> Hmm.. a lot quieter...

So, you have a pcmcia or cardbus card here?  I've tried this with a
cardbus card and it worked fine.

Are you sure you have the latest userspace tools, I didn't think that cs
was needed anymore, but again, without a pcmcia device to test this
with, I really am not sure :(

thanks,

greg k-h

      reply	other threads:[~2006-09-27  4:30 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-19  8:28 2.6.18-rc7-mm1 Andrew Morton
2006-09-19 13:08 ` 2.6.18-rc7-mm1 Olivier Galibert
2006-09-19 14:22   ` 2.6.18-rc7-mm1 Greg KH
2006-09-19 14:21 ` 2.6.18-rc7-mm1 Greg KH
2006-09-19 16:36   ` 2.6.18-rc7-mm1 Andrew Morton
2006-09-19 18:36     ` 2.6.18-rc7-mm1 Greg KH
2006-09-19 14:45 ` 2.6.18-rc7-mm1 Martin J. Bligh
2006-09-19 16:31   ` 2.6.18-rc7-mm1 Andrew Morton
2006-09-19 16:57     ` 2.6.18-rc7-mm1 Olaf Hering
2006-09-19 17:00     ` 2.6.18-rc7-mm1 Martin Bligh
2006-09-21 12:55     ` 2.6.18-rc7-mm1 Andy Whitcroft
2006-10-07 20:26       ` 2.6.18-rc7-mm1 Greg KH
2006-10-09 12:31         ` 2.6.18-rc7-mm1 Andy Whitcroft
2006-10-09 16:08           ` 2.6.18-rc7-mm1 Greg KH
2006-09-19 17:39 ` [-mm patch] missing class_dev to dev conversions Frederik Deweerdt
2006-10-04  5:10   ` Greg KH
2006-09-19 20:25 ` 2.6.18-rc7-mm1 Rafael J. Wysocki
2006-09-19 20:36   ` 2.6.18-rc7-mm1 Andrew Morton
2006-09-19 21:30     ` 2.6.18-rc7-mm1: networking breakage on HPC nx6325 + SUSE 10.1 Rafael J. Wysocki
2006-09-19 22:06       ` Rafael J. Wysocki
2006-09-19 22:06         ` David Miller
2006-09-19 22:30           ` Greg KH
2006-09-19 22:56             ` Rafael J. Wysocki
2006-09-20  2:28               ` Greg KH
2006-09-20  1:31             ` Dmitry Torokhov
2006-09-20  1:03       ` Valdis.Kletnieks
2006-09-20 14:23     ` 2.6.18-rc7-mm1 Mike Galbraith
2006-09-20 13:18       ` 2.6.18-rc7-mm1 Rafael J. Wysocki
2006-09-21  9:44       ` 2.6.18-rc7-mm1 Andi Kleen
2006-09-21 13:11 ` 2.6.18-rc7-mm1 -- ppc64 crash in slab_node ?? Andy Whitcroft
2006-09-21 17:28   ` Andrew Morton
2006-09-21 18:02     ` Christoph Lameter
2006-09-21 18:07       ` Andy Whitcroft
2006-09-21 18:03     ` Andy Whitcroft
2006-09-21 13:40 ` 2.6.18-rc7-mm1 Ian Kent
2006-09-21 21:07 ` 2.6.18-rc7-mm1 Mark Haverkamp
2006-09-21 22:19   ` 2.6.18-rc7-mm1 Arnd Bergmann
2006-09-22 11:47 ` [PATCH -mm] x86_64 mm generic getcpu syscall fix Cedric Le Goater
2006-09-22 12:19   ` Andi Kleen
2006-09-23 11:03 ` 2.6.18-rc7-mm1 - gregkh-driver-pcmcia-device.patch breaks orinoco card Valdis.Kletnieks
2006-09-27  3:29   ` Greg KH [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=20060927032921.GI31633@suse.de \
    --to=gregkh@suse.de \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@osdl.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