![]() | |||||||||||||
Messages in this thread |
On Thu, May 06, 2004 at 02:18:24PM +0200, Arjan van de Ven wrote: > On Thu, 2004-05-06 at 13:59, Matthew Wilcox wrote: > > On Thu, May 06, 2004 at 11:44:14AM +0100, Christoph Hellwig wrote: > > > On Thu, May 06, 2004 at 02:22:46PM +0530, Sourav Sen wrote: > > > > Hi, > > > > > > > > The following simple patch creates a read-only file > > > > "memmap" under <mount point>/firmware/efi/ in sysfs > > > > and exposes the efi memory map thru it. > > > > > > doesn't exactly fit into the one value per file approach, does it? > > > > It's not exactly modifiable. > > come on, it's the ideal hotplug memory interface ;) > should we try to unify the memory map exports between architectures > instead of matching the firmware-of-the-day for each architecture ?? Well, firmware-du-jour is what /sys/firmware/... is for ;-) I don't have a clear picture of what a hotplug memory interface would look like; and even if I did, I don't think the EFI memory map is of much help in that matter. -- "Next the statesmen will invent cheap lies, putting the blame upon the nation that is attacked, and every man will be glad of those conscience-soothing falsities, and will diligently study them, and refuse to examine any refutations of them; and thus he will by and by convince himself that the war is just, and will thank God for the better sleep he enjoys after this process of grotesque self-deception." -- Mark Twain - 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/ | ||||||||||||
| Last update: 2005-03-22 13:02 [from the cache] ©2003-2008 | |||||||||||||