All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Habets <errandir_news@mph.eclipse.co.uk>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH] sparc: remove sunzilog_console_init
Date: Thu, 29 Jun 2006 17:02:09 +0000	[thread overview]
Message-ID: <20060629170209.GA4800@palantir8> (raw)
In-Reply-To: <20060628141601.GA31139@palantir8>

On Wed, Jun 28, 2006 at 11:35:41AM -0700, David Miller wrote:
> From: Martin Habets <errandir_news@mph.eclipse.co.uk>
> Date: Wed, 28 Jun 2006 15:34:02 +0100
> 
> > It was tested on a SS20 with the console on a sunzilog.
> 
> Where does the register_console() call occur then?
> 
> Oh, it happens in the serial layer because we set
> the ->cons member of sunzilog_reg right?

Yes, sunzilog_ports_init calls uart_add_one_port, which calls
register_console (at serial_core.c:2270) with the new SUNZILOG_CONSOLE
function.

It's all more convoluted, but effectively SUNZILOG_CONSOLE has replaced
sunzilog_console_init.

>> I did some transformations over the last year that somehow
>> made this function no longer invoked, when it should be,
>> and I need to figure that out and fix the problem properly.

While it is possible to keep the function and call it like before
from sunzilog_ports_init, personally I don't see the point. Better
call SUNZILOG_CONSOLE if that's what you realy want.

-- 
Martin

  parent reply	other threads:[~2006-06-29 17:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-28 14:16 [PATCH] sparc: remove sunzilog_console_init Martin Habets
2006-06-28 14:34 ` Martin Habets
2006-06-28 16:43 ` Raymond Burns
2006-06-28 18:32 ` David Miller
2006-06-28 18:35 ` David Miller
2006-06-29 17:02 ` Martin Habets [this message]
2006-06-29 17:08 ` Martin Habets
2006-06-29 19:53 ` David Miller
2006-06-29 19:54 ` David Miller
2006-06-29 22:19 ` Raymond Burns

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=20060629170209.GA4800@palantir8 \
    --to=errandir_news@mph.eclipse.co.uk \
    --cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.