linux-kernel - Re: [PATCH 0/3 v6] drivers/bus: Freescale Management Complex bus driver patch series

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:	Thu, 26 Feb 2015 15:33:13 +0100
From:	Alexander Graf <agraf@...e.de>
To:	Stuart Yoder <stuart.yoder@...escale.com>,
	"arnd@...db.de" <arnd@...db.de>
CC:	Jose Rivera <German.Rivera@...escale.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
Subject: Re: [PATCH 0/3 v6] drivers/bus: Freescale Management Complex bus
 driver patch series



On 27.01.15 15:35, Stuart Yoder wrote:
> Hi Arnd/Alex,
> 
> German has posted an example driver for the fsl-mc bus in his RFC
> "[RFC PATCH 1/1] drivers/bus: fsl-mc object allocator driver".
> 
> In addition I have made available the skeleton for a driver for
> one of the objects/devices (crypto) that will be discovered on
> the bus:
>     https://github.com/stuyoder/linux
>     branch: fsl-ms-bus
> 
> ...it is not functional yet, but shows how a driver registers with
> the bus, get's probed, performs initialization.

Ok, so if I grasp this correctly the idea is that we have a driver
attaching to an individual device on the fsl-mc bus. That driver then
goes and allocates / blocks more devices from that bus as it initializes.

Is that model always possible? Which device would a NIC bind to for
example? I merely want to make sure we're not running ourselves into a
bad corner ;).


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