Re: External interrupt type?

return 0; +} + static struct irq_chip mpc52xx_extirq_irqchip = { .typename = " MPC52xx IRQ[0-3] ", .mask = mpc52xx_extirq_mask, .unmask = mpc52xx_extirq_unmask, .ack = mpc52xx_extirq_ack, + .set_type = mpc52xx_extirq_set_type, }; /* rg kd On Fri, 2008-03-14 at

External interrupt type?

Hello, I am dealing with external interrupts on an custom board of the mpc5200b. Kernel is 2.6.24 from kernel.org. I can declare the interrupt in the dts for the board and the control register is set correctly, i.e. the correct external interrupt is enabled. On the other hand the type is ignore

RE: LPC burst accesses

bank, which implies multiplexed mode of the bank. Multiplexed mode I am not able to do, at least not at this time. rg kd -- Kári Davíðsson | [EMAIL PROTECTED] Hugbúnaðargerð | www.marel.com Tel: +354 563 8156 Fax: +354 563 8001 Iceland -Original

LPC burst accesses

Hi, I am in the process of optimizing read accesses to an FPGA in one of our custom mpc5200b boards. I have attempted to do this in two ways, i.e. 1) With the the general SDMA task. Also used by the AC97 audio codec driver. 2) Trought the SCLPC fifo offered in relation with the LP bus. The doc

RE: OF devices and non OF devices

Yes there was indeed. Combination of my misunderstanding, device trees and board specific initialization. Things are working now. Thanks, kd From: John Rigby [mailto:[EMAIL PROTECTED] Sent: 5. júlí 2007 17:21 To: Kári Davíðsson Cc: linuxppc-embedded

RE: OF devices and non OF devices

From: John Rigby [mailto:[EMAIL PROTECTED] Sent: 3. júlí 2007 16:31 To: Kári Davíðsson Cc: linuxppc-embedded@ozlabs.org Subject: Re: OF devices and non OF devices One place to find binding between OF devices and non OF devices is in arch/powerpc/sysdev/fsl_soc.c The typica

OF devices and non OF devices

to the non OF part of the driver space. Any hints or pointers on where to find this glue? Regards, kd P.S. Kernel is post 2.6.20. -- Kári Davíðsson | [EMAIL PROTECTED] Hugbúnaðargerð | www.marel.com Tel: 563-8156 Fax: +354 563 8001 Iceland

Small patches to serial port and ehternet on mpc8xx

Hi, Here are two patches for arch/ppc/8xx_io/uart.c and arch/ppc/8xx_io/enet.c, it applies against the linux sources from the rsync mirror at mvista for the linuxppc-2.4.x devel tree. The first one (enet.patch) adds the polling method for the ethernet driver. It is essential if one wants to us

register_blk_dev seems to do nothing during boot for /dev/mtdblock0

Hi, You (as in "a script/program living on the rootfs") do not need to mount the root to access the root at boot this is handled by the kernel. Check root_dev_names[] in init/do_mounts.c (linuxppc-2.4.19-pre6) and check if a reference to mtdblock is there. You should see something like

register_blk_dev seems to do nothing during boot for /dev/mtdblock0

Hi, If you are using devfs, it is called /dev/mtdblock/0 _not_ /dev/mtdblock0. Do not forget to mount the devfs on boot. Regards, K.D. > -Original Message- > From: "Callebaut, Beno?t" [mailto:benoit.callebaut at barco.com] > Sent: 13. mars 2003 13:11 > To: Linuxppc-Embedded (E-mail) >

[linuxppc-embedded:] 8xx_io/enet.c

> -Original Message- > From: Reinhard Schwillinsky [mailto:rsw at maxxio.at] > Sent: 10. desember 2002 10:43 > To: K?ri Dav??sson > Cc: linuxppc-embedded at lists.linuxppc.org > Subject: Re: [linuxppc-embedded:] 8xx_io/enet.c > [snip snap] > > > > I am a litle unclear on the ethernet opera

8xx_io/enet.c

Duhhh, I was not even running with CONFIG_ENET_BIG_BUFFERS enabled. Enabling this got rid of the error.. Regarding your patch, then 20% throughput increase looks very tempting 8-) Thanks and sorry for the noise, K.D. > -Original Message- > From: Joakim Tjernlund [mailto:joakim.tjer

8xx_io/enet.c

Hello, I am hitting the following code (i.e. the printk() is reached) in the interrupt handler for the ethernet on a custom 823e board in arch/ppc/8xx_io/enet.c /* Check for receive busy, i.e. packets coming but no place to * put them. This "can't happen" because the receive i

Microcode patching

I can deffinitly recomend the driver Joakim sent here. Works much better than the stock driver. K.D. > -Original Message- > From: Joakim Tjernlund [mailto:joakim.tjernlund at lumentis.se] > Sent: 8. n?vember 2002 15:56 > To: Christian Schroeder; linuxppc-embedded at lists.linuxppc.org >

rsync

Hi, Has mvista closed down the rsync access to the kernel source trees? Is someone else providing rsync access or even tar.bz2 access? Regards, K.D. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

DHCP Client???

Yes, it works fine for our purposes. K.D. > -Original Message- > From: Steven Scholz [mailto:steven.scholz at imc-berlin.de] > Sent: 17. okt?ber 2002 12:06 > To: LinuxPPC > Subject: DHCP Client??? > > > > Hi there, > > is someone successfully using the udhcp Server/Client Package from >

[Fwd: Re: kernel command line for CRAMFS root filesystem]

Do not use root=/dev/mtdblock/2 but root=/dev/mtdblock2 even if you are using devfs root=/dev/mdtblock/2 will be interpreted as root=/dev/mtdblock0 This is because of how the kernel parses the root argument on the command line. Hope this helps, K.D. > -Original Message- > From: Julien

cramfs root filesystem corruption

Inactive meaning "unmounted" or just not beeing used? K.D. > -Original Message- > From: Paul Ruhland [mailto:pruhland at microwavedata.com] > Sent: 31. ma? 2002 14:04 > To: wd at denx.de > Cc: linuxppc-embedded at lists.linuxppc.org > Subject: Re: cramfs root filesystem corruption > > >

cramfs root filesystem corruption

Let me guess? Are you updateing the cramfs on a running system, i.e. a system where the cramfs is mounted somewhere? K.D. > -Original Message- > From: Paul Ruhland [mailto:pruhland at microwavedata.com] > Sent: 30. ma? 2002 18:51 > To: linuxppc-embedded at lists.linuxppc.org > Subject:

How to mount romfs in flash as root filesystem?

> -Original Message- > From: Gunnar Larisch [mailto:la at softing.com] > Sent: 30. apr?l 2002 08:41 > To: Wolfgang Denk > Cc: Dross Zhou; linuxppc-embedded at lists.linuxppc.org > Subject: Re: How to mount romfs in flash as root filesystem? > > > > On Mon, Apr 29, 2002 at 04:35:24PM +0200,

sporadic kernel panic during boot (MPC8xx, FEC)

I have had this "random crashes" for linux 2.4.18-pre1 from linuxppc-2_4_devel for some time now, it was not to annoying, since so much other stuff has been unstable for us. Theses crashses ware mostly during booting of the kernel, i.e. if the kernel made it through the boot it seemed to run stabl

Setting i2c_i2brg

This is covered in chapter 16.13 of the reference manual for the mpc823e, especially in 16.13.7 "Programming the I2C Controller" Check 16.13.7.5 where they discuss the I2BRG register. I believe you can run it at any speed upto 115kb/s (you might even get higher but then it is device specific) Ho

rsync access of kernel sources

Hi, Sometimes when I have rsynced with the mvista mirror of the kernel sources the source tree is in a inconsistent state, i.e. some files are missing. I suspect this is because I rsynced at the same time as the mirror is beeing updated. I imagine this is done automatically at predefined times.

Kernel Oops when receiving a lot of UDP packets while booting

> -Original Message- > From: Peter Desnoyers [mailto:pdesnoyers at chinook.com] > Sent: 7. jan?ar 2002 15:02 > To: K?ri Dav??sson > Cc: LEROY Christophe; linuxppc > Subject: Re: Kernel Oops when receiving a lot of UDP packets while > booting > > > > I have verified that I am getting packet

Kernel Oops when receiving a lot of UDP packets while booting

Hi, I have verified that I am getting packets over the ethernet before the scc_enet_open() is called, I somehow suspect that this might be causing my random crashes. I inserted the following in enet.c static int opened = 0 and in scc_enet_open() I put opened = 1; and in scc_enet_interrupt()

Level 7 interrupt

Hi, I am using linuxppc_2_4_devel. I have been seeing ocational crash of the kernel during boot (I measured around 1% crashes by putting /sbin/reboot in /etc/init.d/rcS). After having spent some time debugging this I noticed that in kernel/m8xx_setup.c there is registered an interrupt handler fo

ramdisk problems: No init found

You have to make shure the links excist on the ramdisk, specially then link from /bin/init to /bin/busybox. K.D. > -Original Message- > From: Alex Zeffertt [mailto:ajz at cambridgebroadband.com] > Sent: 12. desember 2001 17:22 > To: linuxppc-embedded > Subject: ramdisk problems: No init

CPM interrupts raised to early? (was More I2C stuff,)

Hi, > -Original Message- > From: Joakim Tjernlund [mailto:Joakim.Tjernlund at lumentis.se] > Sent: 29. okt?ber 2001 21:46 > To: K?ri Dav??sson > Cc: linuxppc-embedded at lists.linuxppc.org > Subject: RE:CPM interrupts raised to early? (was More I2C stuff,) > > > Hi Kari > > This rings a b

CPM interrupts raised to early? (was More I2C stuff,)

Hi, After recovreing few hours of sleep during the weekend I am back to the I2C stuff. I was wrong that the interrupt routine was never called (in i2c-algo-8xx.c). Somehow cpm_debug > 1 became cpm_debug == 1 to my eyes. Anyways after incresingddd the debug level, i.e. setting cpm_debug = 2 I veri

More I2C stuff

Hi, I got the I2C stuff working (kind off), i.e. the drivers compile and run without crashing. Writing and reading seem to work, i.e. by looking with scope on the signals everyting looks looks normal (I have a microchip i2c memory on the i2c bus for testing). The interrupt handler is never calle

microcodepatch

Hi, Indeed the microcode patch seemd to be different, but even though I use the I2C 823 patch downloaded from the mot.com site. Everything behaves the same untill I compile the I2C support code into the kernel then the network does not crash the kernel. K.D. > -Original Message- > From:

microcodepatch

I will apply this patch. But the ethernet is crashing before I install the I2C driver. (The I2C driver is compiled as a module). K.D. > -Original Message- > From: Peter Desnoyers [mailto:pdesnoyers at chinook.com] > Sent: 24. okt?ber 2001 19:07 > To: K?ri Dav??sson > Cc: Linux Embedded p

microcodepatch

> -Original Message- > From: Der Herr Hofrat [mailto:der.herr at hofr.at] > Sent: 24. okt?ber 2001 19:02 > To: K?ri Dav??sson > Cc: Linux Embedded ppc (E-mail) > Subject: Re: microcodepatch > > > > > > > Hi, > > > > Are there any known issues regarding the I2C patch and the ethernet > > dr

microcodepatch

Hi, Are there any known issues regarding the I2C patch and the ethernet driver? If I disable the microcode patch everything works fine, except the I2C stuff. I am using the linuxppc_2_4_devel tree ported to our custom board with ehternet on SCC2. Regards, K.D. ** Sent via the linuxppc-embedd

crashme produces hang of linux

Hi, Once I was exsperimenting with crashme and it was very easy to get it to crash the kernel, it was always on floating point instructions. It was before there was any floating point emulation in the kernel (in the 2.2.x days and you are running 2.2.14). I have not tried crashme since then but y

What is the version RTLinux and its corresponding version of Linux can support 8260?

I do not know enough of 8260, nor RT-linux, but you seem to be using the kernel from kernel.org. Even though it is the official kernel for most people (read Intel people). There are some deviations from the kernel that ppc people use. Try to download the kernel from fsmlabs.com. I believe that the

Whate kind of kernel errors cause an Segmentation Fault

Well he asked what kind of kernel error causes segfault. If I am not wrong returning EFAULT, e.g. from driver causes the kernel to send signal 11 (SIGSEGV) to the application which has default signal handler that causes the application to crash. K.D. > -Original Message- > From: Kenneth

Whate kind of kernel errors cause an Segmentation Fault

EFAULT i believe check linux/include/asm/errno.h K.D. > -Original Message- > From: Ralph Blach [mailto:rcblach at raleigh.ibm.com] > Sent: 30. mars 2001 14:19 > To: Embedded Linux list > Subject: Whate kind of kernel errors cause an Segmentation Fault > > > What kind of kernel return co

how to get the size of a code section.

I am not aware of one, your connection from elf file to application is Elf32_Ehdr in elf.h. An example on how to use this structure is in the binary loader in the kernel, fs/binfmt_elf.c and you can read the spec (just do a search for it on google.com). If you just want to "manage" some elf file

flash writing with Linux

> -Original Message- > From: Matthias Fuchs [mailto:matthias.fuchs at esd-electronics.com] > Sent: 19. mars 2001 17:16 > To: Subodh Nijsure; linuxppc-embedded > Subject: Re: flash writing with Linux > > > > Hi Subodh, > > Subodh Nijsure wrote: > > > > Perhaps you can take a look at mtd and

USB questions (for the MPC8xx)

Hi, This clear up alot of my confusion about the USB host driver. Thanks, K.D. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

USB questions (for the MPC8xx)

Hi, In the m8xxhci.c hci driver for the mpc one can select to use TIMER1 for the SOF generator. A interruopt handler, m8xxhci_timer_interrupt() is registered to handle this interrupt and generate the SOF. Why is it then that the timer is also exported to PA6? Why is it the the USE_TIMER1_FOR_SOF

Going to sleep atomically

Oooops. Sorry for the confusion. I stand corrected. K.D. > -Original Message- > From: Roland Dreier [mailto:roland at topspincom.com] > Sent: 8. mars 2001 16:42 > To: Embedded Linux list > Cc: K?ri Dav??sson > Subject: Re: Going to sleep atomically > > > > KD> Like in blocking read(

Going to sleep atomically

Like in blocking read() and poll() etc? interruptable_sleep_on() or sleep_on() in poll() use poll_wait() K.D. P.S. "Linux Device Drivers" by Rubini is an excellent guide to driver writing, although it is getting quite old (in kernel-time space). Other drivers can serve as tutrials too. K.D. >