From: Santiago Garcia Mantinan <manty@manty.net>
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0test3 problems on Acer TravelMate 260 (ALSA,ACPIvsSynaptics,yenta)
Date: Mon, 11 Aug 2003 19:35:38 +0200 [thread overview]
Message-ID: <20030811173538.GA2604@man.beta.es> (raw)
In-Reply-To: <20030811114850.E32508@flint.arm.linux.org.uk>
Hey, what a quick reply, here goes the info you asked for, if you need any
more just ask for it.
> - does 2.6.0-test3 detect the card at boot ?
> - if not, what are the complete kernel messages ?
Yes and no, I mean, it detects a card, but not the card it has in, it tries
to load memory_cs when I have a wireless card in, the card should load
hostap_cs, in fact if after booting I remove it and insert it twice, it
recognices the card well and tries to load hostap_cs.
Here are the messages it outputs:
Linux Kernel Card Services 3.1.22
options: [pci] [cardbus] [pm]
PCI: IRQ 10 for device 0000:01:09.0 doesn't match PIRQ mask - try
pci=usepirqmask
PCI: Found IRQ 11 for device 0000:01:09.0
PCI: Sharing IRQ 11 with 0000:00:1d.1
IRQ routing conflict for 0000:01:09.0, have irq 10, want irq 11
Yenta: CardBus bridge found at 0000:01:09.0 [1025:1024]
Yenta IRQ list 02b8, PCI irq10
Socket status: 30000811
cs: memory probe 0x0c0000-0x0fffff: excluding 0xc0000-0xcffff
0xdc000-0x103fff
> - does 2.6.0-test3 detect it at every insertion after the first
> "insert remove insert" cycle, or does it always need an even
> number of insertions for it to be recognised?
It always needs an even number of insertions.
> - does 2.4 and 2.6-test3 yenta find the same IRQs ?
Seems so, these are the messages for yenta on 2.4.21:
Linux Kernel Card Services 3.1.22
options: [pci] [cardbus] [pm]
PCI: Found IRQ 11 for device 01:09.0
PCI: Sharing IRQ 11 with 00:1d.1
IRQ routing conflict for 01:09.0, have irq 10, want irq 11
Yenta IRQ list 00b8, PCI irq10
Socket status: 30000007
cs: memory probe 0x0c0000-0x0fffff: excluding 0xc0000-0xcbfff
0xe0000-0xfffff
> - which version of pcmcia-cs are you using with 2.4 ?
3.2.2
> - which IRQ(s) does 2.4 i82365 use ?
The same ones as yenta, here you have the messages I get with it just in
case:
Linux PCMCIA Card Services 3.2.2
kernel build: 2.4.21 #1 Sat Jun 14 19:43:14 CEST 2003
options: [pci] [cardbus] [apm]
Intel ISA/PCI/CardBus PCIC probe:
PCI: Found IRQ 11 for device 01:09.0
PCI: Sharing IRQ 11 with 00:1d.1
IRQ routing conflict for 01:09.0, have irq 10, want irq 11
O2Micro OZ6912 rev 00 PCI-to-CardBus at slot 01:09, mem 0x10001000
host opts [0]: [pci/way] [pci irq 10] [lat 32/176] [bus 2/5]
ISA irqs (default) = 3,4,5,7 PCI status changes
Hope this helps, if you need anything else, just ask for it.
Regards...
--
Manty/BestiaTester -> http://manty.net
next prev parent reply other threads:[~2003-08-11 17:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-11 10:22 2.6.0test3 problems on Acer TravelMate 260 (ALSA,ACPIvsSynaptics,yenta) Santiago Garcia Mantinan
2003-08-11 10:48 ` Russell King
2003-08-11 17:35 ` Santiago Garcia Mantinan [this message]
2003-08-12 1:45 ` Mark W. Alexander
2003-08-12 8:39 ` Santiago Garcia Mantinan
2003-08-12 10:54 ` Mark W. Alexander
2003-08-12 9:25 ` Takashi Iwai
2003-08-12 15:11 ` Santiago Garcia Mantinan
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=20030811173538.GA2604@man.beta.es \
--to=manty@manty.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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).