Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Kumba <kumba@gentoo.org>
To: linux-mips@linux-mips.org
Subject: Re: [PATCH 2.6.X] Early console for Cobalt
Date: Sun, 12 Feb 2006 23:18:57 -0500	[thread overview]
Message-ID: <43F008B1.7070103@gentoo.org> (raw)
In-Reply-To: <20060213.114359.07641583.nemoto@toshiba-tops.co.jp>

Atsushi Nemoto wrote:
>>>>>> On Sun, 12 Feb 2006 17:10:25 +0000, Peter Horton <pdh@colonel-panic.org> said:
> pdh> Adds early console support for Cobalts.
> 
> We already have EARLY_PRINTK.  How about using it?  (like dec does)

I already tried getting early printk to work....Either it wasn't initializing 
early enough for my needs, I was enabling it incorrectly, or it just doesn't 
work on Cobalt.  This does work, however, and already pointed out one obvious 
flaw I have in a patch I've been using on Cobalt (setting cpu_scache_line_size 
to > 0 when cobalt lacks an scache).

For systems where the serial device can be difficult to use until initialized 
late in the boot cycle (Octane comes to mind), early_printk won't function either.

Maybe some kind of framework is needed for defining the kinds of early console 
various systems can support?


--Kumba

-- 
Gentoo/MIPS Team Lead
Gentoo Foundation Board of Trustees

"Such is oft the course of deeds that move the wheels of the world: small hands 
do them because they must, while the eyes of the great are elsewhere."  --Elrond

  reply	other threads:[~2006-02-13  4:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-12 17:10 [PATCH 2.6.X] Early console for Cobalt Peter Horton
2006-02-13  2:43 ` Atsushi Nemoto
2006-02-13  4:18   ` Kumba [this message]
2006-02-13  4:38     ` Atsushi Nemoto
2006-02-13 13:19   ` Ralf Baechle
2006-02-13  9:56 ` Ralf Baechle

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=43F008B1.7070103@gentoo.org \
    --to=kumba@gentoo.org \
    --cc=linux-mips@linux-mips.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