linux-kernel - Re: [advice sought] EOMA68 kernel 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]

Message-ID: <20120310195105.6d301bd5@pyramind.ukuu.org.uk>
Date:	Sat, 10 Mar 2012 19:51:05 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	lkcl luke <luke.leighton@...il.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux on small ARM machines 
	<arm-netbook@...ts.phcomp.co.uk>
Subject: Re: [advice sought] EOMA68 kernel support

>  of particular concern is that a CPU card could be running on (small!)
> backup battery / supercapacitor whilst being hot-swapped, and thus
> that means that the LCD module (drivers/eoma68/lcd.ko?) would need to
> be loaded and unloaded from userspace (udev).  that's not going to be
> a problem, is it?  i may just be imagining skeletons in the closet,
> here.

Your device tree describes devices. Your bus creates them when you
hotplug and it removes them when you hot unplug. The rest is the drivers
problem to behave properly, and refcount right.

>  * it's the purposes to which the 16 GPIOs can be put that will be
> radically different from one I/O board to the next.  GPIO 0 could be
> "powerup for WIFI" on one I/O board, but "lid open/shut switch" on
> another.

It's "GPIO 0 of card X" and providing you remember that, watch your
refcounting and don't remap a new device over the address space of an old
one during a hotplug you should be fine.

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