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
b1802b51
Commit
b1802b51
authored
Aug 14, 2003
by
Greg Kroah-Hartman
Committed by
Tom Rini
Aug 14, 2003
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
[PATCH] I2C: fix up the wording for the pii4x bugfix.
parent
b33e0eeb
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
1 deletion
+1
-1
drivers/i2c/busses/i2c-piix4.c
drivers/i2c/busses/i2c-piix4.c
+1
-1
No files found.
drivers/i2c/busses/i2c-piix4.c
View file @
b1802b51
...
@@ -164,7 +164,7 @@ static int piix4_setup(struct pci_dev *PIIX4_dev, const struct pci_device_id *id
...
@@ -164,7 +164,7 @@ static int piix4_setup(struct pci_dev *PIIX4_dev, const struct pci_device_id *id
/* Some BIOS will set up the chipset incorrectly and leave a register
/* Some BIOS will set up the chipset incorrectly and leave a register
in an undefined state (causing I2C to act very strangely). */
in an undefined state (causing I2C to act very strangely). */
if
(
temp
&
0x02
)
{
if
(
temp
&
0x02
)
{
dev_info
(
&
PIIX4_dev
->
dev
,
"
Fixed I2C problem on Force CPCI735
\n
"
);
dev_info
(
&
PIIX4_dev
->
dev
,
"
Worked around buggy BIOS (I2C)
\n
"
);
temp
=
temp
&
0xfd
;
temp
=
temp
&
0xfd
;
pci_write_config_byte
(
PIIX4_dev
,
SMBHSTCFG
,
temp
);
pci_write_config_byte
(
PIIX4_dev
,
SMBHSTCFG
,
temp
);
}
}
...
...
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