-
Notifications
You must be signed in to change notification settings - Fork 54
Add hardware support specification #43
Conversation
|
@skuusela can you comment if the USB ethernet is used in CI and if it has different hardware than listed here? |
93c11d6 to
5871b3b
Compare
|
@jlaako The way DUTs are connected in CI looks like this: https://github.com/01org/DAFT#1-overview. |
| - microSD | ||
|
|
||
| Following on-board devices/interfaces has not been tested. | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
have not been tested
doc/hardware.rst
Outdated
| USB Mass Storage | ||
| ---------------- | ||
|
|
||
| Devices compliant with USB Mass Storage device class has been tested to work. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
have been tested to work
doc/hardware.rst
Outdated
| ----------------- | ||
|
|
||
| Devices compliant with USB Communication Device Class (CDC) should work, but | ||
| has not been tested. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
have not been tested
| --------- | ||
|
|
||
| Devices compliant with USB Audio Class 1.0 and 2.0 should work, but has not | ||
| been tested. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
have not been tested
|
@skuusela OK, thanks, which driver at the client side talks to that interface? I assume it ends up as some class compliant device. |
|
@jlaako The driver seems to be cdc_ether. |
|
@skuusela ok, then we have at least partially tested USB CDC support so I can change that part in the doc from untested to tested. |
9bbdf05 to
2093305
Compare
|
@mythi I think this initial revision should be good to go now |
doc/hardware.rst
Outdated
|
|
||
| IoT Reference OS Kit supports a selection of hardware that have been tested to | ||
| work to a limited extent, specified here. IoT Reference OS Kit may also work | ||
| on other Intel(r) Architecture hardware, but it have not been tested. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
has not been tested
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
or validated?
Add a document listing supported validated and tested hardware and potential known pending hardware support items. Signed-off-by: Jussi Laako <jussi.laako@linux.intel.com>
|
@jlaako thanks. looks good |
* meta-iot-web 1e515ff...775f6c2 (6): > Merge pull request intel#46 from nagineni/update_restserver > iot-rest-api-server.bb: Update iot-rest-api-server to v0.5.0 > Merge pull request intel#45 from nagineni/node_gcc_7 > nodejs: Fix Node.js build errors with gcc7 > Merge pull request intel#43 from TizenTeam/sandbox/pcoval/on/master/latest > nodejs: Fix FTBFS by adding missing argument to d.getVar Signed-off-by: Sudarsana Nagineni <sudarsana.nagineni@intel.com>
Add a document listing supported validated and tested hardware and
potential known pending hardware support items.