Hi Dave,
I run embedded Linux on ppc405 (ml403 xilinx evaluation board). I use
the GPIO based device build on FPGA part of the xilinx chip. My gpio device
generates interrupts whenever it changes its state.
I use Montavista gpio driver with some modifications to react on interrupts.
Each
Hi Dave,
I have found the book by Rubini you have mentioned:
http://www.oreilly.com/catalog/linuxdrive3/book/index.csp
I did not find however what would be the best way to propagate interrupt
signals to the USER level / notify the client that interrupt has occurred.
I have checked also in
Dear all,
Does anyone know that whether U-boot can support Xilinx TEMAC core to tftp
the Linux kernel or not. In my design I am using TEMAC instead of the
normal enet. While I found that in the Xilinx u-boot tree, there is only a
directory for xilinx_enet instead of xilinx_temac. I am not sure
Hi All:
I'm trying to bring up linux 2.6.21.1 on an ml405 board. The kernel
boots fine but the init process does not produce any output. The /init
program resides in an initramfs file system and I believe the /dev
device files have been set up correctly. Here's an excerpt from my
initramfs
Dear Sharon,
Sorry that I don't know the detail of what you suggested. Could you say
something more on that? Shall I patch U-boot to add the driver for TEMAC in
U-boot? and where is the patch? Or I just modify some parameters in the
existing files? Thanks for your detailed information and
I have mpc83xx,
I saw that I need to use swab32 to any read\write operation from registers,
I don't understand why I need it?
Do I need it for all registers?
Why in the mpc8313 reference in registers description some bits look like
31,30,29,.,3,2,1,0
And some: 0,1,2,3.,30,31
Is it just
Hi Anton,
it looks as if your init executable is not doing the right thing and for
some reason terminates. Maybe your inittab configuration is wrong? Maybe
the init executable has been compiled with the wrong options?
You can try to copy another executable (e.g. sh, getty) into /init and
see if
Just a guess, but do you have stdout and friends defined as recommended
in the Compulsory links section of Documentation/devices.txt?
-Michael
-Original Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
rg] On Behalf Of Anton Kowalski
Sent: Wednesday, August 08,
Wolfgang,
Thanks, I'll try your suggestion.
It's worth noting that the init executable is calling into the kernel.
I put a printk in sys_write, which is on the call path of printf() and
the output is sent to the console. However, the output of printf is
not to be seen. This suggests the problem
The thing that points to a problem with init is:
Kernel panic - not syncing: Attempted to kill init!
What is the string that is supposed to be printed? Maybe the printf
tries to print a string at an invalid address, causing init to crash?
Also, you can check if you set the option for console
Yoni Levin wrote:
I have mpc83xx,
I saw that I need to use swab32 to any read\write operation from registers,
Only little endian registers (such as PCI).
Why in the mpc8313 reference in registers description some bits look like
31,30,29,.,3,2,1,0
And some: 0,1,2,3.,30,31
Most PowerPC
Yoni Levin wrote:
I have mpc83xx,
I saw that I need to use swab32 to any read\write operation from registers,
BTW, you should be using in/out_le32() (or for PCI MMIO, readl/writel)
rather than swab32(). This will be more efficient since it can use the
lwbrx/stwbrx instructions, and it will
Hi Domen,
On Tue, 24 Jul 2007 07:14:31 +0200, Domen Puncer wrote:
Disabling module on stop doesn't work on some CPUs (ie. mpc8241,
as reported by Guennadi Liakhovetski), so remove that.
Disable I2C module on errors/interrupts to prevent it from
locking up on mpc5200b.
Signed-off-by:
Hi Mirek,
I run embedded Linux on ppc405 (ml403 xilinx evaluation board).
I use the GPIO based device build on FPGA part of the xilinx
chip. My gpio device generates interrupts whenever it changes
its state.
I use Montavista gpio driver with some modifications to react
on interrupts. Each
On Wed, 8 Aug 2007, Jean Delvare wrote:
Hi Domen,
On Tue, 24 Jul 2007 07:14:31 +0200, Domen Puncer wrote:
Disabling module on stop doesn't work on some CPUs (ie. mpc8241,
as reported by Guennadi Liakhovetski), so remove that.
Disable I2C module on errors/interrupts to prevent it from
On 8/8/07, Wolfgang Reissnegger [EMAIL PROTECTED] wrote:
The thing that points to a problem with init is:
Kernel panic - not syncing: Attempted to kill init!
What is the string that is supposed to be printed? Maybe the printf
tries to print a string at an invalid address, causing init to
Indeed I hadn't set up the compulsary links correctly. In reading
through the devices.txt document I realized that I don't have /proc
mounted either. So the following links might not make much sense until
/proc is up.
slink /dev/fd /proc/self/fd 777 0 0
slink /dev/stdin /proc/self/fd/0
Hi all,
First off big thanks to the guys working on the Cypress USB C67X00 driver!
Without them I would not even be this far.
But my question for them is: How are you guys initializing the Cypress chip?
It looks like the driver is expecting the cypress to be programmed and ready.
I have a
On Aug 5, 2007, at 4:00 AM, Joachim Förster wrote:
Meanwhile, I had a _very_ short look into ASoC ... and I don't really
know ... My driver already uses the AC97 Layer of ALSA, so in some way
the codec is already separated from the controller. Xilinx' AC97
Controller Reference does have some
On Tue, 2007-08-07 at 23:43 +0200, Clemens Koller wrote:
You can either use FPU emulation or do the floating point stuff on the e500
core's SPE (Signal Processing Engine) which is AFAIK not supported by any
major distribution.
I do have FPU emulation enabled in the kernel. I was able to get a
20 matches
Mail list logo
