Hacker News new | past | comments | ask | show | jobs | submit login

I read a lot of kernel source at work. Every now and then I stumble across a comment or commit message like this which really gives me a chuckle and makes my day.

Also if you've ever actually used a Rockchip device you'll know they're absolute shit. Pirated Android phone images on incomplete Android device frameworks. They do bullshit like displaying on the TV at 1080p but the Netflix app displays at 720p in the top left corner. How unsurprising they fucked the calendar up too.

Before you go defend the brave embeddded developers from the mean nasty LKML, just think of all the consumers who've paid $100 for TV sticks which advertised an experience and didn't even come close to fulfilling that promise, with absolutely zero after-sales support or updates coming out of Rockchip. Fuck those guys.

If you are any form of hacker who takes pride in your work, you'll recognise this for the colossal fuck-up it actually is.




RK3288 from Rockchip is in several of the Chromebooks that are currently on the market, including Chromebook Flip and the ASUS Chromebit.

They perform quite well there if I may say so, when a proper amount of effort has been put into the software running on them.

The chips from Chinese manufacturers aren't really better or worse than most of the others out there, it's just that they often take shortcuts on the software side -- or rather, in particular the low-cost system OEM/ODMs do.


I've learned never to trust software implementations from third-party companies. They generally work well enough for pre-sales demonstrations, but you should always expect to do a bunch of post-sales bug fixing and feature implementation if you want to build a real product out of them. The same thing goes for BSPs from third parties.

Basically it's extremely rare to find third-party software that is completely trustworthy, even when you pay a bunch of money to ensure that this is the case. Hence why IEC62304 speaks directly to third-party software as enhancing risk. The best thing you can hope for is that the bugs are fairly benign or are easy to work around.


I've made pretty good money a few times by taking BSPs provided by vendors and transforming them into something actually usable and robust. And these aren't sketchy Chinese OEMs, these are well-established vendors.


Even Microsoft is not immune to date bugs - remember their Zunes freezing on a leap year?

http://bit-player.org/2009/the-zune-bug

This was in software, not hardware, more serious than just the date being wrong, and they didn't even provide a fix other than "wait until the day passes":

http://gizmodo.com/5121822/official-fix-for-the-zune-30-fail


typing this from a rockchip rk3188 laptop. with enough RAM, and a proper linux install, they're rock(sorry) solid.

This would certainly explain the weird date issue I had in Android last year, though.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: