public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Sune Mølgaard" <sune@molgaard.org>
To: linux-kernel@vger.kernel.org
Cc: mj@ucw.cz
Subject: Re: [PATCH] 2.4.30 PicoPower IRQ router
Date: Tue, 26 Apr 2005 21:00:52 +0200	[thread overview]
Message-ID: <426E8FE4.5040307@molgaard.org> (raw)
In-Reply-To: <200504261740.08794.lists@b-open-solutions.it>

Alessandro Amici wrote:
> just in case you didn't notice: your patch is empty :)

How so? I see it fine in the mail that came back to me, but ok. I'll
repost below.

> and try to gather info on someone actually in charge of the subsystem 
> you are modifying and CC him. random patches on l-k may not get the 
> needed attention.
> 

I thought of that and forwarded to Martin Mares, but thank you for the tip

Best regards,

Sune

--Start patch--

--- linux-2.4.30/arch/i386/kernel/pci-irq.c	2005-04-04
03:42:19.000000000 +0200
+++ linux/arch/i386/kernel/pci-irq.c	2005-04-25 08:43:02.501678464 +0200
@@ -157,6 +157,25 @@
  }

  /*
+ * PicoPower PT86C523
+ */
+
+static int pirq_pico_get(struct pci_dev *router, struct pci_dev *dev,
int pirq)
+{
+  outb(0x10+((pirq-1)>>1), 0x24);
+  return ((pirq-1)&1) ? (inb(0x26)>>4) : (inb(0x26)&0xf);
+}
+
+static int pirq_pico_set(struct pci_dev *router, struct pci_dev *dev,
int pirq, int irq)
+{
+  outb(0x10+((pirq-1)>>1), 0x24);
+  unsigned int x;
+  x = inb(0x26);
+  x = ((pirq-1)&1) ? ((x&0x0f)|(irq<<4)) : ((x&0xf0)|(irq));
+  outb(x,0x26);
+}
+
+/*
   * ALI pirq entries are damn ugly, and completely undocumented.
   * This has been figured out from pirq tables, and it's not a pretty
   * picture.
@@ -609,6 +628,23 @@

  #endif

+static __init int pico_router_probe(struct irq_router *r, struct
pci_dev *router, u16 device)
+{
+  switch(device)
+  {
+    case 0x0002:
+      r->name = "PicoPower PT86C523";
+      r->get = pirq_pico_get;
+      r->set = pirq_pico_set;
+      return 1;
+
+    case 0x8002:
+      r->name = "PicoPower PT86C523 rev. BB+";
+      r->get = pirq_pico_get;
+      r->set = pirq_pico_set;
+      return 1;
+  }
+}

  static __init int intel_router_probe(struct irq_router *r, struct
pci_dev *router, u16 device)
  {
@@ -814,6 +850,7 @@
  }
  		
  static __initdata struct irq_router_handler pirq_routers[] = {
+        { 0x1066, pico_router_probe },
  	{ PCI_VENDOR_ID_INTEL, intel_router_probe },
  	{ PCI_VENDOR_ID_AL, ali_router_probe },
  	{ PCI_VENDOR_ID_ITE, ite_router_probe },

--End patch--

-- 
The best way to accelerate a Macintosh is at 9.8m sec sec.
- Marcus Dolengo


  reply	other threads:[~2005-04-26 19:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-25  7:36 [PATCH] 2.4.30 PicoPower IRQ router Sune Mølgaard
2005-04-26 15:40 ` Alessandro Amici
2005-04-26 19:00   ` Sune Mølgaard [this message]
2005-04-27 11:28     ` Domen Puncer
2005-04-27 18:24       ` Sune Mølgaard
2005-04-27 21:00         ` Jesper Juhl
2005-04-28 10:36           ` Sune Mølgaard
2005-04-30 12:34           ` Sune Mølgaard

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=426E8FE4.5040307@molgaard.org \
    --to=sune@molgaard.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mj@ucw.cz \
    /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