[PATCH] Re: 2.4.2 yenta_socket problems on ThinkPad 240

Jeff Garzik (jgarzik@mandrakesoft.com)
Sat, 16 Jun 2001 17:11:40 -0400


This is a multi-part message in MIME format.
--------------66207676316662F835AEDC44
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Linus Torvalds wrote:
> As far as I can tell, the yenta code should _really_ do something like
>
> PCI_PROMARY_BUS: dev->subordinate->primary
> PCI_SECONDARY_BUS: dev->subordinate->secondary
> PCI_SUBORDINATE_BUS: dev->subordinate->subordinate
> PCI_SEC_LATENCY_TIMER: preferably settable, not just hardcoded to 176

Ah, nice. That produces numbers on my laptop that look a bit better.
Patch attached (which conflicts with the previous yenta.c patch).

I left 176 hardcoded for now, pending thinking on the rest of your
message...

-- 
Jeff Garzik      | Andre the Giant has a posse.
Building 1024    |
MandrakeSoft     |
--------------66207676316662F835AEDC44
Content-Type: text/plain; charset=us-ascii;
 name="yenta.patch"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="yenta.patch"

Index: drivers/pcmcia/yenta.c =================================================================== RCS file: /cvsroot/gkernel/linux_2_4/drivers/pcmcia/yenta.c,v retrieving revision 1.1.1.25.4.1 diff -u -r1.1.1.25.4.1 yenta.c --- drivers/pcmcia/yenta.c 2001/06/16 19:21:56 1.1.1.25.4.1 +++ drivers/pcmcia/yenta.c 2001/06/16 21:09:40 @@ -644,9 +644,9 @@ config_writeb(socket, PCI_LATENCY_TIMER, 168); config_writel(socket, PCI_PRIMARY_BUS, (176 << 24) | /* sec. latency timer */ - (dev->subordinate->number << 16) | /* subordinate bus */ - (dev->subordinate->number << 8) | /* secondary bus */ - dev->bus->number); /* primary bus */ + (dev->subordinate->subordinate << 16) | /* subordinate bus */ + (dev->subordinate->secondary << 8) | /* secondary bus */ + dev->subordinate->primary); /* primary bus */ /* * Set up the bridging state:

--------------66207676316662F835AEDC44--

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/