-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
yaml --- r: 276027 b: refs/heads/master c: 90459ce h: refs/heads/master i: 276025: 3527d8e 276023: ec4bbd8 v: v3
- Loading branch information
Bob Liu
authored and
Tejun Heo
committed
Nov 22, 2011
1 parent
8ca50d4
commit d265994
Showing
223 changed files
with
1,928 additions
and
2,682 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,2 @@ | ||
--- | ||
refs/heads/master: cb3599926e3e7b3678583195effa61a03026ab0e | ||
refs/heads/master: 90459ce06f410b983540be56209c0abcbce23944 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,24 +1,22 @@ | ||
The I2C protocol knows about two kinds of device addresses: normal 7 bit | ||
addresses, and an extended set of 10 bit addresses. The sets of addresses | ||
do not intersect: the 7 bit address 0x10 is not the same as the 10 bit | ||
address 0x10 (though a single device could respond to both of them). | ||
address 0x10 (though a single device could respond to both of them). You | ||
select a 10 bit address by adding an extra byte after the address | ||
byte: | ||
S Addr7 Rd/Wr .... | ||
becomes | ||
S 11110 Addr10 Rd/Wr | ||
S is the start bit, Rd/Wr the read/write bit, and if you count the number | ||
of bits, you will see the there are 8 after the S bit for 7 bit addresses, | ||
and 16 after the S bit for 10 bit addresses. | ||
|
||
I2C messages to and from 10-bit address devices have a different format. | ||
See the I2C specification for the details. | ||
WARNING! The current 10 bit address support is EXPERIMENTAL. There are | ||
several places in the code that will cause SEVERE PROBLEMS with 10 bit | ||
addresses, even though there is some basic handling and hooks. Also, | ||
almost no supported adapter handles the 10 bit addresses correctly. | ||
|
||
The current 10 bit address support is minimal. It should work, however | ||
you can expect some problems along the way: | ||
* Not all bus drivers support 10-bit addresses. Some don't because the | ||
hardware doesn't support them (SMBus doesn't require 10-bit address | ||
support for example), some don't because nobody bothered adding the | ||
code (or it's there but not working properly.) Software implementation | ||
(i2c-algo-bit) is known to work. | ||
* Some optional features do not support 10-bit addresses. This is the | ||
case of automatic detection and instantiation of devices by their, | ||
drivers, for example. | ||
* Many user-space packages (for example i2c-tools) lack support for | ||
10-bit addresses. | ||
|
||
Note that 10-bit address devices are still pretty rare, so the limitations | ||
listed above could stay for a long time, maybe even forever if nobody | ||
needs them to be fixed. | ||
As soon as a real 10 bit address device is spotted 'in the wild', we | ||
can and will add proper support. Right now, 10 bit address devices | ||
are defined by the I2C protocol, but we have never seen a single device | ||
which supports them. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
/* | ||
* Copyright (C) 2006 Atmark Techno, Inc. | ||
* | ||
* This file is subject to the terms and conditions of the GNU General Public | ||
* License. See the file "COPYING" in the main directory of this archive | ||
* for more details. | ||
*/ | ||
|
||
#ifndef _ASM_MICROBLAZE_NAMEI_H | ||
#define _ASM_MICROBLAZE_NAMEI_H | ||
|
||
#ifdef __KERNEL__ | ||
|
||
/* This dummy routine maybe changed to something useful | ||
* for /usr/gnemul/ emulation stuff. | ||
* Look at asm-sparc/namei.h for details. | ||
*/ | ||
#define __emul_prefix() NULL | ||
|
||
#endif /* __KERNEL__ */ | ||
|
||
#endif /* _ASM_MICROBLAZE_NAMEI_H */ |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.