Re: Is the change to IDE probing really necessary?
- From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
- Date: Mon, 24 Nov 2008 18:54:53 +0000
O> On a machine requiring probing of the legacy ports, the suggested
probe_mask of 0x3f results in other devices being registered as IDE
devices. Suggest to the user they use 0x3 which is the old value of
probe_mask prior to commit 20df429dd6671804999493baf2952f82582869fa.
NAK
This makes no sense.
0x3F means probe them all.
0x03 means only peer at primary/secondary.
If you don't want them probed, don't pass arguments asking for them to be
probed!
"how is a distro install using modules meant to be fixed up?"
If the distribution supports non PCI bus boxes then pass a mask of 0x3F
on non PCI boxes. If the distribution is for PCI systems then leave the
mask alone.
If you want it to just work automatically use pata_legacy instead as that
automatically flips between probing ISA tertiary devices and leaving
things well alone according to the presence of PCI bus.
Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: Is the change to IDE probing really necessary?
- From: Mel Gorman
- Re: Is the change to IDE probing really necessary?
- References:
- Is the change to IDE probing really necessary?
- From: Mel Gorman
- Re: Is the change to IDE probing really necessary?
- From: Mel Gorman
- Is the change to IDE probing really necessary?
- Prev by Date: Re: [PATCH] MIPS: Make BUG() __noreturn.
- Next by Date: Re: about TRIM/DISCARD support and barriers
- Previous by thread: Re: Is the change to IDE probing really necessary?
- Next by thread: Re: Is the change to IDE probing really necessary?
- Index(es):