9 May 2013 13:30
Re: lfs-chat Digest, Vol 1328, Issue 1
LM <lmemsm <at> gmail.com>
2013-05-09 11:30:47 GMT
2013-05-09 11:30:47 GMT
Aleksandar Kuktin wrote:
I'm beginning to think that way as well. Our local Linux users group was demoing a Raspberry Pi. They couldn't hook it directly to a monitor. Without X, they wouldn't have been able to view it on a monitor via the network.
Would be curious what small graphics or GUI libraries would be recommended for such a system. At present, I'm trying to concentrate on SDL, ncurses/pdcurses and FLTK. Am currently investigating if I can find enough replacements for programs I commonly use that only require lighter weight GUI libraries. For instance, I work with audacity a lot. Some other possibilities might be apcstudio (FLTK) or rezound (Fox Toolkit), but not sure if they offer all the same editing capabilities.
By the way, another non-X option besides Wayland is to use the framebuffer. There are various ports of common GUI libraries that work with DirectX and there are some interesting tools that work directly with framebuffer.
I still think that X without a desktop environment and with one or two
small graphical libraries is better.
I'm beginning to think that way as well. Our local Linux users group was demoing a Raspberry Pi. They couldn't hook it directly to a monitor. Without X, they wouldn't have been able to view it on a monitor via the network.
Would be curious what small graphics or GUI libraries would be recommended for such a system. At present, I'm trying to concentrate on SDL, ncurses/pdcurses and FLTK. Am currently investigating if I can find enough replacements for programs I commonly use that only require lighter weight GUI libraries. For instance, I work with audacity a lot. Some other possibilities might be apcstudio (FLTK) or rezound (Fox Toolkit), but not sure if they offer all the same editing capabilities.
By the way, another non-X option besides Wayland is to use the framebuffer. There are various ports of common GUI libraries that work with DirectX and there are some interesting tools that work directly with framebuffer.
Sincerely,
Laura
-- -- http://linuxfromscratch.org/mailman/listinfo/lfs-chat FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
In the 3.9-rc kernel there is a new cpufreq driver for Intel
SandyBridge CPUs, enabled by CONFIG_X86_INTEL_PSTATE. The help
says:
This driver provides a P state for Intel core processors.
The driver implements an internal governor and will become
the scaling driver and governor for Sandy bridge processors.
When this driver is enabled it will become the perferred
scaling driver for Sandy bridge processors.
Since I have a SandyBridge processor on this machine, I enabled
this setting. The first thing I noticed was that my own cpufreq
initscript failed - I set 'ondemand' as the .config default, and in
the initscript I set that for each core. But this driver only
provides powersave or performance. A workaround to set the old
acpi driver is to add intel_pstate=disable to the grub command line.
After fairly extensive testing, I can confirm that the new driver
is reasonable - my .config default of 'ondemand' brings up the
'powersave' setting which is not very useful - a setting slightly
slower than with powersave in the acpi driver, probably good for
battery life but painful when compiling :)
The 'performance' setting, OTOH, is good - with the acpi driver
'performance' stays at full speed (3300 MHz in my case), but with the
new P-state driver it falls back to the default 48% speed (1584 MHz
in my case) quickly, and ramps up towards full speed equally
quickly.
Testing builds of gcc-4.7.2 shows the new 'performance' setting is a
little faster (with -j4) than the old acpi 'ondemand'. A kernel
(x86_64) -j4 defconfig build is, however, marginally slower and one
build (hopefully just an outlier!) was quite a lot slower [ typically
6m52 for acpi, 6m57 for intel_pstate but that one build took 7m20 ].
So, for kernels >= 3.9 on SandyBridge use the 'performance' scaling
governor instead of 'ondemand' if you enable this new driver [ e.g.
test for the /sys/devices/system/cpu/intel_pstate/ directory in your
own initscript, or perhaps change the default setting in your
.config ].
This was a public information bulletin.
ĸen
--
das eine Mal als Tragödie, das andere Mal als Farce
RSS Feed