Hi Siarhei!

Am 20.03.2016 um 15:49 schrieb Siarhei Siamashka:
This patch is just unsafe if pushed alone, that's why it implicitly
depends on the other "fel: Move the temporary scratch buffer under the
IRQ stack" patch.

I see. My impression was that while "unclean" on its own, it's still functional - at least to a degree where stuff like "sunxi-fel sid" might actually allow device identification before doing more complicated stuff (in a second sunxi-fel invocation). But of course it's preferable to properly resolve the dependenices first.

And instead of cluttering the documentation with the "Use these commands
with caution!" warnings (which many people will miss or ignore anyway),
it's better to do a proper job in the first place.

It would simply give us something to point users to, if they try antics like "./sunxi-fel readl 0x88888888" and come back complaining "That always fails with: libusb usb_bulk_send error -7". (Just like you) I suspect people will do this anyway, no matter where / how we put up warning signs in the first place... :-P

Regards, B. Nortmann

--
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to