| Summary: | [sugarbay] parport_pc probe fail of 00:0b | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BSPs | Reporter: | wenhua.fan <wenhuax.fan> |
| Component: | bsps-configuration | Assignee: | Darren Hart <dvhart> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Low | CC: | bruce.ashfield, dvhart, ke.yu, wenhuax.fan, yp.bsp.watcher, yp.watcher |
| Version: | unspecified | ||
| Target Milestone: | 1.1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
wenhua.fan
2011-06-22 00:44:27 UTC
Bruce, have there been any relevant base or standard config changes that might cause this? Tom, any relevant sugarbay changes? Nothing that hits the sugarbay. We've got quite a few meta changes, but they have all been in the tree for sometime, and none are near parport support. so no great ideas here. There is no such issue in Yocto1.1 M2 RC3 testing. Tree/Branch: Poky/1.1_M2 Poky Commit id: fa4bcfdb73167f8159b88e5a4d711c0d37627a70 Image location: http://autobuilder03.jf.intel.com/crownbay-1.1_M2/nightly/20110717-1/machines/crownbay/x86_32/core-image-sato-sdk-live-crownbay-20110717223745.hddimg.bz2 Verify this bug. |