casta
Joined 19 years ago
Joined 19 years ago
I picked TinyStories-1M, synthesized via yosys against SKY130 PDK. It's GPT-Neo with 8 layers. At int8 it's ~30mm^2 per layer (including kv caches, multipliers and all the attention stuff). So it's 250 mm^2 for the full toy model.
I'm kinda surprised, I spent no time, so if you want to etch a toy model, you can do that (you can probably reduce the area significantly). If you want a mask for that is probably going to cost 100k though.
While Tokyo has one of the worst fertility rates, it's not like the rest of Japan is doing particularly well. Also, I was staying in Azabujuban and I was surprised by the amount of kids I saw there.
I do take multiple other rides a day and in the weekend though, so I hit 12 rides pretty quickly, probably in around 4 days.
Also, you could not cache a config as valid. The configuration validity depends on the current state of the display controller. For example, if a configuration of planes on one CRTC can be set might depend on how much bandwidth is currently required by another one. I remember having to get rid of framebuffer compression on one monitor if another monitor had a resolution above a certain threshold.
Planes rotation property can be 0,90, 180 and 270, you can also flip them: https://www.kernel.org/doc/html/v4.12/gpu/drm-kms.html#c.drm.... If I remember correctly I implemented/upstreamed a few of these properties support for Rockchip display controllers.
If you can rotate a specific buffer will likely depend on your display controller plus if it's tiled or not though, since rotating a linear buffer is going to destroy BW.
If you are writing code only for one specific display controller you can look at the drivers and just figure out which configs are ok.
If your DP supports it, you don't need to GPU composite for screenshots, you can use the write back connector.
This is what we were doing on ChromeOS.
For the "who can cook them" in the spreadsheet, I guess it's just a matter of what we're used to cook. I'm from Italy, she's from Malawi, I'm sure I could cook 'nsima and she could cook polenta.
We did solve the problem in a much easier way though. We do have 40 recipes we usually cycle through. I wrote them in a spreadsheet and marked them based on who can cook them, if it's brunch, lunch or dinner, quick or elaborate, summery or wintery.
Then in another sheet I just create a list of those recipes/dishes picked randomly based on the day of the month.
If we start the discussion "what do we eat tonight", I can just open the spreadsheet. 99% of the time proposing the option for that day on the sheet gives us closure and we're done.