You should try 2.4.6-pre5, it already includes a patch for you :)
pci=assign-busses on the command line.
--
Jeff Garzik | Andre the Giant has a posse.
Building 1024|
MandrakeSoft |
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
I wrote:
> 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?
After some discussion of various alternatives, including always turning it
on (bad for some systems), or writing a function to try to determin
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_
Alan Cox wrote:
>
> > 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?)
>
> Im not sure unconditionally is wise. However turning it into a routine th
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 pro
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.
6 matches
Mail list logo
