about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* .Kartik K. Agaram2021-07-251-9/+9
|
* .Kartik K. Agaram2021-07-251-5/+5
|
* .Kartik K. Agaram2021-07-251-4/+4
|
* shell: starting to implement arraysKartik K. Agaram2021-07-252-5/+65
|
* .Kartik K. Agaram2021-07-251-11/+10
|
* .Kartik K. Agaram2021-07-241-0/+3
|
* .Kartik K. Agaram2021-07-241-5/+4
|
* .Kartik K. Agaram2021-07-222-31/+0
|
* update memory map doc and anticipate a gotchaKartik K. Agaram2021-07-223-3/+15
|
* .Kartik K. Agaram2021-07-203-46/+46
|
* .Kartik K. Agaram2021-07-2039-531/+94
|
* .Kartik K. Agaram2021-07-2018-41/+41
| | | | | Update run instructions for linux/app/ examples, and make sure they are correct.
* .Kartik K. Agaram2021-07-204-1346/+2
| | | | | Delete the examples from Crenshaw. They're extremely rudimentary, and they were really just trial runs for the Mu toolchain.
* start work on running the Mu toolchain atop MuKartik K. Agaram2021-07-1914-14/+14
|
* .Kartik K. Agaram2021-07-192-10/+3
|
* .Kartik K. Agaram2021-07-192-3/+71
|
* error message when trying to jump to primitiveKartik K. Agaram2021-07-191-0/+15
|
* .Kartik K. Agaram2021-07-191-9/+9
|
* .Kartik K. Agaram2021-07-191-21/+0
|
* .Kartik K. Agaram2021-07-192-2/+1
|
* .Kartik K. Agaram2021-07-191-176/+0
|
* render functions in MRU orderKartik K. Agaram2021-07-194-45/+92
|
* .Kartik K. Agaram2021-07-171-2/+2
|
* .Kartik K. Agaram2021-07-162-1/+101
|
* forgot to `git add` a fileKartik K. Agaram2021-07-161-0/+1098
|
* .Kartik K. Agaram2021-07-162-3/+3
|
* .Kartik K. Agaram2021-07-166-1539/+1363
|
* .Kartik K. Agaram2021-07-162-1133/+23
|
* more powerful load-sectorsKartik K. Agaram2021-07-163-18/+46
|
* .Kartik K. Agaram2021-07-165-33/+33
|
* .Kartik K. Agaram2021-07-163-21/+0
|
* .Kartik K. Agaram2021-07-16241-9375/+18695
|
* .Kartik K. Agaram2021-07-1689-102/+293
|
* .Kartik K. Agaram2021-07-162-5/+5
|
* .Kartik K. Agaram2021-07-161-1/+1
|
* .Kartik K. Agaram2021-07-161-55/+0
|
* .Kartik K. Agaram2021-07-156-45929/+0
|
* .Kartik K. Agaram2021-07-141-0/+1217
|
* color dithering seems to be workingKartik K. Agaram2021-07-141-1/+8
|
* .Kartik K. Agaram2021-07-141-0/+1
|
* .Kartik K. Agaram2021-07-141-1/+1
|
* clarify a corner case in 2's complement integersKartik K. Agaram2021-07-141-0/+31
| | | | https://merveilles.town/@akkartik/106577885001702701
* dithering ppm files using all 256 colorsKartik K. Agaram2021-07-131-2/+205
| | | | | Not quite working yet, but yields an interesting 'sketching-like' effect.
* scaling the palette working on third attemptKartik K. Agaram2021-07-131-2/+16
| | | | | See commits b4e997adb8 and 2777479a94. This seems like a good sign that dithering is now extremely precise.
* get rid of our ugly rounding codeKartik K. Agaram2021-07-131-8/+1
| | | | | | | | | | | | | | | It turns out "truncating" the last 4 bits is actually more accurate, because it divides up the palette evenly. Before: 0-7 -> 0 8-0x17 -> 1 0x18-0x27 -> 2 ... 0xd8-0xe7 -> 0xe 0xe8-0xff -> 0xf The first interval is just 8 shades, and the final interval is 24 shades.
* clean up some unseemly specklesKartik K. Agaram2021-07-131-3/+2
| | | | | | | Turns out they were a bug after all, and scaling the palette was just making them more obvious. The bug: I was carefully clamping to 0xf0 to avoid rounding later, but I forgot to do so for values between 0xf0 and 0xff. As a result, some values could round up past 0xff and turn black.
* cleanupKartik K. Agaram2021-07-131-65/+5
|
* give up on .pgm files with color depths != 255Kartik K. Agaram2021-07-131-9/+5
| | | | | | Things kinda seem to work for color depths close to 255, but it isn't really the goal here, and I don't have the skills of numerical analysis to track this down.
* undoKartik K. Agaram2021-07-131-19/+7
|
* experimentKartik K. Agaram2021-07-131-7/+19
| | | | | Now scaling pixels to 255 levels looks a lot better. Still worse, though. On both t.pgm and barbara.pgm.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-14 10:05:16 +0000