From: Dmitriy Tochansky <toch@dfpost.ru>
To: linux-mips@linux-mips.org
Subject: Re: yenta_socket
Date: Mon, 23 May 2005 20:25:14 +0400 [thread overview]
Message-ID: <20050523202514.3d97d1b5.toch@dfpost.ru> (raw)
In-Reply-To: <20050523184501.3e733eb3.toch@dfpost.ru>
On Mon, 23 May 2005 18:45:01 +0400
Dmitriy Tochansky <toch@dfpost.ru> wrote:
> Yenta: CardBus bridge found at 0000:00:11.0 [e4bf:2000]
> yenta 0000:00:11.0: Preassigned resource 0 busy, reconfiguring...
> yenta 0000:00:11.0: Preassigned resource 1 busy, reconfiguring...
> Yenta: Enabling burst memory read transactions
> Yenta: Using CSCINT to route CSC interrupts to PCI
> Yenta: Routing CardBus interrupts to PCI
> Yenta TI: socket 0000:00:11.0, mfunc 0x0fc01d02, devctl 0x66
> drivers/pcmcia/ti113x.h pci_irq_status = 0
> Yenta TI: socket 0000:00:11.0 probing PCI interrupt failed, trying to fix
> Yenta TI: socket 0000:00:11.0 falling back to parallel PCI interrupts
> Yenta TI: socket 0000:00:11.0 no PCI interrupts. Fish. Please report.
> CPU 0 Unable to handle kernel paging request at virtual address 00000004, epc =0
> ....
Hm... Bus 5?
Linux Kernel Card Services
options: [pci] [cardbus]
PCI: Bus 1, cardbus bridge: 0000:00:11.0
IO window: 00001000-00001fff
IO window: 00002000-00002fff
PREFETCH window: 40000000-41ffffff
MEM window: 42000000-43ffffff
PCI: Bus 5, cardbus bridge: 0000:00:11.1
IO window: 00003000-00003fff
IO window: 00004000-00004fff
PREFETCH window: 44000000-45ffffff
MEM window: 46000000-47ffffff
PCI: Enabling device 0000:00:11.0 (0000 -> 0002)
PCI: Enabling device 0000:00:11.1 (0000 -> 0002)
--
Dmitriy Tochansky
toch@dfpost.ru
JID: dtoch@jabber.ru
prev parent reply other threads:[~2005-05-23 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-23 14:45 yenta_socket Dmitriy Tochansky
2005-05-23 15:54 ` yenta_socket Atsushi Nemoto
2005-05-23 16:18 ` yenta_socket Dmitriy Tochansky
2005-05-23 16:25 ` Dmitriy Tochansky [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=20050523202514.3d97d1b5.toch@dfpost.ru \
--to=toch@dfpost.ru \
--cc=linux-mips@linux-mips.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