Hi Afzal, Thanks for the suggestion. This is something I was actually looking at just the other day. I contemplated changing it, but have not done so yet. I left it alone because I believe the folks that did all the core OMAP35x and LAN9221 timing and driver work knew way more than I about all this. Now, if there is a difference between the way the OMAP35x is clocked or setup and the way my AM35x is clocked or setup, then I would expect these values to change. So far however, I've not seen a difference, and I have not seen anyone else trying to wire up a 9221 to an AM35xx. This confuses me. Is the AM35xx not capable of supporting a 9221's timings for some reason? If it can support it, why would it seem everyone is still using the slower 9220? Even the TI reference materials suggest the LAN9220, http://processors.wiki.ti.com/index.php./Ethernet_Connectivity_via_GPMC.
I've had a thread (http://e2e.ti.com/support/dsp/sitara_arm174_microprocessors/f/416/p/172157/690750.aspx) sitting over at the TI E2E forums for a while now on this subject of GPMC, OMAP35x vs. AM35x, and the LAN9221. So far, I've not received any feedback. :-( Thanks for your thoughts! I may try fiddling a bit just to see if that helps. ----- Original Message ----- From: "Mohammed, Afzal" <af...@ti.com> To: CF Adad <cfa...@rocketmail.com> Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>; Tony Lindgren <t...@atomide.com>; "Shilimkar, Santosh" <santosh.shilim...@ti.com> Sent: Thursday, June 7, 2012 5:32 AM Subject: RE: Please help! AM35xx mm/slab.c BUG Hi "", On Wed, Jun 06, 2012 at 13:21:23, CF Adad wrote: > Thanks again. I'm really starting to think the GPMC almost has to be > contributing. Does adding cycle2cycle delay / bus turnaround prevent the issue ?, SMSC datasheet mentions about special restrictions on back to back read and write-read, reading BYTE_TEST should take care of it, not sure whether driver takes care of all scenarios as per datasheet. Perhaps cycle2cycledelay would help us achieve it if driver doesn't take care of it. Regards Afzal -- 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
