Subject: Re: more pciide problems...
To: matthew green <mrg@eterna.com.au>
From: Manuel Bouyer <bouyer@antioche.lip6.fr>
List: port-sparc
Date: 01/31/2001 16:05:34
On Wed, Jan 31, 2001 at 02:30:55PM +1100, matthew green wrote:
> 
> 
> so, i've almost gotten my U5 working properly with 2 ide disks and the ide
> cdrom drive, the latter being slave on the primary channel the disks being
> masters.  a good boot shows:
> 
> pciide0 at pci2 dev 3 function 0: CMD Technology PCI0646 (rev. 0x03)
> pciide0: bus-master DMA support present
> pciide0: primary channel configured to native-PCI mode
> pciide0: using vector 32 for native-PCI interrupt
> atapibus0 at pciide0 channel 0
> cd0 at atapibus0 drive 1: <CRD-8240B, 1997/12/02, 1.22> type 5 cdrom removable
> cd0: drive supports PIO mode 4, DMA mode 2
> wd0 at pciide0 channel 0 drive 0: <ST34342A>
> wd0: drive supports 16-sector PIO transfers, LBA addressing
> wd0: 4103 MB, 8894 cyl, 15 head, 63 sec, 512 bytes/sect x 8404830 sectors
> wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 2 (Ultra/33)
> wd0(pciide0:0:0): using PIO mode 4, DMA mode 2 (using DMA data transfers)
> cd0(pciide0:0:1): using PIO mode 4, DMA mode 2 (using DMA data transfers)
> pciide0: secondary channel configured to native-PCI mode
> wd1 at pciide0 channel 1 drive 0: <ST315320A>
> wd1: drive supports 16-sector PIO transfers, LBA addressing
> wd1: 14594 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 29888820 sectors
> wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 4 (Ultra/66)
> wd1(pciide0:1:0): using PIO mode 4, DMA mode 2 (using DMA data transfers)
> 
> 
> a good boot only happens after a powercycle.  after a reboot, i get:
> 
> 	pciide0: secondary channel ignored (disabled)
> 
> instead of the wd1 lines.
> 
> 
> any ideas?

Well, the channel is disabled for some reason, I suspect by the OF.
It's just a bit to reset in the PCI config space; but the driver doesn't touch
it because usually the user has explicitely disabled it in the BIOS
(yes, I know, it's PC centric, but we have to deal with it too).

We could have the driver clear the bit for native mode (in this case there's
no risk of conficts with another add-on board), based on a compile-time
option. Would this be enouth ?

--
Manuel Bouyer, LIP6, Universite Paris VI.           Manuel.Bouyer@lip6.fr
--