Hi Dirk,
On 03/27/2013 08:06 AM, Dirk Behme wrote:
Hi Eric,
On 27.03.2013 15:00, Eric Nelson wrote:
Hi Fabio,
On 03/27/2013 06:37 AM, Fabio Estevam wrote:
On Wed, Mar 27, 2013 at 5:57 AM, Dirk Behme
wrote:
>>
The VPU library relies on the output of /proc/cpuinfo (specifically
the line
Hi Eric,
On 27.03.2013 15:00, Eric Nelson wrote:
Hi Fabio,
On 03/27/2013 06:37 AM, Fabio Estevam wrote:
On Wed, Mar 27, 2013 at 5:57 AM, Dirk Behme wrote:
Some additional rethinking: I missed that we have a Linux kernel, too ;)
c) It's the job of the Linux kernel to export the CPU revision
Hi Fabio,
On 03/27/2013 06:37 AM, Fabio Estevam wrote:
On Wed, Mar 27, 2013 at 5:57 AM, Dirk Behme wrote:
Some additional rethinking: I missed that we have a Linux kernel, too ;)
c) It's the job of the Linux kernel to export the CPU revision to the VPU
library. In case the Linux kernel compl
On 27.03.2013 14:37, Fabio Estevam wrote:
On Wed, Mar 27, 2013 at 5:57 AM, Dirk Behme wrote:
Some additional rethinking: I missed that we have a Linux kernel, too ;)
c) It's the job of the Linux kernel to export the CPU revision to the VPU
library. In case the Linux kernel completely ignores
On Wed, Mar 27, 2013 at 5:57 AM, Dirk Behme wrote:
> Some additional rethinking: I missed that we have a Linux kernel, too ;)
>
> c) It's the job of the Linux kernel to export the CPU revision to the VPU
> library. In case the Linux kernel completely ignores what we are doing in
> U-Boot and calc
On Wed, Mar 27, 2013 at 5:02 AM, Dirk Behme wrote:
> I'll check this.
>
> Rethinking about the issue here, my recent understanding is:
>
> a) We have a VPU library which only understands 0x63 (Quad) and 0x61
> (DualLite/Solo)
Correct.
> b) We have Troy's existing get_cpu_rev() [1] which seems t
On 27.03.2013 09:02, Dirk Behme wrote:
On 26.03.2013 18:04, Fabio Estevam wrote:
Hi Dirk,
On Tue, Mar 26, 2013 at 12:43 PM, Dirk Behme
wrote:
Hi Fabio,
On 26.03.2013 13:54, Fabio Estevam wrote:
Currently when booting a mx6 solo processor get_cpu_rev() returns
0x62xxx,
which
is an invalid
On 26.03.2013 18:04, Fabio Estevam wrote:
Hi Dirk,
On Tue, Mar 26, 2013 at 12:43 PM, Dirk Behme wrote:
Hi Fabio,
On 26.03.2013 13:54, Fabio Estevam wrote:
Currently when booting a mx6 solo processor get_cpu_rev() returns 0x62xxx,
which
is an invalid mx6 CPU revision.
Do you have somewhere
Hi Dirk,
On Tue, Mar 26, 2013 at 12:43 PM, Dirk Behme wrote:
> Hi Fabio,
>
>
> On 26.03.2013 13:54, Fabio Estevam wrote:
>>
>> Currently when booting a mx6 solo processor get_cpu_rev() returns 0x62xxx,
>> which
>> is an invalid mx6 CPU revision.
>
>
> Do you have somewhere a list of valid CPU rev
Hi Fabio,
On 26.03.2013 13:54, Fabio Estevam wrote:
Currently when booting a mx6 solo processor get_cpu_rev() returns 0x62xxx, which
is an invalid mx6 CPU revision.
Do you have somewhere a list of valid CPU revisions? From two points of
view:
a) the i.MX6 hardware spec
b) the VPU library
Hi Fabio,
On 03/26/2013 05:54 AM, Fabio Estevam wrote:
Currently when booting a mx6 solo processor get_cpu_rev() returns 0x62xxx, which
is an invalid mx6 CPU revision. This causes run-time problems when trying to use
VPU library in the kernel, as this library loads the VPU firmware according
to
Currently when booting a mx6 solo processor get_cpu_rev() returns 0x62xxx, which
is an invalid mx6 CPU revision. This causes run-time problems when trying to use
VPU library in the kernel, as this library loads the VPU firmware according
to the CPU type.
Fix get_cpu_rev() so that it correctly retu
12 matches
Mail list logo
