From: jbarnes@sgi.com (Jesse Barnes)
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] Update SN2 defconfig
Date: Tue, 16 Mar 2004 17:38:51 +0000 [thread overview]
Message-ID: <20040316173851.GB29899@sgi.com> (raw)
In-Reply-To: <20040315190240.GY6699@localhost>
On Tue, Mar 16, 2004 at 09:36:28AM -0700, Bjorn Helgaas wrote:
> On Monday 15 March 2004 11:14 pm, David Mosberger wrote:
> > The ia64 EARLY_PRINTK support is not part of the official kernel, so
> > they should be lost to avoid warnings (if someone wanted to integrate
> > the ia64 EARLY_PRINTK patch with the other early-printk support in the
> > kernel, that would certainly be welcome, though).
>
> I'm cooking some stuff in this area. I think it will give us the
> equivalent of early printk pretty much for free. It doesn't help
> with SGI boxes, though, because they have the funny console ;-)
> I'll try to post a preliminary patch today or tomorrow.
Our console should work very early on (our driver supports a polling
mode that should allow this), so hopefully we can reuse your work...
Thanks,
Jesse
next prev parent reply other threads:[~2004-03-16 17:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 19:02 [PATCH] Update SN2 defconfig Martin Hicks
2004-03-15 19:05 ` Jesse Barnes
2004-03-16 6:14 ` David Mosberger
2004-03-16 16:36 ` Bjorn Helgaas
2004-03-16 17:37 ` Jesse Barnes
2004-03-16 17:38 ` Jesse Barnes [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-25 22:27 [PATCH] update sn2_defconfig Jesse Barnes
2004-06-16 16:08 Jesse Barnes
2004-08-20 19:31 Jesse Barnes
2004-11-01 22:38 Jesse Barnes
2006-04-27 10:10 [patch] update sn2 defconfig Jes Sorensen
2006-04-27 11:50 ` Robin Holt
2006-04-27 12:10 ` Jes Sorensen
2006-04-27 23:51 ` Luck, Tony
2006-04-28 7:45 ` Jes Sorensen
2006-10-09 9:24 [patch] update sn2_defconfig Jes Sorensen
2007-09-19 9:54 Jes Sorensen
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=20040316173851.GB29899@sgi.com \
--to=jbarnes@sgi.com \
--cc=linux-ia64@vger.kernel.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