public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Smith <eric@brouhaha.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.2 yenta_socket problems on ThinkPad 240
Date: 15 Jun 2001 23:14:13 -0000	[thread overview]
Message-ID: <20010615231413.17697.qmail@brouhaha.com> (raw)

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?
That way people with broken BIOSes could solve it by simply adding the
argument in their lilo.conf.  In an ideal world the BIOSes would get
fixed and such a workaround would be unnecessary, but in my experience
trying to get a vendor to fix a BIOS problem is an exercise in futility.

If no one is opposed to my proposed change, I'll be happy to generate a
suitable patch and send it in.

Thanks!
Eric Smith

             reply	other threads:[~2001-06-15 23:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-15 23:14 Eric Smith [this message]
2001-06-15 23:25 ` 2.4.2 yenta_socket problems on ThinkPad 240 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         ` [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=20010615231413.17697.qmail@brouhaha.com \
    --to=eric@brouhaha.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox