From: Olaf Hering <olh@suse.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.5 and serial console
Date: Mon, 5 May 2003 21:44:10 +0200 [thread overview]
Message-ID: <20030505194410.GA30123@suse.de> (raw)
In-Reply-To: <20030505192910.GA5447@ip68-0-152-218.tc.ph.cox.net>
On Mon, May 05, Tom Rini wrote:
> On Mon, May 05, 2003 at 07:45:44PM +0200, Olaf Hering wrote:
> > On Mon, May 05, Tom Rini wrote:
> >
> > > On Sun, May 04, 2003 at 06:51:16PM +0200, Olaf Hering wrote:
> > >
> > > > Morning,
> > > >
> > > > is there a fix for this? It seems to involve Makefile tweaking, at least.
> > >
> > > What .config file?
> >
> > It seems CONFIG_SERIAL_8250_CONSOLE is gone. I can not activate it
> > anywhere.
>
> You don't ahve CONFIG_SERIAL_8250 selected either. But you do have
> CONFIG_SERIAL_CONSOLE enabled. So the question is then, (a) why do you
> have that set (pmac serial console?) and (b) why don't you have
> CONFIG_SERIAL_8250 set?
I had serial console set. Maybe I screwed my config while hunting for a
workaround.
[*] Support for PowerMac serial ports
[*] Support for console on serial port
Well, I bet such a zImage links in 2.4.
I just enabled the PC part and now I have CONFIG_SERIAL_8250.
grepping for CONFIG_FOO doesnt work anymore, you must grep for FOO now.
fun...
Gruss Olaf
--
USB is for mice, FireWire is for men!
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-05-05 19:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-04 16:51 2.5 and serial console Olaf Hering
2003-05-05 17:25 ` Tom Rini
2003-05-05 17:45 ` Olaf Hering
2003-05-05 19:29 ` Tom Rini
2003-05-05 19:44 ` Olaf Hering [this message]
2003-05-07 20:20 ` Tom Rini
2003-08-15 21:48 ` Olaf Hering
2003-08-15 23:46 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2003-05-04 22:20 Milton D. Miller II
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=20030505194410.GA30123@suse.de \
--to=olh@suse.de \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).