On Wednesday 22 September 2010 14:33:54 Alex Mihaylov wrote: > 2010/9/22 Christian Lamparter <chunkeey@xxxxxxxxxxxxxx>: > > why polling? They even say "14. Wait for the READY interrupt". > > This code from Sagrad: be careful with code... Haven't you read the comical license?! I'm not sure how ST react once they figured out that Sagrad leaked parts of the secret code, which might even cost them the FCC badge?! > SPIDRVReadReg32(SPI_ADRS_HOST_INTERRUPTS) - poll SPI register. IRQ > from STLC chip disabled. so what you are trying to say is that they have knowingly ignored their own specification? But who cares, as long as they do provide a "complete" driver+stack solution for their paying customers. > > Also, on power_on the driver currently waits just 10 and not 240 ms, > > maybe this could just be the problem... > > OK. I try change this. > note: 2.6.25.4 is very old and the spi subsystem (which isn't backported in cw) has changed quite a bit since then. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
