On Tue, Apr 15, 2008 at 7:40 PM, rodolfo <[EMAIL PROTECTED]> wrote:
> Hi Grant likely,
>
> I got kernel 2.6.20 from kernel.org and I want boot it on XUP Virtex II Pro
This is an old kernel. Use a current kernel.
> University board.
> I edited the Makefile putting:
> ARCH? = ppc
> CROSS_CO
On Apr 15, 2008, at 11:25 AM, Gutson Daniel-ADG035 wrote:
Hi,
I'm doing some work on 2.6.10, and got this problem:
- there are some io_block_mapping calls in the setup_io_mapping
callback, that use the BATs, and passing same va and pa each one.
Problem arises later when vmallocs gets a a
Hi Grant likely,
I got kernel 2.6.20 from kernel.org and I want boot it on XUP Virtex II Pro
University board.
I edited the Makefile putting:
ARCH? = ppc
CROSS_COMPILE? = ppc_4xx-
But I can't see anything about SystemACE driver on make menuconfig from
this Kernel. How can I add SystemACE control
Hi all,
I am trying to switch my design from the PLB Temac to the local link temac,
and i have a problem when trying to run ifconfig in my init script. It
gives me a BUG: soft lockup - CPU#0 stuck for 11s! [ifconfig:208]
Here is the rest of the dump, thanks for your help in advance.
[ 233.11496
Sorry I didn't make myself clear. I just want to use FPU as a normal
co-processor under Linux. I mean different programs and maybe
multiple users, well, for single precision. So I think the exception
handler really helps!
Thank you Steve and John, I added the exception handler. It solved
Hi Shan,
It's not clear what you're trying to do. If you have only one application using
the FPU, and you're setting up the APU and FPU from that user application, I'm
not sure if you need the FPU unavailable handler.
If you're going to have multiple applications use the FPU, then you should us
> -Original Message-
> From: Shanyuan Gao [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 15, 2008 11:47 AM
> To: Stephen Neuendorffer; linuxppc-embedded@ozlabs.org
> Cc: John Bonesio; Yoshio Kashiwagi
> Subject: Re: Problems of using APU/FPU under linux
>
> No, actually I am using head
No, actually I am using head_4xx.S and I cannot find FPU_UNAVAILABLE
in there. Do I need to set it?
And I commented out the _GLOBAL(giveup_fpu) in head_4xx.S because it
has conflicts with fpu.S
Shan
On Apr 15, 2008, at 2:37 PM, Stephen Neuendorffer wrote:
Shanyuan,
Did you install th
Hi,
The following modification is required if you use APU in user space.
in include/asm-powerpc/reg.h
-#define MSR_USER (MSR_KERNEL|MSR_PR|MSR_EE)
+#define MSR_USER (MSR_KERNEL|MSR_PR|MSR_EE|MSR_VEC)
Yoshio Kashiwagi - Nissin Systems
> Thank you very much, Steve and John!
>
> My advisor a
Shanyuan,
Did you install the FPU_UNAVAILABLE trap in head_40x.S?
> -Original Message-
> From: Shanyuan Gao [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 15, 2008 11:34 AM
> To: Yoshio Kashiwagi; linuxppc-embedded@ozlabs.org
> Cc: Stephen Neuendorffer; John Bonesio
> Subject: Re: Prob
Thank you, Yoshio!!
I just applied the change, seems it works! But it doesn't work
correctly. I mean it won't give me traps any more, but the answer is
not correctly. I just tried to multiply two float numbers. But it
gives me 0.
The first time I change the reg.h was to enable apu enable,
Hi,
Currently, I have problem of the UBoot MCC driver. I setup the
internal loopback on MPC8568. And here is the data of each channel:
Channel #Tx DataRx Data
0 0x010x9D
1
Hi,
I'm doing some work on 2.6.10, and got this problem:
- there are some io_block_mapping calls in the setup_io_mapping
callback, that use the BATs, and passing same va and pa each one.
Problem arises later when vmallocs gets a a pointer within the mapped
ranges. In other words, seems like
Disclaimer: I'm working on a new project here, so I'm not 100% up-to-date on
the system as a whole.
I've been tasked to find out why our RTC clock is not being updated after
suynching with a NTP timesource. In our previous release, the RTC seemed to be
updated every 11 minutes via the timer_in
Hi,
We have a design with LLTEMAC0 using channels 0 & 1, and LLTEMAC1 using channel
0. When the Linux kernel boots, we had the following error message:
---
Registering device xilinx_lltemac:0
Registering device xilinx_lltemac:1
xilinx_lltemac.1: failed to claim resource 0
cannot register dev xili
15 matches
Mail list logo