Re: Emdebian sprint / runtime device fingerprinting in bootloader

2011-02-24 Thread Eric Cooper
On Thu, Feb 24, 2011 at 07:09:51AM +, Andy Green wrote: > Well saying that it's very similar, then listing differences like > GPIOs that could easily be runtime-detectable, doesn't really pin > down whether that's a problem or not. See the arch/arm/mach-kirkwood directory in the Linux tree. A

Re: Emdebian sprint / runtime device fingerprinting in bootloader

2011-02-23 Thread Andy Green
On 02/23/2011 06:21 PM, Somebody in the thread at some point said: On Wed, Feb 23, 2011 at 04:45:25PM +, Andy Green wrote: Maybe Steve Sakoman can suggest some example boards that will be difficult to tell apart at runtime, but it matters? Here's one example: the Seagate DockStar is very s

Re: Emdebian sprint / runtime device fingerprinting in bootloader

2011-02-23 Thread Eric Cooper
On Wed, Feb 23, 2011 at 04:45:25PM +, Andy Green wrote: > Maybe Steve Sakoman can suggest some example boards that will be > difficult to tell apart at runtime, but it matters? Here's one example: the Seagate DockStar is very similar to the Marvell Sheevaplug (same Kirkwood SoC), but has a dif

Re: Emdebian sprint / runtime device fingerprinting in bootloader

2011-02-23 Thread Andy Green
On 02/23/2011 10:28 AM, Somebody in the thread at some point said: Hi - Any scripting config left from kernel package install could be batched and deferred until first boot where it runs natively. Hmm this is a bit too far-looking for me I mention it because kernel post-install scriptlets