An embeddable version of KolibriOS carefully optimized for last-generation AMD Fusion APUs.

http://websvn.kolibrios.org/listing.php?repname=Kolibri+OS&path=%2Fkernel%2Fbranches%2FKolibri-A%2Ftrunk

Main features:
- faster graphics,
- extended PCI-express services
- driverless access to MMIO, DMA and Configspace blocks
- ROM boot options
- fast non-scalable vectorized fonts
- reduced kernel size ~60kB

Main applications:
- technical vision and wideband DAq,
- new hardware development/testing,
- resource-hungry embedded systems,
- Media-aimed OS,
- experimental KolibriOS concepts testing,
- Kolibri-B project development.

So, Kolibri can run on 64bit machines. I am right

Yes, it surely can.

Even MS-DOS can run on 64bit machines.
am I wrong?

Your right.

art_zh link you have given points on sources. Is there somewhere binary version, or better full distro

http://kolibrios.org/en/

will try it, maybe fall in love later

In this site I can download img file with 32 bit distro, but I want 64 bit Kolibri. Maybye I should compile Kolibri A kernel (link art_zh has given), and inject to image instead old 32 bit kernel.

Then you need to wait for a short while -- Kolibri64 is still under development

you asked could Kolibri run on a 64bit machine --
it surely can... in x86_32 mode

A binary image is here:

ftp://ftp.kolibrios.org/users/art_zh/-A/

NB: it will only run on AMD Fusion machines, see the source!

What sort of optimizations? Llanos CPUs parts were basically the same as 45nm K10s. The only very specific thing I recall hearing is that there was a dedicated pathway bewthem the CPU and GPU to transfer blocks of data internally instead of the CPU writting to RAM for the GPU to read from it.

i'm sad because I haven't access to any AMD Fusion machine. I tried in under qemu64 - no succes.

Apart of these architectural differences, every processor/chipset has its own specific hardware implementation: MSRs, GPIO pinouts, devices' ID and configuration space, system bus control, power control, SIO access etc.

An obvious way to resolve these platform-specific dependencies is to rely on ACPI and BIOS structures and (on the top OS level) to include unique device drivers to the OS API.

Kolibri-A does not use ACPI and minimally relies on BIOS/CoreBoot helpers. Instead, it communicates with the given hardware directly, in accordance with AMD's BKDG and other system references.

This approach dramatically reduces system latencies and code size; it found to be very useful for many embedded and hardware-development tasks...

macgub
... but (in the other hand) it will surely work on Fusion platworms only.