linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linuxppc-dev@ozlabs.org, cbe-oss-dev@ozlabs.org,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: [RFC] powerpc: experimental of serial port driver
Date: Sat, 09 Dec 2006 07:50:04 +1100	[thread overview]
Message-ID: <1165611004.1103.35.camel@localhost.localdomain> (raw)
In-Reply-To: <1165588888.3328.8.camel@hades.cambridge.redhat.com>

On Fri, 2006-12-08 at 14:41 +0000, David Woodhouse wrote:
> On Fri, 2006-12-08 at 15:43 +1100, Benjamin Herrenschmidt wrote:
> > I'd rather call it 8250_of.c and have it be specific to 8250's.
> 
> Didn't we already do that once?

Not really, right now, we use a platform driver (though it should work,
again, I'm not completely sure why we need that at all).

legacy_serial.c should be detecting all 8250 type ports at boot, init
them, setup a udbg console for them, and later on, register them as
platform devices with the 8250 driver. The problem right now is that the
code in there will only do that for known busses, which doesn't include
opb. So we should just fix it for opb and things should work.

Ben.

      parent reply	other threads:[~2006-12-08 20:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-07 20:40 [RFC] powerpc: experimental of serial port driver Arnd Bergmann
2006-12-08  4:43 ` Benjamin Herrenschmidt
2006-12-08 14:41   ` David Woodhouse
2006-12-08 15:12     ` Arnd Bergmann
2006-12-08 20:50       ` Benjamin Herrenschmidt
2006-12-08 23:42         ` Arnd Bergmann
2006-12-09  2:13           ` Benjamin Herrenschmidt
2006-12-09 16:44             ` Sergei Shtylyov
2006-12-09 17:39               ` David Woodhouse
2006-12-08 20:50     ` Benjamin Herrenschmidt [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=1165611004.1103.35.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=arnd@arndb.de \
    --cc=cbe-oss-dev@ozlabs.org \
    --cc=dwmw2@infradead.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).