Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
A
ast2050-flashrom
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
3
Issues
3
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Raptor Engineering Public Development
ast2050-flashrom
Commits
63dab697
Commit
63dab697
authored
Mar 14, 2020
by
Raptor Engineering Development Team
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix FTBFS on POWER systems
parent
0951d2a2
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
0 deletions
+4
-0
internal.c
internal.c
+4
-0
No files found.
internal.c
View file @
63dab697
...
...
@@ -131,6 +131,7 @@ int register_superio(struct superio s)
int
is_laptop
=
0
;
int
laptop_ok
=
0
;
#if IS_X86 || IS_MIPS
static
void
internal_chip_writeb
(
const
struct
flashctx
*
flash
,
uint8_t
val
,
chipaddr
addr
);
static
void
internal_chip_writew
(
const
struct
flashctx
*
flash
,
uint16_t
val
,
...
...
@@ -155,6 +156,7 @@ static const struct par_master par_master_internal = {
.
chip_writel
=
internal_chip_writel
,
.
chip_writen
=
fallback_chip_writen
,
};
#endif
enum
chipbustype
internal_buses_supported
=
BUS_NONE
;
...
...
@@ -358,6 +360,7 @@ int internal_init(void)
}
#endif
#if IS_X86 || IS_MIPS
static
void
internal_chip_writeb
(
const
struct
flashctx
*
flash
,
uint8_t
val
,
chipaddr
addr
)
{
...
...
@@ -400,3 +403,4 @@ static void internal_chip_readn(const struct flashctx *flash, uint8_t *buf,
mmio_readn
((
void
*
)
addr
,
buf
,
len
);
return
;
}
#endif
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment