Messages in this thread | | | Subject | Re: [RFC 4/4] firewire: add mem1394 | From | Andi Kleen <> | Date | 05 Feb 2006 21:17:11 +0100 |
| |
Andrew Morton <akpm@osdl.org> writes:
> Johannes Berg <johannes@sipsolutions.net> wrote: > > > > +config IEEE1394_MEMDEV > > + tristate "IEEE1394 memory device support" > > + depends on IEEE1394 && EXPERIMENTAL > > + help > > + Say Y here if you want support for the ieee1394 memory device. > > + This is useful for debugging systems attached via firewire > > + since it usually allows you to read from and write to their memory, > > + depending on the controller and machine setup. > > 1394 is evil. Does this mean that if a machine is completely > dead-and-crashed, we can still suck all its memory out over 1394 with no > cooperation from the dead machine's kernel? If not, what limitations are > there?
Yes it can. BenH's firescope tool does this already using raw1394 (I have it working now on x86-64 too). I dont quite see the point of adding another kernel driver for it though. This can be all done fine in userspace.
-Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |