Why would you want to do that? The only reason why Linux should be ported to a handheld is that Linux should get more prestige, as the operating system that runs on more hardware platforms than any other. Linux (and other unices) are built for computers with disk drives and a keyboard. Most handhelds don't have neither or the hardware support is poor. Another problem is the lack of virtual memory. If there is none, the usual way of letting applications have control of a large memory area of their own is not efficient. If anyone is working on an open source operating system for handhelds (that isn't cLinux), mail me. I am interested.
It is supported by the hardware, but not by the OS. Greyscale uses twice as much RAM for graphics, so I guess that why they left it out. Remember that the first Pilot only had 256K of RAM. (or so) I have heard rumors that the PalmV hardware does not support grey scale though. The Palm VII is based on the same old hardware as always, though.
I don't believe that would work without disturbing the screen image. The user is looking straight at it, and all the vibration would be disturbing to watch.
The people behind the Star system (Star is the predecessor to all GUI systems today) used the simple argument that it does not have to be picked up to be used.
Håkan Lantz did invent the digitizer board that works with electromagnetic fields. Doug Engelbart invented the two-wheel mechanical mouse, the kind that has two conical wheels underneat, that you can see with old DEC terminals and workstations. Both inventions where made roughly at the same time, and both devices look and behave crudely like the mice we use today... but
neither of them invented the mouse that has a rubber-coated steel ball that we use today. Both people invented mouse-like devices, and called their invention "x-y position indicator".
I am a little curious wether JIT compilation is the way to go.. I believe it would be better if a JVM worked in two threads: one thread performs batch compilation and one thread interprets the JVM code, but switching to a compiled method when available. The interpreter should also move methods to the top of the compilation queue when they are entered. With the JIT approach, I am afraid that interactive programs would lose. The compiler would not use the idle time, whereas the concurrent approach would use it. .... Or is there something that I have not understood?
Slashdot Mirror
Why would you want to do that? The only reason why Linux should be ported to a handheld is that Linux should get more prestige, as the operating system that runs on more hardware platforms than any other.
Linux (and other unices) are built for computers with disk drives and a keyboard. Most handhelds don't have neither or the hardware support is poor.
Another problem is the lack of virtual memory. If there is none, the usual way of letting applications have control of a large memory area of their own is not efficient.
If anyone is working on an open source operating system for handhelds (that isn't cLinux), mail me. I am interested.
Too bad I can not participate:
1: I am unemployed,
2: I am sick for real. =)
It is supported by the hardware, but not by the OS.
Greyscale uses twice as much RAM for graphics, so I guess that why they left it out.
Remember that the first Pilot only had 256K of RAM. (or so)
I have heard rumors that the PalmV hardware does not support grey scale though.
The Palm VII is based on the same old hardware as always, though.
I don't believe that would work without disturbing the screen image. The user is looking straight at it, and all the vibration would be disturbing to watch.
The people behind the Star system (Star is the predecessor to all GUI systems today)
used the simple argument that it does not have to be picked up to be used.
Håkan Lantz did invent the digitizer board that works with electromagnetic fields.
Doug Engelbart invented the two-wheel mechanical mouse, the kind that has two conical
wheels underneat, that you can see with old DEC terminals and workstations. Both inventions where made roughly at the same time, and both
devices look and behave crudely like the mice we use today... but
neither of them invented the mouse that has a rubber-coated steel ball that we use today.
Both people invented mouse-like devices, and called their invention "x-y position indicator".
I am a little curious wether JIT compilation is the way to go.. I believe it would be better if a JVM worked in two threads: one thread performs batch compilation and one thread interprets the JVM code, but switching to a compiled method when available. The interpreter should also move methods to the top of the compilation queue when they are entered. With the JIT approach, I am afraid that interactive programs would lose. The compiler would not use the idle time, whereas the concurrent approach would use it.
.... Or is there something that I have not understood?
The domain "freshmeat.nu" is still available, if someone
wants to start a new site. Just my 2 cents.
Could anyone who has seen the site sift through
his/her browser cache and please put up a mirror.
I would like to see how it looked.