hi
your device has an incomplete CIS on the card and therefor needs an updated
one loaded. i think there's the problem...
get and extract the pcmcia-cs package, then do a:
cp etc/cis/3CXEM556.dat /lib/firmware/3CXEM556.cis
(note the change from .dat to .cis)
rgds
-daniel
--
To
The network is ok now
...but, I don't have sound anymore: «
eth0: 3Com 3c589, io 0x310, irq 5, hw_addr 00:00:86:52:4B:CB
add the line:
exclude irq 5
to /etc/pcmcia/config.opts. this will tell pcmcia not to use that irq line...
rgds
-daniel
On Wednesday 17 August 2005 02.26, Daniel Ritz wrote:
hi
On Tuesday 16 August 2005 22.47, Philippe Bourcier wrote:
I tried latest debian 2.6.12 kernel; see:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=321419
irq 11: nobody cared!
[c01388fa] __report_bad_irq+0x2a/0xa0
to CS_IN_USE
which results in the function having the CB irq assigned. yenta_set_socket
then just changes the irq routing to use the PCI interrupt but the first
functions irq handler is registered on an ISA interrupt. boom.
Signed-off-by: Daniel Ritz [EMAIL PROTECTED]
diff --git a/drivers/pcmcia
On Tuesday 12 April 2005 23:14, Philippe Bourcier wrote:
hi all,
On Tue, Apr 12, 2005 at 12:05:02AM +0200, maximilian attems wrote:
received another bug report concerning TI irq routing.
your patch don't seem to fix this PCI1250 rev2.
you'll find the bug report at
.
Signed-off-by: Daniel Ritz [EMAIL PROTECTED]
--- 1.40/drivers/net/pcmcia/3c574_cs.c 2005-01-25 22:50:25 +01:00
+++ edited/drivers/net/pcmcia/3c574_cs.c2005-04-09 21:49:02 +02:00
@@ -1274,6 +1274,9 @@
spin_lock_irqsave(lp-window_lock, flags);
update_stats(dev
of func1 to func0 if INTRTIE is set
make sure that if the INTRTIE bit is set both functions of the
cardbus bridge use the same IRQ before doing any probing...
[ yes i hate the TI bridges for the fact that they are very flexible
so that so many BIOS vendors get it wrong. ]
Signed-off-by: Daniel Ritz
On Friday 01 April 2005 19:52, Dominik Brodowski wrote:
Seems to be the IRQ storm issue again... Daniel, IIRC you worked on that
issue before: do you have an idea on how to write a proper patch for this
issue?
nope it looks more like something else. looking at the debian bug report:
- lspci
On Friday 01 April 2005 19:52, Dominik Brodowski wrote:
Seems to be the IRQ storm issue again... Daniel, IIRC you worked on that
issue before: do you have an idea on how to write a proper patch for this
issue?
btw. i'm working on the patch again. but like the routing code it's not
so easy to
9 matches
Mail list logo
