On Tue, Sep 02, 2008 at 06:14:38PM -0600, Gary Thomas wrote:
> David Gibson wrote:
>> On Tue, Sep 02, 2008 at 03:56:30PM -0600, Gary Thomas wrote:
>
>>> What gives? Why is explicit hex sometimes an error and sometimes not?
>>
>> Because we changed the format at one point. Originally (the "dts-
David Gibson wrote:
On Tue, Sep 02, 2008 at 03:56:30PM -0600, Gary Thomas wrote:
What gives? Why is explicit hex sometimes an error and sometimes not?
Because we changed the format at one point. Originally (the "dts-v0"
format) it was implicitly hex everywhere, which turned out to be a
m
On Tue, Sep 02, 2008 at 03:56:30PM -0600, Gary Thomas wrote:
> What gives? Why is explicit hex sometimes an error and sometimes not?
> Is the format of this file documented anywhere (I've not found it)?
If the file has /dts-v1/; at the top, it uses version 1 of the device
tree syntax, which has C
On Tue, Sep 02, 2008 at 03:56:30PM -0600, Gary Thomas wrote:
> Following on with my RTC problem, I cut&pasted this from
> the TQM5200 dts file:
> [EMAIL PROTECTED] {
> #address-cells = <1>;
> #size-cells = <0>;
>
Following on with my RTC problem, I cut&pasted this from
the TQM5200 dts file:
[EMAIL PROTECTED] {
#address-cells = <1>;
#size-cells = <0>;
compatible = "fsl,mpc5200-i2c","fsl-i2c";
reg
On Thu, 27 Mar 2008 10:40:43 +1100
"David Gibson" <[EMAIL PROTECTED]> wrote:
> >>> Note that a stock symbol needs to be written in uppercase; in
> >>> lowercase, it is just a random name that has no collision
> >>> protection.
> >>
> >> Um.. bit too late for that. AFAIK, uppercase has been used
On Wed, Mar 26, 2008 at 04:32:28PM +0100, Segher Boessenkool wrote:
Well.. stock ticker is the new convention. IEEE1275 used IEEE
assigned OUI strings (Organization Unique Identifiers). Often those
are the same as the stock ticker, but not always.
>>>
>>> Erm, an OUI is a 24-bit nu
Well.. stock ticker is the new convention. IEEE1275 used IEEE
assigned OUI strings (Organization Unique Identifiers). Often those
are the same as the stock ticker, but not always.
Erm, an OUI is a 24-bit number. I think you're confusing something
here.
Yes, I think I am. I somehow had the
On Fri, Mar 21, 2008 at 12:35:39PM +0100, Segher Boessenkool wrote:
Convention is to use the stock ticker symbol. If the company is
private and has no stock ticker symbol, then the company name should
be used.
>>>
>>> I didn't know that. ADI it is then.
>>
>> Well.. stock ticker is
Convention is to use the stock ticker symbol. If the company is
private and has no stock ticker symbol, then the company name should
be used.
I didn't know that. ADI it is then.
Well.. stock ticker is the new convention. IEEE1275 used IEEE
assigned OUI strings (Organization Unique Identifier
I wondered about this. Since the AD from Analog Devices is built into
the part number, I didn't know if it was needed. And analog-devices
is
pretty long ;)
But I am willing to put it in if it is necessary.
Convention is to use the stock ticker symbol. If the company is
private and has no
On Fri, Mar 21, 2008 at 01:09:41AM -0400, Sean MacLennan wrote:
> On Thu, 20 Mar 2008 22:34:21 -0600
> "Grant Likely" <[EMAIL PROTECTED]> wrote:
>
> > Convention is to use the stock ticker symbol. If the company is
> > private and has no stock ticker symbol, then the company name should
> > be us
On Thu, 20 Mar 2008 22:34:21 -0600
"Grant Likely" <[EMAIL PROTECTED]> wrote:
> Convention is to use the stock ticker symbol. If the company is
> private and has no stock ticker symbol, then the company name should
> be used.
I didn't know that. ADI it is then.
IIC0: [EMAIL PROTECTED] {
On Thu, Mar 20, 2008 at 10:12 PM, Sean MacLennan
<[EMAIL PROTECTED]> wrote:
> On Thu, 20 Mar 2008 17:26:42 -0500
> "Scott Wood" <[EMAIL PROTECTED]> wrote:
>
> > > ad7414 {
> > > compatible = "ad7414";
> >
> > This should proabably have a manufacturer prefix.
>
> I wondered abo
On Thu, 20 Mar 2008 17:26:42 -0500
"Scott Wood" <[EMAIL PROTECTED]> wrote:
> > ad7414 {
> > compatible = "ad7414";
>
> This should proabably have a manufacturer prefix.
I wondered about this. Since the AD from Analog Devices is built into
the part number, I didn't know if it wa
Sean MacLennan wrote:
Ok, here is what I did
IIC0: [EMAIL PROTECTED] {
compatible = "ibm,iic-440ep", "ibm,iic-440gp", "ibm,iic";
reg = ;
interrupt-parent = <&UIC0>;
interrupts = <2 4>;
index = <0>;
ad7414 {
compatible = "ad7414";
This should p
Ok, here is what I did
IIC0: [EMAIL PROTECTED] {
compatible = "ibm,iic-440ep", "ibm,iic-440gp", "ibm,iic";
reg = ;
interrupt-parent = <&UIC0>;
interrupts = <2 4>;
index = <0>;
ad7414 {
compatible = "ad7414";
int
Sean MacLennan wrote:
The warp has an AD7414 chip hanging off the I2C bus. This chip can
raise an interrupt when it crosses a critical threshold.
This interrupt is tied to IRQ2 from the processor. What is the best
way to describe this interrupt in the DTS?
The warp.dts is available on request,
The warp has an AD7414 chip hanging off the I2C bus. This chip can
raise an interrupt when it crosses a critical threshold.
This interrupt is tied to IRQ2 from the processor.
No it's not. PowerPC has only one interrupt [*]. You probably
mean it is tied to IRQ2 on your "main" interrupt control
The warp has an AD7414 chip hanging off the I2C bus. This chip can
raise an interrupt when it crosses a critical threshold.
This interrupt is tied to IRQ2 from the processor. What is the best
way to describe this interrupt in the DTS?
The warp.dts is available on request, but the one in the for-2
On Tue, Feb 12, 2008 at 12:37:07PM -0500, Nick wrote:
> Hi,
>
> I need some help. I am trying to access timer 7 on the MPC5200B
> processor. I have the DTS file setup like this
Others have addressed the most salient points, but some general
corrections for your device tree..
> [EMAIL
On Feb 12, 2008 11:07 AM, Jarno Manninen <[EMAIL PROTECTED]> wrote:
> On Tuesday 12 February 2008 19:37:07 Nick wrote:
>
> > How do I specify the timer based on the cell-index?
>
> I don't know if that is possible to do in a one call, but maybe using the
> approach from mpc52xx_uart might help?
>
>
On Tuesday 12 February 2008 19:37:07 Nick wrote:
> How do I specify the timer based on the cell-index?
I don't know if that is possible to do in a one call, but maybe using the
approach from mpc52xx_uart might help?
--clip--
for_each_node_by_type(np, "serial") {
if (!of_
On Feb 12, 2008 10:37 AM, Nick <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I need some help. I am trying to access timer 7 on the MPC5200B
> processor. I have the DTS file setup like this
>
> [EMAIL PROTECTED] {// General Purpose Timer
> device_type = "gpt";
> compatibl
Hi,
I need some help. I am trying to access timer 7 on the MPC5200B
processor. I have the DTS file setup like this
[EMAIL PROTECTED] {// General Purpose Timer
device_type = "gpt";
compatible = "fsl,mpc5200b-gpt","fsl,mpc5200-gpt";
cell-index = <7>;
25 matches
Mail list logo
