From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Eric Smith <eric@brouhaha.com>,
linux-kernel@vger.kernel.org, arjanv@redhat.com, mj@ucw.cz
Subject: [PATCH] Re: 2.4.2 yenta_socket problems on ThinkPad 240
Date: Sat, 16 Jun 2001 17:11:40 -0400 [thread overview]
Message-ID: <3B2BCB8C.85792582@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0106161153440.9942-100000@penguin.transmeta.com>
[-- Attachment #1: Type: text/plain, Size: 672 bytes --]
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 |
[-- Attachment #2: yenta.patch --]
[-- Type: text/plain, Size: 868 bytes --]
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:
prev parent reply other threads:[~2001-06-16 21:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-15 23:14 2.4.2 yenta_socket problems on ThinkPad 240 Eric Smith
2001-06-15 23:25 ` Jeff Garzik
2001-06-16 13:25 ` Alan Cox
2001-06-16 17:55 ` Jeff Garzik
2001-06-16 18:02 ` Alan Cox
2001-06-16 18:15 ` Linus Torvalds
2001-06-22 23:14 ` Eric Smith
2001-06-22 23:27 ` Jeff Garzik
2001-06-16 18:16 ` Linus Torvalds
2001-06-17 4:03 ` Albert D. Cahalan
2001-06-16 18:10 ` Linus Torvalds
2001-06-16 18:23 ` Alan Cox
2001-06-16 19:22 ` Linus Torvalds
2001-06-16 21:11 ` Jeff Garzik [this message]
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=3B2BCB8C.85792582@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjanv@redhat.com \
--cc=eric@brouhaha.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mj@ucw.cz \
--cc=torvalds@transmeta.com \
/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