Re: GSoC: Generic DMA engine framework
Hi, On 2010-04-30 19:44:45 (+0200), Jakub Klama jc...@semihalf.com wrote: This summer I'll add generic mechanism for using general purpose DMA engines found in embedded system-on-chip devices. This will make possible to schedule transfers from kernel and userspace and will allow to use DMA in other devices using systemwide DMA engine. My earlier experience with kernel development was writing FreeBSD/arm port to TI DaVinci Digital-media system-on-chip - more details here: [1]. Development of this project will be done also on DaVinci - I'll provide implementation of its DMA engine as well as example DMA-enabled device driver - DaVinci's SD/MMC controller (current implementation uses only PIO transfers). You can read more details here: http://wiki.freebsd.org/SOC2010JakubKlama I will appreciate your comments and suggestions about this project. This looks like a very interesting project. I'm quite interested in seeing the idam(4) driver as I'm working on a driver for the hardware crypto engine in the 88F5182 (and later the 88F6xxx I hope) and it'd be much improved by DMA support. Good luck, Kristof ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: GSoC: Generic DMA engine framework
On 2010-05-03 22:12:28 (+0200), Rafal Jaworowski r...@semihalf.com wrote: Not sure how far you went with the crypto engine work, but be advised we already have completed the CESA driver, only I haven't managed to commit the code yet.. Let me know if you'd like to see / test drive this. Yes, I'd be quite interested to see how my attempts compare to your work. Does it support the Sheevaplug SoC or the 88F5182 (Orion)? I didn't study the Sheevaplug documentation in great detail but I believe the CESA is similar (but not identical) on the two chips. BTW: out of curiousity, what is the platform based on 88F5281 you're using? It's a TS-7800: http://www.embeddedarm.com/products/board-detail.php?product=TS-7800 Regards, Kristof ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: GSoC: Generic DMA engine framework
On 2010-05-03, at 21:51, Kristof Provost wrote: Hi, On 2010-04-30 19:44:45 (+0200), Jakub Klama jc...@semihalf.com wrote: This summer I'll add generic mechanism for using general purpose DMA engines found in embedded system-on-chip devices. This will make possible to schedule transfers from kernel and userspace and will allow to use DMA in other devices using systemwide DMA engine. My earlier experience with kernel development was writing FreeBSD/arm port to TI DaVinci Digital-media system-on-chip - more details here: [1]. Development of this project will be done also on DaVinci - I'll provide implementation of its DMA engine as well as example DMA-enabled device driver - DaVinci's SD/MMC controller (current implementation uses only PIO transfers). You can read more details here: http://wiki.freebsd.org/SOC2010JakubKlama I will appreciate your comments and suggestions about this project. This looks like a very interesting project. I'm quite interested in seeing the idam(4) driver as I'm working on a driver for the hardware crypto engine in the 88F5182 (and later the 88F6xxx I hope) and it'd be much improved by DMA support. Not sure how far you went with the crypto engine work, but be advised we already have completed the CESA driver, only I haven't managed to commit the code yet.. Let me know if you'd like to see / test drive this. BTW: out of curiousity, what is the platform based on 88F5281 you're using? Rafal ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: GSoC: Generic DMA engine framework
On 2010-05-03, at 22:22, Kristof Provost wrote: On 2010-05-03 22:12:28 (+0200), Rafal Jaworowski r...@semihalf.com wrote: Not sure how far you went with the crypto engine work, but be advised we already have completed the CESA driver, only I haven't managed to commit the code yet.. Let me know if you'd like to see / test drive this. Yes, I'd be quite interested to see how my attempts compare to your work. Does it support the Sheevaplug SoC or the 88F5182 (Orion)? I didn't study the Sheevaplug documentation in great detail but I believe the CESA is similar (but not identical) on the two chips. I believe the 88F5182 has CESA as well, although as far I can see the main difference is that while the 88F6xxx (and MV-78xxx) CESA has an associated (to some extent can be considered as dedicated) TDMA engine, the one in 88F5182 does not, and can only use the generic purpose engine (IDMA). Our driver assumes TDMA and was only tested with 88F6xxx and 78xxx, so it seems there's some work involved with getting this to work on the 5182. Let me carve the code out for your reference so that you can try to extend it to work wirh Orion. BTW: out of curiousity, what is the platform based on 88F5281 you're using? It's a TS-7800: http://www.embeddedarm.com/products/board-detail.php?product=TS-7800 Does the generic DB-88F5XXX kernel config and existing code work with this device, or have you had to modify anything? Rafal ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: GSoC: Generic DMA engine framework
On 2010-05-03 22:47:31 (+0200), Rafal Jaworowski r...@semihalf.com wrote: On 2010-05-03, at 22:22, Kristof Provost wrote: On 2010-05-03 22:12:28 (+0200), Rafal Jaworowski r...@semihalf.com wrote: Not sure how far you went with the crypto engine work, but be advised we already have completed the CESA driver, only I haven't managed to commit the code yet.. Let me know if you'd like to see / test drive this. Yes, I'd be quite interested to see how my attempts compare to your work. Does it support the Sheevaplug SoC or the 88F5182 (Orion)? I didn't study the Sheevaplug documentation in great detail but I believe the CESA is similar (but not identical) on the two chips. I believe the 88F5182 has CESA as well, although as far I can see the main difference is that while the 88F6xxx (and MV-78xxx) CESA has an associated (to some extent can be considered as dedicated) TDMA engine, the one in 88F5182 does not, and can only use the generic purpose engine (IDMA). Our driver assumes TDMA and was only tested with 88F6xxx and 78xxx, so it seems there's some work involved with getting this to work on the 5182. Let me carve the code out for your reference so that you can try to extend it to work wirh Orion. Thanks. BTW: out of curiousity, what is the platform based on 88F5281 you're using? It's a TS-7800: http://www.embeddedarm.com/products/board-detail.php?product=TS-7800 Does the generic DB-88F5XXX kernel config and existing code work with this device, or have you had to modify anything? I've disabled PCI but that's about it. Regards, Kristof ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
