Hi John, Steve and others,
in generic platform will be generic DTS which I sent in first versions.
This DTS will be for simple platform. There is not copyright.
FDT generator add copyright notice on the top of file. I added it when I start
to program this BSP. Xilinx only add their copyright
Modern versions of u-boot create a chosen node automatically. So if
we set the chosen node in the dts file, there will be 2 chosen nodes
passed in to the kernel, and the kernel command line will be taken from
the wrong node. So, remove the extra chosen node from the dts file.
Signed-off-by:
Hi Segher,
you find bug because there is microblaze asm code in generic folder.
Big thanks. I'll fix it and I'll look at parameters too.
Michal
+static inline unsigned int
+csum_tcpudp_nofold(unsigned long saddr, unsigned long daddr, unsigned
short len,
+ unsigned short
Hi Steve, John a others,
In my opionion, we should only include dts files for reference designs, and it
must be documented how to get the design that the dts corresponds to.
MD5 hashing might be one way to prevent people from getting the dts file wrong,
however without some way of checking it
Eric B Munson writes:
--- a/include/asm-powerpc/elf.h
+++ b/include/asm-powerpc/elf.h
@@ -257,7 +257,8 @@ do {
\
else\
clear_thread_flag(TIF_ABI_PENDING);
Hi all,
I am working on a PPC Motorola card, which runs Linux 2.4.22. The
card has 2 GB onboard memory. But with use 1456 MB of the available
memory. To increase the memory capacity i need to increase the used
memory at least 64 MB. With CONFIG_HIGHMEM option all of the 2 GB memory
Kumar Gala wrote:
On Jun 26, 2008, at 9:13 AM, Wolfgang Grandegger wrote:
Kumar Gala wrote:
On Jun 26, 2008, at 8:15 AM, Wolfgang Grandegger wrote:
It adds the missing RTC node to tqm8548.dts and enables support for
I2C, DS1307 and LM75 in the default configuration.
Signed-off-by: Wolfgang
Added a new driver for Xilinx XPS PS2 IP. This driver is
a flat driver to better match the Linux driver pattern.
Signed-off-by: Sadanand [EMAIL PROTECTED]
Signed-off-by: John Linn [EMAIL PROTECTED]
---
drivers/input/serio/Kconfig |5 +
drivers/input/serio/Makefile |1 +
On Mon, Jun 23, 2008 at 08:48:28PM +0300, Adrian Bunk wrote:
This patch makes asm/elf.h export less non-userspace stuff to userspace.
I don't think this header should be exported at all. There's a
userspace elf.h that should be used instead.
___
I still have bad dreams about the of_serial patch I did as a newbie
related to reg_shift and reg_offset ;)
I'm still a newbie, but we'll do whatever needs to be done.
Any thoughts from Josh?
-- John
-Original Message-
From: Stephen Neuendorffer
Sent: Sunday, June 29, 2008 9:42 PM
To:
John == John Linn [EMAIL PROTECTED] writes:
Added a new driver for Xilinx XPS PS2 IP. This driver is
a flat driver to better match the Linux driver pattern.
This should probably go to the linux-input@ list as well.
Signed-off-by: Sadanand [EMAIL PROTECTED]
Signed-off-by: John Linn
Scott,
actually I'm having trouble with my PCI interrupts.
We are running 2.6.26-rc6 on a MPC8343 based board.
There are two external PCI devices connected (FPGA + miniPCI socket).
The FPGA is working fine and uses IRQ0 for its PCI_INTA line.
As soon there's a miniPCI module present and the
On Mon, Jun 30, 2008 at 02:15:25PM +1000, David Gibson wrote:
On Fri, Jun 27, 2008 at 04:10:17PM -0500, Kumar Gala wrote:
Added DMA nodes for the elo/elo-plus DMA engines.
Renamed the interrupt controller alias in mpc832x_rdb.dts to ipic so that
its the same as all the other boards.
On Jun 30, 2008, at 10:35 AM, Scott Wood wrote:
On Mon, Jun 30, 2008 at 02:15:25PM +1000, David Gibson wrote:
On Fri, Jun 27, 2008 at 04:10:17PM -0500, Kumar Gala wrote:
Added DMA nodes for the elo/elo-plus DMA engines.
Renamed the interrupt controller alias in mpc832x_rdb.dts to ipic
so
Added a new driver for Xilinx XPS PS2 IP. This driver is
a flat driver to better match the Linux driver pattern.
Signed-off-by: Sadanand [EMAIL PROTECTED]
Signed-off-by: John Linn [EMAIL PROTECTED]
---
V2
Changes from v1:
Ran the scripts/checkpatch.pl on the patch as I should have done
before
Hi,
Against which kernel is this patch against ?
Regards,
Daniel.
Tim Yamin wrote:
Changes from previous version:
- Add FIFO status error checking code before a DMA transaction starts
and after it is completed.
- Fix an incorrect check in the previous patch causing spurious dma
On Fri, 27 Jun 2008 22:29:59 -0700
Grant Likely [EMAIL PROTECTED] wrote:
On Fri, Jun 27, 2008 at 9:52 AM, Kim Phillips
[EMAIL PROTECTED] wrote:
delete obsolete device-type property, delete model property
(use compatible property instead), prepend fsl, to Freescale
specific properties. Add
On Mon, 30 Jun 2008, Paul Mackerras wrote:
Eric B Munson writes:
--- a/include/asm-powerpc/elf.h
+++ b/include/asm-powerpc/elf.h
@@ -257,7 +257,8 @@ do {
\
else\
On Sun, 29 Jun 2008 01:37:12 +0200
Segher Boessenkool [EMAIL PROTECTED] wrote:
I'm really don't like fsl,sec1.0 or any of the variants as a
compatible property either because it can easily be abused (it's not
anchored to a specific physical part so the meaning can shift over
time); but
Currently when a 32 bit process is exec'd on a powerpc 64 bit host the value
in the top three bytes of the personality is clobbered. This patch adds a
check in the SET_PERSONALITY macro that will carry all the values in the top
three bytes across the exec.
These three bytes currently carry flags
On Mon, Jun 30, 2008 at 03:03:29PM +1000, Paul Mackerras wrote:
Grant Likely writes:
+simpleboot-*)
+platformo=$object/simpleboot.o
+binary=y
+;;
esac
Evidently your patch does more than just Add documentation...
Ugh.
While writing the documentation, I noticed that
Modern versions of u-boot create a chosen node automatically. So if
we set the chosen node in the dts file, there will be 2 chosen nodes
passed in to the kernel,
That's a bug in uboot, then: when it creates a property, it should
delete an already existing property with the same name in that
you find bug because there is microblaze asm code in generic folder.
No, I found it because I was reading the code, I didn't even notice
this was in asm-generic :-)
Big thanks. I'll fix it and I'll look at parameters too.
Thanks.
Segher
___
Stephen Neuendorffer wrote:
Grant Likely wrote:
I think the easiest solution is to change the Kconfig so that
PPC_UDBG_16550 is only selected based on !XILINX_VIRTEX. I've done this
in my tree, but I've been swamped with other things at the moment, so I
haven't verified it.
This
interrupt-map = 0x5800 0 0 1 ipic 0x30 0x8 - FPGA @ IRQ0
0x6000 0 0 1 ipic 0x11 0x8 - miniPCI INTA @
IRQ1
0x6000 0 0 2 ipic 0x11 0x8;- miniPCI INTB @
IRQ1
Is it legal to use a single irq pin twice ?
The device tree simply describes the
Ah.. good idea... hadn't thought of that, I guess.
John Linn: I have no time to look at this. Can you see if such a fix
fixes the problem?
Steve
-Original Message-
From: Grant Likely [mailto:[EMAIL PROTECTED] On Behalf Of Grant
Likely
Sent: Monday, June 30, 2008 9:34 AM
To:
I'll give it a try, sounds easy.
-- John
-Original Message-
From: Stephen Neuendorffer
Sent: Monday, June 30, 2008 10:49 AM
To: [EMAIL PROTECTED]; John Linn
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
linuxppc-dev@ozlabs.org; git
Subject: RE: [PATCH] [POWERPC] Xilinx: add compatibility
Also, these made-up names make you do more work: you'll need to
who said they were made up?
I did. These names do not refer to some physical part you can buy.
write up a binding for them, explaining exactly what a 1.0 device
etc. is (or at least point to documentation for it). If you use
Segher,
actually I'm the hardware designer ... :-) having trouble with
software.
The outputs are open-drain and can be connected (wired-or) together.
Otherwise shared irq wouldn't be possible that easy.
cheers,
André
Segher Boessenkool wrote:
interrupt-map = 0x5800 0 0 1 ipic 0x30
On Mon, Jun 30, 2008 at 07:24:48AM -0700, John Linn wrote:
Added a new driver for Xilinx XPS PS2 IP. This driver is
a flat driver to better match the Linux driver pattern.
Signed-off-by: Sadanand [EMAIL PROTECTED]
Signed-off-by: John Linn [EMAIL PROTECTED]
I don't know much about the serio
Grant Likely wrote:
From: Grant Likely [EMAIL PROTECTED]
There have been many questions on and off the mailing list about how
exactly the bootwrapper is used for embedded targets. Add some
documentation and help text to try and clarify the system.
Signed-off-by: Grant Likely [EMAIL
John == John Linn [EMAIL PROTECTED] writes:
John Added a new driver for Xilinx XPS PS2 IP. This driver is
John a flat driver to better match the Linux driver pattern.
John Signed-off-by: Sadanand [EMAIL PROTECTED]
John Signed-off-by: John Linn [EMAIL PROTECTED]
John ---
John V2
John
Ahh... sorry about that Peter, didn't ignore your comments on purpose.
Just got on a tangent about sending it to the other mailing list and
forgot to look on down.
I'll review them.
-- John
-Original Message-
From: Peter Korsgaard [mailto:[EMAIL PROTECTED] On Behalf Of Peter
Korsgaard
Hi Grant, John,
On Mon, Jun 30, 2008 at 11:16:28AM -0600, Grant Likely wrote:
On Mon, Jun 30, 2008 at 07:24:48AM -0700, John Linn wrote:
+config SERIO_XILINX_XPS_PS2
+ tristate Xilinx XPS PS/2 Controller Support
+ help
+ This driver supports XPS PS/2 IP from Xilinx EDK.
+
On Mon, 30 Jun 2008 18:55:34 +0200
Segher Boessenkool [EMAIL PROTECTED] wrote:
Also, these made-up names make you do more work: you'll need to
who said they were made up?
I did. These names do not refer to some physical part you can buy.
right, they refer to devices in multiple
On Mon, Jun 30, 2008 at 08:38:21AM -0700, John Linn wrote:
+ spin_lock_init(drvdata-lock);
+ dev_set_drvdata(dev, (void *)drvdata);
No need to cast to void *.
+
+ if (!regs_res || !irq_res) {
+ dev_err(dev, IO resource(s) not found\n);
+ retval =
On Mon, Jun 30, 2008 at 07:45:06PM +0200, Anatolij Gustschin wrote:
Grant Likely wrote:
From: Grant Likely [EMAIL PROTECTED]
There have been many questions on and off the mailing list about how
exactly the bootwrapper is used for embedded targets. Add some
documentation and help text
Hi Stephen,
next-20080630 kernel build fails on powerpc, with randconfig
CC arch/powerpc/mm/mem.o
arch/powerpc/mm/mem.c: In function ‘arch_add_memory’:
arch/powerpc/mm/mem.c:130: error: implicit declaration of function
‘create_section_mapping’
make[1]: *** [arch/powerpc/mm/mem.o] Error 1
Convert i2c-mpc to an of_platform driver. Utilize the code in drivers/of-i2c.c
to make i2c modules dynamically loadable by the device tree.
Signed-off-by: Jon Smirl [EMAIL PROTECTED]
---
arch/powerpc/sysdev/fsl_soc.c | 122 -
Add the of_find_i2c_device_by_node function. This allows you to follow a
reference in the device to an i2c device node and then locate the linux device
instantiated by the device tree. Example use, an i2s codec controlled by i2c.
---
drivers/i2c/i2c-core.c |2 +-
drivers/of/of_i2c.c|
On Mon, Jun 30, 2008 at 02:10:23PM -0400, Dmitry Torokhov wrote:
Hi Grant, John,
On Mon, Jun 30, 2008 at 11:16:28AM -0600, Grant Likely wrote:
On Mon, Jun 30, 2008 at 07:24:48AM -0700, John Linn wrote:
snip
+/*
+ * sxps2_write() sends a byte out through the PS/2 interface.
+ *
+
On Mon, Jun 30, 2008 at 02:34:13PM -0400, Jon Smirl wrote:
+ result = request_irq(i2c-irq, mpc_i2c_isr,
+ IRQF_SHARED, i2c-mpc,
i2c);
That's a rather excessive indentation of the continuation line -- it
looks like it was aligned
André Schwarz wrote:
There are two external PCI devices connected (FPGA + miniPCI socket).
The FPGA is working fine and uses IRQ0 for its PCI_INTA line.
As soon there's a miniPCI module present and the driver loaded (actually
an ath5k WiFi module) the system complains after a while :
irq 48:
Hi guys,
Did anyone have a chance to go over this patch? Looking forward to
receive feedbacks on it.
Thanks!
Regards,
Luis
On Fri, 2008-06-20 at 17:14 -0300, Luis Machado wrote:
On Thu, 2008-05-22 at 13:51 +1000, Paul Mackerras wrote:
Luis Machado writes:
This is a patch that has been
Thanks Peter, those make sense. We'll incorporate those comments.
-Original Message-
From: Peter Korsgaard [mailto:[EMAIL PROTECTED] On Behalf Of Peter
Korsgaard
Sent: Monday, June 30, 2008 8:45 AM
To: John Linn
Cc: linuxppc-dev@ozlabs.org; Sadanand Mutyala
Subject: Re: [PATCH] powerpc:
Kumar Gala wrote:
I believe this comes into play when we have more than one DMA controller
and sometimes there are special uses like on 8610.
Maybe, though I'd just use a phandle to express that (unless you need to
program the number that you're using, rather than just use a specific one).
Thanks Grant. Sounds like there's a few things that not everyone does
the same based on comments from others.
In general, all pretty easy changes that in general make sense.
Thanks,
John
On Mon, Jun 30, 2008 at 07:24:48AM -0700, John Linn wrote:
Added a new driver for Xilinx XPS PS2 IP. This
Kumar, could you apply these patches for 2.6.27?
http://patchwork.ozlabs.org/linuxppc/patch?id=18584
http://patchwork.ozlabs.org/linuxppc/patch?id=18587
-Scott
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
On Tue, 24 Jun 2008 11:44:13 -0500
Timur Tabi [EMAIL PROTECTED] wrote:
Update the Freescale DIU driver to use page_alloc_exact() to allocate a
DMA buffer. This also eliminates the rheap-based memory allocator. We
can do this now because commit 6ccf61f9 allows us to allocate 8MB physically-
What's the cell-index in these nodes used to index? Given the
confusion there's been about the proper use of this property, a
comment indicating which shared registers this is used to index is
probably a good idea.
There's supposed to be a cell-index in the *channels* to index into
the
shared
Also, these made-up names make you do more work: you'll need to
who said they were made up?
I did. These names do not refer to some physical part you can buy.
right, they refer to devices in multiple physical parts you can buy.
Part-you-can-buy documentation clearly indicates the SEC
Thanks Dmitry, see my comments inline.
-- John
On Mon, Jun 30, 2008 at 08:38:21AM -0700, John Linn wrote:
+spin_lock_init(drvdata-lock);
+dev_set_drvdata(dev, (void *)drvdata);
No need to cast to void *.
OK.
+
+if (!regs_res || !irq_res) {
+dev_err(dev, IO
Paul Mackerras wrote:
Robert Jennings writes:
From: Brian King [EMAIL PROTECTED]
The Cooperative Memory Overcommit (CMO) on System p does not currently
support native PCI devices or eBus devices when enabled.
Then why would we get any native PCI or eBus devices in the device
tree?
We
On Mon, 30 Jun 2008 23:19:05 +0200
Segher Boessenkool [EMAIL PROTECTED] wrote:
Also, these made-up names make you do more work: you'll need to
who said they were made up?
I did. These names do not refer to some physical part you can buy.
right, they refer to devices in multiple
On Mon, Jun 30, 2008 at 02:00:12PM -0600, John Linn wrote:
Since xps2_recv() and xps2_send() are used by the sxps2_* routines and
by the irq handler, they should be moved to about them in this file.
OK, keeping them close makes maintenance easier I guess.
Oops, there is a typo in my
Add the of_find_i2c_device_by_node function. This allows you to follow a
reference in the device to an i2c device node and then locate the linux device
instantiated by the device tree. Example use, an i2s codec controlled by i2c.
---
drivers/i2c/i2c-core.c |2 +-
drivers/of/of_i2c.c|
Convert i2c-mpc to an of_platform driver. Utilize the code in drivers/of-i2c.c
to make i2c modules dynamically loadable by the device tree.
Signed-off-by: Jon Smirl [EMAIL PROTECTED]
---
arch/powerpc/sysdev/fsl_soc.c | 122 -
Yes. As a side note, since there are multiple devices that contain
e.g. a sec-1.0, it would be prudent to describe the exact incarnation
in the device tree, like mpc8272-sec or something, in either model
but 'fsl,sec-X.Y' /does/ describe the exact incarnation,
No it doesn't. If it's on a
The following commits have been added to the master and powerpc-next
branches of the powerpc.git repository. This includes patches pulled
from Kumar's and Josh's trees.
Paul.
Adrian Bunk (3):
drivers/macintosh: Various cleanups
powerpc: Don't export asm/asm-compat.h to userspace
On Tue, 1 Jul 2008 01:27:58 +0200
Segher Boessenkool [EMAIL PROTECTED] wrote:
Yes. As a side note, since there are multiple devices that contain
e.g. a sec-1.0, it would be prudent to describe the exact incarnation
in the device tree, like mpc8272-sec or something, in either model
but
Paul Mackerras writes:
The following commits have been added to the master and powerpc-next
branches of the powerpc.git repository. This includes patches pulled
from Kumar's and Josh's trees.
Hold off from pulling this for now, everyone... I inadvertently broke
builds with 64k pages by
Currently the kernel fails to build with the above config options with:
CC arch/powerpc/mm/mem.o
arch/powerpc/mm/mem.c: In function 'arch_add_memory':
arch/powerpc/mm/mem.c:130: error: implicit declaration of function
'create_section_mapping'
This patch explicitly includes asm/sparsemem.h
On Mon, Jun 30, 2008 at 11:55:02PM +0530, Kamalesh Babulal wrote:
Hi Stephen,
next-20080630 kernel build fails on powerpc, with randconfig
CC arch/powerpc/mm/mem.o
arch/powerpc/mm/mem.c: In function ‘arch_add_memory’:
arch/powerpc/mm/mem.c:130: error: implicit declaration
On Tue, 2008-07-01 at 11:27 +1000, Paul Mackerras wrote:
Paul Mackerras writes:
The following commits have been added to the master and powerpc-next
branches of the powerpc.git repository. This includes patches pulled
from Kumar's and Josh's trees.
Hold off from pulling this for now,
I wrote:
Hold off from pulling this for now, everyone... I inadvertently broke
builds with 64k pages by leaving in some stuff that was purely for
testing in my Only demote individual slices rather than whole
process patch. I'll re-do the tree in order to avoid breaking
bisection.
I have
On Tue, 01 Jul 2008 11:45:10 +1000
Benjamin Herrenschmidt [EMAIL PROTECTED] wrote:
On Tue, 2008-07-01 at 11:27 +1000, Paul Mackerras wrote:
Paul Mackerras writes:
The following commits have been added to the master and powerpc-next
branches of the powerpc.git repository. This
Any chance to get my 4xx PTE rework in too ?
I asked you about that 2 weeks ago. I also asked you to spin a v2 with
the comments Kumar asked for. I got nothing back.
If you want it in 2.6.27, do that soon please :)
Oops... though I did it. Let me check what I have ...
Ben.
Below are a couple of fixes for VSX.
Signed-off-by: Michael Neuling [EMAIL PROTECTED]
---
Paulus: please apply to your powerpc-next tree
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
This correctly hooks the VSX dump into Roland McGrath core file
infrastructure. It adds the VSX dump information as an additional elf
note in the core file (after talking more to the tool chain/gdb guys).
This also ensures the formats are consistent between signals, ptrace
and core files.
Fix compile error when CONFIG_VSX is enabled.
arch/powerpc/kernel/signal_64.c: In function 'restore_sigcontext':
arch/powerpc/kernel/signal_64.c:241: error: 'i' undeclared (first use in this
function)
Signed-off-by: Michael Neuling [EMAIL PROTECTED]
---
arch/powerpc/kernel/signal_64.c |1
On Jun 30, 2008, at 9:44 PM, Benjamin Herrenschmidt wrote:
Any chance to get my 4xx PTE rework in too ?
I asked you about that 2 weeks ago. I also asked you to spin a v2
with
the comments Kumar asked for. I got nothing back.
If you want it in 2.6.27, do that soon please :)
Oops...
This is some preliminary work to improve TLB management on SW loaded
TLB powerpc platforms. This introduce support for non-atomic PTE
operations in pgtable-ppc32.h and removes write back to the PTE from
the TLB miss handlers. In addition, the DSI interrupt code no longer
tries to fixup write
In message [EMAIL PROTECTED] you wrote:
Fix compile error when CONFIG_VSX is enabled.
arch/powerpc/kernel/signal_64.c: In function 'restore_sigcontext':
arch/powerpc/kernel/signal_64.c:241: error: 'i' undeclared (first use in this
function)
FYI.. this was caused by a merge conflict with
On 6/24/08 5:08 PM, Grant Erickson wrote:
Various instances of the EMAC core have varying: 1) number of address
match slots, 2) width of the registers for handling address match slots,
3) number of registers for handling address match slots and 4) base
offset for those registers.
As the
On May 20, 2008, at 2:39 PM, Rune Torgersen wrote:
Fix CPM serial port corruption when running with CONFIG_PREEMPT_RT.
Userland usage of console, and kernel printf's were stepping on each
others toes.
Also only take lock if not in an oops.
Signed-off-by: Rune Torgersen [EMAIL PROTECTED]
There isn't any reason at this point that we can't build 82xx, 83xx 86xx
support in with the other 6xx based boards. Twiddle the Kconfigs to allow
this.
This allows us to remove the machine type selection for related to 6xx.
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
Rebased against
To allow for a single kernel image on e500 v1/v2/mc we need to fixup lwsync
at runtime. On e500v1/v2 lwsync causes an illop so we need to patch up
the code. We default to 'sync' since that is always safe and if the cpu
is capable we will replace 'sync' with 'lwsync'.
We introduce CPU_FTR_LWSYNC
77 matches
Mail list logo
