From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Eric Smith <eric@brouhaha.com>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@transmeta.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
arjanv@redhat.com, mj@ucw.cz
Subject: Re: 2.4.2 yenta_socket problems on ThinkPad 240
Date: Fri, 15 Jun 2001 19:25:41 -0400 [thread overview]
Message-ID: <3B2A9975.D648D55B@mandrakesoft.com> (raw)
In-Reply-To: <20010615231413.17697.qmail@brouhaha.com>
Eric Smith wrote:
>
> On 6-Jun-2001, I reported:
> > I upgraded my IBM ThinkPad 240 (Type 2609-31U) from Red Hat 7.0 to
> > Red Hat 7.1, which uses the 2.4.2 kernel and the kernel PCMCIA drivers.
> > Before the upgrade, all my CardBus and PCMCIA devices were working fine.
> > Now the yenta_socket module seems to be causing problems, and none of
> > the cards work.
>
> Arjan van de Ven of Red Hat tracked my problem down to a broken BIOS,
> which is not configuring the TI PC1211 CardBus bridge correctly. Even
> IBM's latest BIOS for the ThinkPad 240, IRET75WW released 17-May-2001,
> has this problem. Apparently IBM has issued fixes for other ThinkPads
> because the problem occurs with Windows 2000, but since Windows 2000 is
> not supported on the ThinkPad 240, it is unlikely that they will fix it.
>
> A one line change to linux/include/asm-i386/pci.h fixes it:
>
> -#define pcibios_assign_all_busses() 0
> +#define pcibios_assign_all_busses() 1
>
> Given that this macro exists, I surmise that other people have been
> bitten by similar problems. So now my question is:
>
> Does it make sense to turn pcibios_assign_all_busses into a variable
> with a default value of zero, and implement a kernel argument to set it?
I believe Alan had mentioned something on IRC about seeing a case where
the CardBus bridge's secondary and subordinate bridge numbers were 1 on
bootup, but 0 after the yenta driver got ahold of it. So, there is the
potential that the yenta driver is not setting things up quite
correctly.
To answer your question, I wouldn't mind at all having a kernel command
line setting that turned the above into a variable...
I would love to just define it unconditionally for x86, but I believe
Martin said that causes problems with some hardware, and the way the
BIOS has set up that hardware. (details anyone?)
--
Jeff Garzik | Andre the Giant has a posse.
Building 1024 |
MandrakeSoft |
next prev parent reply other threads:[~2001-06-15 23:26 UTC|newest]
Thread overview: 15+ 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 [this message]
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 ` [PATCH] " Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2001-06-07 0:09 Eric Smith
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=3B2A9975.D648D55B@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;
as well as URLs for NNTP newsgroup(s).