linux-kernel - Re: Handling of modular boards

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120509084102.GA16228@mail.gnudd.com>
Date:	Wed, 9 May 2012 10:41:02 +0200
From:	Alessandro Rubini <rubini@...dd.com>
To:	linus.walleij@...aro.org
Cc:	broonie@...nsource.wolfsonmicro.com, swarren@...dotorg.org,
	sameo@...ux.intel.com, linux-embedded@...r.kernel.org,
	linux-kernel@...r.kernel.org, grinberg@...pulab.co.il,
	olof@...om.net, arnd@...b.de, linux-arm-kernel@...ts.infradead.org
Subject: Re: Handling of modular boards

Hello.

>> This is another issue - a similar set of problems does apply to some PCI
>> type cards where the PCI device is essentially a bridge to a typical
>> embedded system - though practically speaking it's much less severe.
> 
> I think Alessandro is working on a board like that right now, so looping
> in Ale to this discussion to get his attention...

> I think Alessandro is working on a board like that right now, so looping
> in Ale to this discussion to get his attention...

Yes, that's it. The vendor of my thing has wrapped everything under
pci headers, so the "typical embedded system", which actually is a
demasculated ARM SoC is self-described by PCI (no need for device tree)

A previous poster said:
>>> b) Doesn't integrate well with hotplug; the DT for the board
>>> configuration is static at boot. What if a board can be unplugged and
>>> another plugged in; a reboot or similar would be needed to adjust the
>>> kernel to this.

I think you need some enumeration mechanism in this case. Actually, I
think this will become common in the near future, as you can reprogram
your FPGA devices while the system runs.

The issue is real, and I'm involved in a self-description project; it
allows to use the well-known bus abstraction (with bus controller,
devices, drivers) to ease handling soft cores that may come and go
while the system is alive.

Thank you Linus for involving me, I'll now go to read the whole thread
/alessandro
--
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/