IVA and SGX not getting detected on 3630 ES1.2
Hi, I have a freshly built beagleboard xM on my desk which is giving me some trouble: xM revision A: [0.00] OMAP3630 ES1.0 (l2cache iva sgx neon isp 192mhz_clk ) new xM revision C: [0.00] OMAP3630 ES1.2 (l2cache neon isp 192mhz_clk ) So the IVA and SGX aren't getting detected, while they *are* present. Any hints where I should look to debug this? regards, Koen-- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: IVA and SGX not getting detected on 3630 ES1.2
Op 21 mrt. 2012, om 08:36 heeft Koen Kooi het volgende geschreven: Hi, I have a freshly built beagleboard xM on my desk which is giving me some trouble: xM revision A: [0.00] OMAP3630 ES1.0 (l2cache iva sgx neon isp 192mhz_clk ) new xM revision C: [0.00] OMAP3630 ES1.2 (l2cache neon isp 192mhz_clk ) So the IVA and SGX aren't getting detected, while they *are* present. Any hints where I should look to debug this? This is on 3.0.25 if that makes a difference.-- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: IVA and SGX not getting detected on 3630 ES1.2
xM revision A: [0.00] OMAP3630 ES1.0 (l2cache iva sgx neon isp 192mhz_clk ) new xM revision C: [0.00] OMAP3630 ES1.2 (l2cache neon isp 192mhz_clk ) on a rev. C -xm with kernel 3.2.8: [0.00] OMAP3630 ES1.2 (l2cache iva sgx neon isp 192mhz_clk ) maybe u-boot makes some difference? regards p. -- Peter Meerwald +43-664-218 (mobile) -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: IVA and SGX not getting detected on 3630 ES1.2
Op 21 mrt. 2012, om 13:29 heeft Peter Meerwald het volgende geschreven: xM revision A: [0.00] OMAP3630 ES1.0 (l2cache iva sgx neon isp 192mhz_clk ) new xM revision C: [0.00] OMAP3630 ES1.2 (l2cache neon isp 192mhz_clk ) on a rev. C -xm with kernel 3.2.8: [0.00] OMAP3630 ES1.2 (l2cache iva sgx neon isp 192mhz_clk ) maybe u-boot makes some difference? From what I can tell the kernel reads the register directly, so u-boot shouldn't make a difference. regards, Koen-- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
