linux-kernel - Re: [PATCH v3 07/24] C6X: devicetree support

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:	Wed, 28 Sep 2011 16:57:34 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Mark Salter <msalter@...hat.com>
Cc:	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
	devicetree-discuss@...ts.ozlabs.org,
	Grant Likely <grant.likely@...retlab.ca>
Subject: Re: [PATCH v3 07/24] C6X: devicetree support

On Wednesday 28 September 2011, Mark Salter wrote:
> > Other architectures allow simply appending the device tree to the
> > kernel image file, which is more convenient for users and does
> > not require much kernel support. Have you tried this?
> 
> Well, I considered it. My main reason for doing it this way was one of
> debugging convenience. The debugger loads an ELF file and while I was
> making lots of device tree changes in the tree and in the code, it was
> more convenient to have one ELF file to deal with rather than an ELF
> file and a dtb. And the thought was to get rid of it altogether once
> bootloader support comes along. Maybe the thing to do would be to just
> rip it out of the kernel. It can almost as easily be post-processing
> step outside the kernel.

Ok, if you plan to properly support it in the boot loader anyway,
that's probably the best option.

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