On Wed, Sep 30, 2015 at 02:21:18PM +, Shivraj Patil wrote:
>
> On Wed, Sep 30, 2015 at 07:03:46PM +0530, shivraj.pa...@imgtec.com wrote:
> > From: Shivraj Patil
> [...]
>
> > +static int get_cpuinfo(uint32_t *hwcap) {
> > +FILE *f = fopen("/proc/cpuinfo", "r");
>
> under qemu i get thi
On Wed, Sep 30, 2015 at 02:23:43PM +, Shivraj Patil wrote:
>
> imgtec.com> writes:
>
> > +FILE *f = fopen("/proc/cpuinfo", "r");
>
> Is this what every other software for mips does?
> How does the kernel (or whatever sets cpuinfo) know?
>
> Shivraj:- We have used generic cpuinfo as it
On Wed, Sep 30, 2015 at 02:21:18PM +, Shivraj Patil wrote:
>
> On Wed, Sep 30, 2015 at 07:03:46PM +0530, shivraj.pa...@imgtec.com wrote:
> > From: Shivraj Patil
> [...]
>
> > +static int get_cpuinfo(uint32_t *hwcap) {
> > +FILE *f = fopen("/proc/cpuinfo", "r");
>
> under qemu i get this
imgtec.com> writes:
> +FILE *f = fopen("/proc/cpuinfo", "r");
Is this what every other software for mips does?
How does the kernel (or whatever sets cpuinfo) know?
Shivraj:- We have used generic cpuinfo as it is unrestricted to access from
user space compared to the kernel setting hwcaps
On Wed, Sep 30, 2015 at 07:03:46PM +0530, shivraj.pa...@imgtec.com wrote:
> From: Shivraj Patil
[...]
> +static int get_cpuinfo(uint32_t *hwcap) {
> +FILE *f = fopen("/proc/cpuinfo", "r");
under qemu i get this:
cpu_flags(raw) = 0x
cpu_flags_str(raw) =
cpu_flags(effective) = 0x
On Wed, Sep 30, 2015 at 07:03:46PM +0530, shivraj.pa...@imgtec.com wrote:
> From: Shivraj Patil
[...]
> +static int get_cpuinfo(uint32_t *hwcap)
> +{
> +FILE *f = fopen("/proc/cpuinfo", "r");
under qemu i get this:
cpu_flags(raw) = 0x
cpu_flags_str(raw) =
cpu_flags(effective) = 0x00
imgtec.com> writes:
> +FILE *f = fopen("/proc/cpuinfo", "r");
Is this what every other software for mips does?
How does the kernel (or whatever sets cpuinfo) know?
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.or
