i am out of current knowledge about common TV for about 10 years.
Currently in Poland there is aerial TV broadcasted in DVB-T standard.
There are TVs with builtin decoder/demodulator or separate
decoders/demodulator with HDMI output.
But how about just receiving demodulated data and letting
[ping]
on 28/01/2013 17:11 Andriy Gapon said the following:
Guys,
I wonder why the following is the case for the base gcc.
/usr/include/c++/4.2/bits/c++config.h:
/* Define if C99 functions or macros from wchar.h, math.h, complex.h,
stdio.h, and stdlib.h can be used or exposed. */
On 2013-02-01 14:01, Andriy Gapon wrote:
on 28/01/2013 17:11 Andriy Gapon said the following:
I wonder why the following is the case for the base gcc.
/usr/include/c++/4.2/bits/c++config.h:
/* Define if C99 functions or macros from wchar.h, math.h, complex.h,
stdio.h, and stdlib.h can be
on 01/02/2013 15:08 Dimitry Andric said the following:
On 2013-02-01 14:01, Andriy Gapon wrote:
on 28/01/2013 17:11 Andriy Gapon said the following:
I wonder why the following is the case for the base gcc.
/usr/include/c++/4.2/bits/c++config.h:
/* Define if C99 functions or macros from
On 1 Feb 2013, at 13:31, Andriy Gapon wrote:
cstdlib would provide e.g. std::strtoull only when _GLIBCXX_USE_C99 is
defined.
This is entirely consistent with the standard. strtoull() should only be
visible when compiling in C++11 mode, it is not part of C++98 / C++03.
David
On Friday 01 February 2013 13:46:59 Wojciech Puchar wrote:
i am out of current knowledge about common TV for about 10 years.
Currently in Poland there is aerial TV broadcasted in DVB-T standard.
There are TVs with builtin decoder/demodulator or separate
decoders/demodulator with HDMI output.
after reading quite recent topics about disabling/enabling write cache, i
tried to test in on desktop 3.5 drive
kern.cam.ada.write_cache: 1
kern.cam.ada.read_ahead: 1
kern.cam.ada.0.read_ahead: -1
kern.cam.ada.0.write_cache: -1
i tried writing 1 or 0 to kern.cam.ada.0.write_cache, and there
On Friday, February 01, 2013 1:23:26 am Tim Kientzle wrote:
Would still appreciate any suggestions for how to test these.
You can write a simple app to listen for UDP packets and have it join a
multicast group and have another machine on the same network write a packet
to
the
Looking at the cam ata code I can't see how those values would do
anything after booting.
I suspect they should be loader only tunables with the current code
and cant be changed on the fly for a disk that's already been
registered.
Try setting the values in /boot/loader.conf if you haven't
Investigating a bit more a device reset will also trigger the
change so after changing the value you can use camcontrol reset
to trigger the change to apply using e.g.
camcontrol reset 0:0:0
While this is stated in the man for ada its not obvious that
changing the sysctl without a reset won't
[ This topic is better discussed in -multimedia@, suggest that followups
drop -hackers@ ]
i am out of current knowledge about common TV for about 10 years.
Currently in Poland there is aerial TV broadcasted in DVB-T standard.
There are TVs with builtin decoder/demodulator or separate
Wojciech writes:
after reading quite recent topics about disabling/enabling write cache, i
tried to test in on desktop 3.5 drive
kern.cam.ada.write_cache: 1
kern.cam.ada.read_ahead: 1
kern.cam.ada.0.read_ahead: -1
kern.cam.ada.0.write_cache: -1
i tried writing 1 or 0 to
registered.
Try setting the values in /boot/loader.conf if you haven't already?
You can check the actual status of the disk itself using:-
camcontrol identify ada0
this proved your statement.
will check it out at next reboot.
Regards
Steve
- Original Message - From: Wojciech
Investigating a bit more a device reset will also trigger the
change so after changing the value you can use camcontrol reset
to trigger the change to apply using e.g.
camcontrol reset 0:0:0
THIS actually work.
And the results are disastrous. in spite of NCQ working and fully filled,
when
14 matches
Mail list logo