On 10/07/2016 10:31 AM, Alexey Brodkin wrote:
>> They are ugly I agree - but not portable - really ? The whole point is to
>> make
>> > this work on BE w/o changing the src code - this details remains hidden in
>> > an
>> > obscure header.
> That's what I learned the hard way.
> At least I was
On 10/07/2016 10:31 AM, Alexey Brodkin wrote:
>> They are ugly I agree - but not portable - really ? The whole point is to
>> make
>> > this work on BE w/o changing the src code - this details remains hidden in
>> > an
>> > obscure header.
> That's what I learned the hard way.
> At least I was
Hi Vineet,
On Thu, 2016-10-06 at 10:10 -0700, Vineet Gupta wrote:
> On 10/06/2016 02:10 AM, Alexey Brodkin wrote:
> >
> > >
> > > +struct mcip_bcr {
> > > +#ifdef CONFIG_CPU_BIG_ENDIAN
> > > + unsigned int pad3:8,
> > > + idu:1, llm:1, num_cores:6,
> > > +
Hi Vineet,
On Thu, 2016-10-06 at 10:10 -0700, Vineet Gupta wrote:
> On 10/06/2016 02:10 AM, Alexey Brodkin wrote:
> >
> > >
> > > +struct mcip_bcr {
> > > +#ifdef CONFIG_CPU_BIG_ENDIAN
> > > + unsigned int pad3:8,
> > > + idu:1, llm:1, num_cores:6,
> > > +
On 10/06/2016 02:10 AM, Alexey Brodkin wrote:
>> +struct mcip_bcr {
>> +#ifdef CONFIG_CPU_BIG_ENDIAN
>> +unsigned int pad3:8,
>> + idu:1, llm:1, num_cores:6,
>> + iocoh:1, gfrc:1, dbg:1, pad2:1,
>> + msg:1, sem:1,
On 10/06/2016 02:10 AM, Alexey Brodkin wrote:
>> +struct mcip_bcr {
>> +#ifdef CONFIG_CPU_BIG_ENDIAN
>> +unsigned int pad3:8,
>> + idu:1, llm:1, num_cores:6,
>> + iocoh:1, gfrc:1, dbg:1, pad2:1,
>> + msg:1, sem:1,
Hi Vineet,
On Wed, 2016-10-05 at 13:39 -0700, Vineet Gupta wrote:
> The IDU intc is technically part of MCIP (Multi-core IP) hence
> historically was only available in a SMP hardware build (and thus only
> in a SMP kernel build). Now that hardware restriction has been lifted,
> so a UP kernel
Hi Vineet,
On Wed, 2016-10-05 at 13:39 -0700, Vineet Gupta wrote:
> The IDU intc is technically part of MCIP (Multi-core IP) hence
> historically was only available in a SMP hardware build (and thus only
> in a SMP kernel build). Now that hardware restriction has been lifted,
> so a UP kernel
The IDU intc is technically part of MCIP (Multi-core IP) hence
historically was only available in a SMP hardware build (and thus only
in a SMP kernel build). Now that hardware restriction has been lifted,
so a UP kernel needs to support it.
This requires breaking mcip.c into parts which are
The IDU intc is technically part of MCIP (Multi-core IP) hence
historically was only available in a SMP hardware build (and thus only
in a SMP kernel build). Now that hardware restriction has been lifted,
so a UP kernel needs to support it.
This requires breaking mcip.c into parts which are
10 matches
Mail list logo
