HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
grate-driver
grate
C2013–2021
grate-driver / grate

grate

Open source Tegra 2/3/4 2D/3D user-space developer tools

3Distinct people
4Mentions
0Explicit recommenders
91GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Open source Tegra 2/3/4 2D/3D user-space developer tools

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year4 dated mentions

Observed mentions: 2013-04-08 01:10:21 UTC to 2021-10-07 09:53:33 UTC.

0122013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20132014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2021

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC202
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC101
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC000
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC000
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC110

What Hacker News says

4 sources
It's a good article. Those who prefer to have their phones disconnected from Google for whatever reason at least have some options to limit exposure, but unfortunately, preventing the mobile web browser in the phone from leaking information like location, history, and habits to Google (and plenty of others) is going to be really tough. Also, the article glossed over an important issue; the need to use closed-source proprietary binary blob drivers to make the hardware usable. With drivers running in kernel space, the potential damage of an intentionally or unintentionally bad driver is pretty much unlimited. The most problematic drivers are usually the graphics drivers due to complexity and their impact on both system and battery performance. Since the companies making the graphics chips (well, they're often just graphics cores within the
Read the rest
main processor IC rather than separate chips) like nVidia, Qualcomm, Arm Inc (mali), and Broadcom (to a lesser degree lately) refuse to release the documentation necessary for open source hackers to write drivers, tons of unnecessary effort is wasted in attempts to reverse engineer the binary blob drivers so open source drivers can be written. There are quite a few efforts under way to produce open source drivers for various graphics "chips" on various types of ARM systems. Here are a few links I've collected: http://freedreno.github.io/ http://bloggingthemonkey.blogspot.com/ http://limadriver.org/ https://gitorious.org/lima https://github.com/grate-driver/grate/wiki https://github.com/laanwj/etna_viv/wiki http://www.raspberrypi.org/a-birthday-present-from-broadcom/ https://news.ycombinator.com/item?id=7320828 I haven't seen anyone succeed in making a fully open source blob-free phone yet, but people are working towards that goal. Unfortunately, even if open source devs eventually solve all of the blob driver (and chip documentation!) problems, there will still be an unknown, untested, and unaudited chunk of code running on phones that cannot be legally altered; it's the baseband processor. http://en.wikipedia.org/wiki/Baseband_processor Since the baseband processor controls the radio(s), it's actually against the law (FCC in the US) to modify the broadcast/receive power levels or frequencies. As such, each baseband processor has to be tested and certified by the FCC, and any change means it has to be tested and recertified again.
In Android without the mothership

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.