Sadly, after >20 years
ev to work properly (versions of udev
newer than ~173)
--
----
Gary Thomas | Consulting for the
MLB Associates |Embe
ck
in 1995...) I just sent my last one to the recycler a few months
back :-(
--
----
Gary Thomas | Consulting for the
MLB Associates |Embe
t the Linux kernel source file 'Documentation/gpio.txt'
--
----
Gary Thomas | Consulting for the
MLB Associates |Embedded world
On 2012-04-11 10:57, Joakim Tjernlund wrote:
On 2012-04-11 10:14, Gary Thomas wrote:
n.b. sorry if you receive this twice - ThunderBird seems very crashy lately!
I'm trying to update my MPC8379 board from 3.0 to 3.3. I have
this setup in my device tree:
mdio@24520 {
#address-cell
On 2012-04-11 10:14, Gary Thomas wrote:
n.b. sorry if you receive this twice - ThunderBird seems very crashy lately!
I'm trying to update my MPC8379 board from 3.0 to 3.3. I have
this setup in my device tree:
mdio@24520 {
#address-cells = <1>;
#size-cells = <0>;
compatible =
x8 36 0x8 37 0x8>;
interrupt-parent = <&ipic>;
phy-handle = <&phy1>;
linux,network-index = <1>;
};
On 3.0, this works just fine. When I boot the same setup on 3.3,
I get this error
works just fine. When I boot the same setup on 3.3,
I get this error:
fsl-pq_mdio: probe of ff024520.mdio failed with error -16
Is there something I need to change in my DTS file to make this work?
Something else I might be missing?
Thanks
--
.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
--
----
Gary Thomas | Consulting for the
MLB Associates |Embe
bility for
any damage caused by any virus transmitted by this email.
www.wipro.com
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
--
---
Scott,
Is cpm_console_init() must be initialized to fix this issue?
Also, 2.6.21 is truly ancient. Why not try a more recent kernel,
especially if
you are just getting srarted?
I think this is the time, for me to use latest kernel to work on.
BR Naresh Kamboju
-Original Message-----
From: Gary Thomas
l.
www.wipro.com
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
Please do not print this email unless it is absolutely necessary.
Th
On 02/15/2011 11:18 AM, Anatolij Gustschin wrote:
On Tue, 15 Feb 2011 10:47:17 -0700
Gary Thomas wrote:
I'm trying to get my platform support working in mainline
2.6.37. I have a MPC8379 which is working well in 2.6.32.
When I just move my platform to the new kernel, everything
works e
ds (as
far as this part is concerned). I can see it start up,
claim to power up the internal hub, but I never see the
state change interrupt from the hub.
Are there any known gotchas here? Any ideas?
Thanks
--
----
G
On 01/31/2011 01:12 PM, Gary Thomas wrote:
I'm running 2.6.32 on MPC8379, trying to use the SDHCI interface.
It seems to work, reads are fine, but when I write to the device
(I've tried both eMMC soldered-on and pluggable MMC/SD cards),
I get intermittent failures. Specifically, some b
I haven't yet found a pattern.
Is there anything special about this interface? I notice that
it's not really used by any FSL platforms although the driver
claims support.
Any ideas?
Thanks
--
----
Gary Thomas | Co
On 01/08/2011 06:07 AM, Gary Thomas wrote:
On 01/08/2011 12:33 AM, Benjamin Herrenschmidt wrote:
On Fri, 2011-01-07 at 16:06 -0700, Gary Thomas wrote:
I just tried porting my target (MPC8347) from 2.6.28 (remember
that one?) to 2.6.37. Recently I tried this with 2.6.32 without
a lot of success
On 01/08/2011 12:33 AM, Benjamin Herrenschmidt wrote:
On Fri, 2011-01-07 at 16:06 -0700, Gary Thomas wrote:
I just tried porting my target (MPC8347) from 2.6.28 (remember
that one?) to 2.6.37. Recently I tried this with 2.6.32 without
a lot of success, so I thought I'd try the latest :-)
3 of every longword is 0x00?
* The SATA device driver is failing along similar lines.
Any ideas what I'm doing wrong? or what I can look at?
Thanks
--
Gary Thomas | Consulting for the
MLB Associates |Embe
On 11/23/2010 07:44 AM, Gary Thomas wrote:
On 11/22/2010 01:26 PM, Benjamin Herrenschmidt wrote:
On Mon, 2010-11-22 at 03:01 -0700, Gary Thomas wrote:
I have a bit more information on this. I'm pretty sure that the failures
are only happening in my SCSI (SATA actually) code. My board (8
_
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
--
--------
Gary Thomas | Consulting for t
On 11/22/2010 01:26 PM, Benjamin Herrenschmidt wrote:
On Mon, 2010-11-22 at 03:01 -0700, Gary Thomas wrote:
I have a bit more information on this. I'm pretty sure that the failures
are only happening in my SCSI (SATA actually) code. My board (8347ea) has
a PCI bus with a SIL SATA contr
On 11/21/2010 10:59 AM, Gary Thomas wrote:
On 11/19/2010 02:46 PM, Benjamin Herrenschmidt wrote:
On Fri, 2010-11-19 at 08:42 -0700, Gary Thomas wrote:
In this case, note that PCI device :00:0c.0 is at 0xc000.
This causes problems because it's a truly stupid device that does
not
On 11/19/2010 02:46 PM, Benjamin Herrenschmidt wrote:
On Fri, 2010-11-19 at 08:42 -0700, Gary Thomas wrote:
In this case, note that PCI device :00:0c.0 is at 0xc000.
This causes problems because it's a truly stupid device that does
not work properly at PCI [relative] address 0x000
ck (so as to get my
stupid graphics controller working again)??
Thanks for any ideas
--
--------
Gary Thomas | Consulting for the
MLB Associat
On 10/01/2010 06:15 AM, Benjamin Herrenschmidt wrote:
On Fri, 2010-10-01 at 05:55 -0600, Gary Thomas wrote:
On 10/01/2010 05:30 AM, Josh Boyer wrote:
On Fri, Oct 1, 2010 at 5:02 AM, Kumar Gala wrote:
On Oct 1, 2010, at 2:05 AM, Ian Munsie wrote:
Some PowerPC processors can be run in
say I would be very willing to help anyone run in LE mode, let
alone have it randomly selectable.
Indeed, I thought we had killed that Windows-NT dog ~15 years ago :-)
--
--------
Gary Thomas | Consulting for the
x seems to work,
but Tx is totally dead...
--
----
Gary Thomas | Consulting for the
MLB Associates
re configured or not.
--
----
Gary Thomas | Consulting for the
MLB Associates |Embedded world
___
Linuxppc-dev maili
On 06/24/2010 06:54 AM, Gary Thomas wrote:
I thought I had this working, but it seems to only work for UCC3.
Sadly, I can't get it to work on UCC4/UCC5/UCC8 at all.
Starting with UCC4, I have:
/* ttyQE0 (UCC4) */
serial_qe0: ser...@3200 {
device_type = "serial";
compatible = &
.srx
-rw-rw-r-- 1 gthomas gthomas 105318 2009-09-16 15:59 SWUART_8360rev21.c
-rw-rw-r-- 1 gthomas gthomas 34689 2009-09-16 15:14 SWUART_8360rev21.srx
Any ideas what I'm doing wrong?
Thanks
--
Gar
else is wrong...
BTW, I use RedBoot - being the original author, how could I not?
Thanks for the help
--
----
Gary Thomas | Consulting for the
MLB Associates
y at the CPU.
This is behaving very much like there is no clock to the device.
Is there something special that needs to be done to get the BRGs
to work?
--
--------
Gary Thomas | Consulting for the
MLB Associates
:-(
Any ideas what I might be missing?
--
--------
Gary Thomas | Consulting for the
MLB Associates |Embedded world
___
Linuxppc-dev mailing l
r silicon 2.1.
Also presupposes that you have put the microcode under your rootfs /root
directory.
Thanks, I'll give this a try. When I download the firmware this way,
do I need to follow the directions in
Documentation/powerpc/dts-bindings/fsl/cpm_qe/qe/firmware.t
On 06/22/2010 09:10 AM, Chuck Meade wrote:
On 06/22/2010 10:55 AM, Gary Thomas wrote:
I'm still trying to get UCC UART to work on my MPC8358 with
the 2.6.33.3 kernel.
When I try to send data to the port, there is no output, not
even any interrupts on the device. What I see is that the
hardware. How do I know if my board
has functioning UART hardware?
Note: I have UCC1+UCC2 working great with ethernet.
Thanks for any pointers or ideas
--
Gary
From:
linuxppc-dev-bounces+blakeslees=embeddedplanet@lists.ozlabs.org
[mailto:linuxppc-dev-
bounces+blakeslees=embeddedplanet@lists.ozlabs.org] On Behalf Of
Gary
Thomas
Sent: Monday, June 21, 2010 3:00 PM
To: Linux PPC Development
Subject: UCC interactions
I'm running 2.6.33.3 on MPC835
interrupts = <34>;
interrupt-parent = <&qeic>;
port-number = <0>;
rx-clock-name = "brg1";
tx-clock-name = "brg1";
};
Are there known interactions betw
On 06/17/2010 11:56 AM, Gary Thomas wrote:
I'm working with 2.6.33.3 on a MPC8358. I'm trying to get it
to talk to a Marvell (DSA) switch which uses special drivers
and addressing to act like a PHY. I have this working fine
on some older (2.6.28) systems by using a fixed-link PHY
des
;1 1 1000 0 0>;
Thanks
--
--------
Gary Thomas | Consulting for the
MLB Associates |Embedded world
___
Linuxppc-dev mailing list
Linuxppc-
e code simpler and faster.
I don't know about today, but my recollection is that the only
use of little-endian mode on PowerPC was during the early days
attempt to run Windows-NT.
--
--------
Gary Thomas | Con
uxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
--
Gary Thomas | Consulting for the
MLB Associates |Embedded world
On 04/23/2010 07:24 PM, Wolfram Sang wrote:
Hi Gary,
(adding linux-i2c)
On Fri, Apr 23, 2010 at 09:56:07AM -0600, Gary Thomas wrote:
I'm having trouble with the I2C devices on my 8347 platform.
The problem is that I2C device probe() functions are only called
once, as the I2C bus is
On 04/23/2010 09:56 AM, Gary Thomas wrote:
I'm having trouble with the I2C devices on my 8347 platform.
The problem is that I2C device probe() functions are only called
once, as the I2C bus is being initialized (in this case fsl_i2c_init())
I have 2 devices on this bus, one device gets
derstand/fix this
in 2.6.28 if possible.
Thanks
--
----
Gary Thomas | Consulting for the
MLB Associates
On 02/25/2010 02:24 PM, Scott Wood wrote:
Gary Thomas wrote:
On 02/25/2010 02:03 PM, Scott Wood wrote:
Gary, can you check that the MMIO addresses are going to the PCI bus as-is, and
aren't being translated down to zero? I.e. POTARn should equal POBARn, and
likewise in the device
tree&
On 02/25/2010 02:03 PM, Scott Wood wrote:
Benjamin Herrenschmidt wrote:
On Thu, 2010-02-25 at 07:25 -0700, Gary Thomas wrote:
I may have been too hasty pronouncing this fixed. Indeed, the
SATA interface now works, but my video card (Fujitsu Coral-P)
does not work when it's mapped at the b
On 02/24/2010 04:08 PM, Gary Thomas wrote:
On 02/24/2010 03:25 PM, Kumar Gala wrote:
On Feb 24, 2010, at 4:14 PM, Gary Thomas wrote:
On 02/24/2010 01:51 PM, Anton Vorontsov wrote:
On Wed, Feb 24, 2010 at 02:26:20PM -0600, Scott Wood wrote:
Gary Thomas wrote:
Yes, I'm using the exact
On 02/24/2010 03:25 PM, Kumar Gala wrote:
On Feb 24, 2010, at 4:14 PM, Gary Thomas wrote:
On 02/24/2010 01:51 PM, Anton Vorontsov wrote:
On Wed, Feb 24, 2010 at 02:26:20PM -0600, Scott Wood wrote:
Gary Thomas wrote:
Yes, I'm using the exact same kernel with these two different PCI
s
On 02/24/2010 01:51 PM, Anton Vorontsov wrote:
On Wed, Feb 24, 2010 at 02:26:20PM -0600, Scott Wood wrote:
Gary Thomas wrote:
Yes, I'm using the exact same kernel with these two different PCI
setups (done by the boot loader).
Restricting the memory via mem=128M has no effect - the PCI l
On 02/24/2010 12:31 PM, Scott Wood wrote:
Gary Thomas wrote:
On 02/24/2010 11:48 AM, Scott Wood wrote:
Gary Thomas wrote:
Does anyone have experience setting up the PCI controller on
the MPC8349? I have it running fine when my system has 128MB
or less of main memory, but when I have 256MB or
On 02/24/2010 11:48 AM, Scott Wood wrote:
Gary Thomas wrote:
Does anyone have experience setting up the PCI controller on
the MPC8349? I have it running fine when my system has 128MB
or less of main memory, but when I have 256MB or more, it all
falls apart :-(
Any indication of the pertinent
--
Gary Thomas | Consulting for the
MLB Associates |Embedded world
___
Linuxppc-dev mailing list
Linuxppc-dev
On 01/28/2010 05:17 AM, Gary Thomas wrote:
On 01/27/2010 05:05 PM, Gary Thomas wrote:
On 01/27/2010 01:20 PM, Gary Thomas wrote:
I have two nearly identical boards, with very different behavior.
Older 8347 (PVR: 0x80830011)
New 8347 (PVR: 0x80830031)
I lied (more precisely I was lied to and
On 01/27/2010 05:05 PM, Gary Thomas wrote:
On 01/27/2010 01:20 PM, Gary Thomas wrote:
I have two nearly identical boards, with very different behavior.
Older 8347 (PVR: 0x80830011)
New 8347 (PVR: 0x80830031)
I lied (more precisely I was lied to and I passed it on - I've never
seen
On 01/27/2010 01:20 PM, Gary Thomas wrote:
I have two nearly identical boards, with very different behavior.
Older 8347 (PVR: 0x80830011)
New 8347 (PVR: 0x80830031)
I lied (more precisely I was lied to and I passed it on - I've never
seen these boards in person, just worked on them
ow that's a long time ago, but MACHINE CHECK??
(*) To get this platform to run 2.6.20, I had to patch the CPU tables
to recognize it as 8347 (kernels of that vintage relied on the SVR to
make choices, not PVR)
--
--------
Gary Thomas
printk("Cannot set affinity for irq %i\n", irq);
>>> + else if (irq_desc[irq].action)
>>> + printk_once("Cannot set affinity for irq %i\n", irq);
>> Maybe we should add a loglevel to this printk (and the other one in fix_irqs)
>> w
ined, you can't have
CONFIG_BLK_DEV_RAM_COUNT
or CONFIG_BLK_DEV_RAM_SIZE. Use 'menuconfig' to help straighten this out.
> Meanwhile a side question - why does BLK_DEV_RAM_COUNT default to 16?
This is just the number of unique RAM disk devices supported.
--
---
17?
> <6>R??C: Registered udp transport module.?
> <6>RPC: Registered tcp transport module.?
> <3??Root-NFS: No NFS server available' giving up.?
> <3>VFS: Unable to mount root fs v??a NFS' trying floppy.?
> <4>VFS: Cannot open
Albrecht Dreà wrote:
> Am 20.05.09 16:23 schrieb(en) Gary Thomas:
>> > In Linux, when I write the file to /dev/mtdx, the last dword of each
>> block is broken, e.g. when running "dd if=pattern of=/dev/mtd5 bs=512"
>> the dword's at offset 0x1fc, 0x3fc, ... a
I guessed I missed something in the LPB
> setup...
Check your cache setup - the BDI is most certainly not accessing
this via the Data cache whereas Linux probably will be.
--
Gary Thomas | Consulting for the
MLB
latform driver.
>
So somehow, I need to create a platform driver, possibly inside an
of_wrapper, which
eventually instantiates an I2C device on a particular bus, with my
specific platform
data.
Sorry, but I'm lost here. How do I untangle this maze of twisty little
passages?
--
river.
Pretty much as I expected.
Are there examples of how to do this? In particular how to
correlate a GPIO (with interrupt) to another (I2C) device?
--
--------
Gary Thomas | Consulting f
Jon Smirl wrote:
> On Fri, May 1, 2009 at 10:39 AM, Jon Smirl wrote:
>> On Fri, May 1, 2009 at 9:04 AM, Gary Thomas wrote:
>>> I'd like to use an existing I2C driver (a touchscreen device)
>>> with my 834x based platform. How do I arrange to provi
I'd like to use an existing I2C driver (a touchscreen device)
with my 834x based platform. How do I arrange to provide
platform data (i2c_client->dev.platform_data) from my OF world?
--
----
Gary Thomas | Consul
Kumar Gala wrote:
>
> On Apr 23, 2009, at 9:24 AM, Gary Thomas wrote:
>
>> I have found the culprit - in arch/powerpc/kernel/pci_32.c
>>
>> static void
>> fixup_hide_host_resource_fsl(struct pci_dev *dev)
>> {
>> int i, class = d
Kumar Gala wrote:
>
> On Apr 21, 2009, at 6:45 PM, Gary Thomas wrote:
>
>> Kumar Gala wrote:
>>>
>>> On Apr 21, 2009, at 6:00 PM, Gary Thomas wrote:
>>>
>>>>
>>>> I found the difference - in 2.6.28 the inbound/outbound win
Kumar Gala wrote:
>
> On Apr 21, 2009, at 6:00 PM, Gary Thomas wrote:
>
>>
>> I found the difference - in 2.6.28 the inbound/outbound windows
>> don't seem to be set up at all. In 2.6.26, the function 'fsl_add_bridge'
>> was common among ar
e this is the problem.
> Also, what's your .dts look like for the PCI node.
For the record:
bus-range = <0 0>;
ranges = <0x0200 0x0 0xC000 0xC000 0x0 0x1000
0x0100 0x0 0x 0xB800 0x0 0x0010>;
--
Gary Thomas wrote:
> Kumar Gala wrote:
>> On Apr 21, 2009, at 3:30 PM, Gary Thomas wrote:
>>
>>> The [two] big differences I see are that the video card (00:0d.0)
>>> is being assigned 0xC000, which lspci marks as "virtual".
>>> I think I&
Kumar Gala wrote:
>
> On Apr 21, 2009, at 3:30 PM, Gary Thomas wrote:
>
>> The [two] big differences I see are that the video card (00:0d.0)
>> is being assigned 0xC000, which lspci marks as "virtual".
>> I think I've had trouble in the past with mem
Gary Thomas wrote:
> Gary Thomas wrote:
>> I had a stable port of 2.6.26 for my 834x hardware, with a
>> frame buffer on a PCI device. After I upgraded to 2.6.28,
>> this isn't working any more. The frame buffer code is happily
>> writing to a mapped [memory] sp
Gary Thomas wrote:
> I had a stable port of 2.6.26 for my 834x hardware, with a
> frame buffer on a PCI device. After I upgraded to 2.6.28,
> this isn't working any more. The frame buffer code is happily
> writing to a mapped [memory] space on the PCI card, but nothing
> is
ks for any ideas
--
----
Gary Thomas | Consulting for the
MLB Associates |Embedded world
___
Linuxppc-d
ged, 6 insertions(+), 8 deletions(-)
>
> this looks fine, but why don't we go ahead and rename things as well?
> SPI_MPC83xx -> SPI_MPC8xxx, spi_mpc83xx.c -> spi_mpc8xxx.c
mpc8xxx implies mpc82xx (e.g. mpc8272) which is not the same controller
as on the mpc83xx
--
--
ng the latter fixed my problem.
>
> Thanks for the help, and sorry for the noise.
>
Can you share what you had and what you changed it to? I'm
running on very similar systems and may face this exact problem
soon.
Thanks
--
----
Matthew L. Creech wrote:
> On Tue, Mar 31, 2009 at 4:45 PM, Gary Thomas wrote:
>> What does your command line (boot args) when it fails? It should
>> probably have something like "console=ttyS0,115200" in it.
>>
>
> Yes, that's what I'm using
ke this?
What does your command line (boot args) when it fails? It should
probably have something like "console=ttyS0,115200" in it.
--
Gary Thomas | Consulting for the
MLB Associates |Embe
ely wrote:
>> On Thu, Mar 19, 2009 at 5:59 PM, David H. Lynch Jr. wrote:
>>
>>>Does anyone have experience sugestions for building ppc/linux apps
>>> or even ppc kernels under windows.
>>>
>> I hear rumors that there is a Windows v
river (SPI on MPC5200) supposed to work?
If so, what am I missing to get it set up?
If not, what needs to be done to get it there?
Thanks
--
Gary Thomas
Grant Likely wrote:
> On Sat, Feb 28, 2009 at 12:18 PM, Gary Thomas wrote:
>> Grant Likely wrote:
>>>> How do I find the platform_device which was created when this
>>>> particular of_device was instantiated? I made sure that this code
>>>> is
Grant Likely wrote:
> On Sat, Feb 28, 2009 at 11:21 AM, Gary Thomas wrote:
>> Grant Likely wrote:
>>> Once you have a handle to the node, you can iterate through the
>>> of_platform bus devices and look for a node which has a matching node
>>> pointer store
Grant Likely wrote:
> On Sat, Feb 28, 2009 at 10:46 AM, Gary Thomas wrote:
>> Still looking for some help... I need to be able to locate
>> the kernel platform_device which corresponds to an instance
>> from my OF tree. Basically, I have a [somewhat] unrelated
>>
on't seem to be able
to get out of the OF tree and into the actual platform
device tree to find the appropriate instance.
Any pointers?
Thanks
--
Gary
compatible = "gianfar";
reg = <0x25000 0x1000>;
local-mac-address = [ 00 08 e5 11 32 34 ];
interrupts = <35 0x8 36 0x8 37 0x8>;
interrupt-parent = <&ipic>;
Gary Thomas wrote:
> I have two [internal] boards with MPC8347. Both have a PCI
> bus, slightly different set of "wired" peripherals.
>
> On one board, the PCI seems to be working fine. I can talk
> to all of my wired devices, plus one in a plugin slot. The
> [PCI
]0x1001 / probed size 0x / CPU addr 0xb8001000
BAR[1]0x1009 / probed size 0x / CPU addr 0xb8001008
BAR[2]0x1011 / probed size 0x / CPU addr 0xb8001010
BAR[3]0x1019 / probed size 0x0000 / CPU addr 0xb8001018
BAR[4]0x1021
fork+0x4/0xcc
>
> (There are 65 call trace lines)
>
> After that the system continued.
It looks like the stack trace code got stuck in a loop (the last
53 entries are identical) - increasi
that of_irq_map_one() can fail for a myriad of reasons - all quiet
(without debugging on). This function simply masks those into "sorry..."
After a lot of looking I found this in mt DTS:
[EMAIL PROTECTED] {
compatible = "am,can&q
Benjamin Herrenschmidt wrote:
> On Thu, 2008-12-04 at 06:51 -0700, Gary Thomas wrote:
>> I have a MPC5200 based board which has an FPGA for external
>> I/O, etc. This FPGA also funnels interrupts from the various
>> external devices through to the CPU.
>>
>> I&#x
disable port 2 (err = -19)
> hub 1-0:1.0: cannot disable port 2 (err = -19)
> hub 1-0:1.0: state 0 ports 2 chg evt 0004
>
> Please mail me any idea...
Update to the latest kernel (2.6.27+) - there has been lots
of work on the MPC5200 in the past three years (that's how
old 2.6.21 i
arguments about not using "device_type"
and this will be resolved. At the moment, I'm basing my
code on a slightly older kernel codebase (2.6.26), so those
entries remain.
--
---
d one which is SocketCAN compatible).
I don't see such a driver for the MSCAN (the hardware on the MPC5200) in
the stock 2.6.27 tree.
--
----
Gary Thomas | Consulting for the
MLB Ass
ial speed-bumps.
--
--------
Gary Thomas | Consulting for the
MLB Associates |Embedded world
___
Linuxppc-dev mailin
the MPC5200 PCI code (where I'd expect
to find some of these answers) without much elucidation.
Forgive such _newbie_ questions, but I'm just a happy arch/ppc
user trying to catch up to an arch/powerpc world :-)
Tha
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 o
This yielded a syntax error when merged with my platform dts.
When I changed the 'reg=<0x68>' to 'reg=<68>', the syntax error
went away & it worked perfectly.
What gives? Why is explicit hex sometimes an error and sometimes not?
Is the format of this fi
Scott Wood wrote:
On Tue, Sep 02, 2008 at 03:28:19PM -0600, Gary Thomas wrote:
I'm working with a couple FreeScale platforms and having
trouble getting the RTC which is connected via I2C to work.
I had this working fine in the old arch/ppc tree, but it's
failing in the arch/pow
1 - 100 of 102 matches
Mail list logo
