mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Haavard Skinnemoen <hskinnemoen@atmel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: AVR32 architecture patch against Linux 2.6.18-rc1 available
Date: Thu, 06 Jul 2006 15:34:52 +0100	[thread overview]
Message-ID: <1152196492.2987.185.camel@pmac.infradead.org> (raw)
In-Reply-To: <20060706161319.3ae0d9ef@cad-250-152.norway.atmel.com>

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


  reply	other threads:[~2006-07-06 14:35 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-06  8:52 Haavard Skinnemoen
2006-07-06  9:19 ` Andrew Morton
2006-07-06  9:51   ` Russell King
2006-07-06  9:58   ` Arjan van de Ven
2006-07-06 10:43     ` Haavard Skinnemoen
2006-07-06 15:17       ` Russell King
2006-07-06 10:03   ` Haavard Skinnemoen
2006-07-06 10:14     ` Andrew Morton
2006-07-06 13:57       ` Haavard Skinnemoen
2006-07-10  9:03       ` Haavard Skinnemoen
2006-07-10  9:31         ` Andrew Morton
2006-07-10  9:37         ` Andrew Morton
2006-07-10 11:04           ` Haavard Skinnemoen
2006-07-10  9:57         ` David Woodhouse
2006-07-10 11:25           ` Haavard Skinnemoen
2006-07-06 11:30     ` Thomas Gleixner
2006-07-06 11:50       ` Haavard Skinnemoen
2006-07-06 12:10         ` Thomas Gleixner
2006-07-06 11:58 ` David Woodhouse
2006-07-06 14:13   ` Haavard Skinnemoen
2006-07-06 14:34     ` David Woodhouse [this message]
2006-07-06 18:48       ` Haavard Skinnemoen
2006-07-06 23:17         ` David Woodhouse
2006-07-07 10:39   ` Haavard Skinnemoen
2006-07-07 10:44     ` Arjan van de Ven
2006-07-07  8:08 ` Nick Piggin
2006-07-07  8:18   ` Nick Piggin
2006-07-07 16:36   ` Haavard Skinnemoen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1152196492.2987.185.camel@pmac.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=hskinnemoen@atmel.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®