From: "David S. Miller" <davem@redhat.com>
To: Matthew Wilcox <willy@debian.org>
Cc: linux-arch@vger.kernel.org
Subject: Re: [RFC][PATCH 3/3] Convert console list to list_head
Date: Mon, 14 Jun 2004 17:20:22 -0700 [thread overview]
Message-ID: <20040614172022.57239426.davem@redhat.com> (raw)
In-Reply-To: <20040614140204.GC20511@parcelfarce.linux.theplanet.co.uk>
On Mon, 14 Jun 2004 15:02:04 +0100
Matthew Wilcox <willy@debian.org> wrote:
> This gets into one of the ugliest bits of the parisc patch that I haven't
> figured out how to do cleanly yet. We have a firmware console (called
> PDC console) that may be printing to screen or serial. The device
> that's being addressed might be on a PCI bus, so we can't print to it
> while we're walking the PCI busses. We also can't use it after boot, or
> it'll fight with the serial driver. So we have the following patch in our
> tree:
Thanks for mentioning this Matthew. I never considered these kinds
of issues very much on Sparc although it might cause problems
for us too.
When we use the firmware console, it just outputs to whatever
device the firwmare has been configured to use (framebuffer,
serial, etc.) I think we are lucky because if the firmware allocates
resources for a PCI device, we never change things.
next prev parent reply other threads:[~2004-06-15 0:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 12:45 [PATCH 1/3] Provide console_device() Russell King
2004-06-14 12:45 ` [PATCH 1/3] Provide console_suspend() and console_resume() Russell King
2004-06-14 12:46 ` [RFC][PATCH 3/3] Convert console list to list_head Russell King
2004-06-14 14:02 ` Matthew Wilcox
2004-06-15 0:20 ` David S. Miller [this message]
2004-06-14 17:46 ` David Mosberger
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=20040614172022.57239426.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=willy@debian.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