On Sun, 2003-01-12 at 21:27, Alan Cox wrote: > which currently has two problems Ross found > > 1. The processors or so fast we have to enforce the 400nS delay nowdays What about PCI write posting ? How can we enforce the 400ns delay here ? I suspect we can't read back from the taskfile registers after writing the command. Especially when using DMA, I think I remember Andre telling me even tapping alt status might not be safe... So we need to issue a read from the same bus path, but not on any taskfile register from this channel... hrm... any idea ? > 2. The code is racey in some situations with a shared IRQ because we > may get an IRQ after we set the handler but before we send the command, > or implemnted the other way the command can complete before we set the > handler. Yup, that's an old problem indeed. Ben. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Follow-Ups:
- Re: Linux 2.4.21-pre3-ac4Benjamin Herrenschmidt
- Re: Linux 2.4.21-pre3-ac4Alan Cox
- Re: Linux 2.4.21-pre3-ac4Ross Biro
- Linux 2.4.21-pre3-ac4Alan Cox
- Re: Linux 2.4.21-pre3-ac4Benjamin Herrenschmidt
- Prev by Date: [PATCH] Linux PnP Support 0.94 by Adam Belay
- Next by Date: Re: any chance of 2.6.0-test*?
- Previous by thread: Re: Linux 2.4.21-pre3-ac4
- Next by thread: Re: Linux 2.4.21-pre3-ac4
- Indexes:[Main][Thread]