Re: [PATCH v4 1/5] cramfs: direct memory access support
Christoph Hellwig <[email protected]>
| Newsgroups | org.kernel.vger.linux-embedded,org.infradead.lists.linux-mtd,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-fsdevel,org.kernel.vger.linux-kernel,org.kvack.linux-mm |
|---|---|
| Message-ID | <[email protected]> |
On Sun, Oct 01, 2017 at 06:27:11PM -0400, Nicolas Pitre wrote: > If you prefer, the physical address could be specified with a Kconfig > symbol just like the kernel link address. Personally I think it is best > to keep it along with the other root mount args. But going all the way > with a dynamic driver binding interface and a dummy intermediate name is > like using a sledge hammer to kill an ant: it will work of course, but > given the context it is prone to errors due to the added manipulations > mentioned previously ... and a tad overkill. As soon as a kernel enables CRAMFS_PHYSMEM this mount option is available, so you don't just need to think of your use case. The normal way for doings this would be to specify it in the device tree. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>