linux-kernel - Re: DMA_ENGINE: can't use it without selecting a dma engine driver

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] [day] [month] [year] [list]

Message-ID: <4A391C06.2060302@intel.com>
Date:	Wed, 17 Jun 2009 09:38:30 -0700
From:	Dan Williams <dan.j.williams@...el.com>
To:	Dragos Tatulea <dtatulea@...acom.com>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Octavian Purdila <opurdila@...acom.com>
Subject: Re: DMA_ENGINE: can't use it without selecting a dma engine driver

Dragos Tatulea wrote:
> Hi,
> 
>>>        Just discovered that it's impossible to select the dma engine
>>> without compiling a dma engine driver from the kernel. What if I want to
>>> use a different dma engine?
>>>
>> Create a Kconfig entry for your driver in drivers/dma/Kconfig and have
>> it "select DMA_ENGINE".
> That's what I want to avoid. The dma engine driver is out of tree.
> 
> What is the rationale behind this? It seems (to me) impossible to have all
> such drivers in upstream.

It is very straightforward to have all drivers upstream, just send the 
code [1].

The rationale for this configuration scheme is to turn off a lot of 
unnecessary code when we know at build time that a dma driver will never 
be loaded.

If you must keep your driver out of tree simply maintain another out of 
tree patch that allows DMA_ENGINE to be manually enabled.

Regards,
Dan

[1]: http://www.kernel.org/doc/Documentation/SubmittingDrivers

--
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/