[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1347523843.596.30.camel@linux-s257.site>
Date: Thu, 13 Sep 2012 16:10:43 +0800
From: joeyli <jlee@...e.com>
To: jeremy.kerr@...onical.com, Matthew Garrett <mjg@...hat.com>
Cc: linux-kernel@...r.kernel.org, "H. Peter Anvin" <hpa@...or.com>,
Matt Domsch <Matt_Domsch@...l.com>,
Peter Jones <pjones@...hat.com>
Subject: Re: [RFC,PATCH v2] efi: Add support for a UEFI variable filesystem
於 二,2012-09-11 於 15:23 +0800,lee joey 提到:
> From: Matthew Garrett <mjg@...hat.com>
>
> The existing EFI variables code only supports variables of up to 1024
> bytes. This limitation existed in version 0.99 of the EFI
> specification,
> but was removed before any full releases. Since variables can now be
> larger than a single page, sysfs isn't the best interface for this.
> So,
> instead, let's add a filesystem. Variables can be read, written and
> created, with the first 4 bytes of each variable representing its UEFI
> attributes. The create() method doesn't actually commit to flash since
> zero-length variables can't exist per-spec.
>
> Updates from Jeremy Kerr <jeremy.kerr@...onical.com>.
>
> Signed-off-by: Matthew Garrett <mjg@...hat.com>
> Signed-off-by: Jeremy Kerr <jeremy.kerr@...onical.com>
>
> ---
> v2: Add check for < 4-byte writes
Do we have plan to create a new kobject add to /sys/firmware/efi for
provide a fixed mount point to efivars fs?
e.g. /sys/firmware/efi/efivars
Or we just direct reuse current /sys/firmeware/efi/vars? But, that means
we need think for the backward compatibility if choice reuse vars
folder.
Thanks a lot!
Joey Lee
--
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/
Powered by blists - more mailing lists