Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Richard Hirst <rhirst@levanta.com>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] cvs head arch/parisc/kernel/drivers.c issues
Date: Sun, 31 Jul 2005 20:32:29 +0100	[thread overview]
Message-ID: <20050731193229.GE5500@levanta.com> (raw)
In-Reply-To: <20050731090005.GD5500@levanta.com>

With the following patch I can boot my C360, although there is not
ps/2 (obviously, given the second part of the diff):

Index: arch/parisc/kernel/drivers.c
===================================================================
RCS file: /var/cvs/linux-2.6/arch/parisc/kernel/drivers.c,v
retrieving revision 1.25
diff -u -r1.25 drivers.c
--- arch/parisc/kernel/drivers.c        26 Jul 2005 23:55:47 -0000      1.25
+++ arch/parisc/kernel/drivers.c        31 Jul 2005 19:22:21 -0000
@@ -448,11 +448,9 @@
        struct parisc_device * pdev = to_parisc_device(dev);
        struct match_id_data * d = data;
 
-       if (check_dev(pdev)) {
-               if (pdev->hw_path == d->id) {
-                       d->dev = pdev;
-                       return 1;
-               }
+       if (pdev->hw_path == d->id) {
+               d->dev = pdev;
+               return 1;
        }
        return 0;
 }
Index: drivers/input/serio/gscps2.c
===================================================================
RCS file: /var/cvs/linux-2.6/drivers/input/serio/gscps2.c,v
retrieving revision 1.16
diff -u -r1.16 gscps2.c
--- drivers/input/serio/gscps2.c        18 Mar 2005 13:16:54 -0000      1.16
+++ drivers/input/serio/gscps2.c        31 Jul 2005 19:22:29 -0000
@@ -334,7 +334,7 @@
        unsigned long hpa = dev->hpa;
        int ret;
 
-       if (!dev->irq)
+       //if (!dev->irq)
                return -ENODEV;
 
        /* Offset for DINO PS/2. Works with LASI even */


I think the drivers.c part is probably reasonable, although it might be
masking some underlying problem with device discovery.  If I enable the
gscps2 driver the system hangs, possibly with an interrupt storm.

I noticed the 2.6.13 kernel is using completely different IRQ allocations
from 2.6.8 (cat /proc/interrupts); is this expected?


2.6.8

           CPU00
 32:       9151      PARISC-CPU  timer
 33:          0      PARISC-CPU  IPI
 34:        512      PARISC-CPU  lasi
 35:       2053      PARISC-CPU  Dino [8/0]
 36:          0      PARISC-CPU  Cujo
 69:         31            Lasi  GSC PS2 keyboard, GSC PS2 mouse
 86:         68            Lasi  lasi700
 90:        413            Lasi  serial
 96:         30      Dino [8/0]  eth0
 99:       2023      Dino [8/0]  sym53c8xx


2.6.13

 16:       2020        GSC-ASIC  serial
 17:         54        GSC-ASIC  lasi700
 22:       2532         GSC-PCI  sym53c8xx
 23:         36         GSC-PCI  eth0
 64:      94680             CPU  timer
 65:          0             CPU  IPI
 66:       2074             CPU  lasi
 67:       2566             CPU  Dino
 68:          0             CPU  Cujo


When I enable gscps2 it is trying to use IRQ 20.

Richard

_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  parent reply	other threads:[~2005-07-31 19:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-30 23:10 [parisc-linux] cvs head arch/parisc/kernel/drivers.c issues Richard Hirst
2005-07-31  6:12 ` Kyle McMartin
2005-07-31  9:00   ` Richard Hirst
2005-07-31 18:47     ` Kyle McMartin
2005-08-01 20:02       ` Richard Hirst
2005-07-31 19:32     ` Richard Hirst [this message]
2005-07-31 19:38       ` Kyle McMartin
2005-07-31 20:01         ` Richard Hirst
2005-07-31 20:13           ` Kyle McMartin
2005-07-31 20:23           ` Kyle McMartin
2005-07-31 20:27             ` Kyle McMartin
2005-08-01 13:48               ` Richard Hirst
2005-08-01 14:53                 ` Richard Hirst

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=20050731193229.GE5500@levanta.com \
    --to=rhirst@levanta.com \
    --cc=kyle@mcmartin.ca \
    --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