WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Recent Posts

Pages: [1] 2 3 ... 10
Alpha Releases / Re: Tiny Core 12.0 Alpha 2 Testing
« Last post by GNUser on Today at 05:08:45 PM »
Hi, Juanito. I tested several more extensions.

These can be copied over from TCL11, they work as-is:

These need libffi6.tcz appended to their .dep files:

These need readline7.tcz appended to their .dep files:
Hi jazzbiker!
As we all are ageing, maybe we gradualy loose patience, so less tolerance for bullshit (in general).If I am not missleading, the web "standards" were not changed very much for "common users" confort.
 I mean I would like to do the same basic things on internet: secure online banking, reading text, see some static images, few movies or download them on /tmp or stream them, The audio/video container formats are near the same, and can be accesed by external special programs (ffmpeg, gstream?), downloaded (wget, curl). Next to nothing new here!

New is the fat/bloat in the last 12 years, from opera_9 to firefox_84;
Waste of more and more resources (hardware and software), electricity, with zero impact to users.
Hi, Jail Bill Gates!

Congratulations! :)
Hi, nick65go!

if talking about optimization in general we are searching for an extremum, and it can be minimum or maximum. Modern software is optimized for maximum size to comply with fixed standards (in case of browser html css JS and DOM, if I'm not missing any). Size of lynx.tcz with all deps is around 2M.
tcc.tcz is 120 K, gcc is 36 M.
Why are You so pessimistic and name this climax? I'm sure we'll see new shining tops very soon! Nobody would stop the progress! Keep smiling!
Hello everone!
I am logging in and typing this one out on my tiny core shell OS as we speak now

Its one small step for me to becoming a computer geak and avoiding bill gates produce
you say there were 2 sensors. no, only one sensor got used.
the only way to use the other sensor was to land the plane and reboot it. then the other sensor would be selected.
Regarding BadWolf browser, I expected to be minimalist by design, as author intended.
 But its size in TC11_x64 is over 109MB as tcz (so uncompressed). This is because it "is using"
adwaita-icon-theme.tcz   13225984,  12.61 MB
icu61.tcz                       13946880,  13.30 MB
icu65.tcz                       14299136,  13.64 MB !?
webkitgtk4.tcz                 23781376,  22.68 MB

All these 100 MB just for few (less than 10?) test-strings in menus and few icons. When the user just want a browser to navigate https sites with on/off options: javascript and images, and have audio/video/download with external programs.  How small is a web-browser static (no external libs) compiled?

I do not particularly care for this specific browser. But I wonder, in year 2021, is this the climax of optimization and minimal size for a modern browser? If yes, then I am disappointed by almost all linux distributions trends in bloated software.
Hi Jail Bill Gates
A lot of those types of programs require that X is running (GUI) and won't run in a shell.

I rick
I read some of the instruction manual and tried accessing the net
I managed to go to google, wikipida and youtube
I though somewhere in the instructioons it said you can view images in the shell terminal mode but not audio. As there are no image files displayed there what so ever!
Is there anyway I can view an image at all?

Might try and login to my accout hear and post from it on the tiny core shell OS soon
Raspberry Pi / Configuring goodix touch panel
« Last post by xenodius on Today at 10:26:30 AM »
Hello, I'm trying to configure a 'goodix' i2c touch screen on my Pi4B, piCore 12.0 armv7l-- I've seen jgrulichs post but from my understanding reading this and elsewhere, the 'new' way to configure these I2c devices is to use 'dtoverlay=___' in config.txt instead of some kind of magic modprobe string to specify the appropriate device tree overlay driver.

I have the following relevant modules loaded, among many:
Code: [Select]
touchscreen-5.4.51-piCore-v7l.tcz (which contains goodix.ko)

And I added the following in config.txt;
Code: [Select]

But the touchscreen still doesn't work. The script to setup this touchscreen on Raspbian, as near as I can tell, does the same things.

After booting with this config, the following files are created in the device tree;
Code: [Select]

These files contain a single line each, that looks like gibberish in nano... I'd guess, that setup still isn't correct. So I tried specifying the GPIO pins explicitly, e.g. dtoverlay=goodix,interrupt=4,reset=17 however their content remained identical. I also tried dtoverlay=i2c1 for kicks.
Code: [Select]
brcm,function: @^@^@^@^@^@^@^@
brcm,pins: ^@^@^@^D^@^@^@^Q
brcm,pull: ^@^@^@^B^@^@^@^B
name: goodix_pins^@
phandle: ^@^@^@

Looking at other threads for I2c generally on piCore (including the DS3231 RTC which I will setup next) I was able to use i2c-tools with only the touchscreen connected and verify it's detected on I2c.
Code: [Select]
sudo i2cdetect -y 1
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- 5d -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

So it seems I've got a problem with my setup. But I'm not really sure where else to look or go from here-- any suggestions or other docs I could look at would be greatly appreciated.
Hi Jail Bill Gates
A lot of those types of programs require that X is running (GUI) and won't run in a shell.
Pages: [1] 2 3 ... 10