mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Luca <kronos.it@gmail.com>
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Enable legacy support for serial ports when SERIAL_8250_PNP is disabled
Date: Mon, 9 Jul 2007 12:30:01 -0600	[thread overview]
Message-ID: <200707091230.01556.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <68676e00707091030xe7a299je9f4e053ef2a2e98@mail.gmail.com>

On Monday 09 July 2007 11:30:59 am Luca wrote:
> On 7/9/07, Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
> > On Saturday 07 July 2007 05:33:00 pm Luca Tettamanti wrote:
> > > your patch:
> > >
> > > commit 7e92b4fc345f5b6f57585fbe5ffdb0f24d7c9b26
> > > Author: Bjorn Helgaas <bjorn.helgaas@hp.com>
> > > Date:   Tue May 8 00:36:07 2007 -0700
> > >
> > >     x86, serial: convert legacy COM ports to platform devices
> > >
> > > disables probing using legacy code in favour of ACPI/PNP to avoid double
> > > discovery.
> > >
> > > However if SERIAL_8250_PNP is not enabled the user is left without
> > > serial ports (been there, done that - my kernel config suddenly wasn't
> > > working anymore). So:
> >
> > Yes, that's true.  Kconfig should automatically turn on SERIAL_8250_PNP
> > if PNP and SERIAL_8250 are selected, but it does give you a choice if
> > you have EMBEDDED set.  So I guess you must have this:
> >
> >   CONFIG_EMBEDDED=y
> >   CONFIG_PNP=y
> >   CONFIG_SERIAL_8250=y
> >   CONFIG_SERIAL_8250_PNP=n
> >
> > Why do you want PNP support, but not 8250_PNP support?
> 
> That's a good question :-) IIRC the serial PNP code used to mess up
> the mode of the port on my laptop, making it useless for debugging the
> boot. Bug was fixed long ago, but I didn't re-enabled that option.

It wouldn't surprise me if serial PNP can be tripped up by the
incomplete Linux PNP code or by buggy firmware.  If you find any
issues like that, I'll fix them.

> > If you turn off
> > PNP completely, you will have "pnp_platform_devices == 0", and the
> > existing code will do what you need.
> 
> Well for me it's a non-issue, I'm able to "work-around" it in many
> ways. My point is that a configuration that used to work and is still
> valid suddenly doesn't work anymore.

You're right about that, and it is a legitimate issue.  But given the
fact that (PNP && !SERIAL_8250_PNP) should be relatively unusual, my
opinion is that it's not worth extra ifdefs in legacy_serial.c.

If you have to use any workarounds like "legacy_serial.force", I think
that's a bug, and I'll fix it.

Bjorn

  reply	other threads:[~2007-07-09 18:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-07 23:33 Luca Tettamanti
2007-07-09 15:46 ` Bjorn Helgaas
2007-07-09 17:30   ` Luca
2007-07-09 18:30     ` Bjorn Helgaas [this message]
2007-07-11 19:40       ` Luca
2007-07-11 21:07         ` Bjorn Helgaas

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=200707091230.01556.bjorn.helgaas@hp.com \
    --to=bjorn.helgaas@hp.com \
    --cc=kronos.it@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@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

all inboxes | Powered by JetHome®