2011-07-21 15:43:14 +02:00
|
|
|
/*
|
libpayload: New CBFS to support multiple firmware media sources.
Upgrade CBFS in libpayload to use new media-based implementation from coreboot
( http://review.coreboot.org/#/c/2182/ ).
Old CBFS functions (cbfs_find, cbfs_find_file, get_cbfs_header) are still
supported, although the recommended way is to use new CBFS API.
To migrate your existing x86 payload source:
- Change cbfs_find to cbfs_get_file
- Change cbfs_find_file to cbfs_get_file_content
- Prefix every CBFS call with a CBFS_DEFAULT_MEDIA argument.
Ex, char *jpeg_data = cbfs_find_file("splash.jpg", CBFS_TYPE_BOOTSPLASH);
=> char *jpeg_data = cbfs_get_file_content(
CBFS_DEFAULT_MEDIA, "splash.jpg", CBFS_TYPE_BOOTSPLASH);
The legacy setup_cbfs_from_{ram,flash} is also supported, although the better
equivalent is to make a new media instance:
struct cbfs_media ram_media;
init_cbfs_ram_media(&ram_media, start, size);
char *data = cbfs_get_file_content(&ram_media, "myfile", my_type);
Verified by being successfully linked with filo.
Change-Id: If797bc7e3ba975d7e3be905c59424f7a93b8ce11
Signed-off-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-on: http://review.coreboot.org/2191
Tested-by: build bot (Jenkins)
Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
Reviewed-by: Anton Kochkov <anton.kochkov@gmail.com>
2013-01-25 05:42:40 +01:00
|
|
|
* This file is part of the libpayload project.
|
2011-07-21 15:43:14 +02:00
|
|
|
*
|
|
|
|
* Copyright (C) 2008 Jordan Crouse <jordan@cosmicpenguin.net>
|
2012-11-16 23:48:22 +01:00
|
|
|
* Copyright (C) 2012 Google, Inc.
|
2011-07-21 15:43:14 +02:00
|
|
|
*
|
|
|
|
* This file is dual-licensed. You can choose between:
|
|
|
|
* - The GNU GPL, version 2, as published by the Free Software Foundation
|
|
|
|
* - The revised BSD license (without advertising clause)
|
|
|
|
*
|
|
|
|
* ---------------------------------------------------------------------------
|
|
|
|
* This program is free software; you can redistribute it and/or modify
|
|
|
|
* it under the terms of the GNU General Public License as published by
|
|
|
|
* the Free Software Foundation; version 2 of the License.
|
|
|
|
*
|
|
|
|
* This program is distributed in the hope that it will be useful,
|
|
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
* GNU General Public License for more details.
|
|
|
|
*
|
|
|
|
* You should have received a copy of the GNU General Public License
|
|
|
|
* along with this program; if not, write to the Free Software
|
Remove address from GPLv2 headers
As per discussion with lawyers[tm], it's not a good idea to
shorten the license header too much - not for legal reasons
but because there are tools that look for them, and giving
them a standard pattern simplifies things.
However, we got confirmation that we don't have to update
every file ever added to coreboot whenever the FSF gets a
new lease, but can drop the address instead.
util/kconfig is excluded because that's imported code that
we may want to synchronize every now and then.
$ find * -type f -exec sed -i "s:Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, *MA[, ]*02110-1301[, ]*USA:Foundation, Inc.:" {} +
$ find * -type f -exec sed -i "s:Foundation, Inc., 51 Franklin Street, Suite 500, Boston, MA 02110-1335, USA:Foundation, Inc.:" {} +
$ find * -type f -exec sed -i "s:Foundation, Inc., 59 Temple Place[-, ]*Suite 330, Boston, MA *02111-1307[, ]*USA:Foundation, Inc.:" {} +
$ find * -type f -exec sed -i "s:Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.:Foundation, Inc.:" {} +
$ find * -type f
-a \! -name \*.patch \
-a \! -name \*_shipped \
-a \! -name LICENSE_GPL \
-a \! -name LGPL.txt \
-a \! -name COPYING \
-a \! -name DISCLAIMER \
-exec sed -i "/Foundation, Inc./ N;s:Foundation, Inc.* USA\.* *:Foundation, Inc. :;s:Foundation, Inc. $:Foundation, Inc.:" {} +
Change-Id: Icc968a5a5f3a5df8d32b940f9cdb35350654bef9
Signed-off-by: Patrick Georgi <pgeorgi@chromium.org>
Reviewed-on: http://review.coreboot.org/9233
Tested-by: build bot (Jenkins)
Reviewed-by: Vladimir Serbinenko <phcoder@gmail.com>
2015-03-26 15:17:45 +01:00
|
|
|
* Foundation, Inc.
|
2011-07-21 15:43:14 +02:00
|
|
|
* ---------------------------------------------------------------------------
|
|
|
|
* Redistribution and use in source and binary forms, with or without
|
|
|
|
* modification, are permitted provided that the following conditions
|
|
|
|
* are met:
|
|
|
|
* 1. Redistributions of source code must retain the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer.
|
|
|
|
* 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer in the
|
|
|
|
* documentation and/or other materials provided with the distribution.
|
|
|
|
* 3. The name of the author may not be used to endorse or promote products
|
|
|
|
* derived from this software without specific prior written permission.
|
|
|
|
*
|
|
|
|
* THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
|
|
|
|
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
|
|
* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
|
|
|
|
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
|
|
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
|
|
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
|
|
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
|
|
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
|
|
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
|
|
* SUCH DAMAGE.
|
|
|
|
* ---------------------------------------------------------------------------
|
|
|
|
*/
|
|
|
|
|
|
|
|
#ifndef _CBFS_CORE_H_
|
|
|
|
#define _CBFS_CORE_H_
|
|
|
|
|
libpayload: New CBFS to support multiple firmware media sources.
Upgrade CBFS in libpayload to use new media-based implementation from coreboot
( http://review.coreboot.org/#/c/2182/ ).
Old CBFS functions (cbfs_find, cbfs_find_file, get_cbfs_header) are still
supported, although the recommended way is to use new CBFS API.
To migrate your existing x86 payload source:
- Change cbfs_find to cbfs_get_file
- Change cbfs_find_file to cbfs_get_file_content
- Prefix every CBFS call with a CBFS_DEFAULT_MEDIA argument.
Ex, char *jpeg_data = cbfs_find_file("splash.jpg", CBFS_TYPE_BOOTSPLASH);
=> char *jpeg_data = cbfs_get_file_content(
CBFS_DEFAULT_MEDIA, "splash.jpg", CBFS_TYPE_BOOTSPLASH);
The legacy setup_cbfs_from_{ram,flash} is also supported, although the better
equivalent is to make a new media instance:
struct cbfs_media ram_media;
init_cbfs_ram_media(&ram_media, start, size);
char *data = cbfs_get_file_content(&ram_media, "myfile", my_type);
Verified by being successfully linked with filo.
Change-Id: If797bc7e3ba975d7e3be905c59424f7a93b8ce11
Signed-off-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-on: http://review.coreboot.org/2191
Tested-by: build bot (Jenkins)
Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
Reviewed-by: Anton Kochkov <anton.kochkov@gmail.com>
2013-01-25 05:42:40 +01:00
|
|
|
#include <endian.h>
|
|
|
|
#include <stddef.h>
|
|
|
|
#include <stdint.h>
|
2015-07-10 00:07:45 +02:00
|
|
|
#include <stdlib.h>
|
libpayload: New CBFS to support multiple firmware media sources.
Upgrade CBFS in libpayload to use new media-based implementation from coreboot
( http://review.coreboot.org/#/c/2182/ ).
Old CBFS functions (cbfs_find, cbfs_find_file, get_cbfs_header) are still
supported, although the recommended way is to use new CBFS API.
To migrate your existing x86 payload source:
- Change cbfs_find to cbfs_get_file
- Change cbfs_find_file to cbfs_get_file_content
- Prefix every CBFS call with a CBFS_DEFAULT_MEDIA argument.
Ex, char *jpeg_data = cbfs_find_file("splash.jpg", CBFS_TYPE_BOOTSPLASH);
=> char *jpeg_data = cbfs_get_file_content(
CBFS_DEFAULT_MEDIA, "splash.jpg", CBFS_TYPE_BOOTSPLASH);
The legacy setup_cbfs_from_{ram,flash} is also supported, although the better
equivalent is to make a new media instance:
struct cbfs_media ram_media;
init_cbfs_ram_media(&ram_media, start, size);
char *data = cbfs_get_file_content(&ram_media, "myfile", my_type);
Verified by being successfully linked with filo.
Change-Id: If797bc7e3ba975d7e3be905c59424f7a93b8ce11
Signed-off-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-on: http://review.coreboot.org/2191
Tested-by: build bot (Jenkins)
Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
Reviewed-by: Anton Kochkov <anton.kochkov@gmail.com>
2013-01-25 05:42:40 +01:00
|
|
|
|
2011-07-21 15:43:14 +02:00
|
|
|
/** These are standard values for the known compression
|
|
|
|
alogrithms that coreboot knows about for stages and
|
|
|
|
payloads. Of course, other CBFS users can use whatever
|
|
|
|
values they want, as long as they understand them. */
|
|
|
|
|
|
|
|
#define CBFS_COMPRESS_NONE 0
|
|
|
|
#define CBFS_COMPRESS_LZMA 1
|
|
|
|
|
|
|
|
/** These are standard component types for well known
|
|
|
|
components (i.e - those that coreboot needs to consume.
|
|
|
|
Users are welcome to use any other value for their
|
|
|
|
components */
|
|
|
|
|
|
|
|
#define CBFS_TYPE_STAGE 0x10
|
|
|
|
#define CBFS_TYPE_PAYLOAD 0x20
|
|
|
|
#define CBFS_TYPE_OPTIONROM 0x30
|
|
|
|
#define CBFS_TYPE_BOOTSPLASH 0x40
|
|
|
|
#define CBFS_TYPE_RAW 0x50
|
|
|
|
#define CBFS_TYPE_VSA 0x51
|
|
|
|
#define CBFS_TYPE_MBI 0x52
|
|
|
|
#define CBFS_TYPE_MICROCODE 0x53
|
|
|
|
#define CBFS_COMPONENT_CMOS_DEFAULT 0xaa
|
|
|
|
#define CBFS_COMPONENT_CMOS_LAYOUT 0x01aa
|
|
|
|
|
|
|
|
#define CBFS_HEADER_MAGIC 0x4F524243
|
2013-01-04 05:33:03 +01:00
|
|
|
#define CBFS_HEADER_VERSION1 0x31313131
|
|
|
|
#define CBFS_HEADER_VERSION2 0x31313132
|
|
|
|
#define CBFS_HEADER_VERSION CBFS_HEADER_VERSION2
|
2011-07-21 15:43:14 +02:00
|
|
|
|
libpayload: New CBFS to support multiple firmware media sources.
Upgrade CBFS in libpayload to use new media-based implementation from coreboot
( http://review.coreboot.org/#/c/2182/ ).
Old CBFS functions (cbfs_find, cbfs_find_file, get_cbfs_header) are still
supported, although the recommended way is to use new CBFS API.
To migrate your existing x86 payload source:
- Change cbfs_find to cbfs_get_file
- Change cbfs_find_file to cbfs_get_file_content
- Prefix every CBFS call with a CBFS_DEFAULT_MEDIA argument.
Ex, char *jpeg_data = cbfs_find_file("splash.jpg", CBFS_TYPE_BOOTSPLASH);
=> char *jpeg_data = cbfs_get_file_content(
CBFS_DEFAULT_MEDIA, "splash.jpg", CBFS_TYPE_BOOTSPLASH);
The legacy setup_cbfs_from_{ram,flash} is also supported, although the better
equivalent is to make a new media instance:
struct cbfs_media ram_media;
init_cbfs_ram_media(&ram_media, start, size);
char *data = cbfs_get_file_content(&ram_media, "myfile", my_type);
Verified by being successfully linked with filo.
Change-Id: If797bc7e3ba975d7e3be905c59424f7a93b8ce11
Signed-off-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-on: http://review.coreboot.org/2191
Tested-by: build bot (Jenkins)
Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
Reviewed-by: Anton Kochkov <anton.kochkov@gmail.com>
2013-01-25 05:42:40 +01:00
|
|
|
#define CBFS_HEADER_INVALID_ADDRESS ((void*)(0xffffffff))
|
|
|
|
|
2014-11-10 22:14:24 +01:00
|
|
|
/* this is the master cbfs header - it must be located somewhere available
|
|
|
|
* to bootblock (to load romstage). The last 4 bytes in the image contain its
|
|
|
|
* relative offset from the end of the image (as a 32-bit signed integer). */
|
libpayload: New CBFS to support multiple firmware media sources.
Upgrade CBFS in libpayload to use new media-based implementation from coreboot
( http://review.coreboot.org/#/c/2182/ ).
Old CBFS functions (cbfs_find, cbfs_find_file, get_cbfs_header) are still
supported, although the recommended way is to use new CBFS API.
To migrate your existing x86 payload source:
- Change cbfs_find to cbfs_get_file
- Change cbfs_find_file to cbfs_get_file_content
- Prefix every CBFS call with a CBFS_DEFAULT_MEDIA argument.
Ex, char *jpeg_data = cbfs_find_file("splash.jpg", CBFS_TYPE_BOOTSPLASH);
=> char *jpeg_data = cbfs_get_file_content(
CBFS_DEFAULT_MEDIA, "splash.jpg", CBFS_TYPE_BOOTSPLASH);
The legacy setup_cbfs_from_{ram,flash} is also supported, although the better
equivalent is to make a new media instance:
struct cbfs_media ram_media;
init_cbfs_ram_media(&ram_media, start, size);
char *data = cbfs_get_file_content(&ram_media, "myfile", my_type);
Verified by being successfully linked with filo.
Change-Id: If797bc7e3ba975d7e3be905c59424f7a93b8ce11
Signed-off-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-on: http://review.coreboot.org/2191
Tested-by: build bot (Jenkins)
Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
Reviewed-by: Anton Kochkov <anton.kochkov@gmail.com>
2013-01-25 05:42:40 +01:00
|
|
|
|
2011-07-21 15:43:14 +02:00
|
|
|
struct cbfs_header {
|
|
|
|
uint32_t magic;
|
|
|
|
uint32_t version;
|
|
|
|
uint32_t romsize;
|
|
|
|
uint32_t bootblocksize;
|
2015-07-14 22:29:04 +02:00
|
|
|
uint32_t align; /* fixed to 64 bytes */
|
2011-07-21 15:43:14 +02:00
|
|
|
uint32_t offset;
|
2012-11-16 23:48:22 +01:00
|
|
|
uint32_t architecture;
|
|
|
|
uint32_t pad[1];
|
2011-07-21 15:43:14 +02:00
|
|
|
} __attribute__((packed));
|
|
|
|
|
2015-07-14 22:29:04 +02:00
|
|
|
/* this used to be flexible, but wasn't ever set to something different. */
|
|
|
|
#define CBFS_ALIGNMENT 64
|
|
|
|
|
2012-11-16 23:48:22 +01:00
|
|
|
/* "Unknown" refers to CBFS headers version 1,
|
|
|
|
* before the architecture was defined (i.e., x86 only).
|
|
|
|
*/
|
|
|
|
#define CBFS_ARCHITECTURE_UNKNOWN 0xFFFFFFFF
|
|
|
|
#define CBFS_ARCHITECTURE_X86 0x00000001
|
ARM: Generalize armv7 as arm.
There are ARM systems which are essentially heterogeneous multicores where
some cores implement a different ARM architecture version than other cores. A
specific example is the tegra124 which boots on an ARMv4 coprocessor while
most code, including most of the firmware, runs on the main ARMv7 core. To
support SOCs like this, the plan is to generalize the ARM architecture so that
all versions are available, and an SOC/CPU can then select what architecture
variant should be used for each component of the firmware; bootblock,
romstage, and ramstage.
Old-Change-Id: I22e048c3bc72bd56371e14200942e436c1e312c2
Signed-off-by: Gabe Black <gabeblack@google.com>
Reviewed-on: https://chromium-review.googlesource.com/171338
Reviewed-by: Gabe Black <gabeblack@chromium.org>
Commit-Queue: Gabe Black <gabeblack@chromium.org>
Tested-by: Gabe Black <gabeblack@chromium.org>
(cherry picked from commit 8423a41529da0ff67fb9873be1e2beb30b09ae2d)
Signed-off-by: Isaac Christensen <isaac.christensen@se-eng.com>
ARM: Split out ARMv7 code and make it possible to have other arch versions.
We don't always want to use ARMv7 code when building for ARM, so we should
separate out the ARMv7 code so it can be excluded, and also make it possible
to include code for some other version of the architecture instead, all per
build component for cases where we need more than one architecture version
at a time.
The tegra124 bootblock will ultimately need to be ARMv4, but until we have
some ARMv4 code to switch over to we can leave it set to ARMv7.
Old-Change-Id: Ia982c91057fac9c252397b7c866224f103761cc7
Reviewed-on: https://chromium-review.googlesource.com/171400
Reviewed-by: Gabe Black <gabeblack@chromium.org>
Tested-by: Gabe Black <gabeblack@chromium.org>
Commit-Queue: Gabe Black <gabeblack@chromium.org>
(cherry picked from commit 799514e6060aa97acdcf081b5c48f965be134483)
Squashed two related patches for splitting ARM support into general
ARM support and ARMv7 specific pieces.
Change-Id: Ic6511507953a2223c87c55f90252c4a4e1dd6010
Signed-off-by: Isaac Christensen <isaac.christensen@se-eng.com>
Reviewed-on: http://review.coreboot.org/6782
Tested-by: build bot (Jenkins)
2013-10-01 08:00:33 +02:00
|
|
|
#define CBFS_ARCHITECTURE_ARM 0x00000010
|
2014-02-19 20:35:30 +01:00
|
|
|
#define CBFS_ARCHITECTURE_ARM64 0x00000011
|
2012-11-16 23:48:22 +01:00
|
|
|
|
2011-07-21 15:43:14 +02:00
|
|
|
/** This is a component header - every entry in the CBFS
|
|
|
|
will have this header.
|
|
|
|
|
|
|
|
This is how the component is arranged in the ROM:
|
|
|
|
|
|
|
|
-------------- <- 0
|
|
|
|
component header
|
|
|
|
-------------- <- sizeof(struct component)
|
|
|
|
component name
|
|
|
|
-------------- <- offset
|
|
|
|
data
|
|
|
|
...
|
|
|
|
-------------- <- offset + len
|
|
|
|
*/
|
|
|
|
|
|
|
|
#define CBFS_FILE_MAGIC "LARCHIVE"
|
|
|
|
|
|
|
|
struct cbfs_file {
|
|
|
|
char magic[8];
|
|
|
|
uint32_t len;
|
|
|
|
uint32_t type;
|
2015-09-16 18:53:40 +02:00
|
|
|
uint32_t attributes_offset;
|
2011-07-21 15:43:14 +02:00
|
|
|
uint32_t offset;
|
2015-09-16 18:53:40 +02:00
|
|
|
char filename[];
|
2011-07-21 15:43:14 +02:00
|
|
|
} __attribute__((packed));
|
|
|
|
|
2015-09-16 18:53:40 +02:00
|
|
|
/* Depending on how the header was initialized, it may be backed with 0x00 or
|
|
|
|
* 0xff. Support both. */
|
|
|
|
#define CBFS_FILE_ATTR_TAG_UNUSED 0
|
|
|
|
#define CBFS_FILE_ATTR_TAG_UNUSED2 0xffffffff
|
2015-07-10 00:07:45 +02:00
|
|
|
#define CBFS_FILE_ATTR_TAG_COMPRESSION 0x42435a4c
|
2015-09-16 18:53:40 +02:00
|
|
|
|
|
|
|
/* The common fields of extended cbfs file attributes.
|
|
|
|
Attributes are expected to start with tag/len, then append their
|
|
|
|
specific fields. */
|
|
|
|
struct cbfs_file_attribute {
|
|
|
|
uint32_t tag;
|
|
|
|
/* len covers the whole structure, incl. tag and len */
|
|
|
|
uint32_t len;
|
|
|
|
uint8_t data[0];
|
|
|
|
} __attribute__((packed));
|
|
|
|
|
2015-07-10 00:07:45 +02:00
|
|
|
struct cbfs_file_attr_compression {
|
|
|
|
uint32_t tag;
|
|
|
|
uint32_t len;
|
|
|
|
/* whole file compression format. 0 if no compression. */
|
|
|
|
uint32_t compression;
|
|
|
|
uint32_t decompressed_size;
|
|
|
|
} __attribute__((packed));
|
|
|
|
|
2015-09-16 18:53:40 +02:00
|
|
|
/* Given a cbfs_file, return the first file attribute, or NULL. */
|
|
|
|
struct cbfs_file_attribute *cbfs_file_first_attr(struct cbfs_file *file);
|
|
|
|
|
|
|
|
/* Given a cbfs_file and a cbfs_file_attribute, return the attribute that
|
|
|
|
* follows it, or NULL. */
|
|
|
|
struct cbfs_file_attribute *cbfs_file_next_attr(struct cbfs_file *file,
|
|
|
|
struct cbfs_file_attribute *attr);
|
|
|
|
|
2015-09-17 20:45:52 +02:00
|
|
|
/* Given a cbfs_file and an attribute tag, return the first instance of the
|
|
|
|
* attribute or NULL if none found. */
|
|
|
|
struct cbfs_file_attribute *cbfs_file_find_attr(struct cbfs_file *file,
|
|
|
|
uint32_t tag);
|
|
|
|
|
2011-07-21 15:43:14 +02:00
|
|
|
/*** Component sub-headers ***/
|
|
|
|
|
|
|
|
/* Following are component sub-headers for the "standard"
|
|
|
|
component types */
|
|
|
|
|
|
|
|
/** This is the sub-header for stage components. Stages are
|
|
|
|
loaded by coreboot during the normal boot process */
|
|
|
|
|
|
|
|
struct cbfs_stage {
|
|
|
|
uint32_t compression; /** Compression type */
|
|
|
|
uint64_t entry; /** entry point */
|
|
|
|
uint64_t load; /** Where to load in memory */
|
|
|
|
uint32_t len; /** length of data to load */
|
|
|
|
uint32_t memlen; /** total length of object in memory */
|
|
|
|
} __attribute__((packed));
|
|
|
|
|
|
|
|
/** this is the sub-header for payload components. Payloads
|
|
|
|
are loaded by coreboot at the end of the boot process */
|
|
|
|
|
|
|
|
struct cbfs_payload_segment {
|
|
|
|
uint32_t type;
|
|
|
|
uint32_t compression;
|
|
|
|
uint32_t offset;
|
|
|
|
uint64_t load_addr;
|
|
|
|
uint32_t len;
|
|
|
|
uint32_t mem_len;
|
|
|
|
} __attribute__((packed));
|
|
|
|
|
|
|
|
struct cbfs_payload {
|
|
|
|
struct cbfs_payload_segment segments;
|
|
|
|
};
|
|
|
|
|
|
|
|
#define PAYLOAD_SEGMENT_CODE 0x45444F43
|
|
|
|
#define PAYLOAD_SEGMENT_DATA 0x41544144
|
|
|
|
#define PAYLOAD_SEGMENT_BSS 0x20535342
|
|
|
|
#define PAYLOAD_SEGMENT_PARAMS 0x41524150
|
|
|
|
#define PAYLOAD_SEGMENT_ENTRY 0x52544E45
|
|
|
|
|
|
|
|
struct cbfs_optionrom {
|
|
|
|
uint32_t compression;
|
|
|
|
uint32_t len;
|
|
|
|
} __attribute__((packed));
|
|
|
|
|
|
|
|
#define CBFS_NAME(_c) (((char *) (_c)) + sizeof(struct cbfs_file))
|
|
|
|
#define CBFS_SUBHEADER(_p) ( (void *) ((((uint8_t *) (_p)) + ntohl((_p)->offset))) )
|
|
|
|
|
libpayload: New CBFS to support multiple firmware media sources.
Upgrade CBFS in libpayload to use new media-based implementation from coreboot
( http://review.coreboot.org/#/c/2182/ ).
Old CBFS functions (cbfs_find, cbfs_find_file, get_cbfs_header) are still
supported, although the recommended way is to use new CBFS API.
To migrate your existing x86 payload source:
- Change cbfs_find to cbfs_get_file
- Change cbfs_find_file to cbfs_get_file_content
- Prefix every CBFS call with a CBFS_DEFAULT_MEDIA argument.
Ex, char *jpeg_data = cbfs_find_file("splash.jpg", CBFS_TYPE_BOOTSPLASH);
=> char *jpeg_data = cbfs_get_file_content(
CBFS_DEFAULT_MEDIA, "splash.jpg", CBFS_TYPE_BOOTSPLASH);
The legacy setup_cbfs_from_{ram,flash} is also supported, although the better
equivalent is to make a new media instance:
struct cbfs_media ram_media;
init_cbfs_ram_media(&ram_media, start, size);
char *data = cbfs_get_file_content(&ram_media, "myfile", my_type);
Verified by being successfully linked with filo.
Change-Id: If797bc7e3ba975d7e3be905c59424f7a93b8ce11
Signed-off-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-on: http://review.coreboot.org/2191
Tested-by: build bot (Jenkins)
Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
Reviewed-by: Anton Kochkov <anton.kochkov@gmail.com>
2013-01-25 05:42:40 +01:00
|
|
|
#define CBFS_MEDIA_INVALID_MAP_ADDRESS ((void*)(0xffffffff))
|
|
|
|
#define CBFS_DEFAULT_MEDIA ((void*)(0x0))
|
|
|
|
|
|
|
|
/* Media for CBFS to load files. */
|
|
|
|
struct cbfs_media {
|
|
|
|
|
|
|
|
/* implementation dependent context, to hold resource references */
|
|
|
|
void *context;
|
2011-07-21 15:43:14 +02:00
|
|
|
|
libpayload: New CBFS to support multiple firmware media sources.
Upgrade CBFS in libpayload to use new media-based implementation from coreboot
( http://review.coreboot.org/#/c/2182/ ).
Old CBFS functions (cbfs_find, cbfs_find_file, get_cbfs_header) are still
supported, although the recommended way is to use new CBFS API.
To migrate your existing x86 payload source:
- Change cbfs_find to cbfs_get_file
- Change cbfs_find_file to cbfs_get_file_content
- Prefix every CBFS call with a CBFS_DEFAULT_MEDIA argument.
Ex, char *jpeg_data = cbfs_find_file("splash.jpg", CBFS_TYPE_BOOTSPLASH);
=> char *jpeg_data = cbfs_get_file_content(
CBFS_DEFAULT_MEDIA, "splash.jpg", CBFS_TYPE_BOOTSPLASH);
The legacy setup_cbfs_from_{ram,flash} is also supported, although the better
equivalent is to make a new media instance:
struct cbfs_media ram_media;
init_cbfs_ram_media(&ram_media, start, size);
char *data = cbfs_get_file_content(&ram_media, "myfile", my_type);
Verified by being successfully linked with filo.
Change-Id: If797bc7e3ba975d7e3be905c59424f7a93b8ce11
Signed-off-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-on: http://review.coreboot.org/2191
Tested-by: build bot (Jenkins)
Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
Reviewed-by: Anton Kochkov <anton.kochkov@gmail.com>
2013-01-25 05:42:40 +01:00
|
|
|
/* opens media and returns 0 on success, -1 on failure */
|
|
|
|
int (*open)(struct cbfs_media *media);
|
2011-07-21 15:43:14 +02:00
|
|
|
|
libpayload: New CBFS to support multiple firmware media sources.
Upgrade CBFS in libpayload to use new media-based implementation from coreboot
( http://review.coreboot.org/#/c/2182/ ).
Old CBFS functions (cbfs_find, cbfs_find_file, get_cbfs_header) are still
supported, although the recommended way is to use new CBFS API.
To migrate your existing x86 payload source:
- Change cbfs_find to cbfs_get_file
- Change cbfs_find_file to cbfs_get_file_content
- Prefix every CBFS call with a CBFS_DEFAULT_MEDIA argument.
Ex, char *jpeg_data = cbfs_find_file("splash.jpg", CBFS_TYPE_BOOTSPLASH);
=> char *jpeg_data = cbfs_get_file_content(
CBFS_DEFAULT_MEDIA, "splash.jpg", CBFS_TYPE_BOOTSPLASH);
The legacy setup_cbfs_from_{ram,flash} is also supported, although the better
equivalent is to make a new media instance:
struct cbfs_media ram_media;
init_cbfs_ram_media(&ram_media, start, size);
char *data = cbfs_get_file_content(&ram_media, "myfile", my_type);
Verified by being successfully linked with filo.
Change-Id: If797bc7e3ba975d7e3be905c59424f7a93b8ce11
Signed-off-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-on: http://review.coreboot.org/2191
Tested-by: build bot (Jenkins)
Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
Reviewed-by: Anton Kochkov <anton.kochkov@gmail.com>
2013-01-25 05:42:40 +01:00
|
|
|
/* returns number of bytes read from media into dest, starting from
|
|
|
|
* offset for count of bytes */
|
|
|
|
size_t (*read)(struct cbfs_media *media, void *dest, size_t offset,
|
|
|
|
size_t count);
|
|
|
|
|
|
|
|
/* returns a pointer to memory with count of bytes from media source
|
|
|
|
* starting from offset, or CBFS_MEDIA_INVALID_MAP_ADDRESS on failure.
|
|
|
|
* Note: mapped data can't be free unless unmap is called, even if you
|
|
|
|
* do close first. */
|
|
|
|
void * (*map)(struct cbfs_media *media, size_t offset, size_t count);
|
|
|
|
|
|
|
|
/* returns NULL and releases the memory by address, which was allocated
|
|
|
|
* by map */
|
|
|
|
void * (*unmap)(struct cbfs_media *media, const void *address);
|
|
|
|
|
|
|
|
/* closes media and returns 0 on success, -1 on failure. */
|
|
|
|
int (*close)(struct cbfs_media *media);
|
|
|
|
};
|
|
|
|
|
2015-07-10 00:07:45 +02:00
|
|
|
/* returns pointer to a file entry inside CBFS or NULL on error */
|
libpayload: New CBFS to support multiple firmware media sources.
Upgrade CBFS in libpayload to use new media-based implementation from coreboot
( http://review.coreboot.org/#/c/2182/ ).
Old CBFS functions (cbfs_find, cbfs_find_file, get_cbfs_header) are still
supported, although the recommended way is to use new CBFS API.
To migrate your existing x86 payload source:
- Change cbfs_find to cbfs_get_file
- Change cbfs_find_file to cbfs_get_file_content
- Prefix every CBFS call with a CBFS_DEFAULT_MEDIA argument.
Ex, char *jpeg_data = cbfs_find_file("splash.jpg", CBFS_TYPE_BOOTSPLASH);
=> char *jpeg_data = cbfs_get_file_content(
CBFS_DEFAULT_MEDIA, "splash.jpg", CBFS_TYPE_BOOTSPLASH);
The legacy setup_cbfs_from_{ram,flash} is also supported, although the better
equivalent is to make a new media instance:
struct cbfs_media ram_media;
init_cbfs_ram_media(&ram_media, start, size);
char *data = cbfs_get_file_content(&ram_media, "myfile", my_type);
Verified by being successfully linked with filo.
Change-Id: If797bc7e3ba975d7e3be905c59424f7a93b8ce11
Signed-off-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-on: http://review.coreboot.org/2191
Tested-by: build bot (Jenkins)
Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
Reviewed-by: Anton Kochkov <anton.kochkov@gmail.com>
2013-01-25 05:42:40 +01:00
|
|
|
struct cbfs_file *cbfs_get_file(struct cbfs_media *media, const char *name);
|
|
|
|
|
2015-07-10 00:07:45 +02:00
|
|
|
/*
|
|
|
|
* Returns pointer to a copy of the file content or NULL on error.
|
|
|
|
* If the file is compressed, data will be decompressed.
|
|
|
|
* The caller owns the returned memory.
|
|
|
|
*/
|
libpayload: New CBFS to support multiple firmware media sources.
Upgrade CBFS in libpayload to use new media-based implementation from coreboot
( http://review.coreboot.org/#/c/2182/ ).
Old CBFS functions (cbfs_find, cbfs_find_file, get_cbfs_header) are still
supported, although the recommended way is to use new CBFS API.
To migrate your existing x86 payload source:
- Change cbfs_find to cbfs_get_file
- Change cbfs_find_file to cbfs_get_file_content
- Prefix every CBFS call with a CBFS_DEFAULT_MEDIA argument.
Ex, char *jpeg_data = cbfs_find_file("splash.jpg", CBFS_TYPE_BOOTSPLASH);
=> char *jpeg_data = cbfs_get_file_content(
CBFS_DEFAULT_MEDIA, "splash.jpg", CBFS_TYPE_BOOTSPLASH);
The legacy setup_cbfs_from_{ram,flash} is also supported, although the better
equivalent is to make a new media instance:
struct cbfs_media ram_media;
init_cbfs_ram_media(&ram_media, start, size);
char *data = cbfs_get_file_content(&ram_media, "myfile", my_type);
Verified by being successfully linked with filo.
Change-Id: If797bc7e3ba975d7e3be905c59424f7a93b8ce11
Signed-off-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-on: http://review.coreboot.org/2191
Tested-by: build bot (Jenkins)
Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
Reviewed-by: Anton Kochkov <anton.kochkov@gmail.com>
2013-01-25 05:42:40 +01:00
|
|
|
void *cbfs_get_file_content(struct cbfs_media *media, const char *name,
|
2014-01-12 13:45:52 +01:00
|
|
|
int type, size_t *sz);
|
2011-07-21 15:43:14 +02:00
|
|
|
|
2013-07-01 13:57:37 +02:00
|
|
|
/* returns decompressed size on success, 0 on failure */
|
2011-07-21 15:43:14 +02:00
|
|
|
int cbfs_decompress(int algo, void *src, void *dst, int len);
|
libpayload: New CBFS to support multiple firmware media sources.
Upgrade CBFS in libpayload to use new media-based implementation from coreboot
( http://review.coreboot.org/#/c/2182/ ).
Old CBFS functions (cbfs_find, cbfs_find_file, get_cbfs_header) are still
supported, although the recommended way is to use new CBFS API.
To migrate your existing x86 payload source:
- Change cbfs_find to cbfs_get_file
- Change cbfs_find_file to cbfs_get_file_content
- Prefix every CBFS call with a CBFS_DEFAULT_MEDIA argument.
Ex, char *jpeg_data = cbfs_find_file("splash.jpg", CBFS_TYPE_BOOTSPLASH);
=> char *jpeg_data = cbfs_get_file_content(
CBFS_DEFAULT_MEDIA, "splash.jpg", CBFS_TYPE_BOOTSPLASH);
The legacy setup_cbfs_from_{ram,flash} is also supported, although the better
equivalent is to make a new media instance:
struct cbfs_media ram_media;
init_cbfs_ram_media(&ram_media, start, size);
char *data = cbfs_get_file_content(&ram_media, "myfile", my_type);
Verified by being successfully linked with filo.
Change-Id: If797bc7e3ba975d7e3be905c59424f7a93b8ce11
Signed-off-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-on: http://review.coreboot.org/2191
Tested-by: build bot (Jenkins)
Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
Reviewed-by: Anton Kochkov <anton.kochkov@gmail.com>
2013-01-25 05:42:40 +01:00
|
|
|
|
|
|
|
/* returns a pointer to CBFS master header, or CBFS_HEADER_INVALID_ADDRESS
|
|
|
|
* on failure */
|
|
|
|
const struct cbfs_header *cbfs_get_header(struct cbfs_media *media);
|
|
|
|
|
2011-07-21 15:43:14 +02:00
|
|
|
#endif
|