RE: [Ltib] MPC8313 question - again

[Vijay . Nikam]

> I think I understand the dts file for the bottom interrupt ID numbers,
> but I am not so sure about the top eTEC interrupts.

Basically device tree (dts) describes the system hardware and boot program loads a device tree into a kernel's memory. And a dts is a tree data structure with nodes that describes the physical devices in a system. So bottom interrupt ID numbers are physicals ones which are given in the processor manual. And the top interrupts are virtual irq which kernel gives when you register your interrupt handler and you need to use virtual irq only. But to get virtual irq you need to first define physical Interrupt ID number in dts.

> FYI, the numbers were reversed between TSEC2 and TSEC1 between version 1.0 of the CPU
> and version 2.0.  Rev A of the RDB has 1.0.  I am going to flip them
> around on a 2.6.28 kernel and see what happens.

Even though you modify dts to reflect the changes (you given below) still I dont think it will work as core will not understand it. As it has to be resolved at silicon level which has been done for version 2.0, but giving a try is better option as it will help to understand the concept. It will be nice to know your progress, thanks.

> Where can I find out more info on the format of the .dts file?

You can find more information regarding format/syntax also you need to check the bindings for every device nodes, if you kernel source then check;

/Documentation/powerpc/booting-without-of.txt
/Documentation/powerpc/dts-bindings/fsl/

Kind Regards,
Vijay Nikam


address@hidden wrote: -----


To: address@hidden
From: Mark Bishop <address@hidden>
Sent by: address@hidden
Date: 11/03/2009 7:06PM
Subject: RE: [Ltib] MPC8313 question - again


I need to modify the .dts file to reflect this:
(from the errata sheet)
0 = TSEC2 ERR
1 = TSEC2 RX
2 = TSEC2 TX
3 = TSEC1 ERR
4 = TSEC1 RX
5 = TSEC1 TX
Software should also be updated to reflect the proper eTSEC interrupt
ID numbers as follows:
32 = TSEC2 TX
33 = TSEC2 RX
34 = TSEC2 ERR
35 = TSEC1 TX
36 = TSEC1 RX
37 = TSEC1 ERR


I think I understand the dts file for the bottom interrupt ID numbers,
but I am not so sure about the top eTEC interrupts.  FYI, the numbers
were reversed between TSEC2 and TSEC1 between version 1.0 of the CPU
and version 2.0.  Rev A of the RDB has 1.0.  I am going to flip them
around on a 2.6.28 kernel and see what happens.

Where can I find out more info on the format of the .dts file?



Quoting Stuart Hughes <address@hidden>:

