Hello again
> "next" please. "master" is only for bug fixes now, since the merge window is > closed. ACK > xilinx_iic.c ??? This really sounds like I2C. Please choose a different name. What about xilinx_irq? > >> The Makefile will select among uic.c or xilinx_iic.c > > Yes, this is possible. But IIRC then the microblaze CPU suport has the same or > at least a similar interrupt handler. Isn't there a way to use some interrupt > code on both CPU architectures? You are right, but I cannot see how to share code between architechtures... If WD don't have a good idea we should have here the xilinx iic code repeated. > >> ml507: >> As you know I have been sending patches for the ml507 board. I will >> wait until this patch in accepted until I resend the ml507 patch. Is >> this ok? > > To clarify: You will wait to send the ml507 board support patches until the > CPU & interrupt stuff is accepted? Yes, because the ml507 code depends directly on the CPU and the IRQ stuff. Best Regards -- Ricardo Ribalda http://www.eps.uam.es/~rribalda/ ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ U-Boot-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/u-boot-users
