summaryrefslogtreecommitdiff
path: root/layout.c
diff options
context:
space:
mode:
authorhailfinger <hailfinger@2b7e53f0-3cfb-0310-b3e9-8179ed1497e1>2011-12-14 22:25:15 +0000
committerhailfinger <hailfinger@2b7e53f0-3cfb-0310-b3e9-8179ed1497e1>2011-12-14 22:25:15 +0000
commitbaf84624cd340c9b8dfaa45c56060ab788f4945e (patch)
tree7d9ffba077715cf9e75c9f4a36d0d7f11a3181f6 /layout.c
parent98ddd394a74b53a26dab082be5981122b5e80927 (diff)
downloadflashrom-baf84624cd340c9b8dfaa45c56060ab788f4945e.tar.gz
Use struct flashctx instead of struct flashchip for flash chip access
struct flashchip is used only for the flashchips array and for operations which do not access hardware, e.g. printing a list of supported flash chips. struct flashctx (flash context) contains all data available in struct flashchip, but it also contains runtime information like mapping addresses. struct flashctx is expected to grow additional members over time, a prime candidate being programmer info. struct flashctx contains all of struct flashchip with identical member layout, but struct flashctx has additional members at the end. The separation between struct flashchip/flashctx shrinks the memory requirement of the big flashchips array and allows future extension of flashctx without having to worry about bloat. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> Acked-by: Michael Karcher <flashrom@mkarcher.dialup.fu-berlin.de> git-svn-id: https://code.coreboot.org/svn/flashrom/trunk@1473 2b7e53f0-3cfb-0310-b3e9-8179ed1497e1
Diffstat (limited to 'layout.c')
-rw-r--r--layout.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/layout.c b/layout.c
index d719a05..530ebd5 100644
--- a/layout.c
+++ b/layout.c
@@ -240,7 +240,7 @@ int find_next_included_romentry(unsigned int start)
return best_entry;
}
-int handle_romentries(struct flashchip *flash, uint8_t *oldcontents, uint8_t *newcontents)
+int handle_romentries(struct flashctx *flash, uint8_t *oldcontents, uint8_t *newcontents)
{
unsigned int start = 0;
int entry;