linux-kernel - Re: [patch 1/5] Staging: VME Framework for the Linux Kernel

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:	Tue, 11 Aug 2009 00:54:34 -0400
From:	Mike Frysinger <vapier.adi@...il.com>
To:	Martyn Welch <martyn.welch@...anuc.com>
Cc:	"Emilio G. Cota" <cota@...ap.org>, Greg K-H <gregkh@...e.de>,
	linux-kernel@...r.kernel.org, devel@...uxdriverproject.org,
	Sebastien Dugue <sebastien.dugue@...l.net>
Subject: Re: [patch 1/5] Staging: VME Framework for the Linux Kernel

On Mon, Aug 10, 2009 at 08:44, Martyn Welch wrote:
> For using the VME bus for communication between two SBCs, I think we could
> use the CRCSR space to provide some information about the resources used on
> each board for say, a virtual network driver like the rapidIO subsystem
> provides. Possibly using the "device tree" stuff used on PowerPC, Blackfin
> and Sparc archs (I believe) for passing device layout between the firmware
> and kernel at boot.

Blackfin doesnt use device trees and there are no plans to do so
-mike
--
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/