linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	linux-serial@vger.kernel.org
Subject: Re: 8250.c::autoconfig() fails loopback test on MPC824[15]
Date: Mon, 6 Aug 2007 21:15:34 +0200	[thread overview]
Message-ID: <e8ffca0a9f533e4685f0573e72b90239@kernel.crashing.org> (raw)
In-Reply-To: <200708051841.17471.arnd@arndb.de>

> Another option altogether would be to allow the device node to
> specify the linux specific serial port flags in a separate property,
> like "linux,uart-port-flags" that contains the same flags that
> setserial can set from user space. That would also be useful
> if you want to specify UPF_MAGIC_MULTIPLIER on certain high-speed
> ports, because it cannot be autoprobed.

Such high-speed ports should simply use a proper "compatible"
entry.  Similarly with the problem at hand.


Segher

      parent reply	other threads:[~2007-08-06 19:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-04 23:17 8250.c::autoconfig() fails loopback test on MPC824[15] Guennadi Liakhovetski
2007-08-04 23:35 ` Arnd Bergmann
2007-08-05 14:06   ` Guennadi Liakhovetski
2007-08-05 16:41     ` Arnd Bergmann
2007-08-05 21:31       ` Jon Loeliger
2007-08-05 21:39         ` Guennadi Liakhovetski
2007-08-05 21:50           ` Jon Loeliger
2007-08-05 21:57           ` Arnd Bergmann
2007-08-06 19:29             ` Segher Boessenkool
2007-08-06 19:54               ` Guennadi Liakhovetski
2007-08-06 19:15       ` Segher Boessenkool [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=e8ffca0a9f533e4685f0573e72b90239@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=arnd@arndb.de \
    --cc=g.liakhovetski@gmx.de \
    --cc=linux-serial@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.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).