On Thu, 2006-07-06 at 16:13 +0200, Haavard Skinnemoen wrote:
> > "DMA controller framework".... isn't that what drivers/dma was
> > recently invented for? If appropriate, you should probably use that.
> > If not, you should explain why, and perhaps we should get it fixed.
>
> It was written some time before the drivers/dma stuff. I suppose I
> should try to use the DMA subsystem instead.
>
> As I understand it, though, drivers/dma is mostly for memory-to-memory
> to transfers, while what I really need is memory-to-hardware and
> hardware-to-memory transfers.
With MMIO those are just a not-so-special case of memory-memory, surely?
If the new framework doesn't support that, it probably _should_.
> > You're a bit behind on syscall support -- I note you have
> > TIF_RESTORE_SIGMASK (which means you're ahead of x86_64) but you
> > haven't wired up ppoll() and pselect(), amongst others.
>
> I'll sync up with i386. By the way, are there any syscalls I
> _shouldn't_ have wired up? It's probably too late to remove any of them
> at this point, but if we get it sorted out quickly, we might get away
> with a shorter grace period than usual...
Looks OK -- I don't see any of the obvious ones like oldstat, oldfstat,
etc.
--
dwmw2
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
