All of lore.kernel.org
 help / color / mirror / Atom feed
From: rico-linux-kernel@patternassociates.com
To: linux-kernel@vger.kernel.org
Subject: Re: serverworks usb under 2.4.22
Date: 14 Nov 2003 08:58:41 -0000	[thread overview]
Message-ID: <20031114085841.28270.qmail@patternassociates.com> (raw)

>From:	Ingo Oeser <ioe-lkml@rameria.de>
>Date:	Fri, 14 Nov 2003 08:51:00 +0100
>...
>I for one need to pass "noapic" on the kernel command line. Otherwise
>the IRQ routing is broken, I can't get the USB IRQ and the kernel complains.
>a lot about a broken APIC IRQ routing.
>
>My board is an ASUS CUR-CLS. The chipset there is "ServerWorks LE".

Ingo,

My ServerWorks HE chipset is a close cousin.  The common BIOS was written
by Intergraph, and marketed by Phoenix.  It somehow fails to communicate
its decisions about IRQ routing to Linux.  One may get lucky by moving
hardware around but, with the following patch, you are guaranteed use
of the chipset USB while still enjoying the IO-APIC.  Patch has been
necessary from 2.4.0 through 2.4.17 and, by the sounds of it, to current
2.4 versions.

You must edit the patch to use the correct IRQ for your hardware config
(11 in my case).  To determine the IRQ, access USB hardware while
monitoring interrupt counts in /proc/stat

--------start of patch--------------------------------------------------
*** usb-ohci.c.orig	Mon Dec 31 11:35:13 2001
--- usb-ohci.c	Mon Dec 31 12:10:39 2001
***************
*** 2581,2601 ****
--- 2581,2605 ----
  
  	mem_base = ioremap_nocache (mem_resource, mem_len);
  	if (!mem_base) {
  		err("Error mapping OHCI memory");
  		return -EFAULT;
  	}
  
  	/* controller writes into our memory */
  	pci_set_master (dev);
  
+ #if 0
  	return hc_found_ohci (dev, dev->irq, mem_base, id);
+ #else
+ 	return hc_found_ohci (dev,       11, mem_base, id);
+ #endif
  } 
  
  /*-------------------------------------------------------------------------*/
  
  /* may be called from interrupt context [interface spec] */
  /* may be called without controller present */
  /* may be called with controller, bus, and devices active */
  
  static void __devexit
  ohci_pci_remove (struct pci_dev *dev)
--------end of patch--------------------------------------------------

             reply	other threads:[~2003-11-14  8:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-14  8:58 rico-linux-kernel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-14  1:24 serverworks usb under 2.4.22 rico-linux-kernel
2003-11-14 14:57 ` Brian Beattie
2003-11-14  0:17 Brian Beattie
2003-11-14  7:51 ` Ingo Oeser
2003-11-14 16:04   ` Brian Beattie

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=20031114085841.28270.qmail@patternassociates.com \
    --to=rico-linux-kernel@patternassociates.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.