Alright, alright, what do I do now? I did NOT wire any ata devices, and
hints only list the on-motherboard ata controllers (one of them has a CD
drive attached to it, that's it):
hint.ata.0.at="isa"
hint.ata.0.port="0x1F0"
hint.ata.0.irq="14"
hint.ata.1.at="isa"
hint.ata.1.port="0x170"
hint.ata.1.irq="15"
-mi
On 31 Oct, Andrey A. Chernov wrote:
> On Wed, Oct 31, 2001 at 02:57:42 +0300, Andrey A. Chernov wrote:
>> On Tue, Oct 30, 2001 at 14:57:17 -0800, Peter Wemm wrote:
>>
>> > date: 2000/05/26 13:59:05; author: sos; state: Exp; lines: +8 -13
>> > If devclass_alloc_unit() is called with a wired unit #, and this is
>> > buzy, only search upwards for a free slot to use..
>> >
>> > This broke unit numbering on ATA systems where PCI attached
>> > controllers come before the mainboard ones...
>>
>> This need to be resolved somehow else, not by using next free slot
>> causing multiply consoles, keyboards, etc. detected (with panic).
>> Probably upper level numbering code, i.e. ATA needs to detect its
>> conflicts, not bus numbering code itself.
>
> Giving more details:
> ATA code must test wired slot, and, if it is busy, increase number to
> next free slot and give it to bus code afterwards.
-mi
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
