mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: mustang4@free.fr
To: Willy Tarreau <willy@w.ods.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux Kernel Hang or stop after uncompressing MPC8245
Date: Mon, 15 Aug 2005 22:08:18 +0200	[thread overview]
Message-ID: <1124136498.4300f6321bb1b@imp5-q.free.fr> (raw)
In-Reply-To: <20050815165141.GA29660@alpha.home.local>

Thanks Willy,

So i just compile a new Kernel with options we have talking about...
And it's freeze, nothing to the console...

So i need to find the way to enable the Level-Triggered Interrupts in the kernel
to the right IRQ address...
I read the thread... but i can't find the thing to change in kernel source or
kernel configuration.

Or perhaps i enable to many option in
"Device Drivers  --->" "Character devices-->" "Serial drivers  --->"
<*> 8250/16550 and compatible serial support                     x x
  x x    [*]   Console on 8250/16550 and compatible serial port           x x
  x x    (4)   Maximum number of non-legacy 8250/16550 serial ports       x x
  x x    [*]   Extended 8250/16550 serial driver options                  x x
  x x    [*]     Support more than 4 legacy serial ports                  x x
  x x    [*]     Support for sharing serial interrupts                    x x
  x x    [ ]     Autodetect IRQ on standard ports (unsafe)                x x
  x x    [*]     Support special multiport boards                         x x
  x x    [*]     Support RSA serial ports

Try autodetect IRQ ?
I'll try to learn more about  edge/level irq sharing...

Yann

> Hi,
>
> On Mon, Aug 15, 2005 at 06:56:42PM +0200, mustang4@free.fr wrote:
> > Hi,
>
> > This is what my board say (in console mode) about serial address:
> > 0x08 COM1             DUART8245    0xfc004500 0x07a12000 0x00000001
> 0x01effc70
> > 0x09 COM2             DUART8245    0xfc004600 0x07a12000 0x00000001
> 0x01e107d0
>
> Have you read this thread ?
>
>   http://ozlabs.org/pipermail/linuxppc-embedded/2005-August/019482.html
>
> It discusses your about your board, on which interrupts must be set to LEVEL
> and not EDGE. BTW, they also used 8250. I don't know how you have to
> configure
> the serial ports though.
>
> This boot log also confirms that you have to use 8250/16550 :
>
>   http://mhonarc.axis.se/jffs-dev/msg01350.html
>
> > >   - are you sure that you enabled "console on serial port" in the config
> ?
> > Yes, i enable " Support for console on virtual terminal" but i enable
> > "Non-standard serial port support" option too...
> > So i recompile without the last one... and i recompile "with Serial drivers
> > --->" "[*]   Console on 8250/16550 and compatible serial port" perhaps it's
> > that... And i came back to you.
> > But, perhaps i've allready tested... i ll check.. it's not a default option
> ?
>
> It's not necessarily a default option. There are many console and serial
> ports combination available. BTW, you could also try netconsole which will
> send you the console data over an ethernet port if you cannot get the serial
> to work.
>
> > >   - how can you be certain that the serial will appear on ttyS0 and not
> ttyS1
> > >     or another one (the kernel might detect another serial port which it
> > >     assigns ttyS0)
> > I pass parameter directly to the kernel;
>
> ok.
>
> > Another option i set :
> >  Default bootloader kernel arguments  x x  x x(console=ttyS0,9600
> console=tty0
>
> ok.
>
> Regards,
> Willy
>
>



  reply	other threads:[~2005-08-15 20:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-15 16:10 mustang4
2005-08-15 15:55 ` Willy Tarreau
2005-08-15 16:56   ` mustang4
2005-08-15 16:51     ` Willy Tarreau
2005-08-15 20:08       ` mustang4 [this message]
2005-08-15 20:54         ` Willy TARREAU
2005-08-16 13:34           ` mustang4

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1124136498.4300f6321bb1b@imp5-q.free.fr \
    --to=mustang4@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=willy@w.ods.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®