Right. Guess I found it hard way :) After using LEVEL interrupt, it all works now.
On 8/2/05, Kumar Gala <kumar.gala at freescale.com> wrote: > > On Aug 1, 2005, at 10:38 PM, JohnsonCheng wrote: > > > Dear Daniel, > > > > I also meet this problem on MPC8245 with linux-2.6.12.3, and I > > found it uses > > LEVEL for interrupt in sandpoint.c. Do you have any idea for it? > > All internal interrupts on the MPC8245/1 should be LEVEL interrupts. > > - kumar > > > -----Original Message----- > > From: linuxppc-embedded-bounces at ozlabs.org > > [mailto:linuxppc-embedded-bounces at ozlabs.org] On Behalf Of Daniel Ann > > Sent: Monday, August 01, 2005 9:27 AM > > To: Anton W?llert > > Cc: linuxppc-embedded at ozlabs.org > > Subject: Re: Serial console > > > > Thanks for your input Anton. > > I'm not all that certain about sandpoint platform has its own serial > > driver so I've worked with 8250.c. Anyway, I've got it working now. It > > was problem with interrupt. As soon as I changed interrupt from EGDE > > to LEVEL it began working. Altho I'm faced with yet another problem > > with openpic but I'm digging thru it at the moment. > > > > BTW, I have no idea why EDGE didnt work and LEVEL does. > > > > Cheers, > > Daniel > > > > On 7/30/05, Anton W?llert <a.woellert at gmail.com> wrote: > > > >> Daniel Ann wrote: > >> > >>> Hi folks, > >>> > >>> Having all the kernel boot up log on console means that I've done > >>> some > >>> part right. But why am I not getting anything from the user > >>> processes > >>> on the console screen ? > >>> > >>> Is there anything I need to do on the kernel config ? > >>> > >>> > >> > >> Hi, we've had the same problem some time ago on a tqm850l > >> (mpc850). Our > >> problem was, that we had registered two serial consoles in the kernel > >> config or something like that. we had to disable all serial-driver > >> stuff > >> and enable just the platform-specific serial-console driver. we > >> tracked > >> this down with inserting a printk(buf) into the tty_write fs-op of > >> the > >> serial-port driver in drivers/char/tty_io.c. the ttyS0 was used > >> but has > >> taken another serial-driver than the platform specific. > >> > >> may this help you :) > >> > >> > >> anton > >> > >> > > > > > > -- > > Daniel > > _______________________________________________ > > Linuxppc-embedded mailing list > > Linuxppc-embedded at ozlabs.org > > https://ozlabs.org/mailman/listinfo/linuxppc-embedded > > > > _______________________________________________ > > Linuxppc-embedded mailing list > > Linuxppc-embedded at ozlabs.org > > https://ozlabs.org/mailman/listinfo/linuxppc-embedded > > > > -- Daniel
