linux-kernel - Re: x86: IPC driver patch for Intel Moorestown platform

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, 21 Jul 2009 16:10:23 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	"Gurudatt, Sreenidhi B" <sreenidhi.b.gurudatt@...el.com>,
	"x86@...nel.org" <x86@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Alan Cox <alan@...ux.intel.com>
Subject: Re: x86: IPC driver patch for Intel Moorestown platform

> 1. built-in code adds platform-device for mrst_ipc
> 2. user space auto-loads the mrst_ipc driver
> 3. mrst_ipc driver creates child devices for each of its attached
>    devices

The devices talking to it already are devices - but they will be input
devices, watchdogs, etc. They already belong in existing classes.

I also don't believe the mrst ipc is enumerable either. If it was
enumerable it would make a lot more sense.

Having the mrst a platform device which itself contains the hardcoded
magic addresses definitely sounds a good move.
--
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/