<@whitequark> does anyone want to debug a horrible USB issue?
<@whitequark> <...> BULK IN URBs not finishing
<me> is this a ZLP issue?
*pulls out OpenVizsla*
It was a ZLP issue. #USBNotEvenOncepic.twitter.com/ymXVirIXsG
If it ain't broke, I'll fix it!
I'm porting Linux to Apple Silicon Macs at @AsahiLinux.
http://patreon.com/marcan | http://github.com/sponsors/marcan
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Add this Tweet to your website by copying the code below. Learn more
Add this video to your website by copying the code below. Learn more
By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.
| Country | Code | For customers of |
|---|---|---|
| United States | 40404 | (any) |
| Canada | 21212 | (any) |
| United Kingdom | 86444 | Vodafone, Orange, 3, O2 |
| Brazil | 40404 | Nextel, TIM |
| Haiti | 40404 | Digicel, Voila |
| Ireland | 51210 | Vodafone, O2 |
| India | 53000 | Bharti Airtel, Videocon, Reliance |
| Indonesia | 89887 | AXIS, 3, Telkomsel, Indosat, XL Axiata |
| Italy | 4880804 | Wind |
| 3424486444 | Vodafone | |
| » See SMS short codes for other countries | ||
This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.
Hover over the profile pic and click the Following button to unfollow any account.
When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.
The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.
Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.
Get instant insight into what people are talking about now.
Follow more accounts to get instant updates about topics you care about.
See the latest conversations about any topic instantly.
Catch up instantly on the best stories happening as they unfold.
<@whitequark> does anyone want to debug a horrible USB issue?
<@whitequark> <...> BULK IN URBs not finishing
<me> is this a ZLP issue?
*pulls out OpenVizsla*
It was a ZLP issue. #USBNotEvenOncepic.twitter.com/ymXVirIXsG
Whenever I see OpenVizsla being used for real USB work I have creeping flashbacks to when I - like uh, 20 years ago - evangelized Desktop Linux; some projects may better be kept in a proof-of-concept stage. But maybe it wasn't _that_ bad? (OpenVizsla, I mean. KDE 1 surely was.)
Both OV1 and KDE1 were disasters, and both became usable by version 3 :-)
Did you realize an XMOS would be perfect for Glasgow as well? You get deterministic, event-driven IO, and you can program it in a C-like language, so no need to mess with RTL. XMOS has excellent USB support as well. You really should use that. It's great!
I don't think "programming in a C-like language" is inherently an advantage (quite the opposite!), but more importantly, while XMOS can probably match HX8K on many tasks, I don't think it can match ECP5
Sorry, that was meant to be ironic: OV1 used XMOS and was quite the disaster. OV3 switched to an FT2232H+FPGA, using migen and python, and was a wonderful universal development platform. XMOS performs great on paper but projects eventually fail for stupid (but valid) reasons.
oh. yeah I've never given XMOS more than a passing look, so I haven't even suspected it was supposed to be sarcastic.
As far as I can tell the sole decent use case for XMOS is USB audio (or maybe other audio). I have a DIY DSP thing running my speakers using an XMOS and it has better latency (0.25ms analog-to-analog, ish) than ~every high-end DSP box you can buy.
That's running 15 biquad EQ filters × 6 channels at 96kHz 32bit internal resolution (24bit codec), on two XMOS chips. Good luck getting that latency on a traditional DSP. But for anything else? Stay far, far, FAR away from XMOS.
In 2013 @0x111a and I designed a board that was essentially Glasgow (even the same 74LVC1T45 level translation), except with XMOS for lack of an open FPGA toolchain, and quickly came to the same assessment of the XMOS ecosystem.pic.twitter.com/eIiwtR8FBE
At least you weren't crazy enough to try to use that cursed dual-row QFN package.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.