lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 27 Jun 2008 20:13:04 +0200
From:	Haavard Skinnemoen <haavard.skinnemoen@...el.com>
To:	David Brownell <david-b@...bell.net>
Cc:	Dan Williams <dan.j.williams@...el.com>,
	Adrian Bunk <bunk@...nel.org>,
	Pierre Ossman <drzeus-list@...eus.cx>,
	linux-kernel@...r.kernel.org, linux-embedded@...r.kernel.org,
	kernel@...32linux.org, "Nelson, Shannon" <shannon.nelson@...el.com>
Subject: Re: [PATCH v4 4/6] dmaengine: Make DMA Engine menu visible for
 AVR32 users

On Fri, 27 Jun 2008 09:37:21 -0700
David Brownell <david-b@...bell.net> wrote:

> On Thursday 26 June 2008, Dan Williams wrote:
> > I agree with removing the arch dependency, and I do not think we
> > necessarily need to add HAVE_DMA_ENGINE.
> 
> I think a HAVE_DMA_ENGINE would be better than what you're doing
> below:  moving the arch dependency into the network code, and
> adding this !HIGHMEM64G thing (which is really just a more subtle
> arch dependency).

The !HIGHMEM64G dependency wasn't added; it was there before. I happen
to believe the code that breaks HIGHMEM64G is rather ugly, but that's no
reason to NAK this particular patch. Besides, I'm not really that
interested in the XOR parts of the framework.

> Note that HAS_DMA is very different from having DMA engine support...
> one is a specific interface, the other is the generic mechanism with
> any of its numerous (and often peripheral-specific) interfaces.

They may be different, but you can't have DMA engine support on
platforms that don't provide the DMA mapping API. At least not at the
moment.

The patch looks good to me.

Haavard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