Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
L
linux
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
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
nexedi
linux
Commits
600223fe
Commit
600223fe
authored
Oct 17, 2003
by
Anton Blanchard
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
ppc64: Fix for sym2 problem (first place that checked pci_set_mwi return code)
parent
cb57e089
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
8 additions
and
5 deletions
+8
-5
include/asm-ppc64/pci.h
include/asm-ppc64/pci.h
+8
-5
No files found.
include/asm-ppc64/pci.h
View file @
600223fe
...
@@ -35,11 +35,14 @@ struct pci_dev;
...
@@ -35,11 +35,14 @@ struct pci_dev;
static
inline
int
pcibios_prep_mwi
(
struct
pci_dev
*
dev
)
static
inline
int
pcibios_prep_mwi
(
struct
pci_dev
*
dev
)
{
{
/*
/*
* pSeries firmware sets cacheline size and hardware treats
* We would like to avoid touching the cacheline size or MWI bit
* MWI the same as memory write, so we dont change cacheline size
* but we cant do that with the current pcibios_prep_mwi
* or the MWI bit.
* interface. pSeries firmware sets the cacheline size (which is not
* the cpu cacheline size in all cases) and hardware treats MWI
* the same as memory write. So we dont touch the cacheline size
* here and allow the generic code to set the MWI bit.
*/
*/
return
1
;
return
0
;
}
}
extern
unsigned
int
pcibios_assign_all_busses
(
void
);
extern
unsigned
int
pcibios_assign_all_busses
(
void
);
...
...
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