> Hi Vijay,
>
> It is possible to take a Freescale ISO images and graft the platform
> specific parts, but this means copying not only config/platform/_target_
> but probably also some kernel/u-boot spec files and some content in the
> pkgs directory (if not on the GPP).  The positive side of doing this is
> that the Savannah CVS LTIB gets updated more often than ISOs in general
> and so will track updates.  The down side is that it's a manual process,
> the download is slow and you still only end up with kernels etc from
> whatever time the BSP ISO was released.
>
> IMHO it would be better to try to persuade Freescale to release out
> these platforms to Savannah at the same time as they put the ISOs up on
> their website or shortly after.  I would be more than willing to do the
> merge.
>
> Regards, Stuart
>
> On Wed, 2009-03-11 at 11:27 +0530, address@hidden wrote:
>> Yes it is an hardware issue, but this has been resolved in the REV.B
>> board. Perhaps you can get this information in Rev.A Errata sheet.
>>
>> I also have an mpc8313 Rev A board and was trying to port latest BSP
>> available from freescale but was not successful and the lastest BSP is
>> written for Rev.B board. And lot of silicon bugs has been resolved.
>>
>> The lastest BSP can be downloaded from www.freescale.com/powerbsp and
>> later you can add it in LTIB if you want. I dont know if Stuart will
>> agree with this ? ? ?
>>
>> I think using Rev.B based board will be much better option as lot of
>> silicon bugs has been resolved according freescale to support team. As
>> it could happen that fixing it hardware would cause some other issue,
>> perhaps. Yes I beileve it could be a painful job but ...
>>
>> Kind Regards,
>> Vijay Nikam
>>
>> address@hidden wrote:
>> -----
>>
>>
>> To: address@hidden
>> From: Mark Bishop <address@hidden>
>> Sent by: address@hidden
>> Date: 11/03/2009 2:42AM
>> Subject: RE: [Ltib] MPC8313 question - again
>>
>>
>> I agree with that - if it is a hardware issue.
>>
>> I've already got another ticket with Freescale, I'll see where I get
>> with this.
>>
>> What really sucks is that I bought several of these boards and
>> distributed to  software teams all over the world.  Replacing all of
>> them is going to Really Suck(tm)  </rant>
>>
>>
>> Quoting Tom Moulton <address@hidden>:
>>
>> > If I remember correctly the SPI issue is not software, not booting
>> Freescale
>> > won't help.
>> >
>> > I think GPIO 30 (or is it 31) is the SPI Select line and that was
>> wired
>> > wrong.
>> >
>> > You MAY be able to do a hardware hack to get it working on a Rev A
>> board, I
>> > am not 100% sure.
>> >
>> > tom
>> >
>> > -----Original Message-----
>> > From: address@hidden
>> > [mailto:address@hidden] On Behalf Of
>> Mark Bishop
>> > Sent: Tuesday, March 10, 2009 4:49 PM
>> > To: address@hidden
>> > Subject: [Ltib] MPC8313 question - again
>> >
>> > I realize that this mailing list isn't a Freescale support forum,
>> and
>> > I will take my issues I have with them to there 'Support Channel'.
>> > However, I do have a few questions that hopefully you do want to
>> answer.
>> >
>> > I've got a Rev A board and the two most recent RDBs cause all kinds
>> of
>> > issues.  The only one I can get to work is from 2007 (2.6.20).  All
>> I
>> > want is SPI enabled for this friggin board.  The 2007 RDB from
>> > Freescale doesn't have working SPI.
>> >
>> > I really just want to give Freescale the boot, so I downloaded the
>> > most recent ltib from bitshrine and I see that it isn't one of the
>> > selectable platforms on the first screen.  So, here is my question:
>> Is
>> > there some files from CVS that I can download to make it avail or do
>> I
>> > just resign myself to trying to get actual support from Freescale?
>> >
>> >
>> > _______________________________________________
>> > LTIB home page: http://bitshrine.org
>> >
>> > Ltib mailing list
>> > address@hidden
>> > http://lists.nongnu.org/mailman/listinfo/ltib
>> >
>> >
>> >
>> >
>> >
>>
>>
>>
>> _______________________________________________
>> LTIB home page: http://bitshrine.org
>>
>> Ltib mailing list
>> address@hidden
>> http://lists.nongnu.org/mailman/listinfo/ltib
>> Email Disclaimer:
>> ---------------------------
>>
>> This e-mail and any files transmitted with it are for the sole use of
>> the
>> intended recipient(s) and may contain confidential and privileged
>> information. Computer viruses can be transmitted via email.The
>> recipient should check this email and any attachments for the presence
>> of viruses.
>> The company accepts no liability for any damage caused by any virus
>> transmitted by this email.
>>
>> _______________________________________________
>> LTIB home page: http://bitshrine.org
>>
>> Ltib mailing list
>> address@hidden
>> http://lists.nongnu.org/mailman/listinfo/ltib
>
>
>



_______________________________________________
LTIB home page: http://bitshrine.org

Ltib mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/ltib
Email Disclaimer:
---------------------------

This e-mail and any files transmitted with it are for the sole use of the
intended recipient(s) and may contain confidential and privileged information. Computer viruses can be transmitted via email.The recipient should check this email and any attachments for the presence of viruses.
The company accepts no liability for any damage caused by any virus transmitted by this email.