linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kent Borg <kentborg@borg.org>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: register_serial() confusions
Date: Wed, 26 Feb 2003 11:33:41 -0500	[thread overview]
Message-ID: <20030226113341.C23430@borg.org> (raw)
In-Reply-To: <20030225193807.A18152@borg.org>; from kentborg@borg.org on Tue, Feb 25, 2003 at 07:38:07PM -0500


On Tue, Feb 25, 2003 at 07:38:07PM -0500, Kent Borg wrote:
>
> How does register_serial() get called?  (Does it?)

It turns out "Does it?" was key.  If I am on the right track, my
non-module, non-PCMCIA code will never call register_serial().

Yes, I was missing some initialization, and is was my missing adding a
call to my version of serial_console_init().  Oops.  Sorry to be a
bother.


-kb

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2003-02-26 16:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-26  0:38 register_serial() confusions Kent Borg
2003-02-26 16:33 ` Kent Borg [this message]

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=20030226113341.C23430@borg.org \
    --to=kentborg@borg.org \
    --cc=linuxppc-embedded@lists.linuxppc.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).