It seems Andrew Gallatin wrote: > > After recent ATA commits, my Promise UDMA66 controller is now running > its drives in PIO4 mode. Previously, UDMA66 was working fine. > > Here's a dmesg snippet: > > atapci0: <Promise UDMA66 controller> port 0xdf00-0xdf3f,0xdfe0-0xdfe3,0xdfa8-0xd > faf,0xdfe4-0xdfe7,0xdff0-0xdff7 mem 0xfc8a0000-0xfc8bffff irq 2 at device 2.0 on > pci0 > ata2: at 0xdff0 on atapci0 > ata3: at 0xdfa8 on atapci0 > <..> > ad4: 19092MB <ST320414A> [38792/16/63] at ata2-master PIO4 > > The controller itself looks like this: > > [EMAIL PROTECTED]:2:0: class=0x018000 card=0x4d33105a chip=0x4d38105a rev=0x01 > hdr=0x00 > vendor = 'Promise Technology Inc' > device = 'PDC20262 FastTrak66 EIDE Controller' > class = mass storage > > > I've found that I can recover from this problem by forcing > ATAPI_DEVICE() to always return 1. It seems to want to return 0 > for devices not on the primary ata controller. > > I'm confused.. What's the point of ATAPI_DEVICE()? Am I not allowed > to use extra controllers anymore?
ATAPI_DEVICE is used on those controllers that cannot do ATAPI DMA, the test here is bogusly reversed, I'll fix asap... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
