From: Grant Grundler <grundler@parisc-linux.org>
To: Andy Walker <andy@puszczka.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] No PS2 keyboard/mouse on B132L, 2.6.[34]
Date: Mon, 8 Mar 2004 22:36:15 -0700 [thread overview]
Message-ID: <20040309053615.GA11669@colo.lackof.org> (raw)
In-Reply-To: <25271.193.161.152.244.1078745317.squirrel@www.puszczka.com>
On Mon, Mar 08, 2004 at 12:28:37PM +0100, Andy Walker wrote:
> Why is 8/12 (0x00089) reported as unknown in the device table and in
> proc/interrupts? Its the Zalon HVD SCSI.
...
> 6. unknown device at 0xfff8c000 [8/12] { 4, 0x0, 0x03c, 0x00089 }
It means we don't have an entry for Zalon in arch/parisc/kernel/hardware.c
Can you submit a patch for that?
(I confess: I'm being very lazy tonight and don't want to figure
what needs to go into the hardware.c array)
> zalon_probe: Zalon vers field is 0x1, IRQ 35
> ncr53c720-0: rev 0xf irq 35
> ncr53c720-0: ID 7, Fast-10, Parity Checking, Differential
> scsi0 : ncr53c8xx-3.4.3e
> Using anticipatory io scheduler
> Vendor: SEAGATE Model: ST39173WD Rev: 5764
> Type: Direct-Access ANSI SCSI revision: 02
Zalon is obviously recognized and seems to be working.
...
> weasel drivers # cat /proc/interrupts
> CPU00
> 2: 0 EISA cascade
> 32: 5268327 PARISC-CPU timer
> 33: 11276 PARISC-CPU lasi
> 34: 0 PARISC-CPU Dino parisc8:0
> 35: 49026 PARISC-CPU parisc8:12
hrm...good question. Oic. RTFC. :^)
In drivers/scsi/zalon.c:
if (request_irq(irq, ncr53c8xx_intr, SA_SHIRQ, dev->dev.bus_id, host)) {
printk(KERN_ERR "%s: irq problem with %d, detaching\n ",
dev->dev.bus_id, irq);
goto fail;
}
sorry, can't help with the keyboard/mouse problems...
hth,
grant
next prev parent reply other threads:[~2004-03-09 5:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 11:28 [parisc-linux] No PS2 keyboard/mouse on B132L, 2.6.[34] Andy Walker
2004-03-09 5:36 ` Grant Grundler [this message]
2004-03-09 11:27 ` Andy Walker
2004-03-09 21:16 ` Matthew Wilcox
2004-03-09 21:04 ` Matthew Wilcox
2004-03-10 4:59 ` Grant Grundler
2004-03-09 10:03 ` Helge Deller
[not found] ` <28565.193.161.152.244.1078828435.squirrel@www.puszczka.com>
2004-03-09 21:59 ` Helge Deller
2004-03-09 22:21 ` Andy Walker
2004-03-14 7:37 ` [parisc-linux] " Martin Schulze
2004-03-14 15:28 ` M. Grabert
2004-03-14 18:12 ` Martin Schulze
2004-03-14 19:55 ` Helge Deller
2004-03-14 20:28 ` Martin Schulze
2004-03-14 21:19 ` Helge Deller
2004-03-15 17:14 ` [parisc-linux] " Martin Schulze
2004-03-15 19:46 ` [parisc-linux] " Helge Deller
2004-03-15 20:02 ` Andy Walker
2004-03-18 9:55 ` Martin Schulze
2004-03-14 19:48 ` Helge Deller
2004-03-14 20:49 ` [parisc-linux] " Martin Schulze
2004-03-15 0:31 ` Grant Grundler
2004-03-15 8:42 ` Martin Schulze
2004-03-15 15:05 ` Martin Schulze
2004-03-15 22:47 ` Helge Deller
2004-03-14 20:47 ` [parisc-linux] " Martin Schulze
2004-03-14 21:24 ` Helge Deller
-- strict thread matches above, loose matches on Subject: below --
2004-03-09 11:05 [parisc-linux] " Andy Walker
2004-03-08 11:03 Andy Walker
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=20040309053615.GA11669@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=andy@puszczka.com \
--cc=parisc-linux@lists.parisc-linux.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