[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [microblaze-uclinux] Questions about the Ethernet interface
More progress, but still not working properly - when the driver calls
request_irq, it doesn't specifiy the SA_INTERRUPT flag, meaning that the
driver interrupt handler is itself executed with interrupts still enabled.
I can't figure out what's going on with this interrupt, is it level or
edge sensitive? For some reason, I'm getting recursive interrupts
have to go home now, will be back on it tomrrow, getting ther eslowly :)
John Williams wrote:
> Hi Peter,
> haven't got the xenet working yet, but close - however have found a bug
> you might like to pass on to montavista.
> basically, it's because the irq for the device gets requested in
> xenet_open, however the xenet_ioctl call does an enable_irq(dev->irq).
> So, if you haven't opened the device before doing the ioctl, you end up
> enable an interrupt that has no handler installed. I'm not sure if
> linux is supposed to detect and block this situation, or whether it's up
> to the driver to put an interlock on the request_irq / enable_irq sequence.
> not a biggie, but thought I should let you know.
> microblaze-uclinux mailing list
> Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
> Mailing List Archive :
Dr John Williams, Research Fellow,
Reconfigurable Computing, School of ITEE
University of Queensland, Brisbane, Australia
Ph : (07) 3365 8305
microblaze-uclinux mailing list
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/