public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Mark A. Greer" <mgreer@mvista.com>
To: davidm@hpl.hp.com
Cc: linux-kernel@vger.kernel.org, steiner@sgi.com, davidm@napali.hpl.hp.com
Subject: Re: can we drop early_serial_setup()?
Date: Mon, 23 Sep 2002 18:44:14 -0400	[thread overview]
Message-ID: <3D8F993E.81D33FE8@mvista.com> (raw)
In-Reply-To: 200209200459.g8K4xJcW011057@napali.hpl.hp.com

David,

Sorry for the delay, we've had email problems most of last week.

Yes, we can get rid of the early_serial_setup() in ev64260_setup.c, no
problem there.  I'm very busy on some other things right now but I'll try
to get to that soon.  If you can't wait, go ahead and make the change and
I will test it for you.

Mark
--

David Mosberger wrote:

> The early_serial_setup() routine was broken during the big serial
> clean up that happened a while ago.  I fixed this problem for ia64 by
> introducing a new routine called early_register_port() (see below).
> It serves the same purpose as early_serial_setup(), with the only
> difference being that the argument passed to it is now a "uart_port"
> structure (instead of a "serial_struct").  Russell King suggested to
> get rid of early_serial_setup() alltogether, since it is broken anyhow
> and serves no purpose anymore.  However, as far as I can tell, there
> are two places left which use this routine:
>
>         arch/ia64/sn/kernel/setup.c
>         arch/ppc/platforms/ev64260_setup.c
>
> It's should be easy to convert these files to early_register_port(),
> but since I can't test the platform's in question (PPC and SGI SN
> machine), I'd like to know whether it's OK to drop
> early_serial_setup() now.  If someone wants some hints on how to do
> the conversion, let me know (sample code is in 8250_hcdp.c).
>
> Thanks,
>
>         --david
>
> int __init early_register_port (struct uart_port *port)
> {
>         if (port->line >= ARRAY_SIZE(serial8250_ports))
>                 return -ENODEV;
>
>         serial8250_isa_init_ports();    /* force ISA defaults */
>         serial8250_ports[port->line].port = *port;
>         serial8250_ports[port->line].port.ops = &serial8250_pops;
>         return 0;
> }


      parent reply	other threads:[~2002-09-23 22:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-20  4:59 can we drop early_serial_setup()? David Mosberger
2002-09-20 23:33 ` Matt Porter
2002-09-20 23:23   ` David Mosberger
2002-09-21 13:45     ` Matt Porter
2002-09-23 19:02       ` David Mosberger
2002-09-23 22:44 ` Mark A. Greer [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=3D8F993E.81D33FE8@mvista.com \
    --to=mgreer@mvista.com \
    --cc=davidm@hpl.hp.com \
    --cc=davidm@napali.hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steiner@sgi.com \
    /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