3 ms·
1. There are, but they only exist in software. You have to write a different glue layer for virtually every device. And sometimes the device's model doesn't rea
by notalaser 11y ago
1. There are, but they only exist in software. You have to write a different glue layer for virtually every device. And sometimes the device's model doesn't really fit your driver's.
2. Not... really. Standards are supposed to do that. Many hardware manufacturers don't really implement them in a proper manner, and "whoever designed this flash controller should die a slow, painful death" is not something users care about.
3. If the device is well-documented and relatively standard-abiding, it's extremely fun if you're passionate about it and relatively painless if you're not. Otherwise, it's about as fun as digging a tunnel under Mordor with a toothpick.
- tracker1 11y agoEven then, most standards have parts that are obtuse to say the least, others that aren't really needed for a given application and others that are just open to some interpretation or otherwise not clearly defined... In the end, people tend to do the best they are able to in a given situation. Often that means ignoring some parts, and making assumptions for others so that your product can ship instead of waiting over a year for a standards body that might clarify something.